TMS is working like a charm.  When I pull out catalogued datasets that are on 
tape under TMS control, they are delete as requested.
Our problem is with datasets on disk that are migrated by HSM.
We don't seem to have any expiry date on the catalog for any dataset.
I did come across some expiry dates in the catalog that were older than the 
creation date.
Go figure!
My focus is only on SMS managed datasets and volumes.
What will happen if I set the HSM SETSYS EXPIREDDATASETS parameter?
Will the system go crazy deleting what I estimate to be over 100,000 datasets?
Uriel


________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
retired mainframer [[email protected]]
Sent: Friday, September 21, 2012 3:43 PM
To: [email protected]
Subject: Re: DFSMSHSM is a not deleting expired datasets

If the tape datasets are still catalogued, then the TMS is not doing its job
completely.  The catalog should not have an entry that points to a
volser/fileseq that does not match what is in the TMS database.

In addition to the management class parameters for DASD datasets, other
factors can affect when a dataset is deleted.  Possibilities include:
     Expiration date in the catalog entry
     Setting of the HSM SETSYS EXPIREDDATASETS parameter
     Threshold parameter in the storage group for an SMS volume
     Setting of the HSM ADDVOL THRESHOLD parameter for an ML1 or non-SMS
primary volume

:>: -----Original Message-----
:>: From: IBM Mainframe Discussion List [mailto:[email protected]] On
:>: Behalf Of Uriel Carrasquilla
:>: Sent: Friday, September 21, 2012 10:25 AM
:>: To: [email protected]
:>: Subject: DFSMSHSM is a not deleting expired datasets
:>:
:>: I listed three high level qualifiers (HLQ) and found 27,000 datasets
:>: that were catalogued, some of them on disk, some of them on HSM (ML-1 or
:>: ML2) and some other on tapes (TMS).
:>:
:>: Found that TMS is doing its job and expired datasets were gone.
:>:
:>: With thos dasets on DASD and under HSM (migrated), found the MGT-CLASS
:>: and calculated when they were supposed to be expired (either from last
:>: reference or days since creation).  Talked to my business users and
:>: confirmed that the datasets are supposed to be gone.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to