Re: Debugging error

steema@xxxxxxxxxxxxx wrote:

> In debugging the program the code gets stuck in this loop:
> on the delete. I am not understanding how to continue to debug
> the problem, if there is no loop out.
>
> C                   do        lstrrn2       count
> C     count         chain     sfl2
> C                   if        %found
> c                   z-add     udate         badate
> c                   z-add     btime         batime
> c                   movel     user          bauser
> c                   write     edflog
> C     asnkey        delete    mllc1wpk                            90
> C                   endif
> C                   enddo

I don't see how this is a debugging problem per se. The fact that you are
in debug should not be influencing the path through the program. When you
say it gets stuck on the delete, do you mean it never completes that
instruction, or do you mean it goes round the loop forever?

If the former you might suspect that the record you are trying to delete is
locked, possibly by the same program if you have more than one file
definition encompassing the underlying physical, although in normal
circumstances the instruction would eventually time out and return. A
common error is to read the file for update while loading the subfile. This
can leave a lock on the last record read. In RPG/IV you can use the N
extender on the read or chain opcode to avoid creating a lock.

If OTOH it just goes round and round the loop, what is the value of
"lstrrn2"? What is the definition of "count"? If "lstrrn2" is not less than
the maximum value that "count" can hold the loop can never end.

--
Dave...


______________________________________________________________________
This message may contain confidential information which may also be legally 
privileged and is intended only for the use of the parties to whom it is 
addressed. If you are not an intended recipient you are hereby notified that 
any disclosure, copying, distribution or use of any information in this e-mail 
is strictly prohibited. If you receive this message in error please notify the 
sender by return e-mail and then destroy it. Further, we make every endeavour 
to keep our network free from viruses. However, you do need to verify that this 
e-mail and any attachments are free of viruses as we can take no responsibility 
for any computer viruses which might be transferred by way of this e-mail. All 
information and attachments remain the property of Stolt Offshore Group and 
should be held as confidential.