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

296 AppendixA
NMS Error Messages
ND Error Messages
NDIERR 163 MESSAGE: FREADBYKEY failed — corrupt file likely. (NDIERR 163)
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 164 MESSAGE: FREAD failed — corrupt file likely. (NDIERR 164)
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 165 MESSAGE: FLOCK failed — internal error. (NDIERR 165)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 166 MESSAGE: FCONTROL/FUNLOCK failed — internal error.
(NDIERR 166)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NDIERR 167 MESSAGE: Cannot read node name backreference record — corrupt
file likely. (NDIERR 167)
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 180 MESSAGE: FOPEN of message catalog failed. (NDIERR 180)
CAUSE: The message catalog NMMGRCAT.PUB.SYS could not be opened.
Possible CAUSEs and solutions include incorrect software installation,
insufficient user access rights to the file, or incorrect version of
software.
ACTION: Restore NMMGRCAT.PUB.SYS from a backup tape, increase
user’s access rights, or reinstall the product.
NDIERR 181 MESSAGE: GENMESSAGE failed. (NDIERR 181)
CAUSE: A message could not be read from the message catalog. A
possible CAUSE is incorrect version of the software.
ACTION: Reinstall the product.
NDIERR 190 MESSAGE: Error in NMCONF Intrinsic; check for error status.
(NDIERR 190)
CAUSE: A problem was encountered when calling an NMCONF
procedure.
ACTION: Refer to the accompanying NMCONF error message.