IBM i Technology Updates

IBM i 7.6 TR2 and IBM i 7.5 TR8: What’s New

A practical guide to the July 2026 IBM i updates, including new SQL services, Db2 for i changes, RPG enhancements, security, ACS, Navigator, modernization, BRMS, high availability, and hardware support.

SA

Saurabh Arora

IBM i Solution Architect | Technical Lead | Modernization & Integration Specialist

Published July 26, 202617 min read
IBM iIBM i 7.6IBM i 7.5Technology RefreshDb2 for iRPGSQL ServicesACSNavigator for iModernization

IBM i 7.6 Technology Refresh 2 and IBM i 7.5 Technology Refresh 8 deliver far more than a short list of operating-system fixes. The July 2026 update wave adds new Db2 for i functions, SQL services, RPG language features, security capabilities, management interfaces, modernization tooling, high-availability improvements, and hardware support.

This guide organizes the update into practical areas and links to detailed Era of i lessons where we have already built working examples.

The goal is not merely to repeat IBM’s announcement list.

It is to answer:

What changed?
Which release supports it?
Which PTF level is required?
Why does it matter?
Where can I see a practical example?

At a glance

The key Db2 for i Group PTF levels are:

IBM i 7.6    SF99960 Level 3
IBM i 7.5    SF99950 Level 12

Many of the SQL and application-development enhancements are available on both releases.

A smaller group of security and Service Tools Server capabilities is available only on IBM i 7.6.

A Technology Refresh is not a new IBM i release.

It delivers new function and hardware support through PTF groups for an existing release. Always review the complete prerequisite, cumulative, HIPER, Db2, HTTP, Java, and product-specific PTF requirements before implementation.

Check the installed Db2 Group PTF level

Before testing the new SQL services, confirm the installed group:

SELECT
    PTF_GROUP_NAME,
    PTF_GROUP_LEVEL,
    PTF_GROUP_STATUS
FROM QSYS2.GROUP_PTF_INFO
WHERE PTF_GROUP_NAME IN
      (
          'SF99960',
          'SF99950',
          'SF99704',
          'SF99703'
      )
ORDER BY
    PTF_GROUP_NAME,
    PTF_GROUP_LEVEL DESC;

For the July 2026 enhancements covered here, the important target levels are:

SF99960 Level 3 on IBM i 7.6
SF99950 Level 12 on IBM i 7.5

A service can still depend on another PTF group, licensed program, Java level, authority setting, or supporting component.

Db2 for i functional enhancements

SQL Error Logging Facility

QSYS2.SQL_ERROR_LOG makes selected SQL failures queryable through the SQL Error Logging Facility, commonly called SELF.

It can preserve information such as:

This is especially useful for intermittent production failures that are difficult to reproduce after the original job ends.

Read the practical guide: Find and Analyze IBM i SQL Errors with SQL_ERROR_LOG

Trigger pseudo-columns

Db2 for i now provides additional trigger context through pseudo-columns.

These values can help trigger logic identify details about the operation being processed without duplicating context-management logic in every application.

Potential uses include:

This deserves a dedicated future SQL Way entry because trigger behavior must be tested carefully for inserts, updates, deletes, multi-row statements, and replication scenarios.

Convert internal system timestamps

Two functions bridge normal SQL timestamps with the eight-byte internal timestamp format used by selected IBM i interfaces:

FROM_SYSTEM_TIMESTAMP
TO_SYSTEM_TIMESTAMP

Use FROM_SYSTEM_TIMESTAMP when an API, table, or system interface returns the internal eight-byte value:

Convert an Internal IBM i System Timestamp to an SQL Timestamp

Use TO_SYSTEM_TIMESTAMP when an interface requires that internal representation:

Convert an SQL Timestamp to an Internal IBM i System Timestamp

URL encoding

URL_ENCODE safely represents query-string values containing spaces, ampersands, plus signs, slashes, percent signs, or non-ASCII characters.

