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

176 AppendixA
NMS Error Messages
NMCN Error and Warning Messages
NMCNERR 33 MESSAGE: NM Log Process: Unable to add to NM Monitor port table.
(NMCNERR 33)
CAUSE: NMMONADDID failed for MainLogMonitor.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMCNERR 34 MESSAGE: NM Log Process: Unable to create logging buffer data
segment. (NMCNERR 34)
CAUSE: NM Log Process is unable to acquire an extra data segment.
ACTION: See “Insufficient MPE Resources” at the beginning of this
appendix.
NMCNERR 36 MESSAGE: NMLG FILE NUMBER
nnnn ERROR #nnn . NM LOGGING
STOPPED. (NMCNERR 36)
CAUSE: If the error number is greater than 1, this is the file system
error that occurred when accessing file NMLG
nnnn , where nnnn is the file
number specified. If the error number is 1, then see the comments to
NMCNERR 23.
ACTION: Correct this problem, then type RESUMENMLOG.
NMCNERR 38 MESSAGE: NMLG FILE NUMBER nnnn ERROR #nnn . NM LOGGING
SUSPENDED. (NMCNERR 38)
CAUSE: If the error number is greater than 1, this is the file system
error that occurred when accessing file NMLG
nnnn , where nnnn is the file
number specified. If the error number is 1, refer to message
NMCNERR 23.
ACTION: Correct this problem, then type RESUMENMLOG.
NMCNERR 42 MESSAGE: UNABLE TO ACCESS NMLG FILE NUMBER nnnn .
(NMCNERR 42)
CAUSE: The log buffer indicates the logging state is normal or
suspended, but it contains a current file number of zero, or FFILEINFO
returned a < > condition on the file.
ACTION: Try typing RESUMENMLOG. If SHOWNMLOG after this gives this
message again, try rebooting the system to force logging to open a new
NMLG
nnnn file.
NMCNERR 44 MESSAGE: NM Log Process: Unable to create log dictionary data
segment. (NMCNERR 44)
CAUSE: NM Log Process is unable to acquire an extra data segment.
ACTION: See “Insufficient MPE Resources” at the beginning of this
appendix.