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

Appendix A 185
NMS Error Messages
NMDUMP Error and Warning Messages
NMDUMPWARN
30
MESSAGE: Invalid trace destination specified in global header.
Reassigned according to file characteristics. (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 CR may be filed against the trace
facility. Refer to “Submitting a CR” at the beginning of this appendix.
CAUSE: Data file has become corrupt.
ACTION: No action is actually needed. NMDUMP recovers from such an
error in the data file. However, you may attempt to recreate the data
file.
NMDUMPWARN
31
MESSAGE: No data records are in the input file. (NMDUMPWARN 31)
CAUSE: No data records were logged/traced to the data file.
ACTION: None.
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 data file.
NMDUMPWARN
32
MESSAGE: No additional data records are in the input file.
(NMDUMPWARN 32)
CAUSE: It is the end of the file.
ACTION: None.
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 data file.
NMDUMPWARN
33
MESSAGE: An out-of-range block length was found. It was
reassigned the maximum allowable value, 1024. (NMDUMPWARN 33)
CAUSE: An internal error in the NMS log facility which caused bad data
to be written to the log data file.
ACTION: No action is actually needed. NMDUMP recovers from such an
error in the data file. However, an CR may be filed against the log
facility. Refer to “Submitting a CR” at the beginning of this appendix.