In 2016 IBM released Db2 12 for z/OS and embarked upon a continuous delivery model which has proven immensely successful in delivering new features and enhancements to our customers without compromising software quality. In 2022, we released Version 13 of Db2 for z/OS and recommenced the delivery of function levels and individual features through the same continuous delivery model.

Now, as I have made clear at recent conferences, we see the need for a new version of Db2 beyond V13. This will allow us to make internal changes that position Db2 for the future, changes that cannot be delivered through individual or even sets of APARs.

The next version of Db2 also presents a unique opportunity to focus more clearly upon that future based upon strategic technology whilst no longer being constrained by the need to support obsolete, deprecated function, much of which was originally designed and developed many decades ago.

For this reason the next version of Db2 will no longer support the following:

Simple, segmented or classic partitioned tablespaces; BRF or basic (6 byte) format pagesets; hash pagesets; synonyms; VTAM connectivity.

This is neither the time nor place to go through all the benefits of "newer" technology, such as UTS tablespaces and TCP/IP, compared to the list above. As a general statement there are a number of reasons why it makes sense to draw a line in the sand with the next version. New function in Db2 has been linked to the use of UTS tablespaces for years, therefore continued use of non-UTS objects prevents the ability to take advantage of valuable enhancements in Db2. It should come as no surprise to anyone that the future of Db2 is UTS and online conversion through online REORG has been available for years. Yet the longer this conversion is delayed, the more costly conversion is likely to be due to increased data volumes. Consolidation upon strategic technology also makes sense since it will improve product quality and stability and streamline development and test, in turn improving our ability to deliver new enhancements quicker to the market. These considerations will benefit everyone.

There are many details regarding the next version of Db2 that will be communicated in due course. No doubt the most pressing question for many is timeframe. The exact timing has yet to be committed and is subject to change, however we do not anticipate releasing the next version before 2028. The end-of-support date for V13 will be set well into the future to allow ample time for preparation and transition.

In the meantime, we have work to do too. Rest assured that we have exciting plans for new capabilities in the next version, including significant simplification, usability, performance and availability improvements. Also, we will continue to deliver new enhancements through continuous delivery in V13, and you will see in the coming months changes being rolled out to convert the remainder of the catalog, directory and workfiles to UTS to prepare for what I have outlined here. 

This plan should not be cause for concern but rather the opportunity and impetus to start planning now, if you have not done so already, for the future of Db2 for z/OS, IBM's flagship database - a future that has as its solid foundation the groundbreaking technological innovation of the past 40 years but that is firmly focused upon the decades to come.