"Schwarz, Barry A" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> I ran an IDCAMS DIAGNOSE against all my VVDSs. Most were clean but a > couple reported an IDC11367I attention/warning "The following VVDS > referenced catalogs were not encountered." It then listed some obsolete > and no longer existing catalogs. They are holdovers from my last > upgrade (from 2.5 to 2.10). There are no data sets catalogued in or > referring to these catalogs any more. (I had a few data sets that > pointed to obsolete catalogs and that generated a different, more severe > error which I was able to fix.) > > The message manual says to use DELETE NOSCRATCH to remove the VVDS from > the catalog but that is backwards. The non-existent catalog doesn't > refer to anything. It is the VVDS that refers to the catalog, > apparently in some general reference section rather than as part of a > data set entry. The IDCAMS manual talks about breaking the association > between a catalog and a VVDS but only from the catalog's viewpoint > (DELETE NOSCRATCH again). > > I know I could migrate all the data sets different packs and use ICKDSF > and IDCAMS to remove all traces of the VVDS (which would then get > rebuilt when data sets are allocated on the pack) but there has to be a > better housekeeping method. >From Managing Catalogs: "To break the connection between a BCS and a VVDS, use DELETE NOSCRATCH, specifying the VVDS as the entry name, and the BCS in the CATALOG parameter. If the VVDS is available, it is checked to determine if the BCS in the CATALOG parameter has any data sets on the volume. If data sets are found on the volume, the DELETE command will fail. If the VVDS is not available, no check is performed. " Thanks, Mark Thomen Catalog/IDCAMS/VSAM Development ---------------------------------------------------------------------- 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
