3.2.4 Estimating disk capacity

a:

Number of job information items for QUEUE jobs and submit jobs

Use the following formula:

number-of-QUEUE-jobs-and-submit-jobs-that-are-executed-per-day x (number-of-days-job-information-retained + 1)

b:

Environment variable size specified in the job execution definition for QUEUE jobs and submit jobs (the maximum is 20 KB; 0 is set when no environment variables are used)

c:

Size of the data output to the standard error output file and the standard output file by submit jobs

d:

Maximum number of concurrently executable jobs for an agent (standard: 5)

Estimation is required only when QUEUE jobs and submit jobs are used in the standard configuration. Estimation is not required for a standard configuration without ISAM.

For the execution environment and execution logs for QUEUE jobs and submit jobs, estimate the disk space requirements for the database directory in the execution environment for QUEUE jobs and submit jobs. If the directory has been changed, estimate the disk space requirements for the directory after the change.

For a standard configuration, a, b, and c must be estimated for the number of QUEUE jobs and submit jobs. Each time a QUEUE job or submit job is executed, an execution log for that job is saved. Execution logs are deleted when their retention period (number of days) expires. Note, however, that the size of the database used for the execution environment for QUEUE jobs and submit jobs is not reduced at the moment execution logs are deleted. Accordingly, you need to perform periodic maintenance for the ISAM files used in this execution environment.

For details about how to perform maintenance, see 5.2.2 How to check the unused area of the ISAM files used in the execution environment for QUEUE jobs and submit jobs, and when the database should be reorganized in the JP1/Automatic Job Management System 3 Administration Guide. For details about how to change the number of days for retaining job information, see 20.5 Setting up the job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.

This item depends on the parameters used for job execution, such as the standard output file, the standard error output file, environment variables, and transfer files. As a rough estimate, a job requires 0.5 megabytes multiplied by the maximum number of concurrently executable jobs for an agent (standard: 5). However, if you can estimate an average value for the files described above, change the default value for calculation.

a: The total size of the temporary change information

Calculate the total of the temporary change information size for each root jobnet. To do so, use the following equation:

0.002 x A + 0.003 x B

A: The number of the operations performed on the root jobnet and its lower units that are to be saved as temporary change information

B: The number of operations in A that are performed to add execution schedules by specifying passing information

Temporary change information increases every time you perform an operation that is saved as temporary change information on the root jobnet and its lower units. Note, that for a root jobnet and its lower units for which the expired temporary change information is stored, the expired temporary change information is automatically deleted when you perform an operation that is saved as temporary change information. For details about the operations that are saved as temporary change information and the expiration date of temporary change information, see 4.5.16(1) Displaying temporary change information in the manual JP1/Automatic Job Management System 3 Overview.

Estimate the total for all the registered root jobnets.

Because the data is stored in the directory for job error information, estimate the disk space for the new directory if the storage destination in the JOBINFDIR environment setting parameter is changed.

When an event job (including one set in a start condition) is executed, the definition data of the executed event job and the information about the event when the monitoring condition is satisfied are exchanged between processes such as the event/action control manager and the event/action control agent. During that time, if communication fails because of a temporary network failure or because the destination process is busy, the information to be sent is temporarily stored in a file as unreported information and then re-sent after a preset interval.

The estimated size for unreported information is the maximum size needed to retain the information.

Note that unreported information is deleted when retransmission is successful.

This value is calculated as follows:

Disk space for unreported information = (0.025 x A) + (0.005 x B) (units: megabytes)

A: Number of events one scheduler service can process per hour

B: Number of retained items of unreported information that is to be sent from event/action control to schedule control

If all the data to be transmitted between the event/action control manager and the event/action control agent becomes unreported information, the maximum for A becomes 1,000. For details about the number of events that one scheduler service can process per hour, see 3.1.5 Event monitoring performance.

If all the data to be sent from event/action control to schedule control becomes unreported information, the maximum for B becomes 15,000.

If all the unreported information is retained, the maximum disk space for unreported information is (0.025 x 1,000) + (0.005 x 15,000) = 100 (units: megabytes).

Estimated only when the temporary change operation management function is used.

Because this data is stored in the directory for job error information, estimate the disk space of the actual directory if you have changed the storage directory.

The size of the data used by the job execution control manager process (jpqman) of each scheduler service to manage job information

If you use an external database, you need to estimate the volume of user data only if you use the -i %so option, the -f %r option, or the -r option of the ajsshow command. In this case, the contents of the standard output and the standard error output of the job specified for the ajsshow command are output to the directory specified for the STDFILEOUTDIR environment setting parameter. For this reason, estimate only the disk capacity required for the number of times the ajsshow command is executed. Note, as well, that the execution results of the ajsshow command are not automatically deleted. Manually delete them as needed.

When an external database is used, the amount of used disk space is 0.

When the backup enhancement function is used, the amount of used disk space is 0.

• Of the user data used by scheduler services, jobnet definitions and job execution information are included in the embedded database.

  For details about how to estimate the disk space used by the embedded database, see 23.2 Estimating the database area in the JP1/Automatic Job Management System 3 Configuration Guide.

• For details about how to estimate the disk space requirements after migration from a version 8 embedded database, see 8.5.2(7) Estimating the disk space requirements after migration from a version 8 embedded database.