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 [email protected] From: "Staller, Allan" <[email protected]> To: [email protected] Date: 09/24/2012 10:13 AM Subject: Re: DFSMSHSM is a not deleting expired datasets Sent by: IBM Mainframe Discussion List <[email protected]> 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 [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
