7.3.8 Using the jobnet release function

This subsection describes the basic operation cycle for using the jobnet release function and the recommended methods of operation.

Organization of this subsection

(1) Basic operation cycle
(2) Redoing registration of a jobnet-definition release
(3) Recommended methods of operation
(4) Other methods of operation
(5) When a release is registered or canceled within one day of the release time
(6) When a jobnet is registered for execution within one day after the release time

(1) Basic operation cycle

The following figure shows the basic operation cycle for using the jobnet release function.

Figure 7‒14: Basic operation cycle for using the jobnet release function

In this example, jobnet A-00, which is used for development, has the same definition contents as the jobnet A in the production environment. When the jobnet release function is used to switch the jobnet A definition, a copy of jobnet A-00 is edited and tested as jobnet A-01 ((1) in the figure). Next, the release is registered ((2) in the figure). In this process, the definition of release-source jobnet A-01 is copied to the production environment, and managed as one of the definitions of release-target jobnet A. If you then edit the definition of the release-source jobnet after the jobnet-definition release has been registered, the release-target jobnet will not be affected.

The following operational points must be considered:

Managing the master jobnet definition

The release-source jobnet is the master jobnet when you change the release-target jobnet definition. If necessary, create an archive for the release-source jobnet definition.
Periodically deleting unnecessary execution result generations

Jobnet definitions in the Applied status are automatically deleted the next time

a jobnet-definition release is registered unless a generation is created from that jobnet definition. However, a jobnet definition from which a generation has been created is not deleted. You should therefore consider deleting unnecessary execution-result generations by canceling registration of the generations before you register a release.

Even after registering a jobnet-definition release, you can still edit the release-target jobnet definition by using JP1/AJS3 - View and commands. The edited jobnet definition is applied to the jobnet definition whose status is Being applied. Note, however, that information such as execution-result details cannot be retained because the edited jobnet definition is also applied to the generations created according to the release-target jobnet definition. Therefore, consider always using the basic operation cycle except in case of an emergency.

To Page Top

(2) Redoing registration of a jobnet-definition release

If you need to further edit a jobnet definition after it has been registered for release, you can redo the registration. To redo a release registration, cancel the release, edit the jobnet definition, and then re-register the jobnet-definition release. The following figure shows an example of redoing registration of a jobnet-definition release.

Figure 7‒15: Operation for redoing registration of a jobnet-definition release

In this example, because editing of the jobnet definition is required after the jobnet-definition release has been registered, the release with the release ID A-01 is canceled ((1) in the figure). Next, the development version of jobnet A-01 is re-edited and tested again ((2) in the figure), after which the release is registered again ((3) in the figure).

To Page Top

(3) Recommended methods of operation

The following describes the recommended methods for using the jobnet release function.

(a) General method of operation

Because a jobnet with a definition in the Release wait status cannot be registered for release, multiple jobnet definitions (for example, definitions for August and September) cannot be registered for release at one time. Therefore, after you have registered a release, wait until the jobnet definition you registered for release is switched into operation (status changes to Being applied), and then registered the next jobnet definition for release. At this point, consider registering the release at least one day before the release time to allow extra time as a safety period, as shown in the following figure.

Figure 7‒16: Recommended method for using the jobnet release function

(b) Operation when the execution order control for root jobnets is used

Execution order control for root jobnets connects a jobnet connector and a connection-destination jobnet if they have the same execution date. However, because they are connected while both are running, an attempt to register a jobnet-definition release or cancel the registration while the connection exists might cause problems. For example, a generation preceding the attempted operation might be connected, or the generation to be connected might not be found during operation processing. To prevent problems when using execution order control for root jobnets, make sure that the release registration or release cancellation operation has been completed at least four days^# before the jobnet connector and a generation of the connection-destination jobnet are to be executed.

#: This number of days is the number of days during which the execution date might be the same due to the base time or time zone setting.

Figure 7‒17: Example of operation when execution order control for root jobnets is used

(c) Operation when an execution schedule is changed by temporarily changing the plan

■ When registering a release

If you register a release for a jobnet registered for fixed execution with a period or a number of future generations specified, generations after the specified release time are re-created^# based on the jobnet definition registered for release. Any changes made by temporarily changing the plan before the release is registered are not passed to the re-created generations.

If you want to apply information about temporary changes made before release entry to the subsequent jobnet definition, use the function for re-execution of temporary changes. This function lists temporary changes made to the jobnet after it was registered for execution. From the displayed list of changes, you can then select which operations to perform again.

For details about the function for re-execution of temporary changes, see 4.5.16 Displaying and re-executing temporary change operations for a job or jobnet in the manual JP1/Automatic Job Management System 3 Overview. For details about how to check temporary changes and re-execute operations, see 9.17 Displaying and re-executing temporary changes in the JP1/Automatic Job Management System 3 Operator's Guide.

#: At this time, the following message appears: KAVS4751-W Since the new generation (execution-ID) is created to change the jobnet definition of the generation (unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.

■ When canceling a release

If you cancel the release for a jobnet registered for fixed execution with a period or a number of future generations specified, the jobnet definition generations specified for release cancellation are re-created^# for the jobnet definition whose status becomes Being applied after cancellation of the release. Information about changes made by temporary changes to the plan before cancellation of the release is not passed to the re-created generations.

Therefore, before canceling a release, use information such as the scheduler log to check the information about temporary changes to the plan performed for generations of the jobnet definition whose release is to be canceled. If necessary, redo the temporary changes to the plan for the re-created generations after the release is canceled.

