Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172708

From BetaArchive Wiki
Knowledge Base

BID Response Not Honoring Pacing Indicator from FMI Application

Article ID: 172708

Article Last Modified on 7/16/2004


  • Microsoft SNA Server 3.0 Service Pack 4, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 4.0, when used with:
    • Microsoft Windows NT 4.0

This article was previously published under Q172708


If an SNA Client system does not receive a Host data stream after successful session initialization, a problem with pacing may have occurred between the Host and the SNA Server. Users will not receive data from the Host, even though the session is still active in SNA Manager.


When a host sends a pacing indicator (Byte 2 of the RH set to 81) in an FMI message, SNA Server changes it to a value of 80 (no pacing). The Host is then unable to send the data because it has not received a pacing response.

A modification made to SNA Server version 3.0 had a side effect of disabling pacing if the first RU received on a session does not have the PI (pacing indicator) bit set.

For additional information about the RH (request header), please refer to the IBM SNA Formats Guide (GA27-3136).


Snaservr.exe has been modified so that pacing is not disabled.


Microsoft has confirmed this to be a problem in SNA Server 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):


Keywords: kbbug kbfix kbnetwork KB172708