When Operations Sentinel begins monitoring an MCP host system, SP-AMS internally generates an automation initialization message before SP-AMS processes any data from the host system. SP-AMS generates this message each time a connection to an MCP host system is initially established and an SP-AMS database is active.

The initialization message is processed by SP-AMS as if it had been sent from the host system. SP-AMS handles the initialization message the same way it handles other system messages: it compares the message to the patterns defined in the active SP-AMS database. Therefore, it can cause a pattern to match the message and perform initialization actions for each host system that is to be monitored.

In response to matching this internally generated message, SP-AMS should send a message containing a valid usercode and password to the connected MCP host system. This must occur before the interface software begins sending data to the Operations Sentinel server. You specify the usercode in the SP-AMS database. It should have privileged status and system user status. The configuration file includes a parameter that allows you to specify whether a nonprivileged usercode is permitted. See Section 3.

The Unisys sample database includes a message pattern that matches the internally generated message. This pattern produces a usercode/password message response of SPO/SPO. When a usercode/password failure occurs, an error message is generated. See Section 6.

If several MCP host systems are being automated, the usercode and password can be different for each system. In this case, create a unique pattern in the SP-AMS database for each system, or use SP-AMS conditional logic within a single pattern to supply the appropriate usercode and password for each system. See sample database MCPMon.bld for an example of this technique.

Following is the text of the internally generated initialization message:

Single Point AMS automation started using database db-name for system host-id.

where:

db-name

identifies the database being used.

host-id

identifies the system being monitored.

See the SP-AMS Administration Guide for additional information.