In a recent note <[EMAIL PROTECTED]> said: > Date: Mon, 31 Jul 2006 12:20:31 -0300 > > >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. > Some months ago in these pages I proposed the rudiments of a scheme of obtaining a SHR ENQ on each DEB when a data set is opened, and an EXCL ENQ on the DEB of any extent to be freed. Mark Thomen (IIRC) countered with examples of system code that manipulate extents without ever creating DEBs. The consensus of the list was that my idea was refuted and the topic closed.
Apparently it has resurfaced. But no one has considered the rescue of the idea -- that any code which manipulates extents ought to be repaired either to create DEBs or at least to issue the ENQs that would be required. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
