OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-71
SUBSYS (Subsystem) Objects
manager-process
is the name you have given the MHS manager process (the MON object). This
name must be a letter followed by zero through three alphanumeric characters.
subsystem
is the name you have chosen to distinguish the SUBSYS object from all the other
objects in this OSI/MHS subsystem. This name must be a letter followed by 0
through 15 alphanumeric characters.
For example, if your MHS manager process is called $ZMHS, you could choose
$ZMHS.#SUBS1 as the name you use in SCF commands to control the SUBSYS
object. You specify the subsystem name in the ADD command for the SUBSYS
object.
SCF Commands for the SUBSYS Object
You can direct any of the following SCF commands to the OSI/MHS SUBSYS object
specified or assumed in the command. (Note that the SUB modifier is not supported in
any of these commands for the SUBSYS object.)
ABORT Changes the summary state of the OSI/MHS subsystem from STARTED
to STOPPED.
Before you can abort the subsystem, you must stop all of its subordinate
CLASS and GROUP objects.
For the SUBSYS object, the ABORT and the STOP commands have the
same effect.
ADD Creates and names an OSI/MHS subsystem (SUBSYS object) with the
name and attributes specified in the command, then adds the name and
attributes to the OSI/MHS configuration database.
The newly added SUBSYS object must still be started, then subordinate
objects added and started.
A required attribute of this object is OSI-MGR. Use it to specify the
process name for the OSI manager of the OSI/AS subsystem that will
transfer messages for your OSI/MHS subsystem. The OSI manager
must reside on the same system (node) as the MHS manager of the
OSI/MHS.
Other required attributes are MTA-ASSOC-FNAME, USER-FNAME, and
ROUTING-FNAME. They name the association, user, and routing
databases, which make up the OSI/MHS registration database.