-------------------------------<snip>--------------------------
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.
--------------------------------<unsnip>---------------------
True, but keep in mind that in a SMS-managed DASD farm, ALL datasets
must be cataloged, somewhere.
------------------------------<snip>----------------------------
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.
-------------------------------<unsnip>--------------------------
IIRC, when a VVDS is created "automatically", during the definition of
another VSAM file, it went into the same catalog as the file being
defined. Subsequent deletion of the VSAM file could very well leave the
VVDS cataloged in an unrelated catalog. In the case of a manual
definition of a VVDS, I'm not sure where the catalog entry would be
placed, but I THINK IDCAMS would catalog the VVDS according to existing
ALIAS/CAATALOG relationships.
----------------------------------------------------------------------
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
