OSI/MHS SCF Reference Manual

Introduction

OSI /MHS SCF Reference Manual—424828-001

1-8

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 or sets of remote X.400 users using these MTA objects.

You can configure up to 800 adjacent MTA objects.

Examples of MTA object names include:

$ZMHS.#NEWYORK

$ZMHS.#TOKYO

$ZMHS.#HK

PROCESS Object

The PROCESS object type defines a process to the OSI/MHS subsystem. This object is

used to trace and monitor OSI/MHS processes. You can direct requests to a specific

process, to groups of processes, to 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 object names include:

$ZMHS.#MS3

$ZMHS.#\HOE.MR3

ROUTE Object

The ROUTE object type defines 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 the OSI/MHS subsystem as a whole. You use the

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

subsystem as a whole.

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. For

information about the SUB modifier, see the Subsystem Control Facility (SCF)

Reference Manual.

An example of a SUBSYS object name is:

$ZMHS.#SUBSYSA