IBM i PTF Management and Maintenance Planning

Program temporary fixes (PTFs) are how IBM delivers fixes, and some new function, for IBM i and its licensed programs. Applying them is easy; applying them safely, on a predictable schedule, with a way back if something goes wrong, is what separates a well-run system from one that accumulates risk.

This guide is about planning: the kinds of PTFs you will deal with, how to see what is installed, how temporary and permanent application and immediate and delayed PTFs affect your maintenance window, and a checklist for production. For the mechanics of ordering cumulative packages, managing group PTFs, and upgrading the operating system, see IBM i PTF Management and OS Upgrades.

Why Maintenance Planning Matters

Every IBM i system runs a particular combination of licensed program releases and fix levels. Left alone, that combination drifts further from what IBM currently supports and tests: security fixes are missing, known defects stay in place, and the eventual catch-up becomes a large, risky change instead of a routine one.

A maintenance plan answers four questions before anything is applied:

  • What will be applied, and why?
  • When will it be applied, and does it need an IPL?
  • How will you know it worked?
  • How will you back out if it did not?

Kinds of PTFs

  • Individual PTFs fix a specific problem in a specific licensed program. You usually order one when IBM support identifies it for a problem you have, or it arrives as a requisite of another PTF.
  • Cumulative PTF packages collect fixes for the operating system and Licensed Internal Code up to a point in time. They are the baseline that most maintenance plans are built on.
  • PTF groups collect the PTFs for a functional area, such as Db2 for i, Java, the HTTP server, or security. IBM updates groups more often than the cumulative package, and each group has a level number that increases with each update.
  • HIPER PTFs fix high-impact or pervasive problems. IBM collects them in a HIPER PTF group so that they can be applied between cumulative packages.
  • Technology Refreshes deliver new function for a release through a PTF group. Treat them as functional changes that need testing, not as routine fixes.

HIPER and Defective PTFs

Not every PTF is safe to apply blindly. IBM’s Preventive Service Planning (PSP) information for each release lists HIPER problems that are not yet included in the latest cumulative package and, in a “PTFs in error” section, PTFs that were later found to be defective. A defective PTF is often called a PE PTF.

Before every maintenance window:

  1. Read the current PSP information for your release, including the HIPER and PTFs-in-error sections.
  2. Check whether any PTF you plan to apply, or have already applied, is listed as defective, and what the recommended fix is.
  3. Read the cover letter of each individual PTF for special instructions, such as required IPLs, pre-requisites, or actions to take after applying it.

Seeing What Is Installed

Start every plan with a baseline. WRKPTF and DSPPTF show the PTFs for a product and their status:

/* Work with the PTFs for the operating system */
WRKPTF LICPGM(5770SS1)

/* Display the status of one PTF */
DSPPTF LICPGM(5770SS1) SELECT(SI12345)

/* Print the PTF status of every product for your change records */
DSPPTF LICPGM(*ALL) OUTPUT(*PRINT)

WRKPTFGRP lists the PTF groups installed and their levels:

WRKPTFGRP

The same information is available through SQL, which is easier to save, compare, and automate:

-- Installed PTF groups and their status
SELECT PTF_GROUP_NAME, PTF_GROUP_DESCRIPTION, PTF_GROUP_LEVEL, PTF_GROUP_STATUS
  FROM QSYS2.GROUP_PTF_INFO
 ORDER BY PTF_GROUP_NAME, PTF_GROUP_LEVEL DESC;

-- Compare installed group levels with the levels IBM currently lists
SELECT PTF_GROUP_ID, PTF_GROUP_TITLE,
       PTF_GROUP_LEVEL_INSTALLED, PTF_GROUP_LEVEL_AVAILABLE,
       PTF_GROUP_CURRENCY, LAST_UPDATED_BY_IBM
  FROM SYSTOOLS.GROUP_PTF_CURRENCY
 ORDER BY PTF_GROUP_CURRENCY, PTF_GROUP_ID;

SYSTOOLS.GROUP_PTF_CURRENCY reads IBM’s Preventive Service Planning information over the internet, so the partition needs outbound access to IBM. If it cannot connect, the currency column says the information is not available.

Temporary and Permanent Application

PTFs are applied temporarily or permanently:

  • Temporarily applied PTFs can be removed. The previous version of the changed objects is kept so that you can go back.
  • Permanently applied PTFs cannot be removed. The saved previous version is discarded.
/* Apply PTFs temporarily */
APYPTF LICPGM(5770SS1) SELECT(*ALL) APY(*TEMP)

/* Later, after the system has run successfully, make them permanent */
APYPTF LICPGM(5770SS1) SELECT(*ALL) APY(*PERM)

A common practice is to apply new PTFs temporarily and make them permanent only after the system has run on them through at least one normal business cycle. Making older PTFs permanent before the next maintenance window also keeps the number of temporarily applied PTFs, and the storage they use, under control.

Immediate and Delayed PTFs

