Interacting with External Event Systems › Using the CA NSM Interface › Troubleshooting the Event Traffic Controller › Successful Return Code on Non-existent Host Name

Successful Return Code on Non-existent Host Name

Symptom:

Why would a successful return code result from UNIWTO when a non-existent host name is specified?

Solution:

If Event Manager is running on the same local host as CA Automation Point, Event Manager has store and forward enabled, and CA Automation Point sends a UNIWTO message to a remote node name that does not exist, the UNIWTO returns successfully under the assumption that the host is down. Event Manager expects to store the message and forward it when the remote host comes back up.