Registering and Unregistering XA-Compliant Data Sources

After you create an external XA-compliant data source, 3transactions can register and unregister the data source using the mi_xa_register_xadatasource( ) or ax_reg( ) and mi_xa_unregister_xadatasource( ) or ax_unreg( ) functions.

The mi_xa_register_xadatasource( ) function 3and the ax_reg( ) function both register XA-compliant, 3external data sources. However, these functions use different parameters 3and have different return values.

Similarly, the mi_xa_unregister_xadatasource( ) and ax_unreg( ) functions 3perform the same operation, but use different parameters and have 3different return values.

Unlike SQL CREATE operations, which create entries in system 3catalog tables, registration is transient, lasting only for the 3duration of the transaction. A transaction must be started, implicitly 3or explicitly, before the application can register the XA data source.

In a distributed environment, you must register a data source 3using the local coordinator server.

Multiple registrations of the same XA data source in a transaction 3have the same effect as a single registration. Dynamic Server does 3not maintain a count of the number of times an application has registered. 3A single call to ax_unreg( ) or mi_xa_unregister_xadatasource( ) unregisters 3the data source from the transaction.