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

The information displayed is the configuration currently used by the OSS Monitor.
The syntax of the SCF INFO SUBSYS command and an example appear under “INFO SUBSYS,
INFO MON, and INFO PROCESS Commands” (page 307).
Checking the Version of the OSS Monitor
When the OSS Monitor is running, you can use the SCF VERSION command to determine the
product-version information for the running copy of the OSS Monitor. For example, if you enter
the following SCF commands:
ASSUME PROCESS $ZPMON
VERSION
the system displays basic product-version information for the running OSS subsystem.
The use of product-version information is described in “Gathering Version Information About OSS
Files” (page 249).
The syntax of the SCF VERSION command and an example appear under “VERSION SUBSYS,
VERSION MON, and VERSION PROCESS Commands” (page 332).
Changing the OSS Subsystem Configuration
If the OSS Monitor is currently running, you can change the configuration of the OSS Monitor in
the ZOSSPARM database file by using the SCF ALTER SUBSYS command. You can change:
• The timeout value used for requests to an OSS name server
• The default spooler location assigned when no REPORT attribute is configured for a fileset
• The default processor in which the FSCK utility is started when the subsystem needs to run it
and either no processor is configured for the fileset or the processor configured for the fileset
is unavailable
• The name of the Guardian disk volume that contains the program files to be used for the CVT
utility, the OSS Monitor, and other OSS environment management software
• The setting for the automatic startup service
The syntax of the SCF ALTER SUBSYS command and an example appear under “ALTER SUBSYS,
ALTER MON, and ALTER PROCESS Commands” (page 285).
The changed values are effective immediately.
Enabling the Automatic Startup Service
To enable the automatic startup service:
1. Start the OSS Monitor without using the AUTOSTART option. See “Starting the OSS Monitor”
(page 51).
2. Use the SCF ALTER command to set the DESIREDSTATE attribute to STARTED for all filesets
and servers that are to be automatically started. See “ALTER FILESET Command” (page 269)
and “ALTER SERVER Command” (page 278).
3. Use the SCF ALTER SUBSYS, AUTOSTART AUTO command to enable the automatic startup
service and initiate automatic startup. See “ALTER SUBSYS, ALTER MON, and ALTER PROCESS
Commands” (page 285).
Removing the OSS File System
This action can be performed in one of these ways:
• Using the procedure described in this subsection.
• Using the OSSREMOV utility. See “OSSREMOV Utility” (page 407)for more information.
To remove the entire OSS file system (all filesets) from your local NonStop node:
Removing the OSS File System 59