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

processor halt, the OSS Monitor restarts the OSS name server when the processor becomes available
again.
The OSS Monitor remembers the state of all filesets (DIAGNOSING, STARTED, STOPPED, or
UNKNOWN) if it stops and is restarted, even after a system load.
Software Requirements
SCF is required for the OSS environment, and the version of SCF must be compatible with that of
the OSS PM. You can determine the versions of SCF and the OSS PM on your system by using the
SCF VERSION command described in “VERSION SUBSYS, VERSION MON, and VERSION
PROCESS Commands” (page 332).
Localization
The OSS PM does not use the National Language Support (NLS) product. All error messages and
help text are displayed in English.
Networking and Distributed Processing
The OSS Monitor controls one local NonStop node.
Error Handling
The OSS PM defines a set of SPI error messages specific to the OSS environment that are returned
from the OSS Monitor. For normal successful completion of all commands, the standard SPI status
value of ZSPI^ERR^OK is returned.
Some OSS Monitor commands require that the OSS Monitor access its configuration files. If the
OSS Monitor cannot access these files or if they contain invalid data, an error is returned.
For each command involving a fileset, the OSS Monitor first checks whether the fileset exists by
searching the ZOSSFSET file for an entry whose fileset name matches the desired name. If the
fileset name is successfully located in the ZOSSFSET file, the OSS Monitor then verifies that the
current object state of the fileset is compatible with the initial state required by the command being
executed. If the fileset is not successfully located, the appropriate SPI error is returned.
If the OSS Monitor encounters a serious internal inconsistency, it attempts to issue the “internal
error” message (message E00001). For additional information about OSS messages, see
“Messages” (page 335).
Subsystem and Process Attributes
For the OSS Monitor:
• The subsystem ID is 143.
• The device type is 24.
• The device subtype is 0.
• The name of the program file is $SYSTEM.SYSnn.OSSMON.
OSS Monitor SCF Command Reference Information
Use the SCF commands described on the indicated pages to manage the OSS Monitor:
“ADD FILESET Command” (page 256)
“ADD SERVER Command” (page 265)
“ALTER FILESET Command” (page 269)
“ALTER SERVER Command” (page 278)
“ALTER SUBSYS, ALTER MON, and ALTER PROCESS Commands” (page 285)
“CONTROL FILESET Command” (page 288)
“CONTROL SERVER Command” (page 289)
“DELETE FILESET Command” (page 292)
OSS Monitor SCF Command Reference Information 255