7.1.10 Setting for disabling deletion of job information when JP1/AJS3 starts

Job information deletion processing is executed either at the base time for deleting job information, which is specified in the environment settings, or when the JP1/AJS3 service starts. When a base time is used, job information is deleted if it has been kept longer than the set number of days at the base time. When deletion is timed with JP1/AJS3 service startup, job information is deleted if it has been kept longer than the set number of days at the start time. If a failover occur in a cluster configuration while a large number of jobs are being executed, or if the JP1/AJS3 service is restarted due to a system error or other issue, job execution performance might decline due to the conflict with job deletion processing.

By using either of the following options to disable the deletion of job information when the JP1/AJS3 service starts, you can avoid conflict between deletion processing and job execution:

Delete expired job information when JP1/AJS3 starts, using the base time as the reference point

When you use this option, job information that has been kept longer than the set number of days at any point between the base time and start time is not deleted when the JP1/AJS3 service starts. However, if the JP1/AJS3 service was stopped at the previous base time and deletion processing was not performed, expired job information might still remain in the database. Only this expired job information will be deleted the next time JP1/AJS3 starts.

By electing to delete expired job information at the base time without stopping the JP1/AJS3 service, you can prevent job information from being deleted when the JP1/AJS3 service starts.
Disable deletion of job information when JP1/AJS3 starts

This option disables deletion of job information when the JP1/AJS3 service starts.

When you resume JP1/AJS3 operation after a long period of inactivity, there might be a large amount of expired job information to be deleted. In this case, the successive I/O requests generated by the deletion process on ISAM files when the JP1/AJS3 service starts could slow the execution of jobs immediately after service startup.

With this option set, job information is deleted only at the base time, not at service startup. This prevents adverse effects on the execution performance of jobs executed immediately after the JP1/AJS3 service starts. Do not use this option, however, if your system is set up to stop the JP1/AJS3 service at the base time for deleting job information.

If you use this option with the JP1/AJS3 service set to stop at the base time for deleting job information, expired job information will accumulate over time, and the job execution environment database will occupy more and more space on the disk. An increase in the disk space occupied by the job execution environment database can have various effects, including preventing the JP1/AJS3 service from starting and jobs from being executed, and can even affect programs other than JP1/AJS3.

The following describes how to disable deletion of job information at JP1/AJS3 service startup when the retention period for job information is set as one day or longer.

Organization of this subsection

(1) Setting procedure
(2) Environment setting parameter
(3) Setting for disabling deletion of job information when JP1/AJS3 starts and its effects

(1) Setting procedure

Stop JP1/AJS3.

In Windows:

From Administration Tools in the Windows Control Panel, choose Services and stop the following service:

- JP1/AJS3 service

In UNIX:

Execute the following commands to stop the JP1/AJS3 processes and to check that all processes have stopped:

# /etc/opt/jp1ajs2/jajs_stop^#1

# /opt/jp1ajs2/bin/jajs_spmd_status

#1

First check whether the JP1/AJS3 processes are set to stop automatically.
Execute the following command to set the environment setting parameter described in (2) below.
```
jajs_config -k definition-key-name "environment setting parameter-name"=definition-contents
```
Restart JP1/AJS3.

The setting takes effect.

To Page Top

(2) Environment setting parameter

Table 7‒7: Environment setting parameter for disabling deletion of job information when the JP1/AJS3 service starts
Definition key	Environment setting parameter	Definition contents
`[{JP1_DEFAULT\|logical-host-name}\JP1NBQMANAGER\Database]`^#	`"StartUpDelete"=`	Setting to disable the deletion of job information at JP1/AJS3 service startup

#: In the portion {JP1_DEFAULT|logical-host-name}, specify JP1_DEFAULT for the physical host, or logical-host-name for a logical host.

For details about what is defined in this environment setting parameter, see 20.5.2(9) StartUpDelete in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

(3) Setting for disabling deletion of job information when JP1/AJS3 starts and its effects

The following table shows the relationship between the disabling deletion of job information when JP1/AJS3 starts, and whether deletion processing is performed.

Table 7‒8: Relationship between the setting for disabling deletion of job information when JP1/AJS3 starts, and whether deletion processing is performed
Setting for disabling deletion of job information at JP1/AJS3 startup	Deletion of job information at JP1/AJS3 startup	Time for deleting job information
`0`	Yes^#	Base time
`1`	Yes	Start time of JP1/AJS3 service
`2`	No	--

Legend:

Yes: Deletion processing is performed.

No: Deletion processing is not performed.

--: Not applicable.

#

Job information is not deleted when the JP1/AJS3 service starts if deletion took place at the preceding base time.

To Page Top