PI74456: DB2 12 FOR Z/OS CONTINUOUS DELIVERY DDF RELATED CONSIDERATIONS
A fix is available
Closed as new function.
DB2DDF E26995 S28617 DB2 12 for z/OS Continuous Delivery DDF related considerations.
**************************************************************** * USERS AFFECTED: * * All Distributed Data Facility (DDF) users. * * DB2 12 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 12 for z/OS Continuous Delivery DDF related new * * function. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 12 for z/OS Continuous Delivery DDF related new function.
DDF related changes have been made to complement the DB2 12 for z/OS Continuous Delivery model. . DB2 now exchanges its current functional level with remote partners (requester or server). . After an explicit SQL CONNECT statement, the SQLCA SQLERRM field will contain the functional level of the DB2 for z/OS database (local or remote) where the application is currently connected. The value is provided only if the connected database is DB2 12 for z/OS with this change applied. This SQLCA SQLERRM information is in addition to the product level information that is already returned in the SQLCA SQLERRP field. . The Display Location command report will now provide a new DSNL209I message reflecting the functional level (for DB2 12 for z/OS requester or server partners) or the service/build level (for non DB2 for z/OS requester partners) related to the remote partner. The value is provided only if the remote partner provides this level of information. . IFCID 365 location statistics information will now provide the partner's functional/service/build level in a new QLSTPRLV field. The value is provided only if the remote partner provides this level of information. . IFCID 3 accounting information will now provide the partner's functional/service/build level in a new QLACPRLV field. The value is provided only if the remote partner provides this level of information. . DB2 now validates remote IBM Data Server driver applications with respect to their requested clientApplCompat value or maintenance level. If any errors are detected, SQLCODE -30025 will be returned, associated with a new 0600 reason code, and the client connection will be rejected. . New sample installation jobs, DSNTIJLC and DSNTIJLR, are provided to assist in performing a Bind (Copy) or Rebind of the IBM Data Server driver packages in order to conform to the desired APPLCOMPAT level required by the remote application. Messages and Codes changes are introduced to support the new function: . SQLCODE -30025 is changed. -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 format of product identifier values is pppvvrrm, where ppp is a 3-letter product code (such as DSN for DB2), vv is the version, rr is the release, and m is the modification level. For example, DSN12015 identifies DB2 12 after the activation of function level 500 or higher. The product code (ppp) is one of the following values: AQT for IBM® DB2 Analytics Accelerator for z/OS ARI for DB2 Server for VSE & VM DSN for DB2 for z/OS JCC for IBM Data Server Driver for JDBC and SQLJ QSQ for DB2 for i SQL for DB2 for Linux, UNIX, and Windows Modification (m) values have the following meanings: . Values '0', '1', '2', '3', and '4' identify modification levels of DB2 12 before new function is activated . Values '5', '6', '7', '8', and '9' identify modification levels after new function is activated. 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. 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. 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. . If identifier is in the format product-identifier:*:package-applcompat-value, a client application compatibility value was not set for the application, but package-applcompat-value is V12R1M501 or greater. clientapplcompat-value must be set when package-applcompat-value is V12R1M501 or greater. To fix the problem, first determine whether the client or driver is at a level that supports client application compatibility. Then take one of the following actions. . If the client or driver is at a level that supports client application compatibility, set the client application compatibility for the application to the value of package-applcompat-value. . If the client or driver is not at a level that supports client application compatibility, and it is possible to upgrade the client or driver, upgrade the client or driver. Then set the client application compatibility for the application to package-applcompat-value or less. . If the client or driver is not at a level that supports client application compatibility, and it is not yet possible to upgrade the client or driver, bind or rebind the driver packages with APPLCOMPAT set to V12R1M500 or less. 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 . Message DSNL209I is new. DSNL209I L209-FUNCTIONAL LEVEL=function-level Explanation This message follows a line of information in a DSNL200I message for a remote location, when the function level for the remote location is known. For descriptions of the message contents, see DSNL200I. The message number and subsystem recognition character are not included in this message. However, L209 is included in the message text to identify the message. System action Processing continues. Other necessary documentation changes, including support use information, regarding this function will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.
Reported component name
DB2 OS/390 & Z/
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
DSNXEDWA DSNLTAC1 DSNLCRTD DSNLSSST DSNLCDG1 DSNLXSR DSNLXRWA DSNIIEPL DSNLDUMP DSNLXRCM DSNLTACC DSNWVCST DSNLXRCN DSNLQCRP DSNWVCSP DSNLAGNT DSNX8EKG DSNLAGNX DSNWVZPS DSNLXRSQ DSNLTXAC DSNLCMSL DSNLXRSS DSNLXHOP DSNLXRSL DSNLTMIN DSNLXRBF DSNLTUOW DSNLXRFT DSNWAAPI DSNLZOSR DSNTXACT DSNWAFRR DSNTXSTB DSNLTCCN DSNLTCN2 DSNLTRAG DSNLQINA DSNLTCA2 DSNLTCA1 DSNLZREX DSNDQLAC DSNLTRN1 DSNWZDG2 DSNLDL DSNTLRAC DSNLTEX1 DSNTIJLC DSNFLDIR DSNWACDF DSNWAACT DSNXTAD DSNGEFLC DSNX8SMF DSNLZSEA DSNFCDIR DSNWDFDS DSNLZHC1 DSNLIRTR DSNLZHC0 DSNLCDP1 DSNLZHC2 DSNGEPLC DSNTIJLR DSNGEIEP DSNLZRPY DSNLDTI2 DSNLSSRB DSNLTPIF DSNLZOBO DSNLCTDR DSNLIINI DSNWDFDI DSNLXHCN DSNLQACT DSNXECNT DSNWVZSA DSNWARDS DSNWVSMT DSNB1TAD DSNLZR00 DSNLZR02 DSNLZRDT DSNLQXED DSNLTMSC DSNGEINT DSNWVAPR DSNWDST1 DSNLXRUW DSNLTEXC DSNLARAL DSNLCSRR DSNGEXLC DSNLIZLD DSNWVZIT DSNDQLST
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
Applicable component levels
RC10 PSY UI44780
UP17/03/15 P F703
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.