Consider the following scenario:
You run an IBM mainframe application that calls an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPI-C) application. The APPC or CPI-C application runs on a Microsoft Host Integration Server 2010-based server or on a Microsoft Host Integration Server 2010 Client system.
The Transaction Program (TP) Name for the mainframe application that is specified in the Function Management Header-5 (FMH-5) Attach message is an IBM Service Transaction Program name. The first character in the name is an EBCDIC hexadecimal number in the following range:
X'00' through X'3F' The EBCDIC hexadecimal number is a nonprintable character.
In this scenario, the Microsoft SNA Server service (snaservr.exe) may reach 100 percent CPU usage. Additionally, the service may crash (stop responding) when it processes the TP Name for the IBM Service TP.
IBM Service Transaction Program names can contain one, two, or four characters. The SNA Server service must check the TP name length when the service processes an incoming request. This problem occurs because of an incorrect check to verify the length of the TP Name for IBM Service Transaction Programs.
The hotfix that resolves this issue is included in cumulative update package 1 for Host Integration Server 2010.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2533330 Cumulative update package 1 for Host Integration Server 2010
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about another issue that is related to IBM Service Transaction Programs, click the following article number to view the article in the Microsoft Knowledge Base:
2417432 FIX: An APPC or CPI-C application does not run if the application uses one character for the IBM Service Transaction Program name on Host Integration Server 2009The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.