Tom Marchant wrote:
...
The VVDS does not necessarily have to be cataloged in the master
catalog. It has to be cataloged in every catalog that contains a
data set that is on that volume. You show a data set called
DSN120T.DSNDBD.AQDBBB1.AQIXOCIC.I0001.A001 on the volume. What
happens if you issue
TSO LISTC ENT('SYS1.VVDS.VHAW157') ALL CATALOG('user.catalog')
where user.catalog is the catalog that
DSN120T.DSNDBD.AQDBBB1.AQIXOCIC.I0001.A001 is cataloged in?
...
It may have been true at one time, but for some time it has been the
case that there is no functional purpose for having a VVDS cataloged in
any catalog. When a VVDS needs to be accessed, it is always accessed
based on volume-level information on the volume associated with some
dataset, not based on any VVDS information that might be found in a catalog.
The cataloging/uncataloging of VVDS datasets is not consistently
enforced. It is quite possible to have an SMS dataset on a volume whose
VVDS is not cataloged in the same catalog; and it is equally possible to
have a VVDS cataloged in a catalog which has no datasets on that volume.
This unfortunately also means that the presence or absence of a VVDS
entry in a catalog is a very imprecise indicator for determining which
volumes and catalogs need to be cross-checked when running a catalog
DIAGNOSE.
There are vendor utilities that will catalog/uncatalog VVDS datasets in
catalogs to make this consistent with the datasets in the catalog, but
unless you have a fairly static environment they will quickly get out of
sync again.
--
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
