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

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

2.3 Messages beginning with KAVT (Messages about the event/action control)

This section lists the messages that begin with KAVT (Messages about the event/action control).

KAVT0001-I

Event Action Manager will now start.

The event/action control manager starts.

(S)
Continues processing.

KAVT0002-I

Finish Event Action Manager.

The event/action control manager has terminated.

(S)
Terminates the event/action control manager.

KAVT0003-I

Event Action Manager has started.

The event/action control manager has started.

(S)
Continues processing

KAVT0008-E

Failed to initialize process. (maintenance-information)

The event/action control manager could not be started.

(S)
Terminates the event/action control manager.

(O)
Check the following and then restart JP1/AJS3:
  • Check whether JP1/Base is running.
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the contents of the environment settings are correct. In particular, check whether the name of the directory for output of the wait information file is set correctly.
    After correcting any errors, stop the JP1/AJS3 service and then restart it.

KAVT0009-E

Failed to initialize socket. (maintenance-information)

The event/action control manager could not be started.

(S)
Terminates the event/action control manager.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the JP1/AJS3 that has the same logical host name is running.
  • Check whether the host name is determined.
    If it is not determined, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.
  • Check whether the JP1/AJS3 port number is registered in the services file.
    If it is not registered, register it.

KAVT0020-E

A definition file name could not be created. (maintenance-information)

An attempt to create a configuration definition file name has failed in the event/action control manager.

(S)
Continues processing without changing the status of the jobnet with start conditions or the event job.

(O)
Check the length of the name of the directory for output of the wait information file that was specified when JP1/AJS3 was set up. The maximum length allowed is 160 bytes. Change the configuration definition information (environment setting) and then restart JP1/AJS3.

KAVT0023-E

An error occurred during processing of a request to monitor event icons. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while event job monitoring was starting.

(S)
Terminates the event job in the Failed to start status.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Retry operation on the identified event job:
  • Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk that contains the directory for output of the wait information file.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0025-E

The last registered contents cannot be recovered because the processing to recover consistency failed.

The system cannot resume the monitoring of the jobnet with start conditions or the event job that was being monitored when the event/action control manager was stopped last time.

(S)
Places the previously registered jobnet with start conditions in the Monitor terminated status or places the event job in the Unknown end status status, and then start the event/action control manager.

(O)
Check the following:
  • Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
Because the wait information file might have been corrupted, cold-start JP1/AJS3.

KAVT0026-I

The cold start processing will now start

A cold start will now start on the event/action control manager.

(S)
Continues processing.

KAVT0027-E

The cold start processing failed. (maintenance-information)

An attempt to perform a cold start on the event/action control manager has failed.

(S)
Starts the event/action control manager while some of the event jobs being monitored are still running.

(O)
Check the following, and then re-execute the cold start:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0034-E

An error occurred during processing of a request to kill an event icon. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during forced termination of an event job.

(S)
Cancels the forced termination of the event job. The event job is now monitoring an event.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:
  • Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0036-E

An error occurred during processing of a bypass request for an event icon. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during bypass processing of an event job.

(S)
Cancels forced termination of the event job. The event job is now monitoring an event.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0039-I

Terminating because of a bypass request.

Event monitoring will now terminate because a bypass request was accepted.

(S)
Continues processing.

KAVT0042-E

The standard error output file could not be output. (file=file-name) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An attempt to write to the standard error output file has failed during execution of an event job.

(S)
Continues processing without outputting an execution result details message to a file.

(O)
Make sure that the directory specified in the name of the directory for job error information in the configuration definition information (environment setting) exists. Then use the ajsname command with the -I option to identify the job name from the unit ID.

KAVT0043-I

The icon will now end because of a kill request.

Event monitoring will now terminate because a forced termination request was accepted.

(S)
Continues processing.

KAVT0045-E

The icon will now end because an error occurred.

An error occurred during the start of an event.

(S)
Continues processing.

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0058-E

An error occurred during processing of the request to monitor the start condition. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred immediately after monitoring of a jobnet with start conditions started.

(S)
Terminates the jobnet with start conditions.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Re-register the identified jobnet for execution:
  • Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk containing the directory for output of the wait information file.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0059-E

Past time is set as the stop time. (time=set-time) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The effective period specified for the start condition is earlier than the current time.

(S)
Terminates the jobnet with start conditions.

(O)
Specify an effective period for the start condition later than the current time, and then reregister it.

KAVT0062-E

An error occurred during processing of the request to end start-condition monitoring. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during the termination of monitoring the start condition.

(S)
Cancels the forced termination of the jobnet with start conditions, and continues processing.

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified jobnet with start conditions has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:
  • Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0082-E

An error occurred during processing of phenomena at an event icon end. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during generation of an event for an event job.

(S)
Continues processing without changing the status of the event job.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:
  • Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0084-E

The file for storing macro variables could not be output. (file=file-name) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Output to the macro variable storage file failed.

(S)
Continues processing.

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT0089-E

An error occurred during processing of the phenomena at the start of event-icon monitoring. (maintenance-information) (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while the agent was reporting the start of an event job.

(S)
Continues processing without monitoring the event job.

(O)
Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job:
  • Check whether the system resources are sufficient. Especially, check whether there was sufficient space on the disk containing the directory for output of the wait information file during JP1/AJS3 operation.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0092-E

An error occurred during processing of phenomena for the agent machine activation report. (maintenance-information, host=agent-host-name)

Although the agent host reported the startup, an error occurred during startup of the agent within the manager.

(S)
Continues processing without monitoring anything on the agent.

(O)
Check the following, and then restart JP1/AJS3 on the agent host:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the target host and JP1/AJS3 have started.

KAVT0094-E

The send source is invalid. (RequestPP=send-source) (maintenance-information)

Invalid data was received.

(S)
Discards the invalid data received, and continues processing.

(O)
Invalid data was detected in the port (jp1ajs2eamgr). The part may have been accessed incorrectly. Examine the cause of the trouble.

KAVT0098-E

An error occurred in the processing of the time-out period of the start condition. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred during processing of the timeout period for the jobnet with start conditions.

(S)
Does not stop the jobnet with start conditions even after the period of time specified as the valid range has elapsed. The jobnet with start conditions remains in the Now monitoring status.

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Terminate the identified jobnet with start conditions forcibly. If the jobnet cannot be terminated forcibly, an inconsistency has occurred in the management status of event jobs. Restart the manager and the agent on which the start condition is executed.
  • Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk containing the directory for output of the wait information file.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0099-I

The start conditions stopped because the time-out period elapsed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition terminated because the time-out period elapsed.

(S)
Continues processing.

KAVT0101-E

An error occurred during resending of unreported information. (maintenance-information) (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while re-sending the unreported information to the agent.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0103-E

Even with the specified number of retries, no messages could be sent. (file=unreported-information-file-name) (host=agent-host-name, maintenance-information)

Although the manager continued to retry establishing communication with an agent host for a certain period of time, transmission was not successful.

For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)
Deletes all communication data that has not been sent to the agent up to this time. As a result, the following symptoms might occur:
  • If an event job is registered for execution, the status of the job does not change from now queuing to now running.
  • If an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)
Check whether:
  • Check whether the agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • Check whether the JP1/AJS3 service on the agent host is running or whether the agent host machine itself is running.
    If JP1/AJS3 on the agent host and the agent host itself are not running, start them.
  • Check whether there are problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.
In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:
  • Check whether the status of an event job registered for execution has changed from now queuing to now running.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Ensure that no event has been detected within a certain period of time after the relevant message was output.
    Because data waiting to be returned remains on the agent, start the agent.
    Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected during a certain period of time after this message was output.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0106-I

The start condition stopped because the specified number was detected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition terminated because the system detected the satisfied start condition the specified number of times.

(S)
Continues processing.

KAVT0108-I

The start condition was satisfied. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

The start condition was satisfied.

(S)
Continues processing.

KAVT0110-E

An error occurred during resending of unreported information to scheduler service. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred while resending the unreported information to the scheduler service.

(S)
Continues processing without changing the status of the jobnet with start conditions.

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) was not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0116-E

Some information cannot be reported to scheduler service because the processing to recover consistency failed.

During startup of JP1/AJS3, the system failed to acquire information that could not be reported before termination of JP1/AJS3. As a result, some information cannot be reported to the scheduler service.

(S)
Aborts the information that could not be reported to the scheduler service last time, and starts the event/action control manager without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check the following and take appropriate action. If neither of the following conditions is met, contact the system administrator and collect data (see 1.2.3 To the system administrators).

Check the following:
  1. Check that the file in the output directory for the queued information has not been deleted.
  2. Check whether there is a unit (a jobnet with start conditions or an event job) whose status has not changed.

Take the following action:
  1. If the condition shown in check item 1 is met, perform a cold start.
  2. If the condition shown in check item 2 is met, check the unit (a jobnet with start conditions or an event job) whose status has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0118-E

The shared definition could not be read. (maintenance-information)

The shared definition information could not be read.

(S)
Assumes the default value and continues processing.
If processing cannot be continued, take action according to the message output after this message.

(O)
Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can collect it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0145-E

An error occurred during sending of start mode to an agent host. (host=host-name, mode=start-mode, maintenance-information)

An error occurred during sending of start mode to an agent host. Since the startup of the manager host could not be reported to the agent indicated by host-name, monitoring of the events on the agent may be unsuccessful.

(S)
Discards the data, allowing event monitoring on the agent host indicated in host-name to continue.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the network or agent machine has not stopped.
  • Check whether the host name is determined. If has not, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.

KAVT0147-E

An error occurred during the processing of an event for reporting the shutdown of an agent machine. (maintenance-information) (host=agent-host-name, maintenance-information)

An error occurred during the processing in response to the shutdown report from an agent host.

(S)
Continues processing without changing the status of the event job that is running on the agent.

(O)
Check the following, and then check the event job whose status has not changed. Then use the ajschgstat command or the Change Job Status dialog box or forced termination to change the status of the event job:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
  • Check whether the scheduler service has started.

KAVT0157-E

Start condition is cancelled due to failure in receiving new branch-execution ID within specified time interval. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID) (time=maintenance-information)

A branch-execution ID could not be obtained within the specified time interval. The start condition terminates.

(S)
Terminates the jobnet with start conditions in the Monitor terminated status.

(O)
Make sure that the scheduler service has started, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Re-register the jobnet with start conditions for execution.

KAVT0171-E

Connection of the sending pipe failed. (maintenance-information)

The sending pipe could not be connected.

(S)
Terminates the event/action control manager.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.
If the above conditions are not satisfied, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0178-E

An error occurred during child process creation. (maintenance-information) (maintenance-information)

An error occurred during creation of a child process.

(S)
Terminates the event/action control manager.

(O)
Check whether:
  • The system resources are sufficient.
  • The user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • The directory created during installation of JP1/AJS3 was deleted inadvertently.
If the above conditions are not satisfied, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0187-E

The process will now stop because Event Action SubManager is finished.

The process stops because the event/action control submanager has terminated.

(S)
Terminates the process.

(O)
Check whether the directory for output of the wait information file can be referenced.
Especially for a logical host, check whether the shared disk containing the directory for output of the wait information file was unmounted while JP1/AJS3 was running.
Then restart JP1/AJS3.

KAVT0193-W

The events that occurred during the maintenance mode are discarded because the option to improve event job reliability is invalid. (scheduler-service-name)

The reliability improvement option is invalid, so events occurring in maintenance mode are discarded.

(S)
Continues processing.
Discards events occurring in maintenance mode.

(O)
If no event occurs in maintenance mode, you to not need to take any actions. If an event occurs in maintenance mode, validate the reliability improvement option.

KAVT0194-W

Memory became insufficient during the maintenance mode start notification. (scheduler-service-name)

Memory became insufficient during the notification of maintenance mode activation. An error may occur when an activation condition event is detected in maintenance mode.

(S)
Keeps the maintenance mode.

(O)
See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT0247-E

The number of tokens from the send destination is invalid. (maintenance-information) (maintenance-information)

Information from the send destination is invalid.

(S)
Continues processing without changing the status of the jobnet with start conditions or the event job.

(O)
Check whether:
  • The system resources are sufficient.
  • The version of the manager matches that of the agent.
  • The LANG settings match between JP1/Base and JP1/AJS3.
  • A program other than JP1/AJS3 is using the port defined for jp1ajs2eamgr. Use the netstat command or another means to check this.

KAVT0250-W

Because the total of macro variables exceeded the maximum, part of the data was truncated.

The total number of macro variables exceeded the limit. A part of the data was truncated.

(S)
Inherits the macro variables with the part of data truncated.

(O)
Redefine the macro variables so that the sum of the size of the values specified in the macro variables does not exceed 4,096 bytes. In particular, if you define a jobnet with start conditions using AND, the macro variables for all of the event jobs defined in the jobnet with start conditions will be merged. Therefore, make sure that the total size of the values specified in merged macro variables does not exceed 4,096 bytes.

KAVT0261-E

The report to scheduler service failed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The data could not be sent to the scheduler service.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check whether the scheduler service has started. If it has started, the unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event.
Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then re-register the jobnet or job for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0268-W

The data arrival confirmation of a socket failed. (maintenance-information) (host=agent-host-name, maintenance-information)

An attempt to communicate with the agent indicated in agent-host-name has failed due to a temporary communication error. The start time of a jobnet with start conditions or an event job may be delayed.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
A communication error may have occurred due to one of the following reasons. For a jobnet with start conditions or an event job, no action is required because the data that caused the communication error will be resent automatically after the predefined period of time:
  • The network or the agent machine has stopped.
  • A temporary communication error occurred.
  • The event job attempted processing exceeding its throughput.
If a network error occurred, examine the cause of the error and correct it.
If the agent machine indicated in agent-host-name has stopped, restart it.
If a one-time communication error occurred due to heavily-loaded communications that are caused by too many event jobs being processed at once, ignore the message and continue the operation. However, if this message frequently appears, the throughput may be exceeded. See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and recheck the estimates for using event jobs.

KAVT0271-E

An attempt to get the IP address of the host (name-of-host-whose-IP-address-could-not-be-obtained) during the start notification from the agent (name-of-host-notifying-startup-from-agent) failed. (maintenance-information)

During startup of the agent host, an attempt to start a jobnet with start conditions or an event job for the agent started by the manager has failed.

(S)
A jobnet with start conditions or an event job that was being monitored on the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can no longer be monitored.

(O)
On the manager host, use the jp1ping command to check whether the IP address of the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can be obtained. For details on the jp1ping command, see the Job Management Partner 1/Base User's Guide.
If the IP address cannot be obtained, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the correct IP address can be obtained by name resolution. Next, forcibly terminate the relevant jobnet with start conditions or event job, and then re-execute it.

KAVT0272-E

An attempt to get the IP address of the host (name-of-host-whose-IP-address-could-not-be-obtained) during the stop notification from the agent (name-of-host-notifying-termination-from-agent) failed. (maintenance-information)

During termination of the agent host, an attempt to stop an event job for the agent started by the manager has failed.

(S)
The status of the event job being executed on the host indicated by name-of-host-whose-IP-address-could-not-be-obtained remains now running.

(O)
On the manager host, use the jp1ping command to check whether the IP address of the host indicated by name-of-host-whose-IP-address-could-not-be-obtained can be obtained. For details on the jp1ping command, see the Job Management Partner 1/Base User's Guide.
If the IP address cannot be obtained, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the correct IP address can be obtained by name resolution. Next, start the agent and forcibly terminate the relevant event job.

KAVT0273-W

Too many simultaneous events are generated for a jobnet with a start condition, so processing performance may be degraded. (jobnet-name) (host=agent-host-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Too many concurrently occurring events for the jobnet with starting conditions may lower processing performance.

(S)
Continues processing.

(O)
Use the ajsname command with the -I option to identify the unit name from the unit ID. Recheck the number of events that occur for the identified jobnet with start conditions, and then reduce the number of events.

KAVT0280-E

An attempt to get the IP address of the host (agent-host-name) during the starting of the manager failed. (maintenance-information)

During starting of the event/action control manager, an attempt to obtain the IP address of the agent host has failed.

(S)
Continues processing.

(O)
Check whether you can obtain the IP address associated with the agent host name. If you cannot obtain it, set the environment so that the IP address can be resolved by DNS or the hosts file.

KAVT0281-E

An error occurred, caused by an internal aspect of the event action function. Execution of the event job will result in an error. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

An error occurred due to an internal factor of the event/action control. Execution of the event job will result in an error.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).
The unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event. Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then re-register the jobnet or job for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0282-E

An error occurred, caused by an internal aspect of the event action function. (maintenance-information)

An error occurred due to an internal factor of the event/action control.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).
The unit (a jobnet with start conditions or an event job) may not have been registered, executed, or operated, or processing may not have been done in response to the event. Make sure that the status of the currently running unit (a jobnet with start conditions or an event job) has not changed. Then re-register the jobnet or job for execution, or use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0283-E

Memory is insufficient. (maintenance-information)

Memory was insufficient.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated. The unit (a jobnet with start conditions or an event job) may not have been registered, executed, or operated, or processing may not have been done in response to the event. Make sure that the status of the currently running unit (a jobnet with start conditions or an event job) has not changed. Then re-register the jobnet or job for execution, or use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0284-E

Memory is insufficient. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

Memory was insufficient.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated. The unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-service-name, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event. Use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then register the job or jobnet for execution. Alternatively, use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0285-I

An attempt to communicate with the agent has failed. (host=agent-host-name, maintenance-information)

An attempt to communicate with the agent has failed.

An attempt to communicate with the agent indicated in agent-host-name has failed due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0287-E

The files will be deleted, because the internal files of event action control have been destroyed. (maintenance-information)

The files will be deleted because the internal files of the event action control have been corrupted.

(S)
Continues processing.

(O)
Take appropriate action as shown below:
  1. When you use JP1/AJS3 in a manager-agent configuration, perform a cold start for JP1/AJS3 on the agent host.
  2. If this message was output during startup of JP1/AJS3, all jobnets with start conditions or event jobs being registered terminate abnormally. Re-register them for execution.
  3. If this message was output during operation, restart JP1/AJS3. Then, re-register the jobnet with start conditions or the event job for execution.

KAVT0293-W

An attempt to communicate with the agent has failed.(host=agent-host-name, maintenance-information)

An attempt to communicate with the agent indicated by host= agent-host-name has failed.

The start time of a jobnet with a start condition or an event job might be delayed.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
The cause of the communication error might be one of the following:
  • There is a network failure.
  • The agent machine or the JP1/AJS3 has stopped.
  • The IP address of agent-host-name cannot be acquired.
If there is a network failure, investigate the cause of the network failure and correct the cause.
If the agent machine indicated by host=agent-host-name or JP1/AJS3 has stopped, restart the agent machine or JP1/AJS3.
If the IP address of the agent host indicated by host=agent-host-name cannot be acquired, configure DNS and hosts so that the IP address is resolved, and restart JP1/AJS3.

KAVT0294-W

Unreported information for scheduler-service-name will now be deleted, because the total amount of unreported information for the scheduler service has exceeded threshold.

Unreported information for scheduler-service-name will be deleted because the total amount of unreported information for the scheduler service exceeded the value indicated in threshold.

(S)
Deletes unreported information for the scheduler service, beginning from the oldest item, each time the threshold is exceeded.

(O)
Check whether:
  • The scheduler service has started.
  • There is an event job whose status has not changed properly.
    If you find such an event job, change the job status or re-execute the job as required.

KAVT0295-W

Unreported information will now be deleted, because the amount of unreported information for scheduler-service-name has exceeded threshold.

Unreported information will be deleted because the amount of unreported information for scheduler-service-name exceeded the value indicated in threshold.

(S)
Deletes unreported information for the indicated scheduler service, beginning from the oldest item, each time the threshold is exceeded.

(O)
Check whether:
  • The scheduler service has started.
  • There is an event job whose status has not changed properly.
    If you find such an event job, change the job status or re-execute the job as required.

KAVT0296-W

Unreported information for agent-host-name will now be deleted, because the total amount of unreported information for the agent has exceeded threshold.

Unreported information for agent-host-name will be deleted because the total amount of unreported information for the agent exceeded the value indicated in threshold.

(S)
Deletes unreported information for the agent, beginning from the oldest item, each time the threshold is exceeded. This action might result in the following symptoms:
  • When an event job is registered for execution, the status of the job does not change from now queuing to now running.
  • When an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)
Check whether:
  • The agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • The IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • The JP1/AJS3 service on the agent host is running or the agent host machine itself is running.
    If JP1/AJS3 on the agent host and the agent host itself are not running, start them.
  • There are problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.
In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:
  • Check whether the status of an event job registered for execution has changed from now queuing to now running.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Ensure that no event has been detected within a certain period of time after the relevant message was output.
    Because data waiting to be returned remains on the agent, restart the agent.
    Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected within a few hours after the relevant message was output.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0297-W

Unreported information will now be deleted, because the amount of unreported information for agent-host-name has exceeded threshold.

Unreported information will be deleted because the amount of unreported information for the agent indicated in agent-host-name exceeded the value indicated in threshold.

(S)
Deletes unreported information for the indicated agent, beginning from the oldest item, each time the threshold is exceeded. This action might result in the following symptoms:
  • When an event job is registered for execution, the status of the job does not change from now queuing to now running.
  • When an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.

(O)
Check whether:
  • The agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • The IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • The JP1/AJS3 service on the agent host is running or the agent host machine itself is running.
    If JP1/AJS3 on the agent host and the agent host itself are not running, start them.
  • There are problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.
In addition to performing the actions described above, you might also need to perform the following additional actions, depending on the type of deleted communication data:
  • Check whether the status of an event job registered for execution has changed from now queuing to now running.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Check whether the now running status of an event job (including an event job defined in the start conditions) that has been forcibly terminated has changed.
    If there is no change, forcibly terminate the job, and then re-execute it.
  • Ensure that no event has been detected within a certain period of time after the relevant message was output.
    Because data waiting to be returned remains on the agent, restart the agent.
    Note that when the agent is restarted, it resends the remaining data to the manager. If the amount of the data is large, manager load might increase severely, succeeding jobs might have to wait a long time in the queue, or event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected within a few hours after the relevant message was output.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0301-I

Event Action SubManager will now start.

The event/action control submanager starts.

(S)
Continues processing.

KAVT0302-I

Event Action SubManager has started.

The event/action control submanager has started.

(S)
Continues processing.

KAVT0303-I

Event Action SubManager will now end.

The event/action control submanager terminates.

(S)
Continues processing.

KAVT0325-E

Event Action Manager has ended so the process will now stop.

The event/action control submanager will terminate because the event/action control manager has terminated.

(S)
Terminates the event/action control submanager.

(O)
Determine the cause of the termination of the event/action control submanager from the integrated trace log, and take corrective action. Then restart JP1/AJS3.

KAVT0328-E

The file read-in of list for repetition check failed. (maintenance-information)

An attempt to read an internal file used in the event/action control submanager has failed.

(S)
Terminates the event/action control submanager.

(O)
Check whether:
  • The system resources are sufficient.
  • The user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.

KAVT0332-W

The number of requests from the scheduler service exceeds threshold. Processing the requests from the scheduler service might be delayed.

The number of requests from the scheduler service exceeded the value indicated in threshold. Processing for the requests from the scheduler service might be delayed.

(S)
Continues processing.

(O)
Check the schedule. If a mass of event jobs or jobnets with start conditions are scheduled to be registered for execution at the same time, recheck the operation. For example, schedule the registration of jobs or jobnets at different times.

KAVT0333-W

The number of the reported events from agent-name exceeds threshold. Processing the events from agent-name might be delayed.

The number of events reported from the agent indicated in agent-name exceeded the value indicated in threshold. Processing for the events from the agent might be delayed.

(S)
Continues processing.

(O)
Check whether:
  • Check the definition of the event job or the jobnet with start conditions for which the agent is defined as the execution host. If the definition will cause a mass of events to be generated at the same time, recheck the operation to reduce the number of events to be generated.
  • If this message is output after JP1/AJS3 on the agent is restarted, do the following:
  • Check whether the agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • Check whether the JP1/AJS3 service on the agent host are running or whether the agent host machine itself is running.
    If JP1/AJS3 on the agent host and the agent host itself are not running, start them.
  • Check whether there are problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them.
#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0340-W

Communication to check the operation of the Event Action SubManager failed. The communication will be retried.(maintenance-information)

A communication error occurred during processing to periodically check whether the event/action control submanager is running.

The communication will be retried.

(S)
Continues processing.

(O)
Check the following:
  • Check whether a mass of events has been detected.
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.
  • Check whether any process is accessing a file in the JP1/AJS3 installation path.
  • Check whether memory is sufficient.
Correct the above problems, and then check whether the event jobs and start conditions work normally.
If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.
Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVT0341-W

Communication to check the operation of the Event Action Manager failed. The communication will be retried.(maintenance-information)

A communication error occurred during communication to periodically check whether the event/action control manager is running.

The communication will be retried.

(S)
Continues processing.

(O)
Check the following:
  • Check whether a mass of events has been detected.
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.
  • Check whether any process is accessing a file in the JP1/AJS3 installation path.
  • Check whether memory is sufficient.
Correct the above problems, and then check whether the event jobs and start conditions work normally.
If they do not work normally after a while, there might be a problem with the status monitoring of the event jobs and start conditions.
Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVT0342-I

Communication to check the operation of the Event Action SubManager has been restored.(maintenance-information)

Communication to check the operation of the event/action control submanager has been recovered.

(S)
Continues processing.

KAVT0343-I

Communication to check the operation of the Event Action Manager has been restored.(maintenance-information)

Communication to check the operation of the event/action control manager has been recovered.

(S)
Continues processing.

KAVT0344-W

There is no response from the Event Action SubManager.(maintenance-information)

No response has been sent from the event/action control submanager.

(S)
Continues processing.

(O)
Check the following:
  • Check whether a mass of events has been detected.
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.
  • Check whether any process is accessing a file in the JP1/AJS3 installation path.
  • Check whether memory is sufficient.
Correct the above problems, and then check whether the event jobs and start conditions work normally.
If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.
Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVT0345-W

There is no response from the Event Action Manager.(maintenance-information)

No response has been sent from the event/action control manager.

(S)
Continues processing.

(O)
Check the following:
  • Check whether a mass of events has been detected.
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.
  • Check whether any process is accessing a file in the JP1/AJS3 installation path.
  • Check whether memory is sufficient.
Correct the causes of the above problems, and then check whether the event jobs and start conditions work normally.
If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions.
Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command. For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVT0346-I

A response from the Event Action SubManager has been confirmed.(maintenance-information)

A response from the event/action control submanager has been confirmed.

(S)
Continues processing.

KAVT0347-I

A response from the Event Action Manager has been confirmed.(maintenance-information)

A response from the event/action control manager has been confirmed.

(S)
Continues processing.

KAVT0401-E

An internal error occurred. (maintenance-information)

An error occurred due to an internal factor of the event/action control.

(S)
Determines the event job to be an error.

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0402-E

Memory became insufficient. (maintenance-information) (maintenance-information)

Memory became insufficient.

(S)
Determines the event job to be an error.

(O)
See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT0403-E

The specified agent is not defined in the job execution environment. (host=exec-agent, maintenance-information)

The execution agent name defined for the execution agent is not defined as an execution agent.

(S)
Determines the event job to be an error.

(O)
Make sure that the execution agent name specified for the execution agent for the job is correct, or check whether an execution agent group name is specified.
Event jobs (including those defined as start conditions of jobnets with start conditions) do not support execution agent groups. For details on the operation performed when an execution agent group is specified for the event job, see 7.6 Notes on using event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
If the execution agent name specified for the job is correct, the execution agent has not been defined in the agent management information. Add the agent specified as the execution agent for the job to the agent management information.

KAVT0404-E

An error occurred during communication with the agent. (maintenance-information)

Communication with the agent failed.

(S)
Determines the event job to be an error.

(O)
Check whether the execution host and JP1/AJS3 have started.

KAVT0405-W

Because communication with the agent failed, it will be retried.

An attempt to communicate with the agent has failed due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
Check whether the execution host and JP1/AJS3 have started.

KAVT0406-E

