Re: Debugging with RDi

What you’re seeing is CGI as normal. Unlike 5250 jobs a web request will not always be handled by the same server instance - hence it is in a different job that the one you are debugging. One way to deal with this is to have a separate server instance (different port) for your development and limit it to a single server job. Haven’t done that in a very long time so I can’t recall exactly how you set it up - it is part of the Apache config and hopefully someone else can provide the detail if you need it.

The reason I not longer use it is because I always use SEP (Service Entry Points). This will work no matter what job your program is activated in and has the advantage that you are testing the program under “real” conditions - limiting it to a single instance can mask the fact that you haven’t stored state information correctly.

You use SEP from RDi Locate the program in question in the library list, right click and select Debug or … and then Set Service Entry

Now the program will break at its first line whenever it is called regardless of the job.

You must either delete and reset the SEP (or refresh it) any time you recompile it.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Apr 25, 2016, at 4:52 PM, 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.