The indoubt attributes of the transaction definition
You can control the action that CICS® takes after a communication failure during the indoubt period by specifying indoubt attributes when you define the transaction, using the WAIT, WAITTIME, and ACTION attributes of the TRANSACTION resource.
These options are honored when communication is lost with the coordinator and the UOW is in the indoubt period.
- WAIT({YES|NO})
- Specifies whether or not a unit of work is to wait, pending recovery
from a failure that occurred after it had entered the indoubt period,
before taking the action specified by ACTION.
- YES
- The UOW is to wait, pending recovery from the failure, to resolve its indoubt state and determine whether recoverable resources are to be backed out or committed. In other words, it is to be shunted.
- NO
- The UOW is not to wait. CICS takes immediately whatever action is specified on the ACTION attribute.
Note: The setting of the WAIT option can be overridden by other system settings—see TRANSACTION definition attributes. - 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 unit of work releases locks within a reasonable time.
- ACTION({BACKOUT|COMMIT})
- Specifies
the action to be taken when communication with the coordinator of
the unit of work is lost, and the UOW has entered the indoubt period.
- BACKOUT
- All changes made to recoverable resources are backed out, and the resources are returned to the state they were in before the start of the UOW.
- COMMIT
- All changes made to recoverable resources are committed and the UOW is marked as completed.
The action is dependent on the WAIT attribute. If WAIT specifies YES, ACTION has no effect unless the interval specified on the WAITTIME option expires before recovery from the failure.
Whether you specify BACKOUT or COMMIT is likely to depend on the kinds of changes that the transaction makes to resources in the remote system—see Specifying indoubt attributes—an example.

