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

Appendix A 293
NMS Error Messages
ND Error Messages
NDIERR 120 MESSAGE: One or more required parameters are missing.
(NDIERR 120)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 121 MESSAGE: Directory file not open. (NDIERR 121)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 122 MESSAGE: Relop parameter invalid; must be 0, 1 or 2. (NDIERR 122)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 123 MESSAGE: Name type invalid; must be 1 (NS node name).
(NDIERR 123)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 124 MESSAGE: Name length invalid for name type. (NDIERR 124)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 125 MESSAGE: FFINDBYKEY failed — corrupt file likely. (NDIERR 125)
CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a backup tape. If this fails,
see “Submitting a CR” at the beginning of this appendix.
NDIERR 126 MESSAGE: Cannot find a matching node name in the directory.
(NDIERR 126)
CAUSE: In the directory, no entry could be found with the requested
nodename and global/local flag setting, or a partial nodename (generic
key) was requested and no match could be found.
ACTION: Supply the nodename of an existing entry, or a generic key to
satisfy the match.
NDIERR 127 MESSAGE: FREAD failed — corrupt file likely. (NDIERR 127)
CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a backup tape. If this fails,
see “Submitting a CR” at the beginning of this appendix.
NDIERR 128 MESSAGE: FLOCK failed — internal error. (NDIERR 128)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.