|
email@james-w-kilgore.com (James W Kilgore) wrote: >"If the INDARA in not specified, the indicators are included in the record area >of the I/O buffer. ..... The application programmer does not have to worry about >mapping these fields into additional variables defined within the program. For >programmer productivity, this is a big bonus." > >Their words, not mine. :-) > >This may be a way of retrieving the indicator settings, don't know, never been >there. I think this is probably a blind alley. Most RPG programmers are not familiar with INDARA because the indicators are automatically defined in the program, and it makes sense for them to be in the record area. In COBOL, for example, the indicators are not built into the language and it's easier for a COBOL programmer to define a separate indicator structure than to have the same indicators defined in multiple records. This is what INDARA is for, it does not make indicators accessible that were not accessible before. Sorry, Dave Kahn, ABB Steward Ltd. +--- | 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.