|
Jon, If a key is found and a record is read on a chain/reade the indicator is set off. If a key is found for a setll the indicator is set on. They also set %found/%EOF, and %equal. They do what the name implies, but I would rather have a consistent representation when the expected operation works or doesn't work. I do convert to a common variable and value, translating when necessary. For example, if a record is read the status is *ON. If a key is located the status is *ON. David Morris >>> Jon.Paris@hal.it 04/19/00 10:01AM >>> >> The problem I have with this is that it is not consistent. Sorry David but I have no idea what you mean. How much more consistent can you get than 1 built-in has an exact correlation to 1 "indicator" ? >> When was the last time you needed to know if a record was found on the setll preceding the last read? Again I just don't know what you mean here. I don't think I do need to know, and I don't see any way in which the current built-ins force you to worry about it. Do you mean that you use a single indicator for everything and then "copy" that into a specific state variable ? +--- | 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.