HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd.)
NMGRERR 97 MESSAGE There is no next screen after this screen.
(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 an SR" 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.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 101 MESSAGE Internal error: Midas file number not in file
table. (NMGRERR 101)
CAUSE The file number was not located in a search
through the table. It is likely that a file
number was changed in NMMGR but not entered in
the table.
ACTION Exit NMMGR, and rerun NMMGR and try to observe
what damage has been done. Repair if possible
or restore the configuration file. If the
problem still exists, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 102 MESSAGE Internal error: Unable to remove closed file
from file table (NMGRERR 102)
CAUSE An attempt to clear the file table of a closed
file failed.
ACTION Exit NMMGR. It is possible that no damage
occurred. Rerun NMMGR. If the problem still
exists, see "Submitting an SR" at the beginning
of this appendix.
--------------------------------------------------------------------------
NMGRERR 103 MESSAGE Internal error: NMMGR file table inconsistent.
(NMGRERR 103)
CAUSE On trying to access the file table, an error was
found in the table. This will happen at open
time if an attempt is made to put a file into
the file table and if the slot in the table is
already occupied.
ACTION Exit NMMGR. It is possible that no damage
occurred. Rerun NMMGR. If the problem still
exists, see "Submitting an SR" at the beginning
of this appendix.
--------------------------------------------------------------------------
NMGRERR 104 MESSAGE Netxport has locked the file; cannot begin
guided task; wait (NMGRERR 104)
CAUSE The network transport is being started using the
file that NMMGR has open as the active
configuration file. A guided dynamic update
cannot be started until the transport has been
started.
ACTION Wait until the transport is started and then try
again.
--------------------------------------------------------------------------
NMGRERR 105 MESSAGE The file has been locked; type 'STOP' to abort,
or wait (NMGRERR 105)
CAUSE Either the transport is being started using the
file NMMGR has open as the active configuration
file, or NMMGR is processing a guided dynamic
update which cannot continue until the transport
has been started.
ACTION Wait until the transport is started and then try
again.
--------------------------------------------------------------------------
NMGRERR 106 MESSAGE The file has been locked; cannot begin guided
task (NMGRERR 106)
CAUSE The transport is using the file NMMGR has open
as the active configuration file. Guided
configuration cannot be performed on an active
configuration file (only guided dynamic updates
can).
ACTION None.
--------------------------------------------------------------------------
NMGRERR 107 MESSAGE The file has been locked; Type 'STOP' to abort
(NMGRERR 107)
CAUSE The transport is being started using the file
NMMGR has open as the active configuration file.
NMMGR is performing a guided configuration which
cannot continue while the transport is up. The
file cannot be modified except with guided
dynamic updates until the transport is brought
down.
ACTION Type 'STOP' in the command window and press
ENTER to stop guided configuration.
--------------------------------------------------------------------------
NMGRERR 108 MESSAGE The file has been locked; cannot make any
modifications (NMGRERR 108)
CAUSE Transport is using the file NMMGR has open as
the active configuration file. The file cannot
be changed except with guided configuration.
ACTION Enter guided configuration to perform this
function.
--------------------------------------------------------------------------
NMGRERR 109 MESSAGE This file has been locked; subtree copy aborted.
(NMGRERR 109)
CAUSE The transport is being initiated using the file
that NMMGR has open as the active configuration
file, and NMMGR was in the middle of a subtree
copy.
ACTION When the transport is no longer running, purge
the subtree you were copying into and restart
the subtree copy.
--------------------------------------------------------------------------
NMGRERR 110 MESSAGE Internal error: Cannot check file lock status;
data not updated (NMGRERR 110)
CAUSE NMMGR cannot determine whether or not the
transport is using this file.
ACTION If the transport is being started or shut down,
wait until it is finished and then try again.
If the problem still exists, see "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 111 MESSAGE Enter an ni name into the required field.
(NMGRERR 111)
CAUSE During guided configuration for an NI, you
neglected to enter an NI name into the NI field.
ACTION Enter the proper NI name into the NI field.
--------------------------------------------------------------------------
NMGRERR 112 MESSAGE The DELETE and RENAME options are not allowed in
guided update. (NMGRERR 112)
CAUSE You are in guided update and have attempted to
delete or rename an entry from the Gateway
Select screen.
ACTION Enter manual configuration to perform this
function.
--------------------------------------------------------------------------
NMGRERR 113 MESSAGE HP-IBM not validated. Type exit again to leave
NMMGR. (NMGRERR 113)
CAUSE Data in the SNANODE, NRJE, or IMF subsystems was
changed and HP-IBM was not successfully
validated afterwards.
ACTION The user can go to the validation screen and
validate HP-IBM. The user can type exit again
and leave the file unvalidated.
--------------------------------------------------------------------------
NMGRERR 114 MESSAGE Cannot find validation program NMMGRVAL.PUB.SYS
(NMGRERR 114)
CAUSE File does not exist.
ACTION Check to see what happened to the file
NMMGRVAL.PUB.SYS. If it has been inadvertently
purged, try restoring it from a backup tape.
--------------------------------------------------------------------------
NMGRERR 115 MESSAGE Cannot send mail to validation program (NMGRERR
115)
CAUSE Internal error.
ACTION Contact your Hewlett-Packard representative.
--------------------------------------------------------------------------
NMGRERR 116 MESSAGE Cannot activate validation program
NMMGRVAL.PUB.SYS (NMGRERR 116)
CAUSE Internal erorr.
ACTION Contact your Hewlett-Packard representative.
--------------------------------------------------------------------------
NMGRERR 117 MESSAGE Cannot receive mail from validation program
(NMGRERR 117)
CAUSE Internal error.
ACTION Contact your Hewlett-Packard representative.
--------------------------------------------------------------------------
NMGRERR 118 MESSAGE Duplicate LU Numbers on page 1 or page 2.
(NMGRERR 118)
CAUSE The user entered two LU's with the same LU
Numbers. The duplicate numbers may be on the
same page of LU data, or one may be on page 1 of
LU data and the other on page 2 of LU data.
ACTION Make sure all LU's have unique numbers.
--------------------------------------------------------------------------
NMGRERR 119 MESSAGE Duplicate LU names on page 1 or page 2.
(NMMGRERR 119)
CAUSE You have entered two LUs with the same LU name.
These names may be on the same page (1 or 2) of
LU data, or one name may be on page 1 and the
other on page 2.
ACTION Make sure all LUs have unique names.
--------------------------------------------------------------------------
NMGRERR 120 MESSAGE LU Numbers must be 1-255. (NMGRERR 120)
CAUSE The user entered an LU Number out of the
acceptable range of 1-255.
ACTION Enter an LU Number that is in the range 1-255.
--------------------------------------------------------------------------
NMGRERR 121 MESSAGE IP Address with node portion of zeroes is
reserved for broadcast (NMGRERR 121)
CAUSE You entered an IP address with the node portion
of the IP address equal to zero.
ACTION Modify the node portion of the IP address to a
valid IP address.
--------------------------------------------------------------------------
NMGRERR 122 MESSAGE LU Name must be a letter followed by letters or
digits. (NMGRERR 122)
CAUSE The user entered a string that contained some
non alpha-numeric characters.
ACTION Re-enter the string with alpha-numeric
characters only.
--------------------------------------------------------------------------
NMGRERR 123 MESSAGE IP Mask can only contain digits separated by
periods or spaces. (NMGRERR 123)
CAUSE The IP mask was entered incorrectly. Each octet
(XXX) can only contain digits. The octets can
be separated by periods or blank spaces.
ACTION Enter a mask in the correct format.
--------------------------------------------------------------------------
NMGRERR 124 MESSAGE IP Mask octets can only contain values between 0
and 255. (NMGRERR 124)
CAUSE One or more of the octets entered in the IP mask
contains a number less than 0 or greater than
255.
ACTION Enter a mask with octets within the range 0 to
255.
--------------------------------------------------------------------------
NMGRERR 125 MESSAGE IP Mask must contain exactly four octets.
(NMGRERR 125)
CAUSE More or less than four octets (XXX) were
entered.
ACTION Re-enter the mask with exactly four octets.
--------------------------------------------------------------------------
NMGRERR 126 MESSAGE IP Subnet Mask of 255.255.255 is not allowed.
(NMGRERR 126)
CAUSE An IP Subnet Mask of 255.255.255 was entered.
This is not a legal mask.
ACTION Re-enter the mask with a different value.
--------------------------------------------------------------------------
NMGRERR 127 MESSAGE The LU Numbers must be blank. (NMGRERR 127)
CAUSE If the PU Type is 2.1 and the PU Dependent
Support is N, then there cannot be any LU
Numbers associated with the LU names.
ACTION Make all the LU Numbers blank and try again.
--------------------------------------------------------------------------
NMGRERR 128 MESSAGE Invalid SNA LU Name Format. Must be
XXXXXXXX.XXXXXXXX. (NMGRERR 128)
CAUSE The user entered an invalid SNA LU name. The
SNA LU Name must be in the format of
AXXXXXXX.AXXXXXXX, where A is any alpha
character and X in any alphanumeric character.
ACTION Re-enter SNA LU name in the correct format and
try again.
--------------------------------------------------------------------------
NMGRERR 130 MESSAGE No previous page. (NMGRERR 130)
CAUSE The user pressed the PREV PAGE function key on a
paged data screen and there was no previous page
of data.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 131 MESSAGE Invalid IP Address Class Type; press Help for
more information. (NMGRERR 131)
CAUSE The class of the IP address that the user
entered was not a valid class.
ACTION Enter an IP address with a valid class; A, B, C,
or E are accepted. (Press the Help key for more
information on entering a valid IP address.)
--------------------------------------------------------------------------
NMGRERR 132 MESSAGE Invalid IP Network Address Number; press Help
for info. (NMGRERR 132)
CAUSE The network number portion of the IP address is
not valid with the given IP class. The valid
network address numbers are:
Class Range
A 001 000.000.001 - 127 255.255.255
B 128.001 000.001 - 191.255 255.255
C 192.000.001 001 - 223.255.255 255
D 224.000.000.000 - 255.255.255.255
ACTION Enter a valid IP address. (Press the Help key
for more information on entering a valid IP
address.)
--------------------------------------------------------------------------
NMGRERR 133 MESSAGE Invalid Node Address; press Help for information
(NMGRERR 133)
CAUSE The node portion of the IP address is invalid.
Each octet (group of three digits) must be in
the range of 1 - 255.
ACTION Enter a valid IP address. (Press the Help key
for more information on entering a valid IP
address.)
--------------------------------------------------------------------------
NMGRERR 134 MESSAGE IP Address with node portion of zeros is
reserved. (NMGRERR 134)
CAUSE The node portion of the IP address is all zeros.
ACTION Check the IP address and make sure that the node
portion is not all zeros. Enter a valid IP
address. (Press the Help key for more
information on entering a valid IP address.)
--------------------------------------------------------------------------
NMGRERR 135 MESSAGE IP Address with network portion of zeros is
reserved. (NMGRERR 135)
CAUSE The network portion of the IP address is all
zeros.
ACTION Check the IP address and make sure that the
network portion is not all zeros. Enter a valid
IP address. (Press the Help key for more
information on entering a valid IP address.)
--------------------------------------------------------------------------
NMGRERR 136 MESSAGE IP Address A 127 XXX.XXX.XXX is reserved for
Loopback. (NMGRERR 136)
CAUSE The IP address entered has a network address of
127. This network address with any node address
is reserved for loopback.
ACTION Check the IP address and make sure that the
network address is not 127. Enter a valid IP
address. (Press the Help key for more
information on entering a valid IP address.)
--------------------------------------------------------------------------
NMGRERR 137 MESSAGE IP Address E 255.255.255.255 is reserved for
Broadcast. (NMGRERR 137)
CAUSE The IP address the user entered is a reserved
address.
ACTION Enter a different IP address. (Press the Help
key for more information on entering a valid IP
address.)
--------------------------------------------------------------------------
NMGRERR 138 MESSAGE Bad LAN address. Format is xx-xx-xx-xx-xx-xx; x
is 0-9 or A-F. (NMGRERR 138)
CAUSE The user entered an invalid LAN address on a
screen or in a maintenance mode command.
ACTION Correct the LAN address and repeat the last
command or action. (Press the Help key for more
information on entering a valid LAN address.)
--------------------------------------------------------------------------
NMGRERR 140 MESSAGE SNA/DS not validated. Type exit again to leave
NMMGR. (NMGRERR 140)
CAUSE Data in the SNA.DS subsystem was changed and
SNA/DS was not successfully validated
afterwords.
ACTION Go to the validation screen and validate SNA/DS
or type exit again to leave the file
unvalidated.
--------------------------------------------------------------------------