RE: A different kind of persistence?

["Dane Cox" <DCox@xxxxxxxxxxxxx>]

I had a hunch that's what you'd say, so why then do we persist 'nomain'
modules in the AG after their 'main' module has ended?  Who is going to
use it?  Are we for some reason assuming that the original 'main'
program that used it will be needed again later, so why clean up after
ourselves?  That's an interesting assumption.  I'd be interested in
hearing any further thoughts you might have on this.
  
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Monday, January 10, 2005 4:32 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: A different kind of persistence?

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.

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information. Any unauthorized review, use, printing, saving, 
copying, disclosure or distribution is strictly prohibited. If you have 
received this message in error, please immediately advise the sender by reply 
email and delete all copies.