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

Appendix A 209
NMS Error Messages
NM Error Messages
CAUSE: An error occurred while accessing the specific I/O manager.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMERR 187 MESSAGE: Trace for
linkname has been initiated with some
exceptions : HPE status: INFO = ! subsystem ID = !.
CAUSE: This error is often returned even though tracing has been
enabled.
ACTION: None. If this error occurs frequently, submit an CR. See
“Submitting a CR” at the beginning of this appendix.
NMERR 189 MESSAGE: Invalid length for a trace file name.
CAUSE: MPE/iX trace file names are in the format of
filename.group.account and must contain a maximum of eight
characters in the filename, group, and account fields.
ACTION: Reissue the command using a valid trace file name which
contains no more than eight characters in the filename, group, and
account field.
NMERR 193 MESSAGE: Trace buffer size for a LAPB, SDLC or RJE link must be
between 5 & 16. (NMERR 193)
CAUSE: The current buffer sizes supported for LAPB and SDLC are 5K
to 16K.
ACTION: Configure values in the correct range.
NMERR 200 MESSAGE: Unable to access ! subsystem message catalog !.
(NMERR 200)
CAUSE: The first parameter is the subsystem name or subsysid. The
second parameter is the message catalog file name. This is returned by
a datacomm subsystem message-generating routine. The specified
subsystem encountered an error trying to access an error message in
the specified message catalog file.
ACTION: Something is wrong with the specified message catalog file.
Either it does not exist, or is the wrong version, or is inaccessible due to
someone else either storing it or accessing it exclusively, or some other
I/O error has occurred. Correct the problem with the message catalog
and retry.
NMERR 201 MESSAGE: Error accessing NMCAT.PUB.SYS set=! msg=!.
(NMERR 201)
CAUSE: Returned by NMPRINTERRMSG and usually followed by one
or more of messages 202 through 205 below, which further clarifies the
error. NOTE: This message is actually hardcoded in
NMPRINTERRMSG and is included here only for documentation
purposes.