Ed Gould wrote: >Try disabling the VVDS on the volume >amaspzap the dataset to change the name. >delete the dataset with iehprogm >enable the vvds on the volume
You're a dangerous fella! <big grin> ;-) Good advice, but that is not for the faint hearted... Peter Ten Eyck wrote: >> A question about deleting a dataset that GRS (z/OS 1.13) has enqueued. We >> have two LPARs in a sysplex, each with their own catalog structure. There is >> a dataset named the same and cataloged in each LPAR on two different >> volumes. I would like to delete the dataset in one of the LPARs, but the >> name is in use by the other LPAR and enqueued by GRS. Any suggestions of how >> to delete the dataset in the LPAR (and on the volume) that is not being used? and >Yes. The owner (in use) of the dataset is known. GRS has an enq on that >dataset name. I am trying to delete "that dataset name" in a different LPAR on >a different volume. I am wondering if there is a way to "notify” GRS that it >is OK to let me delete this "version" of the dataset. No, this is WAD! There is not a way to tell GRS you want to bypass it. You're just trying to bypass the integrity of z/OS. Please reread Lizette's good advice. She is a serious expert, trust me! I would suggest that you stop that owner, get rid of the offending dataset by RENAMING (not delete) it and catalog it if needed and start that owner. If the owner is running fine, you can then delete that offending dataset. And no, as a RACF admin, I will not give access with a special profile to delete that reserved dataset. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
