Program temporary fix: Difference between revisions

Revision as of 01:07, 8 February 2018

Revision as of 19:29, 15 April 2019

Line 3:

|title=Should APARs be accepted}}</ref><ref>Nonetheless PROGRAM temproary fix is still in use. {{cite web

|title=Traps do not process for CiscoAPIC models in CA Spectrum

|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''<ref>{{cite web |website=AcronymFinder.com
|title=PTF - Permanent Temporary Fix (humor)
|url=https://www.acronymfinder.com/Permanent-Temporary-Fix-(humor)-(PTF).html}}</ref> 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.