In <0012900002759397000002*@MHS>, on 02/24/98
   at 03:07 PM, Jerry Lawson <jlawson AT THEHARTFORD DOT COM> said:

>Reinhard -

>You are correct and I was wrong :-(

>I did some research and tests here, and found some things I
>am not quite comfortable with.  I set up an Archive
>copygroup with 10 days retention, archived a file, then
>changed the copygroup to 30 days, and then activated the
>changes.  Sure enough, the file now had a 30 day retention.
>I checked my V2 manuals, and the Update Copygroup command
>says that the changes are applied to all files bound to
>this class.  This is consistent with what I found, and what
>you pointed out.

(snip)

I agree with the way it works.  It is what I would expect.
I come from and MVS storage management background and this
is how DFsms works. And the ADSM design was modeled on MVS
dfsms, at least the policy part  was.

"Policy" is paramount!  If the managers are paying attention
and decree  a change in policy, the techies can turn one
knob and effect the change for all the backups in ADSM and
all future backups.  Now if only the managers could
understand the power they have with ADSM!

Bill Colwell
Draper Lab