3.4.2 Monitoring generation and execution generation
When a jobnet with a start condition is executed, two types of generations are generated: a monitoring generation, which controls monitoring for the occurrence of an event, and an execution generation, which waits for the occurrence of the event. When the event being monitored occurs, the start condition is satisfied and the execution generation is executed.
The following figure shows the monitoring generation and the execution generation.
|
When a jobnet with a start condition that has been registered for execution starts at the start time specified for a schedule rule, a monitoring generation in the Now monitoring status and one or more execution generations in the Wait for start condition status are generated.
If an event occurs and the start condition is satisfied, the execution generation in the Wait for start condition status is placed in the Now running status, and a new execution generation with the Wait for start condition status is generated.
Note that when monitoring terminates, the monitoring generation in the Now monitoring status is placed in the Monitor-end normal status. If the condition has not been satisfied before the monitoring terminates, the generation is placed in the Unmonitored + Ended status. If an error occurs in a monitoring generation in the Now monitoring status, the execution generation is not executed even when the start condition is satisfied, but is instead placed in the Ended abnormally status.
You can check these statuses from the Daily Schedule window or the Monthly Schedule window.
- Cautionary note
-
To monitor multiple conditions by using an AND condition, make sure that only specific events occur in succession.
If only particular events occur consecutively, multiple execution generations are generated with the Wait for start cond status. For example, assume that you have defined a start condition by combining the file monitoring job and JP1 event reception monitoring job by the AND operator. In this case, if only the file update event occurs in succession, jobnet execution generations waiting for the JP1 event received event in the Wait for start cond. status are generated as shown in the following figure.
Figure 3‒47: Example when a specific event occurs in succession for a jobnet whose start condition consists of events combined by the AND operator If a large number of execution generations are generated, performance might be affected.
Additionally, note that the maximum number of execution generations that can be retained by a single monitoring generation is 7,680. If the number of execution generations exceeds 7,680, all monitoring generations are placed in the Monitor terminated status.
- Supplementary note
-
If a jobnet with start conditions is executed with a hold attribute defined or is registered for immediate execution by setting a hold attribute, only monitoring generations of the jobnet are placed in the hold status. When these generations are released from the hold, monitoring restarts.