Program temporary fix: Difference between revisions

Revision as of 23:48, 7 December 2017

Revision as of 00:23, 8 December 2017

Line 1:

'''Program temporary fix''' or '''Product temporary fix''' ('''PTF'''), sometimes depending on date,<ref>In is the standard [[IBM]] terminology for2001 a singlelong [[Patchtime (computing)|bugIBMer fix]],wrote or"I groupthought ofit fixes,was distributednow inProduct a form ready to install forTemporary customersFix." {{cite Customersweb 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.

|url=https://groups.google.com/d/topic/bit.listserv.ibm-main/Ir_Jp8C50KM

|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'' 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 follows an APAR, and where an "APAR fix" was issued, the PTF "is a tested APAR."<ref name=Gabe/>