Category: Transaction Integrator


During migration from a previous version of Host Integration Server to 2013 you may encounter some issues because some behaviors have changed.

In case of the Mirror Transaction Id, in previous versions of HIS, you have to specify in the Transaction Integrator a Mirror Transaction Id. There are two defaults MSCS and CSMI. If you have also specified a Mirror Transaction Id in your TI Assembly that you want to use to identity the CICS Transaction on the Mainframe, HIS 2006, 2009, 2010 have always used the value of the TI Assembly.

Now with HIS 2013, there’s no Transaction Integrator and you should use the new Transaction Integration Tool in order to configure the TI Environment. There are 3 scenarios :

  1. mirrorTransactionId=”XXXX” : the result will be “XXXX” on the Host side
  2. you are not using the mirrorTransactionId item : the result will be “CSMI” on the Host side
  3. mirrorTransactionId=”” : the result will be the value of the Mirror Transaction Id from the TI Assembly

You may get the following error when using 2 Phases Commit together with the HIS LU62 Resync Service :

HISETBG0001 Application Integrator has intercepted an exception in method XXXXX. Following is the exception description:

HISMSNA0022 The SNATransport, when processing method XXXXX, has failed when attempting to enlist in a transaction.

Ensure that the remote LU name XXXXX is configured to EnableSyncPoint. “Error in call to iDtcLuRmEnlistmentFactory ->Create,

HRESULT = 8004D10D or HRESULT = 8004D108

To resolve this issue, you only have to do the following steps

  1. Stop the SNA LU 6.2 Resync Service
  2. Stop DTC
  3. Clear DTC log è MSDTC -resetlog
  4. Start DTC
  5. Start the Resync Service
  6. Wait a couple of minutes and see if the event log posts a successful XLN(Exchange of Log names)
  7. Test again and it should work ! 🙂

Be aware that:

  • HIS 2006 uses the old Client Context (array of objects)
  • HIS 2010 uses the new Client Context with many new features
  • Converting from HIS 2006 to HIS 2010 using the TIConverterTool : you can still use the old HIS 2006 Client Context.
  • If you recreate or resave a TI Object on HIS 2010, you will have to use the new HIS 2010 Client Context.

Always keep this in mind if you are in a migration process from HIS 2006 to HIS 2010.

If you want to execute more CICS Transactions in one UOW using HIS 2010, be aware that the behavour changed from HIS 2006 to HIS 2010.

In both cases you need to set up a Remote Environment using SyncPoint and you have to use the Distributed Transaction Coordinator.

The important change is that in HIS 2006, the CICS Transactions are executed by default in the same UOW on the Host.

In HIS 2010 you have to use the “Persist Connections” property in the Client Context in order to execute the CICS Transactions in the same UOW.

Be aware that if you migrate (using the TIConverterTool) your TI Objects from HIS 2006 to HIS 2010, the new Client Context (with Persist Connections) is not used ! You need to recreate or resave the TI Objects so that the new Client Context is taken in account !

Important : You need HIS 2010 CU2 in order to get this work 🙂

After installing the CU1 update for HIS 2010, you don’t need to deploy your Transaction Integrator Components in the Transaction Integrator Manager anymore.
Before you’ve always got the error 1111 – Transaction Integration Object not registered. Now you can simply use your .Net generated TI Object.

Consider the following scenario. You run a web service by using Transaction Integrator (TI) in a Microsoft Host Integration Server 2010 environment. The remote environment is configured to use a CICS LU 6.2 session, and you enable the Allow use of explicit SYNCPOINT commands for non-transactional components property. In this scenario, the transaction may fail, and you receive the following CICS ABEND code: ADPL

=> This fix is already included in the HIS 2010 CU1 Package

Standalone Fix Download Link : http://support.microsoft.com/kb/2507433

In a Microsoft Host Integration Server 2010 environment, you configure a Transaction Integrator (TI) application to use the 2 Phase Commit (2PC) protocol. When you use the application for distributed transaction, the application does not enlist a transaction with the Microsoft Distributed Transaction Coordinator service (MSDTC). Additionally, you may receive the following exception:
The SNATransport, when processing method method-name, has failed when attempting to enlist in a transaction. Ensure that the remote LU name LU-name is configured to EnableSyncPoint.

=> This fix is already included in the HIS 2010 CU1 Package

Standalone Fix Download Link : http://support.microsoft.com/kb/2584671/

In a Microsoft Host Integration Server environment, you run an application to perform distributed transactions that use connection pooling. When you exit the application, an error message is generated by the common language runtime (CLR).

Download Link : http://support.microsoft.com/kb/2550485/en-us

You may receive out-of-memory error messages when you use the Transaction Integrator (TI) Conversion Tool to migrate lots of objects to Microsoft Host Integration Server (HIS) 2010.
For example, you may receive out-of-memory error messages when you use the TI Conversion Tool to convert hundreds of objects to HIS 2010.

Download Link : http://support.microsoft.com/kb/2504356/en-us

In a Microsoft Host Integration Server 2010 environment, you have a web application that uses Host Integration Server Transaction Integrator (TI). When the Host Integration Server TI monitoring thread is running, you notice that the W3wp.exe process consumes 100% of CPU resources. Because of this problem, the web application is unusable.

Download Link : http://support.microsoft.com/kb/2544897/en-us