Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2014-04-16T03:10:56Z by rahulhegde
rahulhegde
rahulhegde
3 Posts
ACCEPTED ANSWER

Pinned topic XA Support for IBM DB2 ODBC Driver with IBM MQ as Transaction Manager

‏2014-04-14T06:25:22Z |

We are developing an AIX and Linux Host Application that will interact with IBM DB2 installed on separate AIX Box via unixODBC Driver Manager v2.3.2. The application is planned to work in XA with Transaction Manager been IBM MQ v7.x.

Question:
We tried creating the same application using IBM 'Embedded SQL' instead of 'unixODBC Driver Manager'. XA works very well but it doesn't work when used with the ODBC Driver. MQ been Transaction Manager, we have added 'IBM DB2' detail as a Resource Manager.

 

  1. I need to know would using unixODBC Driver Manager, result in adding Resource Manager as ODBC Driver and not IBM DB2?
  2. DB2CLI does talk of XA API support but there is no where I found creation of swit(Switch) file for Transaction Manager. Is my understanding correct?

Thanks in advance.

Updated on 2014-04-14T11:53:51Z at 2014-04-14T11:53:51Z by rahulhegde
  • mspringgay
    mspringgay
    16 Posts
    ACCEPTED ANSWER

    Re: XA Support for IBM DB2 ODBC Driver with IBM MQ as Transaction Manager

    ‏2014-04-15T21:04:04Z  in response to rahulhegde

    XA is support by CLI and would use the same XA switch as embedded.  The Transaction Manager setup is the same for either interface. I don't have any direct experience with using XA and unixODBC Driver Manager but would expect it to work with the same setup as well.  In both cases MQ would directly interact with the DB2 application library.

    • rahulhegde
      rahulhegde
      3 Posts
      ACCEPTED ANSWER

      Re: XA Support for IBM DB2 ODBC Driver with IBM MQ as Transaction Manager

      ‏2014-04-16T03:10:56Z  in response to mspringgay

      Thanks Mike for the reply.

      1. Does this mean you have run a CLI application but not using unixODBC Driver Manager and the same worked for you?

      2. We have set connection attribute AUTOCOMMIT to OFF before doing a SQLConnect. Since the run environment for 'embedded SQL' and 'unixODBC Driver Manager application' is same, It looks,  we are missing some more configuration setting in the application.

      Note - unixODBC Driver Manager in background uses IBM DB2 ODBC Driver, this is through the .ini files defined during unixODBC Driver Manager setup.

      Updated on 2014-04-16T04:39:45Z at 2014-04-16T04:39:45Z by rahulhegde