If you are running an Operations Sentinel configuration with both MCP and UNIX host systems, you must combine an SP-AMS database with patterns for MCP (your choice of MCPMon or a database you derived from MCPMon) and an SP-AMS database with patterns for UNIX (for example, spastart) into one active database.

To combine two source databases (file names ending with “.bld”) into one file, specify both of their names when calling BADB to generate the SP-AMS database. Alternatively, combine them into one file with a text editor and then process the combined file with BADB to generate the SP-AMS database.

Be careful when updating message patterns and the resulting actions in a combined database. For example, each separate MCP and UNIX database contains a test mode pattern that matches the message indicating that automation has stopped. In this case, it does not matter which pattern in the combined database matches the message. However, if test mode is turned off for the pattern in one of the databases, you must assign a higher priority to the pattern in that database so that it will be the pattern that matches the message.