Elardus,
I was able to delete the dsn by renaming it first and then deleting it because
I had the STGADMIN.**. authorization. The dsn was SYS1.CICS2.MODINTR
Thanks to you and Kees who helped out.
From: Elardus Engelbrecht <[email protected]>
To: [email protected]
Sent: Monday, July 10, 2017 8:36 AM
Subject: Re: DELETING DSN IN A SYSPLEX
Vernooij, Kees wrote:
"Dsn in use" is not an security issue, it is a GRS issue.
It is indeed so. Thanks.
>Datasets are serialized by their dsname only. If you have different datasets
>on different volumes with the same dsname, they will be serialized.
Ah, yes, thanks for chiming in. I totally forgot about that part. It is a long
time ago we have such duplicate names.
>You can delete the dsname by telling GRS to keep this dataset local.
To Esmie, you need to logon on ALL and every LPAR and check it on SDSF.
Or you can run a batch job with DISP=(OLD,DELETE) and then you will see the job
is standing still. You can then issue a D GRS,C command. Of course, you need to
cancel that job and then those dsn grabbers too.
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
