SP-AMS and Cross-System Automation Commands and Responses

As a result of a match between a pattern in the SP-AMS database and a message sent by an MCP host system, SP-AMS may take an action to send a command back to the host system. In addition, a command event report sent to Operations Sentinel may cause a command to be sent to an MCP host system. This event report may originate

  1. From SP-AMS as a response to a message from a different host.

  2. From CP-AMS or SMART AMS on an OS 2200 system console connected to the same Operations Sentinel server.

  3. From a user-supplied application on a UNIX system connected to the same Operations Sentinel server.

  4. From a spo_event command on a Windows system connected to the same Operations Sentinel server.

Since these cases involve an event on one host system causing an automatic action on another host system, they are referred to as "cross-system automation."

When the host system receives the command, it is acted upon as if it had been entered from an operations terminal. If the command solicits information from the host system, the resulting information messages are sent back to Operations Sentinel for processing by SP-AMS, even if the command did not originate from SP-AMS.