Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference

File Formats, Data Descriptions, MIBs, and System Processes Reference

T_TRANSACTION Class Definition

Overview

The T_TRANSACTION class represents run-time attributes of active transactions within the application.

Attribute Table

Table 62 TM_MIB(5): T_TRANSACTION Class Definition Attribute Table

Attribute¹	Type	Permissions	Values	Default
`TA_COORDLMID`(k)	string	`R--R--R--`	`LMID`	N/A
`TA_LMID`(k)	string	`R--R--R--`	`LMID`	N/A
`TA_TPTRANID`(*)	string	`R--R--R--`	`string`[1..78]	N/A
`TA_XID`(*)	string	`R--R--R--`	`string`[1..78]	N/A
`TA_STATE`(k)	string	`R-XR-XR--`	`GET`: `"`{`ACT` \| `ABY` \| `ABD` \| `COM` \| `REA` \| `DEC` \| `SUS`}`"` `SET`: `"ABD"`	N/A N/A
`TA_TIMEOUT`	long	`R--R--R--`	1 <= `num`	N/A
`TA_GRPCOUNT`	long	`R--R--R--`	1 <= `num`	N/A
`TA_GRPINDEX`	long	`R--R--R--`	0 <= `num`	N/A
`TA_GRPNO`	long	`R--R--R--`	1 <= `num` < 30,000	(²)
`TA_GSTATE`	long	`R-XR-XR--`	`GET`: `"PREP\|PABT\|PCOM"` `SET`:"{`HCO\|HAB`}"	N/A N/A
`TA_GSTATE`	long	`R-XR-XR--`	`GET`: `"PREP\|PABT\|PCOM"` `SET`:"{`HCO\|HAB`}"	N/A N/A
(k)—`GET` key field (*)—`GET/SET` key, one or more required for `SET` operations

¹All attributes in the T_TRANSACTION class are local attributes.
²One or more TA_GRPNO and TA_GSTATE attribute values may be returned with each object of the T_TRANSACTION class. The attribute values for each of these attributes belonging to the particular object are the TA_GRPCOUNT number of occurrences beginning with the TA_GRPINDEX.

Attribute Semantics

TA_COORDLMID: LMID

Logical machine identifier of the server group responsible for coordinating the transaction.

TA_LMID: LMID

Retrieval machine logical machine identifier. Note that transaction attributes are primarily kept local to a site and coordinated via common transaction identifiers by transaction management servers (TMSs).

TA_TPTRANID: string[1..78]

Transaction identifier as returned from tpsuspend() mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

TA_XID: string[1..78]

Transaction identifier as returned from tx_info() mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

TA_STATE:

GET: "{ACTive | ABortonlY | ABorteD | COMcalled | REAdy | DECided |
SUSpended}"

A GET operation will retrieve run-time information for the selected T_TRANSACTION object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) may indicate differing states. In general, the state indicated on the coordinator's site (TA_COORDLMID) indicates the true state of the transaction. The exception is when a non-coordinator site notices a condition that transitions the transaction state to ABortonlY. This transition will eventually be propagated to the coordinator site and result in the rollback of the transaction, but this change may not be immediately reflected on the coordinator site. All states are ACTive equivalent for the purpose of determining permissions.

`PREPrepare`	Indicates that the transaction group contains servers that have called `xa_end` (`TMSUSPEND`) during the course of transactional work and that commit processing is beginning. This state will exist until either all servers that called `xa_end` (`TMSUSPEND`) have caused a call to `xa_end` (`TMSUCESS`), at which point the group state will become `READy`, or until one of the target servers does a rollback of the transaction at which point the group state will become either `PostABorT` or `ABorteD`.
`PostABorT`	Indicates that a server called `xa_end` (`TPFAIL`) and that the TMS has not yet called `xa_rollback`(). (that is, that other servers that had called `xa_end` (`TMSUSPEND`) are being notified by the TMS in order to clean up their associated CORBA objects.
`PostCOMmit`	Not yet implemented.

SET: "{ABorteD}"

A SET operation will update run-time information for the selected T_TRANSACTION object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

`unset`	Modify an existing `T_TRANSACTION` object. This combination is allowed only when in the `REAdy` state and only for the purpose of updating an individual group's state (see `TA_GSTATE` below). Successful return leaves the object state unchanged.
`ABorteD`	Abort the `T_TRANSACTION` object for the application. State change allowed only when in the `ACTive`, `ABortonlY`, or `COMcalled` states. Successful return leaves the object in the `ABorteD` state.

TA_TIMEOUT: 1 <= num

Time left, in seconds, before the transaction will timeout on the retrieval site. Note that this attribute value is returned only when the transaction state (TA_STATE) is ACTive.

TA_GRPCOUNT: 1 <= num

Number of groups identified as participants in the transaction by the information returned from the retrieval site.

TA_GRPINDEX: 1 <= num

Index of the first group specific attribute values (TA_GRPNO and TA_GSTATE) corresponding to this object.

TA_GRPNO: 1 <= num < 30,000

Group number of the participating group.

TA_GSTATE:

GET: "{ACTive | ABorteD | ReaDOnly | REAdy | HCOmmit | HABort | DONe}"

A GET operation will retrieve run-time information for the selected T_TRANSACTION object(s) pertaining to the indicated group. The following states indicate the meaning of a TA_GSTATE returned in response to a GET request. States not listed will not be returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) may indicate differing states for individual groups. In general, the state indicated on the group's site indicates the true state of the group's participation in the transaction. The exception is when the coordinator site determines that the transaction should abort and sets each participant group state to ABorteD. This transition will be propagated to the group's site and result in the rollback of the group's work in the transaction but may not be reflected immediately.

`ACTive`	The transaction is active in the indicated group.
`ABorteD`	The transaction has been identified for rollback and rollback has been initiated for the indicated group.
`ReaDOnly`	The group has successfully completed the first phase of two-phase commit and has performed only read operations on the resource manager, thus making it unnecessary to perform the second phase of commit for this group.
`REAdy`	The group has successfully completed the first phase of two-phase commit and is ready to be committed.
`HCOmmit`	The group has been heuristically committed. This may or may not agree with the final resolution of the transaction.
`HABort`	The group has been heuristically rolled back. This may or may not agree with the final resolution of the transaction.
`DONe`	This group has completed the second phase of the two-phase commit.

SET: "{HCOmmit | HABort}"

A SET operation will update run-time information for the first group in the originating request within the selected T_TRANSACTION object. The following states indicate the meaning of a TA_GSTATE set in a SET request. States not listed may not be set. State transitions are allowed only when performed within the object representing the group's site (TA_LMID).

`HCOmmit`	Heuristically commit the group's work as part of the indicated transaction. State change allowed only when `TA_GSTATE` is `REAdy`, `TA_STATE` is `REAdy`, and the indicated group is not on the coordinator's site. Successful return leaves the object in the `HCOmmit` state.
`HABort`	Heuristically rollback the group's work as part of the indicated transaction. State change allowed only when `TA_GSTATE` is `ACTive` or `REAdy`, `TA_STATE` is `REAdy`, and the indicated group is not on the coordinator's site. Successful return leaves the object in the `HABort` state.

Limitations

None.