Re: Newbie: debug a program running in batch

I wonder how much of the issue can be attributed to Eclipse vs. IBM.

So, I guess my cheat sheet for debugging in RDi is:
1) Exit RDi
2) Delete workspace
3) Start RDi
4) Set the SEP(s), ensuring correct object library and user ID
5) On the i, start a brand new job, ensuring correct library list (or
qualify your program call)

Even with all that, I find I'm still having problems. It appears that the
first call to PGMA is "caught" by the debugger (I have a breakpoint set at
the first executable statement), but subsequent calls to PGMA in the same
CL program stream are not. I just now confirmed this by debugging in the
green screen, which works properly. I've wasted most of my day getting to
this point. Not happy.

- Dan

On Thu, Nov 3, 2016 at 1:16 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I've somewhat reluctant to report RDi problems to IBM. Their goto answer
is "delete your workspace and try again", which IMO is a cheap cop-out on
their part. Report the same problem a few days later, and again "delete
your workspace and try again".