Re: AW: How do you debug CGIDEV2 programs

Hi Dave

I suspect that the limitations of STRSRVJOB are what you have to face. I've not tested this kind of thing. Others will likely know.

And STRDBG itself may have some limitations - I believe you need some *SERVICE special authority to use STRDBG at all - but that is from very dim memory just before I go home!

There are ways to get more authority - some program that'd give you that - but that has to be monitored stringently in any production house, right?

Some of the system users might not be an issue - such as QTMHHTP1 for CGI jobs. But that is a matter of policy in your shop.

Good luck!
Vern

On 8/10/2012 10:37 AM, Dave wrote:

Hi Vern,

What can I do when I don't have the authority to use the profile of
the user running the remote job? Is there some kind of limited
authority that I could be given, at least temporarily?

2012/8/10 Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>:

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.

These instructions mean that you already know the job where the program
will be running, which SEPs were meant to resolve.

To add an SEP in green screen, you use the SBREAK command in debug
session. You then F12 out of the session and wait for a message, where
the complete STRSRVJOB command string is given to you,

Then you execute it as given here in a new job, and then do the STRDBG
in the new job and set the breakpoint with F6 or BREAK, at the same line
number you used for SBREAK.

This is less simple than the case where you know the job to debug, but
I've found a reasonable set of steps that are not onerous. RDP, of
course, takes care of the heavy lifting of the STRSRVJOB and all.

My steps for doing this on green-screen are in the archives -
http://archive.midrange.com/rpg400-l/201102/msg00419.html

Regards
Vern

-snip-