Re: Deleting a dataset that GRS has enqueued.

PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Deleting a dataset that GRS has enqueued. > > I don't know of a 'classic' definition. To me bronze-plex is a fully > functional > parallel sysplex that shares little or nothing more than what's required for > sysplex, essentially t

Deleting a dataset that GRS has enqueued.

323-715-0595 Mobile > jo.skip.robin...@att.net > > > > -Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Skip Robinson > > Sent: Saturday, January 30, 2016 06:09 PM > > To: IBM-MAIN@LISTSER

Re: Deleting a dataset that GRS has enqueued.

On Fri, 29 Jan 2016 16:25:22 -0500, Jim Mulder wrote: > >"I worked on that project and wrote some of the code. I think >that the reason that it does not apply to an SMS-managed data set is >that it conflicts with the concept that you cannot have two >SMS-managed data sets with the same name.

Re: Deleting a dataset that GRS has enqueued.

uncataloged, then the RACF profile allows >that dataset to be renamed despite the GRS enqueue. > >. > >. > >. > >J.O.Skip Robinson > >Southern California Edison Company > >Electric Dragon Team Paddler > >SHARE MVS Program Co-Manager > >323-7

Re: Deleting a dataset that GRS has enqueued.

On Sat, 30 Jan 2016 11:26:30 -0400, Clark Morris wrote: >Could data sets be set up in different catalogs in the bronze-plex >with GRS told not to propagate the enqueue (i.e. local to each system) >in the 2 LPARS? If that can be done, would the experiment work >differently? Would any special

Re: Deleting a dataset that GRS has enqueued.

8:48 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > On Sat, 30 Jan 2016 11:26:30 -0400, Clark Morris wrote: > > >Could data sets be set up in different catalogs in the bronze-plex with > >GRS told not to propagate the enqu

Re: Deleting a dataset that GRS has enqueued.

On 1/30/2016 8:47 AM, Tom Marchant wrote: However, I believe that skip had written in an earlier append that hos bronzeplex was a combination of two sysplexes. If that is the case ... A "classic" bronzeplex is two or more JESplexes within a single sysplex. -- Edward E Jaffe Phoenix Software

Re: Deleting a dataset that GRS has enqueued.

nframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Saturday, January 30, 2016 03:16 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > On 1/30/2016 8:47 AM, Tom Marchant wrote: > > Ho

Re: Deleting a dataset that GRS has enqueued.

On Sat, 30 Jan 2016 20:54:20 -0500, Robert A. Rosenberg wrote: >At 14:53 -0600 on 01/30/2016, Paul Gilmartin wrote about Re: Deleting >a dataset that GRS has enqueued.: > >>Even within a single system, to delete a data from one volume when >>a like named data set on a dife

Re: Deleting a dataset that GRS has enqueued.

