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

168 AppendixA
NMS Error Messages
NMCN Error and Warning Messages
MESSAGE: NM Log Process: Unable to add port dictionary entry.
(NMCNERR 32)
NMCNERR 32 CAUSE: DICTADD returned a non-zero result.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Process: Unable to add to NM Monitor port table.
(NMCNERR 33)
NMCNERR 33 CAUSE: NMMONADDID failed for MainLogMonitor.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Process: Unable to create logging buffer data
segment. (NMCNERR 34)
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.
MESSAGE: NMLG FILE NUMBER nnnn ERROR #nnn. NM LOGGING
STOPPED. (NMCNERR 36)
NMCNERR 36 CAUSE: If the error number is greater than 1, this is the file system
error that occurred when accessing file NMLGnnnn, 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.
MESSAGE: NMLG FILE NUMBER nnnn ERROR #nnn. NM LOGGING
SUSPENDED. (NMCNERR 38)
NMCNERR 38 CAUSE: If the error number is greater than 1, this is the file system
error that occurred when accessing file NMLGnnnn, 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.
MESSAGE: UNABLE TO ACCESS NMLG FILE NUMBER nnnn.
(NMCNERR 42)
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.IfSHOWNMLOG after this gives this
message again, try rebooting the system to force logging to open a new
NMLGnnnn file.
MESSAGE: NM Log Process: Unable to create log dictionary data
segment. (NMCNERR 44)
NMCNERR 44 CAUSE: NM Log Process is unable to acquire an extra data segment.