CIND--in-doubt testing tool

Use CIND to:

Note:
For a description of the concepts involved in the synchronization of distributed applications, including in-doubt periods and shunted UOWs, see the CICS® Intercommunication Guide.

CIND can operate in a standalone system; it provides a way of changing the UOW so that it is distributed, and of causing a failure during syncpoint processing in the in-doubt window.

It can be used to cause a failure in syncpoint processing as follows:

You can also use CIND to shunt a UOW that is genuinely distributed across multiple CICS systems. It must be activated on the CICS system where the syncpoint is initiated, so that it can assume the role of syncpoint initiator and coordinator before any other CICS systems try to do so. In particular, CIND should not be activated for CICS mirror transactions unless the mirror can be guaranteed to be the syncpoint initiator (that is, a mirror running a server transaction that has been DPLed to specifying SYNCONRETURN).

When active, CIND forces all transactions defined to be in a new transaction class, DFHTCIND, to fail in-doubt when they reach syncpoint.

Note:
You cannot use CIND on internal CICS system transactions. If you change a system transaction so that it is defined in transaction class DFHTCIND, CIND detects that it is to be used with a CICS system task, and issues message DFHIN1014 to CSMT. The system task continues to run and CIND does not cause it to fail in-doubt when it reaches syncpoint.

The required resource definitions for CIND are provided in group DFHINDT, which is a member of group list DFHLIST.

Related tasks
Using CICS supplied transactions
Running the CIND in-doubt tool
CIND Messages
[[ Contents Previous Page | Next Page Index ]]