At 14:53 -0600 on 01/30/2016, Paul Gilmartin wrote about Re: Deleting a dataset that GRS has enqueued.: Even within a single system, to delete a data from one volume when a like named data set on a diferent volume is in use ENQ SHR on the same system. This is a irresolvable design flaw (ie

Re: Deleting a dataset that GRS has enqueued.

At 18:19 -0800 on 01/30/2016, Skip Robinson wrote about Re: Deleting a dataset that GRS has enqueued.: I'm not sure what ISPF function you're referring to. This happens all the time in our bronze-plex. Editing SYS1.PARMLIB(ABC) on one system. Cannot concurrently edit SYS1.PARMLIB(ABC

Re: Deleting a dataset that GRS has enqueued.

Bulk] Re: Deleting a dataset that GRS has enqueued. > > At 14:53 -0600 on 01/30/2016, Paul Gilmartin wrote about Re: Deleting a > dataset that GRS has enqueued.: > > >Even within a single system, to delete a data from one volume when a > >like named data set on a diferent volu

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 09:00:05 -0600, 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

Re: Deleting a dataset that GRS has enqueued.

, 2016 01:25 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Deleting a dataset that GRS has enqueued. > > > We took the easy way out and brought down the two STCs that had the > > SMS dataset enqueued, then deleted the version of the dataset that was > >

Re: Deleting a dataset that GRS has enqueued.

On Fri, 29 Jan 2016 13:46:32 -0600, Peter Ten Eyck wrote: >It was mentioned in this thread that GRS could have been modified >to change the scope of the enqueue on the LPAR that the dataset >was not being used on by making it local. Therefore no longer >considered in use by GRS. I did not try

Re: Deleting a dataset that GRS has enqueued.

> We took the easy way out and brought down the two STCs that had the > SMS dataset enqueued, then deleted the version of the dataset that > was not being used. > > It was mentioned in this thread that GRS could have been modified to > change the scope of the enqueue on the LPAR that the

Re: Deleting a dataset that GRS has enqueued.

I will admit that I haven't followed this entire thread but this facility is designed to rename datasets that exist on multiple volumes (like ipl volumes). For SMS managed datasets they must be cataloged and therefore can't exist on multiple volumes. Therefore the enq is held because that

Re: Deleting a dataset that GRS has enqueued.

day, January 28, 2016 06:52 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > On Wed, 27 Jan 2016 18:40:45 -0600, Paul Gilmartin > <paulgboul...@aim.com> wrote: > > >I thought from discussions here a few yea

Re: Deleting a dataset that GRS has enqueued.

jo.skip.robin...@att.net > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Doug Henry > Sent: Thursday, January 28, 2016 08:47 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS ha

Re: Deleting a dataset that GRS has enqueued.

On Jan 28, 2016, at 8:51 AM, Walt Farrell wrote: On Wed, 27 Jan 2016 18:40:45 -0600, Paul Gilmartin wrote: I thought from discussions here a few years ago that IBM has provided a facility that supports renaming of an ENQUEUEd DSN, in the VTOC, after requesting

Re: Deleting a dataset that GRS has enqueued.

UA.EDU] > On Behalf Of Peter Ten Eyck > Sent: Wednesday, January 27, 2016 7:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Deleting a dataset that GRS has enqueued. > > A question about deleting a dataset that GRS (z/OS 1.13) has enqueued. > > We have two LPARs in a sysple

Re: Deleting a dataset that GRS has enqueued.

--- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Walt Farrell >> Sent: Thursday, January 28, 2016 06:52 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. >> >> On W

Re: Deleting a dataset that GRS has enqueued.

On Thu, 28 Jan 2016 10:46:41 -0600, Doug Henry wrote: >I will admit that I haven't followed this entire thread but this facility is >designed to rename datasets that exist on multiple volumes (like ipl volumes). >For SMS managed datasets they must be cataloged and

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 18:40:45 -0600, Paul Gilmartin wrote: >I thought from discussions here a few years ago that IBM has provided a >facility that supports renaming of an ENQUEUEd DSN, in the VTOC, after >requesting confirmation from the operators' console that that DSN on

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 19:18:26 +, Vernooij, CP (ITOPT1) - KLM wrote: > What is wrong with this solution, it is the easiest in my opinion: update > parmlib- set grs - delete. > >You can tell GRS to keep the ENQ for that DSNAME local in the GRSRNLxx parmlib >member. In

Re: Deleting a dataset that GRS has enqueued.

At 10:32 -0600 on 01/27/2016, Tom Marchant wrote about Re: Deleting a dataset that GRS has enqueued.: On Wed, 27 Jan 2016 09:37:29 -0600, 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

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 17:33:47 -0600, Walt Farrell wrote: > >Will GRS allow you to change the RNL specifications for a resource that is >already ENQ'd? Or, perhaps a more accurate question: will the change take >effect before the resource becomes DEQ'd everywhere? > I thought from discussions

Re: Deleting a dataset that GRS has enqueued.

gt;> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Robert A. Rosenberg >> Sent: Wednesday, January 27, 2016 04:59 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. >> >> At 10

Re: Deleting a dataset that GRS has enqueued.

LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > At 10:32 -0600 on 01/27/2016, Tom Marchant wrote about Re: Deleting a > dataset that GRS has enqueued.: > > >On Wed, 27 Jan 2016 09:37:29 -0600, Ed Gould wrote: > > > >>Try disabl

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 19:59:13 -0500, Robert A. Rosenberg wrote: >At 10:32 -0600 on 01/27/2016, Tom Marchant wrote about Re: Deleting a >dataset that GRS has enqueued.: > >>On Wed, 27 Jan 2016 09:37:29 -0600, Ed Gould wrote: >> >>>Try disabling the VVDS on the vol

