ESP Workload Automation

  • 1.  Tuesday Tip: (CA ESP) Eliminate ESP507E messages?

    Broadcom Employee
    Posted 01-13-2015 03:42 PM

    CA Tuesday Tip by Lucy Zhang, Principal Support Engineer for 13/01/2015

     

    When the agent is started without being defined in AGENTDEF table on ESP STC, then ESP507E message will show in JESMSGLG.

     

    PTF RO76447 adds IP address of sender to the error message ESP507E, so that the agent server can be located easily:

    ESP507E

    Missing or invalid agent name in prefix: ******, received

    from yyy.yyy.yyy:zzzzz

    Reason:

    The agent message receiver received a message with a type 2 prefix

    from the IP address yyy.yyy.yyy and the TCP port number zzzzz,

    but the prefix did not contain a valid agent name.

     

    You will either stop the agent, or add the agent to AGENTDEF. As temporary workaround, you may use a wrong IP/DNS/PORT for the related manager ID in agentparm file and restart the agent, so that the agent won't connect to the ESP STC.



  • 2.  Re: Tuesday Tip: (CA ESP) Eliminate ESP507E messages?

    Posted 09-03-2015 09:18 AM

    Lucy,

    have not applied this fix yet, but is this message going to be all in 1 line? A MLWTO?  or 2 distinct lines prefixed with ESP507E?   I cant tell from the PTF doc.

    Just want to have my automation set up to handle the new scenario when we implement the fix.

    Thanks

    Sal



  • 3.  Re: Tuesday Tip: (CA ESP) Eliminate ESP507E messages?

    Broadcom Employee
    Posted 09-04-2015 12:18 PM

    Hi Sal,

     

    I just tested here, it shows in same line:

    X114M_507E Missing or invalid agent name in prefix: LUCYM, received from xx.***.x.***:57945

     

    Hope this helps,

     

    Lucy



  • 4.  Re: Tuesday Tip: (CA ESP) Eliminate ESP507E messages?

    Posted 09-08-2015 10:16 AM

    Thanks Lucy!

     

    Just what I needed to know

     

    Sal