> -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of Chase, John > > > -----Original Message----- > > From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin > > > > On 2014-04-04, at 08:52, Chase, John wrote: > > >>> > > >> Just curious: Does it use the ISPF-style ENQ? > > > > > > We didn't get that level of detail in the vendor's reply, but that > > > would seem to be the most logical > > choice. > > > > > So you're saying they didn't do it that way? > > Not at all. We can't tell from our incident whether they do it that way > because in our incident the > other user had the _entire library_ exclusively allocated, via DISP=OLD. The > vendor's reply said > their product attempts to obtain "exclusive allocation of the JCL _member_" > (emphasis added) before > copying it to the JES internal reader. Thus, the ISPF-style ENQ seems the > most logical choice. I > cannot say definitively whether or not they do it that way.
Update from the vendor: The scheduler DOES NOT attempt to acquire exclusive allocation of a JCL member; it only needs READ access to the JCL library. So, the entire incident is now explained by the errant user somehow obtaining an allocation of that library with DISP=OLD, which "locks out" "everybody" from that library "for the duration". -jc- ********************************************************************** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
