|
Absolutely! Only sequential access methods are subject to EOF conditions. Random access methods are either found or not found. ______________________________ Reply Separator _________________________________ Subject: Re: Debug eval RPGLE %BIFs Author: <MIDRANGE-L@midrange.com > at INET_WACO Date: 1/22/99 12:24 PM boldt@ca.ibm.com wrote: > The operations that set %EOF are: > > - READ > - READC > - READE > - READP > - READPE > - WRITE (subfile only) > > So this is working as described - %EOF is not affected by > successful CHAIN or SETLL operations. FWIW, IMHO a chain really *can't* result in an EOF. It *can* result in a not-found, but not an EOF. So design is correct. I would feel the same about the setll and/or setgt ops. Reads returning an EOF yup. Position to returning an EOF nope. Pls don't change that. -- =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified AS/400 Administrator -- The sum of all human knowledge is a fixed constant. It's the population that keeps growing! +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.