Re: DFSMSHSM is a not deleting expired datasets
A couple of things to check (not mentioned so far): May be HSM is trying delete these datasets, or at least some of them, but is being unsuccessful for some reason. Check the HSM activity logs for possible errors. Also remember that HSM will only delete expired datasets if HSM is managing the particular volume(s). For non-SMS volumes (ADDVOLed with AUTOMIG turned on) and for SMS volumes the storage group containing the volumes must be defined with AM=Y. Richard Marchant -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: 24 September 2012 05:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets From DFHSM Storage Adminstration. EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates Explanation: EXPIREDDATASETS(SCRATCH | NOSCRATCH) is an optional parameter specifying whether or not DFSMShsm should scratch data sets having explicit expiration dates when the date has passed (data set has expired). SMS-managed data sets not having explicit expiration dates are expired when they have met their management class expiration criteria. Note: Explicit expiration dates can be set by JCL, utility parameters, Data Class Expiration parameters, or Data Class Retention parameters. The explicit expiration date for a data set can be found in the data set's VTOC entry. SCRATCH specifies that DFSMShsm scratch data sets that have an expired expiration date when it performs space management and migration cleanup. NOSCRATCH specifies that DFSMShsm ignore the expiration date. DFSMShsm processes the data set as if the expiration date has not been reached. SMS relationship: Parameter applies in some instances to SMS-managed DASD volumes or data sets. SETSYS defaults: None. DFSMShsm defaults: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is not to scratch the expired data sets. Typically, ML2 datasets and BACKUP datasets reside on tape. If the datasets are not expired, no tapes will be released except by recycle or manual deletion. Once all of the datasets on a particular tape are released (via RECYCLE, HDEL, or HBDEL), DFHSM will notify the EDM to expire the tape, and return it to the scratch pool. Caveat. It is possible to set up DFHSM tape pooling, in which case, the tape will be returned to the DFHSM pool, instead of the scratch pool and the EDM will not be invoked. snip I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 /snip snip -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan snip Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. /snip snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip -- 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
Re: DFSMSHSM is a not deleting expired datasets
Thanks to all respondents. A big thanks to Richard for the suggestions. At this point, my management is concerned about changing anything because there must be a reason it's set this way. Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Richard Marchant richard.march...@shoden.co.za To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 09:18 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU A couple of things to check (not mentioned so far): May be HSM is trying delete these datasets, or at least some of them, but is being unsuccessful for some reason. Check the HSM activity logs for possible errors. Also remember that HSM will only delete expired datasets if HSM is managing the particular volume(s). For non-SMS volumes (ADDVOLed with AUTOMIG turned on) and for SMS volumes the storage group containing the volumes must be defined with AM=Y. Richard Marchant -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: 24 September 2012 05:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets From DFHSM Storage Adminstration. EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates Explanation: EXPIREDDATASETS(SCRATCH | NOSCRATCH) is an optional parameter specifying whether or not DFSMShsm should scratch data sets having explicit expiration dates when the date has passed (data set has expired). SMS-managed data sets not having explicit expiration dates are expired when they have met their management class expiration criteria. Note: Explicit expiration dates can be set by JCL, utility parameters, Data Class Expiration parameters, or Data Class Retention parameters. The explicit expiration date for a data set can be found in the data set's VTOC entry. SCRATCH specifies that DFSMShsm scratch data sets that have an expired expiration date when it performs space management and migration cleanup. NOSCRATCH specifies that DFSMShsm ignore the expiration date. DFSMShsm processes the data set as if the expiration date has not been reached. SMS relationship: Parameter applies in some instances to SMS-managed DASD volumes or data sets. SETSYS defaults: None. DFSMShsm defaults: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is not to scratch the expired data sets. Typically, ML2 datasets and BACKUP datasets reside on tape. If the datasets are not expired, no tapes will be released except by recycle or manual deletion. Once all of the datasets on a particular tape are released (via RECYCLE, HDEL, or HBDEL), DFHSM will notify the EDM to expire the tape, and return it to the scratch pool. Caveat. It is possible to set up DFHSM tape pooling, in which case, the tape will be returned to the DFHSM pool, instead of the scratch pool and the EDM will not be invoked. snip I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 /snip snip -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan snip Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. /snip snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip -- For IBM
Re: DFSMSHSM is a not deleting expired datasets
Steve Conway wrote: At this point, my management is concerned about changing anything because there must be a reason it's set this way. Probably yes. Perhaps the (previous) owners wanted to keep them due to some policy/rule. Is it possible for you to list them by 'last used' date and then backup/dump them before going to have HSM deal with them 21000 datasets? Of course, I'm aware that such step could change the expired status of those datasets, but I'm just wondering... Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Interesting thought, Elardus, but I'm just going to leave it alone for now. It's not like I don't have anything to keep me busy. :-) Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Elardus Engelbrecht elardus.engelbre...@sita.co.za To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 10:06 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Steve Conway wrote: At this point, my management is concerned about changing anything because there must be a reason it's set this way. Probably yes. Perhaps the (previous) owners wanted to keep them due to some policy/rule. Is it possible for you to list them by 'last used' date and then backup/dump them before going to have HSM deal with them 21000 datasets? Of course, I'm aware that such step could change the expired status of those datasets, but I'm just wondering... Groete / Greetings Elardus Engelbrecht -- 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
Re: DFSMSHSM is a not deleting expired datasets
Are you doing the release expirebv command on some schedule? font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
EXPIREBV will never touch an ML0/ML1/ML2 dataset. It deals only with backup copies of datasets. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Michael Wickman :: Sent: Tuesday, September 25, 2012 7:57 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFSMSHSM is a not deleting expired datasets :: :: Are you doing the release expirebv command on some schedule? :: :: :: :: :: :: :: font size=1 :: div style='border:none;border-bottom:double windowtext :: 2.25pt;padding:0in 0in 1.0pt 0in' :: /div :: This email is intended to be reviewed by only the intended recipient :: and may contain information that is privileged and/or confidential. :: If you are not the intended recipient, you are hereby notified that :: any review, use, dissemination, disclosure or copying of this email :: and its attachments, if any, is strictly prohibited. If you have :: received this email in error, please immediately notify the sender by :: return email and delete this email from your system. :: /font :: :: -- :: 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
Re: DFSMSHSM is a not deleting expired datasets
Hi, Michael. Not that I know of. Where would that commonly be specified? Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Michael Wickman mwick...@waddell.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 11:06 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Are you doing the release expirebv command on some schedule? font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font -- 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
Re: DFSMSHSM is a not deleting expired datasets
HSEND SETSYS EXPIREDDATASETS(SCRATCH). And yes, it will do all of them the first time SEC SPACE MGMT runs. Just bite the bullet HTH, snip I did a TSO HSEND QUERY SETSYS and noticed that I have scheduled space mgt for primary on (0600, 1800) and for secondary on (2400, 0459). But I also noticed that the Scratch expired Data Sets is set to NO. That could be the problem. How do I turn it on? I am taking it to higher authorities because I will be deleting a massive amount of data. I suspect I will have to create JCL with TSO Batch to HDELETE the expired datasets. At that point I should turn on the parameter to let DFSMSHSM do its job. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
All, I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Staller, Allan allan.stal...@kbmg.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/24/2012 10:13 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU HSEND SETSYS EXPIREDDATASETS(SCRATCH). And yes, it will do all of them the first time SEC SPACE MGMT runs. Just bite the bullet HTH, snip I did a TSO HSEND QUERY SETSYS and noticed that I have scheduled space mgt for primary on (0600, 1800) and for secondary on (2400, 0459). But I also noticed that the Scratch expired Data Sets is set to NO. That could be the problem. How do I turn it on? I am taking it to higher authorities because I will be deleting a massive amount of data. I suspect I will have to create JCL with TSO Batch to HDELETE the expired datasets. At that point I should turn on the parameter to let DFSMSHSM do its job. /snip -- 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
Re: DFSMSHSM is a not deleting expired datasets
Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. HTH, snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Staller, Allan allan.stal...@kbmg.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/24/2012 10:13 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU HSEND SETSYS EXPIREDDATASETS(SCRATCH). And yes, it will do all of them the first time SEC SPACE MGMT runs. Just bite the bullet HTH, snip I did a TSO HSEND QUERY SETSYS and noticed that I have scheduled space mgt for primary on (0600, 1800) and for secondary on (2400, 0459). But I also noticed that the Scratch expired Data Sets is set to NO. That could be the problem. How do I turn it on? I am taking it to higher authorities because I will be deleting a massive amount of data. I suspect I will have to create JCL with TSO Batch to HDELETE the expired datasets. At that point I should turn on the parameter to let DFSMSHSM do its job. /snip -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Allan, I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Monday, September 24, 2012 10:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. HTH, snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
From DFHSM Storage Adminstration. EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates Explanation: EXPIREDDATASETS(SCRATCH | NOSCRATCH) is an optional parameter specifying whether or not DFSMShsm should scratch data sets having explicit expiration dates when the date has passed (data set has expired). SMS-managed data sets not having explicit expiration dates are expired when they have met their management class expiration criteria. Note: Explicit expiration dates can be set by JCL, utility parameters, Data Class Expiration parameters, or Data Class Retention parameters. The explicit expiration date for a data set can be found in the data set's VTOC entry. SCRATCH specifies that DFSMShsm scratch data sets that have an expired expiration date when it performs space management and migration cleanup. NOSCRATCH specifies that DFSMShsm ignore the expiration date. DFSMShsm processes the data set as if the expiration date has not been reached. SMS relationship: Parameter applies in some instances to SMS-managed DASD volumes or data sets. SETSYS defaults: None. DFSMShsm defaults: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is not to scratch the expired data sets. Typically, ML2 datasets and BACKUP datasets reside on tape. If the datasets are not expired, no tapes will be released except by recycle or manual deletion. Once all of the datasets on a particular tape are released (via RECYCLE, HDEL, or HBDEL), DFHSM will notify the EDM to expire the tape, and return it to the scratch pool. Caveat. It is possible to set up DFHSM tape pooling, in which case, the tape will be returned to the DFHSM pool, instead of the scratch pool and the EDM will not be invoked. snip I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 /snip snip -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan snip Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. /snip snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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
Re: DFSMSHSM is a not deleting expired datasets
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
Re: DFSMSHSM is a not deleting expired datasets
One trap I fell into was the backup. If a dataset is not backed up, DFhsm won't delete it, even if it's expired. * * *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-251* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Eight Consecutive Years* On Fri, Sep 21, 2012 at 1:59 PM, Hervey Martinez hervey.marti...@custserv.com wrote: 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 -- *Accredited District Since 2008; Re-certification - January 2013* Home of Florida's first LEED Gold Certified School Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
There is a patch for this. See the DFHSM Diagnosis manual. Look for DBU (delete backed up). snip One trap I fell into was the backup. If a dataset is not backed up, DFhsm won't delete it, even if it's expired. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
TMS is working like a charm. When I pull out catalogued datasets that are on tape under TMS control, they are delete as requested. Our problem is with datasets on disk that are migrated by HSM. We don't seem to have any expiry date on the catalog for any dataset. I did come across some expiry dates in the catalog that were older than the creation date. Go figure! My focus is only on SMS managed datasets and volumes. What will happen if I set the HSM SETSYS EXPIREDDATASETS parameter? Will the system go crazy deleting what I estimate to be over 100,000 datasets? Uriel From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of retired mainframer [retired-mainfra...@q.com] Sent: Friday, September 21, 2012 3:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets If the tape datasets are still catalogued, then the TMS is not doing its job completely. The catalog should not have an entry that points to a volser/fileseq that does not match what is in the TMS database. In addition to the management class parameters for DASD datasets, other factors can affect when a dataset is deleted. Possibilities include: Expiration date in the catalog entry Setting of the HSM SETSYS EXPIREDDATASETS parameter Threshold parameter in the storage group for an SMS volume Setting of the HSM ADDVOL THRESHOLD parameter for an ML1 or non-SMS primary volume :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Uriel Carrasquilla :: Sent: Friday, September 21, 2012 10:25 AM :: 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. -- 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
