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

176 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
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 log data file. (NMDUMPERR 27)
NMDUMPERR 27 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 log file.
MESSAGE: EOF was reached on the output file. The output listing is
incomplete. (NMDUMPWARN 28)
NMDUMPWARN
28
CAUSE: The output disk file was not built large enough to hold the full
dump listing.
ACTION: Redirect the output to a non-disk file, or increase the number
of records in the output file with a FILE equation or BUILD command.
MESSAGE: Error occurred during output of formatted data record.
(NMDUMPERR 29)
NMDUMPERR 29 CAUSE: A file system error occurred when NMWRITE was trying to
write to the output file. (A probable file system error in this case would
be “out of disk space.”)
ACTION: Verify that the system is at least not “out of space”: Re-run
NMDUMP and see if the same 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: Invalid trace destination specified in global header.
Reassigned according to file characteristics. (NMDUMPWARN 30)
NMDUMPWARN
30
CAUSE: An internal error in the NMS trace facility which caused bad
data to be written to the data file.
ACTION: No action is actually needed. NMDUMP recovers from such
an error in the data file. However, an SR may be filed against the trace
facility. Refer to “Submitting an SR” at the beginning of this appendix.
CAUSE: Data file has become corrupt.