At 12:20 -0300 on 07/31/2006, Shmuel Metz (Seymour J.) wrote about
Re: Data set ENQueues and DEQueues in Jobs:
>Part of the problem with this type of incorrect "conflict" is that
the SYSDSN Queue (the QNAME used for the ENQ/DEQ) regards the DSN
(the RNAME) as the identifier of the Dataset not the CORRECT DSN with
VOLSER.
Which volser? You would have to be very careful to avoid a deadly
embrace.
You trimmed my quote back too far. I acknowledged in my statement
that the root cause of the need to not include the VOLSER in the
RNAME is that the ENQ is being done prior to the allocation of the
dataset being managed by the ENQ (some times before the dataset even
exists such as in the case of a DISP=NEW). So long as you do not know
which version of a dataset you are going to use, you can not include
the VOLSER in the RNAME (as I noted this restriction DOES NOT apply
to ISPF or other SVC99 usage since at that point in time you DO know
the dataset's VOLSER and thus can use it for non-SYSDSN private
QNAMEs such as ISPF's SYSEDIT[?]).
----------------------------------------------------------------------
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
