|
On Mon, 2 Dec 2019, 14:56, Andrew Lopez wrote:
FYI This one is bad. Can actually require re-installing the O/S!!
We somehow dodged the bullet here. We're on Level 17 (installed yesterday), but >Level 16 shows as having been installed as well. Does anyone know what would cause >some servers to not have a problem, and others to experience this?
More details on the issue can be found at https://www.itjungle.com/2019/12/02/db2->for-ibm-i-7-3-hits-a-bad-patch/, but it doesn't get into the details of why some >systems can run Level 16 without a problem.
We, too, have either dodged a bullet or we're living on borrowed time. Installed lvl 16 last Friday morning (with CUME & Groups) and the system (8202-E4D) is humming along.
I'm scheduling an out-of-cycle apply for lvl 17 this weekend, hopefully allowing me to sleep better.
--Buzz
________________________________
This electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
