Reduce ESP507E ESP Workload Automation JESMSGLG output.

Products

• ESP Workload Automation

Issue/Introduction

Customers find extensive ESP507E messages in ESP JESMSGLG from agents that are attempting to connect to ESP. However there is no Agent defined in the ESP AgentDef member. These errors, if left, do have the potential to cause performance problem.

Environment

Component: Workload Automation ESP
Release: All Releases

Cause

ESP507E messages in ESP JESMSGLG are from undefined agents.

Resolution

The best way is to locate the agent server based on the IP address on this message, and remove the related ESP manager information in the agentparm.txt and restart the agent.

There is a way to resolve it without updating the agentparm.txt on agent side.

The following can be used to re-direct the messages from the undefined agent. This can be used as a workaround when it's not possible to update the agentparm.txt for those agents:

1. Find out the agent name and it's IP address on ESP507E message. 
2. Find out the agent input port and encryption key. Note: the two values are NOT on ESP507E message. Some companies have standard
    values for them, if not, this method cannot be used.
3. Add the agent thru OPER AGENT agent_name DEFINE command; 
4. Issue OPER MGRADDR NAME(agent_name) PORT(wrong_port) to change the manager port in agentparm to a non-existing port,
    so the agent can't connect to the ESP. 
5. Issue OPER AGENT agent_name DELETE to remove the agent.