Microsoft KB Archive/905685

= FIX: A Host Integration Server 2004 server routes all incoming FMH-5 Attach messages for an invokable TP to the same Host Integration Server 2004 server when the same invokable TP is running on multiple Host Integration Server systems =

Article ID: 905685

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2004 Standard Edition

-



Note The information in this article applies to both Microsoft Host Integration Server 2000 and Microsoft Host Integration Server 2004.



SUMMARY
When the same invokable APPC/CPI-C transaction program (TP) runs on multiple Host Integration Server systems, you may notice that a Host Integration Server 2004 server routes all incoming Function Management-5 (FMH-5) Attach messages for that invokable TP to the same Host Integration Server system.

For example, consider the following scenario. Five instances of an invokable TP that is named APINGD are running on two Host Integration Server 2004 clients. These clients are named CLIENT1 and CLIENT2. A Host Integration Server 2004 server is named SERVER1. In this scenario, you notice that SERVER1 may route all the FMH-5 Attach messages for APINGD to CLIENT1. However, SERVER1 does not load balance the FMH-5 Attach messages for APINGD across CLIENT1 and CLIENT2.



MORE INFORMATION
A Host Integration Server 2004 server keeps track of invokable TPs in the Host Integration Server subdomain by using a TP table. Each Host Integration Server 2004 server maintains a local TP table that lists the following information:
 * Invokable TPs that are running locally on the Host Integration Server 2004 server
 * Invokable TPs that are registered by Host Integration Server clients. These clients have sponsor connections to the SnaBase service of the Host Integration Server 2004 server.

Additionally, each Host Integration Server 2004 server maintains a remote TP table that lists the following information:
 * Invokable TPs that are running on other Host Integration Server 2004 servers in the subdomain
 * Invokable TPs that are running on Host Integration Server clients. These clients have sponsor connections to the SnaBase services of the other Host Integration Server 2004 servers in the subdomain.

The software update in this article enables Host Integration Server 2004 to load balance invokable APPC/CPI-C TP requests if the requested invokable TP is available on multiple systems. After you apply this software update, a Host Integration Server 2004 server will maintain a separate index into its local and remote TP tables. The index enables the Host Integration Server 2004 server to start searching the local and remote TP tables at the point where the last search ended. Therefore, the Host Integration Server 2004 server can distribute the FMH-5 Attach messages across multiple instances of an invokable TP in a round-robin order.

Host Integration Server 2004 maintains a priority table that is based on the type of invokable TP. For example, the priority table may use the following order:
 * Operator-started TP
 * Auto-started TP
 * Whether the TP is local or remote
 * Whether the APPC LU in the incoming request matches the APPC LU that is used by the invokable TP

The FMH-5 Attach request is routed to the invokable TP instance that has the lowest priority number in the priority table.

Host Integration Server 2004 servers do not load balance invokable TPs across local and remote TP tables. If an FMH-5 Attach message specifies an invokable TP that is registered in both the local TP table and the remote TP table of a Host Integration Server 2004 server, the FMH-5 Attach message is routed to the invokable TP that is registered in the local TP table.

Host Integration Server 2000
A software update for Host Integration Server 2000 is unavailable.

Host Integration Server 2004
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Host Integration Server 2004 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this software update has the file attributes (or later file attributes) 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.

Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.



Additional query words: HIS2004 HIS2000

Keywords: kbinfo kbbug kbfix kbhis2000 kbqfe kbpubtypekc kbhis2004 KB905685

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.