OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-8
Combining the Steps
Combining the Steps
You can combine the previous steps in one command file. The following example
shows the orderly startup of an OSI/MHS subsystem using a command file.
This command file shows the following:
•
Starting an alternate collector. (The primary collector, $0, runs automatically as
part of the operating system.)
•
Starting the MHS manager using the PARAM command options and the RUN
command.
•
Defining the MHS objects to the subsystem using a command file.
•
Starting the MHS objects.
Defining and Starting the Entry and Wait
Managers
The entry and wait managers are server processes that are used in conjunction with
gateway associations. If your OSI/MHS subsystem includes gateway associations,
you must define and start the entry and wait managers before starting any GI groups.
For each gateway association, you must have:
•
One to five entry managers
•
One wait manager
CONFIRM ON
ALLOW ALL
== start an alternate collector
EMSACOLL/name $ALT,NOWAIT,CPU 1/BACKUP 0
== start the MHSMGR process
CLEAR ALL
PARAM CONFIG-DB-SVOL $DATA4.T3CDB
PARAM COLLECTOR $0
PARAM COLLECTOR-1 $AC01
PARAM BACKUPCPU 3
PARAM SWAPVOL $DATA1
RUN $MYVOL.OSIMHS.MHSMGR/NAME $ZC1, CPU 1, OUT $S.#ZC1, SWAP $DATA1,
NOWAIT/
DELAY 30
== define the objects to the subsystem
OBEY excfmta1
NAMES $MHS1
== start the MHS objects
START SUBSYS $ZC1.#ZC1
START APPL $ZC1.*
START CLASS $ZC1.*
START GROUP $ZC1.*
EXIT