Re: Activation Groups and Threads

Hmm... okay, how would normal overrides handle this?  Let me try to
explain the example a little better:

Files:
  SomeLib/SomeFile
  SomeOtherLib/SomeFile

CL:
  OVRDBF SomeFile SomeLib/SomeFile
  Call PgmA

PgmA:
  Open SomeFile (opens SomeLib/SomeFile)
  Call PgmB

PgmB:
  Open SomeFile (Opens SomeLib/SomeFile)

Now, what we actually want is for PgmB to open SomeOtherLib/SomeFile.
SomeOtherLib is in the library list, SomeLib is not.  How do you get
PgmB to open SomeOtherLib/SomeFile?

Now, if PgmA was in one activation group, and PgmB was in another
activation group...  Say PgmA is in activation group *CALLER.  PgmB
is in named activation group Utilities.  We leave the programs just
as they are (since OVRDBF defaults to *ACTGRPDFN).  We recompile PgmB
giving it activation group Utilities.  We run this procedure again.

Now PgmB is going to open SomeOtherLib/SomeFile.  Like we want it to,
in this hypothetical case.  Because the OVRDBF no longer applies to it,
since it's in a different activation group.

How would you do this with OVRDBF and no named Activation Groups?  There
may be a way, I just don't know what it is.

Regards,

Jim Langston

Me transmitte sursum, Caledoni!

FKolmann@netscape.net wrote:
> 
> Hi Jim,
> Thank for the reply.
> 
> -  SNIP-
> 
> >Okay, say you have an application that uses a certain database file,
> >and you want to do an override on this database file.  So you do the
> >override, then realize that some other called program is now opening
> >up your overridden file but you really want to open the original file.
> >You have a bit of a quandary, and what you would probably wind up doing
> >is a kluge by creating a CL that does an override, calling the other
> >program, then setting the override back or some such nonsense.
> >
> >Enter Activation Groups.  You compile your main program in one activation
> >group, and the other called program in another activation group.  Now
> >you can specify on your override which activation group it is to apply
> >to, and so the two different programs will be opening up two different
> >database files with the same name, one using the override and one not.
> >
> >As I said, in most cases you don't need to use activation groups per se
> >so go with the default activation group.
> 
> Thank you for the example and I see by your last sentence that you can
> also see the flaw above but, you cannot have the same file-name for
> different files in the one library and ordinary overrides can handle this
> case, you don’t need AGs.
> 
> -SNIP-
> 
> Thanks Jim, I see by the number of your replies that you are one helpful
> guy, and you always have my respect.
> 
> Regards Frank Kolmann

Regards,

Jim Langston
+---
| 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
+---