Re: DFSMS and deleting expired data sets by management class
Colleen and the others who responded to my request, Just as a wrap-up on this issue, it appears as though I needed to shut off the auto backup on these datasets before they would go away. I turned off the auto backup and my test datasets were deleted when they expired. I ran a couple more tests to verify this as well. Thanks everybody for your help and input on this. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Pommier, Rex R. Sent: Friday, August 14, 2009 4:55 PM To: IBM-MAIN@bama.ua.edu Subject: Re: DFSMS and deleting expired data sets by management class Colleen, I'll try turning backup off and see if they go away tonight. Just for my own knowledge, with the number of datasets deleted set to 1, I have to have a backup before it will allow expiration? I was under the impression that this was more of a maximum number of backups to keep for a deleted dataset. IOW, in this case, I have # backups of deleted set to 1, # of backups of active dataset set to 3, and retain days only backup set to 2. Given these numbers I thought the system would keep up to 3 backups of primary datasets, and when the primary gets deleted, it would also delete any backups I have greater than one, if they exist, and then after 2 days delete the last backup. I didn't think it required a backup before deleting the primary. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 4:39 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by managment class Hi Rex, You have auto backup turned on and you have # of data sets data set deleted set to 1. Turn backup off and they'll expire or you'll need to use the patch you found. If you are only wanting to keep them for 5 days after last reference then I'm guessing that a backup isn't necessary. Colleen Gordon -- 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
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
Re: DFSMS and deleting expired data sets by management class
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
Re: DFSMS and deleting expired data sets by management class
snip From my SMS construct, I have the expire non usage set to 5 days: unsnip Since we seem to be to the point of 'grasping at straws', I would add 'are you sure the DSN has 5 days of non use'? I've had problem with things, eg dumps, scans, etc, causing the reference date to be updated. Haven't had the problem lately but I haven't looked either. I don't think that there's a patch like the MGCB.+26 patch for SMS available for deleting but I'm surprised that HSM doesn't give an error message if it's trying to delete the DSN and can't. Neal's point about Auto Migrate, or something like that, has to be the issue. Not much help but thinking 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
Re: DFSMS and deleting expired data sets by management class
Hi Colleen, Both of the datasets that I allocated are defined as PS. From a 3.4 listing of one of the test datasets: Data Set Name . . . . : I.RRP.JUNK General DataCurrent Allocation Management class . . : MCINTUATAllocated tracks . : 1 Storage class . . . : SCSTD Allocated extents . : 1 Volume serial . . . : ZD2001 Device type . . . . : 3390 Data class . . . . . : DCSTD Current Utilization Organization . . . : PS Used tracks . . . . : 0 Record format . . . : FB Used extents . . . : 0 Record length . . . : 80 Block size . . . . : 27920 1st extent tracks . : 1 Secondary tracks . : 1 Data set name type : SMS Compressible : NO Creation date . . . : 2009/08/06 Referenced date . . : 2009/08/07 Expiration date . . : ***None*** -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 1:17 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by management class HSM cannot manage a data set with DSORG unknown. You must assign a dataclass for HSM to manage it. If a data set is eligible for expiration but space management is not expiring it; this indicates that there could be a problem with the records in the MCDS. You'll need to audit the MCDS to see what the errors are and correct them. If the data sets are not eligible for expiration but your want to expire them anyway; you'll have to HDELETE them. Colleen Gordon -- 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 -- 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
Re: DFSMS and deleting expired data sets by management class
On this one, I do know that the ***NONE*** is not a factor in HSM EXPIRE processing as Rex desires. I had my MCTEMP and MCWEEK working for years before I expanded my DFHSM set-up to honor EXPDT and RETPD from JCL. Dave Gibney Information Technology Services Washington State University -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 1:31 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by management class Data Set Name . . . . : I.RRP.JUNK Here's the problem Rex, the expiration data is NONE. When do you want the data sets to expire? X days after creation or x days after last reference date? Setup the management class to expire the data sets in one way or another and they'll expire. General Data Current Allocation Management class . . :MCINTUAT Allocated tracks . : 1 Storage class . . . : SCSTDAllocated extents . : 1 Volume serial . . . : ZD2001 Device type . . . . : 3390 Data class . . . . . : DCSTD Current Utilization Organization . . . : PS Used tracks . . . . : 0 Record format . . . : FB Used extents . . . : 0 Record length . . . : 80 Block size . . . . : 27920 1st extent tracks . : 1 Secondary tracks . : 1 Data set name type : SMS Compressible : NO Creation date . . . : 2009/08/06 Referenced date . . : 2009/08/07 Expiration date . . :***None*** Colleen Gordon -- 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 -- 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
Re: DFSMS and deleting expired data sets by management class
Colleen, I thought the expiration date in this screen was only populated if I put an EXPDT or RETPD in the JCL I used to create it. From what I read in the manuals, the MGMT class expire non-usage is used when the dataset doesn't have an expiration date on it. From my SMS construct, I have the expire non usage set to 5 days: SMS constructs (with extra lines deleted): LINE MGMTCLASEXPIRE EXPIRERET OPERATOR NAMENON-USAGE DATE/DAYSLIMIT ---(1) --(2)------(3)--- ---(4) --(5)-- MCINTUAT5 NOLIMIT NOLIMIT Rex -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 3:31 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by management class Data Set Name . . . . : I.RRP.JUNK Here's the problem Rex, the expiration data is NONE. When do you want the data sets to expire? X days after creation or x days after last reference date? Setup the management class to expire the data sets in one way or another and they'll expire. General Data Current Allocation Management class . . :MCINTUAT Allocated tracks . : 1 Storage class . . . : SCSTDAllocated extents . : 1 Volume serial . . . : ZD2001 Device type . . . . : 3390 Data class . . . . . : DCSTD Current Utilization Organization . . . : PS Used tracks . . . . : 0 Record format . . . : FB Used extents . . . : 0 Record length . . . : 80 Block size . . . . : 27920 1st extent tracks . : 1 Secondary tracks . : 1 Data set name type : SMS Compressible : NO Creation date . . . : 2009/08/06 Referenced date . . : 2009/08/07 Expiration date . . :***None*** Colleen Gordon -- 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
Re: DFSMS and deleting expired data sets by management class
Colleen, Not a problem. I followed that rabbit earlier which is how I found the page in the manual that explained the use of **none** in the expiration date. Here is the mgmt class def'n. Hopefully line wrap won't mess it up too bad. LINE MGMTCLASEXPIRE EXPIRERETPARTIAL OPERATOR NAMENON-USAGE DATE/DAYSLIMIT RELEASE ---(1) --(2)------(3)--- ---(4) --(5)-- (6) MCINTUAT5 NOLIMIT NOLIMIT CONDITIONAL PRIMARY LEVEL 1 CMD/AUTO # GDG ON ROLLED-OFF BACKUP DAYS DAYS MIGRATE PRIMARY GDS ACTION FREQUENCY ---(7)-- --(8)-- --(9)--- --(10)-- ---(11)--- --(12)--- 10 35 BOTH --- --- 0 # BACKUPS# BACKUPS RETAIN DAYS RETAIN DAYS (DS EXISTS) (DS DELETED) ONLY BACKUP EXTRA BACKUPS ---(13) (14) ---(15) (16)- 3 12 1 ADM/USER AUTOLAST MOD LAST DATE LAST TIME BACKUPBACKUP USERIDMODIFIEDMODIFIED --(17)-- -(18)- --(19)-- ---(20)--- --(21)--- BOTH YES RRP 2009/08/05 11:49 Fields 22-38 are all blank. BACKUP COPY ABACKUP COPY TECHNIQUE TECHNIQUE (39) (40) STANDARD STANDARD -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 4:03 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by management class Hi Rex, Yes, you're right. Sorry about that. Can you cut and paste the entire management class definition? Backup shouldn't have anything to do with it unless you have backup turned on in the management class. Colleen Gordon -- 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 -- 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
Re: DFSMS and deleting expired data sets by management class
Colleen, I'll try turning backup off and see if they go away tonight. Just for my own knowledge, with the number of datasets deleted set to 1, I have to have a backup before it will allow expiration? I was under the impression that this was more of a maximum number of backups to keep for a deleted dataset. IOW, in this case, I have # backups of deleted set to 1, # of backups of active dataset set to 3, and retain days only backup set to 2. Given these numbers I thought the system would keep up to 3 backups of primary datasets, and when the primary gets deleted, it would also delete any backups I have greater than one, if they exist, and then after 2 days delete the last backup. I didn't think it required a backup before deleting the primary. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Colleen Gordon Sent: Friday, August 14, 2009 4:39 PM To: IBM-MAIN@bama.ua.edu Subject: DFSMS and deleting expired data sets by managment class Hi Rex, You have auto backup turned on and you have # of data sets data set deleted set to 1. Turn backup off and they'll expire or you'll need to use the patch you found. If you are only wanting to keep them for 5 days after last reference then I'm guessing that a backup isn't necessary. Colleen Gordon -- 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 -- 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
