Requirement

SP-AMS can provide automation of any data stream whose cursor positioning controls include only carriage return and line feed characters. Output from full-screen applications cannot be represented in an SP-AMS database.

Environment

SP-AMS runs as a service on the Operations Sentinel server, and continually provides automation for all MCP and UNIX systems managed by that server. A single, active SP‑AMS database specifies the same patterns for all MCP and UNIX systems. Automation is not specific to any instance of Operations Sentinel Console.

Control of Automation

SP-AMS starts automating actions in response to system messages for a connected MCP or UNIX system when Operations Sentinel begins managing the system. An operator using Operations Sentinel Console can control the automation mode of connected hosts and activate and deactivate SP-AMS databases

Automation starts when Operations Sentinel Console is monitoring the system. Automation stops when Operations Sentinel stops monitoring the system, for example: you turn monitoring off for the system.

Automation of UNIX hosts uses the Operations Sentinel console session or the spo_ping interface. Automation of MCP hosts uses the Operations Sentinel Interface for ClearPath MCP.

Automation Modes

Using Operations Sentinel Console you can select automation for each MCP and UNIX managed host. The automation mode controls the automation information that is written to the log SP‑AMS, and determines whether the actions specified by a matched pattern are actually executed. You can use the automation mode to debug the automation provided for a particular system. By recording automation actions in the log SP-AMS, you can identify unexpected results or errors before actually executing the actions.

Activating or Deactivating an SP-AMS Database

Activating or deactivating an SP-AMS database controls automation. Activation and deactivation activities can be automated or an operator can manually control the actions through the Automation Control table.