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

Appendix A 253
NMS Error Messages
NMGR Error and Warning Messages
NMGRERR 301 MESSAGE: Internal NMMGR error: corrupt file likely. (NMGRERR 301)
CAUSE: This is an internal error.
ACTION: The directory file is probably corrupt and should be replaced
by a copy from a backup tape. Restore both data and key files. See
“Submitting a CR” at the beginning of this appendix.
NMGRERR 302 MESSAGE: No next page of node names. (NMGRERR 302)
CAUSE: This is an informative message that is issued when the user
hits
NEXT PAGE and there are no subsequent names in the directory, or
when the name supplied does not exist.
ACTION: None.
NMGRERR 303 MESSAGE: No previous page of node names. (NMGRERR 303)
CAUSE: This is an informative message that is issued when the user
hits
PREV PAGE and there are none, or when the name supplied does
not exist.
ACTION: None.
NMGRERR 304 MESSAGE: A node with the same name and global/local setting
already exists. (NMGRERR 304)
CAUSE: This is an informative message that is issued when the user
tries to add a node name that already exists into the directory. The
name is probably misspelled, or the wrong global/local setting was
given.
ACTION: Correct the node name, the global/local setting, the type,
and/or the enable flag.
NMGRWARN 305 MESSAGE: Cannot find a node with this name and global/local
setting. (NMGRWARN 305)
CAUSE: This is an informative message that is issued when the user
tries to delete or update a node name that does not exist. The name is
probably misspelled, or the wrong global/local setting was given.
ACTION: Correct the node name, the global/local setting, the type,
and/or the enable flag.
NMGRERR 306 MESSAGE: RENAME requires a new node name and/or new
global/local setting. (NMGRERR 306)
CAUSE: This is an informative message that is issued when the user
tries to rename a node name (global/local setting), but both the new
node name and new global/local setting were omitted.
ACTION: Specify the missing information.