Ted, > >It's just showing that you have 2 additional candidate volumes > allocated. They have not yet been assigned. > > It's a control block thing. > It doesn't cost anything; it can protect you from future growth problems. > > The last two shops I worked at had 20 volumes allocated in most dataclasses. > I would recommend the 59 vol max. > It doesn't cost; it can save.
Each candidate volume takes room in the catalog which could have a big impact on gdg (b) records where the favorite limit is high, up to 255 and there is a clear favorite high level qualifier and no clear favorites for the second node. We have a very large user catalog. I would recommend dynamic volume count if you don't have something that will dynamically add volumes. > Especially, since only the secondary allocation size is 'remembered' > on all future volumes. True for nonvsam datasets but volume count also applies to vsam datasets. The space allocation used for vsam when extending to a new volume is the primary though you can change that to secondary for SMS managed datasets. Regards, John ---------------------------------------------------------------------- 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
