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

226 AppendixA
NMS Error Messages
NMGR Error and Warning Messages
NMGRERR 36 MESSAGE: Invalid syntax for file name. (NMGRERR 36)
CAUSE: The user attempted to OPEN or CREATE a configuration file
with an invalid file name.
ACTION: Check the spelling and syntax of the file name.
NMGRERR 37 MESSAGE: ENTER executes commands: the command field is blank.
(NMGRERR 37)
CAUSE: The user pressed
[ENTER] without putting a command in the
command window. NMMGR uses
[ENTER] ONLY for commands.
Modifications to the configuration file are all made using function keys.
ACTION: Make modifications to the configuration file by using the
function keys.
NMGRERR 38 MESSAGE: MPE command warning. (NMGRERR 38)
CAUSE: The user executed an MPE command (by entering the command
preceded by a colon and pressing ENTER), and the command
terminated in a warning state.
ACTION: Use the Error Information screen and check the Command
Interpreter error for further information.
NMGRERR 39 MESSAGE: Unable to set termination trap handler. (NMGRERR 39)
CAUSE: The termination trap handling procedure for program aborts
cannot be set. This error indicates an internal MPE problem in the
procedure XDSNTRAP, which places a termination procedure PLABEL
in the process context for use by MPE during process termination.
ACTION: Check the MPE installation to see that XDSNTRAP is present
and working.
NMGRERR 40 MESSAGE: Must open a file before using this command.
(NMGRERR 40)
CAUSE: The user is trying to view a configuration screen without first
opening a configuration file.
ACTION: Open the configuration file and enter the command again.
NMGRERR 41 MESSAGE: Internal error: Unexpected screen length. (NMGRERR 41)
CAUSE: The configuration file is corrupted.
ACTION: Restore a backup copy of the configuration file if possible and
run NMMGRVER again. If the error still occurs, submit a Change
Request. See “Submitting a CR” at the beginning of this appendix.
CAUSE: The forms file is corrupted or is a bad version.
ACTION: See “Invalid Software Installation” at the beginning of this
appendix.