Re: Batch Debug

["david.gibbs@xxxxxxxxxx" <devdmg@xxxxxxxxxxxxxxxxxxxxxxxx>]

On 25 Sep 97 at 19:36, Terry Grider wrote:

> Thanks for the reply, but what I really need is the whole recipe. 
> Step 1, Step 2, etc.  I seem to remember something about having to
> supply the job number assigned once it has been submitted to batch
> but I'm not quite sure where or when you use it if at all.

Ah... ok... here goes... 

I'm assuming you want to do a normal debug... not ISDB.  

1. Change your program to use the DLYJOB command for at least 60 
seconds (that's just to allow enough time to start the debugger).

2. Use WRKUSRJOB and determine  the full job id of the job that's 
being delayed (it includes jobname, userid, and job number).  The job 
should be in function DLY-<seconds>.

3. Prompt the STRSRVJOB command and enter the job id you retrieved in step 2.

4. Prompt the STRDBG and enter the information necessary.

5. Start adding your ADDBKP and similar debugging commands.

6. Your program is now being debugged... when the program hits a 
breakpoint, it will interupt your current session like a break 
message and allow you to display variables, and all the other 
debugging commands.

7. When you are done debugging, enter the command ENDDBG.  Then enter 
the command ENDSRVJOB.

That's it.  I'm pretty sure I hit all the important stuff.

david
--

David Gibbs
Sr. Software Engineer
Silvon Software
Westmont, IL
(630) 655-3313 x6479
http://www.silvon.com
mailto:david.gibbs@silvon.com

Opinions expressed are strictly my own and do 
not necessarily reflect those of my employer

Sometimes you have loose your mind to come to your senses.


                   -- DMRoth
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---