Setting a single transaction indoubt

About this task

If you want a single transaction to go indoubt regardless of its transaction class, an application can link to program DFHINDAP. (No commarea is required in this case.) This causes that single transaction to go indoubt without the need to type CIND ON. This single transaction can be resynchronized by typing CIND RESYNC COMMIT, and so on, as described in Running the CIND indoubt tool.

DFHINDAP works by enabling the indoubt task-related user exit if necessary and then issuing an API call to the indoubt task-related user exit to add the dummy coordinator. This has the advantage of allowing a test application to decide it wants to force indoubt dynamically, after it has started. Hence a UOW, other than the first one in the transaction can be forced indoubt.



dfha74m.html | Timestamp icon Last updated: Monday, 5 June 2017