Socket communication failed. (maintenance-information)

Communication with the event/action control manager failed.

(S)
Determines the event job to be an error.

(O)
Check whether an error has occurred in the network.
If no error has occurred in the network, the error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0408-E

The definition information of the specified agent is now being changed so you cannot use the agent. (host=agent-host-name, maintenance-information)

You cannot use the agent host indicated in agent-host-name because its configuration definition information is being changed.

(S)
Determines the event job to be an error.

(O)
Wait until the change of the configuration definition information (environment setting) terminates, than then retry.

KAVT0409-I

The data was sent to the agent.

The data was sent to the agent.

(S)
Continues processing.

KAVT0410-E

The parameter (parameter) after replacing a macro variable is too long (length=parameter-length).

The parameter, after replacing a macro variable, is too long.

(S)
Determines the event job to be an error.

(O)
Recheck the setting of the parameter that caused the error, and then re-execute the event job. If ex is indicated in parameter, also check the setting of the jobnet execution host.

KAVT0411-E

The macro variable (macro-variable-name) has not been inherited.

The macro variable was not inherited.

(S)
Determines the event job to be an error.

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

KAVT0412-W

The half at new branch execution ID acquisition waiting time has passed. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)

One half (30 minutes#2) of the waiting time for acquisition of the branch execution ID (one hour#1) has passed.

30 minutes#2 later, the status of the jobnet with start conditions might change to Monitor terminated.

#1
For the compatible ISAM configuration, 30 minutes.

#2
For the compatible ISAM configuration, 15 minutes.

(S)
Continues processing.

(O)
Startup of a jobnet with start conditions takes a long time due to heavy loading on the schedule control.
The probable causes are:
  • Many events being monitored by the jobnet with start conditions have occurred.
  • Many jobnets in a batch or a jobnet containing many jobs was registered for execution or terminated forcibly.
  • A jobnet with many logs to keep was unregistered.
  • A jobnet with many fixed generations was unregistered.
  • Many jobnets set in the schedule have reached the start time at the same time.
  • A jobnet with start conditions having many generations whose start conditions (AND) are partially satisfied is terminated forcibly, or is placed in Monitor terminated status due to the valid range of start condition.
  • The system loading is heavy due to a program other than JP1/AJS3.
If any of the above problems occurred and JP1/AJS3 caused the load, wait until processing terminates. If a program other than JP1/AJS3 caused the load, terminate that program as required.
To determine the name of the delayed jobnet with start conditions, you can use the unit ID displayed by executing the ajsname command with the -I option specified.

KAVT0498-I

JP1/AJS2 Event Action Manager will now start.

The event/action control manager will now start.

(S)
Continues processing.

KAVT0499-I

JP1/AJS2 Event Action Manager will now end.

The event/action control manager will now terminate.

(S)
Continues processing.

KAVT0502-E

The installation path could not be acquired.

The directory that installs JP1/AJS3 could not be obtained. For Windows, the registry information may be corrupted.

(S)
Terminates the event/action control agent.

(O)
Registry information may have been corrupted. Re-reinstall and then restart JP1/AJS3.

KAVT0508-E

A message-reception pipe could not be opened. (process type=process-type maintenance-information) (process name=process-name, maintenance-information)

An attempt to create a pipe file used in the event/action control agent has failed.

(S)
Continues processing while the function of the process indicated in process-type is disabled.

process-type
0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job
1: Monitoring Files job
2: Receive MQ Message job
3: Email Reception Monitoring job
4: Interval Control job
5: Receive MSMQ Message job

(O)
Check the following, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0511-E

Memory became insufficient. (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

A memory shortage occurred.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
First, use the ajsname command with the -I option specified to identify the name of the relevant jobnet with start conditions or the relevant event job. Next, perform the following operation to change the status of the jobnet or job in an ended status:
  • For a jobnet with start conditions, forcibly terminate the jobnet.
  • For an event job, terminate the jobnet forcibly or by changing the job status.
Then, if necessary, re-execute the jobnet or job.
For details on the ajsname command, see ajsname in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
In addition, check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in the documentation for the product (such as Release Notes).

KAVT0512-E

The socket could not be opened. (Manager=name-of-manager-at-send-destination) (maintenance-information)

Communication with the manager host failed.

(S)
Terminates the process if the error occurred during startup of the event/action control agent process.
If the error occurred after the process started, the system continues processing and retries the communication.

(O)
Check whether:
  • A network failure occurred.
  • JP1/AJS3 is running on the manager host.
  • The host name has been resolved.
    If the host name has not been resolved, check the hosts and jp1hosts files and the DNS server settings.
If the error occurred during startup of the event/action control agent process, preventing the startup of the process, also check the following:
  • Check whether the local host name is registered in the hosts file.
  • Check whether the JP1/AJS3 port number is registered in the services file.
    If the JP1/AJS3 port number is not registered, register it, and then restart JP1/AJS3.
  • Check whether there is a process whose name begins with jpo.
    In Windows
    Use Task Manager to check for the process. If you find such a process, restart JP1/AJS3 or the system.
    In UNIX
    Use the ps command to check for the process. If you find such a process, use the kill command to kill the process, and then restart JP1/AJS3.

KAVT0513-E

JP1/AJS2 multi-weighting could not be initialized. (maintenance-information)

An unexpected error occurred.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.

KAVT0515-E

Main loop of an agent failed. (maintenance-information)

An attempt to start the event/action control agent has failed.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.

KAVT0520-W

The event monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The functions of the JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be used because an attempt to start the process that executes these jobs has failed.

(S)
Continues processing in a reduced mode for the functions.

(O)
If you want to use these functions, check the following and then restart JP1/AJS3.
If you do not intend to use these functions, ignore this message and continue operation.
  • Check whether an executable file with the same name as the process name indicated in process name=process-name exists.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether memory is sufficient.
    For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0521-W

The file monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the file monitoring job cannot be used because an attempt to start the process that executes this job has failed.

(S)
Continues processing in a reduced mode for the function.

(O)
If you want to use this function, check the following and then restart JP1/AJS3.
If you do not intend to use these functions, ignore this message and continue operation.
  • Check whether an executable file with the same name as the process name indicated in process name=process-name exists.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether memory is sufficient.
    For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0522-W

The message queue monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the Receive MQ message job cannot be used because an attempt to start the process that executes this job has failed.

(S)
Continues processing in a reduced mode for the function.

(O)
If you want to use this function, check the following and then restart JP1/AJS3.
If you do not intend to use these functions, ignore this message and continue operation.
  • Check whether an executable file with the same name as the process name indicated in process name=process-name exists.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether memory is sufficient.
    For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0523-W

The mail monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The function of the email reception monitoring job cannot be used because an attempt to start the process that executes this job has failed.

(S)
Continues processing in a reduced mode for the function.

(O)
If you want to use this function, check the following and then restart JP1/AJS3.
If you do not intend to use these functions, ignore this message and continue operation.
  • Check whether an executable file with the same name as the process name indicated in process name=process-name exists.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether memory is sufficient.
    For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0524-W

The timer monitoring function is unusable. (maintenance-information, process name=process-name, maintenance-information)

The functions for interval control and timeout cannot be used because an attempt to start the process that executes the jobnet with these functions specified has failed.

(S)
Continues processing in a reduced mode for the function.

(O)
If you want to use this function, check the following and then restart JP1/AJS3.
If you do not intend to use these functions, ignore this message and continue operation.
  • Check whether an executable file with the same name as the process name indicated in process name=process-name exists.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether memory is sufficient.
    For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT0526-E

The JP1/Base definition could not be read. (maintenance-information)

An attempt to read common definition information has failed.

(S)
Terminates the event/action control agent.

(O)
Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can acquire it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT0530-E

The end request for the pipe could not be written. (process type=process-type maintenance-information) (process name=process-name, maintenance-information)

An attempt to write to a pipe file used in the event/action control agent has failed.

(S)
Continues processing while the function of the process indicated in process-type is disabled.

process-type
0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job
1: Monitoring Files job
2: Receive MQ Message job
3: Email Reception Monitoring job
4: Interval Control job
5: Receive MSMQ Message job

(O)
The process indicated in process-type may still remain in the system.
In UNIX, use the ps command to check whether the process remains in the system. If the process remains, use the kill command to terminate it.
In Windows, restart the system.
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0539-E

The auxiliary file could not be read. (auxiliary file=auxiliary-file-name) (maintenance-information)

An attempt to write to a communication information file for a monitoring process in the event/action control agent has failed.

(S)
Places the job in the Ended abnormally status, and continues processing.

(O)
Check the following, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0541-E

The pipe could not be written to. (process type=process-type maintenance-information)

An attempt to write to a pipe file used in the event/action control agent has failed.

(S)
Continues processing while the function of the process indicated in process-type is disabled.

process-type
0: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job
1: Monitoring Files job
2: Receive MQ Message job
3: Email Reception Monitoring job
4: Interval Control job
5: Receive MSMQ Message job

(O)
Check the following, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
Check whether the directory created at JP1/AJS3 installation is unintentionally deleted. If the code indicated in maintenance-information is -1, this means that the agent process has terminated. Restart JP1/AJS3 on the agent.

KAVT0542-E

The auxiliary file name could not be acquired. (maintenance-information)

An attempt to acquire a communication information file for a monitoring process used in the event/action control agent has failed.

(S)
Places the job in the Ended abnormally status, and continues processing.

(O)
Check the following, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0544-E

The auxiliary file could not be read. (auxiliary file=auxiliary-file-name) (maintenance-information)

An attempt to read a communication information file for a monitoring process used in the event/action control agent has failed.

(S)
Places the job in the Ended abnormally status, and continues processing.

(O)
Check the following, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation is unintentionally deleted.

KAVT0559-E

The socket sending failed. (Manager=name-of-manager-at-send-destination) (maintenance-information)

The socket could not be sent to the manager.

(S)
Continues or terminates processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
This message appears when the manager is loaded or when a network error occurred. Check whether the manager host and JP1/AJS3 have started, check the unit (a jobnet with start conditions or an event job) whose status has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status.

KAVT0562-I

The agent process of the event action function will now start.

The event/action control agent will now start.

(S)
Starts the event/action control agent.

KAVT0563-I

The agent process of the event action function will now end.

The event/action control agent will now end.

(S)
Terminates the event/action control agent.

KAVT0566-E

The size of the working path exceeds the limit.

The length of any of the following directory names exceeded 228 bytes: After correcting the error, stop the JP1/AJS3 service and restart it.

  • The JP1/AJS3 installation directory name
  • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

(S)
Terminates processing.

(O)
Correct the length of the following directory names to 228 bytes or smaller.
  • The JP1/AJS3 installation directory name
  • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

KAVT0567-E

The requested event icon is unusable. (event type=event-type) (host= manager-host-name, maintenance-information)

The requested event job cannot be used. Alternatively, the manager requested a code that was not supported.

(S)
Continues processing while the function of the event job indicated in event-type is disabled.

event-type
JP1/AJS2_EVACT_MAIL_WATCH: Email reception monitoring job
JP1/AJS2_EVACT_MQ_WATCH: Message queue reception monitoring job
JP1/AJS2_EVACT_MSMQ_WATCH: MSMQ reception monitoring job

(O)
Check whether the function of the requested event job is enabled in the agent configuration definition (environment setting).
For details about the email reception monitoring job, see 2. Linking Mail Systems in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT0570-E

The handle from the process monitor could not be acquired. (maintenance-information) Stopping via the JPI/AJS2 service is not possible.

Communication with the JP1/AJS3 process monitor failed.

(S)
Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3 service.

(O)
To terminate the event/action control agent in UNIX, use the kill command to terminate the jpoagent process. In Windows, restart the system.
The JP1/AJS3 process monitor may not operate correctly. Reinstall JP1/AJS3 and then restart.

KAVT0572-E

A report to the process monitor failed. (maintenance-information)

Communication with the JP1/AJS3 process monitor failed.

(S)
Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3 service.

(O)
To terminate the event/action control agent in UNIX, use the kill command to terminate the jpoagent process. In Windows, restart the system.
The JP1/AJS3 process monitor may not operate correctly. Reinstall JP1/AJS3 and then restart.

KAVT0582-W

Unreported information exceeded the warning value. Check whether the manager (manager-name) is running.

The amount of information that cannot be reported to the manager exceeded the warning value.

(S)
Continues processing.

(O)
This message warns you of the number of unprocessed events that exceeded the specified value. Check whether the manager has started, and then check the following.

- If the manager is not running
Start the manager so that it can receive notifications from the agent.

- If the manager is running
Check the following:
  • Check whether an event job has terminated normally or whether a jobnet with start conditions has started.
    If processing is proceeding without any problems, ignore this message and allow the processing to continue.
  • Check whether many events that are monitored with start conditions have occurred.
    Review the definitions of event jobs or jobnets with start conditions that are defined to be executed on the relevant agent. If a definition will result in many events, review and change operation to reduce the number of events that will occur.
  • Check whether the manager and agent can communicate with each other.
    See the following supplementary notes and check whether the manager and agent can communicate with each other.

Supplementary notes
  • Check whether the agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • Check whether the manager host name# can be resolved on the agent host.
    If the manager host name cannot be resolved, review the environment settings, such as the hosts and jp1hosts files on the agent host and the DNS settings, and ensure that the manager host name can be resolved.
  • Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • Check whether the IP address obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.
    If these IP addresses do not match, correct the environment settings, such as the hosts and jp1hosts files on the agent host and the DNS settings, so that the correct IP address is resolved by name resolution.
  • Check whether there are problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are communication problems, correct them. Similarly, check whether the agent host can communicate with the manager host, and correct any problems you find.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT0588-E

The specified working path does not exist.

The directory specified for any of the following directory names does not exist: After correcting the error, stop the JP1/AJS3 service and restart it.

  • The JP1/AJS3 installation directory name
  • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

(S)
Terminates processing.

(O)
Specify the following directory names.
  • The JP1/AJS3 installation directory name
  • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])

KAVT0590-W

During end processing, an event request (event-request-type) from the manager (manager-name) cannot be accepted.

The agent does not accept new event requests from the manager during termination processing.

(S)
Continues processing.

(O)
Restart JP1/AJS3, and then use the jpoagtjobshow command to make sure that the event job is being monitored. Then continue processing.

KAVT0593-W

The MS message queue monitoring function is unusable. (maintenance- information, process name=process-name, maintenance-information)

The MSMQ monitoring function is unusable.

(S)
Continues processing in a reduced mode for the functions.

(O)
Refer to the message that describes the cause of the error, and then follow the instructions.

KAVT0600-E

Failed in creation of status file. (maintenance-information)

A work file for managing the status of an agent in the event/action control agent could not be created.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT0603-W

Elapsed time since restart-time is used for time-out due to temporary interruption of monitoring.

The restart of the agent machine or other reasons temporarily interrupted monitoring. The elapsed time since the monitoring restarted is used for time-out.

(S)
Continues processing.

(O)
Check the time the monitoring restarted, and continue operation.

KAVT0606-W

Sending to the manager failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information)

The agent attempted to report the status of an event job to the manager, but could not communicate with the manager indicated in manager-name due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
This message is output when the manager is loaded. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time. If this error message is output repeatedly, however, check whether the manager host and JP1/AJS3 have started.

KAVT0607-W

The socket could not be opened so the event job status will be re-reported. (Manager=manager-name) (maintenance-information)

The agent attempted to report the status of an event job to the manager, but could not communicate with the manager indicated in manager-name due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
This message appears when the agent cannot resolve the manager name. Ignore the message and continue the operation because the data that caused the communication error will be resent to the manager automatically after a predefined period of time. If this error message is output repeatedly, however, check whether:
  • A network error does not occur.
  • The manager machine has stopped.
  • The manager host name has been resolved. If it has not, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.

KAVT0608-W

The socket accept failed. (code=return-code) (maintenance-information)

The socket could not receive data.

(S)
Continues processing.

(O)
The job may remain in the queue or in the execution status while the event is established. Check the job execution status.

KAVT0609-W

The socket receiving failed. (IP Address=IP-address host=host-name)

The connection is severed while the socket is receiving data.

(S)
Continues processing.

(O)
The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0610-W

The socket receive error occurred. (IP Address=IP-address host=host-name) (maintenance-information)

An error occurred while the socket is receiving data.

(S)
Continues processing.

(O)
The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0611-W

The socket close error occurred. (IP Address=IP-address host=host-name) (maintenance-information)

An error occurred while the socket is terminating the reception of data.

(S)
Continues processing.

(O)
The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name.

KAVT0612-W

Sending to the manager confirm failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information)

The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the manager indicated in manager-name due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
This message might appear when the communication status between the manager and the agent is unstable. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time.
If this message appears frequently, check whether:
  • A network failure has occurred.
  • JP1/AJS3 on the manager host is running.
  • A heavy load is placed on the manager.

KAVT0613-W

Sending to the manager confirm failed so the event job status will be re-reported. (Manager=manager-name) (maintenance-information)

The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the manager indicated in manager-name due to a temporary communication error.

(S)
Retries communication after the predefined period of time.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(O)
This message might appear when the communication status between the manager and the agent is unstable. Ignore the message and continue the operation because the data that could not be sent will be resent to the manager automatically after a predefined period of time.
If this message appears frequently, check whether:
  • A network failure has occurred.
  • JP1/AJS3 on the manager host is running.
  • A heavy load is placed on the manager.

KAVT0615-W

Unreported information resend max over. Unreported information will be abandoned. (Manager=manager-name)

The agent retried communicating with the manager for the predefined period of time, but could not send the status of the event job.

For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(S)
Continues processing without reporting the event job status.

(O)
This message appears when the manager machine has not started or when a communication error occurred. Check whether the manager host and JP1/AJS3 have started.

KAVT0616-E

A subagent-message-reception pipe could not be opened. (code=maintenance-code)

An attempt to create a pipe file used in the event/action control subagent has failed.

(S)
Terminates the event/action control subagent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0618-E

The end request for the subagent pipe could not be written. (code=maintenance-code)

An attempt to write to a pipe file used in the event/action control subagent has failed.

(S)
Terminates the event/action control subagent.

(O)
The jpoagtsub process may still remain in the system.
In UNIX, use the ps command to check whether the process remains in the system. If the process remains, use the kill command to terminate it.
In Windows, restart the system.
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0620-E

The subagent pipe could not be written to. (code=maintenance-code)

An attempt to write to a pipe file used in the event/action control subagent has failed.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job). If the jpoagtsub process is not running, the system terminates the event/action control subagent.

(O)
Check the following, making sure that the status of the unit (a jobnet with start conditions or an event job) has not changed, and then retry:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
  • Use a command such as a ps command to check whether the jpoagtsub process is running. If it is not running, restart JP1/AJS3.

KAVT0621-E

Waiting for a subagent pipe connection from the monitoring process failed. (code=maintenance-code)

The information could not be obtained from the event/action control subagent.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.
  • Check whether any other program has forcibly terminated the jpoagtsub process illegally.

KAVT0625-E

A subagent-message-reception pipe could not be read. (code=maintenance-code)

The information could not be obtained from the event/action control subagent.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
  • Check whether any other program has forcibly terminated the jpoagtsub process illegally.

KAVT0628-E

The subagent function is unusable. (maintenance-information)

An attempt to start the event/action control subagent has failed.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0629-E

An agent-message-reception pipe could not be opened. (code=maintenance-code)

An attempt to create a pipe file used in the event/action control agent has failed.

(S)
Terminates the event/action control agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0632-E

The agent pipe could not be written to. (code=maintenance-code) (host= manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The pipe file of the event/action control agent could not be written.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then retry the operation:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0633-E

Waiting for an agent pipe connection from the monitoring process failed. (code=maintenance-code)

The information could not be obtained from the event/action control agent.

(S)
Terminates the event/action control subagent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.
  • Check whether any other program has forcibly terminated the jpoagent process illegally.

KAVT0635-E

The agent-message-sending pipe could not be connected. (code=maintenance-code)

Reporting to the event/action control agent was impossible.

(S)
Terminates the event/action control subagent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0637-E

An agent-message-reception pipe could not be read. (code=maintenance-code) (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The information could not be obtained from the event/action control agent.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then retry the operation:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0641-W

An attempt to wait for connection from a host (IP-address) failed. (maintenance-information)

Connection from the host could not be placed in the wait state.

(S)
Continues processing.

(O)
Check jp1hosts to see whether the definition of the host indicated in IP-address is correct. The jpomgrsub and jpoagent processes may still remain in the system. In UNIX, use the ps command to check whether the processes remain in the system. If the processes remain, use the kill command to terminate them. In Windows, restart the system.

KAVT0642-E

The process will now stop because Event Action Agent finished.

The event/action control agent will stop because the event/action control subagent terminated.

(S)
Terminates the event/action control agent.

(O)
Use the integrated trace information log to determine the cause of the event/action control subagent being terminated and take action. Then, restart JP1/AJS3.

KAVT0643-E

The process will now stop because Event Action Subagent finished.

The event/action control subagent will stop because the event/action control agent terminated.

(S)
Terminates the event/action control subagent.

(O)
Use the integrated trace information log to determine the cause of the event/action control agent being terminated and take action. Then, restart JP1/AJS3.

KAVT0646-E

The agent pipe over retry count (code=maintenance-information) (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information)

The pipe file of the event/action control agent could not be written.

(S)
Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).

(O)
Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID. Make sure that the status of the identified unit (a jobnet with start conditions or an event job) has not changed, and then retry the operation:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT0649-E

A host name in the FQDN format could not be obtained. Processing is canceled. (code=maintenance-code) (host=host-name, maintenance-information)

The system could not obtain a host name in the FQDN format.

(S)
Terminates processing.

(O)
Check whether the DNS has been set up correctly.

KAVT0650-W

Port information about the event action function cannot be read, so the default port number is used. (port number=default-port-number, code=maintenance-code)

The system terminates processing because information about the port number for the event/action control cannot be read.

(S)
Terminates processing.

(O)
Check whether the port number for the event/action control is set in the services file, and then restart JP1/AJS3.
For details about port numbers, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0651-E

Port information about the event action function cannot be read. (port=service-name, code=maintenance-code)

The system cannot read information about the port number for the event/action control, so the system terminates processing.

(S)
Terminates processing.

(O)
Check whether the port number for the event/action control is set in the services file, and then restart JP1/AJS3.
For details about port numbers, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVT0654-E

The files will be deleted, because the internal files of event action control have been destroyed. (maintenance-information)

The files will be deleted because the internal files used for event action control have been corrupted.

If this message appears, the following phenomena may have occurred:

  • Information about the events that occurred before JP1/AJS3 stopped was lost.
  • Monitoring was not resumed for the jobnets with start conditions and event jobs that were running before JP1/AJS3 stopped.

(S)
Continues processing.

(O)
To resume monitoring on the agent, restart JP1/AJS3 on the manager host. Then check the status of the jobnet with start conditions or the event job, and then re-register the job for execution.

KAVT0900-I

JP1/AJS2 event action agent will now start.

The event/action control agent will now start.

(S)
Continues processing.

KAVT0901-I

JP1/AJS2 event action agent will now end.

The event/action control agent will now terminate.

(S)
Continues processing.

KAVT0910-E

Invalid specification in configuration definition. (item-name : maintenance-information)

The configuration definition contains an invalid specification.

(S)
Assumes the default and continues processing.

(O)
Correctly specify the value indicated by item-name. The output item names are described in 2. Environment Setting Parameters in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVT0911-E

An attempt to read the configuration definition failed. (item-name : maintenance-information)

An attempt to read the configuration definition has failed.

(S)
Assumes the default and continues processing.

(O)
If the system assumes an unexpected value, correct the cause of the error and then reissue the request. 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, recheck the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, collect the internal trace log and then contact the system administrator.

KAVT0912-E

Event Action 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 the event/action control if the process indicated in process-name is either of the following:
  • jpomgrsub
  • jpoagtsub
If one of the following processes is indicated in process-name, the system operates at a reduced level while the function of the process is disabled:
  • jpoeventwatch: Receive JP1 Event job, Monitoring Log Files job, or Monitoring Event Log job
  • jpocwtflMain: Monitoring Files job
  • jpocwtmlmain: Email Reception Monitoring job
  • jpocwtmqmain: Receive MQ Message job
  • jpocwttmMain: Interval Control job or an event job with a timeout specified
  • jpocwtmsmain: Receive MSMQ Message job

- Operations based on the specification of the detail process termination option
  • When N is specified for the EVProcessHA environment setting parameter to disable the detail process termination option, if a job related to a detail process that terminated abnormally is registered for execution, the job terminates abnormally.
    For example, the file monitoring job that is executed when the jpocwtflMain process has terminated abnormally terminates abnormally.
  • If you use a cluster system or enable the detail process termination option by specifying Y for the EVProcessHA environment setting parameter or using the default, the system terminates the event/action control if an error occurs. At this time, operation does not continue at a reduced level irrespective of the process indicated in process-name.
For details about the detail process termination option, see 2.4 Setting up the event/action control environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

(O)
Examine the cause of the error from the system error message that was output before or after the message, and then take action. 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).
To continue processing, collect data and then restart JP1/AJS3.
There is no problem if this message appears when you execute jajs_killall.cluster command.

KAVT0950-I

The JP1/AJS2 monitor resource went online.

The monitored resource was placed online.

(S)
Continues processing.

KAVT0951-I

The JP1/AJS2 monitor resource went offline.

The monitored resource was placed offline.

(S)
Continues processing.

KAVT0952-I

OpenView Environment (maintenance-information) Setup skipped.

Setup of HP NNM Link was skipped.

(S)
Continues processing.

KAVT0953-I

OpenView Environment of JP1/AJS2 was installed normally.

HP NNM Link was installed normally.

(S)
Continues processing.

KAVT0954-I

OpenView Environment of JP1/AJS2 was uninstalled normally.

HP NNM Link was uninstalled normally.

(S)
Continues processing.

KAVT0955-I

Symbol of JP1/AJS2 was deleted normally.

The symbol was deleted normally.

(S)
Continues processing.

KAVT0958-I

Resource monitoring will now start.

Resource monitoring starts.

(S)
Continues processing.

KAVT0959-I

Resource not found.

The resource is not found.

(S)
Continues processing.

KAVT0960-I

Resource status to be offline.

The resource is placed offline.

(S)
Continues processing.

KAVT0961-I

Resource status to be online.

The resource is placed online.

(S)
Continues processing.

KAVT0962-I

Resource monitoring bring to a termination.

Resource monitoring terminated.

(S)
Terminates processing.

KAVT0963-I

Resource monitoring will now end.

Resource monitoring terminates.

(S)
Terminates processing.

KAVT0980-W

Unreported information will now be deleted, because the amount of unreported information for manager-host-name has exceeded threshold.(host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID maintenance-information)

Unreported information will now be deleted because the amount of unreported information for manager-host-name has exceeded the threshold.

(S)
Continues processing.

(O)
This message appears when the remaining unprocessed data that could not be reported to the manager is deleted when the amount of data exceeds the threshold, so that resources such as memory and disk space remain available.
For the manager host and agent host indicated in the message, check whether JP1/AJS3 on the manager host is running. If it is not running, start it. If JP1/AJS3 on the manager host is running, check the following:

- Check whether many events being monitored by the jobnet with start conditions have occurred
Check the definition of an event job or a jobnet with start conditions for which the agent is defined as the target host. If the definition will cause a mass of events to be generated at the same time, review the operation and reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in the following procedure:
  1. Check the scheduler service name and unit ID indicated in AJSServiceName=scheduler-service-name, UnitID=unit-ID in the message.
  2. On the manager host, execute the ajsname command with the scheduler service name and unit ID you obtained in step 1 specified.
    Example:
    ajsname -F scheduler-service-name -I unit-ID
    /name-of-the-jobnet with start conditions/.CONDITION/JP1 event reception monitoring

