6.1 Status levels of jobnets, jobs, and jobnet connectors
The following table lists the statuses that apply to jobnets, jobs, and jobnet connectors.
- Legend:
-
Root : Root jobnet
Nested : Nested jobnet
Y : Displayed.
N : Not displayed.
-- : Not applicable
- #1
-
If you execute the ajsshow command to display the status, an -R mark, indicating rerun, is added to a unit that meets one of the following conditions:
-
A unit that was rerun in a rerun operation
-
A jobnet that contains a unit that was rerun
-
A unit operating after the rerun in the root jobnet that contains rerun units
An -R mark is not added to a nested jobnet that is already in the Now running status when the rerun starts or to units included in that nested jobnet. If you rerun only specific units by specifying the Only this unit option, the -R mark is not added to succeeding units because they are not included in the rerun.
For the ajsshow command syntax, see ajsshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
-
- #2
-
This status includes cases in which a jobnet generation whose start time has arrived or a re-executed jobnet generation is waiting for another jobnet generation that is being executed when concurrent execution for the jobnet is disabled. It also includes cases in which the execution suppression function is suppressing the start of jobnet execution.
- #3
-
For the Not executed + Ended and Skipped so not exe. status levels, you can distinguish between units that are scheduled and not scheduled in JP1/AJS3 - View by displaying them with different colored icons. This is not possible when the status name is only displayed in text format, or in the command output.
A jobnet becomes scheduled when an execution schedule (scheduled start time) has been set but the jobnet has not yet been executed. If no execution schedule has been set, the status of the job is not scheduled.
A job becomes scheduled when an execution schedule (scheduled start time) has been set for an upper-level jobnet, and the job has not been prohibited. In all other cases the job has not scheduled status.
In JP1/AJS3 - View, you can set different colors for the scheduled and not scheduled statuses using the General page in the Preferences dialog box. For details, see 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide and 12.3.44 Select Color dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.
By using the Web GUI (Job Portal), you can set different colors for the scheduled and not scheduled statuses by using the display color settings file (ajs3web_color.conf). For details, see the section corresponding to the OS. For Windows, see 3.4.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
- #4
-
All nest jobnets or remote jobnets that are subordinate to a jobnet that has been placed in the Skipped so not exe. status are placed in the Skipped so not exe. status regardless of whether they have been scheduled. The jobs in those jobnets are placed in the Not executed + Ended status.
However, in the case where no start conditions are used, when the root jobnet is placed in the Skipped so not exe. status, the event job defined as a start condition enters Bypassed.
- #5
-
The jobnet is placed in the Not executed + Ended status even when the upper-level jobnet has been placed in the Skipped so not exe. status.
- #6
-
The next execution schedule is also placed in the Skipped so not exe. status. If successive generations are placed in this status, only the generation whose start time is closest to the current time remains. However, this does not apply when successive execution generations of a jobnet with a start condition are placed in the Skipped so not exe. status.
- #7
-
A jobnet with a timeout period of one day is still placed in Skipped so not exe. status if it is registered for execution immediately before the base time and the timeout period elapses before the jobnet is executed.
- #8
-
Abnormal termination shown here indicates one of the following abnormal termination statuses (Not executed + Ended is not included, which indicates that the unit was not executed):
-
Ended abnormally
-
Interrupted
-
Invalid exe. seq.
-
Killed
-
Failed to start
-
Unknown end status
-
Skipped so not exe.
-
- #9
-
This status might only be displayed for a start condition (.CONDITION) or for a jobnet for which a start condition is defined. The Interrupted monitoring status might also be displayed for an event job defined in the start condition.
- #10
-
The status of units that belong to a root jobnet is Not executed + Ended.
- #11
-
Abnormal end is one of the following statuses:
-
Ended abnormally
-
Not executed + Ended
-
Interrupted
-
Invalid exe. seq.
-
Killed
-
Failed to start
-
Unknown end status
-
Skipped so not exe.
-
- #12
-
For details, see 2.2.4(4) Transitions of jobnet connector and connection-destination jobnet statuses in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
- Supplementary notes
-
-
JP1/AJS3 - View includes a function for displaying a colored icon (yellow by default) for waiting units for which a hold attribute has been set. The color of the icon indicates the hold plan for the unit. Waiting units are those with statuses such as Waiting for start time, Waiting for prev. to end, Waiting to execute and Wait for start cond. In JP1/AJS3 - View, you can access the function for displaying a hold plan in the Preferences dialog box. For details about accessing this function, see the description of the General page in 12.3.42 Preferences dialog box in the JP1/Automatic Job Management System 3 Operator's Guide. You must be running JP1/AJS - Manager and JP1/AJS - View version 06-71 or later to use this function.
If you use the function for displaying a hold plan in the Web GUI (Job Portal), specify the necessary settings in the display color settings file (ajs3web_color.conf). For details, see the section corresponding to the OS. For Windows, see 3.4.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.
-
At termination of a preceding unit that belongs to a Wait for prev. to end jobnet for which the hold attribute is set, the succeeding jobnet moves from Wait for prev. to end to Wait for start time status, and then to Being held status.
-
In JP1/AJS3 - View or JP1/AJS2 - View version 08-50 or later, you can set a filter so that Waiting to execute units for which the hold attribute is set will be included in listings of Being held units in the Monthly Schedule window or Daily Schedule window. To include Waiting to execute units that have the hold attribute in listings of Being held units, in the Filter Settings dialog box select the Being held status includes hold plan check box. For details, see 12.7.11 Filter Settings dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.
-
The scheduled end time for a jobnet or job is displayed together with the execution status. The scheduled end time is calculated based on the average execution time of the job or jobnet in the past (the average processing time of the job or jobnet when it ended normally). For details, see 4.4.2(2) Execution simulation. The actual time taken for a job or jobnet to execute depends on system conditions such as the CPU utilization at the time. The scheduled start time and the scheduled end time are therefore intended only as guidelines.
-