I run with USERDATASETSERIALIZATION and since I have many potentially multi volume PS datasets (Stripped/Extended in default dataclass), I really need to continue this. I also do EXPIREDDATASETS(SCRATCH). I also have disk datasets created with EXPDT=98nnn because I implemented TMM long ago. I have a process in place to detect and ALTER dsname NULLIFY RETENTION these and allow the MGMTCLAS (which is derived from EXPDT) to control expiration. Recently, the applications people shifted some processing around and found the window to create and then DFHSM expires before I get the EXPDT reset. This caused the next job to fail :( With USERDATASETSERIALIZATION, the DFHSM Integrity Age for Space Management is set to zero days. It appears a longer Integrity Age would delay this scratching of the dataset.
I am contemplating using a PATCH to set this age to 1 or 2 and see if this keeps the dataset around long enough to reset. Does anyone have any experience or thoughts on such a DFHSM patch? Dave Gibney Information Technology Services Washington State University ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
