Does it exist somewhere else and the system is trying to catalog it? -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Mark Jacobs Sent: Wednesday, October 16, 2019 9:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] STGADMIN.DPDSRN Confusion
The dataset that I'm renaming it to does not exist on that volume. DSLIST - Data Sets on volume Z22C02 Row 1 of 2 Command ===> Scroll ===> CSR Command - Enter "/" to select action Message Volume ------------------------------------------------------------------------------- SYS1.PROD.PARMLIB.NEW Z22C02 SYS1.PROD.PARMLIB.NEW.COPY Z22C02 Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, October 16, 2019 10:23 AM, Pommier, Rex <rpomm...@sfgmembers.com> wrote: > Mark, > > Am I missing something here? The way I'm reading this error is that you're > trying to rename your SYS1.PROD.PARMLIB.NEW dataset to > SYS1.PROD.PARMLIB.NEW.ORIG and SYS1.PROD.PARMLIB.NEW.ORIG already exists on > volume Z22C02. Aren't you just getting a "duplicate name" error? > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf > Of Mark Jacobs > > Sent: Wednesday, October 16, 2019 9:16 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] STGADMIN.DPDSRN Confusion > > I'm attempting to rename an inuse non-vsam dataset, even with read access to > the STGADMIN.DPDSRN.SYS1.* profile, it's failing with these error messages. > > IGD17060I DELETE/RENAME FAILED BECAUSE DATA SET IS OPEN ON VOLUME > Z22C02 DATA SET IS SYS1.PROD.PARMLIB.NEW IEC614I RENAME FAILED - RC > 008, DIAGNOSTIC INFORMATION IS (040B0446), > STEP2,Z22C02,SYS1.PROD.PARMLIB.NEW > DATA SET NAME IS IN USE BUT YOU HAVE AUTHORITY TO OVERRIDE THIS TEST > IGD17056I RENAME FAILED, DUPLICATE DATA SET NAME ON VOLUME Z22C02 DATA > SET IS SYS1.PROD.PARMLIB.NEW.ORIG > > X'04' X'0B' ENQRET X'46' > Validate DADSM RENAME request; enqueue on SYSDSN failed. Also, the caller has > appropriate RACF READ authority to be able to specify that the data set being > renamed is not the data set in use. > See Renaming a Data Set That Might be in Use in z/OS DFSMSdfp Advanced > Services.Sent from ProtonMail, Swiss-based encrypted email. > > What am I missing here? > > Mark Jacobs > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get&search=markjacobs@protonma > il.com > > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > -------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > The information contained in this message is confidential, protected from > disclosure and may be legally privileged. If the reader of this message is > not the intended recipient or an employee or agent responsible for delivering > this message to the intended recipient, you are hereby notified that any > disclosure, distribution, copying, or any action taken or action omitted in > reliance on it, is strictly prohibited and may be unlawful. If you have > received this communication in error, please notify us immediately by > replying to this message and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. > > > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > ------ > > 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 The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN