Knowledge Base

FIX: Error message when an application calls a Host Integration Server 2004 Transaction Integrator method: "(1609) The destination program terminated with an abend code of 1007"

Article ID: 921483

Article Last Modified on 12/4/2007

APPLIES TO

Microsoft Host Integration Server 2004 Enterprise Edition

SYMPTOMS

When an application calls a Microsoft Host Integration Server 2004 Transaction Integrator method to send data to a CICS application, the CICS application abends (terminates). Additionally, the CICS application returns an error to Transaction Integrator. Additionally, Transaction Integrator logs an error message in the Application log that resembles the following:

Event Source: COMTI
Event ID: 102
Description:
(102) Transaction Integrator reported the following exception to the client:
Component: Component Name
Method: Method Name
Exception description: 
(1609) The destination program terminated with an abend code of 1007. CICS Mirror Transaction Transaction Name, destination program Destination Program Name.

This problem occurs if the following conditions are true:

The Transaction Integrator method contains parameters that are defined as double automation data types.
The Transaction Integrator method maps the double automation data types to PIC S9(9) COMP COBOL data types.

CAUSE

This problem occurs because Transaction Integrator does not map double automation data types to COMP COBOL data types.

RESOLUTION

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

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.

File name	File version	File size	Date	Time	Platform
Convertprimex.dll	6.0.2036.0	75,264	22-Jun-2006	16:46	x86
Ibmcobol.xml	Not Applicable	52,368	22-Jun-2006	16:34	Not Applicable
Microsoft.hostintegration.ti.convertprimex.interop.dll	6.0.1701.0	8,704	22-Jun-2006	16:46	x86
Microsoft.hostintegration.tidesigner.app.dll	6.0.2036.0	368,640	22-Jun-2006	16:47	x86
Microsoft.hostintegration.tidesigner.ctrl.dll	6.0.2036.0	90,112	22-Jun-2006	16:48	x86
Microsoft.hostintegration.tidesigner.wizards.dll	6.0.2036.0	462,848	22-Jun-2006	16:48	x86
Tracing.dll	6.0.2036.0	542,208	22-Jun-2006	16:46	x86

WORKAROUND

To work around this problem, the following conversion mapping can be manually added at the end of the Lbmcobol.xml file in the %SNAROOT% (C:\Program Files\ Microsoft Host Integration Server\system) directory. This conversion mapping allows for double automation data types to be mapped to COMP COBOL data types:

       <CONVERSION>

           <VARIANTYPE>5</VARIANTYPE><HOSTYPE>1</HOSTYPE><LABEL>PIC S9(n)V9(n) COMP</LABEL>

           <PROPERTY><ATTRIBUTE>DefSize</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MinSize</ATTRIBUTE><DATA>1</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MaxSize</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>DefScale</ATTRIBUTE><DATA>0</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MinScale</ATTRIBUTE><DATA>0</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MaxScale</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>SignFlag</ATTRIBUTE><DATA>0</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>TREFlag</ATTRIBUTE><DATA>2</DATA></PROPERTY>

       </CONVERSION> 

       <CONVERSION>

           <VARIANTYPE>5</VARIANTYPE><HOSTYPE>1</HOSTYPE><LABEL>PIC 9(n)V9(n) COMP</LABEL>

           <PROPERTY><ATTRIBUTE>DefSize</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MinSize</ATTRIBUTE><DATA>1</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MaxSize</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>DefScale</ATTRIBUTE><DATA>0</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MinScale</ATTRIBUTE><DATA>0</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>MaxScale</ATTRIBUTE><DATA>10</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>SignFlag</ATTRIBUTE><DATA>1</DATA></PROPERTY>

           <PROPERTY><ATTRIBUTE>TREFlag</ATTRIBUTE><DATA>2</DATA></PROPERTY>

       </CONVERSION>

STATUS

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

MORE INFORMATION

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

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

Keywords: kbhotfixserver kbqfe kbpubtypekc kberrmsg kbcode kbfix KB921483

Microsoft KB Archive/921483

Contents