6.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet

The number of generations to be saved for a root jobnet or root remote jobnet can be set to a value from 1 to 99 (the maximum can be increased to 999). However, if an attempt is made to unregister the execution of a jobnet that satisfies either of the following conditions, the unregistration processing takes a long time:

Jobnet whose number of generations to be saved is 30 or more
Jobnet for which the number of generations to be saved is 10 or more and a start condition (LEGACY is set for the SAVEGENTYPE environment setting parameter) is used

If processing to unregister the execution of a jobnet takes a long time, the status of the start-condition monitoring of other jobnets might become Monitor terminated or execution of the jobnet might fail.

These problems occur because the unregistration mode set in the scheduler service is synchronous. If the unregistration mode is synchronous, the time required to cancel registration depends on the number of generations to be deleted. If there are many generations for which execution needs to be unregistered, a long time is required, with adverse effects on the execution of other jobnets.

To prevent these problems, change the unregistration mode to asynchronous. Note that the procedure for changing the unregistration mode to asynchronous differs depending on whether the registration information for the jobnet being executed before the mode is changed is necessary.

When JP1/AJS3 is initially installed and set up, you do not need to change the unregistration mode because asynchronous (yes) is specified for the BACKGROUNDLEAVE environment setting parameter. However, if JP1/AJS3 is installed as an upgrade installation, unregistration mode might be set to synchronous (no).

If synchronous is set for the BACKGROUNDLEAVE environment setting parameter or if BACKGROUNDLEAVE has not been set, we recommend that you change the unregistration mode to asynchronous due to the time required to unregister execution. If you change the mode to synchronous, note that registration information is deleted for the jobnets being executed before the mode is changed.

Before you change the unregistration mode of a scheduler service, make sure that the scheduler service is not running.

Use the procedures below to change the unregistration mode of a scheduler service.

Organization of this subsection

(1) Procedure for changing the unregistration mode from synchronous to asynchronous
(2) Procedure for changing the unregistration mode from asynchronous to synchronous

(1) Procedure for changing the unregistration mode from synchronous to asynchronous

The following operation is unnecessary if the BACKGROUNDLEAVE environment setting parameter is already set to asynchronous (yes).

(a) When the registration information for the jobnet that was being executed is not necessary

To change the unregistration mode from synchronous to asynchronous when the registration information for the jobnet that was being executed is not necessary:

Execute the following command to stop the scheduler service:
```
jajs_spmd_stop -n jajs_schd -F scheduler-service
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd_stop -n jajs_schd -F AJSROOT1
```
Execute the following command:
```
jajs_config -k [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service] "BACKGROUNDLEAVE"="yes"
```
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

Example:

When the scheduler service is AJSROOT1 on the JP1_DEFAULT physical host, execute the command as follows:
```
jajs_config -k [JP1_DEFAULT\JP1AJSMANAGER\AJSROOT1] "BACKGROUNDLEAVE"="yes"
```
Execute the following command to cold-start the scheduler service:
```
jajs_spmd -n jajs_schd -F scheduler-service -cold
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd -n jajs_schd -F AJSROOT1 -cold
```

(b) When registration information for the jobnet that was being executed is necessary

To change the unregistration mode from synchronous to asynchronous when the registration information for the jobnet that was being executed is necessary:

Important: You cannot use this procedure when the backup enhancement function is enabled. Use the procedure in (a) When the registration information for the jobnet that was being executed is not necessary to change the unregistration mode from synchronous to asynchronous.

Execute the following command to stop the scheduler service:
```
jajs_spmd_stop -n jajs_schd -F scheduler-service
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd_stop -n jajs_schd -F AJSROOT1
```
Execute the following command:
```
jajs_config -k [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service] "BACKGROUNDLEAVE"="yes"
```
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

Example:

When the scheduler service is AJSROOT1 on the JP1_DEFAULT physical host, execute the command as follows:
```
jajs_config -k [JP1_DEFAULT\JP1AJSMANAGER\AJSROOT1] "BACKGROUNDLEAVE"="yes"
```
Convert the information about registration for execution to asynchronous type.

Execute the following command:
```
JP1/AJS3-installation-folder\tools\ajsregcnv -F scheduler-service
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
JP1/AJS3-installation-folder\tools\ajsregcnv -F AJSROOT1
```
Execute the following command to start the scheduler service:
```
jajs_spmd -n jajs_schd -F scheduler-service
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd -n jajs_schd -F AJSROOT1
```

To Page Top

(2) Procedure for changing the unregistration mode from asynchronous to synchronous

To change the unregistration mode from asynchronous to synchronous:

Execute the following command to stop the scheduler service:
```
jajs_spmd_stop -n jajs_schd -F scheduler-service
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd_stop -n jajs_schd -F AJSROOT1
```
Execute the following command:
```
jajs_config -k [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service] "BACKGROUNDLEAVE"="no"
```
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

Example:

When the scheduler service is AJSROOT1 on the JP1_DEFAULT physical host, execute the command as follows:
```
jajs_config -k [JP1_DEFAULT\JP1AJSMANAGER\AJSROOT1] "BACKGROUNDLEAVE"="no"
```
Execute the following command to cold-start the scheduler service:
```
jajs_spmd -n jajs_schd -F scheduler-service -cold
```
Example:

When the scheduler service is AJSROOT1, execute the command as follows:
```
jajs_spmd -n jajs_schd -F AJSROOT1 -cold
```

To Page Top