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

166 AppendixA
NMS Error Messages
NMCN Error and Warning Messages
MESSAGE: NM Log Monitor: Another MainLogMonitor exists. This
one terminating. (NMCNERR 16)
NMCNERR 16 CAUSE: A Main Log Monitor process has found its entry already exists
in the port dictionary.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Monitor: Unable to obtain port data segment.
(NMCNERR 17)
NMCNERR 17 CAUSE: INITPORTDST returned a DST number of 0. The system is
unable to allocate any extra data segments.
ACTION: See “Insufficient MPE Resources” at the beginning of this
appendix.
MESSAGE: NM Log Monitor: Unable to create port in data segment.
(NMCNERR 18)
NMCNERR 18 CAUSE: CREATEPORT returned a PORTID of 0.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Monitor: Unable to add port in dictionary entry.
(NMCNERR 19)
NMCNERR 19 CAUSE: DICTADD returned a non-zero result.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Monitor: Unable to add to NM Monitor port table.
(NMCNERR 20)
NMCNERR 20 CAUSE: NMMONADDID failed for MainLogMonitor.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Monitor: Unable to create user logging data
segment. (NMCNERR 21)
NMCNERR 21 CAUSE: Main Log Monitor is unable to acquire an extra data segment.
ACTION: See “Insufficient MPE Resources” at the beginning of this
appendix.
MESSAGE: NM Log Monitor: Unable to create trace dictionary data
segment. (NMCNERR 22)
NMCNERR 22 CAUSE: Main Log Monitor is unable to acquire an extra data segment.
ACTION: See “Insufficient MPE Resources” at the beginning of this
appendix.