IBM i Maintenance Services After Power9 End of Support: Running Is Not Supported

A regional credit union relies on an IBM Power9 S924 running IBM i 7.4 for its core banking integrations and member services.

As the server approached the end of IBM's standard service period, the IT manager signed a lower-cost contract with a third-party hardware maintenance provider. The provider keeps spare parts locally, responds quickly to service requests, and repairs the server when problems arise.

During the annual security review, however, the auditor asks when the last firmware update was installed and whether the operating system is still covered by standard support.

The IT manager confirms that no firmware update has been applied since January and that the operating system has been outside standard support since September.

The server is running, and its hardware is being maintained. But that does not mean it receives the software updates and security fixes expected of a fully supported system.

This distinction matters when planning IBM i maintenance after Power9 end of support. Third-party maintenance can extend hardware life and reduce costs, but it does not replace firmware updates, operating system fixes, or application support.

A sound IBM i maintenance services plan must address all three areas rather than treating a hardware maintenance contract as complete support.

What Power9 End of Standard Service Means

IBM's Power9 maintenance notice, issued in September 2024, set January 31, 2026, as the End of Standard Service date for several Power9 models: the S914, S922, S924, H922, H924, and L922.

After this date, IBM no longer provides standard preventive service or develops new machine code updates, patches, and fixes for the affected systems. This includes security fixes.

Organizations that need additional time can consider IBM's Hardware Support Extension. According to the notice, this offering includes IBM-certified parts, the latest IBM-certified firmware and machine code, information about known defects, and notifications about product issues and security exposures.

The choice between extended IBM support and third-party maintenance depends on an organization's requirements. However, the two options do not provide the same level of coverage.

What Third-Party Maintenance Can and Cannot Do

Third-party maintenance providers specialize in keeping older hardware running. They typically offer:

1. Parts replacement from their own inventories.
2. On-site engineers for hardware repairs.
3. Faster response times than some manufacturer contracts.
4. Lower cost than extended manufacturer support.

What they cannot provide is new IBM firmware or machine code. Only IBM develops those updates. If a new firmware vulnerability is found after end of service, a third-party provider has no patch to apply. The same applies to operating system fixes, which come from IBM through PTFs.

For many organizations, third-party maintenance is a reasonable bridge. The risk arises when it is treated as a complete support strategy.

The OS Clock Runs Separately

Hardware and operating system support follow separate timelines. Organizations must track both to understand their actual support coverage.

IBM announced that IBM i 7.4 would move from standard support to Service Extension on September 30, 2026, with the extension available until September 30, 2029. Service Extension is a paid offering with a narrower scope than standard support.

Many Power9 systems run IBM i 7.4. These organizations therefore face two separate lifecycle concerns: the hardware has passed its standard service date, and the operating system has moved to extended support.

A hardware maintenance agreement does not resolve either software concern. Organizations must decide how to manage the operating system's support status and what to do about firmware updates that are no longer available through standard service.

Three Layers of IBM i Maintenance

A practical IBM i maintenance strategy separates hardware upkeep, firmware and operating system support, and application maintenance. Each layer has different requirements and needs its own plan.

Layer One: Hardware Upkeep

Hardware maintenance covers the physical server, including component replacement, repairs, diagnostics, and environmental monitoring.

Organizations can choose IBM Hardware Support Extension, third-party maintenance, or a move to newer hardware or cloud infrastructure. The right option depends on the system's importance, the cost of continued maintenance, and the time available before an upgrade.

Layer Two: Firmware and Operating System Support

This layer covers firmware, the operating system, and licensed programs, including the availability and application of security fixes.

Options include IBM standard support for eligible releases, Service Extension for older releases, or an upgrade to IBM i 7.5 or 7.6 on supported hardware.

The important point is to confirm exactly which updates and fixes are available under the chosen support arrangement. Hardware repairs alone do not keep the software current.

Layer Three: Application Support

Business applications running on IBM i also need ongoing maintenance. This includes fixing defects, implementing changes, managing integrations, monitoring performance, and documenting how the applications work.

Organizations can handle these responsibilities internally, work with an application support partner, or combine both approaches.

Each layer should have a designated owner, clearly defined contract terms, and a regular review schedule. This makes gaps in support easier to identify before they cause operational problems.

Why "Maintained" Is Not the Same as "Safe"

Treating hardware maintenance as a substitute for complete system support can expose an organization to several risks:

1. Firmware vulnerabilities: Security weaknesses may remain unpatched when no new firmware fix is available.
2. Operating system vulnerabilities: Systems outside standard support may miss fixes unless the required extension or other eligible support arrangement is in place.
3. Audit findings: Organizations in regulated industries may face compliance issues if their systems do not meet applicable support requirements.
4. Application compatibility problems: Software vendors may stop certifying or supporting older operating system releases.
5. Extended outages: Resolving certain failures may take longer when the required fixes or replacement options are no longer available.

Security deserves particular attention. IBM i has a strong security reputation, but organizations still need to apply available fixes and maintain appropriate access controls. When firmware and operating system updates stop, known and newly discovered vulnerabilities can leave systems increasingly exposed.

A maintenance contract should therefore be assessed by what it actually covers, not simply by whether the provider can keep the server running.

Read: Top 10 AI/ML Development Companies to Watch in 2026

