McKown, John wrote:
-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL
Sent: Thursday, March 30, 2006 6:00 PM
To: [email protected]
Subject: Re: z/OS 1.7 and "Large Sequential Data Set" Offering
True, but not all VTOCs have INDEXes
Why not in this day and age?
Even my non-SMS volumes, few that they may be, have an index.
They were out long before SMS was.
-
-teD
My SPOOL volumes do NOT have a VTOCIX on them. The VTOC is cylinder 0
(minus track 0, of course). The rest of the volume is the SPOOL dataset.
Absolutely no need for a VTOCIX. The same would be true of any non-SMS
volume which is designed to have a minimal number of permenantly
allocated datasets. OK, OK, so a 1 cylinder VTOCIX or even a VTOC+VTOCIX
taking up cylinder 0 only would work too. I just don't bother.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology
...
We found a good reason for having a VTOCIX on our SPOOL volumes during
some of our early DR testing:
If you do Point-in-Time DR backups using DFDSS with ESS flash Copy to
DASD and DFDSS dump of the flash-copy volumes to tape, the volser is not
copied to the flash-copy target (so the target can remain online for
dump to tape), but at restore time DFDSS "knows" the true volser and
plugs the correct volser when restoring at the DR site. One of our JES
SPOOL volumes ended up with an incorrect volser at DR testing because it
didn't have a VTOCIX. It turned out that DFDSS required either a VTOCIX
or a VVDS be present in order to determine the "true" volser during the
RESTORE. Not sure whether this is still the case, but ever since we've
made a point of having a VTOCIX on every volume.
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
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
