On Wed, 14 Oct 2009 14:40:17 -0400, Arthur T. <[email protected]> wrote:
>On 14 Oct 2009 03:11:45 -0700, in bit.listserv.ibm-main >(Message-ID:<listserv%[email protected]>) >[email protected] (Luc Martens , KBC) wrote: > >>we recently had some incidents which caused us a lot of >>debugging before we noticed what was going one. >>Some JES2 parmlib definitions did not correspond with the >>actual state of the definitions in JES2. > > This doesn't exactly address your issue, but is it >time (and is it feasible) to open a requirement to >IBM? The requirement would be for a JES2 command which >would create a valid parmlib that matched the current >settings. > <snip> <soap box> It's nice to dream. But why stop there? The entire operating system is full of places you can make dynamic changes without "hardening" them. z/OS PARMLIB is full of them. LNKLST, APF, EXITs, SMF, PPT, Subsystems, ... and the list goes on. Then there are your major subsytems (CICS, DB2, MQ, CICS, WAS) that also support dynamic changes. Some changes survive recycles / restarts without overt action, some don't. This is what change control and procedures are meant for. If you don't have both and enforce them, bad things will happen eventually. I realize it's nice to have the double check but the best tool is probably still a sledge hammer to the fingers of those that don't follow those procedures. </soap box> Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
