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

184 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
NMDUMPERR 26 MESSAGE: Error — invalid trace data file. (NMDUMPERR 26)
CAUSE: There was a system failure while tracing was enabled and the
file was closed improperly.
ACTION: Attempt to retrace the error situation.
CAUSE: An internal error in the NMS trace 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 file.
NMDUMPERR 27 MESSAGE: Error — invalid log data file. (NMDUMPERR 27)
CAUSE: There was a system failure while logging was enabled and the
file was closed improperly.
ACTION: Attempt to retrace the error situation.
CAUSE: An internal error in the NMS 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 log file.
NMDUMPWARN
28
MESSAGE: EOF was reached on the output file. The output listing is
incomplete. (NMDUMPWARN 28)
CAUSE: The output disk file was not built large enough to hold the full
dump listing.
ACTION: Redirect the output to a nondisk file, or increase the number of
records in the output file with a FILE equation or BUILD command.
NMDUMPERR 29 MESSAGE: Error occurred during output of formatted data record.
(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”: Rerun
NMDUMP and see if the same 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.