OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-69
SUBSYS (Subsystem) Objects
Examples of Commands for ROUTE Objects
The following are examples of commands for ROUTE objects.
The following examples show nonsensitive commands you can use to obtain
information about OSI/MHS ROUTE objects:
NAMES ROUTE $ZMHS.
∗
NAMES ROUTE $ZMHS.#BOSTON1.ROUTE
∗
NAMES ROUTE $ZMHS.#NYC05
INFO ROUTE $ZMHS.#OSIMHS003.ROUTE1
INFO ROUTE $ZMHS.#OSIMHS003.ROUTE1, DETAIL
INFO ROUTE $ZMHS.#
∗
.ROUTEPRIMARY
∗
, DETAIL
As the following command illustrates, the only attribute you must specify when adding
a ROUTE object is its priority:
ADD ROUTE $ZMHS.#BOSTON1.ROUTE7, PRI 7
This example shows a catch-all route, by which a message that fails to match O/R
names with the selection criteria defined in any other ROUTE object goes to the MTA
named in this route definition.
SUBSYS (Subsystem) Objects
One SUBSYS object must be defined for each OSI/MHS subsystem. Using the
SUBSYS object type, you can configure system-wide attributes, such as:
•
File names of the OSI/MHS databases
•
Process name of the OSI manager process
•
Process name of a password server process, if applicable
•
Management domain attributes (country name, ADMD, PRMD)
•
Accounting events enabled
SUBSYS Object Summary States
An OSI/MHS subsystem goes through a sequence of states that depend on and
summarize the states of its subordinate objects. You can use the SCF STATUS
command to inquire about the summary state of the subsystem. Other SCF
commands allow you to change its summary state.