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 ax_unreg() functionThe ax_unreg() function allows DataBlade® modules or applications using user-defined routines (UDRs) to unregister previously registered XA-compliant, external data sources (also called resource managers) from transactions.

The ax_unreg() function

The ax_unreg() function allows DataBlade® modules or applications using user-defined routines (UDRs) to unregister previously registered XA-compliant, external data sources (also called resource managers) from transactions.

Syntax

int ax_unreg(int rmid,
                               int4 flags)

rmid: The resource manager ID.
flags: Must be set to TMNOFLAGS. The value for TMNOFLAGS is defined in the $INFORMIXDIR/incl/public/xa.h file.


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

Usage

The ax_unreg() function unregisters an XA data source from the transaction in which it was previously registered. By default, all XA-compliant external data sources are unregistered at the end of a transaction. Use the ax_unreg() function to unregister the XA data source before the end of the transaction so the data source does not participate in the transaction.

Multiple registrations of the same XA data source in a transaction have the same effect as a single registration. Since HCL OneDB™ does not maintain a count of the number of times an application has registered, a single call to ax_unreg() unregisters the data source from the transaction.

The resource manager ID must be present in a row in the ’informix’.sysxadatasources system catalog table that was created with this SQL statement:

CREATE XADATASOURCE datasourcename USING xadstype

An application can use the mi_xa_get_xadatasource_rmid() function to get the resource manager ID.

When the ax_unreg() function is called, you must set flags to TMNOFLAGS.

If the function call is successful, the function returns TM_OK. If the function call is not successful, an error appears.

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

Make sure the rmid value is correct.
Make sure the flags passed as TMNOFLAGS.
Make sure that the ax_unreg() function is called from within the transaction.
Make sure that the ax_unreg() function is not called:
- From the subordinator of a distributed transaction.
- From within the resource manager global transaction.
- In a nonlogging database.
- From any of the XA purpose functions that are specified in a CREATE XADATASOURCE TYPE statement, which creates a type of XA-compliant external data source.
Make sure you are not unregistering an XA data source that is not registered.

The mi_xa_unregister_xadatasource() function also allows DataBlade modules to unregister previously registered XA-compliant, external data sources from transactions. However, the ax_unreg() function and the mi_xa_unregister_xadatasource() function use different parameters and have different return values.

For more information about working with XA data sources, see the HCL OneDB DataBlade API Programmer's Guide. Also refer to the "Distributed Transaction Processing: The XA Specification." This is the X/OPEN standard specification that is available on the Internet.

Return values

TM_OK: The value The data sources are unregistered.
TMER_TMERR: The value indicates that an error occurred and the function was not successful.
TMER_INVAL: The value indicates that invalid arguments were specified.
TMER_PROTO: The value The routine was invoked in an improper context.