IBM i PTF Guide, Volume 19, Number 8
March 1, 2017 Doug Bidwell
It pays to be regular when it comes to systems management, and it is not a good thing to get too far behind. Take Windows Server as an example. With tens of millions of customers and plenty of bugs and security patches for this target-rich environment, Microsoft has to do everything in its power to try to keep the Windows installed base – both servers and PCs – patched and secured.
Windows Update can be used to automatically apply patches as they come out in the wake of Patch Tuesday once a month, or customers can set up a dedicated machine to run Windows Server Update Services, which downloads the Windows patches to a central server within your datacenter and then allows system admins to review the patches and then push them out to the PCs and servers on the corporate network.
IBM has not done anything like this for PTFs – there is no automatic update or SUS server. But with IBM i 7.2 and 7.3, Big Blue has added a policy-driven automatic patching mechanism that is similar to Windows Update. It is probably wise to set it up and put it on hold, and then after reviewing the patches, apply them manually to IBM i 7.2 or 7.3. The automatic function is a good thing, but you have to know what the heck you are doing automatically.
Our recommendation is a little more subtle. We think you should create your own Patch Wednesday. Use the IBM i PTF Guide and determine what is best for your organization and follow a regular cadence of applying patches and keeping current. If you don’t want to do this yourself, then DLB Associates is happy to provide such a managed PTF service for you.
Now, without further ado, here is the archive of the IBM i PTF Guide: