Tried that but got these results:

DELETE                                      -                         
          HLQC01.HLQC002.HLQ3.HLQ04.ED0399C7 -                         
         FILE(DD1)  -                                                  
         VVR                                                           

IDC3014I CATALOG ERROR                                                 
IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFP-16
IDC0551I ** ENTRY HLQC01.HLQC002.HLQ3.HLQ04.ED0399C7 NOT DELETED       
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8              

The explanation for return code 90 and reason code 16 is:

   16                  Explanation: DELETE VVR request for a VVR with an
                       associated catalog.

Do you have any idea what this means?

Peter

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of Adams, Rick
> Sent: Monday, December 27, 2010 4:23 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: How to delete orphaned Data and Index components?
> 
> Peter,
> A DELVVR should take care of these.  Here is an example JCL.  Plug in the
> volser where the orphan entry resides and the orphan entry dsn.
> 
> //STEP020  EXEC PGM=IDCAMS
> //DDNAME1  DD UNIT=3390,VOL=SER=volser1,DISP=OLD
> //DDNAME2  DD UNIT=3390,VOL=SER=volser2,DISP=OLD
> //SYSPRINT DD  SYSOUT=*
> //SYSIN    DD  *
>  DELETE -
>    HLQC01.HLQC002.HLQ3.HLQ04.ED0399C7 -
>    FILE(DDNAME1) -
>    VVR
>  DELETE -
>    HLQC01.HLQC002.HLQ3.HLQ04.O19KLAD7 -
>    FILE(DDNAME2) -
>    VVR
> 
> Thanks....Rick
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of Farley, Peter x23353
> Sent: Monday, December 27, 2010 2:25 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: How to delete orphaned Data and Index components?
> 
> I have somehow created a data and index component of a VSAM KSDS that are
> orphaned from the cluster name.  The cluster was deleted and re-created
> and now has differently named data and index components, so I don't think
> I can "connect" the orphaned components to that cluster name.
> 
> All file creation and deletion was done in batch jobs.  The orphaned
> components were created using the LIKE operand in an IEFBR14 step.
> 
> Neither TSO delete nor IDCAMS batch delete will allow me to remove the
> components.  IDCAMS complains as follows:
> 
> IDC2552I ENTRY TYPE IS INVALID FOR DELETE
> IDC0551I ** ENTRY HLQC01.HLQC002.HLQ3.HLQ04.ED0399C7 NOT DELETED
> IDC2552I ENTRY TYPE IS INVALID FOR DELETE
> IDC0551I ** ENTRY HLQC01.HLQC002.HLQ3.HLQ04.O19KLAD7 NOT DELETED
> IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
> 
> The IDC2552I explanation in the Fine Manual only says I can't delete these
> entry types but doesn't tell me how I *can* delete them.
> 
> Is there any way to delete these orphaned components?
> 
> TIA for any help, RTFM, etc. you can provide.
> 
> Peter
--

This message and any attachments are intended only for the use of the addressee 
and
may contain information that is privileged and confidential. If the reader of 
the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to