SLI_CLOSE May Hang if CICS Doesn't Respond to SHUTC (180704)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 4.0
This article was previously published under Q180704 SYMPTOMS
When an SLI application calls SLI_CLOSE, the SLI_CLOSE may never complete
if the host sends an UNBIND request but fails to send a SHUTC response.
This problem was found when connecting an SLI application to CICS. If the
CICS region is stopped and started, in some cases the SLI application's
SLI_CLOSE request failed to complete.
The following API and message sequence summarizes the failure scenario:
SLI Program SLI API SNA Server/Host
=========== ========= =================
< SLI program in session with the host >
SLI_BID ->
<- SHUTD
<- SLI_BID (LUA_SESSION_END_REQUESTED)
SLI_CLOSE ->
SHUTD +RSP ->
CHASE ->
<- CHASE +RSP
SHUTC ->
<- UNBIND (type 01 = normal)
SENSE 08390000 ->
UNBIND +RSP ->
CAUSE
The SLI interface was hanging if it received an UNBIND when waiting for a
SHUTC response.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was corrected in the latest SNA Server versions 3.0 and 4.0
U.S. Service Packs. For information on obtaining these Service Packs,
query on the following word in the Microsoft Knowledge Base (without the
spaces):
MORE INFORMATION
With this update applied, the SLI interface will now complete the SLI_CLOSE
if an UNBIND is received, even if no SHUTC response is received.
| Modification Type: | Major | Last Reviewed: | 6/30/2004 |
|---|
| Keywords: | kbbug kbfix KB180704 |
|---|
|