I also thought the name of the VTOC (well, its 3rd qualifier) didn't have necessarily to match the DASD volser.
In case you copy your DASD using the Flashcopy technique with DUMPCOND, and you later DUMP the volume
(for DR purposes or whatever other reason) well, it DOES matter.
If the VTOC's 3rd qualifier does not match the volser, the RESTORE will create a wrong volser:
volser xxxxxx --> flash with dumpcond to Fxxxxx --> dump to tape --> full restore --> volser= Fxxxxx :-(
If the VTOC's 3rd qualifier matches the volser, the RESTORE creates the right
volser :
volser xxxxxx --> flash with dumpcond to Fxxxxx --> dump to tape --> full restore --> volser= xxxxxx
Of course, you are referring to the VTOC Index, SYS1.VTOCIX.xxxxxx, not
the VTOC.
It is true that the "xxxxxx" does not have to match the volser of the
volume on which it resides, although there can be only one such dataset
in the VTOC.
The documentation on DUMPCONDITIONING is a little vague. It says that
the volume must have an active VTOCIX for DUMPCONDITIONING to work. If
it is not active, you will get the results you quoted.
So, the question seems to be "is the VTOCIX active?", and nothing to do
with the VTOCIX name.
Note that the VTOCIX on a volume may become disabled for a variety of
reasons; other than a few console messages, there may be no notification
of such a condition. Or it may be that the VTOCIX was allocated but
never activated (the BUILDIX function of ICKDSF).
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
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
