Do the entries for the clusters also exist in the USERCAT? If so, you should specify the cluster name in the DELETE ... NOSCRATCH command.
If not, you need to figure out how the cluster was deleted but not the data component and prevent it from happening again. One brute force way to end up with a clean catalog is to REPRO MERGECAT all the other catalog entries into a new catalog. Then either (1) change all the aliases to point to this catalog or (2) delete and recreate the old catalog and REPRO MERGECAT everything back. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :>: Behalf Of Ken French :>: Sent: Friday, June 29, 2012 8:45 AM :>: To: IBM-MAIN@LISTSERV.UA.EDU :>: Subject: Unable to Delete Orphaned VSAM Data Components :>: :>: I have several VSAM data components in one of my USERCATs that are :>: cataloged to volumes that no longer exist. I've searched extensively on :>: how this might be done, and have tried several variations of the IDCAMS :>: DELETE command without success, including DELETE <entry> NOSCRATCH, :>: DELETE <entry> TRUENAME. I even attempted to REPRO MERGECAT the orphaned :>: entries to a new, temporary USERCAT that I planned to simply delete if :>: the MERGECAT was successful. Any ideas on how to eliminate these :>: undesired and orphaned catalog entries? Keep in mind that the volumes :>: these entries are pointing to do not exist on my system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
