KAVS0902-E

A memory shortage occurred. If the KFPA11912-E message is indicated in the maintenance information, the system load is excessive because either too many processes are running concurrently, or the value of pd_lck_pool_size for the embedded database is too small.

Also, if the file specified for the command argument exceeds 2 gigabytes is specified, this message might be output.

(S)

Cancels the processing during which insufficient memory was detected. If insufficient memory was detected during allocation of memory for a key component that could not continue processing, the system aborts the process.

(O)

Check the following settings:

• In UNIX, see Release Notes, and make sure that the value of the kernel parameter for memory is greater than the estimated value.

• Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

• If the KFPA11912-E message is indicated in the maintenance information, specify yes for the UNITDEFDIVIDEUPDATE environment setting parameter to divide the data into several blocks that can then be written separately to the database. Alternatively, change the value of the pd_lck_pool_size for the embedded database.

  For details on the UNITDEFDIVIDEUPDATE environment setting parameter, see 20.4.2(100) UNITDEFDIVIDEUPDATE in the JP1/Automatic Job Management System 3 Configuration Guide.

  For details about pd_lck_pool_size, see the description of the single server definition in 23.1.1 Examining the embedded-database operating environment and operating method in the JP1/Automatic Job Management System 3 Configuration Guide.

  If necessary, re-execute the processing for which memory was insufficient.

  If the KFPA11912-E message was indicated in the maintenance information when you performed one of the following operations in an environment where yes was specified for the UNITDEFDIVIDEUPDATE environment setting parameter, take the appropriate action for the operation you performed:

(1) If the ajsdefine command or ajsrestore command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option or -i option in the command.

(2) If the ajsimport command was executed:

Perform either of the following operations:

- Delete the unit you attempted to create, and then re-execute the command.

- Specify the -f option in the command.

(3) If the ajscopy command was executed or JP1/AJS3 - View was used to copy a unit:

Perform the following:

- Delete the unit at the copy destination, and then retry the copy.

(4) If the ajsdelete command or ajssuspend command was executed:

Perform the following:

- Re-execute the command.

(5) If the ajsrelease command was executed or JP1/AJS3 - View was used to enter a job or jobnet for release:

Perform the following:

- Cancel the release, and then retry entering the job or jobnet for release.

(6) If JP1/AJS3 - View was used to restore a unit:

Perform the following:

- Delete the unit you attempted to restore, and then retry the restoration.

• Make sure that the file specified for the command argument does not exceed 2 gigabytes.