5740XYR00 DB2DDF DDF migration information relative to DB2 10 for z/OS. FOR INFORMATION REGARDING POTENTIAL MIGRATION ISSUES DUE TO INCOMPATIBLE CHANGES IN DB2 10, REFER TO THE FOLLOWING SECTIONS IN THE DB2 10 FOR Z/OS INSTALLATION AND MIGRATION GUIDE: . Application and SQL release incompatibilities for migration from Version 8 . Application and SQL release incompatibilities for migration from Version 9.1 MIGRATION ISSUES WITH APAR RESOLUTION: The following list of available maintenance is recommended for seamless migration to DB2 10 for z/OS. PM24292 To support the seamless migration of DB2 for z/OS data sharing members in a remote Sysplex workload balancing environment, the following client driver levels are recommended. . IBM Data Server Driver Package (ODBC, CLI, JDBC, SQLJ, ...) recommendation is to be at the Version 9.7 Fix Pack 6 or higher, or Version 10.1 Fix Pack 3 or higher, or Version 10.5 Fix Pack 3 or higher. PM33761 This APAR corrects the following symptom: An application using IBM Data Server Driver for JDBC and SQLJ Type 4 Connectivity calls a stored procedure with OUT or INOUT parameters on a DB2 for z/OS data sharing group in V8/V10 or V9/V10 coexistence mode and receives incorrect data output results (INCORROUT), or encounters various java.lang exceptions, including: - ArrayIndexOutOfBoundsException - NullPointerException - StringIndexOutOfBoundsException PM28500 This new function APAR provides Additional System Profile Monitoring support. There are additional profile filters added for system profile monitoring function in this APAR. These additional filters include: -- Client user ID, or -- Client application name, or -- Client workstation name, or -- Server location name or server location alias. This APAR also provides a default filter capability which helps users define a default profile threshold used to monitor all connections or all threads entering a DB2 server. PM17665 DB2 for z/OS server authorization processing, relative to remote (via DRDA) DB2 for z/OS client applications only, has been changed to behave consistently with the current behavior relative to remote non-DB2 for z/OS clients. This new server authorization behavior essentially represents more stringent authorization requirements that must now be met. PM37300 This APAR changes the authorization check at server for DB2 for z/OS to recognize secondary IDs from DB2 for z/OS requesters when Private Protocol is disabled. It also contains a new value for the existing ZPARM PRIVATE_PROTOCOL which allows plan owner based authorization while disallowing all private protocol behavior. PM26570 This APAR corrects the following symptom: Error message: CSV003I REQUESTED MODULE DBPROTOC NOT FOUND is issued when processing package or plan REBIND/BIND commands that were generated by DSNTP2DP (The Private Protocol to DRDA protocol REXX Catalog Analysis tool) via job DSNTIJPD. Alternatively, the following message is logged in the SYSTSPRT output destination: ***ERROR*** PACKAGES(06) processing terminated due to I/O error against OUTPKGS. PM27409 This APAR corrects the following symptom: ABEND=04E-00D3440D at DSNLIRTR+0CF4 and a subsequent DB2 04F subsystem abend. PM26077 This APAR corrects the following symptom: SQLCODE +204 or -204 returned from remote system during remote package bind for a reference to an object that should have been found on the requester system. PM40872 / UK69946 PREPARATION FOR APAR PM42237 PM42237 / UK69950 An application using IBM Data Server Driver for JDBC and SQLJ Type 4 Connectivity calls a stored procedure with OUT or INOUT parameters on a DB2 for z/OS data sharing group in V9/V10 or V8/V10 coexistence mode and receives incorrect data output results or encounters various java.lang exceptions, including: - ArrayIndexOutOfBoundsException - NullPointerException - StringIndexOutOfBoundsException See the closing text for APAR PM42237 for more information. PM54662 After a DB2 for z/OS database server is migrated to Version 10, a .NET application using the IBM Data Server driver calls a stored procedure on the migrated server. The CALL fails with the CLI error message CLI0102E, indicating the conversion between the parameter type in the stored procedure declaration and the argument type specified in the application's CALL statement is not supported by the driver. The .NET application did not encounter this error before the DB2 server was migrated to V10. PM79161 Required to use IBM Data Server Driver Package at Version 10.5 or higher. PM77180 Provide the pre-v10 behavior when the DDF_COMPATIBILITY ZPARM is set for the IBM Data Server Driver for non-JAVA clients for a remote Stored Procedure call. PM94719 Provides IFCID 366 tracing to ensure customers know they are going through a path that depends on DDF_COMPATIBILITY setting. PM86374 SQLCODE -420 due to unsupported DB2 10 NFM implicit casting of invalid character data relative to IBM Data Server Driver related applications. Also see IBM Data Server Driver APAR IC92430. IC71055 The following DRDA exception may occur for IBM Data Server Driver for JDBC and SQLJ requesters when connecting to a DB2 10 for z/OS server under compatibility mode CM8 or CM9. It is recommended that IBM Data Server Driver APAR IC71055 be applied to correct this issue. See APAR IC71055 for more information. . DSNL032I DRDA EXCEPTION CONDITION with REASON=00D35B16 and ERROR ID=DSNLZSDT002C may occur at a DB2 10 for z/OS CM8 or CM9 server where the IFCID=0191 trace record indicates that an SQLDTA object with invalid data type of NFDP (x'BB') is received. This datatype is not supported until the DB2 10 for z/OS server is at NFM level. PM99142 SQLCODE -4700 is returned to the end user application when a DB2 10 NFM requester flows the prepare statement attribute 'WITH EXTENDED INDICATORS' to a downstream server which doesn't support this statement attribute. An example of a downstream server that does s not support this attribute is DB2 10 CM. The problem can occur using JCC Type 2 driver for z/OS (when it connects to local DB2 and hops out) or JCC Type 4 driver (when it connects to a remote DB2 and hops out). PM96295 PM96293 Timestamp with Timezone related conditions. All z/OS Connectivity: DB2 V10 NFM or higher server supports TIMESTAMP with TIME ZONE type. When application sends data like 9999-12-31 23:59:59.0 to a timestamp column into these DB2 servers, SQLCODE181(-181) may occur. This is because by default the driver was sending TIME ZONE information to the server. In the boundary values case, the server is not able to process it. With the current fix, the driver is NOT sending TIME ZONE information to theserver if the date part is 9999-12-31 or 0001-01-01.(RTC 37158) PI04839 PI05569 IC96609 Timestamp with Timezone related conditions. PM92838 Disable implicit cast relative to remote JCC environments.
Reported component name
PB LIB INFO ITE
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following: