At 00:37 -0600 on 07/31/2006, Paul Gilmartin wrote about Re: Data set
ENQueues and DEQueues in Jobs:
And thereby hangs a long and knotted tale of how TSO ALLOCATE
will sometimes create a data set with only a SHR ENQ on the
DSNAME; fail to catalog it because of a duplicate catalog entry,
then fail to delete it because it can't obtain an EXCL ENQ
because another job has a SHR ENQ on the same DSNAME.
That is because it does not do the allocate via a Protecting QNAME
that uses a RNAME of DSN+VOLSER (you do a two QNAME ENQ [the
protecting one and the brain-dead SYSDSN] will fail if you can not
get BOTH ENQs)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
