View previous topic :: View next topic
|
Author |
Message |
kaustubhkhole
New User
Joined: 20 Oct 2008 Posts: 19 Location: Hyderabad
|
|
|
|
Hi All
Is there any way by which I can find the caller program name from the Callee program
For E.g.
If program A is calling program B.
Is there by any chance I can know the program which is calling B . Keeping a break point at B ?
I hope I am clear |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
|
|
|
|
Should we assume Xpediter since you're in the Compuware forum -- even though you didn't tell us little details like the tool, the language of the calling program, the language of the called program, and what you've already tried that hasn't worked? Have you tried Xpediter option 2.6.1? The Xpediter COBOL User's Guide talks about returning to the calling program -- read chapters 5.1 and 5.3 for more details. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
there is also the simple fact that if pgm b has been CALLed,
how did the TS/OP invoke this CALL? |
|
Back to top |
|
|
kaustubhkhole
New User
Joined: 20 Oct 2008 Posts: 19 Location: Hyderabad
|
|
|
|
I am Sorry for missing out on details..
You are correct .. I am using Xpediter to debug programs .. Both programs are in Cobol .. Forther it's an online program
It would be great if you could give me the link of COBOL User's Guide (Xpediter option 2.6.1)
The problem is that I am able to figure out that the control is going to B ..when I set a break point the flow halts at program B ... But I need to find which program is calling B .. |
|
Back to top |
|
|
Sam Davies
New User
Joined: 25 Jun 2009 Posts: 6 Location: UK
|
|
|
|
Hi,
So your are using Xpediter/CICS. Once you have stopped at a breakpoint you want to identify the calling program.
I would suggest you activate Xpediter's Trace function - this is option 1.4 from the primary menu.
Then set your breakpoint in the called program.
Then clear the screen and run your test. Once you stop at your breakpoint, look at the trace output - this is option 2.4 from the primary menu. This will give you a statement trace across all programs that were executed. Here you should see the calling program. NOTE: The trace will only record programs and statements for programs are available in the DDIO file. If you don't have a compile listing for a program, it will NOT appear in the trace.
Cheers.
Sam |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
Sam Davies wrote: |
NOTE: The trace will only record programs and statements for programs are available in the DDIO file. If you don't have a compile listing for a program, it will NOT appear in the trace. |
this is probably the most important part of the post. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
It would be great if you could give me the link of COBOL User's Guide (Xpediter option 2.6.1) |
If your organization is licensed to use the product, you can download it from Compuware Support:
frontline.compuware.com/ |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
I'm assuming you are accessing the sub-program via a CALL USING from the CALLER and NOT an EXEC CICS LINK?
Sometimes these terms are used synonymously and just wanted make sure.
Regards, |
|
Back to top |
|
|
kaustubhkhole
New User
Joined: 20 Oct 2008 Posts: 19 Location: Hyderabad
|
|
|
|
Sam Davies wrote: |
Hi,
So your are using Xpediter/CICS. Once you have stopped at a breakpoint you want to identify the calling program.
I would suggest you activate Xpediter's Trace function - this is option 1.4 from the primary menu.
Then set your breakpoint in the called program.
Then clear the screen and run your test. Once you stop at your breakpoint, look at the trace output - this is option 2.4 from the primary menu. This will give you a statement trace across all programs that were executed. Here you should see the calling program. NOTE: The trace will only record programs and statements for programs are available in the DDIO file. If you don't have a compile listing for a program, it will NOT appear in the trace.
Cheers.
Sam |
Hi Sam ... Could you please advice us on activating the Trace function
Thank you. |
|
Back to top |
|
|
mprobst
New User
Joined: 14 Oct 2006 Posts: 14 Location: Appleton Wi USA
|
|
|
|
SET TRACE ON will turn program tracing on.
Using option 0.1 you can see what is all set.
Also, it is NOT TRUE that you need a DDIO listing available for the programs to show up in the trace. Without the DDIO, you will not see the lines of code executed along the way, but you will still see the names of the programs that were executed. |
|
Back to top |
|
|
|