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

252 AppendixA
NMS Error Messages
NMGR Error and Warning Messages
NMGRERR 286 MESSAGE: Illegal path name identifier in destination path name.
(NMGRERR 286)
CAUSE:A path ID in the destination pathname is not legal.
ACTION: Check the destination path id for typing mistakes.
NMGRERR 287 MESSAGE: Invalid destination path — path too long. (NMGRERR 287)
CAUSE: The source and destination paths must be the same length.
When entering data on the subtree copy screen, the source path may
appear longer, but should this be the case, the destination path uses
IDs from the source path. This error is generated in the other case
when the destination path is longer than the source path.
ACTION: Check to make sure that you are not missing path ids in the
source path.
NMGRERR 288 MESSAGE: Source path contains empty path identifiers.
(NMGRERR 288)
CAUSE: This occurs when the user leaves path IDs empty in the middle
of the source path field on the copy subtree screen.
ACTION: Check the source path, and fix the path, so that none of the
source path IDs in the middle of the source path are blank.
NMGRERR 289 MESSAGE: The source and destination may not be the same file and
path. (NMGRERR 289)
CAUSE: The user is attempting to copy over the source data, which is
not allowed.
ACTION: Select another file or path to copy into.
NMGRERR 290 MESSAGE: The file does not exist or cannot be opened.
(NMGRERR 290)
CAUSE: An NMCONF file to be opened for a copy could not be accessed.
ACTION: Check the spelling of the filename. Do a “listf <filename>” to
see if file exists.
NMGRERR 291 MESSAGE: Source path is not allowed to be copied. (NMGRERR 291)
CAUSE: The source path is not permitted to be copied by the subtree
command.
ACTION: None.
NMGRERR 300 MESSAGE: Internal NMMGR error: cannot close current Network
Directory. (NMGRERR 300)
CAUSE: This is an internal error.
ACTION: See “Submitting a CR” at the beginning of this appendix.