I used below command D GRS,RES=(*,SYS1.SIEKLNKE)
to check the current enqueue and its been used by XCFAS and LLA. and i tried to bring down even LPAR and tried renaming this dataset from other LPAR but still no success. On Sat, Jun 17, 2017 at 5:00 PM, venkat kulkarni <venkatkulkarn...@gmail.com > wrote: > i used below command > > > On Sat, Jun 17, 2017 at 4:44 PM, Dan Little <dwlit...@gmail.com> wrote: > >> Do you mean SYS1.SIEALNKE? The return code you are getting means it is >> enqueued. >> >> Validate DADSM RENAME request; enqueue on SYSDSN failed. >> >> On Jun 17, 2017, 09:29 -0400, Lizette Koehler <stars...@mindspring.com>, >> wrote: >> > A thought or two >> > >> > 1) Is the SYS1.SIEKLNKE currently in the LINKLST? If so, are you just >> refreshing the library? >> > 2) If SYS1.SIEKLNKE does not current exist, you could build a new >> LINKLST and add it to the new list. >> > >> > In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG >> to empty the current library. Then copy the modules into the cleaned out >> library. Then issue a F LLA,UPDATE command (Check out the syntax) >> > >> > In case two, there are many examples in the archives of how to build a >> new Linklst. >> > >> > D GRS,RES=(*,SYS1.SIEKLNKE) will list enqueues for this file. >> > >> > >> > >> > Lizette >> > >> > >> > > -----Original Message----- >> > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On >> > > Behalf Of venkat kulkarni >> > > Sent: Saturday, June 17, 2017 12:45 AM >> > > To: IBM-MAIN@LISTSERV.UA.EDU >> > > Subject: PDSE dataset rename issue >> > > >> > > Hello Group, >> > > We have requirement to add new SYS1.SIEKLNKE dataset into system. But >> this >> > > dataset was allocated to LLA and XCF. So, we unallocated to linklist >> and stop >> > > LLA. After this, we tried renaming this dataset using ispf 3.4 to >> .old but >> > > system didnt allowed and received below error. >> > > >> > > >> > > IEC614I rename failed rc 08 diagnostic information 040B0426, 914 >> > > >> > > I am unable to find any authentication issue or any other causing this >> > > problem. >> > > >> > > Can you please help. >> > > >> > > >> > >> > ---------------------------------------------------------------------- >> > 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 >> > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
