July 2026: PTF Group, HMC Software, Storage System, & Power Firmware Levels

Keeping an IBM i environment current is one of the simplest ways to protect uptime, but it is also one of the easiest things to fall behind on. New PTF groups, HMC service packs, storage code levels, and server firmware all move on their own schedules, and knowing what “current” actually means for your specific system takes more than a quick glance at a support page.

Below are the levels our team is installing for clients right now, along with the release schedules, support windows, and planning notes that matter most when you are deciding what to update and when. If you want a second set of eyes on where your environment stands today, reach out and we will walk through it with you.

Updated as of: July 27, 2026

IBM i PTF Groups

Below is a table of the current major group PTF levels for the last few IBM i releases. This is what we are installing for our clients. 

>
Group 7.6 7.5 7.4 7.3 7.2
Cumulative Package 26190 26197 26183 23257 21084
Technology Refresh 2 8 12 13 9
HIPER (High-Impact/PERvasive) 30 104 175 238 278
Security 21 64 96 136 163
Db2 3 12 33 33 27
Db2 Mirror 3 11 29
Java 6 21 33 42 38
Backup Recovery Solutions 4 20 50 72 87
HTTP Server 11 30 51 67 51
TCP/IP 6 13 17 14
High Availability 4 14 23 22 22
Power11 GA PTF (7.6)/Hardware (7.4-) 1 2 18 35
Performance Tools 3 8 18 19 15
Standard Support Ends 9/30/2026 9/30/2023 4/30/2021
Support Extension Ends 9/30/2029 9/30/2028 4/30/2026

The easiest way to check your levels is to use Navigator for i or run the CL command WRKPTFGRP. All applicable groups should have a status of Installed and should be current for your release and installed licensed programsThere are more groups than are listed here, but these are the most common. Our team can help you determine which PTF groups you should have on your machine based upon your installed licensed programs. 

HMC Software

HMC service packs are always cumulative and encompass all previous service packs and standalone fixes for the corresponding release level. Most standalone fixes also supersede previous fixes released since the last service pack, but this is not always the case. Fix Central and the release notes will indicate when a PTF supersedes a previous one. Superseded fixes do not need to be individually applied to bring an HMC current, but any fix released after the service pack and not marked as superseded will need to be applied for the console to be considered “current.” When upgrading to a new release, follow up with the latest service pack and any applicable standalone fixes. 

Recent HMC software builds include dedicated “Update” (for service packs within your current release) and “Upgrade” (for transitioning the console to a major new version milestone) wizards built directly into the GUI under HMC Management. This automated wizard can securely retrieve and apply packages directly from IBM’s remote servers in a few steps, leaving very little room for error. If you are working within a legacy or isolated environment that cannot retrieve fixes automatically over the network, be sure to thoroughly read the official release notes for your target HMC version, service pack, and individual PTFs to verify installation steps and prerequisite pathways before you begin. 

HMC Version Latest Service Pack Latest Fix (x86/ppc) End of Service Pack Support
V11R2 M1120
V11R1 M1112 MF71764/MF71765
V10R3 M1064 MF71762/MF71763 9/30/2026
V10R2 M1043 MF71723/MF71724 4/30/2025
V10R1 M1023 MF71705/MF71706 4/30/2024
V9R2 M953 MH01958/MH01959 4/30/2023
V9R1 M942 MH01898/MH01899 9/30/2021
V8R8.7.0 M3 MH01818/MH01819
MH01847/MH01848
8/31/2019

