KAVU5501-E

This is a message from the database system.

(O)

Check whether any of the following probable causes are present:

1. The message contains File lock error:

   The database file could not be accessed because it was busy.

   The probable cause of the busy database are:

   - Backup was being executed.

   - A command (except the jpqdbcond -L command) that uses an ISAM database was being executed.

   - A virus check program was running.

   - The JP1/AJS3 data collection tool (for Windows only)

2. The message contains SHMMNI insufficient:

   The shared memory ID was insufficient.

3. The message contains File not found or insufficient system resources:

   Free space on the disk was insufficient.

4. The message contains File not found or insufficient system resources:

   The job execution environment database does not exist.

5. The message contains System error occurred:

   The ISAM file is in an invalid state.

Take one of the following actions according to the cause of the error, and then reissue the request:

1. Adjust the schedule to execute the program or command that exclusively used the database file at a different time from when other jobs are executed.

2. Check the values set in the kernel parameters to check (ipcs) the current usage, and then recheck the kernel parameter settings.

3. Check the disk status. If the message appears during reorganization, estimate the disk space requirements for each database, allocate sufficient free space on the disk, and then reorganize the database. For details on how to reorganize the database, see 9.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the JP1/Automatic Job Management System 3 Administration Guide.

4. Use the jpqimport command to create a job execution environment database.

   For details on this command, see 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

5. Check the status of the ISAM file. If the status is invalid, re-create the ISAM file.

   For details on how to check the status of the ISAM file and how to re-create the ISAM file, see 2.11 Troubleshooting problems related to invalid ISAM files in the manual JP1/Automatic Job Management System 3 Troubleshooting.