|
Let me back up for a minute. First, I compile everything with DbgView(*List) when using debug. Second, after releasing the batch job and pressing F10 to enter debug commands, I rarely set break points initially. I press F10 (in debug) to start step mode. This way the program breaks immediately upon starting. I continue to press F10 to step through the program unless I need a breakpoint to get directly to a problem. Third, make sure you are setting break points on code that is going to be executed. Hope this helps. I'm also at V4R4. On Fri, 25 May 2001 08:30:43 -0500 Kirk.Palmer@Walsworth.com wrote: > The problem is that even if I set a break point for the > program running in the > batch job, the debugger will not stop a the break point. > If the program > runs long enough, I believe I can DSPMODSRC to look at > the value of some > variables, but the breakpoints don't work. > > When we first started programming with RPG IV (V3R2??) > the breakpoints did > work on batch programs, but lately they don't. Debugging > interactive > programs works just fine. > > FYI, we are currently running on V4R4. > > I would appreciate some help with this. > > Thanks, > Kirk > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.