- Check whether the manager host and the agent host can communicate with each other
Check the following:
  • Check whether the agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the settings, such as those for the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • Check whether the manager host name# can be resolved on the agent host.
    If the manager host name cannot be resolved, review the settings, such as those for the hosts and jp1hosts files and on the agent host and the DNS settings, and ensure that the manager host name can be resolved.
  • Check whether the IP address of the agent host obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, review the settings, such as those for the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address can be obtained by name resolution.
  • Check whether the IP address of the manager host obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.
    If these IP addresses do not match, review the settings, such as those for the hosts and jp1hosts files and on the agent host and the DNS settings, so that the correct IP address can be obtained by name resolution.
  • Check for any problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are any problems, correct them. Also check the agent host the same way and correct problems, if any.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command
Also check the following and take action if necessary:
  • If an event job is registered for execution but the job status does not change from Now queuing to Now running, check the items described in (O), forcibly terminate the job, and then retry the operation.
  • If a jobnet with start conditions or an event job is forcibly terminated but the job status remains Now running, check the items described in (O), and then forcibly terminate the job or jobnet again.
  • Check whether an event that must be detected has occurred within a certain period of time after this message was output.
    For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
    If such an event occurred, check the items described in (O), re-execute the event job if necessary, and then re-generate the events to be monitored.

KAVT0981-W

Reply queue information is discarded because there is no reply for a certain period of time to the information reported to manager-host-name. (host=agent-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID maintenance-information)

Reply queue information is discarded because there is no reply to the information reported to manager-host-name within 24 hours.

(S)
Continues processing.

(O)
This message appears when reply queue information is deleted because no response is sent within 24 hours since the data was reported to the manager, so that resources such as memory and disk space remain available.
For the manager host and agent host indicated in the message, check whether JP1/AJS3 on the manager host is running. If it is not running, start it. If JP1/AJS3 on the manager host is running, check the following:

- Check whether many events being monitored by the jobnet with start conditions have occurre
Check the definition of an event job or a jobnet with start conditions for which the agent is defined as the target host. If the definition will cause a mass of events to be generated at the same time, review the operation and reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in the following procedure:
  1. Check the scheduler service name and unit ID indicated in AjsServiceName=scheduler-service-name, UnitID=unit-ID in the message.
  2. On the manager host, execute the ajsname command with the scheduler service name and unit ID you obtained in step 1 specified.
    Example:
    ajsname -F scheduler-service-name -I unit-ID
    /name-of-the-jobnet with start conditions/.CONDITION/JP1 event reception monitoring

- Check whether the manager host and the agent host can communicate with each other
Check the following:
  • Check whether the agent host name# can be resolved on the manager host.
    If the agent host name cannot be resolved, review the settings, such as those for the hosts and jp1hosts files on the manager host and the DNS settings, and ensure that the agent host name can be resolved.
  • Check whether the manager host name# can be resolved on the agent host.
    If the manager host name cannot be resolved, review the settings, such as those for the hosts and jp1hosts files and on the agent host and the DNS settings, and ensure that the manager host name can be resolved.
  • Check whether the IP address of the agent host obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host.
    If these IP addresses do not match, review the settings, such as those for the hosts and jp1hosts files on the manager host and the DNS settings, so that the correct IP address can be obtained by name resolution.
  • Check whether the IP address of the manager host obtained by resolving the manager host name on the agent host is the same as the actual IP address of the manager host.
    If these IP addresses do not match, review the settings, such as the hosts and jp1hosts files on the agent host and the DNS settings, so that the correct IP address can be obtained by name resolution.
  • Check for any problems with the network environment.
    Use the ping command or another means to check whether the manager host can communicate with the agent host via TCP/IP. If there are any problems, correct them. Also check the agent host the same way and correct problems, if any.

#
  • For a physical host:
    For DNS operation, the host name in the FQDN format. For other cases, the host name obtained by executing the hostname command
  • For a logical host:
    In Windows
    The host name indicated in xxxxx in JP1/AJS3_xxxxx in the Services window that is displayed by choosing Services or by choosing Administrative Tools and then Services in the Control Panel window on the agent host
    In UNIX
    The host name indicated after the jajs_spmd process that is displayed by executing the ps command

KAVT1001-I

The event-receiving process will now end.

The event (such as a JP1 event and log trap) monitoring process will now terminate.

(S)
Terminates the event (such as a JP1 event and log trap) monitoring process.

KAVT1002-I

The event-receiving process will now start

The event (such as a JP1 event and log trap) monitoring process will now start.

(S)
Continues processing.

KAVT1003-E

Failed to get logical host. (maintenance-information) (maintenance-information)

Information required for operating an event (such as a JP1 event and log trap) monitoring process could not be acquired.

(S)
Terminates the event (such as a JP1 event and log trap) monitoring process. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)
Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can collect it, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1004-I

The event sever was connected. (event-server-name)

The JP1/Base event service was connected.

(S)
Continues processing.

KAVT1005-W

Connection to the event server is not possible now. (event-server-name)

Connection to the JP1/Base event service was released.

(S)
Retries connection to the JP1/Base event service. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored until the JP1/Base event service can be connected again.

(O)
Check whether the JP1/Base event service has started.

KAVT1006-I

Connecting the event server will be retried. (event-server-name)

The system will retry the connection to the JP1/Base event service.

(S)
Continues processing.

KAVT1007-W

The event sever is inactive. (event-server-name)

The JP1/Base event service has not yet started.

(S)
Continues processing while retrying the connection because the JP1/Base event service has not started. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored until the JP1/Base event service starts.

(O)
Check whether the JP1/Base event service has started.

KAVT1008-E

Initialization error (maintenance-information) (maintenance-information)

Initialization required for acquiring information has failed.

(S)
Continues processing. The system terminates the event (such as JP1 event and log trap) monitoring process depending on the location where the error occurred. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)
Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1013-E

Failed to analyze job data. (maintenance-information) (maintenance-information)

The definitions of a Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job contain an error.

(S)
Terminates the job abnormally because the job definitions contain an error.

(O)
Check the version of JP1/AJS3 that executes the job to see whether a definition not supported by that version is specified.

KAVT1014-E

An error occurred during the creation of an action definition file. (maintenance-information)

Internal processing (file creation) required for starting the Monitoring Log Files job has failed.

(S)
Abnormally terminates the log file monitoring job.

(O)
Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job. Especially, check the space available on the disk that contains the JP1/AJS3 system folder (directory). If you cannot find any problem, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1015-E

The log-file trap command could not start. (maintenance-information)

An attempt to start the Monitoring Log Files job has failed.

(S)
Places the log file monitoring job into Ended abnormally status.

(O)
An error message for the JP1/Base log-file trap function has been output to the Execution Result Details dialog box. Take action according to the instructions given by that message. If you specify SEQ2 for the log file output format for the log file monitoring job, check the following according to the OS on the host specified as the target host for the job.
  • For a UNIX environment
    Check whether the version of JP1/Base and JP1/AJS is 07-00 or later.
  • For a Windows environment
    Check whether the JP1/Base version is 08-10 or later, and the JP1/AJS version is 08-00 or later.

KAVT1017-I

Condition is concluded.( maintenance-information)

The received event satisfied the job conditions.

(S)
Continues processing.

KAVT1025-W

No end judgment file exists. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job was not found.

(S)
Ignores information about end judgment and continues processing.
If Normal if message matches or Normal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job abnormally.
If Abnormal if message matches or Abnormal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job normally.

(O)
Check whether the specified file exists in the Receive JP1 Event job. End judgment of the job may not have been performed correctly because the end judgment file is missing. Check the Receive JP1 Event job.

KAVT1026-W

The end judgment file includes no data. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job does not contain data.

(S)
Ignores information about end judgment and continues processing.
If Normal if message matches or Normal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job abnormally.
If Abnormal if message matches or Abnormal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job normally.

(O)
Check the contents of the file specified in the Receive JP1 Event job. End judgment of the job may not have been performed correctly. Check the Receive JP1 Event job.

KAVT1027-E

An error occurred during processing of an end judgment file. (end-judgment-file-name)

The end judgment file specified in the Receive JP1 Event job cannot be read.

(S)
Assumes that the end judgment information does not exist. Continues processing.
Terminates the Receive JP1 Event job abnormally.

(O)
Check whether the system resources are sufficient, and whether the user who started JP1/AJS3 can view the file specified in the Receive JP1 Event job. End judgment of the job may not have been performed correctly. Check the Receive JP1 Event job.

KAVT1028-E

Memory became insufficient. (maintenance-information)

Memory was insufficient during processing of the event job.

(S)
Continues processing. The system determines the event job to be an error depending on the location where the error occurred.

(O)
See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.

KAVT1029-E

The event could not be created. (maintenance-information) (maintenance-information)

An attempt to connect to the JP1/Base event service has failed.

(S)
Retries until the JP1/Base event service is connected. The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored during the retries.

(O)
Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1030-E

The event server could not be connected. (maintenance-information) (maintenance-information)

An attempt to connect to the JP1/Base event service has failed.

(S)
Retries until the JP1/Base event service is connected. The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored during the retries.

(O)
Check whether the JP1/Base event service can start. If the JP1/Base event service can start, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1031-E

Failed to get Pipe Data. (maintenance-information) (maintenance-information)

An attempt to receive a pipe from the agent or the event search process has failed.

(S)
Cancels pipe processing. The system terminates the event (such as JP1 event and log trap) monitoring process depending on the location where the error occurred. Detection of a Receive JP1 Event job, a Monitoring Log Files job, or a Windows event trap job may have failed.

(O)
Check whether the system resources are sufficient, whether the permission environment of the user who started JP1/AJS3 is correct, and whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT1032-E

Failed to send Pipe Data. (maintenance-information) (maintenance-information)

An error occurred during inter-process communication.

(S)
Interprocess communication failed. The system continues processing. If the error occurred during registration, registration of the event job will be unsuccessful. If the error occurred after registration, the job execution status may be incorrect.

(O)
Check the following, and then retry the event job that caused the error:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT1033-E

An auxiliary file could not be opened. (maintenance-information) (maintenance-information)

An attempt to open a file used in the event (such as JP1 event and log trap) monitoring process has failed.

(S)
Cannot start monitoring of the job.

(O)
Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
After the check, re-register the job.

KAVT1037-E

Failed to get Event. (maintenance-information) (maintenance-information)

An attempt to acquire JP1 events has failed. Some JP1 events could not be acquired.

(S)
Retries connection to the JP1/Base event service.
The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored until a KAVT1004-I or KAVT1044-I message is output

(O)
Check whether the JP1/Base event service is running. If the JP1/Base event service has been terminated unintentionally, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT1040-E

Error occurred in Event function. (maintenance-information) (maintenance-information)

An error occurred during acquisition of JP1 events.

(S)
Retries connection to the JP1/Base event service. No events can be monitored until the KAVT1004-I or KAVT1044-I message is output.

(O)
See the description of the API settings file (api) in the Job Management Partner 1/Base User's Guide, and check whether the api file is set correctly.
Also check whether the JP1/Base event service is running. If the JP1/Base event service has been terminated unintentionally, contact the system administrator, and collect data (see 1.2.3 To the system administrators)

KAVT1041-W

A macro variable exceeds 4096 bytes.

An event that meets the specified monitoring condition occurred, but the sum of the size of values specified in macro variables exceeded 4,096 bytes.

(S)
Truncates the portion after the 4,096th byte and continues processing. The maximum size of the value for macro variables is 4,096 bytes.

(O)
Redefine the macro variable so that the sum of the size of values specified in the macro variables does not exceed 4,096 bytes. The portion exceeding the 4,096th byte is not passed to the succeeding jobnet or job. Check the status of the succeeding jobnet or job. If you find any problem, recheck the job definition.

KAVT1042-E

Failed to start. maintenance-information maintenance-information

An attempt to initialize the JP1 event monitoring process has failed.

(S)
Terminates the JP1 event monitoring process. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT1045-E

A log-file trap command parameter could not be created. (maintenance-information)

Internal processing required for starting the Monitoring Log Files job has failed.

(S)
Memory was insufficient. The system terminated the Monitoring Log Files job abnormally.

(O)
Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job.

KAVT1046-E

The event ID is invalid. (maintenance-information)

The event ID defined for the Receive JP1 Event job is invalid.

(S)
Abnormally terminates the Receive JP1 Event job.

(O)
Define the event ID correctly, and then retry.

KAVT1047-W

An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information)

An error occurred while analyzing the macro variable.

(S)
Abnormally terminates the job without creating the macro variable.

(O)
The specification of the macro variable may be incorrect. Recheck the definition and re-execute the job.

KAVT1048-W

The parameter (parameter) is not specified.

The required event monitoring condition is not specified in the Monitoring Log Files job.

(S)
Abnormally terminates the Monitoring Log Files job.

(O)
Specify the required monitoring condition.

KAVT1050-E

Event receiving process ended. (maintenance-information) (maintenance-information)

The JP1 event monitoring process detected an error and terminated.

(S)
Terminated the JP1 event monitoring process because an error that prevents further processing occurred. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)
Follow the instructions given by the message that was output immediately before this message, and then restart JP1/AJS3.

KAVT1052-W

The log-file trap daemon (service) ended.

The log-file trap daemon (service) has stopped while executing the log-file trap monitoring job.

(S)
Continues processing while retrying until the log-file trap daemon (service) starts.

(O)
Start the daemon (service).

KAVT1055-W

The log-file trap daemon (service) is inactive.

The Monitoring Log Files job has started, but the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) has not started yet. The Monitoring Log Files job remains in the Now running status, and cannot monitor log files.

(S)
Assumes the Monitoring Log Files job to be in the Now running status, and retries until the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) starts.

(O)
Start the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows).

KAVT1056-W

Log Trap Job is finished.

Log file trapping has terminated.

(S)
Retries and re-executes the command, and then continues monitoring.

(O)
Even if this message appears, there is no problem with operation if the job terminated normally. Ignore the message and continue the operation.
If this error message appears repeatedly, check whether the log-file trap function operates correctly.

KAVT1058-I

retry again.

A temporary error occurred. The system re-executes the log file trapping command.

(S)
Continues processing.

KAVT1059-I

Watching start.

The log file trapping command was successfully executed. The system starts monitoring the log file.

(S)
Continues processing.

KAVT1060-W

A forced-termination request was accepted.

The system accepted a forced-termination request. The job is forcibly terminated.

(S)
Accepts the kill request and forcibly terminates the job.

KAVT1061-W

Cancel time up.

The timeout period had elapsed. The job is canceled.

(S)
Cancels the job due to the specified timeout period being elapsed.

KAVT1062-W

Information could not be output. (maintenance-information) (maintenance-information)

Memory was insufficient. The JP1 event-receiving job could not output a message to the Execution Result Details dialog box.

(S)
Continues processing without outputting the message to the Execution Result Details dialog box because memory was insufficient.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT1065-W

The log-file trap command could not stop. (process-ID-of-log-file-trap (thread-ID) (operation-definition-file-name-at-executing-log-file-trap-command)

The Monitoring Log Files job terminated normally, but the process for monitoring log files could not stop or the termination could not be confirmed. The process for monitoring log files may not have stopped.

(S)
Ignores the error and continues processing.

(O)
Resources may be insufficient. Check whether the system resources are sufficient.
If this message appears, stop the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows) when you stop JP1/AJS3 next time.
If this message appears repeatedly, stop the JP1/AJS3 services and the JP1/Base log-file trap daemon (UNIX) or log-file trap service (Windows).

KAVT1066-E

Main loop of an event-receiving process failed. (maintenance-information)

An attempt to initialize the process has failed.

(S)
Terminates the process for monitoring events (JP1 events and log trapping). A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.

(O)
Check whether the system resources are sufficient, and then restart JP1/AJS3.

KAVT1067-E

Language setting could not be acquired. (maintenance-information) (maintenance-information)

The character set in the configuration definition information could not be acquired.

(S)
Assumes LANG=C for the character set, and continues the regular expression check for the monitoring conditions of the JP1 event-monitoring job.

(O)
Check whether the system resources are sufficient.
A monitoring condition using a regular expression may not work correctly. Check the generated JP1 event again, and change the status of the Receive JP1 Event job.

KAVT1200-E

An error occurred during the search for JP1 events. The JP1 event search will now stop. (maintenance-information)

An error occurred while the pre-execution event search function was searching for a JP1 event.

(S)
Cancels processing.

(O)
Check whether the JP1 event search function is available and whether a problem occurred in the JP1/Base event service.

KAVT1201-E

An attempt was made to start a JP1 event search, but the JP1 events were in a disabled state. (maintenance-information)

The pre-execution event search function cannot search for JP1 events.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required, see JP1/Base Release Notes.

KAVT1202-E

The reading of JP1 event search conditions from the file was not possible. (maintenance-information)

The system could not read from a file the search conditions for the JP1 event to be searched for by the pre-execution event search function.

(S)
Cancels processing.

(O)
Check the file system for errors.

KAVT1203-E

The writing of JP1 event search conditions to the file was not possible. (maintenance-information)

The system could not write to a file the JP1 event searched for by the pre-execution event search function.

(S)
Cancels processing.

(O)
Check the file system for errors.

KAVT1204-E

An error occurred during the reading of the event filter file. (maintenance-information, system-error-message)

An error occurred during a read from the event filter file.

(S)
Cancels processing.

(O)
Determine the cause of the error according to the system error message, and then remove the cause.

KAVT1205-E

An error occurred during the opening of the search results output file. (maintenance-information, system-error-message)

An error occurred while the search result output file was being opened.

(S)
Cancels processing.

(O)
Based on the system error message, determine the cause that disabled the read operation. Then, remove the cause.

KAVT1206-E

An error occurred during status file making process. maintenance-information, system-error-message

An error occurred during the creation of a status file.

(S)
Cancels processing.

(O)
Based on the system error message, determine the cause that disabled the read operation. Then, remove the cause.

KAVT1207-E

An error occurred during the renaming of the search results output file. (maintenance-information)

An error occurred while the search result file was being renamed.

(S)
Cancels processing.

(O)
Determine the cause of the error from the maintenance information, and correct the error.

KAVT1210-E

An attempt to create an event search filter file failed. The search for events prior to execution will not start.

Although the option for finding events before starting event monitoring is specified, an event ID is not specified.

(S)
Abnormally terminates the Receive JP1 Event job.

(O)
When using the option for finding events before starting event monitoring, you must also specify an event ID. Recheck the definition of the Receive JP1 Event job, and re-execute it.

KAVT1211-E

An attempt to create an event search filter file failed. file-name, error-code, maintenance-information

The system could not create an event search filter file.

(S)
Cancels processing.

(O)
Correct the cause that disabled the creation of the event search filter file, and then re-execute the operation.

KAVT1212-E

An attempt to start the event search process failed. file-name, error-code, maintenance-information

The system could not start the event search process.

(S)
Cancels processing.

(O)
Correct the cause that disabled the start of the event search process, and then re-execute the operation.

KAVT1213-E

An end that event search process did not expect was detected.

The system detected an unexpected termination of the event search process.

(S)
Cancels processing.

(O)
Determine the cause of the unexpected termination of the event search process, and then correct that cause.

KAVT1214-E

Making of the pipe was failed, and the search for events prior to execution cannot use. maintenance-information

An attempt to create an internal file used for the option for finding events before starting event monitoring has failed. This option cannot be used.

(S)
Cancels initialization of the option for finding events before starting event monitoring. The execution status of the Receive JP1 Event job with this option specified may be invalid.

(O)
Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently. Change the status of the event job that is placed in an invalid status. Alternatively, if you are using a macro variable for inheriting information received by an event job, generate the event that meets the monitoring condition again.

KAVT1217-I

An instance was established by the search for events prior to execution. (job-name, Event Arrived Time=arrival-time-of-event-satisfying-conditions)

As a result of the pre-execution event search, the system found an event that satisfies the job conditions.

(S)
Continues processing.

KAVT1226-W

Old JP1 events will be discarded because the number of preserved JP1 events issued during a search of pre-execution events has exceeded the threshold. (Seq No=serial-number-in-event-DB, Event ID=event-ID-basic-code, Event Arrived Time=event-arrival-time)

JP1 events will be discarded, beginning from the oldest one, because the number of held events generated during a search of pre-execution events has exceeded the threshold.

(S)
Deletes JP1 events generated during a search of pre-execution events, beginning from the oldest one, each time the threshold is exceeded, and continues processing.

(O)
Check whether all of the JP1 events having a serial number greater than the one indicated in serial-number-in-event-DB were detected. If any one of these JP1 messages was not detected, change the status of the job as required. Alternatively, if you are using the status-inherit option, again generate the event that meets the monitoring condition.

KAVT2001-I

The file monitoring process will now start.

The file monitoring process starts.

(S)
Starts the file monitoring process.

KAVT2004-I

The file (file-name) was created.

The file was created.

(S)
Continues processing.

KAVT2005-I

The file (file-name) was deleted.

The file was deleted.

(S)
Continues processing.

KAVT2006-I

The last modification time of file (file-name) has changed.

The last modification time of the file has changed.

(S)
Continues processing.

KAVT2007-I

The size of the file (file-name) has changed.

The size of the file has changed.

(S)
Continues processing.

KAVT2012-I

The file monitoring process will now end.

The file monitoring process terminates.

(S)
Terminates the file monitoring process.

KAVT2013-E

The name of the file to be monitored is not specified.

The name of the file to be monitored is missing.

(S)
Abnormally terminates the job.

(O)
Specify the name of the file to be monitored in the unit definition parameter for the ajsdefine command.

KAVT2014-E

The specified name of the file to be monitored is not a full path name.

The name of the file to be monitored is specified incorrectly.

(S)
Abnormally terminates the job.

(O)
Check the name of the file to be monitored, and then specify the full path name using the correct format.

KAVT2015-E

You cannot specify an asterisk (*) in a directory name.

A wildcard (*) cannot be specified in the directory name.

(S)
Abnormally terminates the job.

(O)
Check whether the wildcard (*) is specified in the directory name of the specified name of the file to be monitored.

KAVT2016-E

The specified name of the file to be monitored already exists as a directory.

The specified name of the file to be monitored already exists as a directory.

(S)
Abnormally terminates the job.

(O)
Specify the correct name of the file to be monitored, or delete the directory.

KAVT2017-W

The time-out period elapsed.

The time-out period expired. Cancels the job.

(S)
Specify the time-out period to cancel the job.

KAVT2018-W

A kill request was accepted.

The request to forcibly cancel a job is accepted. The job is forcibly canceled.

(S)
Forcibly cancel the job by the request.

KAVT2019-E

The file monitoring process ended. (maintenance-information)

The file monitoring process detected an error and terminated.

(S)
Terminated the file monitoring process because an error that prevents further processing occurred during processing. A Monitoring Files job cannot be monitored.

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT2020-I

The watching start option (file-name) is satisfied.

The monitoring start option is satisfied.

(S)
Continues processing.

KAVT2021-W

The memory for message output became insufficient. (file-name, maintenance-information)

Memory became insufficient. The message cannot be output to the detailed log.

(S)
Continues processing without outputting the message to the detailed log due to insufficient memory.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT2022-W

The open file check cannot execute because memory became insufficient. (file-name, maintenance-information)

Memory was insufficient. The system could not check whether another process opened the file to be monitored.

(S)
Checks again whether there is a process that has opened the file at the next execution interval. Establishment of the file monitoring event job is delayed until the check finishes.

(O)
If this message appears repeatedly, check whether there is sufficient memory for executing the program, and then try again to change the status of the file indicated in file-name.

KAVT2023-E

Memory became insufficient. (maintenance-information)

Memory became insufficient.

(S)
Checks whether the file status was updated again at the next execution interval. Alternatively, abnormally terminates the job.

(O)
Check whether there is sufficient memory for execution.
Use JP1/AJS3 - View to check for a Monitoring Files job that terminated abnormally. If you find a Monitoring Files job that terminated abnormally, re-register it.

KAVT2024-W

The file information could not be obtained. The file monitoring event may not have occurred. (file-name, maintenance-information)

An attempt to acquire the status of the file to be monitored has failed.

(S)
The current status of the file to be monitored was unknown. The system checks the status again at the next execution interval. Any change in the file status that is made before the next execution interval will not be detected.

(O)
Check the following:
  • Check whether there are sufficient resources.
  • Check whether the size of the file to be monitored is smaller than 2 gigabytes.
    To monitor a file equal to or greater than 2 gigabytes, specify the large file support option.
  • Make sure that the file to be monitored is not being updated.
If a change in the file status could not be detected, check the file status and then try again to change the status of the file indicated in file-name.

KAVT2025-E

You cannot specify 10 for the file monitoring interval.

Specify at least ten seconds for the monitoring interval.

(S)
Abnormally terminates the file monitoring job due to the invalid monitoring interval specified.

(O)
Check whether the conditions for specifying a 10-second or smaller monitoring interval are satisfied.

KAVT2026-E

The name of the file to be monitored cannot be obtained. (maintenance-information) (maintenance-information)

The name of the file to be monitored could not be obtained.

(S)
An error occurred while obtaining the name of the file to be monitored. Abnormally terminates the job.

(O)
Check the status of the directory or the file to be monitored.

KAVT2028-E

An attempt to start the file monitoring process failed. (maintenance-information) (maintenance-information)

The file monitoring process could not be started.

(S)
Terminates the file monitoring process because an error preventing further processing occurred.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether the system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT2029-E

An attempt to obtain pipe data failed. (maintenance-information) (maintenance-information)

The pipe data could not be received from the agent.

(S)
Terminates the file monitoring process because an error occurred during pipe processing with the agent.

(O)
Check the following, and then restart JP1/AJS3:
  • Check whether system resources are sufficient.
  • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2030-E

An attempt to send pipe data failed. (maintenance-information) (maintenance-information)

The pipe data could not be sent to the agent.

(S)
An error occurred while processing the pipe from the agent. Terminates the file monitoring process depending on the location where the error occurred.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the permission environment of the started user is correct.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2031-E

An error occurred during the operation of a file. (maintenance-information) (maintenance-information)

An error occurred while the file monitoring process is using the file.

(S)
Abnormally terminates the job depending on the location where the error occurred.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the permission environment of the started user is correct.
  • Check whether the directory created during installation of JP1/AJS3 was unintentionally deleted.
  • Check whether the following message was output in the same time zone: KAVT2034-W The status passing option file cannot be opened. The status passing cannot be executed. (file-name, maintenance-information).
    If this message was output, follow the instructions given by the KAVT2034-W message.
  • Check whether the size of the file to be monitored is smaller than 2 gigabytes.
    To monitor a file equal to or greater than 2 gigabytes, use the large file support option to specify monitoring of large files.

KAVT2032-E

An error exists in the definition contents of the file monitoring job. (maintenance-information) (maintenance-information)

An invalid definition is made for the file monitoring job.

(S)
Abnormally terminates the job because an invalid definition is made for the file monitoring job.

(O)
Check the definition. Then, retry.

KAVT2033-E

An attempt to set the next time monitoring failed. (maintenance-information) (maintenance-information)

The settings of monitoring for the next time could not be done.

(S)
An error occurred while making the settings of monitoring for the next time. Abnormally terminates the job.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the permission environment of the started user is correct.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT2034-W

The status passing option file cannot be opened. The status passing cannot be executed. (file-name, maintenance-information)

The file used for storing inherited status for the Monitoring Files job could not be opened. The status of the monitored file is not inherited. When JP1/AJS3 starts, the status of the file being monitored before JP1/AJS3 stopped is not inherited.

(S)
Does not attempt to read and use the status of the monitored file. When JP1/AJS3 starts, the system processes the Monitoring Files job without inheriting the status of the file being monitored before JP1/AJS3 stopped last time.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
  • For a cluster system, check whether the setting of the status passing option for a Monitoring Files job between the primary node and the secondary node matches.
  • For a cluster system that uses event jobs for DNS operation, check whether the setting for operation using the FQDN format between the primary node and the secondary node matches.
For details about the conditions for inheriting the status using the status passing option for the Monitoring Files job, see 7.6.2 Notes on the Monitoring Files job in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
If this message appears when the condition necessary for inheriting the status is not satisfied, this means that the file used for storing inherited status was deleted due to termination of the Monitoring Files job. Ignore the message and continue the operation.

KAVT2035-E

The name of the file to be monitored includes an invalid character. (file-name, maintenance-information)

An invalid character is specified in the name of the file to be monitored.

(S)
An invalid character is specified in the name of the file to be monitored. Abnormally terminates the job.

