Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You receive Event 102 (2167) when a Transaction Integrator method that connects to an IBM IMS application uses the IMS Connect programming model in a Host Integration Server environment

FIX: You receive Event 102 (2167) when a Transaction Integrator method that connects to an IBM IMS application uses the IMS Connect programming model in a Host Integration Server environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • In a Microsoft Host Integration Server environment, you have a Transaction Integrator method that connects to an IBM IMS application.
  • The Transaction Integrator method uses the IMS Connect programming model.
In this scenario, the following error message may be logged in the Application log:
Event ID: 102

Source: HIS Application Integration

Description:

Error HISETBG0001 Application Integrator has intercepted an exception in method MethodName. Following is the exception description: (2167) HISMITW0025 The IMSConnectTransport attempted to receive an LLZZ while processing method MethodName but not enough data was received. IP Address: TCP/IP address, port: port number, Transaction Id: tranid, Error description: Success.

↑ Back to the top

Cause

This issue error occurs when the LLZZ field in an IMS message segment is split across two network packets. In this situation, the Transaction Integrator method receives two network packets. The first network packet has the first two bytes of the LLZZ field at the end of the network packet. The second network packet has the last two bytes of the LLZZ field at the start of the network packet.

↑ Back to the top

Resolution

Hotfix Information

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:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
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.

Prerequisites

You must have cumulative update package 1 for Microsoft Host Integration Server 2009 installed to apply this hotfix. 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:
2587090 Cumulative update package 1 for Host Integration Server 2009

File information

The English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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 versions of Microsoft Host Integration Server 2009, 32-bit (x86) editions
File nameFile versionFile sizeDateTimePlatform
Microsoft.hostintegration.ti.imsconnecttransport.dll8.0.3872.275,68826-Oct-201119:36x86
For all supported versions of Microsoft Host Integration Server 2009, 64-bit (x64) editions
File nameFile versionFile sizeDateTimePlatform
Microsoft.hostintegration.ti.imsconnecttransport.dll8.0.3872.275,68826-Oct-201119:36x86
Microsoft.hostintegration.ti.imsconnecttransport.dll8.0.3872.275,68826-Oct-201119:42x86
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

When IBM IMS sends a message, the message can consist of one or more segments. Each segment includes a four-byte LLZZ field. The first two bytes of the LLZZ field represent the length of the message segment. (This includes the four bytes for the LLZZ field.) The last two bytes of the LLZZ field are reserved for use by IMS.

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kb

↑ Back to the top

Article Info
Article ID : 2635163
Revision : 1
Created on : 1/7/2017
Published on : 11/10/2011
Exists online : False
Views : 335