Db2 13 - What's new - New-function APARs for Db2 13 in 2024

APAR PH63832 (December 2024) enhances some of the COPY utility processing to be zIIP eligible. This enhancement can help reduce CPU costs associated with creating backups.

Related function levels for this APAR: FL 500 New function in this APAR takes effect after the PTF is applied and function level 500 or higher is activated; FL 507 Activating function level 507 or higher verifies that this APAR is applied.

Starting in Db2 13 with APAR PH61970 (November 2024), the REBIND PACKAGE command for advanced triggers supports the EXPLAIN(ONLY) option. This allows you to obtain the EXPLAIN information for advanced triggers without having to change the package.

In addition, when the EXPLAIN(ONLY) option is specified in the REBIND PACKAGE command, the PLANMGMT(EXTENDED) and PLANMGMT(BASIC) options allow the OWNER and OWNERTYPE values to be changed. With this APAR applied, you can rebind the package with a specific owner under which the EXPLAIN tables are created.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 507 Activating function level 507 or higher verifies that this APAR is applied.

For more information, see the following related topics:

With APAR PH63145 (November 2024), the MODIFY STATISTICS utility can be executed against a single partition of a partitioned object without deleting the aggregate statistics. This enhancement adds a new PART keyword and supports a LISTDEF with the PARTLEVEL keyword specified. When MODIFY STATISTICS is executed with the PART keyword or with LISTDEF with the PARTLEVEL keyword, the utility will delete all the partition level statistics for only the specified partitions.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 507 Activating function level 507 or higher verifies that this APAR is applied.

For more information, see the following related topics:

With APAR PH58162 (September 2024), Db2 requests performance blocks (IWMPBs) for WLM enhanced delay monitoring for all threads in 64-bit HVCommon storage, and these control blocks no longer reside in the extended common service area (ECSA). This change further reduces the amount of ECSA storage footprint for processing threads beyond the reductions in the original Db2 13 release.

With these changes, delays for all local attach threads and all distributed server threads (DBATs) are monitored in RMF, and their buffer pool delays might trigger WLM buffer pool adjustments.

The DSNL044I message is also updated to indicate when an IWM4MCRE macro request fails to allocate more IWMPBs for local attach threads or DBATs. After Db2 issues DSNL044I for this condition, the processing of threads continues, but thread delays are not reflected in the RMF information, and buffer pool delays no longer trigger possible WLM buffer pool adjustments. For more information about this situation, see the APAR closing text.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 507 Activating function level 507 or higher verifies that this APAR is applied.

For more information, see the following related topics:

In Db2 12 or later, APAR PH62990 (September 2024) changes Db2 so that a Db2 subsystem that is not a member of a Db2 data sharing group can create a single listen socket for a location alias port by requesting that the socket is bound to INADDR_ANY. If a PROFILE.TCPIP PORT statement also specifies an IP address in the BIND parameter for the alias port, then TCP/IP binds the listen socket to the specified address.

It addresses specific concerns that certain customers raised after they applied the PTF for APAR PH59744.

In most cases, if the PORT statement BIND parameter specifies an IP address for the alias port, it should specify the same IP address that Db2 displays for TCPPORT or SECPORT in the DSNL084I message in DISPLAY DDF command output.

However, if the PORT statement BIND parameter for the alias port specifies a different IP address than Db2 displays for its main TCPPORT or SECPORT, then TCP/IP binds the alias listen socket to the IP address that was specified in the PORT statement BIND parameter. The result is that the alias port can only be reached by targeting that specific IP address. Db2 does not learn or display any information about the IP address for the alias port.

This APAR does not change the location alias behavior of Db2 data sharing group members

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 507 Activating function level 507 or higher verifies that this APAR is applied.

For more information, see the following related topics:

Staring in Db2 13 function level 100 or higher, APAR PH62438 (September 2024) enhances Db2 13 to use the SPECIFICIMP function for calls the WLM sysplex routing service (IWMSRSRS), if that function is available. The SPECIFICIMP function applies all factors of the SPECIFIC function, but it also considers how much other work with lower importance can be displaced, thus enabling higher importance work to be distributed more evenly .

When a Db2 for z/OS® server is a part of a data sharing group, Db2 returns a list of eligible members with a weight assigned to each member. This list is provided by WLM when Db2 calls the IWMSRSRS sysplex routing services. Db2 member is assigned a relative weight according to WLM and remote clients accessing the Db2 data sharing group can route work to the Db2 member with the higher weight.