(O)
Check whether the name of the file to be monitored is created using the character codes that JP1/AJS3 can recognize.

KAVT2036-W

The open file check is impossible because the monitoring target file has no write permission. (file-name, maintenance-information, maintenance-information)

The system cannot perform an open file check for the file to be monitored because there is no permission to write into the file. The system does not assume that the file monitoring condition is satisfied.

(S)
The system does not assume that the file monitoring condition is satisfied. Continues processing.

(O)
Give the JP1/AJS3 service account the permission to write into the file to be monitored. In Windows, if the read-only checkbox for the file to be monitored is selected, deselect it.

KAVT2037-W

A macro variable exceeds 4096 bytes.

A file with the specified monitoring condition was updated, but the sum of the size of the values specified in macro variables exceeded 4,096 bytes.

(S)
The maximum amount of data that can be used for all macro variables per event is 4096 bytes (includes variable names). If the macro variable data exceeds 4096 bytes, the system uses only the first 4096 bytes and continues processing.

(O)
Check the execution status of the succeeding jobnet or job. If you find any problem, recheck the job definition.

KAVT2038-E

Monitoring can not be continued. Because the information on file of 2 Gbytes or more is contained in the status passing option file. (file-name)

Monitoring cannot be continued because the file used for storing the inherited status contains information about a file equal to or greater than 2 gigabytes.

(S)
Terminates the job abnormally.

(O)
Check whether the large file support option is set to no. If it is set to no, the large file support option may have been enabled before JP1/AJS3 stopped and the status passing option for the Monitoring Files job may have been enabled.
  • When the large file support option can be enabled:
    Enable the large file support option, restart JP1/AJS3, and then re-execute the job. Note, however, that the statuses of the files that were monitored before JP1/AJS3 stopped are not inherited.
    To enable the large file support option, specify yes for the LARGEFILEUSE environment setting parameter. For details about the environment setting parameters, see 2.9 Setting up JP1/AJS3 shared information in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
  • When the large file support option cannot be enabled:
    Make sure that the file indicated in file-name or any file under the directory specified using the wildcard characters is smaller than 2 gigabytes. Make sure that the size of the file to be monitored does not exceed 2 gigabytes during monitoring, and then re-execute the job. Note, however, that the statuses of the files that were monitored before JP1/AJS3 stopped are not inherited.
For details about the conditions for inheriting the status using the status passing option for the Monitoring Files job, see 7.6.2 Notes on the Monitoring Files job in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

KAVT3001-I

Mail was received.

Mail was received.

(S)
Continues processing.

KAVT3002-I

Mail could not be received.

Mail could not be received.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail.

KAVT3003-E

Mail could not be saved.

Saving mail was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to save files for the disk size or authorization.

KAVT3004-E

JP1/AJS2 Mail monitoring Service stopped. Stop processing.

The system stops processing since the JP1/AJS2 mail monitoring service stopped.

(S)
Cancels processing.

(O)
Use the message that is output previously to determine the cause of the error.

KAVT3005-E

JP1/AJS2 Mail monitoring process is terminated. Stop processing.

The system stops processing since the JP1/AJS2 mail monitoring service terminated.

(S)
Cancels processing.

(O)
Use the message that is output previously to determine the cause of the error.

KAVT3006-E

Initialization failed. (reason)

Initialization was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3012-E

MAPI could not be initialized. (reason)

MAPI used for sending and receiving email could not be initialized.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3014-E

Logon failed. (mapi_code=maintenance-information maintenance-information maintenance-information maintenance-information)

Logon was impossible.

(S)
Continues processing.

(O)
Check whether the profile name specified in setup is correct, and then retry.

KAVT3015-I

The result of logon. (mapi_code=maintenance-information maintenance-information maintenance-information maintenance-information)

This message indicates the results of logon to the profile.

(S)
Continues processing.

KAVT3016-E

Profile name used in send processing during logon is not within the definition.

A profile name used during logon is not defined for send processing.

(S)
Cancels processing.

(O)
Check whether the profile name specified in setup is correct, and then retry.

KAVT3017-E

During send processing, logon failed. (reason)

An attempt to log on to the mail system failed during email send processing.

(S)
Cancels processing.

(O)
If reason indicates insufficient memory, secure memory sufficient for execution, and then re-execute the job. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3019-E

The send processing could not be initialized. (reason)

Initialization of the email send processing could not be carried out.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3023-E

Mail could not be initialized. (reason)

An attempt to initialize the attributes of email to be sent has failed.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3025-E

The destination could not be set. (reason)

The email destination could not be set.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3027-E

Mail to be sent could not be created. (reason)

Creating mail to send was impossible.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3029-I

The text will be reprocessed because memory became insufficient.

The text will be reprocessed due to insufficient memory.

(S)
Continues processing.

KAVT3030-E

The text could not be reprocessed. (reason)

An error occurred during processing of the text file for the email.

(S)
Cancels processing.

(O)
Check the environment settings such as the path to the text file and the access permissions for the file.
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3033-I

The text was re-processed.

The text was re-processed successfully.

(S)
Continues processing.

KAVT3034-E

The attached file could not be defined. (reason)

An attached file for email could not be set.

(S)
Cancels processing.

(O)
Check the environment settings such as the path to the attached file and the access permissions for the file.
If reason indicates insufficient memory, secure memory sufficient for execution, and then re-execute the job. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVT3036-E

Sending failed. (reason)

Sending was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason shows mapi_code = xxxxxxxx (eight hexadecimal digits), see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting, and correct the problem, and then retry.

KAVT3038-E

The send processing could not be preprocessed.

Preprocessing a send was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3039-E

During send processing, logoff failed. (reason)

Logoff from the mail system during email send processing failed.

(S)
Cancels processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings.

KAVT3041-E

The profile name used in the reception processing during logon is not within the definition.

A profile name used during logon is not defined in the environment settings.

(S)
Cancels processing.

(O)
Check whether the profile name specified in setup is correct, and then retry.

KAVT3042-E

During reception processing, logon failed. (reason)

Logoff for reception processing was impossible.

(S)
Cancels processing.

(O)
Check whether the mail server has gone down or a profile is created correctly.

KAVT3044-E

The reception processing could not be initialized. (reason)

Initializing the reception processing was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3048-E

The list of received mail could not be acquired. (reason)

Acquiring a received mail list was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3050-E

During reception processing, mail could not be read.

Reading mail was impossible for reception processing.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail.

KAVT3051-E

Mail could not be read. (reason)

Reading mail was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3054-E

The text could not be acquired. (reason)

Acquiring the text was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail or the text is specified correctly. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3057-E

The data length of the text could not be acquired. (reason)

Acquiring the text data length was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. Also, check whether the text file is set correctly. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3060-E

The reception time could not be acquired.

Acquiring the reception time was impossible.

(S)
Cancels processing.

(O)
Contact the system administrator.

KAVT3061-E

The received mail could not be read. (reason)

Reading mail to receive was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3064-E

The list of attached files could not be acquired. (reason)

Acquiring an attached file list was impossible.

(S)
Cancels processing.

(O)
Check whether the attached file list is correct.

KAVT3066-E

During reception processing, the attached file could not be read.

Reading an attached file of mail was impossible for reception processing.

(S)
Cancels processing.

(O)
Check whether the disk space is sufficient.

KAVT3067-E

The attached file could not be read. (reason)

Reading an attached file was impossible.

(S)
Cancels processing.

(O)
Check whether the attached file is correct.

KAVT3070-E

The attached file could not be saved. (reason)

Saving an attached file was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to save the attached file. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3073-E

The attached file could not be saved.

Saving an attached file was impossible.

(S)
Continues processing.

(O)
Refer to the message output previously and determine the cause.

KAVT3074-E

The attached file could not be saved because it was an OLE object.

The file attached to email could not be saved because the file was an OLE object.

(S)
Continues processing.

(O)
The JP1/AJS3 mail linkage function cannot save attached files that include OLE objects. Accordingly, do not monitor reception of email to which such files are attached. Alternatively, do not specify the folder for saving attached files as a post-reception option for the email reception monitoring job.

KAVT3075-E

An error occurred during the saving of the attached file. (GetLastError=error-code file=attached-file-name)

An error occurred while a file attached to email was being saved.

(S)
Continues processing.

(O)
Take action according to the error code indicated in the message (return code from the Windows GetLastError() function).

KAVT3076-E

The opening-completed setting failed. (reason)

Setting a piece of opened mail was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3078-E

The text could not be saved.

The email text could not be saved.

(S)
Continues processing.

(O)
Check the environment settings such as the path for saving the text file, the disk space for saving the text file, and the access permissions for the file.
In addition, allocate sufficient memory for execution. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3079-E

The list file could not be created.

A list file containing a list of files attached to the email could not be created.

(S)
Continues processing.

(O)
Check the environment settings such as the path for saving the list file, the disk space for saving the list file, and the access permissions for the file.
In addition, allocate sufficient memory for execution. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT3080-E

During reception processing, a file could not be saved.

Saving a file was impossible for reception processing.

(S)
Continues processing.

(O)
Check whether the environment is set up to save a file.

KAVT3081-E

During reception processing, the icon could neither be sent nor received.

Communicating with the icons was impossible for reception processing.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive mail.

KAVT3083-E

Failed to delete mail. (reason)

Deleting mail was impossible.

(S)
Continues processing.

(O)
If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3085-E

The reception processing could not be pre-processed.

Pre-processing the reception processing was impossible.

(S)
Cancels processing.

(O)
Use the message that is output previously to determine the cause of the error.

KAVT3086-E

During reception processing, logoff failed. (reason)

Logoff was impossible for reception processing.

(S)
Cancels processing.

(O)
Check whether the environment is set up to log in the mail server. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.

KAVT3106-I

Mail reception will now start.

Mail reception starts.

(S)
Continues processing.

KAVT3107-I

Mail sending will now start.

Mail sending starts.

(S)
Continues processing.

KAVT3112-E

The parameter is specified incorrectly.

An invalid parameter is found.

(S)
Cancels processing.

(O)
Correct the invalid parameter, and then retry.

KAVT3200-I

Start process of controlling MAPI (Send).

The MAPI send control process starts.

(S)
Continues processing.

KAVT3201-I

Start process of controlling MAPI (Receive).

The MAPI receive control process starts.

(S)
Continues processing.

KAVT3202-I

End process of controlling MAPI (Send).

The MAPI send control process terminates.

(S)
Continues processing.

KAVT3203-I

End process of controlling MAPI (Receive).

The MAPI reception control process terminates.

(S)
Continues processing.

KAVT3204-E

Failed to create a temporary file. file=file-name GetLastError=GetLastError-number

A temporary file to be used for mail system linkage could not be created.

(S)
Cancels processing.

(O)
Use file=file-name GetLastError=GetLastError-number to determine the cause of the error that prevented the indicated file from being created.

KAVT3205-E

Failed to read a temporary file. file=file-name GetLastError=GetLastError-number

A temporary file to be used for mail system linkage could not be read.

(S)
Cancels processing.

(O)
Determine the cause of the error that prevented the file indicated in file=file-name GetLastError=GetLastError-number from being read.

KAVT3206-E

Failed to create a folder. folder-name

A folder could not be created.

(S)
Cancels processing.

(O)
Determine the cause of the error that prevented the folder indicated shown in folder-name from being created.

KAVT3207-W

The mail data was too long, so it was truncated.(maintenance-information)

Because the data size specified in the definition of the email sending job was too long, the excess part was truncated. maintenance-information indicates the truncated part of the data as follows:

  • Title
    The title was truncated.
  • Text
    The text was truncated.

(S)
Truncates the excess part, and continues processing of the email sending job.

(O)
See 15.4.27 Detailed Definition - [Send Mail] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, and 15.4.28 Detailed Definition - [Send Mail] - [Attached File] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, and check the maximum number of bytes that can be used for information in the definition of email sending jobs.

KAVT3210-W

The send destination address was not found. (maintenance-information)

The specified email address was not found in the send destination mail system. Alternatively, the mail system in which the email address has been registered was not found.

maintenance-information indicates the number of email addresses that are specified in the email sending job but were not found.

(S)
Ignores the email address that was not found, and continues processing.

(O)
Check whether the specified email address was registered in the send destination mail system, and whether the mail system is running and ready for communication.
For the send destination email address, check whether email can be sent and received by using Microsoft Outlook alone without using JP1/AJS3, and whether a dialog box that requires a response from the user appears during sending or receiving.
If sending or receiving email is not possible or if such a dialog box appears, check and, if necessary, correct the following settings in the profile so that email can be sent and received. Then execute the email sending job.
  • Check whether the correct mail system name was specified for the send destination.
  • Check whether the specified email account has been registered in the connected mail system.
  • Check whether the correct password is set for the email account.
  • Check whether the profile settings are correct.

KAVT3211-W

The send destination address is ambiguous. maintenance-information

The email sending job cannot identify some of the specified email addresses.

(S)
Deletes the unidentifiable email addresses from the destinations list and continues processing of the email sending job.

(O)
Check whether the specified email addresses are correct by referring to the indicated maintenance information (the number of addresses that cannot be identified).
In addition, export the property information of all accounts registered on the mail server to a file. Then, using each of the specified email addresses as a search string, search the file to check whether the email address is the same as another property (such as a user name or office name).
For details on how to export the property information about accounts registered on the mail server, see the documentation for the mail server software.

KAVT3212-E

None of the specified mail addresses exist or all the mail addresses were specified incorrectly, so sending of the mail will now stop. (mapi_code=MAPI-code)

Sending email is canceled for one of the following reasons:

  • No email addresses are specified for the email sending job.
  • None of the specified email addresses can be found in the send destination mail system.
  • None of the mail systems in which the specified email addresses have been registered can be found.

(S)
Cancels processing.

(O)
If email addresses are not specified for the email sending job, specify them.
Check whether the specified email address was registered in the send destination mail system, and whether the mail system is running and ready for communication.
For details about the contents of mapi_code, see 2.10(4) Mail transmission job or mail reception monitoring job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
For the send destination email address, check whether email can be sent and received by using Microsoft Outlook alone without using JP1/AJS3, and whether a dialog box that requires a response from the user appears during sending or receiving.
If sending or receiving email is not possible or if such a dialog box appears, check and, if necessary, correct the following settings in the profile so that email can be sent and received. Then execute the email sending job.
  • Check whether the correct mail system name was specified for the send destination.
  • Check whether the specified email account has been registered in the connected mail system.
  • Check whether the correct password is set for the email account.
  • Check whether the profile settings are correct.

KAVT3268-I

Sent mail.

Mail was sent.

(S)
Continues processing.

KAVT3271-E

Mail could not be sent.

Sending mail was impossible.

(S)
Cancels processing.

(O)
Take action according to the error or warning message about email transmission that was output immediately before this message.

KAVT3273-I

Processing of mail sending will now start.

The mail transmission starts.

(S)
Continues processing.

KAVT3274-I

Processing of mail sending will now end.

The mail transmission terminates.

(S)
Terminates processing.

KAVT3275-E

The environment variable is specified incorrectly. (specified-data)

The environment variables are specified incorrectly.

(S)
Cancels processing.

(O)
Check the system resources, and then retry.

KAVT3276-E

The data is specified incorrectly. (specified-data)

Data is specified incorrectly in the definition of the email sending job.

(S)
Cancels processing.

(O)
In the definition of the email sending job, check the part indicated in specified-data, including the text file of the email, attached files, or list file of attached files.

KAVT3277-E

A required item is missing.

Mandatory items are missing.

(S)
Cancels processing.

(O)
Specify necessary items in the mail send definition, and then retry.

KAVT3278-E

The parameter is specified incorrectly. (specified-data)

A parameter is specified incorrectly.

(S)
Cancels processing.

(O)
Correct the invalid parameter, and then retry.

KAVT3279-E

The configuration definition could not be read. (return-code)

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
Also check whether Administrator permissions are set for the following accounts:
  • Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped
  • Account of the OS user when an OS user is specified for the account of the JP1/AJS3 service
  • Account of the OS user set for the JP1/AJS3 Mail service when the mail linkage function is used on the service
If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3280-E

You are not authorized to access the configuration definition. (return-code)

There is no authorization to access the configuration definition. If you send mail, try sending with the authorization that can refer to the JP1/AJS3 information.

(S)
Cancels processing.

(O)
Try access with the administrator's authorization.

KAVT3281-E

The specified key does not exist in the configuration definition. (return-code)

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
Also check whether Administrator permissions are set for the following accounts:
  • Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped
  • Account of the OS user when an OS is specified for the account of the JP1/AJS3 service
  • OS user account set in the JP1/AJS3 Mail service when the mail linkage function is used on the service.
If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3282-E

An unexpected error occurred. (return-code-of-GetLastError-function)

An unexpected error occurred in the email sending job.

(S)
Cancels processing.

(O)
Take action according to the message that was output immediately before this message, or by checking the return code of the Windows GetLastError() function.

KAVT3283-E

The process will now stop because the mail monitoring process or service terminated.

Processing is stopped due to the mail monitoring process or service halt.

(S)
Cancels processing.

(O)
Use the message that is output previously to determine the cause of the error.

KAVT3284-E

Contact with the mail monitoring process or service failed. (return-code-of-GetLastError-function)

Contacting the mail monitoring process or service was impossible.

(S)
Cancels processing.

(O)
Check whether the JP1/AJS3 mail monitoring process or the service is running.

KAVT3285-E

Communication with the mail monitoring process or the service failed.

Communication with the mail monitoring process or service was impossible.

(S)
Cancels processing.

(O)
Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3286-E

Communication of mail information failed.

Communicating the mail information was impossible.

(S)
Cancels processing.

(O)
Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3287-E

The communication pipe could not be created.

Creating a communication pipe was impossible.

(S)
Cancels processing.

(O)
Check whether the JP1/AJS3 mail monitoring process or service is running.

KAVT3288-E

The thread could not be created. (return-code-of-GetLastError-function)

The email sending job has failed to create a thread.

(S)
Cancels processing.

(O)
Check the return code of the Windows GetLastError() function, and then take appropriate action.
If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3289-E

Fail to acquire completion status of thread. (return-code-of-GetLastError-function)

The email sending job has failed to acquire the end status of the thread.

(S)
Cancels processing.

(O)
Check the return code of the Windows GetLastError() function, and then take appropriate action.
If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3290-E

Memory became insufficient.

There is not enough memory.

(S)
Cancels processing.

(O)
Allocate sufficient memory to execute, and then retry.

KAVT3291-E

JP1/AJS2 mail monitoring process or service is not running. (return-code-of-GetLastError-function)

The JP1/AJS3 mail monitoring process or service is not running.

(S)
Cancels processing.

(O)
Start the JP1/AJS3 mail monitoring process or service.

KAVT3292-E

The installation path for JP1/AJS2 could not be acquired. (return-code)

Acquiring a JP1/AJS3 installation path was impossible.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly. Alternatively, check whether the user who executes the email sending job has permission to reference the registry.

KAVT3293-E

An error was detected in the mail monitoring process or service. (return-code-of-MAPI-function)

An error was detected in the mail monitoring process or service.

(S)
Cancels processing.

(O)
Check the error details by comparing return-code-of-MAPI-function with the following MAPI codes, and then take action. Also see the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
  • 8004010D: The disk space is insufficient.
  • 8004010E: The resources are insufficient.
  • 80040111: Logon failed.
  • 80040115: A network error occurred.
  • 80040116: A disk I/O error occurred.
  • 80040124: The mail account is invalid.
  • 8004010F: The destination mail address is not found.
  • 80040607: The destination mail address is not found.
  • 80040700: The destination mail address is incomplete.

KAVT3294-E

Operating environment of mail linkage is invalid. (definition=UNIX)

An invalid character has been used in the environment settings for the mail linkage function.

(S)
Cancels processing.

(O)
Specify use of the desktop or service in the environment setting parameter used for mail system linkage. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT3295-E

No environment has been defined.

The mail linkage is not set up.

(S)
Cancels processing.

(O)
Specify use of the desktop or service in the environment setting parameter used for mail system linkage. Then, start the mail monitoring process or mail service, and execute the email sending job. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT3296-E

The environment settings include an invalid character. (definition=execution-mode)

An invalid character is used in the environment settings for the mail linkage function.

(S)
Cancels processing.

(O)
Check the contents indicated in execution-mode in the message. Then, on the Mail Linkage page in the Manager Environment Settings dialog box or Agent Environment Settings dialog box, specify the setting requiring use of the mail linkage function on the desktop or on the service.

KAVT3297-E

The length of the text exceeds the maximum.

The length of the text exceeded the upper limit.

(S)
Cancels processing.

(O)
Check the upper limit of the text. For details about the upper limit, see 15. Windows and Dialog Boxes in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVT3298-E

The folder specified for storing mail text files does not exist. (folder-name)

A folder that stores the text file does not exist.

(S)
Cancels processing.

(O)
Check whether a storage folder for the file exists.

KAVT3299-E

The folder specified for storing the attached files does not exist. (folder-name)

A folder that stores the attached files does not exist.

(S)
Cancels processing.

(O)
Check whether a storage folder for the file exists.

KAVT3300-E

The folder specified for storing the list of attached files does not exist. (folder-name)

A folder that stores the attached file lists does not exist.

(S)
Cancels processing.

(O)
Check whether a storage folder for the file exists.

KAVT3301-E

The specified mail text file does not exist. (file-name)

A text file does not exist.

(S)
Cancels processing.

(O)
Check whether the specified file exists.

KAVT3302-E

The text file could not be read. (file-name)

Reading a text file was impossible.

(S)
Cancels processing.

(O)
Check whether the specified file is correct.

KAVT3303-E

The specified attached file or files do not exist.

The file or attached file list does not exist.

(S)
Cancels processing.

(O)
Check whether the specified file exists.

KAVT3304-E

The attached files or list of attached files could not be read.

Reading the attached file or attached file list was impossible.

(S)
Cancels processing.

(O)
Check whether the specified file is correct.

KAVT3401-I

Start JP1/AJS2 Mail monitor process.

The JP1/AJS3 mail monitoring process is started.

(S)
Continues processing.

KAVT3402-I

The JP1/AJS2 mail monitoring process started.

The JP1/AJS3 mail monitoring process has started.

(S)
Continues processing.

KAVT3403-I

Start JP1/AJS2 Mail monitoring service.

The JP1/AJS3 mail monitoring process is started.

(S)
Continues processing.

KAVT3404-I

The JP1/AJS2 mail monitoring service started.

The JP1/AJS3 mail monitoring service has started.

(S)
Continues processing.

KAVT3405-I

The JP1/AJS2 mail monitoring process will now end.

The JP1/AJS3 mail monitoring process stops.

(S)
Continues processing.

KAVT3406-I

JP1/AJS2 Mail monitoring process stopped.

The JP1/AJS3 mail monitoring process stopped.

(S)
Cancels processing.

KAVT3407-I

The JP1/AJS2 mail monitoring service will now end.

The JP1/AJS3 mail monitoring service stops.

(S)
Continues processing.

KAVT3408-I

JP1/AJS2 Mail service stopped.

The JP1/AJS3 mail monitoring service was stopped.

(S)
Cancels processing.

KAVT3409-E

The environment definition could not be read.

The settings of the environment setting parameters to be used for mail system linkage cannot be read from the system.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
Also check whether Administrator permissions are set for the following accounts:
  • Account of the OS user to whom the JP1 user who logs in to JP1/AJS3 - View is mapped
  • Account of the OS user when an OS user is specified for the account of the JP1/AJS3 service
  • Account of the OS user set for the JP1/AJS3 Mail service when the mail linkage function is used on the service
If you cannot check the above items, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVT3420-W

The data set for inheritance information (macro-variable-name-of-truncated-data) is too long and was truncated to maximum-macro-variable-size bytes.

The data set for inheritance information was greater than the maximum size of the macro variable. The data was truncated to the maximum size.

(S)
Continues processing.

(O)
Check whether the subsequent job operates correctly.

KAVT3451-I

The mail linkage communication process will now start.

The mail linkage communication process starts.

(S)
Continues processing.

KAVT3452-I

The mail linkage communication process started.

The mail linkage communication process has started.

(S)
Continues processing.

KAVT3453-I

The mail linkage communication process stopped.

The mail linkage communication process has stopped.

(S)
Terminates processing.

KAVT3454-I

Mail reception monitoring will now start.

Monitoring of mail reception starts.

(S)
Continues processing.

KAVT3455-E

Mail reception monitoring will now stop.

Mail reception monitoring stops.

(S)
Continues processing.

(O)
Refer to the error message output previously and determine the cause of the error.

KAVT3456-I

The reception of messages that satisfy the conditions was confirmed.

The reception of messages that satisfy the conditions was confirmed.

(S)
Continues processing.

KAVT3457-I

Monitoring of mail reception will now end because the time-out period elapsed.

Monitoring of mail reception terminates because the time-out period has elapsed.

(S)
Continues processing.

KAVT3458-I

Method of mail monitor is "JP1/AJS2 Mail Service" -or- "JP1/AJS2 Mail Process".

This message shows the method of mail monitoring.

(S)
Continues processing.

KAVT3459-E

Method of mail monitor is not established. Please set up environment.

Check the environment definition, and then retry.

(S)
Cancels processing.

(O)
Check the environment definition, and then retry.

KAVT3460-E

Cannot recognize method of mail monitoring. Please set up environment again. (settings)

An invalid character was used in the environment settings for the mail linkage function.

(S)
Cancels processing.

(O)
Check the information indicated in settings in the message. Then, specify use of the desktop or service in the environment setting parameters used for mail system linkage. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT3461-W

An error occurred during creation of a macro variable.

An error occurred while creating a macro variable.

(S)
Continues processing.

(O)
Refer to the error message output previously, and determine the cause of the error.

KAVT3462-W

A macro variable exceeds 4096 bytes. Some macro variables could not be created.

The macro variable exceeded 4,096 bytes. Some macro variables could not be created.

(S)
Continues processing.

(O)
Set a macro variable that does not exceed 4,096 bytes.

KAVT3463-E

The platform is specified incorrectly.

A platform is specified incorrectly.

(S)
Cancels processing.

(O)
Check the platform, and then retry.

KAVT3464-W

The mail monitoring process or service is not running.

The mail monitoring process or service is not running.

(S)
Cancels processing.

(O)
Start the mail monitoring process or service.

KAVT3465-I

Start of the mail monitoring process or service was confirmed.

Start of the mail monitoring process or service was confirmed.

(S)
Continues processing.

KAVT3466-E

The definition of the mail monitoring job is invalid.

The email reception monitoring job is defined incorrectly.

(S)
Cancels processing.

(O)
Correct the definitions of the email reception monitoring job, and then retry.

KAVT3467-E

Memory became insufficient.

A memory shortage occurred.

(S)
Cancels processing.

(O)
Allocate sufficient memory for execution, and then retry.

KAVT3468-E

An event for canceling registration of a job could not be created.

Creating an event for canceling job registration was impossible.

(S)
Cancels processing.

(O)
Check the status of the event server.

KAVT3469-E

The option for not linking mail is selected. Mail reception will not be monitored.

The mail linkage is not set up.

(S)
Cancels processing.

(O)
Specify use of the desktop or service in the environment setting parameter used for mail system linkage. Then, start the mail monitoring process or mail service, and execute the email reception monitoring job. For details, see 2.2.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT3473-E

The count of the mail monitoring job is over a max job's count. (Max job's count=maximum-registration-count)

The number of registered email reception monitoring jobs has exceeded the limit value.

(S)
Cancels processing.

(O)
If necessary, unregister the email reception monitoring jobs so that the number of registered jobs is below the limit value.
For details about the limit values, see the cautionary notes in 2.5.1(1) Judging whether received email satisfies the monitoring conditions in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVT3499-E

An unexpected error occurred. (maintenance-information)

An error occurred during inter-process communication of the email reception monitoring job.

(S)
Cancels processing.

(O)
Take action according to the message that was output immediately before this message or by checking the maintenance information (return code of the Windows GetLastError function).

KAVT3501-I

The mail reception process will now start.

The mail reception process starts.

(S)
Continues processing.

KAVT3502-I

The mail reception process will now end.

