Re: Tracing statements executed in debug -- MIDRANGE-L

Can't be done....look at the help text for the ADDTRC command...

<snipfromhelptext

Restrictions:

 o   You can use this command only in debug mode.  To start debug
     mode, refer to the Start Debug (STRDBG) command.

 o   You cannot use this command if you are servicing another job,
      and that job is on a job queue, or is being held, suspended, or
      ended.

o   You cannot use this command to trace bound programs.

/snipfromhelptext>

Steve

----- Original Message -----
From: "Dan" <dbcemid@yahoo.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, December 17, 2002 12:09 PM
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
>
> --- Steve Landess <steve_landess@hotmail.com> wrote:
> > Dan -
> >
> > What kind of program is PC8741ICXX?
> >
> > If it is an ILE program, you cannot trace it.  ILE programs cannot be
> > traced.   If it is an OPM program, you _can_ trace it, but all you
> > will get
> > out of the trace is statement numbers.
> >
> > Procedure for producing trace from a program:
> >
> > 1)  Start debug like indicated in your message
> > 2)  Add a trace using ADDTRC
> > 3)  Run the program
> > 4) Use DSPTRCDTA OUTPUT(*PRINT) to display the trace data after
> > running the
> > program to display the trace data to a report
> > 5) RMVTRC *ALL
> > 6) ENDDBG
> >
> > Have you considered using interactive debug instead?  I almost
> > _always_ use
> > interactive debug now, instead of trace...
> >
> > Steve Landess
> > Austin, Texas
> > (512) 423-0935
> >
> > ----- Original Message -----
> > From: "Dan" <dbcerpg@yahoo.com>
> > To: <rpg400-l@midrange.com>
> > Sent: Tuesday, December 17, 2002 10:59 AM
> > Subject: Tracing statements executed in debug
> >
> >
> > > Wondering if there is a way to trace the statements run in a
> > program so
> > > that I can see where a particular subroutine was called from.  I
> > tried
> > > using:
> > >   STRDBG PGM(DEVDB/PC8741ICXX) MAXTRC(32767) TRCFULL(*WRAP)
> > > UPDPROD(*YES) OPMSRC(*YES)
> > > but am unable to determine how to see the results of the trace.  I
> > have
> > > gone to the CMDTRC menu and tried various commands, but am coming
> > up
> > > empty.
> > >
> > > Since I anticipate that the trace will show only statement numbers,
> > it
> > > would be nice to be able to see the trace results with the code
> > that
> > > was executed.  Anybody doing this?
> > >
> > > TIA, Dan
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>