EXPLANATIONS FOR SNA ERRORS WITH LU6.2 APPLICATION
ITEM: RTA000037130
QUESTION:
Customer has received some SNA errors with his LU6.2 application.
The system is currently at AIX 3.2.4 with the most current
SNA refresh. He cannot find any detailed information on these
errors. Could you please assist with an explanation for the
following:
1) When and Why does SNA send a SIG 30 (Signal 30) to his connected
TP's?
2) He received an errno 163 (SNA_NORCB) return code to his LU6.2
function. This error is defined in luxsna.h. What is an rcb?
What do you do when you run out of rcb's? Could you please provide
detailed information.
---------- ---------- ---------- --------- ---------- ----------
The signal 30 is a SIGUSR1 signal which is sent to an application which
has an SNA connection opened. The SIGUSR1 is sent to indicate that the
connection has gone down (either by failure or by being stopped). The
program should close the connection and then attempt to reopen the
connection before continuing. In other words, when the program starts,
it should issue the 'signal(SIGUSR1, sig_handler);' call so that when
the SIGUSR1 is received, the sig_handler() routine will be called.
The sig_handler() routine should be a user written function which will
close the connection, reopen the connection and then call the signal()
routine again to reset the action for SIGUSR1 to sig_handler (so that
if the SIGUSR1 is sent again, the same action will take place).
In response to the second set of questions, an RCB is a Resource
Control Block. The resource being referred to is a conversation.
The resource control block is used by SNA Services to maintain
information about a conversation. This error is generally caused
by either a session failure (a conversation is held over a session) or
the number of sessions, as defined by the Mode for this SNA connection,
has reached the limit. If the error is being received when a call
is made after the SIGUSR1 has been received for that connection,
this would certainly explain the error. By following the suggestions
in the first part of this response, this error should not continue to
occur.
If the problem persists, I will need additional information to provide
more details. First, on what call is the errno 163 being returned?
Is the connection still active? Has a SIGUSR1 been received?
Also, the best place to get better details on an error is from the
SNA Internal Error log (/var/sna/snalog.1). This log must be enabled by
setting 'Perform ERROR LOGGING' to yes in the SNA Node profile. Please
include any errors from the SNA Internal Error log also.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q649516 CNKQW
Additional search words:
AIX ALTERNATE CNKQW COMMUNICATIO ERR ERROR EXPLANATIONS INDEX IX
JAN94 OZNEW RISCSNA RISCSYSTEM SNA SOFTWARE
WWQA: ITEM: RTA000037130 ITEM: RTA000037130
Dated: 11/1996 Category: RISCSNA
This HTML file was generated 99/06/24~12:43:14
Comments or suggestions?
Contact us