In Single Point Operations level 9.2, information about MCP system components is provided by the Single Point Operations Interface for ClearPath MCP (hereafter referred to as the MCP agent) running on the monitored MCP system. The MCP agent generates console messages describing the state of the system. These messages are matched by an SP-AMS automation database, which generates AC event reports that populate any active Single Point Operations Status classifications.
Beginning with Operations Sentinel level 11.0, everything works the same, except the SP-AMS automation database must be upgraded to use the new class definitions (see “Step One: Use the New Class Definitions”) and event report syntax (see “Step Two: Use the New Object Identification Syntax”).
Step One: Use the New Class Definitions
The following table lists the old Single Point Operations level 9.2 component class names and the corresponding new Operations Sentinel class names.
Table 5. Old and New MCP Class Names
| Old Component Classes | New Classes |
| MCP_Appl | MCP Appl |
| MCP_Disk_Family | MCP Disk Family |
| MCP_Disk_Pack | MCP Disk Pack |
| MCP_Printer | MCP Printer |
| MCP_Host | MCP System |
| MCP_Tape | MCP Tape |
Note: Except for the use of spaces as separators, the names are identical.
In Single Point Operations level 9.2, each component class has a number of attributes associated with it. Beginning with Operations Sentinel level 11.0, each class has a number of properties associated with it. Most of the old attribute names have corresponding property names that are exactly the same. However, some property names are different from the old attribute names. The differences are the result of enforcing the use of spaces as separators, removing the special characters that are no longer permitted in property names, and improving readability.
The following table lists the property names that are different from the old attribute names. Some of these properties apply to a single class and some to the multiple classes. If a property name is not listed, it is exactly the same as the old attribute name.
Table 6. New MCP Property Names
| Old Attribute Names | New Property Names | Associated Class |
|---|---|---|
| Proc User | Process User | MCP System |
| Proc Initial Pbit | Process Initial Pbits | MCP System |
| Proc Other Pbit | Process Other Pbits | MCP System |
| Proc IO Finish | Process IO Finish | MCP System |
| Proc MCP | Process MCP | MCP System |
| Proc True Idle | Process True Idle | MCP System |
| Proc False Idle | Process False Idle | MCP System |
| Proc Search | Process Search | MCP System |
| Mem Avail | Memory Available | MCP System |
| Mem Olay | Memory Overlay | MCP System |
| Mem Save | Memory Save | MCP System |
| Mem Total | Memory Total | MCP System |
| ASDINUSE | ASD In Use | MCP System |
| Write-Enabled | Write Enabled | MCP Tape |
| Serial-Number | Serial Number | MCP Tape |
| Tape-Name | Tape Name | MCP Tape |
| Volume-Scratch | Volume Scratch | MCP Tape |
| Tape-Density | Tape Density | MCP Tape |
| % Available | Percent Available | MCP Disk Family |
| % Available | Percent Available | MCP Disk Family |
| % Available | Percent Available | MCP Disk Pack |
| Mix-Number | Mix Number | MCP Appl |
| App-Name | App Name | MCP Appl |
| Pack-Type | Pack Type | MCP Disk Pack |
| Family-Serial-Number | Family Serial Number | MCP Disk Pack |
| Family-Index | Family Index | MCP Disk Pack |
| Family-Name | Family Name | MCP Disk Pack |
Implementing Step One is an editing task: replace old component class and property names with new class and property names. Do this wherever AC and DE event reports are used, either in SP-AMS database, scripts, or programs implemented using the Event Server API.
Step Two: Use the New Object Identification Syntax
In Single Point Operations level 9.2, objects were identified in AC and DE event reports using the CLASS, INSTANCE, and sometimes HOST attributes. HOST is not used in SP-AMS database because it is automatically added by the Event Server. CLASS is one of the component classes mentioned above, for example, "MCP_Tape". INSTANCE is the name of the component itself. HOST is the name of the system that owns the component. For example, a component named "tape1" of component class "MCP_Tape" that is owned by system "sys1" would be identified using the old syntax in an AC event report as follows:
TYPE=AC | CLASS=MCP_Tape | INSTANCE=tape1 | HOST=sys1
Beginning with Operations Sentinel level 11.0, only CLASS and INSTANCE are used. The syntax of each is used to identify the complete ownership tree of the object. Thus, both CLASS and INSTANCE identify both the owner of the object as well as the object itself. Each subpart of the identification is separated with a space-period-space ( . ). For example, using the new syntax, the same "tape1" object is identified as follows:
TYPE=AC | CLASS=MCP System . MCP Tape | INSTANCE=sys1 . tape1
In SP-AMS database, the name of the system (for example, "sys1") is identified using the special SP-AMS syntax "\_HOSTID\" and the name of the component (for example, "tape1") is typically extracted from the console message along with property values.
Implementing Step Two is also an editing task. Edit CLASS to add "MCP System . " in front of the new class name you created in Step One. For INSTANCE, add "\_HOSTID\ . " in front of all INSTANCE values. Do not do this if the class is already "MCP System".
Single Point Operations level 9.2 provided a sample AMS database named “MCPMon” that used the old syntax. Beginning with level 11.0, Operations Sentinel updates this database to use the new syntax and renames it to “MCPMonitor”.