Job Management Partner 1/Automatic Job Management System 3 Messages 2

1.1 Messages beginning with KAVU (Messages about the job execution control)

This section lists messages that begin with KAVU (messages about job execution control).

function-name: of some messages may not be displayed.

In some cases, destination-host-name, port-number, and system-error-number might not be displayed for messages that have these elements.

When a job other than a QUEUE job or a submitted job is executed, the queue element of the message that is output indicates the execution agent or execution agent group.

When a job other than a QUEUE job or a submitted job is executed, the agent-host-name and agent-name elements of the message that is output indicate the execution agent name or execution agent group. Note, however, that the target host is displayed in the following messages:
KAVU4220-E, KAVU4221-E, KAVU4222-E, KAVU4223-E, KAVU4294-I, KAVU4295-W, KAVU4296-E, KAVU4297-W, KAVU4299-I, KAVU4504-W, KAVU4530-W, KAVU4531-W, KAVU4534-W, KAVU4535-I, KAVU4538-W, KAVU4546-W, KAVU4547-W, KAVU4548-W, KAVU4549-W, KAVU4550-W, KAVU4551-W, KAVU4552-W, KAVU4553-W, KAVU4554-W, KAVU4555-W, KAVU4556-W, KAVU4557-W, KAVU4558-W, KAVU4559-W, KAVU4560-W, KAVU4561-W, KAVU4562-W, KAVU4563-W, KAVU4564-W, KAVU4565-W, KAVU4566-W, KAVU4567-W, KAVU4568-W, KAVU4569-W, KAVU4570-W, KAVU4571-W, KAVU4572-W, KAVU4573-W, KAVU4574-W, KAVU4575-W, KAVU4576-W, KAVU4578-W, KAVU4580-W, KAVU4581-W, KAVU4582-W, KAVU4583-W, KAVU4584-W, KAVU4585-W, KAVU4586-W, KAVU4587-W, KAVU4588-W, KAVU4589-W, KAVU4590-W, KAVU4591-W, KAVU4596-W, KAVU4597-W, KAVU4598-W, KAVU4700-E, KAVU4701-E, KAVU4702-E, KAVU4703-E, KAVU4704-E, KAVU4717-E, KAVU4718-E

To distinguish the job execution control managers that output messages, (scheduler-service-name) might be appended to the message. If (scheduler-service-name) is displayed, the message has been output by the job execution control manager for the indicated scheduler service. If (scheduler-service-name) is not displayed, the message has been output by the submit-job execution control manager.

For operation in the compatible ISAM configuration, see the JP1/AJS2 manual.

KAVU0200-E
function-name: A logical contradiction occurred.

A logical contradiction occurred.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0201-E
function-name: The parameter is specified incorrectly.

The function has a parameter error.

(S)

Cancels the requested processing.

(O)

Make sure that the argument specified for the command is correct.

Also check the message output to the standard error output. Also check the integrated trace log for whether a KAVU message was output before or after this message. If a KAVU message was output, read the message explanation.

Remove the cause of the error, and then retry the operation.

KAVU0202-E
function-name: An internal factor caused an error.

An error occurred because of an internal factor.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0203-E
function-name: JpqInit function is not issued.

The JpqInit function is not issued.

(S)

Cancels the requested processing.

(O)

Make sure that the JpqInit function is correctly called, and then retry.

KAVU0204-E
function-name: An environment setting or logical host name information is invalid.

An environment setting or logical host name information is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0205-E
function-name: Memory became insufficient.

Memory became insufficient.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0206-E
function-name: A logical contradiction occurred.

An error was found in a communication protocol parameter during processing of a request from the client. Alternatively, an attempt to acquire information about a logical host name or environment setting has failed at the function issuer. If a request is issued while the hosts file is being copied by overwriting the current one at the function issuer, an attempt to acquire the logical host name may fail.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation in that message to correct the cause of the error, and then reissue the request. If no such message was output or if the problem persists, use the data collection tool to collect data, and then contact the system administrator.

KAVU0207-E
function-name: The file cannot be opened because file path or file does not exist at the send source.

The file cannot be opened because file path or file does not exist at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0208-E
function-name: The file cannot be opened because you lack access permission for the file at the send source.

The file cannot be opened because you lack access permission for the file at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0209-E
function-name: The file cannot be opened because some other process is using the file at the send source.

The file cannot be opened because some other process is using the file at the send source.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0210-E
function-name: The file at the send source cannot be opened.

The file at the send source cannot be opened.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the original file name of the job definitions.

KAVU0211-E
function-name: The file at the send source cannot be read.

The file at the send source cannot be read.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0212-E
function-name: Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written.

Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then call the function again.

KAVU0213-E
function-name: The file specified as the acquisition destination of the standard output or standard error output file could not be written.

The file specified as the acquisition destination of the standard output or standard error output file could not be written.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0214-W
function-name: The standard (error) output file at the manager consists of 0 bytes of data.

No file was found when an attempt was made to collect data in the standard output file or the standard error output file by using the jpqjobget command.

(S)

Terminates the requested processing.

KAVU0215-E
function-name: TCP/IP communication could not be connected to the manager.

A connection for TCP/IP communication could not be established with the job execution control manager process.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is possible between the manager host specified for executing the request and the requesting client host. If TCP/IP communication is possible or if the manager host and the requesting client host are the same, check the startup status of the following processes.

For Windows

If the message output process is the flow control process (ajsflowd.exe) or the job completion wait process (ajssubwd.exe), check whether the KAVU6100-I message has been output to the integrated trace log and whether the job execution control status notification process (jpqnfyd.exe) has been started. If the message output process is any other process (when the process name in the integrated trace log is UAP), make sure that the job execution control manager process (jpqman.exe) has started. If any of these processes has not started, restart the JP1/AJS3 service and retry the operation.

For UNIX

If the message output process is the flow control process (ajsflowd) or the job completion wait process (ajssubwd), check whether the KAVU6100-I message has been output to the integrated trace log and whether the job execution control status notification process (jpqnfyd) has been started. If the message output process is any other process (when the process name of the integrated trace log is UAP), check that the job execution control manager process (jpqman) has been started. If any of these processes has not started, restart the JP1/AJS3 service and retry the operation.

Also check the integrated trace log of the manager host for whether a KAVU message indicating a TCP/IP communication connection error was output before or after this message. If a KAVU message was output, read the message explanation. If no KAVU message has been output or if you cannot identify the cause of the problem, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the requesting client host.

KAVU0216-E
function-name: A timeout occurred for the request to acquire status notification.

A timeout occurred for the request to acquire status notification.

When acquiring the information on status notification for the job using the JpqGetReport and JpqOpenEnumReport functions supplied by JP1/AJS2 - Client Toolkit or JP1/AJS2 - SDK, the information on status notification could not be received within the period of time specified for the ulTimeout argument of these functions.

(S)

Cancels the requested processing.

(O)

Make sure that the job that will receive the status notification is correct, and then call the function again.

When acquiring the information on status notification for the job using the JpqGetReport and JpqOpenEnumReport functions supplied by JP1/AJS2 - Client Toolkit or JP1/AJS2 - SDK, retry in the application, or re-execute the application depending on the configuration of the application.

KAVU0217-E
function-name: The IP address could not be converted.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then call the function again.

KAVU0218-E
function-name: The manager cannot accept requests in the present status.

The manager cannot accept requests in the present status.

(S)

Cancels the requested processing.

(O)

Check the following possible causes, and then call the function again:

Check whether daemon operation has started.

Check whether the manager is running in reduced mode.

KAVU0219-E
function-name: The specified queue or agent does not exist.

The specified queue or agent does not exist.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

You changed the local host name after installing JP1, and then executed a job for the local agent.

The agent specified as the execution host in the jobnet or job definition was not defined in the manager.

The agent name defined in the manager is invalid.

No queue has been added.

The queue name or agent was specified incorrectly when a command with a name beginning with jpq was used.

The execution host of the job was specified using an IP address.

Take one of the following actions according to the cause of the error, and then re-execute.

Change the host name correctly according to 8.9.1 Changing the name of the host that runs JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Check the specification of the execution host name. If an incorrect host name is specified, specify the correct one. To add an agent definition to the manager, perform step 3, below.

Execute one of the following commands to define the correct agent.
- For a PC job, UNIX job, action job, or custom job:
ajsagtadd command
- For a QUEUE job or submitted job:
jpqimport or jpqagtadd command

Use the jpqqueadd command to add a queue.

Check the queue name or agent name.

As the execution host of the job, specify the name defined as an agent in the manager.

For details about the commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0220-E
function-name: There is no response from the manager.

The manager does not respond.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present:

The specified port number is invalid.

A communication error occurred.

The manager is heavily loaded.

The specified transfer file size exceeds the value set in LimitReceiveFileSize environment setting parameter when the setting for limiting file reception was specified.

Take one of the following actions according to the cause of the error, and then re-execute.

Recheck the port number.

Check the network status.
Also check whether hardware, including network cards, cables, and hubs, is operating correctly.

Use the top command (in UNIX) or Task Manager (in Windows) to check the process that is causing a heavy load on the manager.
Also check whether the requested processing is performed just around the same time as the deletion of JP1/AJS3 job information.
If they are performed at the same time, change the schedule to delete the JP1/AJS3 job information when few jobs are being executed.

Check whether the size of the transfer file exceeds the value set in LimitReceiveFileSize environment setting parameter.

KAVU0221-E
function-name: An internal factor at the manager caused an error.

An error occurred because of an internal factor of the manager.

(S)

Cancels the requested processing.

(O)

Check the integrated trace log for whether a KAVU message was output before or after this message. If a KAVU message was output, read the message explanation to identify the cause of the error, remove the cause, and then call the function again. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU0222-E
function-name: The queue is closed.

No jobs can be registered because the queue entrance is closed.

(S)

Cancels the requested processing.

(O)

The action to be taken differs depending on the type of the job.

For a PC job, UNIX job, action job, or custom job:
Use the ajsagtalt command to change the status of delivery-limitations for the execution agent to enabled, and then issue the request again.

For a QUEUE job or submitted job:
Use the jpqqueopen command to open the queue entrance, and then issue the request again.

For details about the ajsagtalt command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1

For details about the jpqqueopen command, see jpqqueopen in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0223-E
function-name: The number of queued jobs in the specified queue reached the limit or the queue resources reached the limit.

The number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue or the maximum number of jobs allowed in the system.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end and then issue another request, or review the queue definition information and adjust the maximum number of jobs allowed in the queue or the system.

If the maximum number of jobs allowed in the queue has been reached, the KAVU4515-W message is output to the integrated trace log. If the maximum number of jobs allowed in the system has been reached, the KAVU4520-W message is output to the integrated trace log.

Take the corrective action specified in the message that is output.

KAVU0224-E
function-name: You lack operate permission.

The user requesting execution by the manager process for job execution control does not have the required JP1 permission level for the operation.

(S)

Cancels the requested processing.

(O)

Check the JP1 permission level of the user that issued the execution request.

Before you execute a command for job execution control, you must register the requesting OS user as a JP1 user on the authentication server. Also, if required, grant the JP1 user execute permission. For details about the execute permission required for commands, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 12.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

KAVU0225-W
function-name: The job does not exist.

The job does not exist.

(S)

Cancels the requested processing.

(O)

No corresponding job was found when a command was executed for enumerating jobs. Make sure that the specified host name, queue name, and job status are correct, and then retry the operation.

If a command other than a command for enumerating jobs was executed, make sure that the specified job number is correct, and then retry the operation. Check the specified job number against the KAVU message that was output before or after this message to the standard error output or the integrated trace log.

KAVU0226-E
function-name: You cannot perform this operation because this job is being executed (or has not ended).

You cannot perform this operation because this job is being executed (or has not ended).

(S)

Cancels the requested processing.

(O)

Wait for the job to end, and then retry the operation.

KAVU0227-E
function-name: The destination queue does not exist.

The destination queue does not exist.

(S)

Cancels the requested processing.

(O)

Check the queue name specified as the name of the destination queue, check whether the queue exists, and then retry the operation.

KAVU0228-E
function-name: The destination queue has reached the queuing limit.

The number of jobs registered in the queue specified as the destination queue has reached the maximum number of jobs allowed in the queue.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0231-W
function-name: There is no queue in the manager.

The manager host does not have any queue definition information.

(S)

Terminates the requested processing.

KAVU0232-E
function-name: No agent is connected to the manager.

There is no agent definition information on the manager host.

(S)

Cancels the requested processing.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0233-E
function-name: The macro variable (macro-variable-name) has not been inherited.

The macro variable has not been inherited.

(S)

Places the job in the failed to start status.

(O)

The macro variable name has not been inherited from the preceding job. Recheck the jobnet definition, and then re-execute the job.

KAVU0234-W
function-name: The status notification process is closed.

The status monitoring process has terminated because a JpqCloseReport or JpqCloseReportp function was issued while the request for acquiring the job status notification information was being processed.

(S)

Cancels the requested processing.

KAVU0235-E
function-name: The request to acquire status notification was already issued.

A request to acquire status notification for the specified job has already been issued.

(S)

Cancels the requested processing.

(O)

Make sure that no other process issued a request to acquire status notification, and then call the function again.

KAVU0236-E
function-name: The status was acquired by another acquisition status notification request.

Another request to acquire status notification already acquired status notification.

(S)

Cancels the requested processing.

(O)

Make sure that no other process issued a request to acquire status notification, and then call the function again.

KAVU0237-E
function-name: The manager (job status notification process) is busy.

The manager or job status notification process is busy.

(S)

Cancels the requested processing.

(O)

Re-execute the function after a while.

KAVU0238-E
function-name: Memory became insufficient at the manager (job status notification process).

Memory became insufficient at the manager or job status notification process.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0239-E
function-name: VOS3 user information is invalid.

VOS3 user information is incorrect.

(S)

Cancels the requested processing.

(O)

Use the jpqreguser command to check whether the specified user is correctly registered, and then retry.

KAVU0240-E
function-name: A fatal error occurred in the manager (job status notification process).

A fatal error occurred in the manager or job status notification process.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0241-E
function-name: A logical contradiction occurred in the manager (job status notification process).

An error was found in a communication protocol parameter in the manager or job status notification process. If this error message appears when JP1/AJS3 links to another system such as JP1/OJE for VOS3 or JP1/NQSEXEC, the other system may have a problem.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, see the explanation provided in that message to correct the cause of the error, and then reissue the request. If no such message was output or if the problem persists, use the data collection tool to collect data, and then contact the system administrator.

KAVU0242-E
function-name: The requested the manager does not support the request.

This message may be displayed if you operate a queue or agent in JP1/NQSEXEC or JP1/OJE for VOS3.

(S)

Cancels the requested processing.

(O)

Ask the system administrator whether the requested manager (product) can process the request.

KAVU0243-E
function-name: An error occurred after submission.

An error occurred after a job was submitted.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0244-E
function-name: The execution environment is invalid.

An error disabling job execution has been detected. The cause of the error is an invalid system environment for job execution control.

(S)

Cancels the requested processing.

(O)

The authentication server may not be started. If this is the case, start the authentication server. If a KAVU2227-E message was output before this message, the IP address of the host issuing the request might be invalid. If this message was output, check whether the IP address output in the message is usable.

For all other cases, check the integrated trace log for whether a KAVUxxxx message was output before or after this message. If a KAVUxxxx message was output, read the message explanation, remove the cause of the problem, and then retry the request. If no KAVU message was output or if you are unable to solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0245-E
function-name: The same external identifier already exists.

The same external identifier already exists.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0246-E
function-name: The transfer file could not be created on the manager.

The function failed to create the file transferred when the job was submitted in the manager.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0247-E
function-name: The transfer file could not be written on the manager.

The function failed to write the file transferred when the job was submitted in the manager.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0248-E
function-name: The job was forcibly terminated, but it might not have terminated.

An attempt was made to forcibly terminate the job but the job may still be running.

(S)

Terminates the requested processing.

(O)

Use the integrated trace information log to check the cause of the error.

KAVU0249-E
function-name: The job status notification has already been received in the same process.

The reception of the job status notification has already been started in the same process.

(S)

Cancels starting of the daemon.

(O)

Check whether the request is called more than once in the same process.

KAVU0250-E
function-name: The job status notification process cannot be created.

The job status notification process could not be created.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0251-E
function-name: The job status notification could not be received because resources were insufficient when the notification started.

The reception of the job status notification could not be started because resources became insufficient when the notification started.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0252-E
function-name: The job status notification process could not be started.

The job status notification process could not be started.

(S)

Cancels starting of the daemon.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0253-E
function-name: The file cannot be created because there is no path to the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be created because there is no path to the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Check the path to the file, and then call then the function again.

KAVU0254-E
function-name: The file cannot be created because you lack access permission to the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be created because you do not have access permission for the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Check the access permission for the path to the file, and then call the function again.

KAVU0255-E
function-name: The file cannot be opened because some other process is using the file specified as the acquisition destination of the standard output or standard error output file.

The file cannot be opened because another process is using the file specified to acquire the standard output or standard error output file.

(S)

Only acquires the information.

(O)

Terminate the process that is accessing the file, and then call the function again.

KAVU0256-E
function-name: The file specified as the acquisition destination of the standard output or standard error output file cannot be created.

The file specified to acquire the standard output or standard error output file cannot be created.

(S)

Only acquires the information.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0257-W
function-name: The specified exclusive execution resource name does not exist.

The system does not contain the specified exclusive execution resource name.

(S)

Cancels the requested processing.

(O)

Specify the correct exclusive execution resource name, and then call the function again.

KAVU0258-W
function-name: The specified queue or agent already exists.

The specified queue or agent already exists.

(S)

Cancels the requested processing.

(O)

Specify the correct queue name or agent name, and then call the function again.

KAVU0259-W
function-name: The specified exclusive execution resource name already exists.

The specified exclusive execution resource name already exists.

(S)

Cancels the requested processing.

(O)

Specify the correct exclusive execution resource name, and then call the function again.

KAVU0260-E
function-name: Failed to process because some job is being executed.

Some jobs cannot be changed or deleted because they are being executed.

(S)

Cancels the requested processing.

(O)

Waits until the job execution terminates, and then call the function again.

KAVU0261-E
function-name: Failed to process because of exceeding the maximum number defined in the environment settings.

Addition is impossible because the number of queues, agents, or exclusive execution resources exceeded the maximum number in the environment settings.

(S)

Cancels the requested processing.

(O)

Recheck the maximum number of definitions in the environment settings, and then call the function again.

KAVU0262-E
function-name: The specified agent cannot be deleted because some queue is connected.

The agent cannot be deleted because the agent is not disconnected from the queue.

(S)

Cancels the requested processing.

(O)

Disconnect the agent from the queue, and then call the function again.

KAVU0263-E
function-name: The specified agent is not connected.

The specified agent is not connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0264-E
function-name: The agent is already connected.

The specified agent has already been connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0265-W
function-name: There is no exclusive execution resource in the manager.

The specified exclusive execution resource is not defined.

(S)

Cancels the requested processing.

(O)

Correct the error, and then call the function again.

KAVU0266-W
function-name: The agent to be changed the priority is not connected.

The agent which priority you want to change is not connected.

(S)

Cancels the requested processing.

(O)

Specify the correct agent, and then call the function again.

KAVU0267-E
function-name: The agent cannot be added because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of addition of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being added due to a notification error.

(S)

Cancels the requested processing.

(O)

Waits until modification of the other agent terminates, and then call the function again.

KAVU0268-E
function-name: The agent cannot be deleted because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of deletion of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being deleted due to a notification error.

(S)

Cancels the requested processing.

(O)

Waits until modification of the other agent terminates, and then call the function again.

KAVU0269-E
function-name: Job could not be submitted because agent host was failed to create automatically.

The agent could not be automatically created. This prevented the job from being submitted.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the job.

KAVU0300-E
function-name: The logical host name could not be acquired.

The function cannot acquire the logical host name.

(S)

Cancels the requested processing.

(O)

Correct the error in the environment settings or correct the invalid definitions. Then, call the function again.

KAVU0301-E
function-name: No agent host name is specified.

An agent host name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0302-E
function-name: The agent host name is too long.

The agent host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0303-E
function-name: The agent host name is invalid.

An incorrect agent host name is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0304-E
function-name: No destination is specified for storing the acquired number of agent information.

The storage area for the number of agent information items is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0305-E
function-name: The standard error output file name at the agent is too long.

The name of the standard error output file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0306-E
function-name: The standard output file name at the agent is too long.

The name of standard output file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0307-E
function-name: The standard input file name at the agent is too long.

The name of standard input file at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0308-E
function-name: The destination for storing the agent name is too small.

The agent name storage area is too small.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0309-E
function-name: The type of open/close is specified incorrectly.

The queue open/close type is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0310-E
function-name: The status of job exit from the queue is invalid.

The status of the job exit of the queue is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0311-E
function-name: No destination is specified for storing the acquired number of connection information items about the queue and the agent.

The storage area for the number of information items on the connection between the queue and agent is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0312-E
function-name: The acquired number of connection information items about the queue and the agent is invalid.

The number of information items on the connection between the queue and agent is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0313-E
function-name: The destination for storing the connection information about the queue and the agent is invalid.

The storage area for information on the connection between the queue and agent is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0314-E
function-name: The destination for storing the connection information about the queue and agent is too small.

There are too few storage areas for information on the connection between the queue and agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0315-E
function-name: The status of job entrance for the queue is invalid.

The status of the job entrance of the queue is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0316-E
function-name: The process for the queue exit is invalid.

The invalid processing is specified for the job exit of the queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0317-E
function-name: No destination is specified for storing queue information.

The queue information storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0318-E
function-name: The process for the queue entrance is invalid.

The invalid processing is specified for the job entrance of the queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0319-E
function-name: No queue name is specified.

A queue name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0320-E
function-name: The queue name is too long.

A queue name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0321-E
function-name: The queue name is invalid.

A queue name is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0322-E
function-name: No size is specified for the queue name storing destination.

The size of the queue name storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0323-E
function-name: The client computer name could not be acquired.

The function failed to acquire the name of the client computer.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0324-E
function-name: The client host name is too long.

The client host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0325-E
function-name: The service name (service-name) could not be acquired.

The function failed to acquire the service name.

(S)

Cancels the requested processing.

(O)

Check the services file, specify a correct port number and then call the function again.

KAVU0326-E
function-name: The request destination user name is too long.

The name of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0327-E
function-name: The request destination password is too long.

The password of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0328-E
function-name: The request group name is too long.

The group name of the VOS3 user you registered is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0329-E
function-name: The type of the submit destination name is invalid.

The type of the submit destination is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0330-E
function-name: No destination is specified for storing the submit destination name type.

The storage area for the type of the submit destination name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0331-E
function-name: The job number is invalid.

The job number is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0332-E
function-name: No destination is specified for storing the job number.

The storage area for the job number is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0333-E
function-name: No job submit date is specified.

The date/time when the job will be submitted is not specified.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0334-E
function-name: The job submit date is invalid.

The job submit date/time is incorrect.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0335-E
function-name: No external identifier is specified to the job.

The external identifier to be assigned to the job is not specified.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0336-E
function-name: The external identifier to the job is too long.

The length of the external identifier to be assigned to the job is incorrect.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0337-E
function-name: The job recovery status is specified incorrectly.

An incorrect job recovery status is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0338-E
function-name: The job execution method is specified incorrectly.

An incorrect job execution method is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0339-E
function-name: The method for judging the job end status is specified incorrectly.

The method of judging the job end status is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0340-E
function-name: No file name is specified for the job end judgment.

The name of the file for determining whether the job is terminated normally or abnormally is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0341-E
function-name: The file name for the job end judgment is too long.

The name of the file for determining whether the job is terminated normally or abnormally is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0342-E
function-name: The job request user name is too long.

The name of the user who requested the job is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0343-E
function-name: Job moving destination queue name is too long.

The name of the queue to which you want to move jobs is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0344-E
function-name: Job execution account name is too long.

The name of the job execution account is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0345-E
function-name: No job execution start date is specified.

The job start date/time is not specified.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0346-E
function-name: The job execution start date is invalid.

The job start date/time is incorrect.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0347-E
function-name: No job execution end date is specified.

The job end date/time is not specified.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0348-E
function-name: The job execution end date is invalid.

The job end date/time is incorrect.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0349-E
function-name: The job time-out period is out of range.

The timeout for job execution is out of range.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0350-E
function-name: No job owner name is specified.

The job owner name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0351-E
function-name: The job owner name is too long.

The job owner name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0352-E
function-name: The job owner name cannot be specified.

You cannot specify a job owner name.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0353-E
function-name: No detailed information is specified about the job.

The details of the job are not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0354-E
function-name: The destination for storing job information is specified incorrectly.

The job information storage area is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0355-E
function-name: The job status is invalid.

The job status is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0356-E
function-name: The requested amount of information is invalid.

The number of requests for information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0357-E
function-name: The direction of the job insert relative position is specified incorrectly.

The direction for the relative position where the job should be inserted is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0358-E
function-name: The job definition information is invalid.

The job definition has an error.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0359-E
function-name: The size of the job definition information is invalid.

The size of the job definition information is invalid.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0360-E
function-name: A parameter error occurred during the analysis of the job definition information.

A parameter error occurred while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0361-E
function-name: Memory became insufficient while analyzing the job definition information.

Memory became insufficient while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0362-E
function-name: An unknown error occurred while analyzing the job definition information.

An error of unknown origin occurred while the function was analyzing the job definition.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0363-E
function-name: No job name is specified.

A job name is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0364-E
function-name: The job name is too long.

A job name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0366-E
function-name: The script is too long.

A script statement is too long.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too long.

