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

Appendix A 183
NMS Error Messages
NMDUMP Error and Warning Messages
NMDUMPWARN
23
MESSAGE: No data records, from the subsystems selected, were
found within the time selected. (NMDUMPWARN 23)
CAUSE: No records were logged/traced to the file from the selected
subsystems during the time range specified.
ACTION: None.
CAUSE: If the input file is a log file, logging for the subsystems selected
may not be enabled.
ACTION: Check the logging configuration portion of NMCONFIG.PUB.SYS
to ensure that logging to disk is enabled for the subsystem(s) and log
class(es) desired. If it is not, make the appropriate changes to the
configuration file through NMMGR.PUB.SYS.
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.
NMDUMPERR 24 MESSAGE: Error — invalid data record in trace file. (NMDUMPERR 24)
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 25 MESSAGE: Error — invalid data record in log file. (NMDUMPERR 25)
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 logfile.