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

190 AppendixA
NMS Error Messages
NM Error Messages
NMERR 20 MESSAGE: Unable to obtain data segment for tracing. (NMERR 20)
CAUSE: Main NMLogMon was unable to get anextra data segment, or if
internal tracing was specified, was unable to lock the extra data
segment it did get.
ACTION: See “Insufficient MPE Resources” and “Submitting a CR” at
the beginning of this appendix.
NMERR 21 MESSAGE: Must have 1 <= data length <= 8192 bytes. (NMERR 21)
CAUSE: A call to NMCONFadddata or NMCONFupdatedata cannot
send more than 8192 bytes of data. This is probably an internal error in
the calling subsystem.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMERR 25 MESSAGE: Multiple accesses to a trace entity are not supported.
(NMERR 25)
CAUSE: The trace entity passed to NMOPENTRACE is a duplicate trace
entry. NMS tracing will not support multiple NMOPENTRACE calls for
the same trace entity. A trace entity is a unique combination of the
parameters
SubSystemID , TraceElement , and TraceType . A user
entered a command requesting a particular kind of trace when this
trace is already active.
ACTION: Do not request a trace when that trace is already active.
CAUSE: An internal error has occurred.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMERR 26 MESSAGE: Trace entity is not currently being traced. (NMERR 26)
CAUSE: A request was made for the
TraceID of a trace entity that is not
currently active. Returned by NMGETTRACEID. (A trace entity is
composed of a
SubSystemID , TraceElement , and TraceType ).
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMERR 27 MESSAGE: Request can not be completed immediately. (NMERR 27)
CAUSE: A nowait type request cannot be processed immediately.
Returned by some of the NMnnTRACE and NMnnLOG procedures
when the
MODE parameter is set to 1 (nowait mode) and NMS Tracing or
NMS Logging cannot process the request immediately.
ACTION: Normally this is not an error condition.
NMERR 28 MESSAGE: Subsystem not configured in logging configuration.
(NMERR 28)
CAUSE: The
SubSystemID passed to NMOPENLOG cannot be found in
the LOGGING subtree of the NMCONFIG.PUB.SYS configuration file. The
subsystem has not been configured for logging, or the entry is spelled
wrong, or the configuration file has been corrupted.