The following describes the status and actions of job nets registered in the Jobscheduler.
The job net status is any of the following. The display color is the Gantt chart color in which the status is displayed in the Gantt Chart window.
Completed
Displayed in blue.
The job net is considered to be completed when all the jobs have been normally completed. For the normal end of a job status, see "14.1.1 Job Status".
Abended
Displayed in red.
The job net is considered to be abended when a job belonging to the job net has been abnormally terminated and the job net has been terminated. The following shows an example.
Cancelled
Displayed in yellow.
The job net is considered to be cancelled when the user has executed the cancel operation to the executing job nets or the job nets in the warning status which include cancelled jobs.
The job net is also considered to be cancelled when the user has executed the cancel operation to a job belonging to the job net and the job net has been terminated. The following shows an example.
Warning
Displayed in brown.
The job net is considered to be warning when the job net includes any abended or cancelled job, and a job is in execution on another route.
Note
The status of the job net will continue to be warning even if there are no longer any abended jobs in the job net as a result of the abended jobs being restarted. When the job net completes, the status display will return to the normal status display (such as completed or pseudo-normal).
Executing
Displayed in green.
The job net is considered to be executing when the job net is in execution. In other words, when jobs belonging to the job net is in execution.
The job net is also considered to be executing when the user has executed the pause operation to a job belonging to the job net and the job has been paused.
Waiting
Displayed in pink.
The job net is considered to be waiting when the job net has been scheduled for execution for the current day.
Paused
Displayed in orange.
The job net is considered to be paused when the user has executed the pause operation.
If the execution conditions are satisfied while the job net is being paused, the job net will be started after resuming. If the execution conditions for the job net are satisfied for the second time while the job net is being paused, the execution reject message "refused" will be output to the log file jobdb*.log and the job net with the second execution conditions will not be executed. The first job net will be executed upon resuming.
Disabled
Displayed in gray.
The job net is considered to be disabled when the user has executed the disable operation.
If the startup time comes while the job net is in the disabled status, it will be skipped and will be in the pseudo-normal status. When the next startup schedule exists for the day, the job net will be in the waiting status. If the next startup time comes while the job is in the disabled status, the job net will be skipped at every startup time and will be in the completed status after the enable operation.
If the job net has been registered as a job in another job net, it will be skipped and the status will be pseudo-normal after the preceding job, child job net, or linked job net completes. The succeeding job, child job net or linked job net will then be executed.
If the disabled job net belongs to a group, the disabled job net will be skipped and be in the pseudo-normal status upon completion of the preceding job. The succeeding job will be executed continuously.
Confirmed
Displayed in dark blue.
The job net is considered to be checked when the user has executed the confirm operation to the abended job nets (including cancelled job nets when Check canceled Option is checked in the Define Jobscheduler Startup Parameters window) while the confirm operation is enabled.
If the Validate job net confirmation check box is selected in the Advanced Settings for Verification window (which is displayed by clicking the Advanced Settings button in Verification at error occurrence in the Use function1 sheet of the Define Jobscheduler Startup Parameters window), abended job nets will not start until the confirmation process is complete, even if the subsequent startup conditions are satisfied. Also, the job net will not be displayed in the startup schedule for the day even after the day change time.
By coping with abended job nets and executing the confirm operation, the job net will be executed when the execution conditions are satisfied as scheduled.
Pseudo-normal
Displayed in light blue.
The job net is considered to be pseudo-normal when all the executable jobs have been completed and pseudo-normal jobs and completed jobs or only pseudo-normal jobs exist in the job net.
Start Delayed
Displayed in pink in the time chart, which is the same as waiting status. Displayed with dot arrow in pink rectangle in the status field.
The job net is considered to be start delayed when the job net remains the waiting condition after the scheduled startup date and time. When the job net is started while in the start delayed status, the job net will be in the executing status.
End Delayed
Displayed in green in the time chart, which is the same as executing status. Displayed with a dot arrow in green rectangle in the status field.
The job net is considered to be end delayed when the job net does not end after the scheduled end date and time. When the job net ends while in the end delayed status, the job net will be in the executed status.
Carried Over
Displayed in pink in the time chart, which is the same as waiting status. Displayed with a vertical line and an arrow in pink rectangle in the status field.
When a job net scheduled to be executed on the day has not been executed even after the day change time and has not been re-scheduled, the job net is considered to be carried over. Upon the day change time, the status changes from start delayed to carried over.
The job net can be carried over only if it satisfies all of the following conditions and has not been executed beyond the day change time as no message event has occurred.
The Execution condition is set to "Execute at(run once per day)" or "Start only when message event has occurred" on the Standard information sheet of the Job Net Properties window.
The "Carry over the process regardless of the day change time" are checked on the Message sheet of the Job Net Properties window.
Not executed
Displayed in white.
The "Startup on Power-on if power is off during scheduled execution" box is unchecked on the Standard information sheet of the Job Net Properties window, and the job net was not started because the scheduled time has passed during server power-on.
Closed:
A message that is output to the event log or SYSLOG. It is not displayed in the Gantt Chart window.
The Jobscheduler service or the Jobscheduler daemon has been terminated during job or job net execution.
Refused:
A message that is output to the event log or SYSLOG. It is not displayed in the Gantt Chart window.
The execution has been refused. The scheduled job nets are not executed.
Possible causes are as follows.
When a job net was being executed or in the warning status, new startup conditions of job net were satisfied.
When new startup conditions were satisfied while a job net was in "Abended" status in an environment in which the Validate job net confirmation check box was selected in the Advanced Settings for Verification window.
When a job net was "paused," multiple startup conditions were satisfied.
Skipped:
A message that is output to the event log or SYSLOG. It is not displayed in the Gantt Chart window.
The job or job net was "disabled" when its startup conditions were satisfied and, therefore, it was not executed.
