HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd)
NMGRERR 141 MESSAGE Subsystem(s) are not validated. Type ERR for
more information. (NMGRERR 141)
CAUSE One or more of the subsystems in NMMGR have not
been validated.
ACTION To see which subsystems have not been validated,
type ERRORS in the command line and press the
Enter key. Go to the validation screen to
validate the unvalidated subsystems or type exit
again to leave the file unvalidated.
--------------------------------------------------------------------------
NMGRERR 200 MESSAGE Error in build statement table. (NMGRERR 200)
CAUSE This is an internal NMMGR error. The number of
statements in an internal table does not match
the number expected by NMMGR.
ACTION Restore the file NMMGRCAT.PUB.SYS. Then run
NMMAINT.PUB.SYS to make sure the version of
NMMGR is correct.
--------------------------------------------------------------------------
NMGRERR 201 MESSAGE Internal error in Guided config scanner.
(NMGRERR 201)
CAUSE This is an internal guided configuration error
caused by a corrupt NMMGRCAT.PUB.SYS file.
CAUSE Restore NMMGRCAT and retry. If this fails see
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 202 MESSAGE Aux NMCONF file already open. (NMGRERR 202)
CAUSE This is an internal guided configuration error
caused when more than one NMCONF file is opened
by the guided configuration open statement.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 203 MESSAGE Cannot open source, destination, or Aux NMCONF
file. (NMGRERR 203)
CAUSE This is caused when the source/destination file
or the file NMAUX1.PUB.SYS is either missing, is
the wrong version, is locked for exclusive
access, or was corrupted during a subtree copy.
ACTION If doing a subtree copy, check to see that the
source and destination files really exist. If
performing a guided configuration task, copy
NMAUX1.PUB.SYS from backup tape, and run
NMMAINT.PUB.SYS to make sure that you have the
correct version.
--------------------------------------------------------------------------
NMGRERR 204 MESSAGE Aux NMCONF file not opened. (NMGRERR 204)
CAUSE This is an internal guided configuration error
caused when data is copied from the auxiliary
file to the user file and the auxiliary file was
not opened.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 205 MESSAGE Aux file does not contain specified path.
(NMGRERR 205)
CAUSE This is a guided configuration error caused when
NMMGRCAT specifies a path in the auxiliary file
that does not exist.
ACTION Copy NMAUX1.PUB.SYS from back-up tape, and run
NMAINT.PUB.SYS to make sure that the version of
NMAUX1 is the same as the version of NMMGR.
--------------------------------------------------------------------------
NMGRERR 206 MESSAGE Path to subtree in user file does not exist.
(NMGRERR 206)
CAUSE This problem could be caused by a corrupt file
or by an old configuration file that needs to be
updated.
ACTION Run NMMGRVER.PUB.SYS. If needed, restore a known
good configuration file from a back-up tape, or
create a new configuration file with NMMGR.
--------------------------------------------------------------------------
NMGRERR 207 MESSAGE Internal error; Guided token overflow. (NMGRERR
207)
CAUSE This is an internal guided configuration error.
ACTION Restore NMMGRCAT.PUB.SYS from a back-up tape.
If this fails see "Submitting an SR" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 208 MESSAGE Unexpected Guided Config error. Type ERRORS.
(NMGRERR 208)
CAUSE An unexpected or internal guided configuration
error occurred.
ACTION Type the "ERROR" command after this message is
displayed for clarification of the error(s). A
PC value is specified at the end of this error
message. If you are unable to include the value
problem, submit an SR. See "Submitting an SR" at
the beginning of this appendix. Be sure to
include the value of the PC with the SR.
--------------------------------------------------------------------------
NMGRERR 209 MESSAGE Cannot Stop Guided Configuration. (NMGRERR 209)
CAUSE The STOP command is allowed only on screens
which contain a "path." This is most likely to
occur when the user types the command "STOP" on
the errors screen during guided configuration.
ACTION Move to a screen which contains a "path" at the
top of the menu and retype the stop command.
--------------------------------------------------------------------------
NMGRERR 211 MESSAGE Cannot perform NEXT function. (NMGRERR 211)
CAUSE This error occurs when the user attempts to use
the NEXT command when no selection screen has
been encountered.
ACTION There is no need to use this function at this
time.
--------------------------------------------------------------------------
NMGRERR 214 MESSAGE Function is not allowed during Guided
configuration. (NMGRERR 214)
CAUSE The user has pressed a function key that is not
allowed during guided configuration. If the
user is on a data screen, it is possible to
advance by pressing the Update function key.
ACTION Press a labeled function key.
--------------------------------------------------------------------------
NMGRERR 215 MESSAGE Illegal vplus field specified in Guided config.
(NMGRERR 215)
CAUSE This is an internal guided configuration error
that is caused by missing information in the
forms file.
ACTION Restore NMMGRF.PUB.SYS from back-up tape, and
run NMMAINT.PUB.SYS. If this fails see
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 216 MESSAGE Illegal Guided config variable name. (NMGRERR
216)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 217 MESSAGE Illegal path iden name in Guided config.
(NMGRERR 217)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 218 MESSAGE Max num of items that can be put to a screen
exceeded. (NMGRERR 218)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 219 MESSAGE String overflow. (NMGRERR 219)
CAUSE This is an internal guided configuration error.
ACTION Restore NMMGRCAT.PUB.SYS from a back-up tape.
If this fails see "Submitting an SR" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 220 MESSAGE Boolean logic error. (NMGRERR 220)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 221 MESSAGE Missing ENDIF statement. (NMGRERR 221)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 222 MESSAGE Select loops nested too deep. (NMGRERR 222)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 223 MESSAGE Select stack underflow probably missing SELECT.
(NMGRERR 223)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 224 MESSAGE Missing ENDSELECT statement. (NMGRERR 224)
CAUSE This is an internal guided configuration error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 226 MESSAGE Unknown statement in Guided Configuration
driver. (NMGRERR 226)
CAUSE This is an internal guided configuration error.
ACTION Restore NMMGRCAT.PUB.SYS from back-up tape. If
this fails see "Submitting an SR" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 227 MESSAGE Command not allowed on error or version screen.
(NMGRERR 227)
CAUSE Certain commands are only allowed on states
which contain a path. This is likely to occur
when the user types STOP on the errors screen or
the version screen during guided configuration.
ACTION Move to a state which contains a path and retype
the stop command.
--------------------------------------------------------------------------
NMGRERR 228 MESSAGE The network interface data and the topology key
must match. (NMGRERR 228)
CAUSE The type of the network interface does not match
the topology key which you selected.
ACTION Make sure you pressed the correct topology key
and have the correct network interface name.
Check the type of the network interface name by
going to NEXPORT.NI (do a direct branch).
--------------------------------------------------------------------------
NMMGRERR 229 MESSAGE The Network interface is not allowed to have
mapping data updated.(NMGRERR 229).
CAUSE The Network Interface must be of type router.
ACTION Check the type of the network interface name by
going to NETXPORT.NI (do a direct branch).
--------------------------------------------------------------------------
NMGRERR 230 MESSAGE The Network interface may not be of type
LOOPBACK. (NMGRERR 230)
CAUSE There is no Internet data to configure under the
loopback network interface.
ACTION Do not use this function with loopback.
--------------------------------------------------------------------------
NMGRERR 231 MESSAGE No network interface found, or unknown type.
(NMGRERR 231)
CAUSE You may have spelled the name incorrectly.
ACTION Check the spelling and reenter.
CAUSE The type may be unknown.
ACTION Check the type of the network interface name by
going to NETXPORT.NI (do a direct branch). File
an SR if the type is labeled as UNKNOWN. (See
"Submitting an SR" at the beginning of this
appendix). Delete the unknown type and retry.
--------------------------------------------------------------------------
NMGRERR 232 MESSAGE Unable to open source NMCONF file for copy.
(NMGRERR 232)
CAUSE File does not exist or is the wrong version.
ACTION If in guided configuration, then NMAUXI.PUB.SYS
could not be opened. If performing a copy
subtree, check the source file to make sure it
exists and is the correct version.
--------------------------------------------------------------------------
NMGRERR 233 MESSAGE Unable to open destination NMCONF file for copy.
(NMGRERR 233)
CAUSE File does not exist or is the wrong version.
ACTION If in guided configuration, then
NMCONFIG.PUB.SYS or the user file does not
exist, or is corrupt. You may check the version
by running NMMAINT.PUB.SYS. You may also run
NMMGRVER to determine if your file is corrupt.
If performing a copy subtree, check the
destination file to make sure it exists. Check
the version and check to see if the file is
corrupt (as above).
--------------------------------------------------------------------------
NMMGRERR 234 MESSAGE No PC return value is on the Gosub stack.
(NMGRERR 234)
CAUSE There is an internal G-code error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 235 MESSAGE Illegal PC value specified in statement.
(NMGRERR 235)
CAUSE There is an internal G-code error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 236 MESSAGE The Gosub stack is full. (NMGRERR 236)
CAUSE There is an internal G-code error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 237 MESSAGE The Network interface must be of type X.25.
(NMGRERR 237)
CAUSE The operation is illegal if the NI is not an
X.25 link.
ACTION Check to make sure that the NI is an X.25 link.
--------------------------------------------------------------------------
NMGRERR 240 MESSAGE Data must be entered and Updated before
continuing. (NMGRERR 240)
CAUSE While running guided configuration, the user
tried to press Next Screen without first
pressing Update Data while at the path
SNANODE.nodename.
ACTION Enter the correct data and press Update Data.
--------------------------------------------------------------------------
NMGRERR 250 MESSAGE The NI Name must be specified. (NMGRERR 250)
CAUSE At the Guided HP Configuration screen, the user
attempted to fine tune the parameters for an NI
configuration without specifying the NI name in
the NI Name field.
ACTION Enter a valid NI name in the NI Name field and
press the FineTune Parms key again.
--------------------------------------------------------------------------
NMGRERR 251 MESSAGE The NI Name does not exist in the configuration
file. (NMGRERR 251)
CAUSE The user attempted to perform an operation on an
non-existent NI. Either the NI is not configured
or the specified NI name is incorrect.
ACTION Specify the correct NI name of a configured NI
and try again.
--------------------------------------------------------------------------
NMGRERR 253 MESSAGE The NI name already exists and is of another
type. (NMGRERR 253)
CAUSE The user attempted to create an NI using an NI
name that has already been configured for
another NI of a different type.
ACTION Specify an NI name that has not already been
used and try again.
--------------------------------------------------------------------------
NMGRERR 254 MESSAGE This link name is used by another NI; select
another name. (NMGRERR 254)
CAUSE While configuring an NI, the user specified a
link name that has already been configured for a
different NI and cannot be shared.
ACTION Specify a different link name and try again.
--------------------------------------------------------------------------
NMGRERR 255 MESSAGE A link name must be entered. (NMGRERR 255)
CAUSE The user attempted to update the configuration
file without specifying a link name, which is
required for this screen.
ACTION Enter a link name in the Link name field and try
again.
--------------------------------------------------------------------------
NMGRERR 256 MESSAGE This link cannot be renamed. It is used by
another NI.(NMGRERR 256)
CAUSE The user attempted to change the name of a link
that is used by more than one NI.
ACTION Leave the link name as it is or reconfigure one
or the other of the NIs to use a different link.
--------------------------------------------------------------------------
NMGRERR 257 MESSAGE The NI name does not exist. Please specify a
type to create it. (NMGRERR 257)
CAUSE At the Guided HP Configuration screen, the user
entered a new NI name and pressed the Config
Network key without specifying a type in the NI
type field. The type must be specified if the
NI does not already exist.
ACTION If you are configuring a new NI, enter the type
of the new NI in the NI type field and press
Config Network. If you are updating an existing
NI and entered the wrong name in the NI name
field, enter the correct NI name and press
Config Network.
--------------------------------------------------------------------------
NMGRERR 258 MESSAGE Data saved, but profile doesn't exist. Use
GoToProfiles command to create it. (NMGRERR
258)
CAUSE At the DTS Configuration screen or at one of the
DTC card configuration screens, the user
specified the name of a profile that is not
configured and then pressed the save data key.
ACTION Press the Go To Profiles key if one exists for
the screen. If not, type GoToProfiles in the
command line and press Enter. This will take
you to the profile configuration screens.
Configure the nonexisting profile(s) and save
the information in the configuration file. When
you are finished, press the Prior Screen key
until NMMGR returns you to the screen you were
at when you originally entered the nonexisting
profile name. There is no need to re-enter the
data on this screen, since it has already been
saved. Continue with the next configuration
task.
--------------------------------------------------------------------------
NMGRERR 259 MESSAGE A DTC name must be specified. (NMGRERR 259)
CAUSE At the DTC Configuration screen, the user
pressed the Read DTC function key without
specifying a DTC name.
ACTION Enter a valid DTC name and try again.
--------------------------------------------------------------------------
NMGRERR 260 MESSAGE The DTC name does not exist; enter data and
press Save Data to create it. (NMGRERR 260)
CAUSE At the DTC Configuration screen, the user
specified a nonexisting DTC name and pressed
either the Config Card key or the Read DTC key.
ACTION If an incorrect DTC name was entered, enter the
correct DTC name and try again. If the DTC name
is correct but the DTC has not yet been
configured, enter the information for the DTC
and press the Save Data key, then try again.
--------------------------------------------------------------------------
NMGRERR 261 MESSAGE The DTS Link does not exist. Enter a Link name
and press Save Data. (NMGRERR 261)
CAUSE At the DTS Configuration screen, the user
entered a nonexisting link name and pressed the
Tune DTS Link key.
ACTION If an incorrect link name was entered, enter the
correct link name and try again. If the link
name is correct but the link has not yet been
configured, enter the information for the link
and press the Save Data key, then try again.
--------------------------------------------------------------------------