This is exactly why there are products like CA OPS/MVS and Automan and probably a few others. People sometimes are new to a procedure, they do accidentally make mistakes, and read and write instructions incorrectly. It is up to the systems management to make sure that proper process is in place to catch and disallow mistakes that will bring the systems down. It is perfectly legitimate to specify procedures that require certain devices to always be online, or online at specific times and dates. It is reasonable that these are documented and embedded into software procedures to ensure that they are adhered to. The operator should not be fired, but given education. The systems management that allowed this to happen are a better candidate for dismissal.
On 10/22/07, Howard Brazee <[EMAIL PROTECTED]> wrote: > > On 22 Oct 2007 12:56:30 -0700, [EMAIL PROTECTED] (Jon Brock) wrote: > > >Color me disbelieving. > ><snip> > >I think in the 30+ years I have been around OS360 and MVS and z/os, > >there has never been an operator mistake of a typo. > > I liked the time where the Vax operator put in a date a century in the > future. DIR SINCE TOMORROW found the file I created before I called > him. > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
