Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

AUTOSTART { AUTO | MANUAL }
specifies whether the automatic startup service should start servers or filesets that are configured
for automatic startup. If this parameter is specified on the command line, it overrides any
previous specification of an AUTOSTART PARAM. This parameter also overrides the current
value for the AUTOSTART attribute of the subsystem; see the SCF “ALTER SUBSYS, ALTER MON,
and ALTER PROCESS Commands” (page 285)for more information.
1. Use the TACL STATUS command to verify that the OSS Monitor process $ZPMON is running:
STATUS $ZPMON
2. If the OSS Monitor process is not running, check the Event Management Service (EMS) log
for related event messages. See “Messages” (page 335), for explanation of any messages
received and possible corrective actions.
Starting the OSS Monitor from a TACL prompt with an AUTOSTART value of AUTO does not take
full advantage of the automatic startup service. To fully use the automatic startup service (so that
the OSS environment is brought up when the system is loaded), you must start the OSS Monitor
as a persistent process.
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, &
52 Operating the OSS Environment