Re: CHAIN Versus SETLL and READ When Data Needed

Here's what I do:

   C      eval    Error = *off
    * S1 = stay on Screen 1
   C      eval    S1 = *on
   C      dou     (Error = *off) or (S1 = *off)
... etc
    * Process Screen 2 if no errors on Screen 1.
   C      if      Error = *off
   C      exsr    Screen2
   C      endif
   C      enddo

Wes Reinhold wrote:

A lot of what I do is interactive screen processing.  DOW 0=0 allows
staying on the screen until a function key (or whatever) is used it
exit.  It also allows for verification of fields doing an iter if an
error is found (while displaying a message).

I can't imagine not using it.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Thursday, March 01, 2007 9:10 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: CHAIN Versus SETLL and READ When Data Needed

Is that a good practice?  I can't imagine a design need for an endless
loop?

Wes Reinhold wrote:

There was a lot of 'bad mouthing' of iter, leave, etc. yesterday.  How

would you get out of a DOW 0=0 without using them?

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.