OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-13
Restarting the Subsystem
5. STATUS CLASS with the DETAIL option shows you the state of each group.
6. STOP MON stops the MHS manager.
7. EXIT takes you out of SCF.
Restarting the Subsystem
To restart the OSI/MHS subsystem, you first run the MHS manager and then start the
objects. You do not need to define the objects because they already exist. The
following command file is the same as the command file for starting the subsystem,
except that the step of defining the objects is eliminated.
There is no need to start the APPL objects unless they have been stopped.
Updating the OSI/MHS Software
To update the OSI/MHS subsystem with new software, you perform the following steps:
1. Perform an orderly shutdown.
2. Install the new software, using the installation procedure.
3. Run the MHS manager process.
4. (Redefine if necessary and) start the subsystem objects.
The OSI/MHS softdocs (which are the documents you receive with each update of the
software) contain all the relevant information for that update. They have a full
description of what has changed since the previous update. The install subvolume
contains the updated version of the software.
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
== start the OSI/MHS objects
START SUBSYS $ZC1.#ZC1
START CLASS $ZC1.*
START GROUP $ZC1.*
EXIT