As I said, all of our Mgmt Classes specify 1 backup (for both 'exists'
and 'deleted') and "365" for both Retain Days attributes.
What was said was "almost" 8000, actually it was 7,720 days (at the time of
the report). And that would be just about the time *we* implemented HSM.
About 21 years, just about 1985.
Maybe it's an instance of HSM "keeping extraneous information hanging
around", as Bob said back on the 15th. And I'm trying to deal with it!
Hundreds of HSM tapes that CA-1 says were created 1999, 2000, 2001; just a
few dozen in 2006.
Larry M. Burch
City of Albuquerque
Albuquerque NM USA 87102
On Fri, 22 Dec 2006 09:54:38 -0500, Richards.Bob
<[EMAIL PROTECTED]> wrote:
>Heck, that almost makes it pre-HSM! :-)
>
>Bob Richards
>
>
>
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
>Behalf Of O'Brien, David W. (NIH/CIT) [C]
>Sent: Friday, December 22, 2006 9:05 AM
>To: [email protected]
>Subject: Re: Deleting HSM Backups questions
>
>I believe the original post mentioned backups with an age of 8000 days
>or more. That would make them pre-SMS.
>
>________________________________
>
>From: Friske, Michael [mailto:[EMAIL PROTECTED]
>Sent: Fri 12/22/2006 8:58 AM
>To: [email protected]
>Subject: Re: Deleting HSM Backups questions
>
>
>
>For SMS managed data sets, EXPIREBV uses what is specified in the
>MGMTCLAS to determine when to delete old backup versions.
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
