Using ax_reg( )

The ax_reg( ) function 3registers an XA data source with the current transaction. This function 3must be repeated with each new transaction.

Use the following syntax for an ax_reg( ) function:

int ax_reg(int rmid, XID *xid, int4 flags)

For example:

    #include "xa.h"
3     #include "milib.h"
3     int   rmid, retcode;
3    XID  *xid;
3   if ( (rmid = mi_xa_get_xadatasource_rmid("informix.Newyork")) <= 0)
3       {
3        /* Error while getting XA data source id */
3       }
3    if ( !(xid = (XID *)mi_alloc(sizeof(XID)) ))
3          {
3        /* Memory allocation error */
3          }
3  retcode  = ax_reg(rmid, xid, TMNOFLAGS);
3if (retcode != TM_OK )
3     {
3         /* ax_reg() Error  */
3     }
3 /* ax_reg() is Successful */

When you use the ax_reg( ) function, follow 3these guidelines: 3

3
• Be sure the correct rmid (resource manager 3ID) is correct. 3 3

  You 3can use the mi_xa_get_xadatasource_rmid( ) function 3to enable the DataBlade module to get the ID the correct rmid value.

  3 3

  The resource manager ID must be present in a row in the sysxadatasources system 3catalog table that was created with the CREATE XADATASOURCE statement 3of SQL.

3
• xid is a valid pointer to the XID data 3structure, which is defined in the $INFORMIXDIR/incl/public/xa.h file. 3Make sure that memory for xid is allocated.
3
• Set flags to TMNOFLAGS. The value for TMNOFLAGS is defined in the $INFORMIXDIR/incl/public/xa.h file.
3
• Only call the ax_reg( ) function within 3an explicit or implicit transaction.
3
• Do not call the ax_reg( ) function in 3these contexts: 3 3
  3
  • From the sub-ordinator of a distributed transaction or from 3within a resource manager global transaction 3 3

    Dynamic Server can operate as a resource manager in a global 3transaction managed by a third party transaction manager. The ax_reg( ) function 3should not be used if Dynamic Server is operating as a resource 3manager.

  3
  • In a non-logging database
  3
  • From any of the XA purpose functions that are specified in a 3CREATE XADATASOURCE TYPE statement, which creates a type of XA-compliant external 3data source.

Multiple registrations of the same XA data source in a single 3transaction do not effect either the transaction or the XA data 3source.

For more information on this function, see the IBM Informix: DataBlade API Function Reference.