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: The Volser is not part of the
ENQ - Only the DSN) that is hard/impossible to fix based on the
different times and ways the ENQ is issued. IOW: The Volume that the
dataset resides on can at times be unknown until AFTER the ENQ is
issued. Thus there is no way that an ENQ on a dataset named DSN1
which is on VOLSER1 can be told from an ENQ for a dataset named DSN1
residing on VOLSER2. JES3 made some allowance but even it had to work
on with DSN and ignore the VOLSERs. There are ENQs such as that used
when SPF Editing which get issued with the knowledge of the VOLSER
where the dataset resides so they can have use the VOLSER to help the
ENQ be more specific and thus allow editing of members in different
datasets with the same DSN - I do not know if this occurs or if the
bare-bones DSN-Only is used to be the consistent with SYSDSN's RNAME.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
