And here we go DELETE NOSCRATCH
IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 54 Explanation: DELETE failed because the data set is being renamed but it has not completed. Programmer Response: Rename the data set with the IDCAMS ALTER command and then delete it. So I tried ALTER NEWNAME IDC3009I ** VSAM CATALOG RETURN CODE IS 130 - REASON CODE IS IGG0CLEC-18 18 Explanation: The data set name specified in NEWNAME is involved in another ALTER NEWNAME request that is not yet complete. So, the catalog "knows" there is an uncompleted ALTER NEWNAME.. On Tue, Nov 29, 2016 at 1:48 AM retired mainframer <[email protected]> wrote: > It helps if you show us the command you issued and the exact error message > you received, including the msg ID. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Rob Schramm > Sent: Monday, November 28, 2016 9:46 PM > To: [email protected] > Subject: Rename in-process catalog issue > > I am looking at some nonvsam catalog entries that indicate that a rename > has started. The problem is that the volume that the datasets used to > reside on does not exist anymore. > > I have tried DELETE NOSCRATCH which indicates that a rename is in-process > and to try ALTER .. ALTER won't work either. My understanding of the > special non-supported IBM tool to fix weird issues with VVDS entries.. is > that it won't help because I don't actually have a VVDS. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Rob Schramm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
