ALL changes? How does that pan out when your zOS is out of spool or your IMS is on its last Online Log?
Do you add spool volumes/OLDS right away, or do you take an unplanned outage pending an approved Change Management record? My philosophy is FLY THE AIRPLANE. My first employer was an airline, and that's where I got my view of system operations. Ever wonder the original reason for a cockpit door? That door keeps the passengers away from the pilots when bad things are happening. Pilots talk to each other first and recover the aircraft. They converse with the ground, if possible. Hence, "FLY THE AIRPLANE". When the terrifying dive, turbulence, rough landing are over, the pilot may tell the passengers, what happened. With a friendly, southern (or Crocodile Dundee) drawl. "Those of you on the left side of the aircraft, may have observed a small puff of smoke as the #2 engine bucked off the pylon. But we still have three good ones to pull us back to the barn." I'm sure FLY THE AIRPLANE is why this Qantas A380 got back home safe. http://www.atsb.gov.au/newsroom/news-items/2013/in-flight-uncontained-engine-failure-airbus-a380.aspx By the way, auditors fall into the "passenger" category. Oh, and that application change that filled the IMS logs and spewed a plethora of dumps onto spool, was definitely change-managed up the kazoo. You KNOW it was. Note: I am a firm believer in Change Management. Auditor checklists...not so much. These are not necessarily the opinions of my current "airline". >We've been getting a lot of questions from audit regarding how we can tell if >ALL changes are authorized. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
