OEM User's Guide

OEM External Specification
OEM User’s Guide—520330-001
A-73
Rule #1 - Hierarchical Name Space
Rule #1 - Hierarchical Name Space
Construct object names according to the following hierarchical name space rule:
name ::= class object [ class object [ class object ] ... ]
name ::= hierarchical name of the object or class instance.
class ::= name of the class instance.
object ::= name of the object instance.
Class and object instances indicated by class object pairing should adhere to what
is generally accepted as the conventional hierarchical model for the object. For example,
on NonStop™ Kernel systems, node names are listed first. When working with
hierarchical name space organizations that refer to NonStop™ Kernel nodes, the node
name should appear first in the name.
Rule #2 - Path Delimiter
Class and object names must be separated by the path separator delimiter. This delimiter
is defined as the backslash character. This character has been chosen to minimize
conflicts between NonStop™ Kernel names, DOS 8.3 names, and Windows long file
names.
Rule #3 - Null Classes and Objects
The initial class name can be null when the object name is a Compaq node name.
Because a Compaq node name delimiter is also a backslash, object/class names added
under a Compaq node can logically start with the backslash character delimiter.
Additionally, the trailing object name can be null, thus allowing specification of
classes hierarchies without underlying object instances.
Rule #4 - Case Sensitivity
Names are not case sensitive. For example, \Chicago\Disk\$System is equivalent to
\chicago\disk\$system. Because the OEM maintains the case of names as they are
initially defined and displays these names as such, clients should adopt case consistency
conventions. Compaq recommends adopting the convention used by Windows Explorer,
where the first letter of each name is in uppercase and the remainder in lowercase.
Rule #5 - Class Names
Class names that refer to classes that are shared by multiple clients must adhere to
consistent use of well-known names. For example, CPU and disk classes must be
referred to as "Cpu" and "Disk" by all clients that reference them:
\Chicago\Cpu\0, \Chicago\Cpu\1
\Chicago\Disk\$System, \Chicago\Disk\$Data
\Chicago\Process\$Cmon
\London\Transaction\London.2.8232