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. Ideas? Rob Schramm -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
Rob, The VVDSFIX tool should get rid of the BCS entry for you by using . . . CMD=DELBCSR;dataset.name Then, if the volume is still around (believe you mentioned it was not) you can use DEL dataset.name NVR to remove the NVR record. Regards, Steve Emge -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
I just dealt with this, need a 2.1 system with a storage admin profile,.. then delete NOSCRATCH will work. Rob Schramm On Mon, Dec 5, 2016, 12:25 PM Steve Emge wrote: > Rob, > > The VVDSFIX tool should get rid of the BCS entry for you by using . . . > CMD=DELBCSR;dataset.name > > Then, if the volume is still around (believe you mentioned it was not) you > can use DEL dataset.name NVR to remove the NVR record. > > Regards, > Steve Emge > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Monday, November 28, 2016 9:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
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 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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Rob Schramm > Sent: Monday, November 28, 2016 9:46 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
And now for the answer http://www-01.ibm.com/support/docview.wss?uid=isg1OA36138 Turns out that issuing the DELETE NOSCRATCH on a 2.1 system can have a better effect (RACF/ACF2/TSS willing) and will clean up the mystery bit that gets set during a failed ALTER NEWNAME. Rob Schramm On Tue, Nov 29, 2016 at 2:21 AM Rob Schramm wrote: > 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 < > retired-mainfra...@q.com> 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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Rob Schramm > Sent: Monday, November 28, 2016 9:46 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > > Rob Schramm > -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
I see you found an answer, but did you try: //DD1 DD DISP=SHR,,UNIT=SYSDA,VOL=SER=xx DEL 'dsn' NVR FILE(DD1) HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Monday, November 28, 2016 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. Ideas? Rob Schramm -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
Doesn't NVR require the volume? Rob On Tue, Nov 29, 2016, 8:35 AM Allan Staller wrote: > I see you found an answer, but did you try: > > //DD1 DD DISP=SHR,,UNIT=SYSDA,VOL=SER=xx > > DEL 'dsn' NVR FILE(DD1) > > HTH, > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Rob Schramm > Sent: Monday, November 28, 2016 11:46 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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. > > Ideas? > > Rob Schramm > -- > > Rob Schramm > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ::DISCLAIMER:: > > > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
OP says that the volume does not exist any longer. I'm afraid that the JCL example would go into allocation and eventually fail. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 29, 2016 5:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Rename in-process catalog issue I see you found an answer, but did you try: //DD1 DD DISP=SHR,,UNIT=SYSDA,VOL=SER=xx DEL 'dsn' NVR FILE(DD1) HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Monday, November 28, 2016 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. Ideas? Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
Classification: Public Might need to zap the catalog then.. We have TACM that can do that, and there are other products with the same capability. Andy Styles z/Series Systems Programmer -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: 29 November 2016 16:06 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rename in-process catalog issue -- This email has reached the Bank via an external source -- OP says that the volume does not exist any longer. I'm afraid that the JCL example would go into allocation and eventually fail. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 29, 2016 5:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Rename in-process catalog issue I see you found an answer, but did you try: //DD1 DD DISP=SHR,,UNIT=SYSDA,VOL=SER=xx DEL 'dsn' NVR FILE(DD1) HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Monday, November 28, 2016 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. Ideas? Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. Telephone: 0345 603 1637 Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority. Cheltenham & Gloucester plc is authorised and regulated by the Financial Conduct Authority. Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings is a division of Lloyds Bank plc. HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC218813. This e-mail (including any attachments) is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it (including any attachments) immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Telephone calls may be monitored or recorded. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rename in-process catalog issue
If a simple del cluster doesn't work I head over to my trusty ISMF panels. It has never failed me in cleaning up broken VSAM clusters or VSAM catalog entries with no physical file. ;-D an -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Styles, Andy (SD EP zPlatform) Sent: Tuesday, November 29, 2016 11:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rename in-process catalog issue Classification: Public Might need to zap the catalog then.. We have TACM that can do that, and there are other products with the same capability. Andy Styles z/Series Systems Programmer -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: 29 November 2016 16:06 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rename in-process catalog issue -- This email has reached the Bank via an external source -- OP says that the volume does not exist any longer. I'm afraid that the JCL example would go into allocation and eventually fail. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 29, 2016 5:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Rename in-process catalog issue I see you found an answer, but did you try: //DD1 DD DISP=SHR,,UNIT=SYSDA,VOL=SER=xx DEL 'dsn' NVR FILE(DD1) HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Monday, November 28, 2016 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. Ideas? Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. Telephone: 0345 603 1637 Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority. Cheltenham & Gloucester plc is authorised and regulated by the Financial Conduct Authority. Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings is a division of Lloyds Bank plc. HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC218813. This e-mail (including any attachments) is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it (including any attachments) immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Telephone calls may be monitored or recorded. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
