Re: RDP Debug when STRDBG active

Are you allowed to change the CL? If so, you could condition the STRDBG so that
it doesn't execute if the job is already in debug. I think a CHGDBG with no
parameters will throw an error that you can monitor for to condition the STRDBG.

Dave Shaw
Mohawk Industries



----- Original Message ----
From: "Anderson, Kurt" <KAnderson@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries (wdsci-l@xxxxxxxxxxxx)" <wdsci-l@xxxxxxxxxxxx>
Sent: Tue, March 5, 2013 11:25:01 AM
Subject: [WDSCI-L] RDP Debug when STRDBG active

While I love RDP, I haven't moved from STRDBG over to debugging from within
RDP. I have a program issue and I thought I'd give RDP's debug a try.

We have test jobs setup that automatically run STRDBG to prevent updating of
production libraries. Using StrDbg, when it hits that line I get an error I can
ignore. Now, when I set the SEP in a RPG source, which is a program called by
the CL that executes STRDBG (among other things), the debug view is never coming
up. I tried adding a SEP to the CL before the STRDBG gets hit, and when that
happens, I get an error and can hit ignore, but for some reason it's not
entering the RPG code for me to debug. In the RPG program I set the breakpoint
at the very beginning to make sure I wasn't running into an issue where the
statement I put a breakpoint on wasn't getting called. I just now set a
breakpoint in the CL after the STRDBG statement, and it doesn't break.

I've now spent about 45min on this and feel like I've had no success. I know
our method of testing (using a mix of production and test libraries) isn't going
to change. Are there any other suggestions as to what I might try?