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

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

1.4 Messages beginning with KNAC (Messages that are output by communication control and agent management)

This section lists messages that begin with KNAC (messages output by communication control and agent management).

Organization of this section
(1) KNAC0001 to KNAC0999
(2) KNAC1001 to KNAC1999

(1) KNAC0001 to KNAC0999

The messages that are output by communication control are explained below.

KNAC0001-I

Network service started. (host-name)

The communication control function has started.

(S)
Continues processing.

KNAC0002-I

Network service ended. (host-name)

The communication control function has terminated.

(S)
Terminates the communication control function.

KNAC0003-E

An attempt to start the network service failed. (host-name) : maintenance-information-1 maintenance-information-2 maintenance-information-3

Startup of the communication control function has failed. You will not be able to receive notifications about job execution and job termination during agent execution.

(S)
Terminates the communication control function.

(O)
Check the following, and then restart the JP1/AJS3 service:
  • Whether system resources are sufficient
  • Whether the user who started JP1/AJS3 has superuser privileges or has logged as a member of the Administrators group
  • Whether the maximum number of processes that can be started in the entire system is temporarily exceeded
  • Whether the host name has been resolved
    If the host name has not been resolved, check the hosts file, DNS server settings, and jp1hosts definition file.

KNAC0005-E

Memory became insufficient. : maintenance-information-1 maintenance-information-2 maintenance-information-3

A memory shortage has occurred.

(S)
Cancels processing.
The system cancels the communication control function if it detects a memory shortage while memory is being secured for the basic part, for which processing cannot be continued.

(O)
See Release Notes, and check whether the required amount of memory has been allocated.
If the the required amount of memory has been allocated, stop other unnecessary applications, and then re-execute the processing during which the memory shortage occurred. If the same message is output again, revise the memory estimate.

KNAC0006-E

Unexpected error occurred during communication control processing.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An unexpected error occurred during communication control processing.

(S)
Continues processing.

(O)
Collect data, and contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC0007-E

Invalid communication control environment settings file: maintenance-information-1 maintenance-information-2 maintenance-information-3

The environment settings file for communication control is invalid.

(S)
Ignores the invalid setting, and continues processing.

(O)
Check the services file and specify the correct service name and port number, and then restart the JP1/AJS3 service. For details about the ports used for JP1/AJS3, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
If the problem persists, collect data, and contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC0011-E

System resources became insufficient during communication.

A system resource shortage has occurred during communication processing.

(S)
Interrupts the current processing.

KNAC0013-W

Thread for communication abnormally ended, and then restarted.: maintenance-information-1 maintenance-information-2 maintenance-information-3

A restart occurred because the communication thread terminated abnormally.

(S)
Continues processing.

KNAC0014-E

The port can't change to the reception state.: port_number=port-number maintenance-information-1 maintenance-information-2

The port number specified in the environment settings file for communication control cannot be changed to the receive state.

(S)
Continues processing.

(O)
Check whether the port specified in the services file is being used by another program. If it is being used by another program, terminate the program, and then restart the JP1/AJS3 service.
For details about the ports used for JP1/AJS3, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KNAC0401-W

Received data is invalid. (maintenance-information-1,maintenance-information-2)

Invalid data has been received.

(S)
Ignores the data, and continues processing.

(O)
Check whether the port name or port number defined in the environment settings file for communication control is correct.

KNAC0601-E

An error occurred during TCP/IP communication process-name(connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)
Cancels the requested processing.

(O)

When the process-name is connect or accept:
Check the following probable causes:
  • JP1/AJS3 was not running.
  • The port numbers used on the manager and the job execution host when a job was submitted did not match.
  • The default gateway was changed while JP1/AJS3 was running.
  • The IP address of the manager on the logical host and the IP address of the agent belong to different networks.
  • There was a problem with the network (includes the hardware).
  • The number of socket ports that can be used in the entire system was insufficient.
  • A memory shortage occurred.
  • In a cluster configuration, the logical IP address is released faster than JP1/AJS3 stops in the failover settings.
Take corrective action for above causes as described below, and then issue the request again.
  • Start JP1/AJS3.
  • Before changing the network configuration, you must stop the JP1/AJS3 service.
  • Review the network settings, including the hardware settings. For example, execute the ping command to check whether communication is possible.
  • Check the socket status, and wait until there are fewer TIME_WAIT sockets. You can also suppress communication errors by increasing the recovery time for the TIME_WAIT port managed by the OS.
  • Check the memory status and re-estimate the memory requirement.
  • The settings need to be specified so that the logical IP address is released later than JP1/AJS3 stops.

