4.5.4 Executing a registered jobnet immediately
Immediate execution generates an execution schedule defined for the current time and runs the registered jobnet immediately. This operation is available for root jobnets registered for planned execution, and for jobnets that are registered for fixed execution and are scheduled for the next execution.
When you immediately execute a root jobnet that is scheduled for the next execution, you can choose to either leave the next execution schedule intact (Also in next schedule), or cancel it (Not in next schedule).
When you try to immediately execute a nested jobnet, if the upper-level jobnet does not have an execution schedule, the nested jobnet is not executed. The nested jobnet is not executed until the upper-level jobnet is executed.
When a root jobnet is executed immediately, whether the lower-level nested jobnets are executed depends on the method of execution specified when the root jobnet was registered, as follows:
- Immediate execution of a root jobnet registered for planned execution
-
Execution schedules are generated for the nested jobnets.
- Immediate execution of a root jobnet registered for fixed execution
-
Execution schedules are not generated because with the fixed execution method the schedule is preset.
The scheduled start time of the nested jobnets is adjusted so that they execute within 48 hours of the base time on the day that the root jobnet is scheduled to run.
If immediate execution is performed for a jobnet linked with lower-level jobnets#, the start time of each jobnet that belongs to the selected jobnet also changes accordingly.
- #
-
For JP1/AJS3 - View, this applies when the Change date and time of all lower jobnets check box is selected, and immediate execution is performed by selecting Execute Immediately from Change Plan. For a command, this applies when immediate execution is performed by executing the ajsplan command with the -i option specified.
- Cautionary note
-
An immediately executed root jobnet runs at the point in time that immediate execution is performed, even if it was defined using a 48-hour schedule. For example, if a jobnet due to start at 34:00 on August 1 is executed immediately at 8:00 on August 2, it will be executed as of 8:00 on August 2, not as of 32:00 on August 1.
The following figure shows an example of a jobnet definition. The example is used to explain operation of immediate execution performed for a jobnet registered for planned execution or fixed execution when the current time is 12:00 on August 1.
-
When the root jobnet is executed immediately
When the root jobnet is executed immediately, changes to the execution schedules of the lower-level nested jobnets depend on the method of execution specified when the root jobnet was registered, as follows:
-
Root jobnet registered for planned execution
The following figure shows how the time changes if the root jobnet registered for planned execution is executed immediately.
Figure 4‒32: When the root jobnet registered for planned execution is executed immediately
For root jobnet A, a schedule for execution at 12:00 on August 1 (8/1) is created. Root jobnet A is executed immediately based on this schedule.
Nested jobnet B is not executed because it has not been scheduled for execution on August 1 (8/1).
For nested jobnet C, the start day for the schedule definition is the registered day and overlaps the execution date of root jobnet A that is executed immediately. Therefore, a schedule for execution at 15:00 on August 1 (8/1) is created for nested jobnet C, and nested jobnet C is executed based on this schedule.
Nested jobnet D is not executed because it has not been scheduled for execution on August 1 (8/1).
If you want to execute nested jobnets B and D, select nested jobnets B and D, and execute them immediately before immediately executing the root jobnet.
-
-
Root jobnet registered for fixed execution
The following figure shows how the time changes if the root jobnet registered for fixed execution is executed immediately.
Figure 4‒33: When the root jobnet registered for fixed execution is executed immediately For root jobnet A, a schedule for execution at 12:00 on August 1 (8/1) is created. Root jobnet A is executed immediately based on this schedule.
For nested jobnets B and C, no execution schedule is created. However, because the time adjustment for root jobnet A is within 48 hours of the base time, execution of these nested jobnets is rescheduled for the last date and time (23:59:59 on August 2 (8/2)).
Nested jobnet D is not executed because it has not been scheduled for execution on August 1 (8/1).
If you want to execute nested jobnet D, select nested jobnet D, and execute it immediately before immediately executing the root jobnet.
-
When a root jobnet linked with lower-level jobnets is executed immediately
The following figure shows how the time changes if the root jobnet registered for planned execution or fixed execution is immediately executed with lower-level jobnets linked.
Figure 4‒34: When a root jobnet linked with lower-level jobnets is executed immediately For root jobnet A, a schedule for execution at 12:00 on August 1 (8/1) is created. Root jobnet A is executed immediately based on this schedule.
The start times of nested jobnets B and C are moved back in proportion to the time difference between the start time of root jobnet A and the current time. In the above figure, the execution time of root jobnet A changes by 46 hours. Accordingly, execution of jobnets B and C is rescheduled for 17:00 on August 1 (8/1), which is 46 hours earlier than the time they were originally scheduled.
Nested jobnet D is not executed because it has not been scheduled for execution on August 1 (8/1).
If you want to execute nested jobnet D, select nested jobnet D, and execute it immediately before immediately executing the root jobnet.
You can perform this operation using either the GUI, or the ajsplan command. For details on using the GUI, see 9.4 Immediately executing the execution schedule of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide. Alternatively, for details on the ajsplan command, see the description of ajsplan in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.