IBM i V7.4 will reach its end of software support at the end of September. If you’re still running V7.4 without a transition plan, that deadline is not an abstract vendor milestone. It is the date IBM stops issuing PTFs for your platform. The security exposure that follows is measurable, documented, and growing every month you wait.

PTFs Are More Important Than Most IT Teams Realize

Program temporary fix (PTF) is IBM’s term for a software patch. When leading software vendors issue a security update, your team installs it. Similarly, your IBM i system administrator applies PTFs when they become available. The mechanism differs, but the purpose is the same. These updates close known software vulnerabilities to protect your business operations.

IBM stops producing these crucial fixes when platform versions retire. Your internal business applications will continue to run without immediate, noticeable disruption. However, newly discovered vulnerabilities will remain unaddressed on your legacy platform. Moving to a supported version restores your security posture.

IBM has consistently issued security announcements since the Log4j disclosure. Their updates arrive at a pace approaching one per month. This update schedule is definitely not an anomaly for the platform. It is the normal cadence of the platform security maintenance cycle.

Global security researchers continue to identify bugs within the older codebase. IBM actively patches these identified issues under its current support agreements. Upgrading your system guarantees that you continue to receive these essential vendor security enhancements.

The NIST National Vulnerability Database publicly records these security disclosures. Official external auditors frequently reference this database during routine compliance checks.

The True Cost of Staying on an Unsupported OS Version

Organizations remaining on V7.4 after September will not be immediately compromised. However, their security exposure will increase after that date. That risk also increases over time. Each passing month typically brings another software security announcement. Missing these updates widens the gap between your environment and those that are secure.

IBM explicitly states that extended software support operates on a best-efforts basis. Many engineers familiar with earlier operating system versions have already retired. Requesting a security fix for a retired version is never guaranteed. In some unique situations, a specific legacy repair might not exist.

V7.3 and older platform versions are already past their support windows. Version 7.4 officially joins that retired group at the end of September. V7.5 and V7.6 remain on active support and continue receiving necessary PTFs. The path forward is clear and completely resolves any accumulating software debt. We covered this in a post about how falling behind on PTFs creates a security liability.

Navigating the IBM i Version Upgrade Process

The V7.4 upgrade process is smoother than most internal teams expect. It’s rarely complexity that prevents organizations from initiating their system upgrades. More often than not, it is a lack of familiarity with what the process actually requires.

The upgrade path to V7.5 or V7.6 is well-defined. Many modern clients experience faster transitions at much lower costs than expected. The organizations that move quickly are the ones that engage experienced IBM i professionals early in the process. They also confirm their ISV licensing situation and let a team with documented upgrade history run the overnight cutover.

Bob Losey has supported IBM i environments since the AS/400 debuted in 1988. He has successfully guided hundreds of clients through complex software transitions. Many of these transitions initially looked impossible to the internal technology teams.

“We just pushed their applications, custom written in RPG at V5R3, right across into a logical partition at V7.5. Normally, you’d go from V5 to V6 to V7.5, and that would cost about $15,000. This approach, we just pushed them right across. The entire cost of that consulting was about $2,000 to $3,000, not $15,000. We got them cut across in 30 days.” – Bob Losey, Founder and President, Source Data Products

That client example involves an environment significantly older than V7.4. Deferring your upgrade due to budget concerns often ignores efficient solutions. The actual transition experience is typically much smoother than internal teams anticipate. Source Data’s 8-step overnight upgrade process eliminates migration guesswork and compresses the project timeline.

Teams approaching the V7.4 deadline should secure a clear picture of the transition soon. Reach out to my team at Source Data to begin your assessment.

Important ISV Software Considerations to Address Before Finalizing Your Upgrade Plan

One question determines everything before you set an official upgrade timeline. Does your environment utilize independent software vendor applications?

ISV software carries a proprietary license key tied to your environment. Moving to new servers often requires a transfer fee from software providers. These transfer fees vary widely across different vendor ecosystems. Some vendors handle this cleanly while others introduce highly restrictive administrative processes.

