EDF and DTP programs
You can test a transaction that is using distributed transaction processing (DTP) across a remote link by telling execution diagnostic facility (EDF) to monitor the session on the link.
You can do this on either (or both) of the participating systems that are running under CICS and have EDF installed. You cannot do this if the transaction has been routed from another CICS region because you must use single-screen mode for remote transactions.
CEDF sysidThis causes EDF to associate itself with any transaction attached across any session belonging to the specified system.
CEDF sessionidYou can determine the session identifier with the INQUIRE TERMINAL command, but this means that the transaction must be running and must have reached the point of establishing a session before you start EDF.
If a transaction that uses distributed transaction processing also has a terminal associated with it, or if you can invoke it from a terminal (even though it does not use one), you can use EDF to test it in the usual way from that terminal.
CEDF sysid,OFFFailure to turn off EDF could cause another transaction that is using a link to that system to be suspended.
EDF and distributed program link commands
You can use EDF, in single- or dual-terminal mode, to test a transaction that includes a distributed program link (DPL) command. However, EDF displays only the DPL command invocation and response screens. CICS commands issued by the remote program are not displayed, but a remote abend, and the message a remote abend has occurred, is returned to the EDF terminal, along with the system identifier of the system from which the abend was received. After control is returned to your local program, EDF continues to test as normal, but the program status word (PSW) is not displayed if the abend is in a remote program.