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

Messages
Open System Services Management and Operations Guide—527191-002
A-32
Unnumbered Messages
Cause. The OSS Monitor detected an invalid value for the AUTOSTART attribute on
its command line during startup.
Effect. The OSS Monitor terminates. The existing AUTOSTART attribute value for the
subsystem is unchanged.
Recovery. Restart the OSS Monitor with a correct value, as indicated in the message.
filename
is the Guardian filename of the affected OSS configuration file.
err
is the Guardian file-system error number that describes the failure.
Cause. During automatic conversion of the OSS configuration files from a previous
release version update (RVU), the OSS Monitor found an entry in the ZPCONFIG file
that could not be written to the indicated configuration file.
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
Invalid value specified on the command line for the AUTOSTART
attribute -- must be AUTO or MANUAL
OSS Monitor failed in adding converted record to filename
file -- Error: err