Actually I knew: –VSAM data sets: 255 extents prior to z/OS 1.7 per component, but only up to 123 extents per volume per component (123 extents per volume in z/OS 1.7 as well).
- z/OS 1.7 with Data Class ‘Extent Constraint Removal’ set to YES + DB2 APARs: 123 extents per volume * 59 volumes (both dfp limitations and per component) = 7,257 extents –Striped VSAM data sets, up to 4080 extents per data component (16 stripes (volumes) max for VSAM*255 extents per stripe). With z/OS 1.7 the 255 extents maximum is removed for SMS managed components. Max Scarpa Ted MacNEIL <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 13/09/2007 14.16 Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: DASDs Extents in DB2 world >I agree on limit, even if with z/OS 1.7 the limit was greatly increase The limit was not changed with z/OS 1.7. It's still 123 extents per volume, with a max of 255 overall for multi-volume. What was changed is that multiple extents that are side by side (on all but the primary volume) are consolidated into a single extent. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
