Re: How do you debug CGIDEV2 programs

Darryl

Take a look at this post I put up in February of 2011 - it looks messy but it's easier to do than to explain - I also just posted this URL in another reply today.

http://archive.midrange.com/rpg400-l/201102/msg00419.html

It was aimed at doing CGI jobs, which would include CGIDEV2 jobs. It says to use the QTMHHTP1 user, of course. For other kinds of server jobs, those details need changing.

I use this all the time at customer sites that are using our browser-based product. Often I cannot use the graphical debuggers at their sites - can't rely on it, at any rate.

Enjoy!
Vern

On 8/10/2012 1:22 PM, Darryl Freinkel wrote:

Debugging a CGIDEV program is not an easy process. The reason for this is
that you will not know which job to set your debug session on. Typically,
the server side programs (RPG) are run in subsystem QHTTPSVR. If you are
using vanilla configurations of CGIDEV2, you will see several jobs running
in QHTTPSVR with the job name CGIDEV2APA. There will be at least 2 jobs that
will service your call and depending on what is going on in your system
there could be more. The problem is which job will be executed when you run
the call.

You could use the green screen STRSRVJOB and STRDBG, but which job are you
going to monitor. There is also the Java debugger which essentially has the
same issue.

I found the best way to debug a CGI program is to use one of the
WDSc/RDi/RDp tools from IBM/Lotus. There you can start a SEP (Debug(service
Entry)/Service entry point) which does the best job of finding and debugging
your program. It automagically locates and debugs the program from whichever
job it happens to be called from.

Darryl Freinkel | Assignment 400 Group, Inc.
Tel: 770.321.8562 ext 111 | Fax 770.321.8562