Important Deployment Notes:

  • General HMC-Power Support Pattern: Major HMC software versions beginning with v8 have been able to manage their corresponding Power architecture along with up to two generations prior. HMC releases prior to v8 followed a much different numbering scheme and release schedule that did not necessarily coincide with Power Systems architecture, so check the release notes for server support details on older HMC versions. 
    • HMC v11 can manage Power11, Power10, and POWER9 systems. 
    • HMC v10 can manage Power10, POWER9, and POWER8 systems. 
    • HMC v9 can manage POWER9, POWER8, and POWER7/7+ systems. 
    • HMC v8 can manage POWER8, POWER7/7+, and POWER6 systems. 
  • Physical Appliance Limitations: If you utilize a physical hardware HMC appliance, be aware that physical machine types impose strict code execution ceilings. Review the official IBM Supported HMC Hardware Matrix to verify your physical unit’s support limits before pushing a major update; attempting to force an unsupported version onto an incompatible appliance can leave your console unusable. 
  • Virtual Consoles (vHMC): Virtual HMC appliances can be updated to newer versions using standardized network installation images or the integrated GUI wizard. A virtual HMC appliance can generally support any major software release, provided that the underlying hypervisor processor architecture matches (x86 vs. Power hardware) and the logical partition (LPAR) or virtual machine (VM) has been allocated sufficient RAM, storage space, and vCPU resources as outlined in the target version’s deployment release notes. Regardless of technical capability, you must have entitlement to the HMC version you install. 

IBM Storage Virtualize Software (FlashSystem/Storwize)

These are the recommended PTF levels from IBM for the Storage Virtualize software. 

Long Term Support (LTS) Releases:
Release Minimum Recommended Latest
9.1.0 9.1.0.0 9.1.0.7 9.1.0.7
8.7.0 8.7.0.6 8.7.0.13 8.7.0.13
8.6.0 8.6.0.0 8.6.0.10 8.6.0.11
8.5.0 8.5.0.5 8.5.0.17 8.5.0.18
8.4.0 (EoS) 8.4.0.6 8.4.0.19 8.4.0.20

The minimum version is a stable level at or above which a system can normally remain unless it needs a particular fix or feature. The recommended version is a stable version IBM currently recommends which may contain important or critical fixes. 

Non-Long Term Support (Non-LTS) Releases 
Release Latest PTF
9.1.1 / 9.1.2 / 9.1.3 9.1.3.0 [Jul 2026]
8.7.1 / 8.7.2 / 8.7.3 Superseded by 9.1.0 (LTS)
8.6.1 / 8.6.2 / 8.6.3 Superseded by 8.7.0 (LTS)
8.5.1 / 8.5.2 / 8.5.3 / 8.5.4 Superseded by 8.6.0 (LTS)
8.4.1 / 8.4.2 Superseded by 8.5.0 (LTS)

Non-LTS releases are only recommended if new features are required. 

Navigating IBM Storage Virtualize Code Releases :

Like HMC software updates, IBM Storage Virtualize code releases are cumulative. Storage code deployment also relies heavily on an automated internal safety process. Each update requires the Software Update Test Utility, which checks the system configuration and current code level for known conditions that could interfere with the update. The utility runs as part of the update process and reports warnings or errors that must be reviewed before proceeding. Administrators should also manually review the system event log, applicable flash alerts, release notes, and host interoperability requirements before beginning an update. 

When looking at the storage lifecycle list, there are three architectural concepts you must grasp to maintain absolute uptime: 

  • Long-Term Support (LTS) vs. Non-LTS Releases: Beginning with the 8.4 and 8.5 code streams, IBM split its storage software roadmap into two distinct categories: 
    • LTS Releases (e.g., v8.5.0.x or v8.7.0.x): These are long-term maintenance baselines designed for standard enterprise data centers. They focus strictly on stability, bug fixes, and security patches over a prolonged lifecycle without introducing disruptive new features. 
    • Non-LTS / Innovation Releases (e.g., v8.6.1.x or v8.6.2.x): These are shorter-lived feature releases meant for environments requiring cutting-edge functionalities (such as early access to advanced cyber-vault integrations or flash grid enhancements). They go out of support much faster, forcing rapid, consecutive upgrade cycles. 
  • The Interoperability and Cross-Reference Trap: Unlike an HMC—which can lazily look backward two generations—Storage Virtualize upgrade paths are explicitly defined by IBM. Some source and target combinations permit a direct upgrade, while others require an intermediate LTS or bridge level. 
  • The Host Attachment Protocol Baseline: Upgrading storage firmware changes how the target ports interact with your SAN switches and host adapters. Always ensure your host multipathing drivers (such as IBM i native multi-pathing or AIX MPIO) and Fibre Channel adapter microcodes are verified against the IBM System Storage Interoperation Center (SSIC) before initiating a cluster upgrade. 

