Revision as of 00:23, 8 December 2017 edit Pi314m (talk \| contribs) Extended confirmed users 15,149 edits →The "P" of PTF can be program or product, but it has become the outcome of when an APAR becomes PERMANENT ! ← Previous edit		Revision as of 21:27, 8 December 2017 edit undo Chatul (talk \| contribs) Extended confirmed users 8,448 edits APAR might be fixed only by a new release; one PTF might fix multiple APARsw. Next edit →
Line 5: \|url=https://support.ca.com/us/knowledge-base-articles.TEC1984606.html \|date=September 11, 2017 \|website=ca.com}}</ref> is the standard [[IBM]] terminology for a single [[Patch (computing)\|bug fix]], or group of fixes, distributed in a form ready to install for customers. Customers sometime explain the acronym in a tongue-in-cheek manner as ''permanent temporary fix'' or more practically ''probably this fixes'', because they have the option to make the PTF a permanent part of the operating system if the patch fixes the problem. A PTF normally follows an APAR, and where an "APAR fix" was issued, the PTF "is a tested APAR."<ref name=Gabe/> or set of APAR fixes. However, if an APAR is resolved as "Fixed If Next" or "Permanent Restriction" then there may be no PTF fixing it, only a subsequent release. ==PTF usage==

Program temporary fix: Difference between revisions