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

Appendix A 167
NMS Error Messages
NMCN Error and Warning Messages
MESSAGE: NM Log Monitor: Input/Output error in accessing the
system disc cold load area. (NMCNERR 23)
NMCNERR 23 CAUSE: An error occurred trying to access the area of disk where the
next NMLGnnnn, and NMTCnnnn, file name numbers are stored. Check for
other error indications that may affect the system disks, including I/O
errors.
ACTION: Correct any situation that may cause disk I/O errors. If the
problem persists, see “Submitting an SR” at the beginning of this
appendix.
MESSAGE: NM Log Monitor: Illegal parameter passed; create failed.
(NMCNERR 24)
NMCNERR 24 CAUSE: The user has attempted to enter a parameter which is not
valid.
ACTION: Check input parameters and try again.
MESSAGE: NM Log Monitor: CREATEPROCESS error n on
NMLOGMON.PUB.SYS. (NMCNERR 25)
NMCNERR 25 CAUSE: CREATEPROCESS failed for NMLOGMON. The
NMLOGMON.PUB.SYS program file might not be present, or might not be
Load-able. This could happen if the NMS software is not correctly
installed, or if there is a mismatch between NMLOGMON and SL
module versions. Also, there could be other MPE limitations such as
insufficient table space.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Process: Internal error trying to set up NMS
logging. (NMCNERR 26)
NMCNERR 26 CAUSE: An unexpected error has occurred.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: NM Log Process: Unable to obtain port data segment.
(NMCNERR 30)
NMCNERR 30 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 Process: Unable to create port data segment.
(NMCNERR 31)
NMCNERR 31 CAUSE: CREATEPORT returned a PORTID of 0.
ACTION: See “Submitting an SR” at the beginning of this appendix.