Re: RPGLE SEP Debugging of a program that has many functions

On 8/28/2013 2:18 PM, Gerald Kern wrote:

We have several RPGLE programs that contain numerous calls to bound
functions, procedures, sub-procs etc, and often when using SEP to debug a
program, when attempting to step into any of these via F5, the source for
the object being stepped into may not display properly. Sometimes in the
debug view it is necessary to right click on the white space and select
show *listing but often that option is greyed out, unless I actually open
the source in RDi and recompile it first.

so if all of our *modules information shows debug data = *yes why do I
still need to open the source and recompile everything just to enable
viewing the source code properly during a debug session?

I *think* the 'debug data = yes' is different to the DBGVIEW setting
that was in effect at the time the module was compiled. Which is to say
that it'll say yes even if you have DBGVIEW(*STMT) (the default).

Or is there a preference setting that might be of help here? I'm using RDi
V9.0.0.1 but this is something that has been happening for as long as I can
remember.

I have my RDi compile commands set so I always get the debug view I
want. For instancd,
CRTBNDRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R)
OPTION(*EVENTF) DBGVIEW(*LIST)

or, for SQL:
CRTSQLRPGI OBJ(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
RPGPPOPT(*NONE) REPLACE(&R) TOSRCFILE(*CURLIB/QSQLTEMP1)
COMPILEOPT('DBGVIEW(*LIST)')

--buck