IBM i Updates
IBM i 7.6 TR3 and 7.5 TR9: What’s New for Developers and Administrators
A practical first look at IBM’s autumn 2026 updates: simpler RPG arrays, program context, CVE remediation visibility, SQL diagnostics, and operational changes.
An array declaration that carries its own values. A way to ask RPG about the running program. SQL that connects CVEs with remediation status. IBM’s latest Technology Refresh announcements contain several changes worth turning into small, practical improvements.
IBM lists IBM i 7.6 TR3 and IBM i 7.5 TR9 in its October 2026 announcements. These updates follow the releases covered in the 7.6 TR2 and 7.5 TR8 overview.
Announcement preview — checked October 28, 2026
The associated Db2 PTF groups are planned for November 20, 2026. The examples in this new series have not yet been compiled or run on IBM i. Component availability and prerequisites must be checked individually.
What should you try first?
Start with a small change: simplify an array declaration, inspect one partition’s CVE remediation information, or review a diagnostic improvement relevant to an existing support problem. Each gives a team something concrete to evaluate before planning broader adoption.
| Your work | Start here | Suggested evaluation |
|---|---|---|
| RPG development | INZ(*LIST) and DIM(*INZ) |
Replace a small, fixed list of assignments in a sandbox program. |
| Application support | %INFO |
Design a consistent diagnostic message containing execution context. |
| Security maintenance | CVE_CURRENCY |
Compare the report with one documented maintenance case. |
| SQL troubleshooting | SELF exclusions | Identify recurring expected errors that obscure useful findings. |
| Operations | Authentication and certificate changes | Review the affected clients and automation before maintenance. |
RPG: start with the declarations
IBM lists array initialization from a value list, automatic sizing from the initializer, and initialization from an enumeration for both releases. For example:
dcl-s statuses char(1) dim(*inz)
inz(*list : 'N' : 'P' : 'S');
This is a useful code-review exercise. The reviewer can see the intended set of statuses beside the declaration, then inspect how the rest of the program uses it. Begin with a small internal list; do not change an externally agreed parameter layout just to shorten a declaration.
For detailed explanations, examples, and downloadable source, see:
The announcements also introduce %INFO for program and job context, broaden string values accepted by OPTIONS(*STRING), and add ALWUPD control for programs created through CRTBNDRPG. IBM’s RPG enhancement list.
For application logging, %INFO provides execution context that can make diagnostic messages more useful. When retrieving job settings, distinguish the current job values from those captured during module initialization. For deployment workflows, review how ALWUPD affects the ability to update a program with UPDPGM.
Security reporting: connect CVEs to remediation
The CVE_INFO guide explains how to retrieve published vulnerability information. IBM describes the new SYSTOOLS.CVE_CURRENCY view as connecting CVEs with their remediating PTFs and indicating whether relevant fixes or group levels are applied on the system being queried. IBM CVE_CURRENCY.
The practical question becomes: what does the maintenance owner need to investigate on this partition? Start with one report and one bulletin. Compare the evidence before building a dashboard or assigning a compliance label.
Read the first CVE_CURRENCY walkthrough.
There is another useful maintenance addition: DEFECTIVE_PTF_CURRENCY_LOCAL compares installed fixes with a locally downloaded IBM feed and reports defective PTFs lacking the corrective fix. It complements the maintenance checks described in the local Group PTF currency guide. IBM defective PTF currency service.
SQL diagnostics and administration
Both enhancement pages list SELF exclusion support and HTTP logging and decompression options. The 7.6 page additionally lists new access-path identifiers in SYSINDEXSTAT and disk-path timeout services. These are selected differences, not a complete compatibility matrix. IBM 7.6 details, IBM 7.5 details.
When evaluating SELF exclusions, test both an expected SQL error and an unexpected one. Confirm that the exclusion removes the intended noise while retaining failures that need investigation. For background on capturing and reviewing those failures, see diagnosing SQL failures after the job ends.
To evaluate the HTTP changes, use a controlled endpoint that returns a known compressed response. Check the documented options for the installed PTF level, then compare the response and diagnostic output.
For a straightforward configuration check, QSYS2.SMTP_ATTRIBUTES exposes the settings configured through CHGSMTPA. This makes SMTP configuration available for review through SQL. IBM SMTP_ATTRIBUTES.
Operational changes to review before maintenance
The release pages also describe telnet printer-session authentication, DCM API enhancements, Navigator changes, and updates to migration, mirroring, and backup tooling. Successful-sign-on auditing and the new CHGPRF authentication-method parameter are listed on the 7.6 page. 7.6 operational changes, 7.5 operational changes.
Before maintenance, identify the affected printer clients, certificate scripts, authentication flows, and recovery procedures. Assign an owner to review each area against IBM’s detailed product documentation and include the required checks in the maintenance plan.
Availability: check the component, not just the TR name
IBM’s Db2 PTF schedule currently lists:
| IBM i release | Db2 group | Planned level | Planned availability |
|---|---|---|---|
| 7.6 | SF99960 | 4 | November 20, 2026 |
| 7.5 | SF99950 | 13 | November 20, 2026 |
These are Db2 group levels, not RPG compiler PTF identifiers. As of October 28, 2026, the RPG Cafe page available for this review still lists the July 2026 enhancement PTFs. That list does not establish the prerequisites for the new array syntax.
Before adopting a feature, record the release, relevant product and PTF levels, compilation command, and target runtime. Check SQL precompiler support separately when the source contains embedded SQL. Code for IBM i extensions and related tools also have their own release histories.
A small first experiment
Start with the INZ(*LIST) lesson. Compile the supplied source after the required compiler support is confirmed, inspect the three values, and save the compiler listing. Then make the one-line change in the DIM(*INZ) lesson and repeat.
Keep the source, compiler listing, output, and PTF levels together as a reproducible reference for the team.
References
Documentation and supporting sources for this article.

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