View previous topic :: View next topic
|
Author |
Message |
kinatingopi
New User
Joined: 30 Apr 2014 Posts: 6 Location: USA
|
|
|
|
Hi,
I have a CICS program and corresponding transaction which gets executed from a batch program. How can I get control of execution of this CICS program to see why its abending.
Is there a way, when a CICS program is called from a batch program within xpediter, I get control of the CICS program in xpediter or CICS itself? I put a break point in CICS program, but didnt get control. Is there a way I get control across terminals?
Thanks,
Gopi |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
You can always add displays and check corresponding CICS region job to see the cause.
We can intercept in Xped. May be the control did not even cross the break point in your case. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
don't have access to manual or mf but,
in cics xped, you can trap a transaction or module
by putting all * (e.g. ***********) in the terminal name field on the screen.
but, be sure you are the only one testing, you will catch all invocations of the trans/module.
i think it is menu option 0.6 but I don't remember. you will have to explore.
the * trick was not ever documented (as of 2012 when I last worked) but it works.
putting DISPLAYs in a cics module used to be a no-no
if for no other reason, all the background shit that it started.
MY OPINION - if you have xped, you certainly do not need displays for debugging- batch or cics. |
|
Back to top |
|
|
kinatingopi
New User
Joined: 30 Apr 2014 Posts: 6 Location: USA
|
|
|
|
Thank you all... putting ** in the terminal ID worked. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
thx for the feedback, glad I was able to help.
what are the menu options, by the way? |
|
Back to top |
|
|
|