HP 3000 Manuals HP 3000 Manuals
NMERR Messages (contd.)
NMERR 101 MESSAGE Fix levels differ in one or more modules.
(NMERR 101)
CAUSE There is a version mismatch between the various
modules of the subsystem. Incorrect
installation of the subsystem software.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 102 MESSAGE Update levels differ in one or more modules.
(NMERR 102)
CAUSE There is a version mismatch between the various
modules of the subsystem. Incorrect
installation of the subsystem software.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 103 MESSAGE Version levels differ in one or more modules.
(NMERR 103)
CAUSE There is a version mismatch between the various
modules of the subsystem. Incorrect
installation of the subsystem.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 104 MESSAGE One or more subsystem modules are missing.
(NMERR 104)
CAUSE A module required for normal operation of the
subsystem is missing.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 105 MESSAGE One or more subsystem modules are invalid.
(NMERR 105)
CAUSE An error has occurred trying to read the version
ID of one or more of the subsystem's modules.
An I/O error, disc error, or similar has
prevented reading the version stamp correctly.
ACTION Correct this problem and retry. If necessary
see "Invalid Software Installation" at the
beginning of this appendix.
CAUSE Some of the program files and data files have
the version stamp located in the last user label
record. Perhaps the file was copied without
copying its user label records properly.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 106 MESSAGE MODULE FLAGS parameter invalid.
CAUSE The MODULE FLAGS MODE field (bits 7:6) is not in
the range 0 to 5, or the TYPE field (bits 13:3)
is not in the range 0 to 2. Returned by
NMSUBSYSVERS, SUBSYSOVERS, and other subsystem
level 2 version check procedures. Probable
internal error by caller.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 107 MESSAGE FLAGS options are incompatible.
CAUSE Some mutually incompatible option bits were set
in the FLAGS parameter. Returned by
NMSUBSYSVERS, SUBSYSOVERS, and other subsystem
level 2 version check procedures.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 130 MESSAGE Unable to create the link manager process.
(NMERR 130)
CAUSE A non-zero result code was returned by
NMMONSTARTREQ to NMOPENLINK.
Returned by NMOPENLINK. Loader error trying to
load LINKMGR.PUB.SYS program file.
ACTION Try to ALLOCATE LINKMGR.PUB.SYS. If this fails,
correct the problem according to the error
messages given. If this succeeds, retry the
action that led to the problem. If this error
occurs again, this is not the problem.
CAUSE Out of MPE resources.
ACTION See "Insufficient MPE Resources" at the
beginning of this appendix.
CAUSE A non-zero result code was returned by
NMMONSTARTREQ to NMOPENLINK. Returned by
NMOPENLINK. Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 131 MESSAGE Invalid item detected in configuration record.
(NMERR 131)
CAUSE Error reading and/or interpreting data from
configuration file. Returned by NMOPENLINK.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 132 MESSAGE Link in exclusive use by another subsystem.
(NMERR 132)
CAUSE Link has already been opened by another process.
Returned by NMOPENLINK. Another process has this
link opened.
ACTION Shut down the other process to free the link.
CAUSE A LINKMGR process which had this link previously
did not close it when expected. This is an
internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix. If possible, include a memory dump
with the SR.
--------------------------------------------------------------------------
NMERR 133 MESSAGE Start param length error in Link Manager.
(NMERR 133)
CAUSE Either a software version mismatch, or an
internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 134 MESSAGE A successful NMOPENLINK for this link must occur
before executing this function. (NMERR 134)
CAUSE NMOPENLINK has not yet been called successfully.
Returned by NMCLOSELINK, NMMANAGELINK,
NMLINKINFO, and NMLINKDIAL. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 135 MESSAGE Required items missing in configuration record.
(NMERR 135)
CAUSE Error reading data from configuration file.
Returned by NMOPENLINK. Configuration file is
not valid.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 136 MESSAGE Parameter information exceeds permissible
length. (NMERR 136)
CAUSE Information buffer given by caller exceeds 128
words in length. Returned by NMMANAGELINK and
NMLINKDIAL. This is usually an internal error in
the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 137 MESSAGE A successful NMOPENLINK for this link must occur
before executing this function. (NMERR 137)
CAUSE NMOPENLINK has not been executed successfully
for this link. Returned by NMCLOSELINK,
NMMANAGELINK, NMLINKINFO and NMLINKDIAL This is
usually an internal error in the calling
subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NNMERR 138 MESSAGE Unable to find DC/LDM in system I/O tables.
(NMERR 138)
CAUSE The NSLINK ldev was not configured for the link
in NMCONFIG.PUB.SYS when the system was started.
ACTION Ensure the NSLINK ldev is configured for the
link used by NS, and re-boot. More information
may be found in the NMLG log file.
--------------------------------------------------------------------------
NMERR 139 MESSAGE Unable to find the specified linkname in system
I/O tables. (NMERR 139)
CAUSE The specified linkname is not configured in the
LINK subtree of the configuration file.
ACTION Check that the linkname specified to the
subsystem has a matching linkname configured
under the LINK configuration subtree.
--------------------------------------------------------------------------
NMERR 142 MESSAGE Status request to communication board failed.
(NMERR 142)
CAUSE Call to procedure TRAN'GETINFO failed. Returned
by NMLINKINFO and LINKCONTROL. Bad software
installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 146 MESSAGE User specified buffer inadequate for request.
(NMERR 146)
CAUSE Caller did not supply a buffer large enough for
returned data. Returned by NMLINKINFO. Bad
software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 147 MESSAGE Link manager buffer area inadequate for request.
(NMERR 147)
CAUSE Link Manager's internal buffer is not large
enough to handle this request. Returned by
NMLINKINFO. Bad software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 148 MESSAGE Specified item code is out of range. (NMERR
148)
CAUSE No information item corresponds to the given
item code. Returned by NMLINKINFO. Bad software
installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 149 MESSAGE Dial request to communications board failed.
(NMERR 149)
CAUSE Error calling procedure TRAN'CONFIGDIAL.
Returned by NMLINKDIAL. Bad software
installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 154 MESSAGE Dial facility is not supported. (NMERR 154)
CAUSE Call to LINKDIALREQ failed. Returned by
NMLINKDIAL. Bad software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 155 MESSAGE Multicast address downloading is not supported.
(NMERR 155)
CAUSE Call to NMLINKDOWNMC is not supported. Bad
software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 156 MESSAGE This NMLINK intrinsic is not supported under
HPE. (NMERR 156)
CAUSE Bad software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 157 MESSAGE DS/LDM open request failed. (NMERR 157)
CAUSE The request to open the DC/LDM failed. Returned
by NMOPENLINK. Bad software installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMMER 158 MESSAGE DS/LDM close request failed. (NMERR 158)
CAUSE The request to close the DC/LDM failed.
Returned by NMCLOSELINK. Bad software
installation.
ACTION Make sure that the versions of NMS software and
port translator software are compatible. See
"Invalid Software Installation" at the beginning
of this appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 159 MESSAGE Unable to allocate device. (NMERR 159)
CAUSE Either the ldev does not exist, or is the wrong
type or subtype, or some other problem caused
ALLOCATE or GETDEVINFO to fail. Returned by
NMOPENLINK .
ACTION Check NM log entry. If status is betwen -3 and
10, the status is from ALLOCATE. If it is
between 99 and 103, this is GETDEVINFO. If the
status is 200, the ldev is the wrong type or
subtype for NMOPENLINK. Also, check that the
ldev is correctly configured and is available.
--------------------------------------------------------------------------
NMERR 160 MESSAGE Number of parameters exceeds maximum of 20.
(NMERR 160)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Check the parameters against the LINKCONTROL
syntax. Try again.
--------------------------------------------------------------------------
NMERR 161 MESSAGE Expects link name parameter. (NMERR 161)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Specify the link name parameter and try again.
--------------------------------------------------------------------------
NMERR 162 MESSAGE Expects a name from one to eight characters
long. (NMERR 162)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Check the spelling and try again.
--------------------------------------------------------------------------
NMERR 163 MESSAGE Expects alphanumeric name starting with
alphabetic. (NMERR 163)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Check the spelling and try again.
NMERR 164 MESSAGE Expects a semicolon after link name parameter.
(NMERR 164)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Correct and try again.
--------------------------------------------------------------------------
NMERR 165 MESSAGE Expects TRACE keyword. (NMERR 165)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Specify keyword and try again.
--------------------------------------------------------------------------
NMERR 166 MESSAGE Expects an equals sign after TRACE keyword.
(NMERR 166)
CAUSE Returned after entering LINKCONTROL command
incorrectly.
ACTION Correct and try again.
--------------------------------------------------------------------------
NMERR 171 MESSAGE Specified linkname is not an active datacomm
device. (NMERR 171)
CAUSE The specified linkname does not exist.
ACTION Check the spelling of your entry and try again.
CAUSE The device specified is not configured.
ACTION Check the list of configured devices and try
again.
--------------------------------------------------------------------------
NMERR 172 MESSAGE Specified pathname is not a datacom device.
CAUSE The specified pathname is not a valid datacom
device address.
ACTION Check the pathname in the configuration file and
re-enter.
--------------------------------------------------------------------------
NMERR 175 MESSAGE Unexpected internal error accessing
configuration data. (NMERR 175)
CAUSE An unexpected error has occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------