>We had to tell our operators the same thing you need to tell your Prod Control >staff - stop trying to play with the inits and do something else with your >time...
I've had that ongoing battle since 1981. I once worked at a small shop, about 20 years ago, just as 3480's were being introduced. We had only 4, and three jobclasses for them: 1. K -- one cartriddge drive 2. L -- two drives 3. M -- 3 or 4 drives (weekends only) I had set up the init structure to allow for 2 CLASS=K, and one CLASS=L. And, one CLASS=M, active only on weekends. The drives were constantly active. Then, one operator noticed there was a queue of CLASS=M, and started setting and opening initiators during the week. We got the old WAIT/NOHOLD messages, and K/L throughput (critical jobs) started waiting. They raised a complaint to me, and my senior management wanted to know "what I had done wrong". It took a long time to explain what Ops had done, and why I had done what I done. And, after I explained it all, Ops still complained that "there a queues in CLASS=M", and we reserve the right to manage that. Unfortunately, my management didn't back me up. So, whenever K/L jobs didn't meet targets, which directly impacted revenue, I would re-assign the problem tickets to Ops, with the same explanation, each time. It took almost a year, but my word became law on initiator management. My performance review though was based on the perceived impact that "I" had made, rather than Ops. I left shortly after, to a job where they hired me for my expertise, and listened to it. This has made me overly sensitive to ops dinking with inits. In general, they're (at best) not improving service, and (usually) making it worse. - 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
