>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
