I interpreted the "can live without" as just an affirmation that
applications could continue to access the volume without failure while
the index delete/rebuild was in progress, not as a recommendation for
running that way long-term.
We used to not put a VTOCIX on our spool volumes either, until we found
an unexpected side effect at DR: Using DFDSS with FlashCopy without
copying the volser allows keeping both volumes online, and a subsequent
DFDSS DUMP with dump conditioning allows the dump of the FlashCopy
volume to be restored later with the original source volume volser -
except that on a restore from a volume dump of a volume without a VTOCIX
and without a VVDS, the correct original volser is not restored, just
the FlashCopy volume volser! Apparently with DFDSS and dump
conditioning, the VTOCIX plays a role in determining the original source
volser.
JC Ewing
Mark Jacobs wrote:
Ted MacNEIL wrote:
Note that a nonSMS volume can live without a VTOC index.
But, it performs better with one.
IBM Canada always recommended putting one on the pack, even before SMS was
announced.
Because....
You also find free space.
-
Too busy driving to stop for gas!
----------------------------------------------------------------------
...
There are only a couple of volumes that I don't request a vtocix,
usually volumes that only have one dataset like a page or spool volume.
----------------------------------------------------------------------
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