The important rule is:

Encode each parameter value—not the complete URL.

URL-Encode API Parameters with Db2 for i

Database-engineer control for SQE debug retention

SYSIBMADM.QIBM_SQEDEBUG_BY_DAYS provides control over how long SQL Query Engine debug data is retained.

This is primarily a database-engineering and support capability.

A future Era of i guide will cover:

New Db2 security control on IBM i 7.6

IBM i 7.6 adds:

QIBM_IOSYSCFG_DDM

as a function-usage control related to DDM configuration authority.

This is part of IBM’s broader effort to replace broad special authority with more targeted function-usage controls.

It is an IBM i 7.6-specific security enhancement.

New IBM i SQL services

IBM i 7.6 TR2 introduces 17 new IBM i services.

Twelve of those are also delivered to IBM i 7.5 TR8.

Shared by IBM i 7.6 and 7.5

Create a data journal reader

QSYS2.CREATE_DATA_JOURNAL_READER

This service generates a table function tailored to one journaled database file.

Instead of returning only generic entry data, the generated reader can expose supported application fields as individual SQL columns.

Create a Data Journal Reader for an IBM i Table

Geographic mirroring information

QSYS2.GEOGRAPHIC_MIRRORING_INFO

The view exposes information such as:

Monitor IBM i Geographic Mirroring with SQL

Audit journal JD and RU services

The release adds:

SYSTOOLS.AUDIT_JOURNAL_JD
SYSTOOLS.AUDIT_JOURNAL_RU

These services make additional audit-journal entry types easier to query through SQL.

They will become separate security-focused Era of i lessons because audit entries require careful explanation of:

Validate a CL command without running it

SYSTOOLS.CHECK_COMMAND_SYNTAX

The function returns a Boolean result showing whether the CL command passes syntax checking.

It does not execute the command and does not prove that the caller is authorized to run it.

Validate an IBM i CL Command Without Running It

Query IBM security bulletins

SYSTOOLS.CVE_INFO

The table function retrieves current IBM security-bulletin information for an IBM i release.

It requires internet connectivity from the partition and should be treated as an input to vulnerability assessment—not proof that the local system is exploitable.

Query IBM i CVEs with SQL

Check Group PTF currency from a local feed

SYSTOOLS.GROUP_PTF_CURRENCY_LOCAL

This service compares installed Group PTF levels with an approved local copy of IBM’s PSP XML feed.

It is particularly useful for partitions that cannot connect directly to the internet.

Check IBM i Group PTF Currency with a Local XML Feed

Parse qualified job names

The new helpers are:

SYSTOOLS.JOB_NAME
SYSTOOLS.JOB_NUMBER
SYSTOOLS.JOB_USER
SYSTOOLS.JOB_NAME_DETAILS

They split a qualified IBM i job name:

job-number/job-user/job-name

into reusable SQL values.

Parse a Qualified IBM i Job Name with SQL

Find file overrides in the current job

SYSTOOLS.OVERRIDE_INFO_ALL

This view returns the file overrides active at the current call level of the current job.

It can help explain why a program opened the expected file name but accessed an unexpected object, member, output queue, or device.

Find All IBM i File Overrides in the Current Job

IBM i 7.6-only services

The following services require IBM i 7.6 at the applicable PTF level.

Service Tools Server configuration entries

IBM i 7.6 can store partition-specific Service Tools Server LAN configuration entries for recovery scenarios where a replicated or FlashCopy load-source image starts on different hardware.

The services are:

QSYS2.SERVICE_TOOLS_SERVER_CONFIGURATION_ENTRY_INFO
QSYS2.ADD_SERVICE_TOOLS_SERVER_CONFIGURATION_ENTRY
QSYS2.CHANGE_SERVICE_TOOLS_SERVER_CONFIGURATION_ENTRY
QSYS2.REMOVE_SERVICE_TOOLS_SERVER_CONFIGURATION_ENTRY

