APPC or CPI-C TPs May Fail When Using Dependent LU 6.2 Sessions

• Microsoft SNA Server versions 3.0, 3.0 Service Pack 1 (SP1), 3.0SP2, and 4.0

SYMPTOMS

An APPC or CPI-C application may fail to get an active conversation with a host if a previous conversation over the same Local APPC LU has ended. For example, if there was a conversation over local LU LOCAL1 and remote LU REMOTE1, an APPC or CPI-C application may fail to get an active conversation over local LU LOCAL1 and remote LU REMOTE2 even if the previous conversation has ended.

When this occurs, the APPC or CPI-C application call to [MC_]ALLOCATE or CMALLC never completes because SNA Server has not unbound the previous dependent LU/LU session before attempting to solicit a bind to a different Remote APPC LU.

NOTE: This does not occur when you use Independent LU 6.2 sessions.

CAUSE

SNA Server is not ending the previous dependent APPC session by sending an UNBIND to the host. This causes any additional APPC sessions over the same local APPC LU and different remote APPC LUs to fail to get active conversations until the first APPC session is shut down.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 4.0. A fix to this problem is available, but has not been regressiontested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

MORE INFORMATION

The SNA Server service has been updated so that it will unbind the initial dependent APPC session if it is not active when it receives a request to open a new APPC session over the same local APPC LU and a different remote APPC LU.

Keywords          : kbbug3.00 kbbug3.00.sp1 snaappc snacpic snaprog snatp kbbug3.00.sp2 kbbug4.00 kbnetwork
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbfix