"John Hooper" <jhoo...@foodlion.com> wrote in message news:<listserv%201007071639213340.0...@bama.ua.edu>... > I have looked at the exits and I don't see two things that I would have to > have to recover from SYSDSN ENQ failures. First, I can't see a way to get > control on and ENQ failure and secondly, even if I could, I could not see a way > to redrive the original ENQ request for SYSDSN. Also, all of the ENQ exits > seem to indicate that a "wait" is not allowed. A WTOR or STIMER does that if > you want to wait a bit and retry. Also, there seems to be discussion about > my possible "solution" to remove RACF read access. It is true that ENQ and > RACF have no connection. It is just likely that a DD statement in JCL or a > utility control statement will at least eventually open the file even though the > ENQ might have already been satisfied. A security failure will reduce the > likelyhood that the programmer will just follow the old adage "if at first you > don't succeed, resubmit the job and hope for a miracle". > > It also looks like the most common approach to prevent development access > from interfering with production process is to isolate production data from > development. Is that the consensus? Thanks. >
Well no, the original problem is a production job wanting a data set that is held by a development job. Apparently both may/need use the same data and you cannot separate them. If you could, you can also deny the development job any access to the data set in the current environment. A simple solution is to use JCL allocation: the system issues the contention message, the automation tool traps it checks the situation and cancels the development job. Kees. > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
