Select the product you need help with

FIX: Event ID 102 is logged in Host Integration Server 2006 and in Host Integration Server 2004 when the first segment of data that TI receives from an IBM IMS application begins with the "DFS" character string

Article ID: 941986 - View products that this article applies to.

SYMPTOMS

In Microsoft Host Integration Server 2006 and in Microsoft Host Integration Server 2004, Transaction Integrator (TI) logs an event that resembles the following:

Event ID: 102
Source: COMTI
Description: (102) COM Transaction Integrator reported the following exception to the client:
Component: Component_Name
Method: Method_Name
Exception description: (2168) The TCP transport received an error message from IMS when using IMS Connect or OTMA. Message=DFS Data , Transaction Transaction_Name . IP Address: TCP/IP_Address , port: Port_Number

This problem occurs when the first segment of data that TI receives from an IBM Information Management System (IMS) application begins with the "DFS" character string.

Back to the top | Give Feedback

CAUSE

This problem occurs because TI processes the data that begins with the "DFS" character string as an IMS error message when TI receives the data from the IBM IMS application.

Back to the top | Give Feedback

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 this specific problem. 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=support

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

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 one of following products installed to apply this hotfix:

Host Integration Server 2006
Host Integration Server 2004 Service Pack 1 (SP1)
Host Integration Server 2004

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

Host Integration Server 2004

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Convertprimex.dll	6.0.2102.0	84,496	06-Sep-2007	01:26	x86	SP1
Db2oledb.dll	6.0.2102.0	500,736	06-Sep-2007	01:26	x86	SP1
Dcgen.dll	6.0.2102.0	109,056	06-Sep-2007	01:26	x86	SP1
Ddmstr.dll	6.0.2102.0	53,248	06-Sep-2007	01:26	x86	SP1
Dpl1.dll	6.0.2102.0	29,688	06-Sep-2007	01:26	x86	SP1
Drdaresync.exe	6.0.2102.0	346,632	06-Sep-2007	01:26	x86	SP1
Hipobjects.dll	6.0.2102.0	1,069,576	06-Sep-2007	01:26	x86	SP1
Microsoft.hostintegration.dataaccesslibrary.dll	6.0.2102.0	95,304	06-Sep-2007	01:24	x86	SP1
Microsoft.hostintegration.dataaccesstool.exe	6.0.2102.0	2,712,640	06-Sep-2007	01:24	x86	SP1
Microsoft.hostintegration.msdb2client.dll	6.0.2102.0	123,968	06-Sep-2007	01:24	x86	SP1
Mseidb2c.dll	6.0.2102.0	80,896	06-Sep-2007	01:26	x86	SP1
Mseidb2d.dll	6.0.2102.0	444,416	06-Sep-2007	01:26	x86	SP1
Mseidrda.dll	6.0.2102.0	709,632	06-Sep-2007	01:26	x86	SP1
Snanls.dll	6.0.2102.0	87,040	06-Sep-2007	01:26	x86	SP1
Sysctblj.exe	6.0.2102.0	39,936	06-Sep-2007	01:26	x86	SP1
Sysctblk.exe	6.0.2102.0	38,912	06-Sep-2007	01:26	x86	SP1
Sysctbls.exe	6.0.2102.0	38,912	06-Sep-2007	01:26	x86	SP1
Sysctblt.exe	6.0.2102.0	38,912	06-Sep-2007	01:26	x86	SP1
Tagen.dll	6.0.2102.0	105,472	06-Sep-2007	01:26	x86	SP1
Tranlu62.dll	6.0.2102.0	62,976	06-Sep-2007	01:26	x86	SP1
Trantcp.dll	6.0.2102.0	114,176	06-Sep-2007	01:26	x86	SP1
Trnsdt.dll	6.0.2102.0	19,968	06-Sep-2007	01:26	x86	SP1
Trnsdtj.dll	6.0.2102.0	16,896	06-Sep-2007	01:26	x86	SP1
Trnsdtk.dll	6.0.2102.0	15,872	06-Sep-2007	01:26	x86	SP1
Trnsdts.dll	6.0.2102.0	15,360	06-Sep-2007	01:26	x86	SP1
Trnsdtt.dll	6.0.2102.0	15,872	06-Sep-2007	01:26	x86	SP1

Host Integration Server 2004 SP1

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Trantcp.dll	6.0.2414.0	114,176	14-Dec-2007	14:30	x86

