This blog explains the importance of keeping your IBM i OS current with PTFs and Technology refreshes. My purpose is to provide a clear understanding of the important of PTFs.
I am concerned about a common inattention among our iSeries clients that neglect IBM PTFs to keep their IBM i OS (OS400/i5/OS) current. I understand the common justification – “the system is working fine, and it will all get taken care of on the next version release. If it ain’t broke, don’t fix it. So, why not wait?
First, let me explain what a “PTF” is. PTF stands for Program Temporary Fix. A PTF is a software patch to fix a “bug” or make an “improvement” with the IBM Licensed Program Products (LPPs), generally the operating system. The “temporary” part of this means that it is an interim fix until the next release of the OS comes out. At that time the “fix” will be incorporated into the new release code.
Starting with V6R1, IBM has greatly slowed down the frequency of new OS releases to give their customers more time to assess and upgrade to the newest version (IBM has many world-wide clients that struggle to upgrade to a new OS release in less than 3 years). So, instead of a new OS every 2 years, IBM offers new functionality as well as fixes by issuing Technology Refreshes, or TRs.
This means the old approach of waiting for the next IBM i OS to update your PTFs is more precarious. Because of the longer time interval between IBM i OS releases, it is more important now to keep up on PTFs because it will be a longer time before the new OS version comes out.
In addition to updating the PTF level, the TRs add additional capabilities to the existing OS. For example, some of what has been added to V7R1 are User Profile Enhancements, Object Audit Enhancements, Data Encryption, Security Enhancements, and updated programming tools. These have all been delivered via TR to V7R1. There have also been several TRs for V7R2.
So why should you care about PTFs and TRs?
- If you ever use IBM software support, the first thing they ask is what your PTF level is. If you are back level, they will generally want you to get caught up before they will even start working on your issue.
- When IBM identifies a widespread problem, such as the recent WebSphere Application Server Java vulnerability, they develop a fix. However, that fix is based on the most up to date version of the OS level it is for. They do not go back and test those fixes on OS versions that are not current with the latest PTFs and TRs. So, while the fix is tested and verified, there is no guarantee that it will work on a system that is back level on PTFs.
- Skipping too many PTF/TR levels can cause IBM i OS and Microcode incompatibility. (Microcode is the software that programs hardware functions, also called firmware or Licensed Internal Code.) This can prevent you from upgrading your server to a new OS level until the microcode is updated, causing additional downtime, and in some cases, requiring that the upgrade be reverted until the problem is fixed. Current PTF’s cannot be installed if the TR level is too far behind. It requires that additional steps be taken and more time to update the system Licensed Internal Code (LIC).
- IBM’s trend has to been to add the same OS functionality to all current OS levels with TRs. So, for example, new features and functionality included in V7R2, are added to V7R1 via TRs. This means you can operate at an OS level longer without upgrading to some new release to obtain some functionality that you or your software vendor requires.
- IBM LPPs such as WebSphere products are patched through the same process, but require extra steps, and are dependent on your overall PTF and TR level. These LPP patches are essential to enhancing performance and securing these products from intrusion.
We strongly recommend that our clients keep up to date on PTFs and TRs. Talk to your software vendors, they will tell you the same thing. Once you learn the process, managing and applying PTFs is not difficult. Or, if you prefer, talk to us, we can handle your updates on a turnkey basis, with very little interruption to your users or processes.
Leave a Reply