GET_LU_STATUS_VERB Hangs On Call from Second Thread

• Microsoft SNA Server, versions 3.0, 3.0 SP1

SYMPTOMS

When two threads are using the same TP_ID, the GET_LU_STATUS verb hangs on the second call.

CAUSE

When a GET_LU_STATUS call is made the second time on two threads using the same TP_ID, the second call should return an AP_TP_BUSY.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

MORE INFORMATION

With the fix applied, the GET_LU_STATUS returns an AP_TP_BUSY on the second call to the same TP_ID.

Additional query words:

Keywords : kbnetwork snaappc snaprog kbfix3.00.sp2
Version : WINDOWS:3.0,3.0 SP1
Platform : WINDOWS
Issue type : kbbug