Normally, the expired datasets are cleaned up during HSM's Primary & Secondary Space management. What time do these run in your shop?
Regards, Hervey -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Uriel Carrasquilla Sent: Friday, September 21, 2012 1:25 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. What I found is that somehow from around 1998, nothing ever got delete again (we have been running MVS/zOS for the last 40 years). The sad story, it seems that 21,000 datasets should be removed. I suspect that I will find the same story with my other 100 HLQ or so for my applications. Is there such a thing as a parameter in DFSMSHSM that is supposed to do the actual delete? Is this the normal way that zOS operates, in which case, why bother writing ACL rules for SMS? What is your experience at your shop? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
