|
Dane Cox wrote: > > Wow, thanks everybody for the information. This has been quite > educational! I do have one more observation/question if you'll bear > with me a little longer... > > Let's take this scenario one step further and say that I have a second > RPGLE 'main' program that is bound to the same 'nomain' module exactly > the same way as the first and that the program is called from the same > 'batch' job. It is also compiled with the same options as the first. > In other words, same everything except program name (and likely > different internal functionality). > > Does this second program create a different 'instance' of the module for > its own use, or will it use the one that is already resident in the AG? > That's called "bind by copy". Each program will have a separate instance of the module. To get two programs to share the same instance of the module, the module has to be in a service program either in a named AG or in *CALLER where both callers are in the same AG.
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.