Re: SEP debugger in RDp

Start with a technical question...SEP Debugger = the Debug Perspective?

If so...you will want to add your program as the only program in the Debug Configuration list, and make sure the Step Into checkbox is checked. Once that program comes up in the debug view, as you are stepping through and come upon a program you can't step into due to authority issues, use the Step Over button (also F6 on your keyboard). I think that'll do it. It will limit you on some features such as the animated step into, but hopefully it will help you get the job done.

-- Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of ssc1478
Sent: Thursday, March 01, 2012 10:26 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] SEP debugger in RDp

(Reposting to proper group)

In the SEP debugger in RDp, if I am getting authority errors which
prevents me from debugging at all.

I have a pgm that I compiled that uses production pgms/srvpgms which I
don't have debug authority to.  Usually, that means I can't step into
the pgm/srvpgm which is fine. I only want to debug the one I compiled.

I can't do that with the SEP debugger.  If I don't have authority to
all the pgms/srvpgms, it doesn't let me debug at all.

Is this the way it works?  Or is there a setting I can set?

Thanks for the help!

Phil