|
I'm guessing there are only 998 records in the subfile, which means the 999th iteration of the loop is failing to access a subfile record. That would explain why RRN is 998 before the READC. Perhaps setting RRN to 0 before the READC is all you need to do. Donald R. Fisher, III Project Manager The Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@roomstoreeast.com <clip> **NOTE SUBFILE SIZE is 1000. When I look at RRN on pgm subfile rec after 999 loop and before readc it's 998? READC to end loop? Might work but... I thought write would do it. Do I need to force RRN to be 1 before write of control record? Or will it reset? Other loops later use RRN for CHAIN, LOOP CNT,etc. on subfile records. Thanks Again, Bill H -----Original Message----- From: Mike.Barton@pinkroccade.co.uk [mailto:Mike.Barton@pinkroccade.co.uk] Sent: Thursday, November 07, 2002 11:32 AM To: rpg400-l@midrange.com Subject: Re: Subfile Next Changed >Hi All, > >Do not ask why, but this subfile is TRYING to be totally control/edited by >the program before any writes/update to PF. >About 3 thousand plus lines. > < snip> > >Is this *ON because control rec(RC00103C) to subfile not written or exfmt >before READC? Or RRN to subfile at bottom? >Why READC not seeing it as changed? > >Mind fried trying to find. >Thanks > >Bill H Bill yes you need to do a WRITE {subfile control record} before the READC (this will effectively re-set the start point). Mike This communication and the information it contains: - (a) Is intended for the person(s) or organisation(s) named above and for no other person(s) or organisation(s). Access to this mail by anyone else is unauthorised. (b) Is confidential, and may be legally privileged or otherwise protected in law. Unauthorised use, circulation, copying or disclosure of any part of this communication may be unlawful. (c) May be susceptible to interference, and should not be assumed that it has come in its original form and/or from the stated sender or PinkRoccade UK accepts no responsibility for information, errors or omissions in this e-mail or use or misuse thereof or any act done or omitted to be done in connection with this communication. If you are not the intended recipient, please inform postmaster@pinkroccade.co.uk immediately and delete it and all copies from your system. _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.