A fix is available
APAR status
Closed as program error.
Error description
DB2DDF SQLCODE -30025 (and message DSNL076I) clientApplCompat failure condition may not be detected. NOTE: The service license package DB2LIC.SYSLIC is not validated against any client driver level or clientApplCompat property. Any APPLCOMPAT value is acceptable for the DB2LIC.SYSLIC package with all client driver levels. *************************************************************** Additional Symptoms and Keywords: SQLCODE -30025 SQLCODE30025 SQL30025N SRN30025 DSNL076I MSGDSNL076I clientApplCompat APPLCOMPAT
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Distributed Data Facility (DDF) users. * * Specifically applications which use the IBM * * Data Server Driver to access Db2 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: * * SQLCODE -30025 (EXECUTION FAILED * * BECAUSE FUNCTION IS NOT SUPPORTED BY * * THE SERVER WHICH CAUSED TERMINATION OF * * THE CONNECTION) and message DSNL076I * * (DDF CONNECTION REJECTED DUE TO * * INCOMPATIBLE APPLCOMPAT VALUES) are * * inconsistently or inaccurately * * issued for IBM Data Server Driver * * applications. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** Db2 validates client driver level and clientApplCompat property setting against the APPLCOMPAT value for driver packages to ensure the client application environment is compatible with the package being executed. When an incompatibility is detected, an SQLCODE -30025 and console message DSNL076I is issued. In some cases, a false incompatibility is detected, or not detected at all, because the package validated by Db2 does not reflect the package executed. This can happen when: - The currentPackagePath property is set in the application. - Profile table SPECIAL_REGISTER functionality is used to SET CURRENT PACKAGE PATH for the connection. These errors in validation occur because Db2 examines the package specified on the DRDA request instead of the package resolved after all special registers have been applied.
Problem conclusion
Db2 has been changed to validate driver level and clientApplCompat property setting after package resolution so that the actual package being executed is validated.
Temporary fix
Comments
×**** PE21/10/04 FIX IN ERROR. SEE APAR PH41055 FOR DESCRIPTION
APAR Information
APAR number
PH11251
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-04-18
Closed date
2020-05-14
Last modified date
2022-04-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI69503
Modules/Macros
DSNLXRSS DSNXEPM
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI69503
UP20/05/22 P F005
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]
Document Information
Modified date:
07 April 2022