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

192 AppendixA
NMS Error Messages
NM Error Messages
NMERR 35 MESSAGE: Internal error: Invalid data segment number. (NMERR 35)
CAUSE: Condition code “>” returned from an internal data segment
move routine. An invalid DST number was specified. This message is
returned if a bad condition code is received after call of one of the move
routines between data segments: MBFDS, MFDS, MBTDS. This is an
internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMERR 36 MESSAGE: Unable to find port for NM Monitor process. (NMERR 36)
CAUSE: Returned by NMMONADDID and NMMONMAINTREQ.
NMMON does not have an entry in Port Dictionary. Cause: internal
problem, or bad software installation.
ACTION: See “Version Incompatibilities” and “Submitting a CR” at the
beginning of this appendix.
NMERR 37 MESSAGE: Calls from split stack are not supported. (NMERR 37)
CAUSE: Returned by NMMONADDID, NMMONSTARTREQ,
NMMONMAINTREQ, NMOPENLINK, NMCLOSELINK,
NMMANAGELINK, NMLINKINFO and NMLINKDIAL. Attempt to
call above procedures in Split stack. Caused by an internal problem, or
bad software installation.
ACTION: See “Invalid Software Installation” and “Submitting a CR” at
the beginning of this appendix.
NMERR 38 MESSAGE: Parameter length out of range. (NMERR 38)
CAUSE: Returned by NMMONSTARTREQ, NMOPENLINK, and
NMOPENLOG2. Length given for string parameter negative or too
long. Caused by an internal problem, or bad software installation.
ACTION: See “Invalid Software Installation” and “Submitting a CR” at
the beginning of this appendix.
NMERR 39 MESSAGE: System shutdown in progress. Can’t complete request.
(NMERR 39)
CAUSE: Returned by NMMONADDID, NMMONSTARTREQ,
NMMONMAINTREQ, NMOPENLINK, NMCLOSELINK,
NMMANAGELINK, NMLINKINFO and NMLINKDIAL. NMMON and
Link Manager are in the process of shutting down.
ACTION: This is normally not an error condition.
NMERR 40 MESSAGE: Port table full. Unable to expand capacity. (NMERR 40)
CAUSE: Returned by NMMONADDID. NMMON cannot expand its DL
DB area. Caused by an internal problem, or bad software installation.
ACTION: See “Invalid Software Installation” and “Submitting a CR”’ at
the beginning of this appendix.