HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd)
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 Service Request.
See "Submitting an SR" 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.
--------------------------------------------------------------------------
NMGRERR 42 MESSAGE Internal error: Unexpected screen contents.
(NMGRERR 42)
CAUSE This is an internal NMMGR error. NMMGR has
encountered unexpected data from the screen.
ACTION Check to see that the correct version of NMMGR
is installed. See "Submitting an SR" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 43 MESSAGE Internal error: Unexpected data record length.
(NMGRERR 43)
CAUSE This is an internal NMMGR error. NMMGR cannot
properly create a data record from the input
from the screen.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 44 MESSAGE Internal error: Unexpected data record
contents.
(NMGRERR 44)
CAUSE NMMGR cannot properly display a data field in
the configuration file on the screen. The
configuration file is corrupted.
ACTION Restore a back-up copy of the configuration file
if possible.
--------------------------------------------------------------------------
NMGRERR 45 MESSAGE Internal error: Unexpected status code from
procedure. (NMGRERR 45)
CAUSE This is an internal NMMGR error. An unknown
status code is returned from a procedure.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 46 MESSAGE Specified path is not in this configuration
file.
(NMGRERR 46)
CAUSE The user has entered a path name in the command
field that is not in the configuration file.
ACTION Check the path name entered and try again.
--------------------------------------------------------------------------
NMGRERR 47 MESSAGE Internal error: No child with this type is in
schema. (NMGRERR 47)
CAUSE This is an internal NMMGR error. NMMGR cannot
match a path name and a type code to an internal
table.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 48 MESSAGE Internal error: Can't find this path in the
schema. (NMGRERR 48)
CAUSE This is an internal NMMGR error. NMMGR cannot
match a path name to an internal table.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 49 MESSAGE Internal error: The root node has parent node.
(NMGRERR 49)
CAUSE This is an NMMGR internal error. NMMGR is
scanning the configuration file off the
boundary.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 50 MESSAGE Internal error: The schema has an invalid
format.
(NMGRERR 50)
CAUSE This is an internal NMMGR error. NMMGR cannot
locate a node in an internal table describing
the configuration file structure.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 51 MESSAGE No screen for this path. (NMGRERR 51)
CAUSE There is no screen to display that is associated
with this path name. A path exists in the
configuration file but is not recognized by
NMMGR.
ACTION This path is for internal use only. Check the
pathname and try again.
--------------------------------------------------------------------------
NMGRERR 52 MESSAGE Internal error: Cannot create version stamps.
(NMGRERR 52)
CAUSE NMMGR creates version stamps for each subsystem
in configuration file at file creation time, and
in some cases at file open time. This is an
internal NMMGR error. NMMGR cannot create
version stamps in the configuration file due to
an NMCONF error. Check the NMCONF error number
for detail.
ACTION Purge this new file and try to recreate it. If
an error still occurs, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 53 MESSAGE Version mismatch found on specified subsystem.
Please run NMMGRVER. (NMGRERR 53)
CAUSE NMMGR checks version stamps of each subsystem in
the configuration file at file open time.
Version checking results show that there is
configuration data for at least one subsystem in
the configuration file that is not supported by
this version of NMMGR.
ACTION Run the version control program NMMGRVER to
update the file, or open another file, or create
a new file.
--------------------------------------------------------------------------
NMGRERR 54 MESSAGE Internal error: Version checking routine
failed. (NMMGRERR54)
CAUSE NMMGR checks version stamps of each subsystem in
the configuration file at file open time. An
error has occurred in the version checking
routine. The configuration file may have
corrupt data records or invalid paths.
ACTION Restore a back-up copy of the configuration file
if possible.
--------------------------------------------------------------------------
NMGRERR 55 MESSAGE Internal error: Version-flag checking failed.
(NMGRERR 55)
CAUSE An internal NMMGR error has occurred: unable to
get vsflag status. The possible causes include:
internal error in vsflag_check_driver, or the
parameters file_num, file_type_column, or
vsflag_path do not match those stored in vsflag
array at open time.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 56 MESSAGE Version mismatch found on specified subsystem.
(NMGRERR 56)
CAUSE NMMGR checks version stamps of each subsystem in
the configuration file at accessing time. The
version checking result shows that the specified
subsystem has a mismatched version stamp in the
configuration file that is not supported by this
version of NMMGR.
ACTION Since this version stamp is greater than what
NMMGR supports, use NMMGR to create a new file.
In this case, the NMMGRVER conversion utility
will not help.
--------------------------------------------------------------------------
NMGRERR 70 MESSAGE Internal error: Unable to get info on VPLUS
screen field. (NMGRERR 70)
CAUSE NMMGR was unable to retrieve information on the
screen field via VPLUS utilities.
ACTION Go to the Errors screen and check the VPLUS
error message to determine the specific error.
Correct the error and try again.
CAUSE NMMGR was unable to retrieve information on the
screen field via VPLUS utilities. The forms
file NMMGRF.PUB.SYS and NMMGR are different
versions, or the forms file is corrupt.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 71 MESSAGE Internal error: Unable to get info on VPLUS
form.
(NMGRERR 71)
CAUSE NMMGR was unable to retrieve information on the
screen field via VPLUS utilities.
ACTION Go to the Errors screen and check the VPLUS
error message to determine the specific error.
Correct the error and try again.
CAUSE NMMGR was unable to retrieve information on the
screen field via VPLUS utilities. The forms
file NMMGRF.PUB.SYS and NMMGR are different
versioms, or the forms file is corrupt.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 72 MESSAGE Internal error: Data field alignment error.
(NMGRERR 72)
CAUSE This is an NMMGR internal conversion table
error.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 73 MESSAGE Internal error: Data field extraction is out of
bounds. (NMGRERR 73)
CAUSE This is an NMMGR internal conversion table
error. NMMGR cannot locate data for a field to
display on this screen.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 74 MESSAGE Internal error: Conversion code not yet
implemented. (NMGRERR 74)
CAUSE This is an NMMGR internal conversion table
error. NMMGR encountered an unknown conversion
code.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 75 MESSAGE Internal error: String overflow. (NMGRERR 75)
CAUSE This is an internal NMMGR error. A character
string passed to one of the conversion routines
is too long.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 76 MESSAGE Internal error: Screen conversion ptr is out of
bounds. (NMGRERR 76)
CAUSE This is an internal NMMGR error.
ACTION Go to the Errors screen and check for a VPLUS
error message to determine the specific error.
Correct any errors and try again.
CAUSE This is an internal NMMGR error. The forms file
NMMGRF.PUB.SYS and NMMGR are not the same
version, or the forms file is corrupt.
ACTION Restore a back-up copy of NMMGRF.PUB.SYS.
--------------------------------------------------------------------------
NMGRERR 77 MESSAGE Internal error: Data conversion ptr is out of
bounds. (NMGRERR 77)
CAUSE This is an internal NMMGR conversion table
error.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 78 MESSAGE Internal error: Missing description for this
screen. (NMGRERR 78)
CAUSE This is an NMMGR internal table error. The
screen name is not in an internal conversion
table.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 79 MESSAGE Internal error: Invalid scr field position from
VPLUS. (NMGRERR 79)
CAUSE This is an internal NMMGR error. NMMGR cannot
properly locate field data from this screen.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 80 MESSAGE Internal error: Data field not on proper unit
boundry. (NMGRERR 80)
CAUSE This is an internal NMGRR conversion table
error.
ACTION Submit a Service Request. See "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 81 MESSAGE Cannot lock NM configuration file. (NMGRERR 81)
CAUSE NMMGR was unable to successfully lock the
configuration file.
ACTION Go to the Errors screen and check for any NMERR
or FSERR error messages to determine the
specific error. Correct the error and try
again. If necessary, submit a Service Request.
See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 82 MESSAGE Cannot unlock NM configuration file. (NMGRERR
82)
CAUSE NMMGR was unable to successfully unlock the
configuration file.
ACTION Go to the Errors screen and check for any NMERR
or FSERR error messages to determine the
specific error. Correct the error and try
again. If necessary, submit a Service Request.
See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 83 MESSAGE Press Delete again to confirm deletion.
CAUSE The Delete key needs to be pressed twice to
accomplish the deletion.
ACTION Press the Delete key a second time to confirm
the deletion.
--------------------------------------------------------------------------
NMGRERR 84 MESSAGE Cannot access the NMMGR help catalog. (NMGRERR
84)
CAUSE NMMGR was unable to open the NMMGR help catalog,
NMMGRHLP.PUB.SYS.
ACTION Restore the NMMGR help catalog.
--------------------------------------------------------------------------
NMGRERR 85 MESSAGE Incomplete summary printed. (NMGRERR 85)
CAUSE Some configuration data could not be found or
printed in the summary.
ACTION Check the summary to ensure that all required
fields are configured.
CAUSE The data that could not be found or printed is
replaced with asterisks in the summary printout.
ACTION Check the summary to ensure that all required
fields are configured.
--------------------------------------------------------------------------
NMGRERR 86 MESSAGE Cannot invoke subsystem summary routine.
(NMGRERR 86)
CAUSE The subsystem summary output routine cannot be
load processed from the group, account, or
system SL.
ACTION Stream the install job I00INMAC.NMA.HPPL87 to
add the routine to system SL.
--------------------------------------------------------------------------
NMGRERR 87 MESSAGE DTS/LINK not validated. Type exit again to
leave NMMGR. (NMGRERR 87)
CAUSE Data in the DTS or LINK subsystem was changed
and DTS/LINK was not successfully validated
afterwards.
ACTION The user can go to the validation screen and
validate DTS/LINK or the user can type exit
again and leave the file unvalidated.
--------------------------------------------------------------------------
NMGRERR 88 MESSAGE Error in NMMGR help catalog. (NMGRERR 88)
CAUSE The MPE HELP subsystem could not use the help
file NMMGRHLP.PUB.SYS.
ACTION Make sure that the file NMMGRHLP.PUB.SYS is
properly formatted (RUN MAKECAT.PUB.SYS,HELP).
CAUSE The MPE HELP subsystem could not use the help
file NMMGRHLP.PUB.SYS.
ACTION RESTORE the file NMMGRHLP.PUB.SYS.
--------------------------------------------------------------------------
NMGRERR 90 MESSAGE Invalid IP Address; press Help for more
information. (NMGRERR 90)
CAUSE The user entered an IP address that failed IP
address edits (address was invalid).
ACTION Enter a valid IP address; check the class letter
(A, B, C, or E accepted). (Press the Help key
for more information on entering a valid IP
address.)
--------------------------------------------------------------------------
NMGRERR 91 MESSAGE Must be xx-xx-xx-xx-xx-xx where x is a hex
number. (NMGRERR 91)
CAUSE The user entered a LAN station address that
failed station address edits (address was
invalid).
ACTION Enter a valid LAN station address; must be six
pairs of hex digits. (Press the Help key for
more information on entering a valid LAN station
address.)
--------------------------------------------------------------------------
NMGRERR 92 MESSAGE Reachable Net IP Addr can't be the same as the
Gateway IP Addr. (NMGRERR 92)
CAUSE A reachable network IP address is the same as
the gateway IP address. The network portion of
these addresses must be different.
ACTION Correct either the reachable network IP address
or the gateway IP address and re-enter.
--------------------------------------------------------------------------
NMGRERR 93 MESSAGE Enter the required Reachable Net IP Address with
Hops. (NMGRERR 93)
CAUSE User attempted to update information without
entering required data. At least one Reachable
Net IP Address/Hop pair is required on page 1 of
the Reachable Networks screen.
ACTION Enter the required information and continue.
--------------------------------------------------------------------------
NMGRERR 94 MESSAGE Maximum page count exceeded. (NMGRERR 94)
CAUSE User attempted to go to next page at the maximum
page count (256).
ACTION Use CONDENSE PAGE.
CAUSE User attempted to do "LAST PAGE" or "CONDENSE
PAGE". The configuration file may have
Reachable Network paths in excess of 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.
--------------------------------------------------------------------------