RE: Debugging service pgm - eval vs F11

> > OTOH, you are correct that I started debug after the program
> crashed.  In my
> > experience, that has never made a difference in being able to view the
> > values of fields used by the program with the debugger EVAL
> command vs F11.
>
> I don't know why F11 works and EVAL doesn't.  And I don't really
> understand what's going on under the covers.
>
> It's just been my experience that when a program crashes, it becomes
> difficult to view (or change) the contents of variables. It sounds like
> you've had the exact opposite experience :)    I haven't explored it
> further than that, my solution has been to set a breakpoint on the line
> that I know it'll crash on, and then run the program again and reproduce
> the problem.  This way, it'll hit the breakpoint before it crashes, and I
> can see everything that's going on.

Yeah, that's another thing to try.  In this case, seeing the "404" was
enough of a clue to fix the problem, but the weird behavior had me wondering
if there was a PTF for it.  Google didn't turn up anything except some old
V5R1 problems with debug.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.9/118 - Release Date: 10/3/2005