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

Effect
The OSS Monitor process terminated abnormally with the SPI error code value 17. The OSS
environment is not available.
Recovery
Perform the following steps:
1. See the Guardian Procedure Errors and Messages Manual for a description of the file-system
error and possible corrective actions. Correct the problem.
2. Remove the invalid database files by entering the following at a TACL prompt:
VOLUME $SYSTEM.ZXOSSMON
PURGE ZOSSFSET ZOSSFS00 ZOSSFS01 ZOSSSERV ZOSSPARM
3. Restart the OSS Monitor to restart the database creation process:
OSSMON /NAME $ZPMON, TERM $ZHOME, NOWAIT/
If the problem persists, check the Event Management Service (EMS) log for related messages.
Contact your service provider and provide all relevant information as follows:
• Description of the problem and accompanying symptoms
• Details from the message or messages generated
• Supporting documentation such as EMS logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global Customer Support Center
(GCSC), supply your system number and the numbers and versions of all related products as
well.
OSS Monitor failed in reading filename file -- Error: err
filename
is the Guardian filename of the affected OSS configuration file.
err
is the Guardian file-system error number that describes the failure.
Cause
The OSS Monitor could not read the indicated OSS configuration file. This message might
indicate that the configuration file is corrupted.
Effect
The OSS Monitor process terminated abnormally with the SPI error code value 17. The OSS
environment is not available.
Recovery
Perform the following steps:
1. See the Guardian Procedure Errors and Messages Manual for a description of the file-system
error err and possible corrective actions. Correct the problem.
2. Remove the invalid database files by entering the following at a TACL prompt:
VOLUME $SYSTEM.ZXOSSMON
PURGE ZOSSFSET ZOSSFS00 ZOSSFS01 ZOSSSERV ZOSSPARM
3. Restart the OSS Monitor to restart the database creation process:
OSSMON /NAME $ZPMON, TERM $ZHOME, NOWAIT/
If the problem persists, check the Event Management Service (EMS) log for related messages.
Contact your service provider and provide all relevant information as follows:
• Description of the problem and accompanying symptoms
• Details from the message or messages generated
• Supporting documentation such as EMS logs, trace files, and a processor dump, if applicable
OSS Monitor Messages 359