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

198 AppendixA
NMS Error Messages
NM Error Messages
NMERR 72 MESSAGE: This command has no parameter. (NMERR 72)
CAUSE: Parameters were specified for an NMS command that does not
require any parameters. Returned by SHOWNMLOG,
RESUMENMLOG, and SWITCHNMLOG. User entered parameters for
an NMS CI command SHOWNMLOG, SWITCHNMLOG, or RESUMENMLOG.
ACTION: Enter the command name alone without any other text on the
$STDIN or $STDINX record.
NMERR 73 MESSAGE: Invalid logging configuration file. (NMERR 73)
CAUSE: NMCONFIG.PUB.SYS contains invalid logging configuration data.
Returned by NMOPENLOG, NMWRITELOG.
ACTION: See “Corrupt Configuration File” at the beginning of this
appendix.
NMERR 74 MESSAGE: NM Log dictionary table is full. (NMERR 74)
CAUSE: Network management logging facility has a log dictionary table
with a fixed number of available entries. If no free entries are available
to complete the caller request this error message is returned.
Incompatible software versions installed.
ACTION: See “Invalid Software Installation” and “Version
Incompatibilities” at the beginning of this appendix. If this does not
resolve the problem, then see “Submitting a CR” at the beginning of
this appendix.
NMERR 75 MESSAGE: Data is already associated with this identifier. (NMERR 75)
CAUSE: Returned by: NMCONFADDDATA. NMFILE detected
NMFSERR 12. User attempted to add data to a path location where
data already exists. This may not necessarily be an error if the calling
program is trying to determine if data already exists at that location.
This could also be caused by database corruption, or by an internal
error.
ACTION: If data base corruption is suspected, then see “File System
Error” at the beginning of this appendix. If an internal error is
suspected, then see “Submitting a CR” at the beginning of this
appendix.
NMERR 76 MESSAGE: File associated with this transaction is not locked.
(NMERR 76)
CAUSE: Returned by: NMCONFUNLOCKFILE. NMFILE determined
that an NMCONFUNLOCKFILE was attempted on a transaction
without a corresponding NMCONFLOCKFILE. This is not necessarily
an error if the intent of the caller was to determine the lock status of
the file. This could also be caused by an internal error.
ACTION: If an internal error is suspected, see “Submitting a CR” at the
beginning of this appendix.