|
>Indicators are static by definition. Don't you mean "global?" I always thought that "static" meant that the subprocedure has local storage for the variable; storage that is untouched by any other parts of the program and is not re-initialised each time the procedure is called. They live only in THAT procedure and survive across CALLP boundaries. Global variables also survive across CALLP boundaries, but that's because no subprocedure owns them. Any line of code can manipulate them, subprocedure or mainline. Response indicators (like CF03 03 'Exit') are global and live until the next READ operation sets them. This doesn't change with subprocedures because there's no way to define a local version of an indicator. Buck +--- | 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.