If it ain't broke, don't fix it needs to be replaced with It is broke, we just haven't hit it yet.
Paul Fenstermacher | Sys Admin, Sr | Corporate Systems - POWER Systems
Administration | Jack Henry & Associates, Inc.
2135 E. Primrose | Springfield, MO 65804 | 417-235-4114 x177389 |
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 <midrange-l@xxxxxxxxxxxx>
Subject: If it ain't broke, don't fix it
The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.
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".
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.