#: At this time, the following message appears: KAVS4751-W Since the new generation (execution-ID) is created to change the jobnet definition of the generation (unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.

■ When an operation entails the recalculation of schedules

In addition to operations to register or cancel a release, generations are also re-created when an operation entails the recalculation of schedules^#1. Any changes made by using temporary changes to the plan before the operation is performed are not passed to the re-created generations.

Therefore, before you perform an operation that entails the recalculation of schedules, use information such as the scheduler log to check the information about temporary changes to the plan that have been performed. If necessary, redo the temporary changes to the plan for the re-created generations.

Operations that entail the recalculation of schedules are as follows:

Making temporary changes to the plan or stopping execution^#2
Changing the calendar definition to be referenced by a release-target jobnet
Changing the calendar definition to be referenced by an exclusive jobnet
Changing the base time and base day of an upper-level job group
Changing the schedule definition of a release-target jobnet
Changing the schedule definition of an exclusive jobnet
Warm-starting or disaster-recovery-starting the scheduler service
Releasing suspension
Registering or canceling a job-definition release for an exclusive jobnet

#1: At this time, the following message appears: KAVS4751-W Since the new generation (execution-ID) is created to change the jobnet definition of the generation (unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.
#2: The following message appears only if the type of execution registration is planned execution registration: KAVS4751-W Since the new generation (execution-ID) is created to change the jobnet definition of the generation (unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.

To Page Top

(4) Other methods of operation

The jobnet release function makes it possible to register a jobnet-definition release for any jobnet, thereby making possible operation that is suitable for a development environment. The following describes methods of operation when only production devices are used and when management of a master jobnet is not necessary.

(a) Operation when only production devices are used

If only production devices and no development devices are used, you can switch a jobnet definition by using the same procedure used in the basic operation cycle. After the release is registered, the release-source jobnet is managed as the master jobnet, just as in the basic operation cycle. The following figure shows an example of using only production devices.

Figure 7‒18: Example of operation when only production devices are used

Note that the above operation is also possible if the release-source jobnet and the release-target jobnet belong to the same job group.

(b) Operation when management of a master jobnet is not necessary

If management of a master jobnet is not necessary, you can edit a jobnet definition copied from the release information. Note, however, that only jobnet definitions whose status is Being applied can be copied. Therefore, in preparation for redoing a release registration, preserve the release-source jobnet until the status of the jobnet definition registered for release changes to Being applied. For example, you can use the ajsprint command to output the release-source jobnet to a file.

The following figure shows an example of operation that does not require management of a master jobnet.

Figure 7‒19: Example of operation when management of a master jobnet is not necessary

In this example, release-source jobnet A-01 is deleted after release ID A-00 is registered for release ((1) in the figure). Next, a jobnet definition is copied from the release information for jobnet A, and is edited and tested as jobnet A-01 ((2) in the figure). Finally, the release is registered.

To Page Top

(5) When a release is registered or canceled within one day of the release time

When you use the jobnet release function, we recommend that you register releases at least one day before the release time. However, in case of an emergency, you can specify a release time that is less than one day after the release is registered. Similarly, you can cancel the release of a jobnet definition in Release wait status less than one day after it has been registered.

However, you must note the following when you register or cancel a release within one day of the release time. In addition, you need to consider a method of operation that avoids registering or canceling a release in this way.

Until the processing to register a jobnet-definition release has completed, execution of generations whose start time is later than the release time is prohibited. As a result, if processing to register a release takes a long time, execution of these generations will be delayed.
Until the processing to cancel a jobnet-definition release has completed, execution of generations whose start time is later than the release time of that jobnet definition is prohibited. As a result, if release cancellation processing takes a long time, execution of these generations will be delayed.

To Page Top

(6) When a jobnet is registered for execution within one day after the release time

If you register a jobnet-definition release and then register the jobnet for execution at a time less than one day after the release time, you must take note of the schedule rules for the release-target jobnet. If you use either of the execution registration methods below, a generation is created after the base time of the day on which the jobnet is registered for execution. As a result, if you register the jobnet for execution after the release time, the scheduled generation on that day is executed with the jobnet definition whose status is Applied.

Planned execution registration
Fixed execution with a period or a number of future generations specified

The following figure shows operation when the jobnet is registered for execution at time less than one day after the release time.

Figure 7‒20: When the jobnet is registered for execution at a time is less than one day after the release time (1)

In this figure, the jobnet-definition release is registered with a release time of 15:00 on August 1 specified, and the jobnet is registered to be executed at a time that is less than one day after the release time (from 15:00 to 23:59 on August 1). At 15:00 on August 1, the status of the jobnet definition with the release ID 001 changes to Being applied. Because the jobnet is registered to be executed within one day after the release time, a scheduled generation for 00:00 on August 1 is created for the jobnet definition that has the release ID AJS_AUTO, whose status is Applied. The jobnet for the scheduled generation for 00:00 on August 1 is executed at the moment it is registered to be executed.

Consider a situation in which a jobnet definition that has the release ID 002 is registered for release after the status of the definition that has the release ID 001 becomes Being applied. If the jobnet definition that has the release ID AJS_AUTO does not have an execution result generation, this jobnet definition is deleted. Thereafter, when the jobnet is registered for execution on August 1, no scheduled generation for 00:00 on August 1 is created, as shown in the following figure, because the jobnet definition whose status is to become Being applied at 00:00 on August 1 (that is, the jobnet definition that has the release ID AJS_AUTO) does not exist.

Figure 7‒21: When the jobnet is registered for execution less than one day after the release time (2)

To Page Top