NS3000/iX Error Messages Reference Manual (36923-90041)

Chapter 19 373
Logging Location Codes
Control Process Logging Location Codes
ACTION: This error in itself was not fatal, and network startup
continued. However, X25 may not operate correctly. If X25 connections
are not working, stop then restart the network. If the problem persists,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
665 CLAS0002 CAUSE: After successfully starting a TOKEN link and all its network
specific protocols because a :NETCONTROL command was issued,
NETCP encountered an error trying to send a broadcast information
message to the UDP protocol module (PARM = 32-bit status returned
by the call to send_msg).
ACTION: This error in itself was not fatal, and NETCP startup
continued. After this failure, most of Transport, with the exception of
UDP, will probably run correctly. However, certain actions, such as Path
Verifies, can indirectly result in more sends to UDP, which may cause
more errors. When convenient, try stopping Transport using
:NETCONTROL STOP, then restart it and bring up the TOKEN link
again. If the same problem persists, see Appendix A, “Submitting an
SR,” of this manual.
MESSAGE: Bad status
666 CLAS0002 CAUSE: While processing a :NETCONTROL STATUS command, NETCP
encountered an error trying to send a reply message back to the NETUI
module (PARM = 32-bit status returned by the call to send_msg).
ACTION: This error in itself was not fatal, and Transport should
continue to run. However, ifthe sessionwhich issued the :NETCONTROL
STATUS command still exists, that session will now be hung. If the
session does not exist, this also indicates a bug since supported HP
commands to abort the session should have been disabled by NETUI. A
system restart will be required to clear the session’s hang. If the session
is on the system console, a :CONSOLE command may be attempted to
temporarily move the logical console to another terminal until a system
restart is convenient. If the problem persists, issue a :NETCONTROL
TRACEON=MHDSBN command beforehand, to enable NETCP tracing
which may capture the problem. When the problem occurs, issue a
:NETCONTROL TRACEOFF command from another terminal, then take a
system dump and send in the dump and the resulting trace file; see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
668 CLAS0002 CAUSE: While processing a :NETCONTROL STATUS command which
reported an error because a requested module was not active, or
because no buffer was available to hold excess error information,
NETCP then encountered another error while trying to send a reply
message about the first error, back to the NETUI module (PARM =
32-bit status returned by the call to send_msg). The cause of the first
error cannot be determined, except if NETCP message tracing was
enabled, the message was traced.