Job Data (ttaad5500m000)

Use this session to view the job data, which you can maintain and display in the Job Data (ttaad5100s000) session.

From this session, you can start the Sessions by Job (ttaad5501m000) session to view or maintain the settings of the sessions linked to the job.

You can also use the Job Data (ttaad5500m000) session to start the job.

How you start the job depends on the job’s status:

  • If the job’s status is Free, you can start the job in the following ways:
    • Use the Activate Job (ttaad5203m000) session. You can start this session from the appropriate menu in the Job Data (ttaad5500m000) session.
    • Use the rc.startjob shell command (UNIX platform)
    • Use the startjob.bat batch file (Windows platform)
  • If you want the LN Job Daemon to start the job, you must change the job’s status to In Queue. Before you set the status to In Queue, make sure that all sessions have been added to the job (at least one session must be in the job). If the Job Daemon is already running, the job will be active as soon as the job status changes to In Queue and the record is saved.
Note: 
  • To change the job status to In Queue, click Queue Job on the appropriate menu in the Job Data (ttaad5500m000) session. For more information about job statuses, see the online help of the Status field.
  • The user who created the job is the owner of the job. Other users, except super users, cannot modify the job.

With the commands on the appropriate menu, you can start sessions to do the following:

  • View or maintain the settings of the sessions linked to a job
  • Activate a job
  • Put the job in a queue
  • Block a job
  • Cancel a job
  • Release a job

Field Information

Job

The job identification code.

User

The LN user ID of the person who created the job.

Note: The user who created the job is also the owner of the job. Only this user, and super users, can modify the job.
Periodical

If this check box is selected, the job is periodical: the job is started or restarted periodically at a date and time defined in the job calendar or by a regular interval.

Suspend Job Until Next Execution

Indicates whether the periodical job must be executed automatically after last execution. After execution of a periodical job, the next execution date is automatically updated according to the given period and/or calendar date.

If this check box is selected,, the job is suspended until the next execution date. For jobs started by the Activate Job (ttaad5203m000) 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 next execution date that is defined in the calendar or by the interval.

If this check box is cleared, the job runs once and is then stopped. For jobs started by the Activate Job (ttaad5203m000) 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 Activate Job (ttaad5203m000) session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat.

Note: You can use the Job Data (ttaad5100s000) session to select or clear this check box.
Use External Schedule

If this check box is selected, an external job scheduler, such as Maestro from UNISON, or an external program, for example, a UNIX crontab starts the job. Therefore, in that case, the calendar/time schedule in the job data is ignored.

Planned Execution

The date/time of the planned execution of the job. If the job is periodical, this field shows the next date of the calendar or the date corresponding to the given period, after executing the job.

Note: You can specify the dates and times for a calendar in the Dates by Calendar (ttaad5107m000) session.
Last Execution Date

The date on which the job was last executed.

Status

Displays the status of the job.

Allowed values

Free

The job’s basic data is defined and the job is ready to be started.

You can start the job in the following ways:

  • Use the Activate Job (ttaad5203m000) session.
  • Use the rc.startjob shell command (UNIX platform)
  • Use the startjob.bat batch file (Windows platform)
Running

The job is started and is running.

Waiting

The job is started and is waiting to be carried out at the next execution date and time.

Note: A job with the Waiting status will not be started by the job daemon: the Job Daemon only starts jobs with the In queue status.
In queue

The job is queued and will be started automatically when the job daemon runs.

To queue a job, use the Queue Job command in the Job Data (ttaad5500m000) session.

Blocked

The job is blocked and cannot be started.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

Canceled

The job has been stopped with the Cancel Jobs (ttaad5204m000) session. A job is also canceled when the Maximum Duration is exceeded.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

Runtime error

This status signals an error during the execution of the job. You can use the Print Job History (ttaad5411m000) session to print the corresponding error messages.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

Linked to Job Group

If this check box is selected, the job is linked to a job group, see the Job Groups (ttaad5140m000) session.

Last Date Session Added

The last date and time a session was added to the job.

When a session is added, the existing history records become useless for the calculation of the expected duration of the job.

After the job is executed again, the expected duration is recalculated. Only history records that include the new session are used in the calculation. Older records are ignored.

Related topics