Kurt,
Using RDP 8.0.3, I can debug the JOB, whether it is a Green-Screen Session or Batch job. And the RDP debugger works Great!
I change my preference to update Production files:
Windows>Preferences>Run/Debug/IBM I Debug> Check-box "Update production files.
This debug functionality of "JOB" does NOT work well on RDP 8.5.1, it got broke somewhere sadly. I get the error, where is says cannot find source. <perplex-look>
Because, when trying to solve an error, I need to debug that job that is executing RIGHT NOW, not put it into SEP debug first. <grin>
However, I do like the SEP debug, when I know to debug up ahead of time!
But, there are times when the "Debug JOB" that has been around since WDSC is great to just debug a job! I normally leave the USER & JOB-NUMBER as "*" (asterisk) to get the current active job. And I can reuse my "debug job" template over and over again! <Cool!>
Anyway, WHENEVER I debug using RDP, I only use RDP 8.0.3, because overall I have few issues. And I can update my code, when I encounter an error! Awesome!
Of course I have to end Debug and restart to Re-Test... <LOL>
-Ken Killian-
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: Tuesday, March 05, 2013 11:37 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP Debug when STRDBG active
When I realized that, I set the SEP to occur prior to the STRDBG execute.
midrange.com
