RE: The Dark Side of the Do Loop

With DOU the check on the criteria is performed at the end of the do
loop.  Perchance you have an iter prior to your enddo that is causing
this?  If so then best bet is to immediately after *iin30 is on execute
the leave opcode OR....change to a DOWne *ON which will check at the
start of the do loop. 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of steema@xxxxxxxxxxxxx
Sent: Tuesday, January 31, 2006 2:23 PM
To: RPG programming on the AS400 / iSeries
Subject: The Dark Side of the Do Loop

I have a subroutine that is predicated on a Doueq.

This cond. is met, yet the program keeps going back into there at the
first ELSE point, then it goes back to the prev. ENDSR. *in30 has been
set
on. All of this, shows up in my debugging.

IOW, it is stuck. I cannot understand how to unravel this.


 c                   endsr
 c     rest          begsr
 c     *in30         doueq     *on
 c                   eval      a = j + 10
 c     er(V)         scan      alphc:a       fl1               2 0
 c                   if        %found
 c                   exsr      movar
 c                   leave
 c                   else