Implementing the new syntax and the new class definitions involves completing the following steps:

Step One: Use the New Class Definitions

Beginning with level 11.0, Operations Sentinel supplies a default starter configuration. This starter configuration contains class definitions for various components of OS 2200, MCP, and UNIX/Linux systems. Subsections “OS 2200 Changes” through “UNIX/Linux Changes” describe in more detail the differences between these classes and those supplied in sample classifications in Single Point Operations level 9.2.

In general, you must update all references to the old component class definitions to reflect the new class definitions. This includes references in automation databases (CP-AMS and SP-AMS), scripts that reference event reports, and user programs implemented using the Event Server API. Generally, you need to modify references to attribute change (AC) and delete object (DE) event reports only.

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 the HOST attributes. HOST is not used in CP-AMS databases because it is automatically added by the Event Server. In Single Point Operations level 9.2, CLASS is one of the component classes defined in a classification. 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 like this:

TYPE=AC | CLASS=Tape | INSTANCE=tape1 | HOST=sys1

Beginning with Operations Sentinel level 11.0, only the CLASS and INSTANCE attributes 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 and the "OS 2200 Tape" class, the same "tape1" object is identified like this:

TYPE=AC | CLASS=OS 2200 System . OS 2200 Tape | INSTANCE=sys1 . tape1

In general, you must edit all values of CLASS to add a prefix containing the name of the host class and the separator. For example, after converting the class names in Step One, you have a class named "OS 2200 Tape". In Step Two, change the class from "OS 2200 Tape" to "OS 2200 System . OS 2200 Tape".

Similarly, you must edit all values of INSTANCE to add a prefix containing the name of the system object that owns the object. For example, if you have an object named "tape1" owned by a host system named "sys1", change the value of INSTANCE from "tape1" to "sys1 . tape1". In automation databases, you typically use the special syntax "$HOST$" or "\_HOST\" instead of a specific host name.

Once you switch to the new syntax, remove the HOST attribute. In general, the HOST attribute is ignored when you use the new syntax.