3.4.4 Concurrent execution of execution generations
If a start condition is satisfied when a monitoring generation is in the Now monitoring status and an execution generation is in the Now running status, a new execution generation is generated. The behavior of the execution generation depends on whether concurrent execution is enabled or disabled. The following figure shows the behavior according to the concurrent execution setting.
|
|
![[Figure]](GRAPHICS/ZUF03620.GIF)
-
When concurrent execution is enabled
An execution generation is executed every time the start condition is satisfied, even if the previous execution generation is still in progress.
-
When concurrent execution is disabled
If the start condition is satisfied when no execution generation is running, the execution generation is executed. If the start condition is satisfied while the execution generation is running, the next execution generation waits until the current execution generation ends#.
- #
-
When an execution generation is running, you can change the status of the next generation to Skipped so not exe. without waiting for the current execution generation to end. To do this, open the Define Details - [Start Condition] dialog box, and select Does not stay with skip in the Pause exec. gen. for start cond. area. For details, see 3.4.6 Retention of execution generations with satisfied start conditions.
To enable the concurrent execution of execution generations, use the Define Details - [Jobnet] dialog box (for a root jobnet) or the Define Details - [Remote Jobnet] dialog box (for a root remote jobnet). For details, see 12.3.8 Define Details - [Jobnet] dialog box (for a root jobnet) in the JP1/Automatic Job Management System 3 Operator's Guide or 12.3.10 Define Details - [Remote Jobnet] dialog box (for a root remote jobnet) in the JP1/Automatic Job Management System 3 Operator's Guide.