RE: confusing coding?

I did end up solving this issue...

It had nothing to do with an infinite loop or LR. The error was buried inside a subroutine where it was re-reading and excessive number of records because the programmer was using a partial key.

For each customer it was reading all of their order history, in some cases, over 1000x.

I put a counter in various places and set a conditional breakpoint to find this issue.

Honestly, I found the discussion quite interesting.


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of smith5646midrange@xxxxxxxxx
Sent: Friday, August 8, 2025 4:25 PM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: confusing coding?

Did this ever get solved? As far as I can tell, the thread went ADHD and
none of the tangents offered a reason.

If this has not been resolved, I am in agreement with LR being a possible
issue. Is there any way the seton LR can be accidentally bypassed (wrapped
in an IF that is false, in a loop that a LEAVE is exiting before it gets
executed, etc.)? That would definitely make the program run forever.

If it has been resolved, I'm curious what the problem was.

Greg Wilburn
Director of IT
301.895.3792 ext. 1231