Mar/Apr'26

Welcome to MainframeMatters Mar/Apr issue!

This Mar/Apr issue explores how Db2 for z/OS is evolving on every front—from killing off persistent performance myths and taming dynamic SQL, to embracing autonomous operations, statement‑level invalidation in Db2 13, and AI‑driven integration with modern applications. Together, these themes show Db2 shifting from a finely tuned workhorse into a smarter, self‑optimizing data platform that can keep pace with modern engineering practices without sacrificing its trademark reliability.

At the same time, the human side of the mainframe remains front and center. You’ll find guidance for new Db2 sysprogs, perspective from veterans who have “seen it all,” and practical takes on how to cut through outdated rules of thumb so that tuning decisions are grounded in real measurements instead of folklore. The throughline across every article is simple: the future of Db2 for z/OS belongs to teams that combine deep platform expertise with modern automation, AI, and disciplined engineering practices.

Check out the articles in this issue to see the latest across the mainframe space - thanks for reading Mainframe Insider!

IBM Db2 sets the new standard as the autonomous database for the agentic AI era

Today, IBM has introduced the next chapter of Db2: the autonomous database powered by the newly released Db2 Genius Hub. The autonomous database proactively monitors, detects and reacts to issues, acting autonomously when appropriate with human oversight.

This experience is enabled through Db2 Genius Hub, a next generation AI-powered console, that transforms how Db2 database administrators (DBAs) manage sprawling, complex data estates by shifting database operations from reactive troubleshooting to proactive, agentic-based resilience.

For decades, Db2 has powered mission critical workloads where reliability is non-negotiable and downtime is not an option. Db2 Genius Hub brings intelligence-first operations to these Db2 environments, where data teams can experience up to... (Read the full article)

In-Memory Techniques for Accelerating Db2 Programs

Performance optimization remains a top priority for organizations running Db2 applications on IBM Z. Whether the workload is a high-volume batch job or a high-frequency CICS transaction, repetitive database access can be a hidden performance bottleneck. Each SQL request consumes CPU resources, requires Db2 to manage access paths and data pages, and may involve physical I/O. When applications repeatedly retrieve the same data, the overhead can be substantial.

One effective way to improve Db2 performance is to keep frequently used data closer to the application. That can be done through Db2 memory structures, application-managed caches, temporary staging techniques, or an external transparent caching layer.

Below are several proven approaches that help accelerate Db2 workloads by keeping frequently used data closer to programs.

Why Keeping Data Closer Improves Performance

Many Db2 programs repeatedly access the same reference, lookup, and other slow-to-change tables. When those requests can be satisfied without repeated trips through the full Db2 execution path, performance can improve substantially.

Benefits can include faster response times, higher batch throughput, reduced Db2 CPU utilization, and lower I/O overhead. Db2 buffer pools are the clearest built-in example: they keep table and index pages in memory so Db2 can avoid unnecessary physical reads... (Continue reading)

Db2 Performance Myths That Refuse to Die

After decades of working with IBM Db2 for z/OS, I’m continually surprised that some performance myths simply refuse to go away. Despite new releases, new features, and new hardware generations, the same half-truths and oversimplifications keep resurfacing in design meetings and tuning discussions.

Performance tuning is nuanced. It requires understanding tradeoffs, workload patterns, and business requirements. When we rely on myths instead of measurement, we risk making things worse—not better.

Let’s examine a few Db2 performance myths that deserve to be retired once and for all.

Myth #1: “More Indexes Always Improve Performance”

This may be the most persistent myth of them all. Yes, indexes can dramatically improve read performance. But every index carries overhead:

INSERTs must update every index.
DELETEs must remove entries from every index.
UPDATEs may require index maintenance.
REORG and RUNSTATS processing increases... (Continue reading)

The Challenges of Managing Dynamic SQL in Db2 for z/OS

In the world of Db2 for z/OS, SQL performance tuning is one of the most critical — and often most complicated — DBA responsibilities. While static SQL has long been the bread and butter of traditional mainframe applications, the growing use of dynamic SQL—driven by modern applications, APIs, and distributed workloads—has changed the tuning game.