Host Integration Server 2006, 32-bit (x86) version

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Tranlu62.dll	7.0.2877.0	90,624	06-Mar-2008	06:24	x86	SP1
Trantcp.dll	7.0.2877.0	148,992	06-Mar-2008	06:25	x86	SP1

Host Integration Server 2006, 64-bit (x64) version

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Tranlu62.dll	7.0.2877.0	132,608	06-Mar-2008	06:30	x64	SP1	Not Applicable
Trantcp.dll	7.0.2877.0	214,016	06-Mar-2008	06:30	x64	SP1	Not Applicable
Tranlu62.dll	7.0.2877.0	90,624	06-Mar-2008	06:24	x86	SP1	SYSWOW
Trantcp.dll	7.0.2877.0	148,992	06-Mar-2008	06:25	x86	SP1	SYSWOW

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

Back to the top | Give Feedback

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 | Give Feedback

This problem was first addressed in the Host Integration Server 2004 update that is described in article 917599. The information in this article supersedes the information in Microsoft Knowledge Base article 917599. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

917599

(http://support.microsoft.com/kb/917599/ )

FIX: Transaction Integrator (TI) logs an event in Host Integration Server 2004 when the first segment of data that TI receives from an IBM IMS application begins with the "DFS" character string

The changes that are implemented in update 917599 are included in Host Integration Server 2004 SP1.

Based on customer feedback, additional changes were made to better handle incoming IBM IMS application data that begins with the "DFS" character string. The additional changes are described in this article.

By default, TI processes the data that begins with the "DFS" character string as an IMS error message when TI receives the data from an IBM IMS application. Therefore, event ID 102 is logged.

Host Integration Server 2004 and Host Integration Server 2004 SP1

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

After you apply one of the updated Host Integration Server 2004 hotfixes that are described in this article, you can configure TI to process the data that begins with the "DFS" character string as regular application data. To do this, follow these steps:

Click Start, click Run, type regedit, and then click OK.
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar\Defaults
Right-click Defaults, point to New, and then click Key.
Type AllowDFSAsUserData, and then press ENTER.
Click AllowDFSAsUserData.
Right-click Default, and then click Modify.
In the Value data box, type TRUE, and then click OK.
Exit Registry Editor.

If you enable the

AllowDFSAsUserData

registry key, TI processes the data that begins with the “DFS” character string as regular application data unless the MOD_NAME value in the Request Mode Message (*REQMOD*) structure equals DFSMO. If the MOD_NAME value equals DFSMO, TI still processes the data that begins with the “DFS” character string as an IMS error message.

Host Integration Server 2006

After you apply the Host Integration Server 2006 hotfix that is described in this article, a TI remote environment (RE) that is defined to communicate with an IBM IMS application by using TCP/IP includes the Error Recognition configuration options. You can use the Error Recognition configuration options to specify how TI processes the data that begins with the "DFS" character string.

The Error Recognition configuration options are as follows:

DFS at beginning of 1st Data Segment
If you select this option, TI processes all the data that begins with the “DFS” character string as an IMS error message.
MFS MOD name returned in RMM
If you select this option, the MFS Mode name box becomes available. You use the MFS Mode name box to specify the MOD_NAME value that is used to determine whether the incoming data is an IMS error message. For example, if the MOD_NAME value equals DFSMO, TI still processes the data that begins with the “DFS” character string as an IMS error message. Otherwise, TI processes the data as regular application data, and TI returns the data to the calling TI application.

To access the Error Recognition configuration options in a TI RE configuration, follow these steps:

Click Start, click All Programs, click Microsoft Host Integration Server 2006, and then click TI Manager.
Expand Windows-Initiated Processing, and then expand Remote Environments.
Right-click the TI RE that is defined to communicate with the IBM IMS application, and then click Properties.
Click the IMS tab.
Configure the Error Recognition configuration options.

Note The

AllowDFSAsUserData

registry key does not apply to Host Integration Server 2006.

An IBM IMS application may return a valid error message that contains the "DFS" character string. In this case, TI may not process the valid error message as an IMS error message if you change the way that TI processes the data that begins with the "DFS" character string. This behavior could lead to other unexpected errors in the calling TI application or in the TI run-time environment. Therefore, change the default behavior only if the following conditions are true:

The IBM IMS applications in your environment return the "DFS" character string as application data.
This application data must be processed by TI, and then this application data must be passed to the calling TI application.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

The 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.

Back to the top | Give Feedback