Previous Topic: Example: DCMT DISPLAY DISTRIBUTED TRANSACTION CommandNext Topic: DCMT DISPLAY FILE Command

DCMT DISPLAY Commands › DCMT DISPLAY DISTRIBUTED TRANSACTION Command › DCMT DISPLAY DISTRIBUTED TRANSACTION Command Usage

DCMT DISPLAY DISTRIBUTED TRANSACTION Command Usage

Output from DCMT DISPLAY DISTRIBUTED TRANSACTION

The following summary information is shown for distributed transactions included in this display.

Field

Value

Task/LTE

The task or logical terminal element associated with the transaction. If an active task is processing the transaction, the task ID is shown. If a logical terminal but no task is associated with the transaction, the LTE's ID is shown. A distributed transaction that is pending resynchronization or pending completion by RRS or an XA transaction manager may have no associated task or logical terminal.

Distributed transaction ID

The distributed transaction ID (DTRID) assigned to the transaction.

Branch ID

The identifier of the top-level branch of the transaction.

Ctrl

The type of the transaction manager, or coordinator, that controls the transaction. Possible types are:

  • IDMS—CA IDMS
  • RRS—RRS
  • XA—XA transaction manager
  • CICS—CICS system

State

The state of the transaction. Possible states are:

  • Reset—InReset
  • InFl—InFlight
  • InPrp—InPrepare
  • InDbt—InDoubt
  • LstAg—LastAgent
  • InBck—InBackout
  • InCmt—InCommit
  • Forg—Forgotten

Ind

An indication of whether this transaction is pending resynchronization. Possible values are:

  • Rsy—The transaction is pending resynchronization
  • Rst—The transaction was restarted and is pending resynchronization

Outcome

The transaction's outcome to date. Possible outcomes are:

  • OK—OK
  • OK_P—OK_Pending
  • FGT—Forget
  • BACK—Backout
  • BK_P—Backout_Pending
  • HC—Heuristic Commit
  • HM—Heuristic Mixed
  • HR—Heuristic Reset

Output from DCMT DISPLAY DISTRIBUTED TRANSACTION ID/XID/BID

The detail displayed for a distributed transaction includes information on each of the branches comprising the transaction. A transaction always has one top-level branch and may or may not have subordinate branches.

The information listed below is displayed for a top-level branch. See the description above of the summary output for details on each of these fields:

Field

Value

Task/LTE

The task or logical terminal element that is associated with the transaction.

Res indicator

Indicates if this this transaction is pending resynchronization. Possible values are:

  • Rsy—The transaction is pending resynchronization
  • Rst—The transaction was restarted and is pending resynchronization

Distr. tr. ID

The distributed transaction id (DTRID) assigned to the transaction.

Control

The type of the transaction manager, or coordinator, that controls the transaction. Possible types are:

  • IDMS—CA IDMS
  • RRS—RRS
  • XA—XA transaction manager
  • CICS—CICS system

Branch ID1

The identifier assigned to the branch.

State1

The state of the transaction. Possible states are:

  • Reset—InReset
  • InFl—InFlight
  • InPrp—InPrepare
  • InDbt—InDoubt
  • LstAg—LastAgent
  • InBck—InBackout
  • InCmt—InCommit
  • Forg—Forgotten

Local ID1

The local transaction ID (LID) if database access is performed under control of the branch.

Outcome1

The transaction's outcome to date. Possible outcomes are:

  • OK—OK
  • OK_P—OK_Pending
  • FGT—Forget
  • BACK—Backout
  • BK_P—Backout_Pending
  • HC—Heuristic Commit
  • HM—Heuristic Mixed
  • HR—Heuristic Reset

External ID1

The external identifier assigned to the transaction branch if applicable. :tnote. 1—This information is displayed for all transaction branches. :etnote.

Information on interests

For each interest in the branch that has been registered by the resource manager, the following information is provided:

Field

Value

Controlling Interest

An indication of whether this is a controlling interest. A controlling interest is one that was registered by the transaction's coordinator.

RM-name

The name of the resource manager that registered the interest.

Role

The role the associated resource manager plays within the transaction. Possible values are:

  • SDSRM—Server Distributed Resource Manager
  • CRM—Communications Resource Manager
  • PART—Participant

Interest state

The state of the interest.

Protocol

The commit protocol used by the resource manager. Possible values are:

  • Presumed Abort
  • Presumed Nothing

One phase commit

If the resource manager supports a one-phase commit protocol. Possible values are:

  • Supported—Indicating that the resource manager is capable of processing a one-phase commit request.
  • Not Supported—Indicating that the resource manager is not capable of processing a one-phase commit request.
  • Only—Indicating that the resource manager is only capable of supporting a one-phase commit request.

Journal

Specifies if the interest is journaled.

Resync

Specifies if resynchronization is pending with the interest's resource manager.

Manual

Specifies if the transaction must be completed manually, due to a resynchronization failure.

Restart

Specifies if the interest was restarted following an abnormal system termination.

More Information

For more information about the following topics, see the Database Administration Guide: