This is just a discussion topic (Thank you Skip for making me think about this ;-O)
In the past we needed to have them as we were tight on storage. But today, is that still the case. What is a good reason to either have or don't have SPILL/OVERFLOW pools when we can just add more storage to the pool. I can add a MOD54 to a pool but that mod54 is not full until I use up all of the allotted storage to the MOD54 in the storage array. So the storage array can be over provisioned until I need to go and get management to buy more physical storage. Do I lose anything by having datasets "spill" over to a different pool that may not have the same protection as the one it is in? HSM Backup, Dump, Cleanup processes? Or are there other considerations. Just asking a question or two. So basically, why use SPILL/OVERFLOW when you can just add dasd, or do lots of migration? We have the automation tool set up to monitor the pools and if they get too full, then start migration on the datasets in that pool. No manual intervention required. DFHSM and DFSMS do not think like humans when it comes to dataset management. So there a need to out maneuver them to make datasets go where we want. Lizette Koehler statistics: A precise and logical method for stating a half-truth inaccurately ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
