OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-67
ROUTE Objects
The first several examples illustrate the nonsensitive commands you can use to obtain
information about a PROCESS object:
NAMES PROCESS $ZMHS.#MSP1
STATS PROCESS $ZMHS.#MSP3
STATUS PROCESS $ZMHS.#MSP2
STATUS PROCESS $ZMHS.#MSP2, DETAIL
The next example shows a sensitive command you can use for information:
STATS PROCESS $ZMHS.#MSP3, RESET
This STATS command differs from the earlier, nonsensitive example because it resets
the statistics counters. Even so, it is comparatively safe to use because it does not
affect other objects.
The next command generates and saves all the trace records for process
$MHS1.#MSP3. When the record file is full, the next record wraps around to the
beginning of the file and is written over the first record.
TRACE PROCESS $MHS1.#MSP3, SELECT ALL, WRAP, TO $DATA.MHS.TRACE
ROUTE Objects
A ROUTE object defines the route-selection criteria that describe the path to a user or
set of users through an adjacent MTA. Route-selection criteria are determined by the
partial or complete originator/recipient (O/R) name.
You can configure several routes through a single MTA. Alternate routes to the same
recipient or set of recipients must have exactly the same O/R name attributes. The
priority attribute of the ROUTE object determines the order in which OSI/MHS will try
the routes. Therefore, an alternate route to an O/R name has the same selection
criteria as the primary route, but it has a different priority.
The ROUTE object that defines a route or set of routes through an adjacent MTA is
subordinate to the MTA object that represents the MTA. All the routes defined for an
OSI/MHS subsystem are recorded in its routing database.
Using the ROUTE object type, you determine the route-selection criteria used for
transmitting messages to a particular user or set of users. In general, alternate routes
go through different MTAs, to provide for cases in which an MTA is unavailable or
abnormally busy. It is also possible to define multiple MTA objects pointing to the same
real MTA; in this case, alternate routes are used primarily to increase throughput.
ROUTE Object States
A ROUTE object has a summary state of DEFINED only. Therefore, you can alter a
ROUTE object immediately after you add it.
Caution. If you make any major changes to the routing database while messages are in
transit, those changes will severely affect message delivery. You should establish the routes
prior to subsystem startup.