The situation you describe would be true for SMS using Guaranteed space. For non-SMS volumes you should be getting 16 extents on volume one followed by 16 extents on volume2 for a PS file.
Regards, Dave O'Brien -----Original Message----- From: Bill Ashton [mailto:bill00ash...@gmail.com] Sent: Wednesday, July 18, 2012 8:52 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How does multi-volume second extents work These are not SMS-managed volumes..just plain old ordinary 3390s... Billy On Wed, Jul 18, 2012 at 8:46 AM, Darth Keller <darth.kel...@assurant.com>wrote: > I thought I knew this off the top of my head, but someone gave me a > problem > > that doesn't fit what I thought. > > > > Let's say I have a PS file allocated as CYL(2500,500), and it is > allocated > > to VOLSR1 and VOLSR2. Can someone point me to the doc that explains > this, > > or can someone explain to me what happens when I need to take > > secondary extents? > > > > For instance, I thought this would be the case: > > 1. Allocate first extent (2500) on VOLSR1 2. 2nd extent (2500) on > > VOLSR2 3. 3rd (500) on VOLSR1 > > 4 - ## (500) on VOLSR1 until 16 extents or the VOLSR1 has < 500C > available > > in 5 pieces, then continue on with VOLSR2. > > ## (500) on VOLSR2 until 16 extents or B37 abend if < 500C available. > > > > I haven't done a lot with multi-volume files, so I might have this > wrong, > > and would welcome your straightening me out. Thanks! > > > > > So far no one's mention the Guaranteed Space parameter. It seems to > me that part of what's discussed above apply when using GS (#1, 2, & 3). > > Time to dig out the manual if GS is a consideration. > dd keller > > > > This e-mail message and all attachments transmitted with it may > contain legally privileged and/or confidential information intended > solely for the use of the addressee(s). If the reader of this message > is not the intended recipient, you are hereby notified that any > reading, dissemination, distribution, copying, forwarding or other use > of this message or its attachments is strictly prohibited. If you have > received this message in error, please notify the sender immediately > and delete this message and all copies and backups thereof. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Thank you and best regards, *Billy Ashton* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
