OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-20
OSI/MHS Objects
more groups of the same kind. Each group contains one or more processes. For
example, the MS class includes all the MS groups in the OSI/MHS subsystem, and
each MS group contains one MS process and one PDU store.
An APPL object defines information about users of OSI/MHS message stores—that is,
about user agents—or users of gateways. APPL objects are subordinate to the
SUBSYS object. APPL (user application) objects, which represent message-store
users, are related to MS GROUP objects, which define the message stores; APPL
(gateway) objects, which represent gateway users, are related to GATEWAY objects,
which define the gateways.
A DLIST object defines a local distribution list within the OSI/MHS subsystem. DLIST
objects are subordinate to the SUBSYS object. Each DLIST has zero or more
DLISTMEMBER objects subordinate to it.
A DLISTMEMBER object defines a member of a local distribution list. DLISTMEMBER
objects are subordinate to the DLIST object.
A CUG object defines a closed user group, a set of users who may exchange
messages only with one another. CUG objects are subordinate to the SUBSYS object.
Each CUG object has zero or more CUGMEMBER objects subordinate to it.
A CUGMEMBER object defines a member of a closed user group. CUGMEMBER
objects are subordinate to the CUG object.
An MTA object represents an adjacent MTA. MTA objects inherit attributes from the
SUBSYS object, and contain zero or more ROUTE objects.
A ROUTE object defines the path to use for routing messages to a specific recipient or
set of recipients. ROUTE objects are subordinate to MTA objects (representing
adjacent MTAs).
A GATEWAY object represents a Transfer X400 gateway or a gateway based on the
Gateway Programmatic Interface (GPI). GATEWAY objects inherit attributes from the
SUBSYS object, but are independent of all other object types. GATEWAY objects are
related to APPL (gateway) objects.
An ENTRY object identifies a message queue in the OSI/MHS subsystem. ENTRY
objects inherit attributes from the SUBSYS object, but are independent of all other
object types.
Naming OSI/MHS Objects
In every subsystem that uses SCF, objects are named according to a DSM convention
to identify them in SCF commands. For instance, every fully qualified object name
starts with the name of a system (node). For OSI/MHS, this is the system where the
MHS manager process resides. This system name is optional; omit it only if you are
sure it will default to the name of the system that has your MHS manager process.