Transfer fees sometimes arrive as massive budgetary surprises during the planning phase. These quotes often bear little relationship to the actual technical transition work. Experienced consultants can often negotiate these initial quotes down to reasonable numbers.

If the ISV allows migration and quotes a reasonable fee, the upgrade path is straightforward. Restrictive vendor terms require early identification so you have adequate negotiation time.

The September Deadline’s Impact on Compliance and Cyber Insurance

The end-of-support date is a key point for compliance and cyber insurance qualification. Modern cyber insurers reward organizations that maintain fully supported, current environments. That significantly affects your ongoing policy underwriting and annual insurance renewals.

External auditors expect organizations to maintain active vendor support for production systems. They frequently reference robust NIST SP 800-53 security controls during their rigorous examinations. Operating unpatched legacy environments leads to audit findings that require immediate remediation.

Organizations managing this transition smoothly always begin their assessments early. They confirm ISV fees and review current PTF levels to identify paths. You should always engage a professional team with documented experience in platform upgrades.

FAQs About IBM i End of Support Deadlines

When does IBM i V7.4 reach the end of support?

The V7.4 operating system loses official vendor software support at the end of September. That means IBM stops issuing critical security patches and OS-level fixes after this date. Organizations running this version must navigate any newly discovered vulnerabilities without vendor assistance.

What is a PTF, and why does it matter for IBM i end of support?

Program temporary fix is IBM’s term for a security patch. They deliver performance enhancements and essential software updates. Without these updates, newly discovered platform vulnerabilities remain unaddressed. Missing active support windows creates a measurable gap visible to external compliance auditors.

Can I stay on V7.4 after the end of September?

You can continue running older versions without receiving ongoing security patches. Future vulnerabilities will remain unresolved without an official IBM-provided repair strategy. External auditors and cyber insurers carefully evaluate these unsupported systems during standard renewals.

How long does an IBM i V7.5 upgrade typically take?

A properly prepared upgrade can be completed within a 30-day operational window. The final system cutover routinely executes as a highly efficient overnight process. Administrative preparation determines the overall timeline far more than raw technical complexity. Resolving software licensing and confirming updates before your cutover date prevents delays.

Does upgrading IBM i to V7.5 require new hardware?

Purchasing new server hardware is not a strict technical requirement. Many modern upgrades run perfectly on your existing, fully supported POWER hardware systems. Cloud-hosted logical partitions successfully deliver supported environments while eliminating traditional hardware refreshes. Moving to Cloud400 hosting during an OS upgrade often costs less than purchasing hardware.

What should I confirm before starting my V7.4 upgrade?

Confirming two items early ensures a smooth transition timeline. First, confirm the transfer fees from any ISVs. Second, verify your current PTF level before finalizing any official cutover dates. Gathering this information early helps you build an accurate transition budget.

Which versions of IBM i are still on active support?

V7.5 and V7.6 are currently on active software support and receive ongoing PTFs. Version 7.3 and all earlier legacy iterations are past their support windows. Version 7.4 completes its active lifecycle and officially retires at the end of September. Upgrading guarantees your business retains access to necessary vendor-provided security patches.

How do ISV transfer fees affect an IBM i V7.4 upgrade plan?

Independent software applications carry proprietary license keys tied to the systems they run on. Many ISVs charge fees to move the software to a new server. These fees range from nominal to substantial. Securing precise figures early prevents massive budget surprises during the migration process. Early discovery also provides time to negotiate initial vendor quotes. We explore this further in a post about software transfer fees.

The Upgrade Window for V7.4 Is Closing

Running IBM i V7.4 past the end of support introduces risk that grows with every security disclosure. Organizations that act now maintain control over their upgrade process and security posture. Those that delay accept growing exposure with no remediation path from IBM.

Source Data works with clients to plan and execute efficient IBM i upgrades. Our process removes uncertainty and compresses timelines without disrupting operations. Contact our team to evaluate your environment and take the next step forward.

Bob Losey is the founder and president of Source Data Products. He has held Premier IBM Business Partner status continuously since 1992 and served as President of the Association of Service and Computer Dealers International (ASCDI), bringing four decades of IBM midrange field experience to every client engagement.