If it's SMS, the VVDS has data for non-VSAM also. I agree with you. Stop new allocations (DISNEW), Carefully move everything (make take several passes), when it's empty, re-init it and allocate a sufficiently large VVDS on it.
I still always allocate a VVDS right after I init a new volume. I do not let the automatic allocation happen. Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Linda Mooney > Sent: Tuesday, October 18, 2011 3:42 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: IEC331I 050-030(VVDSFULL, PROD06) > > Hi Esmie, > > > > If you take the all of the VSAM datasets off of the volume, you can delete > the VVDS (I can send you the IDCAMS if you want) and allocate a new, > bigger one on the same volume. > > > > Personally, I would not zap a VVDS. I know that some probably would, but > not me , I wouldn't. I would stop new allocations. I would move off the > data > to another volume using a logical copy, not a physical copy - CA-Disk, FDRDSF, > DSS . I recommend taking a look at the size of the VTOC and the VTOC index > as well. Since the VVDS is too small the others are likely to be too small > too. The VVDS should be cleaned out before and deleted BEFORE you re-init > the volume. I can help you with the VVDS clean out, if you want. I have > done many of them. > > > > Do you have QuickRef? Its DASD free space panel will show you the > percentage of free space in the VTOC and index. It works with single > volume, SMS pool, or volser pattern. It's an easy way to check a bunch of > volumes. > > > > Having one volume with a too small VVDS sug gests that there are probably > more out there. Folks often take the defaults and new folks often code sizes > according to the way it is in the book. The more datasets that may be > assigned to a volume, the bigger VTOC, VTOC index and VVDS will be > needed. It is better to have all three generously sized rather than too > small. > > > > HTH, > > > > Linda > > ________________________________ > > > From: "esmie moo" <esmie_...@yahoo.ca> > To: IBM-MAIN@bama.ua.edu > Sent: Tuesday, October 18, 2011 3:48:23 AM > Subject: Re: IEC331I 050-030(VVDSFULL, PROD06) > > Linda, > > I did what you asked. I ran the report and moved 90 dsns from the volume, > however the problem still persists. I was told to check OEM option to ZAP > the VVDS. I would like to try that out but I am not sure where I should look > for it. > > > ________________________________ > From: Linda Mooney <linda.lst...@comcast.net> > To: IBM-MAIN@bama.ua.edu > Sent: Monday, October 17, 2011 4:06:12 PM > Subject: Re: IEC331I 050-030(VVDSFULL, PROD06) > > Hi Esmie, > > > > If you want to get a look at the contents of the VVDS, you can run this - > > > > //STEP1 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > PRINT - > INDATASET(SYS1.VVDS.Vvolser) - > COUNT(1) > > > It should shed some light on what has filled it up. > > > HTH, > > > > Linda > > > > ----- Original Message ----- > > > From: "esmie moo" <esmie_...@yahoo.ca> > To: IBM-MAIN@bama.ua.edu > Sent: Monday, October 17, 2011 11:59:24 AM > Subject: IEC331I 050-030(VVDSFULL, PROD06) > > Good Afternoon Gentle Readers > > I am trying to trouble shoot the following problem : IEC331I 050- > 030(VVDSFULL, PROD06) > According to the message error explanation it says that the VVDS is > full. When I check via ISPF 3.4 is shows that it is a 1 ext. The VVDS was > built > at TRACKS(30 1). To fix the problem the doc says to move dsns off that > volume. I tried that but the problem persists when the system is trying to > allocate a dsn on the volume. Since the volume is SMS managed (phew), I > put it at DISNEW. The doc says to backup the volume, and reinitialize it > with a > larger VVDS. > Is there something else I can try before I try the doc's recommendation? > > Thanks in advance. > > ---------------------------------------------------------------------- > 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