Dynamic SQL brings with it agility and flexibility but also introduces a new layer of complexity that can hinder performance if not well managed. With this in mind, we’ll look at why dynamic SQL can be so challenging, what DBAs can do to get ahead of performance problems, and how a product like Infotel’s DB/IQ QA can help simplify and streamline the process. (Continue reading)

Db2 13 for z/OS Brings Precision with Statement-Level Invalidation

In the ongoing evolution of Db2 for z/OS, each new release brings capabilities that aim to improve efficiency, reduce overhead, and increase system availability. Db2 13 for z/OS continues this trend with a subtle but powerful enhancement: statement-level invalidation. It’s a change that may not grab headlines, but for DBAs and performance tuners, it’s a game-changer.

The Problem with Broad-Stroke Invalidation
Traditionally, when an object such as a table or index was altered, Db2 would invalidate entire packages. This broad-brush approach meant that even if only a single SQL statement within a package was impacted by the change, the entire package would be invalidated and require a rebind. (...Read more)

AI-Enhanced Db2 for z/OS: Revealing Hidden Insights through Modern Application Integration

In today's data-driven world, enterprises need seamless integration between databases and modern applications to unlock valuable insights. IBM Db2 for z/OS, a powerful relational database, offers robust connectivity options with Apache Spark and Python, enabling efficient data processing, analytics, and AI-driven insights.

This blog explores how Spark and Python connectivity to Db2 can streamline data workflows and enhance real-time analytics. Additionally, we delve into IBM Db2 SQL Data Insights (SQLDI) and its use of word embedding techniques to uncover hidden patterns within structured and unstructured data. By leveraging these capabilities, businesses can monetize hidden insights within their Db2 ecosystem and drive smarter decision-making.

For decades, IBM Db2 for z/OS has been the backbone of mission-critical applications for enterprises worldwide. Its reliability, performance, and security are unmatched. However, as businesses increasingly adopt AI and machine learning technologies, there's a growing need to bridge the gap between traditional relational databases and modern data science tools. (Read the full article)

IBM z17: What It Means for Db2 for z/OS

Every new generation of the IBM Z mainframe comes with excitement—not just for its technical advancements, but also for the unveiling of its sleek front panel design, often kept secret until launch. The latest member of the family, IBM z17, which was released in June, brings significant enhancements in AI capabilities and performance that directly benefit Db2 for z/OS workloads alongside that cool new front panel. Here’s what it means for you.

Smarter with AI: Accelerated Performance for Db2

The IBM z17 is powered by the new Telum II processor, which is specifically designed to handle AI workloads. The Telum II boasts:

  • 8 cores running at 5.5 GHz, up from 5 GHz in z16
  • A second-generation on-chip AI accelerator (zAIU) for intelligent, low-latency AI inferencing

Db2 leverages this AI acceleration through SQL Data Insights, allowing concurrent AI queries to run faster and more efficiently. (Read the full blog)

Tips for New Db2 Sysprogs

I’ve been a db2 sysprog for over 20 years. I have built hundreds of db2 subsystems ranging from stand alone subsystems, adding members to a group, and brand new datasharing groups with up to 20 members. I have installed maintenance thousands of times across the years and performed version upgrades from v5 through v13. Chances are, if it can happen in db2 z, I have seen it. My experience comes from shops large and small mostly in retail and finance. I’ve been at shops with only one production db2 and at shops with well over 100.

I recently attended a db2 conference for the first time in several years. I quickly realized that I am no longer the youngest person in the room and am in fact a senior sysprog, no matter how much part of me wants to deny that fact. While mingling between sessions or at events, I inevitably ran in to newer sysprogs who all seemed to have the same question. What tips or advice do you have for someone just starting out as a db2 sysprog? Keep reading for my answer.

RTFM. Read the friendly manual. When I started out, the manuals were printed and shipped with your software order. (Read more...)

All Images licensed via Freepik Premium

All product names, logos, and brands are property of their respective owners. Use of these names, logos, and brands does not imply endorsement.

If you found this valuable, please consider sharing it with your colleagues.

Log-On Software Inc., 15 Constitution Dr., STE 1A, Bedford, NH 03110, United States, 603-458-5300

Unsubscribe Manage preferences