Verify the actually assigned management class for the datasets in question. It may not be the one you think it is. Actually, IIRC, by default, the dataset cannot be deleted from ML2 if there is no backup.
There is a patch available in the DFHSM Implementation/Customization Guide to change this behavior. http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com. ibm.zos.r11.arci000/disdbu.htm Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664 3565 | [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Phil Kingston Sent: Friday, June 08, 2012 4:50 AM To: [email protected] Subject: DFHSM Secondary Space Management All, I have a management class that is supposed to delete selected datasets after 30days non usage. The datasets end up on either ML1 or ML2. It appears though that HSM secondary space management is not deleteing these and were getting a build up of datasets which should have been deleted. The key parts of management class DEL030 are as follows: Expire Non-usage 30 Expire date/days NOLIMIT Primary Days 5 Level 1 Days 21 ADM/USER Backup BOTH Auto Backup NO (was YES. Changed to NO yesterday!) The Storage Group has Auto Backup set to yes. HSM performs NO auto backup though. Any ideas why my datasets don't get deleted? Regards, Phil Kingston ---------------------------------------------------------------------- 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
