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

288 AppendixA
NMS Error Messages
ND Error Messages
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.
MESSAGE: FREAD failed — corrupt file likely. (NDIERR 164)
NDIERR 164 CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.
MESSAGE: FLOCK failed — internal error. (NDIERR 165)
NDIERR 165 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: FCONTROL/FUNLOCK failed — internal error.
(NDIERR 166)
NDIERR 166 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Cannot read node name backreference record — corrupt
file likely. (NDIERR 167)
NDIERR 167 CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.
MESSAGE: FOPEN of message catalog failed. (NDIERR 180)
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 back-up tape, increase
user’s access rights, or reinstall the product.
MESSAGE: GENMESSAGE failed. (NDIERR 181)
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.
MESSAGE: Error in NMCONF Intrinsic; check for error status.
(NDIERR 190)
NDIERR 190 CAUSE: A problem was encountered when calling an NMCONF
procedure.
ACTION: Refer to the accompanying NMCONF error message.
MESSAGE: Error in Network Directory intrinsic; check for error
status. (NDIERR 191)
NDIERR 191 CAUSE: This is an internal error.