|
Jeff, Except that if one program sets these variables, other programs immediately see the changes. An easy way to percolate/signal changes between programs in an application. Yes, you'll still need to *define* the variables in your program, but that's easy, by putting them in a copybook called e.g. MSGDS as e.g.: D msgDs DS /IF DEFINED(msgds_export) D Export /ELSE D Import /ENDIF D msg_type 1A D msg_text 128A Varying In the service program, use the following: /DEFINE(MSGDS_EXPORT) /COPY QRPGLESRC,MSGDS and in all the other programs, simply use this: /COPY QRPGLESRC,MSGDS and you're fine. Rory On 10/27/06, Jeff Young <cooljeff913@xxxxxxxxx> wrote:
>Nathan. What I do not see, is how I would access this common data in my programs without having to define the variables in the program using the Import keyword. If I do that, then I do not have any advantage in a service program with the data in it. Thanks, Jeff Young
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.