New-function APARs for Db2 12 in 2024 and later

Tip: Depending on how when and how you order the product code for Db2 12 or Db2 13, you might find that the external changes from any of the following APARs are already built-in when you install a new Db2 environment or migrate to Db2 13. Also, you can expect that external changes from the following APARs with availability dates earlier than 2022-06 are likely to be already built-in when you migrate to Db2 13, regardless of whether you apply the PTFs in Db2 12.

Enhance DSNTXAZP for automatic discovery of more Db2 subsystem attributes (phase 2)

In Db2 12, APAR PH62011 (December 2024) enhances the capabilities of the DSNTXAZP tool to discover more types of configuration parameters, including BSDS and log parameters, the DSNHDECP parameter, certain data parameters, IRLM parameters, Db2 catalog size parameters, routine parameters, work file database parameters, and data sharing group parameters.

This APAR introduces the following new actions in the DSNTXAZP tool:

UPDATE_APPL_DEF

This action creates a new CLIST defaults member and updates it using the name of the application defaults module. The following DSNTIDxx entry (CLIST parameter) is updated: DSNHDECP. End of change

UPDATE_CATALOG_SIZE

This action creates a new CLIST defaults member and updates it using the current Db2 catalog sizes only. The following DSNTIDxx entries (CLIST parameters) are updated: NUMCOLUM, NUMDATAB, NUMPKGS, NUMPKSTS, NUMPLANS, NUMPLPL, NUMTABLE, NUMTABSP, NUMVIEWS. End of change

UDPATE_DATA_PARAM

This action creates a new CLIST defaults member and updates it using the attributes of the non-VSAM data sets and storage groups created by the installation and IVP jobs only. The following DSNTIDxx entries (CLIST parameters) are updated:

VOLSDAT3, DATACLS3, MGMTCLS3, STORCLS3
INSICPRE

UPDATE_IRLM

This action creates a new CLIST defaults member and updates it using the IRLM startup procedure parameters only. The following DSNTIDxx entries (CLIST parameters) are updated: IRLMDISC, IRLMGRPN, IRLMIDEN, IRLMLKSZ, IRLMLTE, IRLMMLMT, IRLMMLTU, IRLMPGPR, IRLMTRAC. End of change

UPDATE_WKFL_DB

This action creates a new CLIST defaults member and updates it using the current Db2 work file database and table space settings only. The following DSNTIDxx entries (CLIST parameters) are updated:

WKDBNAME
S32KNOTS, S32KSGSZ, S4KNOTS, S4KSGSZ
T32KNOTS, T32KSGSZ, T4KNOTS, T4KSGSZ

APAR PH62011 also expands the scope of the following existing DSNTXAZP actions:

UPDATE_LOG

Creates a new CLIST defaults member and updates it using the BSDS and active log settings only. The following DSNTIDxx entries (CLIST parameters) are updated:

LOGSPRE1, LOGSPRE2
BSDSNAM1, BSDSNAM2
VBSDSLOG
VOLSDAT6, DATACLS6, MGMTCLS6, STORCLS6
VOLSDAT7, DATACLS7, MGMTCLS7, STORCLS7
LOGSNUM

UPDATE_MVS_PARMLIB

This action creates a new CLIST defaults member and updates it using the current MVS parmlib settings only. The following DSNTIDxx entry (CLIST parameters) are updated: MVSSPREF, Start of change

SGRPATNM

UPDATE_ROUTINE

This action creates a new CLIST defaults member and updates it using the current routine settings only. The following DSNTIDxx entries (CLIST parameters) are updated:

AUTHID, SECDEFID
WLMENVG, WLMENVP, WLMENV1, WLMENVU, WLMENVX, WLMENVJ, WLMENVR, WLMENVD, WLMENVC, WLMENVM, WLMENVW
RTxnnACL, RTxnnPKO, RTxnnWLM
STOGJRT, STGIJRT

For more information, see the following related topics:

Allow binding of a location alias to a different IP address for a standalone Db2 subsystems

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

For more information, see the following related topics:

Enhance DSNTXAZP for automatic discovery of more Db2 subsystem attributes (phase 1)

In Db2 12, PH57613 (April 2024) enhances the DSTNXAZP tool with the capability to discover and collect the various attributes of a specified Db2 subsystem. The DSNTXAZP tool is executed when you run by job DSNTIJXZ to update the CLIST defaults input member in preparation for migration to Db2 13.

Specifically, DSNTXAZP is enhanced to collect the following attributes of a Db2 12 subsystem.

Attribute category	Settings
Application programming defaults	DSNHDECP (APPL DEFAULTS)
Authorization ID preferences for Db2-supplied routines, migration jobs, and IVP jobs	AUTHID (ROUTINES CREATOR) SECDEFID (SEC DEF CREATOR) INSSQLID (INSTALL SQL ID) INSPKOWN (INSTALL PKG OWNER) INSGRLST (INSTALL GRANTEE(S)) IVPSSQLID (IVP SQL ID) IVPPKOWN (IVP PKG OWNER) IVPGRLST (IVP GRANTEE(S))
Active Logs parameters	LOGSPRE1 (COPY 1 PREFIX) LOGSPRE2 (COPY 2 PREFIX)
Distributed Data Facility (DDF) parameters	DDLOC (DB2 LOCATION NAME) DDLUNAM (DB2 VTAM LUNAME) GENLUNM (DB2 GENERIC LUNAME) IPNAME (DB2 TCP/IP IPNAME) TCPPORT (TCP/IP PORT) SECPORT (SECURE PORT) RESYNPRT (RESYNC PORT)
Default WLM environment names for Db2-supplied routines	WLMENVG (FOR MOST DB2 ROUTINES) WLMENVP (FOR ROUTINES IDENTIFIED TO PROGRAM CONTROL) WLMENV1 (FOR SERIALIZED ROUTINES) WLMENVU (FOR DB2 UTILITIES ROUTINES) WLMENVX (FOR DB2 XML PROCESSING ROUTINES) WLMENVJ (FOR DB2 JAVA ROUTINES) WLMENVR (FOR DB2 REXX ROUTINES) WLMENVD (FOR UNIFIED DEBUGGER ROUTINES) WLMENVC (FOR THE DB2 CICS ROUTINE) WLMENVM (FOR DB2 MQSERIES ROUTINES) WLMENVW (FOR DB2 WEB SERVICES ROUTINES)
Access control list, package owner, and WLM application environment for Db2-supplied routines	RT`xnn`ACL (GRANT EXECUTE) RT`xnn`PKO (PACKAGE OWNER) RT`xnn`WLM (WLM ENV NAME) Where `x` is a letter B–Q and `nn` is numerals 01–44.

For more information, see the following related topics:

Detail information for a page with minimum LRSN that causes a GRECP recovery delay

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.

For more information, see the following related topics: