Ok, thanks. Diagnose was the correct thing to do anyway since it gives you the corrective action.
Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Fri, 29 Jun 2012 15:18:21 -0600, Ken French <[email protected]> wrote: >Mark - > >I got an error when I ran LISTCAT ENT(data_component) ALL, presumably because >the volume that the DATA component pointed to did not exist on the system. >Thus I was unable to see the expected 'ASSOCIATIONS' information for the DATA >component, which would have given me the name of the associated CLUSTER. When >I ran LISTCAT ENT(data_component) DATA I got no error, but the command simply >returned the name of the DATA component and the catalog where it was cataloged >(no CLUSTER info). > >The message I got from the DELETE TRUENAME told me the base object (CLUSTER) >actually existed, which lead me to run DIAGNOSE to try to figure out the >associated CLUSTER name. Once I had a CLUSTER name the DELETE <sphere_name> >CLUSTER NOSCRATCH worked without problem. > >- Ken > >> Date: Fri, 29 Jun 2012 15:50:55 -0500 >> From: [email protected] >> Subject: Re: Unable to Delete Orphaned VSAM Data Components >> To: [email protected] >> >> On Fri, 29 Jun 2012 13:58:20 -0600, Ken French <[email protected]> wrote: >> >> >Mark, Craig and all that contributed - >> > >> >I ran DIAGNOSE on the USERCAT that contained the entry for the DATA >> >component I was trying to delete and found the associated CLUSTER name. >> >Both the DATA and CLUSTER component names were in the DB2 naming convention >> >that I'm not very familiar with. Once I found the CLUSTER name I was able >> >to issue DELETE <entry> CLUSTER NOSCRATCH against the CLUSTER entry, which >> >deleted both the DATA component and the CLUSTER. >> > >> >The error message received from the DELETE TRUENAME attempt told the story: >> > >> >Explanation: An incorrect DELETE TRUENAME request was specified. The >> >associated base object exists. Programmer Response: User error. >> > >> >Thanks to all for the help. >> > >> >> If you had added "ALL" to your listcat (which I was going to suggest), that >> should have shown the cluster name associated with the data component. >> >> Glad you have it resolved. >> >> Regards, >> >> Mark >> -- >> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS >> mailto:[email protected] >> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html >> Systems Programming expert at http://expertanswercenter.techtarget.com/ >> >> ---------------------------------------------------------------------- >> 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
