Yup! Charles
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of retired mainframer Sent: Wednesday, April 22, 2015 10:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ENQ for the life of the job > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Paul Gilmartin > Sent: Wednesday, April 22, 2015 5:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ENQ for the life of the job > > The OP's peculiar constraint is that the serialization must be > achieved with no change to existing JCL. Does anyone else find it a little absurd that a trivial change to some JCL is a constraint violation but way outside the box solutions (which are much more complicated and may require a lifetime of maintenance) such as SMF and JES exits or a software modification to the change management system (which will probably require JCL changes any way if even feasible) that fiddles with some system control block(s) are acceptable? This looks like one of those PHB edicts to fix the problem but not change anything. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN