This section describes messages internally generated by AMS and Operations Sentinel, and how to match them.
AMS generates the following messages:
[SP-AMS]
Automation initialization, generated when Operations Sentinel begins monitoring a system. See 7.2.
[SP-AMS]
Automation termination, generated when Operations Sentinel stops monitoring a system. See 7.3.
Database activation, generated when an autoaction database is activated. See 7.4.
Database deactivation, generated when an autoaction database is deactivated. See 7.5.
The spo_ping interface in Operations Sentinel generates messages to report the status of each ping operation for each system configured for spo_ping monitoring. You can include patterns in an SP-AMS database to match these messages. See 7.6.
The spo_ssh, spo_ssh1, and spo_ssh2 interfaces, also in Operations Sentinel, generate messages to handle the login process to the managed system, similar to Telneting to a system. You can include patterns in an SP-AMS database to match and respond to these messages. See 7.7.
The OS 2200 console generates messages that deal with the state of the OS 2200 Console window hold pane. See 7.7. It generates a message when a read-and-reply message is removed from the read-and-reply pane or when a held message is removed from the hold pane.