Re: Debug getting lost?

Hi, David:

Did you set a breakpoint, and then recompile the *PGM, and then you expect that breakpoint to still be honored in the newly compiled *PGM?

If you did that, the breakpoint would be set in the old copy of the *PGM that now resides in QRPLOBJ, renamed with a "Q" followed by a hexadecimal timestamp. :-o

Also, when you start debug through WDSCi or RDi, what is really happening is that there are some jobs running on the host (System i) server on your behalf -- under your user profile (depending of course on how you set up your connection to the host in WDSCi or RDi),

When debug is started for a given *PGM (or *SRVPGM), that program object must get "activated" into an activation group in some job (probably the WDSCi or RDi server-side job) to set the breakpoint.

Try issuing:
WRKUSRJOB yourUserID *ACTIVE

and see if you can find those jobs running on OS/400 or i5/OS on behalf of WDSCi or RDi.

Often, you must sign-off and sign-on again (to force all activation groups to end and get reclaimed) in an interactive 5250 session when using the 5250 debugger (STRDBG), so you need to somehow force those server-side jobs to end and restart them again, probably by closing WDSCi or RDi, or at least exiting from the debugger, and then starting it up again, whenever you recompile a program you are debugging.

Hope that helps,

Mark S. Waterbury

David Gibbs wrote:

On 12/3/2009 10:30 AM, Jim Essinger wrote:

I just had a thought. I have experienced this before, but to fix it is
signed off of the display I was using to test on, and signed back on. My
thought was that the session was using the older version of the program from
the replace library. When I reclaimed activation groups, or signed off and
back on, it seemed to clear the problem.

Already tried that. Doesn't seem to be related. I can sign off and back on again, but the debugger still doesn't hit.

david