> On Thu, 3 May 2007 13:57:09 -0500, Betsy Jeffery wrote: > > I've got a PDSE that has it's NVR in one catalog and it's catalog entry in a > different one. > ... > I have a new PDSE with the contents of the corrupt dataset > ready to go but I have yet to find a way to get rid of the bad one.
Then Zelden wrote: > I just went though something similar with an uncataloged SMS controlled > PDS that I cleaned up today on a sandbox LPAR. > > I tried all the "usual" methods. Define recatalog, delete nvr, etc. etc. > Don't ask what the exact errors were... I tried getting rid of it some weeks > ago and gave up and didn't keep the output. > > Anyway... when all else fails... ZAPing the VTOC works. Anyone else a little concerned at all this ???. There have been various rumblings about the Catalog code since 1.7 came out. Flaky is a term that comes to mind. I happen to be a bit sensitive to the state of our catalogs - and the data they represent. I have *never* had a "DEL NSCR" fail for a "normal" dataset (yes I know that is stretching linguistics when PDSE is involved), and as for Marks PDS, I can't remember the last time I had to zap a VTOC. Ugh. Shane ... ---------------------------------------------------------------------- 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
