> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Matt Simpson > Sent: Friday, June 03, 2005 4:02 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Advice on expanding VTOC index > > > I have some volumes (Shark logical 3390) with VTOC Indexes > that are full, or very close to it. > > If possible, I would like to expand the indexes without > taking the volumes offline or making them > unavailable. The problem is that the index, the VTOC, and > the VVDS are all adjacent (in that order, starting at CYL 0). > > The tools I have to work with are ICKDSF and FDRCPK. > > The ICKDSF manual suggest that the index can be extended with > the REFORMAT EXTINDEX command, but only if EXTVTOC is also > specified to expand the VTOC in its current location. > There's no room for the VTOC to grow in its current location > unless the VVDS moves. The VTOC can be moved with the > NEWVTOC operand, but only if the volume is offline. > > FDRCPK will expand/move a VTOC, but apparently only if the > volume is being compakted from a tape backup, which would > imply making it unavailable to running jobs. > > > It appears that my only option, if it is an option, is to > move the VVDS with FDRCPK. But the doc is a little fuzzy on > that, and doesn't give me a warm fuzzy feeling. > > Does anybody have any insight? Am I out of luck? Do I have > to shut down whoever is using the volumes to move things around? >
Personally, I don't usually care a great deal if the VTOCIX is right up against the VTOC & VVDS. I prefer it, but it only affects pack fragmentation. So, for a "temp fix", I would do: 1) V SMS,VOL(......),Q,NEW 2) ICKDSF "BUILDIX DDNAME(......) OSVTOC" 3) Delete the IXVTOC 4) Realloc the IXVTOC with CONTIG 5) ICKDSF "BUILDIX DDNAME(......) IXVTOC" I have also been known to QUINEW the volume (as in #1 above), then use DFDSS (you'd use FDR) to try to copy all the DSNs off of the volume. Another thought is to try to force the IXVTOC to allocate at the very end of the volume. The exact location is not very relevant WRT performance with a Shark. Just with "volume fragmentation". -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
