1) Can CEDF be specific at the program level/ Transaction level. For example i want to debug a program which come in between appliaction and it needs to stop when the program is called? is any facility.
2) I came to know CEDX can be specified with transaction level . Can any one please send me the screen shots regarding how to onvoke / advantages . Can it be specific at the program level.
Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
CEDF (Terminal Oriented) and CEDX (Transaction Oriented) are used to debug programs, displaying (stopping at) EXEC CICS commands only.
The program defined to the transaction will always be your starting point.
When you say "CALL" to you mean "LINK"? If is is "CALL" then you cannot debug the called-program. If the called program issues EXEC CICS commands then they'll be displayed.
Using CEDx, you have the ability to stop at a particular CICS command <PF9>, display working-storage <PF5> or suppress displays <PF4>. If you're displaying working-storage, press <PF4> and the current EIB will be displayed. You can also invoke CECI, providing you have authority. Depending on the screen, <PF3> will terminate your session and take you out of CEDx completely.
CEDF and CEDX are both well documented in the applicable CICS manuals.
Note that CEDX was introduced with CICS/ESA 4.1, whereas, CEDF has been around since the inception of command-level CICS.
Remember, using CEDX ties-up all tasks associated with the transaction you're trying to debug, whereas, CEDF ties-up the transaction running on your terminal-id or different terminal-id (if you're debugging a transaction running on another user's terminal).
You'd invoke that via : CEDF tttt (tttt is the target terminal)
To exit CEDF debugging : CEDF tttt,OFF
IMHO, a CICS application programmer should know the basics of using CEDx.