The mail reception process terminates.

(S)
Terminates processing.

KAVT3504-E

Failed to analyze job data. (DB-data) (error-code-of-function)

A failure occurred in the function that analyzes job data.

(S)
Cancels processing.

(O)
Check whether the job is defined correctly.

KAVT3512-E

Memory became insufficient. (maintenance-information)

A memory shortage occurred.

(S)
Cancels the process without enough memory and continues processing.

(O)
Check the system for free space.

KAVT3513-E

Failed to get Pipe Data. (maintenance-information) (maintenance-information)

Acquiring the pipe data from the agent was impossible.

(S)
Cancels the pipe processing. Terminate the mail reception process depending on the place of occurrence.

(O)
Check whether:
  • The system resources are sufficient.
  • The permission environment of the started user is correct.
  • The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3514-E

Failed to send Pipe Data. (maintenance-information) (maintenance-information)

Sending the pipe data to the agent was impossible.

(S)
Cancels piping and continues processing. The job execution status may be incorrect.

(O)
Check whether:
  • The system resources are sufficient.
  • The permission environment of the started user is correct.
  • The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3515-E

An auxiliary file could not be opened. (maintenance-information) (maintenance-information)

Unable to open an auxiliary file from the agent.

(S)
Abnormally terminates the job request.

(O)
Check whether:
  • The system resources are sufficient.
  • The permission environment of the started user is correct.
  • The directory created during installation of JP1/AJS3 is not deleted inadvertently.

KAVT3519-W

A macro variable exceeds 4096 bytes.

The macro variable exceeded 4,096 bytes after conversion.

(S)
Since the macro variable exceeded 4,096 bytes after conversion, rounds down the succeeding macro variables and continues processing.

(O)
The part of the macro variable exceeding 4,096 bytes is not passed. Check the macro. If you find any problem, review the job definition.

KAVT3520-E

Failed to start. (maintenance-information) (maintenance-information)

Preparing the process startup was impossible.

(S)
Terminates the mail reception process.

(O)
Restart the mail reception process.

KAVT3521-W

An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information)

An error occurred while analyzing a macro variable.

(S)
Does not create a macro variable and abnormally terminates the job.

(O)
Re-execute the job as required.

KAVT3522-W

Information could not be output. (maintenance-information) (maintenance-information)

Outputting the information to the standard error output was impossible.

(S)
Does not output the information due to insufficient memory and continues processing.

(O)
Check the system for free space.

KAVT3523-W

Forced termination was accepted.

The system accepted a kill request. The job is forcibly terminated.

(S)
Accepts the kill request and forcibly terminates the job.

KAVT3524-W

Cancel time up.

The timeout period had elapsed. The job is canceled.

(S)
Cancels the job due to the specified timeout period being elapsed.

KAVT3525-W

Mail Lock File(maintenance-information)could not be created.( maintenance-information)( maintenance-information)

An error occurred during creation of the lock file used for locking files.

(S)
Cancels processing, and continues processing after a monitoring interval elapses.

(O)
If this message is output more than once, determine the cause of the error from the maintenance information.

KAVT3526-W

Mail File(maintenance-information)can not be locked, because the file is being used by another application.

The lock processing failed because the monitored mail file was already locked.

(S)
Cancels processing, and continues processing after a monitoring interval elapses.

KAVT3528-W

Mail File(maintenance-information)could not be opened.( maintenance-information)

The mail file could not be opened.

(S)
Cancels the processing, and continues processing.

(O)
Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3530-E

A mail lock file (lock-file-name) could not be released. (maintenance-information) (maintenance-information, system-error-message)

Releasing the lock file was impossible.

(S)
Cancels processing.

(O)
Collect data about this internal error and then contact the system administrator.

KAVT3531-W

Mail File(maintenance-information)could not be read.( maintenance-information)( maintenance-information)

The mail file could not be read.

(S)
Cancels the processing, and continues processing.

(O)
Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3532-W

Mail File(maintenance-information)could not be deleted.( maintenance-information)( maintenance-information)

A mail file could not be deleted.

(S)
Cancels the processing, and continues processing.

(O)
Determine the cause of the error from the maintenance information, and take appropriate action.

KAVT3533-W

A mail file (mail-file-name) could not be written. (maintenance-information) (maintenance-information) (maintenance-information, system-error-message)

Writing a mail file was impossible.

(S)
Cancels the process without enough memory and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being written. Then take action.

KAVT3534-E

Mail watching ended. (maintenance-information) (maintenance-information)

The mail reception process detected an error and terminated.

(S)
Terminates the mail reception process because an irrecoverable error occurred during the processing.

(O)
Take action according to the message that is output previously. Restart JP1/AJS3 to ensure correct operation.

KAVT3538-W

The environment definition could not be read. (maintenance-information) (maintenance-information)

Reading an environment definition was impossible.

(S)
Continues processing.

(O)
Check the content of the environment definition, and then restart JP1/AJS3 and reload.

KAVT3539-W

No monitoring user name is specified.

A monitoring user name is not specified in the environment definitions.

(S)
Continues processing.

(O)
Redefine the environment definitions.

KAVT3540-W

No mail file directory is specified.

A mail file directory is not specified in the environment definitions.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3541-W

The file for saving mail is not specified.

A mail save file is not specified in the environment definition.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3542-W

The monitoring user name exceeds (specified-byte-length) bytes.

The monitoring user name in the environment definition exceeds the maximum byte length.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3543-W

The mail file directory name exceeds (specified-byte-length) bytes.

The mail file directory name in the environment definition exceeds the maximum byte length.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3544-W

The name of the file for saving mail exceeds (specified-byte-length) bytes.

The length of the mail for saving file names in the environment exceeds the maximum byte length.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3545-W

No directory is specified for backing up mismatched mail.

A mismatched mail save directory is not specified in the environment definition.

(S)
Continues processing.

(O)
Redefine the environment definition if required.

KAVT3546-W

The name of the directory for backing up mismatched mail exceeds (specified-byte-length) bytes.

The mismatched mail save directory name in the environment definition exceeds the maximum byte length.

(S)
Continues processing.

(O)
Redefine the environment definition.

KAVT3547-W

Information about mail file (maintenance-information) could not be obtained: maintenance-information (maintenance-information, system-error-message)

Obtaining the file information for the mail files was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file information from being obtained. Then take action.

KAVT3548-W

The input file for the mail filtering application could not be opened: (maintenance-information, system-error-message)

Opening an input file was impossible in the mail filter applications.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3549-W

The input file for the mail filtering application could not be written to: (maintenance-information, system-error-message)

Writing an input file was impossible in the mail filter applications.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3550-W

The output file from the mail filtering application could not be read: (maintenance-information, system-error-message)

Reading an input file was impossible from the mail filter applications.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being read. Then take action.

KAVT3551-E

An error occurred in the mail filtering application. Return value: return-code-of-mail-filter-application

An error occurred in the internal mail filter applications and the mail was not converted correctly.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Check the mail filtering application.

KAVT3552-W

Mail could not be taken out of the mail file.

Fetching the mail from the mail file of the monitoring user was impossible.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

KAVT3553-W

The inherited mail file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening an inheritance mail file was impossible.

(S)
Terminates the corresponding job without inheritance information.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3554-W

The inherited mail file (file-name) could not be written to: (maintenance-information, system-error-message)

Writing an inheritance mail file was impossible.

(S)
Terminates the job without inheritance information.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3555-W

The inherited mail file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing an inheritance mail file was impossible.

(S)
Terminates the job without inheritance information.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed, and then take action. Re-execute the job if needed.

KAVT3556-W

The file for saving mail (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail save file was impossible.

(S)
Terminates the job and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action. Re-execute the job if needed.

KAVT3557-W

The file for saving mail (file-name) could not be written to: (maintenance-information, system-error-message)

Writing a mail save file was impossible.

(S)
Terminates the job and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action. Re-execute the job if needed.

KAVT3558-W

The file for saving mail (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a mail save file was impossible.

(S)
Terminates the job and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3559-E

The mail filtering application could not be called: (maintenance-information, system-error-message)

Calling a mail filter application was impossible.

(S)
Continues processing.

(O)
Check the mail filter application.

KAVT3560-W

The output file from the mail filtering application could not be opened: (maintenance-information, system-error-message)

Opening an output file in the mail filter applications was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3561-W

File information about the mail filtering application could not be obtained: (maintenance-information, system-error-message)

Acquiring the output file information in the mail filter applications was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file information from being obtained. Then take action.

KAVT3562-E

The file output from the mail filtering application contains no mail.

No mail is found in the output file of the mail filter applications.

(S)
Continues processing.

(O)
Check the mail filter application.

KAVT3563-W

Unrecognized data exists at the beginning of the mail file.

There is unrecognizable data found at the beginning of a mail file.

(S)
Leaves unrecognizable data in the mail and continues processing.

(O)
Stop JP1/AJS3 as required and then delete unrecognizable data.

KAVT3564-W

The mail file has no recognizable data.

Only unrecognizable data is found in the monitoring mail file.

(S)
Leaves unrecognizable data in the mail and continues processing.

(O)
Stop JP1/AJS3 as required and then delete unrecognizable data.

KAVT3565-W

The arrival date of the mail cannot be confirmed.

No arrival data is found for the mail.

(S)
Continues processing.

(O)
Stop JP1/AJS3 and then check the mail system.

KAVT3566-W

Mail File could not be compressed.: maintenance-information (maintenance-information, system-error-message)

Compressing the mail file was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of unsuccessful rewriting. Then take action.

KAVT3567-W

The mail reception list file (file-name) could not be created.

Creating a mail reception list file was impossible.

(S)
Continues processing.

(O)
Take action according to the message that is output previously.

KAVT3568-W

The mail reception list file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail reception list file was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3569-W

The mail reception list file (file-name) could not be written to: (maintenance-information, system-error-message)

Writing a mail reception list file was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the mail reception list from being written. Then take action.

KAVT3570-W

The mail reception list file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a mail reception list file was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3571-W

The error mail file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a mail file for failures was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3572-W

The error mail file (file-name) could not be written: (maintenance-information, system-error-message)

Writing an error mail file was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3573-W

The error mail file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing an error mail file was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3574-I

Mail was saved in the error mail file (file-name).

Mail was saved in the error mail file.

(S)
Continues processing. Depending on the location where the error occurred, the system cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Take action according to the message that is output previously.

KAVT3575-W

The file for storing mismatched mail (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a save file for mismatched mail was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being opened. Then take action.

KAVT3576-W

The file for storing mismatched mail (file-name) could not be written: (maintenance-information, system-error-message)

Writing a save file for mismatched mail was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.

KAVT3577-W

The file for storing mismatched mail (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a save file for mismatched mail was impossible.

(S)
Cancels processing, waits for the monitoring interval and continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the file from being closed. Then take action.

KAVT3578-W

The file for storing mismatched mail (file-name) cannot be locked, because another application is using the file.

Since the mismatched mail save file is locked, the lock processing failed.

(S)
Cancels processing, waits until the next monitoring interval, and continues processing.

KAVT3580-I

The mail data table could not be created.

The mail data table for retrieving monitored mail and job information could not be created.

(S)
Cancels processing, waits for the monitoring intervals, and continues processing.

(O)
Take action according to the message that is output previously.

KAVT3585-W

No monitoring interval is specified.

The environment definition does not specify the monitoring intervals.

(S)
Assumes ten minutes.

(O)
Redefine the environment definition as required.

KAVT3586-W

Specify a monitoring interval from 1 to 1,440.

The monitoring interval for the environment definition exceeds the range of 1 to 1,440.

(S)
Assumes ten minutes.

(O)
Redefine the environment definition as required.

KAVT3587-W

The inherited mail file could not be created. (file-name)

Creating an inheritance mail file was impossible.

(S)
Does not create the inheritance mail file, but terminates the job.

(O)
See the mail monitoring log file.

KAVT3588-W

The directory could not be created. (directory-name) (maintenance-information)

Creating a directory was impossible.

(S)
Continues processing.

(O)
Use maintenance information and system error message to determine the cause of the error that prevented the directory from being created. Then take action.

KAVT3593-W

The directory to store inherited information is not specified.

A storage directory for inheritance information is not specified to the environment definitions.

(S)
Assumes an inheritance information directory in units of a logical host.

(O)
Redefine the environment definition as required.

KAVT3594-I

Mail will be monitored.

Mail will be monitored in response to the request from the job.

(S)
Continues processing.

KAVT3595-W

Mail cannot be monitored.

Mail cannot be monitored in the current state.

(S)
Continues processing and accepts the job request.

(O)
Check the environment definition, and then restart JP1/AJS3.

KAVT3596-E

Main loop of a mail reception process failed. (maintenance-information)

The main processing of a mail reception process could not start.

(S)
Terminates the mail reception process.

(O)
Check whether the system resources are sufficient and whether the permission environment of the started user is correct, and then retry.

KAVT3597-E

An error occurred during the access of the file(file-name). (maintenance-information) (maintenance-information) (maintenance-information, system-error-message)

An error occurred during the access to the file.

(S)
Continues processing.

(O)
Check whether:
  • The maintenance information provides a file.
  • The system resources are sufficient.
  • The permission environment of the started user is correct.

KAVT3598-E

An error occurred during mail reception monitoring: maintenance-information maintenance-information maintenance-information maintenance-information

An error occurred during monitoring of mail reception.

(S)
Continues processing.

(O)
Collect the data about the internal error, and then contact the system administrator.

KAVT3700-I

jposendml command will now start.

The mail sending command starts.

(S)
Continues processing.

KAVT3701-I

sendmail will now start.

sendmail starts.

(S)
Continues processing.

KAVT3702-I

Mail was sent normally.

Mail was sent normally.

(S)
Terminates processing.

KAVT3703-I

temporary file:("temporary-file-name")

The working file name was created.

(S)
Continues processing.

KAVT3704-E

The command was interrupted.

The command was interrupted.

(S)
Cancels processing.

(O)
Determine the cause of the interruption by referring to another output message, and then retry.

KAVT3705-E

Usage: jposendml [-p platform-name]

Sending mail is specified incorrectly.

(S)
Cancels processing.

(O)
Correctly specify sending mail.

KAVT3706-E

A temporary file could not be created. (file: "temporary-file-name")

Creating a temporary file for sending mail was impossible.

(S)
Cancels processing.

(O)
Check that there is sufficient disk spaces, and then retry.

KAVT3707-E

The specified platform is invalid. (Platform: "platform-name")

The specified platform is invalid.

(S)
Cancels processing.

(O)
Check the definitions and re-execute the job.

KAVT3708-E

No platform is specified.

No platform is specified.

(S)
Cancels processing.

(O)
Check the definitions and re-execute the job.

KAVT3709-W

The title was too long, so it was truncated.

An item name for sending it was truncated because it is too long.

(S)
Continues processing.

(O)
Check the JP1/AJS3 job definitions.

KAVT3710-E

The mail-destination address is invalid: ("mail-destination-address")

An invalid mail destination address is specified.

(S)
Cancels processing.

(O)
Check the definitions and then re-execute the job.

KAVT3711-E

No mail-destination address is specified.

A mail destination address is not defined.

(S)
Cancels processing.

(O)
Check the definitions and then re-execute the job.

KAVT3712-E

The mail-destination address exceeds the maximum length: ("mail-destination-address")

You specified the mail send destination address with more than 256 bytes.

(S)
Cancels processing.

(O)
Check the definitions and then re-execute the job.

KAVT3714-E

No mail text file was found.

A mail text file was specified, but the file does not exist.

(S)
Cancels processing.

(O)
Check whether the file exists.

KAVT3715-E

The mail text file cannot be read.

A mail text file name was specified, but the file could not be read.

(S)
Cancels processing.

(O)
Check whether the file can be read.

KAVT3716-W

Mail text was too long, so it was truncated.

Mail text was too long, so it was truncated.

(S)
Continues processing.

(O)
Check the length and contents of text you want to send.

KAVT3717-E

sendmail command caused an error: (error: message-for-sendmail-command)

An error occurred while using the sendmail command for sending mail.

(S)
Cancels processing.

(O)
Use the message of the sendmail command to determine the cause of the error. Re-execute the job if needed.

KAVT3718-I

Mail has been queued.

Mail is not sent immediately. It is queued and then delivered.

(S)
Sends mail normally.

(O)
If mail is not sent after a while, check that there are sufficient disk spaces, and then retry.

KAVT3719-E

sendmail returned an unexpected error. (error: return-code-of-sendmail-command)

The sendmail command for sending mail returned an unexpected error.

(S)
Cancels processing.

(O)
Use the return code of the sendmail command to determine the cause of the error. Re-execute the job if needed.

KAVT3720-E

A required program is missing. (program: program-name)

A program necessary for sending mail does not exist. Check whether the sendmail command is provided.

(S)
Cancels processing.

(O)
Check that there are necessary programs for sending mail, and then set up the environment that allows correct operations.

KAVT3721-E

Message Put error. (error: error-code-at message-output, message-whose-output-was-attempted)

Output of a message was attempted, but an error occurred.

(S)
Continues processing.

(O)
Check that there is sufficient disk spaces, and then retry.

KAVT3722-E

jposendml is unusable.

This product cannot use the email function.

(S)
Cancels processing.

KAVT3723-E

Message Put error. (reason)

An attempt was made to output a message, but memory became insufficient.

(S)
Cancels processing.

(O)
Check that there are sufficient disk spaces, and then retry.

KAVT3801-E

Illegal option (-character) exists.

You specified an illegal option.

(S)
Cancels processing.

(O)
Specify a correct option.

KAVT3802-E

Value for option (-option) is not specified.

A value is not specified for the option.

(S)
Cancels processing.

(O)
Specify the necessary option.

KAVT3803-E

Extra argument(s) exist.

You specified an extra argument.

(S)
Cancels processing.

(O)
Delete the unnecessary argument.

KAVT3804-E

Invalid value for option (-option).

An invalid option was specified.

(S)
Cancels processing.

(O)
Specify the correct option.

KAVT3805-E

Option (-option) appears twice or more.

An option was specified more than once.

(S)
Cancels processing.

(O)
Specify only one option among the choice of options.

KAVT3806-E

Monitoring User name not specified.

A monitoring user name is missing.

(S)
Cancels processing.

(O)
Specify the monitoring user name.

KAVT3807-W

Retry processing is canceled.

An exclusive retry was canceled because the specified retry cancel time had elapsed.

(S)
Cancels processing.

(O)
Since this error causes mail to bounce to its sending source, re-send it as required.

KAVT3810-E

I/O error occurred: maintenance-information maintenance-information maintenance-information system-error-message

An I/O error occurred in inputting/outputting a file while executing the mail delivery command.

(S)
Cancels processing.

(O)
Check whether:
  • The system resources are sufficient.
  • The permission environment of the started user is correct.
  • The directory created during installation of JP1/AJS3 was deleted inadvertently.

KAVT3811-E

Insufficient memory: maintenance-information maintenance-information maintenance-information

A memory shortage occurred during the execution of the mail delivery command.

(S)
Cancels processing.

(O)
Check that there is free space in memory in the system.

KAVT3814-E

An error occurred in Mail Send Command: maintenance-information maintenance-information (maintenance-information) (system-error-message)

(S)
Cancels processing.

(O)
Use maintenance information and system error message to determine the cause of the error.

KAVT3820-I

Execute Mail Send Command.: maintenance-information maintenance-information

Execute the mail delivery command.

(S)
Continues processing.

KAVT3821-I

Mail Send Command finished.

The mail delivery command terminated.

(S)
Terminates processing.

KAVT3822-I

Retrying.

The mail delivery command retries to create a lock file.

(S)
Continues processing.

KAVT3823-I

Read a mail.

The mail delivery command reads mail from standard input.

(S)
Continues processing.

KAVT3824-I

Wrote a mail.

The mail delivery command is written mail into the mail file.

(S)
Continues processing.

KAVT4031-E

SUP will now stop because an error that stops processing occurred (GetLastError=GetLastError-code, Locate=output-location)

SUP stopped because a fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4036-E

Messages could not be sent because an error that stops processing occurred. (return-code-of-GetLastError, output-location)

Sending messages was impossible because a fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4037-E

SUP management process stopped. Fatal error occurred. (error-code)

The SUP management process stopped because a fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly.

KAVT4039-E

The TP1 service does not exist.

The TP1 service is missing.

(S)
Cancels processing.

(O)
Check whether OpenTP1 is installed correctly.

KAVT4057-I

A message was received.

A message was received.

(S)
Continues processing.

KAVT4058-I

A message was sent.

A message was sent.

(S)
Continues processing.

KAVT4068-E

Insufficient memory. (error-code-of-GetLastError)

Memory cannot be allocated.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4069-E

Unable to open message body file. (error-code-of-GetLastError)

The message body file could not be opened.

(S)
Cancels processing.

(O)
Check whether the correct file is specified.
If the correct file is specified, use the error code of GetLastError to determine the cause that prevented the file from being opened, and then take appropriate action.

KAVT4070-E

Unable to ascertain size of a message body file. (error-code-of-GetLastError)

The size of the message body file could not be obtained.

(S)
Cancels processing.

(O)
Check whether the correct file is specified.

KAVT4071-E

Unable to read message body file. (error-code-of-GetLastError)

The message body file could not be read.

(S)
Cancels processing.

(O)
Check whether the correct file is specified.
If the correct file is specified, check whether system resources are sufficient.

KAVT4072-E

Unable to close message body file. (error-code-of-GetLastError)

The message body file could not be closed.

(S)
Cancels processing.

(O)
Use the error code of GetLastError and the system error message to determine the cause that prevented the file from being closed, and then take appropriate action.

KAVT4075-E

Unable to send message.

The message could not be sent.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4076-E

Failed to close the queue.

The queue could not be closed.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4080-E

Unexpected error occurred. (fail in acquisition of handle) (error-location)

An unexpected error occurred.

(S)
Cancels processing.

(O)
Contact the system administrator.

KAVT4122-E

The MQSeries service is not running.

The MQSeries service is not started.

(S)
Cancels processing.

(O)
Check whether the MQSeries service is started.

KAVT4123-E

The MQSeries service does not exist.

The MQSeries service does not exist.

(S)
Cancels processing.

(O)
Check whether MQSeries is installed correctly.

KAVT4124-E

The status of the MQSeries service could not be acquired.

Acquiring the MQSeries service status was impossible.

(S)
Cancels processing.

(O)
Check whether MQSeries is installed correctly.

KAVT4125-I

The MQSeries service was started.

The MQSeries service has started.

(S)
Continues processing.

KAVT4134-I

The processing of message sending will now start.

Message sending starts.

(S)
Continues processing.

KAVT4135-I

The processing of message sending will now end.

Message sending terminates.

(S)
Continues processing.

KAVT4136-E

The parameter is specified incorrectly.

The specified parameter is invalid.

(S)
Cancels processing.

(O)
Check whether the variable is correct.

KAVT4138-E

The data is specified incorrectly. (specified-data)

The specified data is invalid.

(S)
Cancels processing.

(O)
Check whether how to specify the variable is correct.

KAVT4139-E

A required item is missing.

Necessary items are missing.

(S)
Cancels processing.

(O)
Make sure that all necessary items are specified correctly for the Send MQ Message job.

KAVT4140-E

The configuration definition could not be read. (maintenance-information)

Reading the configuration definition was impossible.

(S)
Cancels processing.

(O)
Check whether JP1/Base and JP1/AJS3 are installed correctly.

KAVT4141-E

You are not authorized to access the configuration definition. (maintenance-information)

The access permission to the configuration definition does not exist.

(S)
Cancels processing.

(O)
Handle the system with a privilege to the configuration definition.

KAVT4142-E

The specified key does not exist in the configuration definition. (maintenance-information)

The configuration definition does not have the key.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly.
If JP1/AJS3 is installed correctly, check the reason why the specified key does not exist in the configuration definition of the message queue sending job, and then take appropriate action.

KAVT4143-E

An unexpected error occurred. (maintenance-information)

An unexpected error occurred.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly. If installed correctly, contact the system administrator.

KAVT4144-E

The send process (process-name) could not be started. (return-value-of-GetLastError)

Stating a send process was impossible.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly.
If JP1/AJS3 is installed correctly, use the code of GetLastError to determine the cause of the error that prevented the send process from being started, correct the error, and then retry.

KAVT4148-E

The installation path for JP1/AJS2 was not found.

The JP1/AJS3 installation destination is not found.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is installed correctly.

KAVT4150-E

The send process (system-used) ended abnormally. (GetLastError-return-code)

The sending process indicated by system-used terminated abnormally.

(S)
Cancels processing.

(O)
Determine why the send process terminated abnormally from the return code of GetLastError, and take appropriate action.

KAVT4152-E

Failure occurred at the time of queue manager program connection (MQSeries-error-code, error-location)

A failure occurred during the connection to the queue management program.

(S)
Cancels processing.

(O)
Check whether the queue management program is running.
If it is running, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4155-E

An error that stops processing occurred during message sending. (MQSeries-error-code)

A fatal error that stops processing occurred during the sending of messages.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.
If the environment is set up to send and receive messages, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4156-I

The queue was closed.

The queue was closed successfully.

(S)
Continues processing.

KAVT4158-I

The queue was opened. (error-location)

The queue was opened successfully.

(S)
Continues processing.

KAVT4159-I

An attempt to open the queue will be retried. (error-location)

A retry is made to open the queue.

(S)
Continues processing.

KAVT4160-E

The queue cannot be opened because the specified remote queue name is invalid. (MQSeries-error-code, error-location)

Opening a queue was impossible because the remote queue name is invalid.

(S)
Cancels processing.

(O)
Check whether the environment is set up to be connected to the remote queue.
If the environment is set up to allow connection, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4161-E

The queue cannot be opened because the base queue of the specified alias queue cannot be recognized. (MQSeries-error-code, error-location)

Opening a queue was impossible because the base queue of the alias name queue cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4162-E

The queue cannot be opened because the transfer queue is being used incorrectly. (MQSeries-error-code, error-location)

The system cannot open a queue because the transfer queue has an error.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4163-E

The queue cannot be opened because the transfer queue cannot be recognized. (MQSeries-error-code, error-location)

Opening a queue was impossible because the transfer queue could not be recognized.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4164-E

The queue cannot be opened because the specified remote queue manager program cannot be recognized. (MQSeries-error-code, error-location)

Opening a queue is impossible because the specified remote queue management program cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly.
If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4165-E

The queue cannot be opened because the specified queue manager program cannot be recognized. (MQSeries-error-code, error-location)

Opening a queue is impossible because the specified queue management program cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the specified queue management program is correct.
If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4166-E

The queue cannot be opened because the object cannot be recognized. (MQSeries-error-code, error-location)

Opening a queue is impossible because an object cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4167-E

The queue cannot be opened because the default transfer queue is being used incorrectly. (MQSeries-error-code, error-location)

Opening a queue is impossible because the use of the default transfer queue is invalid.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4168-E

The default transfer queue cannot be recognized. (MQSeries-error-code, error-location)

A default transfer queue was unrecognizable.

(S)
Cancels processing.

(O)
Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4170-E

Messages cannot be sent because the queue is full. (MQSeries-error-code)

Sending a message is impossible because the queue is full.

(S)
Cancels processing.

(O)
Delete unnecessary messages from the queue.
If unnecessary messages have already been deleted, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4171-E

Messages cannot be sent because the message length exceeds the maximum length for the queue. (MQSeries-error-code)

Sending a message was impossible because the message length exceeded the maximum for a queue.

(S)
Cancels processing.

(O)
Check the message length to send.
If the length of the message to be sent does not exceed the maximum for a queue, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4172-E

Messages cannot be sent because the queue was deleted. (MQSeries-error-code)

Sending a queue was impossible because a queue was deleted.

(S)
Cancels processing.

(O)
Check whether the queue is correct.
If the specified queue is correct, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4173-E

Messages cannot be sent because there is insufficient disk space for the queue. (MQSeries-error-code)

Sending a message was impossible because there was no disk space for the queue.

(S)
Cancels processing.

(O)
Check the disk space.
If there is sufficient disk space, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action.

KAVT4174-E

Messages could not be sent because memory became insufficient. (MQSeries-error-code)

Sending a message was impossible because there was insufficient memory.

(S)
Cancels processing.

(O)
Check the disk space.

KAVT4175-E

Messages could not be sent. (MQSeries-error-code)

Sending a message was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4176-E

The message's priority exceeds the maximum. (MQSeries-error-code)

The message priority exceeds the maximum you can specify.

(S)
Cancels processing.

(O)
Check whether the message priority is specified correctly.

KAVT4177-W

An error occurred during connection to the queue manager program, but processing continues. (MQSeries-error-code, error-location)

An error occurred while connecting the queue management program, but the system continues processing.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4178-I

A message was sent to the dead-letter queue.

A message was sent to the dead-letter queue.

(S)
Continues processing.

KAVT4179-I

A message was sent to the queue.

A message was sent to the queue.

(S)
Continues processing.

KAVT4180-E

The status of the TP1 service could not be acquired. (error-code)

Acquiring the TP1 service status was impossible.

(S)
Cancels processing.

(O)
Check whether OpenTP1 is installed correctly.

KAVT4181-E

The TP1 service is not running.

The TP1 service is not running.

(S)
Cancels processing.

(O)
Start the OpenTP1 service.

KAVT4182-E

An unexpected error occurred during communication with SUP (GetLastError-return-code, output-location)

An unexpected error occurred during communication with SUP.

(S)
Cancels processing.

(O)
Check whether JPOMQSUP is setup correctly.

KAVT4183-E

The communication pipe with SUP could not be created. (GetLastError-return-code, output-location)

Creating a communication pipe with SUP was impossible.

(S)
Cancels processing.

(O)
Check whether JPOMQSUP is set up correctly.

KAVT4184-E

Messages cannot be sent because the message data file could not be opened. (error-code)

The system cannot send a message because opening a message data file failed.

(S)
Cancels processing.

(O)
Check whether the specification of the message data file is correct.

KAVT4185-E

Messages cannot be sent because the message data file could not be read. (error-code)

The system cannot send a message because reading a message data file failed.

(S)
Cancels processing.

(O)
Check whether the specification of the message data file is correct.

KAVT4186-E

Messages cannot be sent because there is no message data file. (error-code)

The system cannot send a message because no message data file exists.

(S)
Cancels processing.

(O)
Check whether the specification of the message data file is correct.

KAVT4187-E

Messages cannot be sent because memory became insufficient. (error-code)

The system cannot send a message because a memory shortage occurred.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4188-E

Messages cannot be sent because memory could not be allocated. (error-code)

The system cannot send a message because memory allocation failed.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4189-E

The queue could not be opened. (error-code)

Opening a queue was impossible.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4190-E

Messages could not be sent. (error-code)

Sending a message was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4192-E

The queue cannot be opened because the specified remote queue name is invalid. (error-code)

Opening a queue is impossible because the specified remote queue name is invalid.

(S)
Cancels processing.

(O)
Check whether a correct queue is specified.

KAVT4193-E

Messages could not be received. (error-code)

Receiving a message was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4195-E

The queue could not be closed. (error-code)

Closing a queue was impossible.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4196-E

Messages cannot be received because memory became insufficient. (error-code)

The system cannot send a message because a memory shortage occurred.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4197-E

Messages cannot be received because memory could not be allocated. (error-code)

The system cannot send a message because of the memory allocation problem.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4198-E

Messages cannot be sent because the queue is full. (error-code)

The system cannot send a message because the queue is full.

(S)
Cancels processing.

(O)
Delete unnecessary messages.

KAVT4199-E

Messages cannot be sent because the queue was deleted. (error-code)

The system cannot send a message because the queue was deleted.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4200-E

Messages cannot be sent because there is insufficient disk space for the queue. (error-code)

Sending a message was impossible because there was no disk space for the queue.

(S)
Cancels processing.

(O)
Check the disk space.

KAVT4201-E

Messages cannot be sent because the message length exceeds the maximum length of the queue. (error-code)

The system cannot send a message because the message length exceeds the maximum queue length.

(S)
Cancels processing.

(O)
Check the message length to send.

KAVT4202-E

Messages cannot be sent because memory became insufficient. (error-code)

The system cannot send a message because there is insufficient memory.

(S)
Cancels processing.

(O)
Check the disk space.

KAVT4203-E

The queue cannot be opened because the base queue of the specified alias queue cannot be recognized. (error-code)

The system cannot open a queue because the system cannot recognize the base queue of the alias queue.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4204-E

The queue cannot be opened because the transfer queue is being used incorrectly. (error-code)

Opening a queue was impossible because the use of the transfer queue was invalid.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4205-E

The queue cannot be opened because the transfer queue cannot be recognized. (error-code)

The system cannot open the queue because the transfer queue cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4206-E

The queue cannot be opened because the specified remote queue manager program cannot be recognized. (error-code)

The system cannot open a queue because the specified remote queue manager cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue manager is specified.

KAVT4207-E

The queue cannot be opened because the specified queue manager cannot be recognized. (error-code)

The system cannot open a queue because the specified queue manager cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue manager is specified.

KAVT4208-E

The queue cannot be opened because the specified queue name or model queue name cannot be recognized. (error-code)

The system cannot open a queue because the specified queue name or model queue name cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4209-E

The queue cannot be opened because the default transfer queue is being used incorrectly. (error-code)

The system cannot open a queue because the use of the default transfer queue is invalid.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4210-E

The queue cannot be opened because the default transfer queue cannot be recognized. (error-code)

The queue cannot be opened because the default transfer queue is used incorrectly.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4211-E

Messages cannot be sent because the queue was deleted. (error-code)

The system cannot send a message because a queue has been deleted.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4212-E

Messages cannot be received because the queue manager program has ended. (error-code)

The system cannot receive a message because the queue manager has already terminated.

(S)
Cancels processing.

(O)
Start the queue manager.

KAVT4213-E

The queue could not be re-opened because it was deleted. (error-code)

The attempt to reopen the queue was impossible because a queue was deleted.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4214-E

Messages could not be sent because an error occurred in SUP. (error-code)

Sending a message was impossible because an error occurred in SUP.

(S)
Cancels processing.

(O)
Check whether JPOMQSUP is set up correctly.

KAVT4215-E

Messages could not be received because an error occurred in SUP. (error-code)

Receiving a message was impossible because an error occurred in SUP.

(S)
Cancels processing.

(O)
Check whether JPOMQSUP is set up correctly.

KAVT4216-E

The file for storing messages could not be output. (error-code)

Outputting a message storage file was impossible.

(S)
Cancels processing.

(O)
Check whether the file can be written.

KAVT4222-E

The queue could not be opened.

Opening a queue was impossible.

(S)
Places the job in the Ended abnormally status if it was an event job, or places the job in the Monitor terminated status if it was a jobnet with start conditions.

(O)
Take action according to the instructions given by the message "KAVT4419-W An error occurred during an MQSeries access. (func=MQSeries-API-name, ErrCode=MQSeries-API-return-value, maintenance-information)" that was output to the integrated trace log.
If you cannot determine the cause of the error, collect the data about the internal error, and then contact the system administrator.

KAVT4223-E

An error occurred during message reception.

An error occurred during the reception of a message.

(S)
Places the job in the Ended abnormally status if it was an event job, or places the job in the Monitor terminated status if it was a jobnet with start conditions.

(O)
Take action according to the instructions given by the message "KAVT4419-W An error occurred during an MQSeries access. (func=MQSeries-API-name, ErrCode=MQSeries-API-return-value, maintenance-information)" that was output to the integrated trace log.
If you cannot determine the cause of the error, collect the data about the internal error, and then contact the system administrator.

KAVT4230-E

Messages could not be received because memory could not be allocated.

Receiving a message was impossible because memory could not be allocated.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4232-E

The file for storing messages could not be output.

Outputting a message storage file was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to write a file.

KAVT4235-E

The queue cannot be opened because the specified remote queue name is invalid.

The system cannot open a queue because the specified remote queue name is invalid.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4236-E

The queue cannot be opened because the base queue of the specified alias queue cannot be recognized.

Opening a queue is impossible because the base queue of the alias queue cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4237-E

The queue cannot be opened because the transfer queue is being used incorrectly.

Opening a queue is impossible because the method of using a transfer queue is incorrect.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4238-E

The queue cannot be opened because the transfer queue cannot be recognized.

Opening a queue is impossible because a transfer queue cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4239-E

The queue cannot be opened because the specified remote queue manager program cannot be recognized.

Opening a queue is impossible because the specified remote queue management program cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue management program is specified.

KAVT4240-E

The queue cannot be opened because the specified queue manager program cannot be recognized.

Opening a queue is impossible because the specified queue management program cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue management program is specified.

KAVT4241-E

The queue cannot be opened because the specified queue name or model queue name cannot be recognized.

Opening a queue is impossible because the specified queue name or model queue name cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4242-E

The queue cannot be opened because the default transfer queue is being used incorrectly.

Opening a queue is impossible because the use of the default transfer queue is incorrect.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4243-E

The queue cannot be opened because the default transfer queue cannot be recognized.

Opening a queue is impossible because a default transfer queue cannot be recognized.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified.

KAVT4244-E

Messages cannot be sent because the queue was deleted.

Receiving a message is impossible because a queue was deleted.

(S)
Cancels processing.

(O)
Check whether a correct queue is specified.

KAVT4245-E

Messages could not be received because the queue manager program ended.

Receiving a message is impossible because the queue management program terminates.

(S)
Cancels processing.

(O)
Start the queue management program.

KAVT4246-E

Messages cannot be received because memory became insufficient.

Receiving a message became impossible because a memory shortage occurred.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4247-E

Messages cannot be received because memory could not be allocated.

Receiving a message is impossible because memory allocation failed.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4248-E

The queue could not be closed.

Closing a queue was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4249-E

The queue could not be disconnected.

Disconnecting a queue was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4250-E

The queue could not be connected.

Connection to the queue was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4251-E

Messages could not be received because an error occurred in the access process.

Receiving a message was impossible because an error occurred in the access process.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4252-E

The queue could not be re-opened because it was deleted.

An attempt to reopen the queue was impossible because it was deleted.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4253-E

The queue manager program stopped.

The queue management program stopped.

(S)
Cancels processing.

(O)
Start the queue management program.

KAVT4254-E

Failed to execute SUP. (error-code)

Starting SUP was impossible.

(S)
Cancels processing.

(O)
Check whether JP1MQSUP is set up correctly.

KAVT4255-E

The data length is invalid. (data-name)

The character string length is invalid.

(S)
Cancels processing.

(O)
Check whether the data is correct.

KAVT4256-E

The specified file does not exist. (return-code)

The file does not exist.

(S)
Cancels processing.

(O)
Check whether the file is correct.

KAVT4257-E

The queue could not be opened, so the data was sent to the dead-letter queue instead.

Since the queue could not be opened, the data was sent to the dead-letter queue.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified and whether messages can be sent to that queue.

KAVT4258-E

Messages could not be sent, so data was sent to the dead-letter queue instead. (error-code)

Since messages could not be sent, the data was sent to the dead-letter queue.

(S)
Cancels processing.

(O)
Check whether the correct queue is specified and whether messages can be sent to that queue.

KAVT4259-E

An unjust character is designated in queuing system name of constitution definition information.

An invalid character is specified in the queuing system name in constitution definition information.

(S)
Cancels processing.

(O)
The environment may not be set up. Set up the environment again.

KAVT4260-I

Accept to request SUP stopped.

A request to stop the SUP was accepted.

(S)
Continues processing.

KAVT4261-I

Accept to request SUP restarted.

A request to restart the SUP was accepted.

(S)
Continues processing.

KAVT4401-I

JP1/AJS2 message queue monitoring process (TP1/Message Queue) will now start.

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) starts.

(S)
Continues processing.

KAVT4402-I

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) started.

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) has started.

(S)
Continues processing.

KAVT4403-I

The JP1/AJS2 message queue monitoring process (MQSeries) will now start.

The JP1/AJS2 message queue monitoring process (MQSeries) starts.

(S)
Continues processing.

KAVT4404-I

The JP1/AJS2 message queue monitoring process (MQSeries) started.

The JP1/AJS2 message queue monitoring process (MQSeries) has started.

(S)
Continues processing.

KAVT4405-I

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) will now stop.

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) stops.

