With the availability of the PTF for APAR PH66983, you can now activate function level V13R1M508 to enable the following new capabilities in your Db2 13 for z/OS environment.
BLOCKING_THREADS table function enhancements
Both the BLOCKING_THREADS table function and the -DISPLAY BLOCKERS command are enhanced with table, index, and space level granularity, so Db2 database administrators can more efficiently and resolve blocking threads to ensure seamless online schema changes, optimal database performance, and operational efficiency. Learn more
More than 93 active and archive log pairs
The maximum number of active log data sets is increased to 1,000 per log copy and the maximum number of archive log data sets is increased to 14,500 per log copy. This enhancement increases the maximum amount of active and archive logs to allow for 24–48 hours of active log data, without expanding the size of their active log data sets. When active log data sets are not larger than 48 GB, replication and recovery performance is greatly improved, and logs can be sent for analysis. Learn more
Specify sort work or DGTT usage for PBG table spaces in work file databases
Function level 508 introduces the capability for DBAs to more easily specify whether Db2 uses a certain work file table space for sort processing or declared global temporary table (DGTT) specify whether table spaces in a work file database are used for sort work or declared global temporary table (DGTT) processing. Specifically, applications that run at APPLCOMPAT level V13R1M508 or higher can specify two new keyword clauses in CREATE TABLESPACE statements for table spaces in work file databases: FOR SORT and FOR DGTT.
The new FOR SORT clause specifies that a PBG table space is used for sort processing only. Likewise, the FOR DGTT clause specifies that the table space is used for declared global temporary table (DGTT) work and scrollable cursors only. These keywords are accepted only when the database specified by the IN database-name clause is a work file database.
The description of the WFDBSEP subsystem parameter has also been updated to describe the results of specifying these keywords. Learn more
Generation of UUID values
Four new built-in scalar functions support generation and formatting of UUID values in Db2 for z/OS. A universally unique Identifier (UUID) is a 128-bit label used to uniquely identify objects in computer systems, without central authority. UUIDs are commonly used in microservices and cloud services. These new built-in functions are available for use by applications that run at APPLCOMPAT level V13R1M508 or higher: The GENERATE_UUID and GENERATE_UUID_BINARY function return UUID values, and the VARBINARY_FORMAT and VACHAR_FORMAT_BINARY functions support conversion of the generated UUID values. Learn more.
More local applications control with Db2 profile tables
Profile tables can be used for setting built-in global variables and setting special registers for local applications, without needing to change application code. That is, you can insert rows in the DSN_PROFILEATTRIBUTES_TABLE with ATTRIBUTE2='1' to specify that a profile applies to local applications only, or with ATTRIBUTE2='2' to specify that a profile applies to both local and remote applications for most global variables and special registers. A NULL value in the ATTRIBUTE2='2' continues to specify that the profile applies only to remote applications. With this enhancement, the local profile support is available for most special registers and all global variables that are supported by profile tables. Learn more
Populating DSSIZE records in Db2 catalog tables for all UTS objects
After the catalog level is updated to V13R1M08 or higher, Db2 starts consistently populating data set size records in the following Db2 catalog columns, for all objects in UTS and LOB table spaces: DSSIZE and PIECSIZE columns in the SYSINDEXES table; and DSSIZE columns in the SYSINDEXPART, SYSTABLESPACE, and SYSTABLEPART tables. By knowing these values, the DBAs can more easily determine when indexes are becoming full, without resorting to complicated calculations, and prevent outages during heavy application workloads.
This catalog level update also changes the data type of the DSSIZE columns to BIGINT in the SYSINDEXES and SYSINDEXPART catalog tables.
You can also run a special one-time CATMAINT job to populate any missing DSSIZE and PIECESIZE column values for existing UTS and LOB objects any time that the Db2 catalog level is V13R1M508 or higher. However, before you do so, it is important that you verify that your Db2 13 environment does not have a problem that was identified in Db2 12 APAR PH32731. The APAR closing text includes queries that you can use to check for this problem. Learn more
Rebind phase-in for SQL PL and trigger packages
Function level 508 extends support for the rebind phase-in capability that was introduced for most packages in Db2 12 to packages for SQL PL routines and triggers. This capability enables DBAs to deploy new application features that depend on packages SQL PL routines and triggers without taking an outage, especially in busy Db2 environments, where the packages are often continuously executed by one or more threads. Learn more
Preparations for converting Db2 catalog objects to UTS
When the CATMAINT utility updates the Db2 catalog level for V13R1M508, it also prepares the catalog for future conversion of remaining non-UTS objects by creating many new table spaces with the DEFINE NO attribute.
However, function level 508 does not enable the conversion process for any of the catalog tables, and it is expected to be enabled by one or more future Db2 13 function levels.
The - DISPLAY GROUP command is also enhanced with a new option, UTSCONVERSION, which returns a report about the status of the UTS conversions for catalog and directory objects.
Verification of previous new-function APARs
As with all function levels since FL 504 in Db2 13, activation of function level 508 verifies that the PTFs are consistently applied in your Db2 environment for a series of earlier new-function APARs. The enhancements in these APARs can generally be used at any Db2 13 function level in each Db2 subsystem or data sharing member where the PTFs are applied. However, activating function level 508 guarantees that they are applied consistently your Db2 environment and cannot be removed. To find these APARs, see the “Verifying function level column” in New-function APARs for Db2 13.
#Db2forz/OS