Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!USCMVSA!LDW From: LDW@USCMVSA.BITNET (Leonard D Woren) Newsgroups: bit.listserv.ibm-main Subject: Re: Structuring MVS for integrity. Message-ID: Date: 2 Feb 90 05:23:00 GMT Sender: IBM Mainframe Discussion list Reply-To: IBM Mainframe Discussion list Lines: 22 Approved: NETNEWS@PSUVM Gateway > > A DELETE...NOSCRATCH still tries to check > > the integrity of the VVDS obviously wanting to check the volume which > > no longer exists. Do I need to temporarily clip a volume back to this > > volser in order to statisfy the catalog managements ability to get to > > the device? Do I have to create a VVDS on this temporary volume too? > > > You need to clip a volume to the old name, and mount it in order to > delete the VVDS entry. You do not need to define the VVDS, simply > issue the DELETE VVDS NOSCRATCH command. For DFP 3.1, OY19185 is fixed by UY33397 (8903). This allows DELETE SYS1.VVDS.Vxxx NOSCRATCH to work if volume xxx does not exist. I called the support center on this one a while back because we had VVDS catalog entries pointing to 3350s. It's a bit difficult to "temporarily clip a volume back" to that volser just to delete the VVDS catalog entry when we no longer have any 3350s... Leonard D. Woren Senior MVS Systems Programmer University of Southern California