4.2.3 Jobnet generation management

(a) Saved-generation management by using the total management method

With the total management method, if the number of saved generations exceeds the preset number of logs to keep, saved generations are deleted starting with the oldest generation. For monitoring generations, when the last execution generation in a monitoring generation is deleted, the monitoring generation is also deleted.

Note that if you use the total management method, you must make sure that you set the number of logs to keep to at least 2. For example, if you want at least one monitoring generation to be saved and at least two execution generations to be saved, you need to set the number of logs to keep to at least 3. If the number of logs to keep is set to 1, the execution results might be deleted when processing for saved-generation management is performed, such as when the scheduler service is started.

The following figure shows an example of total-management-method processing when Number of logs to keep is 2 and Valid range of start condition is 4 (number of times satisfied).

(b) Saved-generation management by using the individual management method

With the individual management method, the number-of-logs-to-keep setting is applied separately to monitoring generations and to execution generations. More execution generations than the number of logs to keep are saved so you must consider how many execution generations will be created by the specified start condition. If JP1/AJS3 has been upgraded from JP1 Version 8 or an earlier version of JP1/AJS2, the individual management method is still used for the management of saved generations. If you use a jobnet with a start condition, take into consideration that you will be switching to the total management method.

Note that cautionary notes apply when you increase the number of generations that will be saved for a jobnet with a start condition. These notes can be found in (4) Notes applying when JP1/AJS3 has been upgraded from JP1 Version 8 or an earlier version of JP1/AJS2.

The following shows examples of the individual management method. These examples assume that Number of logs to keep is 2, and Valid range of start condition is 4 (number of times satisfied).

• If the number of saved generations exceeds the number of logs to keep on the first day

  The following figure shows an example of processing when the number of saved execution generations exceeds the value of Number of logs to keep on the first day.

  Figure 4‒17: Example of the individual management method when the number of logs to keep is exceeded on the first day

• If the number of saved generations exceeds the number of logs to keep on the second day or later

  The following figure shows an example of processing when the number of saved execution generations exceeds the value of Number of logs to keep on the second day or later.

  Figure 4‒18: Example of the individual management method when the number of logs to keep is exceeded on the second day or later

(a) Switching from the individual management method to the total management method

The method for managing saved generations for a jobnet with a start condition is determined by the value of the SAVEGENTYPE environment setting parameter. You can use the jajs_config command to change the value of this parameter. For details about this environment setting parameter, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.

If you switch from the individual management method to the total management method, generations other than those retained by the total management method are deleted when the scheduler service starts. The time (in seconds) required for this deletion processing is proportional to the sum of number-of-logs-to-keep x number-of-logs-to-keep calculated for all registered root jobnets, but can be affected by hardware and other conditions. If the time required for the deletion processing is likely to affect operation, manually delete unnecessary generations before changing the management method. This step should reduce the time required for the scheduler service to start.

Note that generations are also deleted when a generation's registration for execution is canceled. If generations are canceled by using registration cancellation or saved-generation management in synchronous mode, the time required for deletion can be reduced by switching to asynchronous mode. Asynchronous mode is the default setting when JP1/AJS3 09-00 or a later version or JP1/AJS2 08-00 or a later version is installed as a new installation. For an upgrade installation, however, synchronous mode might be set. You can determine which deletion mode has been set by checking the value of the BACKGROUNDLEAVE environment setting parameter. If the value is no (synchronous mode) or the parameter is not specified, we recommend that you explicitly specify the value yes for the parameter to set asynchronous mode.

For details about changing the mode in Windows, see 6.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide. For details about changing the mode in UNIX, see 15.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide.

(b) Continuing operation with the individual management method

If you continue operation with the individual management method rather than switching to the total management system, the following notes, which apply for JP1 Version 8 or an earlier version of JP1/AJS2, apply.

For the individual management method, the setting of the number of logs to keep is applied separately to monitoring generations and to execution generations, as described in (3)(b) Saved-generation management by using the individual management method. The number of generations that are saved by this method is equal to number-of-logs-to-keep x (number-of-logs-to-keep + 1). The load on any database access operation, such as canceling execution registration, increases proportionately with the number of logs to keep that is set. Determine the value to be specified as the number of logs to keep after careful consideration of the possible impact on system performance. For the relationship between the number of logs to keep that is set and system performance, see 7.2 Relationship between number of logs to keep and performance in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

If you choose to use the individual management method for operation of a jobnet with a start condition, we recommend that you set the number of logs to keep to a value less than 10, and use the ajsshow command to save execution results as needed. For details about the ajsshow command, see ajsshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

You must also be careful when decreasing the number of logs to keep for a jobnet that is already registered for execution. Decreasing the number of logs to keep will render some saved generations no longer necessary, and will cause them to be deleted all at once. Their deletion occurs when the status of the next scheduled monitoring generation changes to Now monitoring, creating generations that exceed the number of logs to keep that has been set. The number of generations that will be eliminated is the value of (old-number-of-logs-to-keep - new-number-of-logs-to-keep) x (old-number-of-logs-to-keep + 1). Accordingly, if the value of Number of logs to keep is large, and monitoring generations and execution generations each equal to this value have been saved, a drastic decrease in Number of logs to keep will eliminate many generations at one time, adversely affecting operation.

The following figure explains how generations are eliminated when the number of logs to keep is decreased.

As shown in the above example, when the value of Number of logs to keep is 10 and 110 generations are saved, if the value is changed to 2, 88 generations are deleted all at once.

If you continue to use the individual management method, keep the above notes in mind.