Request Unit Sizes Greater Than 16 KB Are Incorrectly Calculated When Creating APPC BINDs (326367)
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
- Microsoft SNA Server 4.0 SP4
- Microsoft Host Integration Server 2000
This article was previously published under Q326367 SYMPTOMS
If you set an Advanced Program-to-Program Communications (APPC) Mode definition's Max Send RU Size or Max Receive RU Size to greater than 32 KB (32,768), the SNA Server service specifies primary and secondary maximum request unit (RU) size values that are not valid in a BIND request (BIND bytes 10 and 11, respectively).
As a result, the SNA Server service issues an SNA UNBIND command to end the session.
CAUSE
The SNA Server service is designed to limit the RU size to 16384 (16 KB) bytes, however, SNA Manager limits the RU size to 65527 bytes (65 KB).
The SNA Server service handles the maximum RU size setting as follows: - If the maximum RU size is between 16384 and 32768, the SNA Server service uses an RU size of 16384 bytes.
- If the maximum RU size is greater than 32768, the SNA Server service uses an invalid value for the RU size because the two-byte signed value overflows.
WORKAROUND
To prevent this problem from occurring, set maximum send and receive RU size values that are between 256 and 16384.
STATUSMicrosoft has confirmed that this is a problem in SNA Server 4.0 and Host Integration Server 2000.
Modification Type: | Minor | Last Reviewed: | 3/17/2005 |
---|
Keywords: | kbbug kbnofix KB326367 |
---|
|