Using supplied transactions and EDF
You can use CICS-supplied transactions or the execution diagnostic facility (EDF) to find out whether a transaction started successfully.
Debug nonterminal transactions
You can use CEDX to debug nonterminal transactions. CICS intercepts the transaction specified on the CEDX tranid command, and displays the EDF diagnostic panels at the terminal at which the EDF command is issued. CEDX provides the same function and diagnostic display panels as CEDF, and the same basic rules for CEDF also apply to CEDX.
Debug transactions from a terminal
CEDF tttt
At
the remaining terminal, enter the transaction, or sequence of transactions,
that initiate the transaction that is being tested. Wait long enough
for the transaction to start. If no output appears at the second terminal,
the transaction has not started. If you have not yet done so, consider
using trace to get more information about the failure.Debug transactions that use TD queues or TS queues
You can use CEBR to investigate your transaction if the transaction reads or writes to a transient data queue, or writes to a temporary storage queue. A change in such a queue is strong evidence that the transaction ran, provided that the environment is sufficiently controlled that nothing else could produce the same effect.
You must be sure that no other transaction that might be executed while you are doing your testing performs the same action. The absence of such a change does not mean that the transaction did not run; it might have run incorrectly, so that the expected change was not made.
Debug transactions that write to files
If your transaction writes to a file, you can use CECI before and after the transaction to look for evidence of the execution of your transaction. A change in the file means the transaction ran. If no change occurred, that does not necessarily mean that the transaction failed to run; it could have worked incorrectly, so that the changes you were expecting were not made.