Re: Rrn of Physical files

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

Is this the program that you don't have the source for, or is that another
problem?

If you -have- the source, insert a few statements to log the information
you need to a file or printer or screen...   or place the program in debug
mode.

If you just have object code, try to force an error and take the D=Dump
option when the program dies.  It may give you a statement number at the
'blowup' point that you can use for debugging.  You can at least get the
program to stop each cycle through.  With information from the dump, you
can check variable values.

--Paul E Musselman
PaulMmn@ix.netcom.com

-=-=-=-=-=-=-=-=-=-=-=-

>The program reads 8 records before I can get control back.  This happens in
>a matter of 1/2 second??  I need to know which 8 RRN's these are?
>
>Scott Swaim
>scott@qualitycorps.com
>
>(The opinions expressed are not necessarily those of my employer,
>unless they are correct.  They would like as much credit as possible.)
>
>>find your job, key a 5 in front of it.  then, take option 14, and cmd 11
>(or maybe 10
>>depending on your release)
>>
>>from there, you can see the record #'s.
>>
>>nj





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---