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

Appendix A 183
NMS Error Messages
NM Error Messages
ACTION: Manually check the configuration using NMMGR and ensure
the logging entry for that subsystem is configured properly. Refer to the
appropriate reference manual for assistance.
MESSAGE: LogClass not configured in configuration file.
(NMERR 29)
NMERR 29 CAUSE: NMS logging cannot find the specified log class in the
configuration file NMCONFIG.PUB.SYS. Returned by NMWRITELOG.
The log class specified for the calling subsystem is not configured
correctly in NMCONFIG.PUB.SYS.
ACTION: Use NMMGR to manually check and correct the logging
configuration in CONFIG.PUB.SYS. Make sure that the class name is
spelled correctly. Refer to the appropriate reference manual for
assistance.
MESSAGE: Unable to repetition trace to beginning of file. (NMERR 31)
NMERR 31 CAUSE: FCONTROL 5 failed.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: This program may not be run as a user process.
(NMERR 32)
NMERR 32 CAUSE: User attempted to :RUN one of the NMS program files that are
not allowed to be :RUN. These program files include
LINKMGR.PUB.SYS, NMFILE.PUB.SYS, NMLOGMON.PUB.SYS,
PCMANAGE.PUB.SYS, NMLOGICS.PUB.SYS.
ACTION: None.
MESSAGE: Unable to access logging configuration file. (NMERR 33)
NMERR 33 CAUSE: An unexpected error occurred while NMS logging was trying to
read the logging configuration data in NMCONFIG.PUB.SYS. Returned
by NMOPENLOG.
ACTION: See “Corrupt Configuration File” at the beginning of this
appendix.
MESSAGE: Invalid reference parameter specified. (NMERR 34)
NMERR 34 CAUSE: Condition code “>” returned from an internal data segment
move routine. One of the parameters, passed by reference, would cause
a bounds violation if written to. This message is returned if a bad
condition code is received after call of one of the move routines between
data segments: MBFDS, MFDS, MBTDS, MTDS. This is an internal
error.
ACTION: See “Submitting an SR” at the beginning of this appendix.