Before this APAR, when Db2 uses the SPECIFIC function to call IWMSRSRS routing service, it does not take into consideration the importance factor of the work when calculating the relative weight for each Db2 member. The resulting workload distribution can be less effective compared to a distribution which considers the importance of the work being routed.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

Starting in Db2 13 with APAR PH60133 (July 2024), you can use the IFCID 417 statistics trace to class 10 and 11 to collect an inventory of new client information that correlates with the IFCID 365, 411, and 412 records. The IFCID 417 trace is written for events that occur within a statistics interval (STATIME_DDF or STATIME_MAIN).

The IFCID 417 trace can be used in correlation with IFCID 365, 411, and 412 records to answer the following questions:

Which applications connect by means of the Db2 Connect gateway
What is the identifying name, userid, product id, and IP address of problem applications
Which client drivers are used and what are their versions, build levels, and license types
Which applications are using client drivers with special builds due to security or bug fixes
What are the Db2 function levels of remote applications connecting to a Db2 server

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

Starting in Db2 13, APAR PH60536 (July 2024) introduces support for users with the DISPLAY privilege to issue the DISPLAY ML and DISPLAY RLIMIT commands. This change makes these commands more consistent with the behavior of other DISPLAY commands.

Before this APAR, users issuing the DISPLAY ML command needed to have at least one of the following administrative authorities:

SQLADM authority
System DBADM authority
SYSOPR authority
SYSCTRL authority
SYSADM authority

Before this APAR, users issuing the DISPLAY RLIMIT command needed to have at least one of the following administrative authorities:

System DBADM authority
SYSOPR authority
SYSCTRL authority
SYSADM authority

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

APAR PH58161 (May 2024) enables Db2 13 to use an ENF80 signal provided by z/OS Communications Server to determine when the TCP/IP stack leaves or rejoins the sysplex. When Db2 detects a change in the status of the TCP/IP stack, it now issues message DNSL524I. Messages DSNL085I and DSNL089I in the DISPLAY DDF command output are also updated to display an UNAVAILABLE status if the TCP/IP stack leaves the sysplex.

This APAR also removes use of a DVIPA listener port that was previously introduced by APAR PI79095. The sole purpose of this port was to enable Db2 to discover when the TCP/IP stack left or rejoined the sysplex, and it had no listen depth and could not accept connections from clients. However, some customers encountered exceptions in compliance tools when this DVIPA listener port was used.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

APAR PH60669 (June 2024) enhances message DSNJ114I to report the COPYID and data set name of the log data set that is receiving the error, to help system programmers identify the problem and take appropriate actions sooner. Db2 issues the DSNJ114I message if it is unable to allocate an archive log on one copy but is still able to allocate to the other copy.

Before this APAR, the DSNJU004 utility was needed to be used identify the location of the error.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

APAR PH60870 (May 2024) introduces the new model retraining capability of SQL Data Insights (SQL DI). When you enable an object for AI query, SQL DI trains a neural network model based on the data you select. As the data change, the accuracy of the model may degrade over time. After the application of this APAR, you can retrain the model whenever necessary.

For more information, see the following related topics:

With the availability of IBM® Data Server Driver for JDBC and SQLJ APAR PH60240, which introduces version 4.33 driver release (May 2024), and APAR PH54501 (July 2023) applied in Db2 13 for z/OS, applications that use the JDBC Type 2 driver and trusted contexts can now specify password phrases of up to 100 characters.

For more information, see the following related topics:

Starting in Db2 13 with APAR PH59837 (April 2024), you can enable Cross-Origin Resource Sharing (CORS) support for Db2 REST services. Cross-Origin Resource Sharing (CORS) is a protocol standard for permitting a web page or application to access remote content from a different domain (or port) than the site that the web page was loaded from. You can enable Db2 REST services to use the HTTP Cross-Origin Resource Sharing (CORS) protocols, including support for the CORS "pre-flight" HTTP OPTIONS verb and CORS HTTP request/response header fields.

The configuration and management of the Db2 REST CORS origin authorization rules are implemented using a new z/OS RACF RESOURCE CLASS (DSNRAUTH) and associated RACF generic or discrete resource profiles to represent the allowed remote (origin) sites.

The CORS origin checking is managed as a system wide Db2 setting which is independent of the "end-user" that is driving the CORS request. So, the authorization ID associated with the DDF (ssidDIST) started task address space is used for the CORS origin resource authorization check.

