KAVT0296-W

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 name cannot be resolved, specify 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.

• 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 the IP addresses are different, specify 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.

• 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