If no messages are on the ServiceNow instance - ironstream_for_servicenow_event_mgmt - 7.4

Symptom

No z/OS messages are arriving on the ServiceNow instance.

Solution

1. Verify that the appropriate Ironstream server programs are running on the Proxy Server by opening the Configuration browser page (by default located at http://MIDservername:9853 ). Check the status of the MCS process and verify that the Message Connection and Command Connection to the mainframe are in a “Connected” state.
2. Verify that the connection between the ServiceNow instance and the Service Now MID server is up and running by checking the status of the "ServiceNow MID Server" service from the Windows Services application.
3. Verify that the SN_SECRET value from the ServiceNow instance is correctly copied and labeled in the \conf\ev390info file.
4. Verify that the VP390 job is running on the mainframe agent. Use the command MODIFY VP390,SHOW TASK to verify that
   • The MVS subtask is defined and active, which collects the console messages.
   • The TCP subtask is active and has an established session with the MID server on the ports listed.