The Catalog entry is in the VVCR not the other way round. The DELETE NOSCRATCH merely causes the dataset to be uncataloged. The VVR for that dataset is still intact. The DEFINE RECATALOG must catalog the dataset back in the same BCS as it only has the VVR in the VVDS for information.
>From the AMS for CATALOGS manual RECATALOG Recreates the catalog entries if valid VVDS entries are found on the primary VVDS volume..... Catalog entries can be re-created only in the catalog specified in the VVR except for entries that are swap space, page space, or SYS1 data sets. Also the ALIAS defined in the Master CATALOG would Relate the dataset HLQs to a specific BCS (Usercatalog). HTH Colin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jon Perryman Sent: Wednesday, January 15, 2014 11:41 AM To: [email protected] Subject: Re: zFS Indirect volser support Wouldn't the DELETE NOSCRATCH mark the VVCR as not in a catalog and available for RECATALOG? Otherwise we couldn't RECATALOG to another UCAT or must it always be recataloged to the original catalog? Jon Perryman. ----- Original Message ----- > From: "Pearce, Colin E" <[email protected]> > >T he VVDS keeps the name of each BCS, that has datasets cataloged on >the volume, in its VSAM Volume Control Record - VVCR. So the DEFINE >RECATALOG, will use the BCS information in the VVDS VVCR, plus the >information in the associated VVR, in order to recatalog the dataset to the >correct User Catalog. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
