Since this is an orphaned catalog .... try DELETE ... cat.name VVR and then 
follow it w/the same delete except
change the 'VVR' to an 'NVR'.

Kind Regards

Jim 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Rouse, Willie
Sent: Thursday, July 18, 2013 12:45 PM
To: [email protected]
Subject: [SPAM] Re: Orphaned ICF catalog in the VVDS

Dave,

I guess I don't understand:   put a corresponding entry into the "dummy" bcs 

I created and empty ucat  with orphan name. Then tried to delete it with the 
following JCL

//VVR EXEC PGM=IDCAMS,REGION=512K                     
//SYSPRINT DD SYSOUT=*                                
//DD1 DD DSN=SYS1.VVDS.VPP1013,DISP=OLD           
//SYSIN DD *                                          
  DELETE  CATALOG.MVSICFM.VIP1080     NSCR FILE(DD1)  
/*                                                    
I get:
IDCAMS  SYSTEM SERVICES                                           TIME: 
                                                                        
  DELETE  CATALOG.MVSICFM.VIP1080     NSCR FILE(DD1)                    
IDC3014I CATALOG ERROR                                                  
IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFK-18 
IDC0551I ** ENTRY CATALOG.MVSICFM.VIP1080 NOT DELETED                   
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8               

Respectfully,
Willie C. Rouse
Senior Mainframe Consultant
Prince George's County, Maryland
Office of Information Technology
9201 Basil Court/ Room B8
Largo, MD 20774
Voice: 301-883-7189
Fax: 301-883-3790




-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of David Devine
Sent: Thursday, July 18, 2013 12:24 PM
To: [email protected]
Subject: Re: Orphaned ICF catalog in the VVDS

Hi Willie,
I believe that Allan has hit the nail on the head for the solution, but i think 
you may also have to put a corresponding entry into the "dummy" bcs so that the 
delete nscr will match up on both sides.
Just tried it on a pack on our sysprog lpar in the same situation, recreated 
the "lost" catalog and got an idc3012i on the delete nscr for the 
sys1.vvds.vxxxxx.

An inelegant solution but quick and easy would be to disnew the volume, empty 
it out (hsm migrate or dfdss copy etc.) then delete the vvds and define a nice 
new empty one, then enable the volume back to sms.
Sod's law will probably have it that there's a permanently allocated dataset on 
the volume to put the kibosh on that idea!

If you fancy being a guinea pig, theres "VVDSFIX" an unsupported IBM program 
you can download. 

 You can read about and download this tool from this URL:
http://www.ibm.com/support/docview.wss?uid=isg3S1000618 

Was on a share presentation a few years back.
Looks like it could be vaiable. 

Never used it, but i'm sure there are people around who have.

Dave          

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN



This E-mail and any of its attachments may contain Prince George’s County 
Government or Prince George's County 7th Judicial Circuit Court proprietary 
information or Protected Health Information, which is privileged and 
confidential.  This E-mail is intended solely for the use of the individual or 
entity to which it is addressed.  If you are not the intended recipient of this 
E-mail, you are hereby notified that any dissemination, distribution, copying, 
or action taken in relation to the contents of and attachments to this E-mail 
is strictly prohibited by federal law and may expose you to civil and/or 
criminal penalties. If you have received this E-mail in error, please notify 
the sender immediately and permanently delete the original and any copy of this 
E-mail and any printout.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to