Jack, Unfortunately timing was my enemy here. For the purpose of the test, I set the mgmt class to 5 days. Initially I had created the datasets (simple 3.4 allocate) without opening them. 5 days came and went, and the datasets didn't go away. Being that I had never opened the datasets, HSM apparently didn't feel the need to back them up. About the time I was starting to pose the questions to the group about it, I decided to update one of the datasets so HSM would see the change and back it up. I think I changed the MGMTCLASS to nobackup about - um - 5 days later. However, when I changed to nobackup both of my test datasets went away, the one that had been modified and the empty dataset.
Because the one that hadn't been changed also got deleted, I am figuring that it was the nobackup that caused the deletes to happen. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Kelly Sent: Thursday, August 20, 2009 10:50 AM To: IBM-MAIN@bama.ua.edu Subject: Re: DFSMS and deleting expired data sets by management class <snip> I turned off the auto backup and my test datasets were deleted when they expired. <unsnip> Rex, now you have me really mystified. I thought that the thread indicated that you had HSM backup the DSNs (DCLASS, DSORG, etc) but they wouldn't delete. Now it appears that you changed the MGMTCLAS to 'no backup' and they delete OK? Jack Kelly 202-502-2390 (Office) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
