RE: Tracing statements executed in debug

Actually, it's a little more complicated than that.  This is a
2800-line Cobol program which uses "PERFORM par1 THROUGH par9-exit".
I'm not an expert on Cobol, but I believe Cobol will "perform" every
paragraph beginning from par1 and (through) par9-exit.  It's more
difficult than isolating an RPG subroutine call.

But your advice will be useful in the future, as I had not considered
that idea before.

Thanks, Dan

--- Joel Fritz <JFritz@sharperimage.com> wrote:
> If it's a subroutine or procedure, you might consider setting
> breakpoints at
> every point in the program it's called and just going with the
> interactive
> debug.  I've done that more times than I care to admit. <g>
>
> > -----Original Message-----
> > From: Dan [mailto:dbcemid@yahoo.com]
> > Sent: Tuesday, December 17, 2002 10:10 AM
> > To: midrange-l@midrange.com
> > Subject: Re: Tracing statements executed in debug
> >
> >
> > > Have you considered using interactive debug instead?  I almost
> > > _always_ use
> > > interactive debug now, instead of trace...
> > Me too.  But I needed to be able to see where a particular piece of
> > code was being called from and, since it was "callable" from many
> > different points in the program, interactive debug would not have
> > allowed me to trace "backwards" from where I would set a
> breakpoint.
> >
> > You gave me the clue as to what I was doing wrong.  I was
> specifying
> > OPMSRC(*YES) on the STRDBG command, which puts debug in the ILE
> > environment, and that's why I wasn't getting any trace data.  So,
> this
> > is a case of not being able to have your cake and eat it too.
> >
> > BTW, in the scenario I described where tracing statements is
> required,
> > how would one accomplish that with an ILE program?
> >
> > - Dan

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com