Re: Newbie: debug a program running in batch -- WDSCI-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.

There was no recompile between the two calls to PGMA. I set the SEP before
I started the job that called PGMA. As evidenced by the fact that the
debugger "caught" the first call, the library list and user ID were
correct. I am using RDi 9.5.0.3.

It took me 5 minutes to use the green-screen debugger and find the problem
in my source code.

- Dan

On Thu, Nov 3, 2016 at 2:14 PM, Tyler, Matt <matt.tyler@xxxxxxxxxxxxxx>
wrote:

It would be helpful to know what happens between these steps, "It appears
that the first call to PGMA is "caught" by the debugger" and "but
subsequent calls to PGMA in the same CL". SEPs cannot monitor for any
changes that occur to the program object. So if you happen to recompile
the code after setting the SEP you have to refresh the SEP entry to get the
debugger to start up again. Also, the debugger used to not allow you to
set the SEP after you have activated the program once in a job.

I only mention this because at RDi 9.5.1.0 APAR SE65785, I have yet to see
behavior like this. I also have RDi installed as a local user copy and
not in the Program Files, so that might make a difference as well.

Thanks, Matt

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.