RE: Service Program Question.

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

I can see how _very_ careful planning could allow you to do that.  You do
have to make sure that a routine that gets called thousands of times in a
batch process is not *NEW.  I think the danger is in having to rely on very
careful planning.  Some idiot like me could come along and ruin everything.
<g>

I think your approach can work, but I'm not sure it would work for me.  To
tell the truth, I haven't found a good use for a named activation group yet
either.  "Reg" resource scoping seems to fit all the jobs we run.  No shared
open data paths, no special file override considerations, no commitment
control.  I tend to compile everything *CALLER.  I know that that's not
considered good practice either.

> -----Original Message-----
> From: Sims, Ken [mailto:KSIMS@SOUTHERNWINE.com]
> Sent: Friday, April 07, 2000 9:56 AM
> To: rpg400-l@midrange.com
> Subject: RE: Service Program Question.
> 
> 
> Hi Jon, Joel, et.al. -
> 
> > >> RCLACTGRP *ELIGIBLE can lead to unexpected results if 
> >there are several activation groups going at the same time.  
> >I believe it's safer to reclaim them by name.
> >
> >I'm with Joel on this one.  I'm firmly of the opinion that 
> >IBM only put *ELIGIBLE in to simplify their own testing.  
> >The only time I _ever_ feel it is safe to use is when testing 
> >- there's too many opportunities for screw-ups to use it in 
> >production.
> 
> Personally, I never need RCLACTGRP either *ELIGIBLE _or_ by 
> name.  I have
> never [yet] found a good use for a named activation group.  All of my
> programs that take advantage of activation groups are either 
> ACTGRP(*NEW) or
> ACTGRP(*CALLER).  As a result the activation groups reclaim 
> themselves when
> the ACTGRP(*NEW) program ends.
> 
> Ken
> Southern Wine and Spirits of Nevada, Inc.
> Opinions expressed are my own and do not necessarily 
> represent the views of
> my employer or anyone in their right mind.
> 
> 
+---
| 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
+---