×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
