HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages
NMGRERR 1 MESSAGE Terminal is of incorrect type or cannot be
opened. (NMGRERR 1)
CAUSE The user's terminal is not a block mode terminal
supported by VPLUS/3000.
ACTION Check the terminal type and strap settings.
CAUSE The user is attempting to run NMMGR from a batch
job. Batch operation is not supported.
ACTION None.
CAUSE A terminal I/O or internal VPLUS/3000 error
occurred.
ACTION Check the version of VPLUS/3000 and repeat
VPLUS/3000 installation if necessary.
--------------------------------------------------------------------------
NMGRERR 2 MESSAGE Form file is missing or cannot be opened.
(NMGRERR 2)
CAUSE NMMGR was unable to open the forms file
NMMGRF.PUB.SYS at program startup. The file
NMMGRF.PUB.SYS is missing.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
CAUSE A file equation exists for NMMGRF.PUB.SYS.
ACTION Check for file equations using LISTEQ5.PUB.SYS
and RESET if necessary.
CAUSE File NMMGRF.PUB.SYS is not a valid VFAST or
VFORM forms file, or it has become corrupted.
ACTION Restore a back-up copy of NMMGRF.PUB.SYS.
CAUSE An internal VPLUS/3000 error occurred.
ACTION Check the version of VPLUS/3000 and repeat
VPLUS/3000 installation if necessary.
--------------------------------------------------------------------------
NMGRERR 3 MESSAGE That type is not defined for this class of
items.
(NMGRERR 3)
CAUSE The user entered a type name in the TYPE field
of a typed-select screen that is not defined for
this screen.
ACTION Check the subsystem manual for correct type
names and try again.
--------------------------------------------------------------------------
NMGRERR 4 MESSAGE That function is not implemented. (NMGRERR 4)
CAUSE The user pressed an invalid function key (with a
blank label), or pressed the [ENTER] in a screen
without a command window (currently only the
OPEN FILE screen).
ACTION None.
--------------------------------------------------------------------------
NMGRERR 5 MESSAGE Not a valid GR cmd or @athname or : cmd.
(NMGRERR 5)
CAUSE The user typed an unrecognizable command in the
command window and pressed [ENTER].
ACTION Check the spelling of the command, and check the
list of valid commands in your subsystem node
management or configuration manual.
--------------------------------------------------------------------------
NMGRERR 6 MESSAGE End of file on $STDINX. Cannot accept further
input. (NMGRERR 6)
CAUSE The user typed :EOF or :EOD in response to the
prompt:
"Press Return when done viewing screen
contents."
ACTION This error is irrecoverable since the terminal
is closed for further input. Run NMMGR again to
continue configuration.
--------------------------------------------------------------------------
NMGRERR 7 MESSAGE Warning: Screen changed. Use UPDATE to save
data.
CAUSE The user changed information on a data screen
and pressed a key other than UPDATE. This
warning prevents accidential exit from the
screen without saving changes.
ACTION The user may ignore the warning by pressing a
key other than UPDATE, or may save changes by
pressing UPDATE.
--------------------------------------------------------------------------
NMGRERR 8 MESSAGE There are no entries at this level to display.
CAUSE The user pressed the PREV PAGE or NEXT PAGE key
in a selection screen when there are no items to
be displayed on this select screen. Scrolling
with these keys is only necessary when there are
already items configured.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 9 MESSAGE Internal NM configuration file error. (NMGRERR
9)
CAUSE NMMGR has encountered an unexpected condition in
the configuration file.
ACTION Check the NMCONF error (if one is reported) for
further information.
CAUSE NMMGR has encountered an unexpected condition in
the configuration file. Two or more users are
updating the same configuration file
concurrently, and one renames or deletes a path
which another is configuring.
ACTION Coordinate activity between users.
CAUSE NMMGR has encountered an unexpected condition in
the configuration file. An internal error
occurred. Submit a Service Request. See
"Submitting an SR" at the beginning of this
appendix.
ACTION Check the version of NMCONF.
--------------------------------------------------------------------------
NMGRERR 10 MESSAGE Unexpected type: NM config file corrupt or bad
version. (NMGRERR 10)
CAUSE NMMGR has encountered a link data record with a
type code (word #1) that is not currently
supported. The configuration file may have been
corrupted by a file system or disc error.
ACTION Restore an old version of the configuration file
if possible, or delete and reconstruct the
corrupt link data record.
--------------------------------------------------------------------------
NMGRERR 11 MESSAGE Type must be present. (NMGRERR 11)
CAUSE The user attempted to add a new LINK without
specifying a link type.
ACTION The type for a new link must be specified.
--------------------------------------------------------------------------
NMGRERR 12 MESSAGE Unexpected data: NM config file corrupt or bad
version. (NMGRERR 12)
CAUSE NMMGR has encountered unrecognizable data in the
configuration file. A file system or disc error
may have corrupted the configuration file.
Possible situations which may cause this error
include: 1) A data record does not match the
expected format. 2) A link data record has an
unexpected type code (word #1). 3) A link
exists without a data record to indicate its
type.
ACTION Restore an old version of the configuration file
if possible, or delete and reconstruct the
corrupt link data record.
--------------------------------------------------------------------------
NMGRERR 13 MESSAGE Maximum number of allowed items already
configured. (NMGRERR 13)
CAUSE The user attempted to add more items than the
maximum allowed at this level.
ACTION Check the NMMGR manual for these maximum values.
--------------------------------------------------------------------------
NMGRERR 14 MESSAGE Cannot build command table; NMCAT.PUB.SYS
corrupt. (NMGRERR 14)
CAUSE The file NMCAT.PUB.SYS is not a valid message
file, does not exist, or is corrupt.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
A file equation exists for NMMGRCAT.PUB.SYS.
ACTION Check for file equations using LISTEQ2.PUB.SYS
and RESET if necessary.
CAUSE The table of commands in the NM catalog file
NMCAT.PUB.SYS is corrupt or missing. File
NMCAT.PUB.SYS is not a valid catalog file, or it
has become corrupted.
ACTION Restore a back-up copy of NMMGRF.PUB.SYS.
CAUSE The table of commands in the NM catalog file
NMCAT.PUB.SYS is corrupt or missing. Set 7 of
NMCAT.PUB.SYS (the command set) is missing, or
some commands have been deleted from this set.
ACTION Restore a back-up copy of NMMGRF.PUB.SYS.
--------------------------------------------------------------------------
NMGRERR 15 MESSAGE Missing data: NM config file corrupt or bad
version. (NMGRERR 15)
CAUSE NMMGR was unable to locate type code in data
record.
ACTION Restore an old version of the configuration file
if possible, or delete and reconstruct the
corrupt link data record.
--------------------------------------------------------------------------
NMGRERR 16 MESSAGE Cannot set up form for next screen. (NMGRERR
16)
CAUSE The forms file NMMGRF.PUB.SYS may be missing or
corrupt.
ACTION Go to the Errors screen and check any other
errors which are displayed. See "Invalid
Software Installation" at the beginning of this
appendix.
CAUSE A terminal I/O error may have occurred. A user
may have entered :EOF or :EOD in response to the
prompt "Press RETURN when done viewing
contents," thereby closing the terminal for
further input.
ACTION Check the state of the terminal. Run NMMGR
again if the terminal is closed for input.
CAUSE A data record may be corrupted, making it
impossible for NMMGR to display it.
ACTION Go to the Errors screen and check any other
errors which are displayed. See "Invalid
Software Installation" at the beginning of this
appendix.
CAUSE NMMGR was unable to display the form for the
screen which the user selected. An internal
VPLUS/3000 or NMCONF error may have occurred.
ACTION Check the version of VPLUS/3000 and NMCONF and
restore back-up copies if necessary.
--------------------------------------------------------------------------
NMGRERR 17 MESSAGE No errors have yet occurred. (NMGRWARN 17)
CAUSE The user has gone to the ERRORS screen to check
the last error, but no errors have occurred.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 19 MESSAGE MPE command error. (NMGRERR 19)
CAUSE The user executed an MPE command (by entering
the command preceded by a colon and pressing
ENTER), and the command terminated in an error
state.
ACTION Use the Error Information screen and check the
Command Interpreter error for further
information.
--------------------------------------------------------------------------
NMGRERR 20 MESSAGE Item does not exist: use the ADD key to create
a new item. (NMGRERR 20)
CAUSE The user tried to DELETE, RENAME, or UPDATE an
item in a select screen, but the item does not
exist in the configuration file.
ACTION Use the ADD key if you intend to add the new
item; otherwise check the spelling of the item
name.
--------------------------------------------------------------------------
NMGRERR 21 MESSAGE Item already exists. (NMGRERR 21)
CAUSE The user tried to ADD an item in a select
screen, but the item already exists.
ACTION Check the spelling of the item name.
--------------------------------------------------------------------------
NMGRERR 22 MESSAGE Cannot open NM configuration file. (NMGRERR 22)
CAUSE A file system error occurred.
ACTION Go to the Errors screen and check for a file
system error (FSERR). Correct the error and try
again.
CAUSE The NMFILE.PUB.SYS process of the Node
Management Services is not running.
ACTION Go the Errors screen and check for FSERR 97. If
this error occurred, the problem may be due to a
version mismatch in the NMS subsystem. See
"Invalid Software Installation" at the beginning
of this appendix.
--------------------------------------------------------------------------
NMGRERR 23 MESSAGE Cannot reopen NM configuration file. (NMGRERR
23)
CAUSE NMMGR was unable to reopen the configuration
file after closing it for compression.
ACTION Check the NMCONF or File System error (if one is
reported) for further information. This error
is fatal and cannot be recovered except by
running NMMGR again. See message NMGRERR 22.
--------------------------------------------------------------------------
NMGRERR 24 MESSAGE Cannot compress NM configuration file. (NMGRERR
24)
CAUSE A file system error occurred.
ACTION Go to the Errors screen and check for a file
system error (FSERR). Correct the error and try
again.
CAUSE You are not the creator of the configuration
file.
ACTION Go the Errors screen and check for FSERR 94. If
this error occurred, you can copy the file and
then compress it, or ask the creator to compress
the file.
CAUSE NMMGR was unable to compress the configuration
file because at least one other user is
currently accessing the file.
ACTION COMPRESS requires exclusive access to the
configuration file. Use LISTF,2 to check
whether other users are accessing this file.
Wait until the file is not being accessed and
try again.
CAUSE The absolute value of the number of records to
add or remove is too large. The resulting file
would not have been able to contain all the
records in the file, or, if a positive number
was specified, the resulting file would have
exceeded the 64,000 record limit.
ACTION Enter a different value.
--------------------------------------------------------------------------
NMGRERR 25 MESSAGE NA or NM capability is needed to run NMMGR.
(NMGRERR 25)
CAUSE The user does not have the Node Manager or
Network Administrator capability required to run
NMMGR.
ACTION Check user capability with program
LISTDIR5.PUB.SYS, and contact the account
manager or system manager if an additional
capability is needed.
--------------------------------------------------------------------------
NMGRERR 26 MESSAGE File already exists. Use OPEN FILE (f1).
(NMGRERR 26)
CAUSE The user tried to CREATE a file in the OPEN FILE
screen when the file already exists.
ACTION Delete the file to create a new, empty
configuration file, or use the OPEN key to open
an existing file.
--------------------------------------------------------------------------
NMGRERR 27 MESSAGE Must specify new name for rename. (NMGRERR 27)
CAUSE The user tried to RENAME an item in a select
screen without specifying the new name.
ACTION Enter a name in the rename field and try again.
--------------------------------------------------------------------------
NMGRERR 28 MESSAGE File does not exist. Use CREATE FILE (f2).
(NMGRERR 28)
CAUSE The user tried to OPEN a file in the OPEN FILE
screen when the file does not exist.
ACTION Use the CREATE key to create a new file.
--------------------------------------------------------------------------
NMGRERR 31 MESSAGE That command is ambiguous--use more letters.
(NMGRERR 31)
CAUSE The user typed an ambiguous command prefix in
the command window and hit ENTER.
ACTION Make the prefix unambiguous by using more
letters of the command. Check the NMMGR manual
for unambiguous command prefixes.
--------------------------------------------------------------------------
NMGRERR 32 MESSAGE Internal Error: Maximum path depth exceeded.
(NMGRERR 32)
CAUSE This error in an internal NMMGR error. NMMGR
has created a path whose depth exceeds the
maximum allowable depth for paths.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 33 MESSAGE Path name format is invalid. (NMGRERR 33)
CAUSE NMMGR encountered a path name whose format is
not recognized. A possible situation which may
cause this error is that the user has entered an
incorrect path name in the command window.
ACTION Check your subsystem node management or
configuration manual for correct format of a
path name and check the subsystem manual for
valid paths.
CAUSE An internal NMMGR error has occurred.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 34 MESSAGE Error occurred while listing configuration file.
(NMGRERR 34)
CAUSE An error occurred during output of the tree
structure or data records of a configuration
file.
ACTION Check the NMCONF or File System error to
determine the specific error.
CAUSE The configuration file may have corrupt data
records or invalid paths.
ACTION Delete and reconstruct the corrupt link data
record, or restore a backup copy of the
configuration file if possible and run NMMGRVER
again. If the error still occurs, submit a
Service Request. See "Submitting an SR" at the
beginning of this appendix.
CAUSE If the file FORMLIST is equated to a disc file,
the file may be too small to accommodate the
output listing.
ACTION Check the size of the file and change the file
size specification if necessary.
--------------------------------------------------------------------------
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.
--------------------------------------------------------------------------