LU 6.2 Data Compression Fails When Initiated by Host System (262473)
The information in this article applies to:
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
This article was previously published under Q262473 SYMPTOMS
SNA Server does not use LU 6.2 data compression when the BIND is a host initiated, non-extended BIND. Compression is not used even though it has been configured on both the connection and on the APPC mode definition.
CAUSE
When SNA Server negotiates LU 6.2 compression, it checks the level of compression that is configured on the mode entry and the level of compression that is configured on the connection. It obtains this information from a connection record in an internal connection table.
This problem occurs because SNA Server is incorrectly reading the connection record, and therefore, it obtains the wrong value for compression support. Because of this, SNA Server does not accept the host systems request for data compression.
RESOLUTIONTo resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
WORKAROUND
This problem does not occur when SNA Server initiates the BIND with the host. In most scenarios, setting an Automatic Activation Limit on the APPC mode definition eliminates this problem by forcing SNA Server to initiate the BIND with the host.
STATUSMicrosoft has confirmed that this is a problem in Microsoft SNA Server version 4.0, 4.0 SP1, 4.0 SP2, and 4.0 SP3.
This problem was first corrected in SNA Server 4.0 Service Pack 4.
Modification Type: | Major | Last Reviewed: | 11/24/2003 |
---|
Keywords: | kbbug kbfix kbQFE kbSNA400PreSP4fix kbSNA400sp4fix KB262473 |
---|
|