When Third-Party Maintenance Makes Sense

Third-party hardware maintenance can be a practical choice under specific conditions.

1. An upgrade is already planned: The organization needs to keep the existing server operational until replacement hardware is ready.
2. The system is not business-critical: A development environment or archive partition may have different availability requirements from a production system.
3. Additional security controls are in place: Network isolation, restricted access, and other safeguards can reduce exposure during the transition.
4. Operating system support is managed separately: The organization has a defined arrangement for OS support and understands which fixes remain available.

In each case, the decision should be documented. The organization should record the risks, the controls in place, the person responsible for accepting those risks, and the date by which the temporary arrangement will end.

Compensating Controls for the Bridge Period

Organizations that need to continue running Power9 hardware or IBM i 7.4 for a limited period can use compensating controls to reduce exposure while preparing for an upgrade. These measures do not replace security fixes, but they can limit the ways an attacker might reach vulnerable systems.

Network segmentation can restrict which users and systems can connect to an IBM i partition. Security teams should review user profiles with special authorities and remove unnecessary access. Unused TCP/IP services, including FTP and Telnet, should be disabled where they are not required.

Exit programs can restrict and log access through database and file-serving interfaces. Audit journaling should also be enabled, with security-relevant events reviewed regularly.

Access to the Hardware Management Console and service processor needs similar attention because management interfaces can expose systems to firmware-level risks.

Organizations should document these measures and explain why they are necessary. Auditors and regulators may ask which risks were accepted, who approved the decision, how the risks are being controlled, and when the transition will end.

A written risk acceptance record, approved by business and IT leaders and linked to the upgrade schedule, provides a clear account of the decision.

Testing Recovery on Aging Hardware

Recovery planning becomes more important as hardware ages. Replacement parts may take longer to obtain, and certain failures may require an entire component to be replaced.

Organizations should verify that backups are complete and can be restored successfully. They should also review high availability and disaster recovery targets to ensure they still meet business requirements.

Recovery to alternate hardware or cloud capacity should be tested before an outage occurs. A recent, successful restore test helps confirm that the organization can recover its systems if the aging server fails during the transition period.

Choosing an IBM i Maintenance Company

When evaluating an IBM i maintenance company, organizations can ask:

1. Which layers does the provider cover: hardware, firmware and OS, applications, or all three?
2. How will firmware and OS fixes be obtained and applied?
3. What is the plan if a security vulnerability affects firmware after end of service?
4. How does the provider support upgrades to current releases and hardware?
5. What reporting is provided on hardware status, PTF levels, and support coverage?
6. How is application knowledge documented and shared?

Providers of IBM iSeries support and IBM AS400 support that answer clearly across all three layers help organizations avoid gaps.

Building an IBM i Maintenance Services Plan

A practical plan for IBM i maintenance services after Power9 end of support includes:

1. Inventory: hardware models, serial numbers, support status, OS releases, licensed programs, and applications.
2. Risk assessment: which systems are critical, which face regulatory requirements, and what exposure exists.
3. Hardware decision: IBM extension, third-party maintenance, new Power10 or Power11 hardware, or cloud.
4. OS decision: upgrade to IBM i 7.5 or 7.6, or purchase Service Extension for a defined period.
5. Application support model: internal, partner, or combined, with documentation requirements.
6. Security controls: compensating controls for any period on unsupported firmware or releases.
7. Timeline: dates for upgrades, contract changes, and reviews.

The plan should be reviewed at least annually and whenever IBM announces new lifecycle dates.

Cloud and Newer Hardware as Alternatives

Moving to newer hardware or cloud infrastructure can address some of the limitations associated with aging Power9 systems. Power10 and Power11 systems receive current firmware support, and IBM i 7.6 runs on these platforms.

Organizations can also consider IBM Power Virtual Server or managed Power cloud providers. These options reduce the need to own and maintain physical hardware, although the scope of hardware, OS, and application responsibilities depends on the chosen service arrangement.

Migration requires planning, testing, and resources. However, organizations should compare the total cost over several years rather than looking only at the immediate expense of new hardware.

The calculation should include extended support, third-party maintenance, migration work, ongoing operations, and the risks associated with aging infrastructure.

Application Support Remains Essential

Upgrading hardware and software does not remove the need for application maintenance. Many IBM i applications have been in use for decades, contain extensive customizations, and depend on knowledge held by a small number of employees.

IBM System i support for these applications should cover defect resolution, change requests, performance monitoring, integration management, and technical documentation.

The loss of experienced IBM i professionals can make these systems difficult to maintain, particularly when application logic and dependencies have not been documented.

Capturing that knowledge and sharing it with the people responsible for future changes is as important as maintaining hardware availability.

Final Thoughts

IBM i maintenance services after Power9 end of support must account for more than hardware availability. A server can continue running under a third-party maintenance contract while its firmware and operating system face separate support limitations.

Organizations should manage hardware upkeep, firmware and OS currency, and application support as distinct responsibilities. Each needs a clear owner, an appropriate support arrangement, and a timeline for review or upgrade.

Before the next security audit, IT teams should confirm when the last firmware update and PTFs were applied, which support options remain available, and how future vulnerabilities will be addressed.

These checks help organizations make informed decisions about extending the life of existing systems without confusing operational continuity with complete support.