OSI/MHS Management Programming Manual

Introduction to Management Programming for

OSI/MHS

OSI/MHS Management Programming Manual—424824-001

1-15

ROUTE Object

The ROUTE object type defines primary and alternate routing information to the

OSI/MHS subsystem. It is used to access the routing database for routing information

about users and to reconfigure users.

Examples of ROUTE object names include:

$ZMHS.#NEWYORK.PROUTE

$ZMHS.#TOKYO.VIAEAST

$ZMHS.#HN.VIASATELLITE

SUBSYS Object

The SUBSYS object type identifies an entire OSI/MHS subsystem. You use the

SUBSYS object to configure general aspects of the subsystem and to inquire about the

subsystem as a whole. Each X.400 MTA and its co-located message stores is a separate

OSI/MHS subsystem with its own subsystem manager process.

You can stop and start the SUBSYS object to reconfigure the subsystem; however,

commands addressed to the SUBSYS object do not support the SUB modifier.

An example of a SUBSYS object name is $ZMHS.#ZMHS.

OSI/MHS Object-Type Hierarchy

The object types defined by OSI/MHS are related to one another in a hierarchy. Some

commands can then be selectively applied to an object, its subordinates, or both.

Figure 1-7 shows the hierarchy of the OSI/MHS object types.

The SUBSYS object (which corresponds to the entire OSI/MHS subsystem) is at the top

of the OSI/MHS hierarchy. Objects of type CLASS, APPL, DLIST, CUG, MTA,

GATEWAY, and ENTRY are subordinate to the SUBSYS object.

Objects of type GROUP are subordinate to a corresponding object of type CLASS.

Subordinate to the GROUP object is the PROCESS object. The PROCESS object has

no subordinate objects.

The APPL object has no subordinate objects.

Subordinate to the DLIST object is the DLISTMEMBER object. The DLISTMEMBER

object has no subordinate objects.

Subordinate to the CUG object is the CUGMEMBER object. The CUGMEMBER

object has no subordinate objects.

Subordinate to the MTA object is the ROUTE object. The ROUTE object has no

subordinate objects.

The GATEWAY and ENTRY objects have no subordinate objects.

The MON (MHS manager) object has no subordinate objects.