6.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. Therefore, when the JP1/AJS3 service is restarted (in hot-start mode), the jobs that were in Waiting to execute or Now queuing status when the service stopped are canceled and returned to Wait for prev. to end status. These jobs are then automatically resubmitted to continue 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]](GRAPHICS/ZJ070010.GIF)
In the case of JP1/AJS3 - Manager version 11-50 or later, not only the jobs that were in Now queuing status but also those in Waiting to execute status when the service stopped are resubmitted to continue jobnet operation. The jobs that were in Waiting to execute or Now queuing status when the service stopped are resubmitted when the service restarts. Consequently, the job execution condition developed when the service stopped might affect the job execution performance and the maximum number of concurrently executable jobs after the service restarts.
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. When the service is restarted in disaster-recovery-start mode, the job status changes to Unknown end status.