I've got just the opposite thought. I would probably be "disturbed" if a dataset that I wanted to delete wouldn't go because it doesn't have a backup. I'm thinking of the situation where, for example, at my site we use a specific naming convention for SMS-managed datasets that are "temporary" in that they are only used for a job or a few jobs then are deleted. They aren't "permanent" datasets that have to hang around for days or longer. We keep them around for restarts and reruns, but at the end of their needed time in the batch cycle, they are deleted. It would cause misery to revamp our batch stream to change it to accommodate the idea that these short-term datasets couldn't be deleted until they have been backed up.
"I told you to delete, now go away already!!!" :-) Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gibney, Dave Sent: Friday, August 14, 2009 1:55 PM To: [email protected] Subject: Re: DFSMS and deleting expired datasets by management class I honestly don't know about back-up before expire. Coleen is probably correct. I was just thinking "logically". I know I would be "disturbed" if a dataset I expected to have a backup for was expired before the backup was made. But, I can't site a case either way right now. Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Pommier, Rex R. > Sent: Friday, August 14, 2009 11:12 AM > To: [email protected] > Subject: Re: DFSMS and deleting expired datasets by management class > > Dave, > > I know DFHSM won't migrate a dataset without it being backed up > beforehand, but it won't delete one either? The manual I'm looking at > says that DFHSM processes expiration attributes before it processes > migration attributes. And in the backup section of the same manual it > says the number of backup copies of a deleted dataset says how many to > retain. It says nothing about needing to have backups before allowing > a > delete. > > I double-checked and the datasets I'm testing with have all their > attributes. > > I guess I'll wait a week and see if the one I updated will go away. > > Thanks. > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Gibney, Dave > Sent: Friday, August 14, 2009 12:45 PM > To: [email protected] > Subject: Re: DFSMS and deleting expired datasets by management class > > > Not so much as not opened. But, it won't mess with invalid datasets. > An unopened dataset could be incompletely defined (usually an unknown > DSORG). > And, usually DFHSM won't migrate or delete without a backup > existing. > > Dave Gibney > Information Technology Services > Washington State University > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Pommier, Rex R. > > Sent: Friday, August 14, 2009 10:41 AM > > To: [email protected] > > Subject: Re: DFSMS and deleting expired datasets by management class > > > > Jack, > > > > Secondary Space Mgmt runs at 23:00 every night. I see no errors in > the > > HSM sysouts. > > > > Is it possible that HSM won't touch a dataset that hasn't been > opened? > > For my test, I merely allocated some datasets then left them sit. I > > just opened one today and changed it to see if that would make any > > difference. > > > > Rex > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of John Kelly > > Sent: Friday, August 14, 2009 10:14 AM > > To: [email protected] > > Subject: Re: DFSMS and deleting expired datasets by management class > > > > <snip> > > I'm trying to get DFSMShsm to delete expired datasets based on > > management > > class > > <unsnip> > > > > Does SECONDARY SPACE MANAGEMENT run? That's where they should get > > deleted > > if in fact they have not been 'accessed' in 5 days. Also look in the > > HSM > > > > SYSOUTs for the SECONDARY SPACE MANAGEMENT (or process the FSRs) and > > see > > > > if give you and error for the DSNs that should be scratched. > > I don't think that HSM will backup a DSN that hasn't been opened, or > at > > least given the basics by a Data Class. > > > > Jack Kelly > > 202-502-2390 (Office) > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
