DSNL076I csect-name DDF CONNECTION REJECTED DUE TO INCOMPATIBLE APPLCOMPAT VALUES. LUWID=luw-id CLIENTAPPLCOMPAT=clientapplcompat-value PACKAGE APPLCOMPAT=package-applcompat-value PACKAGE=package THREAD-INFO=thread-information
Explanation
The remote client application environment specified an incorrect clientApplCompat value relative to the APPLCOMPAT value associated to the package being executed. This message is issued in conjunction with an SQLCODE -30025 CLIENTAPPLCOMPAT_INCONSISTENCY condition that is returned to the remote client application. For more information, see SQLCODE -30025.
- csect-name
- The name of the control section that issued the message.
- luw-id
- The logical unit of work ID of the thread.
- clientapplcompat-value
- The client application compatibility value that is provided by a client application:
- For applications that use Java drivers, clientapplcompat-value is the value of the clientApplcompat Connection or DataSource property for the connection to the Db2 for z/OS® data server.
- For applications that use other clients or drivers, such as the CLI driver, clientapplcompat-value is the value of the ClientApplCompat configuration keyword.
- package-applcompat-value
- The APPLCOMPAT bind option value for the package that was used to execute the first SQL statement in the application.
- package
- The collection ID, package name, and consistency token, delimited by a period (.), of the associated package.
- thread-information
- Information about the thread. The information is presented in a colon-delimited list that
contains the following segments:
- The primary authorization ID that is associated with the thread.
- The name of the user's workstation.
- The ID of the user.
- The name of the application.
- The statement type for the previously executed statement: dynamic or static.
- The statement identifier for the previously executed statement, if available. The statement identifier can be used to identify the particular SQL statement. For static statements, the statement identifier correlates to the STMT_ID column in the SYSIBM.SYSPACKSTMT table. For dynamic statements, the statement identifier correlates to the STMT_ID column in the DSN_STATEMENT_CACHE_TABLE table. That statement might not have contributed to the current failure.
- The name of the role that is associated with the thread.
- The correlation token that can be used to correlate work at the remote system with work
performed at the DB2 subsystem. The correlation token, if available, is enclosed in '<' and '>'
characters, and contains three components, separated by periods:
- A 3 - 39 character IP address.
- A 1 - 8 character port address.
- A 12 character unique identifier
An asterisk (*) in any segment indicates that the information is not available.
System action
An SQLCODE -30025 CLIENTAPPLCOMPAT_INCONSISTENCY condition is returned to the remote client application and the remote connection is terminated.
Operator response
Notify the system programmer for analysis.
System programmer response
Contact the database administrator for assistance. If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.
Problem determination
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- Query result of the SYSIBM.SYSPACKAGE catalog table for the collection ID (COLLID) and package name (NAME) values specified in the message.
Database administrator response
- Upgrade the client or driver. Refer to Setting application compatibility levels for data server clients and drivers for information
on required client driver levels. Tip: It is recommended that after you upgrade the client or driver, you set the client application compatibility level for the application to a value that is less than or equal to package-applcompat-value.
- If it is not yet possible to upgrade the client or driver, bind or rebind the client or driver
packages with the APPLCOMPAT value set to V12R1M500 or lower.
For drivers only, you can use the DSNTIJLC job to bind copies of the driver packages, or the DSNTIJLR job to rebind the driver packages, at the correct application compatibility level.
If you bind copies of the driver packages, you need to modify the configuration keyword or bind option that controls the current package set so that applications use the correct set of driver packages.
If clientapplcompat has a value other than * (asterisk), the clientapplcompat-value is greater than package-applcompat-value. clientapplcompat-value must be less than or equal to package-applcompat-value. Determine whether the remote client application uses any capabilities for which the minimum function level is greater than package-applcompat-value. Then take one of the following actions:
- If the remote client application does not use any capabilities that require a higher application compatibility setting, the remote client application compatibility setting should be set to package-applcompat-value.
- If the remote client application uses capabilities that require clientapplcompat-value, use a version of the IBM data server driver or client for which the package application compatibility is greater than or equal to clientapplcompat-value.
Query the SYSIBM.SYSPACKAGE catalog table to find existing IBM data server driver or client packages at the right application compatibility level. If no packages exist, bind or rebind driver or client packages. For drivers only, you can use the DSNTIJLC job to bind copies of the driver packages, or the DSNTIJLR job to rebind the driver packages, at the correct application compatibility level.
If you bind copies of the driver packages, the remote client must modify its configuration keyword or bind option that controls the current package set so that remote applications will use the correct set of driver packages.
For more information, see Setting application compatibility levels for data server clients and drivers.
Severity
0 (informational)
