Microsoft KB Archive/938124

= FIX: Host Integration Server 2006 Transaction Integrator logs an error message for a COMP-3 field because of increased validation checking =

Article ID: 938124

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2006

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



SYMPTOMS
Microsoft Host Integration Server 2006 Transaction Integrator (TI) performs validation checks on COMP-3 data fields more rigorously than earlier versions of Host Integration Server. For example, if a mainframe application returns null values for a COMP-3 field, the Host Integration Server 2006 version of Transaction Integrator logs an error in the Application log. However, earlier versions of Transaction Integrator do not log an error when a mainframe application returns null values. Instead, earlier versions of Transaction Integrator return a value of zero to the Windows client application.

The error that is logged resembles the following: Event Type: Error

Event Source: COMTI

Event Category: General

Event ID: 102

Description:

(102) Transaction Integrator reported the following exception to the client:

Component:

Method:

Exception description:

(1524) An invalid packed decimal value was encountered in  in. Check the mainframe server program. If it is correct, verify that the correct Transaction Integrator-created component library is deployed.

EXPLANATION

An Automation exception representing an error condition was returned to a Transaction Integrator client. The description shown above contains more information about the exception that was reported.

ACTION

The exception may be caused by communication problems or errors in your host application. See the exception description for corrective actions.



CAUSE
This problem occurs when you use COM-3 packed decimal values, and the last part of the last byte contains the information for the sign of the number. Consider the following scenario:
 * The field is a 3-byte packed decimal field (PIC S9(5) COMP-3).
 * The hexadecimal value 00 12 3C is the 3 bytes of data that are returned from the host application.

In this scenario, Transaction Integrator interprets the data as a value of +123. In Host Integration Server 2006, Transaction Integrator logs an error if the last part of the byte has a value of 0 through 9. For example, if the data for the 3-byte packed decimal field is returned as the hexadecimal value 40 40 40, the Host Integration Server 2006 version of Transaction Integrator logs an error because the sign is zero. Earlier versions of Transaction Integrator do not log an error. However, earlier versions of Transaction Integrator do return a value of +40404 to the client application.



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

Prerequisites
No prerequisites are required.

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

Registry information
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

You must change the registry to enable this hotfix after you install the hotfix. You must create a registry key to disable Transaction Integrator from performing more rigorous checks in Host Integration Server 2006. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then right-click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar\Defaults

Note In a 64-bit Windows operating system, right-click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Cedar\Defaults

 Click New, and then click Key. Type AcceptBadCOMP3Sign, and then press ENTER. Right-click AcceptBadCOMP3Sign, click New, and then click String Value. Type Activate, and then press ENTER.

Note The value that is contained in the Activate registry entry is not relevant.</li> Click the File menu, and then click Exit.</li></ol>

The registry entry makes Host Integration Server 2006 do less checking for the COMP-3 field. To disable this change, rename the Activate registry entry or the AcceptBadCOMP3Sign registry key. For example, rename the Activate registry entry as the Deactivate registry entry.

Note Make sure that Transaction Integrator is not running when you make this registry change. Transaction Integrator must be stopped for the new registry changes to take effect.

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.

<div class="workaround_section">

WORKAROUND
To work around this problem, modify the mainframe application so that the mainframe application returns only valid numeric data for all COMP-3 fields.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about software update terminology, 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

Additional query words: COMTI TI

Keywords: kbhotfixserver kbqfe kbpubtypekc kbcode kberrmsg kbfix KB938124

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.