Job data procedure

After completing the procedure, a job is ready to be started.

No prerequisites are required for the environment.

Before you can use periodical jobs in LN, you must define the basic job data. In LN, you can start periodical jobs according to a schedule that is defined in the job calendar, a regular interval or using job scheduling lines. You can define the interval in the basic job data. After you define the basic job data, you can add sessions and shell commands to the job. The default settings of the sessions in the job can be maintained, when required, with an optional step in the procedure.

  1. Create a job calendar.

    To start periodical jobs, you can use a job calendar. The job calendar contains the dates and times the job must be carried out.

    See the session.

  2. Specify the dates in a job calendar.

    In the job calendar, you must define the date and time that the job must be started.

    See the session.

  3. Define the basic job data.

    First define the basic parameters for the job, before you can add sessions to a job with the session. You can make a periodical job non-interactive. To start the job, specify a predefined job calendar, a regular interval or scheduling lines in these sessions:

    If you select the Suspend Job until Next Execution check box, the job is suspended until the next execution date. When jobs are started by the session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Waiting. The job is automatically restarted at every subsequent execution date that is defined in the calendar.

    If you clear the Suspend Job Until Next Execution check box, the job is carried out once and then terminated. When jobs are started by the session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Free. To restart the job, you must manually start the session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat.

  4. Add sessions to a job.

    A job must contain one or more sessions. These sessions must be carried out according to the data that is specified in the session. Typically, a job starts print or process sessions.

    Under Error Handling, you can specify how LN must continue if an error occurs during the execution of the session. You can, for example, indicate that LN must execute, or skip, several sessions of the job if an error occurs during the execution of the session.

  5. Optionally, add a shell command to the job.

    You can use this session to link the job to a shell command to a job to manipulate the command’s execution. To ensure that the shell command has the correct effect on the job, you must test the script. Typically, to test the job and shell script, you can redirect the output to a file or printer. You can redirect the output to a file or printer with one of the operating system's output redirection facilities.

    See the session.

  6. Change the default settings of the sessions in the job.

    This procedure is optional, and you can use this procedure to change the settings of the sessions that are linked to the job. For example, you can change the execution order of the sessions or the device to which the output of a session is sent.

    See the session.