RE: activation groups and rclrsc

FYI, the *ELIGIBLE option should NOT be used in a production job stream.  It
it much better to reclaim the specific AG that you wish to reclaim.
*ELIGIBLE is overkill for your purpose.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Horn
Sent: Monday, January 09, 2006 3:54 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: activation groups and rclrsc


Thanks Richard

I think that is the answer I was looking for.

Jim


------------------------------

message: 6
date: Mon, 9 Jan 2006 16:52:06 +0100
from: "Richard ECUYER" <recuyer@xxxxxxx>
subject: Re: activation groups and rclrsc

perhaps with a rlcactgrp *eligible (clear all activation groups opened)

----- Original Message ----- 
From: "Jim Horn" <jimh@xxxxxxxxxxxxxx>
To: "Rpg400-L@Midrange. Com" <rpg400-l@xxxxxxxxxxxx>
Sent: Monday, January 09, 2006 4:10 PM
Subject: activation groups and rclrsc


> I know that previously there was much discussion on this,
> but -
>
> We currently have many programs that run in the default
> activation group and some in *caller.  We even have some old
> s36 stuff.
>
> We have  a situation where some users process multiple
> companies by calling a cl program that changes the current
> library.  This worked fine in the old opm model, but is not
> working for programs that use service programs that open
> files .  Would it work to put a rclrsc command in the cl
> program that changes the current library?
>
> We are trying to implement the new/caller activation group
> option, but we have a lot of programs that sometimes are the
> caller and sometimes are the callee so sorting this out is
> somewhat of a challenge.
>
> Thanks
> Jim Horn
>
>