Re: WDSCI-L Digest, Vol 13, Issue 39

On 1/23/2015 4:56 PM, Dale Janus wrote:

Thanks for the refresher on what things are called.

Heh, new terminology and jargon is slowly stealing what few brain cells
I have left :-)

I am debugging the main program and the SEP is open. It shows the last
two programs I debugged. It does NOT show the date routine program.
Yet when I run one of the two programs shown in the SEP, the date
routine program gets debugged. It does not show up in the SEP. (there
are 7 tabs in the view, console, tasks, debug console, etc. One of which
is IBM I service entry points.)

This is where I get lost. Shouldn't my date routine program that is
being debugged show up in the SEP view?

Dave Shaw understood you but I was slow on the uptake. The quick answer
is no, the date program won't show up in the SEP view. Dave covered
that in his post, but to reiterate:

If you start debugging MAIN and MAIN calls A, B and C, the debugger will
follow your code as it executes - even into those 3 programs you didn't
explicitly set up for debugging!

If you don't want to go into the date program, when the debugger gets to
the CALL DATEPGM operation, step over it rather than stepping into it.

I'm a keyboard guy, so I know the keystrokes better than the icons.
F5 does a 'Step into'
This executes the line of code and it will follow the code into
subroutines, subprocedures, and programs.
F6 does a 'Step over'
This executes the line of code and it will NOT follow the code
into subroutines, subprocedures, and programs.
F7 does a 'Step return'
This executes all of the lines of code in the program until
a RETURN is encountered, at which point it will execute the
RETURN and stop at the next instruction.
F8 does a 'Run'
This executes all of the lines of code until the program
terminates.

All of these are 'overridden' by breakpoints. For example, if a
breakpoint is set inside a subprocedure and you step over it, the
breakpoint will fire anyway.

Some other useful keys I like:
Ctrl-Shift-L - run to the line the cursor is on.
Ctrl-F9 - Find the line the debugger is stopped on. Useful when I
scroll up and down looking at the source and forget where I was in my
debug session :-)