NAME

tkadmin list transactions - lists unresolved transactions in a server and their current state

SYNOPSIS

tkadmin list transactions -server servername [-originator application] [-participant application] [-global identifier]

ARGUMENTS

-server servername Specifies the server affected by the command. The server name is the name that is registered with the DCE Directory Service. If the server name is not specified in the command line, it is retrieved from an environment variable, ENCINA_TK_SERVER. 

[-originator application]
Specifies the application that initiated the transaction - that is, the application that issued the “begin tran” functionality.

[-participant application]
Specifies the participating application in the transaction.

[-global identifier] Specifies the global identifier for the transaction. 

DESCRIPTION

The tkadmin list transactions command lists the identities of unresolved transactions in a server and their current states. The state of an unresolved transaction is crucial when attempting to abort a transaction or to force an outcome. The state of the transaction can be one of the following:

active - The transaction is currently active in the server, that is, either the server has begun but not ended the transaction, or, it has received but not replied to an RPC for this transaction, or, a before-prepare callback is in progress that permits work to be done on this transaction. 

inactive - The transaction has been active before, but is no longer active. It is not legal to make RPCs on behalf of the transaction. It is legal to abort the transaction.  The transaction has not been aborted. The application must be prepared before the transaction can be committed. 

preparing - The recovery services in the server are being asked to prepare the transaction. A recovery service may do work as necessary to prepare, but no other work is permitted on behalf of the transaction. 

prepared - All recovery services in the server are prepared. Work on behalf of this transaction is not legal. 

committing - The recovery services are being informed that the transaction has committed. 

committed - All recovery services have committed the work associated with the transaction such that it can be observed by other transactions (after-resolution callbacks take place in this state). 

commit complete - The transaction has completed all commitment related actions. (Commit upcalls and after-resolution callbacks have been completed.) The transaction may not be finished because of heuristic damage reporting requirements or for transaction service protocol reasons. 

before abort - The transaction has aborted but recovery services have not been informed that the transaction is aborting. 

aborting - The recovery services are being informed that the transaction is aborting. 

aborted - All recovery services have aborted the work associated with the transaction such that no effects can be observed by other transactions (after-resolution callbacks take place in this state). 

abort complete - The transaction has completed all abort-related actions. (Abort upcalls and after-resolution callbacks have been completed.) The transaction may not be finished because of heuristic damage reporting reasons or for transaction service protocol reasons. 

finished - All transaction service functions have taken place for this transaction. (The after-finished callbacks take place in this state.) 

present - An RPC is in progress on behalf of this transaction, but no application module has registered to participate. 

none - The application has not participated in the transaction directly. The application has neither begun nor received an RPC for the transaction. The transaction identifier may have been obtained using the transaction relationship functions (parent, descendent, top ancestor), or from a recovery service upcall. It is not legal to perform work on behalf of the transaction. 

The (W) indicates that a transaction is blocked, waiting for a lock. The (H) indicates that a transaction is holding a lock.  Subtransaction states are shown indented beneath parent transactions. 

The following modifiers can be used to list specific unresolved transactions: the -originator option is used to specify the application that initiated the transaction; the -participant option is used to specify a participating application; and the -global option is used to specify the global identifier for the transaction. 

EXAMPLES

In the following example, transaction 29188 is inactive and waiting for one or more locks. Subtransaction 29937, in same transaction family as transaction 29188, is also inactive and waiting for one or more locks. Transaction 38766 is preparing (and now, cannot be aborted via the tkadmin abort transaction command). Transaction 65536 is active and is holding one or more locks.  Subtransaction 65992 is active and holding one or more locks; subtransaction 66452 is inactive and holding one or more locks. 

% tkadmin list transactions

29188 inactive (W)
29937 inactive (W)
38766 preparing
65536 active (H)
65992 active (H)
66452 inactive (H)

PRIVILEGE REQUIRED

Encina Monitor query (q) permission to the application server

Encina RQS query (q) permission to the RQS server

Encina SFS query (Q) permission to the SFS server

RELATED INFORMATION

tkadmin abort transaction

tkadmin force transaction

  —  March 1997