DB2 Version 9.7 for Linux, UNIX, and Windows

LIST DRDA INDOUBT TRANSACTIONS command

Provides a list of transactions that are indoubt between DRDA® requesters and DRDA servers. If DRDA commit protocols are being used, lists indoubt transactions between DRDA sync point managers.

Authorization

None

Required connection

Instance

Command syntax

Read syntax diagramSkip visual syntax diagram
>>-LIST DRDA INDOUBT TRANSACTIONS--+----------------+----------><
                                   '-WITH PROMPTING-'   

Command parameters

WITH PROMPTING
Indicates that indoubt transactions are to be processed. If this parameter is specified, an interactive dialog mode is initiated, permitting the user to commit or roll back indoubt transactions. If this parameter is not specified, indoubt transactions are written to the standard output device, and the interactive dialog mode is not initiated.

A forget option is not supported. Once the indoubt transaction is committed or rolled back, the transaction is automatically forgotten.

Interactive dialog mode permits the user to:
  • List all indoubt transactions (enter l)
  • List indoubt transaction number x (enter l, followed by a valid transaction number)
  • Quit (enter q)
  • Commit transaction number x (enter c, followed by a valid transaction number)
  • Roll back transaction number x (enter r, followed by a valid transaction number).

A blank space must separate the command letter from its argument.

Before a transaction is committed or rolled back, the transaction data is displayed, and the user is asked to confirm the action.

Usage notes

DRDA indoubt transactions occur when communication is lost between coordinators and participants in distributed units of work. A distributed unit of work lets a user or application read and update data at multiple locations within a single unit of work. Such work requires a two-phase commit.

The first phase requests all the participants to prepare for a commit. The second phase commits or rolls back the transactions. If a coordinator or participant becomes unavailable after the first phase, the distributed transactions are indoubt.

Before issuing the LIST DRDA INDOUBT TRANSACTIONS command, the application process must be connected to the DB2® sync point manager (SPM) instance. Use the spm_name database manager configuration parameter as the dbalias on the CONNECT statement.

TCP/IP connections, using the SPM to coordinate commits, use DRDA two-phase commit protocols.