Didn't the transition to Super PAVs (HYPERPAV=XPAV) eliminate the need for UCB relief (I/Os quing in the z/OS I/O subsystem)?
Even so, if your new storage group does not have 59 volumes, only ARCxxxI (infomational messages should be generated; the allocation should still proceed, no? -----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 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. ---------------------------------------------------------------------- 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
