Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
DataBlade® API Function ReferenceThe HCL OneDB™ DataBlade® API Function Reference describes the DataBlade® API functions and the subset of functions that the DataBlade® API supports.
Function descriptionsThis section gives comprehensive reference information about the functions that are valid within DataBlade® API modules. It lists the function descriptions in alphabetical order, with syntax, usage information, and return values for the functions.
The mi_xa_get_current_xid() functionThe mi_xa_get_current_xid() function returns the pointer to the current XID structure for an XA-compliant, external data source. The XID structure is defined in the $INFORMIXDIR/incl/public/xa.h file.

The mi_xa_get_current_xid() function

The mi_xa_get_current_xid() function returns the pointer to the current XID structure for an XA-compliant, external data source. The XID structure is defined in the $INFORMIXDIR/incl/public/xa.h file.

Syntax

XID * mi_xa_get_current_xid ()


Valid in client LIBMI application?	Valid in user-defined routine?
No	Yes

Usage

The mi_xa_get_current_xid() function must be invoked from within the applicable transaction.

If you receive an error, check for any of the following problems:

Make sure that the mi_xa_get_current_xid() function is called from within the transaction.
Make sure that the mi_xa_get_current_xid() function is not called
- From the sub-ordinator of a distributed transaction.
- In a non-logging database

For more information about working with XA data sources, see the HCL OneDB™ DataBlade® API Programmer's Guide.

Return values

NULL: An error occurred while getting the resource manager ID.

Return values that are other than NULL are pointers to the current XID structure.