Re: Invalid subfile options and SFLMSG

[Booth Martin <booth@xxxxxxxxxxxx>]

I am using a 'for' loop and chaining to each record.  READC has always 
been problematic for me, and the 'for' loop is fast and fixes all issues 
(at least, until this showed up today! :)  )

Kesterson, Randy wrote:
> You need to update ALL subfile records after reading them so that you
> update your position indicator *ON or *OFF.  Also, you didn't specify
> how you're reading your subfile.  If you're doing it with READC, you'll
> need to turn on SFLNXTCHG for each record.
>
> ________________________________________________________________________
> ______________________
> Randy Kesterson, Information Services
> Market Transport Services  - a UTi Worldwide Company| 110 N Marine Drive
> | Portland, OR 97217 | USA
> rpkesterson@xxxxxxxxxxxxxxxxxxx | D +1 503.978.4353 | O +1 503.283.2405
> x353 | F +1 503.978.4392 
>  
>  
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
> Sent: Thursday, March 08, 2007 10:17 AM
> To: RPG programming on the AS400 / iSeries
> Subject: Invalid subfile options and SFLMSG
>
> Invalid subfile options and SFLMSG
>
> Time to get a tad smarter.  Not necessarily smart, just smarter than I 
> am this morning.
>
> OK, here's the scenario:  A subfile with a subfile option field so one 
> can key in a '2' to edit, '4' to delete, '5' to view, etc.  I've added a
>
> validity checking subroutine to be sure the user keyed in a valid value 
> ('2','4', '5' for instance).  I do a "for" loop and test each subfile 
> record. If the option does not validate then I turn on *in70 and update 
> the subfile before continuing the loop.  After the "for" loop there is 
> no further processing, and the screen is exfmt'd again.
>
> Everything works fine so far as I can see, excepting one problem that I 
> can not figure out how to solve.
>
> In testing, if I key several invalid options and press enter, it returns
>
> the error message and places the cursor on the first error of the 
> subfile.  Fine so far.  Now, if I fix the first invalid option but none 
> of the others, and then enter, the cursor goes to the corrected field 
> and still shows as an error.