OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-59
null Objects
created and the MON object defined. The null object is used to list the objects in the
subsystem or to obtain the subsystem version ID.
null Object States
The null object does not have a summary state, even though all the objects within the
subsystem are subordinate to it. The SCF STATUS command, which returns state
information, does not apply to the null object.
Naming null Objects
For any OSI/MHS subsystem, the null object name is the same as the MON object
name. This name has the form:
system
is the name of the system (node) that runs the MHS manager process for this
OSI/MHS subsystem.
manager-process
is the name you have given the MON object (the MHS manager process). This
name must be a letter followed by zero through three alphanumeric characters.
The manager process name is shared by all objects in the subsystem; however, for
all objects except MON and null, it is qualified by one or more additional (lower
level) names.
For example, you could install the MHS manager process and name it
\SYSTEM1.$ZMHS. Then you would use the name $ZMHS in commands directed to
the null object from inside SYSTEM1.
SCF Commands for the null Object
You can direct either of the following SCF commands to the OSI/MHS null object
specified or assumed in the command. These commands are nonsensitive.
[\system.]$manager-process
NAMES Lists the names of all objects that have been defined to the MHS
manager process specified (or assumed) in the command, and
therefore, the names of all objects defined in that OSI/MHS subsystem.
VERSION Displays the version identifier of the MHS manager process.