|
Booth, I think your code will get stuck in the loop - %Found will always be true, since there's only one Chain, which is before the DoW. I imagine it can be made to work, but my brain's off-line at the moment (after lunch, y' know? ;). As an alternate work-around, I've got a few programs that substituted SetLL/ReadE for the priming Chain, then just use %EOF. I found that limiting, too. EndLoop provides a lot of flexibility, since I can set it for any reason I want in the code, plus I can see what's in it while in debug. Using the BIFs directly is more limiting, especially two years later when someone unfamiliar with the code (like me after that amount of time <grin>) has to make a change to it. Just as an example, if I want to add code for %Error at a later time (later in the debug cycle, or later in life), it's very easy to just insert it in the code and add another update of EndLoop, without compromising readability at all. Dave Shaw Spartan International, Inc. Spartanburg, SC -----Original Message----- From: booth@martinvt.com [mailto:booth@martinvt.com] I'm trying to learn this stuff. Why not the code below, but like this? C Key Chain(E) File C DoW (%Found Or Not %EOF) And (Not %Error) * stuff C Key ReadE(E) File C EndDo _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.com _______________________ +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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-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.