Click!
- TAGS:mainframe, printer
- IT TOPICS:Hardware, Mainframes & Supercomputers, Management
Flashback to the 1980s, when this IT pilot fish gets a call that a mainframe-attached printer isn't working in the customer support department.
"I knew that not having this printer operational would impact the department's operation, so I immediately got to work on it and determined that it was a mainframe software problem," fish says.
Over 70 tales of IT woe
(free registration required)
"I had no sooner started looking at the code than the department's manager called me, wanting to know when his printer would be fixed.
"He went on at some length as to how this outage was affecting his department's ability to respond quickly to customer calls.
"I finally said, 'Look, the longer I spend on the phone with you, the longer it will take to fix your printer.'
"I was immediately rewarded with a click in my ear as the manager hung up the phone.
"Some days later, I passed the manager in the hall and apologized for being short with him on the phone. His response was that it was his fault for taking up my valuable time."
Sharky always has time for your true tale of IT life. Send it to me at sharky@computerworld.com. You'll score a sharp Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Now you can post your own stories of IT ridiculousness at Shark Bait. Join today and vent your IT frustrations to people who've been there, done that.
Free Insider Guide
