What the Summer 2026 IBM i Technology Refreshes Did and Did Not Do for AI
IBM i 7.6 TR2 and 7.5 TR8 shipped on July 18, 2026 with no AI features in them. Not a thin AI section, not a preview flag on something half-finished. Nothing.
That sounds like a complaint and it is not one. Every AI thing IBM has done for this platform in 2026 shipped somewhere other than a Technology Refresh, and once you line the dates up, the summer TRs stop looking like a disappointment and start answering a question a lot of shops keep asking: when does AI show up in the operating system? On current evidence, it does not. It shows up next to it.
What actually shipped on July 18
This was a database and security refresh, and a good one. Scott Forstie's team put most of the visible work into Db2 for i, and the security items in 7.6 TR2 are the kind that close an audit finding rather than win a demo.
Named items in IBM i 7.6 TR2 and 7.5 TR8
| Item | What it does |
|---|---|
| SQL Error Logging Facility filtering | Filter SELF error rows down to your own user ID, with the duplicate-detection keys widened to include statement operations. |
| Trigger pseudo columns | Reach the file, library and member that fired a database trigger, resolved after normal column names. |
| URL encode services | RFC 3986 encoding for SQL programs making HTTP calls out of Db2 for i. |
| FROM_SYSTEM_TIMESTAMP and TO_SYSTEM_TIMESTAMP | Two new scalar functions for moving between system timestamp representations. |
| CREATE_DATA_JOURNAL_READER | Turns hexadecimal journal entry data for a journaled file into readable columns. Forstie's framing is that you generate your own helper function for whatever table you need. |
| SYSIBMADM.QIBM_SQEDEBUG_BY_DAYS | Global variable controlling how long SQL query engine debug information is kept in the IFS. |
| QIBM_IOSYSCFG_DDM (7.6 TR2) | A function usage identifier for DDM authorization, so you stop handing out *IOSYSCFG to get it. |
| Bring Your Own Key (7.6 TR2) | External key management through IBM Cloud Key Protect, for cloud and on-premises systems. |
| OAuth 2.0 for SMTP (7.4 and later) | The mail authentication Google and Microsoft now require. |
| CVE_INFO | A SYSTOOLS table function that queries the CVE database and returns publication dates and CVSS severity scores. |
| 17 new IBM i services, 10 enhanced | Across QSYS2 and SYSTOOLS: geographic mirroring views, service tools configuration, external key management, audit journal support, job functions and more. |
Around the operating system, Access Client Solutions 1.1.9.13 added SQL Error Logging Facility support to Run SQL Scripts with seven new examples, and Navigator for i rebuilt the Performance Data Investigator charts from Dojo to Angular so you can read a graph and the data behind it without losing the graph. Migrate While Active picked up external storage replication and the ability to upgrade the operating system during a migration. Useful, ordinary, welcome work.
Where the AI actually went
Put the 2026 dates next to each other and the shape is obvious. Bob 2.0 and the Bob Premium Package for i went generally available on June 24. The Power S1112, the entry Power 11 box that runs inference locally on on-chip Matrix Math Acceleration, went generally available on July 24, six days after the refreshes. The August watsonx Orchestrate release added Build with Bob as a preview and took AgentOps to general availability. IBM Power Autonomous Operations reaches general availability on September 23.
Four AI deliveries in four months, and the Technology Refresh sitting in the middle of them mentions none of it.
If you want the detail on any of those, we cover them separately: IBM Bob explained, Build with Bob in watsonx Orchestrate, and IBM Power Autonomous Operations explained. The running calendar lives on the IBM i AI watch list.
Why AI is not in the TR cadence
A Technology Refresh is an operating system deliverable. It arrives roughly twice a year, it is tied to a release level, it ships as PTF groups, and IBM supports it for the life of that release. That set of promises is the whole point of the TR model and it is why IBM i shops trust it.
Now try to put a model-driven agent inside it. Bob has already gone from 1.0 in March to 2.0 in June. watsonx Orchestrate publishes release notes monthly. The IBM i MCP Server is an open-source project moving at the speed of its repository. Autonomous Operations rides the Power stack, not the IBM i release. Anything that fast, wrapped in a PTF group, would be frozen at the pace of the operating system and stale before the next refresh.
IBM has not explained the split in those terms. This is a reading of where the products actually landed, not a statement of IBM strategy. But the delivery evidence is consistent enough that planning around it beats waiting for a different answer.
What the TRs did do for AI, quietly
Nothing in these refreshes is labeled AI. Several items are still the plumbing an agent ends up using.
CREATE_DATA_JOURNAL_READER turns journal entries into rows you can select. An agent reaching IBM i through the MCP Server reads rows, which means change history that used to need a custom program is now an SQL question. RFC 3986 URL encoding matters the moment an SQL program calls an HTTP endpoint, and calling an inference or embedding endpoint from Db2 for i looks exactly like that. Seventeen new IBM i services are 17 more things an MCP server can expose as a tool with a YAML definition instead of a wrapper somebody has to write and maintain. SQL Error Logging Facility filtering is deeply unglamorous and enormously useful the first time a generated statement fails at three in the morning and you need to find it by user.
IBM presented none of that as AI enablement, and I am not going to pretend otherwise. It is what the features are useful for, not what they were sold as.
What to do if you were waiting for AI in the OS
Stop treating the TR as the release you are waiting on
Two refreshes a year is the wrong clock for a product line that has shipped four times since March. The AI decisions in front of you are product decisions with their own dates.
Install the refreshes anyway
Bring Your Own Key, CVE_INFO, the DDM function usage identifier and OAuth 2.0 for SMTP are the security items that make an AI project approvable later. Being current is cheaper than being current in a hurry.
Watch the product calendars instead
Bob release notes, the watsonx Orchestrate monthly notes, the IBM i MCP Server repository and the Power announcements. That is where anything you can actually deploy will show up first.
One caveat on all of this. Feature lists here come from IT Jungle's July 20 and July 27 coverage and IBM's own announcements, and IBM continues to deliver individual enhancements to existing IBM i releases between refreshes. Confirm the current level of anything you plan around against IBM's own TR pages rather than treating this article as a frozen list.
Sources
- https://www.itjungle.com/2026/07/20/big-blue-finally-unveils-first-ibm-i-tech-refreshes-of-2026/
- https://www.itjungle.com/2026/07/27/what-ibms-got-cooking-in-db2-for-i-in-the-summer-trs/
- https://newsroom.ibm.com/2026-07-15-ibm-launches-new-power-systems-and-software-built-for-enterprises-to-address-risk,-productivity,-and-flexibility
- https://www.itjungle.com/2026/05/04/the-big-easy-connecting-the-dots-on-big-blues-ai-strategy-for-ibm-i/
- https://www.ibm.com/new/announcements/ibm-bob-and-watsonx-orchestrate-close-the-gap-between-building-and-running-agents
Related Tools & Vendors
More From the Library
- AI for Trucking Companies Still Running IBM i: What Actually Works
- Bob, watsonx Orchestrate and the IBM i MCP Server: How the Chain Actually Fits Together
- Build with Bob in watsonx Orchestrate: What Shipped, and What Is Still a Preview
- IBM Bob Pricing and Packages: Which One an IBM i Shop Actually Needs
- IBM Power Autonomous Operations, Explained Before GA: An AI Agent That Runs the Box, Not the Code