Hi A re-allocation of the dataset would be with something like CYLS(3000 2000) VOLUMES(* * * * * *).
Adding a new empty volume to the storage group would be a quick-and-dirty workaround, not a permanent solution. And I have downloaded the "VSAM De-Mystified" and are planning to read it real-soon-now...... Thanks to everybody for the feedback and advise. Mvh Frank On Mon, 20 Apr 2009 08:53:02 -0400, O'Brien, David W. (NIH/CIT) [C] <obrie...@mail.nih.gov> wrote: >Frank, > > According to the manual (and another post) VSAM extends with the Primary allocation. >Assuming that I misunderstood and you plan to re-allocate with 9980 as your Primary allocation, let me ask - Why would you use a Primary allocation that is so large that it >effectively excludes most if not all of the volumes in your storage group? My advice to you is to make your Primary Secondary smaller more reasonable values. > > Get a copy of VSAM De-Mystified from IBM Redbooks. Much of what you think you know about VSAM is false. Don't take that personally, it applies to almost everybody including me. > >Dave O'Brien >NIH Contractor >________________________________________ >From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Frank Allan Rasmussen [frank.allan.rasmus...@regionsyddanmark.dk] >Sent: Monday, April 20, 2009 8:43 AM >To: IBM-MAIN@bama.ua.edu >Subject: Re: VSAM extended allocation > >Hi > >It seems that 3390-9 has the same number of tracks on our system. And that >the IDCAMS input, I thought was the current and correct input, can not be >correct. > >We will follow your adwise. > >Just a thought - if we were to add a new (empty) 3390-9 to the storagegroup >we would have a secornd allocation go there with 9980 cyls allocated? > >Mvh >Frank > > >On Mon, 20 Apr 2009 08:28:03 -0400, O'Brien, David W. (NIH/CIT) [C] ><obrie...@mail.nih.gov> wrote: > >>Frank, >> >> On my system a 3390-9 has 150K tracks per volume or 10K cylinders so I >would suggest you repro your file out to backup, delete/define your VSAM file >with something more reasonable like CYL(300 200) and VOLUMES(* * * * * * >* * * * *) >>or increase the Volumes parameter in your Dataclass, then repro your backup >back into your newly defined VSAM file. >> >>Dave O'Brien >>NIH Contractor >>________________________________________ >>From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of >Lizette Koehler [stars...@mindspring.com] >>Sent: Monday, April 20, 2009 8:09 AM >>To: IBM-MAIN@bama.ua.edu >>Subject: Re: VSAM extended allocation >> >>What is the details of your dataclas - VSAMEXT? >> >>Lizette >> >> > We have a VSAM extended dataset that have filled a 3390-9 volume and >we need to >>> reallocate it. >>> >>> But >> > Im not sure I understand how it was allocated the way it is. >> > Currently: >> > The dataset is on one volume and is 149.700 tracks (data), 308 tracks >(index). Data >>> and index are on same volume. >> > The dataclass has a blank volume count. >> > The IDCAMS input used to allocate with is: >> > DEFINE- >> > CLUSTER- >> > (NAME(PROD.AMB.AMBARKIV)- >> > FREESPACE(0,0)- >> > VOLUME(* *) - >> > CYL(12000 50)- >> > SUBAL SPEED NWCK- >> > RECORDSIZE(150,1582)- >> > TO(2049365)- >> > SHR(2)- >> > IXD- >> > DATACLASS(VSAMEXT) - >> > KEYS(14,0))- >> > DATA- >> > (NAME(PROD.AMB.AMBARKIV.DATA)- >> > CISZ(8192))- >> > INDEX- >> > (NAME(PROD.AMB.AMBARKIV.INDX)- >> > CISZ(1024)) >> > What I do not understand is why the dataset do not allocate a >secondary extend on a >>> new volume in the storagegroup there is free space in the storagegroup. >> > The VOLUME(* *) parameter should overwrite the volume count >attribute in the >>> dataclass or .? >> > I would like to avoid a similar allocation and have the new version >allocated on at least 2 >>> volumes. >> >>---------------------------------------------------------------------- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
