Pinned topic DTCN/RDZ Question
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
When debugging online CICS COBOL program in RDZ 7.6, I set up CICS DTCN parameters (see attached screen shot one) as LoadMod::>CU(s) ==> MORW605 ::> * - This set up desn't trap the program in RDZ debug. When I set up differently like (see attached screen shot two) as LoadMod::>CU(s) * ==> ::> MORW605 - This set up works - RDZ traps the program. Question is what is the difference that first set up doesn't work and the other set up does work- anybody knows? Thanks.
Updated on 2013-02-23T00:39:16Z at 2013-02-23T00:39:16Z by akkina9
akkina9 060000N0Y6124 Posts
Re: DTCN/RDZ Question2013-02-23T00:39:16ZThis is the accepted answer. This is the accepted answer.I suspect your Load module name is not MORW605, instead you have a load module with MORW605 as a compile unit in it. Typically a load module can have one or more compile units. So MORW605 ::> * means any compile unit in Load module MORW605 is enabled for debugging. And * ==> ::> MORW605 means any load module with MORW605 as the compile unit will be debugged. For more information about "LoadMod::>CU(s)" option, look at http://pic.dhe.ibm.com/infocenter/pdthelp/v1r1/index.jsp?topic=%2Fcom.ibm.debugtool.doc_11.1%2Frfieldsondtcnprimarymenu.htm
FYI: From RDz 761 onwards, RDz offers setting up of DTCN profile to debug CICS applications from RDZ user interface (i.e. you no longer have to go to the green screen to set it up). For more info, you can look at http://pic.dhe.ibm.com/infocenter/ratdevz/v7r6/topic/com.ibm.etools.zide.cmn.doc/topics/czdcicsdebug.html