So, we are finally biting the bullet and making 1TB EAV volumes our standard for UCB relief, etc. One “habit” my Storage team over the years had done to mask poor dataset allocations was to make the mainly used DATACLAS multi-volume, with a max of 59 volumes. It was before my time, but I’m 99% sure that was done to avoid x37 abends for max extents. Now that we are going to EAV’s, we’ll be clearing off the mod-54’s and DISNEW them. And with a 20-1 reduction in physical volumes, there will likely be pools that had say 100 volumes, that could end up with just 5 EAV’s.
I’m not a storage guy by craft, so am wondering if there is any magic dust to help with this other than making the owners of the poorly allocated files make adjustments to their allocations? Dave Jousma Vice President | Director, Technology Engineering This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
