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

be resolved, the database cannot be opened by the OSS Monitor at startup and the OSS file
system cannot be restarted.
To fix the situation, enter the following commands at a TACL prompt:
VOLUME $SYSTEM.ZXOSSMON
FUP
ALTER ZOSSFSET, ALTFILE (0,ZOSSFS00)
ALTER ZOSSFSET, ALTFILE (1,ZOSSFS01)
EXIT
After these commands are executed, FUP INFO, DETAIL output does not contain question marks
because the Guardian file system is able to resolve the filename correctly. Subsequent attempts to
open ZOSSFSET succeed.
The ZOSSPARM File
The ZOSSPARM file is an Enscribe file that contains the subsystem configuration database for the
OSS Monitor. Entries in this file can be displayed by using the OSS Monitor SCF INFO SUBSYS
command.This file must be maintained by the system manager using the OSS Monitor SCF ALTER
SUBSYS command. It must be present and must contain valid data before the root fileset is first
mounted.
Entries in the ZOSSPARM file must follow these rules:
• Timeout values must be positive multiples of 1 second.
• Any processor number specified must either be:
In the range 0 through 15◦
◦ -1 (which specifies a process-dependent option)
Changes to the ZOSSPARM file take effect immediately.
When a default ZOSSPARM file is created by the OSS Monitor, it contains entries that have the
default values described in “ALTER SUBSYS, ALTER MON, and ALTER PROCESS Commands”
(page 285).
If your system has been upgraded from a G05.00 or later G-series RVU, the OSS Monitor
automatically creates an initial ZOSSPARM file containing the information from the old system’s
ZPOSPARM.
If your system has been upgraded from a G-series RVU preceding G05.00, the OSS Monitor
automatically creates an initial ZOSSPARM file containing the information from the old system’s
TACL PARAMs. See “PARAMs Used by the OSS Monitor” (page 53).
If your system is upgraded to a G06.17 or later G-series RVU, the OSS Monitor automatically
upgrades an existing ZOSSPARM file.
Figure 14 shows how the entries in the ZOSSPARM file affect communications and diagnostic file
logging. An entry also controls the processor in which the FSCK utility usually runs.
106 Managing Servers