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

524 Chapter21
Logging Location Codes
Control Process Logging Location Codes
ACTION: This error in itself was not fatal, and Transport should
continue to run. However, if the session which 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 a CR,” of this manual.
668 CLAS0002 MESSAGE: Bad status
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.
ACTION: The second error in itself was not fatal, and Transport should
continue to run. However, if the session which 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 a CR,” of this manual.
669 CLAS0002 MESSAGE: Bad status
CAUSE: While processing a request sent by the DIAL protocol module
because a LAPB autodial link is being connected, NETCP encountered
some kind of error (such as errors 315, 316, 322), then encountered a
second error trying to send the bad reply message back to DIAL to
report the first error (PARM = 32-bit status returned by the call to
send_msg).
ACTION: Since DIAL never received its reply, it may take up to 30
minutes for DIAL to time out and reset itself, and during this delay,