HIPER..

3.1.2.x expiration issue.  Versioning parameters in copygroups are ignored,
thus expiration doesn't occur.  And really does a number of your system in
terms of space.

ADSML

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Steve Harris
> Sent: Sunday, August 29, 1999 7:14 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ADSM for MVS 3.1.2.0
>
>
> Jeryl,
>
> I'm running ADSM AIX 3.1.2.0 and have had no problems, albeit our
> adsm use is
> fairly limited.  I've seen the horror stories about the various
> maintenance
> levels on this list, and despite my asking a couple of times
> no-one has been
> able to tell me what the hiper bug was to make them move away
> from 3.1.2.0.
>
> There *have*  been some enhancements along the way, but they're
> not enough to
> make me move:  I'll wait for the new TSM release to settle unless
> some serious
> bug bites me.
>
> Steve Harris
> AIX/ADSM/Oracle and HACMP Guy
> The Wesley Hospital, Brisbane Australia
>
> I'd rather be singing Barbershop Harmony!
>
>
>
>
>
>
>
>
>
> Jeryl Greene <Jgreene AT WPO.IT.LUC DOT EDU> on 08/28/99 03:32:31 AM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
>
>
>
>
>
>  To:      ADSM-L AT VM.MARIST DOT EDU
>
>  cc:      (bcc: Steve Harris/Wesley)
>
>
>
>  Subject: ADSM for MVS 3.1.2.0
>
>
>
> Fax to:
>
>
>
>
>
> Hi!
>
> I've just put up ADSM for MVS 3.1.2.0 in test. What is a good (safe)
> level to be at? I've seen 3.1.2.20, 3.1.2.30 & 3.1.2.40. I'll be
> converting from 2.1.0.13.
>
> Thanks.
>
>
>
> .