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

178 AppendixA
NMS Error Messages
NMDUMP Error and Warning Messages
ACTION: No action is actually needed. NMDUMP recovers from such
an error in the data file. However, an SR may be filed against the log
facility. Refer to “Submitting an SR” 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.
MESSAGE: An out-of-range start data record length was found. It was
reassigned the maximum allowable value, 8192. (NMDUMPWARN 34)
NMDUMPWARN
35
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 SR may be filed against the log
facility. Refer to “Submitting an SR” 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.
MESSAGE: An out-of-range continuation data record length was
found. It was reassigned the maximum allowable value.
(NMDUMPWARN 36)
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 SR may be filed against the log
facility. Refer to “Submitting an SR” 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.