On 19 May 2008 10:37:56 -0700, in bit.listserv.ibm-main you wrote: >Craddock, Chris wrote: >> Woo hoo! A whole 2.5 GiB? John, you're a wild man :-) >> >> This is one of the primary reasons we mainframers are a bit of an >> endangered species. We don't really have any understanding of what's >> "big" anymore. >> > >EAV has been announced with a 3390 architecture that supports up to >268,434,453 cylinders or 228,158,547,671,880 bytes per volume! I have no >idea what's the "right" way to calculate disk space these days. Assuming >you get KB by dividing by 1024 and then MB, GB, TB, etc. by dividing by >1000 each, that would be nearly 223TB *per* volume. I don't care which >platform you work with, that's BIG! > >Of course, the very first EAV release will establish an arbitrary >per-volume size limit of 223GB so we can iron out the capacity and >performance bottlenecks that will undoubtedly arise from implementation >of larger volumes. After that, expect the maximum per-volume size to >start rising again.
Again, we get the band-aid instead of the step forward. Instead of making FBA available to z/OS and coming up with the needed enhancements to PDSE, ESDS and initialization code, the space and CPU cycle wasting CKD is carried forward. It is an architecture that is FBA file hostile (look at the space wasted per track for PDSE, VSAM and any other file system that is at least somewhat page oriented). Clark Morris > >Meanwhile, Cheryl Watson's polling questions in Orlando didn't show very >many people exploiting the largest (54GB) pre-EAV disks. But, the number >is up significantly from when the same question was asked in San Diego. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
