Using the Node Management Services (NMS) Utilities (MPE/iX 7.0, 7.5)

182 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
NMDUMPERR 20 MESSAGE: Error — unexpected end of input data file.
(NMDUMPERR 20)
CAUSE: There was a system failure while tracing/logging was enabled
and the file was closed improperly.
ACTION: Attempt to relog or retrace the error situation.
CAUSE: An internal error in the NMS trace/log facility or the NMDUMP
facility.
ACTION: File a CR (Change Request). Refer to “Submitting a CR” at the
beginning of this appendix.
CAUSE: Data file has become corrupt.
ACTION: Attempt to recreate the trace or log file.
NMDUMPERR 21 MESSAGE: Error occurred during output of file header.
(NMDUMPERR 21)
CAUSE: A file system error occurred.
ACTION: Attempt to find out what file system error occurred: Rerun
NMDUMP and see if error occurs.
CAUSE: An internal error in NMWRITE.
ACTION: Rerun NMDUMP. File a CR (Change Request) if the same
problem occurs. Refer to “Submitting a CR” at the beginning of this
appendix.
NMDUMPWARN
22
MESSAGE: No data records, from the subsystems selected, were
found in the input file. (NMDUMPWARN 22)
CAUSE: No records were logged/traced to the file from the selected
subsystems.
ACTION: None.
CAUSE: If the input file is a log file, logging for the subsystems selected
may not be enabled.
ACTION: Check the logging configuration portion of NMCONFIG.PUB.SYS
to ensure that logging to disk is enabled for the subsystem(s) and log
class(es) desired. If it is not, make the appropriate changes to the
configuration file through NMMGR.PUB.SYS.
CAUSE: An internal error in the NMS trace/log facility or the NMDUMP
facility.
ACTION: File a CR (Change Request). Refer to “Submitting a CR” at the
beginning of this appendix.