RE: I hate Activation Groups....

[Jon.Paris@xxxxxx]

 >> I have a *SRVPGM with an assigned activation group, we'll save ACTGRP
('DAVE')..

So far so good.

 >> Now, I have a normal RPGLE program, with an activation group of
*CALLER, that calls the *SRVPGM.

OK but ..

 >> And a CLP that calls the RPGLE, has a RCLACTGRP DAVE, and the end of
it.

Not so sure why you want to do the reclaim - it is certain to cause a
problem unless (as you note) the program is also in an AG that is
destroyed.

Hans or Barbara will have a definitive answer I'm sure, but I believe it
has to do with ILE programs being "sticky" - that is to say they don't want
to go away.  Even when you set on LR they don't really go away (as an OPM
program would) they simply set an internal flag that tells them to
reinitialize when called again.  However, I believe that the linkage to any
service programs is done when the program is instantiated, not during
initialization, so your poor little program believes that it can "talk" to
a service program that no longer exists.  I suspect the message does not
tell you this because at this stage all it knows is that it has a pointer
to an object that doesn't exist and that is a no-no.  I doubt it knows what
it is a pointer to.

The expectation is that service programs always outlive the programs that
use them.  Think about whether you really need to do the reclaim and also
whether you can run the RPG program in an AG that can be reclaimed (like
QILE) and not in the default AG which is where it will run if you call it
from a CLP and the PGM is *CALLER.

Now repeat after me "Activation Groups are my friends .. if I treat them
properly they will offer me great power.  Activation Groups are my friends
..



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