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

Appendix A 189
NMS Error Messages
NM Error Messages
MESSAGE: Specified file is a back reference file. (NMERR 65)
NMERR 65 CAUSE: The file name (FileName) parameter of the NMOPENTRACE
procedure contains a back referenced file name (the first ASCII
character is “*”). User specified an incorrect filename either in the
command that starts trace for that subsystem, or in the configuration
file for that subsystem.
ACTION: Specify a valid file name and retry.
MESSAGE: User logging entries are not available. (NMERR 67)
NMERR 67 CAUSE: The LogBuf XDS used for a particular NMS trace file or for
NMS logging has no more available entries to add one more user. An
additional entry is used for tracing whenever additional traces are
requested to go to an existing open trace file. An additional entry is
used for logging whenever a subsystem opens a log file. The user has
requested an unexpectedly large number of concurrent traces to go to
the same trace file.
ACTION: Turn off some of the traces and retry.
CAUSE: An internal error has occurred.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Unable to create the trace process. (NMERR 69)
NMERR 69 CAUSE: The tracing subsystem is unable to create a trace server
process for the NMOPENTRACE request (NMMONSTARTREQ failed).
ACTION: See “Invalid Software Installation,” “Insufficient MPE
Resources,” and “Submitting an SR” at the beginning of this appendix.
MESSAGE: Unable to initialize the trace process. (NMERR 70)
NMERR 70 CAUSE: The tracing subsystem is unable to initialize the trace server
process for the NMOPENTRACE request (unable to create a port or
acquire a data segment).
ACTION: See “Invalid Software Installation,” “Insufficient MPE
Resources,” and “Submitting an SR” at the beginning of this appendix.
MESSAGE: Logging has stopped. (NMERR 71)
NMERR 71 CAUSE: An I/O error or File System error occurred earlier and logging
is not currently taking place. Returned by NMOPENLOG.
ACTION: Enter the SHOWLOG command to find out the status of the log
file and the type of error. Correct the error, and restart logging with a
RESUMENMLOG or a SWITCHNMLOG command. Then retry the action that
led to this error.