IBM’s Concurrent Compatibility and Code Cross Reference for IBM Storage Virtualize document contains detailed explanations of these concepts and breaks all versions down by release dependency. This page also links to the hardware interoperability matrices for each line of storage appliance, which you can use to verify your hardware’s compatibility with a particular software release. 

Power Server Firmware (FSP/eBMC)

Below are the latest server firmware levels available for each machine type and model, along with IBM i PTFs for systems with OS-managed firmware. 

Processor Type-Model Latest Firmware IBM i OS-Managed PTF Hardware End of Service
Power11 9242-21B OB1120_183_183 MH12574
9242-21T
9824-22A
9824-42A
9856-22H
9856-42H
9043-MRU OF1120_183_183 N/A
9080-HEU OK1120_159_159 N/A
Power10 9105-22A ML1060_185_053 MH11775
9105-42A
9105-22B
9105-41B
9786-22H
9786-42H
9028-21B
9043-MRX MM1060_185_053 N/A
9080-HEX MH1060_180_048 N/A
POWER9 9008-22L VL950_222_045 MH11774 1/31/2026
9009-22A1/31/2026
9009-41A1/31/2026
9009-42A1/31/2026
9223-22H1/31/2026
9223-42H1/31/2026
9009-22G
9009-41G
9009-42G
5105-22E
9223-22S
9223-42S
9040-MR9 VM950_222_045 N/A
9080-M9S VH950_222_045 N/A 12/31/2027
Power8 8408-E8E SV860_246_165 MH01960 10/31/2023
8408-44E10/31/2024
8284-21A3/31/2024
8284-22A3/31/2024
8286-41A5/31/2024
8286-42A3/31/2024
9119-MHE SC860_246_165 N/A 10/31/2024
9119-MME SC860_246_165 N/A 10/31/2024

Firmware Upgrade Planning Notes:

  • OS-managed firmware updates are always disruptive. After the firmware PTF is loaded and applied, a server IPL is required to activate the new firmware level. Select restart type *FULL on the PWRDWNSYS prompt. 
  • For HMC-managed firmware, updates may be concurrent, meaning they are performed while the system is running, or disruptive, meaning all partitions must be deactivated. The levels shown in the table use the format xxAAAA_BBB_CCC, where AAAA is the firmware release, BBB is the service-pack level, and CCC is the last disruptive service-pack level. 
    • An update within the same firmware release can generally be concurrent when the currently installed service-pack level is equal to or greater than the target level’s CCC value. 
    • An update from an installed service-pack level lower than the target level’s CCC value is disruptive. 
    • A target level in which BBB and CCC are equal is disruptive. 
    • A change to a different firmware release is always disruptive. 
  • Some service packs contain deferred or partition-deferred fixes. Such a service pack may be installed concurrently, but those particular fixes will not become active until the next server IPL or partition reactivation. Consult the firmware readme for details. 
  • POWER8 and newer systems have an Update Access Key (UAK), which is checked when firmware is installed. New systems are shipped with a UAK expiration date aligned with their warranty. The UAK can be renewed through IBM’s Entitled Systems Support website while the machine has an active warranty or IBM hardware maintenance agreement. Firmware released while the UAK was valid can still be installed after the key expires, but firmware with a release date later than the UAK expiration date will be rejected. 

Questions About Your Environment?

If you’d like help checking your levels or planning an update, send us what you’ve got and we’ll take a look.

Discover more from Relion Solutions

Subscribe now to keep reading and get access to the full archive.

Continue reading