Job Management Partner 1/Automatic Job Management System 3 Administration Guide

[Contents][Glossary][Index][Back][Next]


6.2 Checking database usage

JP1/AJS3 uses a database to manage definition information and execution registration information for jobs. If data is added or deleted repeatedly, the efficiency of data usage decreases, resulting in degraded data search performance and potential problems.

You can avoid problems by periodically checking the usage of the database and by using the ajsembdbreclaim command to reclaim space during operation.

Generally, database reorganization is seldom required if you periodically use the ajsembdbreclaim command for maintenance. Note, however, that if the usage efficiency of the database has dropped greatly, database reorganization might be required. For details about how to reorganize the database, see 10.2.2 Reorganizing a database.

Organization of this section
(1) How to check the database usage
(2) How to check the unused area of the ISAM files used in the execution environment for QUEUE jobs and submitted jobs, and when the database should be reorganized

(1) How to check the database usage

You can use output messages to check database usage.

(a) When the database auto-increment function is used

Each time the database has too little remaining free space and is automatically expanded, the KFPH22024-W message is output to the Windows event log or syslog. If the KFPH22024-W message is output repeatedly, reconfigure the database and check whether the data increment value (job definition information and job execution registration information) is appropriate.

(b) When the database auto-increment function is not used

The KFPH00211-I message is output to the Windows event log or syslog when the usage rate reaches 80%, 90%, or 100%. Therefore, periodically check the Windows event log or syslog.

When the usage rate is 80%, you can avoid problems by reorganizing the database. However, when the usage rate reaches 90% or 100%, simply reorganizing the database will not eliminate the problems. Instead, you will need to delete data (job definition information and job execution registration information) or expand the database.

(2) How to check the unused area of the ISAM files used in the execution environment for QUEUE jobs and submitted jobs, and when the database should be reorganized

Execute the jpqdbcond command to check the unused area in the ISAM database.

Notes on using the jpqdbcond command are provided below. For details about the jpqdbcond command, see jpqdbcond in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(a) How to check the unused area

Use the jpqdbcond command to check the unused area in the database.

The following are examples of using the jpqdbcond command:

 
jpqdbcond -L -a -t se,10
 

This command outputs information about the ISAM files used in the execution environment for QUEUE jobs and submitted jobs to the standard output. If the size of the unused area has reached the threshold (10 MB), the command also outputs a message to the standard error output and syslog (Windows event log). By using the options indicated to schedule the jpqdbcond command for execution as a JP1/AJS3 job when not many jobs are executed, you can periodically check the ISAM file status and set the output of warning messages.

 
jpqdbcond -l -a
 

This command outputs the status of the ISAM file used in the execution environment for QUEUE jobs and submitted jobs. The output information includes the percentage of unused area, the unused area size, and a percentage value for data file fragmentation.

 
jpqdbcond -L -a -t j,10
 

This command outputs the following JP1 event when the size of the unused area reaches the threshold (10 MB):

Reorganize the database if the predefined threshold is exceeded.

(b) When the database needs to be reorganized

For the frequency of reorganization in the execution environment for QUEUE jobs and submitted jobs, also use the number of days that job information is saved. For details about the setting for this number, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

For details about the JP1 event output by the jpqdbcond command, see A. JP1 Events Issued by JP1/AJS3.

For details about how to reorganize the database, see 10.3 Reorganizing a database when QUEUE jobs and submit jobs are used.

(c) Notes on the jpqdbcond command

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.