Using the Node Management Services (NMS) Utilities (32022-90053)

174 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
MESSAGE: Error — unexpected end of input data file.
(NMDUMPERR 20)
NMDUMPERR 20 CAUSE: There was a system failure while tracing/logging was enabled
and the file was closed improperly.
ACTION: Attempt to re-log or re-trace the error situation.
CAUSE: An internal error in the NMS trace/log facility or the
NMDUMP facility.
ACTION: File an SR. Refer to “Submitting an SR” at the beginning of
this appendix.
CAUSE: Data file has become corrupt.
ACTION: Attempt to recreate the trace or log file.
MESSAGE: Error occurred during output of file header.
(NMDUMPERR 21)
NMDUMPERR 21 CAUSE: A file system error occurred.
ACTION: Attempt to find out what file system error occurred: Re-run
NMDUMP and see if error occurs.
CAUSE: An internal error in NMWRITE.
ACTION: Re-run NMDUMP. File an SR if the same problem occurs.
Refer to “Submitting an SR” at the beginning of this appendix.
MESSAGE: No data records, from the subsystems selected, were
found in the input file. (NMDUMPWARN 22)
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 an SR. Refer to “Submitting an SR” at the beginning of
this appendix.
MESSAGE: No data records, from the subsystems selected, were
found within the time selected. (NMDUMPWARN 23)
NMDUMPWARN
23
CAUSE: No records were logged/traced to the file from the selected
subsystems during the time range specified.