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

Appendix A 221
NMS Error Messages
NMGR Error and Warning Messages
configuration file concurrently, and one renames or deletes a path which
another is configuring.
ACTION: Coordinate activity between users.
CAUSE: NMMGR has encountered an unexpected condition in the
configuration file. An internal error occurred. Submit a Change
Request. See “Submitting a CR” at the beginning of this appendix.
ACTION: Check the version of NMCONF.
NMGRERR 10 MESSAGE: Unexpected type: NM config file corrupt or bad version.
(NMGRERR 10)
CAUSE: NMMGR has encountered a link data record with a type code
(word #1) that is not currently supported. The configuration file may
have been corrupted by a file system or disk error.
ACTION: Restore an old version of the configuration file if possible, or
delete and reconstruct the corrupt link data record.
NMGRERR 11 MESSAGE: Type must be present. (NMGRERR 11)
CAUSE: The user attempted to add a new LINK without specifying a
link type.
ACTION: The type for a new link must be specified.
NMGRERR 12 MESSAGE: Unexpected data: NM config file corrupt or bad version.
(NMGRERR 12)
CAUSE: NMMGR has encountered unrecognizable data in the
configuration file. A file system or disc error may have corrupted the
configuration file. Possible situations which may cause this error
include: 1) A data record does not match the expected format. 2) A link
data record has an unexpected type code (word #1). 3) A link exists
without a data record to indicate its type.
ACTION: Restore an old version of the configuration file if possible, or
delete and reconstruct the corrupt link data record.
NMGRERR 13 MESSAGE: Maximum number of allowed items already configured.
(NMGRERR 13)
CAUSE: The user attempted to add more items than the maximum
allowed at this level.
ACTION: Check the NMMGR manual for these maximum values.
NMGRERR 14 MESSAGE: Cannot build command table; NMCAT.PUB.SYS corrupt.
(NMGRERR 14)
CAUSE: The file NMCAT.PUB.SYS is not a valid message file, does not
exist, or is corrupt.
ACTION: See “Invalid Software Installation” at the beginning of this
appendix.