Re: Generate a list of every RPG statement executed in a job, in sequence of execution

[Peter Dow <petercdow@xxxxxxxxx>]

This isn't going to help your situation, but in ye olden tymes, (i.e. 
for OPM programs), when you start debug you can specify MAXTRC and 
TRCFULL parameters. When the program is done, DSPTRCDTA *|*PRINT to see 
each of the statements that were executed.

However, according to the help, it's only available for OPM programs, 
and there's no hint of anything like it for ILE.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 7/25/2018 7:13 AM, Dan wrote:
> (cross-posted to WDSC-L, RPG400-L)
>
> I was banging my head trying to debug a program yesterday.  Stepping
> through the RDi debugger was slow and tedious.
>
> Is there something in RDi or some other system command that will generate a
> list of every RPG statement executed in a job, in sequence of execution?  I
> think I understand that code coverage will show a summary of this; line
> 100.00 executed 20 times, line 101.00 executed 5 times, etc. But I'm
> looking for
>
> 0435.00       Dou %eof( CA8555RwL1);
> 0436.00         Reade #142AcctID CA8555RwL1;
> 0437.00         If not %eof( CA8555RwL1);
> 0438.00           y += 1;
> 0439.00           #142Pat(y) = w_su_PatID;
> 0440.00           #142Crg(y) = w_su_CrgID;
> 0442.00           If y = #maxCA0142Rparmarrayelements;
> 0446.00           Endif;
> 0447.00         Endif;
> 0448.00       Enddo;
> 0435.00       Dou %eof( CA8555RwL1);
> 0436.00         Reade #142AcctID CA8555RwL1;
> 0437.00         If not %eof( CA8555RwL1);
> 0438.00           y += 1;
> 0439.00           #142Pat(y) = w_su_PatID;
> 0440.00           #142Crg(y) = w_su_CrgID;
> 0442.00           If y = #maxCA0142Rparmarrayelements;
> 0443.00             Exsr Call_CA0142R_Update_CA8555RwL1;
> 0444.00             Clear CA0142Rout;
> 0445.00             y = 0;
> 0446.00           Endif;
> 0447.00         Endif;
> 0448.00       Enddo;
>
> I'm looking for at least the source line numbers.  Bonus if the code is
> included.
>
> - Dan