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

234 AppendixA
NMS Error Messages
NMGR Error and Warning Messages
the maximum page count.
ACTION: Restore the configuration file with Reachable Network paths
within the maximum page count.
NMGRERR 95 MESSAGE: You must enter a configuration file name to open or
create. (NMGRERR 95)
CAUSE: The user pressed “Open Config” or “Create Config” but did not
enter the configuration file name on the OPEN screen.
ACTION: Supply the configuration file name.
NMGRERR 96 MESSAGE: You must enter a directory file name to open or create.
(NMGRERR 96)
CAUSE: The user pressed “Open Directory” or “Create Directory”, but
did not fill in the Network Directory File Name field on the OPEN
screen.
ACTION: Supply the network directory file name.
NMGRERR 97 MESSAGE: You must enter a directory file name to open or create.
(NMGRERR 97)
CAUSE: The user entered the NEXT command but there is no next
screen.
ACTION: None.
NMGRERR 98 MESSAGE: There is no entry to be condensed. (NMGRERR 98)
CAUSE: No reachable networks exist in the file to be condensed.
ACTION: None.
NMGRERR 99 MESSAGE: Condense Page function failed. (NMGRERR 99)
CAUSE: Error occurs during “CONDENSE PAGE” while doing an
“nmconfgetdata” or “nmconfrenamepath”. It can be caused by a
corrupted configuration file. Another possibility is that an internal
error is occurring with NMCONF intrinsics.
ACTION: Restore a back up copy of the configuration file and try again.
If the error still occurs, see “Submitting a CR” at the beginning of this
appendix.
NMGRERR 100 MESSAGE: Internal error: Nmconf file number not in file table.
(NMGRERR 100)
CAUSE: The file number was changed in NMMGR but not entered in the
table.
ACTION: Exit NMMGR, then rerun it and try to observe what damage
has been done. Repair if possible or restore the configuration file.
CAUSE: The file number was changed in NMMGR but not entered in the
table.