Re: Deleting a dataset that GRS has enqueued.

On Jan 27, 2016, at 10:43 PM, TonyB wrote: Years ago I recall a young sys prog asking for advice on this forum. She qualified her request by stating "but please, no system programmer tricks." I don't call her issue but clearly a risk averse solution was desired. Sent from BlueMail That

Re: Deleting a dataset that GRS has enqueued.

jo.skip.robin...@att.net -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Robert A. Rosenberg Sent: Wednesday, January 27, 2016 04:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. At 10:32

Re: Deleting a dataset that GRS has enqueued.

If it is SYS1 there is a FACILITY class STGADMIN profile that will allow you to bypass the enqueue in 3.4 for rename only if you have access to the profile. On Wednesday, 27 January 2016, Peter Ten Eyck wrote: > Yes. The owner (in use) of the dataset is known. GRS

Re: Deleting a dataset that GRS has enqueued.

LISTSERV.UA.EDU > Subject: Re: Deleting a dataset that GRS has enqueued. > > 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

Re: Deleting a dataset that GRS has enqueued.

. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Ten Eyck Sent: Wednesday, January 27, 2016 4:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Deleting a dataset that GRS has enqueued. Yes. The owner (in use) of the dataset is known. GRS

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 09:00:05 -0600, 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. >

Re: Deleting a dataset that GRS has enqueued.

Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > On Wed, 27 Jan 2016 09:37:29 -0600, Ed Gould wrote: > > >Try disabling the VVDS on the volume > >amaspzap the dataset to change the name. > >delete the dataset with iehprogm > >enable the vvd

Re: Deleting a dataset that GRS has enqueued.

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 Ed On Jan 27, 2016, at 9:00 AM, Peter Ten Eyck wrote: A question about deleting a dataset that GRS (z/OS 1.13) has enqueued. We have two LPARs in a

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 09:37:29 -0600, 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 ITYM disable the VTOC index. I wouldn't want to do it that way. I think that what Kees suggested is

Re: Deleting a dataset that GRS has enqueued.

On Wed, 27 Jan 2016 09:51:56 -0600, Norbert Friemel wrote: >1. Create RACF facility class profile STGADMIN.DPDSRN.olddsname, rename the >dataset (ISPF 3.4), delete the renamed dataset >http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2s382/2.6.3.4 One of the conditions to be able

Re: Deleting a dataset that GRS has enqueued.

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.

Re: Deleting a dataset that GRS has enqueued.

I did that zap a few times until I found the BYPASSNQ program from Gilbert Saint-Flour. I believe he used the old method of SVC screening to replace the ENQ SVC with a BR14 just for the running task, then he called the program specified on the parm. A genius method, but of course this was

Re: Deleting a dataset that GRS has enqueued.

Good info thanks. Sadly the dataset is SMS managed. So reading the documentation you provided, it does not seem like that will work. Scratching head still.. -- For IBM-MAIN subscribe / signoff / archive access instructions,

Re: Deleting a dataset that GRS has enqueued.

Subject: Re: Deleting a dataset that GRS has enqueued. 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 i

Re: Deleting a dataset that GRS has enqueued.

On Jan 27, 2016, at 9:53 AM, Elardus Engelbrecht wrote: 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! ;-) Good advice, but that is not for the faint

Re: Deleting a dataset that GRS has enqueued.

Yes, this is good. I will try that. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Deleting a dataset that GRS has enqueued.

On Jan 27, 2016, at 11:24 AM, Tom Brennan wrote: I did that zap a few times until I found the BYPASSNQ program from Gilbert Saint-Flour. I believe he used the old method of SVC screening to replace the ENQ SVC with a BR14 just for the running task, then he called the program specified on

Deleting a dataset that GRS has enqueued.

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

Re: Deleting a dataset that GRS has enqueued.

Of Peter Ten Eyck > Sent: Wednesday, January 27, 2016 8:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Deleting a dataset that GRS has enqueued. > > A question about deleting a dataset that GRS (z/OS 1.13) has enqueued. > > We have two LPARs in a sysplex, each wi

Re: Deleting a dataset that GRS has enqueued.

use. Regards, Leo -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Ten Eyck Sent: Wednesday, January 27, 2016 10:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Deleting a dataset that GRS has enqueued. A question about deleting