Re: Why not test the lack of change instead of just testing change?

Agreed, the problem is for years most were trained to not fix if it's not
broken.

I am pestering my customers as well to update... Every week I get a few
more that are on V7R1 and trading with a partner using new Ciphers. I feel
like a broken record.

"But it worked last week!"


On Wed, Feb 21, 2018 at 7:56 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Wouldn't it be great if companies and managers did more stringent testing
on not upgrading than upgrading? For example, if IBM issues any PTFs you
would have to run though extensive testing to prove your systems were not
susceptible to any of the things fixed in those PTF's if you chose not to
put them on in a very timely fashion?
If you chose not to upgrade operating systems you had to prove that your
systems had all the stuff in place to handle whatever the new OS could do?
Such as RCAC, enhanced ciphers, etc?

There needs to be more fear in staying behind than the fear of change.




Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD