|
"Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx> wrote:
. . . but when I compile the source, start debug and submit the batch job, the program will whip througheverything without stopping on the specific breakpoint in the RPG program.
Well, that's part of the problem right there: when you start the debugger, you're starting it in your interactive job, NOT in the batch job you're about to submit.
What you need to do is somehow arrange to pause your batch job before it gets to the program you want to debug. Having the CL program send a message to the operator's console, and wait for a reply, seems like it would be a good choice; probably having it wait for a specified amount of time would also work.
While the batch job is waiting for you, you then need to start a service job on it, with the STRSRVJOB command. At that point, THEN you can invoke the debugger, and it will affect the batch job you are servicing, rather than your own interactive job.
Trust me: given that two of our products are client-server applications, and servers run in batch, we've had to use service jobs plenty of times.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
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
