Program temporary fix: Difference between revisions

Content deleted Content added
PTF installation: obsolete parameter; citations
Edit for readability
Line 1:
In IBM terminology, a '''Programprogram temporary fix''' or '''Productproduct temporary fix''' ('''PTF'''), sometimes depending on date,<ref>In 2001 a long time IBMer wrote "I thought it was now Product Temporary Fix." {{cite web
|url=https://groups.google.com/d/topic/bit.listserv.ibm-main/Ir_Jp8C50KM
|title=Should APARs be accepted}}</ref><ref>Nonetheless PROGRAM temporary 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 a singleone or more [[Patchsoftware (computing)bug|bug fix]], or group of fixes, {{endash}} distributed in a form ready to install[[software for customersinstallation|install]].
 
A PTF normally follows an APAR ([[Authorized Program Analysis Report]] (APAR)<ref>{{cite web |last1=IBM Corporation |title=IBM Security: APARs explained |url=https://www.ibm.com/support/pages/ibm-security-apars-explained |website=ibm.com |accessdate=Oct 14, 2019}} a formal report from IBM development to customers that have notified IBM of a problem or suspected defect.</ref>), 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 installation==