If you are using the option that validates a double quotation mark ("), passed information may become longer than the limit of the number of characters because " in the passed information is replaced by \".

KAVU0367-E
function-name: The process priority is invalid.

The process priority is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0368-E
function-name: The port number is invalid.

A port number is incorrect.

(S)

Cancels the requested processing.

(O)

Check the services file, specify a correct port number, and then call the function again.

KAVU0369-E
function-name: The process of analyzing the macro valuable failed.

The function failed to analyze macro variables.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0370-E
function-name: The macro variable is specified incorrectly.

An incorrect macro variable is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0371-E
function-name: The response data from the manager is invalid.

The response from the manager is incorrect.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0372-E
function-name: Enumerated information returned from the manager is invalid.

Enumerated information returned from the manager is incorrect.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0373-E
function-name: The host name of manager is too long.

The manager host name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0374-E
function-name: No destination is specified for storing the operating status of the manager.

The storage area for the manager operation status is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0375-E
function-name: Memory could not be allocated.

The function failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then call the function again. If the same message reappears, re-estimate memory.

KAVU0376-E
function-name: The exclusive execution resource name is too long.

The name of an exclusive execution resource is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0377-E
function-name: The work path name is too long.

The work path name is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0378-E
function-name: The abnormal end threshold is invalid.

The threshold for the abnormal termination status is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0379-E
function-name: The transmission source file name is too long.

The transmission source file name is too long.

(S)

Places the job in the failed to start status.

(O)

The macro variable name specified for the transmission source file name may be too long as a result of replacement.

Recheck the specification of the inherited information and the transmission source file name, and then re-execute the job.

KAVU0380-E
function-name: The transmission destination file name is too long.

The transmission destination file name is too long.

(S)

Places the job in the failed to start status.

(O)

The macro variable name specified for the transmission destination file name may be too long as a result of replacement.

Recheck the specification of the inherited information and the transmission destination file name, and then re-execute the job.

KAVU0383-E
function-name: The environment variable information is invalid.

Environment variable information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0384-E
function-name: The environment variable information is too big.

The amount of environment variable information is too large.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too large.

KAVU0385-E
function-name: The size of the environment variable information is invalid.

The amount of environment variable information is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0386-E
function-name: The environment variable information file name is too long.

The name of the file for environment variable information is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0389-E
function-name: The warning end threshold is invalid.

The threshold for warned termination is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0390-E
function-name: The user name of the own process cannot be acquired.

The function cannot acquire the user name of the local process.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0391-E
function-name: The execution shell path name is too long.

The path name of the shell to execute is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0392-E
function-name: A command parameter for the execution file is too long.

The command parameters for the executable file are too long.

(S)

Cancels the requested processing.

(O)

If you are using a macro variable, make sure that passed information is not too large.

If you are using the option that validates a double quotation mark ("), passed information may become larger than the limit of the number of characters because " in the passed information is replaced by \".

KAVU0393-E
function-name: The execution file name is too long.

The name of the executable file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0395-E
function-name: Neither the execution file name nor the execution script is specified.

Neither an executable file name nor an execution script statement is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0396-E
function-name: The time out value for reception-waiting is invalid.

The timeout for reception is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0397-E
function-name: The start date is invalid in enumerating the end time of the end job.

The start date/time from which to enumerate the terminated jobs based on their end times is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0398-E
function-name: The end date is invalid in enumerating the end time of the end job.

The end date/time to which to enumerate the terminated jobs based on their end times is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0399-E
function-name: The status report identifier is invalid.

The identifier for status notification is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0400-E
function-name: No destination is specified for storing the status report identifier.

The storage area for the identifier for status notification is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0401-E
function-name: The destination for storing the status report information is invalid.

The storage area for the information on status notification is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0402-E
function-name: No information is specified about the host to which the status is reported.

The information on the destination host for status notification is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0403-E
function-name: The specified client computer name is too long.

A too long client computer name is defined.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0404-E
function-name: The start time of the concurrently-executable job limit information is invalid.

The start time of the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0405-E
function-name: The end time for the concurrently-executable job limit information is invalid.

The end time for the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0406-E
function-name: The number for storing the concurrently-executable job limit information is too small.

The number for storing the concurrently-executable job limit information is too small.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0407-E
function-name: The destination for storing the concurrently-executable job limit information is invalid.

The destination for storing the concurrently-executable job limit information is invalid.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0408-E
function-name: No transfer file information is specified.

Information on the file to be transferred is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0409-E
function-name: The number of transfer files is invalid.

The number of files to be transferred is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0410-E
function-name: The specification of whether to output the standard error output file is invalid.

Whether to output errors to the standard error output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0411-E
function-name: The method for writing the standard error output file is specified incorrectly.

How to write data to the standard error output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0414-E
function-name: The path name for the standard error output file is too long.

The path name of the standard error output file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0415-E
function-name: The file name for the standard error output file and the additional write flag specification do not match.

The name of the standard error output file and the specification of the Append flag do not match.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0416-E
function-name: The specification of whether to output the standard output file is invalid.

Whether to output data to the standard output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0417-E
function-name: The method for writing the standard output file is specified incorrectly.

How to write data to the standard output file is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0420-E
function-name: The standard output file path name is too long.

The path name of the standard output file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0421-E
function-name: The file name for the standard output file and the additional write flag specification do not match.

The name of the standard output file and the specification of the Append flag do not match.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0422-E
function-name: The path name for the standard input file is too long.

The path name of the standard input file is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0423-E
function-name: An invalid agent name was returned.

An incorrect agent name is returned.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0424-E
function-name: An invalid queue name was returned.

An incorrect queue name is returned.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0425-E
function-name: The character code is specified incorrectly.

An incorrect character code is specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0426-E
function-name: The number of agent information to be changed is invalid.

The number of agent information items to be changed is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0427-E
function-name: The flag specifying hold or release is invalid.

The flag for determining whether to hold jobs is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0428-E
function-name: The flag for registering hold jobs is invalid.

The flag for registering the jobs to hold is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0429-E
function-name: The destination for storing the number of enumerated jobs is specified incorrectly.

The storage area for the number of enumerated job information items is incorrectly specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0430-E
function-name: The flag indicating the job status to be enumerated is invalid.

The flag for the status of jobs to enumerate is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0431-E
function-name: The enumerated handle is invalid.

An enumeration handle is incorrect.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0432-E
function-name: The password could not be created.

The function failed to create a password for the VOS3 user.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU0433-E
function-name: The execution start date for the specified job is too long.

The start date/time for the specified job is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0434-E
function-name: The name of the host to which the status is reported is too long.

The name of the destination host for status notification is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0435-E
function-name: No destination is specified for storing the current concurrently-executable job limit.

The storage area for the current number of concurrently-executable job limit to acquire is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0436-E
function-name: No destination is specified for storing the number of currently executing jobs.

The storage area for the number of currently executed jobs to acquire is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0437-E
function-name: No type is specified for the job status to be reported.

The job status type for the status notification to send is not specified.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0438-E
function-name: The warning end threshold value exceeds the abnormal end threshold value.

The threshold for warned termination exceeds the threshold for abnormal termination.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0439-E
function-name: The moving destination queue cannot be specified when the home agent host name is specified.

You cannot specify the destination queue if you specify an agent host as the host from which to move jobs.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0440-E
function-name: The direction of the job insert relative position cannot be specified when moving to another queue.

You cannot specify the direction of the relative position where to insert jobs when moving jobs to another queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0441-E
function-name: The job insert relative position cannot be specified when moving to another queue.

You cannot specify the relative position where to insert jobs when moving jobs to another queue.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU0442-W
function-name: The standard output file used in the system could not be deleted.

The function failed to delete the standard output file that the system uses.

(S)

Continues requested processing.

KAVU0443-W
function-name: The standard error output file used in the system could not be deleted.

The function failed to delete the standard error output file that the system uses.

(S)

Continues requested processing.

KAVU0451-E
function-name: The exclusive execution resource name is not specified.

The exclusive execution resource name is missing. The information cannot be displayed.

(S)

Cancels the requested processing.

(O)

Specify the exclusive execution resource name, and then call the function again.

KAVU0452-E
function-name: The size of exclusive execution resource name buffer is not specified.

The size of the buffer for the exclusive execution resource name is missing. The information cannot be acquired.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0453-E
function-name: The maximum number of queuing jobs is out of range.

The maximum number of queued jobs is out of range (1 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the maximum number of queued jobs, and then call the function again.

KAVU0454-E
function-name: The warning number of queuing jobs is out of range.

The number of queued jobs that causes a warning message is out of range (1 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the warning number of queued jobs, and then call the function again.

KAVU0455-E
function-name: The priority value is not specified.

The priority is missing.

(S)

Cancels the requested processing.

(O)

Specify the priority, and then call the function again.

KAVU0456-E
function-name: The exclusive execution resource information is not specified.

The information about the exclusive execution resource is not set.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0457-E
function-name: The job number is not specified.

The job number is missing.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0458-E
function-name: The concurrently-executable job limit is invalid.

The time value of the concurrently-executable job limit is invalid, or the concurrently-executable job limit is out of range (0 to 4,294,967,295).

(S)

Cancels the requested processing.

(O)

Specify the appropriate value for the concurrently-executable job limit, and then call the function again.

KAVU0459-E
function-name: The maximum number of jobs is not specified.

The maximum number of queued jobs is missing.

(S)

Cancels the requested processing.

(O)

Specify the maximum number of queued jobs, and then call the function again.

KAVU0460-E
function-name: The warning number of jobs is not specified.

The warning number of queued jobs is missing.

(S)

Cancels the requested processing.

(O)

Specify the warning number of queued jobs, and then call the function again.

KAVU0461-E
function-name: The exclusive execution resource status is invalid.

The status of the exclusive execution resource is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0462-E
function-name: Job number that use the exclusive execution resource is invalid.

The number of the jobs that is using the exclusive execution resource is invalid.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0463-E
function-name: The warning number of jobs cannot be larger than the max number of jobs.

The warning number of queued jobs for the specified queue is larger than the maximum number of queued jobs allowed for that queue, or the maximum number is smaller than the warning number.

If you modify the warning number of queued jobs, compare it to the maximum number currently set for the queue. If you modify the maximum number, compare it to the warning number currently set for the queue.

(S)

Cancels the requested processing.

(O)

Check the values you specified or the values currently set for the queue, and modify them to appropriate values. Then, call the function again.

KAVU0464-E
function-name: An invalid exclusive execution resource name was returned.

The manager returned an invalid exclusive execution resource name.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0465-E
function-name: The specified port number is invalid.

If you set the option to specify the port number, the system recognizes the value following the colon (:) in the queue name as the port number. Specify the port number that consists of five digits or less.

(S)

Cancels the requested processing.

(O)

Specify the correct port number, and then call the function again.

KAVU0466-E
function-name: The agent name cannot be changed.

The agent host name is specified for modifying the queue name.

(S)

Cancels the requested processing.

(O)

Specify the correct queue name, and then call the function again.

KAVU0467-E
function-name: The specification of the manager host name is invalid (host-name).

The host name specified as the manager host name is invalid.

(S)

Cancels command execution.

(O)

Check whether a remote host name is specified for an urgent command, and then call the function again.

KAVU0470-E
The job termination request failed.

The agent host was requested to forcibly terminate a job, but the attempt to forcibly terminate the job has failed.

(S)

Cancels the requested processing.

(O)

See the explanation of the KAVU message that was output before or after this message. Also use the integrated trace logs for the manager host and agent host to check whether a KAVU message for this job was output. If it was output, also see the explanation of that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU0471-W
The job does not exist. But the job might have ended.

A forced termination of a job was requested, but the requested job was not found.

(S)

Terminates the requested processing.

(O)

The job might not have been executed, or the job might have terminated on the agent host before the forced termination. Use either of the following methods to check the status of the job.

For a PC job, UNIX job, action job, or custom job:
Check JP1/AJS - View or execute the ajsshow command.

For a QUEUE job or submitted job:
Execute the jpqjobget command.

Other probable causes of the error are:

The JP1/AJS3 service on the agent host stopped after the sending of job information from the agent host to the manager host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

Use the integrated trace logs for the manager host and agent host to check whether a KAVU message for this job was output. If it was output, also see the explanation of that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU0476-E
function-name: The job number cannot be assigned.

The job number cannot be assigned because the number of jobs that have not ended yet has exceeded the limit.

(S)

Terminates the requested processing.

(O)

Wait for an executing job to end, and then re-execute the job.

KAVU0477-E
function-name: Insufficient tablespace or RDAREA.

There is no free space in the tablespace or RDAREA.

(S)

Terminates the requested processing.

(O)

Create free space (for example, reorganize the tablespace or RDAREA or increase the tablespace), and then re-execute the job.

A detailed error message regarding the database is output to the Windows event log or syslog. For an embedded DB, the KFPH00211-I message is output. For details about how to reorganize the database, see 10.2.2 Reorganizing a database in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU0478-E
function-name: The database table is locked.

The database table is now locked.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0479-E
function-name: You lack operate permission for the database.

The user attempting the operation does not have operate permission for the database.

(S)

Terminates the requested processing.

(O)

Specify a user that has the required permission, and re-issue the call.

KAVU0480-E
function-name: Could not connect to the database.

The system could not connect to the database.

(S)

Terminates the requested processing.

(O)

Check whether the database is running.

If this message is output while JP1/AJS3 is running, start the database and then restart JP1/AJS3

KAVU0481-E
function-name: A system error occurred during a database process.

A system error occurred during database processing.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

If this message is output while JP1/AJS3 is running, check whether the database is running. If the database is not running, start the database and then restart JP1/AJS3.

KAVU0482-E
function-name: A logical contradiction occurred during a database process.

An invalid parameter was detected during database processing.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0483-E
function-name: The system file(system-file-name) cannot be opened.

An attempt to open the system file has failed.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0484-E
function-name: The system file cannot be closed. (number of files: number-of-files)

An attempt to close the system file has failed.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0485-E
function-name: The system file(system-file-name) cannot be accessed.

An attempt to access the system file has failed.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0486-E
function-name: The system file(system-file-name) cannot be written.

An attempt to write to the system file has failed.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0487-E
function-name: The system file(system-file-name) cannot be read.

An attempt to read the system file has failed.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0488-E
function-name: A system call error occurred in the internal process.

A system call error occurred in the internal process.

(S)

Terminates the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0489-E
function-name: The system file(system-file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions. The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp\schedule

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp/schedule

When a logical host is used
shared-directory/jp1ajs2/tmp/schedule

KAVU0490-W
function-name: The system file(system-file-name : reason-code) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions. If necessary, delete the file indicated by system-file-name in the message.

The default of the AJSTMPDIR environment setting parameter is as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp\schedule

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp/schedule

When a logical host is used
shared-directory/jp1ajs2/tmp/schedule

KAVU0500-E
function-name: Database information could not be obtained.

Database information about the job execution environment could not be obtained.

(S)

Cancels the requested processing.

(O)

Check the following, and then call the function again:

Check whether system resources are sufficient.

Check whether the environment settings for JP1/AJS3 have been made correctly.

Check whether the database has been created correctly.

KAVU0800-I
The user profile was registered.

The jpqreguser command registered VOS3 user information in the JP1/AJS3 host.

(S)

Continues processing.

KAVU0801-I
The user profile was deleted.

The jpqreguser command deleted VOS3 user information from the JP1/AJS3 host.

(S)

Continues processing.

KAVU0802-I
The user profile was updated.

The jpqreguser command updated VOS3 user information.

(S)

Continues processing.

KAVU0803-I
The user profile information will be enumerated.

The jpqreguser command will now start the enumeration of registered VOS3 user information.

(S)

Continues processing.

KAVU0804-I
Enumerating user profile information ended normally.

The jpqreguser command terminated the enumeration of registered VOS3 user information normally.

(S)

Continues processing.

KAVU0810-I
The job (job-number) was submitted.

The job was registered.

(S)

Continues processing.

KAVU0811-I
The job (job-number) was canceled.

The job was terminated forcibly. A job that is waiting for execution, being held, or waiting for time is canceled. Alternatively, a job being executed is terminated forcibly.

(S)

Continues processing.

KAVU0812-I
The job (job-number) status was changed (held / released).

The job status was changed to held or released.

(S)

Continues processing.

KAVU0813-I
The job (job-number) was moved.

The job in the queue was moved.

(S)

Continues processing.

KAVU0814-I
The job (job-number) information was deleted.

The job information and the result file for the terminated job have been deleted from the job execution environment database.

(S)

Continues processing.

KAVU0815-I
The job (job-number) information will be displayed.

The job information (including the job number, job name, job status, and registration time) will be output.

(S)

Continues processing.

KAVU0816-I
Displaying the job information ended normally.

The display of job information terminated normally.

(S)

Continues processing.

KAVU0817-I
JP1 user (assumed-JP1-user-name) is registered for assumed JP1 user.

The system registers the specified JP1 user as an assumed JP1 user and enables the JP1 user assuming function.

(S)

Continues processing.

KAVU0818-I
Assumed JP1 user(assumed-JP1-user-name) is deleted.

The assumed JP1 user was deleted.

(S)

Continues processing.

KAVU0819-I
Assumed JP1 user (assumed-JP1-user-name) is registered.

The currently registered assumed JP1 user is displayed.

(S)

Continues processing.

KAVU0820-I
The job information will be enumerated.

The list of job information for unfinished jobs will be displayed.

(S)

Continues processing.

KAVU0821-I
Enumerating the job information ended normally.

The display of job information (including the job number, job name, and job status) for unfinished jobs terminated normally.

(S)

Continues processing.

KAVU0822-I
Assumed JP1 user is not registered.

The assumed JP1 user is not currently registered.

(S)

Continues processing.

KAVU0825-I
The end job information will be enumerated.

The list of job information for terminated jobs will be displayed.

(S)

Continues processing.

KAVU0826-I
Enumerating the end job information ended normally.

The display of a job information list (including the job number, job name, and job status) for terminated jobs terminated normally.

(S)

Continues processing.

KAVU0835-I
Queue Entrance / Queue Exit of the queue (queue-name) was opened.

The job entrance or exit interface of the queue was opened.

(S)

Continues processing.

KAVU0836-I
Queue Entrance / Queue Exit of the queue (queue-name) was closed.

The job entrance or exit interface of the queue was closed.

(S)

Continues processing.

KAVU0837-I
The queue (queue-name) information will be displayed.

The queue information (including the queue name, the maximum number of jobs that can be registered, the warning value for the registered jobs, and the number of registered jobs) will be displayed.

(S)

Continues processing.

KAVU0838-I
Default queue (queue-name) information will be displayed.

The default queue information (including the queue name, the maximum number of jobs that can be registered, the warning value for the registered jobs, and the number of registered jobs) will be displayed.

(S)

Continues processing.

KAVU0839-I
All queue information except default queue will be displayed.

Information about queues other than the default queue will be displayed.

(S)

Continues processing.

KAVU0840-I
All queue information including default queue will be displayed.

Information about all of the queues including the default queue will be displayed.

(S)

Continues processing.

KAVU0841-I
The queue names will be enumerated.

The queue names other than the default queue will be output.

(S)

Continues processing.

KAVU0842-I
Displaying the queue information ended normally.

The display of queue information terminated normally.

(S)

Continues processing.

KAVU0850-I
The agent (agent-name) definition was changed.

The agent definition information (maximum number of concurrently executable jobs) was changed.

(S)

Continues processing.

KAVU0851-I
The agent host (agent-name) information will be displayed.

The agent host information will be displayed.

(S)

Continues processing.

KAVU0852-I
All agent host information will be displayed.

All agent host information will be displayed.

(S)

Continues processing.

KAVU0853-I
The agent host names will be enumerated.

All the agent host names will be displayed.

(S)

Continues processing.

KAVU0854-I
Displaying the agent host information ended normally.

The display of agent host information terminated normally.

(S)

Continues processing.

KAVU0860-I
The queue (queue-name) was added.

The queue was added.

(S)

Continues processing.

KAVU0861-I
The queue (queue-name) was deleted.

The queue was deleted.

(S)

Continues processing.

KAVU0862-I
The queue (queue-name) definition was changed.

The queue definition information was changed.

(S)

Continues processing.

KAVU0863-I
The agent (agent-name) was connected.

The queue was connected to the agent.

(S)

Continues processing.

KAVU0864-I
The agent (agent-name) was released.

The connection between the queue and the agent was released.

(S)

Continues processing.

KAVU0865-I
The agent (agent-name) was added.

The agent host was added.

(S)

Continues processing.

KAVU0866-I
The agent (agent-name) was deleted.

The agent host was deleted.

(S)

Continues processing.

KAVU0867-I
The exclusive execution resource name (execution-locked-resource-name) was added.

The exclusive execution resource was added.

(S)

Continues processing.

KAVU0868-I
The exclusive execution resource name (execution-locked-resource-name) was deleted.

The exclusive execution resource was deleted.

(S)

Continues processing.

KAVU0869-I
The exclusive execution resource name will be enumerated.

All the exclusive execution resource names will be displayed.

(S)

Continues processing.

KAVU0870-I
The exclusive execution resource (execution-locked-resource-name) information will be displayed.

Information about the exclusive execution resource will be displayed.

(S)

Continues processing.

KAVU0871-I
All exclusive execution resource information will be displayed.

Information about all the exclusive execution resources will be displayed.

(S)

Continues processing.

KAVU0872-I
Enumerating the exclusive execution resource name ended normally.

Enumerating the exclusive execution resource names locked for execution terminated normally.

(S)

Continues processing.

KAVU0873-I
Displaying the exclusive execution resource (execution-locked-resource-name) information ended normally.

The display of information about the exclusive execution resource terminated normally.

(S)

Continues processing.

KAVU0874-I
Displaying all exclusive execution resource information ended normally.

The display of information about all the exclusive execution resources terminated normally.

(S)

Continues processing.

KAVU0875-I
The agent (agent-name) priority was changed.

The priority of the connected agent host was changed.

(S)

Continues processing.

KAVU0900-E
Invalid option (option-name).

An invalid option is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0901-E
The option (option-name) is used more than once.

The option is used more than once.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0902-E
A required option (option-name) is missing.

A required option is not specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0903-E
Only administrator can use option (option-name).

Only the administrator can use the option.

(S)

Cancels command execution.

(O)

Re-execute the command as an administrator.

KAVU0904-E
Illegal character (invalid-character) in operand (operand-name).

The argument includes an invalid character.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0905-E
The operand (operand-name) exceeds the specifiable number of characters (number-of-characters).

The number of characters used in the argument exceeds the maximum.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0906-E
A required operand (operand-name) is missing.

A required argument is not specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0907-E
Value (preset-value) in operand (operand-name) exceeds the limit.

A value exceeding the maximum is specified in an argument.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0908-E
Character (invalid-character) in operand (operand-name) is not a number.

An argument includes a non-numeric character.

(S)

Cancels command execution.

(O)

Specify a number for the argument, and then re-execute the command.

KAVU0909-E
Invalid data format in operand (operand-name).

The data format of the argument is incorrect.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0910-E
An unexpected error occurred. (reason code:reason-code)

Invalid data was detected during parameter analysis.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0911-E
The options (option-name) and (option-name) cannot be specified simultaneously.

The indicated two options cannot be both present.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0912-E
Environment settings or the logical host name is invalid.

The environment settings are incorrect or the logical host name is invalid.

(S)

Cancels command execution.

(O)

Check the environment settings or the logical host name, and then re-execute the command.

KAVU0913-E
Unexpected error occurred. Aborted. (module:reason-location[reason-location], (reason code:reason-code)

Initialization failed at the time of a command startup.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0914-E
Insufficient options specified.

The required option is missing.

(S)

Cancels command execution.

(O)

Specify the option, and then re-execute the command.

KAVU0917-E
The specification of the manager host name is invalid.

The host name specified as the manager host name is invalid.

(S)

Cancels command execution.

(O)

Check whether a remote host name is specified for an urgent command, and then call the function again.

KAVU0920-E
Parameter is specified incorrectly.

An incorrect parameter is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0921-E
The command could not be executed because of internal factor.

The system failed to execute the command because of an internal factor.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0922-E
Memory became insufficient.

Memory became insufficient.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute the command. If the same message reappears, re-estimate memory.

KAVU0923-E
A logical contradiction occurred.

An invalid error was detected during command initialization.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0924-E
The file cannot be opened because file path or file does not exist at the send source.

The system cannot open the file because the file path of the transfer source file is incorrect or the file does not exist.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0925-E
The file cannot be opened because you lack access permission for the file at the send source.

The system cannot open the file because the access authority for the transfer source file is not granted.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0926-E
The file cannot be opened because some other process is using the file at the send source.

The system cannot open the file because another process is using the transfer source file.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU0927-E
The file at the send source cannot be opened.

The system cannot open the transfer source file.

(S)

Cancels command execution.

(O)

The system may not accept the format or the length of the file name. Check the original file name specified.

KAVU0928-E
The file at the send source cannot be read.

The system failed to read the transfer source file.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0929-E
No file path is specified for the file that acquires the standard output file or standard error output file, so the file cannot be created.

A file cannot be created because no file path has been specified for the file used to acquire the data in the standard output file or the standard error output file.

If the jpqjobget command was used, no file was specified in the -oso or -ose option.

(S)

Cancels command execution.

(O)

Check whether a file (and its path) has been specified for the file used to acquire the data in the standard output file or the standard error output file. If there is neither a file nor a path, create them both, and then re-execute the command.

KAVU0930-E
You lack access permission for the file specified as the file that acquires the standard output file or standard error output file, so the file cannot be created.

A file cannot be created because no access permissions have been set for the file used to acquire the data in the standard output file or the standard error output file.

If the jpqjobget command was used, there is no write permission on the file specified in the -oso or -ose option.

(S)

Cancels command execution.

(O)

Check the access permissions on the file specified as the file used to acquire the data in the standard output file or the standard error output file. If there is no write permission, set write permission, and then re-execute the command.

KAVU0931-E
Insufficient disk space. The file specified as the file that acquires the standard output file or standard error output file cannot be written.

The system cannot write the standard output file and standard error output file to the disk because the disk does not have sufficient free space.

(S)

Cancels command execution.

(O)

Increase the free space in the disk, and then re-execute the command.

KAVU0932-E
The file specified as the file that acquires the standard output file or standard error output file is being used in another process, so it cannot be opened.

The file cannot be opened because another process is using the file specified as the file used to acquire the data in the standard output file or the standard error output file.

(S)

Cancels command execution.

(O)

Check whether another process is accessing the file specified as the file used to acquire the data in the standard output file or the standard error output file. If necessary, terminate the process accessing the specified file, and then re-execute the command.

KAVU0933-E
The file specified as the file that acquires the standard output file or standard error output file cannot be created.

The file specified to be used to acquire the data in the standard output file or the standard error output file cannot be created.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0934-E
The file specified as the file that acquires the standard output file or standard error output file could not be written.

An attempt to write to the file specified as the file used to acquire the data in the standard output file or the standard error output file failed.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0935-W
The standard output file or standard error output file contains 0 bytes of data.

No file was found when the jpqjobget command was used to acquire data in the standard output file or the standard error output file.

(S)

Terminates command processing.

KAVU0936-E
Environment settings or the logical host name information is invalid.

An error occurred during reading of the environment setting parameters because the environment settings or logical host name information was invalid.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the command. For UNIX, also check whether the user executing the command has read permission for /opt/jp1/hcclibcnf/regdir/HKEY_LOCAL_MACHINE.dat.

Also, if the integrated trace log contains the KAVU7221-E message (Environment setting parameter (parameter-name=parameter value) on the logical host (logical-host-name) is invalid.), the OS user executing the command might not have been granted write and read permissions for the output path. If this is the case, grant write and read permissions, and then re-execute the command.

KAVU0937-E
Job could not be submitted because agent host (agent-host-name) was failed to create automatically.

The agent could not be automatically created. This prevented the job from being submitted.

(S)

Cancels command execution.

(O)

For details about the cause of the error, check the integrated trace log for a KAVU message output before or after this message, remove the cause of the error, and then re-execute the submit job.

KAVU0938-E
Assumed JP1 user is not registered.

The assumed JP1 user has not been registered, or an invalid assumed JP1 user has been registered.

(S)

If the assumed JP1 user has not been registered, the system cancels the requested processing. If an invalid assumed JP1 user has been registered, the system deletes it.

(O)

Execute the jpqregguestuser command to check whether the assumed JP1 user has already been registered. For details about the jpqregguestuser command, see jpqregguestuser in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0939-E
Cannot access registry. Aborted. (module: error-location [error-location], reason code: reason-code)

Processing of the jpqregguestuser command was canceled because the configuration definition information could not be accessed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0942-E
The agent (agent-host-name) cannot be added because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of addition of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being added due to a notification error.

(S)

Cancels command execution.

(O)

Wait until the agent configuration definition has been changed by the other jpqagtadd and jpqagtdel commands, and then retry the operation.

KAVU0943-E
The agent (agent-host-name) cannot be deleted because the Event Action Manager is processing the modification of the agent.

The Event Action Control Manager is notified of deletion of an agent. However, the Event Action Manager has already been modifying the agent configuration preventing the agent from being deleted due to a notification error.

(S)

Cancels command execution.

(O)

Wait until the agent configuration definition has been changed by the other jpqagtadd and jpqagtdel commands, and then retry the operation.

KAVU0944-E
The information cannot be displayed because of adding or changing processing.

The information could not be displayed because a queue, agent, or exclusive execution resource is being added or modified.

(S)

Cancels the requested processing.

(O)

Wait until the addition or modification terminates, and then re-execute the command.

KAVU0945-E
The manager cannot be connected.

The system cannot connect the manager.

(S)

Cancels command execution.

(O)

Make sure that the daemon is started, TCP/IP communication is available under the specified logical host name. Then, re-execute the command.

KAVU0946-E
IP address could not be acquired from the manager host name.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels command execution.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then re-execute the command.

KAVU0947-E
The agent (agent-host-name)cannot be deleted because some event job is being executed.

The specified agent host cannot be deleted because there are event jobs being executed.

(S)

Cancels command execution.

(O)

Wait until the event job execution terminates, and then re-execute the command.

KAVU0948-E
The maximum number of jobs or the warning number of jobs must be specified.

Specify either the maximum number or the warning number of queued jobs. It is a required option.

(S)

Cancels command execution.

(O)

Specify either the maximum number or the warning number of queued jobs. Then, re-execute the command.

KAVU0949-E
The specified agent (agent-host-name) cannot be released because some job is being executed.

The specified agent cannot be disconnected because there are jobs being executed.

(S)

Cancels command execution.

(O)

Wait until the job terminates, and then re-execute the command.

KAVU0950-E
The manager status does not accept requests.

The current status of the manager process for job execution control does not permit it to accept requests.

(S)

Cancels command execution.

(O)

Make sure that the JP1/AJS3 service on the manager host is not in either of the following states and then re-execute the command.

Being started or being stopped

In maintenance mode

KAVU0951-E
The specified queue does not exist.

The specified queue definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqqueshow command to check the queue definition information. After checking for whether the specified queue definition information exists, retry the operation.

If you did not find the queue definition information, use the jpqqueadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0952-E
The specified agent does not exist.

The specified agent definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about the commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0953-E
No response from the manager.

There was no response from the manager process for job execution control.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to determine the cause of the error and correct it if there is. Then, re-execute the command. If you did not find an error, then no response was returned because the manager process for job execution control was processing another request. In this case, the processing continues even if the command execution is canceled. Use the command or the integrated trace information log to check the result of the requested processing.

KAVU0954-E
The command could not be executed because of internal factor at the manager.

Execution of the command failed for a reason internal to the manager process for job execution control.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVU message was output before or after this message. If a KAVU message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVU message has been output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0955-E
The specified queue is closed.

No jobs can be registered because the specified queue entrance is closed.

(S)

Cancels command execution.

(O)

The job entrance interface of the specified queue may be closed. Execute the jpqqueopen command to open the interface of the specified queue, and then re-execute the command. For details about the command, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0956-E
The number of queued jobs in the specified queue reached the limit or the queue resources reached the limit.

The number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue or the maximum number of jobs allowed in the system.

(S)

Cancels command execution.

(O)

Either wait for an executing job to end and then issue another request, or review the queue definition information and adjust the maximum number of jobs allowed in the queue or the system.

If the maximum number of jobs allowed in the queue has been reached, the KAVU4515-W message is output to the integrated trace log. If the maximum number of jobs allowed in the system has been reached, the KAVU4520-W message is output to the integrated trace log.

Take the corrective action specified in the message that is output.

KAVU0957-E
You lack execute permission for this command.

The user trying to execute the command does not have permission for the command operation. An access permission error occurred on the authentication server used by the manager requested to perform the processing.

(S)

Cancels command execution.

(O)

When a command for job execution control (jpqxxxx command) is used to perform an operation on a single job in the job execution environment or on the job execution environment itself, check the permissions for the JP1 user name that is the same as the OS user name executing the command.

Check whether the OS user executing the command has been registered as a JP1 user on the authentication server and whether the JP1 permission level required for command execution has been set for the JP1 resource group (JP1_Queue) for that JP1 user (OS user).

For details about the execute permission required for commands, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. For details about how to set JP1 permission levels, see 3.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 12.1.1(1) Setting user information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

For Windows, if UAC is being used, the administrator must re-execute the command.

KAVU0958-W
The job does not exist.

For jpqjobshow or jpqendjobshow execution, output occurs when there are no corresponding jobs at all. However, for execution of any other command, output occurs when there is no corresponding job for the specified job number.

(S)

For the jpqjobshow or jpqendjobshow command, the system terminates the command. For a command other than jpqjobshow and jpqendjobshow commands, the system cancels executing the command.

(O)

If you executed a command other than jpqjobshow and jpqendjobshow commands, check the specified job number is correct and then re-execute the command.

KAVU0959-E
The job has already started.

The job has already started. You cannot execute the jpqjobmove or jpqjobalt command for any job for which execution has already started.

(S)

Cancels command execution.

(O)

Execute the jpqjobmove or jpqjobalt command for a job whose execution has not started yet.

KAVU0960-E
The job did not end yet.

The job is not terminated yet.

(S)

Cancels command execution.

(O)

The jpqjobdel command cannot be executed for any job whose execution has not ended yet. Wait for the job to end, and then retry the operation.

KAVU0961-E
The specified destination queue does not exist.

The specified destination queue does not exist.

(S)

Cancels command execution.

(O)

Make sure there is a destination queue, and then re-execute the command.

KAVU0962-E
The job cannot be moved. There are too many queued jobs in destination queue.

You cannot move jobs to the destination queue because the maximum number of jobs that the queue can contain is reached.

(S)

Cancels command execution.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0963-W
There is no queue in the manager.

There is no queue definition information on the manager host specified by the jpqqueshow command.

(S)

Terminates command processing.

KAVU0964-E
No agent is connected to the manager.

The specified agent definition information does not exist.

(S)

Cancels command execution.

(O)

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0965-E
The manager is busy.

The manager is busy.

(S)

Cancels command execution.

(O)

Re-execute the command after a while.

KAVU0966-E
Memory became insufficient at the manager.

Memory became insufficient at the manager.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute the command. If the same message reappears, re-estimate memory.

KAVU0967-E
VOS3 user information is invalid.

The JP1/OJE for VOS3 user information registered by the jpqreguser command is invalid.

(S)

Cancels command execution.

(O)

Execute the -a option in the jpqreguser command to check whether the user information has been registered correctly, and then re-execute the command.

For details about the jpqreguser command, see jpqreguser in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0968-E
A fatal error occurred in the manager.

A fatal error occurred in the manager.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVU message was output before or after this message. If a KAVU message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVU message was output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0969-E
A logical contradiction occurred in the manager.

A logical contradiction occurred in the manager.

(S)

Cancels command execution.

(O)

Check the integrated trace log for whether a KAVU message was output before or after this message. If a KAVU message was output, read the message explanation, remove the cause of the error, and then retry the operation. If no KAVU message was output or if you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU0970-E
That request is not supported by the requested manager.

An unsupported request (such as queue operation and agent operation) might have been executed on a non-JP1/AJS3 host such as JP1/NQSEXEC or JP1/OJE for VOS3.

(S)

Cancels command execution.

(O)

Check whether the request is supported by another system product of the requester.

For details about the supported functions of each command, see 1.3 Linkage with other programs in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0971-E
An error occurred after submission.

An error occurred after a job was submitted.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0972-E
The execution environment is invalid.

The execution environment is incorrect.

(S)

Cancels command execution.

(O)

The authentication server may not be started. If this is the case, start the authentication server. If the authentication server has been started, use the integrated trace information log to determine the cause of the error and correct it. Then, call the function again.

KAVU0973-E
The transfer file could not be created on the manager.

The system failed to create a transferred file in the manager.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0974-E
The transfer file could not be written on the manager.

The system failed to write a transferred file to the manager.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the command.

KAVU0975-E
The job was forcibly terminated, but it might not have terminated.

An attempt was made to forcibly terminated the job but the job may still be running.

(S)

Terminates command execution.

(O)

Use the integrated trace information log to check the cause of the error.

KAVU0976-E
The exclusive execution resource name (exclusive-execution-resource-name) cannot be deleted because some job is being executed.

The specified exclusive execution resource cannot be deleted because there are jobs being executed.

(S)

Terminates command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0977-E
The specified agent (agent-host-name) is not connected.

The specified agent host is not connected to the queue.

(S)

Terminates command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0978-E
The agent (agent-host-name) is already connected.

The specified agent host has already been connected.

(S)

Terminates command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0979-E
The queue (queue-name) definition cannot be changed because some job is being submitted.

The queue definition could not be changed because jobs are being submitted in the queue.

(S)

Terminates command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0980-E
The agent (agent-host-name) cannot be registered because the agents exceeds the maximum number defined in the environment settings.

The agent cannot be added because the number of agents exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary agents or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0981-E
The queue (queue-name) cannot be registered because the queue exceeds the maximum number defined in the environment settings.

The queue cannot be added because the number of queues exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary queues or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0982-E
The exclusive execution resource (exclusive-execution-resource-name) cannot be registered because the exclusive execution resource exceeds the maximum number defined in the environment settings.

The exclusive execution resource cannot be added because the number of exclusive execution resources exceeds the maximum number defined in the environment settings.

(S)

Terminates command execution.

(O)

Delete unnecessary exclusive execution resources or recheck the maximum number defined in the environment settings. Then, re-execute the command.

KAVU0983-E
The warning number of jobs is larger than the number of maximum number of jobs.

The warning number of queued jobs cannot be larger than the maximum number of queued jobs.

(S)

Terminates command execution.

(O)

Specify the appropriate warning number of queued jobs, and then re-execute the command.

KAVU0984-E
The maximum number of jobs is less than the number of warning number of jobs.

The maximum number of queued jobs cannot be smaller than the warning number of queued jobs.

(S)

Terminates command execution.

(O)

Specify the appropriate maximum number of queued jobs, and then re-execute the command.

KAVU0985-E
The user profile is not registered. (user:user-name, remote-host:remote-host-name)

User information is not registered.

(S)

Cancels command execution.

(O)

Check the user to be deleted, and then re-execute the command.

KAVU0986-W
The user profile does not exist.

No user information is registered.

(S)

Terminates command processing.

KAVU0987-E
The password could not be scrambled. (reason code:reason-code)

The system failed to scramble the password.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0988-E
The password could not be unscrambled. (reason-code)

The system failed to unscramble the password.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU0989-E
You lack access permission for, so process cannot be done.

The operation is impossible because you do not have high enough access authority.

(S)

Cancels command execution.

(O)

Check the access permission for the user who issued the request.

KAVU0990-E
The queue (queue-name) cannot be deleted because some job is being executed.

You cannot delete the queue because jobs are being executed in the queue.

(S)

Cancels command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0991-E
The specified agent (agent-host-name) cannot be deleted because some queue is connected.

You cannot delete the agent because the agent is not disconnected from the queue.

(S)

Cancels command execution.

(O)

Use the jpqagtunlink command to cancel the agent-queue connection, and then re-execute the original command. For details about the jpqagtunlink command, see jpqagtunlink in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0992-E
The specified exclusive execution resource name (exclusive-execution-resource-name) does not exist.

The specified exclusive execution resource name is not defined.

(S)

Cancels command execution.

(O)

Specify the correct exclusive execution resource name, and then re-execute the command.

KAVU0993-W
There is no exclusive execution resource information to enumerate.

There is no exclusive execution resource information.

(S)

Cancels command execution.

KAVU0994-E
The maximum number of jobs or the warning number of jobs or the new queue name must be specified.

The maximum number of jobs allowed in the queue, the warning value for number of jobs in the queue, and the new queue name cannot all be omitted. At least one of these values must be specified.

(S)

Cancels command execution.

(O)

Specify one of the maximum number of queued jobs, the warning number of queued jobs, and the new name of the queue. Then, re-execute the command.

KAVU0995-E
The specified agent (agent-host-name) does not exist.

The specified agent is not defined.

(S)

Cancels command execution.

(O)

Specify the correct agent host name.

You can use the jpqagtshow command to check the agent definition information. After checking for whether the specified agent definition information exists, retry the operation.

If you did not find the agent definition information, use the jpqagtadd command to add it dynamically.

For details about commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU0996-E
The agent (agent-host-name) cannot be deleted because some job is being executed.

You cannot delete the agent because jobs are being executed in the agent.

(S)

Cancels command execution.

(O)

Wait until the job execution terminates, and then re-execute the command.

KAVU0997-E
The agent information (agent-host-name) already exists.

The information about the specified agent has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

Specify the correct agent host name, and then re-execute the command.

KAVU0998-E
The queue information (queue-name) already exists.

The information about the specified queue has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

Specify the correct queue name, and then re-execute the command.

KAVU0999-E
The exclusive execution resource information (exclusive-execution-resource-name) already exists.

The information about the specified exclusive execution resource name has already been defined preventing it from being added.

(S)

Cancels command execution.

(O)

Specify the correct exclusive execution resource name, and then re-execute the command.

KAVU1100-I
Started process monitor (logical-host-name).

The process monitor started.

(S)

Continues starting the daemon.

KAVU1101-I
Process monitor (logical-host-name) ended normally.

The process monitor terminated normally.

(S)

Stops the daemon.

KAVU1102-E
Process monitor (logical-host-name) ended abnormally. (reason code:reason-code)

The process monitor for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1103-I
Process monitor (logical-host-name) is already running on the same host.

You cannot activate more than one daemon in the same host.

(S)

Stops starting the daemon.

(O)

Check whether the JP1/AJS3 service is running.

If the JP1/AJS3 service is not running, this message might be output if the JP1/AJS3 service is restarted after abnormal termination. In this case, see 2.1(2) A JP1/AJS3 service has not started in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting, and take corrective action as necessary.

KAVU1104-E
An abnormal end of job execution control was detected.

The process monitor terminated abnormally because it detected the end of the agent process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1105-E
An abnormal end of job queuing control was detected.

The process monitor terminated abnormally because it detected the end of the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1106-E
Job execution control process ended abnormally. (name : process-name, code : end-code, pid : process-ID, sig : signal-number)

The process indicated in process-name terminated abnormally with the end code indicated in end-code.

In UNIX:

When the signal number is other than 0, the process terminated abnormally in response to the signal for the signal number.

In Windows:

The signal number is 0.

The probable causes are:

A JP1/AJS3 resident process was terminated abnormally by a signal.

A JP1/AJS3 resident process was terminated forcibly by jajs_killall.cluster command.

(S)

Terminates job execution control.

(O)

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1).

To continue the operation, collect data and then restart JP1/AJS3.

There is no problem if this message appears when jajs_killall.cluster command is executed.

KAVU1201-E
The logical host (logical-host-name) is invalid.

The length of the logical host name specified in the JP1_HOSTNAME environment variable is invalid.

(S)

Stops the JP1/AJS3 service.

(O)

Check the logical host name specified in the JP1_HOSTNAME environment variable for error, correct the cause of the error, and then restart JP1/AJS3.

KAVU1202-E
An error occurred while obtaining environment settings on the logical host (logical-host-name). (reason code:reason-code)

An error occurred while obtaining environment settings of the logical host.

(S)

Stops the daemon.

(O)

Correct the error in the common definition information or correct the invalid definitions, and then restart.

KAVU1203-E
The agent process could not be started. (reason code:reason-code)

The system failed to start the agent process.

(S)

Stops the daemon.

(O)

In UNIX, reason code 12 indicates insufficient memory. For reason code 12, allocate sufficient memory required for execution and then retry.

When the message contains reason code 11, the number of processes that started concurrently may temporarily exceed the limit determined by the system. If this message (reason code 11) still appears even after you restart JP1/AJS3, use the kernel parameter to increase the maximum number of processes that can start concurrently. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

If you cannot determine the cause of the error by rechecking the above items or if this message appears in Windows, use the data collection tool to collect data, and then contact the system administrator.

KAVU1204-E
The manager process could not be started. (reason code:reason-code)

The system failed to start the manager process.

(S)

Stops the daemon.

(O)

In UNIX, reason code 12 indicates insufficient memory. For reason code 12, allocate sufficient memory to enable execution and then retry.

When the message contains reason code 11, the number of processes that started concurrently may temporarily exceed the limit determined by the system. If this message (reason code 11) still appears even after you restart JP1/AJS3, use the kernel parameter to increase the maximum number of processes that can start concurrently. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

If you cannot determine the cause of the error by rechecking the above items or if this message appears in Windows, use the data collection tool to collect data, and then contact the system administrator.

KAVU1205-E
A logical contradiction occurred. (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred due to a parameter error during inter-process communication for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU1206-E
The wait for the agent initialization completion was timed out.

A timeout occurred when the system was waiting for the agent process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1207-E
The wait for the manager initialization completion was timed out.

A timeout occurred when the system was waiting for the manager process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1208-E
The manager or the agent could not be forcibly terminated. (reason code:reason-code)

The system failed to forcibly terminate the manager or agent process for job execution control. Reason code 0x00010025 indicates unsuccessful termination of the manager process. Reason code 0x00010024 indicates unsuccessful termination of the agent process.

(S)

Continues forced termination of JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. Manually check whether a manager or agent process exists. If the process exists, forcibly terminate it manually, and then restart JP1/AJS3. If no other message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1211-E
The wait for an event from the agent or the manager failed. (module:reason-location, reason code:reason-code)

The system could not receive an event indicating that initialization had completed from the manager or agent process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1212-E
The wait for an event from the agent or the manager was timed out. (module:reason-location[reason-location], reason code:reason-code)

A timeout occurred when the system was waiting for the manager or agent process for job execution control to be initialized.

(S)

Terminates the JP1/AJS3 service forcibly.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation of that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1220-E
The start daemon could not be notified that initialization was completed. (reason code:reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that initialization had completed.

(S)

Stops the JP1/AJS3 service.

(O)

Check whether a KNAD message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the explanation and correct the cause of the error. Then, restart the JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1221-E
The start daemon could not be notified that planned termination was completed. (reason code:reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that the planned termination had completed.

(S)

Continues processing to stop the JP1/AJS3 service.

(O)

Check whether a KNAD message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the message explanation and correct the cause of the error. Then, restart JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1222-E
The start daemon could not be notified that forced termination was completed. (reason-code)

The system could not notify the JP1/AJS3 startup process (jajs_spmd) that the forced termination had completed.

(S)

Continues processing to stop the JP1/AJS3 service.

(O)

Check whether a KNAD message was output to the integrated trace log. If it was output, see the manual Job Management Partner 1/Base Messages to check the message explanation and correct the cause of the error. Then, restart JP1/AJS3 service. If no such message was output or if you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU1224-E
A logical contradiction occurred in pipe communication process. (module:reason-module[reason-module], reason code:reason-code)

An error occurred during inter-process pipe communication for the process monitor for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1225-E
Forced termination started because the start daemon ended abnormally.

The forced termination started because the start daemon (jajs_spmd) abnormally terminated.

(S)

Stops the daemon.

(O)

Use the integrated trace information log and other information to determine the cause of the termination of the start daemon and correct the error. Then, restart.

KAVU1232-E
An error occurred in process monitoring. Forced termination was sent to the agent and the manager.

A forced termination request was sent to the agent and manager processes because an error occurred in the process monitor for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message to correct the cause of the error, and then restart JP1/AJS3. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU1240-I
A forced termination request was received from the start daemon.

The system received a forced termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Stops the JP1/AJS3 service.

KAVU1241-I
The start daemon was notified about the forced termination.

The system successfully notified the JP1/AJS3 startup process (jajs_spmd) of the completion of forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1242-I
A forced termination was sent to the agent or the manager.

The system sent a forced termination request to the agent and manager processes for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1243-I
Forced termination of the agent was confirmed.

The system confirmed the forced termination of the agent process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1244-I
Forced termination of the manager was confirmed.

The system confirmed the forced termination of the manager process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1250-I
A planned termination request (while waiting for a job in the queue to terminate) was received from the start daemon.

The system received a planned termination request (waiting for the termination of a job in the queue) from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until the queued job terminates, and then stops the JP1/AJS3 service.

KAVU1255-I
Planned termination of the agent was confirmed.

The system confirmed the planned termination of the agent process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1256-I
Planned termination of the manager was confirmed.

The system confirmed the planned termination of the manager process for job execution control.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU1290-I
A jobnet restriction stop request was received from the start daemon.

The system received a jobnet restriction stop request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until all the jobnets being executed terminate, and then stops the JP1/AJS3 service.

KAVU1291-I
A restriction stop request was received from the start daemon.

The system received a job restriction stop request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until all the jobs being executed terminate, and then stops the JP1/AJS3 service.

KAVU2200-W
Any transmission processing over the 100-file limit will be ignored.

The system ignored a request to transfer more than 100 files.

(S)

Cancels transferring files.

(O)

Reduce the number of files to be transferred to 100 or fewer.

KAVU2201-E
The communication protocol parameter (parameter-name) exceeded the limit.

An attempt to analyze the communication protocol has failed in the TCP/IP communication protocol.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2210-W
User mapping (user-name) failed in the file transmission process.

A user could not be mapped during file transfer.

(S)

Cancels the requested processing.

(O)

Check the definition of the user mapping, and then reissue the request.

KAVU2211-W
The user (user-name) could not be masked in file transmission process.

A user could not be masked during file transfer.

(S)

Cancels the requested processing.

(O)

Check the definition of the user mapping, and then reissue the request.

KAVU2212-W
No work path exists, so the transfer file or the result file cannot be created.

A transfer file or result file cannot be created because no work path exists.

(S)

Cancels the requested processing.

(O)

Check whether the following items defined in the environment setting parameters exist: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2213-W
You lack access permission for the work path, so the transfer file or the result file could not be created.

A transfer file or result file cannot be created because you do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Check the access permission for the following items defined in the environment setting parameters: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2214-W
No path (file-name) is specified to the destination for storing transfer files or result files.

No path exists for storing transfer files or result files. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

Check whether the following items defined in the environment setting parameters exist: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2215-W
You lack access permission for the path to the destination for storing transfer files, result files or the file (file-name).

You do not have access permission for the file or for the path for storing transfer files or result files. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

Check the access permission for the following items defined in the environment setting parameters: the work directory for executing the manager process, the work directory for executing the agent process, and the work path for executing the job. Then reissue the request.

KAVU2216-W
The transfer file or the result file (file-name) cannot be opened.

The transfer file or the result file cannot be opened. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of a result file. If any other file name is displayed, the error occurred during creation of a transfer file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the original or destination file name. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, use the data collection tool to collect data, and then contact the system administrator.

KAVU2217-W
Another process is using the transfer file or the result file (file-name).

Another process is using the transfer file or the result file. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of the result file. If any other file name is displayed, the error occurred during creation of the transfer file.

(S)

Cancels the requested processing.

(O)

Check whether another process is using the file specified at the transfer source or destination, and then reissue the request.

If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, use the data collection tool to collect data, and then contact the system administrator.

KAVU2218-W
The transfer file or the result file (file-name) could not be accessed.

An attempt to access the transfer file or the result file has failed. If the file name is M_JPQSTDO_job-number or M_JPQSTDE_job-number, the error occurred during creation of the result file. If any other file name is displayed, the error occurred during creation of the transfer file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2219-W
Because there is no environment settings work path, the transfer file cannot be processed.

The transfer file cannot be processed because no work path exists in the common definition information.

(S)

Cancels the requested processing.

(O)

Check the common definition information, and then reissue the request.

KAVU2220-E
Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message still appears, re-estimate the memory requirements.

Memory might be insufficient because an extremely large file was transferred from the agent to the manager. Check whether any of the following probable causes are present:

A standard output file name is specified in the definition of a job that outputs a large amount of standard output data.

A job is defined that will output a large amount of standard error output data.

The data append option is specified for the standard output file and standard error output file for the job.

A large file is specified for the transfer source file name in the job definition.

Take one of the following actions according to the cause of the error:

Specify a NULL device for the standard output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows. Redirect the standard output in the script file or batch file for the job.

If the standard error output file name is specified in the job definition:
Specify a NULL device for the standard error output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows.
If the standard error output file name is not specified in the job definition:
Specify a NULL device for the standard error output file name in the job definition. In particular, enter /dev/null for a job running in UNIX, and enter NUL for a job running in Windows. Alternatively, redirect the standard error output in the script file or batch file for the job.

Disable the data append option.

Do not specify a large file for the transfer source file name.

Alternatively, for the causes described in 1 to 3 above, delete or save standard output files and standard error output files on a regular basis.

KAVU2221-E
There is insufficient disk space. (module:reason-location[reason-location], reason code:reason-code)

There is an insufficient amount of disk space.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU2222-W
You lack access permission for the environment settings work path, so the transfer file cannot be processed.

The transfer file cannot be processed because you do not have access permission for the work path in the common definition information.

(S)

Cancels the requested processing.

(O)

Check the common definition information, and then reissue the request.

KAVU2223-E
The file name of the transfer file (file-name) could not be changed because the file does not exist.

An attempt was made to rename the specified transfer file to the name of a temporary file on the manager host, but the transfer file was not found due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2224-E
The file name of the transfer file (file-name) could not be changed because there was no access permission to the file (file-name).

An attempt was made to rename the specified transfer file to the name of a temporary file on the manager host, but access permission for the transfer file could not be acquired due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2225-E
The file name of the transfer file (file-name) could not be changed because a system call error occurred (system-error-number).

An attempt was made to rename the specified transfer file to a temporary file name on the manager host, but a system call error occurred due to invalid communication protocol data.

(S)

Cancels the requested processing for submitting the job.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2226-E
The file name of the transfer file (file-name) could not be changed.

An attempt was made to rename the specified transfer file to a temporary file name on the manager host, but an error occurred due to invalid communication protocol data.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU2227-E
A connection error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A connection error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)

Probable causes are listed below. Check whether any of them following probable causes are present:

JP1/AJS3 at the connection destination has not started yet.

The port numbers used for submitting a job do not match between the manager and the host where the job was executed.

You changed the default gateway while JP1/AJS3 was running.

The IP address of the logical host manager and that of the agent belong to different networks.

The network, including hardware, has a problem.

No more socket ports can be used in the entire system.

Memory was insufficient.

For a cluster configuration, the system is set up so that the logical IP address is released before JP1/AJS3 stops when a failover occurs.

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

Start JP1/AJS3.

If you changed the port number for JP1/AJS3 or if JP1/AJS3 links to another system such as JP1/NQSEXEC or JP1/OJE for VOS3, correct the port number in the services file.

Before changing the network configuration, stop the JP1/AJS3 service.

Correct the setting so that the IP addresses belong to the same network. Alternatively, see 2.3 Determining the network configuration in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide to specify the setting for communication using multiple network addresses.

Recheck the setting of the network including hardware. For example, execute the ping command to check whether communication is possible.

Check the socket status and wait until no more sockets remains in the TIME_WAIT status. You can also prevent a communication error by reducing the recovery time for the TIME_WAIT ports managed by the OS.

Check the memory status and re-estimate the memory requirements.

Modify the setting so that the logical IP address is released after JP1/AJS3 has stopped.

KAVU2228-E
Connection processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when a connection request was issued to the remote host during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

One of the following problems may have occurred in the connection destination host. Check the following and correct the cause of the error, and then reissue the request.

If JP1/AJS3 at the connection destination has not started, start it.

Check whether the port numbers used for submitting a job match between the manager and the host where the job was executed. If JP1/AJS3 links to another system such as JP1/NQSEXEC or JP1/OJE for VOS3, also check whether the port number in the services file is correct.

If you changed the default gateway while JP1/AJS3 was running, stop the JP1/AJS3 service, and then change the default gateway.

Check and, if necessary, change the setting so that the IP address of the logical host and that of the agent belong to the same network. Also see 2.3 Determining the network configuration in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide to specify the setting for communication using multiple network addresses.

Recheck the setting of the network, including hardware, for a problem in the network. For example, execute the ping command to check whether communication is possible.

For a cluster configuration, if the system is set up so that the logical IP address is released before JP1/AJS3 stops when a failover occurs, correct the setting so that the logical IP address is released after JP1/AJS3 stops.

Note that if you specify too small a value for the connection timeout, retry count, or retry interval, a communication error cannot be prevented due to a too short retry interval for communication. This may cause the error to occur frequently.
Normally, the connection timeout value is set to 90 seconds. For details about how to change the connection timeout value, see 6.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 14.2.8 Changing the interval and number of retry attempts when a TCP/IP connection error occurs in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU2229-E
A transmission error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

An attempt to send protocol data has failed during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2230-E
Transmission processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when protocol data was sent to the remote host during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2231-E
A reception error occurred during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

An attempt to receive protocol data has failed during TCP/IP communication for job execution control.

(S)

Cancels the requested processing.

(O)

JP1/AJS3 at the connection destination may have terminated abnormally during communication. For a cluster configuration, a node switch may have occurred, resulting in forced termination of JP1/AJS3.

Check the status of JP1/AJS3 on the destination host and the contents of the integrated trace log, and then correct the cause of the error. If JP1/AJS3 has stopped, restart it. Then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2232-E
Reception processing timed out during TCP/IP communication. (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

A timeout occurred when the system was waiting for a response after sending protocol data during TCP/IP communication for job execution control. The probable causes are:

When the agent host sends a result file to the manager host at the end of a job, analysis takes a long time because the result file is too large.

When an attempt is made to execute a job with a transfer file specified, analysis takes a long time because the transfer file is too large.

The CPU on the manager host or agent host at the communication destination is heavily loaded. Alternatively, the system resources are insufficient.

Job information is being deleted on the manager host.

(S)

Cancels the requested processing.

(O)

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

Make sure that the result file for the job is not too large. Also, make sure that too much data will not be output even if additional writes are specified for the standard output file or standard error output file.

When you define the job, do not specify too large a transfer file.

Check the CPU load. Also see the kernel parameter settings to check the limit values of system resources.

Adjust the schedule to execute the job at a different time from that when job information was deleted. You must also prevent a lot of jobs from being deleted at the same time. For example, to reduce the number of jobs to be deleted, reduce the number of days for which job information is saved.

For 1 and 2 above, you can also limit the size of a file to be received in advance to prevent processing on some jobs from affecting the entire system. For details, see 6.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 14.2.7 Placing restrictions on file reception in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU2235-E
Another process is using the specified port number(reason code:reason-code). Could not start process(host name:host-name, port number:port-number).

The port cannot be activated because another process may be using the port or port-number is specified more than once.

(S)

Cancels starting of the daemon.

(O)

Check whether port-number which JP1/AJS3 is using is duplicated or another program is using port-number. Also check whether the network is set up correctly so that the IP address can be obtained from the specified host name.

KAVU2236-E
The initialization for TCP/IP communication was failed(reason code:reason-code). Could not start process(host name:host-name, port number:port-number).

The daemon cannot be started because TCP/IP communication could not be initialized.

(S)

Cancels starting of the daemon.

(O)

Check whether the environment is suitable for TCP/IP communication or memory is sufficient for operation. If you still cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU2237-E
Socket could not be opened because the process has too many open files. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

The socket could not be opened because the number of opened files reached the maximum set by the kernel parameter.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

Use the kernel parameter to increase the maximum number of files that can be opened., and then reissue the request. If the message KAVU2241-E is not output, the error has been corrected by a retry. If the message KAVU2241-E is output, the problem may persist. Recheck the setting. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU2238-E
The local host name could not be acquired in the TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

You could not obtain the local host name during TCP/IP communication.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

If the system does not output the message KAVU2241-E after this message while accepting the request, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, or when processing the request, a problem might occur in the name service. Check the status of the local host and correct the error. Then, reissue the request.

KAVU2239-E
Detected the failure of the network subsystem. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error is detected in the network subsystem.

(S)

When accepting the request, retries the acceptance. If the error persists, the system outputs the message KAVU2241-E. When processing the request, the system cancels the processing.

(O)

If the system does not output the message KAVU2241-E after this message while accepting the request, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, or when processing the request, an error might occur in the network subsystem. Check the status of the local host and correct the error. Then, reissue the request.

KAVU2240-E
The acceptance error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

A request could not be accepted during TCP/IP communication.

(S)

Retries the acceptance. If the error persists, the system outputs the message KAVU2241-E.

(O)

If the system does not output the message KAVU2241-E after this message, the error has been corrected by a retry. If the system outputs the message KAVU2241-E, use the data collection tool to collect data, and then contact the system administrator.

KAVU2241-E
The fatal error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error that prevents further processing, even after a retry, occurred during TCP/IP communication.

(S)

Stops the daemon.

(O)

Stop JP1/AJS3.

KAVU2242-W
The error occurred during TCP/IP communication. (host name: host-name, port number: port-number, module: reason-module[reason-module], system error number: system-error-number)

An error occurred during TCP/IP communication.

(S)

Continues processing. However, communication is impossible for some sockets that have been set.

(O)

Check whether the settings (such as an IP address) for communication are correct or the communication status does not have any problem. Then, correct the cause of the error.

To perform communication with the settings after correcting the error, restart the service (daemon).

KAVU2243-I
The size of the transmission source file of the job (job-name) executed on the client (client-host-name) exceeds the limit (bytes). (The transmission destination file name (transfer-destination-file-name))

The size of the transfer source file exceeds the maximum.

(S)

Continues processing.

(O)

Since the system may be over-loaded, check the following setting according to your operation.

We recommend you reduce the size of the specified transfer source file so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter).

How to search for the transfer file:

Search for the file specified in the job indicated in job-name, which was executed on the host indicated in client-host-name.

Cautionary notes

If you did not specify anything for transfer-destination-file-name, JPQ_TEMP is displayed.

If you did not specify anything for job-name, none is displayed.

One of the following is displayed for client-host-name:
1. The name of the host on which the jpqjobsub command was executed
2. The name of the host on which the jobnet was defined and executed
3. The name of the host on which the JpqSubmitJob function was executed
In UNIX, none is displayed.

KAVU2244-E
The size of the transmission source file of the job (job-name) executed on the client (client-host-name) exceeds the limit (bytes). (The transmission destination file name (transfer-destination-file-name))

The size of the transfer source file exceeds the maximum.

(S)

Does not receive the transfer file.

(O)

Reduce the size of the specified transfer source file so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter) or recheck the maximum value of the file size, and then re-execute the job.

How to search for the transfer file:

Search for the file specified in the job indicated in job-name that was executed on the host indicated in client-host-name.

Cautionary notes

If you did not specify anything for transfer-destination-file-name, JPQ_TEMP is displayed.

If you did not specify anything for job-name, none is displayed

One of the following is displayed for client-host-name:
1. The name of the host on which the jpqjobsub command was executed
2. The name of the host on which the jobnet was defined and executed
3. The name of the host on which the JpqSubmitJob function was executed
In UNIX, none is displayed.

If the job terminated abnormally because the size of the file reached the maximum, the message KAVU0220-E is output to the Execution Result Details dialog box.

KAVU2245-W
Because a connection error occurred during TCP/IP communication, it will be retried.
(connection destination host name: connection-destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

Connection processing is retried because a connection error occurred during TCP/IP communication.

(S)

Retries connection processing for TCP/IP communication. If the connection cannot be restored by the retry, the system outputs the message KAVU2227-E.

(O)

If the message KAVU2227-E is not output after this message, there is no problem because the connection was restored by the retry. If the message KAVU2227-E is output, take action according to the instructions in the message.

If the system error number is 10048, there was a shortage of socket ports when the job was executed. See 3.1.1(5) OS tuning in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and consider adjusting the OS parameters.

KAVU2246-W
Because a connection time-out occurred during TCP/IP communication, it will be retried.(connection destination host name: connection-destination-host-name, IP address: IP-address, port number: port-number, system error number: system-error-number)

Connection processing is retried because a connection timeout occurred during TCP/IP communication.

(S)

Retries connection processing for TCP/IP communication. If the connection cannot be restored by the retry, the system outputs the message KAVU2228-E.

(O)

If the message KAVU2228-E is not output after this message, there is no problem because the connection was restored by the retry. If the message KAVU2228-E is output, take action according to the instructions in the message.

KAVU3100-I
Job execution control (logical-host-name) was started.

The system started job execution control.

(S)

Starts the daemon.

KAVU3101-I
Job execution control (logical-host-name) is terminating.

The system is terminating job execution control.

(S)

Continues stopping the daemon.

KAVU3104-I
Job execution control (logical-host-name) ended normally.

Job execution control terminated normally.

(S)

Stops the daemon.

KAVU3105-I
The boot environment of the job execution control (logical-host-name). : maintenance-information

The boot environment for job execution control is displayed.

(S)

Continues the boot processing.

KAVU3110-E
Job execution control (logical-host-name) ended abnormally. (reason code:reason-code)

The agent process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3111-E
Job execution control (logical-host-name) is already running on the same host.

An attempt was made to start more than one agent process for job execution control on the same logical host.

(S)

Cancels the startup of the JP1/AJS3 service.

(O)

Check whether the JP1/AJS3 service (agent process for job execution control) has already started.

KAVU3112-E
Job execution control process ended abnormally. (name : process-name, code : end-code, pid : process-ID, sig : signal-number)

The process indicated in process-name terminated abnormally with the end code indicated in end-code.

When the signal number is other than 0, the process terminated abnormally in response to the signal for the signal number.

The probable causes are:

A JP1/AJS3 resident process was terminated abnormally by a signal.

A JP1/AJS3 resident process was terminated forcibly by jajs_killall.cluster command.

(S)

Terminates job execution control when the process name is jpqagtdmn.

Cancels the requested processing if the process name is jpqagtchild.

(O)

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1).

To continue the operation, collect data and then restart JP1/AJS3 (you do not have to restart JP1/AJS3 when the abnormally terminated process is jpqagtchild).

There is no problem in the following cases:

This message appears when you execute jajs_killall.cluster command.

The message KAVU3589-E has been output immediately before this message.

If this is the case and the KAVU3589-E message was output, read the message explanation and take corrective action.

KAVU3200-E
The user (user-name) request (request-name) for the parameter (parameter-name=parameter value) is invalid.

Invalid data was found in the request parameter during analysis of the request to the agent process for job execution control.

(S)

Cancels the analysis of the request to the agent process for job execution control.

(O)

The request received by the agent process for job execution control might be invalid for the process. Check the services files on the manager and agent hosts to see whether the port number for the jp1ajs2qagt service is also used for other services.

If the port number for the jp1ajs2qagt service is also used for other services, assign a unique port number for the jp1ajs2qagt service, and then restart JP1/AJS3.

In other cases, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3201-E
The user (user-name) request (request-name) failed. (reason code:reason-code)

The request to the agent process for job execution control has failed.

(S)

Cancels the analysis of the request to the agent process for job execution control.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3205-W
The system detected a change in the size of the environment variable file (environment-variable-file-name) while the job (job-number) was starting.

The environment variable file that was being read according to the job definition at job startup was overwritten before reading was completed.

The job might have been started with an invalid environment variable.

(S)

Continues the job startup processing.

If the increase in the environment variable file size was less than 4,096 bytes, the job was started with all environment variables having been read. However, the job might have been started with an invalid environment variable because of the rewriting occurred during reading.

If the increase in environment variable file size was 4,096 bytes or more, the job was started after 4,096 bytes had been added to the pre-change file size.

(O)

Check the job status. If any environment variables might not have been read, take corrective action. Also create or update the environment variable file before the job is delivered to the agent. After the job has been delivered to the agent, do not update the environment variable file until the job is running.

KAVU3210-E
Communication thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for receiving a communication request for the agent process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

The CPU may be over-loaded. Check the load on the CPU. Also use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3211-E
The agent daemon process ended abnormally. (host name:host-name, process name:process-name, process id:process-number)

The agent process for job execution control terminated abnormally.

(S)

Terminates the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3212-E
The monitoring process for job (job-number) ended abnormally. (host name:host-name, process name:process-name, process id:process-number)

The job monitoring process for job execution control terminated abnormally.

(S)

Cancels the monitoring of the job indicated in job-number.

(O)

Check the status of the job process that was started as a job. If the job process is re-executable, re-execute it.

Also use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3213-E
Failed to acquire permission to read environment variable file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

The system failed to access the environment variable file.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the environment variable file specified by the executing OS user can be accessed, and then call the function again.

KAVU3214-E
Failed to acquire permission to execute the execution file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

The system failed to access the executable file.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the execution file specified by the executing OS user can be accessed, and then call the function again.

KAVU3215-E
Failed to read the temporary file (file-name) for the transmission source for the user (user-name). (system call name: system-call-name, reason code: reason-code)

An attempt to read the transfer source file has failed.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the transfer source file specified by the executing OS user can be read, and then call the function again.

KAVU3216-E
Failed to write the transmission destination file (file-name) for the user (user-name). (system call name: system-call-name, reason code: reason-code)

An attempt to write to the transfer destination file has failed.

(S)

Cancels the requested processing.

(O)

Make sure that, based on the file permission (ls -l command) and access control list settings, the file path to the transfer source file specified by the executing OS user can be written to, and then call the function again.

KAVU3221-E
The manager (logical-host-name) could not be notified about job status. (reason code:reason-code)

The system failed to notify the manager process for job execution control of the job status. When a means of preventing duplicated reception of the job result file is set, a job end notification cannot be accepted, probably because the result file (standard output file or standard error output file) is being analyzed on the manager host. If this is the case, the manager host accepts the KAVU4297-W message. If the setting for preventing duplicate reception of job result files is not defined, the manager host may stop or a communication with the manager host may be impossible.

For details on how to prevent duplicated reception of the job result file, see 6.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows), or 14.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

(S)

Cancels the job status notification to the manager process.

(O)

Check the integrated trace log for the manager host to check the running status of the manager process for job execution control.

Also use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU3270-E
Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU3271-E
There is insufficient disk space. (module:reason-location[reason-location], reason code:reason-code, file name:file-name)

The disk does not contain sufficient amount of free space.

(S)

Cancels the requested processing.

(O)

Secure sufficient free space on the disk that contains the file indicated by file-name, and then issue the request again.

KAVU3272-E
A system call error occurred when starting process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during startup of the agent process for execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3274-W
A system call error occurred in the communication process (logical-host-name). (module:reason-location, reason code:reason-code)

A system call error occurred in the communication process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3275-E
A logical contradiction occurred in the communication process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during communication for the agent process for job execution control. The probable causes are:

The temporary file used for job execution control did not exist. (reason-code = 0xe002110d)

You did not have access permission for the temporary file used for job execution control. (reason-code = 0xe002110e)

The amount of free space on the disk was insufficient when the temporary file used for job execution control was being created. (reason-code = 0xe002110f)

The temporary file used for job execution control was locked and opened. (reason-code = 0xe0021110)

An attempt to acquire the logical host name or IP address has failed. (reason-code = 0xe0021120)

Note:

For details on the temporary files used for job execution control, see 7.8.1 Notes on the standard output file and standard error output file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no other KAVU message was output, or if a reason code other than that shown above was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU3276-W
A system call error occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the request process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3278-W
A system call error occurred in the user mapping process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the user mapping process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3280-W
A system call error occurred in the variable solution process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the variable solution process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3281-E
A logical contradiction occurred in the variable solution process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during solution of the macro variable for the agent process for job execution control.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3282-W
A system call error occurred in the standard input/output process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the standard input/output process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3283-E
A logical contradiction occurred in the standard input/output process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during the check of access permission for the file used for job execution.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3284-W
A system call error occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code1:reason-code-1, system call name:system-call-name, reason code2:reason-code-2)

A system call error occurred in the internal process.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from system-call-name and reason-code-2.

In reason-code-2, the following value is output:

Windows

Value obtained by Win32 API function GetLastError

UNIX

Value obtained by errno

If the cause of the error cannot be determined, use the data collection tool to collect data, and then contact the system administrator.

KAVU3285-E
A logical contradiction occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during internal processing for the agent process for job execution control.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3289-W
The authentication server could not be connected, but initialization will continue.

The authentication server could not be connected.

(S)

Continues the daemon.

(O)

If the authentication server is not started, start it.

KAVU3290-W
You lack access permission for the temporary file (file-name). (reason code:reason-code)

You do not have access permission for the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine the cause which may be one of the following:

A privilege to the system file directory (the default is /var/opt/jp1ajs2/sys) has been changed.

A privilege to the work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been changed.

A privilege to the jpqagtlock file or the temporary work file in the system file directory has been changed.

Another program is accessing the above directories or the temporary work file.

If a privilege to the file or the directory has been changed, give the write and read permissions to the OS user that executes jobs. The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU3291-W
The temporary file (file-name) cannot be accessed (system-call-name). (reason code:reason-code)

You could not access the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine the cause which may be one of the following:

The system file directory (the default is /var/opt/jp1ajs2/sys) has been deleted.

The work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been deleted.

Write permission has not been set for the work directory used for executing the agent process (default work directory: /var/opt/jp1ajs2/tmp).

The jpqagtlock file or the temporary work file has been deleted from the system file directory.

Another program is accessing the above directories or the temporary work file.

If the jpqagtlock file or the above directories have been deleted, reinstall JP1/AJS3.

If the work directory used for executing the agent process exists, check whether write permission is set for the directory. If write permission is not set, set write permission for the directory or change the work directory to a directory for which write permission has been set.

The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates normally. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU3293-E
The process has too many open files. (reason code:reason-code)

The number of opened files reached the maximum set by the kernel parameter.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter to increase the maximum number of files that can be opened.

For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU3295-E
No more process can be generated. (reason code:reason-code)

The number of processes reached the maximum set by the kernel parameter.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter to increase the maximum number of processes.

Set the sufficient number of processes considering the number of JP1/AJS3 processes plus the number of job processes that are executed at the same time.

For details about JP1/AJS3 processes, see the explanation of process status checking in 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU3500-W
The operating status (operating-status) does not allow executing request (request-name).

The operating status does not allow executing the request.

(S)

Cancels the requested processing.

(O)

Make sure that the daemon is started, and then reissue the request.

KAVU3502-W
The specified job (job-number) does not exist, or termination notification is already complete.

The specified job does not exist. Alternatively, the termination of the job is already reported.

(S)

Cancels the requested processing.

(O)

Check whether the job is already terminated.

KAVU3503-E
The job (job-number) could not be executed.

The job could not be executed.

(S)

Cancels the request to execute the job.

(O)

Use the integrated trace log to check whether a KAVU message was output before this message. If it was output, also see the explanation provided in that message and correct the cause of the error. Then, re-execute the job.

KAVU3504-W
The transfer file (file-name) was not found.

The file cannot be deleted because the transfer file no longer exists.

(S)

Continues requested processing.

(O)

The transfer file specified to be deleted may have been deleted before job termination. Check whether any program or script is accessing the transfer file.

KAVU3505-W
You lack delete permission for the transfer file (file-name).

You cannot delete the transfer file because you are not permitted to delete it.

(S)

Continues requested processing.

(O)

The permission for the transfer file specified to be deleted may have been changed before job termination. Check whether any program or script is accessing the transfer file.

KAVU3506-W
The transfer file (file-name) could not be deleted. (reason code: reason-code)

The transfer file could not be deleted.

(S)

Continues the requested processing.

(O)

The attribute of the transfer file specified to be deleted may have been changed before job termination. Check whether any program or script is accessing the transfer file.

KAVU3520-E
The monitoring thread for job (job-number) could not be generated. (reason code:reason-code)

The system failed to generate a thread for monitoring the job.

(S)

Cancels the requested processing.

(O)

If reason-code is 8 in Windows, memory may be insufficient. In this case, recheck the memory estimate.

For other cases, use the data collection tool to collect data, and then contact the system administrator.

KAVU3521-W
The job (job-number) process could not be generated. (reason code:reason-code)

The system failed to generate the job process.

(S)

Cancels the requested processing.

(O)

Memory may be insufficient. Check the memory estimate. If there is no problem with the available memory, use the data collection tool to collect data, and then contact the system administrator.

KAVU3522-W
The job (job-number) return code could not be acquired. (reason code:reason-code)

The system failed to acquire the job return code.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3523-W
The job (job-number) could not be forcibly terminated. (reason code:reason-code)

The system failed to forcibly terminate the job.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3530-W
The manager (logical-host-name) might have stopped, or an obstacle occurred.

The manager might have stopped or an error might have occurred in the manager.

(S)

Cancels the requested processing.

(O)

Check the following and then call the function again:

Check whether the daemon has been started.

Check whether the TCP/IP communication is possible with logical-host-name.

Check whether the port number is set correctly.

Check whether the size of the file specified as the standard output or standard error output file is too large.

KAVU3531-W
The manager (logical-host-name) host name might be invalid.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified logical host name, and then reissue the request.

KAVU3532-W
The host name (logical-host-name) IP address could not be acquired.

The network must be set using the hosts file or the DNS server so that the IP address can be obtained from the manager host name.

(S)

Cancels the requested processing.

(O)

Check whether the TCP/IP communication is possible with the manager host name and then call the function again.

KAVU3540-I
Planned termination of the agent (agent-name) started.

The agent process for job execution control started planned termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3541-I
Forced termination of the agent (agent-name) started.

The agent process for job execution control started forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3542-I
The agent (agent-name) is monitoring job termination.

The agent process for job execution control will monitor the termination of running jobs.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU3546-E
The temporary file (file-name) could not be opened. (system call name:system-call-name, reason code:reason-code)

The temporary file cannot be opened because the directory for the temporary file does not exist.

(S)

Cancels the request processing.

(O)

Make sure that the directory to which the temporary file is to be output exists.

Also make sure that access permission that allows the OS user who executes the job to access the directory is set on the directory.

If the problem still cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KAVU3547-E
An attempt to start the job process has failed because the user(user-name) does not have permission to execute the executable file(file-name). (reason code:reason-code)

An attempt to start the job process has failed because the user does not have permission to execute the executable file.

(S)

Cancels the requested processing.

(O)

reason-code indicates the value obtained by the GetLastError function of the Win32 API.

If the Windows UAC function is enabled, an attempt to start the job process failed because the OS user mapped to the execution user did not have administrator permissions. Use the built-in Administrator account to execute the job.

For details on the Windows UAC function, see the Microsoft website.

KAVU3548-E
The size of argument and environment variable in job definition is greater than the system-imposed limit. (system call name:system-call-name, reason code:reason-code)

The total size of the parameters and environment variables specified in the job definition and the environment variable statements specified in the environment variable file exceeds the OS limit on the size of environment variable strings.

(S)

Cancels the request processing.

(O)

Review the parameters and environment variables specified in the job definition, and environment variable statements specified in the environment variable file.

KAVU3549-E
A system call (function-name) error occurred in a job execution process. (reason code:reason-code)

A system call error occurred during execution of the job.

(S)

Cancels the requested processing.

(O)

When function-name is write and reason-code is 0x0000001c, check whether the home directory of the OS user mapped to the execution user or the directory specified in the work path has been placed in the DiskFull status.

If the directory is placed in the DiskFull status, delete unnecessary files to increase free space, and then execute the job. For other cases, use the data collection tool to collect data, and then contact the system administrator.

Check whether the option described in 6.2.16 Executing a job that requires a user profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU3550-W
The execution file (file-name) was not found.

The executable file does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

If you specify the file with a relative path, make sure that the PATH environment variable is correctly set for the corresponding directory and folder.

KAVU3551-W
You lack access permission for the execution file (file-name).

You do not have access permission for the executable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3552-W
The environment variable file (file-name) was not found.

The environment variable file does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3553-W
You lack access permission for the environment variable file (file-name).

You do not have access permission for the environment variable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3554-W
The environment variable file (file-name) cannot be opened.

The system cannot open the environment variable file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the environment variable file name.

KAVU3555-W
The environment variable file (file-name) cannot be accessed (function-name). (reason code:reason-code)

The system failed to access the environment variable file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3556-W
The standard input file (file-name) cannot be found.

The standard input file does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3557-W
You lack access permission for the standard input file (file-name).

You do not have access permission for the standard input file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3558-W
The standard input file (file-name) cannot be opened.

The system cannot open the standard input file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard input file name.

KAVU3559-W
The standard input file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard input file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3560-W
You lack access permission for the standard output file (file-name).

You do not have access permission for the standard output file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3561-W
The standard output file (file-name) cannot be opened.

The system cannot open the standard output file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard output file name.

KAVU3562-W
The standard output file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard output file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3563-W
You lack access permission for the standard error output file (file-name).

You do not have access permission for the standard error output file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3564-W
The standard error output file (file-name) could not be opened.

The system cannot open the standard error output file.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard error output file name.

KAVU3565-W
The standard error output file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the standard error output file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3566-W
The work path name (path-name) is too long, so the file cannot be created.

The work path name is too long, so the file cannot be created.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3567-W
The work path (path-name) cannot be found.

The work path does not exist, or you do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Check whether the work path exists. If it exists, check whether the user who started the JP1/AJS3 service has permission to access the work path. Remove the cause of the error, and then reissue the request.

KAVU3568-W
You lack access permission for the work path (path-name).

You do not have access permission for the work path.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3569-W
The file path (path-name) variable could not be resolved.

The system failed to resolve the file path variable.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3570-W
The parameter (path-name) variable could not be resolved.

The system failed to resolve the parameter variable.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3571-W
User mapping (JP1-user-name) failed.

User mapping failed.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition does not contain the JP1 user.

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

An OS user that has not been mapped is used to register a jobnet by the ajsentry command.

If the user mapping definition does not contain any error, memory may be insufficient. In this case, re-estimate memory.

When the user account has started the JP1/AJS3 service on Windows, this message appears if the user does not have privilege for the service. Check the user privileges for the service.

KAVU3572-W
The user (user-name) could not be masked.

The system failed to mask the user.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

KAVU3573-W
The job priority could not be changed.

The system failed to change the job priority.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3574-W
An error occurred while generating a job process. (reason code:reason-code)

An error occurred while the system was generating a job process.

(S)

Cancels the requested processing.

(O)

reason-code indicates either of the following values:

In Windows:

The value obtained by the GetLastError function of the Win32 API

In UNIX:

The value obtained by errno

The following describes probable causes for reason codes, and suggests corrective actions:

In Windows

reason-code: 87
The size of the environment variable statement specified by the environment variable and environment variable file name might exceed the upper limit of character strings permitted by the OS. Review the environment variable statement specified by the environment variable and environment variable file name.

reason-code: 740
If the Windows UAC function is enabled, an attempt to start the job process failed because the OS user mapped to the execution user did not have administrator permissions. Use the built-in Administrator account to execute the job.
For details on the Windows UAC function, see the Microsoft website.

reason-code: 1816
The OS resources might be insufficient. Check whether the OS resources are sufficient for executing the job.

In UNIX

reason-code: 28
The OS resources might be insufficient. Check whether the OS resources are sufficient for executing the job.

If reason-code indicates a value other than the one indicated above, check the meaning of your OS error codes, and then take appropriate action. If the error persists, collect the internal trace log, and then contact the system administrator.

KAVU3575-W
An error occurred while starting a job process. (reason code:reason-code)

An error occurred while the system was starting a job process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3576-W
The standard error file or standard error output file could not be sent.

The system failed to transfer the standard error file or standard error output file.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then reissue the request.

KAVU3577-W
A system call (function-name) error occurred in a job execution process. (reason code:reason-code)

A system call error occurred in a job execution process.

(S)

Continues processing.

(O)

If function-name is UnloadUserProfile, the UnloadUserProfile function for Win32API has failed. In this case, processing continues, but a resource leak may have occurred.

If this message has been output many times for the UnloadUserProfile function, restart the JP1/AJS3 service.

If this message has been output a number of times in succession, or if an error occurred in a function other than the UnloadUserProfile function, use the data collection tool to collect data, and then contact the system administrator.

Check whether the option described in 6.2.16 Executing a job that requires a user profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 is enabled. If it is enabled, enable the setting described in 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU3578-W
The execution file (file-name) could not be accessed (function-name). (reason code:reason-code)

The system failed to access the executable file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3579-W
A logical contradiction occurred in the job execution process. (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred in the job execution process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3580-W
The user (user-name) does not have administrator permission.

If you specify the execution priority of the Unix job to 4 or 5, the user that attempts to log in to the OS must have superuser privileges.

(S)

Cancels the requested processing.

(O)

Reissue the request as a user who has superuser privileges.

KAVU3581-W
The execution file (file-name) is not an executable file.

The file you attempted to execute is not an executable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU3582-W
The specified execution file (file-name) cannot be merged with the command statement.

The execution file cannot be merged with the command statement.

(S)

Cancels the requested processing.

(O)

Correct the error, and then reissue the request.

KAVU3583-W
No path is specified to the destination for storing transfer files in the manager (logical-host-name).

The path to store transfer files is missing at the manager.

(S)

Cancels the requested processing.

(O)

Check whether the work path is specified in the common definition information for the manager.

KAVU3584-W
The transfer files at the manager (logical-host-name) could not be accessed.

The transfer file on the manager could not be accessed.

(S)

Cancels the requested processing.

(O)

Check whether the work path specified in the common definition information for the manager can be accessed.

KAVU3585-W
The manager (logical-host-name) disk is full.

There is an insufficient amount of disk space on the manager.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk on the manager.

KAVU3586-W
The privilege for service account was not set.

If the service account is set to the user account, privileges necessary for executing the process must be set.

(S)

Terminates the job.

(O)

Check the service account and privileges necessary for it. For details on the necessary privileges when the service account is set to the user account, see 4.2.3(1)(d) Privileges for running JP1/AJS3 services under a user account in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVU3587-W
Failed to set a limit (limit) on a system resource (system-resource-name). (reason code: reason-code)

You attempted to specify limit on system-resource-name but it could not be set.

(S)

Executes the job with the default limit.

(O)

Set the appropriate limit.

KAVU3588-E
Shared memory identifier could not be allocated.

The shared memory ID could not be allocated because the maximum number of shared memory IDs available for the system was exceeded.

(S)

Stops the daemon.

(O)

Use the kernel parameter to increase the maximum number of shared memory IDs available for the system, and then restart. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU3589-E
A pipe timeout error occurred in a job execution process (timeout value(second): seconds)

A timeout occurred during pipe communication in a job execution process.

(S)

Cancels the requested processing.

(O)

A cause may be one of the following:

Too many jobs are executed at once.

The CPU is heavily loaded.

The agent process for job execution control was swapped out for more than 300 seconds and not executed due to insufficient real memory.

If one of these causes persists and a timeout error frequently occurs during pipe communication, we recommend that you specify a timeout period longer for pipe communication on the host where the agent process is executed.

In case of Cause No. 3, check the memory usage for the entire system and increase the memory or suppress the startup of unnecessary processes to gain sufficient real memory.

For details on how to change a timeout value for pipe communication, see 14.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

If the error persists even after changing the timeout value, use the data collection tool to collect data, and then contact the system administrator.

KAVU3590-W
The size of argument and environment variable in job definition is greater than the system-imposed limit.

The size of the parameter and the environment variable specified in the job definition plus the environment variable statement specified in the environment variable file name exceeds the upper limit specified for the system.

(S)

Cancels the requested processing.

(O)

Recheck the parameter or the environment variable specified in the job definition and the environment variable statement specified in the environment variable file name.

KAVU3591-W
The shell (shell-name) is not an executable file. (reason code:reason-code)

The execution shell of the job is not an executable shell.

(S)

Cancels the requested processing.

(O)

Check whether the login shell of the user that attempted to log in to the OS can be started. Alternatively, if the shell is specified by the jpqjobsub command or the JpqSubmitJob function, check whether the shell can be started.

KAVU3592-W
The agent does not have permission for changing owner of the file (type=file-name).

The agent does not have permission to change the owner of the file.

(S)

Cancels the requested processing.

(O)

If the directory for storing the file is mounted on the NFS, the owner of the file may not be able to change. Check whether you can access the file and its directory using the JP1/AJS3 service account. Then, change the access permission for the file and its directory or change the directory so that they can be accessed using the JP1/AJS3 service account. The directory differs depending on a file type. Change the directory according to the following file types:

Temporary script file: The work path in the job definition, or the home directory of the execution user.

Standard output file: The directory to output to

Temporary standard output file: The work directory used for executing the agent process

Standard error output file: The directory to output to

Temporary standard error output file: The work directory used for executing the agent process

KAVU3593-W
The PATH variable for the user (user-name) could not be acquired.

The PATH environment variable for the user that attempted to log in to the OS could not be acquired.

(S)

Cancels the requested processing.

(O)

Check the following:

If the set -u or the script command is included in the login script of the executing OS user, check whether there is a condition that will terminate the processing before it is completed. If the login script contains a statement that is unnecessary for job execution by JP1/AJS3, delete the relevant location or use the JP1JobID environment variable to skip the relevant location. For details about how to change the login script, see 12.4.1 Changing the login scripts in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For the work directory used for agent-process execution, check whether access permissions are set for the user starting the JP1/AJS3 service and the OS user executing the job. If read permission and write permission are not set, set these permissions.

For all other cases, check whether there is too little disk space for the directory used as the work directory when the agent process for job execution control is executed. If the disk capacity is insufficient, create free space and issue another request.

KAVU3594-W
The work path (work-path-name) or the file path (file-name) is too long.

The work directory for the common definition information, the work path for the job definitions, or the name of the file is too long.

(S)

Cancels the requested processing.

(O)

Some work path names or file names may have an allowable length that exceeds the upper limit for the system. This depends on a system.

Set the work path name or the file name according to the upper limit for the system.

KAVU3595-W
The execution shell (execution-shell-name) was not found.

There is no shell used to execute the job.

(S)

Cancels the requested processing.

(O)

Check the shell used to execute the job.

KAVU3596-W
The temporary script file (file-name) for job (job-number) was not found. (system call name:system-call-name, reason code:reason-code)

There is no temporary script file for the job.

(S)

Cancels the requested processing.

(O)

A temporary script file for the job (file whose name begins with JPQ_EXEC) was temporarily created in the home directory of the OS user mapped to the user who executes the job or in the directory in the work path.

Check whether this file was deleted illegally during operation. If an invalid file remains when JP1/AJS3 stops, delete it.

KAVU3597-W
The temporary script file (file-name) for job (job-number) was busy. (system call name:system-call-name, reason code:reason-code)

The temporary script file for the job could not be deleted because the file was running.

(S)

Cancels the requested processing.

(O)

A temporary script file for the job (file whose name begins with JPQ_EXEC) was temporarily created in the home directory of the OS user mapped to the user who executes the job or in the directory in the work path.

Check whether any other program accesses this file illegally during operation. If an invalid file remains when JP1/AJS3 stops, delete it.

KAVU3598-W
The work path (path-name) is not a full path.

The work path must be specified with an absolute path name.

(S)

Cancels the requested processing.

(O)

Check the work path in the job definition.

KAVU3599-W
The end judgment file (file-name) could not be accessed. (reason code:reason-code)

The end judgment file could not be accessed.

(S)

Cancels the requested processing.

(O)

Check whether the access permission is changed illegally for the end judgment file used in the job definition.

KAVU3800-I
Execution of command step (command-line) terminated. (return code : return-code)

Execution of the command step specified in the jp1exec command terminated.

(S)

Continues processing.

KAVU3900-E
The command step (command-line) could not be started. (reason code:reason-code)

The reason code indicates a Win32API detail code.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Make sure that the command exists and you have permission to execute the command, and then re-execute the command.

If the Windows UAC function is enabled and reason-code indicates 0x000002e4, an attempt to start the job process failed because the OS user mapped to the execution user did not have administrator permissions. Use the built-in Administrator account to execute the job.

For details on the Windows UAC function, see the Microsoft website.

KAVU3901-E
The return code for the command step (command-line) could not be acquired. (reason-code)

The system failed to acquire the return code for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3902-E
The temporary file for the command step (command-line) could not be opened. (reason code:reason-code)

The system cannot open the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU3903-E
The temporary file for the command step (command-line) could not be accessed. (reason code:reason-code)

The system failed to access the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

The detail code of Win32API is shown in reason-code.

If reason-code is 0, the jp1exit command may be written more than once in succession in one batch file. Check the batch file containing the jp1exit command.

If you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVU3904-E
The temporary file for the command step (command-line) could not be deleted. (reason code:reason-code)

The system cannot delete the temporary file for the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

More than one jp1exit command may be described in one batch file. Check the batch file containing the jp1exit command.

KAVU3905-E
The host name could not be acquired in the command step. (reason code:reason-code)

The system failed to acquire the host name in the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

KAVU3906-E
Invalid environment settings were detected in the command step. (reason code:reason-code)

The system detected invalid environment settings in the command step.

(S)

Cancels executing the jp1exec or jp1exit command.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then call the function again.

If the integrated trace log contains the message KAVU7221-E (Environment setting parameter (parameter-name=parameter value) on the logical host (logical-host-name) is invalid.), the OS user executing the command might not have been granted write and read permissions for the output path. If this is the case, grant write and read permissions, and then re-execute the command.

KAVU4100-I
Job queuing control (logical-host-name) was started.

Job queuing control was started.

(S)

Starts the daemon.

KAVU4101-I
Job queuing control (logical-host-name) is terminating.

Job queuing control is being terminated.

(S)

Continues stopping the daemon.

KAVU4102-I
Job queuing control (logical-host-name) was paused.

Job queuing control was temporarily terminated.

(S)

Stops the daemon temporarily.

KAVU4103-I
Job queuing control (logical-host-name) was restarted.

Job queuing control was restarted.

(S)

Starts the daemon.

KAVU4104-I
Job queuing control (logical-host-name) ended normally.

Job queuing control terminated normally.

(S)

Stops the daemon.

KAVU4105-I
The queuing control (logical-host-name) has changed to reduced manager operation mode.

Queuing control is placed in reduced manager operation mode.

(S)

Places queuing control in reduced manager operation mode. The system does not accept job execution requests or requests from commands.

KAVU4110-E
Job queuing control (logical-host-name) ended abnormally. (reason code:reason-code)

The manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4111-E
Job queuing control (logical-host-name) or jpqimport command is already running on the same host.

An attempt was made to start more than one manager process for job execution control on the same logical host. Alternatively, the jpqimport command is running.

(S)

Cancels the startup of the JP1/AJS3 service.

(O)

Check whether the JP1/AJS3 service has already started or whether the jpqimport command is running.

KAVU4112-E
The system will wait because the database could not be connected. (Waittime: maximum-wait-time, Host: host-name)

The database could not be connected within the specified maximum wait time.

(S)

Cancels the requested processing.

(O)

Check whether the database is running.

For details about how to check this, see the manual for the appropriate database.

If the database is starting, recheck the value of the maximum wait time.

KAVU4113-W
The database could not be connected within the specified time. (Waittime: maximum-wait-time, Host: host-name)

The system will wait because the database could not be connected.

(S)

Retries the connection after a predefined period of time.

(O)

Check whether the database is running.

For details about how to check this, see the manual for the appropriate database.

KAVU4200-E
The user (user-name) request (request-name) for the parameter (parameter=parameter value) is invalid.

Invalid data was found in the request parameter during analysis of the request to the manager process for job execution control.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

Check the following:

If the requesting host is a JP1/AJS3 host and the parameter name is jobNumber, check whether the number of digits in the specified job number is from 1 to 6. If 7 or more digits have been used, specify another job number that consists of only 1 to 6 digits, and then retry the operation.

If the requesting host is a JP1/AJS3 host and the parameter name is controlStdFile, and if the same file name is specified for the standard output file and the standard error output file for the job, check whether the append option settings match. If there is no match, correct the settings, and then retry the operation. In addition, if you need to change the settings, specify different file names for the standard output file and the standard error output file.

If the requesting host is JP1/AJS3 and the parameter name is szExecAgentName, make sure that the specified execution agent does not have any characters that cannot be used. If there are any, specify a name that does contain the unusable characters, and then retry the operation.

For cases not covered above, a request that the manager process for job execution control does not accept might have been accepted. Check the services file for the manager host and the requesting host, and make sure that the port number for jp1ajs2qman or jp1ajs2qnfy is not the same as that of another port name. If there is a duplication, change the port number that is set, and restart JP1/AJS3.

For all other cases, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the requesting client host.

KAVU4202-E
The user (user-name) lacks permission for the request (request-name). (reason code:reason-code)

The user who issued a request to the manager process for job execution control does not have the permissions required to issue the request.

A user with the JP1_JPQ_User permission level might have operated a job for another user.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

If you executed a command (jpqxxxx command) or issued a function for job execution control, check the permissions for the JP1 user name that is the same as the OS user name performing the operation. Check whether the OS user executing the command or issuing the function for job execution control has been registered as a JP1 user on the authentication server. Also check whether the JP1 resource group (JP1_Queue) to which the JP1 user (OS user) belongs has the JP1 permission level required to execute the command or issue the function.

If the executing JP1 user has only the JP1_JPQ_User permission, operations available to the JP1 user and what that JP1 user can reference does not extend to jobs other than jobs submitted by the executing JP1 user. Accordingly, execution is limited to the user who submitted the job, a user who has the JP1_JPQ_Admin permission, and a user who has the JP1_JPQ_Operator permission.

You therefore need to register the OS user as a JP1 user on the authentication server, and if necessary, grant the JP1 user execute permission.

For details about the execute permission for the commands for job execution control, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU4203-E
An error occurred while checking permission for the user (user-name) request (request-name). (reason code:reason-code)

An error occurred while checking permissions for a user who issued a request to the manager process for job execution control.

(S)

Cancels the analysis of the request to the manager process for job execution control.

(O)

Make sure that the authentication server has started. If the authentication server has not started, start it and then reissue the request. If this error occurs even though the authentication server is running, use the data collection tool to collect data, and then contact the system administrator.

KAVU4210-E
The Communication thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for accepting a communication request for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

The CPU may be over-loaded. Check the load on the CPU. Also use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4211-E
The job dispatcher thread (logical-host-name) ended abnormally. (reason code:reason-code)

The job dispatcher thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVUxxxx message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4212-E
The scheduled monitoring thread (logical-host-name) ended abnormally. (reason code:reason-code)

The thread for monitoring scheduled jobs in a wait state for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4213-E
The thread (logical-host-name) for monitoring the number of concurrently-executable jobs terminated abnormally. (reason code:reason-code)

The thread for monitoring the number of concurrently-executable jobs for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4214-E
The automatic log deletion thread (logical-host-name) ended abnormally. (reason code:reason-code)

The job information deletion thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4215-E
The agent monitoring thread (logical-host-name) ended abnormally. (reason code:reason-code)

The agent monitoring thread for the manager process for job execution control terminated abnormally.

(S)

Stops the JP1/AJS3 service.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4220-E
The job execution request to the agent (agent-host-name) failed. (reason code:reason-code)

The job execution request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

File transfer has failed. (reason-code = 0xe00a000e)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

(S)

Cancels the job execution request to the agent host.

(O)

Use the integrated trace log to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4221-E
The job termination request to the agent (agent-host-name) failed. (reason code:reason-code)

The job termination request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

No job exists on the agent host. (reason-code = 0xa00a0005)

(S)

Cancels the job termination request to the agent host.

(O)

Use the integrated trace log to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host.

If the reason code is 0xa00a0005, indicating that no job exists on the agent host, the job may have already terminated on the agent host before the forced termination. Use either of the following methods to check the status of the job.

For a PC job, UNIX job, action job, or custom job:
Check JP1/AJS - View or execute the ajsshow command.

For a QUEUE job or submitted job:
Execute the jpqjobget command.

If no other message has been output and you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4222-E
The job confirmation request to the agent (agent-host-name) failed. (reason code:reason-code)

The job confirmation request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

No job exists on the agent host. (reason-code = 0xa00a0005)

(S)

Cancels the job confirmation request to the agent host.

(O)

Use the integrated trace log to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host.

If the reason code is 0xa00a0005, indicating that no job exists on the agent host, the JP1/AJS3 service on the agent may have been restarted during execution of the job. In this case, the job was terminated forcibly.

If no other message has been output and you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4223-E
The operating status confirmation request to the agent (agent-host-name) failed. (reason code:reason-code)

The operating status confirmation request to the agent process for job execution control has failed. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The agent host has stopped. (reason-code = 0xe00a0007)

The JP1/AJS3 service on the agent host has stopped. (reason-code = 0xe00a0007)

The agent host name is invalid. (reason-code = 0xe00a0008)

The JP1/AJS3 service on the agent host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the agent host. (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

(S)

Cancels the operating status confirmation request to the agent host.

(O)

Use the integrated trace log to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the agent host, also check the integrated trace log for the agent host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4224-E
Client (client-host-name) could not be notified about job status. (reason code:reason-code)

The system failed to notify the status notification process of job execution control or of the client host of the job status. The probable causes are:

Memory was insufficient. (reason-code = 0xe00a0002)

The client host has stopped. (reason-code = 0xe00a0007)

The status notification process has stopped. (reason-code = 0xe00a0007)

The client host name is invalid (reason-code = 0xe00a0008)

The status notification process for the client host is starting or terminating. (reason-code = 0xe00a0009)

The error was caused by the client host. (reason-code = 0xe00a000d)

The communication protocol is not supported. (reason-code = 0xe00a000e)

(S)

Cancels the job status notification to the status notification process.

(O)

Use the integrated trace log to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If the reason code is 0xe00a000d, indicating that the error was caused by the client host, also check the integrated trace log for the client host. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4225-W
The operating status of the manager (logical-host-name) could not be acquired. (reason code:reason-code)

The system failed to acquire the operating status of the manager.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4226-W
The operating status of the manager (logical-host-name) could not be changed(operating-status). (reason code:reason-code)

The system failed to change the operating status of the manager.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4250-E
The database (logical-host-name) is not created correctly. (reason code:reason-code)

The database directory path or database file for the job execution environment was not found.

(S)

Stops the JP1/AJS3 service.

(O)

Make sure that the path and database file are correctly created for the database directory name for the job execution environment specified in the DatabasePath environment setting parameter. If they are not, use the jpqimport command to create a database, and then restart the JP1/AJS3 service.

KAVU4251-E
You lack operate permission for the database (logical-host-name). (reason code:reason-code)

You do not have access permissions for the database directory path or database file for the job execution environment.

(S)

Stops the JP1/AJS3 service.

(O)

Check the access permissions for the path and database file for the database directory name for the job execution environment specified in the DatabasePath environment setting parameter. You require the write and read permissions for the account that uses the JP1/AJS3 service. If the required permissions are not set, set the required permissions and then restart the JP1/AJS3 service.

The database file contains an ISAM file beginning with JPQ and the .jpqdb.lck file.

KAVU4252-E
A logical contradiction occurred in the database (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An inconsistency was found in the database key file for the job execution environment. The database may have been damaged when JP1/AJS3 was stopped suddenly because the system was turned off inadvertently.

(S)

Stops the JP1/AJS3 service.

(O)

Reorganize the job execution environment database, and then restart the JP1/AJS3 service. If this error occurs again, use the data collection tool to collect data, and then contact the system administrator.

If this error still occurs after re-organizing the database, you must re-create the database.

KAVU4253-E
Environment setting (logical-host-name) does not match current information in the database.

The maximum number of configuration definitions read from the environment settings is smaller than the number of definitions in the job execution environment database. The environment settings may have been changed after a job execution environment (including job execution agents, queues, and execution-locked resources) was created with the configuration definition file for the submit job execution environment (jpqsetup.conf) or after the job was queued.

(S)

Stops the JP1/AJS3 service.

(O)

Make sure that the maximum value for the agent ID, queue ID, or locked resource ID does not exceed the maximum number of definitions specified in the configuration definition file for the (jpqsetup.conf) used for creating the submit job execution environment. To check which configuration definition of the agent ID, queue ID, or execution-locked resource ID exceeds the maximum, see the KAVU45xx message that was output immediately before this message. If the number of registered jobs exceeds the maximum, check whether the maximum number of jobs within the system specified in the environment settings is smaller than the actual number of registered jobs.

KAVU4254-E
It cannot access the database (logical-host-name). (reason code:reason-code)

An attempt to access the job execution environment database has failed. The probable causes are:

The specified database file does not exist. (reason code = 0xe00b0004)

An attempt to lock the database has failed. (reason code = 0xe00b0008)

The system resources (semaphores) were insufficient. (reason code = 0xe00b000f)

The disk has insufficient free space. (reason code = 0xe00b0010)

The number of open files reached the maximum for the system. (reason code = 0xe00b0011)

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the reason code. Check for the system resource limits that you must change. Correct the cause of the error, and then reissue the request.

KAVU4255-E
It cannot connect the database ( logical-host-name). (reason code: reason-code)

An attempt to connect to the job execution environment database has failed. The probable causes are:

The user name or password is invalid. (reason code = 0xe00b0016)

The number of database connections exceeded the server limit. (reason code = 0xe00b0017)

The database is not running. (reason code = 0xe00b0018)

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check whether a KAVU message was output before or after this message.

If one was output, also see the explanation provided by the message. If no message was output or if a reason number other than one indicated above was output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4256-E
The system file(system-file-name) cannot be removed because it lacks access authority.

A system file (a temporary file for job execution control) cannot be deleted because access permissions have not been set.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether access permissions on the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] have been set. The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp\schedule

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp/schedule

When a logical host is used
shared-directory/jp1ajs2/tmp/schedule

KAVU4257-E
The system file(system-file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file is stored in the scheduler service's directory for temporary files.

Check whether the directory specified in the AJSTMPDIR environment setting parameter for the definition key [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] exists, and also check the access permissions. The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp\schedule

When a logical host is used
shared-folder\jp1ajs2\tmp\schedule

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp/schedule

When a logical host is used
shared-directory/jp1ajs2/tmp/schedule

KAVU4258-E
The system file(system-file-name) cannot be opened. (reason code:reason-code)

An attempt to open the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4259-E
The system file cannot be closed. (number of files: number-of-files)

An attempt to close the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4260-E
The system file(system-file-name) cannot be accessed(function-name). (reason code:reason-code)

An attempt to access the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4261-E
The system file(system-file-name) cannot be written(function-name). (reason code:reason-code)

An attempt to write to the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4262-E
The system file(system-file-name) cannot be deleted. (reason code:reason-code)

An attempt to delete the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4263-E
The system file(system-file-name) cannot be read. (reason code:reason-code)

An attempt to read the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4264-E
A logical contradiction occurred in the system file access process. (reason code:reason-code)

A logical contradiction occurred during access to the system file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4265-E
Memory could not be allocated during the system file access. (reason code:reason-code)

Memory could not be secured during access to the system file.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications, and then retry the operation causing the error. If the same message is output again, review the memory estimate.

KAVU4266-E
A system call error occurred in the system file access process. (reason code:reason-code)

A system call error occurred during access to the system file.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4267-E
The agent manager function has stopped and the exec-agent cannot be registered.

The probable cause is one of the following:

The logical host name contains an error.

The execution agent cannot be registered because the agent manager function has stopped.

(S)

Cancels the requested processing.

(O)

Check the logical host name specified in the JP1_HOSTNAME environment variable, and then re-execute the job.

If the agent manager function is not running, start it, and then re-execute the job.

KAVU4268-E
The agent manager function host name cannot be resolved.

The probable cause is one of the following:

The logical host name specified in the JP1_HOSTNAME environment variable could not be resolved.

Connection to the authentication server failed.

(S)

Cancels the requested processing.

(O)

If the JP1_HOSTNAME environment variable contains a logical host name, review the specified value, check the hosts file and other settings, and then re-execute the job.

If the authentication server is not running, start JP1/Base.

KAVU4269-E
An attempt to connect to the agent manager function host failed.

An attempt to connect to the host on which the agent manager function runs has failed.

(S)

Cancels the requested processing.

(O)

Make sure that there is a host on which the agent manager function runs, and then re-execute the job.

KAVU4270-E
The system file name(system-file-name) cannot be changed. (reason code:reason-code)

An attempt to change the system file name has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4271-E
The system file(system-file-name) cannot be moved. (reason code:reason-code)

An attempt to move the system file has failed.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4272-E
A system call error occurred in the system file convert process. (system call name: system-call-name,module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during system file conversion processing.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4273-W
The temporary directory(temporary-directory-name) could not be deleted in the system file convert process.

An attempt to delete the temporary directory failed during system file conversion processing.

(S)

Continues processing.

(O)

If necessary, delete the directory indicated by temporary-directory-name.

KAVU4280-E
Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU4281-E
Insufficient disk space. (module:reason-location[reason-location], reason code:reason-code)

The amount of free space in the disk is insufficient.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU4282-E
A system call error occurred when starting process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred when the manager process for job execution control was starting.

(S)

Stops the JP1/AJS3 service.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4284-W
A system call error occurred in the communication process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during pipe communication for the manager process for job execution control.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4286-W
A system call error occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during analysis of the request for the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4287-E
A logical contradiction occurred in the request process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found during analysis of the request for the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4288-W
A system call error occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in the manager process for job execution control.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4289-E
A logical contradiction occurred in the internal process (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A logical contradiction occurred during internal processing for the manager process for job execution control. Alternatively, a shutdown request from the monitoring process for job execution control could not be accepted because the request was invalid.

(S)

Cancels processing to analyze the request for the manager process for job execution control.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4290-E
User authentication could not be initialized because the logical host name (logical-host-name) or the authentication server is invalid.

The user authentication could not be initialized since the logical host name or the authentication server name was not set or the IP address of the name could not be resolved.

(S)

Stops the JP1/AJS3 service.

(O)

Recheck the environment settings to see whether the logical host name and authentication server name are correctly set. Check the environment settings to make sure that a format error or data error did not occur in definition information below the logical host name key or JP1_DEFAULT key. Also make sure that the IP address can be determined from the specified host name. Correct the cause of the error, and then restart the JP1/AJS3 service.

KAVU4291-E
A logical contradiction occurred during the initialization of user authentication (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found during initialization of user authentication for the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4292-E
A system call error occurred during the initialization of user authentication (logical-host-name). (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred during initialization of user authentication for the manager process for job execution control.

(S)

Stops the JP1/AJS3 service.

(O)

Check whether a JP1/Base KAVA message was output to the integrated trace log for the agent host. If it was output, also see the explanation provided in that message. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4293-W
The authentication server could not be connected, but initialization will continue.

The authentication server could not be connected.

(S)

Continues startup processing of the JP1/AJS3 service.

(O)

Check the authentication server setting to make sure that the authentication server name is set correctly. If the authentication server is not started, start it.

KAVU4294-I
The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Continues processing.

(O)

Since the system may be over-loaded, check the following settings according to your operation:

We recommend you reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter).

KAVU4295-W
The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Receives the result file up to the maximum reception size.

(O)

Reduce the size of the result file. Then, if you need information on the standard output file or standard error output file, re-execute the job.

Reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter). Alternatively, recheck the maximum file size.

KAVU4296-E
The total file size of the result files, i.e. STANDARD-OUTPUT-FILE and STANDARD-ERROR-FILE, of the job with the Job (job-number) and the Agent (agent-host-name), exceed the limit (bytes) of the size of the receiving file.

The result file size exceeds the maximum.

(S)

Receives the result file up to the maximum reception size.

(O)

Reduce the size of the result file. Then, if you need information on the standard output file or standard error output file, re-execute the job.

Reduce the size of the result file (standard output file or standard error output file) specified for the job so it is smaller than the maximum file size (the value set in LimitReceiveFileSize environment setting parameter). Alternatively, recheck the maximum file size.

KAVU4297-W
The result files (standard-output-file, standard-error-output-file) of the job (job-number, agent-host-name) are being analyzed.

This message appears when a means of preventing duplicated reception of the job result file is set.

A job end notification from the agent host cannot be accepted because a result file (standard output file or standard error output file) is being analyzed on the manager host. Since the job end notification from the agent host will be accepted when the analysis of the result file finishes, detection of the job end will be delayed. The agent host outputs the message KAVU3221-E.

For details on how to prevent duplicated reception of the job result file, see 6.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1(for hosts under Windows), or 14.2.6 Preventing duplicated reception of job result files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

(S)

Aborts the job end notification.

(O)

Transferring a large result file containing more than one megabyte causes an unsuccessful request or may require a long time. If you do not need to reference the details about execution results and want to suppress unnecessary file output, specify a NULL device name for standard-output-file-name or standard-error-output-file-name in the job definition. In UNIX, assign /dev/null. In Windows, assign NUL. In particular, enter /dev/null for a job that runs in UNIX and enter NUL for a job that runs in Windows. If a file name is specified, redirect the standard output within the script file or batch file for the job. If the data append option is specified for standard output data or standard error output data, disable this option or delete and save the standard output data file or standard error output data file on a regular basis.

KAVU4299-I
The job at the agent (agent-name) was forcibly terminated.

The running job was forcibly terminated.

(S)

Cancels the requested processing.

KAVU4300-E
Failed to confirm the execution of event job at agent (agent-host-name). (reason code: reason-code)

A request to confirm the existence of the event jobs being executed at the agent failed.

(S)

Stops the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU4301-E
The alteration of agent (agent-host-name) cannot be noticed to the Event Action Manager. (reason code: reason-code)

Changes of the agent could not be reported to the Event Action Control Manager.

(S)

Stops the requested processing.

(O)

Remove the cause of the error, and then call the function again.

KAVU4302-E
Confirming the execution of event job at the agent (agent-host-name) was failed because the Event Action Manager is not started.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4303-E
Confirming the execution of event job at the agent (agent-host-name) was timed out.

The event jobs being executed at the Event Action Control Manager could not be confirmed due to a timeout.

(S)

Stops the requested processing.

(O)

Check the execution status of the Event Action Control Manager, and then call the function again.

KAVU4304-E
Confirming the execution of event job at the agent (agent-host-name) was failed because the Event Action Manager is processing other request.

The execution of the event job cannot be confirmed because the Event Action Control Manager process is currently processing another request for adding or deleting agents.

(S)

Stops the requested processing.

(O)

Wait for a while, and then call the function again.

KAVU4305-E
The alteration of the agent (agent-host-name) cannot be noticed because the Event Action Manager is not started.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4306-E
The alteration of the agent (agent-host-name) cannot be noticed because the Event Action Manager is processing other request.

The requested processing failed because the Event Action Control Manager process has not been started or has not been running.

(S)

Stops the requested processing.

(O)

Check the activation status of the Event Action Control Manager, and then call the function again.

KAVU4307-E
Completion of the alteration of the agent (agent-host-name) cannot be noticed to the Event Action Manager. (reason code: reason-code)

The completion of the alteration of the agent could not be reported to the process of the Event Action Control Manager.

(S)

Modifies the agent definitions.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4308-I
Job information delete process started. (host name: logical-host-name)

The system has started the job information deletion process.

If you execute jobs concurrently with the deletion of job information, job execution performance may degrade. If the time for deleting job information is a concern during job operation, you can estimate the required deletion time by checking the time when this message was output and the number of job information items to be deleted.

This message is not output when the number of days for storing job information is set to 0. For details on job information deletion, see 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Starts the job information deletion process.

KAVU4309-I
Job information is deleted. (host name: logical-host-name, the number of job information: number-of-deleted-items)

The job information deletion process has terminated.

If you execute jobs concurrently with the deletion of job information, job execution performance may degrade. If the time for deleting job information is a concern during job operation, you can estimate the required deletion time by checking the time when this message was output and the number of job information items to be deleted.

This message is not output when the number of days for storing job information is set to 0. For details on job information deletion, see 7.1.8 Option for deleting job information asynchronously in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)

Terminates the job information deletion process.

KAVU4310-I
The number of executing jobs reaches the concurrently-executable-job-limit (maximum-number-of-concurrently-executable-jobs) at the agent (agent-host-name). (host name:host-name,job number:job-number)

The number of jobs being executed on the agent host has reached the concurrently-executable job limit.

(S)

Outputs this message when a job cannot be registered because the number of jobs being executed on the agent host has reached the concurrently-executable job limit. The system outputs this message if you have enabled the output of a confirmation message indicating that the number of jobs being executed has reached the limit.

(O)

If the number of jobs being executed on the agent host has reached the concurrently-executable job limit, the job that cannot be executed is queued until the jobs being executed terminate. If this message appears frequently, recheck the setting of the concurrently-executable job limit. Use any of the following commands to change the concurrently-executable job limit.

For a PC job, UNIX job, action job, or custom job:
ajsagtalt command

For a QUEUE job or submitted job:
jpqagtalt command

For details on the ajsagtalt command, seeajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

For details on the jpqagtalt command, see jpqagtalt in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details on the setting for outputting a confirmation message when the number of jobs being executed has reached the limit, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows) or 14.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

KAVU4311-E
The specified value of a job number is out of range. Specify a job number in the range of 1 to 999999.

The value specified as a job number is outside the range of values that can be specified.

(S)

Cancels the request processing.

(O)

Specify a job number in the range from 1 to 999,999.

If the destination of the request is another system, check whether the specified manager host name is correct.

KAVU4312-E
A system call error occurred while initializing the database of the job execution environment. (system call name:system-call-name, module : reason-location[reason-location], reason code : reason-code)

During a cold start, a system call error occurred while the database in the job execution environment was being initialized.

(S)

Interrupts the initialization of the job execution environment database, and continues the startup processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number. If you are still unable to determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4500-W
The operating status (operating-status) does not allow the executing request (request-name). (host = manager-host-name, rec_IPaddress = IP-address-of-requesting-host, reason-location, reason-code)

The system cannot execute the request in the operating status.

(S)

Cancels the requested processing.

(O)

Check the following possible causes, and then reissue the request:

Check whether daemon operation has started.

Check whether the manager is running in reduced mode.

KAVU4501-W
The request (request-name) cannot be executed in the current job status (status). (host = manager-host-name, rec_IPaddress = IP-address-of-requesting-host, reason-location, reason-code)

The job cannot execute the request in the current status.

(S)

Cancels the requested processing.

(O)

Check the status of the job.

KAVU4502-W
The user (user-name) lacks permission for that job (job-number).

The user does not have permission for the job.

(S)

Cancels the requested processing.

(O)

Check the access permission of the user who issued the request, and the owner name of the job. Then, reissue the request.

KAVU4503-E
Agent host (agent-host-name) was failed to create automatically. (scheduler-service-name)

An unsuccessful attempt was made to create the agent automatically.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then re-execute the job.

KAVU4504-W
A pipe timeout error occurred in a job execution process at the agent(agent-host-name).

A timeout occurred during pipe communication in a job execution process.

(S)

Cancels the requested processing.

(O)

A cause may be one of the following:

Too many jobs are executed at once.

The CPU is heavily loaded.

The agent process for job execution control was swapped out for more than 300 seconds and not executed due to insufficient real memory.

If one of these causes persists and a timeout error frequently occurs during pipe communication, we recommend that you specify a timeout period longer for pipe communication on the host where the agent process is executed.

In case of Cause No. 3, check the memory usage for the entire system and increase the memory or suppress the startup of unnecessary processes to gain sufficient real memory.

For details on how to change a timeout value for pipe communication, see 14.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

If the error persists even after changing the timeout value, use the data collection tool to collect data, and then contact the system administrator.

KAVU4505-W
The job execution environment database could not be initialized. Initialization is canceled.

The job execution environment database could not be initialized during a cold start.

(S)

Performs the normal-start process.

(O)

Check the following:

Check whether the available space on the disk containing the work directory is insufficient for executing the manager process in the job execution environment.

Check whether memory is insufficient.

Check whether any process is accessing a database file in the job execution environment (in Windows).

If this message is output, the job execution environment database has not been initialized.

If you want to initialize the database, correct the above causes and then restart JP1/AJS3.

In some cases, the integrated trace might contain the KAVU4312-E, KAVU5311-E, or KAVU7238-E message. Check them altogether.

KAVU4509-E
The specified agent (agent-host-name) cannot be released because some job is being executed.

The agent could not be disconnected because there are jobs being executed.

(S)

Cancels the requested processing.

(O)

Wait until the jobs terminate, and then call the function again.

KAVU4510-W
The specified job (job-number) does not exist.

The specified job does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4511-W
The specified agent (agent-host-name) does not exist.

The specified agent does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4512-W
The specified queue (queue-name) does not exist.

The specified queue does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4513-W
The specified exclusive execution resource (exclusive-execution-resource-name) does not exist.

The specified exclusive execution resource does not exist.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4514-W
The job cannot be registered because the entrance to queue (queue-name) is closed.

The job cannot be registered because the entrance of the queue is closed.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4515-W
The job cannot be registered because the queue (queue-name) reached the maximum number of jobs (maximum-number).

The job cannot be registered because the number of jobs registered in the queue has reached the maximum number of jobs allowed in the queue.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end before issuing another request, or check the queue definition information and adjust the maximum number of jobs allowed in the queue.

To check the number of jobs registered in the queue, which is the sum of the QUEUING and EXECUTING values, use the -q or -ah option in the jpqqueshow command. Also, to change the maximum number of jobs allowed in the queue, you can use the jpqquealt command. For details about these commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVU4516-W
The queue (queue-name) reached warning number of jobs (warning-number).

The number of jobs in the queue reached the warning level.

(S)

Continues processing the request.

KAVU4518-W
Information (agent-ID) about the agent connected to the queue (queue-name) is missing.

The database does not contain the information about the agent connected to the queue.

(S)

Stops the daemon.

(O)

Check the contents in the database, and then restart.

KAVU4519-E
Some event job is being executed at specified agent (agent-host-name).

The requested processing failed because some event jobs were being executed in agent-host-name.

(S)

Cancels the requested processing.

(O)

Stops the event jobs, and then call the function again.

KAVU4520-W
The job cannot be registered because the system already reached the maximum number of jobs (maximum-number), as stipulated in environment setting (logical-host-name).

The job cannot be registered because the number of jobs registered in the queue has reached the maximum number of jobs allowed in the system as defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Either wait for an executing job to end and then issue another request, or review the value for the maximum number of jobs allowed in the system defined in the environment settings for the job execution environment. For the definition of the maximum number of jobs allowed in the system, see the values that can be specified the MaximumContentJob environment setting parameter.

KAVU4521-W
The agent cannot be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more agents can be registered because the number of registered agents reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Delete unnecessary agents, or review the number of definitions defined in the environment settings.

KAVU4522-W
The queue cannot be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more queues can be registered because the number of queues reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Check the number of queues defined in the environment settings.

KAVU4523-W
The exclusive execution resource could not be registered because the system already reached the number of definitions (number-of-definitions) stipulated in environment setting (logical-host-name).

No more exclusive execution resources can be registered because the number of registered exclusive execution resources reached the maximum defined in the environment settings.

(S)

Cancels the requested processing.

(O)

Check the number of exclusive execution resources defined in the environment settings.

KAVU4524-W
The registered jobs exceed the warning number for the system (warning-number), as stipulated in environment setting (logical-host-name).

The number of jobs in the queue reached the warning level defined in the environment settings.

(S)

Continues processing the request.

KAVU4525-W
The agent cannot be registered because the system already reached the maximum number of execution jobs (maximum-number) stipulated in environment setting (logical-host-name).

No more agents can be registered because the maximum number of jobs to be executed is reached.

(S)

Cancels the requested processing.

(O)

Check the number of jobs defined in the environment settings.

KAVU4526-I
The system recovered from the number of warning statuses, as stipulated in environment setting (manager-host-name).

The system recovered from the warning status because the number of jobs dropped below the number of warning jobs in the environment setting.

(S)

Continues processing.

KAVU4527-E
A logical contradiction occurred during the JP1 assume user check (logical-host-name). (reason module: error-location [error-location], reason code: reason-code)

The assumed JP1 user function had a logical contradiction.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4528-E
Cannot set assume user (user-name) because this user is not found.

The user indicated by user-name has not been registered as a JP1 user. The system could not assume it as a JP1 user.

(S)

Cancels the requested processing.

(O)

Register the user indicated by user-name as a JP1 user.

Alternatively, use the jpqregguestuser command to register the assumed JP1 user correctly, and then restart the JP1/AJS3 service.

KAVU4529-I
The information was recovered because the request for (request-destination) was rejected. (reason code : reason-code)

The information was returned to the status in effect before the request was executed because the request to the request destination was canceled due to some unspecified reason. The request destination is a queue name, agent name, or exclusive execution resource name.

(S)

Continues processing.

KAVU4530-W
The agent (agent-host-name) might have stopped, or an obstacle might have occurred.

The agent might have stopped or an error might have occurred in the agent.

(S)

Cancels the requested processing.

(O)

Check whether the daemon has been started, the TCP/IP communication is possible with agent-host-name, and the port number is set correctly.

KAVU4531-W
The agent (agent-host-name) host name might be invalid.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the specified agent host name.

KAVU4532-W
The client (client-host-name) might have stopped, or an obstacle might have occurred.

The client might have stopped or an error might have occurred in the client.

(S)

Cancels the requested processing.

(O)

Make sure that the client application is started, TCP/IP communication is available under the client host name and port number is valid.

KAVU4533-W
The client (client-host-name) host name might be invalid.

The network must be set up so that the IP address can be determined from the specified host name by using the hosts file or the DNS server.

(S)

Cancels the requested processing.

(O)

Make sure that TCP/IP communication is available under the client host name.

KAVU4534-W
No response was received from the agent (agent-host-name), so the status of job (job-number) was changed to recovered (status).

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but no response was returned from the agent host.

(S)

Cancels the requested processing and changes the job to the status indicated in status.

(O)

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4535-I
The agent (agent-host-name) operating status was changed to recovered.

An operation recovery (recovery from an error or stopped status) was detected during monitoring of the execution host. When an operation recovery for the execution host is detected, the system resumes registering jobs for execution in the execution host. For details on monitoring the target host, see 5.3.8(2) Monitoring execution hosts (agents) in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

(S)

Continues processing.

KAVU4536-W
The transfer file could not be accessed. (reason-code)

The system failed to access the file to be transferred.

(S)

Cancels the requested processing.

(O)

The following describes probable causes for reason codes, and suggests corrective actions. Note that the transfer file refers to the transfer source file applicable to job registration or the applicable result file when a job end notification is received.

Reason code = 0xE002110D

Cause
An attempt was made to transfer a transfer file, but there was no source file for the transfer.

Corrective action
Make sure that there is a source file for the transfer.

Reason code = 0xE002110E

Cause
There are no access permissions on the transfer file.

Corrective action
Make sure that the transfer file has access permissions.

Reason code = 0xE0021110

Cause
The transfer file is being used by another process.

Corrective action
Check whether another process is using the transfer file.
Check whether another job is using the same transfer source file or the same result file.

Reason code = 0xE0021111

Cause
An attempt to create (open) a transfer file has failed.

Corrective action
Use the data collection tool to collect data, and then contact the system administrator.

Reason code = 0xE0021112

Cause
An attempt to read a transfer file has failed.

Corrective action
Use the data collection tool to collect data, and then contact the system administrator.

If any other reason code has been output, use the data collection tool to collect data, and then contact the system administrator.

KAVU4537-W
Job information is removed because inappropriate job information was detected in the database. (job number=job-number, job name=job-name, file name=execution-file-name, submitted time=date/time-of-registration, start time=date/time-to-start-execution, end time=date/time-to-end-execution)

The job was deleted because the job data is corrupted.

(S)

An inconsistency occurred in the database since the JP1/AJS3 process terminated while registering a job or deleting job data.

Delete the job data and returns the database to the normal status. Then, continues processing.

KAVU4538-W
The status of job (job-number) missed at the agent (agent-host-name) was changed to recovered (status).

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but the specified job did not exist on the agent host.

(S)

Cancels the requested processing and changes the job to the status indicated in status.

(O)

The probable causes are:

The JP1/AJS3 service on the agent host stopped while a job end notification from the agent host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4539-W
No agent can execute the job (job-number).

No agent can execute the job.

(S)

If no agent can execute the jog after the waiting time for the job execution expires, change the status of the job.

(O)

The action to be taken differs depending on the type of the job.

For a PC job, UNIX job, action job, or custom job:
Check whether the JP1/AJS service is running on the execution host defined for the execution agent.

For a QUEUE job or submitted job:
Check whether the JP1/AJS service is running on the agent that is connected to the queue.

KAVU4540-I
The manager (manager-host-name) started planned termination.

The manager process for job execution control started planned termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4541-I
The manager (manager-host-name) started forced termination.

The manager process for job execution control started forced termination.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4542-I
The manager (manager-host-name) is monitoring queuing job termination.

The manager process for job execution control monitors the end of a queued job.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4543-I
The manager (manager-host-name) is monitoring executing job termination.

The manager process for job execution control monitors the end of a running job.

(S)

Continues processing to stop the JP1/AJS3 service.

KAVU4545-I
The cold start processing will start in the manager (manager-host-name).

Cold start processing will start on the manager.

(S)

Continues processing.

KAVU4546-W
The PATH variable could not be acquired at the agent (agent-host-name).

The PATH environment variable for the user that attempted to log in to the OS could not be acquired at the agent.

(S)

Cancels the requested processing.

(O)

Check the following:

Check whether there is sufficient free space in the disk.

Check whether the login script for the user that attempted to log in to the OS has any conditions that cause processing to abort.
If the login script has any coding unnecessary for job execution by JP1/AJS3, delete that portion or use the JP1JobID environment variable to skip the portion.

KAVU4547-W
You are not authorized to access the temporary file at the agent (agent-host-name).

You do not have access permission for the following files or directories:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Probable causes are listed below. Check the status of the agent host.

A privilege to the system file directory (the default is /var/opt/jp1ajs2/sys) has been changed.

A privilege to the work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been changed.

A privilege to the jpqagtlock file or the temporary work file in the system file directory has been changed.

Another program is accessing the above directories or the temporary work file.

If a privilege to the file or the directory has been changed, give the write and read permissions to the OS user that executes jobs. The temporary work file (the file that begins with A_JPQ) may remain in the work directory used for executing the agent process even if the job terminates. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU4548-W
The temporary file at the agent (agent-host-name) cannot be accessed.

You could not access the following work directories or files:

Work directory used for executing the agent process, or files in the work directory

System file directory or files in the system file directory

(S)

Cancels the requested processing.

(O)

Examine a cause that may be one of the following at the agent host and check the status of the agent host:

The system file directory (the default is /var/opt/jp1ajs2/sys) has been deleted.

The work directory (the default is /var/opt/jp1ajs2/tmp) used for executing the agent process has been deleted.

The jpqagtlock file or the temporary work file has been deleted from the system file directory.

Another program is accessing the above directories or the temporary work file.

The home directory specified in /etc/passwd for the mapped OS user does not exist.

Write permission has not been set for the work directory used for executing the agent process (default work directory: /var/opt/jp1ajs2/tmp).

If the jpqagtlock file or any of the directories indicated above have been deleted, re-install JP1/AJS3.

If the work directory used for executing the agent process exists, check whether write permission is set for the directory. If write permission is not set, set write permission for the directory or change the work directory to a directory for which write permission has been set.

The temporary work file (the file that begins with A_JPQ) might remain in the work directory used for executing the agent process even if the job terminates normally. If this is the case even after JP1/AJS3 stops, delete the temporary work file.

KAVU4549-W
The process has too many open files at the agent (agent-host-name).

The number of opened files reached the maximum set by the kernel parameter at the agent.

(S)

Cancels the requested processing.

(O)

Use the kernel parameter at the agent to increase the maximum number of files that can be opened. For details on how to estimate the value to be set in the kernel parameter, see Release Notes.

KAVU4550-W
The execution file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the executable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

If this message appears when an action job is executed, the platform specified in the detailed definition of the action job may be invalid. Check the detailed definition, and then retry.

KAVU4551-W
You are not authorized to access the execution file (file-name) at the agent (agent-host-name).

You are not authorized to access the executable file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4552-W
The environment file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the environment variable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4553-W
You lack access permission for the environment file (file-name) at the agent (agent-host-name).

You do not have permission for the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4554-W
The environment file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the environment variable file name.

KAVU4555-W
The environment file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the environment variable file at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4556-W
The standard input file (file-name) is missing at the agent (agent-host-name).

The agent does not contain the standard input file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4557-W
You lack access permission for the standard input file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4558-W
The standard input file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard input file name.

KAVU4559-W
The standard input file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard input file at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4560-W
You lack access permission for the standard output file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4561-W
The standard output file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard output file name.

KAVU4562-W
The standard output file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard output file at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4563-W
You lack access permission for the standard error output file (file-name) at the agent (agent-host-name).

You do not have permission to access the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4564-W
The standard error output file (file-name) at the agent (agent-host-name) cannot be opened.

The system cannot open the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the standard error output file name.

KAVU4565-W
The standard error output file (file-name) at the agent (agent-host-name) cannot be accessed.

The system failed to access the standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4566-W
The work path name is too long at the agent (agent-host-name), so the file cannot be created.

The system cannot create the file because the work path name at the agent is too long.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4567-W
There is no work path at the agent (agent-host-name).

The agent does not have a work path.

(S)

Cancels the requested processing.

(O)

The directory specified in the environment setting parameter for the work directory name for execution of the agent process for job execution control may not exist.

Remove the cause of the error, and then reissue the request.

KAVU4568-W
You lack access permission for the work path at the agent (agent-host-name).

You do not have permission to access the work path of the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4569-W
The file path (path-name) variable at the agent (agent-host-name) could not be resolved.

The system failed to resolve the file path at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4570-W
The parameter (parameter-name) variable at the agent (agent-host-name) could not be resolved.

The system failed to resolve the parameter at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4571-W
The user mapping (JP1-user-name) at the agent (agent-host-name) failed.

User mapping failed at the agent.

(S)

Cancels the requested processing.

(O)

Check whether any of the following probable causes are present. Also check the integrated trace log for the agent to which a message indicating error details may have been output.

In the agent host, the manager host name specified for the server host name for the JP1 user is invalid.

The default queue setting for the agent contains multiple agents to be connected. Because the priority setting contains an error or because an incorrect agent is connected, the job was executed on an unexpected agent.

User mapping is not set on the agent host.

The password of the OS user on the agent host has been changed (for Windows only)

A JP1 user with the same name as that of the OS user who executed the ajsentry command does not exist.

The OS user specified in the detailed job definition is not mapped to the JP1 user.

The JP1 user for the owner differs from the JP1 user who registered the job for execution.

Memory was insufficient.

The execution agent group setting contains multiple associated execution agents. Because the priority setting contains an error or because an incorrect execution agent is associated, the job was executed on an unexpected agent.

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

Set the correct manager host name for the JP1 user.

Execute the jpqagtlink command to change the priority of agents, or execute the jpqagtunlink command to release the connection between the default queue of the agents and the unexpected agent.

Map the JP1 user to the OS user on the agent where the job is to be executed.

Execute the jbsumappass command to re-set the password of the OS user. For password, specify the password of the OS user (for Windows only)

Do either of the following, and then re-execute the ajsentry command:
- Add a JP1 user with the same name as that of the OS user, and map the JP1 user to the OS user.
- Specify the owner as the job execution user in the job definition.

Check the OS user specified in the detailed job definition. Map the OS user to the JP1 user on the agent where the job is to be executed.

Determine whether the owner or the JP1 user who registered the job for execution registers the job for execution, and then set the execution user type correctly.

Check the memory status and then re-estimate memory requirements.

Execute the ajsagtalt command to change the priority, or exclude the association between the execution agent group and the unexpected execution agent.

For details on how to set up user mapping, see 3. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under Windows)or 12. Setup in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for hosts under UNIX).

For details on the JP1/AJS3 commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 or 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details about the JP1/Base commands, see the Job Management Partner 1/Base User's Guide.

KAVU4572-W
The user (user-name) could not be masked at the agent (agent-host-name).

The system failed to mask the user at the agent.

(S)

Cancels the requested processing.

(O)

Check the user mapping definition, and then reissue the request.

KAVU4573-W
The job priority at the agent (agent-host-name) could not be changed.

The system failed to change the job priority at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4574-W
An error occurred when a job process was generated at the agent (agent-host-name).

An error occurred while the system was generating a job process at the agent.

(S)

Cancels the requested processing.

(O)

In Windows, check whether account permissions for the agent host are set correctly. For details on how to set account permissions, see the explanation about how to give user rights to an OS user in an Active Directory environment in Before setting user mapping in the Job Management Partner 1/Base User's Guide.

To change the JP1/AJS3 service startup account from the system account to the user account, you also need permission for replacing a process level token.

For details on the permission necessary when the service account is set to the user account, see 4.2.3(1)(c) When multiple scheduler services are activated and you want to avoid desktop heap shortages in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

For other cases, use the data collection tool to collect data, and then contact the system administrator.

KAVU4575-W
An error occurred when a job process was started at the agent (agent-host-name).

An error occurred while the system was starting a job process at the agent.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log of the agent to remove the cause of the error, and then reissue the request.

KAVU4576-W
The standard error file or standard error output file could not be sent at the agent (agent-host-name).

The system failed to transfer the standard output file or standard error output file at the agent.

(S)

Cancels the requested processing.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then reissue the request.

KAVU4578-W
Execution file (file-name) could not be accessed at the agent (agent-host-name).

The system failed to access the executable file at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4580-W
The user (user-name) does not have administrator permission at the agent (agent-host-name).

If you specify the execution priority of the Unix job to 4 or 5, the user that attempts to log in to the OS must have superuser privileges.

(S)

Cancels the requested processing.

(O)

Reissue the request as a user who has superuser privileges.

KAVU4581-W
The execution file (file-name) at the agent (agent-host-name) is not an executable file.

The file you attempted to execute at the agent is not an executable file.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4582-W
The execution file (file-name) cannot be merged with the command statement at the agent (agent-host-name).

The execution file of the agent cannot be merged with the command statement.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4583-W
The execution shell is missing at the agent (agent-host-name).

The shell being used to execute the job is missing at the agent.

(S)

Cancels the requested processing.

(O)

Check the shell being used to execute the job.

Also check whether the login shell specified in /etc/passwd for the mapped OS user exists.

KAVU4584-W
The agent (agent-host-name) does not have permission for changing owner of the file.

You do not have permission to change the owner of the file using the agent.

(S)

Cancels the requested processing.

(O)

Check the contents of the KAVU3592-W message that is output to the integrated trace information log of the agent, and then change the access permission for the file and its directory, or change the directory.

KAVU4585-W
No path is specified to the destination for storing transfer files at the agent (agent-host-name).

The path to store transfer files is missing at the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4586-W
You are not authorized to access the path to the destination for storing transfer files or the files at the agent (agent-host-name).

You do not have access permission for transfer files of the agent or the path to store them.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4587-W
The agent (agent-host-name) transfer files cannot be opened.

The transfer file of the agent cannot be opened.

(S)

Cancels the requested processing.

(O)

The system may not accept the format or the length of the file name. Check the transfer file name.

KAVU4588-W
Another process is using the agent (agent-host-name) transfer files.

Another process is using the transfer file of the agent.

(S)

Cancels the requested processing.

(O)

Remove the cause of the error, and then reissue the request.

KAVU4589-W
The transfer files could not be accessed at the agent (agent-host-name).

The transfer file could not be accessed at the agent.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU4590-W
The job format is unacceptable at the agent (agent-host-name).

A job execution request was issued to the agent host, but the request was rejected due to an invalid parameter.

(S)

Cancels the requested processing to execute the job.

(O)

Use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4591-W
The agent (agent-host-name) job execution environment is invalid.

A job execution request was issued to the agent host, but the request was rejected due to an invalid execution environment on the agent host. The probable causes are:

You do not have permission to execute the specified executable file.

For a JP1/Script job, the JP1/Script version is not supported or the format of the JP1/Script executable file is not used.

The manager host name could not be converted to an IP address.

Shared memory was insufficient on the agent host.

The agent process has failed to initialize the log.

(S)

Cancels the requested processing to execute the job.

(O)

Use the integrated trace log on the agent host to check the cause of the error. Correct the cause of the error, and then reissue the request. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4593-W
An executable the agent does not exist.

A job execution request was issued to the agent host, but an executable agent host was not found.

(S)

Cancels the requested processing to execute the job.

(O)

Check whether any of the following probable causes are present:

The agent host or the JP1/AJS3 service on the agent host has stopped.

The agent host name has not been resolved on the manager.

The network, including hardware, has a problem.

The port number is not set correctly between the manager and the agent.

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

Restart the agent host or JP1/AJS3 service.

Define the agent host name in the hosts file for the manager.

Recheck the settings of the network, including hardware.

Recheck the port number.

Use the integrated trace logs for the manager host and agent host to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message.

If you still cannot determine the cause after checking the above items, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4594-W
The job execution was canceled.

The system canceled executing the job.

(S)

Terminates the requested processing.

KAVU4596-W
No response was received from the agent (agent-host-name), so the job was forcibly terminated.

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but no response was returned from the agent host.

(S)

Cancels the requested processing and changes the job to the Killed status.

(O)

A communication error may have occurred. Use the integrated trace logs for the manager host and agent host to check whether a KAVU or KNAC message was output before or after this message. If it was output, also see the explanation provided in that message. If no such messages were output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4597-W
A missed job at the agent (agent-host-name) was forcibly terminated.

A request to check the status of, or forcibly terminate, a job was issued to the agent host, but the specified job did not exist on the agent host.

(S)

Cancels the requested processing and changes the job to the Killed status.

(O)

The probable causes are:

The JP1/AJS3 service on the agent host stopped after a job end notification from the agent host failed.

The JP1/AJS3 service terminated abnormally while the job was running on the agent host.

Use the integrated trace logs for the manager host and agent host to check whether a KAVU message was output before or after this message. If it was output, also see the explanation provided in that message. If no KAVU message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4598-W
The work path (path-name) at the agent (agent-host-name) is not a full path.

The work path must be specified with an absolute path name.

(S)

Cancels the requested processing.

(O)

Check the work path in the job definition.

KAVU4626-I
Assume from OS user (OS-user-name) to JP1 user (JP1-user-name).

JP1-user-name is assumed for the specified OS user that has not been registered as a JP1 user.

(S)

Continues processing.

KAVU4700-E
A system call error occurred in a job execution process at the agent (agent-host-name).

A system call error occurred during execution of the job on the agent.

(S)

Cancels the requested processing.

(O)

Check the integrated trace log for the agent to which a message indicating error details may have been output. If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator.

KAVU4701-E
A logical contradiction occurred in a job execution process at the agent (agent-host-name).

A logical contradiction occurred during execution of the job on the agent host.

(S)

Cancels the requested processing.

(O)

Check whether a KAVU message was output to the integrated trace log for the agent host. If it was output, also see the explanation provided in that message. If you cannot determine the cause or if no such message was output, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4702-E
Memory at the agent (agent-host-name) could not be allocated.

An attempt to acquire memory on the agent has failed.

(S)

Cancels the requested processing.

(O)

Check the memory requirements on the agent host, terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU4703-E
The agent (agent-host-name) disk is full.

A job execution request was issued to the agent host, but the request was rejected due to insufficient space on the disk.

(S)

Cancels the requested processing to execute the job.

(O)

Free up space on the disk, and then reissue the request.

KAVU4704-E
No more process can be generated at the agent (agent-host-name).

The number of processes reached the maximum set in the kernel parameter for the agent.

(S)

Cancels the requested processing.

(O)

Increase the maximum number of processes set in the kernel parameter for the agent. Set a sufficient value, considering the number of concurrently executable job processes, in addition to the number of JP1/AJS3 processes.

For details on the JP1/AJS3 processes, see the description of how to check the status of processes in 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU4717-E
An attempt by the agent (agent-host-name) to transmit the result file for the job (job-number) has failed. (reason code : reason-code)

An attempt to transfer a result file from the agent host to the manager host failed at the end of the job.

(S)

Cancels the requested processing.

(O)

Although the job is placed in the Ended abnormally status with the end code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

If the reason code is 0xe0021101, memory on the agent host might have been insufficient during transfer of the result file. Terminate any other unnecessary applications, and then retry. If the same message reappears, re-estimate memory.

Also, memory may be insufficient because the result file is too large. Check the size of the result file for the job. Also, make sure that too much data will not be output even if additional writes are specified for the standard output file or standard error output file.

If the reason code is 0xe0021127, transfer might have failed because the result file was too large. In this case, make sure that the result file for the job is not too large.

For other reason codes, use the integrated trace logs for the manager host and agent host to check the cause of the error, correct the cause of the error, and then retry.

If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU4718-E
An error occurred in the end processing of the job (job-number) at the agent (agent-host-name). (reason code : reason-code)

Termination processing failed after the job process terminated on the agent host.

(S)

Cancels the requested processing.

(O)

Although the job is placed in the Ended abnormally status with the end code -1, the job process itself may have terminated normally. Check the end status of the job process on the agent host.

Use the integrated trace logs for the manager host and agent host to check the cause of the error, correct the cause of the error, and then retry.

If you cannot determine the cause, use the data collection tool to collect data, and then contact the system administrator. Data must be collected on both the manager host and the agent host.

KAVU5002-E
A command executed during reorganization of the job execution environment dataset ended abnormally.: Jischk l3 table-name: return code=return-code-of-Jischk Please look at maintenance-log-file-name)

While maintenance was being performed with the jajs_maintain command, invalid data was detected in the Jischk command, which verifies ISAM file consistency. For details of the error message output by Jischk, see the maintenance log file.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Correct the cause of the abnormal termination of maintenance processing by checking the maintenance log file, and then re-execute the maintenance processing.

For details on the maintenance log file, see the notes in jajs_maintain in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details on the Jischk command, see the Job Management Partner 1/Base User's Guide.

KAVU5003-E
A command executed during reorganization of the job execution environment dataset ended abnormally.: Jisext table-name file-name.back: return code=return-code-of-Jisext)

While maintenance was being performed with the jajs_maintain command, an error occurred in the Jisext command, which extracts data from ISAM files.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. If the error occurred in the script for automatic reorganization of the ISAM database, check whether the service is starting, there is a process that is using the file, or the disk has sufficient free space. Then, re-execute the command.

KAVU5004-E
A command executed during reorganization of the job execution environment dataset ended abnormally.: Jisconv -t SI table-name.back table-name_NEW: return code=return-code-of-Jisconv

While maintenance was being performed with the jajs_maintain command, an error occurred in the Jisconv command, which re-creates ISAM files from extracted data.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. Check whether the disk has sufficient free space, and then re-execute the command. If you cannot determine the cause of the error, collect data and then contact the system administrator.

KAVU5005-E
A backup directory could not be created during reorganization of the job execution environment database. (directory-name): return code=return-code

While maintenance was being performed with the jajs_maintain command, a work directory could not be created.

(S)

Cancels command execution.

(O)

Check whether you have the permission to write into the directory for the temporary file for the job execution environment or the disk has sufficient free space.

KAVU5007-E
A file to back up or recover an ISAM file could not be copied during reorganization of the job execution environment database. (table-name): return code=return-code

While maintenance was being performed with the jajs_maintain command, a file to back up or recover an ISAM file could not be copied.

(S)

Cancels command execution. If there are unprocessed tables, the system continues command execution.

(O)

Check whether the disk has sufficient free space, and then re-execute the command.

KAVU5009-E
An attempt to rename files for recovering ISAM files during reorganization of the job execution environment database failed. (table-name) : return code=return-cod

While executing the script for automatically reorganizing the ISAM database of the job execution environment (jpqautocond) or while maintenance was being performed with the jajs_maintain command, the file could not be renamed to recover the ISAM file.

(S)

Cancels command execution. If there are any tables in the service still being unprocessed, the system continues command execution.

(O)

Check whether you have permission to write to the directory specified in the directory for the job execution environment database.

KAVU5012-E
The script to reorganize the job execution environment table (table-name) could not be started.: maintenance-information

While maintenance was being performed with the jajs_maintain command, the script to reorganize the table could not be started.

(S)

Cancels command execution. If, however, any tables remain unprocessed, the system continues command execution.

(O)

Memory may have become insufficient, or the number of processes started in the system may have reached the limit. If you cannot determine the cause, collect data and then contact the system administrator.

KAVU5013-E
The script to reorganize the job execution environment table (table-name) ended abnormally.: maintenance-information

While maintenance was being performed with the jajs_maintain command, the script to reorganize the table ended abnormally because of an unexpected error.

(S)

Cancels command execution. If, however, any tables remain unprocessed, the system continues command execution.

(O)

Execute Jischk -l3 table-name to check whether a problem has occurred with the table for which reorganization ended abnormally. In addition, collect data and then contact the system administrator.

KAVU5014-E
Preparations for job execution environment reorganization could not be made.: maintenance-information

While maintenance was being performed with the jajs_maintain command, preparations for table reorganization could not be made.

(S)

Cancels command execution.

(O)

System resources may be insufficient because of insufficient memory. If you cannot determine the cause, collect data and then contact the system administrator.

KAVU5015-I
Job execution environment maintenance ended normally.

The maintenance of the job execution environment ended normally.

(S)

Terminates maintenance of the job execution environment normally.

KAVU5016-E
Job execution environment maintenance ended abnormally.: maintenance-information

The maintenance of the job execution environment ended abnormally.

(S)

Terminates maintenance of the job execution environment abnormally.

(O)

See the maintenance log file, and investigate the cause of abnormal termination of maintenance. Then, perform maintenance again.

KAVU5200-E
The database version (version) is invalid.

The version of the job execution environment database is invalid.

(S)

Stops the JP1/AJS3 service.

(O)

Re-create the job execution environment database, and then restart the JP1/AJS3 service.

KAVU5280-E
Memory could not be allocated. (size:size, module:reason-location[reason-location], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels the requested processing.

(O)

Terminate any other unnecessary applications, and then reissue the request. If the same message reappears, re-estimate memory.

KAVU5281-E
Disk space is insufficient. (module:reason-location[reason-location], reason code:reason-code)

The amount of free space in the disk is insufficient.

(S)

Cancels the requested processing.

(O)

Increase the free space in the disk, and then reissue the request.

KAVU5282-W
A system call error occurred during a database process. (module:reason-location[reason-location], reason code:reason-code)

A system call error occurred in a database process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

If this message is output while JP1/AJS3 is running, check whether the database is running. If the database is not running, start the database and then restart JP1/AJS3.

KAVU5283-E
A logical contradiction occurred during a database process. (module:reason-location[reason-location], reason code:reason-code)

An invalid parameter was found in a database process for job execution control.

(S)

Cancels the database process for job execution control.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU5284-E
It is short of the system resources. (reason-location)

The number of files opened in the system reached the maximum, or semaphores are insufficient.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the contents of the message KAVU5501-E.

If the number of files opened in the system reached the maximum, use the kernel parameter to increase the number of files that can open in the system. If semaphores are insufficient, increase the number of semaphores set in the kernel parameter.

For details on how to estimate the values to be set in the kernel parameters, see Release Notes.

KAVU5285-E
There is no the database table, or it is short of the system resources. (reason-location)

The database table does not exist or system resources are insufficient.

(S)

Cancels the requested processing.

(O)

Use the integrated trace log to check the contents of the KAVU5501-E message.

If the database table does not exist, check whether the database table exists in the directory specified in the DatabasePath environment setting parameter for job execution control. If the database table does not exist, you must re-create the database for job execution control.

If the database table exists, check the estimate of the kernel parameters. For details on how to estimate the values to be set in the kernel parameters, see Release Notes.

KAVU5286-E
A disk difficulty occurred. (reason-location)

An input or output error occurred on the disk.

(S)

Cancels the requested processing.

(O)

Check whether there is no problem on the disk volume itself.

KAVU5287-E
The database table is locked. (reason-location)

Another program locks the database table.

(S)

Cancels the requested processing.

(O)

This error may occur if one of the following was being executed when you attempted to execute the job:

The JP1/AJS3 data collection tool _04.bat (for Windows only)

A command (except the jpqdbcond -L command) that uses an ISAM database such as verifying and condensing the ISAM database for JP1/Base or JP1/AJS3

A backup software

In addition to the above cases, this error may occur when you are running a program that opens a database file for the job execution environment in the monopoly mode or in a mode that only shares reading of files.

When you schedule the above operation, make sure that the operation will be performed at a different time from when jobs are executed

If you want to display the ratio of unused area in the ISAM file used for the job execution environment during operation of JP1/AJS3, execute the jpqdbcond command with the -L option.

KAVU5288-E
The database table (table-name) could not condense.

Reorganizing the database for the job execution environment has abnormally terminated.

(S)

Cancels the requested processing.

(O)

Also check the integrated trace log for the KAVU5501-E message.

Check the cause of the error, remove the cause, and then retry reconfiguring the ISAM file in the job execution environment.

KAVU5289-E
Not supported on related programs (product-name).

An attempt was made to use functions that are unsupported in the related programs.

(S)

Cancels the requested processing.

(O)

Check the supported version of a related program, and upgrade the version of the program.

KAVU5290-E
The database file size is larger than the limit, or memory could not be allocated. (reason location: reason-location [reason-location], reason number: reason-number)

The file size may have exceeded the limit or memory could not be allocated during database access.

(S)

Cancels the requested processing.

(O)

The possible causes are:

A file that is equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

The ISAM file is in an invalid status.

Memory is insufficient.

If the cause of the error is 1, recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, 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 on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide

You can use the Jischk command to check for cause number 2. Use this command to 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.12 Troubleshooting problems related to invalid ISAM files in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

If the cause is number 3, terminate all unnecessary applications, and then reissue the request. If the same message reappears, recheck the memory estimate.

If the cause is none of the above, use the data collection tool to collect data, and then contact the system administrator.

KAVU5291-E
The database file size exceeded the limit. (reason location: reason-location [reason-location], reason number: reason-number)

The request was not processed because the size of the job execution environment database exceeded the limit for the size of ISAM files.

(S)

Cancels the requested processing.

(O)

The probable cause of the error is that a file equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

Recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, 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 on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU5292-E
The specified tablespace or RDAREA does not exist. (module:reason-location[reason-location])

The table could not be created because the specified tablespace or RDAREA did not exist.

(S)

Cancels the requested processing.

(O)

Specify the correct tablespace or RDAREA, and then retry.

KAVU5293-E
The specified tablespace or RDAREA is invalid. (module : reason-location[reason-location])

The table could not be created because the specified tablespace or RDAREA was invalid.

(S)

Cancels the requested processing.

(O)

Specify the correct tablespace or RDAREA, and then retry.

KAVU5294-E
Could not connect to the database because the upper limit of a server setting was exceeded. (module:reason-location[reason-location])

The system could not connect to the database because the limit value defined on the database server was exceeded.

(S)

Cancels the requested processing.

(O)

Either stop other processes connected to the database or re-set the limit for the database, and then retry.

KAVU5295-E
Could not connect to the database because the username or password was invalid. (module:reason-location[reason-location])

Connection to the database was not possible because an invalid user name or password was used.

(S)

Cancels the requested processing.

(O)

Specify the correct user name and password, and then retry.

KAVU5296-E
Could not connect to the database. (module:reason-location[reason-location])

The system could not connect to the database.

(S)

Cancels the requested processing.

(O)

Check whether the database is running.

If this message is output while JP1/AJS3 is running, start the database and then restart JP1/AJS3

KAVU5309-E
A system call error occurred while checking the administrator permissions. (system call name:system-call-name,module:reason-location[reason-location],reason code:reason-code)

A system call error occurred when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is the value acquired by the GetLastError function of Win32API. If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5310-E
Memory allocation failed while checking the administrator permissions. (size:size,module:reason-location[reason-location],reason code:reason-code)

Memory could not be secured when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications and issue another request.

If the same message is still output, review the memory estimate.

KAVU5311-E
A system call error occurred while initializing the database of the job execution environment.(system call name : system-call-name, module : reason-location[reason-location], reason code : reason-code)

During a cold start, a system call error occurred while the database in the job execution environment was being initialized.

(S)

Interrupts the initialization of the job execution environment database, and continues the startup processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number.

If the system call name is mkdir and the reason code indicates insufficient write and read permissions, set the write and read permissions for the user starting JP1/AJS3 on the work directory relevant to execution of the manager process in the job execution environment. Then, if necessary, restart.

Default Windows Server 2008 work folder
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp (The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

Default Windows Server 2003 work folder
JP1/AJS3 - Manager-installation-folder\tmp

Default UNIX work directory
/var/opt/jp1ajs2/tmp

If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5501-E
message-from-database-system

This is a message from the database system.

(O)

Check whether any of the following probable causes are present:

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 command _04.bat was being executed.

The message contains SHMMNI insufficient:
The shared memory ID was insufficient.

The message contains File not found or insufficient system resources:
Free space on the disk was insufficient.

The message contains File not found or insufficient system resources:
The job execution environment database does not exist.

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:

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.

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

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 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.

Use the jpqimport command to create a job execution environment database.
For details on this command, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

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.12 Troubleshooting problems related to invalid ISAM files in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVU5502-E
An attempt to acquire the status of the JP1/AJS2 - Datareplicator failed. (host name: host-name, function name: function-name, reason code: reason-code)

The status of JP1/AJS2 - Datareplicator could not be acquired. One of the following problems might have occurred:

If reason-code is 101 or 102
The number of open files has reached the system limit.

If reason-code is 103
Memory is insufficient.

If reason-code is 104
Free disk space is insufficient.

(S)

Cancels the request processing.

(O)

If the reason code is 101 or 102 (the number of open files has reached the system limit), use the kernel parameter to increase the maximum number of files that can be opened. For information about how to estimate the kernel parameter value, see Release Notes.

If the reason code is 103 (memory is insufficient), stop unnecessary applications, and then retry the operation. If the same message is still output, review the memory estimate.

If the reason code is 104 (remaining disk space is insufficient), increase the remaining disk space, and then retry the operation.

If any other reason code is output, use the data collection tool to collect data, and then contact the system administrator.

KAVU5800-I
The definition process for configuration definition ended normally.

The submit job configuration definitions for the configuration definition file for the execution environment (jpqsetup.conf) are defined in the job execution environment database all at one time.

(S)

Continues processing.

KAVU5801-I
The output process for configuration definition ended normally.

The job configuration definitions for the job execution environment were output to a file.

(S)

Continues processing.

KAVU5900-E
There is no daemon starting control lock file.

There is no daemon starting control lock file.

(S)

Cancels command execution.

(O)

Check the lock file .jpqmanlock under the system file directory (/var/opt/jp1ajs2/sys). When you are creating a database for logical hosts, the file name is .jpqmanlock. logical-host-name.

If the system file directory or the lock file shown above has been deleted, you must re-install JP1/AJS3. For logical hosts, you must set up the environment for a cluster again.

For details on how to set up the environment for a cluster, see 16.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU5901-E
The specified file cannot be found.

No file was specified in the jpqimport or jpqexport command.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVU5902-E
The specified file already exists.

The specified file already exists.

(S)

Cancels command execution.

(O)

The information in a file to which the jpqexport command outputs the job execution environment cannot be overwritten. Specify a new file.

Before outputting the job execution environment to a file, always delete or save the existing file.

Remove the cause of the error, and then re-execute the command.

KAVU5903-E
You lack access permission for the specified file.

There are no access permissions on the file specified in the jpqimport command or on the destination directory for the file, or on the destination directory for the file specified in the jpqexport command.

(S)

Cancels command execution.

(O)

Check the access permissions on the file specified in the jpqimport command or on the destination directory for the file, or on the destination directory for the file specified in the jpqexport command. The jpqimport command requires read permission and the jpqexport command requires write permission for the account that executes the command.

Remove the cause of the error, and then re-execute the command.

KAVU5904-E
The specified directory (folder) is missing.

The specified directory (folder) does not exist.

(S)

Cancels command execution.

(O)

Check whether the directory specified in the jpqimport or jpqexport command exists.

Remove the cause of the error, and then re-execute the command.

KAVU5905-W
The system file (file-name) cannot be removed because it lacks access authority.

The system file (a temporary file for job execution control) cannot be deleted since you do not have access permission for it.

(S)

Cancels the deletion of the system file.

(O)

A system file (a temporary file for job execution control) is stored in the relevant work directory when the manager process is executed in the job execution environment. Check the access permissions on the directory specified in the WorkPath environment variable parameter for [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process].

The default are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp

When a logical host is used
shared-folder\jp1ajs2\tmp

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp

When a logical host is used
shared-directory/jp1ajs2/tmp

KAVU5906-W
The system file (file-name) could not be removed because a system call error occurred.

The system file (a temporary file for job execution control) could not be deleted due to a system call error.

(S)

Cancels the deletion of the system file.

(O)

The system file (a temporary file for job execution control) is stored in the relevant work directory when the manager process is executed in the job execution environment. Check whether the directory specified in the WorkPath environment variable parameter for [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] exists, and also check the access permissions.

The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp

When a logical host is used
shared-folder\jp1ajs2\tmp

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp

When a logical host is used
shared-directory/jp1ajs2/tmp

KAVU5910-E
There is no the database table, or it is short of the system resources.

There is no database table for job execution control, or the system resources are insufficient.

(S)

Cancels command execution.

(O)

Check whether the database table file exists in the directory specified in the -dp option of the jpqexport command or in the directory specified in the DatabasePath environment setting parameter for job execution control, and then re-execute the command. If there is no database table, you need to create another database for job execution control.

For a database table in the UNIX environment, the system resources could also be insufficient. Therefore, check the estimate in the kernel parameter.

For information about how to estimate the kernel parameter, see Release Notes.

KAVU5911-E
The specified database table already exists.

The specified database already exists.

(S)

Cancels command execution.

(O)

Check the database table file under the directory containing the database for the job execution environment.

If the database table file is in the directory specified in the DatabasePath environmental setting parameter, create a backup, delete the file, and then re-execute the command.

The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\database\queue
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\database\queue

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\database\queue

When a logical host is used
shared-folder\jp1ajs2\database\queue

For UNIX

When a physical host is used
/var/opt/jp1ajs2/database/queue

When a logical host is used
shared-directory/jp1ajs2/database/queue

KAVU5912-E
You lack connect permission for that database.

You do not have permission to connect the database.

(S)

Cancels command execution.

(O)

Check your database access permission.

KAVU5913-E
You lack access permission for the database.

You do not have permission to access the database.

(S)

Cancels command execution.

(O)

Check your database access permission.

KAVU5914-E
You do not have administrator permission to execute the command.

You do not have permission to execute the command (administrator permission).

(S)

Cancels command execution.

(O)

Re-execute the command as an administrator.

Windows requires administrator permission and UNIX requires the superuser permission.

For Windows, if UAC is being used, the administrator must re-execute the command.

Check whether the KAVU5309-E or KAVU5310-E message was output together with this message. If a KAVU message was output, read the message explanation.

KAVU5915-E
There is no path for storing the database.

The database storage path does not exist.

(S)

Cancels command execution.

(O)

Make sure the directory specified in the command or the directory specified in the DatabasePath environmental setting parameter for job execution control is correct, and then re-execute the command.

If there is no directory for storing the database for job execution control, you need to create another database for job execution control.

KAVU5916-E
An attempt to acquire the status of the JP1/AJS2 - Datareplicator failed. (host name:host-name, function name:function-name, reason code:reason-code)

The status of JP1/AJS2 - Datareplicator could not be acquired. One of the following problems might have occurred:

If reason-code is 101 or 102
The number of open files has reached the system limit.

If reason-code is 103
Memory is insufficient.

If reason-code is 104
Free disk space is insufficient.

(S)

Cancels command execution.

(O)

If the reason code is 101 or 102 (the number of open files has reached the system limit), use the kernel parameter to increase the maximum number of files that can be opened. For information about how to estimate the kernel parameter value, see Release Notes.

If the reason code is 103 (memory is insufficient), stop unnecessary applications, and then retry the operation. If the same message is still output, review the memory estimate.

If the reason code is 104 (remaining disk space is insufficient), increase the remaining disk space, and then retry the operation.

If any other reason code is output, use the data collection tool to collect data, and then contact the system administrator.

KAVU5917-E
You cannot execute this command(command-name) under current condition. (reason code:reason-code)

The command cannot be executed under current conditions. The jpqimport command cannot be executed on a replication-destination manager host on which JP1/AJS2 - Datareplicator is operating.

(S)

Cancels command execution.

(O)

Check whether the command was executed on the replication-destination manager host.

If the command was executed on the replication-destination manager host, execute the command again on the replication-source manager host.

KAVU5920-E
The manager or the jpqimport command is running on the same logical host (logical-host-name).

The JP1/AJS3 service or the jpqimport command is running on the same logical host.

(S)

Cancels command execution.

(O)

If the JP1/AJS3 service is running, stop the JP1/AJS3 service and then re-execute the command.

If the jpqimport command is running, wait for the jpqimport command to complete processing, and then retry the operation.

Before creating another database in the job execution environment, you must always stop the JP1/AJS3 service. Delete or save the files under the directory for saving the created database for job execution control. The files to be deleted means all files under the directory specified in the -dp option or all files under the directory specified in the DatabasePath environment setting parameter for job execution control.

KAVU5921-E
Environment settings or the logical host name is invalid.

The environment settings or the logical host name is invalid.

(S)

Cancels command execution.

(O)

Check whether the specified logical host name is correct and whether the specified logical host name is the same as that in the environment setting parameters. If the logical host name is not specified in the jpqdbcond command, the system assumes the logical host name specified in the JP1_HOSTNAME environment variable. If the JP1_HOSTNAME environment variable is specified, check whether the specified host name is correct.

KAVU5930-E
Memory could not be allocated.

The system failed to allocate memory.

(S)

Cancels command execution.

(O)

Terminate any other unnecessary applications, and then re-execute. If the same message reappears, re-estimate memory.

KAVU5931-E
The disk is full.

The amount of free space in the disk is insufficient.

(S)

Cancels command execution.

(O)

Increase the free space in the disk, and then re-execute.

KAVU5932-E
A system call error occurred. (reason code:reason-code)

A system call error occurred.

(S)

Cancels command execution.

(O)

Also check the integrated trace log for the KAVU5501-E message.

Check the cause of the error, remove the error, and then retry the operation.

If you cannot identify the cause, use the data collection tool on the manager host to collect data, and then contact the system administrator.

KAVU5933-E
A logical contradiction occurred. (reason code:reason-code)

A logical contradiction occurred.

(S)

Cancels command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU5934-E
It is short of the system resources.

System resources became insufficient.

(S)

Cancels command execution.

(O)

Also check the integrated trace log for the message KAVU5501-E.

In a UNIX environment, check the value specified in the kernel parameter.

For information about how to estimate the kernel parameter, see Release Notes.

KAVU5935-E
A disk difficulty occurred.

An input or output error occurred on the disk.

(S)

Cancels command execution.

(O)

Check whether there is no problem on the disk volume itself.

KAVU5936-E
The database table is locked.

Another program locks the database table.

(S)

Cancels command execution.

(O)

Check whether the backup program or another program is accessing the JP1/AJS3 file or directory.

If the integrated trace log contains the KAVU5501-E message, also read the suggested corrective action.

KAVU5937-E
The database version is invalid.

The version of the database is invalid.

(S)

Cancels command execution.

(O)

Make sure that a database is correctly created. Then, re-execute the command.

KAVU5938-E
Condense failed.

Reorganizing the job execution environment database abnormally terminated.

(S)

Cancels command execution.

(O)

Use the integrated trace information log to determine the cause of the error and correct it. Then, re-execute the command.

KAVU5939-E
This version does not support the request so the request cannot be processed.

The request cannot be processed using the current JP1/Base version.

(S)

Cancels command execution.

(O)

Check the supported version of JP1/Base, and upgrade the version.

KAVU5940-E
The database file size is larger than the limit, so processing cannot be performed.

The request was not processed because the size of the job execution environment database exceeded the limit on ISAM file size.

(S)

Cancels the requested processing.

(O)

The probable cause of the error is that a file equal to or greater than 2 gigabytes, which is the limit on ISAM file size, exists in the job execution environment.

Recheck the estimated number of days for job information storage and re-create the job execution environment database.

For details on the number of days for job information storage, 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 on how to re-create a job execution environment database, see the explanation for creating a job execution environment in 2.3.3 Recovering the JP1/AJS3 - Manager setup information in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVU5941-E
The specified tablespace or RDAREA does not exist.

The table could not be created because the tablespace or RDAREA specified in the jpqimport command did not exist.

(S)

Cancels command execution.

(O)

Specify the correct tablespace or RDAREA as an argument of the jpqimport command, and then retry.

KAVU5942-E
The specified tablespace or RDAREA is invalid.

The table could not be created because the tablespace or RDAREA specified in the jpqimport command was invalid.

(S)

Cancels command execution.

(O)

Specify the correct tablespace or RDAREA for the argument of the jpqimport command, and then retry.

KAVU5943-E
Could not connect to the database because the upper limit of a server setting was exceeded.

The system could not connect to the database because the limit value defined on the database server was exceeded.

(S)

Cancels command execution.

(O)

Either stop other processes connected to the database or re-set the limit on the database, and then re-execute the command.

KAVU5944-E
Could not connect to the database because the username or password was invalid.

Connection to the database was not possible because an invalid user name or password was used.

(S)

Cancels command execution.

(O)

Specify the correct user name and password, and then re-execute the command.

KAVU5945-E
Could not connect to the database.

The system could not connect to the database.

(S)

Cancels command execution.

(O)

Check whether the database is running.

KAVU5948-E
A system call error occurred while checking the administrator permissions. (system call name:system-call-name,module:reason-location[reason-location],reason code:reason-code)

A system call error occurred when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is the value acquired by the GetLastError function of Win32API. If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU5949-E
Memory allocation failed while checking the administrator permissions. (size:size,module:reason-location[reason-location],reason code:reason-code)

Memory could not be secured when the jpqimport, jpqexport, or jpqdbcond command was used to check the administrator permissions.

(S)

Cancels the requested processing.

(O)

Stop unnecessary applications and issue another request.

If the same message is output again, review the memory estimate.

KAVU5950-E
The same identifier or object name is already specified. (line:line-number)

This message is output if the defined queue name, agent name, or exclusive execution resource name is duplicated or if a defined identifier (queue ID, agent ID, or exclusive execution resource name) is duplicated.

For these cases, the line number indicates the end of a definition block (where $end is coded).

(S)

Cancels command execution.

(O)

Check the definition information indicated by a line number in the configuration definition file in the submitted-job execution environment. Remove the cause of the error, and then re-execute the command.

KAVU5951-E
There is an invalid character in the object name. (line:line-number)

The object name includes an invalid character.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5952-E
The object name is too long. (line:line-number)

The length of the object name exceeds the maximum.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5953-E
The object number is specified incorrectly. (line:line-number)

This message appears if an invalid numeric value is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5954-E
Invalid time specification. (line:line-number)

An invalid time is specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5955-E
The concurrently-executable job limit is invalid. (line:line-number)

The maximum number of concurrently-executable job limit is incorrectly specified.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5956-E
No default queue is defined. (line:line-number)

In this message, line-number indicates the number of the last line of the definition block (that is, the line containing $end).

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5957-E
More than one default queue is defined. (line:line-number)

More than one default queue is defined.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5958-E
The connection to the agent is incorrect. (line:line-number)

The agent ID of the agent host that is connected to the default queue of the agent or the specification method for the order of priority is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5959-E
The maximum number of queuing jobs is specified incorrectly. (line:line-number)

The specified maximum number of jobs allowed in the queue is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5960-E
The warning number of queuing jobs is specified incorrectly. (line:line-number)

The specified warning value for number of jobs in the queue is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5961-E
The priority value is invalid. (line:line-number)

The priority value is invalid.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5962-E
A syntax error occurred. (line:line-number)

A syntax error occurred.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5963-E
An object number exceeds the number defined in the environment settings. (line:line-number)

The agent ID, queue ID, or exclusive-execution resource ID contains a value that exceeds the maximum number of definitions specified in the environment settings.

(S)

Cancels command execution.

(O)

Remove the cause of the error from the configuration definition information file for submit job execution, and then re-execute.

KAVU5970-E
The definition process for configuration definition ended abnormally.

The definition process for configuration definition for job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Investigate the cause of the error by also using the KAVU message that was output to the standard error output.

Remove the cause of the error, and then re-execute.

KAVU5971-E
The output process for configuration definition ended abnormally.

The output process for configuration definition for job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Investigate the cause of the error by also using the KAVU message that was output to the standard error output.

Remove the cause of the error, and then re-execute.

KAVU5980-I
Database condensing of the job execution environment started. start-date-and-time

The database reorganization of the job execution environment started.

(S)

Continues the database reorganization.

KAVU5981-I
Database condensing of the job execution environment ended normally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the job execution environment has normally terminated.

(S)

Normally terminates the database reorganization.

KAVU5982-E
Database condensing of the job execution environment ended abnormally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the job execution environment terminated abnormally.

(S)

Cancels command execution.

(O)

Check for the message KAVU5501-E in the integrated trace log. Use the integrated trace information log to check the cause of the error, correct the error, and then reorganize the ISAM file of the job execution environment.

KAVU5983-I
The ISAM unused area size on job execution environment is size-in-megabytes.

The size of the unused area of the ISAM file of the job execution environment is output.

(S)

Outputs the size of the unused area of the ISAM file.

KAVU5984-W
The ISAM unused area size of the job execution environment is size-in-megabytes, which exceeds the size-in-megabytes threshold value.

The size of the unused area of the ISAM file of the job execution environment reached the specified size for that area.

(S)

Continues command execution.

(O)

Reorganize the ISAM file of the job execution environment.

KAVU5986-W
The JP1 event could not be sent. (line:line, reason code:reason-code)

An unsuccessful attempt was made to send the JP1 event with the option specified.

(S)

Continues processing.

(O)

Check whether the system resources are sufficient and whether JP1/AJS3 is installed correctly. To send the JP1 event correctly, re-execute the command.

If the same message reappears, use the data collection tool to collect data, and then contact the system administrator.

KAVU6100-I
Job status notification process (host name:logical-host-name, port number:port-number) was started.

The job status notification process was started.

(S)

Starts the daemon.

KAVU6101-I
Job status notification process (host name:logical-host-name, port number:port-number) ended normally.

Job status notification process terminated normally.

(S)

Stops the daemon.

KAVU6102-E
Logical contradiction occurred (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because a logical contradiction occurred.

(S)

Stops starting the daemon.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU6103-E
Invalid environment settings (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because the environment settings have an error.

(S)

Stops starting the daemon.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then restart.

KAVU6104-E
Another process is using the specified port number (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

More than one process cannot use the same port number on the same logical host.

(S)

Stops starting the daemon.

(O)

Check whether another process is started with the specified port. If another process is using the specified port, change the port number and then restart.

KAVU6105-E
Specified port number is out of range. Could not start job status notification process (host name:logical-host-name, port number:port-number).

You can specify a port number from 1024 to 65535.

(S)

Stops starting the daemon.

(O)

Specify a correct port number, and then restart.

KAVU6106-E
Insufficient memory (reason code:reason-code). Could not start job status notification process (host name:logical-host-name, port number:port-number).

The system failed to start the status notification process because memory was insufficient.

(S)

Stops starting the daemon.

(O)

Terminate any other unnecessary applications, and restart. If the same message reappears, re-estimate memory.

KAVU6107-E
Job status notification process (host name:logical-host-name, port number:port-number) is already running on the same host. (reason code:reason-code)

You cannot start more than one daemon with the same port on the same logical host.

(S)

Stops starting the daemon.

(O)

Check whether a daemon is already started. If a daemon is already started, change the port number and then restart.

KAVU6108-E
Job status notification process (host name:logical-host-name, port number:port-number) ended abnormally. (reason code:reason-code)

The status notification process terminated abnormally. This message may also appear when the scheduler service stops or when the jajs_killall.cluster command is executed.

(S)

Stops the daemon.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then restart.

KAVU6109-E
Polling of job status notification process (host name:logical-host-name, port number:port-number) ended abnormally. (reason code:reason-code)

The polling for the status notification process terminated abnormally.

(S)

Stops the daemon.

(O)

Use the integrated trace information log to check the cause of the error, correct the error, and then restart.

KAVU6200-I
Polling for the job status notification process (host name : host-name, port number : port-number) was started.

The status notification process for job execution control started polling.

(S)

Continues processing.

KAVU6201-I
Polling for the job status notification process (host name : host-name, port number : port-number) ended normally.

Polling for the status notification process for job execution control terminated normally.

(S)

Continues processing.

KAVU6202-E
Data overflowed in the job status notification process(host name:logical-host-name, port number:port-number), so the job status notification from the manager (logical-host-name) is being ignored.

The system ignored the status notification from the manager because the number of registered status notifications reached the maximum.

(S)

Ignores the job status notification at this polling, and receives the latest status at the next polling.

(O)

If the JpqSetReport function is not issued, check the job status.

KAVU6203-E
The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) could not be restored because memory became insufficient.

The information on status notification could not be restored due to insufficient memory.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6204-E
The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) could not be restored.

The information on status notification could not be restored.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6205-E
The job status report information (manager descriptor=manager-name, job number=job-number, job status=job-status) was deleted because the job status report information was not acquired during the specified period.

The information on status notification was deleted because it could not be acquired within the specified period of time.

(S)

Loses the information on status notification of the job.

(O)

Set the polling monitoring of the job again.

KAVU6206-E
In the polling for the job status report process, a TCP/IP communication connection to the manager could not be made. (manager descriptor=manager-name, job number=job-number)

TCP/IP communication could not be connected to the manager during the polling for the status notification process.

(S)

Reports that the job has terminated.

(O)

If the manager has not started, starts it. Then, check the job status.

KAVU6207-E
In the polling for the job status report process, the manager's IP address could not be converted. (manager descriptor=manager-name, job number=job-number)

The IP address of the manager could not be converted during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Correct the error and check the job status.

KAVU6208-E
In the polling for the job status report process, the corresponding job did not exist. (manager descriptor=manager-name, job number=job-number)

The job is missing during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check whether the manager contains the job data and check the job status.

KAVU6209-E
In the polling for the job status report process, the specified queue or agent did not exist. (manager descriptor=manager-name, job number=job-number)

The queue or the agent is missing during the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check the queue or the agent and check the job status.

KAVU6210-E
In the polling for the job status report process, you lack operator permission. (manager descriptor=manager-name, job number=job-number)

You do not have operator permission for the polling for the status notification process.

(S)

Reports that the job terminates.

(O)

Check whether the user specified for setting the polling has permission to refer to the job data, and then check the job status.

KAVU6211-E
In the polling for the job status report process, an internal factor at the manager caused an error. (manager descriptor=manager-name, job number=job-number)

An error occurred during the polling for the status notification process due to an internal cause of the manager.

(S)

Reports that the job terminates.

(O)

Use the manager log to correct the error, and then check the job status.

KAVU6212-E
In the polling for the job status report process, an internal factor caused an error. (manager descriptor=manager-name, job number=job-number)

An error occurred during the polling for the status notification process due to an internal cause.

(S)

Reports that the job terminates.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU6213-W
The file cannot be created because there is no path to the file specified as the acquisition destination of the standard output or standard error output file. (manager descriptor=manager-name, job number=job-number)

The file cannot be created because there is no path to the file specified to acquire the standard output or standard error output file.

(S)

Acquired the job data.

(O)

Check the path, and then reissue the request.

KAVU6214-W
The file specified as the acquisition destination of the standard output or standard error output file could not be written. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be written into.

(S)

Acquired the job data.

(O)

Check the path, and then reissue the request.

KAVU6215-W
Insufficient disk space. The file specified as the acquisition destination of the standard output or standard error output file cannot be written. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be written into because there is an insufficient amount of disk space.

(S)

Acquired the job data.

(O)

Check the free space in the disk, and then reissue the request.

KAVU6216-W
The file cannot be opened because some other process is using the file specified as the acquisition destination of the standard output or standard error output file. (manager descriptor=manager-name, job number=job-number)

The file cannot be opened because another process is using the file specified to acquire the standard output or standard error output file.

(S)

Acquired the job data.

(O)

Remove the cause of the error, and then reissue the request.

KAVU6217-W
The file specified as the acquisition destination of the standard output or standard error output file cannot be created. (manager descriptor=manager-name, job number=job-number)

The file specified to acquire the standard output or standard error output file cannot be created.

(S)

Acquired the job data.

(O)

Remove the cause of the error, and then reissue the request.

KAVU6218-W
In the job status notification process, the job information was not acquired because the error occurred during TCP/IP communication. But the job might have ended normally. (manager descriptor=manager-name, job number=job-number)

When the status notification process confirmed the status of the job to the manager process, an error occurred during TCP/IP communication. This error prevented obtaining the job information.

(S)

Cancels the requested processing.

(O)

The job status displayed by JP1/AJS3 - View shows termination with error detection. However, the job may normally be terminated in the manager. Specify the job number in the message for the -j option, and execute the jpqjobget command to check the job information.

KAVU7110-E
System call error occurred in initializing log process.

A system error occurred while the system was initializing log output control.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the integrated trace log for the cause of the stoppage, remove the cause, and then restart the service or daemon. For a command, also retry the operation.

KAVU7111-E
Logical contradiction occurred in initializing log process.

A logical contradiction occurred while the system was initializing log output control.

(S)

Cancels daemon startup processing or command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7112-E
Environment setting parameter (environment-setting-parameter=environment-setting-parameter-value) on logical host (logical-host-name) is invalid. Value (value) is used.

The environment setting parameter on the logical host indicated by logical-host-name is invalid.

(S)

Continues daemon startup processing or command execution under an assumed value.

(O)

Correct the cause of the invalid data in the common definition information or insufficient definition. If the assumed value is different from the intended value, remove the cause of the error, and then restart the service or daemon. For a command, also retry the operation.

KAVU7113-E
An attempt to read the environment settings parameter (environment-setting-parameter) on the logical host (logical-host-name) has failed (reason-code). The value (value) will be assumed.

An attempt to read the environment setting parameter on the logical host indicated by logical-host-name has failed.

(S)

Continues daemon startup processing or command execution under an assumed value.

(O)

If the assumed value is different from an intended value, remove the cause of the error, and then restart the service or daemon. For a command, also retry the operation. The probable cause of the error is insufficient memory. Use the integrated trace log to check whether a log indicating insufficient memory was output at the same time the error occurred. If a log indicating insufficient memory was output, check the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, use the data collection tool to collect data, and then contact the system administrator.

KAVU7200-E
Memory could not be allocated. (size:size, module:reason-module[reason-module], reason code:reason-code)

The system failed to allocate memory.

(S)

Cancels daemon startup processing or command execution.

(O)

Stop unnecessary applications. For a service or a daemon, restart the service or daemon. For a command, retry the operation. If the same message reappears, re-estimate memory.

KAVU7220-E
Environment settings could not be read because logical host name (logical-host-name) is invalid.

The system failed to import the environment settings because the logical host name was invalid.

(S)

Cancels daemon startup processing or command execution.

(O)

Check for an invalid logical host name in the JP1_HOSTNAME environment variable, remove the cause, and then restart the service or daemon. For a command, also retry the operation.

KAVU7221-E
Environment setting parameter (parameter-name=parameter value) on logical host (logical-host-name) is invalid.

An invalid parameter is specified in the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor. For a service or a daemon, restart the service or daemon. For a command, retry the operation.

If this message appears while the definition is correct, memory may be insufficient. Use the integrated trace information log to check whether a log for insufficient memory has been output. If such a log has been output, re-estimate the memory. Also, stop any unnecessary applications that are running. Then restart the service or daemon, or for a command, retry the operation.

If parameter-name is ReportStatusPort=, an urgent command may have been executed on a host where JP1/AJS3 - Agent was installed. The urgent command cannot be executed on JP1/AJS3 - Agent.

If the parameter-name is TraceLogPath=, there is also a chance that write and read permissions have not been set for the OS user starting the command, service, or job for the path that was output. If this is the case, set write and read permissions, and re-execute the command, service, or job.

KAVU7222-E
A system error occurred while acquiring environment settings on logical host name (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred while the system was acquiring the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7223-E
A logical contradiction occurred while acquiring environment settings on logical host name (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred while the system was acquiring the environment settings of the logical host.

(S)

Cancels daemon startup processing or command execution.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7224-E
No physical host name can be acquired that corresponds to logical host name (logical-host-name).

The system cannot acquire the physical host name for the logical host name.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor, and then restart the service or daemon. For a command, also retry the operation.

This message also appears when the IP address of the logical host cannot be acquired.

Make sure that the network is set up using the hosts file or the DNS server so that the IP address can be obtained from the logical host name.

KAVU7225-E
An environment setting on the logical host (logical-host-name) is invalid, or memory became insufficient.

The logical host contains an invalid common definition or memory is insufficient.

(S)

Cancels daemon startup processing or command execution.

(O)

Remove anything invalid in the common definition information, check free memory in the system, and restart the service or daemon. For a command, also retry the operation.

KAVU7226-E
An environment setting parameter (JP1HOSTS) on the logical host (logical-host-name) is invalid.

The logical host contains an invalid jp1hosts definition.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the information in jp1hosts, and then restart the service or daemon. For a command, also retry the operation.

KAVU7227-E
Ineffective environment setting parameter (environment-setting-parameter=environment-setting-parameter-value) on logical host (logical-host-name) is specified.

The environment settings contain an invalid parameter.

(S)

Cancels daemon startup processing or command execution.

(O)

Check the common definition information, and then restart the service or the daemon. If this message was output when a command was being executed, re-execute the command.

In Solaris, specifying the IsLimitWorkSize parameter causes this error to occur.

If the OS is Solaris and environment-setting-parameter in the message is IsLimitWorkSize, review the common definition information and make sure that the IsLimitWorkSize parameter is not used.

KAVU7230-E
User mapping could not be initialized because logical host name (logical-host-name) is invalid.

The system failed to initialize user mapping because the logical host name was invalid.

(S)

Stops daemon startup processing.

(O)

Remove anything invalid in the common definition information or an insufficiently defined factor, and restart the service or daemon. If the problem persists, the limit for number of open files in a process might have been reached. Accordingly, make sure that the limit for number of open files in a process has not been reached, and restart the service or daemon.

KAVU7231-E
A system error occurred during the initialization of user mapping (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred while the system was initializing user mapping.

(S)

Cancels daemon startup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7232-E
A logical contradiction occurred during initialization of user mapping (logical-host-name). (module:reason-module[reason-module], reason code:reason-code)

A logical inconsistency occurred while initializing the user mapping.

(S)

Cancels starting the daemon.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7233-E
A Win32API error (Win32API-function-name) occurred during of get user account. (module:reason-module[reason-module], reason code:reason-code)

A Win32API error occurred when acquiring the account while the system was initializing user mapping.

(S)

Cancels daemon startup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7235-W
The user registered for assumed JP1 user is invalid. Assumed JP1 user was ignored.

An unsuccessful attempt was made to register the assumed JP1 user.

(S)

Disables the assumed JP1 user function, and continues startup of the service.

(O)

Use the jpregguestuser command to delete the assumed JP1 user, and restart the JP1/AJS3 service. To use the assumed JP1 user function, use the jpregguestuser command to register the assumed JP1 user correctly. Then, restart the JP1/AJS3 service.

KAVU7236-W
The port number for service (service-name) on logical host (logical-host-name) could not be acquired. Default value (port-number) is used.

The port number could not be obtained for the service of the specified logical host.

(S)

Uses the default port number to start the daemon or continue command execution.

(O)

Recheck the port number of the services file, and restart the service or the daemon.

KAVU7237-W
Environment setting parameter (environment-setting-parameter=value) on logical host (logical-host-name) is invalid. Value (value) is used.

An invalid parameter is specified in the environment settings of the logical host.

(S)

Assumes a value and continues processing.

(O)

Correct the error in the environment settings or in the definitions. If the assumed value is not an intended one, correct the error, and then reissue the request.

KAVU7238-E
A system call error occurred. (system call name : system-call-name, module : reason-location[reason-location], reason code : reason-code)

A system call error occurred.

(S)

Cancels the requested processing.

(O)

Determine the cause of the error from the system call name and the reason code.

The reason code is a system error number.

If the system call name is rename and the reason code indicates insufficient write and read permissions, set the write and read permissions for the user starting JP1/AJS3 on the work directory relevant to execution of the manager process in the job execution environment. Then, if necessary, restart.

If you cannot identify the cause of the error, use the data collection tool to collect data, and then contact the system administrator.

KAVU7240-E
A double start confirmation file (file-name) cannot be accessed.

The system cannot access the double start confirmation file.

(S)

Terminates the daemon or cancels executing the command.

(O)

Check the lock file .jpqmonlock, .jpqmanlock, or .jpqagtlock in the system file directory (/var/opt/jp1ajs2/sys).

For logical hosts, the file name must be .jpqmonlock.logical-host-name,.jpqmanlock.logical-host-name, or .jpqagtlock.logical-host-name.

If the system file directory or these files have been deleted, you must re-install JP1/AJS3. In addition, for logical hosts, you must set up the environment for a cluster again.

For details on how to set up the environment for a cluster, see 16.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU7242-E
The port number for service(service-name) on logical host(logical-host-name) could not be acquired.

The port number for a service on the specified logical host could not be acquired.

(S)

Cancels starting of the daemon.

(O)

Check the services file, set a port number, and restart the service or daemon.

KAVU7530-E
A logical contradiction occurred in the mapping process for JP1 user (user-name). (module:reason-module[reason-module], reason code:reason-code)

A logical contradiction occurred in the mapping process for the JP1 user.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7531-E
A system error occurred in the mapping process for JP1 user (user-name). (module:reason-module[reason-module], reason code:reason-code)

A system error occurred in the mapping process for the JP1 user.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU7532-E
JP1 user account (host name=logical-host-name, JP1 user name=user-name) could not be mapped.

The user mapping definition does not contain a JP1 user account of the user name.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition does not contain the OS user.

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

An OS user that has not been mapped is used to register a jobnet by the ajsentry command.

If the user mapping definition does not contain any error, memory may be insufficient. In this case, re-estimate memory.

KAVU7533-E
The execution user (user-name) mapped from JP1 user (host name=host-name, JP1 user name=user-name) is invalid. (reason code:reason-code)

An invalid execution user name is mapped.

(S)

Cancels the requested processing.

(O)

If the value indicated by reason-code is included in the list below, take the action appropriate for the reason code:

Windows

If reason-code is 1326
The access token for the OS user executing the job might not have been acquired. Note the following points:
- If the user who executes the job is a domain user, the status of the domain controller might be the cause of the error. For a user account to be referenced, the domain user must be able to log on. However, because JP1/AJS3 does not take into account the number and status of domain controllers, use care when restarting a domain controller during the execution of a job.
- Acquisition of the access token might not be possible due to a temporary error in a Win32 API function. For details, see 5.3.1 User account for job execution in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

If reason-code is 1330
When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the user password has expired.

If reason-code is 1792
When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the NetLogon service is running.

UNIX

If reason-code is 0
If an OS user was being registered or updated by using the passwd command or another command during execution of the job, re-exeucte the job after the registration or updating has been completed.

If reason-code is other than the above, inappropriate OS users might have been registered in the user mapping definition.

Check the following points, and if any applies, register an appropriate OS user.

Whether a non-existent OS user has been registered

Whether an invalid password has been registered for an OS user

Whether an OS user with an invalid account has been registered

Whether an OS user who does not have permission to log on has been registered

If the user mapping definition has no errors, memory might have become insufficient. If so, review memory estimates.

If the OS is Windows, you can reduce the frequency of this error by reusing an access token during job execution. For details on how to enable reuse of an access token during job execution, see 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVU7534-E
JP1 user account (host name=logical-host-name, JP1 user name=user-name) does not correspond to execution user name (user-name).

The JP1 user account does not correspond to the execution user name.

(S)

Cancels the requested processing.

(O)

The user mapping definition may contain an error. Check the following:

The user mapping definition contains an OS user that does not exist.

The user mapping definition contains the OS user with an invalid password.

KAVU7535-E
Win32API error (Win32API-function-name) occurred during of check Administrator account. (module:reason-module[reason-module], reason code:reason-code)

A Win32API error occurred when checking administrator permission while the system was performing the JP1 user mapping process.

(S)

Cancels the requested processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8901-E
An attempt to obtain a list of scheduler services failed. (module:reason-location[reason-location], reason code:reason-code)

While environment setting parameters for job execution control were being migrated during JP1/AJS3 setup processing by the jajs_migrate command, an attempt to obtain the list of scheduler services failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8904-I
Processing of migrating the environment setting parameters of job execution control started.

Processing to migrate the environment setting parameters for job execution control has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8905-E
Processing of migrating the environment setting parameters of job execution control ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

Processing to migrate the environment setting parameters for job execution control has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Take corrective action according to the message that was output immediately before this message, and then re-execute the jajs_migrate command.

KAVU8906-E
An attempt to register the environment setting parameters of job execution control failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to register the environment setting parameters for job execution control that were being migrated failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8907-I
Processing of migrating the environment setting parameters of job execution control ended normally.

Processing to migrate the environment setting parameters for job execution control has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8908-I
Job information delete process started.

Processing to delete the job information has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8909-E
Could not change the current directory. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to change the work directory during processing to delete job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

The work directory referred to here is the work directory used when the manager process in the job execution environment is executed. Check whether the directory specified in the WorkPath environment setting parameter in the definition key [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] exists.

The defaults are as follows:

For Windows Server 2008

When a physical host is used
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

When a logical host is used
shared-folder\jp1ajs2\tmp

For Windows Server 2003

When a physical host is used
JP1/AJS3 - Manager-installation-folder\tmp

When a logical host is used
shared-folder\jp1ajs2\tmp

For UNIX

When a physical host is used
/var/opt/jp1ajs2/tmp

When a logical host is used
shared-directory/jp1ajs2/tmp

If the work directory is missing, create a new one and re-execute the jajs_migrate command. If the work directory exists, use the data collection tool to collect data, and then contact the system administrator.

KAVU8910-E
An attempt to output the job execution environment files failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to output the job execution environment files during processing to delete the job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Make sure that the JP1/AJS3 service has stopped. If the JP1/AJS3 service is running, stop it, and then re-execute the jajs_migrate command. If the JP1/AJS3 service has stopped, use the data collection tool to collect data, and then contact the system administrator.

KAVU8911-E
An attempt to obtain the path for the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to acquire the path to the database in the job execution environment during processing to delete the job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8912-E
An attempt to delete the folder that contains the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to delete the folder containing the database in the job execution environment during the deletion of job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8913-E
An attempt to re-create the job execution environment database failed. (module:reason-location[reason-location], reason code:reason-code)

During JP1/AJS3 setup processing by the jajs_migrate command, an attempt to re-create a database in the job execution environment during the deletion of job information failed.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

KAVU8914-I
The job information delete processing ended normally.

The processing to delete the job information has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8915-E
The job information delete processing ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

The processing to delete the job information has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Take corrective action according to the message that was output immediately before this message, and then re-execute the jajs_migrate command.

KAVU8916-I
Processing of analyzing the job execution environment database started.

Analysis of the database in the job execution environment has started. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8917-I
Processing of analyzing the job execution environment database ended normally.

Analysis of the database in the job execution environment has terminated normally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Continues the JP1/AJS3 setup processing.

KAVU8918-E
Processing of analyzing the job execution environment database ended abnormally. (module:reason-location[reason-location], reason code:reason-code)

Analysis of the database in the job execution environment has terminated abnormally. This processing is actually part of the JP1/AJS3 setup processing performed by the jajs_migrate command.

(S)

Cancels the JP1/AJS3 setup processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

[Contents][Back][Next]

[Trademarks]