New-function APARs for Db2 13 in 2025
- Datagram message support in MQListener
-
APAR PH63420 (February 2025) enhances the MQListener support in Db2 12 or later to send reply messages for datagram messages.
For more information, see the following related topics:
- Enhanced monitoring of work file usage for sorts
-
APAR PH62780 (February 2025) introduces new trace fields to monitor the current usage and highest usage since Db2 was started (high-water mark) for 4 KB and 32 KB work file pages that are used during the sort process.
The new fields can assist users in determining the answers to questions like these:- How much work file space needs to be defined on a Db2 subsystem?
- How much work file space is needed by the largest sorts that are performed?
- How much work file space is consumed at various times during the day?
For more information, see the following related topics:
- Abbreviated spelling APPLCOMPAT supported in SQL syntax
-
With the PTF for APAR PH64377 (January 2025) applied at any function level, Db2 13 supports the abbreviated spelling,
APPLCOMPAT
whereAPPLICATION COMPATIBILITY
is used in any SQL statement that references the CURRENT APPLICATION COMPATIBILIY special register, and whereverUSING APPLICATION COMPATIBILITY
is specified inside theREGENERATE
clauses of the following ALTER statements:- ALTER FUNCTION (compiled SQL scalar)
- ALTER INDEX
- ALTER MASK
- ALTER PERMISSION
- ALTER PROCEDURE (SQL native)
- ALTER TRIGGER (advanced)
- ALTER VIEW
For more information, see the following related topics:
- New REST API and shell CLI for SQL Data Insights server administration and AI object-related management
-
APARs PH64220 and PH64221 (January 2025) introduce the RESTful application programming interface (API) and the shell command-line interface (CLI) of SQL Data Insights (SQL DI). The new interfaces enable you to use OpenAPI-compliant REST API requests and shell CLI commands to administer SQL DI server settings and manage its connections, AI objects, and object models.
Without this update, you manually perform SQL DI server administration and object-related management tasks by using the web user interface (UI) only. After applying the update, you can automate these tasks with the REST API, the shell CLI, or both.
For more information, see the following related topics:
- Installing, configuring, and starting SQL DI
- Creating and managing SQL DI connections, objects, and models with the REST API
- Creating and managing SQL DI connections, objects, and models with the shell CLI
- Viewing or modifying your SQL DI server settings by using the REST API
- Viewing or modifying SQL DI server settings by using the shell CLI
- Db2 SQL Data Insights REST APIs
- Shell commands for SQL Data Insights configuration, administration, and object model management
- PH64220
- EXPLAIN(ONLY) support for Db2 native REST services
-
Starting in Db2 13, APAR PH63990 (January 2025) introduces support for the EXPLAIN(ONLY) option for the Db2 native REST services createService API, and the BIND SERVICE and REBIND PACKAGE commands. This enhancement allows you to obtain access path information without having to create the native REST service. For an existing native REST service, this enhancement allows you to obtain the current access path information without updating the application package, which can potentially change the access paths.
Before this APAR, users could only obtain access path information by creating the native REST service. And for existing native REST services, users could only obtain access path information by using the REBIND PACKAGE command with the EXPLAIN(YES) option. This option modifies the existing package and potentially forces you to commit to access path changes before knowing what the changes are.
For more information, see the following related topics:
- AUTHID based monitoring with security profiles
-
APAR PH63652 (January 2025) introduces the capability to filter profiles that monitor security based on the authorization ID of the connection. The AUTHID can be provided as a fully specified value, a set characters followed by an asterisk (
*
) wildcard, or a single-byte asterisk value. When multiple profiles apply to the same connection a profile with a more specific value takes precedence over one that uses wild cards.The new AUTHID filtering capability can help you to discover and enforce secure connectivity for applications when you know the authorization IDs that are associated with each application, without requiring that you know which IP addresses the applications are using.
Before this enhancement, the MONITOR product-type CONNECTIONS FOR SECURITY keyword can only be specified for profiles with LOCATION based filtering (default, subnet, or specific IP address) in the DSN_PROFILE_TABLE.
For more information, see the following related topics:
- Reduced z/OS console flooding by DSNL030I messages
-
APAR PH62137 (January 2025) reduces situations where Db2 for z/OS server authentication failures, such as invalid user IDs or passwords, can cause DSNL030I and ICH408I messages to flood the z/OS console. This situation can also potentially cause the ssnmMSTR address space to abnormally terminate because it reaches the maximum number of lines.
With this APAR, Db2 no longer issues DSNL030I messages for every authentication error event. Instead, Db2 issues a new DSNL061I message at a minimal interval of 5 minutes for each client identified by unique combination of the reason code, IP address, user ID, and product identifier. Db2 also suppresses the corresponding RACF ICH408I console messages to reduce flooding of the z/OS console and risk of the ssnmMSTR breakdowns.
The DSNL061I message reports specific authentication errors with ‘00F300xx’X reason codes. As a result, z/OS system administrators and Db2 database administrators can better see other important messages.
When Db2 issues the DSNL061I message, the EXTSEC subsystem parameter controls whether it returns information about the security mechanism used in the thread information. That is, Db2 includes the security mechanism information in DSNL061I messages only when YES is specified for the EXTSEC value.
For more information, see the following related topics: