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

Appendix A 175
NMS Error Messages
NMCN Error and Warning Messages
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 a CR” at the beginning of this
appendix.
NMCNERR 24 MESSAGE: NM Log Monitor: Illegal parameter passed; create failed.
(NMCNERR 24)
CAUSE: The user has attempted to enter a parameter which is not valid.
ACTION: Check input parameters and try again.
NMCNERR 25 MESSAGE: NM Log Monitor: CREATEPROCESS error
n on
NMLOGMON.PUB.SYS. (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 a CR” at the beginning of this appendix.
NMCNERR 26 MESSAGE: NM Log Process: Internal error trying to set up NMS
logging. (NMCNERR 26)
CAUSE: An unexpected error has occurred.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMCNERR 30 MESSAGE: NM Log Process: Unable to obtain port data segment.
(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.
NMCNERR 31 MESSAGE: NM Log Process: Unable to create port data segment.
(NMCNERR 31)
CAUSE: CREATEPORT returned a PORTID of 0.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMCNERR 32 MESSAGE: NM Log Process: Unable to add port dictionary entry.
(NMCNERR 32)
CAUSE: DICTADD returned a nonzero result.
ACTION: See “Submitting a CR” at the beginning of this appendix.