Open System Services Management and Operations Guide (G06.25+, H06.03+)

Messages
Open System Services Management and Operations Guide—527191-002
A-38
Numbered Messages
4. Restart the OSS Monitor to restart the database creation process:
OSSMON /NAME $ZPMON, TERM $ZHOME, NOWAIT/
Cause. The OSS Monitor was started with the name shown as processname in the
SPI termination information for this message.
Effect. The OSS Monitor process terminated abnormally with the SPI error code
value -33. The OSS environment is not available.
Recovery. Restart the OSS Monitor with the process name $ZPMON:
OSSMON /NAME $ZPMON, TERM $ZHOME, NOWAIT/
Cause. The version of the OSS Monitor is G09 or later and the system is an HP
NonStop K-series system (release versions D4x).
Effect. The OSS Monitor process issues the error message on its home terminal and
terminates.
Recovery. Restore the previous version of the OSS Monitor.
Cause. The OSS Monitor does not recognize a keyword specified as a parameter on
the command line during startup. This most commonly indicates a typographical error.
Effect. The OSS Monitor terminates.
Recovery. Restart the OSS Monitor using a corrected keyword in its command line.
Numbered Messages
Numbered OSS Monitor SCF messages are described on the following pages in order
by message number.
Process name of OSS Monitor must be $ZPMON
This version of OSSMON only runs on Himalaya S Series servers
Unknown keyword specified on the command line
Note. Negative-numbered messages are common to most SCF subsystem modules. If you
receive a negative-numbered message, see the description of “Common Error Messages” in
the appendix “SCF Error Messages” in the Subsystem Control Facility (SCF) Reference
Manual.