7.4 Resubmitting jobs when a JP1/AJS3 service is restarted

Job execution control manages the following information required for job execution in memory until jobs are distributed to the execution agent:

• Execution agent name set in the upper-level jobnet

• Priority set in the upper-level jobnet

• Return code of the preceding job

• End status of the preceding job

• Job definition information

If a JP1/AJS3 service stops before jobs are distributed, the information required for job execution is deleted from memory. When the JP1/AJS3 service is restarted in hot-start mode, jobs that were queued at the moment the service stopped are canceled and returned to Wait for prev. to end status. The jobs are then automatically submitted again to ensure continued jobnet operation. This sequence of operations is called resubmitting jobs.

When a job is canceled, the KAVS0266-I message is output. Job execution control deletes the canceled job from the queue and returns the job to Wait for prev. to end status. When the job is resubmitted, the job status changes to Waiting to execute, and then to Now queuing. However, if a previous unit has terminated abnormally, the job is not resubmitted, and instead its status changes to Not executed + Ended.

The following figure shows how a job is resubmitted when the JP1/AJS3 service is restarted in hot-start mode.

Figure 7‒3: How a job is resubmitted when the JP1/AJS3 service is restarted (hot start)

When the service is restarted in warm-start mode, the job status changes to Not executed + Ended. When the service is restarted in cold-start mode, the job status changes to Not registered.

To Page Top