When the process-name is send or recv:
The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0602-E

Processing timed out during TCP/IP communication process-name(connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)
Cancels the requested processing.

(O)

When the process-name is connect or accept:
The status of the destination host might be as described below.
Check the host status, remove the cause of the error, and then issue the request again.
  • If JP1/AJS3 at the connection destination is not running, start it.
  • If the default gateway was changed while JP1/AJS3 was running, stop the JP1/AJS3 service before execution starts.
  • The IP address of the manager on the logical host and the IP address of the agent must belong to the same network.
  • Review the network settings to determine whether there is a problem with the network (includes the hardware). For example, execute the ping command to check whether communication is possible.
  • In a cluster configuration, if the logical IP address is released earlier than JP1/AJS3 stops in the failover settings, change the settings so that the logical IP address is released later than JP1/AJS3 stops.
  • Be careful that the values for timeouts, number of retries, and retry interval for communication connections are not too small. Values that are too small will reduce the retry interval for communication, making it difficult to avoid communication faults that could result in frequent errors of the types described.

When the process-name is send or recv:
The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0603-E

Processing retried out during TCP/IP communication process-name(connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)
Cancels the requested processing.

(O)

When the process-name is connect or accept:
Check the following probable causes:
  • The destination JP1/AJS3 was not running.
  • The default gateway was changed while JP1/AJS3 was running.
  • The IP address of the manager on the logical host and the IP address of the agent belong to different networks.
  • There was a problem with the network (includes the hardware).
  • The number of socket ports that can be used in the entire system is insufficient.
  • A memory shortage occurred.
  • In a cluster configuration, the logical IP address is released faster than JP1/AJS3 stops in the failover settings.
Take corrective action for above causes as described below, and then issue the request again.
  • Start JP1/AJS3.
  • Before changing the network configuration, you must stop the JP1/AJS3 service.
  • The same network must be used.
  • Review the network settings, including the hardware settings. For example, execute the ping command to check whether communication is possible.
  • Check the socket status, and wait until there are fewer TIME_WAIT sockets. You can also suppress communication errors by increasing the recovery time for the TIME_WAIT port managed by the OS.
  • Check the memory status, and re-estimate the memory requirement.
  • The settings need to be specified so that the logical IP address is released later than JP1/AJS3 stops.

When the process-name is send or recv:
The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.

KNAC0604-W

