|
Thanks, Martin. That's as elegant a solution as I think I'll find, and adds only one line. The only time I might use the other, longer approach is when I find I do want to implement an ITER, but in most cases, if the logic is that involved, it will be moved to a separate subroutine anyway (no, I'm not quite up to proceduralizing everything uet - this dinosaur moves slowly <grin>). Joe P.S. At least I've gotten to the place, now, where I have two basic source files in each project library: QMODSRC and QPGMSRC. Through judicious use of the H-spec, I can now do a mass compile by selecting option 15 for QMODSRC, then option 14 for QPGMSRC. I have a single binding directory for that project library and it contains all the modules, while each RPGLE program in QPGMSRC has an H-spec that points it to the appropriate binding directory. Baby steps, baby steps. > From: Martin Rowe > > We pretty much all used this method in our department, and got a bit > confused with the right %BIF to use when moving to RPGIV. We settled on > a one line extension to it and just used the (functional equivalent) > SETLL/READE pair instead of the CHAIN and just use %EOF. > > FileKey SETLL File > FileKey READE File > DOW not %EOF(File) > (process) > FileKey READE File > ENDDO
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.