Era of i guides:

These are privileged recovery and service-network operations.

The add, change, and remove procedures should never be treated like ordinary application SQL.

External key manager information

QSYS2.EKM_INFO

This table function reads an External Key Manager description file and returns configuration details such as:

Inspect an IBM i External Key Manager Configuration with SQL

Enhanced IBM i services

The release also enhances existing services:

QSYS2.ASP_INFO
QSYS2.JOBLOG_INFO
QSYS2.QCMDEXC
QSYS2.SCHEDULED_JOB_INFO
QSYS2.SYSDISKSTAT
QSYS2.SYSTEM_STATUS
QSYS2.SYSTEM_STATUS_INFO
QSYS2.SYSTEM_STATUS_INFO_BASIC
SYSTOOLS.GENERATE_SPREADSHEET

Execute CL commands from SQL

The QSYS2.QCMDEXC scalar function adds a PRINT option:

NONE
ERROR
VERBOSE

This controls whether the CL command text is written to the job log.

The new capability improves diagnostics, but it also creates a security decision because commands can contain sensitive information.

Run IBM i CL Commands from SQL and Control Job-Log Output

Generate spreadsheet files

SYSTOOLS.GENERATE_SPREADSHEET can write database or query results to:

CSV
TXT
ODS
XLS
XLSX

Current enhancements support options such as:

Generate Excel, CSV, ODS, and Text Files from IBM i SQL

Existing operational SQL Way guides

The release-specific services build on a broader operational pattern: use SQL to make IBM i information sortable, filterable, repeatable, and automatable.

Two earlier guides in the series are:

These are not limited to TR2 or TR8, but they demonstrate the same philosophy:

SQL complements the native IBM i interface; it does not replace it.

RPG language enhancements

The July 2026 application-development update adds several meaningful RPG capabilities.

ASSERT-T and ASSERT-F

The new assertion operation codes provide a self-documenting way to express conditions that should be true or false.

IBM also provides assertion-processing modes, including approaches that can:

Generic message IDs with ON-EXCP

An ON-EXCP message ID can end with an asterisk:

monitor;

   ProcessOrder();

on-excp 'CPF*';

   // Handle messages beginning with CPF

endmon;

This can reduce repetitive exception blocks when an application intentionally handles a message family.

It should not be used as an excuse to swallow unrelated exceptions without logging or recovery logic.

LIKE(*EXT)

LIKE(*EXT) defines one RPG item using the attributes of a field in an external file:

dcl-s CustomerName
   like(*ext : 'CUSNAME' : 'CUSTOMER');

This can reduce duplicated field definitions and help keep application variables aligned with the database.

It defines an RPG item at compile time.

It does not read the field value at runtime.

%LOOKUPNE and %TLOOKUPNE

These built-in functions find the first array or table element that is not equal to the search argument.

They can simplify logic that previously required a loop or a combination of lookup and boundary handling.

Era of i is publishing detailed examples for these RPG enhancements in the Lessons section.

Security enhancements

Security is one of the most significant IBM i 7.6-specific areas in this update.

External Key Management and Bring Your Own Key

IBM i 7.6 adds native integration with IBM Key Protect for IBM Cloud.

IBM describes capabilities including:

This brings Bring Your Own Key concepts closer to native IBM i cryptographic services.

Save/Restore master-key protection

IBM i 7.6 can remove the Save/Restore key from the partition load source.

The key must then be provided during or after IPL through an approved mechanism.

IBM documents two approaches:

Platform KeyStore
Remote Key Agent

This can be combined with system ASP encryption to prevent the partition from fully IPLing until the required key is available.

That is a powerful security control, but it also raises the importance of:

Cluster support for MFA-enabled users

A new cluster version supports cluster operations for profiles using IBM i integrated multi-factor authentication.

This matters because security controls should not force high-availability teams to choose between modern authentication and supported cluster operation.

