Program temporary fix: Difference between revisions

Revision as of 02:25, 11 January 2023

Latest revision as of 00:57, 12 August 2025

(14 intermediate revisions by 10 users not shown)

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==

{{refimprovemore citations needed section|date=August 2021}}

{{expand section|Maintenance vehicles for other platforms|talk=Service cycle|date=August 2021}}

Initially, installations had to install service via a semi-manual process.<ref>{{cite manualbook

| title = IBM System/360 Operating System - Maintenance Program

| id = C27-6918

| workseries = Systems Reference Library

}}

</ref>

Over time, IBM started to provide service aids such as IMAPTFLE<ref>{{cite manualbook

| title = IBM System/360 Operating System: Service Aids - OS Release 21

| id = GC28-6719-2

| date = March 1972

| edition = Third

| pages = 219-239219–239

| section = Chapter 9: IMAPTFLE

| section-url = http://bitsavers.org/pdf/ibm/360/os/R21.0_Mar72/GC28-6719-2_Service_Aids_Rel_21_Mar72.pdf#page=219

| url = http://bitsavers.org/pdf/ibm/360/os/R21.0_Mar72/GC28-6719-2_Service_Aids_Rel_21_Mar72.pdf

| workseries = Systems Reference Library

}}

</ref>

and utilities such as IEBEDIT<ref>{{cite manualbook

| title = IBM System/360 Operating System - Utilities

| id = GC28-6586-11

| date = June 1970

| edition = Twelfth

| pages = 392-402392–402

| section = The IEBEDIT Program

| section-url = http://bitsavers.org/pdf/ibm/360/os/R19_Jun70/GC28-6586-11_Utilities_Rel_19_Jun70.pdf#page=392

| url = http://bitsavers.org/pdf/ibm/360/os/R19_Jun70/GC28-6586-11_Utilities_Rel_19_Jun70.pdf

| workseries = Systems Reference Library

}}

</ref> to simplify the installation of batches of PTFs. For [[OS/360 and successors]], this culminated in System Modification Program (SMP)<ref>{{cite and [[System Modification Program/Extended]] (SMP/E).book

| title = OS/VS System Modification Program (SMP) - System Programmer's Guide

| id = GC28-0673-6

| date = September 1980

| edition = Seventh

| url = http://bitsavers.org/pdf/ibm/370/OS_VS/GC28-0673-6_OS_VS_System_Modification_Program_%28SMP%29_Systems_Programmers_Guide_7th_ed_198009.pdf

| series = Systems

| publisher = [[IBM]]

| access-date = July 10, 2023

}}

</ref> and [[System Modification Program/Extended]] (SMP/E).<ref>{{cite book

| title = System Modification Program Extended - 8.1

| id = SC28-1107-13

| date = September 1994

| edition = Fourteenth

| url = http://bitsavers.org/pdf/ibm/370/SMP-E/SC28-1107-13_System_Modification_Program_Extended_Reference_Release_8.1_14th_ed_199409.pdf

| publisher = [[IBM]]

| access-date = July 10, 2023

}}

</ref>

For [[VM (operating system)|VM]], this culminated in Virtual Machine Serviceability Enhancements Staged (VM/SP SES) and VMSES/E.

Line 47 ⟶ 66:

==PTF usage==

{{abbreviations|section|HA|date=January 2023}}

{{expand section|Maintenance vehicles for other platforms, alternate methodologies|talk=Service cycle|date=August 2021}}

PTFs used to be distributed in a group on a so-called ''Program Update Tape'' (''PUT'') or ''Recommended Service Upgrade'' (''RSU''), approximately on a monthly basis. They can now be downloaded straight to the system through a direct connection to IBM support. In some instances IBM will release a "Cumulative PTF Pack", a large number of fixes which function best as a whole, and are sometimes codependent. When this happens, IBM issues compact discs containing the entire PTF pack, which can be loaded directly onto the system from its media drive.

