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

ABENDED: processname CPU time: interval 3: Premature process termination
with fatal errors or diagnostics Termination info: code Subsystem:
TANDEM.143.release text-message
processname
is the name of the failed process. Unless otherwise indicated in the specific message description,
this name is always $ZPMON.
interval
is the elapsed time since the start of the failed process, in the form
dd mmm yyyy hh:mm:ss.mil.
code
is the SPI error code of the failure. Values for this are indicated in the specific message
descriptions.
release
is the major release version identifier for the failed process. For example, the version of the
OSS Monitor in the D44.00 release version update (RVU) has the release value D40.
text-message
is the unnumbered message that describes the cause of the failure.
The possible text messages are described on the following pages in alphabetic order.
Invalid value specified for the AUTOSTART PARAM -- must be AUTO or
MANUAL
Cause
The OSS Monitor detected an invalid value for the AUTOSTART PARAM 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.
Invalid value specified on the command line for the AUTOSTART attribute
-- must be AUTO or MANUAL
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.
OSS Monitor failed in adding converted record to 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
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.
356 Messages