And just to add 1 more level of complexity, Guaranteed Space allocates the Primary request on each volume.
Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029 MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] L D Owen <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 08/18/2008 07:32 PM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: DASD Space Allocation >>I was surprised to read that on second and subsequent volumes, allocation is based on SECONDARY amounts. Just to confuse everything, VSAM rules are just the opposite. For VSAM datasets, the Primary is used on each subsequent volume for the initial extent (s) on that volume, and then Secondary for the remaining extents. So: Non-VSAM: Volume 1 (Primary, then Secondary), Volumes 2-n (Secondary) 16 Extents per volume, Max 59 volumes VSAM: Volume 1 (Primary, then Seconary), Volumes 2-n (Primary, then Secondary) Watch me be wrong about this one (123 Extents Maximum), no limit per volume If I'm wrong about the VSAM extents, please correct me. ...L ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
