Ok, I found it (I think). One client was at 3.1.0.6, and that is what
caused the high-retention MC.
Thanks again...
-Tom
Yep, we are using the archmc parm, and this morning I had an archive
run from a client that did specifically use the management class with
the longest retention. It looks to me that this APAR was fixed at
server level 3.1.2.30. But 3.1.0.7 client code is also mentioned.
The way I found this is that I had one management class mis-defined and
it was going directly to tapes. Since I am converting from 3490s to
3590Es, I am watching tape usage very very closely. I was done with my
migration and this morning I had one new 3490 tape used. The management
class used on the archmc parm was to keep the data for 30 days, but the
tape MC was for 3 years (and offsite).
So what gives?
Tom Melton
Emory HealthCare
Emory University
>>> [EMAIL PROTECTED] 10/05/00 12:33PM >>>
As of ADSMv3.1 mid-1999 APAR
IX89638
(PTF 3.1.0.7), archived
directories are
not bound to the management
class with
the longest retention.
Richard Sims, BU
