ILE debug problems

[JeffWilson]

Sorry, but I am new to ILE...why can't I debug an ILE program like a normal RPG? The source debugger comes up, but it won't let me ADDTRC or any of my other favorite debug commands (I know I can add a breakpoint, or conditional breakpoint). Can someone tell me how to trace these pgms? Thanks very much!

Jeff Wilson

 

[slandess]

Get used to not using trace with ILE programs! (see below).

Why not use single step mode (F10) when debugging the ILE program to step thru the program, OR set a breakpoint at a good starting point, then use F10 to step thru the program from the breakpoint.

I have not used JDEDBG OR trace data (ADDTRC) to debug an OPM program since IBM came out with STRISDB. When using STRISDB to debug, F5 is used for single-stepping thru an OPM pgm. I have found that is much easier to debug a program this way than trying to read a trace listing and try to determine the path taken thru the code.

--------------------------------------------------------------------------
From the help text for ADDTRC:

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.

Hope this helps....

 

[JeffWilson]

Steve

Thanks very much. I did exactly what you said about setting a bkp and
stepping. But nothing beats tracing. I find it to be 1,000 times easier than
what I went thru today! But thanks for the info!

Jeff

 

[jdepro]

Steve is RIGHT, its a LOT easier to see the actual path as the code is executed.