(S)
Continues processing.

KAVT4406-I

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) stopped.

The JP1/AJS2 message queue monitoring process (TP1/Message Queue) has stopped.

(S)
Terminates processing.

KAVT4407-I

The JP1/AJS2 message queue monitoring process will now stop. (MQSeries)

The JP1/AJS2 message queue monitoring process (MQSeries) stops.

(S)
Continues processing.

KAVT4408-I

The JP1/AJS2 message queue monitoring process (MQSeries) stopped.

The JP1/AJS2 message queue monitoring process (MQSeries) has stopped.

(S)
Terminates processing.

KAVT4409-I

The JP1/AJS2 SUP control process will now start.

The JP1/AJS2 SUP control process starts.

(S)
Continues processing.

KAVT4410-I

The JP1/AJS2 SUP control process started.

The JP1/AJS2 SUP control process has started.

(S)
Continues processing.

KAVT4411-I

The JP1/AJS2 SUP control process will now stop.

The JP1/AJS2 SUP control process stops.

(S)
Continues processing.

KAVT4412-I

The JP1/AJS2 SUP control process stopped.

The JP1/AJS2 SUP control process has stopped.

(S)
Terminates processing.

KAVT4413-I

Message Queue System to use it is message-queuing-system-to-use

This message indicates the message queuing system to use.

(S)
Continues processing.

KAVT4414-E

The message queuing system to be used is not defined. Set up the environment.

A message queuing system to use is not defined. Set up the environment.

(S)
Cancels processing.

(O)
Check the environment settings.

KAVT4417-I

The message queue function to be linked has started.

The message queuing function to be linked has started.

(S)
Continues processing.

KAVT4418-W

The message queue function to be linked is stopped. (maintenance-information)

The message queuing function to be linked has stopped.

(S)
Cancels monitoring of the message queue reception, and then resumes monitoring after the message queuing function to be linked is started.

(O)
No action is required if the message queuing function to be linked stopped according to the schedule. If it stopped unexpectedly, check the status of MQSeries and then start MQSeries. Even if MQSeries stops, the Receive MQ message job remains in the Now running or Now monitoring status.

KAVT4419-W

An error occurred during an MQSeries access. (func=MQSeries-API-name, ErrCode=MQSeries-API-return-value, maintenance-information)

An error occurred in a MQSeries API.

(S)
For the system operation, see the message that was output before or after this message.

(O)
Check the cause of the error according to func (API name of the MQSeries in which the error occurred) and ErrCode (return value from the MQSeries API) in MQSeries documentation, and then take action as required.

KAVT4451-I

The message queue linkage communication process will now start.

The message queue linkage communication process starts.

(S)
Continues processing.

KAVT4452-I

The message queue linkage communication process started.

The message queue linkage communication process has started.

(S)
Continues processing.

KAVT4453-I

The message queue linkage communication process stopped.

The message queue linkage communication process has stopped.

(S)
Terminates processing.

KAVT4454-I

The monitoring of message queue reception will now start.

The monitoring of message queue reception starts.

(S)
Continues processing.

KAVT4455-E

The monitoring of message queue reception will now stop.

The message queue reception monitoring is stopped.

(S)
Cancels processing.

(O)
Refer to the error message output previously and determine the cause of the error.

KAVT4456-I

The reception of messages that satisfy the conditions was confirmed.

The reception of messages that satisfy the conditions was confirmed.

(S)
Continues processing.

KAVT4457-I

Monitoring of message queue linkage will now end because the time-out period elapsed.

Monitoring of message queue linkage terminates because the time-out period has elapsed.

(S)
Terminates processing.

KAVT4458-I

Message Queue System to use it is message-queuing-system-to-use

This message indicates the message queuing system to use.

(S)
Continues processing.

KAVT4459-E

No message queuing system has been established. Set up the environment.

A message queuing system to use is not set. Define the environment settings.

(S)
Cancels processing.

(O)
Check the environment settings.

KAVT4460-E

An unexpected value is specified for the message queuing system to be used. Set up the environment again. (maintenance-information)

The message queue system to use has an unexpected value. Redefine the environment settings.

(S)
Cancels processing.

(O)
Check the environment settings.

KAVT4461-W

An error occurred during creation of a macro variable.

An error occurred while creating a macro variable.

(S)
Cancels processing.

(O)
Check whether the macro variable is correct.

KAVT4462-W

A macro variable exceeds 4096 bytes. Some macro variables could not be created.

A macro variable exceeds 4,096 bytes and some could not be created.

(S)
Cancels processing.

(O)
Decrease the number of macros to be specified.

KAVT4464-W

A service of the message queuing system is not running.

The message queuing system service is not started.

(S)
Cancels processing.

(O)
Starts the OpenTP1 or MQSeries service.

KAVT4465-I

The startup of the message queuing system service was confirmed.

Startup of the message queuing system service has been confirmed.

(S)
Continues processing.

KAVT4466-E

The definition of the message queue monitoring job is invalid.

The definition of the message-queue message reception monitoring job is invalid.

(S)
Cancels processing.

(O)
Check the job definitions.

KAVT4467-E

Memory became insufficient.

A memory shortage occurred.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4468-E

An event for canceling registration of a job could not be created.

Creating an event for job registration cancellation was impossible.

(S)
Cancels processing.

(O)
Check whether the environment is set up to send and receive messages.

KAVT4469-E

The option for not linking the message queue is selected. Message queue reception will not be monitored.

The status that does not link a message queue is selected. The system does not monitor the message queue reception.

(S)
Cancels processing.

(O)
Check the environment settings.

KAVT4470-E

An unexpected value is specified in the option for message queue linkage. Set up the environment again. (maintenance-information)

The message queue linkage has an unexpected value. Redefine the environment settings.

(S)
Cancels processing.

(O)
Check the environment settings.

KAVT4471-W

The JP1/AJS2 message queue monitoring process is not running.

The JP1/AJS2 message queue monitoring process is not running. The system waits until the process can run.

(S)
Cancels processing.

(O)
Determine the cause of the error from the error message output before this one, and take appropriate action.

KAVT4472-I

The startup of the JP1/AJS2 message queue monitoring process was confirmed.

The JP1/AJS2 message queue monitoring process started.

(S)
Continues processing.

KAVT4474-E

The message queuing system service was not found.

The message queue system service could not be found.

(S)
Cancels processing.

(O)
Check whether the message queue system is installed and set up correctly.

KAVT4499-E

An unexpected error occurred. (maintenance-information)

An unexpected error occurred.

(S)
Cancels processing.

(O)
Contact the system administrator.

KAVT4501-I

A message was received. (queue-name, correlation-ID, message-ID)

A message was received.

(S)
Continues processing.

KAVT4502-E

The message queue will not be linked.

The message queue linkage is not performed.

(S)
Suspends the message-queue message reception monitoring process.

(O)
Use the JP1/AJS3 internal log to determine the cause of the error, and then restart JP1/AJS3 as required.

KAVT4503-E

Message queue linkage cannot start. (maintenance-information, cause-of-error)

The message queue linkage cannot start.

(S)
Terminates the message queue monitoring process.

(O)
Use the JP1/AJS3 internal log to determine the cause of the error, and then restart JP1/AJS3 as required.

KAVT4504-I

The message queue monitoring process will now start.

The message queue monitoring process starts.

(S)
Continues processing.

KAVT4505-I

The message queue monitoring process will now end.

The message queue monitoring process terminates.

(S)
Terminates processing.

KAVT4506-I

The message queue monitoring process will now be suspended.

The message queue monitoring process is suspended.

(S)
Terminates processing.

KAVT4507-E

The argument when the message queue monitoring process was called is invalid.

The argument is invalid when calling the message queue monitoring process.

(S)
Terminates the message queue monitoring process.

(O)
Contact the system administrator.

KAVT4512-E

A temporary directory could not be created: (maintenance-information, system-error-message)

Creating a temporary directory was impossible.

(S)
Terminates the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4513-E

The status file of the message queue linkage function could not be opened: (maintenance-information, system-error-message)

Opening a linkage status file for message queues was impossible.

(S)
Terminates the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4517-E

An internal table could not be created because of insufficient memory: maintenance-information

Creating an internal table was impossible because of insufficient memory.

(S)
Suspends the message queue monitoring process.

(O)
Check whether memory is sufficient.
If memory is insufficient, allocate memory, and then restart JP1/AJS3. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4521-E

