On Thu, 31 Mar 2016 12:31:57 -0500, Elardus Engelbrecht wrote:
>
>>All the while tiptoeing around ENQ lockouts. I discovered, decades ago, that
>>DYNALLOC will create a NEW data set while other jobs are holding ENQ SHR on
>>the DSN. To my dismay; I really wanted that *not* to happen. Went to PMR;
>>got WAD.
>
>I clearly remember your many past posts ('Bad collateral damage, but no
>integrity violation') about this where you submitted a SR about this and got a
>lame WAD answer.
>
>Did you renewed that SR?
>
I discovered the misbehavior decades ago, before SMS existed. I could
recreate it fairly recently, with non-SMS; haven't tried with SMS. IBM
told me that a key factor in the bad design (I believe they chose the worse
of two evils) was the inability then to degrade an ENQ from EXC to SHR.
That ability exists now; they could fix it, but do they want to?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
