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

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 to get its process name
Cause
The OSS Monitor could not determine its own process name. An internal error might have
occurred.
Effect
The OSS Monitor process terminated abnormally with the SPI error code value -7. The OSS
environment is not available.
Recovery
Restart the OSS Monitor with the process name $ZPMON. 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 found invalid format in ZPCONFIG [ reason ]
reason
is a text message that further describes the problem.
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 interpreted.
Effect
The OSS Monitor process terminated abnormally with the SPI error code value 17. The OSS
environment is not available.
Recovery
Perform the following actions:
1. Remove the invalid database files by entering the following at a TACL prompt:
VOLUME $SYSTEM.ZXOSSMON
PURGE ZOSSFSET ZOSSFS00 ZOSSFS01 ZOSSSERV ZOSSPARM
2. Check that the OSS Monitor is using the correct copy of the ZPCONFIG file for the
conversion. If necessary, move the correct copy of the ZPCONFIG file to
$SYSTEM.ZXOSSMON.
3. Check the format of the ZPCONFIG file entries against the sample file shown in “Manually
Setting Up an OSS Environment” (page 386). Correct any format errors.
4. Restart the OSS Monitor to restart the database creation process:
OSSMON /NAME $ZPMON, TERM $ZHOME, NOWAIT/
Process name of OSS Monitor must be $ZPMON
Cause
The OSS Monitor was started with the name shown as processname in the SPI termination
information for this message.
360 Messages