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

CPU FIRST, &
AUTORESTART 5, &
STARTMODE SYSTEM, &
HOMETERM $ZHOME, &
DEFAULTVOL $SYSTEM.SYSTEM
4. At an SCF prompt, to start the OSS Monitor, enter:
START PROCESS $ZZKRN.#ZPMON
5. At an SCF prompt, to verify that the OSS Monitor is running, enter:
STATUS PROCESS $ZZKRN.#ZPMON
6. 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 console
messages received and possible corrective actions.
Running the OSS Monitor as a persistent process does not automatically enable the automatic
startup service or select OSS servers or filesets for automatic restart. See the “ALTER SUBSYS, ALTER
MON, and ALTER PROCESS Commands” (page 285) for information on enabling the automatic
startup service, and see the SCF ADD and ALTER commands for information on configuring automatic
restart of filesets and OSS servers.
For more information about managing generic and persistent processes, see the SCF Reference
Manual for the Kernel Subsystem.
PARAMs Used by the OSS Monitor
In G-series RVUs preceding G04.00, you could alter the behavior of the OSS Monitor by setting
TACL PARAMs before starting the OSS Monitor. The actions controlled by these PARAMs could
be changed only while the OSS Monitor was running and in those instances where an SCF command
allowed you to specify a different value.
Beginning with the G04.00 RVU, the OSS Monitor ignores most TACL PARAMs and uses values
configured in one of the following files:
• The ZOSSPARM file
• The ZOSSSERV file
as appropriate for the related OSS facility. The tasks required to configure and check these files
are described later in this section for the ZOSSPARM file and in “Configuration Files” (page 100)
for the ZOSSPARM file and the ZOSSSERV file.
The TACL PARAMs listed in Table 3 (page 53) are intended to be used during the first execution
of the OSS Monitor. If this is a new installation with no OSS Monitor database, then the OSS
Monitor looks for these PARAMs. It stores the values of these PARAMs in the global subsystem
settings, an action equivalent to using the SCF ALTER SUBYS, IOTIMEOUT value, FSCKCPU
value, AUTOSTART value command described in “ALTER SUBSYS, ALTER MON, and ALTER
PROCESS Commands” (page 285).
Table 3 Currently Used TACL PARAMs for the OSS Monitor
DescriptionPARAM
Specifies whether the automatic startup service should be used for any
stopped servers or filesets that are configured to use that service.This
AUTOSTART { AUTO | MANUAL }
PARAM can provide the initial configuration value for the AUTOSTART
attribute of the subsystem. If this PARAM is supplied after the first execution
of the OSS Monitor, it replaces the current value for the AUTOSTART
attribute of the subsystem. This value is kept in the ZOSSPARM file and
controlled through the SCF ALTER SUBSYS command. See “ALTER
SUBSYS, ALTER MON, and ALTER PROCESS Commands” (page 285) for
more information about the options that can be specified.
Specifies which processor to use when the FSCK integrity-checker program
performs fileset recovery.This PARAM can provide the initial configuration
OSS^FSCK^CPU processor
Managing the OSS Subsystem 53