Re: Rép. : Re: AW: How do you debug CGIDEV2 programs -- RPG400-L

× 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.

Denis

Nice technique - SEP technique can lead to many messages in the initial job that started debug - and they have to be released so that the users are not blocked. On a production system, this is something that could be messy.

So your idea lets you selectively do the debugging, right?

Vern

On 8/10/2012 10:09 AM, Denis Robitaille wrote:

Since I was unaware of this technique to find out the complete job name/number, I used the following work around:

I have the CGI program write the job info to the web page as hiden variable. Then I just display the HTML source and the STRSRVJOB required info is there for me. I can then proceed with the STRSRVJOB and STRDBG.

Denis Robitaille
Directeur Service technique TI
CASCADES INC.
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
T : 819 363-6130
F : 819 363-6155

Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> 2012-08-10 10:07 >>>

As I just replied to Nathan, this does not set ro add an SEP. These are
the old instructions for debugging a job other than your own. The
problem is, you often can't know that job beforehand, especially when
dealing with server jobs like CGI or QZDASOINIT or remote command jobs.

-snip-

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.