Paul Gilmartin wrote:
>Notwithstanding ISPF has effective mechanisms for serializing library updates
>by multiple users.
As long you setup your GRSxxx parmlib member correctly.
>Compressing a data set in use is probably a bad idea.
Oh yes! I burned my fingers by doing that stunt while being a naive junior...
>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?
retired mainframer wrote:
>There is a RACF profile that will allow you to rename the old one and then you
>can delete it.
Are you refering to this dangerous profile STGADMIN.DPDSRN.** in FACILITY Class?
It is similar to STGADMIN.ADR.COPY.TOLERATE.ENQF, but then you use DFDSS and
show the middle finger to GRS.
I only give access after I explained they take responsibility and they promised
not to come crying to me...
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
