Article ID: 970202 - View products that this article applies to.
Consider the following scenario:
This problem is most likely to occur when the Host Integration Server system and the IBM host system are connected by using a high speed network connection.
The IP-DLC link service uses an 8-KB socket receive buffer to receive User Datagram Protocol (UDP) data from the remote IBM systems that it is communicating with. If the IP-DLC link service receives a large amount of data in a very short interval, it is possible that some UDP data will be dropped by the IP-DLC link service. When this occurs, the IP-DLC link service will report that a gap was detected in the data stream. When the remote system is notified that a gap was detected, it resends the data that was not acknowledged by the IP-DLC link service. The retransmission of data can result in decrease in performance.
Service pack information for Host Integration Server 2006To resolve this problem, obtain the latest service pack for Host Integration Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/979497/ )How to obtain the latest Host Integration Server 2006 service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have Host Integration Server 2004 Service Pack 1 (SP1) installed.
Restart RequirementYou do not have to restart the computer after you apply this hotfix.
Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.
File InformationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Microsoft Host Integration Server 2004 SP1
Collapse this tableExpand this table
Microsoft Host Integration Server 2006
A hotfix is currently not available for Microsoft Host Integration Server 2006. Microsoft Host Integration Server 2009
A hotfix is currently not available for Microsoft Host Integration Server 2009
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
After you apply this hotfix, the IP-DLC link service will use a default UDP socket receive buffer size of 32768 bytes (32 KB). You can change the UDP socket receive buffer by adding the following registry parameter:
http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg243669.htmlMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Note RTP connections and the Status Segment parameter of the RTP Transport Header are discussed in Chapter 8 of Inside APPN and HPR - The Essential Guide to New SNA. The RTP Status Segment is used to report gaps (missing data) in the data stream and is also used to acknowledge data.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 970202 - Last Review: October 7, 2011 - Revision: 3.0