The file for storing messages (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a message storage file was impossible.

(S)
Transfers messages to the undeliverable queue (the dead letter queue).

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4522-E

The file for storing messages (file-name) could not be written: (maintenance-information, system-error-message)

Writing a message storage file was impossible.

(S)
Transfers a message to the undeliverable queue (the dead letter queue).

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4523-E

The temporary file for storing messages (temporary-file-name) could not be opened: (maintenance-information, system-error-message)

Opening a temporary file for message storage was impossible.

(S)
Transfers a message to the undeliverable queue (the dead letter queue).

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4524-E

The temporary file for storing messages (temporary-file-name) could not be written to: (maintenance-information, system-error-message)

Writing a temporary file for message storage was impossible.

(S)
Transfers a message to the undeliverable queue (the dead letter queue).

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4525-E

The file (file-name) could not be closed: (maintenance-information, system-error-message)

Closing a file was impossible.

(S)
Continues processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4526-E

Memory became insufficient: maintenance-information

A memory shortage occurred.

(S)
Cancels the processing for the messages currently processed and message retrieval. Then waits for the next monitoring interval.

(O)
Check whether memory is sufficient.
If memory is insufficient, allocate memory , and then restart JP1/AJS3. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4527-E

An error occurred during conversion of character codes: maintenance-information

An error occurred while converting a code.

(S)
Cancels the processing for the messages currently processed. Then, continues the message retrieval for current queues.

(O)
Contact the system administrator.

KAVT4528-E

An error occurred in the processing of synchronous multi-I/O: (maintenance-information, system-error-message)

An error occurred in the synchronous multiple processing of input or output.

(S)
Terminates the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4529-E

Invalid data was written to the pipe: (maintenance-information) maintenance-information

Pipe data is invalid.

(S)
Terminates the message queue monitoring process.

(O)
Contact the system administrator.

KAVT4530-W

An error message remains in a file (file-name).

The message remains during occurrence of the error in a file.

(S)
Continues processing.

(O)
Delete the contents of the temporary files as required.

KAVT4531-E

The process could not be started: (maintenance-information, system-error-message)

Starting a process was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4532-E

The pipe could not be opened: pipe-name (maintenance-information, system-error-message)

Opening a pipe was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4533-E

The pipe could not be read: (maintenance-information, system-error-message)

Reading a pipe was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4534-E

The pipe could not be written to: maintenance-information (maintenance-information, system-error-message)

Writing a pipe was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4535-E

The pipe could not be closed: pipe-name (maintenance-information, system-error-message)

Closing a pipe was impossible.

(S)
Continues processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4536-E

There is no reply to the pipe contact: maintenance-information

The system does not respond to the pipe report.

(S)
Suspends the message queue monitoring process. Continues processing at the next monitoring interval.

(O)
Check the status of the prerequisite message queuing system.

KAVT4537-E

The reply-wait failed: (maintenance-information, system-error-message)

Waiting for a response was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4538-E

Environment information could not be acquired: maintenance-information (maintenance-information, system-error-message)

Acquiring the environment information was impossible.

(S)
Stops and suspends the message queue monitoring system. Alternatively, terminates the message send process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4539-E

The SUP process could not be started: name-of-SUP-function-with-error return-code-SUP-function-with-error

Starting SUP was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.

KAVT4540-W

The transaction process failed, but SUP continues: name-of-SUP-function-with-error return-code-SUP-function-with-error

Processing of a transaction was impossible, but SUP continues.

(S)
Cancels the current processing, and then continues the next processing.

(O)
Investigate the cause of the error from the SUP function name and return value where an error occurred. Then take action to correct the error.

KAVT4541-E

SUP could not start.

SUP could not be started.

(S)
Cancels the current processing, and waits for the next monitoring interval.

(O)
Start OpenTP1.

KAVT4542-E

The results of the SUP start command could not be acquired: (maintenance-information, system-error-message)

Acquiring the results of the SUP startup command was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4543-E

An error occurred in the SUP start command: (error-message-at-issuing-startup-command)

The SUP startup command has an error.

(S)
Suspends the message queue monitoring process.

(O)
Investigate the cause of the error from the error message when issuing the startup command. Then take action to correct the error.

KAVT4547-I

Messages are sent to the queue (queue-name).

Messages are sent to the queue.

(S)
Continues processing.

KAVT4548-E

The value for option (option) is invalid.

The option value has an error.

(S)
Cancels the transmission of the message queue.

(O)
Correct the value of the option, and then re-execute the transmission of the message queue.

KAVT4549-E

An excess argument is specified.

An extra argument is specified.

(S)
Cancels the transmission of the message queue.

(O)
Delete unnecessary arguments, and then re-execute the transmission of the message queue.

KAVT4550-E

Option (option) is specified two or more times.

An option (option) is specified more than once.

(S)
Cancels the transmission of the message queue.

(O)
Specify only once the option that was specified more than once, and then re-execute the transmission of the message queue.

KAVT4551-E

No value is specified for the option (option).

A value is not specified for the option that needs a value.

(S)
Cancels the transmission of the message queue.

(O)
Specify an option value, and then re-execute the transmission of the message queue.

KAVT4552-E

The file (file-name) could not be opened: (maintenance-information, system-error-message)

Opening a file was impossible.

(S)
Cancels the transmission of the message queue.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4553-E

The status of the file (file-name) could not be acquired: (maintenance-information, system-error-message)

Extracting the file status of a file was impossible.

(S)
Cancels the transmission of the message queue.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4554-E

The file (file-name) could not be read: (maintenance-information, system-error-message).

Reading a file was impossible.

(S)
Cancels the transmission of the message queue.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4555-E

The file(file-name) could not be closed: (maintenance-information, system-error-message)

Closing a file was impossible.

(S)
Continues the transmission of the message queue.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4556-E

Memory became insufficient: maintenance-information

A memory shortage occurred.

(S)
Cancels the transmission of the message queue.

(O)
Check whether memory is sufficient.
If memory is insufficient, allocate memory, and then restart JP1/AJS3. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT4557-I

Message will be sent to the dead-letter queue (queue-name), because an error occurred.

An error occurred. The message will be sent to the undeliverable queue (the dead letter queue).

(S)
Continues processing.

(O)
Use the message that is output previously to determine the cause of the error, and take action.

KAVT4558-I

Message will be re-sent to the dead-letter queue (queue-name).

The message will be re-sent to the undeliverable queue (the dead letter queue).

(S)
Continues processing.

KAVT4559-W

The specified dynamic queue (queue-name) already exists. The existing queue will be opened.

The existing queue is opened because a queue having the same name as the specified dynamic queue already exists.

(S)
Sends a message to the existing queue.

(O)
Check the queue status.

KAVT4560-E

An error occurred in the message queuing system: queue-name MQI-call-name reason-code-from-MQI-call maintenance-information

An error occurred while processing a message queuing system.

(S)
Cancels the message queue monitoring system or the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Use the reason code information for the MQI call of MQSeries or TP1/Message Queue to determine the cause of the error, and then take action.

KAVT4561-I

Open handles in the message queuing system exceed the maximum: queue-name MQI-call-name maintenance-information

The number of open handles reached the maximum.

(S)
Continues processing.

(O)
Check the maximum number of handles for the queue management program. Alternatively, reduce the number of monitored queues.

KAVT4562-E

Insufficient system resources: queue-name MQI-call-name maintenance-information

The system resources that are usable are insufficient.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_RESOURCE_PROBLEM error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4563-E

Insufficient storage for message queuing system: queue-name MQI-call-name maintenance-information

There is an insufficient storage area that can be used.

(S)
Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_STORAGE_NOT_AVAILABLE error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4564-W

You are not authorized to access to the message queuing system: queue-name MQI-call-name maintenance-information

Access is not permitted.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_NOT_AUTHRIZED error for the MQI call of MQSeries or TP1/Message Queue and take action to correct the error.

KAVT4565-E

The queue manager program could not be connected: queue-name MQI-call-name maintenance-information

Connection to the queue management program was impossible.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the return value for the MQI call of MQSeries or TP1/Message Queue and take action to make the connection.

KAVT4566-E

Object(queue-name) in the message queuing system was destroyed: MQI-call-name maintenance-information

The object was destroyed.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_OBJECT_DAMAGED error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4567-E

Object name (queue-name) in the message queuing system is invalid: MQI-call-name maintenance-information

An object name is invalid.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the return value for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4568-E

Object(queue-name) in the message queuing system was already opened by another option: MQI-call-name maintenance-information

An object is already opened by a contradictory option.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_OBJECT_IN_USE error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4569-E

PUT usage is prohibited for the queue (queue-name): MQI-call-name maintenance-information

PUT usage is prohibited for the queue.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_PUT_INHIBITED error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4570-E

The queue(queue-name) was deleted: MQI-call-name maintenance-information

A queue was deleted.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_Q_DELETED error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4571-E

An object definition in the message queuing system was changed after the object was opened: queue-name MQI-call-name maintenance-information

The object definitions were changed after they were opened.

(S)
Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_OBJECT_CHANGED error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4572-E

Messages cannot be sent because the queue (queue-name) is full: MQI-call-name maintenance-information

Sending a message is impossible because the queue is full.

(S)
Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_Q_FULL error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4573-E

The message could not be sent to the queue (queue-name) because there is no more disk space free for that queue: MQI-call-name maintenance-information

Sending message is impossible because there is no space for a queue on the disk.

(S)
Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_Q_SAPCE_NOT_AVAILABLE error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4574-E

Messages cannot be sent because the message length exceeds the maximum length for the queue (queue-name): MQI-call-name maintenance-information

Sending a message is impossible because the message length is greater than the maximum length in a queue.

(S)
Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_MSG_TOO_BIG_FOR_Q error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4575-E

The message could not be sent to the temporary dynamic queue: queue-name MQI-call-name maintenance-information

Sending a message is impossible because the system cannot continue a temporary dynamic queue message.

(S)
Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.

(O)
Check the MQRC_PERSISTENT_NOT_ALLOWED error for the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4576-E

An error occurred during sending of the message to the dead-letter queue (queue-name): processing-name reason-code-from-MQI-call-(when-processing-name-is-MQI-call-name) -or-maintenance-information-(for-other-cases)

An error occurred in the message send processing to the undeliverable queue (the dead letter queue).

(S)
Cancels processing. If the error occurred when the message was sent to t an undeliverable queue (a dead letter queue) for the first time, sends the message to an undeliverable queue (a dead letter queue), and then cancels the transmission of the message queue.

(O)
In the case of the reason code from the MQI call of MQSeries or TP1/Message Queue, examine the reason code and take action. If that is not the problem, a memory shortage is possible. Then, take action for insufficient memory.

KAVT4577-E

A sending of the message queue end error occurred in the message queuing system: queue-name MQI-call-name reason-code-from-MQI-call maintenance-information

An error occurred in the message queuing system during transmission of the message queue.

(S)
Continues processing.

(O)
Examine the reason code from the MQI call of MQSeries or TP1/Message Queue and take action.

KAVT4579-I

Data was written to a pipe: pipe-name (maintenance-information)

Data was written to a pipe.

(S)
Executes processing according to the written instruction.

KAVT4581-E

A message queuing system that must not be specified was specified.

The system specified the message queuing system that cannot be specified.

(S)
Cancels the transmission of the message queue, or suspends the message queue monitoring system.

(O)
Check whether the system corresponds to the message queuing system.

KAVT4582-E

The process could not be started: (maintenance-information, system-error-message)

Starting a process was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4583-E

The pipe could not be opened: pipe-name (maintenance-information, system-error-message)

Opening a pipe was impossible.

(S)
Cancels processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4584-E

The pipe could not be read: (maintenance-information, system-error-message)

Reading a pipe was impossible.

(S)
Cancels processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4585-E

The pipe could not be written to when the message was output: maintenance-information (maintenance-information, system-error-message)

Writing a pipe was impossible during message output.

(S)
Terminates processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4586-E

The pipe could not be closed: pipe-name (maintenance-information, system-error-message)

Closing a pipe was impossible.

(S)
Continues processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4587-E

There is no reply to the pipe contact: maintenance-information

No response is provided to pipe contact.

(S)
Cancels processing.

(O)
Contact the system administrator.

KAVT4588-E

The reply-wait failed: (maintenance-information, system-error-message)

Waiting for a response was impossible.

(S)
Cancels processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4589-E

The pipe could not be written to when SUP started: maintenance-information (maintenance-information, system-error-message)

Writing a pipe was impossible during SUP startup.

(S)
Cancels processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4590-E

After the process started, waiting for the replay failed: (maintenance-information, system-error-message)

Waiting for a response was impossible after starting a process.

(S)
Suspends the message queue monitoring process.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4591-E

The process could not be created: (maintenance-information, system-error-message)

Creating a process was impossible.

(S)
Cancels the transmission of the message queue.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4593-I

Data was written to a pipe:pipe-name (maintenance-information)

Data was written to a pipe.

(S)
Executes processing according to the written instruction.

KAVT4595-E

The SUP process could not be started: SUP-function-name-with-error return-value-of-SUP-function-with-error

Starting SUP was impossible.

(S)
Suspends the message queue monitoring process.

(O)
Check the SUP function name where an error occurred and examine the cause of the error. Then take action.

KAVT4596-E

The transaction process failed, but SUP continues: SUP-function-name-with-error return-value-of-SUP-function-with-error

Processing a transaction was impossible, but SUP continues.

(S)
Cancels the current processing and continues the next processing.

(O)
Check the cause of the error from the SUP function names where an error occurred and the return value. Then take action to correct the error.

KAVT4597-E

An error occurred in the SUP start command: (error-message-at-issuing-startup-command)

An error occurred in the SUP startup command.

(S)
Cancels processing.

(O)
Examine the cause of the error from the error message issued for the startup command. Then take action.

KAVT4598-E

The results of the SUP start command could not be acquired: (maintenance-information, system-error-message)

Acquiring the SUP startup command result was impossible.

(S)
Cancels processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4631-E

Fail in read in of configuration definitions information. (return-code)

You could not obtain the configuration definitions.

(S)
Cancels processing.

(O)
The configuration definitions are missing. Alternatively, use the jbssetcnf command to correct the configuration definitions, and then retry.

KAVT4632-E

There is not configuration definitions right to access to information. (return-code)

The privilege of the user is invalid to access the configuration definitions.

(S)
Cancels processing.

(O)
A user who sends or receives messages does not have permission to access the JP1/AJS3 information. Log on as a user who has the access permission.

KAVT4633-E

Specification key does not exist in configuration definitions information. (return-code)

The configuration definitions are missing.

(S)
Cancels processing.

(O)
The configuration definitions are missing. Alternatively, use the jbssetcnf command to correct the configuration definitions, and then retry.

KAVT4634-E

Unexpected error occurred. (return-code)

An unexpected error occurred.

(S)
Cancels processing.

(O)
See the message output before this message to examine the cause of the error.

KAVT4663-E

Failed to open Support File (maintenance-information) (maintenance-information)

Unable to open an auxiliary file from the agent.

(S)
Abnormally terminates the job request.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT4664-E

Failed to send Pipe Data (maintenance-information) (maintenance-information)

Unable to send pipe data to the agent.

(S)
Cancels sending the pipe data and continues processing. The status of job execution may be incorrect.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT4672-I

The SUP started.

The SUP started.

(S)
Continues processing.

KAVT4676-E

Failed to get Pipe Data (maintenance-information) (maintenance-information)

Unable to receive pipe data from the agent.

(S)
Cancels sending the pipe data and continues processing. The status of job execution may be incorrect.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT4681-W

An error occurred during an macro variable. (maintenance-information)

An error occurred during the analysis of the macro variable.

(S)
Abnormally terminates the job without creating the macro variable.

(O)
Re-execute the job as required.

KAVT4682-W

Length of a macro value exceed 4096 bytes.

The macro variable exceeded 4,096 bytes after conversion.

(S)
The length of the macro variable exceeded 4,096 bytes after conversion. Truncates the subsequent macro variables and continues processing.

(O)
The macro variables that has been truncated are not inherited. Check the macro variables and recheck the job definitions if you find a problem.

KAVT4683-W

There was an error in the prerequisite program.

An environment may be set incorrectly for linking the prerequisite program, or the prerequisite program may not be installed.

(S)
Terminates the reception of the events, and then pauses the message queue monitoring.

(O)
Check whether the prerequisite program is installed correctly and the environment is set correctly. Then, restart JP1/AJS3.
If you change the message queue system in the environment settings of JP1/AJS3, restart JP1/AJS3.

KAVT4684-E

Failed to analyze job data. (database-data) (error-code-of-the-function)

An error occurred in the function that analyzes job data.

(S)
Cancels processing.

(O)
Check whether the job is defined correctly.

KAVT4685-W

Definitions parameter (parameter) is not specified.

The required parameter is missing.

(S)
Terminates the job.

(O)
Check whether the job is defined correctly.

KAVT4687-E

There was an error in the prerequisite program.

An environment may be set incorrectly for linking the prerequisite program, or the prerequisite program may not be installed.

(S)
Terminates the transmission of the message queues.

(O)
Check whether the prerequisite program is installed correctly and its environment is set correctly. Then, re-execute the job.

KAVT4688-W

GET request is rejected for Queue (queue-name), because the request is not permitted: MQI-call-name maintenance-information

The MQRC_GET_INHIBITED error occurred during the MQI call of MQSeries or TP1/Message Queue.

(S)
Cancels the processing of the current queue and continues the processing of the remaining queue.

(O)
Examine the correction in the return code of the MQI call of MQSeries or TP1/Message Queue.

KAVT4689-I

Job request was accepted.: message-queue-linkage-file-name

A job request was accepted.

(S)
Processes the job request.

KAVT4690-I

Stop request was accepted.

A stop request was accepted.

(S)
Requests to terminate the message queue monitoring.

KAVT4691-I

Ended normally.: process-name queue-name maintenance-information)

The process indicated by process-name succeeded.

(S)
Continues processing.

KAVT4692-I

Queue (queue-name) is opened again.

The MQRC_Q_DELETE or MQRC_OBJECT_CHANGED error occurred during the MQI call of MQSeries or TP1/Message Queue. The queue is opened again.

(S)
Continues processing.

KAVT4693-I

Message was not found.: queue-name MQI-call-name maintenance-information

The MQRC_NO_MSG_AVAILABLE or MQRC_NO_MSG_UNDER_CURSOR error occurred during the MQI call of MQSeries or TP1/Message Queue.

(S)
Cancels the processing of the current queue and continues the processing of the remaining queue.

KAVT4694-I

The MQSeries process started.

The MQSeries process started.

(S)
Continues processing.

KAVT4695-E

Sending of the message queue is unusable.

Unable to send a message queue.

(S)
Cancels the transmission of the message queue.

(O)
Check whether the environment is set up for using the message queue linkage.

KAVT4696-I

The MQSeries process stopped.

The MQSeries process stopped.

(S)
Continues processing.

KAVT4697-I

The SUP stopped.

The SUP stopped.

(S)
Continues processing.

KAVT4698-W

The message queue monitoring process will now be retried.: maintenance-information: EN=response-time-at-termination, ST=response-time-at-startup, CH=response-time-during-processing

The message queue monitoring is retried.

(S)
Waits again until the message queue monitoring terminates.

(O)
Recheck the response time described in the maintenance information about the message queue monitoring.

KAVT4699-I

The retry of the message queue monitoring process finished.: retry-count

Retry of the message queue monitoring terminated.

(S)
Continues processing.

KAVT4700-E

The processing of the message queue monitor process did not finish.: retry-count

The message queue monitoring did not terminate.

(S)
Continues processing.

(O)
Recheck the response time and the retry count of the message queue monitoring. Also, stop JP1/AJS3, and terminate the jpocwtmqmaii and jp1mqsup processes. Then, restart JP1/AJS3.

KAVT4701-W

The status report of the message queue monitoring process failed.: maintenance-information: 2=unable-to-reserve-an-area, 4=unable-to-open-a-status-file, 8=unable-to-write-status, 16=unable-to-create-a-directory

The status of the message queue monitoring could not be reported.

(S)
Continues processing.

(O)
Use maintenance-information to determine the cause of the error and restart JP1/AJS3.

KAVT4951-E

An excess argument is specified.

An extra argument is specified.

(S)
Cancels command processing.

(O)
Delete an unnecessary argument, and then re-execute the command.

KAVT4952-E

No options are specified.

An option is not specified.

(S)
Cancels command processing.

(O)
Specify an option, and then re-execute the command.

KAVT4953-E

An invalid option is specified.

An invalid option is specified.

(S)
Cancels command processing.

(O)
Specify the correct option, and then re-execute the command.

KAVT4954-I

A SUP stop was requested.

The termination of SUP was requested.

(S)
Continues processing.

KAVT4955-E

SUP could not be stopped.

Requesting to stop SUP was impossible.

(S)
Cancels command processing.

(O)
Check the cause of the error from the error message issued for the startup command. Then take action.

KAVT4956-I

A SUP restart was requested.

The restart of SUP was requested.

(S)
Continues processing.

KAVT4957-E

SUP could not be restarted.

Restarting SUP was impossible.

(S)
Cancels command processing.

(O)
Check the cause of the error from the error message issued for the startup command. Then take action.

KAVT4958-E

The pipe could not be opened: pipe name: pipe-name (error-number, error-message)

Opening a pipe was impossible.

(S)
Cancels command processing.

(O)
Check the cause of the error from the error message and take action.

KAVT4959-E

The pipe could not be written to when SUP started: pipe-name (error-number, error-message)

Writing a pipe at SUP startup time was impossible.

(S)
Stops the daemon for message queue monitoring.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4960-I

Data was written to a pipe: pipe name: pipe-name (command-name)

Data was written to a pipe.

(S)
Continues processing.

KAVT4961-E

The pipe could not be closed: pipe name: pipe-name (error-number, error-message)

Closing a pipe was impossible.

(S)
Continues processing.

(O)
Check the cause of the error from the system error message. Then take action.

KAVT4962-E

For execution, you must have permissions.

The privilege of the user is invalid to execute the command.

(S)
Cancels processing.

(O)
Check the permission of the logged-in user, and then retry.

KAVT5251-I

The processing of MSMQ sending will now start.

The transmission of the MSMQ starts.

(S)
Starts processing.

KAVT5252-I

The processing of MSMQ sending will now stop.

The transmission of the MSMQ stops.

(S)
Terminates processing.

KAVT5253-E

The parameter is specified incorrectly. (data-specified-in-parameter)

The specified parameter is invalid.

(S)
Cancels processing.

(O)
Specify necessary items.

KAVT5254-E

The parameter is specified incorrectly. (data-specified-in-environment-variable)

The specified parameter is invalid.

(S)
Cancels processing.

(O)
Specify necessary items.

KAVT5255-E

The data is specified incorrectly. (data-checked-for-character-string)

The specified data is incorrect.

(S)
Cancels processing.

(O)
Specify necessary items.

KAVT5256-E

A required item is not designated.

A required item is missing.

(S)
Cancels processing.

(O)
Specify necessary items.

KAVT5264-E

The MSMQ service is not running. (service-status-code)

The MSMQ service is not started.

(S)
Continues processing.

(O)
Start the MSMQ service.

KAVT5265-E

The MSMQ service does not exist. (service-status-code)

The MSMQ service does not exist.

(S)
Cancels processing.

(O)
Install MSMQ.

KAVT5266-E

Information about the MSMQ service could not be acquired. (service-status-code)

Acquiring the MSMQ service status was impossible.

(S)
Cancels processing.

(O)
Check whether the MSMQ service is running normally.

KAVT5267-E

The MSMQ server is not connected.

Connection to the MSMQ server is impossible.

(S)
Continues processing.

(O)
Start the MSMQ server.

KAVT5268-E

The connection with the MSMQ server cannot be confirmed. (service-status-code)

Connection to the MSMQ server is impossible.

(S)
Continues processing.

(O)
Check whether the MSMQ server is connected to MSMQ of the JP1/AJS3 - Agent machine.

KAVT5269-E

Message sending will now stop because an error that stops processing occurred.

The system cancels sending a message because a fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check whether the MSMQ service is running normally.

KAVT5272-E

The queue with the specified queue label name was not found.

The queue in the queue label name is missing.

(S)
Cancels processing.

(O)
Check whether the queue label name is correct using the MSMQ explorer.

KAVT5273-E

The queue could not be opened. (return-value-of-MQ-function)

Opening a queue was impossible.

(S)
Cancels processing.

(O)
Check whether the path name of a queue is correct or the access permission exists.

KAVT5274-E

Messages could not be sent. (return-value-of-MQ-function)

Sending a message was impossible.

(S)
Cancels processing.

(O)
Check the queue access permission.

KAVT5275-E

The queue could not be closed. (return-value-of-MQ-function)

Closing a queue was impossible.

(S)
Continues processing.

(O)
Check whether sending or receiving a message terminated.

KAVT5276-E

The format name could not be acquired from the path name of the queue. (return-value-of-MQ-function)

Acquiring a format name from the queue path name was impossible.

(S)
Cancels processing.

(O)
Check whether the queue path name is correct.

KAVT5277-E

An error occurred during an MSMQ access. (MQInstanceToFormatName) (return-value-of-MQ-function)

An error occurred while accessing MSMQ.

(S)
Cancels processing.

(O)
Check whether the queue path name is correct.

KAVT5278-E

An error occurred during an MSMQ access. (MQLocateBegin) (return-value-of-MQ-function)

An error occurred while accessing MSMQ.

(S)
Cancels processing.

(O)
Check whether the queue label name is correct.

KAVT5279-E

An error occurred during an MSMQ access. (MQLocateNext) (return-value-of-MQ-function)

An error occurred during the accessing of MSMQ.

(S)
Cancels processing.

(O)
Check whether the MSMQ service is running normally.

KAVT5280-E

An error occurred during an MSMQ access. (MQLocateEnd) (return-value-of-MQ-function)

An error occurred during the accessing of MSMQ.

(S)
Cancels processing.

(O)
Check whether the MSMQ service is running normally.

KAVT5281-E

An error occurred during analysis of command arguments. (return-value-of-MQ-function)

An error occurred during the analysis of the command argument.

(S)
Cancels processing.

(O)
Check whether the command argument is correct.

KAVT5286-E

The MSMQ message queue linkage function is unavailable.

Using the MSMQ message queue linkage function is impossible.

(S)
Cancels processing.

(O)
Check whether the MSMQ service is running normally.

KAVT5287-E

Message Reception Monitoring Interval is assumed because registry information was not acquired successfully.

Since the registry information could not be acquired, the interval for the message reception monitoring is assumed.

(S)
Assumes the default interval of the message reception monitoring and continues processing.

(O)
Determine the cause of the error preventing you from acquiring the registry information.

KAVT5291-E

The message text file could not be opened.

Opening a message text file was impossible.

(S)
Cancels processing.

(O)
Check whether the file path name is correct.

KAVT5292-E

The size of a message text file could not be acquired.

Acquiring the message text file size was impossible.

(S)
Cancels processing.

(O)
Check the file status.

KAVT5293-E

Memory could not be allocated.

Allocating memory was impossible.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT5294-E

The message text file could not be read.

Reading a message text file was impossible.

(S)
Cancels processing.

(O)
If memory is not enough, allocate memory. Otherwise, check the file status.

KAVT5295-E

The message text file could not be closed.

Closing a message text file was impossible.

(S)
Continues processing.

(O)
Check the file status.

KAVT5297-E

A message could not be sent (return-value-of-MQ-function).

Sending a message was impossible.

(S)
Cancels processing.

(O)
Check the content of the previous message.

KAVT5307-E

The individual information file could not be accessed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Accessing the individual information file was impossible.

(S)
Cancels processing.

(O)
Check the variable, and then retry.

KAVT5308-E

The registry information could not be acquired. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Acquiring the registry information was impossible.

(S)
Assumes a value and continues processing.

(O)
Check whether the registry information is correct.

KAVT5309-I

Message Reception Monitoring Interval is assumed because registry information was not acquired successfully. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Since the registry information could not be acquired, the interval for the message reception monitoring is assumed.

(S)
Assumes the default interval of the message reception monitoring and continues processing.

(O)
Determine the cause of the error preventing you from acquiring the registry information.

KAVT5311-E

Messages could not be received because initialization failed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Initializing was impossible.

(S)
Cancels processing.

(O)
Restart the JP1/AJS3 service or the OS.

KAVT5312-E

Messages cannot be received because an error that stops processing occurred. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

A fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check the content of the previous message.

KAVT5313-E

An error occurred in the end processing. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

An error occurred in a termination.

(S)
Continues processing.

(O)
Check the file or queue status.

KAVT5315-I

A message was received. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

A message was received.

(S)
Continues processing.

KAVT5332-E

Memory could not be allocated. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Allocating memory was impossible.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT5338-E

Message reception will now end because an error that stops processing occurred. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The message reception terminates because a fatal error that stops processing occurred.

(S)
Cancels processing.

(O)
Check the content of the previous message.

KAVT5339-I

Although notification of Monitoring Interval failed, the message continued to be received. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The monitoring interval could not be notified but the messages continue to be received.

(S)
Continues processing.

KAVT5340-E

The queue could not be closed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The queue could not be closed.

(S)
Continues processing.

(O)
Use ErrCode=ErrorCode-number and GetLastErrorCode=GetLastError-number to determine the cause of the error.

KAVT5342-E

The CCSID code is invalid. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The CCSID code is invalid.

(S)
Cancels processing.

(O)
Check the code.

KAVT5343-E

The entered code is invalid. (ASCII) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The input code is invalid. (ASCII)

(S)
Cancels processing.

(O)
Check the code.

KAVT5344-E

The entered code is invalid. (EBCDIC) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The input code is invalid. (EBCDIC)

(S)
Cancels processing.

(O)
Check the code.

KAVT5345-E

The entered code is invalid. (EBCDIC) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The input code is invalid. (EBCDIC)

(S)
Cancels processing.

(O)
Check the code.

KAVT5346-E

The OWNCCSID code is invalid. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The OWNCCSID code is invalid.

(S)
Cancels processing.

(O)
Check the code.

KAVT5352-E

Terminating because the pipe connection thread did not end. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Some internal threads did not terminate during the termination of the MSMQ monitoring. Forcibly terminates the internal threads.

(S)
Continues processing.

(O)
If the system outputs this message during the termination of JP1/AJS3, check whether the MSMQ reception monitoring works normally at the next start of JP1/AJS3.
If MSMQ reception monitoring does not work normally after the system outputs this message during an operation other than the termination of JP1/AJS3, restart JP1/AJS3.

KAVT5356-I

End processing was forced. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Termination is forced.

(S)
Continues processing.

KAVT5358-E

