Re: Invalid subfile options and SFLMSG

["Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>]

can you show us some of your code where you read update the indicator and 
update the subfile, maybe someone can spot the problem?



Nick_Radich@xxxxxxxxxxxxxx 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/08/2007 01:05 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Invalid subfile options and SFLMSG






Booth,

Did you update the subfile record after you turned *off the indicator?

HTH,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



Booth Martin <booth@xxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/08/07 01:01 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Invalid subfile options and SFLMSG






Why wouldn't the indicator be shut off when the message displays?  The 
book says it will.

But, beyond that, I tried what you suggest and that made no difference.

Sharon Wintermute wrote:
> I assume your *in70 is the error indicator.
>
> When you loop thru your subfile records, you need to turn off *in70 when 

you initially read it in.
> Sharon 
>
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Booth Martin
> Sent: Thursday, March 08, 2007 12:17 PM
> 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.