You run an IBM mainframe application that calls an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPT-C) application. The APPC or CPI-C application runs on a Microsoft Host Integration Server 2009-based server or on a Microsoft Host Integration Server 2009 Client system.
Transaction Program (TP) Name for the mainframe application specified in the Function Management Header-5 (FMH-5) Attach message is one character long. For example, Transaction Program (TP) Name has the X’03’ value. This TP name is the IBM Service Transaction Program name.
In this scenario, the application does not run, and two error events that resemble the following are logged on the Host Integration Server 2009-based server:
Event ID: 60 Source: SNA Server Description: Failed to invoke APPC TP <one-character IBM Service TP name> (), local LU = <Local APPC LU>, sense data = 84c0000
EXPLANATION An attempt to invoke the APPC TP shown has failed. The error will be reported to the invoking TP on the remote system with the following primary return code:
AP_ALLOCATION_ERROR. The sense data shown is the secondary return code, which will be one of the following hexadecimal values:
Event ID: 730 Source: SNA Base Service Description: The Host Integration Server computer was unable to locate an invokable TP <converted IBM Service TP name>, APPC LU Alias <Local APPC LU Alias>, Workstation name: <Workstation name>.
An attempt to invoke the APPC TP shown has failed because Host Integration Server did not find the TP name registered on any client in the subdomain. If this is an auto-started TP, make sure the TP is defined on the client machine using the Host Integration Server TPSETUP program.
Note This issue also occurs in earlier versions of Host Integration Server 2009.
This issue occurs because the dynamic access module (DMOD) in Host Integration Server or in Host Integration Server Client does not correctly convert the one character long IBM Service Transaction Program name.
A 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 website:
Note 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.
To apply this hotfix, you must have Microsoft Host Integration Server 2009 installed.
You do not have to restart the computer after you apply this hotfix.
The English version of this hotfix 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 item in Control Panel.
For all supported x86-based versions of Host Integration Server 2009
For all supported x64-based versions of Host Integration Server 2009
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
IBM Service Transaction Program names can contain one, two or four characters. The first character in the name is an EBCDIC hexadecimal number from X'00' to X'3F'. The EBCDIC hexadecimal number is a nonprintable character. Therefore, the IBM Service TP name cannot be converted to a valid registry service key name. However, HIS uses the following mappings to represent some EBCDIC hexadecimal numbers:
EBCDIC hexadecimal number
Other EBCDIC hexadecimal numbers in the range from the X’00 number to the X’3F’ number.
Note The UN value means unknown.
For example, the AS/400 communications TP name that supports a 5250 display emulation is called X'30F0F0F5'. To define this name in the registry for an invokable transaction program, the TP name is set to PO005. In this scenario, the PO represents X'30', 'X'F0 is converted to the number zero (0), and 'X'F5 is converted to the number five (5).
For more information about how to configure IBM Service Transaction Program in HIS, click the following article number to view the article in the Microsoft Knowledge Base:
148970 How to configure SNA service TPs in the registry