I answered my own question... I just kept changing the user on the SEP until it worked.
The SEP must be referencing the "current user" (SDS 358-367) and not the user of the active job that calls MYPGM.
I guess I gave up on SEP too fast.
Thanks
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wilburn
Sent: Tuesday, April 26, 2016 8:41 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debugging with RDi
I use SEP all the time... but you can't use them when the program is already running. Like most, once I've started using RDi and the SEP debugger, I'm never going back.
I don't understand why SEP wouldn't work on this job, other than I may have the user wrong. The job under QHTTPSVR is running under user QTMHHTTP. This job (or one of them) calls MYPGM. I've used SEP on MYPGM for both my user and QTMHHTTP. For some reason it never jumped into debug.
What user is SEP monitoring for? The "Job User" or the "Current User"? The application calling my program would likely have a job user of QTMHHTP1. The user running the CGI application would be the current user.
Is there a way to monitor the entire job, regardless of user?
Thanks,
Greg
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Tuesday, April 26, 2016 6:56 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debugging with RDi
Hi,
Using that "SEP" debugging, is how I got a developer to start using RDI! It is pretty powerful! My co-worker needed to debug a web-service that called an RPG program.
I told him out right, I don't know how to debug it WITHOUT the power of "SEP" inside of RDI!
That is all it took to convince him to start using RDI. It took his co-worker several years, before he started using RDI.
You basically need to tell RDI these three things:
1.) IBM i system/box (a.k.a. Beta/Quality-Assurance/Production/other)
2.) Library/Program name
3.) User-Profile
Then, NO MATTER how the program is evoked, it pops up in RDI! I use the SEP method probably about 80% of the time. Other times, I debug my green screen job, where I got an error.
RDI should be classified as an I.D.D.E.
I.D.D.E. = Integrated Development/Debug Environment. But most just call it IDE.
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Craig Richards
Sent: Tuesday, April 26, 2016 2:20 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debugging with RDi
Greg,
As Glenn mentioned, if you use SEPs then it's pretty easy to debug server processes ( well, threaded stuff can be trickier ).
In addition to the notes Glenn gives - you also have to ensure that you set the correct user that the program will be running under in the batch process.
To do this, once you have set the SEP and can see the program in the SEP view, you can right click or double click ( sorry I don't have RDi running on this machine ) and amend the user to be the correct one.
regards,
On 25 April 2016 at 22:29, Glenn Gundermann <glenn.gundermann@xxxxxxxxx>
wrote:
I don't have a tutorial, so I'm not directly answering your post.
I don't see you mention Service Entry Points in your notes.
This is key.
Right-click the program (or module, or procedure) > Debug or Code
Coverage (Service Entry) > Set Service Entry Point
Yours truly,
Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144
On 25 April 2016 at 16:52, Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Does anyone have a good tutorial on debugging in RDi? Specifically,
debugging Apache CGI jobs running in subsystem QHTTPSVR.
I can find the job (WRKACTJOB), find the same job in RDi Remot
System view, right click and select Debug (Prompt), etc. Then I'm
able to debug the job a few times before it seems to cease breaking at my breakpoints.
If I use the green screen STRSRVJOB and STRDBG I do not have this issue.
Really a PITA to debug these things with RDi.
Greg
--
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.
--
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.
--
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.
--
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.
--
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.
midrange.com
