|
David, You're right. Just out of curiosity I took out the INDARA keyword from a display file and compiled it. The indicators used to set display attributes were made into separate buffer positions on the output but only the response indicators were on the input. Now this may sound like a shotgun solution, but to avoid coding each indicator I would: 1) create a data structure that uses a 99 char field to overlay the indicator array, let's call it IndOutput 2) create a data structure that uses a 99 char field (IndSaved) and 99 element array of 1 char each 3) just before writing to the subfile, I would move IndOutput to IndSaved and output this as a hidden field for each subfile record. 4) just before refreshing the subfile record with the new data, I could test the status of each indicator from IndSaved's corresponding array and could then set the corresponding display indicator Naturally, if the shop standard is to use a block of indicators for display conditioning, the fields and arrays could be smaller. HTH, James W. Kilgore email@James-W-Kilgore.com =============================================================== david.kahn@gbwsh.mail.abb.com wrote: > > > 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. +--- | 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-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.