OSI/MHS Management Programming Manual

Introduction to Management Programming for
OSI/MHS
OSI/MHS Management Programming Manual—424824-001
1-14
MON Object
The group name can have an optional node name, but it must be the same as the name of
the node on which the MHS manager resides. If the node name is omitted, the local
system is assumed.
Examples of group names include:
$ZMHS.#MS.GRP1
$ZMHS.#MR.\COMM.GRP1.
MON Object
The MON object type enables you to address commands to the MHS manager. The
MON object name identifies the MHS manager. It has the same name as the null object.
An example of a MON object name is $ZMHS.
MTA Object
The MTA object type defines adjacent MTAs and their attributes to the OSI/MHS
subsystem. This object is used to control and inquire about adjacent MTAs. Routes are
defined for remote X.400 users using these MTA objects.
You can configure up to 800 adjacent MTA objects per subsystem.
Examples of MTA object names include:
$ZMHS.#NEWYORK
$ZMHS.#TOKYO
$ZMHS.#HK
NULL Object
The NULL object type is used as the object type in commands that do not require a
particular object type. The NULL object type has no hierarchical relationship to any of
the other object types that OSI/MHS supports.
The object name for the NULL object type identifies the MHS manager. An example is
VERSION $ZMHS, where $ZMHS is the manager process.
PROCESS Object
The PROCESS object type defines a process to the OSI/MHS subsystem. You use this
object to trace and monitor OSI/MHS processes. You can send inquiry and TRACE
commands to a specific process, groups of processes, classes of processes, or to all
OSI/MHS processes.
If the PROCESS object name is a network name, the system name is the name assigned
to the group in which the process resides.
Examples of PROCESS names include:
$ZMHS.#MS3
$ZMHS.#\COMM.MR3