Tip: If you want to use the REST CORS functionality before the availability of the RACF module ICHRRCDX update that delivers the new DSNRAUTH class definition, your z/OS RACF security administrator can temporarily create the DSNRAUTH class using the RACF dynamic class descriptor table (CDT) support. for more information, see Creating a temporary DSNRAUTH class by using the RACF dynamic class descriptor table.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 506 Activating function level 506 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

PH59534 (April 2024) introduces support for activating function level 505 in Db2 13. For more information, see the following related topics:

Starting in Db2 13, APAR PH51434 (March 2024) enhances the following Db2 utilities to prevent inconsistencies when copying XML data from a source table to a target table when the table space contains XML versions.

REORG TABLESPACE
RECOVER with FROM
REPAIR with INSERTVERSIONPAGES

Unlike table space versions or index versions, Db2 uses XML versions to optimize concurrency and memory usage. For more information, see How Db2 uses XML versions.

With this APAR, when these utilities create shadow data sets or reformat a data set, they save table space version information to the page set. So, you can run one of these utilities before you copy versioned XML data to prevent problems that might occur because of XML table space version number differences between the source and target tables. These differences can occur when the REORG utility converts the source or target XML table from the 6-byte basic RBA and LRSN format to the extended 10-byte format.

An XML table space that supports multiple XML versions contains columns named START_TS and END_TS, which contain the RBA or LRSN values for the logical creation and deletion of the XML records. The data types of these columns depend on the RBA and LRSN format of the table space: they are BINARY(8) for the deprecated 6-byte basic format and BINARY(10) for the extended 10-byte format. When the REORG utility converts the format of these columns, it also increments the XML table space version number on the page set by 1. This can become an issue while copying a table space because no system page is created to indicate the difference between the version numbers. The resulting mismatch can prevent subsequent access to the data, even if both tables have the same RBA or LRSN format.

The REPAIR utility with the CATALOG option is also enhanced to reconcile the XML table space version differences on the page set after such data is copied. For best results, run REPAIR CATALOG on the XML table space to repair the XML version number on the target object after data is copied or recovered. Doing so allows subsequent insert, update, and delete statements to be able to access the data without any conflict of table version number.

However, if DSN1COPY is used to copy the data from source to target, you must ensure that the START_TS and END_TS columns have the same format in both the source and target table spaces. The REPAIR CATALOG utility cannot validate data format between two objects. It only repairs the target XML version number to match the source XML table.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 505 Activating function level 505 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

APAR PH57811 (January 2024) introduces a capability to apply security profile rules more precisely. This capability is especially useful for enforcing security for new cloud-based clients or specific portions of the network more strictly. With this APAR applied, you can specify any of the following values in the LOCATION column for profiles that use the MONITOR product-type CONNECTIONS FOR SECURITY keyword:

A domain name that resolves to an IP address. An example fully qualified domain name is 'stlmvs1.svl.example.com'.
IPV4 or IPV6 IP address.
IPV4 or IPV6 subnet address.
'*', '::0', or '0.0.0.0' (for all connections).

Before this APAR, only the following values are supported for such profiles: '*', '::0', or '0.0.0.0'.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 505 Activating function level 505 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics:

Starting in Db2 12 with APAR PH54199 (January 2024), adds a new DSNB360I message for detailed information for a page that is identified with minimum page LRSN in a DSNB355I message, to help you locate the page and the object it belongs to promptly in the case the GBP recovery delay is caused by the lagging minimum page LRSN.

Recovery from the group buffer pool recovery pending (GRECP) state might be delayed when the GBP-recovery LRSN is not progressing. The GBP-recovery LRSN is the minimum of the minimum page LRSN and the minimum member LRSN. The minimum page LRSN is the oldest changed page clean-to-dirty LRSN that was recorded at the time of the last group buffer pool checkpoint. The minimum member LRSN is the minimum member-level, write-pending LRSN that was recorded at the last group buffer pool checkpoint.

If the minimum page LRSN is older than the time when the third-to-last group buffer pool checkpoint was taken or the minimum member LRSN is invalid, Db2 issues a DSNB355I message at a group buffer pool checkpoint. The DSNB355I message includes the minimum page LRSN and the local timestamp of the minimum page-level LRSN, but it does not include the page details.

Related function levels for this APAR: FL 100 New function in this APAR takes effect after the PTF is applied at any function level; FL 504 Activating function level 504 or higher verifies that the PTF for this APAR is applied.

For more information, see the following related topics: