Open System Services Management and Operations Guide (G06.29+, H06.07+)

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-005
2-9
Starting the OSS Monitor
Starting the OSS Monitor as a Persistent Process
1. At a TACL prompt, enter:
SCF
ASSUME PROCESS $ZZKRN
2. Start the $ZSMP process as a generic process so that the OSS Monitor can
communicate with it without a delay during restart.
a. At an SCF prompt, enter the following to add $ZSMP to the NonStop Kernel
subsystem configuration as a generic process:
ADD PROCESS $ZZKRN.#ZSMP, &
PROGRAM $SYSTEM.SYSTEM.OSMP, &
NAME $ZSMP, &
PRIMARYCPU 0, &
BACKUPCPU 1 , &
AUTORESTART 0, &
STARTMODE KERNEL, &
HOMETERM $ZHOME, &
DEFAULTVOL $SYSTEM.SYSTEM, &
STARTUPMSG "<BCKP-CPU>"
where STARTUPMSG contains a literal that causes the use of a backup copy
regardless of which specified processor comes up first. The AUTORESTART
value of 0 is used because $ZSMP cannot be stopped by SAFECOM if it is
configured as a persistent process. The STARTMODE value of KERNEL is
used so that $ZSMP starts before $ZPMON (which uses STARTMODE
SYSTEM).
b. At the SCF prompt, enter the following to start $ZSMP:
START PROCESS $ZZKRN.#ZSMP
c. At the SCF prompt, enter the following to verify that $ZSMP is running:
STATUS PROCESS $ZZKRN.#ZSMP
d. If the $ZSMP process is not running, check the Event Management Service
(EMS) log for related event messages. See the Operator Messages Manual for
explanation of any console messages received and possible corrective actions.
3. To add the OSS Monitor to the NonStop Kernel subsystem configuration as a
persistent process, at an SCF prompt, enter:
ADD PROCESS $ZZKRN.#ZPMON, &
PROGRAM $SYSTEM.SYSTEM.OSSMON, &
NAME $ZPMON, &
CPU FIRST, &
AUTORESTART 5, &
STARTMODE SYSTEM, &
HOMETERM $ZHOME, &
DEFAULTVOL $SYSTEM.SYSTEM