-30025 EXECUTION FAILED BECAUSE FUNCTION IS NOT SUPPORTED BY THE SERVER WHICH CAUSED TERMINATION OF THE CONNECTION: LOCATION `location` PRODUCT ID `identifier` REASON `reason-code` (`sub-code`)

Explanation
The current SQL statement failed because the SQL statement was routed to a server that does not
support the requested function. A new connection is required to allow the successful execution of
further SQL statements.

location-name

The name of the server that could not support the required database protocols to perform the
requested function.

identifier

A string in one of the following forms:
product-identifier

product-identifier:clientapplcompat-value:package-applcompat-value

product-identifier

An alphanumeric string that identifies the product.The product identifier (PRDID) value is an 8-byte character value in pppvvrrm format, where: ppp is a 3-letter product code; vv is the version;rr is the release; and m is the modification level. In Db2 12 for z/OS, the modification level indicates a range of function levels:
DSN12015 for V12R1M500 or higher.

DSN12010 for V12R1M100.

For more information, see Product identifier (PRDID) values in Db2 for z/OS.

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.

If the application does not provide a client application compatibility value, this value is
an asterisk (*).

package-applcompat-value

The APPLCOMPAT bind option value for the package that was used to execute the first SQL statement in the application. For more information, see the following topics: 
Application compatibility on Db2 for z/OS

Setting the Db2 for z/OS application compatibility for your JDBC and SQLJ applications

reason-code

A numeric value that identifies the function. Possible values are:

0010

LONG_STMTS

0020

LONG255_IDS

0030

EXTENDED_DESCRIBE

0040

EXTENDED_DIAGNOSTICS

0050

KEEP_DYNAMIC

0060

UNICODE_CONVERSION

0070

ROWSET_CURSOR

0080

DYNAMIC_SCROLLABLE_CURSOR

0090

FLEX_BLOCKING

0100

PACKAGE_PATH

0110

REOPT_ONCE

0120

REOPT_ALWAYS

0130

REOPT_NONE

0140

SCROLL_ORIENTATION

0150

DIV_SCALE

0160

QUERY_INSTANCE

0170

MULTIROW_INPUT

0180

SQL_ATTRIBUTES

0190

SQL_GET

0200

SET

0210

BIND_DEPLOY

0220

DUP_QUERY_SEMANTICS

0230

BINARY_XML_FORMAT

0240

BIND_DEPLOY_FUNCTION

0600

CLIENTAPPLCOMPAT_INCONSISTENCY

For
special instructions on actions to take when reason-code is 0600, see Database administrator response.

sub-code

A single-byte value that indicates how the error was detected in the network. If no additional
information is available, this value is 0. 

'01'x

The local Db2 that is acting as the
requester detected the error. The values that are provided for location-name and
product-identifier
identify the server in error.

'02'x

The server detected the error. The values that are provided for location-name
and product-identifier identify the location and level of the local Db2 server.

'03'x or '04'x

An intermediate server (hop site) detected the error. The values that are provided for
location-name and product-identifier identify
the server in error.

System action
The statement cannot be processed. The
current unit of work is rolled back. The SQLCA is formatted.

If
the reason-code is 0600, a companion DSNL076I message might also be issued to the
Db2 server system console.

Programmer response
Contact the database administrator for assistance in analyzing the SQL statement that prompted
this SQLCODE.

Problem determination
Use the reason-code value that was specified in the code to determine which
function was not supported. Use the sub-code value to further identify the
problem. 

Database administrator response

If
reason-code is 0600, use clientapplcompat-value and
package-applcompat-value to determine the cause of the error and fix the problem:

If identifier is in the format
product-identifier:clientapplcompat-value:package-applcompat-value,
clientapplcompat-value is greater than
package-applcompat-value. clientapplcompat-value must be less
than or equal to package-applcompat-value. Determine whether the 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 application does not use any capabilities that require a higher application compatibility
setting, change the client application compatibility setting to
package-applcompat-value.

If the 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 SYSIBM.SYSPACKAGES 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, 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.
See Setting application compatibility levels for data server clients and drivers for more information.

If identifier is in the
format
product-identifier:*:package-applcompat-value,
a client application compatibility value was not set for the application. In addition,
package-applcompat-value is greater than V12R1M500, and the client or driver is
not at a level that supports the package APPLCOMPAT level
package-applcompat-value. Take one of the following actions.
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, 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.

SQLSTATE

56073

-30025 EXECUTION FAILED BECAUSE FUNCTION IS NOT SUPPORTED BY THE SERVER WHICH CAUSED TERMINATION OF THE CONNECTION: LOCATION location PRODUCT ID identifier REASON reason-code (sub-code)

Explanation

System action

Programmer response

Problem determination

Database administrator response

SQLSTATE

-30025 EXECUTION FAILED BECAUSE FUNCTION IS NOT SUPPORTED BY THE SERVER WHICH CAUSED TERMINATION OF THE CONNECTION: LOCATION `location` PRODUCT ID `identifier` REASON `reason-code` (`sub-code`)