dreport and debug

[Richard Kreiss]

On Apr 11, 2013, at 11:19 AM, Kenneth Brody <kenbrody at spamcop.net> wrote:

> On 4/11/2013 10:44 AM, Richard Kreiss wrote:
> [...]
>> My problem has nothing to do with these new date variables. However, when
>> I run the output, upon reaching certain records the processing stops. To
>> track the specific record on which the processing stops. I have added
>> some show statements, which gives me the transaction number and the date.
>> In addition, I have show statements which show me which subroutines have
>> run. This was to allow me to find where the problem was more quickly.
> [...]
>> I have manually looked at 14 records with the debugger, when I run the
>> output again, the processing continues through those records which
>> previously caused the program to hang up. This is the same whether I run
>> dreport or rreport. The only differences is rreport runs a lot faster
>> than dreport.
> [...]
> 
> Have you considered the possibility that those records were locked by 
> someone else at the time, and by the time you got around to manually 
> checking them out, they were no longer updating that record?
> 
> If it happens again, try using showlock to examine what records are locked.
> 
> -- 
> Kenneth Brody
> _______________________________________________
> 
Ken,

U am the only one in this file. No one else has access to it. 

Richard