CVE visibility in Navigator

Navigator for i now exposes CVE information backed by:

SYSTOOLS.CVE_INFO

This makes IBM security bulletins more visible to administrators who do not regularly use Run SQL Scripts.

IBM Navigator for i — Q2 2026 update

IBM identifies the Q2 2026 Navigator enhancements with HTTP Group PTF updates released June 29, 2026.

Key areas include:

Framework and dashboard

Multi-system management

Navigator adds a CVE Information table that can show CVE counts by system and launch into system-specific detail.

Performance

Enhancements include:

Network and web administration

The update adds or improves:

Work management

Active Jobs adds more query-specific filtering with filters processed through SQL on the server.

This can improve responsiveness and make large job lists easier to narrow.

Security and cryptographic services

Navigator adds interfaces for:

IFS management

New actions include:

Copy
Move
Rename
Send

These changes make Navigator a much more complete browser-based administration interface.

IBM i Access Client Solutions

The current ACS base package is:

Version 1.1.9.13
Build date: May 2026

The current update stream includes both security fixes and functional improvements.

Run SQL Scripts

The TR landing pages highlight:

IFS

ACS adds an IFS Favorites menu for frequently used directories.

Visual Explain

Enhancements include:

SQL Performance Center

Index Advisor adds columns related to maintained temporary index information.

Keep ACS current.

ACS releases can contain security fixes as well as visible features. IBM’s current support pages identify 1.1.9.13 as the latest base package and provide platform PTFs and download options.

Application modernization updates

The modernization story is broader than one product.

Code for IBM i

Current enhancements include:

Db2 for i VS Code extension

The extension adds:

RPGLE and CL extensions

RPGLE enhancements include:

CL enhancements include:

IBM i Testing

The testing extension adds or improves:

IBM i FileSystem extension

A new extension provides QSYS object browsing and object-specific actions.

Examples include:

IBM Bob Premium Package for i

IBM Bob adds IBM i-focused AI personas and workflows for development and database work.

IBM describes capabilities such as:

This is a different direction from IBM Merlin.

IBM’s Merlin 2.0 offering reached end of marketing and service on October 7, 2025, and Merlin 1.0 had already reached end of service.

High availability and migration

IBM i Migrate While Active

IBM continues to enhance Migrate While Active so maintenance and upgrades can be prepared on a synchronized target while production applications remain active.

Current enhancements include:

The objective is a controlled role swap with a smaller outage window.

Geographic mirroring visibility

The new GEOGRAPHIC_MIRRORING_INFO view complements PowerHA tooling by making mirror status queryable and storable.

It should be used as operational visibility—not as a replacement for tested role-swap and recovery procedures.

Db2 Mirror context

The July I/O update includes dedicated RoCE support used by Db2 Mirror for i on selected new adapters.

That is different from a broad Db2 Mirror software feature release.

A separate Era of i article will review the current Db2 Mirror enhancement history and distinguish new hardware enablement from Db2 Mirror function changes.

Backup, recovery, and BRMS

BRMS GUI version 2026.2.0 includes updates in several areas.

BRMS log

New filters can highlight:

Backup history

New views provide object-level and file-level detail.

When object detail exists in the save, the interface can support:

Backup lists

The GUI adds capabilities to:

Administration

A new *SYSOPR role-based usage type provides operational access while restricting some change, copy, and remove actions unless the user owns the BRMS item.

Hardware, I/O, and system function

Both TR packages include support for the entry-level:

IBM Power S1112

The update also adds support for new storage and networking features, including:

Hardware support always requires checking the complete IBM prerequisite information, firmware, hypervisor level, adapter mode, VIOS level, and PTF requirements.

Related platform updates that are not the same as TR2 or TR8

Not every current IBM i technology update is delivered as part of the Technology Refresh.

Integrated Web Services 3.0

IBM introduced IWS 3.0 in October 2025.

