Indoubt options for distributed transactions

When you define user transactions that update remote resources, you can specify options for remote recovery purposes.

The options that you can specify are as follows:

ACTION({BACKOUT|COMMIT})
Specifies the action to be taken when a failure occurs during two-phase commit processing, after the unit of work has entered the indoubt period.

If you specified WAIT(YES), the action is not taken unless the interval specified on WAITTIME expires before recovery occurs.

Whether you specify BACKOUT or COMMIT is likely to depend on the kinds of changes made to resources in the remote system.

WAIT({YES|NO})
Specifies whether a failed indoubt unit of work is to wait, pending recovery from the failure, to resolve its indoubt state, or whether CICS® is to take immediately the action specified by the ACTION option.
Note: A WAIT(YES) option can be overridden by WAIT(NO) defined on an intrapartition transient data queue. If a TD queue that is access by a transaction specifies WAIT(NO), and the transaction specifies WAIT(YES), the TD queue definition forces the transaction to either backout or commit, as specified by the ACTION attribute on the transaction resource definition.
WAITTIME({00,00,00|dd,hh,mm})
Specifies, if WAIT(YES), how long the transaction is to wait before taking the action specified by ACTION.

You can use WAIT and WAITTIME to allow an opportunity for normal recovery and resynchronization to take place, while ensuring that a transaction commits or backs out within a reasonable time. For information about defining wait times for distributed transactions, see The indoubt attributes of the transaction definition.

For more information about recovery of distributed units of work, see Troubleshooting intersystem problems.

For more information about options on the TRANSACTION definition, see TRANSACTION attributes.



dfht2c00167.html | Timestamp icon Last updated: Sunday, 4 June 2017