Thx for your replies, i was focused on removing the enqueue but your approach seems better ;-)
On Fri, 27 May 2022 12:29:16 +0000, Carmen Vitullo <[email protected]> wrote: >what works for me, *sometimes* is i attempt to rename that dataset first, to >.old or something, then delete it. > >I get a warning message, I don't recall the exact message but ISPF eventually >tell me I have the authority and allows the rename , eventual delete @Carmen, i think you have RACF authority on STGADMIN.DPDSRN.**, this is why you can rename a data set in this situation with a simple warning. Unfortunately, it doesn't work on SMS managed data set (seen in the IBM doc https://www.ibm.com/docs/en/zos/2.3.0?topic=gcr-renaming-data-set-that-might-be-in-use), i tried unsuccessfully : >IEC331I 042-002(040B0446),ZOSUSE6 ,IKJACCNT,RNAM,IGG0CLH2 >IEC331I VOL,NW7C55,NAME,RECE230.LOG.CDS02 >IEC614I RENAME FAILED - RC 008, DIAGNOSTIC INFORMATION IS (040B0446), >IKJACCNT,NW7C55,RECE230.LOG.CDS02 >DATA SET NAME IS IN USE BUT YOU HAVE AUTHORITY TO OVERRIDE THIS TEST *** Then this panel (the warning you certainly told me about) : >The system detected that a data set with the above name is in use >(possibly on another system) but it cannot determine whether it is the >data set you wish to rename. If it is the same data set and any program >has it open, renaming it could cause serious system and data integrity >problems. > >You have the extra security authority to rename the data set even though >its name is in use. Refer to the DFSMS documentation on the RENAME macro >for further information. Then this message again >IEC331I 042-002(040B0426),ZOSUSE6 ,IKJACCNT,RNAM,IGG0CLH2 >IEC331I VOL,NW7C55,NAME,RECE230.LOG.CDS02 >IEC614I RENAME FAILED - RC 008, DIAGNOSTIC INFORMATION IS (040B0426), >IKJACCNT,NW7C55,RECE230.LOG.CDS02 *** On Fri, 27 May 2022 15:32:52 +0300, Itschak Mugzach <[email protected]> wrote: >I don’t remember the file number, but the cbttape has a program to delete a >file while ignoring enques. @Itschak, i have found this cbttape file (#183), i'm trying this now. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
