7.4 Changing the unit definition information during registration for execution

In JP1/AJS3, during registration for execution, you can change the file name, execution agent, hold attribute, and other unit definitions that are reflected on unit execution. However, depending on the type of unit for which the definition is changed and the status of the root jobnet when the definition is changed, the changes may or may not be applied to the definitions of the unit.

The following table lists whether changes are applied to the definitions based on the combination of unit type and root jobnet status.

Table 7‒2: Whether changes are applied to the definitions based on the status of the root jobnet and the type of unit
Type of unit	Status of root jobnet
Type of unit	Ended	Now running Running + Warning Running + Abend	Time-wait^#1 Wait for start cond. Holding	Time-wait^#2
Root jobnet	Y^#3	N	N	Y
Nested jobnet	Y^#3	N^#4	Y	Y
Job	Y^#3	N^#4	Y	Y

Legend:

Y: All the changes are applied to unit definitions.

N: The changes are not applied to unit definitions if the definitions are listed in Table 7-3.

#1

The next generation that is scheduled to be executed, and the generation waiting beyond its scheduled start time for the end of another generation currently being executed because concurrent execution is disabled

#2

Only the generation waiting for the start time other than the case of #1

#3

The job or jobnet is executed based on the new definitions when the generation in the Ended status is re-executed.

#4

Changes are applied to unit definitions when the following conditions are satisfied:

Definitions are changed for the unit under the nested jobnet that is not being executed.
The root jobnet containing the unit with new definitions is re-executed.
The root jobnet containing the unit with new definitions is released from suspension.
A service is restarted after unit definitions are changed.

The following table lists the unit definitions for which changes are not applied when "N" is indicated in the above table:

Table 7‒3: Unit definition information for which changes will not be applied when changed during registration for execution
Unit type	Unit definition information for which changes will not be applied
Standard jobs, HTTP connection jobs, Action jobs, Custom jobs, and Passing information setting jobs	Hold Exec. service Delayed end Time required for execution in delayed end Owner Executed by Retry on abnormal end Return code for retry on abnormal end Maximum retry times on abnormal end Retry interval on abnormal end
Event jobs	Hold Delayed end Time required for execution in delayed end
Custom event jobs	Hold Delayed end Time required for execution in delayed end Owner Executed by
Judgment jobs	Hold
Jobnets	Exec. agent Concurrent exec. (root jobnet only) Priority Schedule option (root jobnet only) Timeout period (root jobnet only) Monitor jobnet Time required for execution in monitor jobnet Hold
Remote jobnets	Target manager Concurrent exec. (root remote jobnet only) Schedule option (root remote jobnet only) Timeout period (root remote jobnet only) Monitor jobnet Time required for execution in monitor jobnet Hold
Start condition	Concurrent exec. of monitoring gen. Pause exec. gen. for start cond. Task after abend

For all the unit definition items other than those listed above, changes will be applied. If you want to apply the changes for the items listed above even when they were changed during registration for execution, you must perform an additional operation. For details about the operation, see 7.4.2 Applying the unit definition information changed during registration for execution.

Cautionary note: You can specify settings so that changes made to the unit definition information during registration for execution are applied. However, for the items Timeout period, Pause exec. gen. for start cond., and Task after abend, such changes will not be applied regardless of the specified settings. To apply changes for these items, cancel the execution registration, and then re-register the execution.

The following table lists the timing of reloading (applying) the latest definition information when the setting that applies unit definition information that has changed during execution registration is specified.

Table 7‒4: When the latest definition information is reloaded
Unit type	When the latest definition information is reloaded
Jobs (standard jobs, HTTP connection jobs, event jobs, custom event jobs, action jobs and custom jobs)	Immediately before the jobs wait for execution
Jobnets	Immediately before the jobnets are executed

By changing the definitions before jobs and jobnets are executed, you can execute jobs and jobnets with new definitions.

Cautionary notes

Changes to the definition of an event job and a custom event job in Now running status (including an event job and a custom event job defined as a start condition) do not take effect until the job is in Ended status. If you want to monitor the job with the changed definition contents, place the job in Ended status as follows, and then register the job again:

Event job and custom event job

Kill the job or terminate the job by changing its status.
Jobnet with a start condition

Kill the jobnet as described in 8.1.1 Stopping a jobnet that is monitoring start conditions.

Organization of this section

To Page Top