Classification: Confidential You pays me now or you pays me later... But you still pay. You pays you money and takes your choice.
Perhaps an incremental approach. Create a set of "small" eavs" and have some pain. Later create a set of "medium eavs" and have a little more paint. Create a set of "large eavs" and you are done. A long effort, but IMO, will pay off in the long run... -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jousma, David Sent: Monday, April 7, 2025 2:48 PM To: [email protected] Subject: Re: Migrating Storage pools to EAV [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don't click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] I think the point of my question wasn't worded clearly. The problem is poor allocation coding over the years where coded primary and secondary allocations are NO WHERE NEAR what is really needed. But because we have 100's of volumes in the pool, and a dataclass that allows 59 volume multi-volume dataset, the problem is masked because the dataset can get 123 extents on each of the 59 volumes. With a 20-1 reduction in volumes in the pool(1TB EAV's replacing 20 mod-54's), there might not be 59 volumes in the pool, and that dataset will now take an x-37 abend that we will take the heat for. That is what I am trying to avoid. Seems like my only option is to reduce the size of the EAV so that there are more volumes, or make the developers fix their JCL allocations. I was hoping for the pixie dust to work around the latter, but I don't think there is anything. It would be nice if (here is the pixie dust), that on dataset extent processing, if some number of x space is requested, but is below some threshold percentage of the current file size, or less than some site customizable minimal trk/cylinder quantity that it would get overridden to something larger. Dave Jousma Vice President | Director, Technology Engineering > > -----Original Message----- > From: IBM Mainframe Discussion List [email protected] On Behalf > Of Jousma, David > > Sent: Friday, April 4, 2025 9:21 AM > To: [email protected] > Subject: Migrating Storage pools to EAV > > CAUTION: This email originated from outside of the Texas Comptroller's email > system. > DO NOT click links or open attachments unless you expect them from the sender > and know the content is safe. > > 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 ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
