<<Clueless management too far removed from the system making policy
decisions.>>

The other day, I was on a 5 hour conference call. One of the IBM'ers had the
huevos to tell the clueless managers that if they didn't get more current,
the only answer that would be forthcoming for service calls would be "Call
us back after you've caught up with us."

It was a good thing my phone was on mute. I broke out laughing.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
McKee
Sent: Monday, August 24, 2015 9:52 AM
To: Midrange Systems Technical Discussion
Subject: If it ain't broke, don't fix it

I did not want to pollute the thread "If you have SSDs, please read".

Some years ago, PTFs stopped being applied here. Much like "if it ain't
broke". We had an application that did screen scraping. Long gone. A
Client Access PTF broke the application. A somewhat critical application,
as it turned out. The SA may or may not have contacted the vendor of the
pc software. But, what was done was the PTF was backed out.

After that, no CUMEs were installed. Only PTFs identified by service
advisor.

Various people in command hierarchy, I have no idea how high up, set that
policy.

Potentially very dumb policy. That was why I was a little hesitant to
install PTFs suggested by Scott K that corrected errors with ssh. I am
glad I did, as the enhanced error handling made a number of transfers
performed subsequently a LOT nicer.

Clueless management too far removed from the system making policy decisions.

"Don't confuse me with facts, I have already made up my mind".


John McKee

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].