At 19:37 -0500 on 12/08/2015, Shmuel Metz (Seymour J.) wrote about
Re: Inquire intrdr default job class:
In
<caajsdjgdcfhh4eonuruomvc7ovkk4wu8eado_yimw6fspnw...@mail.gmail.com>,
on 12/08/2015
at 03:21 PM, John McKown <[email protected]> said:
I do not really agree that not including the volser in the SYSDSN
enqueue is a "flaw". If it were done, then their could need to be
multiple ENQs, one for each volume in a multi-volume DSN.
The ENQ is for a PDS member; a PDS can't be multivolume.
But remember this was designed in OS/360
Which didn't allow a multi-volume PDS.
You are focusing too much on the question of if the DSN is a
PDS//PDSE or some other format. The flaw I was pointing out is that
for ANY DSN that is not unique the SYSDSN ENQ invalidly assumes that
the DSN sans VOLSER is enough to identify the dataset. Thus ANY
attempt to open DSN1 on VOLSER1 can prevent access to DSN1 on VOLSER2
due to the incorrect claim by ENQ that there is an ENQ on the VOLSER2
DSN1. This situation existed all the way back to OS/360 as soon as
you had more than 1 volume but has become much more of an issue due
to cross system sharing of the ENQs. I have no solution to this issue
but I am just pointing it out.
As I noted in a prior reply this assumption that DSN (as the RNAME)
is enough to identify the dataset for the SPFEDIT ENQ is broken since
the VOLSER is KNOWN at ENQ time and thus SHOULD be part of the RNAME
so as to allow different datasets with the same name to be
edited/accessed without the current inability to access them.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
