Re: RDP Debug when STRDBG active

When I realized that, I set the SEP to occur prior to the STRDBG execute. After your email, I thought that if I set the breakpoint prior to the execution of STRDBG that I might not have the issue, but I still do. What I'm trying to replicate, is to get RDP to say "Hey I'm debugging, not you, CL." I'm giving an 'I'gnore to the error on the STRDBG command. It seems to me that the program should then continue while in debug mode in RDP, but it isn't.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Tuesday, March 05, 2013 10:32 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP Debug when STRDBG active

Kurt,
AFIK, using RDP debug, under the covers, it issues a STRSRVJOB on the job, then a STRDBG on the program.
If DEBUG is already active on the job, the STRDBG fails.

I do not use the RDP debugger, so am not sure if it issues an error when you try this or just handles it and does nothing.



On Tue, Mar 5, 2013 at 11:24 AM, Anderson, Kurt <KAnderson@xxxxxxxxxxxx>wrote:

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?

Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems, a division of Enghouse Systems Ltd.






--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

--
Jeff Young
Sr. Programmer Analyst
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.