Some PTFs can be applied while the system is running; these are immediate PTFs. Others, including many Licensed Internal Code PTFs, are delayed: they can only be applied during an IPL.

/* Apply the immediate PTFs now. Delayed PTFs can only be applied during an IPL. */
APYPTF LICPGM(5770SS1) SELECT(*ALL) APY(*TEMP) DELAYED(*NO)

Even an immediate PTF may need objects that are in use to be released, or require that a server or subsystem is restarted; the cover letter says so. Plan the maintenance window around the PTF that needs the most disruption, not the least.

For a complete cumulative package or a set of PTFs that includes delayed PTFs, most shops use the PTF menu, which loads the PTFs and sets them to be applied at the next IPL:

GO PTF
/* Option 8: Install program temporary fix package */

Planning IPLs

Delayed PTFs take effect at the next IPL, so the IPL is part of the maintenance plan:

  • Schedule the IPL inside the agreed window and confirm who must be told before and after.
  • Know how long a normal IPL takes on this system, and allow extra time: an IPL that applies PTFs takes longer than a routine one.
  • Confirm that subsystems, servers, and batch schedules restart as expected afterwards.
  • If the window is cancelled after PTFs have been marked for the next IPL, either keep that IPL in the plan or deliberately change what is marked, so that an unplanned IPL does not apply them unexpectedly.

Rollback and Removal

Temporarily applied PTFs can be removed with RMVPTF. Removing a delayed PTF also requires an IPL, and a PTF that other applied PTFs depend on cannot be removed on its own. Permanently applied PTFs cannot be removed at all.

Your real rollback plan therefore has two layers:

  1. Remove specific PTFs when a newly applied, temporarily applied PTF is identified as the cause of a problem, ideally with IBM support’s guidance.
  2. Restore from a save when the problem is broader. Take an appropriate save before major maintenance, such as a cumulative package or an operating system change, and confirm that it completed successfully.

Keeping Key Groups Current

Between cumulative packages, the PTF groups for the parts of the system you depend on deserve their own schedule. Typical priorities are:

  • Security and HIPER fixes — review new levels as soon as they are published and apply them within your security patching policy.
  • Db2 for i — query optimiser and SQL fixes matter for any SQL-heavy workload.
  • Java and the HTTP server — important if you run web applications, integration servers, or Java-based tools on IBM i.
  • Technology Refresh — plan these as feature changes, test them, and apply them when you need the new function or when supported levels require them.

Use SYSTOOLS.GROUP_PTF_CURRENCY or IBM’s PSP information to see which groups are behind, rather than relying on memory.

Planning a Maintenance Window

A practical cadence for most production systems:

  1. Plan — decide the scope (cumulative package, groups, individual PTFs) from the current PSP information and your currency report.
  2. Order — order the PTFs with SNDPTFORD or download them from IBM, and keep the cover letters.
  3. Test — apply them to a test or development partition that matches production and run representative batch jobs, interactive work, and integrations.
  4. Prepare production — take the save your rollback plan requires, confirm the IPL time, and notify users.
  5. Apply — apply the PTFs temporarily and IPL if delayed PTFs are included.
  6. Verify — check PTF status, the job logs of the IPL and key subsystems, and the applications.
  7. Record — save the new PTF and group levels with your change records.
  8. Make permanent — after a period of stable running, permanently apply the PTFs from earlier windows.

Production Checklist

  • Current PSP, HIPER, and PTFs-in-error information reviewed
  • Cover letters read for every PTF with special instructions
  • PTFs tested on a non-production partition
  • Save taken and verified according to the rollback plan
  • IPL scheduled and communicated, if delayed PTFs are included
  • PTFs applied temporarily
  • PTF and group status checked after the window
  • Applications, subsystems, and scheduled jobs verified
  • New PTF levels recorded with the change
  • Earlier PTFs made permanent once stable

Common Mistakes

  • Applying without testing. A PTF that is safe in general can still interact badly with your applications or configuration.
  • Ignoring defective PTFs. Applying a PTF listed in the PTFs-in-error section without its fix repeats a problem IBM has already documented.
  • Making everything permanent immediately. You lose the easiest way back.
  • Never making anything permanent. Temporarily applied PTFs accumulate and use storage, and old temporary PTFs make later maintenance harder.
  • Forgetting the IPL. Delayed PTFs are not active until the system IPLs, and an unplanned IPL can apply marked PTFs at an inconvenient time.
  • Treating maintenance as a yearly event. Large, infrequent catch-ups are riskier than smaller, regular updates.
  • Not recording levels. Without a record of what changed and when, it is much harder to connect a problem to a maintenance window.

Summary

PTF maintenance on IBM i is a routine discipline: know what is installed, read the PSP and cover-letter information, test first, apply temporarily, plan IPLs for delayed PTFs, keep a rollback path, and record what you did. Done regularly, it keeps the system supported and secure without turning every update into a high-risk event. For ordering cumulative packages and group PTFs, and for planning a release upgrade, continue with IBM i PTF Management and OS Upgrades.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top