It is Jakarta EE based and is supported on IBM i 7.4, 7.5, and 7.6.

IWS 3.0 requires:

JDK 17, 64-bit

IBM continues to support IWS 2.6 as well.

IWS is enhanced through the HTTP Server Group PTF stream, so teams should track that page separately from the Db2 and TR groups.

Open-source packages

IBM i open-source packages such as Git, Node.js, Python, OpenSSL, and other tools are commonly delivered and maintained through RPM repositories.

That delivery model is continuous and should not be described as a TR2 or TR8 feature unless IBM explicitly lists a package in the release material.

Merlin lifecycle

Merlin should not be described as a new 2026 modernization update.

IBM states:

Merlin 2.0 reached end of marketing and service on October 7, 2025.
Merlin 1.0 reached end of service earlier.

Teams planning modernization should evaluate currently supported options such as:

What should an IBM i team do first?

A practical adoption plan is:

1. Inventory the current levels

Review:

IBM i release
Technology Refresh group
Cumulative package
HIPER group
Db2 Group PTF
HTTP Server Group PTF
Java options
ACS desktop version
BRMS version
PowerHA and related product levels

2. Identify 7.6-only functions

Do not design a cross-release solution around:

External Key Management
Save/Restore master-key changes
Service Tools Server configuration-entry services
EKM_INFO
QIBM_IOSYSCFG_DDM

without confirming that the target partition is IBM i 7.6.

3. Start with read-only SQL services

Good first candidates include:

Read-only exploration builds understanding before write procedures are introduced.

4. Test language and compiler support

For RPG enhancements, confirm:

5. Treat write services as infrastructure changes

Examples include:

QCMDEXC
Service Tools Server add/change/remove procedures
master-key configuration
external key manager setup
Migrate While Active operations

These require authority review, change control, testing, and recovery planning.

6. Update operating procedures

New function has little value when it is not incorporated into:

Era of i: The SQL Way library

The July 2026 update gave us a strong reason to build a practical SQL knowledge library.

The first 20 entries now include:

  1. Find Active Jobs Consuming Temporary Storage
  2. Find Object Locks and the Jobs Holding Them
  3. Find and Analyze SQL Errors with SQL_ERROR_LOG
  4. Validate a CL Command Without Running It
  5. Query IBM i CVEs with SQL
  6. Check Group PTF Currency with a Local XML Feed
  7. URL-Encode API Parameters with Db2 for i
  8. Convert an Internal System Timestamp to SQL
  9. Convert an SQL Timestamp to an Internal System Timestamp
  10. Parse a Qualified IBM i Job Name
  11. Create a Data Journal Reader
  12. Monitor Geographic Mirroring
  13. Find File Overrides in the Current Job
  14. View Service Tools Server Configuration Entries
  15. Add a Service Tools Server Configuration Entry
  16. Change a Service Tools Server Configuration Entry
  17. Remove a Service Tools Server Configuration Entry
  18. Inspect an External Key Manager Configuration
  19. Run CL Commands from SQL with QCMDEXC
  20. Generate Excel, CSV, ODS, and Text Files from SQL

The series will continue with the remaining new and enhanced services, including audit-journal functions, trigger context, ASP information, job-log enhancements, scheduled-job information, system-status services, and database-engineering controls.

Final takeaway

IBM i 7.6 TR2 and IBM i 7.5 TR8 are not one-dimensional updates.

They move IBM i forward in several connected directions:

SQL as a system-management interface
RPG language productivity
native security and key management
browser-based administration
modern editor tooling
high-availability flexibility
automation and reporting
new Power hardware support

The real value will not come from installing the PTF groups alone.

It will come from identifying the capabilities that solve a real operational, development, security, or recovery problem—and then adopting them with the same discipline applied to any other production change.

Official IBM references

Comments

Share your thoughts, questions, or real-world IBM i experiences related to this article.