An error (content-of-error) occurred during TCP/IP communication process-name, and the processing will be retried (connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

A retry occurred because of a TCP/IP communication error.

(S)
Retries TCP/IP communication (process-name).

(O)
If the system error number is 00002740, note that 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.

KNAC0605-E

The local host name could not be obtained in the TCP/IP communication process-name(connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)
Retries the request acceptance processing, if the processing was request acceptance processing.

(O)
For request acceptance processing, the name service might have caused a problem. Check the status of the local host, remove the cause of the error, and then issue the request again.

KNAC0606-E

The socket could not be opened because the processing has too many open files (connection destination host name: destination-host-name, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)
Retries the request acceptance processing, if the processing was request acceptance processing.
Cancels request processing, if the processing was request processing.

(O)
Increase the maximum number (set in the kernel parameter) of files that can be opened.
For information about how to estimate the kernel parameter, also see Release Notes.

(2) KNAC1001 to KNAC1999

The messages that are output by agent management are explained below.

KNAC1001-I

The agent manager function started (host-name).

The agent management function has been started.

(S)
Continues processing.

KNAC1002-I

The agent manager function ended (host-name).

The agent management function has been terminated.

(S)
Terminates the agent management function.

KNAC1003-E

An error occurred during start processing of the agent manager function.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

Startup of the agent management function has failed.

(S)
Terminates the agent management function.

(O)
Take corrective action according to a previously output message.
If no such message was output, collect data and contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1100-I

The command ended normally.

The command has terminated normally.

(S)
Continues processing.

KNAC1101-I

The output of the agent manager information started.

(S)
Continues processing.

KNAC1102-I

The output of the agent manager information ended.

(S)
Continues processing.

KNAC1111-E

The exec-agent already exists.

The name of an agent that has already been registered was specified in the ajsagtadd command.

(S)
Terminates command processing.

(O)
Check the name that has already been registered, specify a different agent name, and then retry the operation.

KNAC1112-E

The exec-agent-group already exists.

The name of an agent group that has already been registered was specified in the ajsagtadd command.

(S)
Terminates command processing.

(O)
Check the agent group name that has already been registered, specify a different agent name, and then retry the operation.

KNAC1113-E

The exec-agent does not exist.

The name of an unregistered agent was specified.

(S)
Terminates command processing.

(O)
Use the name of a registered agent, and then retry the operation.

KNAC1114-E

The exec-agent-group does not exist.

The name of an unregistered agent group was specified.

(S)
Terminates command processing.

(O)
Use the name of a registered agent group, and then retry the operation.

KNAC1115-E

The exec-agent is already connected.

An attempt was made to associate an already associated execution agent with the execution agent group.

(S)
Terminates command processing.

(O)
Check the agent definition information, and then retry the operation.

KNAC1116-E

The status of delivery-limitation is not blocked.

The status of delivery-limitation for the execution agent or execution agent group that is to be deleted is not shutdown.

(S)
Terminates command processing.

(O)
Change the status of delivery-limitation for the execution agent or execution agent group that is to be deleted to shutdown, and then retry the operation.

KNAC1117-E

Cannot execute because some job is being executed.

Command processing cannot be executed because there is a job whose status is running or queuing.

(S)
Terminates command processing.

(O)
Check the job status, and then retry the operation.

KNAC1118-E

Host name cannot be resolved.

Probable causes are:

  • The logical host name specified in the -h option or the JP1_HOSTNAME environment variable could not be resolved.
  • An attempt to connect to the authentication server failed.

(S)
Terminates command processing.

(O)
If the -h option or the JP1_HOSTNAME environment variable contains a logical host name, review the specified value and check the hosts file and other settings. Then re-execute the command.
If the authentication server is not running, start JP1/Base.

KNAC1119-E

The agent manager function has stopped and the processing cannot be executed.

Probable causes are:

  • The logical host name contains an error.
  • Execution is not possible because the agent management function has stopped.

(S)
Terminates command processing.

(O)
Make sure that the logical host name specified in the -h option or the JP1_HOSTNAME environment variable is identical to the created logical host name, including the use of upper case and lower case, and then re-execute the operation.
If the JP1/AJS3 service is not running, start that service and then re-execute the command.

KNAC1120-E

Cannot delete - the exec-agent is connected to the exec-agent-group.:maintenance-information

The execution agent specified in the -a option in the ajsagtdel command cannot be deleted because it is already connected as the connection-destination execution agent to the execution agent group.

(S)
Terminates command processing.

(O)
Use the ajsagtshow command to check which execution agent group is connected to the connection-destination execution agent. Next, use the ajsagtalt command to exclude the corresponding execution agent that is to be deleted from the execution agent group identified by using the ajsagtshow command, and then retry the operation.

KNAC1121-E

An attempt to connect to the host failed.

An attempt to connect to the host failed.

(S)
Terminates command processing.

(O)
Verify that the host exists, and then retry the operation.

KNAC1122-E

The settings of the agent definition information file (agent-definition-file-name) are invalid (line: line-number, item: item-name).

The agent definition contains an error.

(S)
Terminates command processing.

(O)
Check the definition information on the indicated line (line-number) in the agent definition file, correct the error, and re-execute the command.
line-number indicates the line in the agent definition file causing the error and item-name indicates the item causing the error.
The character strings indicated by item-name and their meanings are as follows:
  • FLAG: Flag
  • AGENT: Name of the execution agent
  • AGENT GROUP: Name of the execution agent group
  • STATUS: Status of delivery-limitation
  • HOST: Name of the target host
  • CON-EXE: Maximum number of concurrently executable jobs
  • LINKAGENT: Name of the execution agent group to be grouped
  • DESCRIPTION: Description
  • *: Items could not be analyzed.

KNAC1123-E

No execution permissions for this command.

The user attempting to execute the command does not have the required permissions for the command operation.

(S)
Cancels command execution.

(O)
Check the following:
  • Whether the OS user executing the command has been registered as a JP1 user on the authentication server
  • Whether the JP1 permission level required to execute the command has been set for the JP1 resource group (JP1_Queue) of the JP1 user (OS user)

KNAC1124-E

The exec-agent cannot be added because the exec-agent already reached the number of definitions.

An execution agent cannot be added because the number of execution agent definitions has reached the limit.

(S)
Cancels command execution.

(O)
Delete an execution agent, and then retry the operation.

KNAC1125-E

The exec-agent-group cannot be added because the exec-agent-group already reached the number of definitions.

An execution agent group cannot be added because the number of execution agent group definitions has reached the limit.

(S)
Cancels command execution.

(O)
Delete an execution agent group, and then retry the operation.

KNAC1126-E

Valid definition does not exist in the specified agent definition information file.:file-name

Probable causes are:

  • The execution agent definition file specified in the -f option of the ajsagtadd command does not contain a valid definition.
  • A directory has been specified in the -f option of the ajsagtadd command.

(S)
Cancels command execution.

(O)
Write the agent definition file correctly, and then re-execute the command. Alternatively, specify the correct file name for the agent definition file, and then re-execute the command.

KNAC1127-E

The number of exec-agent for the connection destination exceeds the limit.:maintenance-information

When the ajsagtadd command was executed to add an execution agent group, the number of connection-destination execution agents specified in the -l option reached the limit for execution agents that can be defined.

(S)
Cancels command execution.

(O)
Review the number of connection-destination execution agents at specified in the -l option of the ajsagtadd command, and then re-execute the command.

KNAC1128-E

The concurrently-executable job limit is invalid.: specified-value

There is a problem with the time period specified in the -c option of the ajsagtadd or ajsagtalt command or with the specification of the maximum number of concurrently executable jobs.

(S)
Cancels command execution.

(O)
Review the element indicated by specified-value, and then re-execute the command.
The maximum number of concurrently executable jobs is specified in time-time=maximum-number-of-concurrently-executable-jobs format, in which the two elements of the time period are specified joined by a hyphen (-). These elements are hours and minutes at 30-minute intervals in hh:mm format.
The values for hh are 0 or a value from 00 to 23.
The values for mm are 0, 00, and 30.
The range of values that can be specified for the maximum number of concurrently executable jobs is from 0 to 4,294,967,295.

KNAC1129-E

The same exec-agent name cannot be specified more than one time.: overlapping-exec-agent-name

The -l option of the ajsagtadd command contains multiple connection-destination execution agents that have the same name.

(S)
Cancels command execution.

(O)
Remove the duplication, and then re-execute the command.

KNAC1130-E

The specified exec-agent for the connection destination does not exist.: exec-agent-name

No connection-destination execution agent is specified in the -l option of the ajsagtadd command or the -l, -m, or -u option of the ajsagtalt command.

(S)
Cancels command execution.

(O)
Use the ajsagtshow or ajsagtprint command to check existing execution agent names, specify the correct execution agent names, and then re-execute the command.

KNAC1131-E

The specified exec-agent is not connected.

The connection-destination execution agent specified in the -m or -u option of the ajsagtalt command has not been connected to the execution agent group specified in the -g option.

(S)
Cancels command execution.

(O)
Use the ajsagtshow or ajsagtprint command to check the name of the execution agent that is connected to the execution agent group, specify the correct execution agent name, and then re-execute the command.

KNAC1500-E

Memory became insufficient.: maintenance-information-1 maintenance-information-2 maintenance-information-3

A memory shortage has occurred.

(S)
Cancels processing.
The system cancels the agent management function if it detects a memory shortage while memory is being secured for the basic part, in which processing cannot be continued.

(O)
Check whether memory use has reached or exceeded the estimated value by examining the status of the process that was running when the problem occurred. Later, if necessary, re-execute the processing in progress when the memory shortage occurred.

KNAC1501-E

An unexpected error occurred during agent management processing.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An unexpected error occurred during agent management processing.

(S)
Continues processing.

(O)
Collect data, and then contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1503-E

Not enough space in file system for agent management.

There is not enough area in the file system used for agent management.

(S)
Interrupts the current processing.

KNAC1504-E

System resources became insufficient during agent management processing.

A system resource shortage has occurred during agent management processing.

(S)
Interrupts the current processing.

KNAC1505-E

The number of files being processed exceeded the system limit during agent management processing.

The number of files that can be processed exceeded the limit for the system during agent management processing.

(S)
Interrupts the current processing.

KNAC1506-E

Shared memory is invalid. The exec-agent information cannot be obtained. maintenance-information-1 maintenance-information-2 maintenance-information-3

The agent information cannot be acquired because shared memory is invalid.

(S)
Cancels the requested processing.

(O)
Restart the JP1/AJS3 service.

KNAC1507-E

A system call error occurred. maintenance-information-1 maintenance-information-2 maintenance-information-3

A system call error occurred.

(S)
Cancels the requested processing.

(O)
Take corrective action for the causes as described below, and then issue the request again.
  • System call name: ftok
  • Reason code: 2 (ENOENT)
    The file used for status monitoring management was not found.
    Check whether the JP1/AJS3 service is running on the specified host while the status monitoring function is enabled.
  • System call name: shmget
  • Reason code: 22 (ENOENT)
    There is no shared memory.
    Check whether the JP1/AJS3 service is running on the specified host while the status monitoring function is enabled.
  • System call name: shmget
  • Reason code: 12 (ENOMEM)
    There is a memory shortage.
    Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the memory estimate.
  • System call name: shmget
  • Reason code: 17 (EEXIST)
    Shared memory exists.
    Check the integrated trace log for whether the KAVU7239-W message was output before or after this message. If the message was output, read the message explanation to determine the cause of the error, remove the cause, and then restart the JP1/AJS3 service.
  • System call name: shmget
  • Reason code: 22 (EINVAL)
    Shared memory exists.
    Check the integrated trace log for whether the KAVU7239-W message was output before or after this message. If the message was output, read the message explanation to determine the cause of the error, remove the cause, and then restart the JP1/AJS3 service.
  • System call name: open
  • Reason code: 12 (ENOMEM)
    There is a memory shortage.
    Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the memory estimate.
  • System call name: open
  • Reason code: 23 (ENFILE)
    The total number of files that can be opened has reached the system limit.
    Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the number-of-files estimate.
  • System call name: open
  • Reason code: 24 (EMFILE)
    The number of files that the process has opened has reached the maximum value.
    Stop unnecessary applications, and then start the JP1/AJS3 service. If the same message is output again, correct the number-of-files estimate.

KNAC1508-E

An error occurred while accessing the database.: maintenance-information-1 maintenance-information-2

An error occurred while the database was being accessed.

(S)
Cancels processing.

(O)
Take corrective action according to a previously output message.
If a message was not output previously, collect data and then contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1509-E

An error occurred in a job execution control.: maintenance-information-1 maintenance-information-2

An error occurred in job execution control.

(S)
Cancels processing.

(O)
Take corrective action according to a previously output message.
If a message was not output previously, collect data and then contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1510-E

An error occurred in an event action control.: maintenance-information-1 maintenance-information-2

An error occurred in event action control.

(S)
Cancels processing.

(O)
Take corrective action according to a previously output message.
If a message was not output previously, collect data and then contact the system administrator.
For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KNAC1511-E

An attempt to connect to the database failed.

An attempt to connect to the database failed.

(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

KNAC1512-E

Database type is invalid.

The type of the database is not an embedded database.

(S)
Terminates processing.

(O)
The operation is not possible in the environment for the compatible ISAM configuration. Change the environment to the standard configuration, and then re-execute the command.

KNAC1513-E

An error occurred by the operation check in the event action control. :scheduler-service-name:maintenance-information

An error occurred during an operation check for event action control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVTxxxx message output previously, and then re-execute the command.

KNAC1514-E

An error occurred by the operation check in the job execution control. :scheduler-service-name:maintenance-information

An error occurred during an operation check for job execution control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVUxxxx message output previously, and then re-execute the command.

KNAC1515-E

An error occurred by the operation cancel report in the event action control.:scheduler-service-name:maintenance-information

An error occurred during a cancellation notification for event action control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. If the scheduler-service-name is an asterisk (*), restart the JP1/AJS3 service. After either restart, re-execute the command.

KNAC1516-E

An error occurred by the operation cancel report in the job execution control.:scheduler-service-name:maintenance-information

An error occurred during cancellation notification for job execution control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. After the restart, re-execute the command.

KNAC1517-E

An error occurred by the operation completion report in the event action control.:scheduler-service-name:maintenance-information

An error occurred during an execution completed notification for event action control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVTxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name. If the scheduler service name is an asterisk (*), restart the JP1/AJS3 service.
After the restart, use the ajsagtshow or ajsagtprint command to make sure that the intended result of the operation was reflected. If the intended result was not reflected, re-execute the command.

KNAC1518-E

An error occurred by the operation completion report in the job execution control.:scheduler-service-name:maintenance-information

An error occurred during an execution notification for job execution control for an agent management command.

(S)
Terminates processing.

(O)
Take corrective action according to the KAVUxxxx message output previously, and then restart the scheduler service indicated by scheduler-service-name.
After the restart, use the ajsagtshow or ajsagtprint command to make sure that the intended result of the operation was reflected. If the intended result was not reflected, re-execute the command.

[Contents][Back][Next]

[Trademarks]

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