Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 1


KAVS0930-E

Exclude error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A lock error occurred.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

During reorganization of ISAM files or when the ajsdbcond command with the -l option specified was executed, the ISAM files could not be locked because there were processes accessing the ISAM files.

Action

The scheduler service might be running or the unit might have been referenced or updated from JP1/AJS3 - View, a command that operates units, or a related product. Stop the scheduler service and make sure that the unit is not being referenced or updated. Then, retry the operation that resulted in the error.

For details about reorganizing ISAM files, see 10.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Cause 2

When the OS is AIX and the ISAM lock table split function is used, the ISAM lock table cannot be allocated.

Action

Stop all the related JP1 services, set ON for the EXTSHM environment variable, and then retry the operation that resulted in the error.

Cause 3

The status of the ISAM lock table has become invalid.

Action

Delete the ISAM lock table, and then retry the operation that resulted in the error.

Cause 4

JP1/AJS3 could not access the ISAM files because they were locked by another product such as backup software or anti-virus software.

Action

Make sure that no other products are accessing the ISAM files, and then retry the operation that resulted in the error.

Cause 5

A deadlock occurred when an embedded database was being used.

Action

The deadlock status is canceled automatically. If necessary, retry the operation that resulted in the error.

If an error message still appears after the above actions are taken, contact the system administrator and then collect data (see 1.2.3 To the system administrators).