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

Appendix A 289
NMS Error Messages
ND Error Messages
ACTION: Refer to the accompanying NMCONF error message. If the
associated error is number 58, then the configuration file to merge from
does not have any directory data in it. The file must first be read by the
network transport by bringing up the transport in order to extract the
directory data.
MESSAGE: Requires Network Administrator capability. (NDIERR 192)
NDIERR 192 CAUSE: User does not have Network Administrator capabilities.
ACTION: Change user capabilities.
MESSAGE: File recovery: cannot open message catalog.
(NDIERR 200)
NDIERR 200 CAUSE: The message catalog NMMGRCAT.PUB.SYS could not be opened.
Possible CAUSEs include: improper product installation, insufficient
user access rights to the catalog file, or an incorrect version of the
software installed.
ACTION: Reinstall the product, increase the user’s access rights, or
restore NMMGRCAT.PUB.SYS from a back-up tape.
MESSAGE: File recovery: FOPEN of temporary command file failed.
(NDIERR 201)
NDIERR 201 CAUSE: MPE could not open a scratch file to write file recovery
commands into. This could be CAUSEd by one or more of the following
reasons:
• Duplicate file name. BeCAUSE the file name generated is random,
this CAUSE is very unlikely.
• User does not have Save Files capability.
• Other file system error.
ACTION: 1. Consult the associated file system error for problem
resolution.
ACTION: 2. Attempt manual recovery of the directory file using
KSAMUTIL.PUB.SYS.
MESSAGE: File recovery: GEMMESSAGE failed. (NDIERR 202)
NDIERR 202 CAUSE: Could not read a message from the catalog
NMMGRCAT.PUB.SYS. A possible CAUSE is that an incorrect version of
the software is installed.
ACTION: Reinstall the product, restore NMMGRCAT.PUB.SYS, or
attempt manual recovery of the directory file using
KSAMUTIL.PUB.SYS.
MESSAGE: File recovery: FWRITE to temporary command file failed.
(NDIERR 203)
NDIERR 203 CAUSE: This is an internal error.