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

Appendix A 177
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, you may attempt to recreate the data
file.
MESSAGE: No data records are in the input file. (NMDUMPWARN 31)
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 an SR. Refer to “Submitting an SR” at the beginning of
this appendix.
CAUSE: Data file has become corrupt.
ACTION: Attempt to recreate the data file.
MESSAGE: No additional data records are in the input file.
(NMDUMPWARN 32)
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 an SR. Refer to “Submitting an SR” at the beginning of
this appendix.
CAUSE: Data file has become corrupt.
ACTION: Attempt to recreate the data file.
MESSAGE: An out-of-range block length was found. It was
reassigned the maximum allowable value, 1024. (NMDUMPWARN 33)
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 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 data record length was found. It was
reassigned the maximum allowable value, 2046. (NMDUMPWARN 34)
NMDUMPWARN
34
CAUSE: An internal error in the NMS log facility which caused bad
data to be written to the log data file.