Db2 13 function levels

New Db2 capabilities and enhancements are continuously delivered in a single maintenance stream as the code becomes ready. You can activate the new capabilities in a data sharing group or Db2 subsystem after a function level is delivered. A function level corresponds to a single PTF that enables the activation of a specific set of enhancements that shipped in previous prerequisite or co-requisite PTFs. The activation of a function level results in the activation of all lower function levels.

Blogs for Db2 for z/OS: See the IBM® Community blog for Db2 for z/OS® and its ecosystem for the latest news about new capabilities and enhancements in Db2 for z/OS continuous delivery, from the IBM experts who design, build, test, and support Db2

Subscribe today!

About function levels in Db2 13

A function level enables a particular set of new Db2 capabilities and enhancements that were previously delivered in the single continuous stream of Db2 code. It includes code that supports new capabilities, defect fixes, and preventive service items. Before you can use the new capabilities of a function level, you must activate the function level, or a higher function level. Activation of a function level implies activation of the capabilities that are introduced by all lower function levels.

For more information about function levels, and how to activate them in Db2 13, see Adopting new capabilities in Db2 13 continuous delivery.

Available function levels in Db2 13 continuous delivery

The following function levels are available in Db2 13. They are listed in release order, beginning with the highest available function level.

Tip: After you activate function level 500, you can use a single procedure to activate any higher function level that is available based on the code level of your Db2 environment. Activating a function level also has the effect of activating any lower function levels. The description of each function level includes the complete procedures for activating it from any lower Db2 13 function level.

