Job Management Partner 1/Automatic Job Management System 3 Overview

3.3.3 Concurrent execution and schedule option

The Concurrent exe. and Schedule option settings determine how the system handles execution schedules when a jobnet with a set processing cycle fails to complete before the start time of the next run. You can enable or disable concurrent execution, and set a schedule option, separately for each root jobnet.

Organization of this subsection

(1) Concurrent execution

(2) Schedule option

(1) Concurrent execution

Concurrent execution means running multiple instances of the same jobnet at the same time. You can enable or disable concurrent execution separately for each root jobnet. By enabling concurrent execution, you can start the next run of a jobnet at the scheduled time in the processing cycle, even if the previous run has not yet completed. Concurrent execution applies only when you select Multi-schedule as the Schedule option, as described below.

By enabling concurrent execution for a jobnet that has a start condition, you can run the jobnet every time the start condition is satisfied, even if earlier executions are still running. For details on start conditions, see 3.4 Defining a start condition.

(2) Schedule option

The Schedule option sets the method for determining the next execution schedule when a jobnet with a set processing cycle fails to complete before the start time of the next run.

JP1/AJS3 provides two schedule options:

Schedule skip

Multi-schedule

Schedule skip
The Schedule skip option skips execution of any jobnet whose previous run is still being processed at the start time of the next run, and instead schedules a jobnet whose previous run is already finished by the start time of the next run. A jobnet whose execution was skipped, because the previous run did not finish before the start time of the jobnet, is placed in the Skipped so not exe. status.
Note that skipping of a jobnet occurs only when the previous run was started by an execution schedule. If the previous run was started by a re-execution operation, the jobnet is executed after the re-executed run ends.

Multi-schedule
When Multi-schedule is selected, jobnet scheduling differs depending on whether concurrent execution is enabled or disabled. If you enable concurrent execution, the next run of a jobnet will be executed at the scheduled time without waiting for completion of the previous run. If you disable concurrent execution, the next run will not be executed until the previous run finishes processing.

The following figure shows how the system handles the next run of a jobnet when Schedule skip and Multi-schedule are selected.

Figure 3-37 Method of execution with 'Schedule skip' and 'Multi-schedule ' selected

When a jobnet is registered for planned execution, the time of the next execution is finalized at the start time of the previous execution. The second and subsequent executions are treated as dummy runs and are not actually scheduled. Therefore, if concurrent execution is disabled and Multi-schedule is selected, a jobnet registered for planned execution will be handled as follows when two or more runs of the jobnet are due to start during execution of the previous run. For details about registration for planned execution and dummy schedules, see 4. Executing an Application.

Figure 3-38 Two scheduled jobnet runs held over

The system schedules the jobnet for 8/2 when the jobnet scheduled for 8:00 on 8/1 has started execution. Because Multi-schedule is set and concurrent execution is disabled, the 8/2 jobnet does not start until the 8/1 jobnet has completed. Similarly, the execution schedule (dummy run) set for 8:00 on 8/3 should be scheduled when the 8/2 jobnet starts execution, but because the 8/1 jobnet does not complete until after 8:00 on 8/3, this dummy run is effectively skipped.

Supplementary note

You can also set Concurrent exec. and Schedule option for a root jobnet in a planning group.

[Contents][Back][Next]

[Trademarks]