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
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
>I have searched the archives, and I am still a little confused about
>this. What level of server and client must I be at to have the archive
>of directories NOT use the management class that has the longest
>retention?
>From http://people.bu.edu/rbs/ADSM.QuickFacts :
ARCHmc
I have searched the archives, and I am still a little confused about
this. What level of server and client must I be at to have the archive
of directories NOT use the management class that has the longest
retention?
Server info:
AIX 4.2.1 (soon to be 4.3.2)
ADSM 3.1.2.55
Client info:
Various l
