RE: Activation groups for beginners

Exactly, Buck, you've got it nailed.  That's the clearest description I've
seen of what is happening here.

Now, I've got to find the best solution to fix the 500 or so driver CL's.
Originally, the service programs were also running in *CALLER, but I was
getting errors on the procedures.  The driver CL's also do a Rclrsc at the
same time as the RclActGrp.  I think Barbara nailed that one when she cited
the example of it closing files and/or other variables but leaving the
service program open and in the *DftActGrp.  I had thought putting all the
service programs in their own activation group would isolate them and I
guess it did, but created this new problem.

So,

1.)  I can't remove the Rclrsc without restructuring the many programs that
depend on it to close them down.
2.)  I can't recompile the CL's without a through investigation of the
override scopes, etc., throughout the entire job.
3.)  I can see no justification for having the RclActGrp in the driver CL's
at all, can you?

My plan now is to remove the RclActGrp from the CL's, but leave the service
programs in their own activation group.  I think this should solve the
immediate problems.

Thanks for your help.

> -----Original Message-----
> From: Buck Calabro [SMTP:Buck.Calabro@commsoft.net]
> Sent: Tuesday, March 19, 2002 4:43 PM
> To:   rpg400-l@midrange.com
> Subject:      RE: Activation groups for beginners
>
> Nelson Smith wrote:
>
> >What I don't quite understand is what
> >bad things is it doing when the joblog
> >shows that no activation groups were
> >in fact reclaimed.
>
> Remember that activating a program happens once per AG, whilst running it
> can happen many times.  Let me guess and see if this is your situation:
>
> OPM CL
>   CALL RPGLE *CALLER
>     CALLP xxx *SRVPGM AG(QILE)
>       return
>     seton LR
>   RCLACTGRP *ELIGIBLE
>
> When the OPM CL calls the RPGLE the first time in this job (8.00AM), it
> gets
> activated in the *DAG because of *CALLER.  During it's activation, it also
> activates the service program.  The service program goes in AG(QILE).  The
> RPGLE does his thing, calling procedures in the service program until it's
> all done.  It sets on LR and returns to the CL program.
>
> At this point, we have two AGs in use: *DAG and QILE.  No programs are
> using
> resources in QILE so it's eligible to be reclaimed.
>
> The CL does his RCLACTGRP and destroys QILE.  The CL program terminates.
> So
> far, so good.  Time passes (it's not 15.00PM) and the CL program gets
> called
> again.  The RPGLE does NOT get activated again because it was already
> activated for the *DAG.  That means the destroyed service program also
> does
> not get activated.  When the RPGLE tries to callp a procedure in the
> non-existent service program, BOOM.
>
> It runs once but falls over later.  In the second execution, the RCLACTGRP
> won't reclaim anything, because nothing activated QILE.  So, the pass at
> 8.00 runs and the job log should show 1 group reclaimed.  The pass at
> 15.00
> will issue the MCH3402, but can't reclaim anything.
>
> Does this match your scenario?
>   --buck
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information 
which maybe confidential or privileged and is intended only for the individual 
or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the 
contents of this message.
All personal messages express views solely of the sender, which are not to be 
attributed to Lincare Holdings Inc., and may not be copied or distributed 
without this disclaimer.
If you received this message in error, please notify us immediately at 
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************