|
No kidding - does that really work? When I need to read a subfile twice in succession, I usually do the READC for the first loop and then a CHAIN for the second, incrementing the subfile pointer until I run out of records. If your method works, that would be a much better way. Dave -----Original Message----- From: Paul Tuohy [mailto:tuohyp@xxxxxxxxxxxxx] Sent: Monday, June 30, 2003 12:45 PM To: Midrange Systems Technical Discussion Subject: Re: READC - OS400 issues? Hi Rick, Before the second read of the subfile, set the RRN field for the subfile (as declared on the SFILE on the F spec) to 1 - it is the eqivalent of SETLL. HTH Paul Tuohy ----- Original Message ----- From: "Rick Rayburn" <the400man@xxxxxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Monday, June 30, 2003 3:42 PM 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. > > _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.