I was once granted access to, and crashability of, "a totally isolated test system" to test my sensitive supervisor state, key 0 code. I managed to cause JES2 on the test system to crash just after it had done a hardware reserve to its checkpoint data set, which, of course, was also shared by the production system. Thus I caused a lengthy non-optimal situation on the production system. My point is to examine every possible link between the two allegedly physically isolated systems with a high-powered magnifying glass and as a criminal trial lawyer would think; i.e., assume that the two systems have at least one link that you haven't found yet, guilty until proven innocent etc.
Bill Fairchild Rocket Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Hooper Sent: Tuesday, July 06, 2010 8:55 AM To: IBM-MAIN@bama.ua.edu Subject: Re: ENQ trap for dynamic allocation >...Totally physically isolate development from production and do not allow >them to even see production files. ---------------------------------------------------------------------- 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 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
