In Single Point Operations level 9.2, the UNIX Resident Monitor (URM) running on the monitored UNIX/Linux system, provides information about UNIX/Linux system components. The URM generated AC event reports that populated any active Single Point Operations Status classifications.
Beginning with Operations Sentinel level 11.0, URM has been replaced by the UNIX/Linux Resource Monitor (ULRM). Since ULRM does not generate AC events and does not run on all of the platforms supported by URM, the older URM has been upgraded to use the new class definitions and event report syntax. However, ULRM is deprecated. Support is minimal and URM will be dropped as a feature in the future release. There is also no support in the user interface for administration of URM. Manual administration is the only option available (see “Manual Administration of URM”).
Any user modifications to URM scripts need to 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 7. Old and New UNIX/Linux Class Names
| Old Component Classes | New Classes |
| CPU | UNIX/Linux CPU |
| FileSystem | UNIX/Linux File System |
| LongProcess | UNIX/Linux Long Process |
| Process | UNIX/Linux Process |
| User | UNIX/Linux User |
| Unix Host | UNIX/Linux Host |
Notes:
Except for the use of spaces as separators, the names are identical.
The UNIX/Linux Host class is not the same as the main UNIX/Linux System class. UNIX/Linux Host is derived from UNIX/Linux System. It contains additional properties, but otherwise behaves like its parent class.
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 to remove some special characters that are no longer permitted in property names.
The following table lists the property names that are different from the old attribute names. If a property name is not listed, it is exactly the same as the old attribute name.
Table 8. New UNIX/Linux Property Names
| Old Attribute Names | New Property Names | Associated Class |
| % User | Percent User | UNIX/Linux CPU |
| % System | Percent System | UNIX/Linux CPU |
| % Wait | Percent Wait | UNIX/Linux CPU |
| % Idle | Percent Idle | UNIX/Linux CPU |
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 in the preceding text, for example, "User". INSTANCE is the name of the component itself. HOST is the name of the system that owns the component. For example, a component named "user1" of component class "User" that is owned by system "sys1" would be identified using the old syntax in an AC event report as follows:
TYPE=AC | CLASS=User | INSTANCE=user1 | 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 "user1" object is identified as follows:
TYPE=AC | CLASS=UNIX/Linux System . UNIX/Linux User | INSTANCE=sys1 . user1
Note: UNIX/Linux Host may be used instead of UNIX/Linux System.
Manual Administration of URM
All URM scripts on all monitored systems must be updated with the URM scripts provided in the current release of Operations Sentinel. The scripts are located in the Operations Sentinel program installation folder under misc\agent\urm. The old manual installation scripts are located under misc\agent\bin. Ensure to back up the previous URM installation before updating the scripts.
Manual administration of URM is the only option available in Operations Sentinel level 11.0 and later. The Operations Sentinel Administration and Configuration Guide for the 9.x releases (7862 2321-008) documents how to manually install the URM.