In Single Point Operations level 9.2, information about OS 2200 system components is provided by the OS 2200 Data Collector running on the monitored OS 2200 system as part of the OMKEY background run. The OS 2200 Data Collector is triggered by the *S*P*D*C keyin on the console and generates console messages describing the state of the system. These messages are matched by a CP-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 you must upgrade the CP-AMS automation database to use the new class definitions (see “Step One: Use the New OS 2200 Class Definitions”) and event report syntax (see “Step Two: Use the New Object Identification Syntax”).

Step One: Use the New OS 2200 Class Definitions

Table 1–2 lists the old Single Point Operations level 9.2 component class names and the corresponding new Operations Sentinel class names.

In Single Point Operations level 9.2, each component class had 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 and removing the special characters that are no longer permitted in property names.

Table 1–3 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.

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 CP-AMS databases, 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 CP-AMS databases because it is automatically added by the Event Server. CLASS is one of the component classes mentioned above, for example, "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 "Tape" that is owned by system "sys1" would be identified using the old syntax in an AC event report as follows:

TYPE=AC | CLASS=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=OS 2200 System . OS 2200 Tape 
| INSTANCE=sys1 . tape1

In CP-AMS databases, the name of the system (for example, "sys1") is identified using the special CP-AMS syntax "$HOST$" and the name of the component (for example, "tape1") is typically extracted from the console message, along with property values.

Implementing Step Two is another editing task. Edit CLASS to add "OS 2200 System . " in front of the new class name you created in Step One. For INSTANCE, simply add "$HOST$ . " in front of all INSTANCE values. Do not do this if the class is already "OS 2200 System."

Single Point Operations level 9.2 provided some sample CP-AMS databases that used the old syntax. Beginning with level 11.0, Operations Sentinel renames some of the same databases and updates them to use the new syntax. Table 1–4 lists the old and newer versions of the database.