Revision as of 23:52, 14 October 2019 edit Peter Flass (talk \| contribs) Autopatrolled, Extended confirmed users 19,403 edits rearrange lead and move "humor" to a separate later section, add info on APAR ← Previous edit		Revision as of 23:57, 14 October 2019 edit undo Peter Flass (talk \| contribs) Autopatrolled, Extended confirmed users 19,403 edits →PTF usage: apply check Next edit →
Line 17: # ''Receive'' (load) the proper PTF to the HA (non-production) system # ''Apply Check'' to make sure necessary prequisite PTFs are installed, or are being installed, and that none have been marked "held" for 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 # ''Receive and apply'' the PTF to the production system and monitor its effects for several weeks Line 22 ⟶ 23: If the system is hindered by the PTF, a [[system administrator]] may sometimes ''reject'' (un-apply) the PTF and seek further support from IBM. However, if no problems are found after the PTF is applied, it can be permanently installed, ''accepted'', or ''committed'', to the system. These repairs to IBM software are often in response to APARs ~~([[Authorized Program Analysis Report]]s)~~ 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==

Program temporary fix: Difference between revisions