On 04/22/2015 12:38 PM, retired mainframer wrote: >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] On >> Behalf Of Paul Gilmartin >> Sent: Wednesday, April 22, 2015 5:10 AM >> To: [email protected] >> 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. > > ---------------------------------------------------------------------- One possible explanation for the no-JCL-change requirement is that the JCL in question may not have a centrally controlled single copy but be in many places, perhaps even user-customized, making coordinating/enforcing a change that requires JCL changes difficult.
If that is the case, one possible workaround it to find some way to generate the customized JCL using a dialog or script of some kind, get all the users trained and required to regenerate the JCL that way every time instead of working with JCL directly, and then at some point change the dialog to implement the needed JCL changes. -- Joel C. Ewing, Bentonville, AR [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
