>I saw, firsthand, the dumbing down of OPS and it disturbed me greatly. When I started in this business, working as an operator was almost a requirement before becoming a SYSPROG.
>I had mgmt come into Operations where I worked that *never* wanted to be at >fault... that was truly their #1 priority. BTDT. GTTS. But, my management (at the time) still gave them the call of if/which changes would be implemented. And, which changes to back out. And, when I complained, they just said I didn't understand, having never been in the trenches. I said, I have the scars to prove it. Remember when you could do a $PQ and blow everything away (before $PQ,ALL was introduced and $PQ was an error). I did that, once. >They achieved this through never making a darn decision on their own... never >sticking their neck out no matter what the situation. I've worked for many financial and government organisations. That is the prevalent attitude in many departments, not just Computer Ops. The problem becomes, eventually a decision will be made, due to the erosion of the situation, and you can only postpone for so long. By the way, I think you have the wrong third letter in 'darn'. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