One reason for the use of physical media is size, and related (default) size limits. "By default, the /home file system on VIOS (Virtual I/O Server<ref>{{cite web |last1=IBM Corporation |title=Virtual I/O Server overview |url=https://www.ibm.com/support/knowledgecenter/TI0003M/p8hb1/p8hb1_vios_virtualioserveroverview.htm |website=IBM Knowledge Center |accessdate=Oct 14, 2019}}</ref>) for [[IBM System p|System p]] is only 10GB in size."<ref name=TecTip>{{cite web |title=Populating the VIOS Virtual Media Repository

|author=Glenn Robinson |work=PowerWire - Connect to the IBMi Community |date=October 28, 2015

|url=http://powerwire.eu/tech-tip-populating-the-vios-virtual-media-repository}}</ref> If the "Cumulative PTF Pack" is larger than the default, "If you try (to) FTP 17GB of ISO images you will run out of space."

TheIn [[z/OS]], the PTFs are processed using [[SMP/E]] (System Modification Program/Extended) in several stages over a course of weeks. Each PTF may include ''HOLDDATA'', in which case it is known as an ''exception SYSMOD''. In rare cases an installation may install a single PTF, but normally it will install all available service except PTFs excluded by, e.g., aging policies, HOLDDATA. Details vary from installation to installation, but a simple service cycle would involve these steps:

# Download the most recent HOLDDATA

# ''Receive'' (load) the proper PTF to the HA (non-production) system

# ''RECEIVE'' (load) the service and HOLDDATA to the ''Consolidated Software Inventory'' (''CSI'')

# ''Apply Check'' to make sure necessary prequisite PTFs are installed, or are being installed, and that none have been marked "held" for errors or other problems

# ''APPLY CHECK'' the service and HOLDDATA to list exception SYSMODs, verify that necessary prerequisites are available, and to list potential problems, e.g., errors.

# ''Apply'' the PTF to the HA system, and review the system's performance over multiple weeks to ensure it does not hinder your productivity or functionality

## Review exception SYSMODs for, e.g., ACTION, DOC, holds.

# ''Receive and apply'' the PTF to the production system and monitor its effects for several weeks

## Update documentation to reflect the exception SYSMODs, and take any necessary actions

## Order and RECEIVE any missing prerequisites.

## ''RESTORE'', ''REJECT'', rework and re-APPLY any local exits or modifications affected by the service.

# ''ApplyAPPLY'' the PTFservice to the HAone system in a [[High-availability cluster|cluster]] (if available), and review the system's performance over multiple weeks to ensure it does not hinder your productivity or functionality

## Selectively ''BYPASS'' HOLDDATA when appropriate

# ''ReceiveRECEIVE and applyAPPLY'' the PTFservice to the production system and monitor its effects for several weeks

If the system is adversely affected by the PTFservice, a [[system administrator]] may sometimes selectively ''restoreRESTORE'' (un-apply) the PTFit and seek further support from IBM. However, if no problems are found after the PTFservice is applied, it can be permanently installed, ''acceptedACCEPTed'', or ''(committed'',) to the system.

These repairs to IBM software are often in response to APARs submitted by customers and others and acted on by IBM, and are a common first step to resolving software errors. It is generally expected by the customer that the problem would be fully corrected in the next release (version) of the relevant product.

==Comparison to APAR==

At times<ref name="AmiTech">"Issues with Cognos and other IBM software can arise from configuration errors, problems in third-party hardware or software, and occasionally, because of a bug in the IBM product itself." {{cite web|url=http://www.amitechsolutions.com/uncategorized/ibm-support-authorized-program-analysis-reports|title=IBM Support – Authorized Program Analysis Reports|website=AmitechSolutions.com|access-date=2017-12-07|archive-url=https://web.archive.org/web/20171208122616/http://www.amitechsolutions.com/uncategorized/ibm-support-authorized-program-analysis-reports/|archive-date=2017-12-08|url-status=dead}}</ref> IBM software has a bug.

Once IBM has ascertained that the cause is not one of

Line 72 ⟶ 98:

* non-IBM software -or-

* user-specified configuration errors,

IBM support staff, if they suspect that a defect in a current release of an IBM program is the cause, will file a formal report confirming the existence of an issue. This is referred to as an ''Authorized Program Analysis Report (APAR).'' See {{cite web|title=APARs and PTFs|website=[[IBM]] |url=https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q040520_.htm}}

APARs also include

Line 82 ⟶ 108:

There are at least 2 levels of fix:<ref>"An APAR fix is usually replaced later by a permanent correction called a PTF." {{cite book

|title=Introduction to the New Mainframe: z/OS Basics

|url=https://books.google.com/books?isbn=0738435341 |isbn=0738435341978-0738435343

|first1=Mike |last1=Ebbers |first2=John |last2=Kettner |first3=Wayne |last3=O'Brien |date=2012| publisher=IBM Redbooks }}</ref>

* The APAR may result in an "APAR fix."

* a permanent correction called a PTF.

The focus of the "APAR fix" is "to rectify the problem as soon as possible"<ref name=Mehdi>{{cite web

|title=Diff between PTF, APAR, INTERMFIX |author=Mehdi Salebi

|url=http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/diff-between-ptfaparintermfix-4353121

|date=August 7, 2011}}</ref> whereas the PTF "is a tested APAR... The PTF 'closes' the APAR. " Prior to that, an APAR is "a problem with an IBM program that is formally tracked until a solution is provided.”<ref name=Gabe>{{cite web

|website=destinationz.org (MSP TechMedia) |author=Gabe Goldberg |date=June 12, 2013

|title=IBM’sIBM's APAR process provides the tools for dealing with software issues

|url=http://www.destinationz.org/Mainframe-Solution/Systems-Administration/APAR-Process-Provides-Tools-to-Deal-With-Software-|archive-url=https://web.archive.org/web/20140401090011/http://destinationz.org/Mainframe-Solution/Systems-Administration/APAR-Process-Provides-Tools-to-Deal-With-Software-|url-status=usurped|archive-date=April 1, 2014}}</ref>

==Humor==

Line 99 ⟶ 125:

|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.

One explanation of Program Temporary Fix says it's temporary, just until the next ice age.

== See also ==

Line 118 ⟶ 145:

[[Category:Software maintenance]]

{{Compu-soft-stub}}

{{OperatingSoftware-systemeng-stub}}