× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The reason that tracing as such is not implemented in RDi probably has a lot to do with the fact that tracing was not really implemented in ILE. Check out STRDBG and you'll see the trace parameters are available for OPM only.

There used to be a utility that could do statement tracing based on the debug APIs - but it seems to have disappeared into the ether with the demise of the iProDeveloper web site.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 25, 2018, at 9:26 AM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:

Dan,

You might was try the command: Start Trace (STRTRC). But, I don't recommend it... <smirk>
Not available in RDI, they left that out for some strange reason. I assume it has a high overhead usage. My guess... :(

Using RDI, I often use "add breakpoint watch" to watch when a variable changes. And I often edit a break-point to break "When" a condition happens. For instance when my "counter" goes over 100. That is if I am using a counter variable.

ON the edit break-point, you can also put a frequency on the break point. Which is maybe why they did NOT put in the start-trace. With all those great debugging tools in RDI, I really don't need the trace. It was an absolute pain to me anyway! <grin>

Oh well, I hope you find this info helpful.

-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Dan
Sent: Wednesday, July 25, 2018 10:14 AM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>; RPG400-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Generate a list of every RPG statement executed in a job, in sequence of execution

(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
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.