Types of Fixes or PTFs

Resolving The Problem

Many different kinds of fixes exist, and each fix has its own purpose. This document introduces you to the different kinds of fixes and discusses when each type is available.

Single fixes

Single PTFs are applied to correct specific reported problems. The following are descriptions of the different types of single fixes that exist:

o	High-impact pervasive (HIPER) PTF A HIPER PTF resolves a severe problem that can have a high impact on IBM OS/400 or IBM i5/OS operations, or it can resolve a low-impact but pervasive problem that affects most IBM iSeries family of servers. The following are examples of these types of situations: o Your system crashes or hangs, and it requires a restart or IPL (initial program load) to recover. o Your system is stuck in a looping condition. o Your system's data integrity is threatened. o Your system experiences a severe performance degradation, or the problem involves the usability of a product's major function.
o	Pre-requisite fix A pre-requisite fix is a fix that must be installed on your server before or at the same time as the fix that you want to install. The system will prevent you from installing your fixes if you do not have the prerequisite fixes. Your fix cover letter or PSP information can identify other fixes that must be installed before or at the same time as the fix that you want to install.
o	Co-requisite fix A co-requisite fix must be installed at the same time as the fix that you are requesting to install. Your fix cover letter or PSP information can identify other fixes that must be installed before or at the same time as the fix that you want to install. In addition, system error messages can notify you that the fix that you are attempting to install has requisite fixes. The system checks that the co-requisite fixes are installed at the same time. In this case, you must verify that your fixes installed successfully.
o	Technical Refresh requisite fix The technical refresh PTF is required to be permanently applied to the system before you can load this fix.
o	Distribution requisite fix A distribution requisite fix is required for distribution purposes only. A distribution requisite fix is sent and installed only if it is named by a fix listed in a fix group and you are using that fix group to send or install fixes. If you are sending only a fix, then the distribution requisite fix is not sent and installed. The system does not require you to apply distribution requisites.
o	Delayed fixes Some fixes cannot be applied immediately because the licensed programs they affect are active. These fixes are called delayed fixes and can be applied only at the next IPL. Delayed fixes that affect the Licensed Internal Code can be applied immediately when running on the A storage area. The cover letter tells you if the PTF is immediate or delayed.
o	Immediate fixes Immediate fixes can be applied without doing an IPL if the objects that they affect are not in use, or they can be applied when you do the next IPL. The cover letter tells you if the PTF is immediate or delayed.

Cumulative PTF packages

Cumulative PTF packages contain fixes for a given release of the OS/400 or i5/OS operating system and associated licensed programs. As the name implies, each package is cumulative; that is, it contains all of the fixes from the previous package plus additional fixes released since the previous package. Many, but not all, new fixes are included in cumulative packages. The fixes that are not included are typically applicable only to a specific user's situation or application. These fixes are not included for general availability to avoid introducing unwanted change and potential programming errors into a cumulative package where code quality has the highest priority. When you order the cumulative PTF package, you also receive the most recent Database PTF group and the HIPER PTF group.

How often a cumulative package is available depends on the stage of the OS/400 or i5/OS release life cycle. During the first six months or so of general availability for a new release, a cumulative package can be available as often as every four to six weeks. After that time, cumulative packages are scheduled on a quarterly basis. After the OS/400 or i5/OS release has been available for a period of time, the frequency can decrease again. The frequency of availability depends on the number of new fixes to be added to the package.

You should install the entire cumulative PTF package after you first load or reload the operating system and periodically throughout the release as defined in your maintenance strategy. For example, you should install cumulative PTF packages quarterly in dynamic environments and less frequently in stable ones. You should also consider installing cumulative fix packages prior to making major hardware or software changes to your environment.

Fix groups

A PTF group, or fix group in iSeries Navigator terminology, is a name that is used to order and manage a group of logically related PTFs. It consists of a list of PTFs that are defined for the purpose of managing those PTFs as one entity. A PTF group can identify other PTF groups, called related PTF groups. For a complete listing of PTF groups, refer to the following Preventive Service Planning Information Web site:

http://www-912.ibm.com/s_dir/sline003.nsf/sline003home

The cumulative PTF package is shown as a PTF group on the Work with PTF Groups (WRKPTFGRP) screen and in the Management Central fix group inventory. The cumulative PTF package is identified as a PTF group named SF99530. However, some operations that are supported by Management Central are not allowed for this fix group. These operations include sending fixes, sending and installing fixes, and installing fixes.

Service packs

Service packs are different from group PTFs. A service pack is a collection of code fixes (not PTFs) for iSeries Access for Windows products that are contained in a single OS/400 or i5/OS PTF.

The following iSeries Access Web site tells you what service packs are available, how you can be notified when a new service pack is available, and how to order and download a service pack:

http://www-03.ibm.com/systems/power/software/i/access/windows_sp.html#action

For information about how to check the service level in iSeries Access for Windows, how to obtain the latest service pack, and how to install it, go to the following Web site:

http://www-03.ibm.com/systems/i/software/access/windows/casp.html#whatspcurrent

Technical Refresh

New at release 7.1 are technical refresh (TR) PTFs. These PTFs take the place of point releases such as V5R4M5. For more information on TRs, refer to document N1012004, FAQ for Technical Refresh for R710.