CICS Debug Issue

We have an issue using IBM Debug with changeman ZMF generated CICS compiles. After promoting executables to our test CICS region, we are able to view source code, but cannot set breakpoints or step thru the code. Is something missing in the CICS region startup job? Any ideas?

#ChangeManZMF

Hello. This was posted in the SBM forum. I'll change the category to ChangeMan ZMF.

We have an issue using IBM Debug with changeman ZMF generated CICS compiles. After promoting executables to our test CICS region, we are able to view source code, but cannot set breakpoints or step thru the code. Is something missing in the CICS region startup job? Any ideas?

#ChangeManZMF

Thank you Richard.

We have an issue using IBM Debug with changeman ZMF generated CICS compiles. After promoting executables to our test CICS region, we are able to view source code, but cannot set breakpoints or step thru the code. Is something missing in the CICS region startup job? Any ideas?

#ChangeManZMF

In order to offer any suggestions on this, I need more information.What language is your CICS program and are you using LE? What version of the compiler is in use? and what compiler options are being specified? What version of z/OS and the Z/OS Debug Tool are in use.Are CICS programs compiled outside of ZMF able to have Debug breakpoints specified? Breakpoints are generally established by the compiler options in use to set runtime hooks. If CICS programs compiled outside of ZMF are are able to have breakpoints established then you may want to compare the compiler options in your ZMF specific JCL and your non ZMF compiler JCL. How are you invoking the Debug facility in CICS? DTCN transaction? David Jackson

We have an issue using IBM Debug with changeman ZMF generated CICS compiles. After promoting executables to our test CICS region, we are able to view source code, but cannot set breakpoints or step thru the code. Is something missing in the CICS region startup job? Any ideas?

#ChangeManZMF

Write a reply I have seen this before. The IBM DEBUG facility in COBOL hard codes the name of the DEBUG dataset in the Load Module. If the ChangeMan standard process is being followed where we create the DEBUG file in a temp dataset -- that is the dataset that is being stored inside the load module and since it is temproary its not there at execution time. I would think there is a way to override the dataset at test time but I am not aware of it and the customer I was working with wasn't either. The reason we store it in a temproary file is so BAT90 will get the right module associated with the source --. The work around we did was to create the DEBUG file directly in the package and then copy it out to a temporary dataset for BT90 analysis. I am sure we could have just created the control cards manually.