OSI/MHS SCF Reference Manual

Introduction
OSI /MHS SCF Reference Manual—424828-001
1-4
OSI/MHS Object Hierarchy
pname
is an alphanumeric string with a maximum length of four characters. It specifies a
valid process name
route
is an alphanumeric string with a maximum length of 16 characters. It is used to
define the location of routing information in the OSI/MHS routing database.
subsys
is an alphanumeric string with a maximum length of four characters, the first of
which must be an alphabetic character. It specifies the name of the subsystem.
OSI/MHS Object Hierarchy
Figure 1-2 shows the hierarchical order of the object types that OSI/MHS supports.
To an MHS manager process, the SUBSYS object type (which corresponds to the entire
OSI/MHS subsystem) is at the highest point of the hierarchy. (The null object type is
not an actual object type, but is used in commands that allow you to obtain information
about all of the object types in a subsystem.) Subordinate to the SUBSYS object type are
the CLASS, GATEWAY, APPL, DLIST, CUG, MTA, and ENTRY object types.
The MON (MHS manager) object type has no subordinate object types and is separate
from the hierarchy structure of the other object types.
Subordinate to the CLASS object type is the GROUP object type. Subordinate to the
GROUP object type is the PROCESS object type. The PROCESS object type has no
subordinate object types.
The GATEWAY object type has no subordinate object types.
The APPL object type has no subordinate object types.
Subordinate to the DLIST object type is the DLISTMEMBER object type. The
DLISTMEMBER object type has no subordinate object types.
Subordinate to the CUG object type is the CUGMEMBER object type. The
CUGMEMBER object type has no subordinate object types.
Subordinate to the MTA object type is the ROUTE object type. The ROUTE object type
has no subordinate object types.
The ENTRY object type has no subordinate object types.