Re: MIDRANGE-L Digest, Vol 4, Issue 2122

I guess what your telling me is to start a Interactive session, start 
debug and call the program to debug the problem?
I need to take the current batch job and cause a storage dump.

m.

> message: 4
> date: Fri, 28 Oct 2005 16:21:09 +0200
> from: "Carel Teijgeler" <coteijgeler@xxxxxxxxx>
> subject: Re: Creating a dump for looping program.
> 
> You can use STRISDB to debug the batch job (being an OPM 
> programme). I think it is the last parm of the command that give 
> you the oppertunity to *SELECT the job to debug.
> 
> Perhaps then you can set the value correctly.
> 
> Regards,
> Carel Teijgeler
> 
> *********** REPLY SEPARATOR  ***********
> 
> On 28-10-05 at 10:01 msmith6@xxxxxxxxxxxx wrote:
> 
> >  Last night I was called by the application staff about one of 
> their 
> >programs looping in batch.  They needed help getting stuff in 
> order.  
> >They asked me to cancel the batch job with a DUMP.  It was at 
> this 
> >point, I realized that the only time I've created a dump was when 
> a 
> >program ABENDed and there was a message wait.  The batch job is a 
> CL 
> >program that calls a series of COBOL and COBOL/LE programs.  The 
> >program that it was looping in is OPM COBOL.  
> >   So my question, is there a way to cancel a job and produce the 
> >formatted dump the programmers are accustomed to when I answer 
> 'D' 
> >or 'F' to a message wait.
> 
>