RE: Debugging a batch program

I use batch debug all the time also, and it works fine.  I compile *source.
I do the same thing as Tim says below.

I have never noticed a 2 page sort of sensation.  I generally forget to put
my submit on hold back to *NO and wait for the next thing I submit for 5-10
minutes before I realize...  :)

Mark

> -----Original Message-----
> From: Hatzenbeler, Tim [SMTP:thatzenbeler@clinitech.net]
> Sent: Friday, May 25, 2001 1:59 PM
> To:   'RPG400-L@midrange.com'
> Subject:      RE: Debugging a batch program
> 
> I know batch debugging works... I use it all the time, by holding the
> jobq, getting the job#, and stuff... and then strsrvjob, and strdbg on
> it... and I'm on v4-4, one thing to check... is make sure you don't have 2
> versions of the program your debugging...  maybe your debugging one that
> never gets called...
> 
> just a thought.... but hang in there... it does work... and it's a lot
> easier to hold a jobq and debug in batch, than it is to change all your
> driving cl's so you can test it interactively... plus your not debugging
> in the same environment are your application really run's in a production
> mode...
> 
> 
> (**side note to everyone else**) when debugging in batch, as you step
> through the code, it appears 2 pages are constantly switching back and
> forth.... is there anyway to solve that little annoyance..
> 
> good luck... and have a nice weekend... 
> 
> tim 
> 
> -----Original Message----- 
> From:   George J. Vitek [SMTP:vitekg@ctpf.org] 
> Sent:   Friday, May 25, 2001 9:52 AM 
> To:     RPG400-L@midrange.com 
> Subject:        Re: Debugging a batch program 
> 
> I'm just guessing, but I believe what you want is a trace function. 
> 
> Kirk.Palmer@Walsworth.com wrote: 
> 
> > I have followed all the steps outlined below to debug a batch program.
> 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 
> > 
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
> > 
> > 
> > 
> > 
> > Date: Wed, 23 May 2001 19:54:22 -0400 
> > From: Patrick W Conner <PWConner@Charter.net> 
> > Subject: Re: Debugging a batch program 
> > 
> > Instead of setting your break point when you are getting the error
> message, 
> > press 
> > F12 to go back to a command line. Release the out queue. A message will 
> > display 
> > stating "...press F10 for debug or enter to continue..." when your job
> goes 
> > active. Press F10. Your source should appear (if not, use the DSPMODSRC 
> > command). 
> > Now, set your break points and continue. 
> > 
> > Hope that helps 
> > 
> > "Wills, Mike N. (TC)" wrote: 
> > 
> > > How do I debug a batch program? 
> > > 
> > > I know you can use STRSRVJOB and then use STRDBG. So what I did was
> put 
> > the 
> > > jobq on hold (test jobq so it is not a major thing to put on hold) so
> I 
> > > could get the job number. Then used STRSRVJOB on the job, followed by 
> > STRDBG 
> > > and was going to set a break point, but it wouldn't let me set one. 
> > > Something about "cannot perform this function when job is not active".
> Am 
> > I 
> > > doing something wrong? The job runs for about 20 seconds normally. 
> > > 
> > > Thanks for any help in advance. 
> > > 
> > > Mike 
> > > 
> > > BTW this is a RPG program. 
> > > +--- 
> > > | 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 
> > > +--- 
> > 
> > +--- 
> > | 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 
> > +--- 
> 
> +--- 
> | 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 
> +--- 
> 
+---
| 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
+---