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

Appendix A 175
NMS Error Messages
NMDUMP Error and Warning Messages
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: Error — invalid data record in trace file. (NMDUMPERR 24)
NMDUMPERR 24 CAUSE: There was a system failure while tracing was enabled and the
file was closed improperly.
ACTION: Attempt to re-trace the error situation.
CAUSE: An internal error in the NMS trace 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 file.
MESSAGE: Error — invalid data record in log file. (NMDUMPERR 25)
NMDUMPERR 25 CAUSE: There was a system failure while logging was enabled and the
file was closed improperly.
ACTION: Attempt to re-trace the error situation.
CAUSE: An internal error in the NMS 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 logfile.
MESSAGE: Error — invalid trace data file. (NMDUMPERR 26)
NMDUMPERR 26 CAUSE: There was a system failure while tracing was enabled and the
file was closed improperly.
ACTION: Attempt to re-trace the error situation.
CAUSE: An internal error in the NMS trace facility or the NMDUMP
facility.