OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-6
Defining All Objects to the MHS Manager Process
Examples of Starting the MHS Manager Process
The following examples demonstrate two methods of setting MHS manager startup
parameters: one as PARAM command parameters, the other as RUN command line
options. You can start the MHS manager process by using PARAM command
parameters, as follows:
CLEAR ALL
PARAM CONFIG-DB-SVOL $myvol.zmhsdb
PARAM COLLECTOR $0
PARAM COLLECTOR-1 $acol
PARAM BACKUPCPU 14
PARAM SWAPVOL $swap
RUN $myvol.osimhs.mhsmgr/name $zmhs, cpu 15, &
out $s.#zmhs.log, swap $myvol, NOWAIT/
DELAY 30 seconds
Or you can start the MHS manager process by specifying the parameters as RUN
command line options:
RUN $myvol.osimhs.mhsmgr/name $zmhs, cpu 15, &
out $s.#zmhs.log, swap $myvol, NOWAIT/ COLLECTOR&
$0, CONFIG-DB-SVOL $myvol.zmhsdb, SWAPVOL $swap,&
BACKUPCPU 14, COLLECTOR-1 $acol
The values you specify as RUN command line options override values you specify as
PARAM command parameters. PARAM command parameters, in turn, override built-in
defaults.
In both situations, if you specify a parameter more than once, the last value applies. If
you specify an unrecognized or otherwise erroneous parameter in the RUN command
line, an error message is issued, and the MHS manager process terminates. If you
specify an unrecognized or otherwise erroneous parameter in the PARAM command, it
is ignored without comment.
Once the MHS manager process is started, you can check the values of the startup
parameters (whether specified through PARAM parameters, on the command line, or
through default values) by using the SCF command INFO MON.
Defining All Objects to the MHS Manager Process
The installation procedure sets up the databases and the PDU stores you need to run
an OSI/MHS subsystem. However, there are particular objects in an OSI/MHS
subsystem that you need to define to the MHS manager process. You can give the
required commands using SCF or a management application. See the OSI/MHS
Management Programming Manual for more information about the programmatic
management interface.
The objects to be defined are APPL, CLASS, (GI, LO, MR, MS, and RS), CUG,
CUGMEMBER, DLIST, DLISTMEMBER, GATEWAY, GROUP, MTA, ROUTE, and
SUBSYS. For more information about defining these objects, see Section 2,