BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Documentation   |   Programming BEA Tuxedo ATMI Applications Using TxRPC   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

The TX functions provide an interface for transaction demarcation. tx_begin(3c) and tx_commit(3c) or tx_rollback(3c) encapsulate any work, including communications, within a transaction. Other primitives are provided to set transaction timeout, declare the transaction as chained or unchained, and retrieve transaction information. These are discussed in detail in the X/OPEN TX Specification, and reviewed in the X/OPEN TxRPC Specification. The X/OPEN TxRPC Specification indicates the interactions between TX and RPC. These are summarized as follows:

• An interface or an operation can have the [transaction_optional] attribute which indicates that if the RPC is called within a transaction, the work done in the called operation will be part of the transaction.

• An interface or an operation can have the [transaction_mandatory] attribute which indicates that the RPC must be called within a transaction or the txrpc_x_not_in_transaction exception is returned.

• If neither of these attributes is specified, then the work in the called operation is not part of any transaction that may be active in the caller.

• If a TxRPC operation is called in the server and tx_open(3c) has not been called, a txrpc_x_no_tx_open_done exception is returned to the caller.

• TxRPC allows tx_rollback(3c) to be called from an operation to mark the transaction as rollback-only, such that any work performed on behalf of the transaction will be ultimately rolled back. It is recommended in this case that the application also return an application-level error to the caller indicating that the transaction will be rolled back.