Well, IBM documentation says:
Almost all types of data sets are EAS-eligible, including the following:
• SMS and non-SMS-managed VSAM data sets (all types), including:
– BCS and VVDS catalog data sets.
– VSAM data sets inherited from prior physical migrations or copies.
– VSAM temporary data sets.
• zFS data sets (they are VSAM).
• Sequential data sets, including extended, basic, and large formats.
• PDS and PDSE data sets.
So no, non-extended format VSAM and PS can be allocated in EAS.
However basic PS files are still restricted to 64k TRKs, so the only way
to circumvent this limitation is multi-vol, which is something author
wants to avoid. :-)
--
Radoslaw Skorupka
Lodz, Poland
W dniu 08.04.2025 o 19:01, salva pisze:
David, have you changed your Dataclass to extended format?
Non-extended PS & VS will be allocated on track-managed space (cyl < 65520)
on EAV vols.
Regards, salva.
El vie, 4 abr 2025 a las 16:20, Jousma, David (<
[email protected]>) escribió:
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
