RE: READC - OS400 issues?

["Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>]

Rick,

I have used this logic before in programs for error checking
first, and then processing "if" the data was clean.
Sounds like this is what you are attempting,
since the issue appears with a function key, check
the display file source (are the keys defined as CF or CA for
your command key(s) ?)  The short explanation being (CF returns
values to the program, CA just returns to the program without
data being exchanged)

Also, I do not see an explicit function of "update subfile record" -
I take it that when you mention update the SFLNXTCHG you do mean to
set it and update the subfile - otherwise; if that is not the case,
this would cause your issue with the logic you are working with.



HTH
Mark A. Manske



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Rick Rayburn
Sent: Monday, June 30, 2003 9:43 AM
To: midrange-l@xxxxxxxxxxxx
Subject: READC - OS400 issues?


...using READC and SFLNXTCHG to process SFL entries.

...validate routine comes first, use READC, update SFLNXTCHG, finish READC
loop.

...if user presses update function key, code falls through and tries to
READC through SFL again to process only records changed for update.

Problem: second READC loop appears to already be at EOF when starting new
READ's (from previous loop?). No records processed, EOF reached immediately.
I know with physical files, we can *LOVAL them back to the beginning and
read them all over again.

Question: Does OS400 support 2 READC accesses within same coding loop (only
1 EXFMT taken originally)? Is there any way to do this by using READC? There
are multiple other methods to handle the updates but I am only interested in
using 2 READC loops upon one function key depression.

Thanx for the time.

Rick Rayburn

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.