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

186 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
CAUSE: Log 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
34
MESSAGE: An out-of-range data record length was found. It was
reassigned the maximum allowable value, 2046. (NMDUMPWARN 34)
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.
CAUSE: Log 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
35
MESSAGE: An out-of-range start data record length was found. It was
reassigned the maximum allowable value, 8192. (NMDUMPWARN 34)
CAUSE: An internal error in the NMS trace facility which caused bad
data to be written to the trace 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.
CAUSE: Trace 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
36
MESSAGE: An out-of-range continuation data record length was
found. It was reassigned the maximum allowable value.
(NMDUMPWARN 36)
CAUSE: An internal error in the NMS trace facility which caused bad
data to be written to the trace 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.
CAUSE: Trace 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.