HP 3000 Manuals HP 3000 Manuals
NMERR Messages (contd)
NMERR 177 MESSAGE I/O manager status indicates error: Offline(!)
HW Fail(!) PFail(!) PFail Recovery(!) 177
Locked(!) HW Recovery(!) HW Sick(!) HW
Dead(!) Resource(!). Run diagnostics for more
information. (NMERR 177)
CAUSE This message is likely caused by a hardware
problem, and is a generic status request to the
I/O manager returned with the specified bits
set. One particular example is that the user
has entered the LINKCONTROL command while the
system is in power fail recovery.
ACTION Correct the problem and try again.
--------------------------------------------------------------------------
NMERR 178 MESSAGE Link H/W device indicates self test failure.
Run diagnostics for more information. (NMERR
178)
CAUSE A failure has occurred in the datacomm hardware.
ACTION Run diagnostics and replace the defective
hardware as necessary.
--------------------------------------------------------------------------
NMMER 179 MESSAGE Unexpected internal error accessing I/O manager.
CAUSE The I/O Manager is an unknown state.
ACTION Run diagnostics for more information.
--------------------------------------------------------------------------
NMERR 181 MESSAGE Trace buffer size must be in the range 1 to 16.
(NMERR 181)
CAUSE The user has entered a number that is not in the
acceptable range. The current buffer sizes
supported are within the ranges of 1K to 16K.
Returned by the LINKCONTROL command parsing
routine.
ACTION Enter a valid number (1 through 16).
--------------------------------------------------------------------------
NMERR 182 MESSAGE HPE status : info =!, subsystem ID = !. (NMERR
182)
CAUSE Status information reported by each individual
module.
ACTION Look at "DHPESTAT.HPESTD.OFFICIAL" for the
definitions of subsystem constants. Find out
the error information by checking the status
reporting file for that particular module.
--------------------------------------------------------------------------
NMERR 185 MESSAGE Only the LANIC link is supported. (NMERR 185)
CAUSE No link other than LAN is currently supported.
ACTION Specify only the LANIC for this application.
--------------------------------------------------------------------------
NMERR 186 MESSAGE Trace request for linkname failed due to : HPE
status: INFO = ! subsystem ID = !.
CAUSE You attempted to start or stop tracing, but
tracing was already enabled or disabled.
ACTION None.
CAUSE An improper value was specified in the
LINKCONTROL command.
ACTION Reissue the LINKCONTROL command with the correct
value.
CAUSE An error occurred while accessing the specific
I/O manager.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 187 MESSAGE Trace for linkname has been initiated with some
exceptions : HPE status: INFO = !, subsystem
ID = !.
CAUSE This error is often returned even though tracing
has been enabled.
ACTION None. If this error occurs frequently, submit
an SR. See "Submitting an SR at the beginning of
this appendix."
--------------------------------------------------------------------------
NMERR 189 MESSAGE Invalid length for a trace file name.
CAUSE MPE-iX trace file names are in the format of
filename.group.account and must contain a
maximum of eight characters in the filename,
group, and account fields.
ACTION Reissue the command using a valid trace file
name which contains no more than eight
characters in the filename, group, and account
field.
--------------------------------------------------------------------------
NMERR 193 MESSAGE Trace buffer size for a LAPB SDLC link must be
between 5 & 16. (NMERR 193)
CAUSE The current buffer sizes supported for LAPB and
SDLC are 5K to 16K.
ACTION Configure values in the correct range.
--------------------------------------------------------------------------
NMERR 200 MESSAGE Unable to access ! subsystem message catalog !.
(NMERR 200)
CAUSE The first parameter is the subsystem name or
subsysid. The second parameter is the message
catalog file name. This is returned by a
datacomm subsystem message-generating routine.
The specified subsystem encountered an error
trying to access an error message in the
specified message catalog file.
ACTION Something is wrong with the specified message
catalog file. Either it does not exist, or is
the wrong version, or is inaccessible due to
someone else either storing it or accessing it
exclusively, or some other I/O error has
occurred. Correct the problem with the message
catalog and retry.
--------------------------------------------------------------------------
NMERR 201 MESSAGE Error accessing NMCAT.PUB.SYS set=! msg=!.
(NMERR 201)
CAUSE Returned by NMPRINTERRMSG and usually followed
by one or more of messages 202 through 205
below, which further clarifies the error. NOTE:
This message is actually hard-coded in
NMPRINTERRMSG and is included here only for
documentation purposes.
ACTION Look for one or more of NMERR 202 through 205
following this message, and take the remedial
action suggested below. Read the text and
comments for the original message specified in
the message, and take the suggested actions.
--------------------------------------------------------------------------
NMERR 202 MESSAGE FOPEN FSERR ! on NMCAT.PUB.SYS. (NMERR 202)
CAUSE Returned by NMPRINTERRMSG and usually followed
by the text of the FSError message.
ACTION Correct the FOPEN problem and retry.
--------------------------------------------------------------------------
NMERR 203 MESSAGE Encountered GENMESSAGE error !. (NMERR 203)
CAUSE Returned by NMPRINTERRMSG. If error number is 1
or 2, NMERR 204 follows with a further
description. Otherwise the error is described
in the MPE Intrinsics Manual under GENMESSAGE.
ACTION If the error number is 1 or 2, see the NMERR 204
message and comments. If the error number is
not 1 or 2, look up the error number in the MPE
Intrinsics Manual under GENMESSAGE. It is likely
the problem is due to a bad software
installation. If this is consistent with the
GENMESSAGE error, see "Getting Help" at the
beginning of this appendix. Otherwise, correct
the problem causing the GENMESSAGE error and try
again.
--------------------------------------------------------------------------
NMERR 204 MESSAGE GENMESSAGE encountered FSERR !. (NMERR 204)
CAUSE Returned by NMPRINTERRMSG. This message follows
NMERR 203 message, and is usually followed with
the text of the FSError message as well.
ACTION Correct the FS error and retry.
--------------------------------------------------------------------------
NMERR 205 MESSAGE FCLOSE FSERR ! on NMCAT.PUB.SYS. (NMERR 205)
CAUSE Returned by NMPRINTERRMSG after printing a
message from NMCAT.PUB.SYS. The FCLOSE of
NMCAT.PUB.SYS failed.
ACTION Correct the File System error and retry.
--------------------------------------------------------------------------
NMERR 206 MESSAGE !: Error trying to access ! msgnum ! setnum
!. (NMERR 206)
CAUSE Returned by a subsystem message-generating
routine when it was unable to access the
specified message catalog. The first parameter
is the Subsys (module) name. The second
parameter is the Subsys message catalog name.
The third parameter is the message number. The
fourth parameter is the set number. Note that
this message is usually followed by one or more
of messages NMERR 207 through 210.
ACTION Check to see that the names entered actually
exist and are spelled correctly. Read any other
error messages which are also displayed, and
take the action(s) recommended to correct the
problem(s) described by those messages.
--------------------------------------------------------------------------
NMERR 207 MESSAGE Encountered FOPEN FSERR ! on !. (NMERR 207)
CAUSE Returned by a subsystem message-generating
routine when it was unable to FOPEN the
specified message catalog. The first parameter
is the FSERR number. The second parameter is
the message catalog name. This message is
usually preceded by message NMERR 206.
ACTION Correct the FOPEN error and retry.
--------------------------------------------------------------------------
NMERR 208 MESSAGE Encountered GENMESSAGE error !. (NMERR 208)
CAUSE Returned by a subsystem message-generating
routine, usually following NMERR 206. The
parameter is the GENMESSAGE errnum. If the
error number is 1 or 2, NMERR 209 follows with a
further description. Otherwise, the error is
described in the MPE Intrinsics Manual under
GENMESSAGE.
ACTION If the error number is 1 or 2, see the NMERR
message # 209. If the error number is not 1 or
2, look up the error number in the MPE
Intrinsics Manual under GENMESSAGE. It is likely
the problem is due to a bad software
installation. If this is consistent with the
GENMESSAGE error, the configuration file may be
corrupted. Run NMMGR and verify that the
configuration file is okay. Otherwise, correct
the problem causing the GENMESSAGE error and try
again.
--------------------------------------------------------------------------
NMERR 209 MESSAGE GENMESSAGE encountered FSERR !. (NMERR 209)
CAUSE Returned by a subsystem message-generating
routine. The parm is the FSERR number. This
message usually follows NMERR 208, and is
usually followed with the text of the FSError
message as well (by calling the intrinsic
FErrMsg).
ACTION Correct the FS error and retry.
--------------------------------------------------------------------------
NMERR 210 MESSAGE Encountered FCLOSE FSERR ! on !. (NMERR 210)
CAUSE Returned by a subsystem message-generating
routine after reading a message from the
specified message catalog. The first parameter
is the FSERR number. The second parameter is
the message catalog name. The FCLOSE of the
message catalog failed.
ACTION Correct the File System error and retry.
--------------------------------------------------------------------------
NMERR 220 MESSAGE Config file internal error detected and recovery
failed. (NMERR 220)
CAUSE The configuration file is possibly corrupted.
ACTION See "Corrupt Configuration Files" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 221 MESSAGE Total data length too large to return as
integer. (NMERR 221)
CAUSE Returned by NMCONFSONINFO. The total data length
associated with the path name and all its first
level sons was greater than 32767 and could not
be returned to caller. It is possible that the
configuration file is corrupt. It is also
possible that there is no error at all. It is
theoretically possible, although unlikely, to
have more than 32767 bytes of data associated
with a path and its first level sons.
ACTION See "Corrupt Configuration Files" at the
beginning of this appendix.
CAUSE Possible internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 222 MESSAGE Son count too large to return as integer.
(NMERR 222)
CAUSE Returned by NMCONFSONINFO. The number of first
level sons linked to the path name sent by the
calling subsystem exceeds 32767. It is possible
that the configuration file is corrupt. It is
also possible that an internal error occurred.
ACTION See "Getting Help" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 223 MESSAGE Request type out of bounds - error in port msg
to NMFILE. (NMERR 223)
CAUSE Returned if NMFILE receives a request type that
it does not recognize as being a valid NMCONF
intrinsic request on its NMCONF subqueue.
ACTION Internal error. See "Getting Help" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMMSG 301 MESSAGE Will use LOGGING configuration for this
subsystem that is already active. (NMMSG 301)
CAUSE Returned by NMOPENLOG, NMOPENLOG2. The open log
was successful and logging may proceed. Note
that there is another openlog outstanding for
the same subsystem id, so the configuration
information already in use will continue to be
used. This result code is returned as a
negative number (-301) to indicate it is not an
error and that the openlog was in fact
successful.
ACTION None.
--------------------------------------------------------------------------