RE: PTFs not on a CUME and/or Group -- MIDRANGE-L

Subject: RE: PTFs not on a CUME and/or Group
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 13 Jul 2020 11:57:42 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I would look at the "recommended fixes" at:
https://www.ibm.com/support/pages/node/667303

There are many reasons that some PTF's are not on any cume or group. Some of these never will be. For example there is a PTF which will change the order or some such thing on some IBM command to the way it used to be on some ancient release. More of a switch than a fix. So you may not want that.

Then there's the paranoid crowd which will not put on a fix until IBM finds a bug in it. When IBM puts out a new fix then they will finally upgrade to the older buggy one because now it is no longer on the "bleeding edge".

Rob Berendt

Follow-Ups:

RE: PTFs not on a CUME and/or Group , Steinmetz, Paul

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