Absolutely make group 16 go away. 17 is effectively the same group but with all needed PTFs so that it installs correctly.

Problem with the *SAVF method is that you will have to spend time comparing what's on 16 and 17. Worse you don't know what combination of PTFs is the problem on 16. While we suspect that it's MISSING PTFs that is the problem we don't know that and SF98198 (Defective PTF listing for i 7.3) does not detail that either. It was last updated July 29 and thus doesn't even call out Group 16 as defective, so no help there.

Conclusion: I would not use that method here, I would use an image catalog. *OR* I would delete ALL PTF *SAVF that are on your system and have not been installed. Then run UPDPTFINF to update the internal PTF database on your system. Then finally re-download group 17.

I like the image catalog option best but then that's the way I usually do this. I apply PTFs to MANY partitions and the use of *SAVFs doesn't work well in that environment.

- Larry "DrFranken" Bolhuis

www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/2/2019 3:06 PM, Steinmetz, Paul via MIDRANGE-L wrote:
I already have groups 16 and 17 downloaded, via *SAVF, waiting to be installed.

How do I either remove/delete group 16?
identify all the PTFs for group 16 and remove/delete the individual PTFs?


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Buzz Fenner
Sent: Monday, December 02, 2019 12:58 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: i7.3 DB Group 16 ** Do NOT Install **

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.



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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.