Function level	New-function capabilities (functional code APARs)	Catalog level	Enabling APAR	Release Date
FL 509	Converting Db2 catalog table spaces to UTS (PH70027) Subnet wildcard filtering for resource limit facility (RLF) (PH70071) Online ownership transfer of application objects (PH69677) Utility history for SHRLEVEL information (PH70075) New catalog columns for STMT_HASHID2 (PH70030) I/O counts in real time statistics (PH70074) Reduced false page P-lock contention in data sharing (PH69217)	V13R1M509	PH70028	2026-04
FL 508	BLOCKING_THREADS table function enhancements (PH67082) Increasing the maximum number of active and archive logs (PH67380) Specify sort work or DGTT usage for PBG table spaces in the work file database (PH67418) Generation of UUID values (PH67353) More local applications control with Db2 profile tables (PH67138) Consistent DSSIZE records in Db2 catalog tables for UTS and LOB objects (PH67419) Rebind phase-in for SQL PL and trigger packages (PH67404) Preparation for conversion of non-UTS catalog and directory objects (PH67554)	V13R1M508	PH66983	2025-10
FL 507	Online conversion of table partitioning from PBR to PBG (PH64949, PH64950) Enhanced application availability for system temporal tables (PH65039) LASTUSED column support in the SYSIBM.SYSPLAN catalog table (PH64762) Referencing temporal and archive-enabled tables in the same SELECT statement (PH65133) Specify greater than 64 GB primary and secondary space allocation quantities (PH64760)	V13R1M507	PH64907	2025-04
FL 506	Non-disruptive clearing of data partitions with LOAD (PH62543) Improved performance for IN-list predicates (PH58750) Db2 trace capacity: More concurrently active traces (PH59020) INSERT with multi-row VALUES clause (PH62561) Add implicitly hidden ROWID columns (PH61629) Lift certain restrictions for column masks (PH62393, PH62690)	V13R1M505	PH62635	2024-10
FL 505	New token-based authentication capability (PH55599) Temporal support for security-related catalog tables (PH59531) New trace destination for Db2ZAI (PH56369) INTERPRET scalar function (PH59595)	V13R1M505	PH59534	2024-04
FL 504	Minimized impact of invalidated packages with statement-level invalidation (PH55497) Db2 trace capacity: More OP buffers (PH55622) Utility object-level history (PH55476, PH55914, PH55915, and PH55916) Enhancements to SQL Data Insights (PH55212) ORDER BY support for a fullselect that invokes LISTAGG (PH55596)	V13R1M504	PH54919	2023-10
FL 503	New default values in existing rows for added ROW CHANGE TIMESTAMP columns (PH51185) Accelerator-only support for more than 32K elements in an IN list (PH50756) SELECT INTO statement support for OPTIMIZE FOR n ROWS (PH50010)	V13R1M501	PH51469	2023-02
FL 502	Db2 controlled sysplex workload balancing (PH48253) Record dependencies and validity at the statement level for packages (PH47560)	V13R1M501	PH47891	2022-10
FL 501	Allow applications to specify a deadlock resolution priority DEADLOCK_RESOLUTION_PRIORITY global variable Real-time statistics scalability Collection of real-time and historical information about utility execution Real-time statistics support for index splits	V13R1M501	None	2022-05
FL 501	Increased flexibility for package ownership Page sampling for inline statistics SQL Data Insights Reduced ECSA storage for IFI buffers Online conversion of tables from growth-based (PBG) to range-based (PBR) partitions Fast index traversal (FTB) support for larger index keys Increased control for applications over how long to wait for a lock Profile table enhancements for application environment settings Ability to delete an active log data set from the BSDS while Db2 is running SPT01 and SYSLGRNX table spaces are converted to DSSIZE 256 GB Improved concurrency for altering tables for DATA CAPTURE Change REORG INDEX SHRLEVEL REFERENCE or CHANGE so the NOSYSUT1 keyword is the default CREATE TABLESPACE uses MAXPARTITIONS 254 by default Long names support for timeout and deadlock messages in IRLM New-function APARS for function level 500 or higher^{1, 2}	V13R1M100	None	2022-05
FL 100	Index look-aside optimization Sort optimization Expanded SORTL usage with learning from execution (IBM z15) Improved locking for INSERT to partition-by-growth (PBG) table spaces Improved cross-partition search for INSERT to PBG table spaces Reduced agent local below-the-bar (BTB) storage DBAT availability improvements Improved performance when using external security Reduced ECSA storage use for distributed data facility (DDF) processing Improved storage monitoring and contraction Dynamic management of CF lock storage by IRLM Improved Db2 installation and migration process for customizing the amount of private storage for IRLM locks Memory usage reduced for REBIND with APREUSE Partition range support in IFCID 306 for users of replication applications EDITPROC support in IFCID 306 for users of nonproxy mode replication applications Relative page numbering for new PBR table spaces Improved default statistics collection granularity REPAIR utility WRITELOG for decompression dictionaries Enhanced space-level recovery with the RECOVER utility Column names longer than 30 bytes Db2 support for z/OS continuous compliance More concurrent open data sets in z/OS 2.5 More efficient cleanup for above-the-bar storage Index page split instrumentation enhancements Accounting information on the longest wait times for common suspension types IBM z16 group buffer pool (GBP) residency time Subsystem parameter simplification Various new-function APARs^{1, 3}	V13R1M100	None	2022-05

Notes:

When the PTF for the APAR is applied in the Db2 subsystem or data sharing member.
When the Effective Function level column at the link indicates FL500.
When the Effective Function level column at the link indicates FL100.

Function levels for migration to Db2 13

The following table describes the main function levels that are used in the Db2 13 migration process.

Function level	Description
FL 100	Db2 starts at function level 100 (V13R1M100) during migration to Db2 13, and fallback and coexistence with Db2 12 in data sharing remain possible. Many new capabilities in Db2 13 remain unavailable. For more information, see Function level 100.
FL 500	Activating function level 500 (V13R1M500) prevents coexistence with and fallback to Db2 12. Function level 500 is also the first opportunity for applications to use many of the new capabilities in Db2 13. However, new capabilities that depend on Db2 13 catalog changes remain unavailable. For more information, see Function level 500.
FL 500 ¹	Function level 501 (V13R1M501) is the first opportunity after migration to Db2 13 for applications to use new features and capabilities that depend on catalog changes in Db2 13. For more information, see Function level 500.

Tip:

After you activate function level 500, you can use a single procedure to activate any higher function level that is available based on the code level of your Db2 environment. Activating a function level also has the effect of activating any lower function levels. For a list of all available function levels and specific activation procedures for each function level, see Db2 13 function levels.