KAVT0980-W

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 name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved.

• Check whether the manager host name^# can be resolved on the agent host.

  If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so 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 the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

• 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 the IP addresses are different, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the correct IP address can be obtained by resolving the name.

• 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(4) Notes on manager/agent system configurations in the JP1/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.