The queue could not be opened: (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Opening a queue was impossible.

(S)
Cancels processing.

(O)
Check the path name and access permission.

KAVT5359-E

An open error is being reported to ICON. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The system notified an open error to ICON.

(S)
Cancels processing.

(O)
Check the path name and access permission.

KAVT5364-E

There is no message: Maintenance-information

No message exists.

(S)
Continues monitoring.

(O)
Check whether the monitoring conditions are correct if a message is sent to the monitoring queue.

KAVT5367-E

Initialization failed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Initialization failed.

(S)
Cancels processing.

(O)
Restart the service and the OS.

KAVT5368-E

There was an error in the prerequisite program. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

MSMQ may not be installed.

(S)
Cancels processing.

(O)
Install MSMQ.

KAVT5371-E

Messages could not be received because the format name could not be acquired from the path name of the queue. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The system could not receive a message because acquiring a format name from the queue path name was impossible.

(S)
Cancels processing.

(O)
Check whether the queue path name is correct.

KAVT5372-E

Messages could not be received because the queue could not be opened. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The system could not receive a message because opening a queue was impossible.

(S)
Cancels processing.

(O)
Check the queue path name and access permission.

KAVT5373-E

An error occurred during message reception. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

An error occurred during the reception of a message.

(S)
Cancels processing.

(O)
Check the content of the previous message.

KAVT5374-E

Memory could not be allocated during message reception. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Allocating memory was impossible while receiving a message.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT5376-E

The status of the queue was changed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The system changed the queue status.

(S)
Closes and reopens a queue, and then continues monitoring.

(O)
Check the queue status.

KAVT5377-E

The queue was deleted. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

A queue was deleted.

(S)
Closes and reopens a queue, and then continues monitoring.

(O)
Use the MSMQ explorer to create a queue.

KAVT5378-E

The MSMQ service is not running. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The MSMQ service is not running.

(S)
Continues processing.

(O)
Start the MSMQ service.

KAVT5379-E

The MSMQ server cannot be connected. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Connection to the MSMQ server was impossible.

(S)
Continues processing.

(O)
Check whether the file path name is correct.

KAVT5380-E

Messages could not be received because memory could not be allocated. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Receiving a message was impossible because memory allocation failed.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT5381-E

Message could not be received because an error that stops processing occurred during message reception.

A fatal error that stops processing occurred during the reception of the message.

(S)
Cancels processing.

(O)
Check the content of the previous message.

KAVT5382-E

The file for storing messages could not be output. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Outputting a message storage file was impossible.

(S)
Continues processing.

(O)
Check whether the file path name is correct.

KAVT5383-E

The queue handle is invalid. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

The queue handle is invalid.

(S)
Closes and reopens a queue, and then continues monitoring.

(O)
Check the queue status.

KAVT5384-E

An error occurred during an MSMQ access. (MQCreateCursor). (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

An error occurred during the accessing of MSMQ.

(S)
Cancels processing.

(O)
Check the queue status.

KAVT5385-E

The inherited information file could not be output. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)

Outputting an inheritance information file was impossible.

(S)
Cancels processing.

(O)
Check whether there is sufficient disk space.
For details on the amount of disk space required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT5451-I

The MSMQ linkage communication process will now start.

The MSMQ linkage communication starts.

(S)
Continues processing.

KAVT5452-I

The MSMQ linkage communication process started.

The MSMQ linkage communication started.

(S)
Continues processing.

KAVT5453-I

The MSMQ linkage communication process stopped.

The MSMQ linkage communication stopped.

(S)
Terminates processing.

KAVT5454-I

The MSMQ reception monitoring will now start.

The MSMQ reception monitoring starts.

(S)
Terminates processing.

KAVT5455-E

The MSMQ reception monitoring will now stop.

The system stops the MSMQ reception monitoring.

(S)
Cancels processing.

(O)
See the message output before this message to examine the cause of the error.

KAVT5456-I

The reception of messages that satisfy the conditions was confirmed.

The reception of messages that satisfies the conditions was confirmed.

(S)
Continues processing.

KAVT5457-I

Monitoring of MSMQ reception will now end because the time-out period elapsed.

The MSMQ reception monitoring terminates because the timeout period expired.

(S)
Continues processing.

KAVT5461-W

An error occurred during creation of a macro variable.

An error occurred during creation of a macro variable.

(S)
Continues processing.

(O)
Check whether the macro variables to be taken over are correct.

KAVT5462-W

A macro variable exceeds 4096 bytes. Some macro variables could not be created.

The number of bytes used in macro variables reached 4096. The system failed to create some macro variables.

(S)
Continues processing.

(O)
Check whether the macro variables to be taken over are correct.

KAVT5464-W

The MSMQ monitor process is not running.

The MSMQ monitor process is not running.

(S)
Cancels processing.

(O)
Starts the OpenTP1 or MSMQ service.

KAVT5465-I

The start of the MSMQ monitor process was confirmed.

The start of the MSMQ monitoring was confirmed.

(S)
Continues processing.

KAVT5466-E

The definition of the MSMQ monitor job is invalid.

The job for the MSMQ reception monitoring is defined incorrectly.

(S)
Cancels processing.

(O)
Check the definition of the job.

KAVT5467-E

Memory became insufficient.

Memory became insufficient.

(S)
Cancels processing.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT6001-I

The JP1 event send command has started.

The JP1 event send command starts.

(S)
Continues processing.

KAVT6002-I

The JP1 event send command ended.

The JP1 event send command terminates

(S)
Continues processing.

KAVT6003-E

No event ID is specified.

No event ID is specified.

(S)
Cancels processing.

(O)
Check the definitions to see if an event ID is specified. When an event ID is specified, contact the system administrator.

KAVT6004-E

An error occurred in the event service. (return-code-of-jevsend-command)

An error occurred in the event service.

(S)
Cancels processing.

(O)
Find the cause of the error from the return code of the jevsend command, correct the error, and then retry.

KAVT6005-E

The installation path of JP1/Base could not be obtained.

The system could not obtain the directory to install JP1/Base. The registry information about Windows may be corrupted.

(S)
Cancels processing.

(O)
Check the registry information about JP1/Base. If the registry information is corrupted, reinstall JP1/Base and restart JP1/AJS3. Then, retry.

KAVT6006-E

Memory became insufficient.

Memory became insufficient.

(S)
Cancels processing.

(O)
Check whether there is sufficient memory for executing the program. Then, retry.

KAVT6100-E

Transmission of the JP1 event was not possible.

The system could not send a JP1 event.

(S)
Cancels processing.

(O)
Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred in the JP1/Base event service.

KAVT6101-E

Confirmation of JP1 event arrival was not possible.

The system checked JP1 event arrival for the specified number of times, but it could not confirm the arrival of any JP1 event.

(S)
Cancels processing.

(O)
Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred in the JP1/Base event service.

KAVT6102-I

Event sending host=event-destination-host-name

The system displays the name of the event transmission destination host. The system outputs this message only when it checks event arrival.

(S)
Continues processing.

KAVT6103-I

The JP1 event was able to transmit a message.

The JP1 event was transmitted.

(S)
Terminates processing.

KAVT6104-E

An attempt to acquire the event sending source host name (local-host-name) failed. maintenance-information

Since the name of the event transmission source host was not specified, the system assumed the local-host name to be the name of the event transmission source host. The system attempted to obtain the local-host name, but it failed.

(S)
Cancels processing.

(O)
Check whether the network settings are correct and whether the host name is specified correctly. If you cannot solve the problem, specify the event transmission destination host and then re-execute the operation.

KAVT7001-I

Timer monitoring process will now start.

The execution interval control process will now start.

(S)
Continues processing.

KAVT7002-I

Timer (timer-value min) monitoring will now start.

The timer monitoring starts.

(S)
Continues processing.

KAVT7003-I

Timer (timer-value min) is over.

The timer expired.

(S)
Terminates processing.

KAVT7004-I

Timer monitoring process will now end.

The execution interval control process will now terminate.

(S)
Terminates processing.

KAVT7005-W

The time-out period elapsed.

A timeout occurred. The system cancels executing the job.

(S)
Cancels processing.

KAVT7006-W

A kill request was accepted.

The system received a request to terminate the job forcibly, so it terminates the job forcibly.

(S)
Cancels processing.

KAVT7007-E

Timer monitoring process ended. (maintenance-information)

The execution interval control process terminated because it detected an error.

(S)
Terminated the process because an error that prevents further processing occurred during processing. An Interval Control job cannot be monitored.

(O)
The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVT7008-W

The memory for message output became insufficient. (maintenance-information)

Memory became insufficient. The message cannot be output to the detailed log.

(S)
Continues processing without outputting a message to the detailed log because memory is insufficient.

(O)
Check whether memory is sufficient.
For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.

KAVT7009-E

Memory became insufficient. (maintenance-information)

Memory became insufficient. The job terminates.

(S)
Terminates the job abnormally due to insufficient memory.

(O)
Check whether there is sufficient memory for executing the program. Then, use JP1/AJS3 - View to examine the event job that caused the error, and then re-execute that job.

KAVT7010-E

An attempt to start the timer monitoring process failed. (maintenance-information) (maintenance-information)

An attempt to start the execution interval control process has failed.

(S)
Terminates the process because an error that prevents further processing occurred during startup of the execution interval control process. An Interval Control job cannot be monitored.

(O)
Make sure that resources are sufficient, and then restart JP1/AJS3.

KAVT7011-E

An attempt to obtain pipe data failed. (maintenance-information) (maintenance-information)

The execution interval control process terminates because an error occurred during inter-process communication with the agent process.

(S)
Terminates the execution interval control process because an error occurred during inter-process communication with the agent process. An Interval Control job cannot be monitored.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
After the check, restart JP1/AJS3.

KAVT7012-E

An attempt to send pipe data failed. (maintenance-information) (maintenance-information)

Interprocess communication with the agent has failed.

(S)
An error occurred during inter-process communication with the agent. The system terminates the execution interval control process depending on the location where the error occurred. If this process is terminated, the Interval Control job cannot be monitored. The Interval Control job may have failed to detect an event.

(O)
Check whether the system resources are sufficient and whether the directory created at JP1/AJS3 installation was unintentionally deleted. If the execution interval control process has started, use JP1/AJS3 - View to check the event job that caused the error, and then re-execute that job. If the execution interval control process has stopped, restart JP1/AJS3.

KAVT7013-E

An error occurred during the operation of a file. (maintenance-information) (maintenance-information)

An attempt to open the information file used for the execution interval control process has failed.

(S)
Cannot start monitoring for the job.

(O)
Check whether the system resources are sufficient and whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
After the check, use JP1/AJS3 - View to examine the event job that caused the error, and then re-execute that job.

KAVT7014-E

An error exists in the definition contents of the timer monitoring job. (maintenance-information) (LINE=maintenance-information)

An incorrect definition is made for the timer monitoring job.

(S)
Abnormally terminates the job because an invalid definition is made for the timer monitoring job.

(O)
Check the definition. Then, retry.

KAVT7015-E

An attempt to set the next time monitoring failed. (maintenance-information) (maintenance-information)

The Interval Control job terminated abnormally because the system resources were insufficient.

(S)
Sufficient resources for performing the next monitoring are not available. The system abnormally terminates the Interval Control job.

(O)
Check the following:
  • Check whether system resources are sufficient.
After the check, use JP1/AJS3 - View to check the event job that caused the error, and then re-execute that job.

KAVT7016-W

A macro variable exceeds 4096 bytes.

A converted macro variable has exceeded 4,096 bytes.

(S)
Truncates the portion after the 4,096th byte and continues processing. The maximum value for macro variables is 4,096 bytes.

(O)
The portion of the macro variable exceeding the 4,096th byte is not passed to the succeeding jobnet or job. Check the status of the jobnet or job. If you find any problem, recheck the definition of the job.

KAVT7501-E

Invalid parameter specification. (specified-parameter)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)
Cancels processing.

(O)
Check the definition of the specified parameter, and then retry.

KAVT7502-E

Invalid environment variable specification. (specified-environment-variable)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)
Cancels processing.

(O)
Check the definition of the specified parameter, and then retry.

KAVT7503-E

Invalid data specification. (specified-data)

An incorrect parameter is specified in the hp OpenView Status Report job.

(S)
Cancels processing.

(O)
Check the definition of the specified parameter, and then retry.

KAVT7506-I

The status report will now start.

The status report starts.

(S)
Continues processing.

KAVT7507-I

The status report will now end.

The status report terminates.

(S)
Terminates processing.

KAVT7508-E

Could not report status. SNMP service is not installed.

The job failed to report the status because the SNMP service was not installed.

(S)
Cancels processing.

(O)
Install the SNMP service.

KAVT7509-E

Could not report status. SNMP service is not started.

The job failed to report the status because the SNMP service was not started.

(S)
Cancels processing.

(O)
Start the SNMP service.

KAVT7510-E

Could not report status. SNMP service community name is not established.

The job failed to report the status because the community name for the SNMP service was not specified.

(S)
Cancels processing.

(O)
Specify the community name for the SNMP service.

KAVT7511-E

The status could not be reported because the destination of the SNMP service trap was not specified.

The job failed to report the status because the trap destination was not specified for the SNMP service.

(S)
Cancels processing.

(O)
Specify the trap destination for the SNMP service.

KAVT7512-E

Failed to report status. (Code=code-for-status-report-error)

The status could not be reported.

(S)
Cancels processing.

(O)
If the code indicated in code-for-status-report-error is 10, check whether the hp OpenView Status Report job was executed by a JP1 user with superuser privileges.
If the code is other than 10, contact the system administrator.

KAVT7513-E

Error in status specification. (string-specified-as-status)

An incorrect status is specified.

(S)
Cancels processing.

(O)
Specify a correct status.

KAVT7514-I

The status was reported. (status=status-that-has-been-sent, info=additional-information-about-the-status)

The status was reported.

(S)
Terminates processing.

KAVT8001-I

The common environment definition command will now start.

The common environment definition command starts.

(S)
Starts processing.

KAVT8002-I

The common environment definition command will now end.

The common environment definition command terminates.

(S)
Terminates the command.

KAVT8003-E

The parameter is specified incorrectly.

An incorrect parameter is specified.

(S)
Cancels processing.

(O)
Specify correct definition parameters, and then retry.

KAVT8004-E

The environment variable is specified incorrectly. (specified-environment-variable)

An incorrect environment variable is specified.

(S)
Cancels processing.

(O)
Check the status of the system resource, and then retry.

KAVT8005-E

The data is specified incorrectly. (specified-data)

Incorrect data is specified.

(S)
Cancels processing.

(O)
Check the definition parameter.

KAVT8007-E

The configuration definition could not be read. (error-code)

The system failed to write the configuration information.

(S)
Cancels processing.

(O)
Check whether the user has the superuser privilege.

KAVT8008-E

A required item is missing.

A required item is not specified.

(S)
Cancels processing.

(O)
Check whether all the required items are specified.

KAVT8009-I

The mail linkage setting was canceled.

The settings for the mail linkage were canceled.

(S)
Terminates the command.

KAVT8010-E

The parameter is specified incorrectly.

An incorrect parameter is specified.

(S)
Cancels processing.

(O)
Check whether the correct parameter is specified. Then, retry.

KAVT8011-E

You are not authorized to access the configuration definition. (error-code)

You are not authorized to access the configuration definition.

(S)
Cancels processing.

(O)
Check whether the environment is set up to access the configuration information, and then retry.

KAVT8012-E

The specified key does not exist in the configuration definition. (error-code)

The specified key does not exist in the configuration definition.

(S)
Cancels processing.

(O)
Check whether JP1/AJS3 is correctly installed.

KAVT8013-E

An unexpected error occurred. (error-code)

An unexpected error occurred.

(S)
Cancels processing.

(O)
Contact the system administrator.

KAVT8014-I

The message queue environment setting command will now start.

The command to set the environment of the message queue starts.

(S)
Continues processing.

KAVT8015-I

The message queue environment setting command will now end.

The command to set the environment of the message queue terminates.

(S)
Terminates the command.

KAVT8016-I

The MSMQ environment setting command will now start.

The command to set the environment of MSMQ starts.

(S)
Continues processing.

KAVT8017-I

The MSMQ environment setting command will now end.

The command to set the environment of MSMQ terminates.

(S)
Terminates the command.

KAVT8018-I

The mail environment setting command will now start.

The command to set the mail environment starts.

(S)
Continues processing.

KAVT8019-I

The mail environment setting command will now end.

The command to set the mail environment terminates.

(S)
Terminates the command.

KAVT8020-E

The specified data is not used on the current platform. (specified-data)

The specified data is not used for the current platform.

(S)
Cancels processing.

(O)
Check whether the data can be used in the current platform, and then retry.

KAVT8021-E

Environment setup did not end normally.

The setup of the environment terminated abnormally.

(S)
Terminates the command.

(O)
See the message output before this message to examine the cause of the error.

KAVT8022-E

For execution, you must have Administrator permissions.

The command must be executed by a user who has Administrator permissions.

(S)
Cancels processing.

(O)
Check the authority of the login user, and then retry.

KAVT8023-I

The message queue linkage settings were canceled.

The settings for the message queue linkage were canceled.

(S)
Terminates the command.

KAVT8024-I

The MSMQ linkage setting was canceled.

The settings for the MSMQ linkage were canceled.

(S)
Terminates the command.

KAVT8025-E

The data length is invalid. (error-code)

The data length is incorrect.

(S)
Cancels processing.

(O)
Check whether the data length is within the specifiable range.

KAVT8026-E

Memory became insufficient. (Maintenance-information)

Memory is insufficient.

(S)
Cancels processing.

(O)
Get enough memory to process and re-execute.

KAVT8107-E

Memory became insufficient.

Memory became insufficient.

(S)
Cancels processing.

(O)
Allocate sufficient memory for execution. Then, retry.

KAVT8301-I

The command terminated normally.

Listing terminated normally.

(S)
Terminates command execution.

KAVT8302-W

The command terminated abnormally.

The command terminated abnormally due to an error.

(S)
Terminates command execution.

(O)
See the message output before this message to examine the cause of the error and correct it. Then, re-execute the command.

KAVT8303-E

Value for option (option) is not specified.

A value is missing for the option that needs a value.

(S)
Cancels command execution.

(O)
Specify the value for the option, and then re-execute the command.

KAVT8304-E

Extra argument(s) exist.

An unnecessary argument exists.

(S)
Cancels command execution.

(O)
Delete the unnecessary argument, and then re-execute the command.

KAVT8305-E

Invalid value for option (option)

The option contains an invalid value.

(S)
Cancels command execution.

(O)
Correct the value for the option, and then re-execute the command.

KAVT8306-E

Option (option) appears twice or more.

The same option is specified more than once.

(S)
Cancels command execution.

(O)
Specify the option only once, and then re-execute the command.

KAVT8307-E

Cannot specify these options together.

You specified the options that could not be used simultaneously.

(S)
Cancels command execution.

(O)
Delete one or the other of the options, and then re-execute the command.

KAVT8308-E

Insufficient memory occurred. (maintenance-information))

Memory became insufficient.

(S)
Cancels command execution.

(O)
Check whether there is sufficient memory.

KAVT8310-W

Because the data was long, the data was truncated and then displayed. (data-truncated (up-to-900-bytes) (name-of-the-item-displayed)

The data to be displayed was unexpectedly long. The data is truncated and then displayed.

(S)
Continues command execution.

(O)
Check whether JP1/AJS3 runs correctly.

KAVT8311-W

The deleting of files failed. (maintenance-information))

The work file could not be deleted during termination.

(S)
Continues command execution.

(O)
Delete the sys_bak folder (directory) under the folder (directory) that stores the work file.

KAVT8312-E

The copying of files failed. (maintenance-information))

The file could not be opened.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8313-W

An error occurred during the access of job data. (error-code) (function-name) (maintenance-information))

An error occurred while accessing the database.

(S)
Continues command execution. The system cannot display the name of the appropriate job and its jobnet name.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
  • If maintenance is in progress, wait until the maintenance finishes and then re-execute the command.

KAVT8314-E

An error occurred during communication with the agent. (error-code) (function-name) (maintenance-information))

Pipes could not be created in, written into, or read from the agent.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
For a cluster system, make sure that the command is not executed in the standby system, and then re-execute the command in the active system.

KAVT8315-W

An error occurred during communication with the monitoring process. (error-code) (function-name) (maintenance-information))

Pipes could not be created in, written into, or read from the monitoring process.

(S)
Continues command execution. The system may not display Status correctly.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8316-E

An error occurred during the access of the agent information file. (error-code) (function-name) (maintenance-information))

An error occurred while accessing (opening, etc.) the information file of the agent.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8317-W

An error occurred during the access of the monitoring process information file. (error-code) (function-name) (maintenance-information))

An error occurred while accessing (opening, etc.) the information file of the monitoring process.

(S)
Continues command execution. The system may not display Status correctly.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8319-E

For execution, you must have Administrator permission.

You are not logged on as a user with the Administrators permission.

(S)
Cancels command execution.

(O)
Log on as a user with the Administrators permission, and then retry.
If the UAC function is enabled in Windows, the administrator must re-execute the command.

KAVT8320-E

The host name could not be obtained. (error-code) (function-name) (maintenance-information))

The host name could not be obtained.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether JP1/AJS3 and JP1/Base have been installed correctly.
  • Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8321-E

The installation path could not be acquired.

The installation path could not be acquired.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether JP1/AJS3 and JP1/Base have been installed correctly.
  • Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8322-E

The configuration definition could not be read.

The configuration definitions could not be read.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether JP1/AJS3 and JP1/Base have been installed correctly.
  • Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.

KAVT8323-E

The registration file could not be read. (path-name) (function-name) (maintenance-information))

The registration file could not be read.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8324-W

The definition information file could not be read. (error-code) (function-name) (maintenance-information))

The definition information file could not be read.

(S)
Continues command execution. The system may not display some data.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8325-W

The unreported information file could not be read. (function-name) (maintenance-information))

The agent-unreported information file could not be read.

(S)
Continues command execution. The system may not display the information correctly.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8327-W

There is no data so data cannot be displayed. (name-of-the-item-displayed) (maintenance-information))

There is no data of the requested value. The data cannot be displayed.

(S)
Continues command execution.

(O)
Check whether the JP1/AJS3 service has been started or whether maintenance is being performed on the service.

KAVT8328-E

There is no specified host name. (host-name) (function-name)

There is no host name that is specified by the -h operand or the JP1_HOSTNAME environment variable.

(S)
Cancels command execution.

(O)
Check whether there is the host name specified or the environment of JP1/AJS3 is set correctly.

KAVT8329-E

The exclusion information could not be obtained. (error-code) (function-name)

The exclusion information could not be obtained.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8330-E

Exclusion failed. (error-code) (function-name)

A lock could not be completed when one of the following commands was executed:

  • jpoagtjobshow
  • jpomanevreset
  • jpomanevshow
  • jpomanjobshow

(S)
Cancels command execution.

(O)
Check the following, and then re-execute the command:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
  • Check whether an attempt was made to concurrently execute more than one command with the same name.
  • For a cluster system, check whether the command was executed on the standby node.
For a cluster system, re-execute the command on the primary node.

KAVT8331-W

Deletion of the exclusion file failed. (error-code) (function-name)

The exclusion file could not be deleted during termination.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8332-E

Exclusion is being applied. (error-code) (function-name)

A lock is being applied by execution of one of the following commands:

  • jpoagtjobshow
  • jpomanevreset
  • jpomanevshow
  • jpomanjobshow

(S)
Cancels command execution.

(O)
Check whether an attempt was made to concurrently execute more than one command with the same name. Wait until execution of the preceding command terminates, and then re-execute the command.

KAVT8333-E

The agent is not running.

The agent has not been started.

(S)
Cancels command execution.

(O)
Check whether the agent has been started. Restart JP1/AJS3 as required.
For a cluster system, make sure that the command is not executed in the standby system, and then re-execute the command in the active system.

KAVT8334-E

The manager name storage file could not be created. (error-code) (function-name) (maintenance-information))

The manager name storage file could not be created or written into.

(S)
Cancels command execution.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVT8335-E

A contradiction was detected during communication.

The event job information which differs from the one acquired by the command is detected.

(S)
Cancels command execution.

(O)
Collect data about this internal error and then contact the system administrator.

KAVT8336-E

Some agent information could not be written.

Some agent information could not be written.

(S)
Lists the event jobs (the system may not display some data), and then abnormally terminates the command.

(O)
Use the integrated trace information log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8337-W

Some monitoring process information could not be written. (monitoring-process-name)

Some information about the monitoring process could not be written.

(S)
Continues command execution. The system may not display Status correctly.

(O)
Use the integrated trace information log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8338-E

None of the agent information could be written.

None of the agent information could not be written.

(S)
Cancels command execution.

(O)
Use the integrated trace information log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8339-W

None of the monitoring process information could be written. (monitoring-process-name)

None of the monitoring process information could be written.

(S)
Continues command execution. The system may not display Status correctly.

(O)
Use the integrated trace information log to determine the cause of the error which prevented the information to be written and take action to correct it.

KAVT8340-E

The main loop of the jpoagtjobshow command failed. (maintenance-information)

The main loop of the jpoagtjobshow command could not be started.

(S)
Cancels command execution.

(O)
Check whether the system resource is sufficient or the privilege of the user is valid. Then, retry.

KAVT8341-E

This command cannot be executed because the JP1/AJS2 service is running.

This command cannot be executed because the target JP1/AJS3 scheduler service is running.

(S)
Cancels execution of the command.

(O)
Stop the target JP1/AJS3 scheduler service, and then re-execute the command.

KAVT8342-E

A file access error occurred. (file-name) (maintenance-information)

An error occurred during access to the file indicated in file-name.

(S)
Performs different operations depending on the executed command.

jpomanevreset command
Continues execution of the command. However, the following may occur:
  • Unnecessary files remain.
  • Information on the agent is not deleted.

jpomanevshow command
Cancels execution of the command.

(O)
Take appropriate action depending on the executed command.

jpomanevreset command
Do the following:
  • Check the file indicated in the message. If the file still remains, you must delete it manually before starting JP1/AJS3. If neither remove nor DeleteFile is contained in maintenance-information, do not delete the file. Instead, correct the cause of unsuccessful access to the file, and then re-execute the command.
  • If you did not specify the -s option, information may still remain on the agent. Perform a cold start manually for JP1/AJS3 on the agent.

jpomanevshow command
Check the following and then re-execute the command:
  • Check whether the system resources are sufficient.
  • Check whether the permission environment of the starting user is correct.
  • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally.

KAVT8343-W

An attempt to communicate with the agent has failed. (agent-host-name) (maintenance-information)

An attempt to communicate with the agent indicated in agent-host-name has failed.

(S)
Continues execution of the command. However, information on the agent may remain undeleted.

(O)
Check the following:
  • Check whether the agent host and JP1/AJS3 have started.
  • Check whether the host name is determined.
    If it has not, check the settings of the JP1_HOSTNAME environment variable, the hosts file, or the DNS server.
  • Check whether the JP1/AJS3 port number is registered in the services file.
    If it is not registered, register it.
Since the information on the agent where the error occurred is not deleted, you must perform a cold start for the JP1/AJS3 service on the agent, as required.

KAVT8351-E

Specified Scheduler service not exist (scheduler-service-name)(maintenance-information).

The scheduler service specified for the -F operand or the DEFAULTSERVICENAME environment setting parameter does not exist.

(S)
Cancels command execution.

(O)
Check whether:
  • The scheduler service specified in the -F option, AJSCONF environment variable, or DEFAULTSERVICENAME environment setting parameter exists on the host specified for the -h option.
  • The JP1/AJS3 environment settings are correct.

KAVT8352-E

Shared memory is not available(maintenance-information).

Shared memory required for command execution is not available.

(S)
Cancels command execution.

(O)
Check whether:
  • The JP1/AJS3 host service is running.
  • System resources (shared memory) are sufficient.

KAVT8401-E

The initialization of communication with the jpoagtjobshow command failed. (return-code) (line-number)

The communication with the jpoagtjobshow command could not be initialized.

(S)
Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
If you want to display the correct information using the jpoagtjobshow command, restart JP1/AJS3.

KAVT8402-E

The reading of requests from the jpoagtjobshow command failed. (return-code)

Requests could not be read from the pipes for the jpoagtjobshow command.

(S)
Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8403-E

A request from jpoagtjobshow command is invalid. (maintenance-information)

Unexpected data was written from the jpoagtjobshow command.

(S)
Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)
Collect data about this internal error and then contact the system administrator. If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8404-E

The creation of information sent to the jpoagtjobshow command failed. (return-code) (line-number)

The information file could not be created for the jpoagtjobshow command.

(S)
Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8405-E

The reporting of information to the jpoagtjobshow command failed. (return-code)

Pipes could not be written into the jpoagtjobshow command.

(S)
Continues processing. The system cannot provide the information for the jpoagtjobshow command.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8406-W

The creation of the information to be sent to the jpoagtjobshow command is incomplete. (return-code) (line-number)

Job information could not be written when creating the information file for the jpoagtjobshow command.

(S)
Continues processing. The system cannot provide the complete information for the jpoagtjobshow command.

(O)
Check the following:
  • Check whether system resources are sufficient.
  • Check whether the privilege of the user is valid.
  • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
If you want to display the correct information using the jpoagtjobshow command, re-execute the command.

KAVT8408-E

There is no logical host name in the environment variable.(return-code)(line-number)

A logical host name is not set for the JP1_HOSTNAME environment variable.

(S)
Cancels command execution.

(O)
Set a logical host name for the JP1_HOSTNAME environment variable, and then re-execute the command.

KAVT8410-E

An attempt to obtain the environmental setting parameter information failed.(return-code)(line-number)

An attempt to obtain environment setting parameter information has failed.

(S)
Cancels command execution.

(O)
Check the following, and then re-execute the command:
  • Check whether the environment setting parameters for JP1/AJS3 and JP1/Base are specified correctly.
  • Check whether memory is sufficient.
    If memory is insufficient, see 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory has been allocated.

KAVT8411-W

An attempt to move then environmental setting parameter failed.(return-code)(line-number)

Migration processing for the environment setting parameters has failed.

(S)
Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)
Check whether the environment setting parameters for JP1/AJS3 and JP1/Base are specified correctly.
Specify the environment setting parameters correctly, and then re-execute the command.

KAVT8412-W

An attempt to create the key of an environmental setting parameter failed.(keyname=key-name)(return-code)(line-number)

An attempt to create a key for the environment setting parameters has failed.

(S)
Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)
Check whether there is an upper-level key for the key that could not be created.
If there is no upper-level key, create it and then re-execute the command.

KAVT8413-E

An attempt to obtain the file name failed.(return-code)(line-number)

An attempt to obtain the file name has failed.

(S)
Cancels command execution.

(O)
Check the following, and then re-execute the command:
  • Check whether the directory created by JP1/AJS3 during installation has been improperly deleted.
  • Check whether memory is sufficient.
    If memory is insufficient, see 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory has been allocated.

KAVT8414-E

An attempt to output the EV_Convert_Log.log files failed. (return-code)(line-number)

An attempt to output an error number to the EV_Convert_Log.log file has failed.

(S)
Cancels command execution.

(O)
Check the following:
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether memory is sufficient.
  • Check whether the directory created during installation of JP1/AJS2 has been deleted illegally.
  • Check whether the log directory in the JP1/AJS3 installation directory contains the EV_Convert_Log.log file.
    If the EV_Convert_Log.log exists, delete it, and then re-execute the command.
For other cases, correct the error and then re-execute the command.

KAVT8415-E

An attempt to move the file failed.(filename=file-name)(return-code)(line-number)

Migration processing for the internal file to be used for the event/action control has failed.

(S)
Continues processing. Note, however, that the system terminates migration processing abnormally.

(O)
Check the following:
  • For a physical host, check whether the disk that contains the JP1/AJS3 installation directory has sufficient free space. Also check whether the installation directory can be accessed.
  • For a logical host, check whether the shared disk has sufficient free space and can be accessed.
  • Check whether memory is sufficient.
  • Check whether the directory created during installation of JP1/AJS2 has been deleted illegally.
  • Check whether the file for which migration failed is in the migration source.
    If this file is in the migration source (JP1/AJS2 system file directory), delete the file and then re-execute the command.
  • Check whether an asterisk (*) is displayed for file-name in the message.
    If an asterisk (*) is displayed for file-name in the message, delete the EVaction_backup directory from the tmp directory in the JP1/AJS2 installation directory, and then re-execute the command.
For other cases, correct the error and then re-execute the command.

KAVT8416-W

The file to be moved is invalid.(filename=file-name)(return-code)(line-number)

The data format of the file to be moved is invalid.

(S)
Renames the file to a name suffixed with _bak, and continues migration processing.

(O)
After setup of the standard configuration has been completed, take the following actions:
  1. For all the scheduler services, execute the jpomanevreset command with the -all option specified.
  2. Cold start the JP1/AJS3 service.
For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVT8417-W

An attempt to back up an invalid file failed.(filename=file-name)(return-code)(line-number)

When the KAVT8416-W message was output, an attempt to rename the file with an invalid data format to a name suffixed with _bak failed.

(S)
Continues migration processing.

(O)
See the corrective actions given for the KAVT8416-W message.

[Contents][Back][Next]

[Trademarks]

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