I'm sure there are tools, but I never had the luxury of acquiring any of them. I simply managed the SMS environment.
You need to understand your DFSMS and DFSMShsm environments *and* the current rules/values your predecessors set up. Big questions: Do you have enough ENABLED capacity in your pools? What are the threshold settings? What are your various criteria for migrating datasets in the first place? Are your management classes for the various datasets/pools meeting your needs? And several dozen other questions that, once the answers are known, will dictate the best setup of dataset migration and freespace management values in your environment. Simply migrating datasets to bring volume freespace up satisfies available volume freespace temporarily, but understanding the activity of the datasets and their migration values will allow you to identify and address the thrashing issue(s). Or just throw more enabled volumes into the various pools until the thrashing stops. But that is the lazy way out and does nothing about your understanding of your environment and is a short term fix at best. Bob -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Dave Jousma Sent: Thursday, November 4, 2021 7:36 AM To: [email protected] Subject: Re: automated SMS Storage pool management >Dave, > >Do you have DFSMShsm? If so, turn on Interval Migration and it manage the % >threshold of freespace for you. > >If you do not have DFSMShsm, what do you have? > >Bob Thanks Bob, we do have HSM. Sorry, I'm not well-versed in this area. Are there tools to know when you need to add capacity vs thrashing and continually migrating? ---------------------------------------------------------------------- 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
