File Formats, Data Descriptions, MIBs, and System Processes Reference
The T_APPQTRANS
class represents run-time attributes of transactions associated with application queues.
It is not possible to retrieve all instances of this class by leaving all key fields unset. Instead, sufficient key fields must be specified to explicitly target a single application queue space. For example, if all key fields except TA_XID
are set in an request using tpcall()
, all T_APPQTRANS
objects associated with the specified queue space will be retrieved.
It is important to keep in mind that transactions represented by objects of this class are not necessarily associated with the application in which they are retrieved. Care must be taken when heuristically committing or aborting a transaction because the transaction may actually belong to or have an effect on another application. The value of the TA_XID
attribute is not guaranteed to be unique across applications.
T_APPQTRANS
are local attributes.T_APPQTRANS
objects—both GET
and SET—
silently open the associated queue space (that is, implicitly set the state of the queue space to OPEn
if it is not already OPEn
or ACTive
). This may be a time-consuming operation if the queue space is large.GET
operation to explicitly target a single application queue space.Transaction identifier as returned by tx_info()
and mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.
GET
: {ACTive
| ABortonlY
| ABorteD
| COMcalled
| REAdy
| DECided
| HAbord
| HCommit
}
A GET
operation retrieves run-time information about the selected transactions. The following list describes the meaning of the TA_STATE
attribute returned in response to a GET
request. All states are ACTive
equivalent for purposes of permissions checking.
A SET
operation updates the state of the selected transactions. The following list describes the meaning of the TA_STATE
attribute returned by a SET
request. States not listed cannot be set.
Heuristically abort the transaction. Successful return leaves the object in the |
|
Heuristically commit the transaction. Successful return leaves the object in the |