1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES READY %COVRLETR WDB2I.R.DB2101S.SMPPTS IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED UK79840 COVER LETTER START PROBLEM DESCRIPTION(S): PM51241 - **************************************************************** * USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE * * command. * **************************************************************** * PROBLEM DESCRIPTION: The -DISPLAY DATABASE command * * displayed INCORROUT STATUS field * * values for the final summary line of * * partitioned table spaces and indexes. * **************************************************************** * RECOMMENDATION: * **************************************************************** The -DISPLAY DATABASE command could display INCORROUT STATUS field values for the final summary line of partitioned objects because the only valid or relevant STATUS field values for an entire partitioned object are: blank, DBETE or DBETE,RECP. The -DISPLAY DATABASE command was changed to only display the following possible valid or relevant STATUS field values: blank, DBETE or DBETE,RECP. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51241 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: Since the -DISPLAY DATABASE command could have displayed INCORROUT STATUS field values for the final summary line of partitioned objects any programs or processes that use that field need to understand that the only valid or relevant STATUS field values for the entire final summary line of partitioned object are: blank, DBETE or DBETE,RECP The DSNT397I message was updated to describe the final summary line for partitioned objects and their possible valid or relevant STATUS field values: blank, DBETE or DBETE,RECP. DOCUMENTATION: The fix for APAR PM25652, introduces a new special option, RRTHashOvrFlwRatio. The Utility Guide and Reference and The Application Programming Guide documentation on DSNACCOX will have a new description of RRTHashOvrFlwRatio as follows: Syntax: -|---+---' '--------------+---|- +-RRTHashOvrFlwRatio-+ '- -1 ---------------' Description: RRTHashOvrFlwRatio 1 Specifies a criterion for recommending that the REORG utility is run on a table space. If the following conditions are true, DSNACCOX recommends running REORG: - The hash access overflow index is being used for access. - The number of hash access overflow index entries divided by the total number of rows (expressed as a percentage) is greater than RRTHashOvrFlwRatio. RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The default value is ' 15'. A plus sign (+) preceding or following the value, or a plus sign by itself indicates that the DSNACCOX stored procedure returns the calculated ratio value in the result set. A negative value indicates that the criterion is not used. The ratio of hash access overflow index entries to the total number of rows is returned in column RRTHashOvrFlwRatPCT of the result set. Figure 4. DSNACCOX formula for recommending a REORG on a table space has an additional criteria: (((QueryType='REORG' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL')) AND (REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR (NACTIVE IS NULL OR NACTIVE > 5) AND ((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND REORGINSERTS > RRTInsertsAbs) OR (((REORGDELETE x 100) / TOTALROWS > RRTDeletesPct) AND REORGDELETE > RRTDeleteAbs) OR (REORGCLUSTERSENS > 0 AND (REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR ((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR | (Object is not using hash organization and ((SPACE x 1024) / RRTDataSpaceRat)) OR ((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS > RRTIndRefLimit) OR REORGMASSDELETE > RRTMassDelLimit OR EXTENTS > ExtentLimit) OR | ((QueryType='REORG' OR QueryType='ALL') AND | ObjectType='ALL' * AND | Overflow index hash access is used**, AND | ((overflow index TOTALENTRY x 100) / TOTALROWS > RRTHashOvrFlwRatio)) OR ((QueryType='RESTRICT' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL') AND The table space is in advisory or informational reorg pending status) |Note: | * ObjectType='ALL' must be specified to use this criteria. | for this criterion to be used. If ObjectType='TS' or | ObjectType='IX' is specified, and '+' is specified for | RRTHashOvrFlwRatio, an error message is issued. If | ObjectType='TS' or ObjectType='IX' is specified, and | '+' is not specified for RRTHashOvrFlwRatio, this 1 | criterion is not used. | ** The overflow index is used when SYSINDEXES.HASH ='Y' AND | SYSINDEXSPACESTATS.REORGINDEXACCESS > 0. Add the following table entry to table for the "DSNACCOX OUTPUT" section. Result set row for second DSNACCOX result set ---------------------------------------------------------------- |Column name | Data type |Description | ---------------------------------------------------------------- |RRTHashOvrFlwRatPCT| Double |This is an optional column, | | | |and it is being returned when | | | |there is a plus (+) sign in | | | |the RRTHashOverFlwRatio. | | | | | | | |If OBJECTTYPE is ALL and REORG| | | |is YES, the ratio of Hash | | | |Access overflow index entries | | | |to the total number of rows, | | | |expressed as a percentage. | | | |Otherwise null. | | | | | | | |If the ratio of Hash Access | | | |overflow index entries to the | | | |total number of rows does not | | | |exceed the value specified for| | | |RRTHashOvrFlwRatio or meet the| | | |criteria requirement, this | | | |value is null. | ---------------------------------------------------------------- ACTION: ***Action for PM28652: See PM28652 APAR/PTF text for additional information. <<<<<<> Post-apply actions after applying the fix for APAR PM28652: (a) STOP PROC(SYSPROC.DSNACCOR) to suspend DSNACCOR activity (b) Rebind package for DSNACCOR. An example on how to do this is BIND PACKAGE(DSNACCOR) MEMBER(DSNACCOR) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOR) to resume DSNACCOR activity ACTION: Post-apply actions after applying the fix for APAR PM25652: (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity (b) Rebind package for DSNACCOX. An example on how to do this is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSN@CCOR PM51241 DSN@CCOX PM51241 DSNACCOR PM51241 DSNACCOX PM51241 DSNTDMUL PM51241 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51241 DSN@CCOR DSN@CCOX DSNACCOR DSNACCOX DSNTDMUL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACCOR DSNACCOX DSNTDMUL MACROS DSN@CCOR DSN@CCOX LISTEND UK79840 COVER LETTER END UK81128 COVER LETTER START PROBLEM DESCRIPTION(S): PM67213 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the DB2-supplied stored procedure * * SYSPROC.ADMIN_TASK_ADD. * **************************************************************** * PROBLEM DESCRIPTION: When a user calls the stored procedure * * SYSPROC.ADMIN_TASK_ADD multiple times * * specifying a PassTicket and the same * * user ID (under which the new task is * * performed), the specified user ID * * might be revoked. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** Currently, the password verification logic in SYSPROC.ADMIN_TASK_ADD causes a password violation to occur for the specified user if the specified password is a PassTicket. This causes the specified user ID to keep incurring a password violation each time ADMIN_TASK_ADD is called with a PassTicket, until the specified user's number of password violations exceeds the "maximum number of password attempts" allowed by the system, at which point the specified user's ID is revoked. The password verification logic in SYSPROC.ADMIN_TASK_ADD is modified to avoid incurring a password violation when a PassTicket is used. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67213 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF modifies the DB2 scheduler for administrative tasks so that a user can add a scheduler task using a PassTicket without the user ID under which the task execution is performed incurring a password violation. The following post-apply actions are required of all current DB2 10 for z/OS customers to activate the changes in this PTF: (1) Stop the DB2 scheduler for administrative tasks. (2) Start the DB2 scheduler for administrative tasks. Each of these actions is detailed below. (1) If the DB2 scheduler is running, stop it first by executing the following console command: MODIFY DSNADMT,APPL=SHUTDOWN where DSNADMT is the name of the scheduler. (2) To start the DB2 scheduler again, execute the following console command: START DSNADMT where DSNADMT is the name of the scheduler. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNA6II PM67213 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67213 DSNA6II THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNA6II LISTEND UK81128 COVER LETTER END UK81181 COVER LETTER START PROBLEM DESCRIPTION(S): PM66489 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users that have applied * * UK77572 or UK77576 * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC010 in exit ICHRAU03 or * * ABEND0C4 RC04 in exit DSNX@XAC may * * occur when Access Control * * Authorization Exit (DSNX@XAC) is * * being used and PTF UK77572 or UK77576 * * is installed. * **************************************************************** * RECOMMENDATION: * **************************************************************** If APAR PM53629 PTFs UK77572(V10) or UK77576(V9) is installed and the RACF DB2 Access Control Authorization Exit (DSNX@XAC) is installed, an ABEND0C4 RC010 in exit ICHRAU03 or ABEND0C4 1 RC04 in exit DSNX@XAC may occur when using IFI interface to execute a DB2 command on a remote member of a datasharing group. This occurs because an incorrect home ASID is used to process authorization checking. DB2 code has been updated to use the correct home ASID for remote IFI command authorization COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66489 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWAAPI PM66489 DSNWACDF PM66489 DSN9SCNP PM66489 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66489 DSNWAAPI DSNWACDF DSN9SCNP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWAAPI DSNWACDF DSN9SCNP LISTEND UK81181 COVER LETTER END UK81198 COVER LETTER START PROBLEM DESCRIPTION(S): PM69372 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of DSNACCOR stored procedure with * * a non catalog tablespace named SYSRTSTS. * **************************************************************** * PROBLEM DESCRIPTION: DSNT408I SQLCODE = -204, ERROR: * * SYSIBM.TABLESPACESTATS IS AN UNDEFINED * * NAME during DSNACCOR stored procedure. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** DSNACCOR stored procedure failed with MSGDSNT408I SQLCODE204 ERROR: SYSIBM.TABLESPACESTATS IS AN UNDEFINED NAME when checking if Real Time Statistics had been migrated to the catalog. DSNACCOR prepares a SELECT IBMREQD from SYSTABLESPACE with name='SYSRTSTS' expecting one row to be returned. In this case, there were two rows that existed. There were two table spaces named SYSRTSTS, a user table space and the catalog 1 table space, DSNDB06.SYSRTSTS, which was not the first row returned in the select. An additional condition should be included on the SELECT to ensure the correct row is returned. DSNACCOR has been modified to SELECT IBMREQD for the catalog data base name DSNDB06 and SYSRTSTS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69372 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@CCOR PM69372 DSNACCOR PM69372 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69372 DSN@CCOR DSNACCOR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACCOR MACROS DSN@CCOR LISTEND UK81198 COVER LETTER END UK81336 COVER LETTER START PROBLEM DESCRIPTION(S): PM68690 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using secondary * * authorization IDs with installation * * SYSADM or installation SYSOPR authority * * for executing START, STOP or DISPLAY * * DATABASE commands. * **************************************************************** * PROBLEM DESCRIPTION: DSNT300I message received for START * * DATABASE command when secondary * * authorization ID had installation * * SYSOPR authority. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNT300I message received for START DATABASE command when secondary authorization ID had installation SYSOPR authority. This occurred because DB2 did not consider secondary authorization IDs associated with the installation SYSOPR authority, during authorization check. This message can also be received for STOP or DISPLAY DATABASE commands when secondary authorization ID has installation SYSOPR and for START, STOP or DISPLAY DATABASE 1 commands when secondary authorization ID has installation SYSADM authority. DB2 code has been corrected to include the secondary authorization IDs associated with installation SYSADM and installation SYSOPR authorities during authorization check for above mentioned commands. ADDITIONAL KEYWORDS: DSNT300I STOP START DISPLAY SYSADM SYSOPR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68690 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTDMI PM68690 DSNUECM4 PM68690 DSNUVARS PM68690 DSNXIASQ PM68690 DSNXIDPL PM68690 DSNXI14 PM68690 DSNZCMD1 PM68690 DSN9SCNP PM68690 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68690 DSNTDMI DSNUECM4 DSNUVARS DSNXIASQ DSNXIDPL DSNXI14 DSNZCMD1 DSN9SCNP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTDMI DSNUECM4 DSNUVARS DSNXIASQ DSNXIDPL DSNXI14 DSNZCMD1 DSN9SCNP LISTEND UK81336 COVER LETTER END UK81866 COVER LETTER START PROBLEM DESCRIPTION(S): PM67319 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of REORG REBALANCE with a fieldproc defined * * on a CHAR data type partitioning key. * **************************************************************** * PROBLEM DESCRIPTION: LIMITKEY in SYSIBM.SYSTABLEPART is not * * in external format after a REORG * * REBALANCE on a table where the CHAR * * partitioning key has a FIELD PROCEDURE * 1 * defined on it. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A REORG REBALANCE was executed on a partitioned table space, where a FIELDPROC was defined on a CHAR partitioning key of the table. The new LIMITKEY inserted into SYSTABLEPART was in internal format, instead of external format, and was not fieldproc decoded. Code has been modified to decode a CHAR LIMITKEY during a REORG REBALANCE utility. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67319 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM42922: See PM37611 APAR/PTF text for additional information. PM42922 is a pre-conditioning APAR that includes changes to support a new function that will be enabled via PM37611. At this time, all of the changes are transparent to the user. In a data sharing group, this pre-conditioning APAR should be applied to all members before the enabling APAR, PM37611, is applied. The new function is not enabled until PM37611 is PM37611 removes the restriction and allows a timestamp with time zone column in a partitioning key as long as it is the last column in the partitioning key. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUDALT PM67319 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67319 DSNUDALT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUDALT LISTEND UK81866 COVER LETTER END UK81876 COVER LETTER START PROBLEM DESCRIPTION(S): PM69204 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users * * of RLF reactive governing * **************************************************************** * PROBLEM DESCRIPTION: Dynamically changed RLFERR / RLFERRD * * install parameter values are not * 1 * applied for RLF reactive governing * * until RLF is restarted after those * * parameter changes. * **************************************************************** * RECOMMENDATION: * **************************************************************** RLF applies RLFERR and RLFERRD install parameter values as ASUTime limit for dynamic SQLs in a local thread and a remote thread respectively for reactive governing when no applicable row for the thread is found from either DSNRLMTxx table nor DSNRLSTxx table. . In the reported case, when those install parameter values are changed dynamically and RLF is not restarted, the updated values were not applied for reactive governing. DB2 has been changed to support dynamic changes of RLFERR and RLFERRD install parameter values for RLF reactive governing even when RLF is not restarted after those changes. This APAR change also includes a fix of the incorrect use of RLFERR install parameter value for a remote thread when DSNRLMTxx table is not created and no applicable row for the thread is found from DSNRLSTxx table. Additional Keywords: ASUTIMELIMIT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69204 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: BEFORE APPLYING THIS PTF, DYNAMIC SQLS COULD GET SQLCODE -905 OR BE PROCESSED WITHOUT SQLCODE -905 BASED ON THE ASUTIME FROM THE ROW WITH 'PUBLIC' LUNAME EVEN WHEN A MORE QUALIFIED ROW EXISTS IN DSNRLSTxx TABLE. AFTER APPLYING THIS PTF, DYNAMIC SQLS WOULD GET SQLCODE -905 OR BE PROCESSED WITHOUT SQLCODE -905 BASED ON THE ASUTIME FROM THE ROW WITH THE MOST QUALIFIED LUNAME COLUMN VALUE IN DSNRLSTxx TABLE. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTCPRE PM69204 DSNTCRCI PM69204 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69204 DSNTCPRE DSNTCRCI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTCPRE DSNTCRCI LISTEND UK81876 COVER LETTER END 1 UK81892 COVER LETTER START PROBLEM DESCRIPTION(S): PM70534 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS or DB2 10 for z/OS users * * of REORG utility * **************************************************************** * PROBLEM DESCRIPTION: Serviceability * **************************************************************** * RECOMMENDATION: Apply PTF when available * **************************************************************** Serviceability. Serviceability. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70534 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGALT PM70534 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70534 DSNUGALT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGALT LISTEND UK81892 COVER LETTER END UK81895 COVER LETTER START PROBLEM DESCRIPTION(S): PM68486 - **************************************************************** * USERS AFFECTED: Users of DB2 10 for z/OS with subsystem * * parameter IMPTKMOD=NO and either LOB * * table spaces or table spaces in work file * * databases. * **************************************************************** * PROBLEM DESCRIPTION: When subsystem parameter IMPTKMOD=NO, * * SYSTABLEPART.TRACKMOD may incorrectly * * be set to 'N' for LOB table spaces * * and table spaces in work file * * databases. * **************************************************************** * RECOMMENDATION: * **************************************************************** When subsystem parameter IMPTKMOD=NO, SYSTABLEPART.TRACKMOD may incorrectly be set to 'N' for LOB table spaces and table spaces in work file databases. The TRACKMOD value should be blank. The table space must be dropped and recreated in order to correct 1 the TRACKMOD value. However, correcting the value is not necessary since it does not affect DB2 functionality. Subsystem parameter IMPTKMOD=NO will no longer result in SYSTABLEPART.TRACKMOD = 'N' for LOB table spaces and table spaces in work file databases. This apar will not fix existing table spaces that incorrectly have SYSTABLEPART.TRACKMOD = 'N'. This does not affect DB2 functionality. ADDITIONAL KEYWORDS: SQLCREATE SQLALTER SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68486 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXICTS PM68486 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68486 DSNXICTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICTS LISTEND UK81895 COVER LETTER END UK81897 COVER LETTER START PROBLEM DESCRIPTION(S): PM70943 - **************************************************************** * USERS AFFECTED: All DB2 9 and and DB2 10 for Z/OS * * users that use views with UNION ALL * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC38 AT * * LOC=DSNXGRDS.DSNXOP0 +1CCA * * could happen for a query satisfying * * the following conditions: * * 1. The query references a view that * * contains UNION ALL * * 2. The view select list contains * * AS name and aggregate function. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC38 AT LOC=DSNXGRDS.DSNXOP0 +1CCA could happen for a query satisfying the following conditions: 1 1. The query references a view that contains UNION ALL 2. The view select list contains AS name and aggregate function. Example: CREATE TABLE T1(T1C1 INT, T1C2 INT); CREATE TABLE T2(T2C1 INT, T2C2 INT); CREATE TABLE T3(T3C1 INT, T3C2 INT); CREATE VIEW V1 AS SELECT T3C1 ,0 AS SUM_TIG ,0 AS SUM_GG0 ,SUM(TXC2) AS SUM_BIN FROM T3, ( SELECT T1C1, T1C2 FROM T1 UNION ALL SELECT T2C1, T2C2 FROM T2 ) TX(TXC1,TXC2) WHERE T3C1 = TXC1 AND T3C1 = 0 GROUP BY T3C1; SELECT * FROM V1; The abend occurs because DB2 did not handle the AS name correctly. DB2 is fixed to handle the AS name correctly when the view is referenced. Additional Keywords: SQLUNIONALL SQLVIEW SQLTABLEEXPR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70943 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOP0 PM70943 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70943 DSNXOP0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOP0 LISTEND UK81897 COVER LETTER END UK81929 COVER LETTER START PROBLEM DESCRIPTION(S): PM70091 - **************************************************************** * USERS AFFECTED: All DB2 10 users running with DB2 trace * * IFCID 318 activated * **************************************************************** 1 * PROBLEM DESCRIPTION: V10 ABEND 04E RC00E20018 AT DSNSTKGG+ * * 0AFC when when IFI READS request was * * issued for IFCID 317. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 processes the READS request for IFCID 317 and the DB2 system parameter (or zparm ) DSN6SYSP.UIFCIDS set to NO, DB2 acquires stack storage to convert the SQL statement text from UNICODE to EBCDIC to insert into the trace records. When the requested storage buffer size exceeds 512K bytes, DB2 stack storage is unable to accommodate it, resulting in the reported intentional DB2 application abend for exceeding DB2 stack storage. DB2 code has been modified to allocate storage from GETMAIN storage instead of DB2 stack storage when converting SQL statement text to EBCDIC for insertion into trace IFCID 317. RELATED KEYWORDS: SQLSTORAGE IFCID318 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70091 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECST PM70091 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70091 DSNXECST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECST LISTEND UK81929 COVER LETTER END UK81974 COVER LETTER START PROBLEM DESCRIPTION(S): PM70145 - **************************************************************** * USERS AFFECTED: All DB2 users who ALTER TRIGGER. * **************************************************************** * PROBLEM DESCRIPTION: After a trigger is altered, customer * * may receive the following REPAIR DBD * * errors, * * * * DSNU920I DSNUEDTG OBDS DIFFER AT * * OFFSET X'00000068' OBDTGALTEREDTS * * DSNU904I DSNUEDTG - * * EXISTING VALUE X'0000000000000000' * * DSNU904I DSNUEDTG - * 1 * EXISTING VALUE X'0000' * * DSNU905I DSNUEDTG - * * REBUILT VALUE X'2011030810261181' * * DSNU905I DSNUEDTG - * * REBUILT VALUE X'8370' * * DSNU913I DSNUEDDR - OBD X'000D' * * COMPARISON COMPLETE -- 1 ERRORS WERE * * FOUND * * * * or * * * * DSNU920I DSNUEDTG OBDS DIFFER AT * * OFFSET X'00000068' OBDTGALTEREDTS * * DSNU904I DSNUEDTG - EXISTING VALUE * * X'2012080110063477' * * DSNU904I DSNUEDTG - EXISTING VALUE * * X'8185' * * DSNU905I DSNUEDTG - REBUILT VALUE * * X'2012080110072584' * * DSNU905I DSNUEDTG - REBUILT VALUE * * X'7914' * * DSNU913I DSNUEDDR - OBD X'0005' * * COMPARISON COMPLETE -- 1 ERRORS WERE * * FOUND * * * **************************************************************** * RECOMMENDATION: * **************************************************************** When ALTER TRIGGER, DB2 does not write out the changed trigger OBD in DASD, as a result, the above repair dbd error is reported. DB2 has been changed to write out trigger OBD. Applying this apar will not fix incorrect trigger OBD which was introduced before. Alter trigger will have the broken field fixed. Additional keyword: SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70145 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDATG PM70145 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70145 DSNGDATG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDATG LISTEND 1UK81974 COVER LETTER END UK82110 COVER LETTER START PROBLEM DESCRIPTION(S): PM68697 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of DSN1COMP * **************************************************************** * PROBLEM DESCRIPTION: When running DSN1COMP against a UTS, * * the following may occur erroneously: * * + DSN1990I message, Code = 'C14'X * * + DSN1990I message, Code = 'C15'X * **************************************************************** * RECOMMENDATION: * **************************************************************** When DSN1COMP is run on a Universal Table Space (UTS), it may produce the following MSGDSN1990I messages erroneously: DSN1990I DSN1CPGD BROKEN PAGE. PAGE NUMBER = 00100002. REASON: ID-MAP ENTRY FOR A RECORD IS FREE. SERVICE INFO: CODE= 'C14'X ... DSN1990I DSN1CPGD BROKEN PAGE. PAGE NUMBER = 00100002. REASON: ID-MAP DOES NOT POINT TO THE RECORD. SERVICE INFO: CODE= 'C15'X ... DSN1COMP has been modified to prevent DSN1990I messages with Code='C14'x or Code='C15'x for a UTS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68697 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN1COMP PM68697 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68697 DSN1COMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN1COMP LISTEND UK82110 COVER LETTER END UK82112 COVER LETTER START PROBLEM DESCRIPTION(S): PM71143 - **************************************************************** * USERS AFFECTED: All db2 v10 user when running a * * UPDATE/DELETE/MERGE statement with target * 1 * table is accessed via index. * **************************************************************** * PROBLEM DESCRIPTION: When LOCKSIZE is not table space, * * UPDATE/DELETE/MERGE statement(s) may be * * failed with RS00C90096 (number of page * * locks reached numlkus install limit) if * * target table is accessed with index and * * there is residual predicates existed. * * The failure is because non-fully * * qualified rows are locked and lead to * * RS00C90096. * **************************************************************** * RECOMMENDATION: * **************************************************************** When LOCKSIZE is not table space, UPDATE/DELETE/MERGE statement(s) may be failed with RS00C90096 (number of page locks reached numlkus install limit) if target table is accessed with index and there is residual predicates existed. The failure is because non-fully qualified rows are locked and lead to RS00C90096. The following query is an example of a failing case. CREATE INDEX I1 ON T1(C2); DELETE FROM T1 WHERE C2=2 AND EXISTS (SELECT * FROM T2); The bindtime code in DB2 is modified to correct the failing condition. Additional keyword: SQLLOCK SQLUPDATE SQLDELETE SQLMERGE 00C90096 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71143 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PK71143 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PK71143 corrects a problem that can cause RS00C90096 (number of page locks reached numlkus install limit) being issued for an update/delete/merge statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMS PM71143 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM71143 DSNXOMS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMS LISTEND UK82112 COVER LETTER END UK82113 COVER LETTER START PROBLEM DESCRIPTION(S): PM68901 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for * * z/OS who use DSNREXX. * **************************************************************** * PROBLEM DESCRIPTION: DSNTZEXE may cause an ABEND0C4 in * * IRXELOAD * **************************************************************** * RECOMMENDATION: * **************************************************************** When a large variable is used as input to an EXECUTE IMMEDIATE or a PREPARE SQL statement in a DSNREXX program, IRXELOAD may abend with an ABEND0C4. DSNREXX is updated to prevent the abend ABEND0C4. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68901 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTZEXE PM68901 DSNTZPRP PM68901 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68901 DSNTZEXE DSNTZPRP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTZEXE DSNTZPRP LISTEND UK82113 COVER LETTER END UK82167 COVER LETTER START PROBLEM DESCRIPTION(S): PM69701 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** 1 * PROBLEM DESCRIPTION: Recieved ABEND04E in DSNGERBK:501E * * followed by ABEND04E in DSNITCUS:5002. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E in DSNGERBK:501E RC00C90101 occured followed by ABEND04E in DSNITCUS:5002. The abend in DSNGERBK is a diagnostic abend used to collect information and then allow processing to continue. After the dump was collected internal control blocks where not reset and this can cause the abend in DSNITCUS. The code has been updated to reset the internal control block when the diagnostic information has been collected. This APAR does not fix the ABEND in DSNGERBK ERQUAL501E. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69701 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGECHK PM69701 DSNGEDFR PM69701 DSNGEDLC PM69701 DSNGEGFB PM69701 DSNGERBK PM69701 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69701 DSNGECHK DSNGEDFR DSNGEDLC DSNGEGFB DSNGERBK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGECHK DSNGEDFR DSNGEDLC DSNGEGFB DSNGERBK LISTEND UK82167 COVER LETTER END UK82179 COVER LETTER START PROBLEM DESCRIPTION(S): PM65392 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users who use dynamic * * caching attributes. * **************************************************************** * PROBLEM DESCRIPTION: A CREATE TABLESPACE statement is * * timeout'ed on a specific DBD lock with * * the reason of 00C9008E when a LOAD * * utility with INCURSOR option is running * 1 * concurrently. * **************************************************************** * RECOMMENDATION: * **************************************************************** A lock timeout error occurs between the CREATE TABLESPACE statement and the LOAD utility with INCURSOR option. The CREATE job attempts to acquire a DBD lock in X mode, but the LOAD with INCURSOR job has held the DBD lock in S mode. The LOAD job should not acquire the DBD lock since it has a dynamic caching attribute. DB2 code is changed to check the dynamic caching attribute properly and would skip the DBD lock if is necessary. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65392 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBCTD PM65392 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65392 DSNIBCTD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBCTD LISTEND UK82179 COVER LETTER END UK82182 COVER LETTER START PROBLEM DESCRIPTION(S): PM65051 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS OF RECOVER UTILITY FROM CONCURRENT * * COPY * **************************************************************** * PROBLEM DESCRIPTION: RECOVER UTILITY WITH PARALLEL * * SPECIFIED DOES NOT CORRECTLY HANDLE * * DFSMSdss FAILURE DURING RESTORE FROM * * CONCURRENT COPY, ALLOWING JOB TO * * CONTINUE, OR CAUSING INFINITE LOOP * **************************************************************** * RECOMMENDATION: * **************************************************************** When running RECOVER utility with PARALLEL specified, if there is a failure in DFSMSdss while attempting to restore a CONCURRENT COPY, the RECOVER job does not properly recognize and process that failure. In DB2 9, this results in an infinite loop for the RECOVER job. In DB2 10, the job will continue and in some cases complete with RC0 despite the object not being correctly recovered. 1 Note that these issues will not be seen unless BOTH of the following are true: - The failing restore is from a CONCURRENT COPY, and - The RECOVER utility is run with the PARALLEL option. Code was changed in RECOVER utility to take appropriate action when it detects a failure in DFSMSdss. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65051 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCBMT PM65051 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65051 DSNUCBMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBMT LISTEND UK82182 COVER LETTER END UK82223 COVER LETTER START PROBLEM DESCRIPTION(S): PM71848 - **************************************************************** * USERS AFFECTED: ALL DB2 10 FOR z/OS USERS OF COPY UTILITY * * SHRLEVEL REFERENCE ON VERY LARGE LISTS OF * * OBJECTS * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E40022 MSGDSNT500I * * RC00C90096 (MAXIMUM NUMBER OF LOCKS * * EXCEEDED) DURING COPY UTILITY ON * * A LARGE LIST OF OBJECTS IN NEW * * FUNCTION MODE * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran a COPY utility job on a large number of objects in New Function Mode (NFM) and it failed with . DSNT500I DSNUGBAC - RESOURCE UNAVAILABLE REASON 00C90096 TYPE 00000302 NAME DSNDB01 .SYSUTILX.X'000003' DSNU017I DSNUGBAC - UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED, REASON=X'00E40022' . This was because the installation-defined maximum number of locks (NUMLKUS) was exceeded by the COPY job. Note that the RESOURCE UNAVAILABLE message preceding the 1 abend could indicate either SYSUTILX or SYSCOPY, and another symptom of this problem could be messages or abends indicating that the maximum number of locks against either of these objects (NUMLKTS) has been exceeded. This problem is much more likely to occur with SHRLEVEL REFERENCE than with SHRLEVEL CHANGE, and usually only with very large lists, approaching 10000 objects or more. COPY utility was changed not to have certain locks count against the maximum lock threshold, allowing larger lists to be copied. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71848 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBADR PM71848 DSNUBAII PM71848 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71848 DSNUBADR DSNUBAII THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBADR DSNUBAII LISTEND UK82223 COVER LETTER END UK82265 COVER LETTER START PROBLEM DESCRIPTION(S): PM70395 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * contain an INLIST predicate with hostvars. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc00E70005 can occur at * * location DSNXGINB M621 or at DSNXRFF * * M931, or an ABEND0C4 rc4 can occur at * * location DSNIRNXT +308 (OFFSET308) for * * a query that contains an INLIST * * predicate that includes hostvars. The * * column is nullable. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc00E70005 can occur at location DSNXGINB M621 or at DSNXRFF M931, or an ABEND0C4 rc4 can occur at location DSNIRNXT +308 (OFFSET308) for a query that contains an INLIST predicate that includes hostvars. The column is nullable. The failure occurs due to predicate transitive closure or 1 predicate push down, when DB2 internally generates a new INLIST predicate for the left side column which is not null. The following example illustrates a failing case. Step 1. Create two Tables, T1 and T2. CREATE TABLE T1(C1 INT, C2 CHAR(2) NOT NULL, C3 INT); CREATE TABLE T2(C1 INT, C2 VARCHAR(2), C3 INT); Step 2. Insert data into both Tables T1 and T2. INSERT INTO T1 VALUES(1,'AA',1); INSERT INTO T2 VALUES(2,'BB',2); Step 3. In a given application, assign values to three host variables. HOSTVARS = ('AA', NULLIF('',''), 'BB'); Step 4. Execute the following query. SELECT TX.C2 FROM (SELECT C2 FROM T1 UNION SELECT C2 FROM T2) TX(C2) WHERE TX.C2 IN (?,?,?); The code in DB2 is modified to process the INLIST properly which will prevent the failures mentioned. Additional Keywords: SQLIN SQLHOSTVAR SQLNULL SQLNOTNULL PARAMETERMARKER SQLPMARKER SQLPMK SQLPREDPUSHDOWN SQLTRANSITIVE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70395 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM70395 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM70395 corrects a problem that can cause an ABEND04E rc00E70005 (DSNXGINB M621 or DSNXRFF M932) or an ABEND0C4 rc4 (DSNIRNXT +308) for queries that contain an INLIST predicate that includes hostvars. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCAT PM70395 DSNXO1S PM70395 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70395 DSNXOCAT DSNXO1S THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCAT DSNXO1S LISTEND UK82265 COVER LETTER END UK82322 COVER LETTER START PROBLEM DESCRIPTION(S): PM63384 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of RESTORE SYSTEM utility * **************************************************************** * PROBLEM DESCRIPTION: RESTORE SYSTEM failed with ABEND878 * * due to DFSMSdss storage shortage when * * the SYSTEM-LEVEL BACKUP has been * * dumped to tape. * **************************************************************** * RECOMMENDATION: * **************************************************************** RESTORE SYSTEM failed during the RESTORE phase with ABEND878 due to DFSMSdss storage shortage when the SYSTEM-LEVEL BACKUP has been dumped to tape. The storage shortage comes about when DFSMSdss is invoked more than 9 times by RESTORE SYSTEM to restore the tape volumes in parallel. RESTORE SYSTEM code has been modified to call DFSMShsm to invoke DFSMSdss in its own address space (cross memory mode, XM) instead of DFSMShsm's address space when z/OS level is 1.12 or later, this allows more tasks to be able to be run concurrently. Note:HSM apar OA40046 must be applied before or at the same time PM63384 is applied. Failure to do so can result in a failure of RESTORE SYSTEM, irrespective of whether any storage-related issues are seen or not. PM63884 adds a documentation change in the Utility Guide and Reference like the following: In Chapter 28. RESTORE SYSTEM,Utility Guide and Reference V9 and V10. Under the section "Authorization required": This RACF authority is required, because the RESTORE SYSTEM utility invokes DFSMSdss when tape is the input 1 | and z/OS level is 1.11(or lower). However, when you | restore database copy pools from tape when z/OS level is | 1.12(or higher) or from a FlashCopy on disk, the RESTORE SYSTEM utility invokes DFSMShsm, which does not require Operations or DASDVOL authority. In Chapter 28. RESTORE SYSTEM,Utility Guide and Reference V9 and V10.Under the section "How to determine which system-level backups DB2 restores": | The RESTORE SYSTEM utility invokes DFSMShsm to restore the database copy pool volumes from a system-level backup on | tape when running z/OS 1.12 or above. Otherwise, it invokes | DFSMSdss. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63384 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM63884 adds a documentation change in Utility Guide and Reference like the following: In Chapter 28. RESTORE SYSTEM,Utility Guide and Reference V10. Under the section "Authorization required": This RACF authority is required, because the RESTORE SYSTEM utility invokes DFSMSdss when tape is the input | and z/OS level is 1.11(or lower). However, when you | restore database copy pools from tape when z/OS level is | 1.12(or higher) or from a FlashCopy on disk, the RESTORE SYSTEM utility invokes DFSMShsm, which does not require Operations or DASDVOL authority. Chapter 28. RESTORE SYSTEM Under the section "How to determine which system-level backups DB2 restores": | The RESTORE SYSTEM utility invokes DFSMShsm to restore the database copy pool volumes from a system-level backup on | tape when running z/OS 1.12 or above. Otherwise, it invokes | DFSMSdss. ACTION: After applying the fix for PM63384, users are advised that the job output of RESTORE SYSTEM utility from tape might not include DFSMSdss messages in cases where DFSMShsm is now called instead. This PTF has changed RESTORE SYSTEM to call DFSMShsm to invoke DFSMSdss in its own address space (cross memory mode, XM) instead of DFSMShsm's address space when z/OS level is 1.12 or later. THE FOLLOWING IMPORTANT ACTION IS REQUIRED: APPLY HSM APAR OA40046 BEFORE OR AT THE SAME TIME PM63384 IS APPLIED. FAILURE TO DO SO CAN RESULT IN A FAILURE OF RESTORE 1 SYSTEM IF PM63384 IS APPLIED AND ACTIVE ON DB2 BUT OA40046 IS NOT APPLIED AND ACTIVE ON HSM. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUVBRD PM63384 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63384 DSNUVBRD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUVBRD LISTEND UK82322 COVER LETTER END UK82324 COVER LETTER START PROBLEM DESCRIPTION(S): PM69474 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of COPYTOCOPY and RECOVER utility * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU030I, RC4, RSN0220 can happen * * when COPYTOCOPY processes a large list * * of objects that are stacked on tape. * **************************************************************** * RECOMMENDATION: * **************************************************************** The COPYTOCOPY utility can intermittently fail when it copies a large list of objects that are stacked on tape. DB2 issues DSNU030I with a RC4 and RSN0220 which indicates that an allocation failed. Code has been changed to fix the allocation error when COPYTOCOPY copies a large list of objects that are stacked on tape and most of the objects span on multiple volumes. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69474 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGQSV PM69474 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69474 DSNUGQSV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGQSV LISTEND 1UK82324 COVER LETTER END UK82353 COVER LETTER START PROBLEM DESCRIPTION(S): PM69230 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 hang when being shut down with the * * CASTOUT(NO) option, or with outstanding * * indoubt or postponed-abort URs. This * * shutdown hang on one member of a data * * sharing group is accompanied by a hang * * on another member of an application * * trying to upgrade a pageset P-lock. * **************************************************************** * RECOMMENDATION: * **************************************************************** For DB2 V10, it is possible for shutdown to drive a close for the same object twice if its P-lock must be kept. This can result in a deadlock with another member trying to upgrade a P-lock, where the shutting-down member denies any attempt to negotiate it because the object is marked "closed by shutdown", and is trying to get the conversion lock for the second close call. Meanwhile, the other member is holding the conversion lock and waiting for the shutting-down member to stop denying its negotiation requests. The pageset close code has been modified to detect that a pageset has already been closed by shutdown. Additionally, for the case of a P-lock held in SIX mode during a CASTOUT(NO) shutdown, the lock will be downgraded to IX mode to reduce the possibility of a blocked negotiation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69230 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CPL PM69230 DSNB1CPP PM69230 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69230 DSNB1CPL DSNB1CPP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CPL DSNB1CPP LISTEND UK82353 COVER LETTER END 1UK82387 COVER LETTER START PROBLEM DESCRIPTION(S): PM67112 - **************************************************************** * USERS AFFECTED: All DB 10 and DB2 9 for z/OS users of * * aggregate functions (also known as set * * functions) that use workfiles * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C9021A DSNISFWL ERQUAL5008 * * issued on a logical workfile that * * resides on several workfile table * * spaces, while processing an aggregate * * function * **************************************************************** * RECOMMENDATION: * **************************************************************** While DB2 was processing an aggregate function (e.g. SELECT COUNT(DISTINCT GRADE) FROM CLASS), a logical workfile was built across several workfile table spaces. When the workfile's fetch processing transitioned from the final segment page on one of its table spaces to the first segment page on another one of its table spaces, the page number in both cases happened to be the same and the DB2 code was under the false impression that the new page was already in the buffer. As a result, the code abended on the condition that the OBID on the page is not an expected one (which is not surprising given that the code was still looking at the prior table space's page in the buffer). Code has been changed to check for table space transition when determining whether a page in the buffer is a needed page. Additional keywords: SQLSETFUNCTION SQLCOUNT SQLDISTINCT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67112 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISFWL PM67112 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67112 DSNISFWL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISFWL LISTEND UK82387 COVER LETTER END UK82411 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM71626 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: The following symptoms are reported: * * o 04E-00D30014 DSNLTBST:000A * * o 04E-00D30014 DSNLTRSI+1C48 (V10) or * * 04E-00D30014 DSNLTRSI+1C54 (V9 ). * * These may be potentially followed * * by: * * . 04E-00D30014 DSNLTPIF:0001 or * * . 04E-00D30014 DSNLTRSI+1AA2 (V10) or * * 04E-00D30014 DSNLTRSI+1BA2 (V9 ). * * Note: In this case, use of the * * Reset Indoubt IPaddr Force * * command should be avoided. * * DB2 may need to be restarted to * * clean up the condition. * * The symptoms occur after or during a * * Reset Indoubt IPaddr Force command. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following conditions are reported: o While active connections exist to a member of a remote data sharing group, a Reset Indoubt IPaddr Force command is entered that refers to the remote member IP address (or '*'). The command processing searches for any active connections to the remote member but incorrectly determines that no connections exist and therefore deletes control block information (LNTD) that the active connections (and threads) are dependant on. The abend occurs during phase 1 commit processing due to the unexpected absence of the control block information. The active connections to the member are not detected because the connections were actually established via the group IP address (D-DVIPA), as opposed to the member specific address, which Reset Indoubt IPaddr Force command processing does not consider. o The 04E-00D30014 DSNLTRSI+1C48 (V10) or DSNLTRSI+1C54 (V9 ) abend is intended to detect a logic error that incorrectly allows DDF related indoubt resource to be purged and would otherwise result in an orphaned indoubt thread that cannot be resolved. However, this detection is not necessary in cases where the indoubt resource is related to a DDF allied thread since the indoubt resource will still be visible and resolvable. Reset Indoubt IPaddr Force command processing is changed to: o consider group IP addresses for dependency on potential resources to be purged. o allow allied indoubt thread related DDF resources to be purged. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71626 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTBST PM71626 DSNLTCKP PM71626 DSNLTDPR PM71626 DSNLTDQL PM71626 DSNLTLCS PM71626 DSNLTP1S PM71626 DSNLTRSI PM71626 DSNLTRSP PM71626 DSNLTSL1 PM71626 DSNLTSTR PM71626 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71626 DSNLTBST DSNLTCKP DSNLTDPR DSNLTDQL DSNLTLCS DSNLTP1S DSNLTRSI DSNLTRSP DSNLTSL1 DSNLTSTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTBST DSNLTCKP DSNLTDPR DSNLTDQL DSNLTLCS DSNLTP1S DSNLTRSI DSNLTRSP DSNLTSL1 DSNLTSTR LISTEND UK82411 COVER LETTER END UK82453 COVER LETTER START PROBLEM DESCRIPTION(S): PM72893 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML * * indexes. * **************************************************************** * PROBLEM DESCRIPTION: ABEND 0C4 may occur at DSNXOMXI+0FF4 * * on DB2 10 for z/OS or at DSNXOMXI+10BA * * on DB2 9 for z/OS when using XML * * indexes in a query with XMLEXISTS * * predicate and with access to a view * * or a table expression * * that has fullselect with UNION ALL. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following query may expose the problem: 1 SELECT * FROM V1 WHERE XMLEXISTS('$c/A1/B1/[C1=$a]' PASSING ATRIB AS "c", CAST('c1c' AS VARCHAR(50)) AS "a") ; In the above query, V1 is a view declared as following: CREATE TABLE T1 (ID CHAR(19), ATRIB XML); CREATE TABLE T2 (ID CHAR(19), ATRIB XML); CREATE INDEX XMLINDEXA ON T1 (ATRIB) GENERATE KEY USING XMLPATTERN '/A1/B1/C1' AS SQL VARCHAR(50); CREATE INDEX XMLINDEXB ON T2 (ATRIB) GENERATE KEY USING XMLPATTERN '/A1/B1/C1' AS SQL VARCHAR(50); CREATE VIEW V1 (ID, ATRIB) AS SELECT * FROM T1 UNION ALL SELECT * FROM T2 ; For the above query, ABEND 0C4-00000004 occurs at DSNXGRDS.DSNXOMXI+10BA on DB2 9 for z/OS, or occurs at DSNXGRDS.DSNXOMXI+0FF4 on DB2 10 for z/OS. DB2 code is modified so that the ABEND no longer occurs. Additional keywords: ABEND0C4 SQLXML XMLINDEXES SQLVIEW SQLUNIONALL SQLTABLEEXPR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72893 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM44087 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM44087 corrects problems that can cause incorrect output for XMLEXIST when indexx access is chosen for XML value index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMXI PM72893 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72893 DSNXOMXI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMXI LISTEND 1UK82453 COVER LETTER END UK82533 COVER LETTER START PROBLEM DESCRIPTION(S): PM72997 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the COPY * * utility when taking incremental image * * copies of table spaces with the MEMBER * * CLUSTER attribute. * **************************************************************** * PROBLEM DESCRIPTION: Excessive logging during incremental * * copy processing on table spaces with * * the MEMBER CLUSTER attribute in * * DB2 10 for z/OS ENFM and NFM. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** During the DB2 10 for z/OS ENFM process the SYSUTILX directory table space moves to a 32K page size. The algorithms for storing data in the new page size also changed at this time. As a result, the creation of incremental copies on table spaces with the MEMBER CLUSTER attribute can see increased logging rates against SYSUTILX in some cases in the DB2 10 for z/OS ENFM and NFM modes. Increased SYSUTILX logging rates can also be seen without MEMBER CLUSTER being used. DB2 utility code has been changed to reduce the amount of logging that is done during COPY processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72997 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGSUU PM72997 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72997 DSNUGSUU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGSUU LISTEND UK82533 COVER LETTER END UK82563 COVER LETTER START PROBLEM DESCRIPTION(S): PM69203 - **************************************************************** * USERS AFFECTED: All DB2 users running On-line REORG Utility * * with SHRLEVEL CHANGE option. * 1 **************************************************************** * PROBLEM DESCRIPTION: REORG SHRLEVEL CHANGE of a PBG table * * space received ABEND04E RC00E40311 due * * to RC00C90206 ERQUAL5002 in DSNIIDIS * **************************************************************** * RECOMMENDATION: * **************************************************************** Received ABEND04E RC00E40311 while running REORG utility with SHRLEVEL CHANGE of a PBG table space with a unique non- partitioned secondary index (NPSI) defined. At the time of error, one of the REORG log apply subtask failed with ABEND04E 00C90206 in DSNIIDIS when DB2 is committing cross partition update changes. This abend was issued because when DB2 could not find the matching index key/rid to delete from the shadow index, which can be valid due to REORG SHRLEVEL CHANGE processing. DB2 code was changed to tolerate the missing key condition on behalf of Online REORG log apply processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69203 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIKDEF PM69203 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69203 DSNIKDEF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIKDEF LISTEND UK82563 COVER LETTER END UK82612 COVER LETTER START PROBLEM DESCRIPTION(S): PM70623 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 ABEND04E WITH RC00C200A2 FAILURE IN * * DSNB1GET+451A. * **************************************************************** * RECOMMENDATION: * **************************************************************** During a restore to a SAVEPOINT operation, undo log processing encountered a failure condition in the middle of a GETPAGE operation. DB2 recovery routines were invoked and the undo operation kept on processing the log records. A subsequent GETPAGE for the space map page detected that the page latch was already held and so a RC00C200A2 abend was taken. 1 For program recovery conditions during DSNIBHUN undo processing, there is a window of uncertainty on whether a latch is held on the space map page. During RESTORE TO SAVEPOINT operations, when error recovery retry handler is invoked, any latches held on the space map page will be released. Subsequent undo calls will latch the space map page anew. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70623 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNILSMG PM70623 DSNILSMU PM70623 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70623 DSNILSMG DSNILSMU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILSMG DSNILSMU LISTEND UK82612 COVER LETTER END UK82618 COVER LETTER START PROBLEM DESCRIPTION(S): PM70983 - **************************************************************** * USERS AFFECTED: All Users of the DB2 Universal JDBC Driver, * * DB2 OLE DB Driver, DB2 z/OS ODBC driver * * or the CLI Driver provided with DB2 for * * Linux, Unix and Windows Version 8 and above * * that connect to DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: The following DB2 supplied Database * * Metadata stored procedure returned * * SQLCODE -104 SQLSTATE=38113 * * when the SCHEMALIST value in the * * OPTIONS parameter exceed 128 bytes * * in length. * * - SYSIBM.SQLCOLPRIVILEGES * * - SYSIBM.SQLCOLUMNS * * - SYSIBM.SQLTABLEPRIVILEGES * * - SYSIBM.SQLTABLES * **************************************************************** * RECOMMENDATION: * **************************************************************** When SCHEMALIST value exceeds 128 bytes in OPTIONS parameter, the following DB2 supplied Database Metadata stored procedures terminated with SQLCODE -104 SQLSTATE 38113. - SYSIBM.SQLCOLPRIVILEGES 1 - SYSIBM.SQLCOLUMNS - SYSIBM.SQLTABLEPRIVILEGES - SYSIBM.SQLTABLES The following DB2 supplied stored procedures have been fixed to support a SCHEMALIST value up to 2048 bytes long. - SYSIBM.SQLCOLPRIVILEGES - SYSIBM.SQLCOLUMNS - SYSIBM.SQLTABLEPRIVILEGES - SYSIBM.SQLTABLES *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU (2) Refresh the WLM environment Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRM DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. (2) Refresh the WLM environment Issue the following VARY MVS command to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment in which the Database Metadata stored procedures SYSIBM.SQLCOLPRIVILEGES, SYSIBM.SQLCOLUMNS, SYSIBM.SQLTABLEPRIVILEGES and SYSIBM.SQLTABLES are running COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM70983 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: **Action for PM70983 (V10): See PTF cover letter for additional information. This PTF modifies DB2 supplied Database Metadata stored procedures SYSIBM.SQLCOLPRIVILEGES, SYSIBM.SQLCOLUMNS, SYSIBM.SQLTABLEPRIVILEGES and SYSIBM.SQLTABLES to fix the SQLCODE -104 problem when SCHEMALIST value length exceed 128 bytes. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU (2) Refresh the WLM environment Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRMs DSNACOLU, DSNACPRU, DSNATBLU and DSNATBPU If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. (2) Refresh the WLM environment Issue the following VARY MVS command to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application 1 environment in which the Database Metadata stored procedures SYSIBM.SQLCOLPRIVILEGES, SYSIBM.SQLCOLUMNS, SYSIBM.SQLTABLEPRIVILEGES and SYSIBM.SQLTABLES are running COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@COLU PM70983 DSN@CPRU PM70983 DSN@TBLU PM70983 DSN@TBPU PM70983 DSNACOLU PM70983 DSNACPRU PM70983 DSNATBLU PM70983 DSNATBPU PM70983 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70983 DSN@COLU DSN@CPRU DSN@TBLU DSN@TBPU DSNACOLU DSNACPRU DSNATBLU DSNATBPU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACOLU DSNACPRU DSNATBLU DSNATBPU MACROS DSN@COLU DSN@CPRU DSN@TBLU DSN@TBPU LISTEND UK82618 COVER LETTER END UK82624 COVER LETTER START PROBLEM DESCRIPTION(S): PM71858 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of applications * * that contain a DELETE WHERE CURRENT OF * * statement. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at * * location DSNXRDWG M583 for a DELETE * * WHERE CURRENT OF statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 can occur at location DSNXRDWG M583 for a DELETE WHERE CURRENT OF statement when running on DB2 10 for z/OS. When DB2 processes a DELETE WHERE CURRENT OF statement, an internal variable is used which is defined with an incorrect 1 type. So, for certain circumstances, for example when the DB2 catalog has a large number of objects, and the OBID of the table involved in this statement is large enough to cause the overflow of this internal variable, the above abend can occur. The code in DB2 has been modified to redefine this internal variable properly so that it will not overflow per a given OBID. Additional Keywords: SQLDELETE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71858 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDWG PM71858 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71858 DSNXRDWG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDWG LISTEND UK82624 COVER LETTER END UK82625 COVER LETTER START PROBLEM DESCRIPTION(S): PM68239 - **************************************************************** * USERS AFFECTED: ALL DB2 10 FOR z/OS USERS OF CHECK DATA * * UTILITY * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E40090 ON CHECK DATA * * UTILITY WHEN INCORRECT SYNTAX IS * * USED * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran CHECK DATA utility with syntax similar to the following: CHECK DATA TABLESPACE dbname.tsname FOR EXCEPTION USE aaa.bbb DELETE YES ERRDDN...WORKDDN.... This syntax is invalid because the keyword USE requires the prior use of the keyword IN, as in this correctly specified syntax: CHECK DATA TABLESPACE dbname.tsname FOR EXCEPTION IN xxx.yyy USE aaa.bbb DELETE YES ERRDDN...WORKDDN.... 1 The job abended with ABEND04E RC00E40090 ("internal error"). Even though the CHECK DATA statement was invalid, it should not have led to this abend. Code was changed in the utility parser to issue MSGDSNU071I DSNU071I - KEYWORD 'USE' REQUIRES KEYWORD 'IN' when CHECK DATA utility is attempted with the USE keyword without a prior corresponding IN keyword. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68239 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGPPB PM68239 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68239 DSNUGPPB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGPPB LISTEND UK82625 COVER LETTER END UK82640 COVER LETTER START PROBLEM DESCRIPTION(S): PM66166 - **************************************************************** * USERS AFFECTED: All DB2 V10 users of IRLM230 (HIR2230). * **************************************************************** * PROBLEM DESCRIPTION: IRLM serviceability changes. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM serviceability changes. GEN: KEYWORDS: *** END IMS KEYWORDS *** IRLM 2.3 serviceability changes. IRLM function level for IRLM 2.3 (only) is changed to 30. Please contact IBM support if you want information regarding this change. For IRLM 2.2 and IRLM 2.3, this APAR adds another change to correctly clear a flag (RLMMAXCC) in IRLM that tracks message DXR167E for MAXCYCLE being issued by the Global Deadlock Manager. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM66166 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL0B0 PM66166 DXRRL010 PM66166 DXRRL020 PM66166 DXRRL1S1 PM66166 DXRRL2U0 PM66166 DXRRL2V0 PM66166 DXRRL24B PM66166 DXRRL240 PM66166 DXRRL241 PM66166 DXRRL249 PM66166 DXRRL750 PM66166 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66166 DXRRL0B0 DXRRL010 DXRRL020 DXRRL1S1 DXRRL2U0 DXRRL2V0 DXRRL24B DXRRL240 DXRRL241 DXRRL249 DXRRL750 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL0B0 DXRRL010 DXRRL020 DXRRL1S1 DXRRL2U0 DXRRL2V0 DXRRL24B DXRRL240 DXRRL241 DXRRL249 DXRRL750 LISTEND UK82640 COVER LETTER END UK82671 COVER LETTER START PROBLEM DESCRIPTION(S): PM73975 - **************************************************************** * USERS AFFECTED: All users of the DB2 BIND PACKAGE command * * that specify the APREUSE and/or APCOMPARE * * option(s) in conjunction with the COPY or * * DEPLOY option. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 IN DSNGEPLC * * OFFSETE4D8 may occur when certain * * packages are bound with the * * APCOMPARE or APREUSE bind option * * in conjunction with the COPY or * * DEPLOY option. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 ABEND04E RC00C90101 IN DSNGEPLC OFFSETE4D8 may occur when certain packages are bound with the APCOMPARE or APREUSE bind option in conjunction with the COPY or DEPLOY option. ABEND04E RC00C90101 IN DSNGEPLC OFFSETE4D8 may occur when certain packages are bound with the APCOMPARE or APREUSE in conjunction with the COPY or DEPLOY option. This PTF fixes the problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73975 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBSTB PM73975 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73975 DSNTBSTB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBSTB LISTEND UK82671 COVER LETTER END UK82676 COVER LETTER START PROBLEM DESCRIPTION(S): PM73092 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users * * of DISPLAY PROFILE command * **************************************************************** * PROBLEM DESCRIPTION: Improper information is retrieved for * * Message ID when the information is * * extracted from the message output of * * DISPLAY PROFILE command. * **************************************************************** * RECOMMENDATION: * **************************************************************** The message output of DISPLAY PROFILE command is formatted with multiple information and displayed in multiple lines under DSNT753I message ID. . In the reported case, user's tool extracted the message ID for each message. However, each line of DSNT753I message was treated as an individual message, resulting in displaying improper information for message ID. DB2 has been modified to correctly format multiple information into multiple lines for DSNT753I message ID. Related keyword: MSGDSNT753I COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM73092 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNT1DSP PM73092 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73092 DSNT1DSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNT1DSP LISTEND UK82676 COVER LETTER END UK82696 COVER LETTER START PROBLEM DESCRIPTION(S): PM73849 - **************************************************************** * USERS AFFECTED: All users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0F8 RC14 on an SVC issued by * * IGGCSI00 due to an active EUT FRR. * * IGGCSI00 was called by DSNPSCT0, * * running under the AUTOBIND service task * * TCB. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNTBAB received control under the AUTOBIND service task TCB and established an EUT FRR for abend recovery. During the AUTOBIND process, IGGCSI00 was invoked by DSNPSCT0 and issued an SVC 78. The SVC abended with S0F8-14 ( ABEND0F8 RC14 ) due to the EUT FRR created by DSNTBAB. DSNTBAB has been changed to create an Estae for abend recovery, while running under the AUTOBIND service task TCB. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73849 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBAB PM73849 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73849 DSNTBAB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNTBAB LISTEND UK82696 COVER LETTER END UK82699 COVER LETTER START PROBLEM DESCRIPTION(S): PM73083 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an * * INSERT SQL statement that references * * to a DB2 generated column for an XML * * column. * **************************************************************** * PROBLEM DESCRIPTION: ABND04E at DSNIDM.DSNIRNXT:5024 or * * ABND04E at DSNNXML.DSNNOGET:M720 * * may occur for an SQL statement * * that satisfies the following * * conditions: * * 1. That statement references to a * * DB2_GENERATED_DOCID_FOR_XML column * * inside a view. * * 2. A non DEFAULT value is inserted into * * the DB2_GENERATED_DOCID_FOR_XML column * * inside a view. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABND04E at DSNIDM.DSNIRNXT:5024 or ABND04E at DSNNXML.DSNNOGET:M720 may occur for an SQL statement that satisfies the following conditions: 1. That statement references to a DB2_GENERATED_DOCID_FOR_XML column inside a view. 2. A non DEFAULT value is inserted into the DB2_GENERATED_DOCID_FOR_XML column inside a view. For Example, CREATE TABLE T1(ID INT, X1 XML); CREATE VIEW VT1(VID, VX1, DB2_GENERATED_DOCID_FOR_XML) AS SELECT ID, X1, DB2_GENERATED_DOCID_FOR_XML FROM T1; INSERT INTO T1 (ID, X1,DB2_GENERATED_DOCID_FOR_XML) VALUES(1,'ABC',NULL); SELECT * FROM VT1; Abend may occur for the SELECT statement above because an invalid value is inserted into the DB2_GENERATED_DOCID_FOR_XML column. DB2 was fixed to not insert an invalid value into a DB2_GENERATED_DOCID_FOR_XML column. Additional Keywords: SQLXML SQLXMLINSERT 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73083 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM58322: See PM58322 APAR/PTF text for additional information about why a REBIND is necessary. PM58322 corrects a problem of missing a negative SQLCODE on the insert or delete operation in the statements such as INSERT, DELETE, MERGE, or SELECT FROM those where the object table references a view and the view definition references a DB2 directory table such as SYSLGRNX. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. ACTION: ***Action for PM73083: See PM73083 APAR/PTF text for additional information about why a REBIND is necessary. PM73083 corrects a problem of ABND04E at DSNIDM.DSNIRNXT:5024 or ABND04E at DSNNXML.DSNNOGET:M720 may occur for an SQL statement that references to a DB2_GENERATED_DOCID_FOR_XML column inside a view and a non DEFAULT value is inserted into this DB2_GENERATED_DOCID_FOR_XML column inside a view. View contains the DB2_GENERATED_DOCID_FOR_XML and a non default value is inserted into this column must be dropped and recreated. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOADT PM73083 DSNXOVC PM73083 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73083 DSNXOADT DSNXOVC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOADT DSNXOVC LISTEND 1UK82699 COVER LETTER END UK82701 COVER LETTER START PROBLEM DESCRIPTION(S): PM74487 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: Stop DDF Mode(Force) processing * * intermittently hangs. * **************************************************************** * RECOMMENDATION: * **************************************************************** A "STOP DDF MODE(FORCE)" command was issued while DDF was in the very early stages of being stopped quiesce, even prior to DB2 issuing the DSNL005I message. DDF stop force processing first issues a CALLRTM ABTERM against the current stop quiesce processing in order to interrupt it. However, the CALLRTM 04F abend happened to occur while stop quiesce processing was making a Unix System Services (USS) socket call in an effort to close the DB2 TCP/IP listener sockets and USS retried from the 04F abend. This prevented the stop force processing from being fully initiated. As a result, DDF stop processing never completes. DSNLITR0 has been changed to detect if a CALLRTM interruption of Stop Quiesce processing has been retried and to "re-abend" with an 04F in order to honor the intended interruption. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74487 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLITR0 PM74487 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74487 DSNLITR0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLITR0 LISTEND UK82701 COVER LETTER END UK82729 COVER LETTER START PROBLEM DESCRIPTION(S): PM68621 - **************************************************************** * USERS AFFECTED: All DB2 Users of the SQL GET DIAGNOSTICS * * statement, DB2 Dynamic Statement Caching, * 1 * and DB2 applications containing both DDL and * * dynamic SQL in the same application bound as * * KEEPDYNAMIC(YES) * **************************************************************** * PROBLEM DESCRIPTION: After preparing or executing a dynamic * * SQL statement from the Dynamic * * Statement Cache, an SQL GET DIAGNOSTICS * * was issued for that dynamic statement * * and the diagnostics info returned shows * * SQLCODE -910 , but the returned SQLCA * * shows SQLCODE0 . The SQLCODE -910 in * * in the diagnostics info is invalid and * * should show SQLCODE0 instead. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application bound KEEPDYNAMIC(YES) did the following: PREPARE dynamic statement 'INSERT INTO TABLE1 ...' for/from the Dynamic Statement Cache ( DSC ) EXECUTE the cached dynamic statement (optional) Execute DDL operation on TABLE1 COMMIT EXECUTE the cached dynamic statement (re-PREPARE not needed because of KEEPDYNAMIC(YES)) - this EXECUTE gets a SQLCODE -910 due to previous DDL operation on TABLE1, so DB2 must do an implicit re-PREPARE for the INSERT statement. The DDL operation also invalidated the previously cached statement, so this implicit re-PREPARE must be a new cache-insert of this INSERT statement into the DSC. SQL GET DIAGNOSTICS was issued and the diagnostics information returned shows SQLCODE -910 . . If another application issued a PREPARE (or DB2 did an implicit re-prepare on EXECUTE) for this INSERT statement and cache- matched the INSERT statement in the DSC, and the application followed that PREPARE/EXECUTE with an SQL GET DIAGNOSTICS statement, the diagnostics information that DB2 returns shows SQLCODE -910, while the SQLCA that DB2 returns shows SQLCODE0. The SQLCODE -910 shown in diagnostics information is invalid, and the SQLCODE0 is correct. . DB2 Development determined that this discrepency between GET DIAGNOSTICS information and the SQLCA was due to the SQLCA with SQLCODE -910 being cached along with the INSERT statement on the implicit re-PREPARE and new cache-insert that occurred on the EXECUTE following the COMMIT in the original application scenario described above. DB2 was changed to ensure that the SQLCA is re-initialized after this SQLCODE -910 before doing the implicit re-PREPARE and new cache-insert of the dynamic statement into the DSC. KEYWORDS: KEEPDYNAMIC YES SQLDYNSTMTCACHE SQLCODE910 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68621 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXERT PM68621 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68621 DSNXERT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERT LISTEND UK82729 COVER LETTER END UK82731 COVER LETTER START PROBLEM DESCRIPTION(S): PM57432 - **************************************************************** * USERS AFFECTED: All DB2 Users preparing for new release. * **************************************************************** * PROBLEM DESCRIPTION: DB2 internal change to support future * * functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR does not address or fix any problem in DB2. It contains changes in support of future function. This APAR does not have any external symptoms. SOLUTION: The code logic is added to support a future new function. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57432 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF does not fix any current incorrect values. After applying this fix, you may use the following sample query to see if there are any orphaned rows caused by the original error: SELECT * FROM SYSIBM.SYSROUTINES R WHERE R.ROUTINETYPE = 'F' AND R.FUNCTION_TYPE = 'S' AND R.ORIGIN = 'N' AND R.INLINE = 'N' AND NOT EXISTS ( SELECT * FROM SYSIBM.SYSPACKAGE P 1 WHERE P.OWNER = R.SCHEMA AND P.NAME = R.NAME AND P.COLLID = R.COLLID AND P.VERSION = R.VERSION)! If this query returns any rows, please contact IBM for further instructions on how to resolve these rows. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBAB2 PM57432 DSNTBAS PM57432 DSNTBBP2 PM57432 DSNTBSPL PM57432 DSNXEAAL PM57432 DSNXEBPG PM57432 DSNXENR PM57432 DSNXENVR PM57432 DSNXEPP PM57432 DSNXERBP PM57432 DSNXIANR PM57432 DSNXICRT PM57432 DSNXIDPL PM57432 DSNXIEPL PM57432 DSNXISB2 PM57432 DSNXISB7 PM57432 DSNXISUB PM57432 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57432 DSNTBAB2 DSNTBAS DSNTBBP2 DSNTBSPL DSNXEAAL DSNXEBPG DSNXENR DSNXENVR DSNXEPP DSNXERBP DSNXIANR DSNXICRT DSNXIDPL DSNXIEPL DSNXISB2 DSNXISB7 DSNXISUB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBAB2 DSNTBAS DSNTBBP2 DSNTBSPL DSNXEAAL DSNXEBPG DSNXENR DSNXENVR DSNXEPP DSNXERBP DSNXIANR DSNXICRT DSNXIDPL DSNXIEPL DSNXISB2 DSNXISB7 DSNXISUB LISTEND UK82731 COVER LETTER END 1 UK82732 COVER LETTER START PROBLEM DESCRIPTION(S): PM66287 - **************************************************************** * USERS AFFECTED: All users that REORG the table space * * containing SYSPACKAGE or the table space * * DSNDB01.SPT01, using SHARE LEVEL REFERENCE. * * This is done in step ENFM0097 in the * * DSNTIJEN JOB. * **************************************************************** * PROBLEM DESCRIPTION: Deadlock or Timeout can occur when * * running a REORG SHRLEVEL REFERENCE * * on the table space that contains * * SYSPACKAGE or the table space * * DSNDB01.SPT01. * **************************************************************** * RECOMMENDATION: * **************************************************************** When performing the ENFM for V10 the REORG of SYSPKAGE can receive timeout or deadlock messages with the AUTOBIND or RTS service tasks. The AUTOBIND and RTS service task has been updated to avoid conflicts with REORG of the table space that contains SYSPACKAGE and the table space DSNDB01.SPT01. Additional Keywords: DB2MIGV10/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66287 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGERTS PM66287 DSNIRTST PM66287 DSNTBAB2 PM66287 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66287 DSNGERTS DSNIRTST DSNTBAB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGERTS DSNIRTST DSNTBAB2 LISTEND UK82732 COVER LETTER END UK82737 COVER LETTER START PROBLEM DESCRIPTION(S): PM72623 - **************************************************************** 1 * USERS AFFECTED: DB2 users who binds plan and packages. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E20009 at * * DSNXESXT DSNSVSFB +0802 * * on a BIND PACKAGE or PLAN * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 erroneously sets flag that indicates bind processing error when there isn't any error and results in the abend. DB2 has been modified to set error indicator flags correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72623 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEPP PM72623 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72623 DSNXEPP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEPP LISTEND UK82737 COVER LETTER END UK82739 COVER LETTER START PROBLEM DESCRIPTION(S): PM69760 - **************************************************************** * USERS AFFECTED: All DB2 10 and DB2 9 for z/OS data sharing * * users of the z/OS SETXCF REBUILD command * * when issued against SCA * **************************************************************** * PROBLEM DESCRIPTION: Timeout MSGDSNT376I MSGDSNT501I with * * RC00C900C0 TYPE00002105 may occur in * * data sharing when a REBUILD of the SCA * * structure is issued (e.g. * * SETXCF START,REBUILD,STRNM=DSNCAT_SCA), * * resulting in stoppage of the rebuild, * * with messages MSGDSN7504I, MSGIXC522I * * and MSGIXC521I * **************************************************************** * RECOMMENDATION: * **************************************************************** REBUILD of the SCA structure may experience a timeout on resource type 00002105 when running concurrently with database exception table (DBET)-heavy activity such as during utility workloads that turn on/off various DBET states like UTRW, RBDP etc. 1 The following sample illustrates the issue: ---------------------------------------------------------------- DSNT376I - PLAN=BCT WITH 398 CORRELATION-ID=014.RBDBET01 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397 THREAD-INFO=SYSOPR:*:*:* IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN= WITH CORRELATION-ID=020.JOBSTO07 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071B10954=7 THREAD-INFO=SYSOPR:*:*:* ON MEMBER V91A DSNT501I - DSNILMCL RESOURCE UNAVAILABLE 399 CORRELATION-ID=014.RBDBET01 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397=0 REASON 00C900C0 TYPE 00002105 NAME INTERNAL LOCK 05 DSN7504I - DSN7LST2 400 SCA STRUCTURE DSNCAT_SCA REBUILD UNSUCCESSFUL. REASON CODE = 8. IXC522I REBUILD FOR STRUCTURE 401 DSNCAT_SCA IS BEING STOPPED TO FALL BACK TO THE OLD STRUCTURE DUE TO CONNECTOR SPECIFIC REASON USER CODE: 00000008 IXC521I REBUILD FOR STRUCTURE DSNCAT_SCA 405 HAS BEEN STOPPED ---------------------------------------------------------------- The reason for the timeout of the SCA REBUILD is that a mainline DBET updater (e.g. a utility) is suspended (while holding the DBET hash lock) by the SCA REBUILD process. When the SCA REBUILD tries to obtain the same lock, it cannot do so because the holder is suspended and therefore the SCA REBUILD times out. Code has been changed to adjust the serialization scheme between mainline DBET updaters and the SCA REBUILD process. For the timing window when the SCA REBUILD tries to obtain the DBET hash lock while a mainline DBET updater is in the notify exit path, the SCA REBUILD timeout will not be resolved until a future enabling APAR, which should be applied only after APAR PM69760 has been applied on all data sharing members. Additional keywords: DB2DSHR SYSPLEXDS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69760 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBAB PM69760 DSNIDBGC PM69760 DSNIDBHK PM69760 DSNIDBMS PM69760 DSNIDBNG PM69760 DSNIDBNI PM69760 DSNIDBPL PM69760 DSNLCMT2 PM69760 DSNLTBAB PM69760 DSNLTLCS PM69760 DSNLTRD PM69760 DSNLTRSI PM69760 DSNLTWCP PM69760 DSN7GJON PM69760 DSN7LDE1 PM69760 DSN7LRE1 PM69760 DSN7LWR1 PM69760 DSN7TGLM PM69760 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69760 DSNIDBAB DSNIDBGC DSNIDBHK DSNIDBMS DSNIDBNG DSNIDBNI DSNIDBPL DSNLCMT2 DSNLTBAB DSNLTLCS DSNLTRD DSNLTRSI DSNLTWCP DSN7GJON DSN7LDE1 DSN7LRE1 DSN7LWR1 DSN7TGLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBAB DSNIDBGC DSNIDBHK DSNIDBMS DSNIDBNG DSNIDBNI DSNIDBPL DSNLCMT2 DSNLTBAB DSNLTLCS DSNLTRD DSNLTRSI DSNLTWCP DSN7GJON DSN7LDE1 DSN7LRE1 DSN7LWR1 DSN7TGLM LISTEND UK82739 COVER LETTER END UK82783 COVER LETTER START PROBLEM DESCRIPTION(S): PM70796 - 1 **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those with remote Java * * applications connecting to a DB2 for z/OS * * server during its migration process. * **************************************************************** * PROBLEM DESCRIPTION: During DB2 for z/OS migration, a * * DSNL032I DRDA exception message, with * * reason code 00D35B16 and error ID * * DSNLZSDT002C, may occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote Java application uses the IBM Data Server Driver for JDBC and SQLJ to connect to a DB2 for z/OS server. The connection environment between the remote client and the DB2 for z/OS server is negotiated with a DRDA SQL Application Manager (SQLAM) level of 7 or lower. After the connection is established (at the SQLAM<8 level), the DB2 for z/OS subsystem is migrated such that the remote client driver will now be aware of a DB2 for z/OS product identifier that reflects a higher version or modification level. The Java application then executes an SQL statement with input parameters. The Java client driver, judging from the updated (now higher) DB2 for z/OS product identifier, incorrectly associates the input parameters with a DECFLOAT data type even though the connection's negotiated SQLAM level did not reflect this capability. When the DB2 for z/OS server receives the request, a DRDA exception is detected and message DSNL032I is issued. The remote application SQL statement will therefore fail. The Java client driver is in error because it is incorrectly making a judgment based on the DB2 for z/OS product ID rather than the negotiated SQLAM manager level of the connection, and a fix is available in V9.7 Fp3a and above. Generally, users are advised to upgrade the client driver to the appropriate level to resolve the issue. However, in some cases it may not be practical for users to upgrade all of their clients before their planned migration to DB2 for z/OS New Function Mode. Thus, for the benefit of user migration plans, a DB2 for z/OS server fix may be appropriate in an effort to tolerate the client system error. DB2 for z/OS server processing has been changed to tolerate and support SQL statements with a DECFLOAT data type as input parameters from a remote Java application for connection environments that are negotiated at SQLAM 7 or lower. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70796 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZSDT PM70796 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70796 DSNLZSDT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZSDT LISTEND UK82783 COVER LETTER END UK82789 COVER LETTER START PROBLEM DESCRIPTION(S): PM69444 - **************************************************************** * USERS AFFECTED: All users of DB2 10 and 9 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 occurred in * * DSNIIMSI due to an invalid pointer * * to the OBDFS structure. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC00000011 occurred in DSNIIMSI because the pointer to OBDFS was not set before we accessed a field in this structure. Code has been changed so that we make sure the pointer is set before accessing a field in the OBDFS structure. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69444 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIIMSI PM69444 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69444 DSNIIMSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIIMSI LISTEND UK82789 COVER LETTER END UK82795 COVER LETTER START PROBLEM DESCRIPTION(S): PM69380 - **************************************************************** * USERS AFFECTED: Internal serviceability for dumps * **************************************************************** 1 * PROBLEM DESCRIPTION: Internal serviceability for dumps * **************************************************************** * RECOMMENDATION: * **************************************************************** Internal serviceability for dumps. Internal serviceability for dumps. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69380 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWDFDM PM69380 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69380 DSNWDFDM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWDFDM LISTEND UK82795 COVER LETTER END UK82830 COVER LETTER START PROBLEM DESCRIPTION(S): PM69872 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DB2 Dynamic * * Statement Cache and dynamic SQL that use * * the GETVARIABLE built-in function and * * the prepare attribute * * CONCENTRATE STATEMENTS WITH LITERALS * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXRSBC :P036 * * during execution of a cached dynamic * * statement that uses the GETVARIABLE * * built-in function and the prepare * * attribute CONCENTRATE STATEMENTS * * WITH LITERALS. * **************************************************************** * RECOMMENDATION: * **************************************************************** The reported DSNXRSBC abend occurred during execution of a dynamic SQL statement when Dynamic Statement Caching (DSC) is active and all of the following conditions were true: (1) the dynamic SQL statement specified the GETVARIABLE built- in function, was prepared with the attribute CONCENTRATE STATEMENT WITH LITERALS, and qualified for literal constant reuse (2) during PREPARE the dynamic statement successfully cache- matched with an existing cached statement specifying the GETVARIABLE function in the DSC, even though the first 1 argument literal string constant (session variable name) of the GETVARIABLE function is different between the two dynamic statements (this is the cache statement sharing behavior when using attribute CONCENTRATE STATEMENTS WITH LITERALS) (3) in the new dynamic statement that first argument literal of the GETVARIABLE function does not specify a valid session variable name, whereas the existing cached statement does specify a valid session variable name . The DSNXRSBC abend occurred during execution of the new dynamic statement that used the invalid GETVARIABLE specification, after the PREPARE of that dynamic statement successfully matched with an existing cached statement in the DSC as described above. Instead of the abend, DB2 should have issued SQLCODE -096 as expected for the new dynamic statement that specified the invalid GETVARIABLE session variable name. . An example scenario follows : DECLARE C1 CURSOR FOR DYNSQL_WITH_LITERAL; . DYNSQL_SELECT = 'SELECT GETVARIABLE('SYSIBM.PLAN_NAME') FROM SYSIBM.SYSDUMMY1' attrstring = CONCENTRATE STATEMENTS WITH LITERALS'; EXEC SQL PREPARE DYNSQL_WITH_LITERAL ATTRIBUTES :attrstring FROM :DYNSQL_SELECT; ** the above PREPARE caches the SELECT that specifies ** the valid GETVARIABLE specification in the DSC EXEC SQL OPEN C1; EXEC SQL FETCH C1; EXEC SQL CLOSE C1; . ** the next SELECT specifies an invalid session variable ** name literal constant in the GETVARIABLE function but ** during PREPARE successfully matches the above cached ** statement in the DSC due to the literal reuse behavior of ** the CONCENTRATE STATEMENTS WITH LITERALS attribute. DYNSQL_SELECT = 'SELECT GETVARIABLE('SYSIBM.PLAN ') FROM SYSIBM.SYSDUMMY1' EXEC SQL OPEN C1; EXEC SQL FETCH C1; ** DB2 should have issued SQLCODE -96 for this SELECT instead ** of abending. . DB2 Dynamic Statement Caching CONCENTRATE STATEMENTS WITH LITERALS behavior for GETVARIABLE usage has been changed to only allow a successful cache match between statements where the GETVARIABLE first string constant argument for session variable name is an exact value match. This allows DB2 to issue SQLCODE -96 during PREPARE when an invalid GETVARIABLE session variable name is specified. Additional search keywords: SQLCODE96 SQLDYNSTMTCACHE AB04E OFFSETP036 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69872 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODTR PM69872 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69872 DSNXODTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODTR LISTEND UK82830 COVER LETTER END UK82841 COVER LETTER START PROBLEM DESCRIPTION(S): PM62481 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: 1. Event based IFCIDs may be written * * outside of an accounting interval. * * Monitor programs need to know whether * * these records can eventually be * * correlated to an accounting record * * (IFCID3). * * * * 2. End SQL event records IFCID53 and * * IFCID58 do not contain the statement * * type. This requires correlation to * * the SQL begin record to identify the * * statement type. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. Additonal correlation information is needed. 2. The statement type needs to be externalized with SQL end event records. 1. A new correlation field QWHCAACE is added to the correlation header. This field is zero if the IFCID is written outside of an accounting interval. Otherwise it will contain a value that can be correlated to QWHSACE in a forthcoming IFCID3 accounting record. For DDF/RRSAF rollup accounting records, QWHCAACE should be correlated to QWARACE as the record will represent multiple transactions. For parallel tasks, QWHCAACE will point to the ACE of the parent task. 1 2. New fields QW0058TOS and QW0053TOS are added to IFCID58 and IFCID53 respectively. These fields will contain the statement type that is ending. Refer to QWHS0058 mapping for a complete list of values that can appear in the QW0058TOS field. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62481 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWHC PM62481 DSNDQW00 PM62481 DSNDQW01 PM62481 DSNWAACT PM62481 DSNWALOG PM62481 DSNWAPCS PM62481 DSNWATGS PM62481 DSNWVAPR PM62481 DSNWVCOL PM62481 DSNWVTIT PM62481 DSNWV001 PM62481 DSNWZDG2 PM62481 DSNXECST PM62481 DSNXELOB PM62481 DSNXERT PM62481 DSNXERT2 PM62481 DSNXETRC PM62481 DSNXI14 PM62481 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62481 DSNDQWHC DSNDQW00 DSNDQW01 DSNWAACT DSNWALOG DSNWAPCS DSNWATGS DSNWVAPR DSNWVCOL DSNWVTIT DSNWV001 DSNWZDG2 DSNXECST DSNXELOB DSNXERT DSNXERT2 DSNXETRC DSNXI14 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWAACT DSNWALOG DSNWAPCS DSNWATGS DSNWVAPR DSNWVCOL DSNWVTIT DSNWV001 DSNWZDG2 DSNXECST DSNXELOB DSNXERT DSNXERT2 DSNXETRC DSNXI14 1 MACROS DSNDQWHC DSNDQW00 DSNDQW01 LISTEND UK82841 COVER LETTER END UK82873 COVER LETTER START PROBLEM DESCRIPTION(S): PM67547 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: Error message MSGDSNP031I or * * MSGDSNP011I RC00D70014, maximum extents * * of 251 reached, is issued when * * extending a DB2 data set associated * * with the page set created with DSSIZE * * (or PIECESIZE) 128 or 256 GB. * **************************************************************** * RECOMMENDATION: * **************************************************************** The current DB2 sliding scale algorithm is designed for page set with DSSIZE (or PIECESIZE) up to 64 GB. The new size 128 and 256 GB introduced in DB2 V10 may receive RC00D70014, maximum extents 251 reached during extend. The error could be avoided if SMS Data Class Extent Constraint Relief is enabled as it allows maximum 7257 extents. DB2 sliding scale is changed to support 128 and 256 GB DSSIZE (or PIECESIZE). It is for DB2 users who do not enable SMS Data Class Extent Constraint Relief feature provided by DFSMS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67547 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNPDFN1 PM67547 DSNPXTN0 PM67547 DSNPXTRC PM67547 DSNUGSPC PM67547 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67547 DSNPDFN1 DSNPXTN0 DSNPXTRC DSNUGSPC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNPDFN1 DSNPXTN0 DSNPXTRC DSNUGSPC 1 LISTEND UK82873 COVER LETTER END UK82887 COVER LETTER START PROBLEM DESCRIPTION(S): PM73884 - **************************************************************** * USERS AFFECTED: All DB2 users of IRLM220(HIR2220) and * * IRLM230(HIR2230). * **************************************************************** * PROBLEM DESCRIPTION: DB2 DDF thread hung in DSNTABA after * * being cancelled. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** A DDF thread could not be cancelled and got hung in DSNTABA. The lock requested by the DDF thread was not held in IRLM at time when dumps were taken for the hang which is usually after several minutes or hours. Additional serviceability is needed to trace suspend/resume of SKPT lock requests in IRLM. This serviceability APAR adds additional tracing of DB2 Skeleton Package Table lock (SKPT)_ being suspended and resumed in IRLM. These traces are written in special internal diagnostic buffer (DIA) in IRLM. There will be additional ECSA requirement maximum about 650K per member when these traces are written. Performance implications will be very minimal. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM73884 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL109 PM73884 DXRRL150 PM73884 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73884 DXRRL109 DXRRL150 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL109 DXRRL150 LISTEND UK82887 COVER LETTER END UK82904 COVER LETTER START PROBLEM DESCRIPTION(S): PM71459 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of LOAD utility with RESTART(PHASE) * 1 * processing. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 DSNUGSDA OFFSET528E during * * a RESTART(PHASE) of a LOAD utility in * * the SORTBLD phase when the SORTOUT * * data set was modified. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LOAD utility was restarted in the RELOAD phase after initially abending in the SORTBLD phase. The TEMPLATE for SORTOUT on the initial utility execution had a disposition of DISP(NEW,DELETE, DELETE) and UNIT SYSDA. However, the TEMPLATE for SORTOUT on the LOAD RESTART(PHASE) had UNIT TAPE. The LOAD utility correctly restarted over in the RELOAD phase, but then suffered an ABEND0C4 DSNUGSDA x'528E' in the ENFORCE phase. Although new data set checkpoint information was saved during the RESTART, the VOLSER from the initial invocation remained in the checkpoint control block. During the ENFORCE phase, this residual value prohibited LOAD from reconnecting to this checkpoint structure, losing all data set positioning values, resulting in the ABEND0C4. A LOAD with ENFORCE CONSTRAINTS should be able to restart after failing in the BUILD or SORTBLD phase as long as it is a PHASE restart in the RELOAD phase. Additional symptoms: OFFSET539C x'539C' OFFSET43D2 x'43D2' Code has been modified to enable the LOAD utility to run to completion by reinitializing data set checkpoint information during a RESTART PHASE in the RELOAD phase of LOAD utility with referential integrity checking (RI). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71459 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUREKY PM71459 DSNURPIB PM71459 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71459 DSNUREKY DSNURPIB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUREKY DSNURPIB LISTEND UK82904 COVER LETTER END 1UK82906 COVER LETTER START PROBLEM DESCRIPTION(S): PM72783 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the REPAIR DBD * * utility. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 DSNUEMC0 OFFSET3A9C when many * * REPAIR DBD TEST DATABASE dbname utility * * statements are included in one SYSIN. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** Multiple REPAIR DBD TEST DATABASE database_name utility statements were included in one SYSIN and executed. The job abended with ABEND0C4 DSNUECM0 +x'3A9C'. The abend was due to incorrect logic causing the utility to check a flag in the utility statement map that is not applicable to the REPAIR. The problem can also occur with REPAIR DIAGNOSE DBD. Also, a large number of statements is not required to hit this failure. Additional symptoms: OFFSET3840 x'38F0' Code has been modified to correct the aforementioned problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72783 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUECM0 PM72783 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72783 DSNUECM0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUECM0 LISTEND UK82906 COVER LETTER END UK83082 COVER LETTER START PROBLEM DESCRIPTION(S): PM71068 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * SQL statements that contain UNION ALL * * and recursive common table expressions. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIBNRF 5003 * * or ERQUAL5003 may occur for an SQL * * statement that satisfies the following * 1 * conditions: * * 1. The SQL statement references to a * * recursive common table expression. * * 2. The common table expression contains * * a UNION ALL and outer join. * * 3. The select list of one branch * * of the UNION ALL references to a not * * null column which comes from the * * preserving side table of the * * outer join. The select list of the * * other branch references to a not null * * value. * * 4. The values on both select list have * * different types or length. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 DSNIBNRF 5003 or ERQUAL5003 may occur for an SQL statement that satisfies the following conditions: 1. The SQL statement references to a recursive common table expression. 2. The common table expression contains a UNION ALL and outer join. 3. The select list of one branch of the UNION ALL references to a not null column which comes from the preserving side table of the outer join. The select list of the other branch references to a not null value. 4. The values on both select list have different types or length For Example, CREATE TABLE T1(C1 INT, C2 CHAR(2) NOT NULL, C3 DECIMAL NOT NULL); CREATE TABLE T2(C1 INT, C2 VARCHAR(2) NOT NULL, C3 DECIMAL NOT NULL); CREATE TABLE T3(C1 INT, C2 VARCHAR(2) NOT NULL, C3 DECIMAL NOT NULL); WITH CTE1 (C2, C3) AS ( SELECT T2.C2, 1 FROM T1 LEFT OUTER JOIN T2 ON T1.C1 = T2.C1 UNION ALL SELECT ' ' AS C2, CTE1.C3 + 1 FROM CTE1, T3 WHERE CTE1.C3 <3) SELECT CTE1.C2 FROM CTE1 ; The abend may occur for the above statement because the nullability of column T2.C2 on the select list is not set correctly. DB2 was fixed to set the nullability of the outer join column correctly. Additional Keywords: SQLNULL SQLUNIONALL SQLOUTERJOIN SQLCTE SQLRECURSIVE COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM71068 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71068: See PM71068 APAR/PTF text for additional information about why a REBIND is necessary. PM71068 corrects a problem of ABEND04E RC00C90101 DSNIBNRF 5003 or ERQUAL5003 that may occur for an SQL statement that satisfies the following conditions: 1. The SQL statement references to a recursive common table expression. 2. The common table expression contains a UNION ALL and outer join. 3. The select list of the one branch of the UNION ALL references to a not null column which came from the preserving side table of the outer join. The select list of the other branch references to a not null value. 4. The values on both select list have different types or length To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM69519: See PM69519 APAR/PTF text for additional information about why a REBIND is necessary. PM69519 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS.DSNXORLI:M111 may happen for an SQL statement that ORDER BY any empty string constant and parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM59659: See PM59659 APAR/PTF text for additional information about why a REBIND is necessary. PM59659 corrects a problem of ABEND04E RC00C90101 at DSNXIDM .DSNXOTFLA:5009 (in DB2 10) , ABEND04E RC00C900D0 at DSNXGRDS.DSNXROHB+9FF6(in DB2 10) or unexpected SQLCODE -404 (in DB2 9) could occur when a SQL statement references a LOB datatype and a different CCSID non LOB datatype in an UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change. ACTION: This PTF fixes the problem of incorrect information could be recorded in the catalog SYSCOLUMNS for an ALTER statement that satisfies the following conditions: 1. The ALTER statement is used to modify the data type of the base table columns. 2. This base table column is used inside a view that contains UNION / UNION ALL. To make this fix effective, the view that satisfies the conditions above must be drop and recreate or regenerate with the ALTER VIEW REGENERATE statement. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCT PM71068 DSNXONDA PM71068 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71068 DSNXOCT DSNXONDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCT DSNXONDA LISTEND UK83082 COVER LETTER END UK83085 COVER LETTER START PROBLEM DESCRIPTION(S): PM74186 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the * * IFCID145 trace record. * **************************************************************** * PROBLEM DESCRIPTION: SQL text in data section 4 of * * IFCID145 could be truncated when * * the length of the SQL text * * exceeds 4996 bytes. The SQL length * * field in the repeating group also * * contains invalid length. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQL text in data section 4 of IFCID145 could be truncated when the length of the SQL text exceeds 4996 bytes. Size of a single data section of any IFCID is limited to 5000 bytes. IFCID145 may try to trace 5004 bytes in the data section 4, and as a result, the SQL text after 4996 bytes could be truncated. When IFCID 145 is in effect and an SQL statement is longer than 5000 bytes, Before the fix the first repeating group contains: x'138800021388' as the first 6 bytes followed 1 by the SQL statement itself. It should be X'138800021384' after the fix. The 1384 is the SQL statement length. The 0002 is for the QW0145RT_Off field. The 1388 in position 1 is the total length of the repeating group. DB2 is updated to generate the IFCID145 trace records correctly. Additional Keywords: IFCID145 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74186 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTR3 PM74186 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74186 DSNXOTR3 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTR3 LISTEND UK83085 COVER LETTER END UK83112 COVER LETTER START PROBLEM DESCRIPTION(S): PM71078 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS * * of LPL or GRECP recovery * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 in DSNFGENM+'0BCC'x * * during Logical Page List (LPL) recovery * * or Group Buffer Pool Recover Pending * * (GRECP) recovery when trying to print * * message DSNI049I on the console log * **************************************************************** * RECOMMENDATION: * **************************************************************** During Logical Page List (LPL) recovery, a timeout was encountered such that the LPL recovery for an object was not successful. Message DSNI005I was displayed on the console log to raise awareness that the LPL recovery was not successful. Subsequently, message DSNI049I was attempted to be printed, however, various string pieces for the message were by mistake left unset and therefore garbage was passed to the message formatting code, which caused the 0C4 abend. Depending on the garbage passed to the message formatting code, another symptom of this problem is that message DSNI049I is actually printed (as opposed to abending), but showing garbage. 1 DB2 was modified to make sure that the string pieces for message DSNI049I are populated before calling the message formatting code. Additional keywords: MSGDSNI005I MSGDSNI049I COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71078 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICLST PM71078 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71078 DSNICLST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICLST LISTEND UK83112 COVER LETTER END UK83238 COVER LETTER START PROBLEM DESCRIPTION(S): PM75108 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those where the DB2 * * Communications Data Base (CDB) is defined * * with SNA inbound translation. * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: Abend 04E-00E30001 DSNTAAL+5236 * * at a DB2 10 for z/OS server when * * accepting an inbound SNA connection * * from a remote requester system. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 10 for z/OS system is configured to utilize SNA inbound translation processing relative to certain remote requester partner LU names. This is configured via SYSIBM.LUNAMES (USERNAMES='I' or 'B') and associated SYSIBM.USERNAMES (TYPE='I') CDB information relative to the remote requester SNA LU name. If the SYSIBM.USERNAMES table information indicates a PASSWORD column value that is 9 or more characters, including blanks, an erroneous 00D31039 (DSNLVINF) reason code condition will be detected during DDF server thread (DBAT) allocation processing. The erroneous (00D31039) failure during allocation processing leads to the reported abend. All SNA inbound connections that are associated to an inbound 1 translation SYSIBM.USERNAMES row with a PASSWORD length greater than 8 will be rejected as a result of the reported abend. The condition can be circumvented by updating the PASSWORD value to be 8 characters or less. Inbound translation SYSIBM.USERNAMES rows with a PASSWORD value exceeding 8 characters, including blanks, are invalid but should not cause DB2 to abend (and hence reject the inbound SNA connection). The SYSIBM.USERNAMES PASSWORD value is not relevant to SNA inbound connections. Although it is recommended that these unnecessary and/or invalid SYSIBM.USERNAMES PASSWORD values be eliminated (null) in any event, DSNLVINF has been changed to ignore the PASSWORD value relative to inbound SNA connections. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75108 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLVINF PM75108 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75108 DSNLVINF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLVINF LISTEND UK83238 COVER LETTER END UK83265 COVER LETTER START PROBLEM DESCRIPTION(S): PM71285 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS UNLOAD utility users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E4D5D2 DSNUULVA OFFSET3FFE * * or DSNU1233I during an UNLOAD utility * * SHRLEVEL CHANGE ISOLATION UR on a * * partitioned table space. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** An UNLOAD TABLESPACE SHRLEVEL CHANGE ISOLATION UR utility was run on a partition-by-range (PBR) table space concurrently with a DML UPDATE. The UPDATE resulted in a cross partition pointer- overflow record. A problem occurred when the pointer subrecord was in a partition that had a different row format than the partition of the overflow record. In one case the UNLOAD abended with an ABEND04E RC00E4D5D2 DSNUULVA x'3FFE'. However, the problem could also cause UNLOAD to issue message: 1 DSNU1233I - DATA IS TOO LONG FOR FIELD field, TABLE table. The problem can occur for any partitioned table space that has mixed BRF and RRF rowformat partitions and cross partition updates. Code has been modified to no longer follow pointer records for UNLOAD SHRLEVEL CHANGE ISOLATION UR. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71285 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUULJA PM71285 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71285 DSNUULJA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULJA LISTEND UK83265 COVER LETTER END UK83266 COVER LETTER START PROBLEM DESCRIPTION(S): PM70630 - **************************************************************** * USERS AFFECTED: All users of the DB2 10 for z/OS * * installation CLIST are affected by this * * APAR. * * * * All users of DB2 10 for z/OS installation * * job DSNTIJRI are affected by this APAR. * **************************************************************** * PROBLEM DESCRIPTION: During installation or migration to V10 * * one or more of the following problems * * is encountered: * * (1) When the LE RUNTIME LIBRARY field * * on installation panel DSNTIPU is * * set to blanks, the installation * * CLIST halts during editing of job * * DSNTIJMV and outputs the following * * message: * * IKJ52506I TEXT NOT FOUND * * (2) When large values are specified for * * work file space on installation * * panel DSNTIP9, the installation * * CLIST returns this (incorrect) * * message: * * DSNT481I DSNTINST DSNALX07 * * DATA SET SIZE MAY BE TOO SMALL. * 1 * REASON IS DATA SET SIZE LIMIT. * * (3) The indexes rebuilt by V10 job * * DSNTIJRI do not match those * * documented in the DB2 V10 * * Installation Guide. * **************************************************************** * RECOMMENDATION: Apply the PTF for this APAR. * **************************************************************** This APAR addresses the following problems: (1) When the LE RUNTIME LIBRARY field on installation panel DSNTIPU is set to blanks, the installation CLIST halts during editing of job DSNTIJMV and outputs the following message: IKJ52506I TEXT NOT FOUND The LE RUNTIME LIBRARY field accepts the local name of the IBM Language Environment runtime library, often referred to as SCEERUN. If this field contains all blanks, the DB2 installation CLIST will remove DD statements that allocate SCEERUN from the installation and sample jobs. Currently, a bug in the installation CLIST causes it to halt during edit of job DSNTIJMV when the LE RUNTIME LIBRARY field is blank. ---------------------------------------------------------------- (2) When large values are specified for work file space on installation panel DSNTIP9, the installation CLIST returns this (incorrect) message: DSNT481I DSNTINST DSNALX07 DATA SET SIZE MAY BE TOO SMALL. REASON IS DATA SET SIZE LIMIT. When you run the installation CLIST in INSTALL mode, space settings specified on panel DSNTIP9 for various types of work files are totalled up by the DSNTCALC exec and displayed on the last panel, DSNTIPC1. Currently, a bug in DSNTCALC causes it to treat the total space as the space for a single file. When the total value exceeds 2 gigabytes, the DSNT481I message shown above is displayed. ---------------------------------------------------------------- (3) The indexes rebuilt by V10 job DSNTIJRI do not match those documented in the DB2 V10 Installation Guide. Job DSNTIJRI can be run after completion of job DSNTIJTC to rebuild indexes on tables affected by DB2 catalog tailoring (CATMAINT) during migration to V10 conversion mode. These indexes are documented in the DB2 Installation Guide in the discussion of DSNTIJRI. They are listed according to whether you have migrated from V8 or from V9. The indexes currently rebuilt by DSNTIJRI do not need to be rebuilt if migration was from V9 - only if migration was from V8. Also, the job currently has no statement 1 for rebuilding DSNXRX01; this index might need to be rebuilt after running DSNTIJTC, whether migration was from V8 or from V9. In response to these problems, this APAR makes the following changes: (1) Installation CLIST logic for editing DSNTIJMV is corrected to handle the case where the LE RUNTIME LIBRARY field is set to blanks. This prevents the CLIST from halting. (2) Installation CLIST space calculations in DSNTCALC are corrected to no longer treat the total space specified for new work files as though it was for a single file. This prevents the CLIST from reporting that the file is too large. (3) DSNTIJRI is modified to rebuild index DSNXRX01. The other rebuild index statements are removed so that, by default, DSNTIJRI is for use for migration from V9. If the DB2 installation CLIST is run for migration from V8, it will readd the rebuild index statements that may be needed after migrating to V10 conversion mode from V8. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70630 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM70630 (V10) This PTF corrects the following errors: (1) A bug that can cause the DB2 installation CLIST to halt during edit of job DSNTIJMV (2) A bug that can cause the CLIST to report insufficient data set size when a large amount of storage is specified for the DB2 work file database. (3) Missing and extraneous REBUILD INDEX statements in job DSNTIJRI. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Optionally update customized copies of job DSNTIJRI Detail for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required for all V10 customers This PTF modifies CLIST members DSNTCALC, DSNTINS1, and DSNTINS2 in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of these CLISTs. You may also want to move them to the prefix.NEW.SDSNCLST 1 data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Optionally update customized copies of job DSNTIJRI ---------------------------------------------------------------- ==> This action is recommended for V10 customers who maintain a customized copy of job DSNTIJRI The DSNTIJRI job can be used to rebuild indexes on DB2 catalog tables that are affected by DB2 catalog tailoring (job DSNTIJEN) during migration to V10 conversion mode. This PTF adds a missing REBUILD INDEX statement to the DSNTIJRI job in the SDSNSAMP target library only. If you maintain a private copy of this job, you need to add the following statement under the SYSIN DD of job step DSNRI1: REBUILD INDEX ("SYSIBM"."DSNXRX01") SORTDEVT(SYSDA) SORTNUM(5) If you migrated to V10 from V9, you can optionally remove the other REBUILD INDEX statements. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTCALC PM70630 DSNTIJRI PM70630 DSNTINS1 PM70630 DSNTINS2 PM70630 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70630 DSNTCALC DSNTIJRI DSNTINS1 DSNTINS2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTCALC DSNTIJRI DSNTINS1 DSNTINS2 LISTEND UK83266 COVER LETTER END UK83268 COVER LETTER START PROBLEM DESCRIPTION(S): PM71835 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures. * **************************************************************** * PROBLEM DESCRIPTION: The following abend may happen when * * calling an external stored procedure: * * * * ABND=04E-00E70005, * * LOC=DSNXGRDS.DSNXOSTP:M270 * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** During routine resolution, DB2 obtains routine information and parm information from SYSROUTINES and SYSPARMS catalog table and store the information in a DB2 control block. In this case, DB2 failed to get parm info from SYSPARMS catalog table and therefore could not store the parm info into the DB2 control block. This results in the 04E abend later when DB2 tries to reference the parm info in the control block. DB2 code has been changed to return an SQLCODE -440 if catalog lookup fails to find the record for parms. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71835 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9CAT PM71835 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71835 DSNX9CAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9CAT LISTEND UK83268 COVER LETTER END UK83355 COVER LETTER START PROBLEM DESCRIPTION(S): PM73350 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the PACK/UNPACK * * scalar function. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E30066 can occur at * * location DSNTGSCC.DSNTBBP2+1E5E when an * * SQL statement that contains the PACK or * * UNPACK scalar function references a * * view. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E30066 can occur at location DSNTBBP2 +1E5E (OFFSET1E5E) when the PACK or UNPACK scalar function is contained in an SQL statement which references a VIEW. The following example illustrates a failing case. Step 1. Create two Tables and two Views. 1 CREATE TABLE T1 (C1 VARCHAR(5), C2 INTEGER); CREATE TABLE T2 (C1 VARCHAR(5), C2 SMALLINT); CREATE VIEW V1 (C1,C2) AS SELECT C1, SUM(C2) FROM T2 GROUP BY C1; CREATE VIEW V2 AS SELECT T1.C1 FROM T1, V1 WHERE T1.C1 = V1.C1; Step 2. Execute the following SQL statement. SELECT PACK( CCSID 1208, 1) INTO VAR1 FROM V2; The execution of this query can result in the abend mentioned above. Please note that the reported problem occurred with a VIEW reference. However, it is possible the problem can occur without a view reference as well. The code in DB2 is modified to process the PACK/UNPACK function properly which will avoid the abend. Additional Keywords: SQLPACK SQLUNPACK SQLVIEW COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73350 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOBFA PM73350 DSNXOBFF PM73350 DSNXOBF3 PM73350 DSNXOBF4 PM73350 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73350 DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 LISTEND UK83355 COVER LETTER END 1UK83359 COVER LETTER START PROBLEM DESCRIPTION(S): PM70647 - **************************************************************** * USERS AFFECTED: Users of REPAIR DBD utility * **************************************************************** * PROBLEM DESCRIPTION: REPAIR DBD TEST/DIAGNOSE reports error * * on table schema name if it contains * * trailing blank(s). * * DSNU920I DSNUEDRT comparison errors * * were found on OBDRX_CRE_NAME_LEN * **************************************************************** * RECOMMENDATION: * **************************************************************** Trailing blanks are insignificant in DB2 identifiers. REPAIR DBD TEST/DIAGNOSE should not report error if table schema name has trailing blank. REPAIR DBD is fixed to not report error if table schema name contains trailing blank. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70647 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUEDFS PM70647 DSNUEDRT PM70647 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70647 DSNUEDFS DSNUEDRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUEDFS DSNUEDRT LISTEND UK83359 COVER LETTER END UK83407 COVER LETTER START PROBLEM DESCRIPTION(S): PM74194 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of partition-by-growth (PBG) * * universal table spaces. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DSNITCUS+011C may occur * * on an insert which causes a new * * partition to be created. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 ABEND0C4 DSNITCUS+011C and other unexpected results may occur on operations, such as INSERT, LOAD, and REORG, which may cause new partitions to be created. The abend is caused by uninitialized CUB storage. The local CUB storage has been initialized to prevent unexpected results on operations which cause new partitions to be created. ADDITIONAL KEYWORDS: SQLPBG SQLALTER SQLINSERT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74194 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIPGA PM74194 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74194 DSNXIPGA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIPGA LISTEND UK83407 COVER LETTER END UK83409 COVER LETTER START PROBLEM DESCRIPTION(S): PM65003 - **************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and * * SQLJ version 4.14.119 is provided by * * this APAR ( JCCV414119 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for both DB2 z/OS V10 and DB2 z/OS V9 * * ( JCCZOSDB2V10, JCCZOSDB2V9 ) * * * * This APAR delivers a new release (4.14) * * of the IBM Data Server Driver for JDBC * * and SQLJ providing an accumulation of * * defect fixes and enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: _______________________________________________________________ All Connectivities: Driver added getAffectedRowCount() API on com.ibm.db2.jcc.DB2Statement interface to return the affected row count number after a successful SQL execution. The affected row count will have the same value that is returned by the database server in the SQLCA after a successful execution of the SQL. (wsdbu01002565) _______________________________________________________________ All Connectivities: Driver improved the performance for JDBC API PreparedStatement.clearParameters(). (wsdbu01041918) _______________________________________________________________ All Connectivities: An SQL statement with more than 2MB size executed by the driver results in dump files creation and the db2diag.log file showing invalid SQL statement length. This problem is fixed. (wsdbu01040802) _______________________________________________________________ All Connectivities: java.sql.Timestamp.valueOf(String s) and com.ibm.db2.jcc.DBTimestamp.valueOfDBString(String s) should behave the same. However, java.sql.Timestamp.valueOf(String s) works with single digit month value, but the same value fails for com.ibm.db2.jcc.DBTimestamp.valueOfDBString(String s). This problem is fixed. (wsdbu01037037) _______________________________________________________________ All Connectivities: When both IBM Data Server Driver for JDBC and SQLJ and Informix native driver are presented in the application classpath and the application specified informix-sqli protocol in the database connection url intending to use the Informix native driver, the IBM Data Server Driver may intercept the call and try to return a connection preventing the Informix native driver to be used. This problem is fixed.(wsdbu01014749) _______________________________________________________________ All Connectivities: Adding a new option to DB2ConnectActivate to handle the secondary id. The option is activatorsqlid. Usage: java -cp com.ibm.db2.jcc.DB2ConnectActivate -host -port -database -user -password İ-bind ( no | yes )¨ İ-collection ¨ İ-activatorsqlid ¨ İ-uninstall ( no | yes )¨ İ-trace ( no | yes )¨ İ-help¨ (wsdbu01004425) 1 _______________________________________________________________ All Connectivities: De-serialize a serialized SQLException object using different IBM Data Server Driver for JDBC and SQLJ version may result in java.lang.RuntimeException or other Exceptions due to incompatible Java Class. This problem is fixed. (wsdbu01003673) _______________________________________________________________ All Connectivities: An java.lang.SecurityException occurs when using the driver with Java SecurityManager enabled even if all permissions are granted to the driver through the applicable security policy. Applications running with -Djava.security.manager option as well as all applets were affected. This problem is fixed. (wsdbu00708452) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when the driver cannot connect to a member and returns a SQLCODE4499 (-4499) error, the connectionErrorOccurred() method might not be called on the connection pool manager(registered event listener). As a result, the subsequent call on this connection will result in a SQLCODE4470 (-4470) error. This problem has been fixed. (wsdbu01058341, wsdbu01059324, wsdbu01058206) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when all the members are not available and there are huge number of threads trying to failover at the same time, a massive flood of sockets might occur. This could result in SQLCODE4499 (-4499) error with message "java.net.BindException: Address already in use: Cannot bind". This is due to a large number of sockets are still in TIME_WAIT and it is reaching the resource limit on the client machine. In addition, SQLCODE1244 (-1224), database manager not accepting new requests error may also occur. This problem has been fixed. (wsdbu01059128) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment where maxRetriesForClientReroute, retryIntervalForClientReroute properties are not set and the application has not made its first successful connection to the group, then the driver loops for 10 minutes before reporting the error. This default behavior has been changed now to retry five times with retryIntervalForClientReroute set to zero when the driver can't even make its first successful connection. However, if a cached server list or an alternate server is specified, the driver will retry 10 minutes during the failover. This is the new default behavior. (wsdbu01049788) _______________________________________________________________ Type-4 Connectivity: If client application with alternate group enabled(enableAlternateGroupSeamlessACR=true) fails over from a primary group (ex: DB2 V10) to a lower version DB2 sysplex group (ex: DB2 V9), queries start to fail. This problem is fixed. (wsdbu01045871) _______________________________________________________________ Type-4 Connectivity: While performing failover during CallableStatement.executeBatch() call, the driver fails to replay the SQL in both workload balancing and sysplex environments even if its at the beginning of the transaction. This defect is fixed. (wsdbu01045345) 1 _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when the primary member is down, the driver may repeatedly throw an SQLException with SQLCODE4499 (-4499) even though other members are available in the system. (wsdbu01045054) _______________________________________________________________ Type-4 Connectivity: With sysplex enabled, when connected to a setup with 3 or more members, application might hang if first two members are brought down one by one. This problem is fixed. (wsdbu01043132) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, an SQLException with SQLCODE204 (-204) may be thrown to the application if a reuseDB2Connection() method is called after successfully failover. This problem is fixed. (wsdbu01041920) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment against pureScale server, even after driver opened its first connection successfully to the primary member and had received the server list of more than one member, the subsequent connections failed to connect to any other members in the server list if the primary member went down. This problem is fixed. (wsdbu01032594) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, the driver has made a performance improvement by not retrying the connectivity to the member that is known unavailable during the auto failover. (wsdbu01031011) _______________________________________________________________ Type-4 Connectivity: A new securityMechanism, com.ibm.db2.jcc. DB2BaseDataSource.TLS_CLIENT_CERTIFICATE_SECURITY, is introduced when connecting to zOS server. When application uses CLIENT_CERTIFICATE_SECURITY, the driver will use SSLSocket to communicate to DB2 server, and the mutual authentication will be done at the network layer using the TLS/SSL. If the target server supports this security mechanism and the mutual authentication is passed, a valid Connection will be returned to the application. If the server does not support this security mechanism or the connection was not authenticated using the TLS/SSL, the drive will throw an DisconnectException. (wsdbu01023931) _______________________________________________________________ Type-4 connectivity: When there is an error during socket creation, the error reported by the driver was incorrectly reporting a message text that included "See attached Throwable for details" even there was no attached java.lang.Throwable. This problem is fixed. (wsdbu01006532) _______________________________________________________________ Type-4 Connectivity: Driver throws SQLException with SQLCODE4225 (-4225) when executing a "SELECT INTO TEMP" statement against Informix database server. This problem is fixed. (wsdbu01000497) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, the value returned by APIs numberOfRequestsBlockedPoolMax() and totalTimeBlocked() from the object that is based on the 1 com.ibm.db2.jcc.DB2PoolMonitor class might not be correct. This problem is fixed. (wsdbu01000053) _______________________________________________________________ Type-4 connectivity: The properties, alternateGroupServerName, alternateGroupDatabaseName, and alternateGroupPortNumber, do not get applied to a connection when supplied through a java.util.Properties object to the java.sql.DriverManager.getConnection(url, prop) API. This has been fixed. (wsdbu00996633) _______________________________________________________________ Type-4 Connectivity: Driver performs a seamless failover even when enableAlternateGroupSeamlessACR is set to false. This defect is fixed (wsdbu00995499) _______________________________________________________________ Type-4 connectivity: When executing batch statements with no input data as a simple insert statement, NullPointerException is thrown in addBatch() API call if sendDataAsIs property is enabled or set to true. This issue is fixed. (wsdbu01043185). _______________________________________________________________ Type-4 XA Connectivity: During auto failover scenario in a workload balancing environment against DB2 zOS server, an XAException with XAER_NOTA error may be thrown on a XA Commit (one phase commit) call even if the driver has successfully failover to a member after starting of a XA transaction. This problem has been fixed. (wsdbu01058658) _______________________________________________________________ Type-2 z/OS Connectivity: A new DataSource/Connection property, currentLocaleLcCtype, is introduced to set the CURRET LOCALE LC_CTYPE special register on DB2 server. This property can only be set before Connection creation and cannot be changed afterwards. (wsdbu01005252) _______________________________________________________________ Type-2 z/OS Connectivity: Driver is no longer overriding column sqltype nullable for Limited Block Fetch against DB2 z/OS V10 due to the fact it may cause potential problem when the fetched column has LOB/XML type and the nullable attribute is NOT NULL. (wsdbu01029064) The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR. COMPONENT: 5740-XYR02-JDBAA12 APARS FIXED: PM65003 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58952 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. 1 See PM58952 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAJJC1 PM65003 DSNAJJC2 PM65003 DSNAJ3CC PM65003 DSNAJ3CE PM65003 DSNAJ3CF PM65003 DSNAJ3CM PM65003 DSNAJ3C0 PM65003 DSNAJ3C1 PM65003 DSNAJ3C2 PM65003 DSNAJ3C3 PM65003 DSNAJ3C4 PM65003 DSNAJ3C5 PM65003 DSNAJ3C6 PM65003 DSNAJ3C7 PM65003 DSNAJ3C9 PM65003 DSNAJ6CC PM65003 DSNAJ6CE PM65003 DSNAJ6CF PM65003 DSNAJ6CM PM65003 DSNAJ6C0 PM65003 DSNAJ6C1 PM65003 DSNAJ6C2 PM65003 DSNAJ6C3 PM65003 DSNAJ6C4 PM65003 DSNAJ6C5 PM65003 DSNAJ6C6 PM65003 DSNAJ6C7 PM65003 DSNAJ6C9 PM65003 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65003 DSNAJJC1 DSNAJJC2 DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5 DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5 DSNAJ3C6 1 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9 MACROS DSNAJJC1 DSNAJJC2 LISTEND UK83409 COVER LETTER END UK83411 COVER LETTER START PROBLEM DESCRIPTION(S): PM65007 - **************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and * * SQLJ version 3.64.111 is provided by * * this APAR ( JCCV364111 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for DB2 z/OS V10, DB2 z/OS V9 and * * the alternate supplemental driver * * for DB2 z/OS V8. ( JCCZOSDB2V10, * * JCCZOSDB2V9, JCCZOSDB2V8) * * * * This APAR delivers a new release (3.64) * * of the IBM Data Server Driver for JDBC * * and SQLJ providing an accumulation of * * defect fixes and enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: 1 _______________________________________________________________ All Connectivities: Driver added getAffectedRowCount() API on com.ibm.db2.jcc.DB2Statement interface to return the affected row count number after a successful SQL execution. The affected row count will have the same value that is returned by the database server in the SQLCA after a successful execution of the SQL. (wsdbu01002565) _______________________________________________________________ All Connectivities: Driver improved the performance for JDBC API PreparedStatement.clearParameters(). (wsdbu01041918) _______________________________________________________________ All Connectivities: An SQL statement with more than 2MB size executed by the driver results in dump files creation and the db2diag.log file showing invalid SQL statement length. This problem is fixed. (wsdbu01040802) _______________________________________________________________ All Connectivities: java.sql.Timestamp.valueOf(String s) and com.ibm.db2.jcc.DBTimestamp.valueOfDBString(String s) should behave the same. However, java.sql.Timestamp.valueOf(String s) works with single digit month value, but the same value fails for com.ibm.db2.jcc.DBTimestamp.valueOfDBString(String s). This problem is fixed. (wsdbu01037037) _______________________________________________________________ All Connectivities: When both IBM Data Server Driver for JDBC and SQLJ and Informix native driver are presented in the application classpath and the application specified informix-sqli protocol in the database connection url intending to use the Informix native driver, the IBM Data Server Driver may intercept the call and try to return a connection preventing the Informix native driver to be used. This problem is fixed.(wsdbu01014749) _______________________________________________________________ All Connectivities: Adding a new option to DB2ConnectActivate to handle the secondary id. The option is activatorsqlid. Usage: java -cp com.ibm.db2.jcc.DB2ConnectActivate -host -port -database -user -password İ-bind ( no | yes )¨ İ-collection ¨ İ-activatorsqlid ¨ İ-uninstall ( no | yes )¨ İ-trace ( no | yes )¨ İ-help¨ (wsdbu01004425) _______________________________________________________________ All Connectivities: De-serialize a serialized SQLException object using different IBM Data Server Driver for JDBC and SQLJ version may result in java.lang.RuntimeException or other Exceptions due to incompatible Java Class. This problem is fixed. (wsdbu01003673) _______________________________________________________________ 1 All Connectivities: An java.lang.SecurityException occurs when using the driver with Java SecurityManager enabled even if all permissions are granted to the driver through the applicable security policy. Applications running with -Djava.security.manager option as well as all applets were affected. This problem is fixed. (wsdbu00708452) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when the driver cannot connect to a member and returns a SQLCODE4499 (-4499) error, the connectionErrorOccurred() method might not be called on the connection pool manager(registered event listener). As a result, the subsequent call on this connection will result in a SQLCODE4470 (-4470) error. This problem has been fixed. (wsdbu01058341, wsdbu01059324, wsdbu01058206) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when all the members are not available and there are huge number of threads trying to failover at the same time, a massive flood of sockets might occur. This could result in SQLCODE4499 (-4499) error with message "java.net.BindException: Address already in use: Cannot bind". This is due to a large number of sockets are still in TIME_WAIT and it is reaching the resource limit on the client machine. In addition, SQLCODE1244 (-1224), database manager not accepting new requests error may also occur. This problem has been fixed. (wsdbu01059128) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment where maxRetriesForClientReroute, retryIntervalForClientReroute properties are not set and the application has not made its first successful connection to the group, then the driver loops for 10 minutes before reporting the error. This default behavior has been changed now to retry five times with retryIntervalForClientReroute set to zero when the driver can't even make its first successful connection. However, if a cached server list or an alternate server is specified, the driver will retry 10 minutes during the failover. This is the new default behavior. (wsdbu01049788) _______________________________________________________________ Type-4 Connectivity: If client application with alternate group enabled(enableAlternateGroupSeamlessACR=true) fails over from a primary group (ex: DB2 V10) to a lower version DB2 sysplex group (ex: DB2 V9), queries start to fail. This problem is fixed. (wsdbu01045871) _______________________________________________________________ Type-4 Connectivity: While performing failover during CallableStatement.executeBatch() call, the driver fails to replay the SQL in both workload balancing and sysplex environments even if its at the beginning of the transaction. This defect is fixed. (wsdbu01045345) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, when the primary member is down, the driver may repeatedly throw an SQLException with SQLCODE4499 (-4499) even though other members are available in the system. (wsdbu01045054) _______________________________________________________________ Type-4 Connectivity: With sysplex enabled, when connected to a 1 setup with 3 or more members, application might hang if first two members are brought down one by one. This problem is fixed. (wsdbu01043132) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, an SQLException with SQLCODE204 (-204) may be thrown to the application if a reuseDB2Connection() method is called after successfully failover. This problem is fixed. (wsdbu01041920) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment against pureScale server, even after driver opened its first connection successfully to the primary member and had received the server list of more than one member, the subsequent connections failed to connect to any other members in the server list if the primary member went down. This problem is fixed. (wsdbu01032594) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, the driver has made a performance improvement by not retrying the connectivity to the member that is known unavailable during the auto failover. (wsdbu01031011) _______________________________________________________________ Type-4 Connectivity: A new securityMechanism, com.ibm.db2.jcc. DB2BaseDataSource.TLS_CLIENT_CERTIFICATE_SECURITY, is introduced when connecting to zOS server. When application uses CLIENT_CERTIFICATE_SECURITY, the driver will use SSLSocket to communicate to DB2 server, and the mutual authentication will be done at the network layer using the TLS/SSL. If the target server supports this security mechanism and the mutual authentication is passed, a valid Connection will be returned to the application. If the server does not support this security mechanism or the connection was not authenticated using the TLS/SSL, the drive will throw an DisconnectException. (wsdbu01023931) _______________________________________________________________ Type-4 connectivity: When there is an error during socket creation, the error reported by the driver was incorrectly reporting a message text that included "See attached Throwable for details" even there was no attached java.lang.Throwable. This problem is fixed. (wsdbu01006532) _______________________________________________________________ Type-4 Connectivity: Driver throws SQLException with SQLCODE4225 (-4225) when executing a "SELECT INTO TEMP" statement against Informix database server. This problem is fixed. (wsdbu01000497) _______________________________________________________________ Type-4 Connectivity: In a workload balancing environment, the value returned by APIs numberOfRequestsBlockedPoolMax() and totalTimeBlocked() from the object that is based on the com.ibm.db2.jcc.DB2PoolMonitor class might not be correct. This problem is fixed. (wsdbu01000053) _______________________________________________________________ Type-4 connectivity: The properties, alternateGroupServerName, alternateGroupDatabaseName, and alternateGroupPortNumber, do not get applied to a connection when supplied through a java.util.Properties object to the 1 java.sql.DriverManager.getConnection(url, prop) API. This has been fixed. (wsdbu00996633) _______________________________________________________________ Type-4 Connectivity: Driver performs a seamless failover even when enableAlternateGroupSeamlessACR is set to false. This defect is fixed (wsdbu00995499) _______________________________________________________________ Type-4 connectivity: When executing batch statements with no input data as a simple insert statement, NullPointerException is thrown in addBatch() API call if sendDataAsIs property is enabled or set to true. This issue is fixed. (wsdbu01043185). _______________________________________________________________ Type-4 XA Connectivity: During auto failover scenario in a workload balancing environment against DB2 zOS server, an XAException with XAER_NOTA error may be thrown on a XA Commit (one phase commit) call even if the driver has successfully failover to a member after starting of a XA transaction. This problem has been fixed. (wsdbu01058658) _______________________________________________________________ Type-2 z/OS Connectivity: A new DataSource/Connection property, currentLocaleLcCtype, is introduced to set the CURRET LOCALE LC_CTYPE special register on DB2 server. This property can only be set before Connection creation and cannot be changed afterwards. (wsdbu01005252) _______________________________________________________________ Type-2 z/OS Connectivity: Driver is no longer overriding column sqltype nullable for Limited Block Fetch against DB2 z/OS V10 due to the fact it may cause potential problem when the fetched column has LOB/XML type and the nullable attribute is NOT NULL. (wsdbu01029064) The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR. COMPONENT: 5740-XYR02-JDBAA12 APARS FIXED: PM65007 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58951 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58951 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAQJBA PM65007 1 DSNAQJBB PM65007 DSNAQJB1 PM65007 DSNAQJB2 PM65007 DSNAQJB3 PM65007 DSNAQJB4 PM65007 DSNAQJB5 PM65007 DSNAQJB6 PM65007 DSNAQJB7 PM65007 DSNAQJB8 PM65007 DSNAQJC1 PM65007 DSNAQJC2 PM65007 DSNAQJC3 PM65007 DSNAQJC4 PM65007 DSNAQJRM PM65007 DSNAQJS1 PM65007 DSNAQJS2 PM65007 DSNAQ3CA PM65007 DSNAQ3CC PM65007 DSNAQ3CE PM65007 DSNAQ3CF PM65007 DSNAQ3CM PM65007 DSNAQ3C0 PM65007 DSNAQ3C1 PM65007 DSNAQ3C2 PM65007 DSNAQ3C3 PM65007 DSNAQ3C4 PM65007 DSNAQ3C5 PM65007 DSNAQ3C6 PM65007 DSNAQ3C7 PM65007 DSNAQ3C8 PM65007 DSNAQ3C9 PM65007 DSNAQ3E1 PM65007 DSNAQ6CC PM65007 DSNAQ6CE PM65007 DSNAQ6CF PM65007 DSNAQ6CM PM65007 DSNAQ6C0 PM65007 DSNAQ6C1 PM65007 DSNAQ6C2 PM65007 DSNAQ6C3 PM65007 DSNAQ6C4 PM65007 DSNAQ6C5 PM65007 DSNAQ6C6 PM65007 DSNAQ6C7 PM65007 DSNAQ6C9 PM65007 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65007 DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9 MACROS DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3E1 LISTEND UK83411 COVER LETTER END 1UK83427 COVER LETTER START PROBLEM DESCRIPTION(S): PM74401 - **************************************************************** * USERS AFFECTED: All DB2 Users preparing for new release * **************************************************************** * PROBLEM DESCRIPTION: DB2 internal change to support future * * functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR does not address or fix any problem in DB2. It contains changes in support of a future function. This APAR does not have any external symptoms. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74401 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDCLN PM74401 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74401 DSNGDCLN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDCLN LISTEND UK83427 COVER LETTER END UK83430 COVER LETTER START PROBLEM DESCRIPTION(S): PM75488 - **************************************************************** * USERS AFFECTED: All DB2 users of pre-v8 bound packages * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at * * DSNXGRDS . DSNXVTRS : M420 * * OR * * ABEND04E RC00E2000C at * * DSNXEDP . DSNSVSVB +0AC2 * **************************************************************** * RECOMMENDATION: * **************************************************************** In the reported case, customer had a stored procedure package bound on DB2 V7. This package contained a statement (eg. s1) that did not bind successfully. When this package was executed on DB2 10, statement s1 was rebound and successfully executed. A subsequent statement in the package dropped an object that s1 referenced, 1 causing invalidation of s1. When s1 was re-executed, it underwent incremental rebind on DB2 10. During incremental rebind, a downstream module used an incorrect offset to access statement text in the internal control block representing s1, leading to the reported abend. DB2 code has been modified to correctly access the statement text in an internal control block during incremental rebind of a section in pre-v8 bound package. RELATED KEYWORDS: 04E 00E70005 00E2000C COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75488 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXERB PM75488 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75488 DSNXERB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERB LISTEND UK83430 COVER LETTER END UK83431 COVER LETTER START PROBLEM DESCRIPTION(S): PM73246 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS with * * TABLESAMPLE SYSTEM and COLGROUP options. * **************************************************************** * PROBLEM DESCRIPTION: A RUNSTATS, with the TABLESAMPLE SYSTEM * * and COLGROUP options, abended with * * ABEND04E RC00E40005 and RC00E40347 * * along with MSGDSNU044I and MSGICE046A * * after MSGDSNU1373I was issued. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** RUNSTATS TABLESPACE with COLGROUP TABLESAMPLE SYSTEM specified was run on a segmented table space and message DSNU1373I - PAGE SAMPLING NOT DONE FOR TABLESPACE ts_name was issued. However, this caused RUNSTATS to pass a zero file size to DFSORT which in turn caused DFSORT to allocate insufficient storage for its use and failed with message ICE046A - SORT CAPACITY EXCEEDED - RECORD COUNT nnn. RUNSTATS then issued message DSNU044I - ERROR FROM SORT COMPONENT RC=16, UTILITY STOPPED and abended 1 with ABEND04E RC00E40005 and RC00E40347. RUNSTATS TABLESPACE TABLESAMPLE SYSTEM code has been modified to bypass sampling code when sampling has been forced off. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73246 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSITS PM73246 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73246 DSNUSITS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSITS LISTEND UK83431 COVER LETTER END UK83440 COVER LETTER START PROBLEM DESCRIPTION(S): PM74977 - **************************************************************** * USERS AFFECTED: All DB2 10 users of the DISPLAY GROUP   * * command preparing for a new release. * **************************************************************** * PROBLEM DESCRIPTION: DB2 DISPLAY GROUP command update * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR does not address any current problem in DB2 10. It contains changes in preparation of future functions.       DB2 DISPLAY GROUP command processing code has been updated in   preparation for a future function.     COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74977 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN7GCMD PM74977 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74977 DSN7GCMD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN7GCMD 1 LISTEND UK83440 COVER LETTER END UK83463 COVER LETTER START PROBLEM DESCRIPTION(S): PM72274 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who use * * IBM DB2 Analytics Accelerator * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides DB2 10 for z/OS * * support for IBM DB2 Analytics * * Accelerator V3. IBM DB2 Analytics * * Accelerator V3 introduces the * * following new features and * * enhancements pertaining to DB2 * * query offloading: * * 1. High Performance Storage Saver * * (HPSS) support * * 2. New subsystem parameter * * GET_ACCEL_ARCHIVE * * 3. New value for subsystem parameter * * QUERY_ACCEL_OPTIONS * * 4. New column ARCHIVE is added to * * SYSACCEL.SYSACCELERATEDTABLES * * 5. DB2 Instrumentation Facility * * related to acceleration services * * is updated/added for serviceability * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR provides DB2 10 for z/OS support for IBM DB2 Analytics Accelerator V3. IBM DB2 Analytics Accelerator V3 introduces the following new main features and enhancements pertaining to DB2 query offloading: 1. HPSS support 2. New subsystem parameter DSN6SPRM.GET_ACCEL_ARCHIVE 3. New value for subsystem parm DSN6SPRM.QUERY_ACCEL_OPTIONS 4. New column ARCHIVE is added to SYSACCEL.SYSACCELERATEDTABLES 5. DB2 Instrumentation Facility related to acceleration services is updated/added for serviceability IBM DB2 Analytics Accelerator V3 is introducing High Performance Storage Saver (HPSS) support. Before HPSS, DB2 keeps all the data that are moved into DB2 Analytics Accelerator. With HPSS, the user can choose to only store the active data on DB2 and DB2 Analytics Accelerator while leaving the history data on DB2 Analytics Accelerator only. This APAR adds a new DB2 subsystem parameter, DSN6SPRM.GET_ACCEL_ARCHIVE. This parameter specifies the default setting of the CURRENT GET_ACCEL_ARCHIVE special register. This is the value used when this special register has not been set by means of the SET CURRENT GET_ACCEL_ARCHIVE statement. Valid options are: 1 * NO : Specifies that when a table is archived in IBM DB2 Analytics Accelerator, the table reference does not include the accelerator archived data. ====> This is the default setting * YES: Specifies that when a table is archived in IBM DB2 Analytics Accelerator, the table reference includes the archived data. This APAR also adds a new option, 3, to an existing DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS. This parameter is used to specify additional types of SQL queries to be included in query offloading. It previously had three options: * NONE: Query offloading is restricted to the standard SQL statements ==> This is the default setting. * 1 : The queries that include data encoded by multi-byte character set EBCDIC encoding scheme are not blocked from executing on IBM DB2 Analytics Accelerator. * 2 : For INSERT statements where a fullselect specifies the data to be inserted, the fullselect part is not blocked from executing on IBM DB2 Analytics Accelerator although the data operated on by the fullselect may not be current in the accelerator. The fullselect will be considered for offload as if it were a stand-alone statement, except that DB2 will not offload the fullselect if the target table of the INSERT has a different encoding scheme than any tables referenced in the fullselect. The new option, 3, specifies that: * 3 : The queries that include DB2 byte-based string functions on data encoded by multi-byte character sets encoding schemes (like Unicode) are not blocked from executing on IBM DB2 Analytics Accelerator although it supports only character-based string functions. If the data on which the string function is specified contains only single-byte characters, executing the function on IBM DB2 Analytics Accelerator will return the same result as executing the function on DB2 irrespective of what encoding scheme is used for the data. However, if the data contains multi-byte characters, the results will not be the same. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is mutually exclusive from all other settings. Options 1, 2, and 3 can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=3 1 QUERY_ACCEL_OPTIONS=(1,2) QUERY_ACCEL_OPTIONS=(1,3) QUERY_ACCEL_OPTIONS=(2,3) This APAR also adds support for a new column, ARCHIVE, to SYSACCEL.SYSACCELERATEDTABLES, a table in the accelerator database. This new column indicates whether the table is archived in IBM DB2 Analytics Accelerator and what portion of the data it contains. It is set by an IBM DB2 Analytics Accelerator stored procedure ACCEL_ARCHIVE_TABLES and used by DB2 for query offloading decision making. Also, the lock size of the containing table space, SYSACCEL, is changed from PAGE to ROW. Figure 1: ========= Column Name Data Type Description ----------- --------- ----------- ARCHIVE CHAR(1) Archive status of the table in the accelerator database. A: Table is archived in the accelerator and the corresponding accelerator contains both active and archived data C: Table is archived in another accelerator and the corresponding accelerator contains the active (current) data only blank: Table is not archived in IBM DB2 Analytics Accelerator ARCHIVE is 'A' when a table is archived in the accelerator as shown in Figure 1. ARCHIVE is set to 'C' after a table is archived on one accelerator by invoking IBM DB2 Analytics Accelerator stored procedure ACCEL_ARCHIVE_TABLES, and IBM DB2 Analytics Accelerator stored procedure ACCEL_LOAD_TABLES is invoked to load data from DB2 into another accelerator. Each table must have at most one row with the value of 'A'. If there exists one entry with 'C' for a given table, there must also exist an entry with 'A'. Otherwise, all rows for the table must be blank. There are also some serviceability changes in this APAR: IFCID 148 field QW0148ST is updated to include the status of the thread that is currently processing an activity related to query acceleration, using a value of 'AC'. The mapping of DSNDQWAC will include a new wait time as follows: 1 QWACAACC Number of wait trace event processed for requests to an accelerator QWACAACW Accumulated wait time for requests to an accelerator The mapping of DSNDQPAC will include a new wait time as follows: QPACAACC Number of wait trace event processed for requests to an accelerator while executing this package QPACAACW Accumulated wait time for requests to an accelerator while executing this package These values will be reflected in IFCID 3, IFCID 239, IFCID 148, IFCID 147, and IFCID 346. To trigger the collection of these new fields, IFCID 378 will be created to document the beginning and IFCID 379 will be created to document the end of an accelerator call event. This record will be included in accounting and monitor classes 3 and 8. **************************************************************** * IFCID 0378 marks the beginning of an accelerator call event * **************************************************************** * QW0378 QW0378ACL Length of Accelerator Name QW0378ACN Name of Accelerator **************************************************************** * IFCID 0379 marks the end of an accelerator call event * **************************************************************** * QW0379 QW0379ACL Length of Accelerator Name QW0379ACN Name of Accelerator Some Q8ST fields are sometimes zero until the connection is terminated. Q8ST statistics will now be collected more frequently so that the statistics data collection is not limited to be available only at the end of thread termination. Some Q8ST fields will become serviceability fields. Such fields in the Q8ST will be marked (S) that were previously externalized. These fields will no longer be formally supported so applications relying on their content should be changed. See HOLD data for information on these fields. Additional Keywords: IDAAV3R1/K IFCID106 IFCID3 IFCID003 IFCID239 IFCID148 IFCID147 IFCID346 IFCID378 IFCID379 Code is added to support IBM DB2 Analytics Accelerator V3 as described above. IFCID 106 is updated to report the new value of QUERY_ACCEL_OPTIONS and the new parameter GET_ACCEL_ARCHIVE. Serviceability fixes described above are 1 added to support the new function. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72274 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: SQL code -4742 is updated to describe when this code can be issued if the new special register CURRENT GET_ACCEL_ARCHIVE is set to YES. The approximate description containing the new text of SQL code -4742 in the DB2 Codes manual is shown below. Refer to the DB2 Codes manual for the exact description. -4742 The statement cannot be executed by DB2 or in the accelerator (REASON reason-code) Explanation: A statement cannot be executed by DB2 or by an accelerator server. | The statement cannot be executed by DB2 if any of the | following conditions are true: | . Special register CURRENT GET_ACCEL_ARCHIVE is set to YES, | and the statement needs to access the data that is stored | only in the accelerator server. . Special register CURRENT QUERY ACCELERATION is set to ALL, so the statement must be executed in the accelerator server. The statement cannot be executed by an accelerator server if any condition that is indicated by a reason code is true. . . . DOCUMENTATION: ***Documentation for PM57643: See PM57643 APAR/PTF text for additional information. The following corrections are to be added to the DB2 for z/OS Messages manual for the DSNX880I message. . Under Explanation, the first occurrence of "sql-code" is corrected to be "return-code". . Under Explanation, following the list of message tokens, the following paragraph is added: If the operation is CONNECT and the return-code is 8, the location name in the row that defines the accelerator in the SYSACCEL.SYSACCELERATORS table is incorrectly set to the local DB2 location. . Under System programmer response, the following paragraph is added: If the operation is CONNECT and the return-code is 8, ensure that the LOCATION column of the row that defines the accelerator in SYSACCEL.SYSACCELERATORS is a valid accelerator location name. ACTION: ***Action for PM72274: This PTF adds a new DB2 subsystem parameter, DSN6SPRM.GET_ACCEL_ARCHIVE. This parameter specifies the 1 default setting of the CURRENT GET_ACCEL_ARCHIVE special register. This is the value used when this special register has not been set by means of the SET CURRENT GET_ACCEL_ARCHIVE statement. Valid options are: * NO : Specifies that when a table is archived in IBM DB2 Analytics Accelerator, the table reference does not include the accelerator archived data. ====> This is the default setting * YES: Specifies that when a table is archived in IBM DB2 Analytics Accelerator, the table reference includes the archived data. This PTF also adds a new option, 3, to an existing DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS. This parameter is used to specify additional types of SQL queries to be included in query offloading. It previously had three options: * NONE: Query offloading is restricted to the standard SQL statements ==> This is the default setting. * 1 : The queries that include data encoded by multi-byte character set EBCDIC encoding scheme are not blocked from executing on IBM DB2 Analytics Accelerator. See APAR PM60170 for more information about this option. * 2 : For INSERT statements where a fullselect specifies the data to be inserted, the fullselect part is not blocked from executing on IBM DB2 Analytics Accelerator although the data operated on by the fullselect may not be current in the accelerator. The fullselect will be considered for offload as if it were a stand-alone statement, except that DB2 will not offload the fullselect if the target table of the INSERT has a different encoding scheme than any tables referenced in the fullselect. The new option, 3, specifies that: * 3 : The queries that include DB2 byte-based string functions on data encoded by multi-byte character sets encoding schemes (like Unicode) are not blocked from executing on IBM DB2 Analytics Accelerator although it supports only character-based string functions. If the data on which the string function is specified contains only single-byte characters, executing the function on IBM DB2 Analytics Accelerator will return the same result as executing the function on DB2 irrespective of what encoding scheme is used for the data. However, if the data contains multi-byte characters, the results will not be the same. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is 1 mutually exclusive from all other settings. Options 1, 2, and 3 can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=3 QUERY_ACCEL_OPTIONS=(1,2) QUERY_ACCEL_OPTIONS=(1,3) QUERY_ACCEL_OPTIONS=(2,3) This PTF also adds support for a new column, ARCHIVE, to SYSACCEL.SYSACCELERATEDTABLES, a table in the accelerator database. It also changes the lock size of the containing table space, SYSACCEL, from PAGE to ROW. DSNTIJAS, the sample job for creating these objects, is modified accordingly. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Update your customized copy of job DSNTIJAS (5) Update your accelerator database Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter GET_ACCEL_ARCHIVE=, where is NO or YES, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If your DSNTIJUZ job does not include GET_ACCEL_ARCHIVE, that parameter will be set to the default of NO when you assemble the DSNZPxxx module. * To specify that queries that include DB2 byte-based string functions on data encoded by multi-byte character sets encoding schemes (like Unicode) are not to be blocked from 1 executing on the accelerator, add or update the keyword parameter QUERY_ACCEL_OPTIONS= where is 3 or a list form such as (1,2,3) to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If your DSNTIJUZ job does not include QUERY_ACCEL_OPTIONS, that parameter will be set to the default of NONE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required This PTF adds an entry for GET_ACCEL_ARCHIVE to the CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP target library. You need to add this entry to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: GET_ACCEL_ARCHIVE CHAR M NONE NONE Change to the value specified for GET_ACCEL_ARCHIVE in step (2), above. If you added or modified the setting for QUERY_ACCEL_OPTIONS, you need to add an entry for it to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value you specified for QUERY_ACCEL_OPTIONS in step (2), above. ---------------------------------------------------------------- (4) Update your customized copy of job DSNTIJAS ---------------------------------------------------------------- ==> This action is required if you maintain a customized copy of DSNTIJAS This PTF modifies installation job DSNTIJAS in the SDSNSAMP target library only. After applying this PTF, you need to update job step DSNTIAC of your customized copy of this job as follows: (a) In the create statement for table space SYSACCEL, change LOCKSIZE from PAGE to ROW. (b) In the create statement for table SYSACCEL.SYSACCELERATEDTABLES, add a line for column ARCHIVE after the line for column SUPPORTLEVEL: , "ARCHIVE" CHAR(1) NOT NULL WITH DEFAULT 1 ---------------------------------------------------------------- (5) Update your accelerator database ---------------------------------------------------------------- ==> This action is required if you have created the accelerator database, DSNACCEL. After applying this PTF, process the following SQL using SPUFI or a similar tool to update the SYSACCEL table space and the SYSACCEL.SYSACCELERATEDTABLES table: ALTER TABLESPACE DSNACCEL.SYSACCEL LOCKSIZE ROW; ALTER TABLE SYSACCEL.SYSACCELERATEDTABLES ADD COLUMN "ARCHIVE" CHAR(1) NOT NULL WITH DEFAULT; The ALTER operation will place the DSNACCEL.SYSACCEL table space where the SYSACCEL.SYSACCELERATEDTABLES table resides in AREO* state (e.g. REORG-pending state). Perform REORG utility on DSNACCEL.SYSACCEL table space to remove it from REORG-pending state. Then re-issue the START ACCELERATOR command for DB2 to validate the new added column. If an accelerator is already started, you may receive an expected message DSNX823I indicating an accelerator is already started. If you are falling back from DB2 10 to DB2 9 or running with release coexistence between DB2 10 and DB2 9, note that the new features added by this APAR will not work on DB2 9. New syntax will receive an SQL error on DB2 9. ACTION: PM66216 corrects a problem that ABEND04E RC00E20001 or RC00C90101 may happen when executing a native SQL procedure that contains a graphic string SQL statement used in a statement PREPARE or EXECUTE IMMEDIATE. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure could be affected by this change. ACTION: ***Action for PM60806 TYPE: ACT PM60806 corrects a problem of missing SQLCODE -312 for a CREATE FUNCTION statement satisfied the following conditions, 1. It is a create sql scalar function, 2. SQLCODE/SQLSTATE is not defined as an SQL variable, 3. SQLCODE/SQLSTATE is referenced in a RETURN statement in function SQL routine body. 4. No table is referenced in the RETURN statement or no column in the referenced table with name as SQLCODE or SQLSTATE. 1 After the application of this PTF, ALTER FUNCTION REGENERATE is required for each SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, SQL scalar function could be affected by this change. AO: Fields in the Q8ST will be marked '(S)' (serviceability) that were previously externalized. These fields will no longer be formally supported so applications relying on their content should be changed. The following fields in Q8ST will be marked '(S)': Q8STACTV Current active requests (S) Q8STMAXA Maximum active requests (S) Q8STAVGQ03 Avg query queue length in last 3 hrs(S) Q8STMAXQ Highest query queue length so far (S) Q8STCCPU Average cpu utilization on (S) accelerator coordinator node Q8STSKEW Data skew (S) Q8STWCPU Average cpu utilization on (S) accelerator worker nodes Q8STWNOD Number of active worker nodes (S) Q8STAVGQ24 Avg query queue length in last 24hrs(S) Q8STQUEW Avg wait time in accelerator queue (S) Q8STQUEM Max wait time in accelerator queue (S) Q8STMIPS Accelerator proccessing capacity (S) in MIPS Q8STCORS Total number of proccessors in the (S) accelerator Q8STSREQ Total number of successful query (S) requests since accelerator started Q8STFREQ Total number of failed query (S) requests since accelerator started Q8STFINV Number of failed query requests (S) due to invalid accelerator state Q8STDSKA Disk storage (MB) available (S) Q8STDSKU Disk storage (MB) in-use (S) Q8STDSKB Disk storage (MB) in-use for DB (S) Q8STCPMU Physical memory (MB) average usage (S) on accelerator coordinator node Q8STNMDS Number of data slices (S) Q8STWPMU Physical memory (MB) average usage (S) on accelerator worker nodes Q8STWSMA Shared memory (MB) data available (S) on accelerator worker nodes Q8STWSMU Shared memory (MB) data average (S) usage on accelerator worker nodes Q8STWSMM Maximum shared (MB) memory data in (S) use on accelerator worker nodes COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM72274 DSNB1TAD PM72274 DSNDQPAC PM72274 DSNDQWAC PM72274 DSNDQWPZ PM72274 DSNDQW05 PM72274 1 DSNDQ8AC PM72274 DSNDQ8ST PM72274 DSNDSPRM PM72274 DSNHSM2V PM72274 DSNHSM7 PM72274 DSNLCDG1 PM72274 DSNLCDP1 PM72274 DSNLCITR PM72274 DSNLCMBE PM72274 DSNLCSRR PM72274 DSNLIAAC PM72274 DSNLIRCA PM72274 DSNLISDA PM72274 DSNLTGBK PM72274 DSNLTSET PM72274 DSNLXCMT PM72274 DSNLXCQH PM72274 DSNLXENV PM72274 DSNLXHOC PM72274 DSNLXRBF PM72274 DSNLXRCL PM72274 DSNLXREL PM72274 DSNLXRFT PM72274 DSNLXROP PM72274 DSNLXRSQ PM72274 DSNLXRSS PM72274 DSNLXRUW PM72274 DSNLXSR PM72274 DSNLXSSR PM72274 DSNLZMON PM72274 DSNLZOSR PM72274 DSNLZR00 PM72274 DSNTIDXA PM72274 DSNTIDXB PM72274 DSNTIJAS PM72274 DSNTIJUZ PM72274 DSNTINST PM72274 DSNTLRAC PM72274 DSNTXACT PM72274 DSNTXAZP PM72274 DSNTXSTB PM72274 DSNVDTA PM72274 DSNWAACT PM72274 DSNWAAPI PM72274 DSNWACDF PM72274 DSNWAFRR PM72274 DSNWARDS PM72274 DSNWVAPR PM72274 DSNWVINT PM72274 DSNWVSMT PM72274 DSNWVSR1 PM72274 DSNWVZIT PM72274 DSNWVZPS PM72274 DSNWVZSA PM72274 DSNWZIFA PM72274 DSNXECW PM72274 1 DSNXECWA PM72274 DSNXECWU PM72274 DSNXEDP PM72274 DSNXEDSC PM72274 DSNXEET PM72274 DSNXELX PM72274 DSNXENR PM72274 DSNXEPM PM72274 DSNXERT PM72274 DSNXERT2 PM72274 DSNXESSR PM72274 DSNXGRM1 PM72274 DSNXGRTM PM72274 DSNXOCAS PM72274 DSNXODML PM72274 DSNXODTR PM72274 DSNXOD5 PM72274 DSNXOEXC PM72274 DSNXOEX1 PM72274 DSNXOFF PM72274 DSNXOFN2 PM72274 DSNXOIN PM72274 DSNXOLTD PM72274 DSNXOMPS PM72274 DSNXONZA PM72274 DSNXONZC PM72274 DSNXONZO PM72274 DSNXONZQ PM72274 DSNXONZS PM72274 DSNXOOS1 PM72274 DSNXOPRU PM72274 DSNXOST PM72274 DSNXOTF PM72274 DSNXOV0 PM72274 DSNXOV1 PM72274 DSNXOYDA PM72274 DSNXOYP1 PM72274 DSNXRRSP PM72274 DSNXRSPG PM72274 DSNXTAD PM72274 DSNX8CDA PM72274 DSNX8CMD PM72274 DSNX8CSA PM72274 DSNX8CTG PM72274 DSNX8CXA PM72274 DSNX8EKG PM72274 DSNX8INI PM72274 DSNX8SMF PM72274 DSNX8STA PM72274 DSN6SPRM PM72274 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72274 DSN@XAZP DSNB1TAD DSNDQPAC DSNDQWAC DSNDQWPZ DSNDQW05 DSNDQ8AC DSNDQ8ST DSNDSPRM DSNHSM2V DSNHSM7 DSNLCDG1 DSNLCDP1 DSNLCITR DSNLCMBE DSNLCSRR DSNLIAAC DSNLIRCA DSNLISDA DSNLTGBK DSNLTSET DSNLXCMT DSNLXCQH DSNLXENV 1 DSNLXHOC DSNLXRBF DSNLXRCL DSNLXREL DSNLXRFT DSNLXROP DSNLXRSQ DSNLXRSS DSNLXRUW DSNLXSR DSNLXSSR DSNLZMON DSNLZOSR DSNLZR00 DSNTIDXA DSNTIDXB DSNTIJAS DSNTIJUZ DSNTINST DSNTLRAC DSNTXACT DSNTXAZP DSNTXSTB DSNVDTA DSNWAACT DSNWAAPI DSNWACDF DSNWAFRR DSNWARDS DSNWVAPR DSNWVINT DSNWVSMT DSNWVSR1 DSNWVZIT DSNWVZPS DSNWVZSA DSNWZIFA DSNXECW DSNXECWA DSNXECWU DSNXEDP DSNXEDSC DSNXEET DSNXELX DSNXENR DSNXEPM DSNXERT DSNXERT2 DSNXESSR DSNXGRM1 DSNXGRTM DSNXOCAS DSNXODML DSNXODTR DSNXOD5 DSNXOEXC DSNXOEX1 DSNXOFF DSNXOFN2 DSNXOIN DSNXOLTD DSNXOMPS DSNXONZA DSNXONZC DSNXONZO DSNXONZQ DSNXONZS DSNXOOS1 DSNXOPRU DSNXOST DSNXOTF DSNXOV0 DSNXOV1 DSNXOYDA DSNXOYP1 DSNXRRSP DSNXRSPG DSNXTAD DSNX8CDA DSNX8CMD DSNX8CSA DSNX8CTG DSNX8CXA DSNX8EKG DSNX8INI DSNX8SMF DSNX8STA DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1TAD DSNHSM2V DSNHSM7 DSNLCDG1 DSNLCDP1 DSNLCITR DSNLCMBE DSNLCSRR DSNLIAAC DSNLIRCA DSNLISDA DSNLTGBK DSNLTSET DSNLXCMT DSNLXCQH DSNLXENV DSNLXHOC DSNLXRBF DSNLXRCL DSNLXREL DSNLXRFT DSNLXROP DSNLXRSQ DSNLXRSS DSNLXRUW DSNLXSR DSNLXSSR DSNLZMON DSNLZOSR DSNLZR00 DSNTLRAC DSNTXACT DSNTXAZP DSNTXSTB DSNVDTA DSNWAACT DSNWAAPI 1 DSNWACDF DSNWAFRR DSNWARDS DSNWVAPR DSNWVINT DSNWVSMT DSNWVSR1 DSNWVZIT DSNWVZPS DSNWVZSA DSNWZIFA DSNXECW DSNXECWA DSNXECWU DSNXEDP DSNXEDSC DSNXEET DSNXELX DSNXENR DSNXEPM DSNXERT DSNXERT2 DSNXESSR DSNXGRM1 DSNXGRTM DSNXOCAS DSNXODML DSNXODTR DSNXOD5 DSNXOEXC DSNXOEX1 DSNXOFF DSNXOFN2 DSNXOIN DSNXOLTD DSNXOMPS DSNXONZA DSNXONZC DSNXONZO DSNXONZQ DSNXONZS DSNXOOS1 DSNXOPRU DSNXOST DSNXOTF DSNXOV0 DSNXOV1 DSNXOYDA DSNXOYP1 DSNXRRSP DSNXRSPG DSNXTAD DSNX8CDA DSNX8CMD DSNX8CSA DSNX8CTG 1 DSNX8CXA DSNX8EKG DSNX8INI DSNX8SMF DSNX8STA MACROS DSN@XAZP DSNDQPAC DSNDQWAC DSNDQWPZ DSNDQW05 DSNDQ8AC DSNDQ8ST DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJAS DSNTIJUZ DSNTINST DSN6SPRM LISTEND UK83463 COVER LETTER END UK83480 COVER LETTER START PROBLEM DESCRIPTION(S): PM73056 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically users of the SET CURRENT * * ROUTINE VERSION statement. * **************************************************************** * PROBLEM DESCRIPTION: The following symptoms may occur for * * two independent problems: * * 1-ABEND 04E-00E70005 * * LOC=DSNXGRDS.DSNXVTXM:M421 * * 2-SQLCODE -725 THE SPECIAL REGISTER * * register AT LOCATION location WAS * * SUPPLIED AN INVALID VALUE * **************************************************************** * RECOMMENDATION: * **************************************************************** The summary of the two independent problems are: 1-An application on a remote client system (Site 1), using transaction pooling, calls a stored procedure on a DB2 for z/OS server (Site 2) that executes a SET CURRENT ROUTINE VERSION that assigns a value of one or more blanks. The stored procedure completes and returns to the application which subsequently drives commit or rollback to complete the transaction. During subsequent transaction processing, the client (Site 1) sends the routine version with a value that had been set by the stored procedure in the previous transaction processing. The DB2 for z/OS (Site 2) thread abends with ABEND 04E-00E70005 LOC=DSNXGRDS.DSNXVTXM:M421. 1 2-An application on a DB2 for z/OS requester (Site 1) executes a SET CURRENT ROUTINE VERSION that assigns an empty string value. The DB2 for z/OS Site 1 requester erroneously sends an invalid special register value when the application executes an SQL statement containing a 3-part-name reference to a DB2 for z/OS server (Site 2). The DB2 for z/OS Site 2 server detects the invalid special register value and issues SQLCODE -725. The conclusion for the two independent problems are: 1-DB2 for z/OS, acting as a server, has been changed to correctly process SET CURRENT ROUTINE VERSION with an assigned value of one or more blanks. 2-DB2 for z/OS, acting as a requester, has been changed to correctly process SET CURRENT ROUTINE VERSION with an assigned empty string value. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73056 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXSR PM73056 DSNLZOSR PM73056 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73056 DSNLXSR DSNLZOSR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXSR DSNLZOSR LISTEND UK83480 COVER LETTER END UK83490 COVER LETTER START PROBLEM DESCRIPTION(S): PM71262 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and * * DB2 10 for z/OS utility users of the * * IFCID 25 utility accounting * **************************************************************** * PROBLEM DESCRIPTION: Utility CPU and elapsed time reported * * in IFICID 25 are constantly increasing * * in LISTDEF processing with OPTIONS * * EVENT(ITEMERROR,SKIP). * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** The CPU and elapsed time values reported in fields QW0025UE, QW0025UC, QW0025UZ, QW0025SC, and QW0025SZ keep growing after 1 one list item was processed with a return code RC8 but list processing continues because OPTIONS EVENT(ITEMERROR,SKIP) is specified. Code has been changed to correctly reset the accounting fields between multiple utility invocations in LISTDEF processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71262 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGULM PM71262 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71262 DSNUGULM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGULM LISTEND UK83490 COVER LETTER END UK83497 COVER LETTER START PROBLEM DESCRIPTION(S): PM67543 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: SQL INSERT may fail with SQLCODE904 * * -904 MSGDSNT500I DSNB1GSR RESOURCE * * UNAVAILABLE RC00C200FD TYPE 00000300 * **************************************************************** * RECOMMENDATION: * **************************************************************** When a flag that indicates the status of a page is checked for an INSERT, INSERT may fail with SQLCODE904 if the page status flag is set and it is a residual value. This will trigger a page resource unavailable error incorrectly. DB2 has been fixed to ignore the page status flag if the page buffer is to be initialized for an SQL operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67543 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1GET PM67543 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67543 DSNB1GET 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1GET LISTEND UK83497 COVER LETTER END UK83501 COVER LETTER START PROBLEM DESCRIPTION(S): PM73557 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where DB2 for z/OS is * * configured for outbound trusted connections * * to remote servers. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -30082 CONNECTION FAILED FOR * * SECURITY REASON 15 :0A:0000000C was * * incorrectly received at a DB2 requester * * while attempting to establish an * * outbound trusted connection to a * * remote server. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 for z/OS requester's Communications Database (CDB) is configured for outbound trusted connections to remote servers. During DB2 outbound connection processing, when the value of the SYSIBM.LOCATIONS TRUSTED column contains 'Y' and the row in SYSIBM.IPNAMES USERNAMES column value contains 'S' to the remote location, DB2 searches the SYSIBM.USERNAMES table for the system authorization ID to be used for establishing the outbound trusted connection. If DB2 is unable to find the system authorization ID (e.g., CDB is unavailable), DB2 fails the outbound connection attempt and incorrectly disables the trusted connection definition to the remote location, even though the CDB reflects a trusted connection definition. In this case, after the first (failed) attempt to establish a trusted connection from the DB2 requester to the remote location, subsequent outbound connections to the same remote location was incorrectly receiving SQLCODE -30082. This is because, DB2 was trying to establish a normal (non-trusted) connection (because DB2 internally disabled the trusted connection definition) to the remote location and the userid associated with the connection failed to be authenticated at the server. DB2 for z/OS requester outbound connection processing has been changed to continue to honor the trusted CDB definition to the remote location when a CDB "row not found" condition is encountered. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73557 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLCITR PM73557 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73557 DSNLCITR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLCITR LISTEND UK83501 COVER LETTER END UK83517 COVER LETTER START PROBLEM DESCRIPTION(S): PM74116 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where TCP/IP communications * * are used. * **************************************************************** * PROBLEM DESCRIPTION: Possible decrease in the statistical * * values representing the number of * * bytes sent to a TCP/IP remote * * location (QLSTBYTS and Q8ACBYTS). * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 issues a TCP/IP SENDMSG when either a request or a reply to a request must be sent to a remote partner. One of the parameters of the SENDMSG service is used by TCP/IP to return, to the caller of the SENDMSG service, the number of bytes that were sent. However, when an error occurs during the SENDMSG processing, the value returned will be a negative number. DB2 incorrectly fails to verify if the value returned in the parameter is greater than zero before using the parameter's value to update the statistical value for the number of bytes sent to a remote location, QLSTBYTS and Q8ACBYTS. Thus, if send errors do occur, the statistical value will appear to decrease over time. DB2 has been changed to ensure that the value returned from the TCP/IP SENDMSG service must be greater than zero before it is used to update the QLSTBYTS and Q8ACBYTS statistical values. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74116 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLISDA PM74116 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74116 DSNLISDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLISDA LISTEND UK83517 COVER LETTER END UK83526 COVER LETTER START PROBLEM DESCRIPTION(S): PM72312 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REPAIR utility. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIKESR ERQUAL5008 * * occurred when running REPAIR LEVELID * * on a user object right after a DB2 * * restart * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a REPAIR LEVELID on a user object right after completion of a DB2 restart, when some catalog table spaces were not opened. REPAIR utility triggered physical open of some catalog table spaces when it tried to retrieve information from the catalog. ABEND04E RC00C90101 at DSNIKESR : 5008 happened because the header pages of those table spaces were not processed correctly during the open processing. The abend can also happen for REPAIR LOCATE PAGE 0. REPAIR utility was modified to open catalog table spaces correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72312 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCBLI PM72312 DSNUCBRL PM72312 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72312 DSNUCBLI DSNUCBRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNUCBLI DSNUCBRL LISTEND UK83526 COVER LETTER END UK83553 COVER LETTER START PROBLEM DESCRIPTION(S): PM72976 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of queries which contain an OLAP function * * and a group by that references a LOB column. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * DSNIDM.DSNONLLE:5003 when running a * * query that contains an OLAP function * * and a group by clause that references a * * LOB column. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNONLLE:5003 when running a query that contains an OLAP function and a group by clause that references a LOB column. The following simple example illustrates a failing case where CLOB1 is defined as a LOB column. SELECT LENGTH(CLOB1) ,ROW_NUMBER() OVER(ORDER BY 1) FROM T1 GROUP BY LENGTH(CLOB1); The code in DB2 is modified to process the LOB properly which will prevent the abend. Additional Keywords: SQLOLAP SQLRANK SQLDENSERANK SQLROWNUMBER SQLGROUPBY SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72976 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM72976 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM72976 corrects a problem that can cause an ABEND04E RC00C90101 at DSNIDM.DSNONLLE:5003 when running a query that contains an OLAP function and a group by clause that references a LOB column. To make this fix effective for a static application, it must be 1 rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOWIN PM72976 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72976 DSNXOWIN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOWIN LISTEND UK83553 COVER LETTER END UK83569 COVER LETTER START PROBLEM DESCRIPTION(S): PM74531 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REPORT RECOVERY * * to report system-level backups (SLB). * **************************************************************** * PROBLEM DESCRIPTION: A REPORT RECOVERY abended with * * ABENDS0C7 RC00000000 at DSNUPPBS + * * x'0872' during SLB reporting. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A REPORT RECOVERY utility fell into an endless loop when reporting SLBs on a data sharing system, which led to an ABEND0C7 RC00000000 at DSNUPPBS OFFSET0872. This problem occurred because the local loop variable overflowed. The REPORT RECOVERY for SLB code has been modified to correct the aforementioned error. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74531 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUPPBS PM74531 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74531 DSNUPPBS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUPPBS 1 LISTEND UK83569 COVER LETTER END UK83605 COVER LETTER START PROBLEM DESCRIPTION(S): PM73526 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * DATETIME arithmetic expression and order * * by clause. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C7 RC0 at DSNXRSBC +546C in * * DB2 9 or DSNXRSBC +8086 in DB2 10, or * * unexpected SQLCODE -406 could occur * * when an SQL statement satisfies the * * following conditions: * * 1. It contains a DATETIME arithmetic * * expression in SELECT LIST, * * 2. It contains an order by clause * * which references the DATETIME * * arithmetic expression result in * * the sort key expression. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C7 RC0 at DSNXRSBC +546C in DB2 9 or at DSNXRSBC +8086 in DB2 10, or unexpected SQLCODE -406 could occur when an SQL statement satisfies the following conditions: 1. It contains a DATETIME arithmetic expression in SELECT LIST, 2. It contains an order by clause which references the DATETIME arithmetic expression result in its sort key expression. The following example could recreate the problems: 1. ABEND0C7 at DSNXGRDS.DSNXRSB SELECT DATE('2012-07-23')- CURRENT DATE C1 FROM SYSIBM.SYSDUMMY1 ORDER BY CAST(C1 AS VARCHAR(10)); 2. SQLCODE -406 SELECT DATE('2012-07-23')- CURRENT DATE Q09 FROM SYSIBM.SYSDUMMY1 ORDER BY -Q09; DB2 doesn't handle the DATETIME arithmetic expression and order by clause correctly which causes the above unexpected behavior. DB2 is updated correctly to handle the DATETIME arithmetic expression and order by clause correctly. Additional keywords: SQLDATE SQLTIME SQLORDERBY SQLCODE406 SQLTIMESTAMP OFFSET546C OFFSET8086 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73526 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM73526: 1 See PM73526 APAR/PTF text for additional information about why a REBIND is necessary. PM73526 corrects a problem of an ABEND0C7 RC0 at DSNXRSBC +8086 or unexpected SQLCODE -406 could occur when an SQL statement satisfies the following conditions: 1. It contains a DATETIME arithmetic expression in SELECT LIST, 2. It contains an order by clause which references the DATETIME arithmetic expression result in its sort key expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOOS2 PM73526 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73526 DSNXOOS2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOOS2 LISTEND UK83605 COVER LETTER END UK83623 COVER LETTER START PROBLEM DESCRIPTION(S): PM74316 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: When operate (INSERT, DELETE, UPDATE, * * SELECT, XMLTABLE, XMLEXISTS, or * * XMLQUERY etc) on an XML column, * * ABEND04E may occur at * * DSNXGRDS DSNXOZAT M300 or * * at DSNIDM DSNIKESE 5004, * * or ABEND0C4 may occur at * * DSNXGRDS DSNXOZAT +3D0A with PTF level * * UK77951 or at DSNIDM DSNIKESE +10B0. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following examples may expose the 0C4 or 04E ABEND, INSERT INTO TBO01.TB01 (C1, DOC) VALUES(1, '123'); DELETE FROM TBO01.TB01 WHERE C1 = 1; 1 UPDATE TBO01.TB01 SET DOC = XMLPARSE(DOCUMENT '789') WHERE C1 = 1; SELECT * FROM TBO01.TB01 WHERE C1 = 1; In the above examples, DOC is an XML column in the table TBO01.TB01. When the ABEND may occur depends on the compiler generated code for the DB2 for z/OS module DSNXOZAT. Currently the compiler generated code for the module DSNXOZAT does not introduce this problem. However, the recompilation of this module without the fix in this APAR may introduce the ABENDs in the future. DB2 code is modified so that the above ABENDs will not occur in the field. Additional keywords: XMLALL XMLINSERT XMLDELETE XMLUPDATE SQLXML ERQUAL5004 OFFSET3D0A OFFSET10B0 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74316 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM39078: See PM39078 APAR/PTF text for additional information about why a REBIND is necessary. PM39078 corrects a problem of missing warning message when a query which references an XML column that does not support multiple XML versions and it is bound with the USE CURRENTLY COMMITTED option. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DOCUMENTATION: Existing warning SQLCODE +20002 is changed by this APAR/PTF. The change will be documented in the DB2 Codes, SQL Reference, Command Reference manuals respectively. The texts for SQLCODE +20002 are: +20002 THE clause SPECIFICATION IS IGNORED FOR OBJECT object-name Explanation This message is issued in response to a clause specification that was ignored on a query statement. System action The statement is processed. 1 User response To stop receiving this message, avoid ACCESSCONCURRENTRESOLUTION(UseCurrentlyCommitted) bind option for a plan or package accessing non-versioned XML, or avoid a statement (accessing non-versioned XML) prepared with "Use Currently Committed" attribute. User response needs real action: If an XML column does not support multiple XML versions, you can convert to an XML column that supports multiple XML versions by following these steps: 1. Unload the data from the table that contains the XML columns. 2. Drop the table. 3. Create the table in a universal table space. The new table supports multiple XML versions. 4. Load the data into the table. SQLSTATE 01624 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOZAT PM74316 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74316 DSNXOZAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOZAT LISTEND UK83623 COVER LETTER END UK83629 COVER LETTER START PROBLEM DESCRIPTION(S): PM70090 - **************************************************************** * USERS AFFECTED: All DB2 users of bind option ENABLE(REMOTE) * * with REMOTE(location-name,...,,...) * * or bind option DISABLE(REMOTE) with * * REMOTE(location-name,...,,...). * **************************************************************** * PROBLEM DESCRIPTION: Applications running on DB2 10 for z/OS * * receive SQLCODE -807 when allocating * * packages bound with the ENABLE(REMOTE) * * REMOTE(location-name,...,< luname>,...) * * bind option. * **************************************************************** * RECOMMENDATION: * **************************************************************** Prior to DB2 10, if the requester was DB2 for z/OS, the server identified requesters by their location names. In DB2 10, 1 servers identify all requesters by their IP addresses (or luname). BIND PACKAGE and REBIND PACKAGE options ENABLE(REMOTE) REMOTE(location-name,...,,...) and DISABLE(REMOTE) REMOTE(location-name,...,,...) do not take IP addresses as option values. When a DB2 10 for z/OS server allocates a package bound with a list of remote connections that are specified by IP addresses, allocation fails, and the application receives SQLCODE -807 because the connection validation fails trying to compare IP addresses against location names. The problem has been addressed by the following two fixes: 1. PM69542: DB2 has been changed to disregard the REMOTE(location-name,...,< luname>,...) option on package allocation. DB2 will continue to do validation as if ENABLE(REMOTE) or DISABLE(REMOTE) were specified without a location list. That is, DB2 enables or disables all remote connections. 2. PM70090: Starting in DB2 10 New Function Mode, DB2 has been changed to ignore the REMOTE(location-name,...,< luname>,...) option on BIND and REBIND PACKAGE command. If REMOTE(location-name,...,,...) option is not specified on REBIND, and the package was bound with ENABLE(REMOTE) REMOTE(location-name,...,,...) or DISABLE(REMOTE) REMOTE(location-name,...,,...) option, DB2 will delete the REMOTE(location-name,...,,...) option from the ENABLE(REMOTE) or DISABLE(REMOTE) bind option for the package. A warning return code and a warning message DSNT204I will be issued on the BIND/REBIND request if the REMOTE(location-name,...,,...) option was ignored. PM69542 is a prereq of PM70090. Additional Keywords: MSGDSNT204I SQLCODE807 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70090 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: See PM70090 APAR/PTF text in the PTF cover letter for additional information about why a warning message may be issued on BIND/REBIND PACKAGE command. PM70090 may cause a warning message DSNT204I to be issued on BIND/REBIND PACKAGE request, if the REMOTE(location-name,...,,...) option was ignored. 1 This is the approximate wording of the new text in the Messages manual: DSNT204I bind-type WARNING FOR object-type object-name, option IS option-status, substitute-option WILL BE USED. Explanation A BIND subcommand was issued with an invalid option. bind-type The type of BIND subcommand, such as REBIND. object-type The type of object, such as PLAN. object-name The name of the application plan. option The unsupported BIND option. option-status Possible values are: INVALID The BIND option is not valid in the context where it is used. NOT USED The BIND option syntax is valid, but the option has no effect. substitute-option The BIND option that was used instead of option. This message can be caused by the use of a deprecated option. System action The bind process continues, using the option that is indicated by substitute-option. Operator response No action is required. Severity 4 (warning) This is an example of the new message if the REMOTE(location-name,...,,...) option was ignored. DSNT204I bind-type WARNING FOR PACKAGE object-name,  REMOTE option IS NOT USED, ENABLE(REMOTE) WILL BE USED. Review the PTF cover letter to determine which, if any, packages could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNFMDIR PM70090 DSNFTDIR PM70090 DSNTBCM1 PM70090 DSNTBCM3 PM70090 DSNTBMSG PM70090 DSNTBRB PM70090 DSNTBRB2 PM70090 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70090 DSNFMDIR DSNFTDIR DSNTBCM1 DSNTBCM3 DSNTBMSG DSNTBRB DSNTBRB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFTDIR DSNTBCM1 DSNTBCM3 DSNTBMSG DSNTBRB DSNTBRB2 LISTEND UK83629 COVER LETTER END UK83646 COVER LETTER START PROBLEM DESCRIPTION(S): PM73328 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users whose queries utilize * * index access. * **************************************************************** * PROBLEM DESCRIPTION: Index Scan using a less filtering * * index may be chosen over INLIST access * * using a more filtering index, which * * may result in an inefficient access * * path. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose Index Scan access using a less filtering index over IN-list access using a more filtering index with additional filtering on the IN-list predicate. This may result in an inefficient access path. For the following example query: SELECT * FROM T1,T2 WHERE T1.C1 =1 AND T1.C4=2 AND T2.C1 IN (1,2) AND T1.C2 = T2.C2 AND T1.C3 = T2.C3; Index I1(C1,C2,C3) on T2, and index I2(C2,C3) on T2 are 1 available to be chosen to access table T2 as an inner table, where I1 is more filtering than I2. However, DB2 may choose Index Scan using I2 over INLIST access using I1 even if the IN-LIST predicate "T2.C1 IN (1,2)" provides additional filtering. This can result in an inefficient access path. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE SQLIN Code is changed to correct the index selection for the situation described above. DB2 will have a better chance to choose more efficient access paths for these types of queries. As with any change to DB2 query optimization that can drive a different access path, there is some risk of query performance regression. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73328 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM73328: See PM73328 APAR/PTF text for additional information about why a REBIND is necessary. PM73328 corrects a problem of selecting Index Scan access using a less filtering index over INLIST access using a more filtering index, which may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCSN PM73328 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73328 DSNXOCSN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCSN LISTEND UK83646 COVER LETTER END UK83649 COVER LETTER START PROBLEM DESCRIPTION(S): PM75890 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * 1 * of IBM DB2 Analytics Accelerator (IDAA). * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4-00000011 DSNTLRES+0076 * * occurred when the * * -START ACCEL SCOPE(GROUP) command was * * issued at a DB2 for z/OS system. * **************************************************************** * RECOMMENDATION: * **************************************************************** The -START ACCEL SCOPE(GROUP) DB2 command was issued at a DB2 subsystem to start a specified accelerator server. When the SCOPE(GROUP) option is specified in the -START ACCEL command, DB2 attempts to acquire a lock from IRLM in order to serialize related commands (-START ACCEL, -DISPLAY ACCEL, and -STOP ACCEL) across the data sharing group. In this case, the DB2 -START ACCEL command processor was unable to acquire the lock (due to lock contention) so IRLM suspended the lock request until the requested lock becomes available. However, the DB2 system thread that was servicing the -START ACCEL SCOPE(GROUP) command was canceled while the thread was suspended in IRLM. So during DB2 recovery processing, DB2 incorrectly freed the (RLPL) parameter list (which contains lock request information for IRLM). When IRLM finally honored the (suspended) lock request, DB2 abended with 0C4-00000011 because the IRLM RLPL has been freed and thus the storage is no longer related to the IRLM lock request for the DB2 -START ACCEL SCOPE(GROUP) command. DB2 query accelerator command processor has been changed to not free the IRLM RLPL parameter list during the recovery processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75890 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX8CMD PM75890 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75890 DSNX8CMD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX8CMD LISTEND UK83649 COVER LETTER END UK83672 COVER LETTER START PROBLEM DESCRIPTION(S): PM75922 - **************************************************************** 1 * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where DB2 10 for z/OS, in V8 * * Conversion Mode (CM8), is a requester to a * * DB2 V9.1 (fixpak 3 or later) for * * Linux/Unix/Windows server and a downstream * * non-DB2 database server is being updated * * via DB2/LUW Federated database support. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -571, or SQLCODE -30090 with * * reason 18, is received by a DB2 10 * * for z/OS (CM8) application when * * attempting to update a Federated * * database server via a DB2 V9.1 or * * V9.5 for Linux/Unix/Windows server. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 9 for z/OS initially included support for a change to the Distributed Relational Database Architecture (DRDA) being implemented by DB2 V9.1 for Linux/Unix/Windows which would enable a DRDA requester, using protected conversation protocols to a DB2/LUW V9.1 (or later) server, to update a Federated database server which was being accessed via unprotected connection protocols. The support required that DB2 9 for z/OS be operating in New Function Mode (NFM) and hence this support is also available in DB2 10 for z/OS NFM or CM9 migration environments. Prior to DB2 9 for z/OS availability, support was also added, in a similar but different manner, to DB2 for z/OS V8 in conjunction with support being added to DB2/LUW V9.1 via fixpak 3. A customer utilized this support provided by DB2 for z/OS V8 and DB2/LUW V9.1. The customer then migrated to DB2 10 for z/OS running in a CM8 migration mode. When the customer then attempts to update the Federated database from a DB2 10 (CM8) for z/OS application, the application can receive SQLCODE -571 or SQLCODE -30090 with reason 18. Federated function should be allowed in DB2 10 for z/OS CM8 environments since it was allowed in DB2 for z/OS V8. DB2 10 for z/OS, for the benefit of CM8 migration environments, has been changed to allow a DB2 (10 - CM8) z/OS application to update a Federated database server via a DB2/LUW V9.1 server which is at fixpak 3 or greater. DB2/LUW V9.5 is also supported. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75922 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTCCN PM75922 DSNLTCN2 PM75922 DSNLTXAC PM75922 DSNLZR00 PM75922 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75922 DSNLTCCN DSNLTCN2 DSNLTXAC DSNLZR00 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTCCN DSNLTCN2 DSNLTXAC DSNLZR00 LISTEND UK83672 COVER LETTER END UK83675 COVER LETTER START PROBLEM DESCRIPTION(S): PM71477 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * REORG TABLESPACE PART n utility users * **************************************************************** * PROBLEM DESCRIPTION: Not all logical partitions of a * * non-partitioned secondary index (NPSI) * * are displayed in MSGDSNT397I after * * MSGDSNU590I RESOURCE NOT AVAILABLE, * * RC00C200EA was issued for a failed * * drain during a REORG TABLESPACE PART n * * SHRLEVEL CHANGE. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A REORG TABLESPACE issued DSNU590I - RESOURCE NOT AVAILABLE, REASON=X'00C200EA' when a drain failed on the NPSI. DSNT361I - DISPLAY DATABASE SUMMARY GLOBAL CLAIMERS was issued, with DSNT397I detailed information on the resource not available which was an NPSI on the table space. However, only the logical partitions that were part of the REORG TABLESPACE PART were included in the MSGDSNT361I DISPLAY. REORG TABLESPACE SHRLEVEL CHANGE or REFERENCE drains the entire NPI and should include all logical partitions of the NPSI in the DISPLAY output. Code has been modified to display all logical partitions of an NPSI if it is the object of the DISPLAY CLAIMERS during a a REORG TABLESPACE PART n or PART (m:n) or PART(m,n) utility. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71477 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURDRN PM71477 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71477 DSNURDRN 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURDRN LISTEND UK83675 COVER LETTER END UK83682 COVER LETTER START PROBLEM DESCRIPTION(S): PM75275 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of RUNSTATS utility on a partitioned * * table space with DB2 subsystem parameters * * STATROLL=YES and STATCLUS=ENHANCED. * **************************************************************** * PROBLEM DESCRIPTION: DATAREPEATFACTORF is 0 in catalog * * table SYSIBM.SYSINDEXSTATS and * * SYSIBM.SYSINDEXES after RUNSTATS INDEX * * PART n on a non-empty partitioned * * table space with ZPARM * * STATCLUS=ENHANCED and STATROLL=YES. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A RUNSTATS INDEX PART n was run on a partitioned table space with DB2 system parameters STATCLUS=ENHANCED and STATROLL=YES. The DATAREPEATFACTORF statistic was 0 in both the SYSINDEXSTATS and SYSINDEXES catalog tables and also reported as 0 in MSGDSNU617I and MSGDSNU627I, but the table was not empty. A similar problem can occur during the LOAD, REORG or REBUILD INDEX utility when gathering inline statistics on indexes. Code has been modified to correctly update SYSINDEXSTATS and SYSINDEXES with the value for DATAREPEATFACTOR and to report the value correctly in DSNU617I and DSNU627I. A documention change is needed in the SQL REFERENCE for catalog tables SYSINDEXES, SYSINDEXES_HIST, SYSINDEXSTATS and SYSINDEXSTATS_HIST The description for DATAREPEATFACTORF will read as follows: The anticipated number of data pages that will be touched following an index key order. This statistic is only collected when the STATCLUS subsystem parameter is set to ENHANCED. This number is -1 if statistics have not been collected. This is an updatable column. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75275 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: APAR PM75275 corrects a problem with RUNSTATS updating 1 SYSIBM.SYSINDEXES and SYSIBM.SYSINDEXSTATS catalog tables with a value of zero for column DATAREPEATFACTORF for non-empty partitions. After applying this APAR, RUNSTATS will update DATAREPEATFACTORF with a non-zero value when applicable, and a zero value if the partition or table is empty. A documention change is needed in the SQL REFERENCE for catalog tables SYSINDEXES, SYSINDEXES_HIST, SYSINDEXSTATS and SYSINDEXSTATS_HIST The description for DATAREPEATFACTORF will read as follows: The anticipated number of data pages that will be touched following an index key order. This statistic is only collected when the STATCLUS subsystem parameter is set to ENHANCED. This number is -1 if statistics have not been collected. This is an updatable column. ACTION: APAR PM75275 corrects a problem with RUNSTATS updating SYSIBM.SYSINDEXES and SYSIBM.SYSINDEXSTATS catalog tables with a value of zero for column DATAREPEATFACTORF for non-empty partitions. After applying this APAR, RUNSTATS will update DATAREPEATFACTORF with a non-zero value when applicable, and a zero value if the partition or table is empty. A documention change is needed in the SQL REFERENCE for catalog tables SYSINDEXES, SYSINDEXES_HIST, SYSINDEXSTATS and SYSINDEXSTATS_HIST The description for DATAREPEATFACTORF will read as follows: The anticipated number of data pages that will be touched following an index key order. This statistic is only collected when the STATCLUS subsystem parameter is set to ENHANCED. This number is -1 if statistics have not been collected. This is an updatable column. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSAIX PM75275 DSNUSEOF PM75275 DSNUSUIX PM75275 DSNUSUPI PM75275 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75275 DSNUSAIX DSNUSEOF DSNUSUIX DSNUSUPI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSAIX DSNUSEOF DSNUSUIX DSNUSUPI 1 LISTEND UK83682 COVER LETTER END UK83700 COVER LETTER START PROBLEM DESCRIPTION(S): PM73307 - **************************************************************** * USERS AFFECTED: DB2 users who ALTER TABLESPACE MAXPARTITIONS * * of a segment table space that has a table * * created before DB2 V5. * **************************************************************** * PROBLEM DESCRIPTION: Customer could receive ABEND04E at * * DSNGDART ERQUAL501A. * **************************************************************** * RECOMMENDATION: * **************************************************************** For the table created before DB2 V5, the internal structure does not have an extension. When ALTER TABLESPACE MAXPARTITIONS, DB2 rebuilds a new OBD with the extension, however DB2 incorrectly accesses the old OBD which results in the above abend. DB2 has been changed to access the new OBD, the above abend can be avoided. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73307 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDART PM73307 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73307 DSNGDART THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDART LISTEND UK83700 COVER LETTER END UK83708 COVER LETTER START PROBLEM DESCRIPTION(S): PM71847 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: An incorrect token is shown by * * MSGDSNT501I * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 Incorrect fields may be used as a source for DSNT501I message generation, causing the token to display as 0 or some other invalid value. The reason for picking up these invalid fields was a change to the placement of the fields containing token information, resulting in unpredictable values obtained from irrelevant fields. An example of the problem: DSNT375I @P PLAN=DISTSERV WITH 555 CORRELATION-ID=db2jcc_appli CONNECTION-ID=SERVER LUW-ID=GA321515.CF3C.CA1B8EFD0A20=19840 <--- OK THREAD-INFO=VGHA21:PrdSvr01:VGHA21:db2jcc_application IS DEADLOCKED WITH PLAN=DISTSERV WITH CORRELATION-ID=db2jcc_appli CONNECTION-ID=SERVER LUW-ID=GA320A6A.DE32.120901230632=51329 THREAD-INFO=VGHA21:sts:vgha21:db2jcc_application ON MEMBER DB2P DSNT501I = DSNILMCL RESOURCE UNAVAILABLE 645 CORRELATION-ID=db2jcc_appli CONNECTION-ID=SERVER LUW-ID=GA321515.CF3C.CA1B8EFD0A20=673975 <-- NOT OK REASON 00C90088 TYPE 00000304 NAME DBEMM01 .BITUIN .X'0002B4'.X'09' Code is changed to use the proper token values when issuing DSNT501I. Please note that due to a large number of paths that might issue DSNT501I, this APAR does not fix every possible DSNT501I message. Only reported cases are resolved with this APAR. A global fix is planned for a future release. If, after this APAR is applied, additional DSNT501I messages with an incorrect token are encountered and reported, this code may be replicated to the appropriate path as necessary. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71847 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRUMS PM71847 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71847 DSNIRUMS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNIRUMS LISTEND UK83708 COVER LETTER END UK83727 COVER LETTER START PROBLEM DESCRIPTION(S): PM73850 - **************************************************************** * USERS AFFECTED: DB2 data sharing users in group restart * **************************************************************** * PROBLEM DESCRIPTION: Auto GRECP recovery fails with * * RC00C200EC or RC00C20069 for * * partitions in a partitioned page * * set * **************************************************************** * RECOMMENDATION: * **************************************************************** Two group buffer pool dependent partitions in a partitioned page set are updated by two members individually, for example, member A updates partition one while member B updates partition two. During group restart, there is a time window where member A's Auto GRECP recovery of partition one requests a drain on partition one, and the request is rejected by member B because it already opens the page set for partition two's recovery. As a result, member A's GRECP recovery of partition one gets skipped. The recovery needs to be manually conducted. The drain logic has been modified to not deny requests during restart if the requested partition is not opened or it has no active page set p-lock. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73850 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1LDA PM73850 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73850 DSNB1LDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1LDA LISTEND UK83727 COVER LETTER END 1UK83733 COVER LETTER START PROBLEM DESCRIPTION(S): PM74488 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users that experience soft * * cancel RC00E50013 failures during log undo * * operations. * **************************************************************** * PROBLEM DESCRIPTION: Threads may hang in DB2 after 00E50013 * * failures. * * -DISPLAY THREAD(*) SERVICE(WAIT) will * * show an agent suspended in DSNTABA. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DISPLAY THREAD(*) SERVICE(WAIT) command indicated a hung agent suspended in DB2 abort cleanup processor. A prior soft cancel RC00E50013 failure incorrectly drove the program recovery retry logic during log undo operations. The agent kept running instead of returning back to recovery manager to process the abend. Soft cancels are non-recoverable and must result in abnormal termination of the DB2 thread. Recovery manager was suspended waiting for a response from the program recovery exit in the log undo code. DB2 program recovery exit code in log undo processor has been corrected to avoid the retry operation in cases where a soft cancel failure 00E50013 occurs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74488 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIB PM74488 DSNIBHUN PM74488 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74488 DSNIB DSNIBHUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIB DSNIBHUN LISTEND UK83733 COVER LETTER END UK83736 COVER LETTER START PROBLEM DESCRIPTION(S): PM72014 - **************************************************************** * USERS AFFECTED: All DB2 users of Data Sharing. * **************************************************************** 1 * PROBLEM DESCRIPTION: ABEND04E in DSNGEFLC+85A4 RC00C90092 * * was received. * **************************************************************** * RECOMMENDATION: * **************************************************************** A data sharing system was running a heavy workload when it received ABEND04E in DSNGEFLC+85A4 RC00C90092. As indicated by the return code RC00C90092 there was a shortage of storage for IRLM. Once the storage problem was relieved the system returned to normal operation. A dump is not required to diagnose this condition so the abend is removed and a resource unavailable message will be returned. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72014 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEFLC PM72014 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72014 DSNGEFLC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFLC LISTEND UK83736 COVER LETTER END UK83737 COVER LETTER START PROBLEM DESCRIPTION(S): PM71778 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * RUNSTATS utility users collecting * * HISTOGRAM statistics. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2002F at DSNSVSFM * * + '0794'x during RUNSTATS TABLESPACE * * INDEX HISTOGRAM on a partitioning * * index. * * * * INCORROUT MSGDSNU632I showing * * zero CARDF and/or FREQUENCY values. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When an user executed RUNSTATS TABLESPACE INDEX HISTOGRAM on a partitioned index, the utility terminated with an ABEND04E RC00E2002F at DSNSVSFM OFFSET0794. The problem occurred during the aggregation of HISTOGRAM 1 statistics. The logic incorrectly tried to use more quantiles than the allocated number of quantiles causing the storage abend. When RUNSTATS was executed on the PARTITIONED INDEX, incorrect MSGDSNU632I was reported in the job output and the catalog was updated with incorrect HISTOGRAM statistics The first key column of the multi key column PARTITIONED INDEX had a very low cardinality. The aggregation logic incorrectly generated bad quantile statistics with some quantiles having zero CARDF and/or FREQUENCYF values ADDITIONAL KEYWORDS: SMC OVERLAY Code was modified to check for the actual number of allocated quantiles array elements before storing the aggregated statistics in the array element. The code was modified to skip processing if the CARDF value in the quantile was zero. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71778 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSAH1 PM71778 DSNUSUCD PM71778 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71778 DSNUSAH1 DSNUSUCD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSAH1 DSNUSUCD LISTEND UK83737 COVER LETTER END UK83750 COVER LETTER START PROBLEM DESCRIPTION(S): PM71137 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using BIND * * QUERY command. * * * * * * * **************************************************************** 1 * PROBLEM DESCRIPTION: 1.There is an existing usability issue * * with BIND QUERY, which is related to * * the design of using the same set of * * tables for both EXPLAIN output and * * BIND QUERY input.It causes confusion * * because the EXPLAIN tables contain * * many rows for many different * * statements but only a small subset of * * these rows are intended to be used as * * input to BIND QUERY.Users must clear * * out the rows that aren't intended to * * be passed into BIND QUERY. * * * * 2.The BIND QUERY LOOKUP (YES) can not * * support to identify rows for statement * * level optimization parameters hints * * and update the corresponding QUERYID * * in DSN_USERQUERY_TABLE. * **************************************************************** * RECOMMENDATION: * **************************************************************** Two requirements are addressed by this APAR: 1.There is an existing usability issue with BIND QUERY, which is related to the design of using the same set of tables for both EXPLAIN output and BIND QUERY input.It causes confusion because the EXPLAIN tables contain many rows for many different statements but only a small subset of these rows are intended to be used as input to BIND QUERY.Users must clear out the rows that aren't intended to be passed into BIND QUERY. 2.The BIND QUERY LOOKUP (YES) can not support to identify rows for statement level optimization parameters hints and update the corresponding QUERYID in DSN_USERQUERY_TABLE. Two new functions are provided by this APAR: 1.A new option is added to the BIND QUERY command called EXPLAININPUTSCHEMA. This option is used to specify the schema name for the tables used as input to BIND QUERY. This allow users to use different tables for EXPLAIN output and BIND QUERY intput, where the user only copies the rows to be input to BIND QUERY from the EXPLAIN output tables. Syntax: >>-BIND QUERY-+-------------+-+----------------------------+->< | .NO-. | | | 'LOOKUP(+YES+)' 'EXPLAININPUTSCHEMA('schema')' 2.The BIND QUERY LOOKUP (YES) is enhanced to identify rows for statement level optimization parameters hints and update the corresponding QUERYID in DSN_USERQUERY_TABLE. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71137 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: Changed option for BIND QUERY in Command Reference: Syntax >>-BIND QUERY--+-------------------+--------------------------> | .-NO--. | '-LOOKUP(-+-YES-+-)-' | >--+---------------------------------+--------------------->< | '-EXPLAININPUTSCHEMA(schema-name)-' Option description LOOKUP | Specifies whether to check catalog tables for existing | statement-level access path or optimization parameter hints | that match rows in DSN_USERQUERY_TABLE. LOOKUP(NO) is the | default value. When LOOKUP(YES) is in effect, new rows are | not inserted into the catalog tables and new hints are not | created. When matching rows are found in the catalog tables, | DB2 inserts the value of the SYSQUERY.QUERYID column into | the DSN_USERQUERY_TABLE.QUERYID column of the matching row. (NO) DB2 reads the information from the DSN_USERQUERY_TABLE and certain EXPLAIN tables and inserts the data into certain catalog tables as appropriate to create the specified statement-level optimization hints. NO is the default value. Depending on the values that are specified in DSN_USERQUERY_TABLE, rows might be read from the following additional input tables: schema.PLAN_TABLE | Where schema is the authorization ID of the issuer of the | BIND QUERY command. Depending on the values that are specified in the input tables, data might be inserted in the following catalog tables: SYSIBM.SYSQUERY SYSIBM.SYSQUERYPLAN SYSIBM.SYSQUERYOPTS The catalog table rows create the following types of statement-level optimization hints: Access path hints Optimization parameter hints 1 DB2 issues the following messages to indicate the results of BIND QUERY operation: | A DSNT280I message for each DSN_USERQUERY_TABLE row that is | inserted successfully into the catalog tables. | A DSNT281I message for each DSN_USERQUERY_TABLE row that is | not successfully inserted into the catalog tables. | A single DSNT290I message if some rows were inserted into | catalog tables successfully or a DSNT291I message if no | rows were inserted successfully. (YES) | DB2 reads information from the DSN_USERQUERY_TABLE and looks | for the matching rows in the following catalog tables: SYSIBM.SYSQUERY SYSIBM.SYSQUERYPLAN | SYSIBM.SYSQUERYOPTS The catalog tables are not populated with new values and no new hints are created. When matching rows exist in the catalog tables, DB2 inserts the value of the | SYSQUERY.QUERYID column into the DSN_USERQUERY_TABLE.QUERYID | column of the matching row. | New rows are not inserted into the catalog tables when | LOOKUP(YES) is specified. Instead, DB2 issues messages to | indicate whether existing hints where identified: | A DSNT280I message for each row in the DSN_USERQUERY_TABLE | that has a valid matching row in the catalog tables. | A DSNT281I message for each row in the DSN_USERQUERY_TABLE | that does not have valid matching rows in the catalog | tables. | A single DSNT290I message if some matching rows were found or | a DSNT291I message if no matches were found. |EXPLAININPUTSCHEMA |Specifies the schema of the EXPLAIN tables to be used for |input during BIND QUERY processing. This option enables you |to create separate EXPLAIN tables to be used only as input to |the BIND QUERY command. By creating separate input tables, |you can eliminate the need to remove unneeded rows that might |interfere with BIND QUERY process from the EXPLAIN output |tables. When the EXPLAININPUTSCHEMA option is not specified, |DB2 uses the tables that are qualified by the authorization |ID of the user that issues the BIND QUERY command. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNECP00 PM71137 DSNECP08 PM71137 DSNECP70 PM71137 DSNTBAP PM71137 DSNXOBNQ PM71137 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71137 DSNECP00 DSNECP08 DSNECP70 DSNTBAP DSNXOBNQ 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNECP00 DSNECP08 DSNECP70 DSNTBAP DSNXOBNQ LISTEND UK83750 COVER LETTER END UK83751 COVER LETTER START PROBLEM DESCRIPTION(S): PM71843 - **************************************************************** * USERS AFFECTED: All DB2 users * **************************************************************** * PROBLEM DESCRIPTION: ABEND 0C4 in DSNVXLT0 when unpinning * * buffers * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 pins a buffer for faster access. The pin and unpin buffer logic uses a latch to serialize. However, some unpin logic does not acquire the latch. When the unpin process and the pageset close process happen simultaneously, the unpin process may get an 0C4 abend because the unpin logic needs to access a pageset level control block and it has been released by the pageset close logic. All unpin logic is modified to serialize using a latch. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71843 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1AUR PM71843 DSNB1CPP PM71843 DSNB1LNK PM71843 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71843 DSNB1AUR DSNB1CPP DSNB1LNK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1AUR DSNB1CPP DSNB1LNK LISTEND UK83751 COVER LETTER END 1 UK83754 COVER LETTER START PROBLEM DESCRIPTION(S): PM77201 - **************************************************************** * USERS AFFECTED: All users of DB2 running with the zOS * * TRAPS NAME(IGVINITGETMAIN) facility enabled. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNJRS03 running DSN1LOGP * * with the zOS TRAPS NAME(IGVINITGETMAIN) * * enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** Working storage is not initialized correctly in DSNJRS06 which can result in an ABEND0C4 RC11 when the zOS TRAPS NAME(IGVINITGETMAIN) is enabled. Working storage initialization in DSNJRS06 has been corrected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77201 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJRS06 PM77201 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77201 DSNJRS06 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJRS06 LISTEND UK83754 COVER LETTER END UK83756 COVER LETTER START PROBLEM DESCRIPTION(S): PM71942 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of ALTER TABLE * * from Hash organized Universal Table Space to * * Non-Hash organized UTS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DSNSVSFB+0652 during REORG * * after the table space is altered to * * drop the hash organization. * **************************************************************** * RECOMMENDATION: * **************************************************************** During REORG after the table space is altered to drop the hash 1 organization an ABEND0C4 DSNSVSFB+0652 occurred because DB2 is trying to free the storage, which is pointed by the residual pointer in the system page for hash organization. DB2 code is changed to reset the residual pointer in the system page for hash organization after the system page is retrieved. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71942 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIROBD PM71942 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71942 DSNIROBD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIROBD LISTEND UK83756 COVER LETTER END UK83760 COVER LETTER START PROBLEM DESCRIPTION(S): PM71779 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of GET * * DIAGNOSTICS for connection information items * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC4 can occur at location * * DSNXRGD OFFSET1C76 when DB2 retrieves * * remote connection information items * * using GET DIAGNOSTICS. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC4 can occur at location DSNXRGD OFFSET1C76 when DB2 retrieves connection information items using GET DIAGNOSTICS CONDITION statement for remote connecting cases. This problem occurs if the server name from condition information can't find the matched name after loop though all the connection arrays. DB2 doesn't handle an internal variable assignment correctly which lead this abend problem. The following example illustrates the problem. 1. Create a simple table and insert a row. CREATE TABLE TB ( C1 INTEGER); INSERT INTO TB VALUES (8); 2. Connect to above server. EXEC SQL CONNECT TO STLEC2; 1 3. Define a cursor could return negative sqlcode. EXEC SQL DECLARE c1 CURSOR FOR SELECT C1 FROM TB WHERE C1=a; EXEC SQL OPEN c1; EXEC SQL FETCH FROM c1 INTO :VAR; 3. Get diagnostics includes connection information items. EXEC SQL GET DIAGNOSTICS CONDITION 1 :VSQLCODE = DB2_RETURNED_SQLCODE, :VC = DB2_CONNECTION_STATE ; The above abend can happen during processing above query. DB2 has been modified to set the internal variable assignment and reference correctly. Additional Keywords: SQLGETDIAG ABEND0C4 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71779 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRGD PM71779 DSNXRGD9 PM71779 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71779 DSNXRGD DSNXRGD9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRGD DSNXRGD9 LISTEND UK83760 COVER LETTER END UK83769 COVER LETTER START PROBLEM DESCRIPTION(S): PM75290 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of RUNSTATS TABLESPACE utility on an empty * * table * **************************************************************** * PROBLEM DESCRIPTION: 1. COLCARD and COLCARDF were set to 1 * * in catalog table SYSIBM.SYSCOLUMNS * * after RUNSTATS TABLESPACE for an * * empty table with SAMPLE and COLGROUP * * FREQVAL for a single column * 1 * * * 2. MSGDSNU623I erroneously issued and * * SYSIBM.SYSCOLDIST updated incorrectly * * when RUNSTATS TABLESPACE COLGROUP * * HISTOGRAM was executed against an empty * * table in a segmented table space * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** 1. RUNSTATS TABLESPACE utility with the SAMPLE keyword was executed against an empty table. COLCARD and COLCARDF were set to 1 in catalog table SYSCOLUMNS when COLGROUP FREQVAL was specified with only a single column. The problem happened because a local variable was not set properly. 2. RUNSTATS TABLESPACE utility with the COLGROUP HISTOGRAM keywords was executed against a segmented table space with an empty table. Message DSNU623I was incorrectly issued and the histogram statistic information in SYSCOLDIST was not updated correctly. The problem happened because a local flag for updating histogram statistic was not turned on for the empty table. RUNSTATS TABLESPACE utility code was modified to fix the reported problems. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75290 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSEF2 PM75290 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75290 DSNUSEF2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSEF2 LISTEND UK83769 COVER LETTER END UK83792 COVER LETTER START PROBLEM DESCRIPTION(S): PM66047 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: This PTF ships a new DB2-supplied * * stored procedure, * 1 * SYSPROC.SET_PLAN_HINT. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** SET_PLAN_HINT is a common SQL API stored procedure which validates, deploys, modifies or deletes access path and optimization hint for a single SQL statement. A summary of these enhancements is described in this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21611647 A new DB2OPT option called LOBBP32K is added for specifying the name of the buffer pool for LOB table spaces created by DSNTRIN that use a 32-KB page size. Customers who prefer that DSNTRIN use a different buffer pool for creating LOB table spaces can update the setting. BP32K is used if the LOBBP32K option is not specified. The example below shows how to use LOBBP32K to specify a buffer pool called BP32K for LOB table spaces created by DSNTRIN that use a 32-KB page size: //DB2OPT DD * STOGROUP(SYSDEFLT) INDEXSTOG(SYSDEFLT) BP4K(BP0) BP8K(BP8K0) BP16K(BP16K0) BP32K(BP32K) LOBBP8K(BP8K0) LOBBP16K(BP16K0) LOBBP32K(BP32K) //CFIGIN DD * COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66047 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF adds a new DB2-supplied stored procedure called SYSPROC.SET_PLAN_HINT. SET_PLAN_HINT is a common SQL API stored procedure which validates and deploys hints for a single SQL statement. This PTF also adds a new optional configuration parameter called LOBBP32K to DSNTRIN, the program for installing and configuring DB2-supplied routines and their supporting DB2 objects. LOBBP32K, if specified, provides the name of the buffer pool for LOB table spaces created by DSNTRIN that use a 32-KB page size. BP32K is used if this parameter is not specified. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to V10, the following actions are required after you apply this PTF: 1 (1) Update customized copies of DB2 installation CLIST members (2) Copy updated DB2 installation panels to alternate libraries (3) Update customized copies of installation job DSNTIJRT (4) Update private copies of the DSNTIDxx CLIST input member (5) Run installation job DSNTIJRT to install new objects (6) Run installation job DSNTIJRV to validate new objects These actions are detailed below: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies CLIST members DSNTINST, DSNTINSV, and DSNTINS1 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your private copies of these CLISTs. You may also want to move them to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Copy updated DB2 installation panels to alternate libraries *********************************************************** * This action is required for all V10 customers who maintain * copies of the DB2 installation panels outside of SMP/E: *********************************************************** This PTF modifies the DB2 installation panels DSNTIPRA and DSNTIPRL in the prefix.SDSNSPFP target library. If you keep the DB2 installation panels in a different library then after applying this PTF, you need to copy the updated panels to that library. ---------------------------------------------------------------- (3) Update customized copies of installation job DSNTIJRT *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies installation job DSNTIJRT in the prefix.SDSNSAMP target library. After you apply this PTF, you need to update your private copies of DSNTIJRT as follows: (a) Add the following to the list of configuration control statements under the CFIGIN DD: SYSPROC.SET_PLAN_HINT WLMENV(DSNWLM_GENERAL) GRANTTO(PUBLIC) Notes: (i) Always leave a blank line between each configuration statement (ii) Inspect each of the new configuration control statements and if required: - Change the WLMENV parameter setting to the name 1 of the WLM environment you use to run this routine at your site - Change the GRANTTO parameter setting to the authorization IDs that need access to this routine - Optionally add the PKGOWNER option (b) Optionally add the LOBBP32K parameter to the DB2OPT DD. The example below shows how to use LOBBP32K to specify a buffer pool for LOB table spaces created by DSNTRIN that use a 32-KB page size: //DB2OPT DD * STOGROUP(TSSTOGRP) INDEXSTOG(IXSTOGRP) BP4K(BP0) BP8K(BP8K0) BP16K(BP16K0) BP32K(BP32K) LOBBP8K(BP8K0) LOBBP16K(BP16K0) LOBBP32K(BP32K) //CFIGIN DD * ---------------------------------------------------------------- (4) Update private copies of the DSNTIDxx CLIST input member *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF adds entries to store values entered into new fields on installation panel DSNTIPRL: - RTL40ACL: GRANT EXECUTE setting for SYSPROC.SET_PLAN_HINT - RTL40WLM: WLM ENV NAME setting for SYSPROC.SET_PLAN_HINT - RTL40PKO: PACKAGE OWNER setting for SYSPROC.SET_PLAN_HINT You need to make the same changes to all private copies of your CLIST output (DSNTIDxx) member. In each such copy, add the following lines: RTL40ACL CHAR M NONE NONE PUBLIC RTL40PKO CHAR M NONE NONE NULL RTL40WLM CHAR M NONE NONE DSNWLM_GENERAL The values shown in the 6th column are the DB2-supplied default settings. If you specified different settings in action (3) above, change the settings in column 6 accordingly. ---------------------------------------------------------------- (5) Run installation job DSNTIJRT to install new objects *********************************************************** * This action is required for all V10 customers *********************************************************** After you have completed the above actions, run your updated copy of job DSNTIJRT to perform the following tasks: (a) install, bind, and grant access to the new routine SYSPROC.SET_PLAN_HINT (b) create table DSN8BQRY.DSN_USERQUERY_TABLE and its 1 containing table spaces, auxiliary table, and indexes (c) create table DSN8BQRY.PLAN_TABLE and its containing table space and index If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. ---------------------------------------------------------------- (6) Run installation job DSNTIJRV to validate new objects *********************************************************** * This action is required for all V10 customers *********************************************************** After you have completed the above actions, run your customized copy of job DSNTIJRV to validate installation and configuration of SYSPROC.SET_PLAN_HINT. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMGC PM66047 DSN@DMGU PM66047 DSN@DMHS PM66047 DSN@DMHU PM66047 DSN@RIN PM66047 DSN@RVFY PM66047 DSN@XAZP PM66047 DSNADMGC PM66047 DSNADMGM PM66047 DSNADMGS PM66047 DSNADMGU PM66047 DSNADMHS PM66047 DSNADMHU PM66047 DSNADMMG PM66047 DSNADMMW PM66047 DSNADMXS PM66047 DSNTESR PM66047 DSNTIDXA PM66047 DSNTIDXB PM66047 DSNTIJRT PM66047 DSNTINST PM66047 DSNTINSV PM66047 DSNTINS1 PM66047 DSNTIPRA PM66047 DSNTIPRL PM66047 DSNTRIN PM66047 DSNTRVFY PM66047 DSNTXAZP PM66047 DSNXRCUF PM66047 DSNXRRTN PM66047 HDBAA10J PM66047 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66047 DSN@DMGC DSN@DMGU DSN@DMHS DSN@DMHU DSN@RIN DSN@RVFY DSN@XAZP DSNADMGC DSNADMGM DSNADMGS DSNADMGU DSNADMHS DSNADMHU DSNADMMG DSNADMMW DSNADMXS DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRL DSNTRIN DSNTRVFY DSNTXAZP DSNXRCUF DSNXRRTN HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMGC DSNADMGM DSNADMGS DSNADMGU DSNADMHS DSNADMHU DSNADMMG DSNADMMW DSNADMXS DSNTRIN DSNTRVFY DSNTXAZP DSNXRCUF DSNXRRTN MACROS DSN@DMGC DSN@DMGU DSN@DMHS DSN@DMHU DSN@RIN DSN@RVFY DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRL LISTEND UK83792 COVER LETTER END UK83795 COVER LETTER START PROBLEM DESCRIPTION(S): PM76277 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 10 for z/OS only. * **************************************************************** 1 * PROBLEM DESCRIPTION: Two problems are reported: * * 1. Message DSN9027I issued when * * Display DDF Alias command * * specifies an alias name that * * contains an underscore ('_'). * * 2. DSN9014I is not issued when the * * Modify DDF Alias command specifies * * two or more alias names. * **************************************************************** * RECOMMENDATION: * **************************************************************** Two problems are reported: 1. Display DDF Alias command does not accept underscore: The Display DDF Alias command is unable to display alias information if the alias name contains an underscore, even though the alias name (with an underscore) can be created (added) via the Modify DDF Alias command. An underscore character, '_', is documented as being a valid character for an alias name. However, the Display DDF Alias command incorrectly fails with message DSN9027I if the specified alias name contains an underscore character. 2. Modify DDF Alias command accepts multiple alias names: Only single alias names are documented as being allowed in the Modify DDF Alias and Display DDF Alias commands. However, the Modify DDF Alias command incorrectly accepts two or more alias names and then provides an incomplete and erroneous result. Two problems are corrected: 1. The Display DDF Alias command is changed to allow an alias name that contains an underscore character. This is now consistent with the behavior of the Modify DDF Alias command. 2. The Modify DDF Alias command will now issue a DSN9014I message if two or more alias names are specified. This is now consistent with the behavior of the Display DDF Alias command. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76277 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN9SCNA PM76277 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76277 DSN9SCNA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN9SCNA LISTEND UK83795 COVER LETTER END 1 UK83796 COVER LETTER START PROBLEM DESCRIPTION(S): PM71167 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of the DROP TRIGGER statement with dynamic * * statement cache enabled. * **************************************************************** * PROBLEM DESCRIPTION: An SQLCODE -904 (or SQLCODE904) occurs * * for a DROP TRIGGER statement when * * dynamic statement caching is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQLCODE -904 (or SQLCODE904) occurs for a DROP TRIGGER statement when dynamic statement caching is enabled. A user can receive an SQLCODE904 rc00E70081, RESOURCE TYPE A00, when executing a DROP TRIGGER statement if there is a prepared dynamic SQL statement currently stored in the prepared statement cache which is accessing the SYSIBM.SYSTABLES catalog table. The locking code in DB2 has been modified so that a DROP TRIGGER can proceed while a statement accessing the same table is stored in the dynamic statement cache. Other statements coming in during the processing of the DROP TRIGGER statement however, may time out with an RC00E70010. Additional Keywords: SQLDROP SQLDYNSTMTCACHE SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71167 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIDTR PM71167 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71167 DSNXIDTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIDTR LISTEND UK83796 COVER LETTER END UK83809 COVER LETTER START PROBLEM DESCRIPTION(S): PM73165 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * 1 * utility users of CATMAINT UPDATE VCAT * * SWITCH * **************************************************************** * PROBLEM DESCRIPTION: CATMAINT UPDATE VCAT SWITCH fails * * with ABEND04E RC00E20013 in * * DSNSGMN+1104 * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** CATMAINT UPDATE VCAT SWITCH failed with an ABEND04E RC00E20013 in DSNSGMN+1104 when altering an index pageset OBD. This was due to a storage shortage. The shortage was a result of altering a large number of objects prior to the failure. Storage was allocated when altering objects and it was released only after the work was committed. Due to a logic error in the code, the commits were not done as frequently as expected and therefore excessive storage was accumulated. This error could also occur when using CATMAINT UPDATE SCHEMA SWITCH or CATMAINT UPDATE OWNER FROM (...) TO ROLE. CATMAINT code has been changed to prevent excessive storage accumulation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73165 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUESCM PM73165 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73165 DSNUESCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUESCM LISTEND UK83809 COVER LETTER END UK83843 COVER LETTER START PROBLEM DESCRIPTION(S): PM75162 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG * * TABLESPACE with LOB object. * **************************************************************** * PROBLEM DESCRIPTION: A REORG TABLESPACE after an ALTER * * MAXPARTITIONS to convert a * * non-partitioned table space with LOB * * objects to a partition-by-growth table * * space abended with ABENDS0C4 RC00000004 * * at DSNURWBF + x'3846' during the RELOAD * 1 * phase. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A non-partitioned table space with a LOB column was converted to a PBG by an ALTER MAXPARTITIONS. A subsequent REORG TABLESPACE included the associated LOB table space to materialize the schema change. This REORG abended with ABEND0C4 RC00000004 when trying to locate the LOB information during the RELOAD phase. This problem occurred because this non-partitioned table space contained dropped tables, however the REORG still used it to locate the LOB objects. Additional Keywords: RC00000038 OFFSET2E78 OFFSET3846 x'2E78' The REORG code has been modified to locate the correct table to build the LOB information. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75162 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURLBI PM75162 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75162 DSNURLBI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURLBI LISTEND UK83843 COVER LETTER END UK83864 COVER LETTER START PROBLEM DESCRIPTION(S): PM76386 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of LOBs (Large Objects). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 rc4 can occur at location * * DSNO2CMT +0310 (OFFSET0310) for DB2 10 * * or at DSNO2CMT +0268 (OFFSET0268) for * * DB2 9 during commit processing when a * * unit of work is exploiting LOBs (Large * * Objects). * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 rc4 at location DSNO2CMT +0310 (OFFSET0310) for DB2 10 or at location DSNO2CMT +0268 (OFFSET0268) for DB2 9 can occur during commit processing when a unit of work is exploiting 1 LOBs (Large Objects). The abend occurs because a non-existing internal control block was referenced incorrectly during the execution of internal tracing logic when writing extensive LOB tracing records. Please note that since these tracing records do not provide valuable information for debugging purposes, they are being disabled by this apar. The code in DB2 is modified to prevent the unexpected abend. Additional Keywords: SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76386 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: *** Action for PM27855 (DB2 10 for z/OS): DB2 has been changed to recognize that the presence of a held locator requires DB2 to maintain the remote application's association to the DB2 thread that owns the locator value. Effectively, DB2 is changed to apply the same behavior to held LOB locators that currently exists for WITH HOLD cursors. Users should be aware that there MAY be operational issues as a result of this change because more remote application environments will have to stay active, after commit processing, IF the application, perhaps erroneously, has established held locators. Basically, the operational impact of this change occurs as a result of requiring an increased number of DB2 threads (DBATs) and remote client system network connections (to the DB2 server) in order to service the same amount of remote application work. Possible symptoms may include: . Reduced number of IFCID 3 accounting records are written. . Increased storage utilization symptoms due to additional threads (DBATs) that may now be required. . Performance degradation, perhaps due to the queuing that may occur as a result of reaching or approaching the MAXDBAT resource limit. . High rate of unexpected "Idle Thread Time-out" conditions (message DSNL030I with reason code 00D3003B) that may result in unexpected remote application failures. . Remote client "connection concentrator" environments may also be adversely affected as a result of their inability to pool connections on a transaction (commit) boundary. Before applying this APAR/PTF change, users are advised to evaluate their exposure by researching their enterprise use of held LOB locators. It is difficult to evaluate the use of held LOB locators in Dynamic SQL, ODBC, or JDBC environments, but the use of static SQL HOLD LOCATOR statements can be determined by a query of the DB2 for z/OS SYSIBM.SYSPACKSTMT catalog table. SELECT * 1 FROM SYSIBM.SYSPACKSTMT WHERE STATEMENT LIKE '%HOLD%LOCATOR%' ORDER BY COLLID,NAME; Evaluation of IFCID 0003 accounting trace information, with respect to non zero DSNDQXST.QXHOLDL values, in conjunction with IFCID 0239 package accounting information, can also be used to help identify packages that utilize held LOB locators. Erroneous or unintentional use of held LOB locators, or the packages that contain them, should be eliminated. Proper or intentional use of held LOB locators will now behave correctly but may also result in operational issues that users should be prepared to detect and accommodate. Users can also consider using the FREE LOCATOR SQL statement when the held locator is no longer needed. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNO2CMT PM76386 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76386 DSNO2CMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNO2CMT LISTEND UK83864 COVER LETTER END UK83879 COVER LETTER START PROBLEM DESCRIPTION(S): PM76352 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of PAIR-WISE JOIN. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc000E70005 can occur at * * location DSNXRTSC:M300 when DB2 sort is * * called to sort RIDs into a workfile * * because DB2 subsystem parameter * * MAXTEMPS_RID=NONE had been set. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc000E70005 can occur at location DSNXRTSC M300 when DB2 sort is called to sort RIDs into a workfile on behalf of PAIR-WISE JOIN because DB2 subsystem parameter MAXTEMPS_RID=NONE (-1) had been set. The MAXTEMPS_RID subsystem parameter determines the maximum amount of temporary storage in the work file database that a single RID list can use. This abend will only occur when PAIR-WISE JOIN is being performed. However, for pair-wise join, when sorting the RIDs into a workfile, the MAXTEMPS_RID parameter setting should be ignored. DB2 has been modified to let the sorting of RIDs be done into a 1 work file for pair-wise join regardless of the MAXTEMPS_RID specified value. Additional Keywords: SQLPAIRWISEJOIN SQLRID SQLSORT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76352 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSFIN PM76352 DSNXSFRT PM76352 DSNXSFUN PM76352 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76352 DSNXSFIN DSNXSFRT DSNXSFUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSFIN DSNXSFRT DSNXSFUN LISTEND UK83879 COVER LETTER END UK83887 COVER LETTER START PROBLEM DESCRIPTION(S): PM71492 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of the * * DSNUTILU or DSNUTILS stored procedure * **************************************************************** * PROBLEM DESCRIPTION: ABENDS30A RC1C in DSNUTILB following an * * authorization error when invoking a * * utility using either the DSNUTILU or * * DSNUTILS stored procedure * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User tried to run a utility stored procedure. However the userid used to submit the job was not authorized so it failed to IDENTIFY to DB2. During termination processing, an attempt was made to free the SYSPRINT data set but because of the authorization failure, the DCB was not set up correctly resulting in the ABEND30A RC1C. DSNUTILB has been changed to correctly free the SYSPRINT DCB when called from either the DSNUTILU or DSNUTILS stored procedure. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71492 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUTILB PM71492 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71492 DSNUTILB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUTILB LISTEND UK83887 COVER LETTER END UK83909 COVER LETTER START PROBLEM DESCRIPTION(S): PM72374 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with selective * * queries. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may choose an inefficient index * * when multiple indexes are estimated to * * be highly selective and the matching * * column coverage of one index is a * * superset of another. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose a poorly performing index for the leading table of a query block if both of the following conditions are true. * Multiple indexes exist that are estimated to provide highly selective matching coverage. * The matching column coverage of one index is a superset of the matching column coverage of the other index. Additional Keywords: SQLPERFORMANCE SQLACCESSPATH DB2 has been modified to select the index with the superset matching column coverage in the scenario described above. Note that when the superset index is not highly selective, additional IO may be required to use the superset matching. Thus, this fix only changes the access path when the index matching is estimated to be highly selective. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72374 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: 1 ***Action for PM72374: A rebind is necessary for static applications to rebuild access paths based on the changes in this PTF. PM72374 corrects a problem in which DB2 chooses an index matching on only a few (or one) column(s) when an alternate index exists with matching that is estimated to be very selective and matching columns that are a superset of the chosen index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM70949: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM70949 corrects a problem in which a tablespace scan access path may be incorrectly chosen when using an internal serviceability feature to influence access path selection with ACCESS_TYPE='INLIST'. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM69949: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM69949 corrects a problem in which DB2 may choose a highly selective or index-only DPSI without page range when a more efficient non-DPSI index exists. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM67292: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM67292 corrects a problem that DB2 may improperly favor range list index scan over multiple index access. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change. DB2BIND: ***Action for PM66098: See PM66098 APAR/PTF text for additional information about why a REBIND is necessary. PM66098 corrects a problem where DB2 does not select an equal unique index even though it may be the best choice, resulting in a query performance problem. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM62712: See PM62712 APAR/PTF text for additional information about why a REBIND is necessary. PM62712 corrects a problem of choosing an inefficient range-list access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM61011: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM61011 corrects a problem in which DB2 incorrectly chooses to sort instead of using reverse index scan to avoid the sort when OPTIMIZE FOR 1 ROW is specified. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM59585: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM59585 corrects a problem in which an inefficient access path is selected when multiple highly selective indexes exist that can provide the same matching coverage. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCCX PM72374 DSNXOCSC PM72374 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72374 DSNXOCCX DSNXOCSC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCCX DSNXOCSC LISTEND UK83909 COVER LETTER END UK83912 COVER LETTER START PROBLEM DESCRIPTION(S): PM73064 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the CHECK INDEX utility on * * partitioned table spaces. * **************************************************************** * PROBLEM DESCRIPTION: CHECK INDEX(ALL) TABLESPACE db.ts * * was not prohibited when there was a * * non-partitioned secondary index (NPSI) * * in REBUILD PENDING STAR (RBDP*). * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A CHECK INDEX(ALL) TABLESPACE database.tablespace was run against a partitioned table space with non-partitioned secondary indexes in RBDP*. The CHECK INDEX ran to completion but should have issued DSNU214I prohibiting the utility with a logical NPSI partition(s) in RBDP*. CHECK INDEX has been modified to issue MSGDSNU214I - REBUILD PENDING ON INDEX ixname PROHIBITS PROCESSING and terminate with RC8. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73064 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKINT PM73064 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73064 DSNUKINT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNUKINT LISTEND UK83912 COVER LETTER END UK83928 COVER LETTER START PROBLEM DESCRIPTION(S): PM65564 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of LOAD utility with PRESORTED option. * **************************************************************** * PROBLEM DESCRIPTION: A LOAD utility with PRESORTED option * * hung after issuing several DSNU345I * * messages for duplicate keys during the * * SORTBLD phase. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LOAD PRESORTED utility ran on a table with a unique index. It hung after issuing several MSGDSNU345I - UNIQUE INDEX KEY DUPLICATES KEY FROM INPUT RECORD record_num LOADED AT RID rid...during the SORTBLD phase. This problem occurred because the SORTBLD phase was waiting for a subtask to write the duplicate keys to the error data set, however this subtask had not been started yet. The LOAD PRESORTED code has been changed to start the required subtask earlier. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65564 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM65564 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved. ACTION: ++HOLD ACTION FOR PM64354: The LOAD utility has been changed to build a unique compression dictionary when loading at the table space level on a COMPRESS YES classic or partition by range table space with 254 or less partitions for SHRLEVEL NONE LOADs. This change will result in LOAD requiring more above the bar 1 virtual storage to support a unique compression dictionary for each partition. For range partitioned table spaces with 254 partitions this would result in about an extra 254MB of virtual storage above the bar. While this is a very small percentage of above the bar storage, it can become a problem on lpars with an inadequate amount of real storage to fulfill the above the bar virtual storage request. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURILD PM65564 DSNURPDS PM65564 DSNURPIB PM65564 DSNURPLD PM65564 DSNURPLL PM65564 DSNURPPD PM65564 DSNURPTB PM65564 DSNURWI PM65564 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65564 DSNURILD DSNURPDS DSNURPIB DSNURPLD DSNURPLL DSNURPPD DSNURPTB DSNURWI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURILD DSNURPDS DSNURPIB DSNURPLD DSNURPLL DSNURPPD DSNURPTB DSNURWI LISTEND UK83928 COVER LETTER END UK83933 COVER LETTER START PROBLEM DESCRIPTION(S): PM71033 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of LOAD utility * **************************************************************** * PROBLEM DESCRIPTION: 1. LOAD INTO TABLE PART with DISCARDS n * * but without DISCARDDN finished load * * processing without checking the DISCARD * * limit * * * * 2. A vast amount of MSGDSNU344I, * * MSGDSNU345I, MSGDSNU1107I or * * MSGDSNU1108I messages were issued * * during a LOAD utility, which flooded * * the message spool and brought down DB2 * * * 1 * 3. MSGDSNU047I followed by ABENDSC03 * * during a LOAD INTO TABLE PART utility * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** 1. A LOAD INTO TABLE PART x with DISCARDS n but without part level DISCARDDN caused LOAD to continue processing without checking the specified DISCARD limit. When DISCARDS n is specified at the PART level, DISCARDDN is required. LOAD is changed to issue MSGDSNU047I - A REQUIRED DD CARD OR TEMPLATE IS MISSING. NAME=DISCARDDN and end with RC8 when user specifies DISCARDS n without specifying part level DISCARDDN. 2. A vast amount of DSNU344I, DSNU345I, DSNU1107I or DSNU1108I messages were issued during a LOAD utility which flooded the message spool and brought down DB2. Load utility needs to suppress the messages at a certain threshold to avoid flooding the spool and bringing down DB2. 3. When user did a partition level LOAD, if the DISCARDDN ddname keyword is specified but the discard data set is not defined, the LOAD failed with message DSNU047I followed by ABENDSC03. The problem happened because DB2 tried to terminate the LOAD without closing the opened SYSREC dataset. 1. LOAD partition parallelism code has been modified to issue message DSNU047I and terminate with RC8 when specifying DISCARDS n but without specifying part level DISCARDDN ddname. 2. LOAD code has been modified to stop issuing the DSNU344I, DSNU345I, DSNU1107I and DSNU1108I messages once a threshold of 2000 has been reached. MSGDSNU1140I will be issued for the message that has reached its limit. The utility will continue to process. 3. LOAD partition parallelism code has been modified to close the opened SYSREC dataset before terminating the LOAD utility. This APAR also introduces the following changes to the Messages publication: Description change for message DSNU1140I: DSNU1140I csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY Explanation The number of instances of the indicated message issued during a utility operation has exceeded the maximum number permitted. csect-name 1 The name of the control section that issued the message. max-messages The maximum number of messages that are issued before this message is issued. This value is controlled by the utility that issues message DSNU1140I. message-number The message number that has reached the limit and is now suppressed. Examples: LOAD example The LOAD utility issues message DSNU1140I after 2000 instances of any of the following messages: DSNU313I, DSNU314I, |DSNU1103I, DSNU1104I, DSNU344I, DSNU345I, DSNU1107I or |DSNU1108I. Any rows that would have triggered the suppressed message are still discarded. UNLOAD example The UNLOAD utility issues message DSNU1140I after 2000 instances of message DSNU1239I when both of the following conditions are true: 1. The UNLOAD statement includes either the FROMCOPY or FROMCOPYDDN option. 2. The value of the MAXERR option in the UNLOAD statement is either a number greater than 2000 or the number 0. Any rows that would have triggered the suppressed message are still not unloaded. System action Processing continues. No additional instances of message-number messages are issued. Only the issuance of the message is suppressed. Any action that is associated with the suppressed message number still occurs. User response No action is required. Severity 0 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71033 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM71033 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. 1 The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved. There is no default DISCARD DD for a LOAD with partition parallelism. A DISCARDDN ddname must be specified for a partition parallel LOAD when using the DISCARDS n keyword at the partition level. If you specify DISCARDS n keyword but omit the DISCARDDN ddname option for the partition, LOAD will issue message DSNU047I - A REQUIRED DD CARD OR TEMPLATE IS MISSING. NAME=DISCARDDN and terminate with RC8. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURBXA PM71033 DSNURBXD PM71033 DSNURELD PM71033 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71033 DSNURBXA DSNURBXD DSNURELD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURBXA DSNURBXD DSNURELD LISTEND UK83933 COVER LETTER END UK83945 COVER LETTER START PROBLEM DESCRIPTION(S): PM73555 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS who use DSNADMSB * * and/or the stored procedure * * ADMIN_INFO_SQL. * **************************************************************** * PROBLEM DESCRIPTION: THIS FIX ADDRESSES SEVERAL ISSUES * * RELATED TO OUTPUT FROM ADMIN_INFO_SQL * * FOR DDL AND STATISTICS. THE SYMPTOMS * * USUALLY ARE INCORRECT OUTPUT WHEN * * BUILDING THE DDL AND STATS OUTPUT * * FILES OR CAN RELATE TO LONG * * PROCESSING TIME. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF ADMIN_INFO_SQL EVENTS: ADMIN_INFO_SQL was sometimes not producing the 1 correct output when creating DDL and STATS output files to be used for DB2 problem analysis. Here are a list of reported issues: Fixed/Added index includes. Added V8 when getting stogroup so that an error does not occur on V10 CM8 Fixed VCATNAME reference in stogroup Added BCREATOR when getting view/MQT info so that set schema is set correctly. Fixed double entry in last Partition MAXVALUE. New Error message when input parameter Tablename = PLAN_TABLE and Plan Info = NONE Tablename != PLAN_TABLE and Plan Info != NONE Write to log info and version checking moved to top of procs for efficiency. Updated DSNTEJ6I SAM sample JCL for DSNADMSB. ADMIN_INFO_SQL had several new features added: Enhanced PLAN_TABLE collection. Enhanced DSN_DETCOST_TABLE. Additional support in PLAN_TABLE service data. Additional table collection. Changed format of STATS output to readable from wrapped or compressed. Added STATS input parameter = 'C' to wrap STATS the old way to save space for large outputs. Collect Alias's related to views. Identify View/MQT processing in DDL output. Easier to read. PROBLEM CONCLUSION: The reported ADMIN_INFO_SQL problems are now corrected. ADDITIONAL KEYWORDS: SQLSP SQLSTOREDPROC ADMININFOSQL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73555 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ++HOLD COMMENT FOR RELEASE A10, TYPE ACT: This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers 1 This PTF updates programs modules DSNADMSB and DSNADMSS plus the DBRM for DSNADMSS (the DBRM for DSNADMSB is not updated). After applying this PTF, proceed as follows to bind a package from the updated DSNADMSS DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2-supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Update your customized copy of job DSNTEJ6I --------------------------------------------------------------- ==> All DB2 V10 customers who maintain a customized copy of DSNTEJ6I need to take this action after applying the PTF. The change affects the default input for the following parameters: Change COLLECT_COLUMN_STATS to N Change EDIT_DDL to Y These default changes are made to minimize the amount of data that is collected. Column statistics can be abundant, but are not always required for analysis. Edit mode will help create DDL in a format that can be more easily applied to a service environment. ACTION: ++HOLD COMMENT FOR RELEASE A10, TYPE ACT: 1 This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. ACTION: ++HOLD COMMENT FOR RELEASE A10, TYPE ACT: This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. It also modifies DSNADMSB, a program that can be used to call SYSPROC.ADMIN_INFO_SQL. In order to take advantage of new collection features incorporated in this version, please ensure that DSN_VIEWREF_TABLE is created before doing static binds or dynamic explains. Also, make sure APAR PM63211 is applied. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRMs DSNADMSS and DSNADMSB --------------------------------------------------------------- ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2 supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. 1 --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. ACTION: This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. It also modifies DSNADMSB, a program that can be used to call SYSPROC.ADMIN_INFO_SQL. This PTF also adds a DCB clause to the SYSPRINT DD in job step DSNADMSB of job DSNTEJ6I. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2 supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF. Issue the following VARY MVS command from the console to refresh the WLM application environment: 1 VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Rebind the package for DSNADMSB --------------------------------------------------------------- ==> All DB2 V10 customers who use the DSNADMSB program to call the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF. Submit a job that contains the following BIND statements: BIND PACKAGE(DSNADMSB) MEM(DSNADMSB) - ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') where is the high-level qualifier for the target DB2 subsystem. --------------------------------------------------------------- (4) Update SYSPRINT DD in job step DSNADMSB of job DSNTEJ6I --------------------------------------------------------------- ==> All DB2 V10 customers who use the job DSNTEJ6I to call DSNADMSB need to take this action after applying the PTF. If you have already installed or migrated to DB2 V10 and you maintain a customized copy of the DSNTEJ6I job, edit your copy, locate the SYSPRINT DD statement, and add DCB=(RECFM=VB,LRECL=4096). For example: //SYSPRINT DD SYSOUT=*,DCB=(RECFM=VB,LRECL=4096) ACTION: This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. It also modifies DSNADMSB, a program that can be used to call SYSPROC.ADMIN_INFO_SQL. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2 supplied stored procedures. 1 If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Rebind the package for DSNADMSB --------------------------------------------------------------- ==> All DB2 V10 customers who use the DSNADMSB program to call the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Submit a job that contains the following BIND statements: BIND PACKAGE(DSNADMSB) MEM(DSNADMSB) - ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') where is the high-level qualifier for the target DB2 subsystem. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMSB PM73555 DSN@DMSS PM73555 DSNADMSB PM73555 DSNADMSS PM73555 DSNTEJ6I PM73555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73555 DSN@DMSB DSN@DMSS DSNADMSB DSNADMSS DSNTEJ6I THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNADMSB DSNADMSS MACROS DSN@DMSB DSN@DMSS DSNTEJ6I LISTEND UK83945 COVER LETTER END UK83965 COVER LETTER START PROBLEM DESCRIPTION(S): PM75917 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users * * accessing the IBM Data Analytics Accelerator * * (IDAA). * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: An application using the IBM Data * * Server Driver for JDBC and SQLJ * * accesses DB2 10 for z/OS in New * * Function Mode (NFM) to open a query or * * to perform an INSERT with subselect * * where the query or subselect, * * respectively, is offloaded to IDAA. * * The request fails with SQLCODE -514 or * * SQLCODE -518 (SQLCODE514 or * * SQLCODE518), respectively, even though * * the dynamic request is prepared. * **************************************************************** * RECOMMENDATION: * **************************************************************** The query or subselect being offloaded to IDAA includes timestamp input data and the application options cause the PREPARE request and OPEN or EXECUTE of the prepared statement to be sent to DB2 10 for z/OS in a chain. DB2 incorrectly rejects the query offload with SQLCODE -514 or SQLCODE -518. DB2 10 for z/OS server processing has been corrected to process timestamp input data from the IBM Data Server Driver for JDBC and SQLJ for queries being offloaded to IDAA. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75917 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXROP PM75917 DSNXERT PM75917 DSNXERT2 PM75917 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75917 DSNLXROP DSNXERT DSNXERT2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXROP DSNXERT DSNXERT2 LISTEND UK83965 COVER LETTER END UK83968 COVER LETTER START PROBLEM DESCRIPTION(S): PM68181 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REPAIR SET utility * **************************************************************** * PROBLEM DESCRIPTION: REPAIR SET tablespace NORCVRPEND * * followed by REPAIR SET index NORBDPEND * * in the same statement only resets the * * table space and ends with RC0. * **************************************************************** * RECOMMENDATION: * **************************************************************** A REPAIR SET NORCVRPEND on a table space with SET NORBDPEND on an index in the same statement ends with return code 0, however, only the table space is repaired while the index remains in RBDP. For example: REPAIR SET TABLESPACE ADMF001.TS1 NORCVRPEND SET INDEX ADMF001.IX1 NORBDPEND SET INDEX ADMF001.IX2 NORBDPEND SET INDEX ADMF001.IX3 NORBDPEND The problem occurred because the REPAIR SET utility used information from the first object while processing the subsequent objects. REPAIR code has been changed to use the correct information when processing multiple objects in the same utility statement. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68181 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCBRS PM68181 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68181 DSNUCBRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNUCBRS LISTEND UK83968 COVER LETTER END UK83981 COVER LETTER START PROBLEM DESCRIPTION(S): PM76421 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS users and DB2 10 for * * z/OS users of queries that can use a sparse * * index. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E2000C can occur at * * location DSNXSMRE.DSNSVSVB+0AC2 from * * storage manager when trying to satisfy * * a storage request for a sparse index. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E2000C can occur at location DSNSVSVB +0AC2 (OFFSET0AC2 or OFFSETAC2) when a (DB2 Sort) storage request for a sparse index can not be satisfied because sufficient storage is not available or because of some other storage constraint. Instead of DB2 failing the query with an abend, Sort should continue, disable sparse index processing, and write the results to a physical workfile. Also, please note, that to avoid these kinds of storage problems for a sparse index, the user might be able to lower their MXDTCACH (max data caching) setting. This may help sort to build the sparse index. DB2 has been modified to check the 'condition' returned (from storage manager) when acquiring storage for a sparse index. This check will determine next processing instead of abending if not enough storage is available. Additional Keywords: SQLSPARSEINDEX SQLPERFORMANCE SQLSORT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76421 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSMRE PM76421 DSNXSMRG PM76421 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76421 DSNXSMRE DSNXSMRG 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSMRE DSNXSMRG LISTEND UK83981 COVER LETTER END UK83996 COVER LETTER START PROBLEM DESCRIPTION(S): PM74543 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with queries * * involving partitioned tables, and EQUAL with * * host variables or parameter markers, and a * * Data Partitioned Secondary Index (DPSI). * **************************************************************** * PROBLEM DESCRIPTION: DB2 may choose a poorly performing * * access path for a partitioned table * * when: * * * * 1. The table is partitioned with only 1 * * limit key, or only the leading column * * of the partitioning key has limits * * specified; or there is more than one * * column but the column limit for other * * columns are always the maximum * * allowable value for that column. * * * * 2. DB2 uses an EQUAL predicate with * * host variables or parameter markers to * * limit the partitions for page range * * access. * * * * 3. The Plan Table shows PAGE_RANGE='Y' * * * * 4. There is at least one DPSI on the * * table. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose a poorly performing access path for a partitioned table when the table is partitioned with only 1 limit key and DB2 uses an EQUAL predicate with a host variable or parameter marker to limit the partitions for page range access. A sample query looks like this: SELECT ... FROM ... WHERE C1 = ? Partitioning index on (C1) or (C1,C2) with limit keys on C1 only. 1 When the problem occurs, it might result in a poorly performing access path being selected by the DB2 optimizer. With this logic corrected, DB2 will choose a more efficient access path when deciding on an access path involving page range access. ADDITIONAL KEYWORDS: SQLACCESSPATH PERFM SQLHOSTVAR PARAMETERMARKER SQLPMARKER SQLPMK PAGERANGE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74543 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74543: See PM74543 APAR/PTF text for additional information about why a REBIND is necessary. PM74543 corrects a problem of choosing a poorly performing access path for a partitioned table when queries involve partitioned tables, and EQUAL with host variables or parameter markers, and a DPSI (Data Partitioned Secondary Index). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM74152: A rebind is necessary for static applications to rebuild internal structures used at runtime based on the changes in this APAR. PM74152 corrects a problem in which DB2 may incorrectly return no rows for a query using page range access where a range predicate exists on a partitioning column defined as CHAR(1). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM52548: See PM52548 APAR/PTF text for additional information about why a REBIND is necessary. PM52548 fixes an abend 0C4 RC00000038 DSNISPBM + 1A64 that can occur during query execution for queries containing IS NULL or LIKE predicates. To make this fix effective for a static application, it must be 1 rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM38082: See PM38082 APAR/PTF text for additional information about why a REBIND is necessary. PM38082 corrects a query performance problem involving significant loss of page range screening for queries with multi-column partitioning keys and predicates with host variables or parameter markers on those columns. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: See PM25059 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM25059 corrects a problem where the page range reduction is done incorrectly. It may cause DB2 to choose a plan with an extra GROUP BY / ORDER BY sort where it is not needed. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPG2 PM74543 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74543 DSNXOPG2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPG2 LISTEND UK83996 COVER LETTER END UK90046 COVER LETTER START PROBLEM DESCRIPTION(S): PM75918 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG * * TABLESPACE utility. * **************************************************************** * PROBLEM DESCRIPTION: REORG TABLESPACE AUX YES failed with * * ABEND04E RC00E40353 in DSNURWBF * * OFFSET43F4 * 1 **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a REORG TABLESPACE SHRLEVEL CHANGE with the AUX YES option, either by default or by explicit specification, on a table space containing one or more tables with LOB column. With concurrent DML running in the background, the utility failed with ABEND04E RC00E40353 in DSNURWBF + x'43F4' in the RELOAD phase, when it encountered a duplicate key condition on one of the LOB table spaces being reorganized. The reported problem was caused by a transient duplicate key violation that REORG should tolerate as part of its ISO(UR) unload processing. Code has been modified for REORG to tolerate the transient duplicate key condition in the aforementioned scenario. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75918 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURWBF PM75918 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75918 DSNURWBF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWBF LISTEND UK90046 COVER LETTER END UK90047 COVER LETTER START PROBLEM DESCRIPTION(S): PM76278 - **************************************************************** * USERS AFFECTED: All DB2 10 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 or ABEND0C1 at an unknown * * PSW address resulting from a bad branch * * or * * ABEND04E RC00C90101 at DSNGEPLC : 500D * * * * when running DML workloads (SELECT, * * INSERT, UPDATE, DELETE, MERGE, REFRESH * * TABLE, SET :hostvar, and VALUES INTO). * **************************************************************** * RECOMMENDATION: * **************************************************************** A code bug in statement bind code may prevent DB2 from correctly storing the entirety of the bound DML access path 1 structures on DASD or in the Dynamic Statement Cache. In particular, the bound access path structures that reside below-the-bar are incorrectly omitted. . This code bug only affects the following DML sql statements o SELECT select statements or cursor selects o INSERT o UPDATE o DELETE o MERGE o REFRESH TABLE (of materialized query tables) o SET :hostvar with scalar-fullselect expressions o VALUES INTO with scalar-fullselect expressions The ABEND0C4 or ABEND0C1 is due to a bad branch when the DB2 engine attempts to execute instructions at an address which it expects to reside in the below-the-bar structures. The branch will typically occur in a module whose name begins with 'DSNI', such as DSNIOST2 , DSNIRNXT , and this will be visible during dump analysis. . The ABEND04E RC00C90101 at DSNGEPLC : 500D may occur when DB2 detects that the directory's length information for this below-the-bar piece is zero. . The package directory structure for the affected statement will indicate a zero length for the below the bar part of the bound statement, which may be evident in a dump. This apar corrects the statement bind code to save away the below-the-bar bound access path structures of certain DML statements. . If the error occurs on a cached dynamic sql statement, you can correct the error by applying this apar. . If the errors on static a sql statement, you can correct the error by both applying this apar and REBINDING the affected package. . . ADDITIONAL KEYWORDS: ERQUAL500D RC00000010 RC00000011 RC000000001 SQLDYNSTMTCACHE iproc pproc sproc uproc xproc COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76278 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM76278: See PM76278 APAR/PTF text for additional information about why a REBIND is necessary. PM76278 corrects a problem of ABEND04E RC00C90101 at DSNGEPLC : 500D or 1 ABEND0C1 or ABEND0C4 at an unknown PSW due to a bad branch when running static DML workloads. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXESX PM76278 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76278 DSNXESX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXESX LISTEND UK90047 COVER LETTER END UK90071 COVER LETTER START PROBLEM DESCRIPTION(S): PM77377 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of queries which are candidates for multiple * * index access selection (basically, queries * * that need to sort RIDs). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at DSNIDM * * DSNISRID 5001 or ERQUAL5001 can occur * * when executing an SQL statement that * * requires RIDLIST sort processing. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 at location DSNIDM DSNISRID 5001 or ERQUAL5001 can occur when executing an SQL statement that requires RIDLIST sort processing. The nature of this problem is that it is infrequent and intermittent and can only occur when multiple RIDLISTs within a RIDMAP are to be sorted. This can happen when sort merges the RIDLISTs together and then discovers the last RIDLIST after merge ends up containing 0 RIDs (this can happen when duplicates are to be removed and there is a duplicate at the end of merge processing). So, in this case, the last RIDLIST is to be removed, freed, and dechained from the previous RIDLIST. It is this dechaining from the previous RIDLIST that was missing when the last RIDLIST was freed. The previous RIDLIST pointer to the freed RIDLIST needs to be zeroed since the storage could (now) be used by some other process. If not, the storage can then be processed as a RIDLIST when it is not leading to the described 1 (or other) failure. Some other possible error symptoms for v10 are: ABEND04E rc00C90101 at DSNIDM DSNISRID 5012 or DSNISRID ERQUAL5012 ABEND0C4 rc4 at DSNXGRDS DSNXSMRL +19A2 or DSNXSMRL OFFSET19A2 Another possible error symptom for v9 is: ABEND04E rc00C90101 at DSNIDM DSNISRID 5001 or DSNISRID ERQUAL5001 The code in DB2 has been modified to correct the chaining of the previous RIDLIST when the last RIDLIST is freed. Additional Keywords: SQLRID SQLSORT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77377 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSFML PM77377 DSNXSMRL PM77377 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77377 DSNXSFML DSNXSMRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSFML DSNXSMRL LISTEND UK90071 COVER LETTER END UK90073 COVER LETTER START PROBLEM DESCRIPTION(S): PM67255 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of IFCID 53/58 in * * tandem with IFCID 316/401, or users of * * IFCID 401 * **************************************************************** * PROBLEM DESCRIPTION: 1. Some execution statistics are not * * recorded correctly for SQL statement- * * -level performance metrics pointed to * * by QWT02R30 in IFCID53/58 when either * * IFCID 316 or IFCID 401 are ON. * 1 * * * 2. Two execution statistics in * * IFCID 401 were recorded incorrectly. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. IFCID53/58 reports execution statistics for SQL statement level traces. Certain execution statistics reported for the following IFCID53/58 fields in the QWT02R30 data block are being calculated twice when IFCID 316 and/or IFCID 401 are ON: . QW0053SR NUMBER OF SYNCHRONOUS BUFFER READS. QW0053WT NUMBER OF BUFFER WRITES. . QW0058SR NUMBER OF SYNCHRONOUS BUFFER READS. QW0058WT NUMBER OF BUFFER WRITES. . The following fields were being recorded with different time values between collection of data in the IFCID 53/58 block and the IFCID 316/401 blocks. . QW0053ET ACCUMULATED IN-DB2 ELAPSED TIME. QW0053CP TIME THAT WAS CONSUMED ON AN IBM SPECIALTY ENGINE. . QW0058ET ACCUMULATED IN-DB2 ELAPSED TIME. QW0058CP TIME THAT WAS CONSUMED ON AN IBM SPECIALTY ENGINE. . 2. IFCID 401 records information for static SQL statements that are currently being tracked in the EDM pool. The values in the following two fields in the IFCID401 trace record were reversed: . QW0401PG NUMBER OF PARALLEL GROUPS CREATED. QW0401WT NUMBER OF BUFFER WRITES. . QW0401PG invalidly contains the value intended for field QW0401WT, and QW0401WT invalidly contains the value intended for field QW0401PG. 1. For elapsed time and cpu accumulation, DB2 has been modified to use the same time fields to keep the IFCID 316/401 and IFCID 53/58 closer in value. . For buffer read/writes, DB2 code has been modified to not calculate twice. . 2. DB2 code has been modified to correctly record the statistics values in the IFCID401 fields QW0401PG and QW0401WT. . RELATED KEYWORDS: PERFM SQLSTATS IFCID053 IFCID58 IFCID316 IFCID401 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67255 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECG PM67255 DSNXECST PM67255 DSNXEET PM67255 DSNXERDS PM67255 DSNXERT PM67255 DSNXOD12 PM67255 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67255 DSNXECG DSNXECST DSNXEET DSNXERDS DSNXERT DSNXOD12 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECG DSNXECST DSNXEET DSNXERDS DSNXERT DSNXOD12 LISTEND UK90073 COVER LETTER END UK90076 COVER LETTER START PROBLEM DESCRIPTION(S): PM74671 - **************************************************************** * USERS AFFECTED: All DB2 users using non-partitioned table * * spaces or indexes whose data sets may be * * migrated. * **************************************************************** * PROBLEM DESCRIPTION: SQL fails with SQLCODE904 RC00D70024 * * * * MSGDSNP012I DSNPCNPO ERROR IN ICF * * CATALOG LOCATE FUNCTION FOR * * data_set_name CTLGRC=AAAAAA08 * * CTLGRSN=AAAAAA08 * **************************************************************** * RECOMMENDATION: * **************************************************************** When a data set belonging to a non-partitioned table space or index is getting recalled, a rare timing window in the recall process may cause SQL operations to fail with SQLCODE904 RC007D0024. DB2 has been fixed to wait for a non-partitioned data set recall process to finish when a rare timing window is hit by a data set open request. MSGDSNP012I will continue to be issued as part of the open process, but SQL operations for this data set will no longer encounter SQLCODE904 RC0070024. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74671 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1OPP PM74671 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74671 DSNB1OPP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1OPP LISTEND UK90076 COVER LETTER END UK90090 COVER LETTER START PROBLEM DESCRIPTION(S): PM75364 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users whoese queries utilize * * the IS NOT DISTINCT FROM predicate. * **************************************************************** * PROBLEM DESCRIPTION: The filter factor of an IS NOT DISTINCT * * FROM predicate can be inaccurately * * estimated, which may result in an * * inefficient access path selection. * * * * The IS NOT DISTINCT FROM predicate can * * be either directly coded in the query * * or internally transformed by DB2. * * * * For example, the following two cases * * are both internally taken as an IS NOT * * DISTINCT FROM predicate: * * * * (1) directly coded IS NOT DISTINCT * * FROM predicate: * * * * T1.C1 IS NOT DISTINCT FROM T2.C1; * * * * (2) DB2 internally transformed IS NOT * * DISTINCT FROM predicate: * * * * T1.C1 = T2.C1 OR * * (T1.C1 IS NULL AND T2.C1 IS NULL); * * * * This compound OR predicate is * * internally transformed to an IS NOT * * DISTINCT FROM predicate by DB2. * * * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** The filter factor estimate of an IS NOT DISTINCT FROM predicate can be inaccurate, which may result in an inefficient access path. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE SQLDISTINCT Code is changed to correct the filter factor calculation for the situation described above. DB2 will have a better chance to choose more efficient access paths for these types of queries. As with any change to DB2 query optimization that can drive a different access path, there is some risk of query performance regression. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75364 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75364: See PM75364 APAR/PTF text for additional information about why a REBIND is necessary. PM75364 corrects a problem of inaccurate filter factor estimate of an IS NOT DISTINCT FROM predicate that may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODFE PM75364 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75364 DSNXODFE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODFE LISTEND UK90090 COVER LETTER END UK90099 COVER LETTER START PROBLEM DESCRIPTION(S): PM75775 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users with queries using * * OPTIMIZE FOR 1 ROW. * **************************************************************** 1 * PROBLEM DESCRIPTION: DB2 may choose an inefficient access * * path when a user issues a query with a * * predicate or predicates that satisfy * * the conditions below: * * * * 1.The query specifies OPTIMIZE FOR 1 * * ROW. * * 2.No sort is going to be performed. * * 3.All the predicate columns are * * contained in the index. * * 4.There is no join in the query. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose an inefficient access path for a query with OPTIMIZE FOR 1 ROW, no sort and no join is going to be performed, and there is an index or indexes which contain all the columns in the predicates. For example, SELECT C4 FROM T1 WHERE C1 = ? AND C2 > ? AND C3 = ? OPTIMIZE FOR 1 ROW Index IX1(C1,C2,C3) The index IX1 contains all the columns in the predicates, and no sort and no join are performed in the query with OPTIMIZE FOR 1 ROW. The problems mentioned above are fixed so that DB2 will choose an efficient access path in that situation. ADDITIONAL KEYWORDS: SQLACCESSPATH SQLPERFORMANCE SQLBETWEEN SQLSUBQUERY SQLOF1R COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75775 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75775: See PM75775 APAR/PTF text for additional information about why a REBIND is necessary. PM75775 corrects a problem of poor query performance for OPTIMIZE FOR 1 ROW when no sort and no join will be performed, and there is an index or indexes which contain all the columns in the predicates. 1 To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCCX PM75775 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75775 DSNXOCCX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCCX LISTEND UK90099 COVER LETTER END UK90150 COVER LETTER START PROBLEM DESCRIPTION(S): PM67974 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC04 may occur in module * * DSNWVCOL when processing a DB2 trace * * record for module DSN3CHGZ. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the user issues a -SET SYSPARM LOAD(dsnzparm) or -SET SYSPARM RELOAD to trigger a ZPARM update an ABEND0C4 may occur in module DSNWVCOL if the DB2 global trace for class 3 or rmid 7 is on. Module DSN3CHGZ has been updated to avoid the ABEND0C4 in DSNWVCOL. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67974 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3CHGZ PM67974 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67974 DSN3CHGZ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3CHGZ LISTEND UK90150 COVER LETTER END 1 UK90155 COVER LETTER START PROBLEM DESCRIPTION(S): PM73796 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REOPT * * and EXTENDEDINDICATOR bind options. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 DSNXRIHB:+0DB0 may * * occur when binding an application with * * REOPT and EXTENDEDINDICATOR options. * * The application contains the INSERT * * or UPDATE statement that * * satisfies one of the following * * conditions: * * 1. The INSERT statement contains host * * variables, or parameter markers on the * * VALUES clauses. * * 2. The UPDATE statement contains host * * variables, or parameter markers on the * * SET clauses. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000004 DSNXRIHB:+0DB0 may occur when binding an application with REOPT and EXTENDEDINDICATOR options. The application contains the INSERT or UPDATE statement that satisfies one of the following conditions: 1. The INSERT statement contains host variables, or parameter markers on the VALUES clauses. 2. The UPDATE statement contains host variables, or parameter makers on the SET clauses. For Example, UPDATE T1 SET C1 = :hv1 WHERE C2 = :hv2; The abend may occur when binding the application contains this statement with REOPT and EXTENDEDINDICATOR bind options. DB2 was fixed to handle REOPT and EXTENDEDINDICATOR bind options correctly. Additional Keywords: SQLREOPT SQLREOPTVARS SQLHOSTVAR SQLREOPTONCE SQLREOPTALWAYS REOPTAUTO COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73796 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM69619 APAR/PTF text for additional information about why a REBIND is necessary. PM69619 corrects a problem that incorrect output may happen for a static SQL statement that satisfies all of the 1 following conditions: 1 It references a table which is in PBR(partitioned by range) tablespace; 2 It contains a predicate on VARCHAR column which is a partition key of PBR table; 3 The option REOPT(ALWAYS) or REOPT(VARS) is specified when binding the package. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXORHV PM73796 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73796 DSNXORHV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXORHV LISTEND UK90155 COVER LETTER END UK90165 COVER LETTER START PROBLEM DESCRIPTION(S): PM76303 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of RUNSTATS SHRLEVEL CHANGE utility * **************************************************************** * PROBLEM DESCRIPTION: A restart current of a RUNSTATS * * SHRLEVEL CHANGE utility incorrectly set * * catalog objects (DSNDB06) in UTRW * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A RUNSTATS SHRLEVEL CHANGE utility was restarted after serialization on a user table space, incorrectly setting certain catalog objects in DSNDB06 to a UTRW state. RUNSTATS includes non-target objects during its serialization process but flags these objects as no utility in progress state needed. A logic error in restart processing was causing RUNSTATS to set these objects in UTRW. Affected catalog table spaces in v10: DSNDB06.SYSDBASE DSNDB06.SYSTSCOL DSNDB06.SYSTSIXS DSNDB06.SYSTSIPT DSNDB06.SYSTSTPT 1 DSNDB06.SYSTSTAB DSNDB06.SYSTSTSP DSNDB06.SYSSTATS DSNDB06.SYSTARG DSNDB06.SYSHIST Affected catalog table spaces in v9: DSNDB06.SYSHIST The RUNSTATS SHRLEVEL CHANGE restart code has been modified to not set UTRW for catalog objects. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76303 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSDRA PM76303 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76303 DSNUSDRA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSDRA LISTEND UK90165 COVER LETTER END UK90173 COVER LETTER START PROBLEM DESCRIPTION(S): PM72911 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of * * an SQL table function and * * common table expression. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may occur * * for an SQL statement that * * references to an SQL * * table function that satisfies * * the following conditions: * * 1.A column is specified as an argument * * to an SQL table function when the body * * of that table function contains a * * materialized common table expression. * * * * 2.An argument to an SQL table function * * is included in the invocation of * * another SQL table function, which * * contains a materialized * * common table expression * * * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** Incorrect output may occur for an SQL statement that references to an SQL table function that satisfies the following conditions: 1.A column is specified as an argument to an SQL table function when the body of that table function contains a materialized common table expression. PM72911 restricts the usage of queries that satisfy the above conditions because of the potential incorrect output. SQLCODE -270 will be issued for queries that satisfy the above conditions. For Example, CREATE FUNCTION TUDF_CTE (P1 INT) RETURNS TABLE (C1 INT) LANGUAGE SQL SPECIFIC MYTUDF2 NOT DETERMINISTIC READS SQL DATA RETURN WITH CTE_T (C1) AS ( SELECT P1 FROM SYSIBM.SYSDUMMY1; UNION ALL SELECT C1+1 FROM CTE_T WHERE C1 < 3 ) SELECT C1 FROM CTE_T; SELECT * FROM T1, TABLE (TUDF_CTE(T1.C1))TX; The SELECT statement will receive SQLCODE -270 because a column is specified as an argument of SQL table function TUDF_CTE and the body of the TUDF_CTE contains a materialized common table expression. 2.An argument to an SQL table function is included in the invocation of another SQL table function, which contains a materialized common table expression. For Example, CREATE FUNCTION TUDF_CTE1 (P1 INT) RETURNS TABLE (C1 INT) LANGUAGE SQL SPECIFIC MYTUDF2 NOT DETERMINISTIC READS SQL DATA RETURN WITH CTE_T (C1) AS ( SELECT P1 FROM SYSIBM.SYSDUMMY1; UNION ALL SELECT C1+1 FROM CTE_T WHERE C1 < 3 ) SELECT C1 FROM CTE_T; 1 CREATE FUNCTION TUDF_CTE2(P1 INT) RETURNS TABLE (C1 INT) LANGUAGE SQL SPECIFIC MYTUDF2 NOT DETERMINISTIC READS SQL DATA RETURN SELECT * TABLE(TUDF_CTE1(P1))TX; SELECT * FROM TABLE(TUDF_CTE2(1))TX; The SELECT statements above will receive SQLCODE -270 because an argument of an SQL table function is included in the invocation of another SQL table function, which contains a materialized common table expression. DB2 was fixed to issue SQLCODE -270 when a column or an argument to an SQL table function is included in the invocation of an SQL table function which contains a materialized common table expression. Additional Keywords: SQLCTE SQLINLINE SQLTABLEUDF SQLCODE270 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72911 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74733: See PM74733 APAR/PTF text for additional information about why a REBIND is necessary. Apar PM74733 corrects an ABEND0C4 RC00000004 failure that can occur at location DSNXGRDS.DSNXRSEQ+02D4 when an SQL statement satisfies the following conditions. 1. It contains a table expression. 2. The table expression references a SEQUENCE. 3. The table expression is merged. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM73526: See PM73526 APAR/PTF text for additional information about why a REBIND is necessary. PM73526 corrects a problem of an ABEND0C7 RC0 at DSNXRSBC +8086 or unexpected SQLCODE -406 could occur when an SQL statement satisfies the following conditions: 1. It contains a DATETIME arithmetic expression in SELECT LIST, 2. It contains an order by clause which references the DATETIME 1 arithmetic expression result in its sort key expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM72911: See PM72911 APAR/PTF text for additional information about why a REBIND is necessary. PM72911 corrects a problem of incorrect output may occur for an SQL statement that references to an SQL table function that satisfies the following conditions: 1.A column is specified as an argument to an SQL table function when the body of that table function contains a materialized common table expression. 2.An argument to an SQL table function is included in the invocation of another SQL table function which contains a materialized common table expression. PM72911 restricts the usage of queries that satisfy the above conditions because of the potential incorrect output. SQLCODE -270 will be issued for queries that satisfy the above conditions. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM66961: See PM66961 APAR/PTF text for additional information about why a REBIND is necessary. PM66961 corrects a problem that incorrect output may happen for an SQL statement that contains a correlated subquery with predicates like 'T2.C1 = T1.C1 OR (T2.C1 IS NULL AND T1.C1 IS NULL)', where T2.C1 or T1.C1 is a correlated column and the predicate can be reduced to NOT DISTINCT FROM predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM65380: See PM65380 APAR/PTF text for additional information about why a REBIND is necessary. PM65380 corrects a problem of ABEND04E RC00E70005 in DSNXGRDS.DSNXOUWF:P009 could occur for an SQL statement 1 that contains multiple outer joins, LOB and scrollable cursor. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM65365: See PM65365 APAR/PTF text for additional information about why a REBIND is necessary. PM65365 corrects a problem that ABEND0C4 RC00000004 at the location DSNXGRDS.DSNXRBND OFFSET07B6 or OFFSET075A may happen for an SQL statement that contains a predicate like 'T1.C1 IS DISTINCT FROM T2.C1' under OR, and T1.C1 has different nullability from T2.C1. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM64633: See PM64633 APAR/PTF text for additional information about why a REBIND is necessary. PM64633 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS.DSNXOSL:P105 could happen for a native SQL procedure when it satisfies all of the following conditions. 1. It contains a 'SELECT aggregate_function INTO sql_variable' statement. 2. The input column to the aggregate_function has different CCSID from the sql_variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOB1 PM72911 DSNXOB2 PM72911 DSNXOOS1 PM72911 DSNXOOS2 PM72911 DSNXOSL PM72911 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72911 DSNXOB1 DSNXOB2 DSNXOOS1 DSNXOOS2 DSNXOSL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXOB1 DSNXOB2 DSNXOOS1 DSNXOOS2 DSNXOSL LISTEND UK90173 COVER LETTER END UK90174 COVER LETTER START PROBLEM DESCRIPTION(S): PM62036 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of * * nested SQL inline table user * * defined functions. * **************************************************************** * PROBLEM DESCRIPTION: APAR PM62036 fixes the following * * problems: * * * * 1. ABEND0C4 at DSNIDM DSNOTCSO +0D00 * * may occur for an SQL statement that * * satisfies the following conditions: * * a. The SQL statement references * * a nested SQL inline table user defined * * function. * * b. The SQL inline table user defined * * function contains a parameter with a * * LOB data type. * * c. The argument of the inline table * * user defined function is a varchar * * literal constant. * * * * 2. SQLCODE -433 or SQLCODE -404 will * * be issued when the length of the * * parameter of an inline table user * * defined function is not large * * enough to hold the argument. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PM62036 fixes the following problems: 1. ABEND0C4 in DSNDIDM DSNOTCSO 0D00 may occur for an SQL statement that satisfies the following conditions: a. The SQL statement references a nested SQL inline table user defined function. b. The SQL inline table user defined function contains a parameter of a LOB data type. c. The argument to the inline table user defined function is a varchar literal constant. For Example, CREATE FUNCTION TAB1 ( STRING CLOB ( 100 ) ) RETURNS TABLE ( ORDINAL INTEGER , INDEX INTEGER ) 1 LANGUAGE SQL DETERMINISTIC NO EXTERNAL ACTION READS SQL DATA RETURN WITH T ( ORDINAL , INDEX ) AS ( SELECT 0 , 0 FROM SYSIBM.SYSDUMMY1 UNION ALL SELECT ORDINAL+1 , LENGTH(CAST ('ABC' AS CLOB(100))) FROM T WHERE ORDINAL < 10) SELECT ORDINAL , INDEX FROM T; CREATE FUNCTION TAB2 ( STRING CLOB ( 64 K ) ) RETURNS TABLE ( ELEMENTS CLOB (100) ) LANGUAGE SQL DETERMINISTIC NO EXTERNAL ACTION READS SQL DATA RETURN SELECT STRING FROM TABLE (TAB1 ('abc')) AS X(COL1, COL2); SELECT ELEM FROM TABLE ( TAB2('ABCD, DEF, GHI,8157')) AS T(ELEM); An abend may occur for the statement above because the varchar argument is not converted to LOB data type correctly when the inline table user defined function TAB2 is called. 2. SQLCODE -433 or SQLCODE -404 will be issued when the length of the parameter of an inline table user defined function is not large enough to hold the argument. For Example, CREATE FUNCTION TAB2 ( STRING VARCHAR(5)) RETURNS TABLE ( COL1 VARCHAR (5)) LANGUAGE SQL DETERMINISTIC NO EXTERNAL ACTION READS SQL DATA RETURN SELECT STRING FROM SYSIBM.SYSDUMMY1; SELECT * FROM TABLE (TAB2 ('12345678'))TX; This statement will receive SQLCODE -404 because the length of the parameter STRING which is 5 bytes is not long enough to hold the argument which is 8 bytes. DB2 was fixed to correctly: 1. Convert varchar data type to a LOB data type correctly. 2. Issue SQLCODE -404 or SQLCODE -433 when the length of the parameter is not large enough to hold the argument. Additional Keywords: SQLLOB SQLINLINE SQLTABLEUDF OFFSET0D00 SQLCODE404 SQLCODE433 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62036 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71335: See PM71335 APAR/PTF text for additional information about why a REBIND is necessary. PM71335 corrects a problem that incorrect output could happen for an SQL statement that satisfies all of the following conditions: 1. It contains multiple table expressions or views. 2. One of the table expression or view contains UNION ALL. 3. A predicate contains a special register that can be pushed down to the table expression or view. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM62036: See PM62036 APAR/PTF text for additional information about why a REBIND is necessary. PM62036 corrects a problem of abend ABEND0C4 at DSNIDM DSNOTCSO 0D00 may occur for an SQL statement that references a nested inline table user defined function with LOB parameter data type and varchar literal constant argument. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOACR PM62036 DSNXOB1 PM62036 DSNXOB2 PM62036 DSNXODSO PM62036 DSNXOEXC PM62036 DSNXOFD PM62036 DSNXOFN3 PM62036 DSNXOGA1 PM62036 DSNXOIWS PM62036 DSNXOJW PM62036 DSNXOOS2 PM62036 DSNXOP0 PM62036 DSNXOP1 PM62036 DSNXORFN PM62036 DSNXOSL PM62036 1 DSNXOVC PM62036 DSNXOVM PM62036 DSNXOV0 PM62036 DSNXOV1 PM62036 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62036 DSNXOACR DSNXOB1 DSNXOB2 DSNXODSO DSNXOEXC DSNXOFD DSNXOFN3 DSNXOGA1 DSNXOIWS DSNXOJW DSNXOOS2 DSNXOP0 DSNXOP1 DSNXORFN DSNXOSL DSNXOVC DSNXOVM DSNXOV0 DSNXOV1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOACR DSNXOB1 DSNXOB2 DSNXODSO DSNXOEXC DSNXOFD DSNXOFN3 DSNXOGA1 DSNXOIWS DSNXOJW DSNXOOS2 DSNXOP0 DSNXOP1 DSNXORFN DSNXOSL DSNXOVC DSNXOVM DSNXOV0 DSNXOV1 LISTEND UK90174 COVER LETTER END UK90197 COVER LETTER START PROBLEM DESCRIPTION(S): PM76924 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V9 and V10 users who need * * an updated copy of the Diagnosis Guide * * and Reference. * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides updated PDF files * * of the DB2 for z/OS V9 and V10 * * Diagnosis Guide and Reference. * **************************************************************** * RECOMMENDATION: * **************************************************************** Users require updated PDF files for the DB2 for z/OS V9 and V10 Diagnosis Guide and Reference. This APAR provides updated PDF files of the DB2 for z/OS V9 and V10 Diagnosis Guide and Reference. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76924 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDR PM76924 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76924 DSNDR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNDR LISTEND UK90197 COVER LETTER END UK90208 COVER LETTER START PROBLEM DESCRIPTION(S): PM75170 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the CURRENT * * TIME ZONE, CURRENT TIMESTAMP, CURRENT DATE, * * and CURRENT TIME special registers or the * * TIMESTAMP WITH TIME ZONE data type with z/OS * * 1.11 or above. * **************************************************************** * PROBLEM DESCRIPTION: DB2 issued an SQLCODE -187 (SQLCODE187) * * for a valid CURRENT DATE, TIME, * * TIMESTAMP or TIME ZONE special * * register, or for a TIMESTAMP WITH TIME * * ZONE data type after the MVS TOD clock * * value has been changed for z/OS 1.11. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 issued an SQLCODE -187 for a valid CURRENT DATE, TIME, TIMESTAMP, or TIME ZONE which results from a special register, or for a TIMESTAMP WITH TIME ZONE data type, after the MVS TOD clock value has been changed on z/OS 1.11. Instead, DB2 should not issue the SQLCODE. The following example helps to illustrate the problem. 1. Change the MVS TOD clock value to 48 hours past (later than) the UTC date on z/OS 1.11. For example, if the current UTC DATE on the system is 2012.341 (December 6th), change the DATE to 2 days later (to be December 8th). SET DATE=2012.343 1 2. Execute the following statement. SELECT CURRENT DATE FROM SYSIBM.SYSDUMMY1; 3. Check the results. DB2 issues an SQLCODE -187. The expected result to be returned is the date 2012-12-08. DB2 does not allow a TIME ZONE beyond +/-24:00 (hours) once the TOD value has been changed to a value beyond or earlier than the system UTC time +/-24:00. This affects the field representing the TOD clock in z/OS 1.11. As a result, DB2 incorrectly issues an SQLCODE -187 when retrieving the changed value to use in setting the special register. PLEASE NOTE. The above problem can also occur when the current system UTC DATE is changed to 2 days earlier. DB2 code has been changed to adjust the TIME ZONE value within the range of +/-12:00 when the system TOD has been changed to (a later or earlier time) a value beyond or earlier than the system UTC time +/-24:00. Additional Keywords: SQLTIMESTAMP SQLTIME SQLDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75170 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The DB2 z/OS for v10 SQL Reference description of the CURRENT TIME ZONE special register will be changed as follows: CURRENT TIME ZONE The CURRENT TIME ZONE special register specifies a value that contains the difference between UTC and local time at the current server, if the SESSION TIME ZONE special register has not been set. The data type is DECIMAL(6,0). The difference between UTC and local time at the current server is represented by a time duration (a decimal number in which the first two digits are the number of hours, the next two digits are the number of minutes, and the last two digits are the number of seconds). The number of hours is adjusted if necessary to fit in the range between -24 and 24 exclusive. Subtracting CURRENT TIME ZONE from a local time converts that local time to UTC. CURRENT TIMEZONE can be specified as an alternative to CURRENT TIME ZONE. 1 Please note, the sentence "The number of hours is adjusted if necessary to fit in the range between -24 and 24 exclusive." was added. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHVCTS PM75170 DSNILECV PM75170 DSNUVCTS PM75170 DSNUVVTS PM75170 DSNXVCTS PM75170 DSNXVTS9 PM75170 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75170 DSNHVCTS DSNILECV DSNUVCTS DSNUVVTS DSNXVCTS DSNXVTS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHVCTS DSNILECV DSNUVCTS DSNUVVTS DSNXVCTS DSNXVTS9 LISTEND UK90208 COVER LETTER END UK90212 COVER LETTER START PROBLEM DESCRIPTION(S): PM72444 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of hash table space. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISEGR ERQUAL5015 * * during inserting to hash table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** In data sharing environment, member A inserted to hash table space the first overflow recod, and accordingly, the first segment for the overflow area was allocated. Member B read the header page and knew overflow area was allocated but the space map page for the first overflow segment was not written to group buffer pool (GBP) by member A yet, member B couldn't tolerate the mismatch and abended in DSNISEGR. DB2 code is modified to make sure the space map page will be written out to GBP instantly for the first overflow segment allocation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72444 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: 1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISEGF PM72444 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72444 DSNISEGF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISEGF LISTEND UK90212 COVER LETTER END UK90222 COVER LETTER START PROBLEM DESCRIPTION(S): PM72676 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of nested * * non-correlated subqueries. * **************************************************************** * PROBLEM DESCRIPTION: The total cost of an access path may * * not be accurately estimated for a query * * when the query contains nested * * non-correlated subqueries. * **************************************************************** * RECOMMENDATION: * **************************************************************** The total cost of an access path may not be accurately estimated for a query when the query contains nested non-correlated subqueries. The COMPCOST of the DSN_DETCOST_TABLE and the PROCMS, PROCSU and TOTAL_COST of the DSN_STATEMNT_TABLE may not be accurately displayed. For example, SELECT 1000000 / (SELECT A.C1 - B.C1 FROM (SELECT T1.C1 FROM T1 ORDER BY T1.C1 FETCH FIRST 1 ROW ONLY) A, (SELECT T2.C1 FROM T2 ORDER BY T2.C1 FETCH FIRST 1 ROW ONLY) B) AS Y FROM T3; A and B are table expressions nested in the table expression Y. The cost estimation of the query above may not be accurate. Additional keywords: SQLACCESSPATH SQLPERFORMANCE SQLEXPLAIN SQLSUBQUERY SQLNONCORRSUBQ Code has been modified to correct the cost estimation of the 1 queries described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72676 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM73214: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM73214 corrects a problem of inaccurate cost estimation for a query when the query contains a view or table expression with UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM72676: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM72676 corrects a problem of inaccurate cost estimation for a query when the query contains nested non-correlated subqueries. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTS PM72676 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72676 DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTS LISTEND UK90222 COVER LETTER END UK90233 COVER LETTER START PROBLEM DESCRIPTION(S): PM68894 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of CHECK DATA SHRLEVEL CHANGE with * 1 * AUXERROR INVALIDATE, LOBERROR INVALIDATE, * * or XMLERROR INVALIDATE * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA generates REPAIR statements * * for invalidating LOB or XML columns * * for a table in a compressed tablespace. * **************************************************************** * RECOMMENDATION: * **************************************************************** CHECK DATA SHRLEVEL CHANGE AUXERROR INVALIDATE generates a REPAIR statement to invalidate the LOB or XML column by setting an invalid bit in the base row. The offsets in the REPAIR statement for both VERIFY and REPLACE are determined by the offset of the column in a non-compressed row. This offset is not valid when running the REPAIR on a compressed row. CHECK DATA with SHRLEVEL CHANGE will issue message DSNU714I when AUXERROR INVALIDATE, LOBERROR INVALIDATE, or XMLERROR INVALIDATE is specified for a compressed tablespace. DSNU714I csect-name CHECK DATA CANNOT GENERATE A REPAIR STATEMENT FOR A COMPRESSED ROW OF TABLE table_name Explanation CHECK DATA detected an inconsistency on a compressed row in table table_name. SHRLEVEL CHANGE and AUXERROR INVALIDATE, LOBERROR INVALIDATE, or XMLERROR INVALIDATE was specified, but a REPAIR statement cannot be generated for a compressed row. System action The CHECK DATA utility continues processing. System programmer response See previous message to determine the inconsistency. Consider modifying the CHECK DATA utility to use SHRLEVEL REFERENCE or the REPORT option of AUXERROR, LOBERROR, or XMLERROR. Severity 4 (error) COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68894 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM68894 provides support to print message DSNU714I when CHECK DATA SHRLEVEL CHANGE cannot generate a REPAIR statement because the base row is compressed. REPAIR statements are generated for some inconsistencies when AUXERROR/LOBERROR/XMLERROR INVALIDATE is specified with SHRLEVEL CHANGE. DSNU714I csect-name CHECK DATA CANNOT GENERATE A REPAIR STATEMENT 1 FOR A COMPRESSED ROW OF TABLE table_name Explanation CHECK DATA detected an inconsistency on a compressed row in table table_name. SHRLEVEL CHANGE and AUXERROR INVALIDATE, LOBERROR INVALIDATE, or XMLERROR INVALIDATE was specified, but a REPAIR statement cannot be generated for a compressed row. System action The CHECK DATA utility continues processing. System programmer response See previous message to determine the inconsistency. Consider modifying the CHECK DATA utility to use SHRLEVEL REFERENCE or the REPORT option of AUXERROR, LOBERROR, or XMLERROR. Severity 4 (error) ACTION: The PTF for APAR PM68894 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the function the PTF provides will not be available. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFMDIR PM68894 DSNFUDRC PM68894 DSNIRNXT PM68894 DSNUKERK PM68894 DSNUKNFK PM68894 DSNUKSCT PM68894 DSNUMSGC PM68894 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68894 DSNFMDIR DSNFUDRC DSNIRNXT DSNUKERK DSNUKNFK DSNUKSCT DSNUMSGC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFUDRC DSNIRNXT DSNUKERK DSNUKNFK DSNUKSCT DSNUMSGC 1 LISTEND UK90233 COVER LETTER END UK90266 COVER LETTER START PROBLEM DESCRIPTION(S): PM76286 - **************************************************************** * USERS AFFECTED: IRLM termination may take over 30 seconds * * after DB2 address spaces are gone causing * * DB2 restart attempt by ARM to fail at times. * **************************************************************** * PROBLEM DESCRIPTION: IRLM termination takes longer sometimes * * causing DB2 restart to be delayed. ARM * * fails to restart DB2, issues MSGDXR116E * * DXR116E for INITIALIZATION FAILED, * * CODE=09 DETECTED BY DXRRL010 * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** After stopping DB2 or IRLM, IRLM termination process may take longer than expected some times. There is a timing window where End-of-Memory may be received from DB2 while there was an active request from DB2 in IRLM which kept IRLM tracking of requests count as non-zero. IRLM healthcheck triggers cleanup activity but the active request count was not adjusted. This caused IRLM ESTAE to wait unnecessarily for 30 seconds before giving up and continuing with the termination process. IRLM address space remains up for this extra time in this situation and would cause failure in restarting IRLM by DB2 ARM. MSGDXR116E is issued when DB2 restart attempt fails. GEN: KEYWORDS: *** END IMS KEYWORDS *** This APAR correctly adjusts IRLM active request counts when DB2 End-of-Memory cleanup recovery is scheduled by IRLM healthcheck. IRLM ESTAE will not have to wait for extra 30 seconds under this condition and IRLM will terminate faster. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM76286 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL272 PM76286 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76286 DXRRL272 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DXRRL272 LISTEND UK90266 COVER LETTER END UK90276 COVER LETTER START PROBLEM DESCRIPTION(S): PM74596 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of CHECK LOB and CHECK DATA utilities * **************************************************************** * PROBLEM DESCRIPTION: Shadow datasets were not deleted when * * CHECK LOB SHRLEVEL CHANGE terminated * * with error. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a CHECK LOB SHRLEVEL CHANGE utility. The CHECK LOB utility called DFSMSdss to create shadow datasets. DFSMSdss met some error and not all the shadow datasets were created. CHECK LOB terminated with RC8, but the shadow datasets were not deleted. The shadow datasets could also be left over if user terminates the CHECK LOB using a TERM UTILITY command after the datasets are created. When CHECK LOB SHRLEVEL CHANGE terminates with RC8, shadow datasets should be cleaned up. The same problem can happen with CHECK DATA SHRLEVEL CHANGE. CHECK LOB and CHECK DATA utilities were modified to clean up shadow datasets properly during error processing when SHRLEVEL CHANGE is specified. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74596 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKLBD PM74596 DSNUK001 PM74596 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74596 DSNUKLBD DSNUK001 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKLBD DSNUK001 LISTEND UK90276 COVER LETTER END 1UK90311 COVER LETTER START PROBLEM DESCRIPTION(S): PM76608 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an SQL * * statement that contains FETCH FIRST n ROWS * * ONLY in a table expression. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output could happen for an * * SQL statement that contains FETCH FIRST * * n ROWS ONLY in a table expression, on * * which there is a predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output could happen for an SQL statement that contains FETCH FIRST n ROWS ONLY in a table expression, on which there is a predicate. An example is shown below: CREATE TABLE T1 ( C1 INT, C2 INT ) ; INSERT INTO T1 VALUES(11, 21); INSERT INTO T1 VALUES(12, 22); SELECT COUNT(*) FROM (SELECT C1, C2 FROM T1 WHERE C1 = 12 FETCH FIRST 1 ROWS ONLY ) AS TX(C1, C2) WHERE C1 = 12 ; The query above should return number 1, while incorrectly returned number 0. DB2 did not correctly process the aforementioned SQL statements, which caused the incorrect output. DB2 has been modified to correctly process the aforementioned SQL statement, so there will be no incorrect output. Additional keywords: SQLTABLEEXPR SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLFFNR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76608 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM76608: 1 See PM76608 APAR/PTF text for additional information about why a REBIND is necessary. PM76608 corrects a problem that incorrect output could happen for an SQL statement that contains FETCH FIRST n ROWS ONLY in a table expression, on which there is a predicate. The access path of the SQL statement maybe changed after applying PM76608, as predicates will not be push down to the table expression that contains FETCH FIRST n ROWS ONLY. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPRU PM76608 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76608 DSNXOPRU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRU LISTEND UK90311 COVER LETTER END UK90325 COVER LETTER START PROBLEM DESCRIPTION(S): PM43293 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where DB2 is a member of a * * data sharing group and is configured with * * DDF THREADS = INACTIVE specified * * (DSN6FAC CMTSTAT INACTIVE). * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: New function is being provided to * * assist users in managing connections * * relative to remote client system * * applications. * **************************************************************** * RECOMMENDATION: * **************************************************************** Operational and/or serviceability improvements are required in the following areas: o When MAXDBAT is reached at a member of a data sharing group, requests from clients (that require a DBAT to process) will queue up until either CONDBAT has been reached or the number 1 of requests waiting for a DBAT exceeds the MAXDBAT value. Those requests can be a request from an inactive connection to execute a new transaction or a request to establish a new connection from a client. When a DBAT does become available, DB2 (DDF) will then associate the DBAT to the next queued connection request so the work can be processed. If, for some reason, DBATs do not become available to handle these requests, the queue of connection requests (waiting for a DBAT) will continue to grow until either the maximum number of remote connections (CONDBAT) has been reached or the depth of the queue has exceeded the MAXDBAT value. - When CONDBAT is reached, new connection requests will be rejected and message DSNL030I is issued with reason code 00D31034. - If the depth of queue has been exceeded before CONDBAT is reached, then DB2 closes the TCP/IP socket and marks the connection for eventual clean up, but a DBAT is still needed to fully complete this connection clean up. A serviceability issue exists in this case because no message is issued to indicate that the client connection was closed. Eventually, DB2 (DDF) could reach a state where no new work could be accepted from a client because the maximum number of remote connections has been reached. Also, since the weight of the DB2 member might not instantly reflect a DBAT unavailability issue with the server, clients may continue to send requests to establish new connections to the member (which would then be instantly rejected) or send requests to run new transactions on existing connections (which would then queue up waiting for a DBAT to process the request). This condition would continue at the member until the DBAT unavailability issue is resolved. However, if these client requests had come from distributed applications using the IBM Data Server Driver or Client product family and/or the DB2 Connect product family configured to operate in sysplex workload balancing mode, those client requests, if given the chance, could have been seamlessly redirected to another member of the data sharing group where execution resources may be more abundant. Another result of the behavior by DB2 to close the client socket (of a connection waiting for a DBAT to process its next request) is that the count of the number of connections from a client may not be reduced to zero when all work has eventually been processed. This inaccurate count may be observed in the DISPLAY LOCATION command report. DB2 needs to provide users with a more effective way to observe and manage this connection behavior. o DB2 for z/OS supports a "KeepDynamic Refresh" concept. When packages are bound with KEEPDYNAMIC(YES), the DBAT/connection association must be maintained and hence there are fewer DBATs available to service other work. A refresh capability exists that causes the DBAT/connection combination to be terminated after one hour of use or 20 minutes of being idle, hence allowing a replacement DBAT to be created to service other work. To prevent this condition from impacting the remote application, this termination of the DBAT/connection 1 only occurs if the client identifies itself with the ability to seamlessly move the client connection over to a new connection at the same member or a different member of a data sharing group. In supporting this KeepDynamic Refresh capability, a serviceability condition exists because no message is issued at the DB2 member indicating that this DBAT/connection termination event has occurred. o When a DB2 server thread (DBAT) abnormally terminates for whatever reason, the information sent to, and received by, the client (and possibly logged for some situations) may not contain the necessary level of information about the DB2 DBAT failure so that effective problem determination can be conducted. The following changes are being made to DB2 10 for z/OS: Draining of queued client connection requests. --------------------------------------------------------------- Two new subsystem parameters will be supported, MAXCONQN and MAXCONQW, for the DSN6FAC macro. Their defaults will be to have essentially no effect, i.e. the maximum number of possible queued connection requests will continue to be controlled solely by the CONDBAT subsystem parameter (which is current behavior). MAXCONQN will represent the maximum number of inactive or new connections that can be queued waiting for a DBAT to process the request. When such a request is added to the connection request queue and MAXDBAT has also been reached, then if the depth of the connection request queue has also reached the value for MAXCONQN (unless MAXCONQN was set to OFF), DDF will close the client connection with the longest time queued. This gives a remote client system the opportunity to redirect the work to other members of the group that have more resources to process the work. This new capability will only occur when the DB2 subsystem is a member of a data sharing group and DB2 was started with DDF THREADS set to INACTIVE. This subsystem parameter value can be updated online. When a client connection is closed due to MAXCONQN being exceeded, message DSNL030I will be issued with a new reason code, 00D31053. To eliminate potential flooding of messages to the console, the message will only be issued if five minutes have elapsed since this message was last issued relative to the same client IP address. MAXCONQW will represent the maximum wait time that a client connection will remain queued for a DBAT to process the next transaction or new connection request. Each queued connection request entry is examined to see if its time waiting in the queue has exceeded the MAXCONQW value. If the time has been exceeded, the client connection will be closed. If the parameter was set to OFF, then the client connection request will wait indefinitely, as traditionally done, for a DBAT. 1 This new capability will only occur when the DB2 subsystem is a member of a data sharing group and DB2 was started with DDF THREADS set to INACTIVE. This subsystem parameter value can be updated online. When a client connection is closed due to MAXCONQW being exceeded condition, message DSNL030I will be issued with a new reason code value of 00D31054. To eliminate potential flooding of messages to the console, the message will only be issued if five minutes have elapsed since this message was last issued relative to the same client IP address. The -DISPLAY DDF DETAIL command report will be enhanced to display the current configured values for the MAXCONQN and MAXCONQW subsystem parameters via a new message, DSNL091I. The number of closed connections due to MAXCONQN and MAXCONQW will be displayed via a new message, DSNL094I. These two new messages can only be displayed when the subsystem is a member of a data sharing group. Also, regardless of the values specified for MAXCONQN and MAXCONQW, a value of zero (OFF) will be assumed if DB2 is configured with DDF THREADS ACTIVE (DSN6FAC CMTSTAT=ACTIVE). Note: The DDF THREADS subsystem parameter is not online changeable. Various statistics values will also be enhanced or added. A new counter, QDSTNCQW is added to global DDF activity statistics (DSNDQDST) and will report the number of client connections closed due to MAXCONQW being exceeded. The description for an existing counter, QDSTNCQC, is changed to indicate that it reflects the number of client connections closed due to MAXCONQN being exceeded. An existing counter, QLSTCNVT, will be now be updated at the server to indicate the number of connections (at this location) that were closed due to either MAXCONQN and/or MAXCONQW being exceeded. This counter is also reported, per remote location, via statistics trace CLASS(7) or IFCID365 as well as an IFC READS call against IFCID365. Reducing member health as number of connections increases. --------------------------------------------------------------- A new message, DSNL074I, will be issued when the current number of client connections exceeds either 80% or 90% of CONDBAT. Correspondingly, the DB2 (DDF) system health will also be reduced to 50% or 25%, respectively, of the current calculated DB2 health value and reported to WLM immediately. A new message, DSNL075I, will be issued when the number of client connections no longer exceeds 80% or 90% of CONDBAT. Correspondingly, the DB2 (DDF) system health will be improved back to either 50% or 100%, respectively, of the calculated DB2 health value and then reported to WLM. The new messages and the corresponding changes to the DB2 (DDF) system health value will only occur when the subsystem is a member of a data sharing group. 1 The health value reported to WLM can now be obtained via the following messages: - DSNV507I issued for the ACTIVE MONITOR as a result of the -DISPLAY THREAD(*) TYPE(SYSTEM) command. - DSNL094I, a new message, issued as a result of the -DISPLAY DDF DETAIL command. The new message will only be issued when the subsystem is a member of a data sharing group. KEEPDYNAMIC Refresh messages. --------------------------------------------------------------- Two different events can occur when KEEPDYNAMIC Refresh is enabled on the connection. The connection/thread has been used too long (greater than one hour) and the connection/thread has been idle too long (greater than 20 minutes). When either of the events have occurred, the DSNL027I message will be issued with two new reason codes, 00D3003E and 00D3003F, to indicate which event has occurred. To eliminate potential flooding of messages to the console, the message will only be issued if five minutes have elapsed since this message was last issued relative to the same client IP address. Note: A connection/thread is ONLY terminated after one hour of use or idle for 20 minutes when the connection/thread is not actively processing a transaction and/or holding a resource (other than the DBAT and allocated KeepDynamic packages) past a commit. DB2 DBAT Termination processing. --------------------------------------------------------------- DB2 DBAT termination processing has been improved to more effectively return information describing the cause of the termination. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM43293 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: ***Documentation for PM43293: See PM43293 APAR/PTF text for additional information. The following text contains the documentation of the function provided by this APAR. The product documentation contained in the Information Management Software for z/OS Solutions Information Center will be updated at a later date. New Subsystem Parameter, MAXCONQN, for DSN6FAC Macro --------------------------------------------------------------- MAXCONQN=(OFF|ON|1<=numeric-value<=19999) OFF - This is the default value for the parameter which means that no attempt will be made to close a client connection. ON - The support is enabled and the value used will be the 1 value specified for MAXDBAT. Thus, a client connection will only be closed when MAXDBAT has been reached and MAXDBAT is also the depth of the connection request queue. However, if CONDBAT is reached first, a client connection will only be closed due to CONDBAT being reached. numeric-value - This is a positive integer less than or equal to the maximum value that can be specified for MAXDBAT. New Subsystem Parameter, MAXCONQW, for DSN6FAC Macro --------------------------------------------------------------- MAXCONQW=(OFF|ON|5<=numeric-value<=3600) OFF - This is the default value for the parameter which means that no attempt will be made to close a client connection. ON - The support is enabled and the value used will be the value specified for IDTHTOIN. numeric-value - This is a positive integer which represents a time duration in seconds which must be greater than or equal to 5 seconds and less than or equal to 3600 seconds (one hour). New Reason Codes --------------------------------------------------------------- 00D3003E Explanation: The connection/thread is running under KEEPDYNAMIC Refresh rules and it has been determined that the connection/thread has been actively in use for over one hour. This determination occurs only after a unit-of-work has completed and no other pending resource usages have caused the thread to stay active with its connection other than the use of KEEPDYNAMIC(YES) bound packages. This is a normal condition if the client has connected to DB2 indicating that it is either sysplex workload balancing enabled or seamless failover enabled and using packages bound with KEEPDYNAMIC(YES). System action: The connection/thread has been terminated. User response: The IBM Data Server Driver for JAVA and the IBM Data Server Driver for ODBC/CLI/.NET support the KEEPDYNAMIC Refresh rules such that when a client socket has been closed from the server, it will then attempt a reconnect back to the same server and mark all statements currently managed under the connection as now requiring a prepare. 00D3003F Explanation: The connection/thread is running under KEEPDYNAMIC Refresh rules and it has been determined that the 1 connection/thread has been idle for over 20 minutes. This determination occurs only after a unit-of-work has completed and no other pending resource usages have caused the thread to stay active with its connection other than the use of KEEPDYNAMIC(YES) bound packages. This is a normal condition if the client has connected to DB2 indicating that it is either sysplex workload balancing enabled or seamless failover enabled and using packages bound with KEEPDYNAMIC(YES). System action: The connection/thread has been terminated. User response: The IBM Data Server Driver for JAVA and the IBM Data Server Driver for ODBC/CLI/.NET support the KEEPDYNAMIC Refresh rules such that when a client socket has been closed from the server, it will then attempt a reconnect back to the same server and mark all statements currently managed under the connection as now requiring a prepare. 00D31053 Explanation: The CONN QUEUED MAX DEPTH subsystem parameter (ZPARM MAXCONQN) has been reached and the connection waiting the longest in the connection request queue has had its TCP/IP socket closed. System action: The client is no longer connected to DB2. User response: This reason code may indicate that a slowdown in the processing of requests has or is occurring. Since MAXDBAT has also been reached, actions should be taken to either increase MAXDBAT or determine the cause of the slowdown of the request processing. 00D31054 Explanation: DB2 has found that a connection request has been waiting for a period of time in excess of the CONN QUEUED MAX WAIT subsystem parameter (ZPARM MAXCONQW) and the connection has had its TCP/IP socket closed. System action: The client is no longer connected to DB2. User response: This reason code may indicate that a slowdown in the processing of requests has or is occurring. Since MAXDBAT would have also been reached, actions should be taken to either increase MAXDBAT or determine the cause of the slowdown of the request processing. New Messages to Display Client Connection Thresholds --------------------------------------------------------------- DSNL074I NUMBER OF CLIENT CONNECTIONS HAS EXCEEDED nn% OF 1 THE MAXIMUM ALLOWED Explanation: This message will be issued when the number of increasing client connections has exceeded either 80% or 90% relative to the MAX REMOTE ACTIVE subsystem parameter (ZPARM CONDBAT). The health value reported to WLM will also be decreased to 50% (when nn is 80) or 25% (when nn is 90) of the calculated DB2 system health value. This is done in an effort to potentially allow remote client systems to direct work to other members which have more resources to process the work. This adjustment will continue until the number of client connections decreases below either the 80% or 90% threshold. The message can only be issued when the DB2 subsystem is a member of a data sharing group and DB2 was started with DDF THREADS set to INACTIVE. System action: Processing continues normally. System Programmer response: Depending on the subsystem's current CONDBAT subsystem parameter value, the display of this message could be of some concern. An investigation into why the number of connections has exceeded the indicated threshold should be undertaken. If the subsystem could handle more inbound connections, a new subsystem parameters module with a higher CONDBAT value can be brought online to alleviate the reduction of the subsystem's health value. As long as DSNL075I is displayed indicating that the number of connections has then dropped below one of the thresholds, no further action should be necessary. However, if the percentage still keeps increasing, one should use the -DISPLAY LOCATION command to find out which client locations are increasing their connections to this DB2 subsystem. A determination should then be made as to whether the cause is due to normal workload growth which would require no more actions are to be taken other than continued monitoring or due to an exception condition which would require further investigation to determine the reason for the exception. DSNL075I NUMBER OF CLIENT CONNECTIONS NO LONGER EXCEEDS nn% OF THE MAXIMUM ALLOWED Explanation: This message will be issued when the number of client connections has decreased such that either the 80% or 90% threshold relative to the MAX REMOTE ACTIVE subsystem parameter (ZPARM CONDBAT) is no longer being exceeded. The health value reported to WLM will also be increased to 50% (when nn is 90) or 100% (when nn is 80) of the calculated DB2 system health value. The message can only be issued when the DB2 subsystem is a member of a data sharing group and DB2 was started with DDF THREADS set to INACTIVE. System action: Processing continues normally. System Programmer response: The display of this message indicates that conditions have improved at the subsystem. 1 No further action is necessary. New Message to Display Configured MAXCONQN and MAXCONQW Values --------------------------------------------------------------- The new DSNL091I message, which is issued as a result of a -DISPLAY DDF command, is being added to display the currently specified MAXCONQN and MAXCONQW values. The message will only be displayed if the DB2 subsystem is a member of a data sharing group. DSNL091I MCONQN=mconqn MCONQW=mconqw Explanation: This message is issued as a result of the -DISPLAY DDF DETAIL command. This message displays some of the subsystem parameter information associated with DDF when the subsystem is a member of a data sharing group. mconqn The depth of the queue of connections (as determined by the value specified for the MAXCONQN parameter of the DSN6FAC macro) waiting for a DBAT to process the next request. When this value is reached, and MAXDBAT has also been reached, DDF will close the oldest waiting client connection. A value of 0 will only be displayed for this parameter if DB2 had been started with the CMTSTAT parameter of the DSN6FAC macro was set to ACTIVE. mconqw The maximum amount of time (as determined by the value specified for the MAXCONQW parameter of the DSN6FAC macro) that a client connection will wait for a thread to process its request. DDF will attempt to close any client connection which has been waiting in excess of this time. A value of 0 will only be displayed for this parameter if DB2 had been started with the CMTSTAT parameter of the DSN6FAC macro was set to ACTIVE. System action: Processing continues normally. New Message to Display Closed Connection Counts and WLM Health --------------------------------------------------------------- The DSNL094I message, which is issued as a result of a -DISPLAY DDF DETAIL command, is being added to show the DB2 system health value as last reported to WLM and the number of client connections which were closed due to either MAXCONQN and/or MAXCONQW being exceeded. This message will only be displayed if the DB2 subsystem is a member of a data sharing group. DSNL094I WLMHEALTH=hlth CLSDCONQN=clsdn CLSDCONQW=clsdw Explanation: This message is issued as a result of the -DISPLAY DDF DETAIL command. The message will only be displayed when the subsystem is a member of a data sharing 1 group. hlth The DB2 system health value (0 to 100) as last reported to WLM. clsdn The number of client connections that have been closed due to MAXCONQN subsystem parameter being reached since DDF was last started. clsdw The number of client connections that have been closed due to MAXCONQW subsystem parameter being reached since DDF was last started. System action: Processing continues normally. Sample -DISPLAY DDF DETAIL Output with New Messages --------------------------------------------------------------- DSNL080I -DB2A DSNLTDDF DISPLAY DDF REPORT FOLLOWS: DSNL081I STATUS=STARTD DSNL082I LOCATION LUNAME GENERICLU DSNL083I STLEC1 USIBMSY.SYEC1A USIBMSY.SYEC1GLU DSNL084I TCPPORT=446 SECPORT=0 RESPORT=5001 IPNAME=-NONE DSNL085I IPADDR=::9.30.85.32 DSNL086I SQL DOMAIN=dune.vmec.svl.ibm.com DSNL086I RESYNC DOMAIN=caladan.vmec.svl.ibm.com DSNL089I MEMBER IPADDR=::9.30.85.33 DSNL090I DT=I CONDBAT= 64 MDBAT= 16 DSNL091I MCONQN= 16 MCONQW= 0 DSNL092I ADBAT= 0 QUEDBAT= 0 INADBAT= 0 CONQUED= 0 DSNL093I DSCDBAT= 0 INACONN= 0 DSNL094I WLMHEALTH=100 CLSDCONQN= 0 CLSDCONQW= 1 DSNL100I LOCATION SERVER LIST: DSNL101I WT IPADDR IPADDR DSNL102I 10 ::9.30.85.34 DSNL102I 10 ::9.30.85.33 DSNL102I 10 ::9.30.85.36 DSNL102I 10 ::9.30.85.37 DSNL102I 10 ::9.30.85.38 DSNL102I 10 ::9.30.85.39 DSNL099I DSNLTDDF DISPLAY DDF REPORT COMP Instrumentation Changes --------------------------------------------------------------- The following DDF system statistical values will now be maintained: DSNDQDST (Global DDF Activity): QDSTNCQC - Number of queued client connections which have had their TCP/IP sockets closed because MAXDBAT was reached and the number of inactive connections queued, waiting for a DBAT, has also reached MAXCONQN in number. The socket close will only be attempted in a member of a data sharing group. (This is an update to an existing field description) QDSTNCQW - Number of queued client connections which have had their TCP/IP sockets closed due to exceeding the time 1 specified by MAXCONQW while waiting for a DBAT to process their next request. The socket close will only be attempted in a member of a data sharing group. DSNDQLST (Location activity): QLSTCNVT - Number of conversations that were terminated from this site to the remote site. This is not a new value but the description will be changed to have the phrase "(meaningful at the AR)" removed. This value at a DDF server will be updated when MAXCONQN or MAXCONQW causes a connection to be teminated. This statistical value is reported for both individual locations as well as DRDA REMOTE LOCS. DSNDQWPZ (Subsystem Initialization Parameters): Fields QWP9MCONQN and QWP9MCONQW are added to trace the MAXCONQN and MAXCONQW settings. The IFCID 106 formatter stored procedures, SYSPROC.DSNWZP and SYSPROC.ADMIN_INFO_SYSPARM are updated to report the MAXCONQN and MAXCONQW settings. ACTION: ***Actions for PM43293: This PTF adds two online changeable DB2 subsystem parameters, MAXCONQN and MAXCONQW, to the DSN6FAC macro. * MAXCONQN: Maximum depth of the connection request queue of connections waiting for a DBAT to process a request. OFF indicates that the queue of is limited only by CONDBAT. ON says that the queue depth will default to MAXDBAT. Minimum for a numeric value is 1 and max is MAXDBAT maximum value. The default is OFF. * MAXCONQW: Maximum time for a connection to wait for a DBAT to process its request. OFF says that the connection will wait indefinitely. ON says that the time value specified for IDTHTOIN will be used. However, if IDTHTOIN is 0, then a warning mnote will be issued stating that MAXCONT is set to OFF because IDTHTOIN is 0. The minimum numeric value will be 5 and the maximum can be 3600 (seconds). The default is OFF. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST 1 target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameters MAXCONQN=, where is OFF, ON, or an integer from 1 to 19999, to the invocation of the DSN6FAC macro. Make sure to add a continuation character in column 72 if needed. If you do not add MAXCONQN here the value will be set to the default of OFF when you assemble the DSNZPxxx module. * Add the keyword parameters MAXCONQW=, where is OFF, ON, or an integer from 5 to 3600, to the invocation of the DSN6FAC macro. Make sure to add a continuation character in column 72 if needed. If you do not add MAXCONQW here the value will be set to the default of OFF when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF adds entries for MAXCONQN and MAXCONQW to the CLIST default input member in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: MAXCONQN CHARR M NONE NONE MAXCONQW CHARR M NONE NONE Change to the value you specified for MAXCONQN in step (2), above. Change to the value you specified for MAXCONQW in step (2), above. If you do not add MAXCONQN to a DSNTIDxx member, the DB2 installation CLIST will assume MAXCONQN=OFF when run with that member as input. If you do not add MAXCONQW to a DSNTIDxx member, the DB2 installation CLIST will assume MAXCONQW=OFF when run with that member as input. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM43293 DSNDQDST PM43293 DSNDQWPZ PM43293 DSNFLDIR PM43293 DSNFMDIR PM43293 1 DSNLBABR PM43293 DSNLCTRC PM43293 DSNLDALB PM43293 DSNLEDDA PM43293 DSNLEDTM PM43293 DSNLIDDC PM43293 DSNLIINI PM43293 DSNLIIN2 PM43293 DSNLILLM PM43293 DSNLILNR PM43293 DSNLQACT PM43293 DSNLQCRP PM43293 DSNLQCTL PM43293 DSNLQDIS PM43293 DSNLTDDF PM43293 DSNLTEXC PM43293 DSNLTMIN PM43293 DSNTIDXA PM43293 DSNTIDXB PM43293 DSNTIJUZ PM43293 DSNTINST PM43293 DSNTXAZP PM43293 DSNVDTM PM43293 DSNWDFDI PM43293 DSNWVZPS PM43293 DSNWZIFA PM43293 DSN6FAC PM43293 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM43293 DSN@XAZP DSNDQDST DSNDQWPZ DSNFLDIR DSNFMDIR DSNLBABR DSNLCTRC DSNLDALB DSNLEDDA DSNLEDTM DSNLIDDC DSNLIINI DSNLIIN2 DSNLILLM DSNLILNR DSNLQACT DSNLQCRP DSNLQCTL DSNLQDIS DSNLTDDF DSNLTEXC DSNLTMIN DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNVDTM DSNWDFDI DSNWVZPS DSNWZIFA DSN6FAC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFLDIR DSNFMDIR DSNLBABR DSNLCTRC DSNLDALB DSNLEDDA DSNLEDTM DSNLIDDC DSNLIINI DSNLIIN2 DSNLILLM DSNLILNR DSNLQACT DSNLQCRP DSNLQCTL DSNLQDIS DSNLTDDF 1 DSNLTEXC DSNLTMIN DSNTXAZP DSNVDTM DSNWDFDI DSNWVZPS DSNWZIFA MACROS DSN@XAZP DSNDQDST DSNDQWPZ DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSN6FAC LISTEND UK90325 COVER LETTER END UK90349 COVER LETTER START PROBLEM DESCRIPTION(S): PM72667 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those that use DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: Message DSNL030I THREAD-INFO message * * displays incorrectly if the primary * * authorization ID value contains the * * '#' character. For example: * * * * DSNL030I csect DDF PROCESSING FAILURE * * FOR * * LUWID=luw-id * * REASON=reason-code * * THREAD-INFO=admf * * 01:*:*:*:*:*:*:* * * * * where primary auth ID = admf#01 * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 message DSNL030I may display the THREAD-INFO text incorrectly if the value of the primary authorization ID associated with the thread contains a '#' character. The THREAD-INFO text displays incorrectly because DB2 uses the '#' character as the newline character for this message. NOTE: This problem only applies to users of DB2 10 for z/OS. The problem does not affect DB2 9 for z/OS or earlier users. This is because the THREAD-INFO message text was introduced in DB2 10 for z/OS where it became necessary to change the newline character. 1 DB2 10 for z/OS has been changed to use a different newline character for formatting the DSNL030I message so that the use of the '#' character for the primary authorization ID will be displayed correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72667 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFLDIR PM72667 DSNFMDIR PM72667 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72667 DSNFLDIR DSNFMDIR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFLDIR DSNFMDIR LISTEND UK90349 COVER LETTER END UK90366 COVER LETTER START PROBLEM DESCRIPTION(S): PM75608 - **************************************************************** * USERS AFFECTED: All DB2 users using buffer pool attribute * * AUTOSIZE=YES. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 in DSNB1ABP * **************************************************************** * RECOMMENDATION: * **************************************************************** When Work Load Manager (WLM) adjustment exit is invoked, it makes an alter buffer pool request with a parameter list asynchronously. In rare cases, WLM adjustment exit is invoked to terminate and free the parameter list before the previous alter buffer pool request is complete. The alter request abends while the parameter list is unexpectedly deallocated. DB2 has been fixed for WLM to allocate a parameter list for altering VPSIZE and the storage for the parameter list is deallocated when the alter request is complete. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75608 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1ABP PM75608 DSNB1WRA PM75608 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75608 DSNB1ABP DSNB1WRA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1ABP DSNB1WRA LISTEND UK90366 COVER LETTER END UK90369 COVER LETTER START PROBLEM DESCRIPTION(S): PM69178 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: When the XMLMODIFY function is called * * to update an XML column with an XML * * type modifier, DB2 might unnecessarily * * validate the entire document. * **************************************************************** * RECOMMENDATION: * **************************************************************** With z/OS R12 or later, or R11 PTF UA59082, or R10 PTF UA59081 and this DB2 PTF applied, DB2 XMLMODIFY validates the XML document under certain conditions. Please refer to DB2 10 for z/OS pureXML Guide for conditions and usage detail. The performance of the XMLMODIFY function on XML columns with an XML type modifier is enhanced. Additional keywords: XMLALL SQLXML XMLSCHEMA XMLUPDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69178 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF enhances DB2 XMLMODIFY function performance on XML column with XML type modifier. This enhancement requires z/OS R12 or later, or R11 PTF UA59082, or R10 PTF UA59081. *************************************************************** Actions for customers who are preparing to install or migrate to DB2 V10: *************************************************************** If you apply this PTF before installing or migrating to DB2 V10, and you use z/OS R10 or z/OS R11 then before you can use the SYSPROC.XSR_COMPLETE stored procedure, you need to have applied z/OS R11 PTF UA59082 or R10 PTF UA59081. 1 *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to DB2 V10, and you use z/OS R10 or z/OS R11 and you use the SYSPROC.XSR_COMPLETE stored procedure then -before- applying this PTF verify that you have applied z/OS R11 PTF UA59082 or R10 PTF UA59081. If you have already installed or migrated to DB2 V10, the following actions are required after you apply this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update customized copies of installation job DSNTIJMV (3) Update the DB2 Java WLM environment variable file (4) Rebind the packages(SYSXSR) that are updated as a result of installing this PTF (5) Refresh the WLM environment for SYSPROC.XSR_COMPLETE (6) re-run SYSPROC.XSR_COMPLETE to compile the schema into a new version of grammar These actions are detailed below: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members *********************************************************** * This action is required for all DB2 V10 customers *********************************************************** This PTF modifies CLIST member DSNTINS1 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your private copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update customized copies of installation job DSNTIJMV *********************************************************** * All DB2 V10 customers who use the SYSPROC.XSR_COMPLETE * stored procedure to perform XML schema validation need to * perform this step. *********************************************************** This PTF modifies installation job DSNTIJMV in the prefix.SDSNSAMP target library. After you apply this PTF, you need to update your customized copy of DSNTIJMV and remove the gxljosrgImpl.jar from the code to generate the DB2 Java WLM environment variable file. Proceed as follows: (a) Edit your customized DSNTIJMV job and locate job step DSNTIJR (b) Remove the words "and gxljosrgImpl.jar" from the comment block that precedes this job step (c) Remove the HFS path and file name for gxljosrgImpl.jar from the CLASSPATH variable. For example, remove: :/usr/include/java_classes/gxljosrgImpl.jar Note that the path and file name may be wrapped onto 1 more than one line. (d) Save your changes. ---------------------------------------------------------------- (3) Update the DB2 Java WLM environment variable file *********************************************************** * All DB2 V10 customers who use the SYSPROC.XSR_COMPLETE * stored procedure to perform XML schema validation need to * perform this step. *********************************************************** This PTF eliminates the need to include the gxljosrgImpl.jar file in the DB2 Java WLM environment variable file. After you apply this PTF, you need to update your copy of this file and remove the HFS path and file name for gxljosrgImpl.jar from the CLASSPATH variable as discussed in step (2)(c), above. If you use the DB2 Java WLM environment variable file provided by job DSNTIJMV, the name and location of the file that contains this variable is given by the PATH setting of the SYSUT2 DD statement in job step DSNTIJR of your customized copy of job DSNTIJMV. --------------------------------------------------------------- (4) Rebind the packages that are updated as a result of installing this PTF. *********************************************************** * All DB2 V10 customers who use the SYSPROC.XSR_COMPLETE * stored procedure to perform XML schema registration need * to perform this step. *********************************************************** Users need to process the following commands to bind the packages that are updated as a result of installing this PTF BIND PACKAGE(SYSXSR) MEMBER(DSNNVXCV) - ACTION(ADD) ISO(CS) CURRENTDATA(YES) ENCODING(UNICODE) - LIBRARY('.SDSNDBRM') Note: is the data set prefix of your DB2 10 target libraries ------------------------------------------------------------- (5) Refresh the WLM environment for SYSPROC.XSR_COMPLETE *********************************************************** * All DB2 V10 customers who use the SYSPROC.XSR_COMPLETE * stored procedure to perform XML schema registration need * to perform this step. *********************************************************** Issue the following VARY MVS command from the console to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment for running the SYSPROC.XSR_COMPLETE stored procedure. ------------------------------------------------------------- 1 (6) Re-run SYSPROC.XSR_COMPLETE to compile the schemas into new version of grammar. ********************************************************** * All DB2 V10 customers who use the SYSPROC.XSR_COMPLETE s * procedure to perform XML schema registration need to * perform this step. ********************************************************** Identify the schema name used in XML type modifier by executing the following statement: SELECT X.XSROBJECTNAME FROM SYSIBM.XSROBJECTS X, SYSIBM.SYSXMLTYPMSCHEMA T WHERE T.XSROBJECTID = X.XSROBJECTID; ACTION: This APAR introduces a new environment variable JDBCSTD for the Java WLM SP environment. When set JDBCSTD=4, The Java SP environment will use JDBC 4.0 standard JCC driver. If JDBCSTD is not set or set as JDBCSTD=3, there will be no change in the behavior and JDBC 3.0 standard driver will be used. The JDBC 4.0 standard driver must be installed when running with JDBCSTD=4 set. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@VXCV PM69178 DSNARA00 PM69178 DSNNOAPU PM69178 DSNNOBXV PM69178 DSNNOCCN PM69178 DSNNOPAR PM69178 DSNNOPVP PM69178 DSNNORCN PM69178 DSNNOUPD PM69178 DSNNQIV PM69178 DSNNQMD PM69178 DSNNRXSG PM69178 DSNNRXSR PM69178 DSNTIJMV PM69178 DSNTINS1 PM69178 DSNXINIT PM69178 DSNX9JVM PM69178 DSNX9SPJ PM69178 DSNX9WLJ PM69178 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69178 DSN@VXCV DSNARA00 DSNNOAPU DSNNOBXV DSNNOCCN DSNNOPAR DSNNOPVP DSNNORCN DSNNOUPD DSNNQIV DSNNQMD DSNNRXSG DSNNRXSR DSNTIJMV DSNTINS1 DSNXINIT DSNX9JVM DSNX9SPJ DSNX9WLJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNARA00 DSNNOAPU DSNNOBXV 1 DSNNOCCN DSNNOPAR DSNNOPVP DSNNORCN DSNNOUPD DSNNQIV DSNNQMD DSNNRXSG DSNNRXSR DSNXINIT DSNX9JVM DSNX9WLJ MACROS DSN@VXCV DSNTIJMV DSNTINS1 DSNX9SPJ LISTEND UK90369 COVER LETTER END UK90405 COVER LETTER START PROBLEM DESCRIPTION(S): PM73015 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of CHECK DATA utility with EXCEPTIONS * * keyword * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA with EXCEPTIONS against a * * partitioned table space with an * * indexed foreign key and referential * * integrity (RI) violations reset * * check pending (CHKP) for the partition * * with violations when reaching the * * EXCEPTIONS limit. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a CHECK DATA utility with EXCEPTIONS n against a partitioned table space in CHKP with an indexed foreign key. MSGDSNU733I was issued indicating a referential integrity violation was found and the utility ended with RC8 because the EXCEPTIONS limit was met. However, the table space was no longer in CHKP because the CHECK DATA utility erroneously reset the CHKP status for both the partition in which it hit the EXCEPTIONS limit and for the partitions which it had not yet finished processing. This problem does not exist if the EXCEPTIONS limit is not met. Additional Keywords: DSNU733I DSNU971I MSGDSNU971I DSNU973I MSGDSNU973I DSNU731I MSGDSNU731I CHECK DATA EXCEPTIONS code has been modified to set and reset 1 CHKP correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73015 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKIFK PM73015 DSNUKNFK PM73015 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73015 DSNUKIFK DSNUKNFK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKIFK DSNUKNFK LISTEND UK90405 COVER LETTER END UK90407 COVER LETTER START PROBLEM DESCRIPTION(S): PM77524 - **************************************************************** * USERS AFFECTED: ALL DB2 10 FOR z/OS USERS WITH VERSIONED * * DATA * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIMOFR:5006 * * WHEN ACCESSING TABLES * * WITH VERSIONED DATA FOLLOWING MODIFY * * RECOVERY UTILITY * **************************************************************** * RECOMMENDATION: * **************************************************************** In a data sharing environment, an ALTER TABLE statement was done which resulted in multiple versions of the data. Without running REORG, COPY utility was run. Later, MODIFY RECOVERY utility was run, and after that access to earlier versions of the data failed with ABEND04E RC00C90101 DSNIMOFR ERQUAL5006, ERQUAL5399, or other abends or SQL codes. This happened because the ALTER and certain update activity was done within a unique timing window, causing COPY to record incorrect oldest version information in SYSIBM.SYSCOPY. MODIFY RECOVERY relies on this information, and because it was incorrect, some versioning info in the OBD was deleted prematurely, and data that needed that info could not be properly accessed. COPY utility was changed to try to ensure that the correct oldest version info is always inserted into SYSCOPY. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77524 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: PM62607 has modified REPAIR VERSIONS TABLESPACE to perform a DRAIN of all readers and writers on the table space. REPAIR VERSIONS updates the catalog and directory with version information for the table space when you have moved the object from one system to another using DSN1COPY with the OBIDXLAT option. REPAIR VERSIONS should be executed before any access to the data and should therefore block all readers and writers during the REPAIR operation. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUADP1 PM77524 DSNUBASI PM77524 DSNUBAUS PM77524 DSNUBINS PM77524 DSNUCATM PM77524 DSNUCBVR PM77524 DSNUGFCR PM77524 DSNUGHSH PM77524 DSNUGTER PM77524 DSNUGTE0 PM77524 DSNUGUVR PM77524 DSNUKNFK PM77524 DSNUKRDY PM77524 DSNUMDEL PM77524 DSNUQUIA PM77524 DSNURBXZ PM77524 DSNURCKF PM77524 DSNURWT PM77524 DSNUYAR4 PM77524 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77524 DSNUADP1 DSNUBASI DSNUBAUS DSNUBINS DSNUCATM DSNUCBVR DSNUGFCR DSNUGHSH DSNUGTER DSNUGTE0 DSNUGUVR DSNUKNFK DSNUKRDY DSNUMDEL DSNUQUIA DSNURBXZ DSNURCKF DSNURWT DSNUYAR4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUADP1 DSNUBASI DSNUBAUS DSNUBINS DSNUCATM DSNUCBVR DSNUGFCR DSNUGHSH DSNUGTER DSNUGTE0 DSNUGUVR DSNUKNFK 1 DSNUKRDY DSNUMDEL DSNUQUIA DSNURBXZ DSNURCKF DSNURWT DSNUYAR4 LISTEND UK90407 COVER LETTER END UK90408 COVER LETTER START PROBLEM DESCRIPTION(S): PM74528 - **************************************************************** * USERS AFFECTED: All DB2 10 and DB2 9 for z/OS users of * * cursors (DECLARE CURSOR) on created global * * temporary tables (CGTT) * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DSNIWKFD +1C9A on created * * global temporary table when there is * * a very large number of cursors open * * on it (e.g. over 500 cursors) * **************************************************************** * RECOMMENDATION: * **************************************************************** The aforementioned abend occurred during cleanup of a created global temporary table (CGTT) that had a very large number of cursors open on it (e.g. over 500). The reason for the abend is that DB2 code was falsely assuming that there cannot be more than 500 cursors opened by the thread. Specifically, because of this incorrect assumption, the the reader CUB chain was not properly maintained, leading to the abend. Code has been changed to correctly process reader CUB chain on a CGTT when there is a very large number of cursors open. Additional keywords: SQLCGTT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74528 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWKFD PM74528 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74528 DSNIWKFD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWKFD 1 LISTEND UK90408 COVER LETTER END UK90447 COVER LETTER START PROBLEM DESCRIPTION(S): PM76452 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * decimal datatype and transitive closure. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C7 RC00000000 occurred at * * DSNXRDEC +3EB2 in DB2 9 or at * * DSNXRDEC +59BC in DB2 10 * * when a transitive closure * * predicate was in the form of * * COLUMN = host-variable where the * * column was a not null decimal and * * a NULL value was sent in during * * execution time for the host variable. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C7 RC0 occurred at location DSNXRDEC +3EB2 in DB2 9 or an ABEND0C7 RC0 occurred at location DSNXRDEC +59BC in DB2 10 when a transitive closure predicate was in the form of COLUMN = host-variable where the column was a not null decimal and a NULL value was sent in during execution time for the host variable. The following example illustrates how this failure can occur. 1. Create two tables, T1 and T2. CREATE TABLE T1(C1 DEC(10,3) NOT NULL); CREATE TABLE T2(C1 DEC(11,3) NOT NULL); 2. Insert values into the two tables. INSERT INTO T1 VALUES(1.1); INSERT INTO T2 VALUES(1.1); 3. Select from two tables and DB2 generates a transitive closure predicate. SELECT 1 FROM T1, T2 WHERE T1.C1 = T2.C1 AND T1.C1 = :HV1; DB2 generated transitive closure predicate: T2.C1 = :HV1 When a NULL value is sent in for :HV1, the above SELECT statement results in an ABEND0C7 failure. that behaves as follows: When the NULL value was sent in, DB2 failed to set the NULL value in the not null buffer in the transitive closure predicate, which causes the ABEND0C7 condition. 1 Please note that the same failure can occur when a typed or untyped parameter marker is used in the above predicates or when the transition variables are used in the same way in the predicates in a trigger package. DB2 was modified to handle the NULL value correctly for the transitive closure predicate described in the example. Additional keywords: SQLNULL SQLTRANSITIVE SQLPREDICATE SQLHOSTVAR SQLPARAMETERMARKER OFFSET3EB2 OFFSET59BC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76452 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM76452: See PM76452 APAR/PTF text for additional information about why a REBIND is necessary. PM76452 corrects a problem of ABEND0C7 RC0 at DSNXRDEC +59BC when a transitive closure predicate takes the form of column = host variable where the column is a not null decimal and a NULL value was sent in during execution time for the host variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMEX PM76452 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76452 DSNXOMEX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMEX LISTEND UK90447 COVER LETTER END UK90450 COVER LETTER START PROBLEM DESCRIPTION(S): PM73640 - **************************************************************** * USERS AFFECTED: All users of CPU or Sysplex Query * * Parallelism * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E at DSNVSRX . DSNVSRX with * 1 * RC00E501A1 , RC00E50048 , or RC00E50079 * * on the parent task at the parallelism * * coordinator subsystem when running cpu * * or sysplex query parallelism followed * * by DB2 ABNORMAL TERMINATION RC00E50054 * **************************************************************** * RECOMMENDATION: * **************************************************************** When a cpu or sysplex query parallelism parent task encounters an sql error, which may or may not originate from a child task, the position of the cursor becomes ambiguous and cannot correctly support further processing or row fetches. . Due to a code bug, DB2 cleaned up prallelism-related group structures and erased internal indicators of the sql error without closing the cursor. . Since the cursor was not closed, DB2 incorrectly allowed subsequent application fetches. These fetches caused DB2 to reference the group-related structures that had already been freed. . In at least one reported case, the group-related structures were already in use again by a second query parallel user. The result was that the structures became incorrectly shared between two concurrent threads. . The sharing of the group-related structures may result in ABEND04E with RC00E50048 or RC00E50079 or RC00E501A1 for the parent tasks of either of the two threads when suspending to synchronize the producer / consumer relationship between the child / parent tasks. . Other symptoms may be possible, such as incorrect output and tight-loop hangs (excessive CPU consumption) on the parent thread. DB2 may also terminate with RC00E50054. . These errors are caused because DB2 incorrectly allows applications to continue fetching or processing rows of parallel queries after sql errors occur for child tasks. . . DB2 code has been changed to drive an implicit CLOSE of any cursor whose query participates in either cpu or sysplex query parallelism that has encountered an sql error (negative sqlcode) condition from a child task. This implicit CLOSE action occurs on the OPEN or FETCH that first encounters the sql error from a child task. . As a result of this change, DB2 will now return SQLCODE -501 to applications that continue fetching rows after an sql error is encountered on a child task. This may require changes and modifications to application programs to expect this SQLCODE on FETCH requests. . Prior to this apar, it was possible for the application to 1 continue fetching without encountering the subject abends, although the data and error information returned to the applications may not have been correct. . There is no change to the existing logic for cursors that encounter an sql error condition from the parent task. DB2 code has been changed to drive an implicit CLOSE of any cursor whose query participates in either cpu or sysplex query parallelism that has encountered an sql error (negative sqlcode) condition from a child task. This implicit CLOSE action occurs on the OPEN or FETCH that first encounters the sql error from a child task. . As a result of this change, DB2 will now return SQLCODE -501 to applications that continue fetching rows after an sql error is encountered on a child task. This may require changes and modifications to application programs to expect this SQLCODE on FETCH requests. . Prior to this apar, it was possible for the application to continue fetching without encountering the subject abends, although the data and error information returned to the applications may not have been correct. . There is no change to the existing logic for cursors that encounter an sql error condition from the parent task. . . . Additional Keywords: DB2PARALL/K DB2OVRLAY/K DB2INCORR/K SQLCODE501 SQLCPUP SYSPLEX SQLSYSPLEXP SQLPARALLELISM COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73640 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: DB2 code has been changed to drive an implicit CLOSE of any cursor whose query participates in either cpu or sysplex query parallelism that has encountered an sql error (negative sqlcode) condition from a child task. This implicit CLOSE action occurs on the OPEN or FETCH that first encounters the sql error from a child task. . As a result of this change, DB2 will now return SQLCODE -501 to applications that continue fetching rows after an sql error is encountered on a child task. This may require changes and modifications to application programs to expect this SQLCODE on FETCH requests. . Prior to this apar, it was possible for the application to continue fetching without encountering the subject abends, although the data and error information returned to the applications may not have been correct. 1 . There is no change to the existing logic for cursors that encounter an sql error condition from the parent task. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEBR PM73640 DSNXEBR9 PM73640 DSNXECPT PM73640 DSNXERT PM73640 DSNXROJF PM73640 DSNXROJL PM73640 DSNXRSTP PM73640 DSNXRSTS PM73640 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73640 DSNXEBR DSNXEBR9 DSNXECPT DSNXERT DSNXROJF DSNXROJL DSNXRSTP DSNXRSTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEBR DSNXEBR9 DSNXECPT DSNXERT DSNXROJF DSNXROJL DSNXRSTP DSNXRSTS LISTEND UK90450 COVER LETTER END UK90516 COVER LETTER START PROBLEM DESCRIPTION(S): PM66212 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * who have interest in the euro-enabled SBCS * * EBCDIC CCSIDs for BALTIC, ESTONIA, and the * * UKRAINE. * **************************************************************** * PROBLEM DESCRIPTION: This apar provides DB2 support for the * * following new CCSIDs; * * CCSID 1156 (BALTIC, EBCDIC), * * CCSID 1157 (ESTONIA, EBCDIC), and * * CCSID 1158 (UKRAINE, EBCDIC). * **************************************************************** * RECOMMENDATION: * **************************************************************** This apar provides DB2 support for the following new EBCDIC CCSIDs; CCSID 1156 (BALTIC, EBCDIC), CCSID 1157 (ESTONIA, EBCDIC), and CCSID 1158 (UKRAINE, EBCDIC). This apar provides DB2 support for the following new EBCDIC CCSIDs; CCSID 1156 (BALTIC), CCSID 1157 (ESTONIA), and CCSID 1 1158 (UKRAINE). Additional Keywords: SQLCCSID COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66212 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: PM43179 corrects a problem of SQLCODE -171 during bind when using a file reference host variable of XML data type in an application prepared by the DB2 coprocessor. To make this fix effective for a static application, it must be recompiled after application of this PTF. If the application is a COBOL application, the following COBOL PTFs may also be required in addition to this PTF to fix the problem: UK71077 Enterprise COBOL for z/OS V3R4 H26L340 UK71078 Enterprise COBOL for z/OS V4R2 HADB420 UK71079 Enterprise COBOL for z/OS V4R1 HADB400 There is no problem applying the PTF for PM43179 without the COBOL PTF. However, the problem described in PM43179 will not be fixed for COBOL applications until the corresponding COBOL PTF is also applied. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHPSRV PM66212 DSNHSMUT PM66212 DSNTSTRT PM66212 DSNURELD PM66212 DSNXVEOA PM66212 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66212 DSNHPSRV DSNHSMUT DSNTSTRT DSNURELD DSNXVEOA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHPSRV DSNHSMUT DSNTSTRT DSNURELD DSNXVEOA LISTEND UK90516 COVER LETTER END UK90518 COVER LETTER START PROBLEM DESCRIPTION(S): PM74991 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users with queries containing * 1 * predicates on columns where frequency or * * histogram statistics have been collected. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may choose an inefficient access * * path when a user issues a query with a * * predicate or predicates that satisfy * * the conditions below: * * * * 1. The predicate refers to a column or * * columns where frequency or histogram * * statistics have been collected. * * 2. The predicate is a range predicate * * with parameter marker (or parameter * * markers) or host variable (or host * * variables) , or the predicate refers * * to a subquery (except an EQUAL or * * NOT EQUAL subquery). * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose an inefficient access path for a query with a predicate or predicates referencing a column where frequency or histogram statistics have been collected. The predicate or predicates are range predicates with parameter markers or host variables, or include subuqueries (except EQUAL or NOT EQUAL subqueries). The problems mentioned above are fixed so that DB2 will choose a more efficient access path in that situation. ADDITIONAL KEYWORDS: SQLACCESSPATH SQLPERFORMANCE SQLBETWEEN SQLSUBQUERY SQLPMK PARAMETERMARKER SQLPMARKER SQLHOSTVAR SQLLT SQLGT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74991 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74991: See PM74991 APAR/PTF text for additional information about why a REBIND is necessary. PM74991 corrects a problem of choosing a poorly performing access path for queries containing predicates on columns where frequency or histogram statistics have been collected. The predicate is a range predicate with parameter marker (or parameter markers) or host variable (or host variables), or the predicate refers to a subquery (except an EQUAL or NOT EQUAL subquery). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODFB PM74991 DSNXODFR PM74991 DSNXODFT PM74991 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74991 DSNXODFB DSNXODFR DSNXODFT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODFB DSNXODFR DSNXODFT LISTEND UK90518 COVER LETTER END UK90524 COVER LETTER START PROBLEM DESCRIPTION(S): PM71713 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users whose queries * * contain OR predicates and stage-2 * * predicates. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 optimizer may select an * * inefficient access path such as table * * space scan or non-matching index scan * * while a multi-index access is more * * efficient. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 optimizer may select an inefficient access path such as table space scan or non-matching index scan while a multi-index access path is more efficient. The problem may occur when the query contains an OR predicate and there is a stage-2 predicate under the OR predicate. For example, SELECT * FROM T1 WHERE (T1.C1 = ? AND ? BETWEEN T1.C2 AND T1.C3) OR (T1.C1 = ? AND ? BETWEEN T1.C2 AND T1.C3) OR (T1.C1 = ? AND ? BETWEEN T1.C2 AND T1.C3); There is an index defined on T1.C1. The multi-index access with the index could be efficient if the selectivity of the 1 predicate "T1.C1 = ?" is good. However, the cost of the multi-index access may be overestimated when there is a stage-2 predicate "? BETWEEN T1.C2 AND T1.C3" under the OR predicate. Consequently, the efficient multi-index access may not be chosen. Additional keywords: SQLACCESSPATH SQLPERFORMANCE MIDX SQLOR Code has been modified to correct the cost estimation of the multi-index access described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71713 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71713: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM71713 corrects a problem that the DB2 optimizer may select an inefficient access path while a multi-index access is more efficient. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGCM PM71713 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71713 DSNXOGCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGCM LISTEND UK90524 COVER LETTER END UK90533 COVER LETTER START PROBLEM DESCRIPTION(S): PM76751 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically users of DB2 stored procedures * * defined with COMMIT ON RETURN YES. * **************************************************************** * PROBLEM DESCRIPTION: The following symptoms may occur when a * * remote requester calls a stored * * procedure on DB2: * 1 * - On a DB2 9 for z/OS server. * * ABEND 04E-00D35011 * * LOC=DSNLZLLM.DSNLZSRD:0028 * * - On a DB2 10 for z/OS server. * * ABEND 04E-00D35011 * * LOC=DSNLZLLM.DSNLZSRM:001E * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote requester at Site 1 connects to a DB2 for z/OS server at Site 2, and calls a stored procedure that runs on Site 2. The stored procedure is defined with COMMIT ON RETURN YES. The stored procedure connects outbound to a DB2 for z/OS server at Site 3 and opens a remote result set cursor. The server thread at Site 3 is subsequently cancelled by DB2 at Site 3 when it exceeds the idle thread timeout threshold. The connection from Site 2 to Site 3 is terminated. When the stored procedure completes, DB2 at Site 2 initiates commit on return processing and fails because DB2 at Site 2 is unable to propagate the commit request to Site 3. After the commit on return failure, DB2 at Site 2 initiates abort processing, closing and freeing all result sets. DB2 at Site 2, in error, attempts to return the result sets which have already been freed, resulting in one of the reported abends. NOTE: This error can occur for any reason the server thread on Site 3 is cancelled, including the -CANCEL THREAD command. DB2 at Site 2 has been corrected to return an SQLCODE -901 and not attempt to return result sets following a commit on return failure. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76751 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXXSS PM76751 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76751 DSNLXXSS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXXSS LISTEND UK90533 COVER LETTER END UK90536 COVER LETTER START PROBLEM DESCRIPTION(S): PM77049 - **************************************************************** * USERS AFFECTED: All DDF users. * **************************************************************** 1 * PROBLEM DESCRIPTION: An ABEND0C4 in CSECT DSNVSDC0 may * * result in an SVC dump being taken * * during distributed transaction * * processing. * **************************************************************** * RECOMMENDATION: * **************************************************************** Distributed transaction dispatch logic may incorrectly request an SVC dump on an expected abend code path while analyzing the linkage stack. CSECT DSNVSDC0 will no longer request an SVC dump when an ABEND0C4 occurs while analyzing the linkage stack. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77049 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNVSDC0 PM77049 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77049 DSNVSDC0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNVSDC0 LISTEND UK90536 COVER LETTER END UK90550 COVER LETTER START PROBLEM DESCRIPTION(S): PM74674 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS WHO START THE DB2 DIRECTORY * * DATABASE IN UT MODE * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E400E1 RC00E200B8 ON * * REORG OF DSNDB06.SYSCOPY WHEN DB2 * * DIRECTORY DATABASE IS STARTED FOR * * UT ACCESS * **************************************************************** * RECOMMENDATION: * **************************************************************** User started the DB2 directory database for UT (utility) access only: -START DB(DSNDB01) ACCESS(UT) A REORG utility on DSNDB06.SYSCOPY was submitted. The job abended with MSGDSNT500I - REASON 00C200B8 TYPE 00000300 1 NAME DSNDB06 .SYSRTSTS.X'00000023' MSGDSNU017I - UTILITY DATA BASE SERVICE MEMORY EXECUTION ABENDED, REASON=X'00E400E1' CAUSE=X'00C200B8' because REORG directed a real time statistics (RTS) update to DSNDB06.SYSRTSTS, and when DB2 tried to log this update (which requires writing to DSNDB01.SYSLGRNX), it failed due to the UT status of the DB2 directory. The problem was this RTS update was not recognized as a utility-driven update, even though it was, and this caused the update to fail if the UT status on the directory was held at the database level. Code was added to utility SYSLGRNX services to ensure that code which properly identifies utility-driven updates was extended to cases where the entire directory database is started for UT access. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74674 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUAHR2 PM74674 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74674 DSNUAHR2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUAHR2 LISTEND UK90550 COVER LETTER END UK90561 COVER LETTER START PROBLEM DESCRIPTION(S): PM77470 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * LOBs (Large Objects). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC11 can occur at location * * DSNOCCSE +030A (OFFSET030A for DB2 9 * * for z/OS) when fetching LOBs using a * * held cursor. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC11 can occur at DSNOCCSE +030A (offset for DB2 9 for z/OS) when fetching LOBs using any cursor defined with the hold attribute. The abend occurs because DB2 failed to set an internal bit to 1 trigger the clean up process for a held cursor in the wake of LOB processing. The clean up activity is supposed to take place when the held cursor is closed. However, when the held cursor is closed, DB2 failed to remove an entry where some internal control blocks are kept on behalf of the held cursor. So, this makes the information kept in that entry obsolete and its location invalid. Subsequently, any reference to this information can cause an abend. The code in DB2 is modified to correct the conditions leading to the abend. Additional Keywords: SQLLOB SQLCURSOR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77470 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNODCRL PM77470 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77470 DSNODCRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNODCRL LISTEND UK90561 COVER LETTER END UK90599 COVER LETTER START PROBLEM DESCRIPTION(S): PM75060 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of * * utilities that offload to zIIP processors * **************************************************************** * PROBLEM DESCRIPTION: RUNSTATS always creates a new enclave * * to off-load to zIIP processors instead * * of executing in the current one if * * already executing in one. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When RUNSTATS can off-load to zIIP processors, it creates an enclave in which they will run. When already executing in an enclave, it needs to schedule into that enclave. While this was reported against RUNSTATS, any utility that will off-load to the zIIP processors can run into this and should continue processing in the current enclave in which it is running. 1 Utilities that off-load work into an enclave will now schedule into the enclave it is currently running in. If it is not, then a new enclave will be created for the off-load to run in. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75060 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURBXA PM75060 DSNURBXC PM75060 DSNURFBR PM75060 DSNURSCN PM75060 DSNUSDRC PM75060 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75060 DSNURBXA DSNURBXC DSNURFBR DSNURSCN DSNUSDRC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURBXA DSNURBXC DSNURFBR DSNURSCN DSNUSDRC LISTEND UK90599 COVER LETTER END UK90605 COVER LETTER START PROBLEM DESCRIPTION(S): PM75585 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * scrollable rowset cursor. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 from * * DSNIDM.DSNISNPG:5004 may be seen * * when fetching from a scrollable * * rowset cursor. * **************************************************************** * RECOMMENDATION: * **************************************************************** While fetching from a scrollable rowset cursor DB2 issued ABEND04E RC00C90101 DSNISNPG:5004 after geting 00C200E9 while trying to read a data page to the buffer pool. The reason for the abend because the read page error return code and reason code were not returned back to the calling routine. Hence the execution continue with incorrect information and caused the reported abend. DB2 code was changed to format and return the error return code and reason code back to the calling routine. 1 ADDITIONAL KEYWORDS: SQLROWSET SQLSCROLL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75585 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRPRV PM75585 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75585 DSNIRPRV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRPRV LISTEND UK90605 COVER LETTER END UK90618 COVER LETTER START PROBLEM DESCRIPTION(S): PM58915 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V9.1 and * * DB2 for z/OS V10 users of the * * IFCID flat file (DSNWMSGS). * **************************************************************** * PROBLEM DESCRIPTION: DSNWMSGS needs to be udpated to * * reflect changes since the * * last quarter of 2012. * **************************************************************** * RECOMMENDATION: * **************************************************************** Updates to the IFCID flat file (DSNWMSGS) since the last quarter of 2012 are needed for all supported DB2 for z/OS versions. This APAR delivers updates to the IFCID flat file (DSNWMSGS) for the following DB2 for z/OS versions: - DB2 for z/OS V9.1 - DB2 for z/OS V10 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58915 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWMSGS PM58915 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58915 DSNWMSGS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MACROS DSNWMSGS LISTEND UK90618 COVER LETTER END UK90676 COVER LETTER START PROBLEM DESCRIPTION(S): PM74815 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of LOAD * * DATA INCURSOR with LOB columns. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS878 RC10 during a LOAD DATA * * INCURSOR with a table having LOB * * columns. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** The Crossloader utility was used to load a table which contained LOB columns. The sum of the input column lengths for the defined cursor exceeded the documented limit of 1GB. However, instead of the LOAD failing with MSGDSNU1178I and RC8, an ABEND878 occurred. This was because LOAD was executing a code path that was specific to spanned records that should not have been executed. LOAD DATA INCURSOR code has been modified to properly check the length of columns and issue MSGDSNU1178 - SUM OF INPUT COLUMN LENGTHS FOR CURSOR cursorname IS TOO LARGE and fail with RC8. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74815 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUROFL PM74815 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74815 DSNUROFL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUROFL LISTEND UK90676 COVER LETTER END UK90679 COVER LETTER START PROBLEM DESCRIPTION(S): PM61099 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 users who use the row and * * column access control * **************************************************************** * PROBLEM DESCRIPTION: This APAR enhances the row and column * * access control for the following * * statements: * * * * 1. To truncate a row access control * * activated table, the authorization * * ID of the TRUNCATE statement must * * be the owner of the subject table, * * or must have one of the system * * authorities that are currently * * listed in the existing privilege * * set, with the exception of the * * SYSCTRL authority. * * * * 2. The insert or update operation * * in the INSERT, UPDATE, or MERGE * * statement to a table that is not * * activated for the column access * * control will no longer receive * * . SQLCODE -20478 reason code 30. * * * * SQLCODE -20478 reason code 30 * * is to ensure the source value * * of an insert or update operation * * is masked to the same value as * * the column value. * * * * 3. If DISTINCT is specified with * * an aggregate function, except * * MAX and MIN aggregate function, * * and the function argument * * references a column with an * * activated column mask, the * * query will receive SQLCODE * * -20478 reason code 26. * * * * 4. If a row permission or column * * mask references a user-defined * * function with the MODIFIES SQL * * DATA option, the CREATE * * PERMISSION or CREATE MASK * * statement will receive SQLCODE * * -20474 reason code 4. * **************************************************************** * RECOMMENDATION: * **************************************************************** PROBLEM SUMMARY: The following are examples to illustrate the behaviors before and after the enhancement item #1, #2, and #3 that are described in the PROBLEM DESCRIPTION section. 1 1. TRUNCATE statement In order to truncate a row access control activated table, the authorization ID of the TRUNCATE statement must be the owner of the subject table, or must have one of the system authorities that are currently listed in the existing privilege set, with the exception of the SYSCTRL authority. For example: A user with SYSADM authority does the following: CREATE TABLE T1 (C1 INT, C2 INT); COMMIT; INSERT INTO T1 VALUES (1,1); INSERT INTO T1 VALUES (1,1); INSERT INTO T1 VALUES (2,2); COMMIT; GRANT DELETE ON T1 TO USRT001; COMMIT; A user with SECADM authority does the following: ALTER TABLE SYSADM.T1 ACTIVATE ROW ACCESS CONTROL; COMMIT; Before the enhancement: USRT001 does the following: TRUNCATE TABLE SYSADM.T1 IGNORE DELETE TRIGGERS IMMEDIATE; ==> TRUNCATE successful After the enhancement: USRT001 does the same: TRUNCATE TABLE SYSADM.T1 IGNORE DELETE TRIGGERS IMMEDIATE; ==> TRUNCATE fails with SQLCODE -551 In order to let USRT001 truncate T1, the SYSADM user grants the system DBADM only authority to USRT001: GRANT DBADM WITHOUT DATAACCESS WITHOUT ACCESSCTRL TO USRT001; USRT001 now can truncate T1: TRUNCATE TABLE SYSADM.T1 IGNORE DELETE TRIGGERS IMMEDIATE; 1 ==> TRUNCATE successful All the rows in SYSADM.T1 will be truncated even though SYSADM.T1 has been activated for the row access control. 2. Insert or update operation in the INSERT, UPDATE, or MERGE statement When the source value of a new row references a column that has a mask, the masked value is used to derive the value for the new row. If the target table is also activated for the column access control, the authorization ID that issues the insert or update operation must be allowed by the source column mask to mask the source column value to itself (in other words, the authorization ID must be allowed by the source column mask to see the column value in order to retrieve it for the insert or update operation). If the source column mask does not allow the authorization ID to mask the column value to itself, an error will be returned at run time (SQLCODE -20478 reason code 30). SQLCODE -20478 reason code 30 is to ensure the source value of an insert or update operation is masked to the same value as the column value. For example: A user with SYSADM authority does the following: CREATE TABLE T1 (C1 INT, C2 INT); COMMIT; INSERT INTO T1 VALUES (1,1); INSERT INTO T1 VALUES (1,1); INSERT INTO T1 VALUES (2,2); CREATE TABLE T2 (C1 INT, C2 INT); A user with SECADM authority does the following: CREATE MASK T1C1_MASK ON SYSADM.T1 FOR COLUMN C1 RETURN CASE WHEN(SESSION_USER = 'PAUL') THEN C1 ELSE C1-10 END ENABLE; COMMIT; ALTER TABLE SYSADM.T1 ACTIVATE COLUMN ACCESS CONTROL; COMMIT; A user with SYSADM authority does the following: GRANT SELECT ON T1 TO PAUL; 1 GRANT INSERT ON T2 TO PAUL; GRANT SELECT ON T1 TO MARY; GRANT INSERT ON T2 TO MARY; Before the enhancement: PAUL does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT succeeds because when column mask T1C1_MASK is applied to column T1.C1 in the subselect, T1C1_MASK masks column T1.C1 to itself for Paul. MARY does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT fails with SQLCODE -20478 reason code 30 because when column mask T1C1_MASK is applied to column T1.C1 in the subselect, T1C1_MASK masks column T1.C1 to expression C1-10 for Mary. After the enhancement: PAUL does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT succeeds because SYSADM.T2 is not activated for the column access control. MARY does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT succeeds because SYSADM.T2 is not activated for the column access control. A user with SECADM authority does the following: ALTER TABLE SYSADM.T2 ACTIVATE COLUMN ACCESS CONTROL; COMMIT; PAUL does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT succeeds because even though SYSADM.T2 is activated for the column access control, 1 when column mask T1C1_MASK is applied to column in the subselect, T1C1_MASK masks column T1.C1 to itself for Paul. MARY does the following: INSERT INTO SYSADM.T2 SELECT * FROM SYSADM.T1; COMMIT; ==> INSERT fails with SQLCODE -20478 reason code 30 because SYSADM.T2 is activated for the column access control and when column mask T1C1_MASK is applied to column T1.C1 in the subselect, T1C1_MASK masks column T1.C1 to expression C1-10 for Mary. 3. Aggregate function with the DISTINCT keyword Before the enhancement: USRT001 does the following: SELECT SUM(DISTINCT C1) FROM SYSADM.T1; ==> SELECT succeeds with one row of value 10 being returned. After the enhancement: SELECT SUM(DISTINCT C1) FROM SYSADM.T1; ==> SELECT fails with SQLCODE -20478 reason code 26 because the argument of an aggregate DISTINCT function must not reference a column with an activated column mask. The rules of the row and column access control has been enhanced for the following statements: 1. TRUNCATE statement To truncate a row access control activated table, the authorization ID of the TRUNCATE statement must be the owner of the subject table, or must have one of the system authorities that are currently listed in the existing privilege set, with the exception of the SYSCTRL authority: In addition, if the row access control is activated for a table, the privilege set must include at least one of the following privileges (SQLCODE -551): . Ownership of the table . DBADM authority for the database . SYSADM authority . System DBADM 1 If the authorization ID of the statement has the required privilege, all rows in the table will be truncated even though the table is activated for the row access control. See an example in the PROBLEM SUMMARY section. 2. Insert or update operation in the INSERT, UPDATE, or MERGE statement When the source value of a new row references a column that has a mask, the masked value is used to derive the value for the new row. If the target table is also activated for the column access control, the authorization ID that issues the insert or update operation must be allowed by the source column mask to mask the source column value to itself (in other words, the authorization ID must be allowed by the source column mask to see the column value in order to retrieve it for the insert or update operation). If the source column mask does not allow the authorization ID to mask the column value to itself, an error will be returned at run time (SQLCODE -20478 reason code 30). See an example in the PROBLEM SUMMARY section. 3. Aggregate function with the DISTINCT keyword If DISTINCT is specified in an aggregate function, with the exception of the MAX and MIN aggregate function, the argument of the function must not reference a column with a column mask (SQLCODE -20478 reason code 26). See an example in the PROBLEM SUMMARY section. 4. User-defined function with the MODIFIES SQL DATA option Such a UDF must not be referenced in a row permission or column mask definition (SQLCODE -20474 reason code 4). Additional keywords: SQLACCESS SQLCONTROL SQLPERMISSION SQLMASK SQLTRUNCATE SQLINSERT SQLUPDATE SQLDISTINCT SQLAGGREGATE SQLMODIFIES SQLUDF SQLCODE20474 SQLCODE20478 SQLMERGE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61099 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM61099: See PM61099 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM61099 enhances the row and column access control rules and the following are the affected statements: 1. TRUNCATE statement To truncate a row access control activated table, the authorization ID of the TRUNCATE statement must be the owner of the subject table, or must have one of the system authorities that are currently listed in the existing privilege set, with the exception of the SYSCTRL authority: In addition, if the row access control is activated for a table, the privilege set must include at least one of the following privileges (SQLCODE -551): . Ownership of the table . DBADM authority for the database . SYSADM authority . System DBADM If the authorization ID of the statement has the required privilege, all rows in the table will be truncated even though the table is activated for the row access control. See an example in the PROBLEM SUMMARY section. 2. Insert or update operation in the INSERT, UPDATE, or MERGE statement When the source value of a new row references a column that has a mask, the masked value is used to derive the value for the new row. If the target table is also activated for the column access control, the authorization ID that issues the insert or update operation must be allowed by the source column mask to mask the source column value to itself (in other words, the authorization ID must be allowed by the source column mask to see the column value in order to retrieve it for the insert or update operation). If the source column mask does not allow the authorization ID to mask the column value to itself, an error will be returned at run time (SQLCODE -20478 reason code 30). SQLCODE -20478 reason code 30 is to ensure the source value of an insert or update operation is masked to the same value as the column value. See an example in the PROBLEM SUMMARY section. 3. Aggregate function with the DISTINCT keyword If DISTINCT is specified in an aggregate function, with the exception of the MAX and MIN aggregate function, the argument of the function must not reference a columnh 1 with a column mask (SQLCODE -20478 reason code 26). See an example in the PROBLEM SUMMARY section. 4. User-defined function with the MODIFIES SQL DATA option Such a UDF must not be referenced in a row permission or column mask definition (SQLCODE -20474 reason code 4). To determine which table or column has the row or column access control, use SYSIBM.SYSTABLES.CONTROL column to identify which type of the access control has been activated for the table, and the SYSIBM.SYSCOLUMNS.CONTROL_ID column to determine which column mask is in effect, then use SYSIBM.SYSDEPENDENCIES to determine whether additional objects are affected. For the static applications, to determine which package is affected, search the SYSIBM.SYSPACKDEP on those affected objects. To make this fix effective for a static application, it must be rebound after application of this PTF. Use the above suggested ways of querying the catalog tables to determine which, if any, applications could be affected by this change. ACTION: This PTF introduces the following enhancements to the row and column access control and the following statements are affected: 1. TRUNCATE statement To truncate a row access control activated table, the authorization ID of the TRUNCATE statement must be the owner of the subject table, or must have one of the system authorities that are currently listed in the existing privilege set, with the exception of the SYSCTRL authority: In addition, if the row access control is activated for a table, the privilege set must include at least one of the following privileges (SQLCODE -551): . Ownership of the table . DBADM authority for the database . SYSADM authority . System DBADM If the authorization ID of the statement has the required privilege, all rows in the table will be truncated even though the table is activated for the row access control. See an example in the PROBLEM SUMMARY section. 2. Insert or update operation in the INSERT, UPDATE, or MERGE statement 1 When the source value of a new row references a column that has a mask, the masked value is used to derive the value for the new row. If the target table is also activated for the column access control, the authorization ID that issues the insert or update operation must be allowed by the source column mask to mask the source column value to itself (in other words, the authorization ID must be allowed by the source column mask to see the column value in order to retrieve it for the insert or update operation). If the source column mask does not allow the authorization ID to mask the column value to itself, an error will be returned at run time (SQLCODE -20478 reason code 30). SQLCODE -20478 reason code 30 is to ensure the source value of an insert or update operation is masked to the same value as the column value. See an example in the PROBLEM SUMMARY section. 3. Aggregate function with the DISTINCT keyword If DISTINCT is specified in an aggregate function, with the exception of the MAX and MIN aggregate function, the argument of the function must not reference a column with a column mask (SQLCODE -20478 reason code 26). See an example in the PROBLEM SUMMARY section. 4. User-defined function with the MODIFIES SQL DATA option Such a UDF must not be referenced in a row permission or column mask definition (SQLCODE -20474 reason code 4). To determine which table or column has the row or column access control, use SYSIBM.SYSTABLES.CONTROL column to identify which type of the access control has been activated for the table, and the SYSIBM.SYSCOLUMNS.CONTROL_ID column to determine which column mask is in effect, then use SYSIBM.SYSDEPENDENCIES to determine whether additional objects are affected. For the static applications, to determine which package is affected, search the SYSIBM.SYSPACKDEP on those affected objects. If a row permission or column mask references a user-defined function with the MODIFIES SQL DATA option, the row permission or column mask must be dropped and recreated with the proper modification. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXA02 PM61099 DSNXA2TM PM61099 DSNXOACA PM61099 1 DSNXOACM PM61099 DSNXODML PM61099 DSNXOFN3 PM61099 DSNXOOS1 PM61099 DSNXOTL PM61099 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61099 DSNXA02 DSNXA2TM DSNXOACA DSNXOACM DSNXODML DSNXOFN3 DSNXOOS1 DSNXOTL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXA02 DSNXA2TM DSNXOACA DSNXOACM DSNXODML DSNXOFN3 DSNXOOS1 DSNXOTL LISTEND UK90679 COVER LETTER END UK90691 COVER LETTER START PROBLEM DESCRIPTION(S): PM73819 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * * of outer join and views * **************************************************************** * PROBLEM DESCRIPTION: ABEND 04E RC00E70005 in DSNXOADJ:M444 * * occurs for an SQL statement referencing * * a view that satisfies the following * * conditions: * * 1. Was created before version 7 and * * without apar PQ32357. * * 2. Contains AS name * * 3. Is materialized and contains outer * * join. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND 04E RC00E70005 in DSNXOADJ:M444 occurs for SQL statement that satisfy the following conditions: 1. Reference views that were created before version 7 and without apar PQ32357. 2. Views contains AS name. 3. Views are materialized and used outer join. The abend occurs because DB2 did not handle the AS name of work file's column correctly. DB2 was fixed to handle the AS name of the work file columns in the view correctly. 1 Additional Keywords: SLQVIEW SQLOUTERJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73819 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOV0 PM73819 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73819 DSNXOV0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOV0 LISTEND UK90691 COVER LETTER END UK90705 COVER LETTER START PROBLEM DESCRIPTION(S): PM74888 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS utilizing * * zIIP processors. * **************************************************************** * PROBLEM DESCRIPTION: Value QWACZIIP_ELIGIBLE in an * * IFCID accounting record can be * * incorrect. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an agent executes a utility, a call to record the stop of accounting time executing that utility will not correctly obtain the zIIP time of the CPU. This incorrect value will then be used in a calculation of QWACZIIP_ELIGIBLE for the subsequent accounting record, resulting in incorrect values for QWACZIIP_ELIGIBLE field. This error could appear in any of these records: IFCID3, IFCID148 and IFCID369 Correctly gather zIIP time information for agents executing utilities. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74888 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQW05 PM74888 1 DSNLTMSC PM74888 DSNTXSTB PM74888 DSNWVSR1 PM74888 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74888 DSNDQW05 DSNLTMSC DSNTXSTB DSNWVSR1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTMSC DSNTXSTB DSNWVSR1 MACROS DSNDQW05 LISTEND UK90705 COVER LETTER END UK90706 COVER LETTER START PROBLEM DESCRIPTION(S): PM79027 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those with remote Java * * applications using Type 2 connectivity * * connecting to a DB2 for z/OS * * server during its migration process. * **************************************************************** * PROBLEM DESCRIPTION: During DB2 for z/OS migration, a * * DSNL032I DRDA exception message, with * * reason code 00D35B16 and error ID * * DSNLZSDT002C, may occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote Java application uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to connect to a DB2 for z/OS server. The connection environment between the remote client and the DB2 for z/OS server is negotiated with a DRDA SQL Application Manager (SQLAM) level of 7 or lower. After the connection is established (at the SQLAM<8 level), the DB2 for z/OS subsystem is migrated such that the remote client driver will now be aware of a DB2 for z/OS product identifier that reflects a higher version or modification level. The Java application then executes an SQL statement with input parameters. The Java client driver, judging from the updated (now higher) DB2 for z/OS product identifier, incorrectly associates the input parameters with a DECFLOAT data type even though the connection's negotiated SQLAM level did not reflect this capability. When the DB2 for z/OS server receives the request, a DRDA exception is detected and message DSNL032I is issued. The remote application SQL statement will therefore fail. 1 The Java client driver is in error because it is incorrectly making a judgment based on the DB2 for z/OS product ID rather than the negotiated SQLAM manager level of the connection, and a fix is available in V9.7 Fp3a and above. Generally, users are advised to upgrade the client driver to the appropriate level to resolve the issue. However, in some cases it may not be practical for users to upgrade all of their clients before their planned migration to DB2 for z/OS New Function Mode. Thus, for the benefit of user migration plans, a DB2 for z/OS server fix may be appropriate in an effort to tolerate the client system error. DB2 for z/OS server processing has been changed to tolerate and support SQL statements with a DECFLOAT data type as input parameters from a remote Java application for connection environments that are negotiated at SQLAM 7 or lower. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79027 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZSDT PM79027 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79027 DSNLZSDT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZSDT LISTEND UK90706 COVER LETTER END UK90730 COVER LETTER START PROBLEM DESCRIPTION(S): PM78362 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and DB2 * * 10 for z/OS users of the LOAD utility with * * partition parallelism * **************************************************************** * PROBLEM DESCRIPTION: Message DSNU255I followed by an * * ABEND04E RC00E4030A during a LOAD * * utility with partition parallelism * **************************************************************** * RECOMMENDATION: * **************************************************************** A LOAD DATA with multiple INTO TABLE PART x INDDN statements issued MSGDSNU255I - KEY COUNT INCONSISTENT FOR BUILD PHASE, NUMBER OF KEYS EXPECTED =nnn, NUMBER OF KEYS PROCESSED=nn, and abended with an ABEND04E RC00E4030A. However, the number of keys processed was correct, but the 1 counts used in this consistency check were incorrect. The same LOAD job ran successfully after a -TERM UTIL command. The problem happened because the key count of the subtask was not initialized properly. The LOAD partition parallelism code has been modified to correct the reported problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78362 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURPLD PM78362 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78362 DSNURPLD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURPLD LISTEND UK90730 COVER LETTER END UK90749 COVER LETTER START PROBLEM DESCRIPTION(S): PM75596 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those where DB2 is configured * * with (DSNTIPR) DDF THREADS INACTIVE * * (DSN6FAC CMTSTAT=INACTIVE). * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: The following intermittent symptoms * * are reported: * * . Abend 04E-00D30014 DSNLTHOP:0130. * * This may be followed by a secondary * * abend 04E-00D35011 DSNLZRPA:001E or * * abend 04E-00D3111C DSNLIRTR:000A. * * . Abend 04E-00D35011 DSNLZR00:0066. * * This may be followed by a secondary * * abend 04E-00D35011 DSNLZRPA:001E. * * . Abend 04E-00D35011 DSNLZRPA:001E. * * This may also be observed as a * * secondary abend during deallocation * * processing in which case DB2 will * * likely terminate with message * * DSNV086E REASON=00E50702. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 A remote application (at site1) accesses a DB2 10 for z/OS server (site2) and calls a Stored Procedure. The Stored Procedure executes an explicit SQL CONNECT to yet another remote system (site3) but the stored procedure neglects to send any (non Set related) SQL following the CONNECT. This results in outbound (connect related) DRDA requests that remain pending to be sent to site3 (and will be sent once SQL is finally executed). DB2 10 for z/OS supports a concept known as a "High Performance DBAT" which allows a RELEASE(DEALLOCATE) package bind option to be honored by DB2 DBATs (server threads), hence improving their performance. A High Performance DBAT is not pooled by DB2 (DDF) Inactive Thread support, and thus the connection environment remains actively associated to the DBAT in order to achieve additional performance benefit. However, in an effort to reduce contention with other work, due to the allocation duration resources that the DBAT may accumulate, at some point the connection environment will be inactivated anyway so the DBAT itself can be terminated and hence release its allocation duration resources. A High Performance DBAT termination condition was detected while the connection environment still had its outbound (connect related) DRDA requests that were pending to be sent to site3. DB2 (DDF) Inactive Thread support incorrectly allows the connection environment to be inactivated even though the pending requests are actually dependent on the specific DBAT that's being terminated. This may lead to unpredictable symptoms including the reported symptoms. DB2 10 for z/OS has been changed to prevent inactivation of a connection, and termination of the associated High Performance DBAT, when there are outbound DRDA requests pending to be processed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75596 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLQCTL PM75596 DSNLQDIS PM75596 DSNLTCCN PM75596 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75596 DSNLQCTL DSNLQDIS DSNLTCCN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLQCTL DSNLQDIS DSNLTCCN LISTEND UK90749 COVER LETTER END 1 UK90752 COVER LETTER START PROBLEM DESCRIPTION(S): PM72563 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users in DATASHARING SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: After the lock structure rebuild, the * * number of Record List Entries (RLE) * * were less than before the rebuild * * started. If the RLEs were in-use * * before the rebuild then the rebuild * * failed because IXLLOCK returned with * * reason code 0C0B (=IxlRsnCodeRTFull). * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Without specifying LTE= in the IRLMPROC, IRLM needs to calculate the number of Lock Table Entries (LTE) before connecting to the lock structure and connecting to the rebuild lock structure. After changing the CFRM policy or initiating a structure alter, the lock structure rebuild may fail because number of LTE increases leaving less space for the Record List Entry (RLE). GEN: KEYWORDS: *** END IMS KEYWORDS *** In the Rebuild Connect logic, the number of Lock Table Entries (LTE) is calculated such that it will not reduce the number of Record List Entries (RLE) after the rebuild. After the lock structure's size increase by a structure ALTER command, the number of LTE stays the same. All the additional storage is contributed to the RLE. If a structure REBUILD is started after a structure ALTER, the number of LTE may increase to the next power of 2. This only happens if the additional size, comparing with the previous structure allocation (original connect allocation or rebuild connect allocation), can cover the storage required to advance the number of LTE to next power of 2 without reducing the number of RLE. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM72563 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL712 PM72563 DXRRL751 PM72563 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72563 DXRRL712 DXRRL751 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL712 DXRRL751 LISTEND UK90752 COVER LETTER END UK90753 COVER LETTER START PROBLEM DESCRIPTION(S): PM79312 - **************************************************************** * USERS AFFECTED: All users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: Not all active log read suspend time * * is included in the IFCID3 class 3 * * accounting field QWAXAWAR. * **************************************************************** * RECOMMENDATION: * **************************************************************** Not all active log read suspend time, determined by the IFCID 34 and 35 trace records, is included in the IFCID3 class 3 accounting field QWAXAWAR. DSNJR007 has been changed to include the active log read suspend time, from the IFCID 34 and 35 trace records, in IFCID3 class 3 accounting time. Also, DSNWALRS has been changed to obtain control block storage from a global storage pool instead of using GETMAIN/FREEMAIN. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79312 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJR007 PM79312 DSNWALRS PM79312 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79312 DSNJR007 DSNWALRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJR007 DSNWALRS LISTEND UK90753 COVER LETTER END 1UK90757 COVER LETTER START PROBLEM DESCRIPTION(S): PM78213 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of SQL statements * * that reference the TIMESTAMPDIFF built-in * * function. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C7 RC0 can occur at location * * DSNXRINT +2304 or OFFSET2304 when * * executing the DSNTIAUL program with an * * SQL statement that contains the * * TIMESTAMPDIFF built-in function. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C7 RC0 can occur at location DSNXRINT +2304 or OFFSET2304 when executing an SQL statement that contains the TIMESTAMPDIFF built-in function. The problem was reported when executing the DSNTIAUL program with an SQL statement that contains the TIMESTAMPDIFF built-in function, but the problem can also occur otherwise. The following example illustrates a failing case. Step 1. Create Table T1. CREATE TABLE T1 (C1 TIMESTAMP NOT NULL); Step 2. Insert a row into Table T1. INSERT INTO T1 VALUES(CURRENT TIMESTAMP) ; Step 3. Execute the following query. SELECT TIMESTAMPDIFF(16,DIGITS(TIMESTAMP(CURRENT TIMESTAMP) - TIMESTAMP(C1))) FROM T1 ; Step 4. Note the result. An SQLCODE171 or SQLCODE -171 is issued from DSNXRINT. Step 5. Execute the following query from within the DSNTIAUL program. SELECT TIMESTAMPDIFF(16,DIGITS(TIMESTAMP(CURRENT TIMESTAMP) - TIMESTAMP(C1))) 1 FROM T1 ; Step 6. Note the result. An ABEND0C7 RC0 occurs from location DSNXRINT +2304. Instead, an SQLCODE -171 issued from DSNXRINT is expected as in Step 4 above. The TIMESTAMPDIFF routine code in DB2 has been modified to correct the conditions leading to the abend when executing a query that references it (from DSNTIAUL or otherwise). Additional Keywords: SQLCODE171 SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78213 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRINT PM78213 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78213 DSNXRINT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRINT LISTEND UK90757 COVER LETTER END UK90758 COVER LETTER START PROBLEM DESCRIPTION(S): PM74968 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REPAIR SET TABLESPACE NOAUXWARN * * with XML columns. * **************************************************************** * PROBLEM DESCRIPTION: A REPAIR OBJECT SET TABLESPACE * * NOAUXWARN which included a base table * * with XML columns failed with * * MSGDSNU076I and ended with RC8. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User ran a REPAIR OBJECT SET TABLESPACE tsname NOAUXWARN on a tablespace which included a base table with XML columns. The REPAIR issued DSNU076I - KEYWORD=NOAUXWARN INVALID FOR BASE TABLE SPACE WITHOUT LOB COLUMNS OR XML TABLE SPACE=tsname and ended with RC8. The REPAIR utility should not be prevented 1 from running against XML table spaces. Additional Keywords: XMLALL Code has been modified to allow the REPAIR utility to execute in the aforementioned case. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74968 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCBRS PM74968 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74968 DSNUCBRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBRS LISTEND UK90758 COVER LETTER END UK90762 COVER LETTER START PROBLEM DESCRIPTION(S): PM74654 - **************************************************************** * USERS AFFECTED: DB2 10 users of external stored procedures * * and user-defined functions (UDFs) of * * PROGRAM TYPE SUB. * **************************************************************** * PROBLEM DESCRIPTION: After an execution of a stored * * procedure or UDF, the Unix System * * Services (USS) process associated with * * the MVS task, if any, is undubbed. * * On some scenarios, it is desireable to * * keep the USS process across executions * * on the the MVS task. * **************************************************************** * RECOMMENDATION: * **************************************************************** USS process associated with the stored procedure or UDF task is undubbed after each execution. There is no option to keep the process for subsequents execution. This means that for each stored procedure or UDF execution that issues a USS system call, a new USS process is initialized There are use cases, such as for performance reason, where this is not wanted. A new option configurable through a Dummy DD statement is provided to control whether the USS process associated with the stored procedure or UDF task is undubbed after execution. Adding the following DD statement to the WLM startup JCL will indicate that in this WLM environment, if there is a USS 1 process dubbed to a PROGRAM TYPE SUB stored procedure or UDF task, the process will not be undubbed at the end of execution: //NOUNDUB DD DUMMY The existing process will be available for use by the next stored procedure and UDF executing on that task. This option must be used with extreme caution since without undubbing, all uSS resources on the process (file descriptors, etc) are not cleaned. the procedure or UDF program must make that it properly cleaned up those resources because the next stored procedure or UDF executiong on that task will use the same process. For more information regarding dub and undub, please see z/OS UNIX System Services manuals and books such as: 'z/OS UNIX System Services Programming: Assembler Callable Services Reference' and 'UNIX System Services z/OS Version 1 Release 7 Implementation'. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74654 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: To enable the new functionality, add the following DD statement to the WLM startup JCL: //NOUNDUB DD DUMMY This indicates that in this WLM environment, if there is a USS process dubbed to a PROGRAM TYPE SUB stored procedure or UDF task, the process will not be undubbed at the end of the routine's execution. Use caution when enabling this option. This option affects all routine executions in the WLM environment. This option should only enabled for routines where there is conscious intent to keep USS processes across routine executions. The clean up of USS resources of the process such as file handles, pipes, sockets, etc. must be handled correctly by the routine. Please also note that any subsequent execution on the MVS task can be from any of the routines queued for that WLM environment. Therefore use of this option should be isolated from WLM environments where routines run that have not been verified to clean up resources appropriately. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9WLM PM74654 DSNX9WLS PM74654 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74654 DSNX9WLM DSNX9WLS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9WLM DSNX9WLS 1 LISTEND UK90762 COVER LETTER END UK90769 COVER LETTER START PROBLEM DESCRIPTION(S): PM76851 - **************************************************************** * USERS AFFECTED: DB2 users that format log records. * **************************************************************** * PROBLEM DESCRIPTION: Missing procedure name in some cases * * for the ending dummy CLR log records. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may write out dummy compensating log records to disallow rollback of necessary system changes. Although the issuing procedure name is present on the begin dummy CLR, it is missing from the end dummy CLR log record. For improved serviceability DB2 will now provide the procedure name on the end dummy CLR log records. DB2 code has been corrected to address this problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76851 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIFOD PM76851 DSNISEGF PM76851 DSNIVOBD PM76851 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76851 DSNIFOD DSNISEGF DSNIVOBD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIFOD DSNISEGF DSNIVOBD LISTEND UK90769 COVER LETTER END UK90798 COVER LETTER START PROBLEM DESCRIPTION(S): PM76120 - **************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: ABEND 04E RC00C90101 on DSNILKDR when * * turbo drain fails in V10 compatible * 1 * mode * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 V10 compatible mode, the turbo drain logic (drain part 0 to drain all partitions in a partitioned page set) needs to drain individual partitions and notify other members. The drain of individual partitions may fail due to drain lock failure. The notify logic can fail when other members, in DB2 V9 or V8, have claimers on the partitions. When either failure happens, the turbo drain logic needs to unlock any drain locks already acquired before the failure. However, the unlock logic may unlock incorrect drain locks or may miss unlocking some of them. This leads to abends in DSNILKDR. The unlock logic during turbo drain has been modified to correctly unlock any drain locks, which should be unlocked. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76120 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1DRA PM76120 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76120 DSNB1DRA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DRA LISTEND UK90798 COVER LETTER END UK90803 COVER LETTER START PROBLEM DESCRIPTION(S): PM74746 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * queries that reference a view which contains * * a SUM function and UNION ALL. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C6 can occur at location * * DSNXGRDS.DSNXVCDF+27B (OFFSET27B) or at * * +27D (OFFSET27D) or an incorrect result * * can be returned for a query that * * satisfies the following conditions: * * * * 1. The query references a VIEW which * * contains a SUM function and UNION * * ALL. * * * 1 * 2. The input to the SUM function is * * an expression. * * * * 3. The expression contains columns * * with a DECIMAL data type and the * * the expression's result data type * * is FLOAT or DECIMAL FLOAT. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C6 can occur at location DSNXVCDF +27B (or at offset +27D) or an incorrect result can be returned from a query that satisfies the following conditions: 1. The query references a VIEW which contains a SUM function and a UNION ALL. 2. The input to the SUM function is an expression. 3. The expression contains columns with a DECIMAL data type and the expression's result data type is FLOAT. The following example helps to illustrate such a failing case. Step 1. Create a Table T1. CREATE TABLE T1 (COL_DEC DECIMAL (9,3)); Step 2. Create a View V1 on T1 that contains a SUM function and UNION ALL. CREATE VIEW V1 AS SELECT SUM(1E0*(NEWCOL - 1)) AS MY_RESULT FROM (SELECT (A.COL_DEC) AS NEWCOL FROM T1 A UNION ALL SELECT 0* 1E0 AS NEWCOL FROM T2 B) AS T; Step 3. Select from the VIEW V1. SELECT * FROM V1; Step 4. Check the results. The result of this query can be an ABEND0C6 in DSNXVCDF as mentioned before or an incorrect result can be returned for statements that reference this view because DB2 did not handle the expression SUM(1E0*(NEWCOL - 1)) properly. The code in DB2 is modified to process the decimal column inside the SUM function with UNION ALL properly. 1 Additional Keywords: SQLUNIONALL SQLVIEW SQLSETFUNCTION SQLSUM SQLINCORR INCORROUT SQLINCORROUT SQLDECIMAL DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74746 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74746: See PM74746 APAR/PTF text for additional information about why a REBIND is necessary. PM74746 corrects a bind time problem that can result in an ABEND0C6-6 at location DSNXVCDF+27B or +27D for a query referencing a large complex view that has a UNION ALL and decimal arithmetic. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. ACTION: Please note that the following action will need to be performed along with applying the ptf for this apar. Any nested views that are created with the symptoms mentioned in the apar description will need to be dropped and recreated. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOP1 PM74746 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74746 DSNXOP1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOP1 LISTEND UK90803 COVER LETTER END UK90805 COVER LETTER START PROBLEM DESCRIPTION(S): PM75843 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * contain FULL OUTER JOIN and reference to * * a timestamp column. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -338 may be issued incorrectly * 1 * for an SQL statement that satisfies the * * following conditions: * * 1. The statement contains a FULL * * OUTER JOIN. * * 2. The ON clause contains a timestamp * * column which is compared with a * * varchar column. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -338 may be issued incorrectly for an SQL statement that satisfies the following conditions: 1. The statement contains a FULL OUTER JOIN. 2. The ON clause contains a timestamp column which is compared with a varchar column. For Example, CREATE TABLE TB1(COL1 TIMESTAMP (12) NOT NULL); CREATE TABLE TB2(COL1 VARCHAR(32)); SELECT * FROM TB1 FULL JOIN TB2 ON TB1.COL1 = TB2.COL1; SQLCODE -338 may be incorrectly issued for the SELECT statement above. DB2 was fixed to remove the SQLCODE for an SQL statement that contains a FULL OUTER JOIN and the ON clause comparing a timestamp column with a varchar column. Additional Keywords: SQLFULLJOIN SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75843 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOB2 PM75843 DSNXORCM PM75843 DSNXOW1 PM75843 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75843 DSNXOB2 DSNXORCM DSNXOW1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOB2 DSNXORCM DSNXOW1 LISTEND UK90805 COVER LETTER END 1UK90809 COVER LETTER START PROBLEM DESCRIPTION(S): PM73636 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who * * are also using IBM DB2 Analytics * * Accelerator * **************************************************************** * PROBLEM DESCRIPTION: This APAR contains the following fixes * * for DB2 IDAA support: * * (1) Correct a problem where a query was * * allowed to offload for a NOT IN * * subquery. * * * * (2) Add a new QUERY_ACCEL_OPTIONS * * value of 99. The new option, 99, * * is for serviceability only and you * * should not use it except when advised * * to do so by IBM service. * **************************************************************** * RECOMMENDATION: * **************************************************************** (1) Before this APAR, we allowed offload for a NOT IN subquery in certain scenarios. This could cause incorrect output for an offloaded query. The offload can occur when one or more NOT IN subqueries is under an OR predicate. For example the following SQL would be offloaded: SELECT C1 FROM T1 WHERE T1.C2> 0 OR T1.C3 NOT IN (SELECT C3 FROM T2 WHERE T2.C1>0); (2) Add a new value of 99 for subsystem parameter QUERY_ACCEL_OPTIONS. The new option, 99, is for serviceability only and you should not use it except when advised to do so by IBM service. (1) Code is fixed to properly block offload of a NOT IN subquery (2) The new option of 99 is added to QUERY_ACCEL_OPTIONS. The value 99 is for serviceability only and you should not use it except when advised to do so by IBM service. Additional Search Keywords: IDAAV2R1/K SQLNOTIN SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K IDAAV3R1/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73636 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM73636 (V10) 1 This PTF also adds a new option, 99, to an existing DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used to specify additional types of SQL queries to be included in query offloading. It previously had these four options: * NONE: Query offloading is restricted to the standard SQL statements ==> This is the default setting. * 1 : The queries that include data encoded by multi-byte character set EBCDIC encoding scheme are not blocked from executing on IDAA. See APAR PM60170 for more information about this option. * 2 : For INSERT statements where a fullselect specifies the data to be inserted, the fullselect part is not blocked from executing on IDAA although the data operated on by the fullselect may not be current in IDAA. The fullselect will be considered for offload as if it were a stand-alone statement, except that DB2 will not offload the fullselect if the target table of the INSERT has a different encoding scheme than any tables referenced in the fullselect. * 3 : The queries that include DB2 byte-based string functions on data encoded by multi-byte character sets encoding schemes (like Unicode) are not blocked from executing on IDAA although IDAA supports only character-based string functions. If the data on which the string function is specified contains only single-byte characters, executing the function on IDAA will return the same result as executing the function on DB2 irrespective of what encoding scheme is used for the data. However, if the data contains multi-byte characters, the results will not be the same. The new option, 99, is for serviceability only and you should not use it except when advised to do so by IBM service. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is mutually exclusive from all other settings. The other options can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=3 QUERY_ACCEL_OPTIONS=(1,2) QUERY_ACCEL_OPTIONS=(1,3) QUERY_ACCEL_OPTIONS=(2,99) No action is required after applying this PTF unless you have been directed to use option 99 of DSN6SPRM.QUERY_ACCEL_OPTIONS. In that case, update your customized copy of job DSNTIJUZ as follows: * Add or update the keyword parameter 1 QUERY_ACCEL_OPTIONS= where is 99 or a list form such as (1,2,3,99) to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If your DSNTIJUZ job does not include QUERY_ACCEL_OPTIONS, that parameter will be set to the default of NONE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. If you added or modified the setting for QUERY_ACCEL_OPTIONS, you need to add or update the entry for it in all private copies of your CLIST output DSNTIDxx member. In each such copy, add or update the following line: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value you specified for QUERY_ACCEL_OPTIONS above in DSNTIJUZ. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWPZ PM73636 DSNDSPRM PM73636 DSNWZIFA PM73636 DSNXONZC PM73636 DSNXONZO PM73636 DSNXOW1 PM73636 DSN6SPRM PM73636 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73636 DSNDQWPZ DSNDSPRM DSNWZIFA DSNXONZC DSNXONZO DSNXOW1 DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWZIFA DSNXONZC DSNXONZO DSNXOW1 MACROS DSNDQWPZ DSNDSPRM DSN6SPRM LISTEND UK90809 COVER LETTER END UK90814 COVER LETTER START PROBLEM DESCRIPTION(S): PM78136 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of COPY SHRLEVEL * 1 * REFERENCE utility * **************************************************************** * PROBLEM DESCRIPTION: An incremental copy may contain more * * data pages than expected when a COPY * * SHRLEVEL REFERENCE FULL NO was * * previously run. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a COPY SHRLEVEL REFERENCE FULL NO on a table space defined with TRACKMOD YES. A subsequent COPY FULL NO was run, and the resulting incremental copy contained some data pages that were not changed between the two COPY jobs. The problem happened because the page modification information on space map pages was not set correctly by the COPY SHRLEVEL REFERENCE FULL NO that was previously run. This may result in incremental copies with more pages copied than expected, or in the case where no pages have been changed, an incremental copy being taken instead of none at all. The problem is intermittent and will not cause any recovery issue or data loss. In the reported case the problem was found when user tried to analyze the data unloaded from the incremental copy data set. COPY SHRLEVEL REFERENCE FULL NO is changed to set page modification information correctly in space map pages for TRACKMOD YES objects. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78136 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBASP PM78136 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78136 DSNUBASP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBASP LISTEND UK90814 COVER LETTER END UK90816 COVER LETTER START PROBLEM DESCRIPTION(S): PM76503 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of a view * * that contains outer joins and a * * table expression with UNION ALL and side-way * 1 * references. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location * * DSNXGRDS DSNXOEXB M200 or ABEND04E * * RC00E72018 at the location DSNXGRDS * * DSNXSMRE OFFSET4EAE(V9 only) could * * happen for an SQL statement referencing * * a view that satisfies all of the * * following conditions: * * * * 1. It contains outer joins. * * 2. It contains a table expression. * * 3. The table expression contains UNION * * ALL and side-way references. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 at the location DSNXGRDS DSNXOEXB M200 or ABEND04E RC00E72018 at the location DSNXGRDS DSNXSMRE OFFSET4EAE(V9 only) could happen for an SQL statement referencing a view that satisfies all of the following conditions: 1. It contains outer joins. 2. It contains a table expression. 3. The table expression contains UNION ALL and side-way references. An examples is shown below: CREATE TABLE T1 ( C1 INT ); CREATE TABLE T2 ( C1 INT ); CREATE TABLE T21 ( C1 INT ); CREATE TABLE T22 ( C1 INT ); CREATE VIEW V1 AS SELECT T1.C1 FROM T1, TABLE(SELECT C1 FROM T21 WHERE T21.C1 = T1.C1 UNION ALL SELECT C1 FROM T22 WHERE T22.C1 = T1.C1 ) TX LEFT OUTER JOIN T2 ON T2.C1 = TX.C1 1 ; SELECT * FROM V1; The SELECT statement above will cause the ABEND. DB2 did not correctly process the aforementioned SQL statements, which caused the ABEND. DB2 has been modified to correctly process the aforementioned SQL statement, so there will be no ABEND. Additional keywords: SQLVIEW SQLTABLEEXPR SQLUNIONALL SQLSIDEWAY SQLSIDEWAYREF SQLOUTERJOIN SQLOUTER SQLJOIN SQLFULL SQLFULLJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76503 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODSO PM76503 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76503 DSNXODSO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODSO LISTEND UK90816 COVER LETTER END UK90818 COVER LETTER START PROBLEM DESCRIPTION(S): PM77203 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of a native SQL * * procedure containing an SQL statement with a * * variable of type Timestamp(0). * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location * * DSNXGRDS DSNXGDT2 M206 could happen * * after rebinding and then running a * * native SQL procedure containing an SQL * * statement with a variable of type * * Timestamp(0). * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 at the location DSNXGRDS DSNXGDT2 M206 could happen after rebinding and then running a native SQL procedure containing an SQL statement with a variable of type Timestamp(0). 1 An example native SQL procedure is shown below: CREATE PROCEDURE SP1(INOUT P1 INT) L1: BEGIN DECLARE HV1 TIMESTAMP(0); SELECT 99 INTO P1 FROM T2 WHERE C1 = HV1; END L1! DB2 did not correctly process the aforementioned SQL statement, which caused the ABEND. DB2 has been modified to correctly process the aforementioned SQL statement, so there will be no ABEND. Additional keywords: SQLSP SQLSTOREDPROC SQLNATIVESQLPL SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77203 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODTR PM77203 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77203 DSNXODTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODTR LISTEND UK90818 COVER LETTER END UK90830 COVER LETTER START PROBLEM DESCRIPTION(S): PM74803 - **************************************************************** * USERS AFFECTED: All DB2 10, DB2 9 and DB2 V8 for z/OS data * * sharing users of the z/OS SETXCF REBUILD * * command when issued against SCA * **************************************************************** * PROBLEM DESCRIPTION: Timeout MSGDSNT376I MSGDSNT501I with * * RC00C900C0 TYPE00002105 may occur in * * data sharing when a REBUILD of the SCA * * structure is issued (e.g. * * SETXCF START,REBUILD,STRNM=DSNCAT_SCA), * * resulting in stoppage of the rebuild, * * with messages MSGDSN7504I, MSGIXC522I * * and MSGIXC521I, caused by concurrent * 1 * mainline DBET updater that happens to * * be in the notify exit path * * * * (PM74803 is the enabling APAR for a * * portion of APAR PM69760's code.) * **************************************************************** * RECOMMENDATION: * **************************************************************** REBUILD of the SCA structure may experience a timeout on resource type 00002105 when running concurrently with database exception table (DBET)-heavy activity such as during utility workloads that turn on/off various DBET states like UTRW, RBDP etc. The following sample illustrates the issue: ---------------------------------------------------------------- DSNT376I - PLAN=BCT WITH 398 CORRELATION-ID=014.RBDBET01 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397 THREAD-INFO=SYSOPR:*:*:* IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN= WITH CORRELATION-ID=020.JOBSTO07 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071B10954=7 THREAD-INFO=SYSOPR:*:*:* ON MEMBER V91A DSNT501I - DSNILMCL RESOURCE UNAVAILABLE 399 CORRELATION-ID=014.RBDBET01 CONNECTION-ID=V91A LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397=0 REASON 00C900C0 TYPE 00002105 NAME INTERNAL LOCK 05 DSN7504I - DSN7LST2 400 SCA STRUCTURE DSNCAT_SCA REBUILD UNSUCCESSFUL. REASON CODE = 8. IXC522I REBUILD FOR STRUCTURE 401 DSNCAT_SCA IS BEING STOPPED TO FALL BACK TO THE OLD STRUCTURE DUE TO CONNECTOR SPECIFIC REASON USER CODE: 00000008 IXC521I REBUILD FOR STRUCTURE DSNCAT_SCA 405 HAS BEEN STOPPED ---------------------------------------------------------------- The reason for the timeout of the SCA REBUILD is that a mainline DBET updater (e.g. a utility) is suspended (while holding the DBET hash lock) by the SCA REBUILD process. When the SCA REBUILD tries to obtain the same lock, it cannot do so because the holder is suspended and therefore the SCA REBUILD times out. 1 APAR PM74803 is particularly for the timing window when the SCA REBUILD tries to obtain the DBET hash lock while a mainline DBET updater is in the notify exit path. Code has been changed to adjust the serialization scheme between mainline DBET updaters and the SCA REBUILD process. APAR PM74803 is the enabling APAR for a portion of APAR PM69760. APAR PM74803 should be applied only after APAR PM69760 has been applied on all data sharing members. Additional keywords: DB2DSHR SYSPLEXDS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74803 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM MULTSYS: ***Action for PM74803: PM74803 is an APAR that includes changes to support a functional code change that will be enabled once this APAR is applied. Earlier, a pre-conditioning APAR PM69760 was delivered. In a data sharing group, this pre-conditioning APAR should be applied to all members before applying this enabling APAR to any member. The code change is enabled once this enabling APAR is applied. The following APAR enables the fix for the problem of timeout by SCA REBUILD when a concurrent mainline DBET updater happens to be in the notify exit path. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBEL PM74803 DSNIDBGN PM74803 DSNIDBGR PM74803 DSNIDBNG PM74803 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74803 DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG LISTEND UK90830 COVER LETTER END UK90843 COVER LETTER START PROBLEM DESCRIPTION(S): PM78058 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users who use the REBIND * * PACKAGE command with the OWNER option. * 1 **************************************************************** * PROBLEM DESCRIPTION: When a user uses a REBIND PACKAGE * * command with the OWNER option and the * * specified owner does not have authority * * to perform the rebind, DB2 issues an * * error message DSNT235I with an * * incorrect OWNER name. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a user uses a REBIND PACKAGE command with the OWNER option and the specified OWNER does not have authority to perform the rebind, DB2 issues an error message DSNT235I with an incorrect OWNER name. Here is an example of a REBIND command followed by the error message: REBIND PACKAGE(PKG0001.*) OWNER(OWNER03) DSNT235I @ DSNTBAP REBIND AUTHORIZATION ERROR USING ( AUTHORITY PACKAGE = LOC001.PKG0001.*.(*) PRIVILEGE = BIND The '(' between 'USING' and 'AUTHORITY' should be the OWNER name, which is 'OWNER03' in this case. The cause of this problem is that the CCSID conversion of the OWNER name is not handled correctly. Additional Keywords: MSGDSNT235I )) Code has been fixed to display the correct owner name in the output message. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78058 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBAPM PM78058 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78058 DSNTBAPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBAPM LISTEND UK90843 COVER LETTER END UK90881 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM79246 - **************************************************************** * USERS AFFECTED: DB2 for z/OS V10 CM8 or ENFM8 users of * * segmented table space, including universal * * tables space, in data sharing environment * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNINXTP ERQUAL5008 * * or * * ABEND04E RC00C9021B DSNIRFNX ERQUAL5009 * **************************************************************** * RECOMMENDATION: * **************************************************************** A new data page was formatted and its associated space map page was also updated. However, there is a timing window where space map page which reflects the new data page was written out to GBP prior to data page. During the timing window, the query with table space scan from the other data sharing member could read the space map page first but got a zero data page since there is no p-lock held on the data page. Therefore, the zero data page was not tolerated and caused ABEND. This problem only happens in V10 CM8 or ENFM8 environment. DB2 code is modified so that reader using table scan will tolerate zero data page as uncommitted phantom page in DB2 V10. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79246 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNINXTP PM79246 DSNIRFNX PM79246 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79246 DSNINXTP DSNIRFNX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNINXTP DSNIRFNX LISTEND UK90881 COVER LETTER END UK90882 COVER LETTER START PROBLEM DESCRIPTION(S): PM77661 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of COPY and Recover * * utilities against classic segmented table * * space. * **************************************************************** * PROBLEM DESCRIPTION: ' DSN1990I DSN1CPGD BROKEN PAGE ' * * message by DSN1COPY using a FCIC of * 1 * classic segmented table space. * * or other symptoms by false pseudo * * delete record for classic segmented * * table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** Utilities, COPY or Recovery, requested DB2 buffer manager to open page set of segmented table space like partitioned table space. Buffer Manager will turn on an internal flag to reflect the special treatment. During log apply phase of the Utility, data manager honored the internal flag and treated the classic segmented table space as universal table space. As the consequence, UNDO insert or REDO delete made a pseudo delete record on the page, and caused the inconsistency. DB2 code is modified to honor another flag which reflects the table space definition to detect whether the table space is partitioned or not, during utility log apply phase. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77661 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBHRE PM77661 DSNIBHUN PM77661 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77661 DSNIBHRE DSNIBHUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBHRE DSNIBHUN LISTEND UK90882 COVER LETTER END UK90884 COVER LETTER START PROBLEM DESCRIPTION(S): PM77134 - **************************************************************** * USERS AFFECTED: All DB2 v10 users in data sharing mode * * who has the SCA structure rebuilt. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 occurs in DSN7LST2 +01B2 * * when handling a SCA structure rebuild. * **************************************************************** * RECOMMENDATION: * **************************************************************** The reported abend occured when DB2 handles one of the z/OS even for the SCA structure rebuild. 1 The event was driven when DB2 is also being stopped. This abend is due to the event exit refrencing an internal control block when DB2 stop process has already deleted that block. DB2 code has been changed to disconnect from the SCA structure during shutdown and also check the internal control block before reference during rebuild exit. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77134 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN7GTRM PM77134 DSN7LST2 PM77134 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77134 DSN7GTRM DSN7LST2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN7GTRM DSN7LST2 LISTEND UK90884 COVER LETTER END UK90892 COVER LETTER START PROBLEM DESCRIPTION(S): PM77300 - **************************************************************** * USERS AFFECTED: DB2 users of COBOL stored procedures or * * user defined functions. * **************************************************************** * PROBLEM DESCRIPTION: User may receive sqlcode -471 with * * reason code 00E79007 when executing * * stored procedures or user defined * * functions prepared in different COBOL * * version. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running a stored procedure or an user defined function, DB2 will verify which language the routine is written in. Currently, DB2 may not recognize the language if the routine is compiled and link-edited in a different version of COBOL. DB2 code has been changed to recognize the COBOL language regardless in which COBOL version the stored procedure or user defined function is compiled and link-edited. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77300 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9WLS PM77300 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77300 DSNX9WLS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9WLS LISTEND UK90892 COVER LETTER END UK90928 COVER LETTER START PROBLEM DESCRIPTION(S): PM76887 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of FOR * * BIT DATA. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RCE70005 in * * DSNXGRDS.DSNXGSFN:M106 could occur * * when an SQL statement satisfies the * * following conditions: * * 1. It contains a table expression or * * view, * * 2. The table expression or view is * * merged, * * 3. It contains a predicate, one side * * is for bit data, the other side is * * not, * * 4. Different CCSID for both sides of * * predicate, and a CAST expression is * * involved. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RCE70005 in DSNXGRDS.DSNXGSFN:M106 could occur when an SQL statement satisfies the following conditions: 1. It contains a table expression or view, 2. The table expression or view is merged, 3. It contains a predicate, one side is for bit data, the other side is not, 4. Different CCSID for both sides of predicate, and a CAST expression is involved. The following example could recreate the abend, CREATE TABLE T1(C1 CHAR(7), C2 INTEGER) ; CREATE TABLE T2(C1 VARCHAR(10) FOR BIT DATA, C2 INTEGER) CCSID UNICODE; SELECT TX1.C2,T2.C2 FROM (SELECT CAST(C1 AS CHAR(8)) C1, C2 FROM T1) AS TX1, T2 WHERE TX1.C1 = T2.C1; 1 DB2 doesn't handle the FOR BIT column correctly during table expression or view merge which causes the abend. DB2 is updated to handle the FOR BIT data correctly. Additional Keywords: SQLFORBIT SQLTABLEEXPR SQLVIEW COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76887 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEXJ PM76887 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76887 DSNXOEXJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXJ LISTEND UK90928 COVER LETTER END UK90930 COVER LETTER START PROBLEM DESCRIPTION(S): PM75399 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the REPORT * * RECOVERY utility. * **************************************************************** * PROBLEM DESCRIPTION: Serviceability changes to the REPORT * * RECOVERY utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** Serviceability changes to the REPORT RECOVERY utility. Serviceability changes have been made to the REPORT RECOVERY utility. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75399 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUPBSD PM75399 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75399 DSNUPBSD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNUPBSD LISTEND UK90930 COVER LETTER END UK90938 COVER LETTER START PROBLEM DESCRIPTION(S): PM71153 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of * * labeled durations * **************************************************************** * PROBLEM DESCRIPTION: The labeled duration is extended to * * support an untyped parameter marker * * in the context of a datetime * * expression. * **************************************************************** * RECOMMENDATION: * **************************************************************** The labeled duration is extended to support an untyped parameter marker in the context of a datetime expression. The assumed data type for the untyped parameter marker is DECIMAL(27,12) for SECOND/SECONDS and DECIMAL(15,0) for others. EXAMPLE ======= SELECT (CURRENT_TIMESTAMP + ? MINUTES) FROM SYSIBM.SYSDUMMY1; The labeled duration has been extended to support an untyped parameter marker in the context of a datetime expression. Additional keywords: SQLYEAR SQLMONTH SQLHOUR SQLMINUTE SQLSECOND COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71153 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: See PM71153 APAR/PTF text for additional information. PM71153 introduces the following changes to externals: SQL Reference PREPARE Notes Untyped parameter marker 1 Table. Untyped parameter marker usage in expressions (including select list, CASE, and VALUES) +------------------------------------+---------------------+ | | | | Location of untyped | Data type (or error | | parameter marker | if not supported) | | | | +------------------------------------+---------------------| | | | | A labeled duration in a datetime | DECIMAL(15,0) | | expression (the portion of a | | | labeled duration that indicates | | | the type of units cannot be a | | | parameter marker). | | | | | +------------------------------------+---------------------| | | | | A labeled duration in a datetime | DECIMAL(27,12) | | expression with a type unit of | | | SECONDS (the portion of a labeled | | | duration that indicates the type | | | of units cannot be a parameter | | | marker). | | | | | +------------------------------------+---------------------+ COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOBFA PM71153 DSNXOBFF PM71153 DSNXOBF3 PM71153 DSNXOBF4 PM71153 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71153 DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 LISTEND UK90938 COVER LETTER END UK90961 COVER LETTER START PROBLEM DESCRIPTION(S): PM77016 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of LOBs (Large * * Objects) and the XML publishing functions. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses the following two * 1 * problems. * * * * 1. DB2 issued an SQLCODE -904 with * * reason code rc00C900D0 for an * * invalid LOB when the REORG Utility * * is in progress reading a LOB. * * * * 2. An ABEND04E RC00E70005 can occur at * * location DSNXRBND m666 when DB2 * * performs processing for the XML * * publishing functions with LOBs. * **************************************************************** * RECOMMENDATION: * **************************************************************** This apar addresses the following two problems. 1. DB2 issues an SQLCODE -904 (SQLCODE904) with reason code rc00C900D0 indicating "an invalid LOB" when the REORG utility is reading a LOB. There are some situations when LOG records are not available to recover a LOB object during the log apply process. During this time, DB2 can mark the LOB as being invalid and can issue an SQLCODE -904 when the LOB is referenced. While the SQLCODE -904 can be informative to some given application, it can prevent the the REORG utility from performing a diagnosis as it still needs to request an IFCID(340) record SQLCODE dump to proceed further. Therefore, on behalf of DB2 utilities, instead of issuing an SQLCODE -904 for this case, DB2 will generate a dump so that diagnosis can proceed immediately. 2. An ABEND04E RC00E70005 can occur at location DSNXRBND M666 when DB2 performs processing for an XML publishing function with LOBs. An ABEND04E RC00E70005 can occur at location DSNXRBND m666 while performing processing for an XML publishing function that is referencing a LOB object and encounters a "resource unavailable" condition. For example, this can occur when DB2 attempts to open a LOB auxiliary index data set and encounters a "resource unavailable" with a rc00C20113 reason code (which indicates that the maximum number of open data sets has been reached). The abend occurs because DB2 fails to route the "resource unavailable" condition case correctly to the proper error handling routine to format the SQLCODE -904 in response. For the first problem, the code in DB2 is modified to generate a dump instead of issuing an SQLCODE -904. For the second problem, the code in DB2 is modified to avoid producing a dump. Additional Keywords: SQLCODE904 SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77016 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNONLLE PM77016 DSNOTCSO PM77016 DSNXXGEN PM77016 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77016 DSNONLLE DSNOTCSO DSNXXGEN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNONLLE DSNOTCSO DSNXXGEN LISTEND UK90961 COVER LETTER END UK90964 COVER LETTER START PROBLEM DESCRIPTION(S): PM76088 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of LOBs * * used in LIKE predicates. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNOGETD 5001 when LOB data is * * used in a LIKE predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur unexpectedly at location DSNOGETD 5001 (ERQUAL5001) when LOB data is used in a LIKE predicate. The following example helps to illustrate the problem. 1. Create Table T1 with a LOB column C2 and populate it. CREATE TABLE T1 (C1 INT, C2 CLOB(100)); INSERT INTO T1 VALUES(1, CLOB('DECLARE VMPLR TABLE (EMPLOYEENUMBER CHAR( 6 )' CONCAT ' , PHONENUMBER CHAR ( 4 ) )')); 2. Execute a query which uses C2 in a LIKE predicate. SELECT * FROM T1 1 WHERE SUBSTR(C2, LOCATE(' CHAR ( ',C2), 50) NOT LIKE '%, ISO )'; The ABEND04E occurs when the above query is executed. The DB2 LOB component does not handle the LOB value properly when it is used in a LIKE predicate. The code in DB2 has been modified to process a LOB column properly when it is used in a LIKE predicate. Additional Keywords: SQLLIKE SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76088 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOGETD PM76088 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76088 DSNOGETD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOGETD LISTEND UK90964 COVER LETTER END UK91020 COVER LETTER START PROBLEM DESCRIPTION(S): PM77357 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL * * statements where global optimization is * * applied. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 at the location * * DSNXGRDS DSNXOGPS OFFSET2C6A could * * happen for an SQL statement when global * * optimization is used. This ABEND is * * dependent on the contents of some * * random storage in the PSA, so normally * * it won't happen. * **************************************************************** * RECOMMENDATION: * **************************************************************** The failure can be observed in the following example: CREATE TABLE TBL1 ( C1 INTEGER, C2 CHAR(10), C3 SMALLINT); 1 CREATE TABLE TBL2 ( C1 INTEGER, C2 CHAR(10), C3 SMALLINT); SELECT C1 FROM TBL1 T1 WHERE T1.C1 IN (SELECT C1 FROM TBL2 T2 WHERE T2.C3=28 ) FOR FETCH ONLY WITH CS; DB2 did not correctly set the internally generated table name of the virtual table, which caused the ABEND. DB2 has been modified to correctly process the virtual table setting, so there will be no ABEND. Additional keywords: SQLGLOBALOPT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77357 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOSO4 PM77357 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77357 DSNXOSO4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSO4 LISTEND UK91020 COVER LETTER END UK91023 COVER LETTER START PROBLEM DESCRIPTION(S): PM75935 - **************************************************************** * USERS AFFECTED: All DB2 10 and DB2 9 for z/OS users of SQL * * UPDATE on parent key in a referential * * integrity scheme, when the dependent table * * resides in a partitioned table space * * (classic-partitioned, partition-by-range * * universal or partition-by-growth) which * * contains more than 254 built partitions and * * table space scan is used to locate rows in * * the dependent table * 1 **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C20305 DSNIRELU+5850 on * * SQL UPDATE attempt on parent key when * * the dependent table resides in a * * partitioned table space (classic- * * partitioned, partition-by-range or * * partition-by-growth) with more than 254 * * partitions built and table space scan * * is used to locate dependent rows * **************************************************************** * RECOMMENDATION: * **************************************************************** When updating a primary key, DB2 must verify that no dependent rows exist. When table space scan was used to search for dependent rows (and the dependent table space was partitioned), DB2 relied on a looping variable that was big enough to represent only up to 254 partitions. Therefore, if the dependent table had more than 254 partitions, the variable would overflow and go to zero. The aforementioned DSNIRELU abend occurred when trying to perform a physical open on the 'zeroeth' partition, which is not a valid partition number. DB2 code has been modified to make sure that table space scan for dependent rows can operate on partitions greater than 254. Additional keywords: SQLPBG SQLUPDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75935 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRELU PM75935 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75935 DSNIRELU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRELU LISTEND UK91023 COVER LETTER END UK91061 COVER LETTER START PROBLEM DESCRIPTION(S): PM75719 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures or * * User Defined Functions (UDFs) that * * have ASUTIME specified. * **************************************************************** * PROBLEM DESCRIPTION: In some cases when a stored procedure * * exceeds the asutime limit, the * 1 * stored procedure task won't get * * detached right away and it will wait * * for a certain time to be terminated. * * This apparently increases the * * stored procedure processing time * * and is considered undesirable for * * those that allow only short processing * * stored procedures. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a timer monitor that monitors the CPU usage for each stored procedure. The timer monitor checks the CPU time at a fixed time interval. If the monitor detects that the stored procedure exceeded the asutime limit, DB2 will cancel the stored procedure. There are cases that the ASUTIME limit exceeded right after the monitor checked the time, so it has to wait for a certain time until the monitor pops up again to detect that. This implicitly increases the stored procedure or UDF processing time. DB2 code has been enhanced to reduce the wait interval for stored procedure or UDF ASUTIME. This would provide a higher rate of monitoring for Stored Procedures or UDFs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75719 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9TIM PM75719 DSNX9WLM PM75719 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75719 DSNX9TIM DSNX9WLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9TIM DSNX9WLM LISTEND UK91061 COVER LETTER END UK91065 COVER LETTER START PROBLEM DESCRIPTION(S): PM79266 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS new function mode (NFM) * * users of universal table space (UTS) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIBHUN ERQUAL5022 * * during ABORT. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** For UTS in V10 NFM, if an INSERT operation reused the rid of the preceding DELETE operation in the same UR, and the UR ABORTed, DB2 UNDO the INSERT operation first and made a pseudo deleted record if PGIDFREE on the page happened to be 0, when it came to UNDO the DELETE operation, DB2 thought the pseudo deleted record was by the DELETE operation but only found length of the pseudo deleted record didn't match that in log record for the DELETE operation and ABENDed the ABORT. DB2 code is modified not to take the pseudo deleted record as the one by the DELETE under UNDO. With the fix, UNDO DELETE will turn the pseudo deleted record into hole and add the logged DELETE data back onto PGFREEP. Page compaction will be conducted if necessary. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79266 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBHUN PM79266 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79266 DSNIBHUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBHUN LISTEND UK91065 COVER LETTER END UK91084 COVER LETTER START PROBLEM DESCRIPTION(S): PM74413 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of sysplex * * parallelism * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC04 at DSNIOST2+2C12 can * * occur while running a sysplex parallel * * query. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC04 at DSNIOST2+2C12 can occur for a query that is run with sysplex parallelism. The abend is caused by a residual SPROC address which missed the cleanup while creating a child task in the local DB2 system. DB2 code is modified to clean up residual addresses for SPROC and PPROC while starting the child task. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74413 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRTSC PM74413 DSNXRTSS PM74413 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74413 DSNXRTSC DSNXRTSS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRTSC DSNXRTSS LISTEND UK91084 COVER LETTER END UK91144 COVER LETTER START PROBLEM DESCRIPTION(S): PM75054 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users who use * * PREPARE statement in SQL/PL to access XML * * data. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 at DSNIDM.DSNOGETD+37FE * * will occur when running a SQL/PL stored * * procedure which contains a PREPARE * * statement and the prepared SQL * * statement accesses XML data. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 at DSNIDM.DSNOGETD+37FE will occur when running a SQL/PL stored procedure which contains a PREPARE statement and the prepared SQL statement accesses XML data. For example: Following command creates a table with one XML column. CREATE TABLE T1 (X1 XML); Following statement will create a SQL/PL stored procedure with a prepare statement and the SQL statement for the prepared statement is inserting data to XML column. CREATE PROCEDURE MYPROC() L1: BEGIN DECLARE MYSQL CHAR(128); 1 DECLARE MYATT VARCHAR(100); DECLARE MYXML VARCHAR(100); SET MYSQL = 'INSERT INTO T1 VALUES(?)' ; SET MYATT = 'ATOMIC'; SET MYXML = '111'; PREPARE S1 ATTRIBUTES MYATT FROM MYSQL; EXECUTE S1 USING MYXML; END L1 @ When the stored procedure is called, the ABEND0C4 at DSNIDM.DSNOGETD+37FE will occur. DB2 code is modified, so the abend will not occur. Additional keywords: SQLXML SQLPL XMLALL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75054 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNAINP PM75054 DSNXRIB9 PM75054 DSNXRID9 PM75054 DSNXRIHB PM75054 DSNXRIHD PM75054 DSNXRIHR PM75054 DSNXRIHS PM75054 DSNXRIS9 PM75054 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75054 DSNNAINP DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNAINP DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 LISTEND UK91144 COVER LETTER END UK91166 COVER LETTER START PROBLEM DESCRIPTION(S): PM73995 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using LOBs or XML and * 1 * where DRDA data encryption is enabled. * **************************************************************** * PROBLEM DESCRIPTION: DB2 server thread hangs when inserting * * an encrypted LOB. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 server processing may not detect the end of encrypted LOB and/or XML data and incorrectly issues a network receive to request additional data. The receive operation hangs because there is no more data to actually receive. DB2 server processing has been changed to properly detect the end of encrypted LOB/XML data. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73995 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLCMRL PM73995 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73995 DSNLCMRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLCMRL LISTEND UK91166 COVER LETTER END UK91168 COVER LETTER START PROBLEM DESCRIPTION(S): PM75473 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: Intermittent performance problems may * * be observed due to contention related * * to DDF communication buffer storage * * usage. * * Unpredictable, storage related, abends * * may also occur. Symptoms may include: * * . ABND=04E-00E20003, * * LOC=DSNGEPLC.DSNSVBK +05EA * * . ABND=04E-00E20003, * * LOC=DSNXEPM .DSNSVBK +05EA * * . ABND=04E-00E20016, * * LOC=DSNSLD1 .DSNSVSTK+0656 * * . ABND=04E-00E20003, * * LOC=DSNXOTDA.DSNSVBK +05EA * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** To satisfy remote application SQL activity, distributed server threads may acquire vast amounts of 64-bit shared private (communication buffer) storage. As storage utilization increases, delays of 20 seconds or more may occur when satisfying storage requests from a storage pool which has a limited number of extra blocks allowed by its definition. This may lead to application/transaction delays and/or storage related abends. DDF initialization has been changed to increase the number of extra blocks allowed to satisfy a get storage request to match the number of blocks that are actually requested at a time. This reduces the number of storage scans and expansions necessary to satisfy a "get storage" request thereby reducing latch contention. This allows threads to get and release storage more quickly which minimizes abends due to storage shortage. This leads to an improvement in overall DDF transaction response time. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75473 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLIINI PM75473 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75473 DSNLIINI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIINI LISTEND UK91168 COVER LETTER END UK91189 COVER LETTER START PROBLEM DESCRIPTION(S): PM80245 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the RUNSTATS * * utility. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E40417 DSNUFOBD OFFSET09A6 * * when using RUNSTATS with the * * USE PROFILE option specified. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A RUNSTATS TABLESPACE with a table specification and USE PROFILE was specified. The specified table name had a view on it with 1 the same name as the specified RUNSTATS table name. View rows in the SYSTABLES catalog table have zeroes for the DBID and OBID column values. RUNSTATS used these zeroed OBID and DBID values resulting in an ABEND04E RC00E40417 DSNUFOBD +x'09A6'. This abend could also happen if the same RUNSTATS as above was used but with the UPDATE PROFILE option. RUNSTATS code has been modified to correct the aforementioned problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80245 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGPRF PM80245 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80245 DSNUGPRF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGPRF LISTEND UK91189 COVER LETTER END UK91203 COVER LETTER START PROBLEM DESCRIPTION(S): PM72526 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: Processing of the deletion of unneeded * * XML document versions is not directed * * to be executed on an available zIIP. * **************************************************************** * RECOMMENDATION: * **************************************************************** For XML columns that support multiple XML versions, after a SQL UPDATE or DELETE, rows for multiple XML versions exist in the XML table space. There is an asynchronously running SRB that deletes the rows for XML versions that are no longer needed. With this APAR applied, DB2 10 for z/OS will direct z/OS to have the asynchronous processing to delete rows for XML versions, when running in an SRB enclave, executed on an available zIIP.** ** This provides only a general description of the type and portions of workloads that are eligible for execution on a zIIP Specialty Engine(SE). IBM authorizes customers to use the zIIP SE only to execute the 1 processing of Eligible Workloads of specific Programs expressly authorized by IBM as specified in the “Authorized Use Table for IBM Machines” provided at www.ibm.com/systems/support/machine_warranties/machine_code/aut .html ("AUT"). No other workload processing is authorized for execution on an SE. IBM offers SEs at a lower price than General Processors/Central Processors because customers are authorized to use SEs only to process certain types and/or amounts of workloads as specified by IBM in the AUT. Additional keywords: XMLALL XMLUPDATE XMLDELETE XMLVERSION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72526 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOCLN PM72526 DSNNXCMT PM72526 DSNXINIT PM72526 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72526 DSNNOCLN DSNNXCMT DSNXINIT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOCLN DSNNXCMT DSNXINIT LISTEND UK91203 COVER LETTER END UK91209 COVER LETTER START PROBLEM DESCRIPTION(S): PM74461 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of UPDATE or * * DELETE statements. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 at DSNIWNRF * * OFFSET515E or DSNIWNRF OFFSET1EB6 for * * an UPDATE or DELETE statement can * * occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000004 at DSNIWNRF OFFSET515E or DSNIWNRF OFFSET1EB6 can occur during execution time for an UPDATE or DELETE statement with a subquery when DB2 chooses IN-list direct table access. IN-list table access is indicated in the ACCESSTYPE column of the PLAN_TABLE as 'IN'. 1 Additional Keywords: SQLUPDATE SQLDELETE SQLIN SQLINLISTTABLE Code is changed to avoid IN-list table access in the situation described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74461 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM74461 corrects a problem of ABEND0C4 RC00000004 at DSNIWNRF OFFSET515E or DSNIWNRF OFFSET1EB6 for an UPDATE or DELETE statement with a subquery. When IN-list direct table access is chosen for an UPDATE or DELETE statement, this problem can occur. IN-list table access is indicated in the ACCESSTYPE column of the PLAN_TABLE as 'IN'. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGBM PM74461 DSNXOGP PM74461 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74461 DSNXOGBM DSNXOGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGBM DSNXOGP LISTEND UK91209 COVER LETTER END UK91210 COVER LETTER START PROBLEM DESCRIPTION(S): PM77580 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of LOB * * Locators in a distributed environment. * **************************************************************** * PROBLEM DESCRIPTION: An intermittent ABEND0C4 rc38 can occur * * at location DSNOCFLO OFFSET0228 when a * * remote application references an unheld * * LOB Locator after a commit. Instead, * * DB2 should issue an SQLCODE -423 * * (SQLCODE423) for an invalid LOB Locator * 1 * value. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an unheld LOB Locator passes the COMMIT point, DB2 automatically frees the LOB Locator. DB2 is expected to issue an SQLCODE -423 if this already freed unheld LOB Locator is still referenced later. However, in a distributed environment, the application (connection) may be pooled away from the DB2 thread after the COMMIT if DB2 is configured with DDF Inactive Thread Support (DSN6FAC CMTSTAT=INACTIVE). The LOB Locator internal structure may not be available when the application (connection) resumes SQL and can be reassigned to a new/different thread. This may lead to the reported ABEND0C4. DB2 code has been modified to issue an SQLCODE -423 in such a scenario instead of abending. Additional Keywords: SQLLOB SQLCODE423 DB2LOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77580 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOCFLO PM77580 DSNOCHLO PM77580 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77580 DSNOCFLO DSNOCHLO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOCFLO DSNOCHLO LISTEND UK91210 COVER LETTER END UK91217 COVER LETTER START PROBLEM DESCRIPTION(S): PM78063 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where remote applications * * connect to DB2 using TCP/IP protocols. * **************************************************************** * PROBLEM DESCRIPTION: The following error occurred at a * * DB2 for z/OS server: * * . Message DSNL511I DSNLIENO TCP/IP * * CONVERSATION FAILED TO LOCATION * * location-name IPADDR=ip-address * * PORT=port SOCKET=RECV * * RETURN CODE=1124 * 1 * REASON CODE=77B77221 * * Remote applications fail to connect * * to DB2 when the above error condition * * occurs. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote application which connects to a DB2 for z/OS server using TCP/IP protocols fails with SQLCODE -300081 and message DSNL511I DSNLIENO TCP/IP CONVERSATION FAILED TO LOCATION SOCKET=RECV RETURN CODE=1124 REASON CODE=77B77221 is issued at the DB2 server. This error occurs because DB2 incorrectly freed the ACEE associated with the xxxxDIST address space during connection authentication processing. When DB2 then tries to invoke z/OS USS BPX1IOC service to obtain security related information for the socket, the BPX1IOC service failed due to the missing xxxxDIST ACEE. Hence, DB2 rejects the connection. DB2 has been changed to ensure that the ACEE associated with the xxxxDIST address space is never deleted during remote connection authentication processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78063 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3AUGC PM78063 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78063 DSN3AUGC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3AUGC LISTEND UK91217 COVER LETTER END UK91220 COVER LETTER START PROBLEM DESCRIPTION(S): PM71945 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users. * **************************************************************** * PROBLEM DESCRIPTION: MSGDXR175E IRLM is unable to obtain * * storage - ECSA may appear on console * * followed by IRA100E for SQA shortage. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** 1 In a system running low on ECSA storage, the virtual storage manager may return a storage block below the 16M line when GETMAIN is called with option LOC=ANY. IRLM could accumulate CSA storage blocks in a short period of time causing CSA to fill up. This can happen typically with monitoring tools sending Query or Notify requests in a data sharing group. IRLM may not be able to quickly release the CSA/ECSA storage as it could run storage compression only at deadlock detection timer intervals which may not be aggressive enough to handle a spike of incoming NOTIFY or QUERY requests. This may lead to MSGDXR175E and/or IRA100E to be issued. This APAR improves CSA/ECSA storage management in IRLM. IRLM will not be acquiring any CSA storage and when will trigger IRLM storage compression sooner if MVS is not able to return the requested block size from ECSA. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM71945 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL400 PM71945 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71945 DXRRL400 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL400 LISTEND UK91220 COVER LETTER END UK91228 COVER LETTER START PROBLEM DESCRIPTION(S): PM78373 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: Message DSNL031I with REASON=00D351FF * * and ERROR ID=DSNLZRPA0001, and/or * * SQLCODE -30061, due to a zero IP * * address being used to access a remote * * system. * **************************************************************** * RECOMMENDATION: * **************************************************************** When many concurrent users are trying to access the same remote location, serialization issues exist during domain name resolution processing that allows a null IP address to be determined for the remote system. The null (zero) IP address is interpreted by the TCP/IP stack as a "loop back" condition that is serviced by the same host (instead of the intended 1 remote host). If another subsystem is configured to listen on the same port (as the intended remote server), the connection request is essentially honored by the wrong partner. The location name (RDBNAME) will therefore not match that of the intended remote system and the connection will be rejected (DRDA RDBNFMRM). This results in message DSNL031I being issued to the console and the application will receive SQLCODE -30061. DB2 for z/OS is changed to correctly serialize domain name resolution processing for the benefit of users that are concurrently accessing the remote system. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78373 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLIDNS PM78373 DSNLVCIP PM78373 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78373 DSNLIDNS DSNLVCIP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIDNS DSNLVCIP LISTEND UK91228 COVER LETTER END UK91247 COVER LETTER START PROBLEM DESCRIPTION(S): PM78772 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of RID list * * access. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 rc00000038 can occur at * * location DSNISRID OFFSET606E when * * another thread was running a query * * using RID list access. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 rc00000038 can occur at location DSNISRID OFFSET606E when another thread is running a package (bound on a release prior to DB2 v10) which is executing a query using RID list access. In a very busy system, when DB2 executes a query with RID list access, if it is contained in a package that is bound prior to v10, DB2 could accidentally free internal storage which is still 1 in use by another thread. Then, when this other thread gains control, an unexpected ABEND0C4 can occur because of it. Please note that as a result of one thread freeing the storage which is in use by another thread, many different kinds of failures (failing symptoms) can occur once the storage is freed. These include but are not limited to the following. ABEND04E with RC00C90301 at DSNXRFR9 offset0FF6 ABEND0C4 with RC00000038 at DSNISRID offset607A ABEND0C4 with RC00000038 at DSNISFRL offset2336 ABEND04E with RC00C90101 at DSNISRID erqual5001 ABEND0C4 with RC00000038 at DSNXSFUN offset02D6 Additionally, this problem can also occur when a pre-v10 bound package that contains a query which uses RID list access is rebound on DB2 v10. Please note that a later apar PM79741 will address this issue. The code in DB2 which incorrectly frees another thread's internal storage has been modified to free the proper storage. Additional Keywords: SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN SQLRID SQLRIDLIST COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78772 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNITCUS PM78772 DSNXRFR9 PM78772 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78772 DSNITCUS DSNXRFR9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNITCUS DSNXRFR9 LISTEND UK91247 COVER LETTER END UK91264 COVER LETTER START PROBLEM DESCRIPTION(S): PM77513 - **************************************************************** * USERS AFFECTED: All DB2 package users. * **************************************************************** * PROBLEM DESCRIPTION: After cancelling a package execution, * * customer may hit the ABEND0C4 at * * DSNGEFSP+B78 followed by DB2 crash * * with RC00F30420. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 internal data structure is not initiated. When the cancel happens after DSNGEPLC obtained a block for a package and before loading the RDS section in it, there could be residual PTHEADER information in the block which causes an ABEND in the ABEND recovery routine. The ABEND in ABEND recovery routine causes DB2 crash. DB2 has been changed to initiate the internal data structure to avoid the abend. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77513 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEGBK PM77513 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77513 DSNGEGBK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEGBK LISTEND UK91264 COVER LETTER END UK91268 COVER LETTER START PROBLEM DESCRIPTION(S): PM74513 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of static applications which reference * * user-defined types (UDTs). * **************************************************************** * PROBLEM DESCRIPTION: REBIND may result in an infinite * * loop when a static application is * * dependent on a UDT. * **************************************************************** * RECOMMENDATION: * **************************************************************** REBIND may result in an infinite loop when the package is dependent on a UDT. REBIND has been modified to prevent the infinite loop. If REBIND results in an infinite loop, the thread may be cancelled to end the infinte loop. ADDITIONAL KEYWORDS: LOOPDSNXIDPM SQLUDT 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74513 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIDPM PM74513 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74513 DSNXIDPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIDPM LISTEND UK91268 COVER LETTER END UK91288 COVER LETTER START PROBLEM DESCRIPTION(S): PM78884 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REORG TABLESPACE/INDEX with * * SHRLEVEL CHANGE/REFERENCE. * **************************************************************** * PROBLEM DESCRIPTION: Shadow data sets were not deleted after * * a -TERM UTIL of a REORG INDEX SHRLEVEL * * CHANGE during the UNLOAD phase. * * * * Shadow data sets were not deleted after * * duplicate keys were detected during a * * REORG SHRLEVEL REFERENCE and failed * * with RC8. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A REORG INDEX SHRLEVEL CHANGE was terminated by a -TERM UTIL command during the UNLOAD phase. The shadow data sets were not deleted because the internal cleanup flag was not set for termination processing if -TERM UTIL command was issued at the end of UNLOAD phase. The problem could also happen for a REORG INDEX SHRLEVEL REFERENCE or a REORG TABLESPACE SHRLEVEL CHANGE or REFERENCE. A REORG TABLESPACE SHRLEVEL REFERENCE ran on a table space with a unique index. The REORG failed with RC8 because some duplicate index keys were detected during the BUILD phase. The shadow data sets were not deleted because the internal cleanup flag was not set for termination processing. The problem could also happen for a REORG TABLESPACE SHRLEVEL CHANGE. REORG code has been changed to cleanup the shadow data sets when 1 an online REORG is terminated by a -TERM UTIL command during the UNLOAD phase or duplicate keys are detected during the BUILD phase. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78884 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURORG PM78884 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78884 DSNURORG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURORG LISTEND UK91288 COVER LETTER END UK91315 COVER LETTER START PROBLEM DESCRIPTION(S): PM80607 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNB1RLS. * **************************************************************** * RECOMMENDATION: * **************************************************************** Abend is due to a serialization issue on a pageset/partition read-lsn chain, when a read-lsn is being registered for a scrollable cursor. Since the scrollable cursor logic is using a different latch to serialize the chain than the other code which manipulates the chain, it may run into an ABEND0C4 due to the chain changing underneath it. DSNB1RLS has been modified to use the correct latch to serialize the read-lsn chain. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80607 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1RLS PM80607 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80607 DSNB1RLS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNB1RLS LISTEND UK91315 COVER LETTER END UK91321 COVER LETTER START PROBLEM DESCRIPTION(S): PM77066 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS data sharing users with * * PM53155 / UK77362, DB2 9 for z/OS data * * sharing users with PM53155 / UK77364 and * * DB2 V8 for z/OS data sharing users with * * PM53155 / UK77363 applied * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBHK ERQUAL500C * * during several data sharing members' * * DB2 checkpoint after group restart, * * leading to their DB2 crash with * * MSGDSNV086E RC00D95001 * **************************************************************** * RECOMMENDATION: * **************************************************************** During group restart, while updating the group DBET in SCA, a subset of the DBET base SCA record(s) for an object was accidentally deleted, which resulted in local DBET entry for the object being built incorrectly. In this case, there were more than 200 partitions with diverse exception states such that the DBET entry for this object had multiple DBET blocks. During internal DBET rectify, at the beginning of forward log apply phase, the group DBET in SCA needed to be updated since local DBET had to reset an internal extend-in-progress state. However, when copying the local DBET blocks to the group DBET in SCA, by mistake not all the DBET blocks were copied. This resulted in an incomplete group DBET in SCA for this object. When other members of the data sharing group came up, their local DBET was built incorrectly, eventually leading to the aforementioned ABEND04E. The first member that performed the rectify was able to come up successfully because his local DBET was not corrupted. Any subsequent DBET updates that this member performed after the group restart automatically cleaned up the group DBET in SCA, which is why the originally failed members were able to restart on their second restart attempt. DB2 code has been modified such that the group DBET in SCA is updated correctly during DBET rectify. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77066 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBNG PM77066 DSNIDBNI PM77066 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77066 DSNIDBNG DSNIDBNI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBNG DSNIDBNI LISTEND UK91321 COVER LETTER END UK91330 COVER LETTER START PROBLEM DESCRIPTION(S): PM77952 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of the online CHECK utility * **************************************************************** * PROBLEM DESCRIPTION: Fast replication did not take place * * during an online CHECK INDEX * **************************************************************** * RECOMMENDATION: * **************************************************************** Message ADR918I with Return Code 1D or 26 was issued during a CHECK INDEX SHRLEVEL CHANGE. DFSMSdss made a choice not to use fast replication because there was a mismatch of VSAM data set attributes. In this case the CASIZE was different because the data set for the table space was allocated in tracks, but DFSMSdss allocated the copy data set in cylinders which caused the mismatch. The following utilities will be affected: CHECK INDEX, CHECK DATA, CHECK LOB Additional Keywords: MSGADR918I New parameters VOLCOUNT(ANY) and TGTALLOC(SRC) are added in the DFSMSdss COPY command when online CHECK utilities use the FLASHCOPY function, so that fast replication will more likely to be taken. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77952 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKCPX PM77952 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77952 DSNUKCPX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKCPX LISTEND UK91330 COVER LETTER END UK91332 COVER LETTER START PROBLEM DESCRIPTION(S): PM79942 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of the LOAD utility * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 RC00000011 at DSNURWBF * * OFFSETAFCA during a LOAD with one INTO * * TABLE clause followed by several INTO * * TABLE PART xx clauses * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** The LOAD utility was used to load a partitioned table space with a single input data set by specifying one INTO TABLE without PART keyword followed by several INTO TABLE with PART xx statements. The LOAD abended with ABEND0C4 RC00000011 at DSNURWBF + x'AFCA'. An example of the abended LOAD statements: LOAD DATA RESUME YES INDDN SYSREC INTO TABLE table name INTO TABLE table name PART x REPLACE For partitioned table spaces, the LOAD was incorrectly accumulating the required space for index keys when there was a INTO TABLE as the first clause followed by an INTO TABLE PART xx clause, which caused an overflow when extracting keys into the key buffer. Additional keywords: RC00000004 OFFSETFDB8 x'FDB8' The LOAD utility code has been modified to correctly count the index key space needed for partitioned table spaces. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79942 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURWIK PM79942 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79942 DSNURWIK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWIK LISTEND UK91332 COVER LETTER END UK91338 COVER LETTER START PROBLEM DESCRIPTION(S): PM70914 - **************************************************************** * USERS AFFECTED: All users of the CATMAINT utility for * * release migrations. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 migration process fails with * * a SQLCODE4732. This indicates that * * there are no available version numbers * * for a table being changed during the * * migration process. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 for z/OS migration process is failing because it is trying to ALTER a catalog table that has no available version numbers (SQLCODE4732). To correct the problem the subsystem must fall back to the release being migrated from so that the version numbers can be recycled. DB2 release migrations will fail if an attempt to alter a catalog table fails because there are no available version numbers. DB2 catalog tables cannot be modified outside of the migration process (CATMAINT). These table modifications are generally done during the same commit scope to keep the number of used version numbers to a minimum. As such, there should be no cases where we are out of version numbers for catalog objects. But we have seen some cases where migrations are failing because there are no available version numbers (SQLCODE4732). We're not sure how the version numbers are being broken at this point. But in this APAR we are changing code that will fail utility processes that update version numbers when we detect that version numbers are going to be broken (ie where the SYSTABLESPACE.CURRENT_VERSION number will end up being less than SYSTABLESPACE.OLDEST_VERSION). In addition, we are changing the premigration checkout jobs, DSNTIJPM and DSNTIJPA, to add queries that will identify cases where the version numbers are bad. The premigration checkout 1 jobs are to be run before migration processing begins (ie in the release being migrated from). If there is a version number problem then the version numbers can be corrected prior to the migration process. This will ensure that the migration process will not fail due to this problem. See the ++HOLD actions for this APAR for further guidance for using DSNTIJPM or DSNTIJPA. The following SELECT statement can be used to determine if there are catalog objects that have version number problems: SELECT SUBSTR(CREATOR,1,8) AS CREATOR, SUBSTR(NAME,1,8) AS NAME, OLDEST_VERSION, CURRENT_VERSION FROM SYSIBM.SYSTABLESPACE WHERE DBID = 6 AND (CURRENT_VERSION < OLDEST_VERSION); If there are table spaces returned with this query then the version numbers can be corrected by a REORG of the table space and then by running MODIFY RECOVERY with DELETE to recycle version numbers. Additional information about version numbers can be found in the Utility Guide and Reference and also in the Administration Guide. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70914 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM70914 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it your DB2 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration. ACTION: ***Action for PM66043 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it for your DB2 - If you are preparing to migrate to DB2 V10, run the updated 1 customized job to check for conditions that may affect your migration. ACTION: ***Action for PM54699 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it for your DB2 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTIJPM PM70914 DSNUGUVR PM70914 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70914 DSNTIJPM DSNUGUVR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGUVR MACROS DSNTIJPM LISTEND UK91338 COVER LETTER END UK91349 COVER LETTER START PROBLEM DESCRIPTION(S): PM74007 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users * **************************************************************** * PROBLEM DESCRIPTION: The first character of the SQLERRP * * field in the SQLCA, or the first * * character of the QW0053SQ field in the * * IFCID 53 trace record, may contain an * * invalid 'FF'x character after * * executing a remote SQL statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 for z/OS application connects to a remote server and calls a stored procedure. The remote server issues an SQLCODE -444 for the CALL request because the procedure could not be found. DB2 for z/OS, while parsing the DRDA SQLCARD object reflecting the SQLCODE -444 condition, overwrites the first 1 character of the SQLCA SQLERRP field with an invalid 'FF'x. Note: This error can occur for any remote SQL statement where the SQLCA contains an SQLERRMT string that is 70-bytes long and character conversion is needed. DB2 for z/OS requester processing has been changed to handle the parsing of DRDA SQLCARD object correctly when conversion occurs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74007 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZRCD PM74007 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74007 DSNLZRCD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZRCD LISTEND UK91349 COVER LETTER END UK91351 COVER LETTER START PROBLEM DESCRIPTION(S): PM74794 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of the DSNACCOX stored * * procedure * **************************************************************** * PROBLEM DESCRIPTION: Three problems for DSNACCOX REORG * * RESTRICT: * * * * 1. INDEXSPACE column is blank and * * should contain the index space name * * * * 2. OBJECTSTATUS does not have the * * partitioned object space(s) that are * * in a restrictive state such as AREOR * * status. * * * * 3. Output contains a row for partition * * 0 that should not be there. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** DSNACCOX REORG RESTRICT yields: 1. A result set with INDEXSPACE being blank when it should be 1 filled in. 2. OBJECTSTATUS does not have the partitioned table/index spaces restrictive DBET state such as AREOR listed. 3. Output erroneously containing a line for partition 0. DSNACCOX has been changed to: 1. Fill in the indexspace name when required and possible. 2. Fill in OBJECT STATUS with the partitioned table space or index space restrictive DBET state. 3. Not put out a line for partition 0. The DB2 9 for z/OS Utility Guide and Reference will be changed with the following: PM74791 introduces the following changes to the DB2 9 for z/OS Utility Guide and Reference - Appendix B. DB2-supplied stored procedures for utility operations Section - DSNACCOX stored procedure Chapter - DSNACCOX output Table 145 - Result set row for second DSNACCOX result set | NAME VARCHAR(128) Table space name, index name, or | index space name. Index space | name is used if the row is added | as a result of checking a | restricted state and the index | name is not available at the time. Information about this changed information 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. The DB2 10 for z/OS Utility Guide and Reference will be changed with the following: PM74791 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference - Appendix B. DB2-supplied stored procedures for utility operations 1 Section - DSNACCOX stored procedure Chapter - DSNACCOX output Table 145 - Result set row for second DSNACCOX result set | NAME VARCHAR(128) Table space name, index name, or | index space name. Index space | name is used if the row is added | as a result of checking a | restricted state and the index | name is not available at the time. Information about this changed information 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. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74794 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM74794 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference - Appendix B. DB2-supplied stored procedures for utility operations Section - DSNACCOX stored procedure Chapter - DSNACCOX output Table 145 - Result set row for second DSNACCOX result set | NAME VARCHAR(128) Table space name, index name, or | index space name. Index space | name is used if the row is added | as a result of checking a | restricted state and the index | name is not available at the time. Information about this changed information 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. ACTION: ***Action for PM74794: See PM74794 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PM74794: 1 (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity (b) Rebind package for DSNACCOX. An example on how to do this is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity ACTION: After you apply the PTF for APAR PM61574, Non Partitioned Index is no longer recommended for reorg or runstats when chklevel 32 is specified and any of the ts partitioned is recommended for reorg or runstats. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@CCOX PM74794 DSNACCOX PM74794 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74794 DSN@CCOX DSNACCOX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACCOX MACROS DSN@CCOX LISTEND UK91351 COVER LETTER END UK91433 COVER LETTER START PROBLEM DESCRIPTION(S): PM79251 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of implicit CAST. * **************************************************************** * PROBLEM DESCRIPTION: Infinite loop could occur when an SQL * * statement satisfies all of the * * following conditions: * * 1.There is a table expression which * * will be merged, * * 2.An implicit CAST or timestamp * * with time zone data type column is * * involved in the table expression, * * 3.The outer query block of the table * * expression contains a predicate * * referencing the implicit CAST * * or timestamp time zone type column * * expression in the table expression. * **************************************************************** * RECOMMENDATION: * **************************************************************** Infinite loop could occur when an SQL statement satisfies all of the following conditions: 1 1.There is a table expression which will be merged, 2.An implicit CAST or timestamp with time zone data type column is involved in the table expression, 3.The outer query block of the table expression contains a predicate referencing the implicit CAST or timestamp with time zone type column expression in the table expression. The following examples could recreate the problem, CREATE TABLE T1 (T1C1 CHAR(1), T1C2 INTEGER, T1C3 SMALLINT); CREATE TABLE T2 (T2C1 INTEGER, T2C2 INTEGER, T2C3 TIMESTAMP WITH TIMEZONE); 1. Implicit Cast example: SELECT * FROM (SELECT CASE WHEN S.SC1 = 1 THEN X.XC1 ELSE T2C2 END CX FROM (SELECT 100 XC1 FROM SYSIBM.SYSDUMMY1 FETCH FIRST 1 ROWS ONLY) X, T2 LEFT OUTER JOIN ( SELECT T1C2 ,MAX(T1C1) SC1 FROM T1 WHERE T1C3 > 1200 GROUP BY T1C2 ) S ON S.T1C2 = T2C1 WHERE T2C2 =100) C WHERE CX IS NULL WITH UR CX is a column with case expression, IMPLICIT CAST is added in CASE WHEN predicate, DB2 doesn't handle the IMPLICIT CAST well which causes the infinite loop. 2. Timestamp with time zone example: SELECT * FROM (SELECT CASE WHEN S.SC1 = T2C3 THEN X.XC1 ELSE T2C2 END CX FROM (SELECT 100 XC1 FROM SYSIBM.SYSDUMMY1 FETCH FIRST 1 ROWS ONLY) X, T2 LEFT OUTER JOIN ( SELECT T1C2 ,MAX(T1C1) SC1 FROM T1 WHERE T1C3 > 1200 GROUP BY T1C2 ) S ON S.T1C2 = T2C1 WHERE T2C2 =100) C WHERE CX IS NULL WITH UR CX is a column with case expression, T2C3 is timestamp with time zone type, SC1 is string type, DB2 doesn't handle the timestamp with time zone column compares with string type column correctly which causes the infinite loop. DB2 is updated to handle the implicit CAST and timestamp with time zone column correctly. Additional Keywords: SQLIMPLICITCAST SQLOUTERJOIN SQLTIMESTAMP SQLTIMEZONE LOOPDSNXOEXB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79251 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOBFA PM79251 DSNXOBFC PM79251 1 DSNXOBFF PM79251 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79251 DSNXOBFA DSNXOBFC DSNXOBFF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBFA DSNXOBFC DSNXOBFF LISTEND UK91433 COVER LETTER END UK91435 COVER LETTER START PROBLEM DESCRIPTION(S): PM79520 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: Lost spacemap updates in data sharing. * * * * Corrupted data can result in any of * * the following symptoms: * * - Incorrect output, INCORROUT. * * - ABEND04E RC00C90101, RC00C90102, * * RC00C90105, or RC00C902xx in * * various CSECTs. * * - Data/index inconsistencies reported * * by the CHECK INDEX utility. * * - Page regression reported by the * * DSN1LOGP utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a spacemap page P-lock was once held in X mode and then later negotiated to S mode, it may persist past the physical closure of the pageset. If this happens, and if the pageset is reopened and the page P-lock requested again, there is a timing window possible with the stealing of the old page buffer, which can leave DB2 thinking the P-lock is held when it has in fact been released. This can result in the spacemap page being regressed and data being broken. DB2 has been modified to ensure that S-mode page P-locks will always be released when the pageset is physically closed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79520 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CBP PM79520 DSNB1CFC PM79520 1 DSNB1GWB PM79520 DSNB1REL PM79520 DSNB1RRR PM79520 DSNB1RWI PM79520 DSNB5COM PM79520 DSNB5SCM PM79520 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79520 DSNB1CBP DSNB1CFC DSNB1GWB DSNB1REL DSNB1RRR DSNB1RWI DSNB5COM DSNB5SCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CBP DSNB1CFC DSNB1GWB DSNB1REL DSNB1RRR DSNB1RWI DSNB5COM DSNB5SCM LISTEND UK91435 COVER LETTER END UK91442 COVER LETTER START PROBLEM DESCRIPTION(S): PM80897 - **************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may issue two DSN9022I messages * * for STOP DB2 NORMAL COMPLETION when * * restarted in LIGHT mode and an RRS * * Indoubt thread was resolved during * * DB2 restart. * **************************************************************** * RECOMMENDATION: * **************************************************************** A timing window exists when restarting DB2 in LIGHT mode, and an RRS Indoubt UR is resolved during restart. A -STOP DB2 command is automatically generated when the final Indoubt UR is resolved. This can cause the WTO routine in DSNYASCP to issue two DSN9022I DSNYASCP 'STOP DB2' NORMAL COMPLETION messages instead of one DSN9022I message for 'START DB2' NORMAL COMPLETION, and one for 'STOP DB2' NORMAL COMPLETION. The WTO routine in DSNYASCP has been corrected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80897 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNYASCP PM80897 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80897 DSNYASCP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNYASCP LISTEND UK91442 COVER LETTER END UK91449 COVER LETTER START PROBLEM DESCRIPTION(S): PM77579 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users reading * * from, or writing to, a DFSMS managed and * * compressed dataset and specifying BUFNO= * * on the DD card * **************************************************************** * PROBLEM DESCRIPTION: UNLOAD, specifying an SMS-managed * * compressed SYSREC along with BUFNO= on * * the DD card results in an ABEND0C1 RC1 * * at IGG019VX +x'04A8' * * * * LOAD, utilizing an SMS-managed * * compressed SYSREC along with BUFNO= on * * the DD card results in either a hang of * * the utility or the utility abends with * * ABEND04E RC00E40071 at DSNUGSDA * * +X'584C' * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** Both of the LOAD and UNLOAD errors were the result of specifying BUFNO=2 on the SYSREC DD card when the data set was DFSMS managed and compressed. This resulted in only 2 buffers being allocated when the data set was opened. However, utility processing later changed that value by specifying that 4 buffers were to be used. For UNLOAD, this caused z/OS code to abend with an ABENDS0C1 RC00000001 (user buffer mismatch error) from IGG019VX OFFSET04A8. For LOAD, one of two problems could occur: 1. If the SYSREC data set contained a small number of rows, MSGDSNU032I (ERROR ON WORKFILE) and MSGDSNU040I (ERROR ACCESSING DDNAME SYSREC) were issued and then LOAD abended with ABEND04E RC00E40071. 2. If the SYSREC data set contained a large number of rows, the utility would hang. 1 ADDITIONAL KEYWORDS: DSNU032I DSNU040I Code has been changed to not reset the number of buffers to use when BUFNO has been specified and the data set is compressed and SMS managed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77579 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGSDA PM77579 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77579 DSNUGSDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGSDA LISTEND UK91449 COVER LETTER END UK91454 COVER LETTER START PROBLEM DESCRIPTION(S): PM61811 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who use both * * temporal support and replication products. * **************************************************************** * PROBLEM DESCRIPTION: DM1541 for DB2 10 for z/OS: A new * * DB2-supplied stored procedure has been * * implemented to set the internal * * option to disable recording of * * temporal history for a system-period * * temporal table and allow values to be * * specified for the special temporal * * column types previously mentioned. * * * * When this procedure is invoked by a * * connection, DB2 behavior (for static * * and dynamic SQL) is affected as * * follows: * * 1, historical rows are not written * * to a history table for update or delete * * operations. * * 2, an application may specify values * * (such as in an INSERT statement or * * UPDATE statement) for a row-begin, * * row-end, or transaction-start-ID * * column even though the column is * * defined as GENERATED ALWAYS, and * * these values will be stored in the * 1 * affected rows. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** DM1541 for DB2 for z/OS V10: A new DB2-supplied stored procedure has been implemented to set the internal option to disable recording of temporal history for a system-period temporal table and allow values to be specified for the special temporal column types previously mentioned. The DB2-supplied procedure is named, SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY. This stored procedure is not intended for general use. It is intended to be used by products that enable DB2 replication. When this procedure is invoked by a connection, DB2 behavior (for static and dynamic SQL) is affected as follows: 1, historical rows are not written to a history table for update or delete operations. 2, an application may specify values (such as in an INSERT statement or UPDATE statement) for a row-begin, row-end, or transaction-start-ID column even though the column is defined as GENERATED ALWAYS, and these values will be stored in the affected rows. Additional Keywords: SQLBITEMPORAL SQLSPTT DB2 code has been modified to implement the DCR. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61811 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71964: See PM71964 APAR/PTF text for additional information about why a REBIND is necessary. PM71964 corrects a problem of incorrect output may occur for an insert with subquery statement that satisfied the following conditions: 1. The source of the insert statement has timestamp data type. 2. The target of the insert statement is a char or varchar column. 3. There is sort involved for the INSERT statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. ACTION: ***Action for PM61811 (V10) This PTF adds a new DB2-supplied stored procedure, SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY, that can be 1 used to facilitate replication of temporal data by disabling recording of temporal history for a system-period temporal table and by allowing values to be specified for special temporal column types of row-begin, row-end, and transaction-start-ID. This stored procedure is not intended for general use. It is intended to be used by products that enable DB2 replication. If you have already installed or migrated to DB2 10 for z/OS, you need to perform the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Copy updated DB2 installation panels to alternate libraries (3) Update your customized copy of job DSNTIJRT (4) Update private copies of the DSNTIDxx CLIST input member (5) Run installation job DSNTIJRT to install new objects Detailed guidance for these actions is given further below. ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies CLIST members DSNTINST, DSNTINSV, and DSNTINS1 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your private copies of these CLISTs. You may also want to move them to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Copy updated DB2 installation panels to alternate libraries *********************************************************** * This action is required for all V10 customers who maintain * copies of the DB2 installation panels outside of SMP/E: *********************************************************** This PTF modifies the DB2 installation panel DSNTIPRL in the prefix.SDSNSPFP target library. If you keep the DB2 installation panels in a different library then after applying this PTF, you need to copy the updated panel to that library. ---------------------------------------------------------------- (3) Update customized copies of installation job DSNTIJRT *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies installation job DSNTIJRT in the prefix.SDSNSAMP target library. After you apply this PTF, you need to add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY GRANTTO() 1 Notes: (a) Always leave a blank line between each configuration control statement (b) Inspect the new configuration control statement and change the GRANTTO parameter setting to the authorization ID(s) that need access to the new routine. (c) Do not specify a WLMENV parameter in the configuration control statement for SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY. ---------------------------------------------------------------- (4) Update private copies of the DSNTIDxx CLIST input member *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF adds an entry to store values entered into the new field on installation panel DSNTIPRL: - RTL39ACL: GRANT EXECUTE setting for SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY You need to make the same changes to all private copies of your CLIST output (DSNTIDxx) member. In each such copy, add the following lines: RTL39ACL CHAR M NONE NONE Change to the setting you specified in action (3), above. ---------------------------------------------------------------- (5) Run installation job DSNTIJRT to install new objects *********************************************************** * This action is optional for V10 customers *********************************************************** After you have completed the above actions, run your updated copy of job DSNTIJRT to install and grant access to the new routine, SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. ---------------------------------------------------------------- COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@RIN PM61811 DSN@XAZP PM61811 DSNIDLER PM61811 DSNILREP PM61811 DSNINUKY PM61811 DSNIRELK PM61811 DSNISRTI PM61811 DSNITDLE PM61811 1 DSNLQCTL PM61811 DSNLQINA PM61811 DSNLTCM1 PM61811 DSNLTDSR PM61811 DSNLTRB1 PM61811 DSNTACT PM61811 DSNTESR PM61811 DSNTIDXA PM61811 DSNTIDXB PM61811 DSNTIJRT PM61811 DSNTINST PM61811 DSNTINSV PM61811 DSNTINS1 PM61811 DSNTIPRL PM61811 DSNTRIN PM61811 DSNTXAZP PM61811 DSNXEBR PM61811 DSNXECW PM61811 DSNXECWA PM61811 DSNXECWU PM61811 DSNXERT2 PM61811 DSNXGRTM PM61811 DSNXOCAS PM61811 DSNXOFF PM61811 DSNXOST PM61811 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61811 DSN@RIN DSN@XAZP DSNIDLER DSNILREP DSNINUKY DSNIRELK DSNISRTI DSNITDLE DSNLQCTL DSNLQINA DSNLTCM1 DSNLTDSR DSNLTRB1 DSNTACT DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRL DSNTRIN DSNTXAZP DSNXEBR DSNXECW DSNXECWA DSNXECWU DSNXERT2 DSNXGRTM DSNXOCAS DSNXOFF DSNXOST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDLER DSNILREP DSNINUKY DSNIRELK DSNISRTI DSNITDLE DSNLQCTL DSNLQINA DSNLTCM1 DSNLTDSR DSNLTRB1 DSNTACT DSNTRIN DSNTXAZP DSNXEBR DSNXECW DSNXECWA DSNXECWU DSNXERT2 1 DSNXGRTM DSNXOCAS DSNXOFF DSNXOST MACROS DSN@RIN DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRL LISTEND UK91454 COVER LETTER END UK91455 COVER LETTER START PROBLEM DESCRIPTION(S): PM72982 - **************************************************************** * USERS AFFECTED: All users of the DB2 XML Schema Registration * * (DSNXSR) database are affected by this * * change. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 installation jobs (DSNTIJSG in * * V9, DSNTIJNX in V9, and DSNTIJRT in * * V10) currently create the LOB table * * spaces in the DSNXSR database as NOT * * LOGGED. These table spaces are: * * SYSXSRA1, SYSXSRA2, SYSXSRA3, and * * SYSXSRA4. * **************************************************************** * RECOMMENDATION: Apply PTF * **************************************************************** DB2 installation jobs DSNTIJSG (in V9), DSNTIJNX (in V9), and DSNTIJRT (in V10) create the DB2 XSR (DSNXSR) database. By default, these jobs create the base table space, SYSXSR, as LOGGED so that changes to DSNXSR tables are recorded in the DB2 log. However, the four LOB table spaces - SYSXSRA1, SYSXSRA2, SYSXSRA3, and SYSXSRA4 - are created as NOT LOGGED, meaning that changes to LOB columns in the DSNXSR tables are not recorded in the DB2 log. This is poor practice, not only because it is inconsistent, but also because NOT LOGGED table spaces can be placed into LPL RECOVER-pending status if a rollback is required in response to a processing error. DSNTIJSG (V9), DSNTIJNX (V9), and DSNTIJRT/DSNTRIN (V10) are updated to create all table spaces in the DSNXSR database as LOGGED by default. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72982 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM72982 (V10) This PTF modifies DB2 installation program DSNTRIN to create the LOB table spaces in the DB2 XML Schema Registration (DSNXSR) database as LOGGED (by default) rather than NOT LOGGED. The affected table spaces are: SYSXSRA1, SYSXSRA2, SYSXSRA3, and SYSXSRA4. Use of the LOGGED attribute facilitates rollback and recovery by ensuring that changes made to the data in these table spaces are recorded in the DB2 log. This change has no effect on existing instances of these table spaces. If you have already created the DSNXSR database, you can alter these table spaces from NOT LOGGED to LOGGED by means of the following SQL statements: ALTER TABLESPACE DSNXSR.SYSXSRA1 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA2 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA3 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA4 LOGGED; Because altering the logging attribute of a table space from NOT LOGGED to LOGGED can place the table space in COPY-pending status, you might need to copy the table spaces after completing this operation. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@RIN PM72982 DSNTESR PM72982 DSNTRIN PM72982 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72982 DSN@RIN DSNTESR DSNTRIN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTRIN MACROS DSN@RIN DSNTESR LISTEND UK91455 COVER LETTER END UK91458 COVER LETTER START PROBLEM DESCRIPTION(S): PM76437 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS * * users of -ACCESS DATABASE SPACENAM PART * * MODE command on partitioned objects. * 1 **************************************************************** * PROBLEM DESCRIPTION: -ACCESS DATABASE SPACENAM MODE command * * with a PART list or range gets * * MSGDSNT315I and ABEND04E RC00C20305 * * DSNILSTS+1FD4 when the PART list or * * range includes a partition number that * * exceeds the object's highest partition * * number. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 encountered an 04E 00C20305 abend with message DSNT315I for the -ACCESS DATABASE SPACENAM PART MODE command when the PART list or range included a partition number that exceeded the object's highest partition number. For example, if object DSN8DA1A.DSN8SA1E has 4 partitions, any of these commands will get the abend: -ACCESS DB(DSN8DA1A) SP(DSN8SA1E) PART(1:99) MODE(OPEN) -ACCESS DB(DSN8DA1A) SP(DSN8SA1E) PART(1,99) MODE(OPEN) The abend was due to DB2 code erroneously handling the PART option. DB2 has been modified for the -ACCESS DATABASE SPACENAM PART MODE command code path to properly handle the PART option. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76437 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNILSTS PM76437 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76437 DSNILSTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILSTS LISTEND UK91458 COVER LETTER END UK91474 COVER LETTER START PROBLEM DESCRIPTION(S): PM59899 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of OLAP * * specifications * **************************************************************** * PROBLEM DESCRIPTION: OLAP specifications MAX and MIN may * 1 * return incorrect output if the input * * expression is null. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may return incorrect output for the OLAP specification result if the following is true: 1. The OLAP specification is MIN or MAX. 2. The first input value processed for the OLAP specification window is the null value and the result value for the row is null. The following is an example where the incorrout occurs: CREATE TABLE TMIN (C1 INT, C2 INT); INSERT INTO TMIN VALUES (NULL,1); INSERT INTO TMIN VALUES (1,2); SELECT MAX(C1) OVER (ORDER BY C2 ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW ) AS OLAPMAX , C1 FROM TMIN; +---------------------------------+ | OLAPMAX | C1 | +---------------------------------+ 1_| ? | ? | 2_| ? | 1 | +---------------------------------+ OLAPMAX should be 1 for the second row. DB2 has been fixed to correctly process the null value for MIN and MAX OLAP specifications. Additional keywords : SQLOLAP DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT SQLMIN SQLMAX COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59899 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM59899: See PM59899 APAR/PTF text for additional information about why a REBIND is necessary. PM59899 corrects an incorrect output problem for MAX or MIN olap specifications. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. 1 DB2BIND: ***Action for PM57492: See PM57492 APAR/PTF text for additional information about why a REBIND is necessary. PM57492 corrects an incorrect output problem where the join predicate involves graphic data and there is a derived predicate for inner table of a sort merge join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGSFL PM59899 DSNXRWND PM59899 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59899 DSNXGSFL DSNXRWND THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSFL DSNXRWND LISTEND UK91474 COVER LETTER END UK91493 COVER LETTER START PROBLEM DESCRIPTION(S): PM76334 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * datetime expressions * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 can happen at * * location DSNXGRDS.DSNXERT OFFSET368C * * when casting from date, time, timestamp * * to character. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000038 can happen at location DSNXGRDS.DSNXERT OFFSET368C when casting date, time, timestamp to characters. This problem may occur intermittently because DB2 does not check for an error SQLCODE before padding the result with blanks. The padding may cause an overlay of storage and/or subsequent abend. The following query illustrates how this abend may occur if the datetime exit returns an error. SELECT CHAR(LASTUSED,LOCAL) 1 FROM SYSIBM.SYSPACKAGE WHERE NAME = 'DSNTIAD' DB2 has been changed to check the return code before padding the result with blanks. Additional keywords : SQLDATE SQLTIME SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76334 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRTIM PM76334 DSNXRTI9 PM76334 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76334 DSNXRTIM DSNXRTI9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRTIM DSNXRTI9 LISTEND UK91493 COVER LETTER END UK91515 COVER LETTER START PROBLEM DESCRIPTION(S): PM76271 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of spatial indexes. * **************************************************************** * PROBLEM DESCRIPTION: Invalid spatial index keys found after * * a CREATE INDEX on a spatial column of * * a table. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** Multiple rows were inserted into a table with a spatial column that included spatial data followed by rows which included empty spatial objects. A subsequent CREATE INDEX was run to create a spatial index for that column. Invalid keys were generated for the empty spatial data. Additional keywords: INCORROUT SQLINCORR SQLINCORROUT DB2INCORR/K DB2INCORR/M CREATE INDEX has been modified to generate the correct spatial index keys. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76271 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: After applying APAR PM76271, the users of spatial indexes should complete the following steps: (1) Check if the table has any empty spatial objects. Example: Run the following statement to check if the spatial table (SPATIALTABLE) has an empty spatial object for a column with the spatial data type (SPATIALCOLUMN). SELECT COUNT(*) FROM SPATIALTABLE WHERE DB2GSE.ST_NUMPOINTS(SPATIALCOLUMN) IS NULL; If the above select returns a value greater than 0 then continue with the second step: (2) Use DSN5SCLP with option drop_idx and create_idx to drop and create a new spatial index for that table. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURBXT PM76271 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76271 DSNURBXT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURBXT LISTEND UK91515 COVER LETTER END UK91525 COVER LETTER START PROBLEM DESCRIPTION(S): PM70834 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS customers who may do a * * mass delete of a table. * **************************************************************** * PROBLEM DESCRIPTION: TOTALROWS, DATASIZE, and NPAGES in * * SYSTABLESPACESTATS table may have * * negative values after a LOAD followed * * by a mass delete on a table. * **************************************************************** * RECOMMENDATION: Apply appropriate PTF. * **************************************************************** TOTALROWS, DATASIZE, and NPAGES in SYSTABLESPACESTATS table may contain negative values. This may occur after a LOAD utility corrects unique index violations or index evaluation errors by removing rows from a table during the INDEXVAL phase, followed by a mass delete operation on the table. DB2 will be updated to set TOTALROWS, DATASIZE, and NPAGES 1 to correct values in the SYSTABLESPACESTATS table following a mass delete. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70834 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISEGD PM70834 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70834 DSNISEGD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISEGD LISTEND UK91525 COVER LETTER END UK91533 COVER LETTER START PROBLEM DESCRIPTION(S): PM78077 - **************************************************************** * USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE * * command with the USE or LPL keywords * **************************************************************** * PROBLEM DESCRIPTION: The -DISPLAY DATABASE command invoked * * with the USE or LPL keyword could * * generate extraneous or redundant * * lines for partitioned objects * **************************************************************** * RECOMMENDATION: * **************************************************************** The -DISPLAY DATABASE command invoked with the USE or LPL keywords could generate extraneous or redundant lines for partitioned objects. Changed the -DISPLAY DATABASE command with the USE or LPL keywords to eliminate extraneous or redundant partition information. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78077 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTDMUL PM78077 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78077 DSNTDMUL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNTDMUL LISTEND UK91533 COVER LETTER END UK91534 COVER LETTER START PROBLEM DESCRIPTION(S): PM74945 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * with queries containing a join. * **************************************************************** * PROBLEM DESCRIPTION: When an index has a low CLUSTERRATIO * * and/or high DATAREPEATFACTOR, DB2 may * * incorrectly determine that it is more * * efficient to use that index to access * * the table as the inner table. This * * may lead to poor query performance. * **************************************************************** * RECOMMENDATION: * **************************************************************** During query optimization, DB2 takes into account the estimated number of qualified pages compared to the bufferpool size. If the number of estimated qualified pages after local predicates are applied on a given index is small enough, DB2 may choose to use the index to access the inner table to take advantage of cached pages in the bufferpool for each probe. When the CLUSTERRATIO of the index is low and/or the DATAREPEATFACTOR of the index is high, DB2 can underestimate the cost of this access path. This happens due to an inconsistency in the way the cost is calculated when using the index to access the table as the inner versus the outer. As a result of this problem, DB2 may choose an inefficient access path resulting in poor query performance. This APAR adds an online-changeable subsystem parameter in DSN6SPRM called OPTIOPIN that controls whether DB2 uses this improved costing. Valid settings are: - ENABLE : DB2 uses the improved costing formula ==> This is the default setting in V10 - DISABLE: DB2 does not use the improved costing formula ==> This is the default setting in V9 Additional Keywords: SQLPERFORMANCE SQLACCESSPATH SQLNLJ SQLHBJ DB2 has been modified so that the costing logic is consistent between inner table and outer table costing. Set zparm OPTIOPIN to ENABLE to take advantage of this improved costing logic. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM74945 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75775: See PM75775 APAR/PTF text for additional information about why a REBIND is necessary. PM75775 corrects a problem of poor query performance for OPTIMIZE FOR 1 ROW when no sort and no join will be performed, and there is an index or indexes which contain all the columns in the predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM74945: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM74945 corrects a problem in which DB2 may choose an access path with an inefficient index used for the inner table of a nested loop join or hybrid join. To make this fix effective for a static application, it must be rebound with new zparm OPTIOPIN set to ENABLE after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. ACTION: ***Actions for APAR PM74945 (V10) This PTF adds an online-changeable subsystem parameter in DSN6SPRM called OPTIOPIN that controls whether DB2 is to use an enhancement to more accurately estimate the cost of accessing the inner table of a join that involved index and data access. Valid settings are: - ENABLE : DB2 uses the improved costing formula ==> This is the default setting - DISABLE: DB2 does not use the improved costing formula If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Rebind static applications that are affected by this change Detailed guidance for these actions follows: ---------------------------------------------------------------- 1 (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter OPTIOPIN=, where is DISABLE or ENABLE, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding OPTIOPIN here, the value will be set to the default of ENABLE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ==> This action is required for all customers This PTF adds an entry for OPTIOPIN to the CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following lines: OPTIOPIN CHAR M DISABLE ENABLE Change to the value you specified for OPTIOPIN in step (2), above. End of actions for APAR PM74945 (V10) COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM74945 DSNDQWPZ PM74945 DSNDSPRM PM74945 DSNTIDXA PM74945 DSNTIDXB PM74945 DSNTIJUZ PM74945 DSNTINST PM74945 DSNTXAZP PM74945 1 DSNWZIFA PM74945 DSNWZIF9 PM74945 DSNXOCCX PM74945 DSNXOMPS PM74945 DSN6SPRM PM74945 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74945 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSNWZIF9 DSNXOCCX DSNXOMPS DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP DSNWZIFA DSNWZIF9 DSNXOCCX DSNXOMPS MACROS DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSN6SPRM LISTEND UK91534 COVER LETTER END UK91557 COVER LETTER START PROBLEM DESCRIPTION(S): PM80462 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * BIND COPY of a native SQL procedure * * package. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * LOOPING DSNTBSPL * * * * PROBLEM SCENARIO: * * * * The reported looping error occurred * * when attempting a BIND COPY of a * * native SQL procedure which does not * * have any SQL statements. * * * * For example, the code portion of a * * CREATE PROCEDURE might look like this: * 1 * * * P1: * * BEGIN * * DECLARE SQLCODE INTEGER ; * * DECLARE EXIT HANDLER FOR SQLEXCEPTION * * SET SQLCODE_OUT = SQLCODE ; * * DECLARE CONTINUE HANDLER FOR SQLWARNING * * SET SQLCODE_OUT = SQLCODE ; * * SET SQLCODE_OUT = SQLCODE ; * * END P1 ? * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: DB2 assumed that there would be SQL statements in the native SQL procedure and as a result did not check for a "record not found" condition. Looping ensues, and the job must be cancelled. PROBLEM CONCLUSION: DB2 has been fixed to check for statement records when looping for a BIND COPY. ADDITIONAL KEYWORDS: BIND COPY SQLNATIVESQLPL LOOPING INFINITE ENDLESS LOOP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80462 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBCM5 PM80462 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80462 DSNTBCM5 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBCM5 LISTEND UK91557 COVER LETTER END UK91560 COVER LETTER START PROBLEM DESCRIPTION(S): PM77114 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of PREPARE statements * * with DB2 Dynamic Statement Cache and * * IFCID 316 or class 29 monitor trace. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 * * at DSNXGRDS . DSNXEIST +F82 * * on a Dynamic Statement Cache * 1 * LONG PREPARE. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 Dynamic Statement Cache (DSC) is active, the DSC LONG PREPARE process inserts the dynamically PREPARed statement in the global cache. When there is not enough space to insert a new statement, DB2 drives the LRU process to remove an old statement in the cache to have space for the new statement. When a statement is being removed from the cache, DB2 may write the IFCID 316 trace record. While tracing the IFCID 316 record, an SQLCODE can occur (such as a conversion error). This negative SQLCODE can affect the LONG PREPARE process of a new statement, which results in undoing the PREPARE of the statement. However, this statement is still advertently inserted in the cache without valid dependency information. The internal control block of the dependency information can be reused for another cached statement later. This inconsistency is detected on a subsequent statement invalidation process resulting in the reported abend. DB2 code has been modified to not insert a statement in the cache, if an error was hit during the LRU process. RELATED KEYWORDS: 04E AB04E IFCID316 0316 OFFSETF82 STMTCACHE SQLDYNSTMTCACHE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77114 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM76278: See PM76278 APAR/PTF text for additional information about why a REBIND is necessary. PM76278 corrects a problem of ABEND04E RC00C90101 at DSNGEPLC : 500D or ABEND0C1 or ABEND0C4 at an unknown PSW due to a bad branch when running static DML workloads. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEGBK PM77114 DSNGEPIS PM77114 DSNXEDS1 PM77114 DSNXESX PM77114 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77114 DSNGEGBK DSNGEPIS DSNXEDS1 DSNXESX 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEGBK DSNGEPIS DSNXEDS1 DSNXESX LISTEND UK91560 COVER LETTER END UK91561 COVER LETTER START PROBLEM DESCRIPTION(S): PM78551 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * views that contain UNION/UNION ALL. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 DSNXOTDA OFFSET0926 * * may occur for an SQL statement that * * references to a view that satisfies * * the following conditions: * * 1. The view contains UNION/UNION ALL * * 2. The statement that references to * * this view contains predicates that * * can cause some of the branches of the * * UNION/UNION ALL inside the view to be * * pruned. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000010 DSNXOTDA OFFSET0926 may occur for an SQL statement that references to a view that satisfies the following conditions: 1. The view contains UNION/UNION ALL 2. The statement that references to this view contains predicates that can cause some of the branches of the UNION/UNION ALL inside the view to be pruned. An example of the possible failing case is like : CREATE VIEW V1 (VC1) AS SELECT C1 FROM T1 WHERE C1 = 1 UNION ALL SELECT C2 FROM T2 WHERE C2 = 2 UNION ALL SELECT C3 FROM T3 WHERE C3 = 3 UNION ALL SELECT C4 FROM T4 WHERE C4 = 4; SELECT * FROM V1 WHERE VC1 IN (1,4); An abend may occur for the SELECT statement above because DB2 1 does not handle the view correctly after the branches of the UNION/UNION ALL inside the view are pruned. DB2 was fixed to handle the view correctly when some of the branches of the UNION/UNION ALL inside view are pruned. Additional KeyWords: SQLUNION SQLUNIONALL SQLVIEW SQLPRUNING COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78551 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTDA PM78551 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78551 DSNXOTDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTDA LISTEND UK91561 COVER LETTER END UK91563 COVER LETTER START PROBLEM DESCRIPTION(S): PM79979 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * * of user defined functions with * * Decimal floating-point data type. * **************************************************************** * PROBLEM DESCRIPTION: 1. SQLCODE -401 may be issued for * * an SQL statement that satisfies * * the following conditions: * * a. The statement references to an * * user defined function in a * * predicate. * * b. The input to the user defined * * function is a SET function which * * returns a numeric data type. * * c. The data type of the parameter of * * the user defined function is * * defined as decimal floating-point. * * * * 2. Abend ABND04E at DSNXGRDS DSNXGDT2 * * M205 could occur for an SQL statement * * that satisfies the following conditions * * a. The statement references to a NULL * * constant in a predicate. * * b. The result data type of the NULL * * constant is decimal floating-point. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** 1. SQLCODE -401 may be issued for an SQL statement that satisfies the following conditions: a. The statement references to an user defined function in a predicate. b. The input to the user defined function is a SET function which returns a numeric data type. c. The data type of the parameter of the user defined function is defined as decimal floating-point. For Example, CREATE TABLE DB2DBA.EMP2 ( EMPNO CHAR(10) , AMT DECIMAL(17,2) ) CREATE FUNCTION TEST (A DECFLOAT(34) , B DECFLOAT(34) ) RETURNS DEC(31,10) NO EXTERNAL ACTION DETERMINISTIC RETURN A/B; SELECT X FROM ( SELECT TEST(SUM(AMT),1000000) AS X FROM DB2DBA.EMP2 GROUP BY EMPNO ) T1 WHERE X <> 1 WITH UR; SQLCODE -401 may be issued incorrectly for the SELECT statement above because DB2 did not handle the decimal floating-point data type in the user defined function TEST correctly. 2. Abend ABND04E at DSNXGRDS DSNXGDT2 M205 could occur for an SQL statement that satisfies the following conditions a. The statement references to a NULL constant in a predicate. b. The result data type of the NULL constant is decimal floating-point. For Example, CREATE TABLE DB2DBA.EMP2 ( EMPNO CHAR(10) , AMT DECFLOAT(34) ) SELECT * FROM DB2DBA.EMP2 WHERE (CASE WHEN AMT IS NULL THEN NULL ELSE AMT/2 END) > 0; Abend could occur for the statement above because DB2 did not handle the decimal floating-point NULL constant correctly. DB2 was fixed to 1. Allow all numeric data types to be compatible with decimal floating-point data type. 1 2. Handle the decimal floating-point constant NULL correctly. Additional Keywords: SQLNULL SQLDECFLOAT SQLUDF COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79979 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM78249 APAR/PTF text for additional information about why a REBIND is necessary. PM78249 corrects a problem that ABEND0C7 RC00000000 at the location DSNXGRDS DSNXRDEC OFFSET59BC could happen for an SQL statement that satisfies all of the following conditions: 1. It contains a table expression with UNION ALL. 2. It contains a HAVING predicate with scalar function ABS, SIGN, CEILING or ROUND. 3. The scalar function contains a SUM function in the input expression. 4. The SUM function is on a DECIMAL column of the table expression. 5. The DECARTH DECP value is DEC31 or 31, and the DECIMAL column is with precision 15. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEXC PM79979 DSNXOEXE PM79979 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79979 DSNXOEXC DSNXOEXE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXC DSNXOEXE LISTEND UK91563 COVER LETTER END UK91565 COVER LETTER START PROBLEM DESCRIPTION(S): PM77032 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of DGTT tables. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc000C90101 can occur at * * location DSNILGCL:5001 when the thread * 1 * is aborted. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc000C90101 can occur at location DSNILGCL:5001 when the thread is aborted and went through the commit phase 2 process. The abend is caused by a residual flag which indicates to write a log record during the cleanup of DGTT tables which should not write a log for DGTTs during the abort process. DB2 has been modified to clear the residual flag left in the commit I phase after the abort at beginning of commit phase II. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77032 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICMT2 PM77032 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77032 DSNICMT2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICMT2 LISTEND UK91565 COVER LETTER END UK91573 COVER LETTER START PROBLEM DESCRIPTION(S): PM77509 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of * * dynamic statements when * * Profile Manager is activated * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E30001 at DSNT1SRQ +0D10 * * on a PREPARE or EXECUTE IMMEDIATE * * SQL statement execution. * **************************************************************** * RECOMMENDATION: * **************************************************************** When Profile Manager is active, for both dynamic and static statements, DB2 processes profile resolution to determine if any profile factor needs to be chosen for the access path selection of a statement. The profile resolution is based on AUTHID, IP Address, PLANNAME, COLLECTION ID, and PACKAGE NAME information of the statement. . For dynamic statements, the value of CURRENT SQLID special register is used for AUTHID for profile resolution. In the reported case, CURRENT SQLID was set to a blank value prior to 1 the PREPARE of a dynamic statement and the blank AUTHID caused the reported abend since a blank AUTHID is disallowed for profile resolution. DB2 code has been changed to tolerate a blank AUTHID for profile resolution for dynamic statements. Additional Keywords: OFFSET0D10, 00E30001, PICD10 O4E, SO4E, AB04E COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77509 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNT1SRQ PM77509 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77509 DSNT1SRQ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNT1SRQ LISTEND UK91573 COVER LETTER END UK91575 COVER LETTER START PROBLEM DESCRIPTION(S): PM79079 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and 10 for z/OS * * of Profile Manager for modeling * * a product subsystem. * **************************************************************** * PROBLEM DESCRIPTION: A profile attribute row is rejected * * when 0(zero) is specified in the * * ATTRIBUTE2 column for MAX_RIDBLOCKS * * attribute keyword. * **************************************************************** * RECOMMENDATION: * **************************************************************** Profile Manager can be used to model a product subsystem in a test subsystem by setting a production environment. For the attribute keywords of the product system modeling, including the MAX_RIDBLOCKS keyword, the acceptable attribute values are non-zero positive integer numbers. Therefore, for the product system modeling keywords, any profile attribute row with 0(zero) value in the ATTRIBUTE2 column is rejected during START PROFILE process. For the MAXRBLK subsystem parameter for RID POOL SIZE in a subsystem, however, 0(zero) is a acceptable value. As a result, it was not allowed to model a product system 1 that has 0(zero) RID POOL SIZE using Profile Manager. DB2 has been modified to support 0(zero) value in the ATTRIBUTE2 column for the MAX_RIDBLOCKS keyword to model a product subsystem that has 0(zero) RID POOL SIZE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79079 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNT1RSP PM79079 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79079 DSNT1RSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNT1RSP LISTEND UK91575 COVER LETTER END UK91577 COVER LETTER START PROBLEM DESCRIPTION(S): PM77562 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of the CREATE TRIGGER statement that defines * * a TRIGGER that contains at least 20 UNION or * * UNION ALL statements. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E2000D can occur at * * location DSNXGXTB DSNSVSFB OFFSET0848 * * when creating a TRIGGER that contains * * at least 20 UNION or UNION ALL * * statements. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E2000D can occur at location DSNXGXTB DSNSVSFB OFFSET0848 when creating a TRIGGER that contains at least 20 UNION or UNION ALL statements. The following CREATE TRIGGER statement is an example of a failing case. CREATE TRIGGER TRIG_01 INSTEAD OF INSERT ON T1 REFERENCING NEW_TABLE AS N FOR EACH ROW MODE DB2SQL BEGIN ATOMIC INSERT INTO T1 1 SELECT * FROM N WHERE N.TKKEY < 2240001 UNION ALL SELECT * FROM N WHERE N.TKKEY BETWEEN 2240001 AND 2500000 UNION ALL ... repeat the above UNION ALL statements ... END! The code in DB2 has been modified to correct the conditions leading to the abend when executing a CREATE TRIGGER statement that defines a TRIGGER that contains at least 20 UNION or UNION ALL statements. Additional Keywords: SQLUNIONALL SQLUNION SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77562 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGRM1 PM77562 DSNXGRTS PM77562 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77562 DSNXGRM1 DSNXGRTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGRM1 DSNXGRTS LISTEND UK91577 COVER LETTER END UK91605 COVER LETTER START PROBLEM DESCRIPTION(S): PM79953 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * predicate with an arithmetic expression * * which contains a host variable and an * * integer constant as its operators. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may choose an inefficient access * * path for an SQL statement satisfies * * the following conditions: * * 1.it contains a VALUE COMPARE predicate * * or a BETWEEN predicate with * * arithmetic expression, * * 2.the arithmetic expression has host * 1 * variable and integer constant as its * * operator, * * 3.matching index access is possible. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may choose an inefficient access path for an SQL statement satisfies the following conditions: 1.it contains a VALUE COMPARE predicate or a BETWEEN predicate with an arithmetic expression, 2.the arithmetic expression has host variable and integer constant as its operators, 3.matching index access is possible for the query. In the following example, DB2 may ignore the matching index access: CREATE TABLE T1(C1 DECIMAL(11,0)); CREATE UNIQUE INDEX INDEX1 ON T1(C1); SELECT C1 FROM T1 WHERE C1=:HV+1; DB2 has been updated to choose a more efficient access path for the above scenario. Addtional Keywords: SQLACCESSPATH SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79953 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM79953: See PM79953 APAR/PTF text for additional information about why a REBIND is necessary. PM79953 corrects a problem of an inefficient access path being chosen by DB2 for a SQL statement which satisfies the following conditions: 1.it contains a VALUE COMPARE predicate or a BETWEEN predicate with an arithmetic expression, 2.the arithmetic expression has a host variable or parameter marker and integer constant as its operators, 3.matching index access is possible for the query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM76452: See PM76452 APAR/PTF text for additional information about why a REBIND is necessary. PM76452 corrects a problem of ABEND0C7 RC0 at DSNXRDEC +59BC when a transitive closure predicate takes the form of column = 1 host variable where the column is a not null decimal and a NULL value was sent in during execution time for the host variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMEX PM79953 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79953 DSNXOMEX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMEX LISTEND UK91605 COVER LETTER END UK91608 COVER LETTER START PROBLEM DESCRIPTION(S): PM79679 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: During a DB2 shutdown, RTS notify * * threads may continue to run after * * the Buffer Manager gets rid of needed * * storage, resulting in abends of the * * notify threads. * **************************************************************** * RECOMMENDATION: Apply the appropriate PTF. * **************************************************************** During a DB2 shutdown, the RTS daemon terminates processing and the Buffer Manager gets rid of needed storage, such as buffer pools. However, some RTS notify threads may continue to run after the RTS daemon terminates. This may cause the notify threads to abnormally terminate with ABEND0C4. The code is updated to have all RTS notify threads finish processing before the RTS daemon terminates and the Buffer Manager cleans up storage. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79679 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTLCTL PM79679 DSNTLEXT PM79679 DSNTLNOT PM79679 1 DSNTLPLK PM79679 DSNTLPNE PM79679 DSNTLSTA PM79679 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79679 DSNTLCTL DSNTLEXT DSNTLNOT DSNTLPLK DSNTLPNE DSNTLSTA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLCTL DSNTLEXT DSNTLNOT DSNTLPLK DSNTLPNE DSNTLSTA LISTEND UK91608 COVER LETTER END UK91643 COVER LETTER START PROBLEM DESCRIPTION(S): PM67402 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of an access * * path using predicate pushdown * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXGRDS * * DSNXEFDA M500 for a query using an * * access path with predicate pushdown * **************************************************************** * RECOMMENDATION: * **************************************************************** The abend is issued by DB2 if a FETCH is done against a cursor after a negative SQLCODE has occurred on the previous fetch. The abend occurs if the query is bound on Version 10 and predicate pushdown has been chosen by the optimizer. The following scenario shows the abend case : CREATE TABLE T1 (C1 VARCHAR(5), C2 INTEGER); INSERT INTO T1 VALUES ('A',1); INSERT INTO T1 VALUES ('1',1); EXEC SQL DECLARE C1 CURSOR FOR SELECT C1,C2 FROM T1 WHERE CAST(C1 AS INTEGER) = 1; EXEC SQL OPEN C1; EXEC SQL FETCH C1 INTO :i :j; -- SQLCODE such as -420 returned EXEC SQL FETCH C1 INTO :i :j; -- abend 04E in DSNXEFDA A FETCH after the SQLCODE abends because DB2 has no position on the cursor. The abend only occurs if the SQLCODE is returned on the first fetch. Alternate symptoms of the problem ------------------------------------------------------------ 1 One symptom of the problem occurs if the first FETCH returns a row of data without error and then an SQLCODE is returned on the second row (or nth row). In this case, DB2 will return the same error SQLCODE for all subsequent fetches because the cursor is not advanced when the SQLCODE is issued. It is also possible to update the wrong row with an UPDATE WHERE CURRENT OF cursor statement after a FETCH that returns a negative SQLCODE. Here is an example : CREATE TABLE T1 (C1 VARCHAR(5), C2 INTEGER ); INSERT INTO T1 VALUES ('A',1); EXEC SQL DECLARE C1 CURSOR FOR SELECT * FROM T1 WHERE C2 = ( SELECT C2 FROM T2 WHERE CAST(T1.C1 AS INTEGER) = T2.C1) FOR UPDATE; EXEC SQL OPEN C1; EXEC SQL FETCH C1 INTO :x,:y; EXEC SQL UPDATE T1 SET C1 = 5 WHERE CURRENT OF C1; The FETCH returns an SQLCODE -420 and the UPDATE incorrectly updates the row in the table. The predicate must be stage 2 for the update problem to occur. DB2 has been fixed to close the cursor when a negative SQLCODE is returned while processing a predicate. Subsequent fetches from the cursor will return -501 SQLCODE. An UPDATE after the FETCH sqlcode will return a -507 SQLCODE. A CLOSE CURSOR after the FETCH sqlcode will return a -501 SQLCODE. DB2 10 for z/OS SQL Reference currently documents this behavior under the FETCH CURSOR SQL statement description. This apar adds another scenario where the cursor is closed. "CURSOR POSITION AFTER EXCEPTION CONDITION: If an error occurs during the execution of a fetch operation, the position of the cursor and the result of any later fetch is unpredictable. It is possible for an error to occur that makes the position of the cursor invalid, in which case the cursor is closed." Additional keywords : SQLPREDPUSHDOWN SQLUPDATE SQLCODE501 SQLCODE507 DB2INCORR/K INCORROUT INCORROUT SQLINCORR OFFSETM500 AB04E COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67402 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM67402: This PTF corrects the following two problems : 1. ABEND04E RC00E70005 at DSNXGRDS DSNXEFDA M500 on a 1 fetch statement. 2. Update of the wrong row with a UPDATE WHERE CURRENT OF statement. Both problems occur if the previous SQL executed was a FETCH from a cursor which returned an error SQLCODE. The position of a cursor is unpredicatable after an error. DB2 has been fixed to close the cursor when a negative SQLCODE is returned while processing a predicate. Subsequent fetches from the cursor will return -501 SQLCODE. An UPDATE after the FETCH sqlcode will return a -507 SQLCODE. A CLOSE CURSOR after the FETCH sqlcode will return a -501 SQLCODE. DB2 10 for z/OS SQL Reference currently documents this behavior under the FETCH CURSOR SQL statement description. This apar adds another scenario where the cursor is closed. "CURSOR POSITION AFTER EXCEPTION CONDITION: If an error occurs during the execution of a fetch operation, the position of the cursor and the result of any later fetch is unpredictable. It is possible for an error to occur that makes the position of the cursor invalid, in which case the cursor is closed." Application code should handle a -501 SQLCODE on a FETCH or CLOSE CURSOR SQL statement if a previous error has occurred. UPDATE should also handle the -507 SQLCODE. A new reason (bullet 3) will be added to the list under the "Programmer response" for SQLCODE -501 : ============================================================= Programmer response Check for a previous SQL return code that might have closed the cursor. - Commit and rollback operations close cursors. - SQL return codes -404, -652, -679, -802, -901, -904,  -909, -910, -911, -913, and -952 might force the cursor to close. - An error SQLCODE during predicate processing closes the cursor. After the cursor is closed, any fetches or close cursor statements will receive SQLCODE -501. If no previous SQL return codes have been issued, correct the logic of the application program to ensure that the cursor is open at the time the FETCH or CLOSE statement is processed. ============================================================== COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEBR PM67402 DSNXEBR9 PM67402 DSNXERT PM67402 DSNXRCAS PM67402 DSNXRNUL PM67402 DSNXRRP PM67402 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67402 DSNXEBR DSNXEBR9 DSNXERT DSNXRCAS DSNXRNUL DSNXRRP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEBR DSNXEBR9 DSNXERT DSNXRCAS DSNXRNUL DSNXRRP LISTEND UK91643 COVER LETTER END UK91646 COVER LETTER START PROBLEM DESCRIPTION(S): PM80266 - **************************************************************** * USERS AFFECTED: All DB2 Users preparing for a new release * * of DB2. * **************************************************************** * PROBLEM DESCRIPTION: DB2 internal change to support future * * functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR does not address or fix any problem in DB2. It contains changes in support of future function. This APAR does not have any external symptoms. The code logic is added to support a future new function. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80266 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOBNQ PM80266 DSNXOD0 PM80266 DSNXOD0A PM80266 DSNXOD0P PM80266 DSNXOPTI PM80266 DSNXOSJH PM80266 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80266 DSNXOBNQ DSNXOD0 DSNXOD0A DSNXOD0P DSNXOPTI DSNXOSJH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBNQ DSNXOD0 DSNXOD0A 1 DSNXOD0P DSNXOPTI DSNXOSJH LISTEND UK91646 COVER LETTER END UK91647 COVER LETTER START PROBLEM DESCRIPTION(S): PM75619 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V9 and V10 users who use * * index-on-expression (IOE) and join tables * * with multiple CCSIDs. * * * * Also for all DB2 for z/OS V10 users who use DB2 * * REAL-TIME STATISTICS for REORG suggestions. * **************************************************************** * PROBLEM DESCRIPTION: There are two problem fixed by this * * APAR. * * * * The first problem may occur on both V9 * * and V10. DB2 may produce incorrect * * output when a UNICODE table joins to * * an EBCDIC view which is a UNION ALL, * * and at the same time, when * * index-on-expression (IOE) is used * * for that query. * * * * For example, * * * * CREATE VIEW MY_EBCDIC_VIEW (...) AS * * (SELECT DISTINCT ... * * FROM ... * * WHERE ... * * UNION ALL * * SELECT DISTINCT ... * * FROM ... * * WHERE ...); * * * * SELECT ... * * FROM MY_UNICODE_TABLE, MY_EBCDIC_VIEW * * WHERE ...; * * * * And for the query, DB2 chooses IOE * * to access MY_UNICODE_TABLE. * * * * The second problem is V10 only. DB2 * * may not issue a REORG suggestion as * * it should. This problem is related to * * DB2 V10 REAL-TIME STATISTICS. * **************************************************************** * RECOMMENDATION: * **************************************************************** There are two problem fixed by this APAR. 1 The first problem may occur on both V9 and V10. DB2 may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. It occurs because DB2 missed the multiple CCSID handling when IOE is used but the index access did not consume all the predicates on index keys for index matching or screening. The second problem is V10 only. DB2 may not issue a REORG suggestion as it should because the access path's senstivity to table clustering is not detected correctly. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K REALTIMESTATS SQLCCSID SQLINDEXONEXP SQLVIEW SQLUNIONALL The two problems are fixed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75619 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. APAR PM75619 corrects two problems. The first problem occurs on both V9 and V10. A query may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. The second problem occurs on V10 only. DB2 may not issue a REORG suggestion as it should. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGP PM75619 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75619 DSNXOGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGP LISTEND UK91647 COVER LETTER END UK91659 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM80175 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the LOAD utility. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E40005 after MSGICE046A * * SORT CAPACITY EXCEEDED in DFSORT when * * loading data from a variable length * * SYSREC data set with large LRECL but * * small actual records. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD DATA attempts to estimate the number of records in the input data set by looking at the record length and the number of allocated pages. For variable length data sets there can be a discrepancy between defined LRECL and actual average length of the records in the data set so that the resulting estimate can be significantly smaller than the actual number. When this low estimate is passed to DFSORT with FILSZ=Un it is possible that DFSORT is choosing a sort path which can not use additional sort work data sets to compensate for a bad estimate and then will fail with ICE046A SORT CAPACITY EXCEEDED. Code has been changed to pass estimates to DFSORT using FILSZ=En when the number of records can not be determined properly from the input (variable length SYSREC, SYSREC on tape, LOAD INCURSOR) and no SORTKEYS or NUMRECS was specified. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80175 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGLSR PM80175 DSNUGMRP PM80175 DSNUGSOR PM80175 DSNUGSRP PM80175 DSNUGSRT PM80175 DSNUKXSR PM80175 DSNURELD PM80175 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80175 DSNUGLSR DSNUGMRP DSNUGSOR DSNUGSRP DSNUGSRT DSNUKXSR DSNURELD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGLSR DSNUGMRP DSNUGSOR DSNUGSRP DSNUGSRT 1 DSNUKXSR DSNURELD LISTEND UK91659 COVER LETTER END UK91689 COVER LETTER START PROBLEM DESCRIPTION(S): PM78872 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS users * * of SQL UPDATE of parent key in a referential * * integrity relationship, when the parent key * * is parent to at least two dependent (child) * * tables * **************************************************************** * PROBLEM DESCRIPTION: SQL UPDATE of parent key (primary key) * * that received uniqueness violation * * SQLCODE803 -803 (and the parent key is * * parent to at least two dependent * * tables) may leave the parent key index * * out of synch with its table, which in * * subsequent processing may be reflected * * in any of the following symptoms: * * * * RC00C90206 DSNIIDIS ERQUAL5002 * * or * * RC00C90206 DSNIDIFS ERQUAL5007 * * or * * MSGDSNU709I during CHECK INDEX * * (NO INDEX ENTRY FOR ROW) * * or * * any other unpredictable data integrity * * symptom * * or * * potential incorrout when the parent key * * index is used in scans * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQL UPDATE was issued on a table with a parent key that is parent to at least two dependent tables' foreign keys. During parent key index insert of the new value, uniqueness violation occurred (SQLCODE -803), which was normal given that the value already existed. During cleanup processing for this condition, a workfile that was built for the purpose of deferred key processing was deleted and its segment deallocated, however during this operation, a bit that signifies that some logging was done (deletion of the old index entry) was accidentally reset, which after the workfile deletion led to bypassing of the log record undo code. As a result, the unique index entry deletion was not undone, which led to the row in the table missing its entry in the index. 1 Later on (could even be days later), an SQL UPDATE tried to update the same row that the first SQL UPDATE had targeted. When this second update tried to update the index entry representing the row, the index entry was not found, which in the reported case led to the 00C90206 abend in DSNIIDIS. Depending on the operation that first runs into this missing index entry condition, other symptoms are possible also, as documented above in the problem description. Code has been changed to ensure that the bit that controls undo of logging activity is properly saved/restored when in cleanup processing for the SQLCODE -803 condition. Additional keywords: SQLUPDATE SQLINCORROUT SQLINCORR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78872 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRICH PM78872 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78872 DSNIRICH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRICH LISTEND UK91689 COVER LETTER END UK91693 COVER LETTER START PROBLEM DESCRIPTION(S): PM69806 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS OF LISTDEF UTILITY WITH PM43441 * * APPLIED. * **************************************************************** * PROBLEM DESCRIPTION: LISTDEF EXCLUDE CLAUSE DOESN'T * * PROPERLY EXCLUDE OBJECTS * * FROM A LIST IN SOME CASES. * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying PM43441 (PTF UK74045 in DB2 9, PTF UK74044 in DB2 10) EXCLUDE clauses in a list of objects defined by LISTDEF utility in some cases do not exclude the intended objects. This problem has been observed when the EXCLUDE clause specifies indexes or index spaces and features the filtering- type keywords RI, LOB, BASE, XML, or ALL, but could also 1 occur for other object types. This problem was due to a logic error in list expansion code that was surfaced by the fix for PM43441. As a result, users may experience various symptoms stemming from utilities being run on objects unexpectedly (because they were not excluded from the LISTDEF), or the appearance of MSGDSNU1001I - CLAUSE IDENTIFIES NO NEW OBJECTS or other messages or indications that a LISTDEF has a different number of objects than expected. Code was added to LISTDEF utility to properly process EXCLUDE clauses so that objects are correctly excluded as expected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69806 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUILSA PM69806 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69806 DSNUILSA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUILSA LISTEND UK91693 COVER LETTER END UK91707 COVER LETTER START PROBLEM DESCRIPTION(S): PM81069 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where applications may access * * a remote data sharing group, via TCP/IP, * * where multiple members utilize the same IP * * address and port. * **************************************************************** * PROBLEM DESCRIPTION: Excessive CPU consumed, or a short * * on storage condition may exist, due * * to an accumulation of DDF related * * LLOC and LIPA control blocks. * * An abend 04E-00D31010 DSNLCCDR:0003 * * may also be observed. * **************************************************************** * RECOMMENDATION: * **************************************************************** A connect operation (as a result of an explicit SQL CONNECT, or an implicit SQL statement which references a three-part name or alias) to a remote data sharing group may incorrectly loop while all members are unavailable, or until the invalid loop is 1 detected via an abend 04E-00D31010 DSNLCCDR:0003. This condition only occurs if a prior access to the group was successful and multiple members were discovered with the same IP address and port. Note: Users can define multiple group members with the same IP address and port by utilizing the TCP/IP SHAREPORT definition. The loop condition may also cause an accumulation of DDF related LLOC and LIPA control blocks. This accumulation issue may be observed by excessive utilization of the LCBLLOCP ("DC-RM LLOC POOL") and LCBLIPAP ('DC-RM LIPA POOL') storage pools, or by excessive CPU consumption as a result of navigating excessively long LLOC control block chains. The problem occurs because DB2 neglects to eliminate ALL occurrences of the failed IP address and port (due to a communication error) from its list of discovered members. This causes DB2 to incorrectly re-detect the failing IP address and port and re-attempt the connect operation. DDF must be recycled (stopped and started) to relieve the LLOC/LIPA storage accumulation condition and to eliminate the long LLOC control block chain. When a communication error is detected during an attempt to connect to a remote data sharing group, DB2 has been changed to remove ALL instances of the failed IP address and port from its list of discovered members. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81069 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTSVL PM81069 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81069 DSNLTSVL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTSVL LISTEND UK91707 COVER LETTER END UK91718 COVER LETTER START PROBLEM DESCRIPTION(S): PM80387 - **************************************************************** * USERS AFFECTED: All DB2 10 users who use queries containing * * the following combination: * * * * 1. a CASE expression in a select list * * 2. an EXISTS predicate in the WHEN clause * 1 * 3. a correlated reference inside the * * EXISTS predicate * **************************************************************** * PROBLEM DESCRIPTION: The following combination causes a * * storage overlay: * * * * 1. a CASE expression in a select list * * 2. an EXISTS predicate in the WHEN * * clause * * 3. a correlated reference inside the * * EXISTS predicate * * * * The known symptoms are: * * * * 04E-00E2000E at DSNIBCTD.DSNSVSFB+0834 * * 0C4-00000004 at DSNXGRDS.DSNXOEXB+103A * * 04E-00E2000E at DSNHCORE.DSNSVSFB+0844 * * 04E-00E2000F at DSNIDALC.DSNSVSFB+0854 * * 04E-00E2000E at DSNXEDC4.DSNSVSFB+0810 * * * * The storage overlay is a single bit * * alteration. The known occurrences are: * * * * 1. eyecatcher 'TRLF' was modified to * * 'TRlF' * * 2. around offset '190'X before the * * eyecatcher 'PDA' * * * * There is a slim chance of an incorrect * * output as the result of this storage * * overlay. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** The following combination causes a storage overlay: 1. a CASE expression in a select list 2. an EXISTS predicate in the WHEN clause 3. a correlated reference inside the EXISTS predicate The known symptoms are: 1. 04E-00E2000E at DSNIBCTD.DSNSVSFB+0834 2. 0C4-00000004 at DSNXGRDS.DSNXOEXB+103A 3. 04E-00E2000E at DSNHCORE.DSNSVSFB+0844 4. 04E-00E2000F at DSNIDALC.DSNSVSFB+0854 5. 04E-00E2000E at DSNXEDC4.DSNSVSFB+0810 The storage overlay is a single bit alteration. The known occurrences are: 1. eyecatcher 'TRLF' was modified to 'TRlF' 2. around offset '190'X before the eyecatcher 'PDA' There is a small chance of an incorrect output as the result 1 of this storage overlay. The following example causes the storage overlay: SELECT CASE WHEN EXISTS(SELECT 1 FROM T2 WHERE T1.C1 = T2.C1) THEN T1.C1 ELSE NULL END FROM T1; When DB2 processes the correlated reference T1.C1 inside the EXISTS predicate, it causes the storage overlay. DB2 has been modified to ensure the above example will not run into a storage overlay. Additional keywords: DB2OVRLAY/K SMCOVERLAY SQLSTORAGE SQLOVERLAY SQLCASEWHEN SQLEXISTS SQLCORRELATED SQLSELECT ABEND0C4 RC04 ABEND04E RC00E2000E RC00E2000F INCORROUT SQLINCORR SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80387 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM80387: See PM80387 APAR/PTF text for additional information about why a REBIND is necessary. PM80387 corrects a problem of a storage overlay when the a query contains the following combination: 1. a CASE expression in a select list 2. an EXISTS predicate in the WHEN clause 3. a correlated reference inside the EXISTS predicate The known symptoms are: 1. ABEND04E LOC=DSNIBCTD.DSNSVSFB+0834 2. ABEND0C4 LOC=DSNXGRDS.DSNXOEXB+103A 3. ABEND04E LOC=DSNHCORE.DSNSVSFB+0844 4. ABEND04E LOC=DSNIDALC.DSNSVSFB+0854 5. ABEND04E LOC=DSNXEDC4.DSNSVSFB+0810 The storage overlay is a single bit alteration. The known occurrences are: 1. eyecatcher 'TRLF' was modified to 'TRlF' 2. around offset '190'X before the eyecatcher 'PDA' There is a small chance of an incorrect output as the result of this storage overlay. 1 To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM75883: See PM75883 APAR/PTF text for additional information about why a REBIND is necessary. PM75883 corrects a problem ofABEND04E at DSNIDM DSNOPUFF 5003 for an SQL statement that satisfies the following conditions: 1. The SQL statement contains a table expression or references to a view. 2. The view or table expression contains UNION/UNION ALL. 3. One branch of the UNION/UNION ALL select list references to a LOB column from a base table. The other branch of the UNION/UNION ALL select list references to a LOB column from a non base table. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOB2 PM80387 DSNXODTX PM80387 DSNXOEXB PM80387 DSNXOGA1 PM80387 DSNXOSL PM80387 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80387 DSNXOB2 DSNXODTX DSNXOEXB DSNXOGA1 DSNXOSL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOB2 DSNXODTX DSNXOEXB DSNXOGA1 DSNXOSL LISTEND UK91718 COVER LETTER END UK91745 COVER LETTER START PROBLEM DESCRIPTION(S): PM74555 - **************************************************************** * USERS AFFECTED: All DB2 users of the -DISPLAY THREAD * * command * **************************************************************** 1 * PROBLEM DESCRIPTION: The -DISPLAY THREAD command could * * generate ABEND04E RC00E50001 in * * DSNGEDLC when processing threads for * * active distributed agents * **************************************************************** * RECOMMENDATION: * **************************************************************** During a -DISPLAY THREAD command the DSNXVITR service may be called to perform UTF to EBCDIC conversion when processing a distributed agent. This conversion service may try to obtain a latch that is incompatible with a latch that the -DISPLAY THREAD command is already holding, resulting in an ABEND04E RC00E50001 in DSNGEDLC. The -DISPLAY THREAD command was changed to use ?DSNLZNAM macro to preform character conversions. This macro will not request an incompatible latch. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74555 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLAGNT PM74555 DSNLAGNX PM74555 DSNLBABR PM74555 DSNLTACC PM74555 DSNLTEXC PM74555 DSNLTSEC PM74555 DSNLXALC PM74555 DSNLXRAL PM74555 DSNLZSER PM74555 DSNVDTA PM74555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74555 DSNLAGNT DSNLAGNX DSNLBABR DSNLTACC DSNLTEXC DSNLTSEC DSNLXALC DSNLXRAL DSNLZSER DSNVDTA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLAGNT DSNLAGNX DSNLBABR DSNLTACC DSNLTEXC DSNLTSEC DSNLXALC DSNLXRAL DSNLZSER DSNVDTA LISTEND UK91745 COVER LETTER END 1UK91747 COVER LETTER START PROBLEM DESCRIPTION(S): PM78555 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures or * * User Defined Functions (UDFs). * **************************************************************** * PROBLEM DESCRIPTION: The following abend may happen * * when UDF or stored procedure * * task is cancelled. * * * * ABND=0C4-00000004, * * DSNVSRX .DSNVSRRX+0FE2 * * * * ABND=0C4-00000010, * * DSNXGRDS.DSNX9CAC+1CF8 * **************************************************************** * RECOMMENDATION: * **************************************************************** When stored procedure or UDF task gets cancelled, there is a small timing window where a DB2 control block might be double freed. This would damage the control block chain and result in various abends. DB2 code has been corrected to eliminate the timing window. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78555 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9WCA PM78555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78555 DSNX9WCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9WCA LISTEND UK91747 COVER LETTER END UK91750 COVER LETTER START PROBLEM DESCRIPTION(S): PM80714 - **************************************************************** * USERS AFFECTED: All HIR2220(IRLM220) and HIR2230(IRLM230) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNKINSL:5004 * * for duplicate key found during DB2 log * * apply process. * **************************************************************** 1 * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** DB2 log apply process may fail with ABEND04E RC00C90101 issued in DSNKINSL for duplicate key found. This may happen as a DB2 member B updated the same RID which was being operated upon by another member A which has not issued commit yet. This problem could be caused by IRLM not setting pseudo-deleter feedback flag correctly in some cases when an inserter requests a table lock while there was a deleter somewhere in the group. There is a small window where pseudo-deleter feedback is not set when the request was not the top waiter in IRLM for that lock. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR corrects IRLM logic to return pseudo-deleter feedback in RLPRCB10 on a lock request when there could be a potential deleter in a data sharing group. Index Manager will correctly retry the request and wait for the deleter. This fix should prevent the duplicate key error in DB2 and ABEND04E RC00C90101. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM80714 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL190 PM80714 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80714 DXRRL190 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL190 LISTEND UK91750 COVER LETTER END UK91752 COVER LETTER START PROBLEM DESCRIPTION(S): PM77554 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNB1RRR * **************************************************************** * RECOMMENDATION: * **************************************************************** When the resource recovery routine is invoked as part of the abort processing, it examines a chain of WPHG control blocks to determine an appropriate clean up action without serializing with other operations. When an ALTER BUFFERPOOL command runs 1 concurrently, it could remove a WPHG control block from the chain and cause the resource recovery routine to abend. DB2 has been fixed to acquire a latch in the resource recovery routine to serialize with other operations that also process the WPHG chain. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77554 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1RRR PM77554 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77554 DSNB1RRR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1RRR LISTEND UK91752 COVER LETTER END UK91786 COVER LETTER START PROBLEM DESCRIPTION(S): PM76617 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (new installations) * * users of the SYSIBM.SYSDUMMYA catalog table. * **************************************************************** * PROBLEM DESCRIPTION: Unexpected SQLCODE -332 when running * * queries involving the SYSIBM.SYSDUMMYA * * catalog table. * **************************************************************** * RECOMMENDATION: * **************************************************************** After running the jobs DSNTIJID, DSNTIJIE, DSNTIJIF and DSNTIJTC to initialize the catalog and directory, the SYSIBM.SYSDUMMYA catalog table and the DSNDB06.SYSTSASC catalog table space do not match the ASCII CCSID settings specified in DSNHDECP. The DSNTIJTC job is supposed to update the CCSID of the catalog objects to match the settings in DSNHDECP, but it did not happen for the ASCII catalog objects. DB2 code has been updated so that the DSNTIJTC job will update the CCSID for the SYSIBM.SYSDUMMYA catalog table and the DSNDB06.SYSTSASC catalog table space. ++HOLD ACT: This PTF updated DB2 code so that the DSNTIJTC job will update the CCSID of the SYSIBM.SYSDUMMYA catalog table and the 1 DSNDB06.SYSTSASC catalog table space. Applying this PTF will not correct the CCSID. Please do the following to ensure the CCSID is correct. For MIXED=YES specified in DSNHDECP: 1. Run query the get the CCSID: SELECT MIXED_CCSID FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB06' AND NAME='SYSTSASC'; 2. If the returned value does not match the value of AMCCSID specified in DSNHDECP, run the following utility: CATMAINT UPDATE UNLDDN CCSID Plans and packages that depend on the SYSIBM.SYSDUMMYA catalog table or the DSNDB06.SYSTSASC catalog table space will be invalidated after running the utility. For MIXED=NO specified (or by default) in DSNHDECP: 1. Run query the get the CCSID: SELECT SBCS_CCSID FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB06' AND NAME='SYSTSASC'; 2. If the returned value does not match the value of ASCCSID specified in DSNHDECP, run the following utility: CATMAINT UPDATE UNLDDN CCSID Plans and packages that depend on the SYSIBM.SYSDUMMYA catalog table or the DSNDB06.SYSTSASC catalog table space will be invalidated after running the utility. Additional keywords: SQLCODE332 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76617 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF updated DB2 code so that the DSNTIJTC job will update the CCSID of the SYSIBM.SYSDUMMYA catalog table and the DSNDB06.SYSTSASC catalog table space. Applying this PTF will not correct the CCSID. Please do the following to ensure the CCSID is correct. 1 For MIXED=YES specified in DSNHDECP: 1. Run query the get the CCSID: SELECT MIXED_CCSID FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB06' AND NAME='SYSTSASC'; 2. If the returned value does not match the value of AMCCSID specified in DSNHDECP, run the following utility: CATMAINT UPDATE UNLDDN CCSID Plans and packages that depend on the SYSIBM.SYSDUMMYA catalog table or the DSNDB06.SYSTSASC catalog table space will be invalidated after running the utility. For MIXED=NO specified (or by default) in DSNHDECP: 1. Run query the get the CCSID: SELECT SBCS_CCSID FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB06' AND NAME='SYSTSASC'; 2. If the returned value does not match the value of ASCCSID specified in DSNHDECP, run the following utility: CATMAINT UPDATE UNLDDN CCSID Plans and packages that depend on the SYSIBM.SYSDUMMYA catalog table or the DSNDB06.SYSTSASC catalog table space will be invalidated after running the utility. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUECM5 PM76617 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76617 DSNUECM5 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUECM5 LISTEND UK91786 COVER LETTER END UK91791 COVER LETTER START PROBLEM DESCRIPTION(S): PM74976 - 1 **************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: Corrupted data, resulting in any of * * the following symptoms: * * - Incorrect output, INCORROUT. * * - ABEND04E RC00C90101, RC00C90102, * * RC00C90105, or RC00C902xx in * * various CSECTs. * * - Data/index inconsistencies reported * * by the CHECK INDEX utility. * * - Page regression reported by the * * DSN1LOGP utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** When updated pages are not written out for a few checkpoints, DB2 checkpoint logic starts a cleanup process. The cleanup logic writes those pages out to DASD after all outstanding writes complete. However, the cleanup logic does not wait for synchronous writes started by a page set p-lock exit process. If the synchronous writes fail and the pages are put into LPL, the LPL recovery that follows, may not recover those pages because DB2 checkpoint already advances after the cleanup process. This leads to data corruption. The DB2 checkpoint cleanup logic is modified to wait for synchronous writes. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74976 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CFC PM74976 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74976 DSNB1CFC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CFC LISTEND UK91791 COVER LETTER END UK91796 COVER LETTER START PROBLEM DESCRIPTION(S): PM74675 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users in DATASHARING SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: IRLM abend878-14 or abend0C4-38 after * 1 * a F IrlmProc,STATUS,RETLOCK,subsys * * command is entered. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Each line is used to display one retain lock. IRLM uses a 2- byte signed variable for the number of lines to be displayed. If the number of retain locks is greater than 32,767 (2 to the power of 15) then overflow occurs causing the abend. GEN: KEYWORDS: *** END IMS KEYWORDS *** Code is changed to use a 4-byte field for the number of lines. Also, GETMAIN subpool is changed to minimize low private storage usage. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM74675 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL0B0 PM74675 DXRRL2B0 PM74675 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74675 DXRRL0B0 DXRRL2B0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL0B0 DXRRL2B0 LISTEND UK91796 COVER LETTER END UK91805 COVER LETTER START PROBLEM DESCRIPTION(S): PM78992 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * parallelism users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIPSBL with * * ERQUAL5003 encountered by a query * * running on parallelism * **************************************************************** * RECOMMENDATION: * **************************************************************** A query running on parallelism encountered an abend ABEND04E RC00C90101 in DSNIPSBL with ERQUAL5003. Investigation shows that a child task was traversing through 1 an internal chain when the chain got updated and an entry got de-chained. As a result, the child task tried to access the de-chained entry and failed a sanity check. Additional Keywords: SQLPARALLELISM PARALLELISM DB2 was modified such that a latch will be acquired when traversing through the internal chain. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78992 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIPSBL PM78992 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78992 DSNIPSBL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIPSBL LISTEND UK91805 COVER LETTER END UK91807 COVER LETTER START PROBLEM DESCRIPTION(S): PM75392 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of DISPLAY * * DATABASE command * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 in DSNIDSTT+'0262'x * * during DISPLAY DATABASE command and * * brought down DB2 * **************************************************************** * RECOMMENDATION: * **************************************************************** DISPLAY DATABASE command (example DISPLAY DB(..) SP(..) LOCKS) encountered an abend ABEND0C4 RC00000038 at DSNIDSTT+0262 and brought DB2 down. A notify exit of DISPLAY DATABASE command got an abend ABEND0C4 at DSNIDSTT+0262 while traversing an internal chain. The PRR of DSNIDSTT did not recover the abend because the PRR was not properly set. Then it caused DB2 to come down with RC00E50702. The ABEND0C4 at DSNIDSTT+0262 occurred because the internal chain was updated by another thread while it was traversed. The update and reference of this internal chain is serialized by 1 a latch. But the thread which updated this internal chain missed to obtain the latch. DB2 was modified to correct the PRR set up during DISPLAY DATABASE. DB2 was also modified to acquire a latch before updating the internal chain. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75392 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICINV PM75392 DSNIDSTT PM75392 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75392 DSNICINV DSNIDSTT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICINV DSNIDSTT LISTEND UK91807 COVER LETTER END UK91810 COVER LETTER START PROBLEM DESCRIPTION(S): PM78558 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users who perform conditional restarts * * with a SYSPITR value as part of a * * procedure to restore their systems to * * prior point in time. * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNJ098E, MSGDSNV086E, RC00E80084 * * DB2 restart failure in data sharing * * on a conditional restart using a * * SYSPITR value obtained from * * MSGDSNU1614I, issued during BACKUP * * SYSTEM utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** User followed the recommendations from the DB2 Administration Guide under the section, "Recovering a DB2 system to a given point in time by using the RESTORE SYSTEM utility." In a data sharing system, the user ran BACKUP SYSTEM utility to back up both the data and log copy pools (i.e., DATA ONLY was NOT specified and/or FULL was specified or defaulted). MSGDSNU1614I was issued to externalize the 1 "DATA COMPLETE LRSN". After manually restoring their log copy pools according to the documented recommendations, they performed a conditional restart specifying a SYSPITR value they obtained from the DATA COMPLETE LRSN reported by the BACKUP SYSTEM. When they tried to restart DB2 on all members one of the members failed to start and MSGDSNJ098E was issued: DSNJ098E - CRCR ENDLRSN OF xxxxxxxxxxxx IS HIGHER THAN ANY KNOWN LRSN, NO TRUNCATION WILL OCCUR DSNV086E - DB2 ABNORMAL TERMINATION REASON = 00E80084 DB2 had been mistakenly externalizing a "data complete lrsn" value that was valid only for the member that BACKUP SYSTEM ran on, but not for other members in the data sharing group. For a member with little or no update activity, it could fail in this way when the procedure is followed. Code in BACKUP SYSTEM utility has been changed to cause a delay of approximately eight seconds to occur after the backup of the data is complete and prior to the start of the backup of the log copy pool. By doing this, it reduces the chances that any members will not have log records which are greater than the value that is seen in message DSNU1614I. This delay is added only when BACKUP SYSTEM utility is run without specifying DATA ONLY, and only in a data sharing environment. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78558 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The DB2 10 PTF for APAR PM78558 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUVABK PM78558 DSNUVBBD PM78558 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78558 DSNUVABK DSNUVBBD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNUVABK DSNUVBBD LISTEND UK91810 COVER LETTER END UK91812 COVER LETTER START PROBLEM DESCRIPTION(S): PM78896 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who observe * * unreadable object names in messages * * DSNU381I and DSNU380I * **************************************************************** * PROBLEM DESCRIPTION: Object names in messages DSNU381I and * * DSNU380I are sometimes unreadable. * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran a utility which placed a table space (or table space partition) into COPY PENDING state. In the UTILTERM phase of most utilities, MSGDSNU381I or MSGDSNU380I are issued to alert the user that an object was put into COPY PENDING state, or that an object was already in COPY PENDING state and that state was not reset by the utility. In some cases under normal activity, the object name is not properly stored in the Database Exception Table (DBET) even when the actual object is properly identified as being in COPY PENDING state. In such cases, DB2 displays the object name with asterisks in the first four characters of both the database and table space name ('****'), each followed by a four hexadecimal digit dbid and psid, respectively, for example: DSNU381I - TABLESPACE ****124F.****2680 IS IN COPY PENDING This APAR was requested to improve the likelihood that DB2 can display the object names properly. Utility code was changed to detect when objects in COPY PENDING state can't be displayed properly in messages DSNU381I and DSNU380I. When possible in these cases, DB2 will attempt an alternative means to try to capture the object names. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78896 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGSRX PM78896 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78896 DSNUGSRX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNUGSRX LISTEND UK91812 COVER LETTER END UK91827 COVER LETTER START PROBLEM DESCRIPTION(S): PM78034 - **************************************************************** * USERS AFFECTED: All users of DSN1LOGP utility * **************************************************************** * PROBLEM DESCRIPTION: DSN1138E RBA AND LRSN CAN NOT BOTH BE * * SPECIFIED ISSUED INCORRECTLY. * **************************************************************** * RECOMMENDATION: * **************************************************************** When RBA or LRSN keywords are omitted, it is possible that DSN1LOGP job fails with message DSN1138E RBA AND LRSN CAN NOT BOTH BE SPECIFIED. This is because it looks at a flag byte which is not initialized. This results in incorrectly detecting an input keyword error. DSN1LOGP parser logic is changed to initialize the storage before it is used. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78034 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN1LPAR PM78034 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78034 DSN1LPAR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN1LPAR LISTEND UK91827 COVER LETTER END UK91829 COVER LETTER START PROBLEM DESCRIPTION(S): PM81913 - **************************************************************** * USERS AFFECTED: All Users of the DSNTIJNH CATENFM job. * **************************************************************** * PROBLEM DESCRIPTION: The DSNTIJNH job was used while in * * NFM and this prevented later * * CATMAINT and CATENFM processing. * 1 **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** The ACOMHALT process from the DSNTIJNH job is only applicable while a subsystem is going through the ENFM process. It should not affect CATMAINT or CATENFM processing outside of an active ENFM process. In the reported case it was interfering with a subsystem's attempt to enter the CM* mode. The DSNTIJNH job is used to halt the DSNTIJEN ENFM process. When used, the ENFM process will stop after the current ENFM step completes. If the DSNTIJNH job is used while in NFM then it may prevent other CATMAINT or CATENFM processing. In the reported problem, a DSNTIJNH job was run while in NFM and then a DSNTIJCS job was run to put the subsystem into CM*. The DSNTIJCS job failed with a return code=6 and the following MSGDSNU777I message being displayed in the job output: DSNU777I -DB2A 042 10:43:44.73 DSNUECMI - CATENFM UTILITY STATUS - SKIPPING STEP BECAUSE HALT WAS SPECIFIED. The subsystem remained in NFM. The same problem would occur if the DSNTIJES job was run to have a subsystem enter the ENFM* mode. Code has been modified to correct the aforementioned problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81913 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUECMI PM81913 DSNUECM0 PM81913 DSNUECM4 PM81913 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81913 DSNUECMI DSNUECM0 DSNUECM4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUECMI DSNUECM0 DSNUECM4 LISTEND UK91829 COVER LETTER END UK91830 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM81984 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of current schema * * special register in the distributed * * environment. * **************************************************************** * PROBLEM DESCRIPTION: DB2 incorrectly returned SQLCODE -725 * * (SQLCODE725) indicating the application * * has supplied an invalid schema value * * for the current schema special register * * when running the application in the * * distributed environment. * * * * This APAR is applicable for all * * applications connecting to DB2 v10 via * * JDBC DataSource interface with * * currentSchema='lowercase' passed in the * * connection string. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 incorrectly returned SQLCODE -725 (SQLCODE725) indicating the application has supplied an invalid schema value for the current schema special register when running the application in the distributed environment. The following java example can help illustrate the error: public class pm17324y { public static void main(String[] args) throws SQLException { try { Class.forName("com.ibm.db2.jcc.DB2Driver"); } catch (ClassNotFoundException e) { e.printStackTrace(); } String url = "jdbc:db2://utecxxx.xxxx.xxx.xxx.xxx:xxx/xxxxxx"; java.util.Properties props = new java.util.Properties(); props.put("user", "xxxxxxx"); props.put("password", "xxxxxxxx"); props.put("traceFile", "trace.out"); props.put("traceLevel", com.ibm.db2.jcc.DB2BaseDataSource.TRACE_ALL + ""); //The following property setting is the one caused the problem props.put ("currentSchema", "dummy_schema_name_01"); Connection con = DriverManager.getConnection(url, props); con.setAutoCommit(false); System.out.println("Got connection " + con.toString()); System.out.println("Autocommit is set to " + con.getAutoCommit()); con.commit(); con.close(); 1 System.out.println("Connection closed."); } } Additional keywords: SQLCODE725 DB2 is fixed to avoid SQLCODE -725 (SQLCODE725). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81984 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXESSR PM81984 DSNXRSPG PM81984 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81984 DSNXESSR DSNXRSPG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXESSR DSNXRSPG LISTEND UK91830 COVER LETTER END UK91831 COVER LETTER START PROBLEM DESCRIPTION(S): PM81473 - **************************************************************** * USERS AFFECTED: All DB2 users * **************************************************************** * PROBLEM DESCRIPTION: The EXTENTS column in * * SYSTABLESPACESTATS or * * SYSINDEXSPACESTATS table, namely real * * time statistics (RTS) table, may have * * incorrect value. For a multi-piece * * linear page set, instead of showing the * * extent number of the last piece, it may * * show that of prior piece. * **************************************************************** * RECOMMENDATION: * **************************************************************** RTS EXTENTS field in the memory is not updated when extending a linear page set into a new subsequent piece. Hence RTS EXTENTS column may have incorrect value. The extend process is fixed to update the RTS EXTENTS field when extending to a new subsequent piece of a linear page set. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81473 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNPXTN0 PM81473 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81473 DSNPXTN0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNPXTN0 LISTEND UK91831 COVER LETTER END UK91836 COVER LETTER START PROBLEM DESCRIPTION(S): PM81637 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS RRSAF users. * **************************************************************** * PROBLEM DESCRIPTION: The user has an RRSAF application * * which is a private context server. * * In some cases a client application * * uses the private context to issue * * SQL, and the private context server * * calls RRS commit on the same * * DB2 agent. The DB2 RRS exit processor * * terminates the server commit thread * * with an ABEND04E RC00F3009B. DB2 * * cannot reset its exits, so DB2 or * * z/OS RRS need to be restarted. * **************************************************************** * RECOMMENDATION: * **************************************************************** The user has an RRSAF application which is a private context server. Client applications use the private context to issue SQL and then return the private context to the server. The server then calls RRS commit processing for that context. In some cases a client application issues SQL and is 'in' DB2 at the same time that the server calls commit using the same DB2 agent. The DB2 RRS exit processor terminates the server commit thread with an ABEND04E RC00F3009B. This termination processing may cause z/OS RRS to call the Exit_Failed_Exit and unset the DB2 exits. DB2 cannot reset its exits, so DB2 or z/OS RRS must be restarted. Module DSN3RRSX has been updated to avoid issuing the RRS return code that causes z/OS RRS to call the Exit_Failed_Exit and unset the DB2 exits. The problem described by this APAR included a sequence of events. An ABEND04E RC0F3009B occurred in DSN3RRSX and the calling application received a reason code 00F3009B. Then an ABEND04E RC00F30095 occurred in DSN3RRSX and z/OS RRS or DB2 had to be restarted. With this APAR fix, an ABEND04E RC0F3009B may still occur in 1 DSN3RRSX and the application may receive a reason code 00F3009B, but this APAR fix should prevent the accompanying ABEND04E RC00F30095 in DSN3RRSX and the need to restart z/OS RRS or DB2. COMPONENT: 5740-XYR01-HIZAA10 APARS FIXED: PM81637 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY IBM recommends that you install DB2 PTF UK77559 to fix HIPER APAR PM59756 before installing this PTF or other DB2 PTFs for RRSAF. PM59756 fixes a base DB2 V10 problem. ACTION: This PTF requires either an ERLY code refresh or a re-IPL of zOS. To refresh, enter the following commands after applying the PTF: MODIFY LLA,REFRESH -STOP DB2 ... (only if the DB2 subsystem is started) -REFRESH DB2,EARLY -START DB2,PARM=... These commands are not necessary if you re-IPL after applying the PTF. ACTION: This PTF requires either an ERLY code refresh or a re-IPL of zOS. To refresh, enter the following commands after applying the PTF: MODIFY LLA,REFRESH -STOP DB2 ... (only if the DB2 subsystem is started) -REFRESH DB2,EARLY -START DB2,PARM=... These commands are not necessary if you re-IPL after applying the PTF. ACTION: This PTF requires either an ERLY code refresh or a re-IPL of zOS. To refresh, enter the following commands after applying 1 the PTF: MODIFY LLA,REFRESH -STOP DB2 ... (only if the DB2 subsystem is started) -REFRESH DB2,EARLY -START DB2,PARM=... These commands are not necessary if you re-IPL after applying the PTF. ACTION: In order for this PTF to be fully effective, an IPL with CLPA or REFRESH DB2,EARLY is required. The DB2 member should be stopped before issuing the REFRESH DB2, EARLY command. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3RRSX PM81637 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81637 DSN3RRSX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3RRSX LISTEND UK91836 COVER LETTER END UK91837 COVER LETTER START PROBLEM DESCRIPTION(S): PM65940 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of an SQL * * statement with an IN list predicate, which * * contains host variables mixed with string * * constants. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 at the location * * DSNXGRDS DSNXRSIN OFFSET10D4 could * * happen for an SQL statement with an IN * * list predicate, which contains host * * variables mixed with string constants, * * when parallelism is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000010 at the location DSNXGRDS DSNXRSIN OFFSET10D4 could happen for an SQL statement with an IN list predicate, which contains host variables mixed with string constants, when parallelism is enabled. An example is shown below: SELECT 1 FROM T1 1 WHERE T1.C1 IN ('Lit1', :HV1, 'Lit2'); DB2 did not correctly process the aforementioned SQL statement, which caused the ABEND. The IN list predicate can be transformed from a few OR predicates, like C1 = 'Lit1' OR C1 = :HV1 OR C1 = 'Lit2' will be transformed into C1 IN ('Lit1', :HV1, 'Lit2'). DB2 has been modified to correctly process the aforementioned SQL statement, so there will be no the ABEND. Additional keywords: SQLHOSTVAR SQLIN PARALLELISM SQLPARALLELISM DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65940 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM65940: See PM65940 APAR/PTF text for additional information about why a REBIND is necessary. PM65940 corrects a problem that ABEND0C4 RC00000010 at the location DSNXGRDS DSNXRSIN OFFSET10D4 could happen for an SQL statement with an IN list predicate, which contains host variables mixed with string constants, when parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTF PM65940 DSNXOW2F PM65940 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65940 DSNXOTF DSNXOW2F THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTF DSNXOW2F LISTEND UK91837 COVER LETTER END UK91848 COVER LETTER START PROBLEM DESCRIPTION(S): PM78014 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users of the LOAD * * utility with variable blocked spanned * * (VBS) input data sets. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 RC00000038 DSNURWBF +x'1FDC' * * during a LOAD utility with a variable * * blocked spanned (VBS) input data set. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** The LOAD utility abended with an ABEND0C4 DSNURWBF OFFSET1FDC because the VBS input data set was incorrectly processed as a FORMAT SPANNED YES record format which is obtained from running an UNLOAD SPANNED YES utility. The same abend occurred when specifying LOAD FORMAT SPANNED NO. In both cases, the LOAD utility was only checking the record format of the data set, and mistaking the presence of a VBS data set as a FORMAT SPANNED YES record. The LOAD utility has been modified to not use record format to determine whether to process a record as FORMAT SPANNED. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78014 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM78014 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved. COMMENTS: The PTF for APAR PM76873 changes current behavior for the REORG TABLESPACE utility specifying DISCARD WHEN and run against a table containing (a) LOB column(s). While the target rows in the base table are discarded, their corresponding LOBs are not. These 'orphaned' LOBs are not a hinderance of any kind so the decision was made to remove the restrictive Auxilliary CHecK Pending (ACHKP) state so the table space is accessible. This will also result in the RC4 not being set for this condition, however, an RC4 might still result for other reasons/conditions. CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURELD PM78014 DSNURWBF PM78014 DSNURWBG PM78014 DSNURWI PM78014 DSNURWT PM78014 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78014 DSNURELD DSNURWBF DSNURWBG DSNURWI DSNURWT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURELD DSNURWBF DSNURWBG DSNURWI DSNURWT LISTEND UK91848 COVER LETTER END UK91885 COVER LETTER START PROBLEM DESCRIPTION(S): PM80074 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of pair-wise join query with * * the dynamic statement cache enabled * * (CACHEDYN = YES) * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXRPJP * * M558 may occur when a pair-wise join * * query is executed multiple times and * * the SQL statement is cached and the * * previous execution of the SQL statement * * returned a negative sqlcode. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 at DSNXRPJP M558 may occur when a pair- wise join query is executed multiple times in a system with the dynamic statement cache enabled (CACHEDYN = YES) and the previous execution returned a negative SQLCODE. After a negative SQLCODE is issued, a certain variable was not reset in this access path, allowing for subsequent executions of the statement to receive this error. The problem can apply to all pair-wise join queries, if and only if the pair-wise join query 1. is executed multiple times and 2. the system SQL dynamic statement cache is enabled (CACHEDYN = YES) and 3. a negative sqlcode is returned in previous execution of the same statement. DB2 is modified to re-initialize the variable properly before pair-wise join is executed. Additional Keywords: SQLPAIRWISEJOIN SQLDYNSTMTCACHE ABEND04E RC00E70005 DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80074 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRPJP PM80074 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80074 DSNXRPJP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPJP LISTEND UK91885 COVER LETTER END UK91889 COVER LETTER START PROBLEM DESCRIPTION(S): PM80201 - **************************************************************** * USERS AFFECTED: 1. All DB2 10 for z/OS users of migrated * * native SQL Procedures and procedures with * * COMMIT ON RETURN YES attribute. * * . * * 2. All DB2 9 and DB2 10 for z/OS users of * * native SQL procedures with a COMMIT * * statement or with COMMIT ON RETURN YES * * attribute. * **************************************************************** * PROBLEM DESCRIPTION: 1a. COMMIT ON RETURN does not occur for * * migrated procedures that are nested * * in native SQL procedures. * * . * * 1b. When an RRSAF application calls a * * native SQL procedure (eg SP1), which * * then calls a migrated native SQL * * procedure with COMMIT ON RETURN YES * * (eg SP2), the error can occur after * * SP2 has completed the COMMIT ON RETURN * * and returns back to SP1's CALL * * statement. * * . * * If SP1 then issues a COMMIT followed * * by DROP of SP2, the DROP may fail with * * SQLCODE -615. * * . * * 2. ABEND04E RC00D93011 * * DSNRGLM1.DSNRUC01 +08DE when a COMMIT * * is being executed inside a Native * * SQL PL procedure. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 1a. When a migrated native SQL procedure calls itself or another stored procedure defined with COMMIT ON RETURN YES attribute, DB2 does not perform the COMMIT upon returning from the nested procedure. . 1b. When an RRSAF application calls a native SQL procedure (eg SP1), which then calls a migrated native SQL procedure with COMMIT ON RETURN YES (eg SP2), the error can occur after SP2 has completed the COMMIT ON RETURN. This is due to the interest in the RRS UR not being deleted causing the reported SQLCODE -615 problem with the subsequent DROP because the following caller's COMMIT does not eallocate the stored procedure package. . 2. When the COMMIT has been issued inside a native SQL procedure, the module which issued the COMMIT had not checked the return code and thus did not issue the subsequent ROLLBACK. The reported problem occurs because the missing implicit ROLLBACK causes Phase 1 COMMIT to fail due to a connection failure. 1a. DB2 code has been modified to perform COMMIT ON RETURN for the called procedure when returning back to the calling Native SQL PL procedure. . 1b. DB2 code has been modified to delete the interest on the RRS UR during the COMMIT ON RETURN. . 2. DB2 code has been modified to check the COMMIT's return code and issue the appropriate implicit ROLLBACK upon failure. ADDITIONAL KEYWORDS: SQLSP SQLSTOREDPROC RRSATTACH SQLDROP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80201 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXESP9 PM80201 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80201 DSNXESP9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXESP9 LISTEND UK91889 COVER LETTER END UK91895 COVER LETTER START PROBLEM DESCRIPTION(S): PM79005 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an MERGE * * SQL statement with parameter markers. * **************************************************************** * PROBLEM DESCRIPTION: Two problems are involved: * * * * 1. ABEND04E RC00E70005 at the * * location DSNXGRDS DSNXORCM M130 * * could happen for a MERGE SQL * * statement with a parameter marker * * that exists in the USING clause and * * used in the THEN or ELSE branch of a * * CASE expression. * * 2. Incorrect output could happen for * * a MERGE SQL statement with a * * parameter marker that exists in the * * USING clause and compares with a * * constant in a predicate or in a * * search condition of a CASE * * expression. * **************************************************************** * RECOMMENDATION: * **************************************************************** The incorrect output can be observed in the following example: CREATE TABLE T1 ( C1 VARCHAR(4), C2 VARCHAR(4)); COMMIT; INSERT INTO T1 VALUES('ABC1', 'XXXX'); HOSTVARS = ('ABC1', 'XYZ1'); MERGE INTO T1 USING (VALUES( ? , ?)) AS PARMS(C1, C2) ON (T1.C1=PARMS.C1) WHEN MATCHED THEN UPDATE SET C2=(CASE WHEN PARMS.C1='ABC1' THEN 'THEN' ELSE 'ELSE' END) WHEN NOT MATCHED THEN INSERT(C1, C2) VALUES(PARMS.C1, PARMS.C2) ; SELECT * FROM T1; It return the result: +-------------+ | C1 | C2 | +-------------+ 1_| ABC1 | ELSE | +-------------+ While the right result should be: +-------------+ | C1 | C2 | 1 +-------------+ 1_| ABC1 | THEN | +-------------+ The ABEND can be observed in the following example: MERGE INTO T1 USING (VALUES( ? , ?)) AS PARMS(C1, C2) ON (T1.C1=PARMS.C1) WHEN MATCHED THEN UPDATE SET C2=(CASE WHEN PARMS.C1='ABC1' THEN PARMS.C2 ELSE 'ELSE' END) WHEN NOT MATCHED THEN INSERT(C1, C2) VALUES(PARMS.C1, PARMS.C2) ; DB2 did not correctly process the aforementioned SQL statements, which caused the incorrect output or ABEND. DB2 has been modified to correctly process the aforementioned SQL statements, so there will be no incorrect output or ABEND. Additional keywords: SQLMERGE SQLCASE PARAMETERMARKER SQLPMARKER SQLPMK DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79005 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM79005: See PM79005 APAR/PTF text for additional information about why a REBIND is necessary. PM79005 corrects a problem that incorrect output could happen for a MERGE SQL statement with a parameter marker that exists in the USING clause and compares with a constant in a predicate or in a search condition of a CASE expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXORCM PM79005 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79005 DSNXORCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXORCM LISTEND UK91895 COVER LETTER END UK91941 COVER LETTER START PROBLEM DESCRIPTION(S): PM81471 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * autobind of a native stored * * procedure. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * ABEND04E RC00E70005 * * CSECT DSNXEAAL:M260 * * * * PROBLEM SCENARIO: * * * * The reported error occurred * * when an autobind error reason * * code was cleared. Later in DB2 this * * was detected and DB2 abended. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: An error occurred while doing an autobind on native stored procedure. The reason code was accidentally cleared so the error did not get detected until further into DB2 where it abended. PROBLEM CONCLUSION: The abend has been fixed by not clearing out an error that happens during autobind. That error can now be externalized through an SQL code, for example. ADDITIONAL KEYWORDS: BIND SQLNATIVESQLPL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81471 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBAB2 PM81471 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81471 DSNTBAB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNTBAB2 LISTEND UK91941 COVER LETTER END UK91954 COVER LETTER START PROBLEM DESCRIPTION(S): PM77669 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of CHECK LOB utility * **************************************************************** * PROBLEM DESCRIPTION: CHECK LOB SHRLEVEL CHANGE reset CHECK * * PENDING (CHKP) status when no * * inconsistencies found * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a CHECK LOB SHRLEVEL CHANGE utility against a LOB table space that was in CHECK PENDING (CHKP) status. The CHECK LOB utility did not find any inconsistencies in the LOB table space and reset the CHKP status. CHECK LOB SHRLEVEL CHANGE should not reset CHKP status. CHECK LOB has been modified to avoid resetting CHKP status for SHRLEVEL CHANGE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77669 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKLBD PM77669 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77669 DSNUKLBD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKLBD LISTEND UK91954 COVER LETTER END UK91971 COVER LETTER START PROBLEM DESCRIPTION(S): PM79804 - **************************************************************** * USERS AFFECTED: All users of the DB2 10 for z/OS * * installation CLIST are affected by this * * change. * **************************************************************** * PROBLEM DESCRIPTION: This APAR addresses two problems: * 1 * (1) In MIGRATE mode for a non-data * * sharing subsystem or the first * * member of a data sharing group, * * when you specify DSNTIDXA or * * DSNTIDXB in the INPUT MEMBER NAME * * field of panel DSNTIPA1, the * * DB2 10 installation CLIST always * * resets DSN6SPRM.LRDRTHLD to its * * new default value of 10. However, * * the reset is appropropriate only * * when the migration input value is * * the old default of 0. * * (2) In MIGRATE mode for the second or * * subsequent member of a data sharing * * group, the CLIST never resets * * LRDRTHLD to 10, regardless of the * * migration input value. * **************************************************************** * RECOMMENDATION: Apply the fixing PTF for this APAR. * **************************************************************** The DSN6SPRM.LRDRTHLD subsystem parameter specifies the number of minutes, from 0 to 1439, that an agent is allowed to hold a read claim before it is reported by warning message and DB2 traces as a long-running reader. If you set LRDRTHLD to 0, DB2 will not report long-running readers. In DB2 10 for z/OS, the default setting of LRDRTHLD was changed from 0 to 10 in order to encourage awareness of long-running readers. By intent, the DB2 installation CLIST will reset the LRDRTHLD value when you migrate to DB2 10. However, the behavior is currently malfunctioning in two ways: (1) Currently, when you run the DB2 10 installation CLIST in MIGRATE mode and specify an INPUT MEMBER NAME of either DSNTIDXA or DSNTIDXB, it always forces the LRDRTHLD setting to the new default setting of 10, regardless of the setting used in the previous release. However, the LRDRTHLD migration input setting should be retained, except when it is the old default of 0. (2) When you migrate the second or subsequent member of a data sharing group, LRDRTHLD is never set to 10, regardless of its migration input value. This problem occurs because the CLIST performs the reset only when you have specified an INPUT MEMBER NAME of DSNTIDXA or DSNTIDXB on panel DSNTIPA1, and DSNTIDXA and DSNTIDXB are used only for the first member. This PTF corrects MIGRATE mode behavior of the DB2 installation CLIST to reset LRDRTHLD to 10 whenever its migration input setting is 0. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79804 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 ACTION: ***Action for PM79804 (V10) This PTF modifies the DB2 installation CLIST to correct errors in the migration handling of the DSN6SPRM.LRDRTHLD parameter. Actions for current DB2 10 customers: ------------------------------------ This PTF modifies CLIST member DSNTINST only in the prefix.SDSNCLST target library. After applying the PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTINST PM79804 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79804 DSNTINST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTINST LISTEND UK91971 COVER LETTER END UK91977 COVER LETTER START PROBLEM DESCRIPTION(S): PM76272 - **************************************************************** * USERS AFFECTED: All DB2 users who create index on a table * * or insert rows to a table which was * * created prior to z/OS, V5. * **************************************************************** * PROBLEM DESCRIPTION: There could be the following problems * * with the table created prior to z/OS, * * V5, * * * * 1. After creating an index on the * * table, any access to the DBD may cause * * an ABEND04E in DSNGEPUF ERQUAL501A * * because the DBD was corrupted. * * * * 2. When inserting a row to the table, * * customer could receive the following * * abends, * * * * ABEND04E RC00C90101 DSNISRTI * * ERQUAL5014 * * ABEND04E RC00C90101 DSNICOFS * * ERQUAL5008 * * ABEND04E RC00C90101 DSNKINSB * 1 * ERQUAL5008 * **************************************************************** * RECOMMENDATION: * **************************************************************** For a table created before z/OS, V5, one of the internal data structures does not exist. Create an index on such a table could incorrectly access this internal data structure which results in OBD overlay. When inserting a row to such a table, DB2 could incorrect access this internal data structure, which results in the above abends. DB2 has been changed to avoid accessing the internal data structure when it does not exist. Applying this apar can fix the abends when inserting a row to the table but it does not fix the OBD which is already overlaid. Contact IBM Software Support for assistance in analyzing this problem. Addional keyword:SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76272 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDBIX PM76272 DSNGDDIX PM76272 DSNICOFS PM76272 DSNISRTI PM76272 DSNKINSB PM76272 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76272 DSNGDBIX DSNGDDIX DSNICOFS DSNISRTI DSNKINSB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDBIX DSNGDDIX DSNICOFS DSNISRTI DSNKINSB LISTEND UK91977 COVER LETTER END UK91979 COVER LETTER START PROBLEM DESCRIPTION(S): PM75150 - **************************************************************** * USERS AFFECTED: All DB2 users of Non-Partitioned Index * * (NPI) on a large table space. * **************************************************************** 1 * PROBLEM DESCRIPTION: For a large table space, the maximum * * number of pieces for an NPI is * * incorrectly inherited from the * * maximum number of partitions of the * * table space. When inserting data to a * * table or creating the NPI, the customer * * may receive the following message, * * * * DSNT501I   * * DMBC DSNKINSL RESOURCE UNAVAILABLE * * CORRELATION-ID=QFSBTC036 * * CONNECTION-ID=SERVER * * LUW-ID= * * GAF263F9.C741.120818101839=561408 * * REASON 00C9009D * * TYPE 00000201  * **************************************************************** * RECOMMENDATION: * **************************************************************** For an NPI on a LARGE(5-byte RID) table space, the index maximum number of pieces is independent of the table space maximum number of partitions, it is calculated from index page size and piece size as the following: Maximum NPI number of pieces = MINIMUM( 4096, 2^32 / (index piece size/index page size) ) DB2 code has been changed to calculate the correct maximum number of pieces for an NPI. Applying the apar does not correct the indexes that were created before the apar. ALTER INDEX CLOSE can fix the maximum number of pieces for the NPI. additional keyword: SQLALTER,SQLCREATE, RC00C9009D, MSGDSNT501I ++HOLD COMMENT FOR RELEASE A10, TYPE DOC: After APAR PM75150 changes, for an Non-Partitioned Index (NPI) on a LARGE (5-byte RID) table space, the index maximum number of pieces is independent of the table space maximum number of partitions, it is calculated from index page size and piece size as the following: Maximum NPI number of pieces = MINIMUM( 4096, 2^32 / (index piece size/index page size) ) Information about this change will be updated in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at DB2 10 for z/OS > DB2 reference information > DB2 SQL > Statements > CREATE INDEX. ++HOLD COMMENT FOR RELEASE A10, TYPE ACT: After applying APAR PM75150, the following steps may help find the affected Non-Partitioned Indexes (NPIs) and the incorrect index maximum number of pieces can be fixed by ALTER INDEX ... CLOSE. 1 1. run a query, such as the sample query below, to identify the databases, table spaces and indexes, SELECT TS.DBNAME AS DB_NAME, TS.NAME AS TS_NAME, IX.NAME AS INDEX_NAME, IX.CREATOR AS IX_CREATOR, HEX(IX.OBID) AS INDEX_OBID, IX.CLOSERULE AS CLOSERULE FROM SYSIBM.SYSINDEXES IX, SYSIBM.SYSTABLES TB, SYSIBM.SYSTABLESPACE TS WHERE TB.NAME = IX.TBNAME AND TB.CREATOR = IX.TBCREATOR AND TB.TSNAME = TS.NAME AND TB.DBNAME = TS.DBNAME AND (TS.PARTITIONS > 254 OR TS.TYPE = 'L' OR TS.TYPE = 'K' OR TS.DSSIZE > 0) AND TS.PARTITIONS <> 0 AND (TS.STATUS = 'C' OR NOT ((IX.INDEXTYPE = 'P' OR IX.INDEXTYPE = 'D') AND TB.PARTKEYCOLNUM <>0)) AND TS.DBNAME <> 'DSNDB06' ORDER BY IX.OBID; +------------------------------------------------------------+ |DB_NAME |TS_NAME |INDEX_NAME|IX_CREATOR|INDEX_OBID|CLOSERULE| +------------------------------------------------------------+ |DB161410|XTB10000|I_NODEIDXT|SC161410 |0056 |N | |DB161410|TU161410|I_DOCIDTB1|SC161410 |0058 |N | ... 2. run REPAIR DBD DIAGNOSE against all databases from the above query. For example REPAIR DBD DB161410. By searching OBDINNUM in th REPAIR DBD output, it has the following mismatch, DSNU916I DSNUEDFT - OBDS DIFFER AT OFFSET X'00000052' OBDINNUM - INFORMATION NOT IN DB2 CATALOG DSNU904I DSNUEDFT - EXISTING VALUE X'0100' DSNU905I DSNUEDFT - REBUILT VALUE X'1000' DSNU913I DSNUEDDR - OBD X'0056' COMPARISON COMPLETE -- 0 ERRORS which confirms the index index I_NODEIDXT with OBID X'0056' has incorrect maximum number of index pieces. 3. fix these indexes found in the above repair DBD output by altering the CLOSE attribute of the identified indexes from their current value and then altering the CLOSE attribut back to their original value. The index name and index attribute information can be found in the query result at 1 step 1. for example, the index SC161410.I_NODEIDXT has the CLOSE attribute CLOSERULE = N. To correct the maximum number of index pieces for I_NODEIDXT, run the following DDL ALTER INDEX index SC161410.I_NODEIDXT CLOSE YES ALTER INDEX index SC161410.I_NODEIDXT CLOSE NO COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75150 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: After APAR PM75150 changes, for an Non-Partitioned Index (NPI) on a LARGE (5-byte RID) table space, the index maximum number of pieces is independent of the table space maximum number of partitions, it is calculated from index page size and piece size as the following: Maximum NPI number of pieces = MINIMUM( 4096, 2^32 / (index piece size/index page size) ) Information about this change will be updated in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at DB2 10 for z/OS > DB2 reference information > DB2 SQL > Statements > CREATE INDEX. ACTION: After applying APAR PM75150, the following steps may help find the affected Non-Partitioned Indexes (NPIs) and the incorrect index maximum number of pieces can be fixed by ALTER INDEX... CLOSE. 1. run a query, such as the sample query below, to identify the databases, table spaces and indexes, SELECT TS.DBNAME AS DB_NAME, TS.NAME AS TS_NAME, IX.NAME AS INDEX_NAME, IX.CREATOR AS IX_CREATOR, HEX(IX.OBID) AS INDEX_OBID, IX.CLOSERULE AS CLOSERULE FROM SYSIBM.SYSINDEXES IX, SYSIBM.SYSTABLES TB, SYSIBM.SYSTABLESPACE TS WHERE TB.NAME = IX.TBNAME AND TB.CREATOR = IX.TBCREATOR AND TB.TSNAME = TS.NAME AND TB.DBNAME = TS.DBNAME AND (TS.PARTITIONS > 254 OR TS.TYPE = 'L' OR TS.TYPE = 'K' OR TS.DSSIZE > 0) AND TS.PARTITIONS <> 0 AND (TS.STATUS = 'C' OR 1 NOT ((IX.INDEXTYPE = 'P' OR IX.INDEXTYPE = 'D') AND TB.PARTKEYCOLNUM <>0)) AND TS.DBNAME <> 'DSNDB06' ORDER BY IX.OBID; +------------------------------------------------------------+ |DB_NAME |TS_NAME |INDEX_NAME|IX_CREATOR|INDEX_OBID|CLOSERULE| +------------------------------------------------------------+ |DB161410|XTB10000|I_NODEIDXT|SC161410 |0056 |N | |DB161410|TU161410|I_DOCIDTB1|SC161410 |0058 |N | ... 2. run REPAIR DBD DIAGNOSE against all databases from the above query. For example REPAIR DBD DB161410. By searching OBDINNUM in th REPAIR DBD output, it has the following mismatch, DSNU916I DSNUEDFT - OBDS DIFFER AT OFFSET X'00000052' OBDINNUM - INFORMATION NOT IN DB2 CATALOG DSNU904I DSNUEDFT - EXISTING VALUE X'0100' DSNU905I DSNUEDFT - REBUILT VALUE X'1000' DSNU913I DSNUEDDR - OBD X'0056' COMPARISON COMPLETE -- 0 ERRORS which confirms the index index I_NODEIDXT with OBID X'0056' has incorrect maximum number of index pieces. 3. fix these indexes found in the above repair DBD output by altering the CLOSE attribute of the identified indexes from their current value and then altering the CLOSE attribut back to their original value. The index name and index attribute information can be found in the query result at step 1. for example, the index SC161410.I_NODEIDXT has the CLOSE attribute CLOSERULE = N. To correct the maximum number of index pieces for I_NODEIDXT, run the following DDL ALTER INDEX index SC161410.I_NODEIDXT CLOSE YES ALTER INDEX index SC161410.I_NODEIDXT CLOSE NO COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDADP PM75150 DSNGDAIP PM75150 DSNGDAIX PM75150 DSNGDBIX PM75150 DSNUEDFT PM75150 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75150 DSNGDADP DSNGDAIP DSNGDAIX DSNGDBIX DSNUEDFT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDADP 1 DSNGDAIP DSNGDAIX DSNGDBIX DSNUEDFT LISTEND UK91979 COVER LETTER END UK91986 COVER LETTER START PROBLEM DESCRIPTION(S): PM78712 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of CASE * * expression and GROUP BY. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -122 may not be issued for * * an SQL statement that satisfies the * * following conditions: * * 1. The statement contains a CASE * * expression in the SELECT list. * * 2. The CASE expression contains * * an IN predicate which references to * * a column which is not in the GROUP BY * * list. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -122 may not be issued for an SQL statement that satisfies the following conditions: 1. The statement contains a CASE expression in the SELECT list. 2. The CASE expression contains an IN predicate which references to a column which is not in the GROUP BY list. For Example, SELECT C1 + 1,(CASE WHEN C2 IN (1,2) THEN 1 ELSE 2 END) AS COL1 FROM TEST.T1 GROUP BY C1 + 1; Column C2 is in the SELECT list but it is not in the GROUP BY list. DB2 did not issue SQLCODE -122 as expected in this case. DB2 was fixed to correctly handle the column which is in the CASE expression and not in the GROUP BY list. Additional Keywords: SQLGROUPBY SQLCASE SQLIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78712 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM78712: See PM78712 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM78712 corrects a problem of not issuing SQLCODE -122 for an SQL statement that contains a CASE expression in the SELECT list and the CASE expression contains an IN predicate which references to a column which is not in the GROUP BY list. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEM PM78712 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78712 DSNXOEM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEM LISTEND UK91986 COVER LETTER END UK91991 COVER LETTER START PROBLEM DESCRIPTION(S): PM81912 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN * * job. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E4002E DSNUGSUU OFFSET53E8 * * during the UTILTERM phase of the * * ENFM REORG of a compressed SPT01 * * table space. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** During the ENFM REORG processing of a compressed SPT01 directory table space, the storage obtained for the compression dictionary is freed but the pointer to that storage was not zeroed out. During UTILTERM processing we then try to look at the dictionary storage which was freed and this resulted in the reported abend. DB2 code has been updated to prevent future occurrences of the problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81912 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM41956: 1 This APAR/PTF fixes a problem found in the DSNTIJEN and DSNTIJNF jobs as part of the migration to new-function mode. The problem does not apply to new DB2 10 installations. Orphaned entries were found in the SYSCOPY and SYSOBDS catalog tables after running the DSNTIJEN and DSNTIJNF jobs as part of the migration to new-function mode. Application of this APAR/PTF will only prevent the DSNTIJEN and DSNTIJNF jobs from leaving the orphaned entries behind. This APAR/PTF does not remove the existing orphaned entries. The orhpaned entries do not affect DB2 normal operations, however they may cause unexpected problems when migrating to future release of DB2. If the DB2 subsystem has never been migrated to new-function mode and the DSNTIJEN and DSNTIJNF jobs have never been run before, you just need to make sure this APAR/PTF is applied before running the DSNTIJEN and DSNTIJNF jobs. If the DSNTIJNF or DSNTIJEN jobs have been run prior to this APAR/PTF, you need to do the following: 1. Run the following query to identify the orphaned entries: (note: the RID built-in function requires new-function mode) SELECT RIGHT(HEX(RID(C)),10),'SYSCOPY' FROM SYSIBM.SYSCOPY C WHERE C.TSNAME = 'DSNVTH01' AND C.DBNAME = 'DSNDB06' AND NOT EXISTS(SELECT * FROM SYSIBM.SYSINDEXES I WHERE I.CREATOR = 'SYSIBM' AND I.NAME = 'DSNVTH01') UNION SELECT RIGHT(HEX(RID(O)),10),'SYSOBDS' FROM SYSIBM.SYSOBDS O WHERE O.DBID = 6 AND O.OBDTYPE = 'R' AND NOT EXISTS (SELECT * FROM SYSIBM.SYSTABLESPACE T WHERE T.DBID = O.DBID AND T.PSID = O.PSID); 2.For each row returned from the query, run the following utility using the RID in the row: (for the SYSCOPY rows returned) REPAIR OBJECT LOCATE TABLESPACE DSNDB06.SYSCOPY RID X'' DELETE (for the SYSOBDS rows returned) REPAIR OBJECT LOCATE TABLESPACE DSNDB06.SYSALTER RID X'' DELETE COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURBDC PM81912 DSNURCAT PM81912 DSNXIENF PM81912 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81912 DSNURBDC DSNURCAT DSNXIENF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURBDC DSNURCAT DSNXIENF LISTEND UK91991 COVER LETTER END UK91998 COVER LETTER START PROBLEM DESCRIPTION(S): PM73177 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of triggers. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -723 or following ABENDs * * could happen when a trigger is fired * * after altering the triggering table, * * which is because the triggering * * table and its table space are not * * recorded in the catalog table * * SYSIBM.SYSPACKDEP. * * * * 1. ABEND04E RC00E2000F at the location * * DSNXEFB DSNSVSFB OFFSET0858 on V10. * * 2. ABEND04E RC00E20027 at the location * * DSNXEFB DSNSVBK OFFSET0A1A on V9. * * 3. ABEND0C4 RC00000011 at the location * * DSNSLD1 DSNSVBK OFFSET100A on V9. * * 4. ABEND04E RC00E20002 at the location * * DSNXEXAT DSNSVBK OFFSET08F2 on V9. * **************************************************************** * RECOMMENDATION: * **************************************************************** The failure can be observed in the following example: CREATE TABLE T1(C1 VARCHAR(10), C2 INTEGER, C3 VARCHAR(50))! CREATE TABLE T2(C1 VARCHAR(100), C2 INTEGER, C3 VARCHAR(50))! CREATE TRIGGER TR1 AFTER INSERT ON T1 REFERENCING NEW AS NEW_TV NEW_TABLE AS NEW_TB FOR EACH ROW MODE DB2SQL BEGIN ATOMIC INSERT INTO T2 VALUES ( CONCAT('TRH2D503 - AFTER UPDATE - ', 1 (SELECT C1 FROM NEW_TB FETCH FIRST ROW ONLY)), NEW_TV.C2, NEW_TV.C3 ); INSERT INTO T2 SELECT * FROM NEW_TB; END! COMMIT! ALTER TABLE T1 ALTER C1 SET DATA TYPE VARCHAR(100)! COMMIT! -- The following INSERT can cause SQLOCODE -723. INSERT INTO T1 VALUES ( '123456789ab', 3, 'T1C3 COLUMN' )! -- The following INSERT can cause the ABEND number 1 or 2. INSERT INTO T1 VALUES ( '123456789abcdefghijk', 3, 'T1C3 COLUMN' )! -- The following INSERT can cause the ABEND number 1, 3 or 4. INSERT INTO T1 VALUES ( '123456789abcdefghijkhijklmnopqrst', 3, 'T1C3 COLUMN' )! DB2 has been modified to record the triggering table and its table space to the catalog table SYSIBM.SYSPACKDEP, so this SQLCODE -723 and ABENDs can be resolved. Additional keywords: SQLTRIGGER SQLCODE723 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73177 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM73177: PM73177 corrects a problem that SQLCODE -723 or following ABENDs could happen when a trigger is fired after altering the triggering table, which is because the triggering table and its table space are not recorded in the catalog table SYSIBM.SYSPACKDEP. 1. ABEND04E RC00E2000F at the location DSNXEFB DSNSVSFB OFFSET0858 on V10. 2. ABEND04E RC00E20027 at the location DSNXEFB DSNSVBK OFFSET0A1A on V9. 3. ABEND0C4 RC00000011 at the location DSNSLD1 DSNSVBK OFFSET100A on V9. 4. ABEND04E RC00E20002 at the location DSNXEXAT DSNSVBK OFFSET08F2 on V9. To make this fix effective, the trigger packages must be rebound after application of this PTF. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNXOTG PM73177 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73177 DSNXOTG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTG LISTEND UK91998 COVER LETTER END UK92000 COVER LETTER START PROBLEM DESCRIPTION(S): PM79378 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of searched * * UPDATE of a symmetric view. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E20002 can happen at * * Location DSNXEFB.DSNSVBK OFFSET1956 * * when processing a searched UPDATE of * * a symmetric view (a view defined using * * WITH CHECK OPTION). * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E20002 can happen at Location DSNXEFB.DSNSVBK OFFSET1956 when processing a searched UPDATE of a symmetric view and the following conditions are met: 1. The query package is bound on pre Version 10, then runs on Version 10. 2. Index scan is used to fetch the rows qualifying for update. 3. All rows qualifying for the update are materialized into the workfile prior to performing the update. The abend occurs during the symmetric view validation due to the access type difference (index scan used for fetching the rows, but actual update involves table scan of a workfile). This problem happens because DB2 doesn't set several internal variables correctly. The following query illustrates how this abend can occur. Define a symmetric view CREATE VIEW SYSADM.VIEW1 (C1, C2, C3, C4, C5, C6, C7, C8 ) AS SELECT ALL C1,C2,C3,C4,C5,C6,C7,C8 FROM SYSADM.TB1 WHERE C8 <= 'N' AND C5 <= C6 WITH CASCADED CHECK OPTION ; Issue an update query. 1 EXEC SQL UPDATE VIEW1 SET C6 = : H WHERE C3 = : H AND AND C7 = : H AND C5 = : H AND C5 + 999 MICROSECOND < : H ; Above abend can happen when processing this update query. Rebind the package on Version 10 can be a workaround for this problem. DB2 has been changed to set the internal variables correctly. Additional keywords : SQLVIEW SQLUPDATE SQLSYMMETRICVIEWCHECK COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79378 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRUP9 PM79378 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79378 DSNXRUP9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRUP9 LISTEND UK92000 COVER LETTER END UK92028 COVER LETTER START PROBLEM DESCRIPTION(S): PM83082 - **************************************************************** * USERS AFFECTED: All data sharing users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00D900F8 in DSNRCPRC during * * a Tracker Site or System Level Point * * in Time conditional restart of DB2 in * * data sharing mode. Restart then fails * * with DSNV086E RC00D95001. * **************************************************************** * RECOMMENDATION: * **************************************************************** The owning work unit information for the SCA Global Member Record lock request in DSNRCPRC is not built correctly. This exposes a very small timing window that can result in an ABEND04E RC00D900F8 following the UNLOCK request. The lock is obtained in data sharing mode during DB2 restart when DB2 is being restarted as a Tracker Site (TRKRSITE system parameter), or with a SYSPITR (System Level Point in Time Recovery mode) conditional restart. PITR SYSPITR SYSPITRT Tracker TRKR DSNRCPRC has been changed to build the lock owning work unit information correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83082 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRCPRC PM83082 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83082 DSNRCPRC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRCPRC LISTEND UK92028 COVER LETTER END UK92059 COVER LETTER START PROBLEM DESCRIPTION(S): PM81268 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for * * z/OS who are also using IBM DB2 Analytics * * Accelerator * **************************************************************** * PROBLEM DESCRIPTION: This APAR contains the following fixes * * for DB2 accelerator support: * * * * (1) Explain of a query that has a * * DSN_QUERYINFO_TABLE.REASON_CODE value * * of 901 will still offload when executed * * with CURRENT QUERY ACCELERATION=ALL * * for DB2 9 z/OS or * * CURRENT GET_ACCEL_ARCHIVE =YES for * * DB2 9 z/OS and DB2 10 z/OS. * * * * (2) A short running query that does * * not have any archived tables is * * offloaded to the accelerator when * * CURRENT GET_ACCEL_ARCHIVE =YES for * * DB2 10 z/OS. * * * * (3) ABEND0C4-RC00000010 * * DSNXGRDS.DSNXONZA+18B0, * * ABEND0C4-RC00000010 * * DSNXGRDS.DSNXONZA+169A, or accelerator * * error message such as * * "ERROR: Relation 'TABLEA-ID_222-ARCH' * * does not exist" on a table that is not * * archived, can occur when a query is * * offloaded to a DB2 10 z/OS subsystem * * defined with multiple accelerators. * * * * (4) A pruned query is incorrectly * 1 * offloaded for DB2 9 z/OS and * * DB2 10 z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR contains the following fixes for DB2 accelerator support: (1) Explain of a query that has a DSN_QUERYINFO_TABLE.REASON_CODE value of 901 will still offload when executed with CURRENT QUERY ACCELERATION=ALL for DB2 9 z/OS or CURRENT GET_ACCEL_ARCHIVE =YES for DB2 9 z/OS and DB2 10 z/OS. (2) A short running query that does not have any archived tables is incorrectly offloaded to the accelerator for DB2 10 z/OS when CURRENT GET_ACCEL_ARCHIVE =YES. (3) When a query is offloaded to a DB2 10 z/OS subsystem defined with multiple accelerators: (a) an accelerator error message such as "ERROR: Relation 'TABLEA-ID_222-ARCH' does not exist" may occur on a table that is not archived. The error message specifies the table name with the '-ARCH' suffix even though the table is not archived; or (b) ABEND0C4-RC10 DSNXGRDS.DSNXONZA+18B0 or ABEND0C4-RC00000010 DSNXGRDS.DSNXONZA+16A can occur. (4) A pruned query is incorrectly offloaded for DB2 9 z/OS and DB2 10 z/OS. (1) A query that has a DSN_QUERYINFO_TABLE.REASON_CODE value of 901 will now issue SQLCODE -4742 with reason code 901 when CURRENT QUERY ACCELERATION=ALL or CURRENT GET_ACCEL_ARCHIVE = YES. (2) Short running queries with no archived tables execute on DB2 when CURRENT GET_ACCEL_ARCHIVE = YES. (3) Code is fixed to resolve the abend/error message. (4) Pruned queries no longer offload to the accelerator for any CURRENT QUERY ACCELERATION or CURRENT GET_ACCEL_ARCHIVE value. An SQLCODE -4742 is not issued for pruned queries when CURRENT QUERY ACCELERATION=ALL or CURRENT GET_ACCEL_ARCHIVE= YES. Keywords: IDAAV2R1/K IDAAV3R1/K SQLCODE4742 SQLEXPLAIN SQLFULL(?) OFFSET18B0 OFFSET16A COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81268 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNXONZA PM81268 DSNXONZO PM81268 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81268 DSNXONZA DSNXONZO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXONZA DSNXONZO LISTEND UK92059 COVER LETTER END UK92061 COVER LETTER START PROBLEM DESCRIPTION(S): PM74666 - **************************************************************** * USERS AFFECTED: All DB2 users of the field QISEKLRU * **************************************************************** * PROBLEM DESCRIPTION: The value for stealable pages QISEKLRU * * is sometimes incorrect, for example * * STEALABLE PAGES could be greater than * * PAGES IN SKEL POOL (ABOVE). * **************************************************************** * RECOMMENDATION: * **************************************************************** A monitor showing the values for the EDM SKEL pool shows incorrect values for STEALABLE PAGES (QISEKLRU) field. The code has been updated to correct a problem which could cause the incorrect STEALABLE PAGES (QISEKLRU) field. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74666 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEFBL PM74666 DSNGERBK PM74666 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74666 DSNGEFBL DSNGERBK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFBL DSNGERBK LISTEND UK92061 COVER LETTER END 1UK92070 COVER LETTER START PROBLEM DESCRIPTION(S): PM79547 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of LOBs in Compat * * Mode (CM). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNOEMNU 5003 when a UNICODE * * conversion error occurs on behalf of * * LOB data. Instead, an SQLCODE -330 * * should be issued. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOEMNU 5003 when a UNICODE conversion error occurs for LOB data. Instead, an SQLCODE -330 (SQLCODE330) should be issued. The following example can illustrate the problem. 1. Create a simple EBCDIC Table T1 with a CLOB column in DB2 10 for z/OS Compatibility Mode (CM). CREATE TABLE T1 (ID INT, TEXT CLOB(100)) CCSID EBCDIC; 2. Insert into the CLOB column in T1 a value which can cause a UNICODE conversion error. EXEC SQL BEGIN DECLARE SECTION; DCL TEXT CHAR(6); EXEC SQL DECLARE :TEXT VARIABLE CCSID UNICODE; EXEC SQL END DECLARE SECTION; // Set HOST VARIABLE :TEXT with UNICODE value causing // conversion error when converting to EBCDIC EXEC SQL INSERT INTO T1 VALUES('1', :TEXT); When the host variable :TEXT is converted from UNICODE to EBCDIC for the INSERT operation, it produces a conversion error. Since DB2 code does not handle the error properly, the code path leads to the unexpected ABEND. The code in DB2 has been modified to issue an SQLCODE -330 for a LOB UNICODE conversion error and prevent the error path leading to the ABEND. Additional Keywords: SQLCODE330 DB2LOB SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79547 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNOEMNU PM79547 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79547 DSNOEMNU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOEMNU LISTEND UK92070 COVER LETTER END UK92079 COVER LETTER START PROBLEM DESCRIPTION(S): PM76353 - **************************************************************** * USERS AFFECTED: Users who use CATMAINT to do VCAT switch * * and use clone tables * **************************************************************** * PROBLEM DESCRIPTION: REPAIR DBD TEST/DIAGNOSE reports error * * on fields OBDPSVID, OBDPSVIX, OBDPSIID, * * or OBDPSIIX for clone objects. * **************************************************************** * RECOMMENDATION: * **************************************************************** After running CATMAINT UPDATE VCAT to change VCAT names, REPAIR DBD TEST/DIAGNOSE report errors on fields OBDPSVID, OBDPSVIX, OBDPSIID, or OBDPSIIX for clone objects like the following: DSNU901I DSNUEDPS - OBD X'xxxx' A FILE PAGESET OBD HAS THE FOLLOWING DIFFERENCES DSNU920I DSNUEDPS - OBDS DIFFER AT OFFSET X'yyyy' OBDPSVID(1) DSNU904I DSNUEDPS - EXISTING VALUE X'aaaaaaaa' DSNU905I DSNUEDPS - REBUILT VALUE X'bbbbbbbb' DSNU906I DSNUEDPS - EXISTING VALUE 'aaaa' DSNU907I DSNUEDPS - REBUILT VALUE 'bbbb' DSNU913I DSNUEDDR - OBD X'xxxx' COMPARISON COMPLETE -- 1 ERRORS WERE FOUND This is because CATMAINT UPDATE VCAT did not update vcat names on clone objects. DB2 is updated so that CATMAINT UPDATE VCAT properly updates VCAT names in clone objects. Applying this APAR will not fix the incorrect VCAT name in clone objects. For clone objects that have bad VCAT name reported by REPAIR DBD TEST/DIAGNOSE, users can drop and then re-create the clone table(s), or use REPAIR DBD REBUILD to fix the problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76353 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: 1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDADP PM76353 DSNGDAIP PM76353 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76353 DSNGDADP DSNGDAIP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDADP DSNGDAIP LISTEND UK92079 COVER LETTER END UK92085 COVER LETTER START PROBLEM DESCRIPTION(S): PM78234 - **************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E3000A received in * * DSNTLCAU followed by DB2 abnormal * * termination with RSN00F30420. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 thread was cancelled during commit processing. This caused an ABEND04E RC00E50013 cancel abend in DSNVXLT0 which was retried by DSNRUC02. The retry logic called DSNTLCAU with residual register content that subsequently caused an ABEND04E RC00E3000A in DSNTLCAU and led to DB2 termination. DSNRUC02 has been changed to correctly call DSNTLCAU following an ABEND/RETRY sequence. Additional Keywords: DB2TERM, DB2ABTERM COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78234 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRUC02 PM78234 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78234 DSNRUC02 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRUC02 LISTEND 1UK92085 COVER LETTER END UK92086 COVER LETTER START PROBLEM DESCRIPTION(S): PM63095 - **************************************************************** * USERS AFFECTED: All users of DB2 for z/OS with queries * * referencing a User Defined Function (UDF) * * with parameter DISALLOW PARALLEL * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIPSFI * * ERQUAL5007 when executing an SQL * * statement containing a UDF with * * the DISALLOW PARALLEL parameter * * while parallelism is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 in DSNIPSFI ERQUAL5007 when executing an SQL statement containing a UDF with the DISALLOW PARALLEL parameter while parallelism is enabled, and the UDF is in a subquery. The DISALLOW PARALLEL setting is not propagated properly to the correlated parent query blocks, leading to the abend. Additional Keywords: SQLCPUP PARALLELISM SQLPARALLELISM DB2PARALL/K SQLUDF Code is updated to propagate the DISALLOW PARALLEL setting properly for the condition described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63095 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. APAR PM75619 corrects two problems. The first problem occurs on both V9 and V10. A query may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. The second problem occurs on V10 only. DB2 may not issue a REORG suggestion as it should. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM63095 corrects a problem of ABEND04E RC00C90101 in DSNIPSFI :5007 when executing an SQL statement containing a User Defined Function (UDF) with the DISALLOW PARALLEL 1 parameter while parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGP PM63095 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63095 DSNXOGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGP LISTEND UK92086 COVER LETTER END UK92088 COVER LETTER START PROBLEM DESCRIPTION(S): PM78974 - **************************************************************** * USERS AFFECTED: All users of DB2 UDB for z/OS Version 9 * * ODBC/CLI and DB2 10 for z/OS ODBC/CLI. * **************************************************************** * PROBLEM DESCRIPTION: An ODBC application may experience * * memory leak in the LE heap pools when * * a stored procedure is called from the * * application and the stored procedure * * returns result sets. * **************************************************************** * RECOMMENDATION: * **************************************************************** When processing a result set returned from a stored procedure, the output SQLDA descriptor area that was used to fetch a previous result set was not properly freed. Memory pointed to by the SQLDA was left allocated, resulting in excessive storage growth in LE heap pools. Code has been changed to deallocate all memory pointed to by the output SQLDA descriptor area when processing stored procedure result sets. COMPONENT: 5740-XYR02-JDBAA17 APARS FIXED: PM78974 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: *** Action for PM78974 (Version 10) This PTF includes the following updated DBRM for the ODBC executable modules DSNAOCLI, DSNAOCLX, and DSNAO64C: DSNCLIQR 1 After applying the PTF, all customers who use these modules need to bind a package from the DBRM listed above. For example: BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIQR) ACTION(ADD) ENCODING(EBCDIC) where is the location of the DBMS where the package binds and where the description of the package resides. Failure to bind the required package could result in SQLCODE=-805 at application run time. Also, refer to the prolog of the CLI sample bind job DSNTIJCL in your SDSNSAMP data set for specific instructions on how to customize the BIND command for binding the DBRMs/packages and the application plan at your site. *** Attention: DB2 data sharing customers need to bind the package only once, after applying the PTF on the first member. ACTION: *** Action for PM76547 (Version 10) This PTF includes the following updated DBRM for the ODBC executable modules DSNAOCLI, DSNAOCLX, and DSNAO64C: DSNCLIQR After applying the PTF, all customers who use these modules need to bind a package from the DBRM listed above. For example: BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIQR) ACTION(ADD) ENCODING(EBCDIC) where is the location of the DBMS where the package binds and where the description of the package resides. Failure to bind the required package could result in SQLCODE=-805 at application run time. Also, refer to the prolog of the CLI sample bind job DSNTIJCL in your SDSNSAMP data set for specific instructions on how to customize the BIND command for binding the DBRMs/packages and the application plan at your site. *** Attention: DB2 data sharing customers need to bind the package only once, after applying the PTF on the first member. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@LIQR PM78974 DSNAOCLI PM78974 1 DSNAOSDK PM78974 DSNAOC0P PM78974 DSNAOG0P PM78974 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78974 DSN@LIQR DSNAOCLI DSNAOSDK DSNAOC0P DSNAOG0P THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAOCLI DSNAOC0P DSNAOG0P MACROS DSN@LIQR DSNAOSDK LISTEND UK92088 COVER LETTER END UK92094 COVER LETTER START PROBLEM DESCRIPTION(S): PM80804 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: Table space growth due to old read-lsn * * value. * **************************************************************** * RECOMMENDATION: * **************************************************************** Any table space with a LOB column will register its commit-lsn as a read-lsn. However, the commit-lsn value can be very old if the object has been read-only for a long time. This old read-lsn gets propagated to the buffer pool level in data sharing, and can prevent space reuse for other objects sharing the same buffer pool. The code which registers a commit-lsn as a read-lsn has been modified to use the current end-of-log lrsn if the object is currently read-only, rather than its local commit-lsn value. Additionally, the local commit-lsn tracking will be improved to allow for advancement when another member gives up its update interest. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80804 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CLM PM80804 DSNB1PPP PM80804 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM80804 DSNB1CLM DSNB1PPP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CLM DSNB1PPP LISTEND UK92094 COVER LETTER END UK92095 COVER LETTER START PROBLEM DESCRIPTION(S): PM78850 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN * * and DSNTIJNF jobs to migrate to * * new-function mode. * **************************************************************** * PROBLEM DESCRIPTION: During the DB2 10 for z/OS ENFM process * * the SYSVTREE and SYSVLTREE catalog * * tables are removed from the catalog. * * The DSNVTH01 index on the SYSVTREE * * table is also removed but it's * * underlying data set is not removed. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** During DB2 10 for z/OS ENFM processing of the SYSVIEWS catalog table space we eliminate the SYSVTREE and SYSVLTREE catalog tables. The DSNVTH01 index is also removed during the ENFM process but it's underlying data set is not deleted at the same time. If a subsystem has already gone through the DB2 10 for z/OS ENFM process and the DSNVTH01 index data set still exists then it can be manually deleted when in V10 NFM. DB2 utility code has been modified so that the DSNVTH01 index data set will be removed during the ENFM process if it is stogroup defined. If the DSNVTH01 index is user-managed then the index data set will not be deleted during the ENFM process. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78850 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURRNM PM78850 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78850 DSNURRNM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNURRNM LISTEND UK92095 COVER LETTER END UK92099 COVER LETTER START PROBLEM DESCRIPTION(S): PM81632 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically IBM DB2 Analytics Accelerator * * (IDAA) users. * * DB2 10 for z/OS only. * **************************************************************** * PROBLEM DESCRIPTION: Connection fails with (jcc) -4499 * * SQLSTATE=58009 Reason 0x12 when * * accessing an IDAA server. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote java client based application connects to a DB2 10 for z/OS server and executes a query that is off-loaded to the accelerator. The same query is executed again but the Java driver detects a DRDA exception during Open processing. The second Open fails, for example, as follows: com.ibm.db2.jcc.am.DisconnectRecoverableException: [jcc][t4][2034][11148][3.61.75] Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x12. ERRORCODE=-4499, SQLSTATE=58009 The exception occurs because the DRDA Open response (OPNQRYRM) from DB2 incorrectly contains a duplicated instance variable (QRYINSID), and the condition only occurs if the java driver functions at a DRDA SQLAM level that is lower than the current SQLAM level of DB2 10 for z/OS. The problem occurs because DB2 10 for z/OS loses state information about the accelerator server. DB2 10 for z/OS is changed to maintain state information related to the accelerator. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81632 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTCCN PM81632 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81632 DSNLTCCN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNLTCCN LISTEND UK92099 COVER LETTER END UK92118 COVER LETTER START PROBLEM DESCRIPTION(S): PM79782 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of ROW_NUMBER expression in OLAP * * specification. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC4 CSECT DSNXRWND OFFSET * * 0338 in DB2 9 for z/OS or ABEND04E * * RC00E2000F CSECT DSNSVSFB OFFSET 0858 * * in DB2 10 for z/OS when running an SQL * * statement containing a ROW_NUMBER * * expression in OLAP specification and * * a GROUP BY clause. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC4 CSECT DSNXRWND OFFSET 0339 in DB2 9 for z/OS or ABEND04E RC00E2000F CSECT DSNSVSFB OFFSET 0858 in DB2 10 for z/OS may occur when running an SQL statement containing a ROW_NUMBER expression in OLAP specification and a GROUP BY clause. For example, CREATE TABLE TA ("ORDER_NUM" VARCHAR (10)); INSERT INTO TA VALUES('1'); SELECT ROW_NUMBER() OVER(ORDER BY ORDER_NUM) FROM TA GROUP BY ORDER_NUM; The SELECT statment above will meet the mentioned ABEND. DB2 code is fixed to correct this abend problem. Additional Keywords: SQLOLAP SQLROWNUMBER SQLGROUPBY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79782 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM79782: See PM79782 APAR/PTF text for additional information about why a REBIND is necessary. PM79782 corrects a problem of ABEND0C4 at DSNXRWND OFFSET 0338 in DB2 V9 for z/OS or ABEND04E at DSNSVSFB OFFSET 0858 in DB2 1 V10 for z/OS. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGSGP PM79782 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79782 DSNXGSGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSGP LISTEND UK92118 COVER LETTER END UK92156 COVER LETTER START PROBLEM DESCRIPTION(S): PM81418 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who * * are also using IBM DB2 Analytics * * Accelerator * **************************************************************** * PROBLEM DESCRIPTION: In Explain table DSN_QUERYINFO_TABLE * * for REASON_CODE=15 the unsupported * * function cannot be easily identified. * **************************************************************** * RECOMMENDATION: * **************************************************************** In Explain table DSN_QUERYINFO_TABLE for REASON_CODE=15 the unsupported function cannot be easily identified. The column QI_DATA shows the following value: 'The query contains DB2 V10 new functionality.' For a complex query it can be difficult to identify the specific V10 functionality that is not supported. For REASON_CODE=15 the column QI_DATA will contain the unsupported function text when possible. For example: EXPLAIN ALL SET QUERYNO=6 FOR SELECT C1,LTRIM ('123DEFG123', '321'),C3 FROM T1 WHERE C1>1 FOR FETCH ONLY; Explain output for the above statement will have DSN_QUERYINFO_TABLE.REASON_CODE=15 and QI_DATA='LTRIM ('123DEFG123', '321')'. Additional Search Keywords: IDAAV2R1/K IDAAV3R1/K SQLEXPLAIN 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81418 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXORFN PM81418 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81418 DSNXORFN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXORFN LISTEND UK92156 COVER LETTER END UK92162 COVER LETTER START PROBLEM DESCRIPTION(S): PM81323 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 Users of isolation level * * uncommitted read (ISO UR). * **************************************************************** * PROBLEM DESCRIPTION: Applications hung due to page latch * * deadlock where ISO(UR) readers were * * involved. * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 9 and 10, when an ISO(UR) reader is reading a pointer-overflow record, it will request a latch on the page with the overflow record while still holding the latch on the page with the pointer subrecord. This can result in a page latch deadlock as in the following scenario. Thread thrd1 and thrd2 were two ISO(UR) readers. Thrd1 held an S latch on page pg1 and requested an S latch on page pg2, because thrd1 was accessing a pointer record on pg1 whose overflow record was on pg2. Thrd2 happened to be accessing a pointer record on pg2 whose overflow page was on pg1. Thrd2 held an S latch on pg2 and requested an S latch on pg1. Neither thrd1 or thrd2 could obtain requested S latch because there were other threads waiting for an X latch on pg1 and pg2, and the X latch requests came before the S latch requests from thrd1 and thrd2. Because thrd1 would not release its latch on pg1 until it got its latch on pg2 and thrd2 would not release its latch on pg2 until it got its latch on pg1, the result was a latch deadlock. DB2 code is modified on overflow page latching of ISO(UR) reader to avoid the page latch deadlock. If page number of overflow page is smaller than that of the base page, DB2 will try conditional S latch on the overflow page. If conditional S latch 1 acquired business goes as usual. Otherwise, DB2 will unlatch base page, then unconditionally latch overflow page. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81323 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIOW PM81323 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81323 DSNIOW THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIOW LISTEND UK92162 COVER LETTER END UK92164 COVER LETTER START PROBLEM DESCRIPTION(S): PM80627 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of a native * * SQL procedure that contains an SQL variable * * with different encoding scheme from the * * application encoding scheme. * **************************************************************** * PROBLEM DESCRIPTION: When an SQL variable in a native SQL * * procedure is defined with different * * encoding scheme from the application * * encoding scheme, SQLCODE -408 may be * * issued incorrectly from REBIND of the * * package for the native SQL procedure, * * BIND DEPLOY of the native SQL * * procedure, BIND COPY of the package for * * the native SQL procedure, or ALTER * * PROCEDURE for the native SQL procedure * * that results in a rebind to be * * attempted. SQLCODE -408 may also be * * issued incorrectly when the native SQL * * procedure is invoked and an incremental * * rebind is attempted. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem can be observed in the following example: CREATE PROCEDURE SP1 ( OUT P1 VARGRAPHIC(8) CCSID UNICODE ) APPLICATION ENCODING SCHEME ASCII 1 L1: BEGIN SELECT 'C1' INTO P1 FROM SYSIBM.SYSDUMMY1; END L1! DB2 did not correctly process the aforementioned native SQL procedure, which caused the SQLCODE -408. DB2 has been modified to correctly process the aforementioned native SQL procedure, so there will be no SQLCODE -408. Additional keywords: SQLCODE408 SQLSP SQLSTOREDPROC SQLNATIVESQLPL SQLCCSID COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80627 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOYPL PM80627 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80627 DSNXOYPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOYPL LISTEND UK92164 COVER LETTER END UK92190 COVER LETTER START PROBLEM DESCRIPTION(S): PM72380 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS. * * * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in CSECT DSNTLDEA or CSECT * * DSNTLTIM. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an IRLM request that has a RURE as an owning work unit is involved in a timeout or deadlock situation, IRLM's DB2 exits will try to determine information of an agent issuing the IRLM request. RUREs may be created in a different address space than the IRLM's DB2 exits run in, thus causing a ABEND0C4. This ABEND0C4 will cause a subsystem termination. Change IRLM's DB2 exit logic to account for the address space that any IRLM request being looked at came from. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72380 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTLDEA PM72380 DSNTLTIM PM72380 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72380 DSNTLDEA DSNTLTIM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLDEA DSNTLTIM LISTEND UK92190 COVER LETTER END UK92212 COVER LETTER START PROBLEM DESCRIPTION(S): PM80168 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Spatial * * functions. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc00E70005 can occur at * * location DSNXRUFM:M140 (OFFSETM140) * * when executing a Spatial query when a * * 'resource unavailable' condition is * * detected during fetch processing. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc00E70005 can occur at location DSNXRUFM M140 (OFFSETM140) for a Spatial query when a 'resource unavailable' condition is detected during fetch processing. Instead, an SQLCODE -904 (SQLCODE904) should be returned to the application. The following example illustrates a simple case. SELECT DB2GSE.ST_DISTANCE(DB2GSE.ST_POINT(0,0,1), DB2GSE.ST_POINT(0,2,1) ) FROM SYSIBM.SYSDUMMYU; If during the execution of this Spatial query a 'resource unavailable' condition (returned by data manager) is detected in module DSNXRUFM during processing for the ST_DISTANCE function, the above mentioned abend can occur. Instead, an SQLCODE -904 should be returned to the application with reason code rc00C9000A. If the execution completes normally, the expected result is 1 the following. +------------------------+ | | +------------------------+ 1_| 2.000000000000000E+00 | +------------------------+ The code in DB2 which processes the ST_DISTANCE function for a Spatial query is modified to return an SQLCODE -904 (to the application) once a 'resource unavailable' condition is detected resulting from fetch processing instead of terminating with an abend. Additional Keywords: SQLSPATIAL SQLCODE904 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80168 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRUFM PM80168 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80168 DSNXRUFM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRUFM LISTEND UK92212 COVER LETTER END UK92216 COVER LETTER START PROBLEM DESCRIPTION(S): PM80338 - **************************************************************** * USERS AFFECTED: All DB2 users using indexes. * **************************************************************** * PROBLEM DESCRIPTION: There are two problems fixed by this * * APAR: * * <1> ABEND0C4 LOC=DSNIDM.DSNKLTCH * * OFFSET23C6 after a soft cancel. * * <2> ABEND04E RC00C90101 * * LOC=DSNIDM.DSNKULTH ERQUAL5003. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** There are two problems fixed by this APAR : <1> ABEND0C4 LOC=DSNIDM.DSNKLTCH OFFSET23C6 after a soft cancel. 1 Index tree lotch recovery routine DSNKLMRR was called after a soft cancel, it used a 31 bit register instead of 64 bit register for the IQUE pointer, corrupted the IQUE pointer and generated the DSNKLTCH ABEND when the bad pointer was later used. <2> During index page split, the thread was canceled after the index tree lotch was acquired but before the index split log record was written. The thread rolled back without releasing the index tree lotch and index tree plock. After the thread rolled back, and the index pageset is closed, the plock exit can encounter ABEND04E RC00C90101 LOC=DSNIDM.DSNKULTH:5003 when called to release the index tree plock. Index manager tree lotch code has been changed in these two areas: <1> Index manager tree lotch recovery routine is changed to use the correct register when setting the IQUE pointer. <2> Index manager routine that releases the index tree lotch is changed to avoid the abend if an index X tree lotch is held but index pageset has been closed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80338 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKLMRR PM80338 DSNKULTH PM80338 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80338 DSNKLMRR DSNKULTH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKLMRR DSNKULTH LISTEND UK92216 COVER LETTER END UK92251 COVER LETTER START PROBLEM DESCRIPTION(S): PM76746 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: A DB2 10 for z/OS application may * * encounter the following error : * * o SQLCODE -30005, with SQLSTATE * * 56072 and SQLERRP DSNLZRDT when * 1 * DB2 is operating in CM. * * o SQLCODE -303, with SQLSTATE * * 56072 and SQLERRP DSNLZRDT when * * DB2 is operating in NFM. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 10 for z/OS application connects to a remote server while DB2 is operating in Conversion Mode (CM). DB2 incorrectly interprets the input SQLDA provided for the SQL statement and thus incorrectly determines that binary XML data is provided. As a result, DB2 incorrectly detects an SQLCODE -30005 condition and fails the SQL since binary XML data type is not supported in a DB2 10 CM environment. Similarly, when the same condition occurs in DB2 10 New Function Mode (NFM), SQLCODE -303 can incorrectly be issued. DB2 10 for z/OS requester processing has been changed to correctly determine when an input SQLDA describes binary XML data. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76746 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXMRF PM76746 DSNLXRBF PM76746 DSNLXRFT PM76746 DSNLZGDT PM76746 DSNLZRDT PM76746 DSNLZVDA PM76746 DSNXROHB PM76746 DSNXROHR PM76746 DSNXROHS PM76746 DSNXROH2 PM76746 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76746 DSNLXMRF DSNLXRBF DSNLXRFT DSNLZGDT DSNLZRDT DSNLZVDA DSNXROHB DSNXROHR DSNXROHS DSNXROH2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXMRF DSNLXRBF DSNLXRFT DSNLZGDT DSNLZRDT DSNLZVDA DSNXROHB DSNXROHR DSNXROHS DSNXROH2 LISTEND 1UK92251 COVER LETTER END UK92252 COVER LETTER START PROBLEM DESCRIPTION(S): PM79973 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users whose * * SQL contains FETCH FIRST 1 ROW ONLY, * * OPTIMIZE FOR 1 ROW, or an EXISTS subquery * **************************************************************** * PROBLEM DESCRIPTION: The DB2 optimizer will prefer an index * * if all the conditions below are true: * * * * 1. The index covers all predicates as * * matching predicates * * 2. The query contains FETCH FIRST 1 * * ROW ONLY or OPTIMIZE FOR 1 ROW in * * this query block, or the current * * query block is an EXISTS subquery * * 3. The table does not have any join * * predicates. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a query contains FETCH FIRST 1 ROW ONLY, OPTIMIZE FOR 1 ROW or an EXISTS subquery, DB2 may choose an inefficient access path. Example SELECT 1 FROM T1 AS A WHERE EXISTS( SELECT 1 FROM T2 AS B WHERE B.C1=? AND B.C2=? ) INDEX on T2 I1(C1, C2, C3, C4) I2(C3, C1, C2) DB2 might choose I2 when the filter factor for predicate B.C1=? and B.C2=? is poor. DB2 will only get 1 row for the EXISTS subquery, so I1 with all predicates as matching predicates would get better performance. Additional keywords: SQLPERFORMANCE SQLACCESSPATH SQLOF1R SQLFF1R SQLEXISTS DB2 would choose an index with all the predicates as matching predicates when the table does not have join predicates and the current query block has OPTIMIZE FOR 1 ROW, FETCH FIRST 1 ROW ONLY, or the current query block is a EXISTS subquery. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79973 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 DB2BIND: ***Action for PM80413: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM80413 corrects a problem in which page range screening (PAGE_RANGE='Y') is not chosen when a DPSI is used with one-fetch index access (ACCESSTYPE='I1'). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM80173: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM80173 corrects a problem that DB2 may select a nested loop join and a table space scan without sparse index used on the inner table for a join in a recursive common table expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM79973: See PM79973 APAR/PTF text for additional information about why a REBIND is necessary. PM79973 corrects a possible query performance problem for a query that contains FETCH FIRST 1 ROW ONLY, OPTIMIZE FOR 1 ROW, or an EXISTS subquery, and there exists an index where all the predicates can be matching predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM76495: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM76495 corrects a problem that an inefficient index may be selected when multiple indexes are estimated to be highly selective and the matching column coverage of one index is the superset of the matching column and the screening column coverage of the inefficient index. To make this fix effective for a static application, it must be 1 rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCSC PM79973 DSNXOGCX PM79973 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79973 DSNXOCSC DSNXOGCX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCSC DSNXOGCX LISTEND UK92252 COVER LETTER END UK92270 COVER LETTER START PROBLEM DESCRIPTION(S): PM78030 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of DECRYPT built-in functions. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc00E70005 can occur at * * location DSNXRSBC P022 when using the * * DECRYPT_BIT built-in function against * * data that is or is not encrypted. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc00E70005 can occur at location DSNXRSBC P022 when using the DECRYPT_BIT built-in function against data that is or is not encrypted. Instead, an -20146 (SQLCODE20146) or +20224 (SQLCODE20224) is expected. The same problem can occur when using the DECRYPT_CHAR or the DECRYPT_BINARY built-in functions. For the DECRYPT_CHAR built- in function, the abend location is DSNXRSBC P018. For the DECRYPT_BINARY built-in function, the abend location is DSNXRBIN M302. Additionally, a different problem can occur when using the DECRYPT_DB built-in function. When this function is used against encrypted data, an SQLCODE20146 is incorrectly issued. An SQLCODE20224 is expected. The following examples are included to illustrate some failing cases for DB2 v10. Given the following Table definition. 1 CREATE TABLE TEST1 (C1 VARBINARY(32000) ) ; Examples without ENCRYPTION. ---------------------------- INSERT INTO TEST1 VALUES(VARBINARY('4321',4)) ; 1. SELECT C1, DECRYPT_BIT(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRSBC P022 Expected result: SQLCODE -20146 2. SELECT C1, DECRYPT_CHAR(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRSBC P018 Expected result: SQLCODE -20146 3. SELECT C1, DECRYPT_BINARY(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRBIN M302 Expected result: SQLCODE -20146 Examples with ENCRYPTION. ------------------------- SET ENCRYPTION PASSWORD ='Ben123'; INSERT INTO TEST1 VALUES(ENCRYPT_TDES (VARBINARY('4321',4))); 1. SELECT C1, DECRYPT_BIT(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRSBC P022 Expected result: SQLCODE +20224 2. SELECT C1, DECRYPT_CHAR(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRSBC P018 Expected result: SQLCODE +20224 3. SELECT C1, DECRYPT_BINARY(C1) FROM TEST1; Result: ABEND04E rc00E70005 DSNXRBIN M302 Expected result: SQLCODE -20143 4. SELECT C1, DECRYPT_DB(C1) FROM TEST1; Result: SQLCODE -20146 1 Expected result: +20224 The code in the DB2 DECRYPT routines has been modified to correct the problem leading to the abends. Instead, the proper SQLCODE will be issued. Additionally, the DB2 V9 and DB2 10 for z/OS DB2 Codes publication will be updated to include the SQLCODE +20224 as follows. ---------------------------------------------------------------- +20224 ENCRYPTED DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING Explanation The DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB function was invoked with an argument that represents an encrypted string that was originally a binary string. A binary string cannot be cast to a character string using the DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB function. System action The statement cannot be processed. Programmer response The encrypted value can only be decrypted using the DECRYPT_BINARY function. SQLSTATE 01658 ---------------------------------------------------------------- Additional Keywords: SQLENCRYPT SQLDECRYPT SQLCODE20143 SQLCODE20146 SQLCODE20224 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78030 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The DB2 V9 for z/OS DB2 Codes publication will be updated to include the SQLCODE +20224 as follows. ---------------------------------------------------------------- +20224 ENCRYPTED DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING Explanation The DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB function was invoked with an argument that represents an encrypted string that was originally a binary string. A binary string cannot be 1 cast to a character string using the DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB function. System action The statement cannot be processed. Programmer response The encrypted value can only be decrypted using the DECRYPT_BINARY function. SQLSTATE 01658 ---------------------------------------------------------------- COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEBR PM78030 DSNXRBIN PM78030 DSNXRBI9 PM78030 DSNXRDBC PM78030 DSNXRDB9 PM78030 DSNXRSBC PM78030 DSNXRSB2 PM78030 DSNXRSB9 PM78030 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78030 DSNXEBR DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB2 DSNXRSB9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEBR DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB2 DSNXRSB9 LISTEND UK92270 COVER LETTER END UK92276 COVER LETTER START PROBLEM DESCRIPTION(S): PM79545 - **************************************************************** * USERS AFFECTED: All DB2 users of external User Defined * * Functions ( UDF ) * **************************************************************** * PROBLEM DESCRIPTION: After a DB2 cancel or MVS cancel or an * * abend of a thread that invokes external * * UDFs from within stored procedures, * * the following symptoms may occur: * * 1. an MVS command to either refresh or * 1 * to quiesce the WLM environment * * issues message IWM031I but does not * * complete * * 2. a STOP DB2 command issues message * * DSNX922I but then hangs and does not * * complete * * 3. a STOP DB2 MODE(FORCE) command hits * * ABEND0C4 RC00000010 RC00000011 * * RC00000038 at various offsets in * * DSNX9CAC or DSNX9TNE * **************************************************************** * RECOMMENDATION: * **************************************************************** Missing code in DB2 recovery code paths caused a cancelled or abended thread to incorrectly skip clean up of WLM-related resources for UDFs that are invoked from within stored procedure instances. Stored procedure instances can occur when an application repeatedly calls a stored procedure that returns result sets but does not close the result sets before the next procedure call. . As a result, the WLM-related resources were orphaned by the cancelled / abending thread. Since WLM and DB2 think that there is still an active user of these WLM resources, the following three symptoms may occur: . 1. If you issue an MVS VARY WLM REFRESH command or an MVS VARY WLM QUIESCE command against the WLM environment that was used by the UDFs, WLM will issue an IWM031I message to say that the refresh or quiesce request is in progress. However, the request will not complete. It will wait for the orphaned resources to be cleaned up. . WORKAROUND for 1: If this problem occurs, it can be resolved by issuing an MVS cancel of the WLM address space. This may result in an expected ABEND04E RC00E50013 from DSNX9SPS and/or DSNX9WCA. . 2. If you issue a STOP DB2 command, it will issue message DSNX922I to notify you that DB2 has begun disconnection of the (WLM) stored procedure address spaces but the process will not complete. DB2 will not issue message DSNX923I to notify you that all (WLM) stored procedure address spaces are disconnected. Instead, DB2 will suspend and hang in module DSNX9SPS waiting for the orphaned resources to be cleaned up. . WORKAROUND for 2: If this problem occurs, it can be resolved either by issuing an MVS cancel of the WLM address space or by issuing a STOP DB2 MODE(FORCE) command. This may result in an expected ABEND04E RC00E50013 from DSNX9SPS and/or DSNX9WCA. . . DB2 code has changed to add in the missing clean up of UDFs that are invoked from inside stored procedure instances. 1 . . ADDITIONAL KEYWORDS: SQLSCALARUDF SQLUDF SQLSP SQLSTOREDPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79545 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECWA PM79545 DSNXEUF0 PM79545 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79545 DSNXECWA DSNXEUF0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECWA DSNXEUF0 LISTEND UK92276 COVER LETTER END UK92278 COVER LETTER START PROBLEM DESCRIPTION(S): PM79546 - **************************************************************** * USERS AFFECTED: All DB2 users of external User Defined * * Functions that have the ALLOW PARALLEL * * option in effect and that are used in I/O * * parallel queries. * **************************************************************** * PROBLEM DESCRIPTION: After running a query that participates * * in I/O query parallelism and whose * * child tasks invoke external UDFs, * * the following symptoms may occur: * * 1. an MVS command to either refresh or * * to quiesce the WLM environment * * issues message IWM031I but does not * * complete * * 2. a STOP DB2 command issues message * * DSNX922I but then hangs and does not * * complete * * 3. a STOP DB2 MODE(FORCE) command hits * * ABEND0C4 RC00000010 RC00000011 * * RC00000038 at various offsets in * * DSNX9CAC or DSNX9TNE * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect code in DB2 I/O query parallelism clean up routines caused DB2 to incorrectly skip clean up of WLM-related 1 resources for ALLOW PARALLEL UDFs that are invoked by the I/O parallelism child tasks. . As a result, the WLM-related resources were orphaned by the thread that ran the parallel query. Since WLM and DB2 thinks that there is still an active user of these WLM resources, the following three symptoms may occur: . 1. If you issue an MVS VARY WLM REFRESH command or an MVS VARY WLM QUIESCE command against the WLM environment that was used by the UDFs, WLM will issue an IWM031I message to say that the refresh or quiesce request is in progress. However, the request will not complete. It will wait for the orphaned resources to be cleaned up. . WORKAROUND for 1: If this problem occurs, it can be resolved by issuing an MVS cancel of the WLM address space. This may result in an expected ABEND04E RC00E50013 from DSNX9SPS and/or DSNX9WCA. . 2. If you issue a STOP DB2 command, it will issue message DSNX922I to notify you that DB2 has begun disconnection of the (WLM) stored procedure address spaces but the process will not complete. DB2 will not issue message DSNX923I to notify you that all (WLM) stored procedure address spaces are disconnected. Instead, DB2 will suspend and hang in module DSNX9SPS waiting for the orphaned resources to be cleaned up. . WORKAROUND for 2: If this problem occurs, it can be resolved either by issuing an MVS cancel of the WLM address space or by issuing a STOP DB2 MODE(FORCE) command. This may result in an expected ABEND04E RC00E50013 from DSNX9SPS and/or DSNX9WCA. . 3. If you issue a STOP DB2 MODE(FORCE) command, without having previously issued a regular STOP DB2 command, then DB2 may encounter ABEND0C4 DSNX9CAC at various offsets or ABEND0C4 DSNX9TNE at various offsets when DB2 attempts to process the orphaned resources. However, DB2 will successfully stop. . . DB2 code has changed to correct the missing clean up of ALLOW PARALLEL UDFs that used by I/O parallel query child tasks. . . ADDITIONAL KEYWORDS: SQLSCALARUDF SQLUDF SQLSP SQLSTOREDPROC DB2PARALL/K SQLIOP PARALLELISM SQLPARALLELISM COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79546 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECL PM79546 DSNXECLF PM79546 DSNXECLN PM79546 DSNXECW PM79546 DSNXECWA PM79546 DSNXECWU PM79546 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79546 DSNXECL DSNXECLF DSNXECLN DSNXECW DSNXECWA DSNXECWU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECL DSNXECLF DSNXECLN DSNXECW DSNXECWA DSNXECWU LISTEND UK92278 COVER LETTER END UK92280 COVER LETTER START PROBLEM DESCRIPTION(S): PM79741 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of RID list * * access. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 rc38 can occur at location * * DSNXSFUN OFFSET02D6 when another thread * * was running a query using RID list * * access. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 rc38 can occur at location DSNXSFUN OFFSET02D6 when another thread is executing a query using RID list access. In a very busy system, when DB2 executes a query with RID list access, it could accidentally free internal storage which is still in use by another thread. Then, when this other thread gains control, an unexpected ABEND0C4 can occur because of it. Please note that as a result of one thread freeing the storage which is in use by another thread, many different kinds of failures (failing symptoms) can occur once the storage is freed. Additionally, this problem can also occur when a pre-v10 bound package that contains a query which uses RID list access is running on DB2 v10. Please note that an earlier apar PM78772 will address this issue. 1 The code in DB2 which incorrectly frees another thread's internal storage has been modified to free the proper storage. Additional Keywords: SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79741 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRFRL PM79741 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79741 DSNXRFRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRFRL LISTEND UK92280 COVER LETTER END UK92286 COVER LETTER START PROBLEM DESCRIPTION(S): PM83887 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: Code to support future new function. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** Changes are required to DB2 10 to make it compatible with a future release of DB2 for z/OS. This APAR updates code in DB2 10 for z/OS so it will be compatible with future releases of DB2 for Z/OS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83887 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGUVR PM83887 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83887 DSNUGUVR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGUVR 1 LISTEND UK92286 COVER LETTER END UK92287 COVER LETTER START PROBLEM DESCRIPTION(S): PM80970 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the TRIM, * * RTRIM, or STRIP scalar functions. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * a query that explicitly or implicitly * * invokes the TRIM, RTRIM, or STRIP * * scalar functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result can be returned for a query that explicitly or implicitly invokes the TRIM, RTRIM, or STRIP scalar functions. The incorrect result can occur because DB2 does not properly save the input or trim character string's CCSID so an improper CCSID is used for character comparison which can then result in an incorrect mismatch. The problem was reported when using MIXED character data. For example if DSNHDECP specifies these settings, ENSCHEME=EBCDIC Japanese CCSID 930 (Japanese Extended Katakana) MIXED/Graphic data support the following query can return an incorrect result when the input string and trim character CCSIDs are not saved properly. SELECT RTRIM('abcd äxäyäzâAâBâCâXâYâZ xyz', 'abcd äxäyäzâXâYâZ xyz') RTRIM FROM SYSIBM.SYSDUMMY1; The code in DB2 which supports the RTRIM functions has been modified to properly save the CCSIDs for both the input and trim strings during processing. Additional Keywords: SQLGRAPHIC SQLTRIM SQLRTRIM SQLSTRIP DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80970 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: 1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRSB2 PM80970 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80970 DSNXRSB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRSB2 LISTEND UK92287 COVER LETTER END UK92288 COVER LETTER START PROBLEM DESCRIPTION(S): PM80978 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS RRSAF users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 was cancelled, and WebSphere * * preserved its TCB which had been * * connected to DB2. WebSphere then * * attempted to use the old DB2 RRSAF * * connection blocks to do a new Identify * * to DB2 and got an ABEND0C4 in module * * DSN3ID00. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 was cancelled, and WebSphere preserved its TCB which had been connected to DB2. WebSphere then attempted to use the old DB2 RRSAF connection block to issue a new Identify to DB2 and received an ABEND0C4 in module DSN3ID00. This problem would not occur if the WebSphere TCB terminated, because DB2 would have freed its task related storage. Module DSNARA70 has been updated to reset a status bit during Identify processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80978 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNARA70 PM80978 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80978 DSNARA70 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNARA70 1 LISTEND UK92288 COVER LETTER END UK92320 COVER LETTER START PROBLEM DESCRIPTION(S): PM77184 - **************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and * * SQLJ version 3.64.119 is provided by * * this APAR ( JCCV364119 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for DB2 z/OS V10 and DB2 z/OS V9 and * * the alternate supplemental driver * * for DB2 z/OS V8. ( JCCZOSDB2V10, * * JCCZOSDB2V9, JCCZOSDB2V8 ) * * * * This APAR delivers a new release (3.64) * * of the IBM Data Server Driver for JDBC * * and SQLJ providing an accumulation of * * defect fixes and enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: _______________________________________________________________ All Connectivities: Driver returns an SQLCODE401 (-401) While updating a column defined in DB2 as SMALLINT using the setBoolean() API of the java.sql.PreparedStatement interface. This issue is fixed.(wsdbu01060873) _______________________________________________________________ Type-4 XA Connectivity: In a workload balancing and XA transaction environment, an SQLCODE4228 (-4228) error might return to the application if auto failover has occurred during a local transaction. (wsdbu01060779) _______________________________________________________________ Type-4 connectivity:A java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 255, may be thrown by the driver when invoking a stored procedure that has array types as parameters and number of parameters are more than 83. The problem has been fixed. (wsdbu01061046) _______________________________________________________________ Type-2 z/OS Connectivity: For an IMS MPP/BMP/IFP application executing in a Persistent JVM environment and calling a Java application which makes DB2 calls through the driver, this 1 driver provides a new partial Reset interface to allow reuse of the JDBC Connection object which can boost performance. For more detailed information, please refer to IMS APAR PM80880. (wsdbu01061827) The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR. COMPONENT: 5740-XYR02-JDBAA12 APARS FIXED: PM77184 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58951 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58951 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAQJBA PM77184 DSNAQJBB PM77184 DSNAQJB1 PM77184 DSNAQJB2 PM77184 DSNAQJB3 PM77184 DSNAQJB4 PM77184 DSNAQJB5 PM77184 DSNAQJB6 PM77184 DSNAQJB7 PM77184 DSNAQJB8 PM77184 DSNAQJC1 PM77184 DSNAQJC2 PM77184 DSNAQJC3 PM77184 DSNAQJC4 PM77184 DSNAQJRM PM77184 DSNAQJS1 PM77184 DSNAQJS2 PM77184 DSNAQ3CA PM77184 DSNAQ3CC PM77184 DSNAQ3CE PM77184 DSNAQ3CF PM77184 DSNAQ3CM PM77184 DSNAQ3C0 PM77184 DSNAQ3C1 PM77184 DSNAQ3C2 PM77184 DSNAQ3C3 PM77184 DSNAQ3C4 PM77184 1 DSNAQ3C5 PM77184 DSNAQ3C6 PM77184 DSNAQ3C7 PM77184 DSNAQ3C8 PM77184 DSNAQ3C9 PM77184 DSNAQ3E1 PM77184 DSNAQ6CC PM77184 DSNAQ6CE PM77184 DSNAQ6CF PM77184 DSNAQ6CM PM77184 DSNAQ6C0 PM77184 DSNAQ6C1 PM77184 DSNAQ6C2 PM77184 DSNAQ6C3 PM77184 DSNAQ6C4 PM77184 DSNAQ6C5 PM77184 DSNAQ6C6 PM77184 DSNAQ6C7 PM77184 DSNAQ6C9 PM77184 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77184 DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAQ3CA DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7 DSNAQ3C8 DSNAQ3C9 DSNAQ6CC DSNAQ6CE DSNAQ6CF DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 1 DSNAQ6C4 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9 MACROS DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3E1 LISTEND UK92320 COVER LETTER END UK92323 COVER LETTER START PROBLEM DESCRIPTION(S): PM80763 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * views that contains aggregate functions * * and decimal data types. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C7 DSNXRDEC at OFFSET DBF4 * * may occur for an SQL statement that * * satisfies the following conditions: * * 1. The statement references to a view. * * 2. The view contains an arithmetic * * operation that involves SUM or AVG * * aggregate functions and decimal types. * * 3. The DEC options at create view time * * and reference time are different * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C7 DSNXRDEC at OFFSET DBF4 may occur for an SQL statement that satisfies the following conditions: 1. The statement references to a view. 2. The view contains an arithmetic operation that involves SUM or AVG aggregate functions and decimal types. 3. The DEC options at create view time and reference time 1 are different. An example of the possible failing case is like : CREATE TABLE T1 (C1_DEC DECIMAL(9, 7) NOT NULL WITH DEFAULT 0); INSERT INTO T1 VALUES (.00001); * Use DEC(15) CREATE VIEW V1 (VC1) AS SELECT (AVG(C1_DEC) * 40000) + 1 FROM T1; * Use DEC(31) SELECT * FROM V1; An abend may occur for the SELECT statement above because the aggregate function AVG result length is not computed correctly. DB2 was fixed to handle the arithmetic operation that involves SUM or AVERAGE aggregate functions and decimal types correctly. Additional Keywords: SQLSUM SQLAVG SQLVIEW SQLDECIMAL SQLARITH SQLDECIMAL31 SQLDEC31 SQLDECIMAL15 SQLDEC15 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80763 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM80763: See PM80763 APAR/PTF text for additional information about why a REBIND is necessary. PM80763 corrects a problem of ABEND0C7 DSNXRDEC at OFFSET DBF4 may occur for an SQL statement that satisfies the following conditions: 1. The statement references to a view. 2. The view contains an arithmetic operation that involves SUM or AVG aggregate functions and decimal types. 3. The DEC options at create view time and reference time are different. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOARI PM80763 DSNXOBFA PM80763 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM80763 DSNXOARI DSNXOBFA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOARI DSNXOBFA LISTEND UK92323 COVER LETTER END UK92325 COVER LETTER START PROBLEM DESCRIPTION(S): PM77185 - **************************************************************** * USERS AFFECTED: All Users of the IBM Data * * Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and * * SQLJ version 4.14.126 is provided by * * this APAR ( JCCV414126 ) * * * * This APAR is applicable to IBM Data * * Sever Driver for JDBC and SQLJ * * for both DB2 z/OS V10 and DB2 z/OS V9 * * ( JCCZOSDB2V10, JCCZOSDB2V9 ) * * * * This APAR delivers a new release (4.14) * * of the IBM Data Server Driver for JDBC * * and SQLJ providing an accumulation of * * defect fixes and enhancements. * * * * Individual items are documented in the * * APAR summary section that follows. * **************************************************************** * RECOMMENDATION: * **************************************************************** JCC sub-category keywords: JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ The following changes are delivered in this APAR: _______________________________________________________________ All Connectivities: Driver returns an SQLCODE401 (-401) While updating a column defined in DB2 as SMALLINT using the setBoolean() API of the java.sql.PreparedStatement interface. This issue is fixed.(wsdbu01060873) _______________________________________________________________ Type-4 XA Connectivity: In a workload balancing and XA transaction environment, an SQLCODE4228 (-4228) error might return to the application if auto failover has occurred during a local transaction. (wsdbu01060779) _______________________________________________________________ Type-4 connectivity:A java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 255, may be thrown by the driver when invoking a stored procedure that has array types as 1 parameters and number of parameters are more than 83. The problem has been fixed. (wsdbu01061046) _______________________________________________________________ Type-2 z/OS Connectivity: For an IMS MPP/BMP/IFP application executing in a Persistent JVM environment and calling a Java application which makes DB2 calls through the driver, this driver provides a new partial Reset interface to allow reuse of the JDBC Connection object which can boost performance. For more detailed information, please refer to IMS APAR PM80880. (wsdbu01061827) The items described in the APAR Problem Summary have been resolved as noted in the summary and included in this APAR. COMPONENT: 5740-XYR02-JDBAA12 APARS FIXED: PM77185 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58952 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58952 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAJJC1 PM77185 DSNAJJC2 PM77185 DSNAJ3CC PM77185 DSNAJ3CE PM77185 DSNAJ3CF PM77185 DSNAJ3CM PM77185 DSNAJ3C0 PM77185 DSNAJ3C1 PM77185 DSNAJ3C2 PM77185 DSNAJ3C3 PM77185 DSNAJ3C4 PM77185 DSNAJ3C5 PM77185 DSNAJ3C6 PM77185 DSNAJ3C7 PM77185 DSNAJ3C9 PM77185 DSNAJ6CC PM77185 DSNAJ6CE PM77185 DSNAJ6CF PM77185 DSNAJ6CM PM77185 DSNAJ6C0 PM77185 DSNAJ6C1 PM77185 1 DSNAJ6C2 PM77185 DSNAJ6C3 PM77185 DSNAJ6C4 PM77185 DSNAJ6C5 PM77185 DSNAJ6C6 PM77185 DSNAJ6C7 PM77185 DSNAJ6C9 PM77185 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77185 DSNAJJC1 DSNAJJC2 DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5 DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5 DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9 MACROS DSNAJJC1 DSNAJJC2 LISTEND UK92325 COVER LETTER END UK92329 COVER LETTER START PROBLEM DESCRIPTION(S): PM83201 - 1 **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: The following abends are reported: * * . 04E-00E50097 DSNLTPDI+258A (V9 ). * * DB2 remains available. * * . 04E-00E50079 DSNLTPDI+2004 (V10). * * This will be followed by a DB2 * * termination indicated by message * * DSNV086E with reason 00E50054. * **************************************************************** * RECOMMENDATION: * **************************************************************** During automatic indoubt thread resolution ("resync") processing, DB2 accepts a resync connection that was initiated by a remote coordinator and receives a decision (commit or abort). The indoubt thread is resumed with the appropriate decision, and the decision is carried out, just as the inbound resync connection suffers a communication error. The communication failure causes the resync thread to be terminated which then incorrectly frees a (ROB) control block that the indoubt thread is still dependent on. The indoubt thread, now with a decision, abends as reported. DB2 has been changed to ensure that the (ROB) control block remains available for the benefit of the indoubt thread that's still dependant on its presence. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83201 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTPDI PM83201 DSNLTRPA PM83201 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83201 DSNLTPDI DSNLTRPA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTPDI DSNLTRPA LISTEND UK92329 COVER LETTER END UK92333 COVER LETTER START PROBLEM DESCRIPTION(S): PM81491 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** 1 * PROBLEM DESCRIPTION: There are 2 known symptoms: * * * * 1. A thread hung in CSECT DSNTABA. * * 2. ABEND378 RC0000001C RC1C as a * * result of a call from CSECT * * DSNTLSUS. * **************************************************************** * RECOMMENDATION: * **************************************************************** A thread involved in an IRLM timeout may require a UTF/EBCDIC conversion. Internal routine to preform such conversion may issue another IRLM call under the same DB2 agent structure. At this point there are 2 possible cases: 1. If the subsequent request times out, it will incorrectly free internal agent storage and return. The original IRLM request will attempt to free the same storage and result in ABEND378 RC0000001C RC1C. 2. If the original request was cancelled while suspended in IRLM, but was already involved in partial timeout processing in IRLM before the cancel, the subsequent request will clear out an internal pointer upon its completion. DB2 system agent uses this pointer during abort processing to see if SYNC should be preformed on the original IRLM request, and will inocrrectly issue the IRLM SYNC request. This will result in a hang of this system agent in CSECT DSNTABA Change DB2 logic to avoid issuing a lock request during the UTF/EBCDIC conversion. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81491 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTLSUS PM81491 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81491 DSNTLSUS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLSUS LISTEND UK92333 COVER LETTER END UK92355 COVER LETTER START PROBLEM DESCRIPTION(S): PM81869 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for zOS users of REFRESH * * TABLE. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIWSET * * ERQUAL5012 When REFRESH TABLE is * * executed more than once within a unit * * of work. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a REFRESH TABLE statement is executed multiple times, DB2 did not clean up some structures at the end of the first execution of the REFRESH TABLE statement. . If a subsequent REFRESH TABLE statement is issued of the same section, DB2 may use residual information from the previous invocation resulting in the reported ABEND04E in DSNIWSET. . Please note, this issue occurs only if both statements were issued in the same unit of work. A COMMIT/ROLLBACK will do the structure clean up when issued. DB2 has been modified to clean up the REFRESH TABLE structures after each invocation of the statement. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81869 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXERT PM81869 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81869 DSNXERT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERT LISTEND UK92355 COVER LETTER END UK92357 COVER LETTER START PROBLEM DESCRIPTION(S): PM82403 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Large Objects * * (LOBs) in a data sharing environment. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNOGLOB 5008 (ERQUAL5008) * * when fetching LOB data in a data * * sharing environment. * 1 * * * In association with the abend, DB2 * * might also experience a storage * * overlay. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOGLOB 5008 (ERQUAL 5008) when fetching LOB data in a data sharing environment. In association with the abend, DB2 might also experience a storage overlay, resulting in various other abends and possibly a DB2 crash. The abend and potential storage overlay are all secondary symptoms caused by a page regression in a data sharing environment when multiple threads are fetching and updating the same LOB column. Please refer to APAR PM82301 for more information regarding how the page regression can occur and what factors can contribute to it. This APAR does not resolve the page regression problem. However, APAR PM82301 does. DB2 should not abend and unexpected storage overlays resulting from page regression should not occur. Instead, DB2 should attempt to detect a potential page regression by placing a sanity check on the page type and take an intentional abend when the page type is not as expected. The code in DB2 is modified to avoid the abend and prevent a storage overlay. Additional Keywords: SQLLOB SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82403 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOGLOB PM82403 DSNOMAPX PM82403 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82403 DSNOGLOB DSNOMAPX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOGLOB DSNOMAPX LISTEND UK92357 COVER LETTER END UK92361 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM76636 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG utility. * **************************************************************** * PROBLEM DESCRIPTION: Restart in the SWITCH phase of a REORG * * of a table space with hash organization * * caused downlevel pages to be copied to * * the inline copy dataset. * * * * Serviceability for REORG to sanity * * check down level inline copied pages. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User restarted a REORG TABLESPACE utility on a table space with hash organization that had previously failed in the SWITCH phase. The restart of the utility completed successfully, but it was found that there were downlevel data pages copied to the sequential inline copy dataset. This was caused by an incorrect reference to the original data set prior to REORG on restart. Also added serviceability code for REORG to sanity check down level pages in the inline copy dataset. Code has been modified to correct the aforementioned restart issue on a hash table space, as well as adding serviceability code to prevent copying of downlevel inline copy pages. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76636 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURFIT PM76636 DSNURMPG PM76636 DSNURSWD PM76636 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76636 DSNURFIT DSNURMPG DSNURSWD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURFIT DSNURMPG DSNURSWD LISTEND UK92361 COVER LETTER END UK92381 COVER LETTER START PROBLEM DESCRIPTION(S): PM79448 - **************************************************************** 1 * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of UNLOAD DELIMITED * **************************************************************** * PROBLEM DESCRIPTION: UNLOAD DELIMITED of a table with EBCDIC * * MBCS without specifying any character * * delimiters, generates invalid default * * delimiters. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** An UNLOAD DELIMITED utility was run on a table with an encoding scheme of EBCDIC MBCS. The UNLOAD statement did not include any character delimiter values (CHARDEL COLDEL DECPT), causing the unloaded data to include default character delimiters. A subsequent LOAD utility, using the generated SYSREC and SYSPUNCH from the UNLOAD failed with MSGDSNU1141I - INVALID DELIMITER CHARACTER ',' (X'6B') and ended with RC8. The default character delimiter values are not valid for EBCDIC MIXED and DBCS tables. If no character delimiters are specified on the UNLOAD statement, UNLOAD will now issue MSGDSNU1141I - INVALID DELIMITER CHARACTER and end with RC8. For EBCDIC MIXED or DBCS tables, user specified delimiters must be x'40' or below for CHARDEL and COLDEL and x'4B' or below for DECPT. The UNLOAD utility has been modified to issue a DSNU1141I message and end with RC8 if defaulted delimiter values are invalid for the target table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79448 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURILD PM79448 DSNUULIA PM79448 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79448 DSNURILD DSNUULIA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURILD DSNUULIA LISTEND UK92381 COVER LETTER END UK92420 COVER LETTER START PROBLEM DESCRIPTION(S): PM78062 - **************************************************************** 1 * USERS AFFECTED: All users of the query 51 in DSNTESQ * * sample. * **************************************************************** * PROBLEM DESCRIPTION: Query 51 did not take clone tables * * into account and returned incorrect * * rows for views that reference clone * * tables. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNTESQ provides queries to identify logical inconsistency in the catalog. Query 51 did not take clone tables into account and returned incorrect rows for views that reference clone tables. The same problem would also happen if there were views that reference history tables. DSNTESQ Query 51 has been updated to correct the problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78062 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTESQ PM78062 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78062 DSNTESQ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTESQ LISTEND UK92420 COVER LETTER END UK92457 COVER LETTER START PROBLEM DESCRIPTION(S): PM82806 - **************************************************************** * USERS AFFECTED: All DB2 users of the dynamic statement cache * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNGEFBK+06D6 can be * * received when using cached dynamic * * statements. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using cached dynamic statements a RUNSTATS utility was run causing some of the statements to be invalidated. This resulted in an ABEND0C4 in DSNGEFBK+06D6. The DB2 code has been updated to prevent the abend when cached dynamic statements are invalidated. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82806 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEPDL PM82806 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82806 DSNGEPDL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEPDL LISTEND UK92457 COVER LETTER END UK92460 COVER LETTER START PROBLEM DESCRIPTION(S): PM81771 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of UNION ALL * * with FETCH FIRST n ROWS ONLY clause. * **************************************************************** * PROBLEM DESCRIPTION: This apar fixes two problems for UNION * * ALL when the FETCH FIRST n ROWS ONLY * * clause is used against a UNION ALL * * result. * * * * 1. INCORROUT happens when a UNION * * ALL with FETCH FIRST n ROWS ONLY * * clause is used against the UNION * * ALL result in a loop. * * * * 2. DB2 incorrectly issue SQLCODE -811 * * when a UNION ALL with FETCH FIRST * * n ROWS ONLY clause is used against * * a UNION ALL result and the result * * is used in an INSERT with SELECT * * clause for MERGE * **************************************************************** * RECOMMENDATION: * **************************************************************** The following two examples illustrate the problems. Example 1. 1. Create a table and populate it. CREATE TABLE T1 (ID INT, ID2 INT, C1 CHAR(10)); INSERT INTO T1 VALUES (1, 1, 'A1'); INSERT INTO T1 VALUES (2, 2, 'A2'); 1 2. SELECT INTO from a UNION ALL with FETCH FIRST 1 ROWS ONLY clause. DCL HVC CHAR(10) VARYING; DCL ID BIN FIXED(31); DO ID = 1 TO 2 WHILE(SQLCODE >= 0 ); EXEC SQL SELECT B1.C1 INTO :HVC FROM (SELECT C1 FROM T1 WHERE ID = :ID UNION ALL SELECT C1 FROM T1 WHERE ID2 = :ID FETCH FIRST 1 ROWS ONLY) B1 WITH UR; END; The application expects HVC return values of A1 and A2, but DB2 only returns A1 and incorrectly returns SQLCODE +100 for the second row. DB2 code does not clean up the internal counter for FETCH FIRST 1 ROWS ONLY for UNION ALL before the second SELECT INTO in the loop, and it leads to SQLCODE +100 eventually. Example 2. 1. Create a table and populate it. CREATE TABLE T1 (ID INT, C1 CHAR(10)); INSERT INTO T1 VALUES (1, 'A1'); INSERT INTO T1 VALUES (1, 'A2'); 2.INSERT with SELECT from UNION ALL with FETCH FIRST 1 ROWS ONLY for a MERGE statement DCL ID BIN FIXED(31); DCL ID3 BIN FIXED(31); DCL HVC CHAR(10) VARYING; ID = 20; ID3 = 1; HVC = 'A20'; EXEC SQL MERGE INTO T1 T11 USING (VALUES (:ID, :HVC) FOR 1 ROWS) AS MT1 (ID, C1) ON (T11.ID = MT1.ID) WHEN MATCHED THEN UPDATE SET C1=MT1.C1 1 WHEN NOT MATCHED THEN INSERT (C1) VALUES(SELECT B1.C1 FROM ( SELECT C1 FROM T1 WHERE ID = :ID3 UNION ALL SELECT C1 FROM T1 WHERE ID = :ID3 FETCH FIRST 1 ROW ONLY) B1) NOT ATOMIC CONTINUE ON SQLEXCEPTION; DB2 is expected to insert a new row with C1='A20' into table T1, but instead DB2 incorrectly returns SQLCODE -811. DB2 code does not set internal structure for FETCH FIRST 1 ROWS ONLY with UNION ALL correctly, and it eventually leads to -811. Please note, to make the fix for the second problem effective for a static application, it must be rebound after application of this PTF. DB2 code has been fixed to address the above two problems. Additional Keywords: SQLUNIONALL SQLCODE811 SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81771 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM81771: See PM81771 APAR/PTF text for additional information about why a REBIND is necessary. PM81771 corrects two problems. 1. A problem of INCORROUT for UNION ALL with FETCH FIRST N ROWS ONLY. 2. A problem of incorrect SQLCODE -811 for UNION ALL with FETCH FIRST N ROWS ONLY in the MERGE INSERT with SELECT clause. To make the fix for the second problem effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGMRG PM81771 DSNXRUNA PM81771 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81771 DSNXGMRG DSNXRUNA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXGMRG DSNXRUNA LISTEND UK92460 COVER LETTER END UK92471 COVER LETTER START PROBLEM DESCRIPTION(S): PM82860 - INTEGRITY PROBLEM COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM82860 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM INTEGRITY: INTEGRITY SET: UK92471 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRJCLIN PM82860 DXRRL500 PM82860 DXRRL504 PM82860 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82860 DXRJCLIN DXRRL500 DXRRL504 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL500 DXRRL504 MACROS DXRJCLIN LISTEND UK92471 COVER LETTER END UK92474 COVER LETTER START PROBLEM DESCRIPTION(S): PM83307 - **************************************************************** * USERS AFFECTED: All DB2 V10 for z/OS users of plans bound on * * DB2 V7 or earlier. * **************************************************************** * PROBLEM DESCRIPTION: Unicode Conversion Services is called * * with a ccsid of 0. This causes slower * * performance to load the plan. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a DB2 plan bound on DB2 V7 or earlier is run Unicode Conversion Services is called to convert a name from EBCDIC to Unicode. The CCSID passed in can be 0. This can affect 1 the performance of loading the plan but the plan will still run successfully. DB2 code has been updated to call Unicode Conversion Services with the correct CCSID when loading a plan bound on DB2 V7 or earlier. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83307 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGESLC PM83307 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83307 DSNGESLC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGESLC LISTEND UK92474 COVER LETTER END UK92478 COVER LETTER START PROBLEM DESCRIPTION(S): PM79279 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of LOBs with an * * Uncommitted Read (UR) isolation level. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90110 can occur at * * location DSNONLLE 5065 (ERQUAL5065) * * when fetching LOB data while using an * * Uncommitted Read (UR) isolation level. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90110 can occur at location DSNONLLE 5065 when fetching LOB data while using an Uncommitted Read isolation level when the LOB map page is marked as invalid. When fetching LOB columns with an Uncommitted Read isolation level (when its LOB map page is marked as invalid), instead of failing as mentioned above, DB2 should issue an SQLCODE -904 (SQLCODE904) with a reason code 00C900D0 (rc00C900D0). The following example might help illustrate the problem: DDL: --- SET CURRENT RULES='STD'; CREATE DATABASE MYDB; CREATE TABLESPACE MYTS IN MYDB CCSID UNICODE MAXPARTITIONS 3; 1 CREATE TABLE SYSADM.MYTABLE (COL1 INT, COL2 CLOB(1M) INLINE LENGTH 0, COL3 CLOB(1M) INLINE LENGTH 0, COL4 CHAR(10) ) IN MYDB.MYTS; INSERT INTO SYSADM.MYTABLE VALUES (1, 'COL1CLOB','COL1CLOB','COL1CHAR'); INSERT INTO SYSADM.MYTABLE VALUES (2, 'COL2CLOB','COL2CLOB','COL2CHAR'); INSERT INTO SYSADM.MYTABLE VALUES(3, 'COL3CLOB','COL3CLOB','COL3CHAR'); Query: ----- SELECT LENGTH(COL2) FROM SYSADM.MYTABLE WHERE COL1 = 1 WITH UR; SELECT COL2 FROM SYSADM.MYTABLE WHERE COL1 = 1 WITH UR; The code in DB2 is modified to prevent the abend and issue the appropriate SQLCODE904. Additional Keywords: SQLLOB SQLCODE904 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79279 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNONLLE PM79279 DSNOTCSO PM79279 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79279 DSNONLLE DSNOTCSO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNONLLE DSNOTCSO LISTEND UK92478 COVER LETTER END UK92479 COVER LETTER START PROBLEM DESCRIPTION(S): PM82258 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * that specify a Declared Global Temporary * * Table (DGTT) in a DROP statement. * **************************************************************** * PROBLEM DESCRIPTION: Users may encounter poor performance * * for long running threads which * * execute DROP statements with DGTT * * specified. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** Users may encounter poor performance when a DGTT is specified in a DROP statement. This may occur when many DGTTs are being dropped in the same long running thread because DB2 keeps a DB2 thread/connection-level history of DB2 objects that are dropped/altered by applications in a specific DB2 thread. This history tracking of dropped/altered objects is thread based and normally must persist for the life of the DB2 thread. After a very high threshold point on the single long running DB2 thread/connection, the DGTT change history may accumulate and negatively impact performance. Performance has been optimized for dropping of DGTTs when many DGTTs have been dropped in the same DB2 thread, such that the DGTT history will no longer cause the reported performance degradation. ADDITIONAL KEYWORDS: SQLDGTT PERFM SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82258 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXISB5 PM82258 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82258 DSNXISB5 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXISB5 LISTEND UK92479 COVER LETTER END UK92481 COVER LETTER START PROBLEM DESCRIPTION(S): PM81820 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of SQL table * * function and outer join. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at DSNXGRDS.DSNXOQ2 * * OFFSET2334 could occur when binding an * * SQL statement with outer join and * * SQL table function involved. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000038 at DSNXGRDS.DSNXOQ2 OFFSET2334 could 1 occur when an SQL statement satisfied the following conditions: 1. It has an outer join to an SQL table function or 1. It references an SQL table function which references an SQL statement with outer join in the RETURN statement of the table function. The following example could recreate the abend, CREATE TABLE T1(T1C1 INTEGER, T1C2 VARCHAR(5)); CREATE TABLE T2(T2C1 INTEGER, T2C2 VARCHAR(4)); 1.CREATE FUNCTION PM81820(P1 VARCHAR(5)) RETURNS TABLE (TUFC1 INTEGER) LANGUAGE SQL READS SQL DATA NO EXTERNAL ACTION DETERMINISTIC RETURN (SELECT T1C1 FROM T1 WHERE T1C2=P1); SELECT * FROM TABLE(PM81820('ABC')) AS A , (SELECT T1C1 FROM T1 FULL OUTER JOIN (SELECT T2C1 FROM T2, T1 WHERE T2C1=T1C1) B ON B.T2C1=T1C1) C WHERE A.TUFC1 = C.T1C1; 2.CREATE FUNCTION PM81820(P1 VARCHAR(5)) RETURNS TABLE (TUFC1 INTEGER) LANGUAGE SQL READS SQL DATA NO EXTERNAL ACTION DETERMINISTIC RETURN (SELECT T1C1 FROM T1 FULL OUTER JOIN (SELECT T2C1 FROM T2, T1 WHERE T2C1=T1C1) B ON B.T2C1=T1C1); SELECT * FROM TABLE(PM81820('ABC')) AS A ; DB2 doesn't handle the above SQL statements correctly, it causes abend. DB2 is updated to handle the SQL table function involved SQL statement correctly. Additional Keywords: SQLTUDF SQLTABLEUDF SQLOUTERJOIN SQLFULLJOIN SQLOUTER SQLJOIN SQLLEFTJOIN SQLLEFT SQLRIGHTJOIN SQLRIGHT OFFSET2334 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81820 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOQ2 PM81820 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM81820 DSNXOQ2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOQ2 LISTEND UK92481 COVER LETTER END UK92490 COVER LETTER START PROBLEM DESCRIPTION(S): PM82763 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E 00C90101 ERQUAL5002 in * * DSNODAL1 when accessing a LOB space * * after a LOAD utility has been run. * * * * ABEND04E RC00C200A4 in DSNB5COM during * * a LOAD, followed by DB2 subsystem * * termination RC00E50702. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a LOAD utility is updating multiple LOG NO LOB spaces, there is a timing window in which DB2 may schedule a second write engine for a LOB while one is already running. Since the LOB is opened in format-write mode, the concurrent running of multiple write engines can result in previously formatted pages being written over with zeroes, which can cause a subsequent ABEND04E RC00C90101 in DSNODAL1. It may also result in a write I/O failure which causes an ABEND04E RC00C200A4 in DSNB5COM, bringing down DB2. The logic which drives writes for LOG NO LOBs has been modified to ensure that a second write engine will not be scheduled if the LOB is being accessed in format-write mode. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82763 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1FLW PM82763 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82763 DSNB1FLW THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1FLW 1 LISTEND UK92490 COVER LETTER END UK92492 COVER LETTER START PROBLEM DESCRIPTION(S): PM79464 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of parallelism. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 DSNXOSR:P014 * * may occur when a query has one miniplan * * with PARALLELISM ON and MERGC = YES * * and SORTN_JOIN = YES and * * PRIMARY_ACCESSTYPE = 'T' and the query * * contains a GROUP BY clause. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 DSNXOSR:P014 may occur when a query has one miniplan with PARALLELISM ON and MERGC = YES and SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T' and the query contains a GROUP BY clause. The following is an example of such failing SQL: SELECT T1.C1, T1.C2, T1.C3 FROM T1, T2 WHERE T2.C1 ... AND T1.C4 .. GROUP BY T1.C1, T1.C2, T1,C3 Note: T1 NLJ T2, T2 miniplan shows MERGC = YES, parallel join, SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T'. The bindtime code in DB2 is modified to correct the sort key set up for a query with a GROUP BY clause that has SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T' and MERGC = YES and parallelism is ON. Additional Keywords: ABEND04E RC00E70005 SQLGROUPBY SQLNLJ NLJ SQLPARALLELISM SQLCPUP DEGREEANY DB2PARALL/K PARALLELISM SQLSPARSEINDEX SPARSEINDEX MERGC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79464 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM79464: See PM79464 APAR/PTF text for additional information about why a REBIND is necessary. PM79464 corrects a problem of ABEND04E RC00E70005 DSNXOSR:P014 when a query has one miniplan with PARALLELISM ON and MERGC = YES and SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T' and the query has a GROUP BY clause. 1 To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOSR PM79464 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79464 DSNXOSR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSR LISTEND UK92492 COVER LETTER END UK92494 COVER LETTER START PROBLEM DESCRIPTION(S): PM84765 - **************************************************************** * USERS AFFECTED: All DB2 V11 users of IRLM230 (HIR2230). * **************************************************************** * PROBLEM DESCRIPTION: New option for QUERYFST request to * * query for a lock waiter. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM QUERYFST request is updated to support DB2 request for querying a lock waiter in IRLM This APAR adds a new option (QWAITER) to QUERYFST request used by DB2. IRLM will set appropriate return and feebback code if any waiter exists in IRLM when the request was issued. RC = 0 indicates existence of waiter(s) for the lock resource RC = 4 with RLPRCB1 would indicate no waiters in IRLM for the lock resource. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM84765 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL1QF PM84765 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84765 DXRRL1QF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL1QF 1 LISTEND UK92494 COVER LETTER END UK92517 COVER LETTER START PROBLEM DESCRIPTION(S): PM80263 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 users of SQL condition * * handlers. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2000C IN DSNSVSVB +0AC2 * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 SQL condition handler processing sometimes allocates internal control blocks to maintain certain diagnostic information associated with the condition that caused the handler to be invoked. These control blocks are only freed upon exit of a stored procedure. This means that if an application had excessive entries into SQL condition handlers (e.g. 100+ million), the allocation of these internal control blocks may cause out-of-storage ABEND conditions, such as the symptom ABEND. DB2 code has been modified to free the noted control blocks at the exit of SQL condition handler, instead of at the end of the stored procedure. Additional Keywords: SQLSTORAGE DB2STGLK/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80263 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRSPL PM80263 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80263 DSNXRSPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRSPL LISTEND UK92517 COVER LETTER END UK92539 COVER LETTER START PROBLEM DESCRIPTION(S): PM80699 - **************************************************************** 1 * USERS AFFECTED: DB2 9 and 10 for z/OS users whose queries * * contain a GROUP BY list which has a SUBSTR * * or YEAR function as well as the column * * referenced by the function. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may be returned for a * * query with a GROUP BY list which has * * a SUBSTR or YEAR function and the * * column referenced by the function. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output may be returned for a query with a GROUP BY list if all the following conditions are satisfied: 1. The GROUP BY list contains a SUBSTR or YEAR function as well as the column referenced by the function; 2. The function appears before the column it references in the GROUP BY list; 3. The function preserves the order of the column it references; 4. There is an index supporting the avoidance of the GROUP BY sort and the index is selected. For example, SELECT SUBSTR(C1,1,4), C1, COUNT(*) FROM T1 GROUP BY SUBSTR(C1,1,4), C1; C1 is a CHAR(10) column. There is an index IX1 created on T1.C1. The DB2 optimizer may select an access path without sort if IX1 is used to access T1 because SUBSTR(C1,1,4) preserves the order of C1. Incorrect output may occur for the query above. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLGROUPBY SQLSUBSTR SQLYEAR Code has been fixed to give correct output for queries described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80699 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM80699: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM80699 corrects a problem that incorrect output may be returned for a query with a GROUP BY list which has a SUBSTR or 1 YEAR function as well as the column referenced by the function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM78070: See PM78070 APAR/PTF text for additional information about why a REBIND is necessary. PM78070 corrects a problem of incorrect output that can happen for a query which contains UNION, EXCEPT, EXCEPT ALL or ORDER BY and whose top query block has exactly one table. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPRP PM80699 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80699 DSNXOPRP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRP LISTEND UK92539 COVER LETTER END UK92609 COVER LETTER START PROBLEM DESCRIPTION(S): PM71744 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 10 for z/OS offers no generic * * solution to trigger the externalization * * of pending real-time statistics into * * the catalog tables * * SYSIBM.SYSTABLESPACESTATS and * * SYSIBM.SYSINDEXSPACESTATS on demand. * **************************************************************** * RECOMMENDATION: APPLY PTF. * **************************************************************** For applications that rely on real-time statistics (RTS) the asynchronous externalization process of RTS might be too imprecise. For these kind of applications a callable interface that can trigger the externalization of pending RTS changes is needed. 1 This APAR adds a new MODE option to the ACCESS DATABASE command. The new option "STATS" can be used to externalize pending real-time statistics. New Syntax: .-,-------------. V | >>-ACCESS--DATABASE(-+---database-name-+-----+-)---------------> +-*---------------------+ +-dbname1:dbname2-------+ +-dbname*---------------+ +-*dbname---------------+ +-*dbname*--------------+ '-*dbstring1*dbstring2*-' .-,----------. V | >--SPACENAM--(--+---space-name-+--------------+--)-------------> +-*---------------------------+ +-spacename1:spacename2-------+ +-spacename*------------------+ +-*spacename------------------+ +-*spacename*-----------------+ '-*spacestring1*spacestring2*-' >--+---------------------------------------+-------------------> | .-,---------------------. | | V | | '-PART--(----+-integer-----------+-+--)-' '-integer1:integer2-' >--MODE--(--+-OPEN----+--)------------------------------------>< +-NGBPDEP-+ '-STATS---' New option description: MODE( mode-value ) STATS: Externalizes the in-memory real-time statistics to the appropriate catalog tables. In data sharing environments, the in-memory statistics are externalized for all members. This mode does not physically open the page sets or change the states of the page sets. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71744 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM71744 introduces the following changes to externals: 1 A new MODE "STATS" is added to the ACCESS DATABASE command. .-,-------------. V | >>-ACCESS--DATABASE(-+---database-name-+-----+-)---------------> +-*---------------------+ +-dbname1:dbname2-------+ +-dbname*---------------+ +-*dbname---------------+ +-*dbname*--------------+ '-*dbstring1*dbstring2*-' .-,----------. V | >--SPACENAM--(--+---space-name-+--------------+--)-------------> +-*---------------------------+ +-spacename1:spacename2-------+ +-spacename*------------------+ +-*spacename------------------+ +-*spacename*-----------------+ '-*spacestring1*spacestring2*-' >--+---------------------------------------+-------------------> | .-,---------------------. | | V | | '-PART--(----+-integer-----------+-+--)-' '-integer1:integer2-' >--MODE--(--+-OPEN----+--)------------------------------------>< +-NGBPDEP-+ '-STATS---' New option description: MODE( mode-value ) STATS: Externalizes the in-memory real-time statistics to the appropriate catalog tables. In data sharing environments, the in-memory statistics are externalized for all members. This mode does not physically open the page sets or change the states of the page sets. Information about this new command option will be included in the Information Management Software for z/OS Solutions Information Center (http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp) at a later date. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNILSTS PM71744 DSNTDDIS PM71744 DSNTDSTP PM71744 1 DSN9SCNA PM71744 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71744 DSNILSTS DSNTDDIS DSNTDSTP DSN9SCNA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILSTS DSNTDDIS DSNTDSTP DSN9SCNA LISTEND UK92609 COVER LETTER END UK92615 COVER LETTER START PROBLEM DESCRIPTION(S): PM79254 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL * * statement containing OUTER JOIN, multiple * * common table expressions (CTE) and SET * * operations. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC90101 at location * * DSNGD001.DSNGDVRT:500B or ABEND04E * * RC90901 at location DSNIDM.DSNIBNRF * * :5007 may occur when an SQL statement * * satisfies all of the following * * conditions: * * * * 1. a common table expression (CTE#1) * * contains OUTER JOIN; * * 2. another common table expression * * (CTE#2) references CTE#1; * * 3. both of the CTE#1 and CTE#2 are * * referenced in full-select. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC90101 at location DSNGD001.DSNGDVRT:500B or ABEND04E RC90101 at location DSNIDM.DSNIBNRF:5007 may occur when an SQL statement satisfies all of the following conditions: 1. a common table expression (CTE#1) contains OUTER JOIN; 2. another common table expression (CTE#2) references CTE#1; 3. both of the CTE#1 and CTE#2 are referenced in full-select. An example helps to illustrate this problem: DDL: CREATE TABLE TEST.T1 (C1 CHAR(2) NOT NULL, C2 CHAR(5) NOT NULL); 1 CREATE TABLE TEST.T2 (C1 CHAR(2) NOT NULL, C2 CHAR(5) NOT NULL); INSERT INTO TEST.T1 VALUES('1A', '11ABC'); INSERT INTO TEST.T2 VALUES('1A', '22EDF'); SQL: WITH CTE1 (COL11, COL12) AS (SELECT B.C1, B.C2 FROM TEST.T1 AS A LEFT OUTER JOIN TEST.T2 AS B ON A.C1 = B.C1), CTE2 (COL21, COL22) AS (SELECT A.COL11, A.COL12 FROM CTE1 AS A UNION ALL SELECT B.C1, B.C2 FROM TEST.T1 AS B) SELECT A.COL12, B.COL22 FROM CTE1 AS A LEFT OUTER JOIN CTE2 AS B ON A.COL11 = B.COL21; DB2 didn't handle the nullability in above SQL statement and cause ABEND04E RC90101 at location DSNIDM.DSNIBNRF:5007. Code in DB2 has been modified correctly to process an SQL statement containing OUTER JOIN, multiple common table expressions (CTE) and SETOP. Additional keywords: SQLCTE, SQLUNIONALL, SQLLEFTJOIN SQLLEFT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79254 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM79254: See PM79254 APAR/PTF text for additional information about why a REBIND is necessary. PM79254 corrects a problem of ABEND04E RC90101 at location DSNGD001.DSNGDVRT:500B or ABEND04E RC90101 at location DSNIDM.DSNIBNRF:5007, when an SQL statement satisfies all of the following conditions: 1. a common table expression (CTE#1) contains OUTER JOIN; 2. another common table expression (CTE#2) references CTE#1; 3. both of the CTE#1 and CTE#2 are referenced in full-select. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCNR PM79254 DSNXOP0 PM79254 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79254 DSNXOCNR DSNXOP0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCNR DSNXOP0 LISTEND UK92615 COVER LETTER END UK92625 COVER LETTER START PROBLEM DESCRIPTION(S): PM82595 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of parallelism * * who have queries on a table with an index * * defined with INCLUDE columns. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2000F in DSNXOAF +0858 * * on a query in parallelism when the * * partitioning index is defined with * * INCLUDE columns * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E2000F in DSNXOAF +0858 can occur on a query in parallelism when the partitioning index is defined with INCLUDE columns. A storage overlay may happen where PCAC blocks can go beyond the allocated space. This will result in the abend when DB2 attempts to free storage. Additional Keywords: SQLSTORAGE DB2OVRLAY/K SMCOVERLAY SQLINCLUDE DB2PARALL/K OFFSET0858 Code is changed so that the correct amount of storage will be allocated for PCAC blocks. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82595 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75044: See PM75044 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM75044 corrects the conditions that can lead to the occurrence of an ABEND04E RC00E72018 at DSNXSZK OFFSET 2DBE when executing a query with group by, running with parallelism. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: See PM69950 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM69950 corrects the conditions that can lead to the occurrence of an ABEND04E RC00C90101 at location DSNOTCSO:5020 when executing a query that contains a select that references a HAVING clause with a LOB, but without a group by and set function, running with parallelism. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOLCM PM82595 DSNXOLM1 PM82595 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82595 DSNXOLCM DSNXOLM1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLCM DSNXOLM1 LISTEND UK92625 COVER LETTER END UK92700 COVER LETTER START PROBLEM DESCRIPTION(S): PM81799 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who use COPY or * * RECOVER online utility with FLASHCOPY * **************************************************************** * PROBLEM DESCRIPTION: Multiple symptoms may occur while * * running COPY online utility with * * SHRLEVEL CHANGE and FLASHCOPY YES or * * FLASHCOPY CONSISTENT options: * * - ABEND04E RS00C90101 * * - DSNKUNR2 ERQUAL5007 * * - DSNIREDO ERQUAL5005 * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** While running COPY online utility with SHRLEVEL CHANGE and FLASHCOPY YES or FLASHCOPY CONSISTENT - ABEND04E RS00C90101 DSNKUNR2 ERQUAL5007 occurred because index compensation log records were being written and later processed during the "log apply" phase, which found inconsistencies. Compensation log records should not be written while running COPY FLASHCOPY. - ABEND04E RS00C90101 DSNIREDO ERQUAL5005 occurred because an error was detected during the "log apply" phase. The error was not correctly handled. Similar abends may occur using RECOVER online utility when FLASHCOPY image copies are used. DB2 has been modified to ensure compensation log records are not written while COPY FLASHCOPY is running. Additionally, ensure error conditions are handled correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81799 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKDLE PM81799 DSNKINSL PM81799 DSNKUNR2 PM81799 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81799 DSNKDLE DSNKINSL DSNKUNR2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKDLE DSNKINSL DSNKUNR2 LISTEND UK92700 COVER LETTER END UK92704 COVER LETTER START PROBLEM DESCRIPTION(S): PM67669 - **************************************************************** * USERS AFFECTED: Internal serviceability: diagnostic logging * **************************************************************** * PROBLEM DESCRIPTION: Internal serviceability: diagnostic * * logging * **************************************************************** * RECOMMENDATION: * **************************************************************** Internal serviceability: diagnostic logging Internal serviceability: diagnostic logging 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67669 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5COM PM67669 DSNKFRMT PM67669 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67669 DSNB5COM DSNKFRMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB5COM DSNKFRMT LISTEND UK92704 COVER LETTER END UK92720 COVER LETTER START PROBLEM DESCRIPTION(S): PM80040 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of COPY utility. * **************************************************************** * PROBLEM DESCRIPTION: COPY utility does not detect broken * * data pages in a table space or abends * * with REASON=X'00E40100' and * * CAUSE=X'00C20042' * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** COPY utility was run on a table space with a broken page but did not detect nor report it and the job completed with rc0. When DSN1COPY with CHECK option was run against the same table space, it reported the broken page with the following message: DSN1990I DSN1CPGD BROKEN PAGE. PAGE NUMBER = 00000002. REASON: PAGE END FLAGS INCNSISTENT SERVICE INFO: CODE= 'C2A'X PGCOMB='00'X PGTAIL='00'X This page had PGCOMB = '00'X and PGEND = 'N', indicating it was broken. COPY utility did not identify it because it does not always check the page end flags of data pages in table spaces. With such broken data pages in table spaces, COPY could also abend with REASON=X'00E40100' and CAUSE=X'00C20042'. Abend was likely to happen when the pages were not already in bufferpool before the COPY job started. Additional Keywords: ABEND04E RC00E40100 RC00C20042 1 COPY utility has been modified to always check page end flags of data pages and not abend with broken pages. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80040 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBAID PM80040 DSNUBASA PM80040 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80040 DSNUBAID DSNUBASA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBAID DSNUBASA LISTEND UK92720 COVER LETTER END UK92783 COVER LETTER START PROBLEM DESCRIPTION(S): PM85053 - **************************************************************** * USERS AFFECTED: All DB2 V11 users of IRLM 2.3(HIR2230) * * data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: IRLM enhancement for DB2 V11 to * * suppress unnecessary child lock * * propagation to the CF lock structure. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM propagates U state child locks for S state parent pageset P-Locks. Propagation of U state child locks would not be necessary in cases where only a single member is doing updates to a table in a data sharing environment. Having a large number of U child locks being sent to CF costs performance and can be avoided until it is needed. This APAR provides enhancements for DB2 V11. For DB2 V11, IRLM will propagate shared S state parent pageset P-lock to the CF as XES exclusive request and will suppress any update U state child lock propagations until there is global contention on the parent pageset P-lock. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM85053 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DXRRL120 PM85053 DXRRL760 PM85053 DXRRL770 PM85053 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85053 DXRRL120 DXRRL760 DXRRL770 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL120 DXRRL760 DXRRL770 LISTEND UK92783 COVER LETTER END UK92835 COVER LETTER START PROBLEM DESCRIPTION(S): PM77755 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of HASH and CLONE * * tables * **************************************************************** * PROBLEM DESCRIPTION: User receives ABEND04E when hash data * * organization mismatches between a clone * * table and its base table * **************************************************************** * RECOMMENDATION: * **************************************************************** Users may receive ABEND04E RC00C90101 at location DSNIDM.DSNISHPI:5005 upon INSERT, LOAD, or other DML when a base table and its clone have different hash space values. Consider the following scenario: (1) CREATE TABLE TB1 IN DB1.TS1 (2) ALTER TABLE TB1 ADD HASH - TS1 is marked as hash organized but not yet materialized. (3) ALTER TABLE TB1 ADD CLONE TB1_CLONE - Clone added with the same definition as base table, table space TS1 definition stays the same. (4) REORG TABLESPACE TS1 - REORG materializes hash organization for the base and updates SYSTABLEPART and SYSTABLESPACE. - However, REORG is not run on the clone and hash has not been materialized for the clone, leaving an inconsistent catalog. Other unexpected results may occur, including ABEND0C9 RC00000009 at location DSNIDM.DSNIACCH OFFSET7D4E and ABEND04E RC00C90101 at location DSNIDM.DSNIACCH OFFSET534C. DB2 has been fixed to block a clone from being added to a table defined with hash. Users will now see SQLCODE148 Reason 17 on ALTER TABLE ADD CLONE when the base table is defined with hash organization. 1 This APAR does not fix existing hash tables that already have mismatches with their clones. Clones must be dropped if a base table is altered to hash. Users may try the following sample query to identify clones to be dropped: SELECT A.CREATOR, A.NAME FROM SYSIBM.SYSTABLES A WHERE EXISTS ( SELECT B.TBCREATOR, B.TBNAME FROM SYSIBM.SYSTABLES B, SYSIBM.SYSTABLESPACE C WHERE B.TBCREATOR = A.CREATOR AND B.TBNAME = A.NAME AND A.TYPE = 'C' AND C.DBNAME = B.DBNAME AND C.NAME = B.TSNAME AND C.ORGANIZATIONTYPE = 'H') Additional Keywords: SQLINSERT SQLUPDATE SQLDELETE SQLALTER ++HOLD COMMENT FOR RELEASE A10, TYPE DOC: PM77755 introduces the following changes to externals: Changed option for SQL statement ALTER TABLE ADD CLONE: When ADD CLONE is used to create a clone of the specified base table, the base table must conform to the following rules: ... - Not be hash-organized, whether or not the hash organization is materialized. New reason added for SQLCODE -148: 17 - The ALTER statement cannot be used to define a clone table because table is hash-organized. Information about this new reason code and changed option 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. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77755 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM77755 introduces the following changes to externals: Changed option for SQL statement ALTER TABLE ADD CLONE: When ADD CLONE is used to create a clone of the specified base table, the base table must conform to the following rules: 1 ... - Not be hash-organized, whether or not the hash organization is materialized. New reason added for SQLCODE -148: 17 - The ALTER statement cannot be used to define a clone table because table is hash-organized. Information about this new reason code and changed option 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXICLN PM77755 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77755 DSNXICLN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICLN LISTEND UK92835 COVER LETTER END UK92841 COVER LETTER START PROBLEM DESCRIPTION(S): PM81767 - **************************************************************** * USERS AFFECTED: All DB2 10 and DB2 9 for z/OS users of * * utilities. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90110 DSNICLDR ERQUAL5002 * * during utility run (in the reported * * case, UTILINIT phase of LOAD) when the * * utility was in error path preparing to * * issue a resource unavailable message. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running a utility (LOAD in the reported case), the utility during its initialization phase checked DBET to see if a pageset can be accessed and claimed. The pageset could not be accessed and so in error path processing (while preparing to issue a resource unavailable message) the claim code made an incorrect check for the DBD type, which led to passing of an incorrect DBD pointer to an OBD-locate macro. DB2 code has been modified to make sure that claim code passes a correct DBD pointer in error path processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81767 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICLDR PM81767 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81767 DSNICLDR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICLDR LISTEND UK92841 COVER LETTER END UK92878 COVER LETTER START PROBLEM DESCRIPTION(S): PM81749 - **************************************************************** * USERS AFFECTED: All DB2 users in data sharing with * * partitioned objects. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C202AA in DSNB1SWD * * ABEND04E RC00C202B2 in DSNB1PPP * **************************************************************** * RECOMMENDATION: * **************************************************************** When inquiring about the retained information of a page set P-lock on a partitioned object, the wrong result may be returned if the specified part number is greater than 255. DB2 has been fixed to expand the part number field in the retained page set P-lock query interface so that a partition number that is larger than 255 is handled correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81749 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CKP PM81749 DSNB1DA2 PM81749 DSNB1DRA PM81749 DSNB1LDA PM81749 DSNB1LDN PM81749 DSNB1PM2 PM81749 DSNB1QLK PM81749 DSNB1RRL PM81749 DSNB1RRS PM81749 DSNB5SPC PM81749 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81749 DSNB1CKP DSNB1DA2 DSNB1DRA DSNB1LDA DSNB1LDN DSNB1PM2 1 DSNB1QLK DSNB1RRL DSNB1RRS DSNB5SPC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CKP DSNB1DA2 DSNB1DRA DSNB1LDA DSNB1LDN DSNB1PM2 DSNB1QLK DSNB1RRL DSNB1RRS DSNB5SPC LISTEND UK92878 COVER LETTER END UK92880 COVER LETTER START PROBLEM DESCRIPTION(S): PM84475 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the BITNOT * * built-in function. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * an SQL statement that contains the * * BITNOT built-in function. * **************************************************************** * RECOMMENDATION: * **************************************************************** The BITNOT built-in function with an argument larger than decimal number 2147483647, which is 7FFFFFFF in hex, returns incorrect result. The following example illustrates a simple failing case. SELECT BITNOT(4294967295) FROM SYSIBM.SYSDUMMY1; 0 is incorrectly returned from this SELECT statement instead of the expected -4294967296. This problem occurs because DB2 doesn't use correct registers to handle the argument. The code in DB2 is modified to use correct registers to handle the argument for the BITNOT built-in function. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLNULLIF COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84475 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNXRLNG PM84475 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84475 DSNXRLNG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRLNG LISTEND UK92880 COVER LETTER END UK92916 COVER LETTER START PROBLEM DESCRIPTION(S): PM77208 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users with parallelism enabled. * **************************************************************** * PROBLEM DESCRIPTION: Numerous ABEND symptoms including * * a DB2 crash may occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** Numerous ABENDs and a DB2 crash may occur. When we run a query with large record size, DB2 parallelism may not be able to handle it correctly. Since some internal inconsistency has been observed about how to handle large size records. The problem is not query specific, only happens when combined record size passing by parallel pipe is larger than 32K. DB2 has been fixed to handle large size record case correctly under parallelism processing. After the fix, ABENDs no longer occur. Additional keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77208 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM77208: See PM77208 APAR/PTF text for additional information about why a REBIND is necessary. PM77208 corrects an ABEND problem that occurs when DB2 handles a query with parallel processing and the combined record length going through parallel pipe is larger than 32K. To make this fix effective for a static application, it must be 1 rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCON PM77208 DSNXOPTT PM77208 DSNXPCRT PM77208 DSNXPRE2 PM77208 DSNXPSEN PM77208 DSNXPSPD PM77208 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77208 DSNXOCON DSNXOPTT DSNXPCRT DSNXPRE2 DSNXPSEN DSNXPSPD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCON DSNXOPTT DSNXPCRT DSNXPRE2 DSNXPSEN DSNXPSPD LISTEND UK92916 COVER LETTER END UK92956 COVER LETTER START PROBLEM DESCRIPTION(S): PM81077 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (NFM only) users of * * workfiles built when the row length in the * * result of a JOIN (or the row length of a * * large sort record) exceeds 32706 bytes (in * * DB2 9 these kinds of queries would have * * received SQLCODE -670 THE RECORD LENGTH OF * * THE TABLE EXCEEDS THE PAGE SIZE LIMIT, while * * in DB2 10 NFM they are supported) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C200B0 DSNB1GNV+0C68 or * * ABEND04E RC00C90101 DSNIWNRF ERQUAL5009 * * during execution of a workfile-using * * query where the row length in the * * result of a JOIN (or the row length * * of a large sort record) exceeds 32706 * * bytes * **************************************************************** * RECOMMENDATION: * **************************************************************** While fetching from a workfile that included spanned records (record size exceeding 32706 bytes), an internal no-more-rows- found condition was returned by data manager, business as usual. 1 Subsequently, runtime positioned on a new row in said workfile, and was now trying to fetch from it again, however, residual spanned record-related fields (in the internal CUB structure) that represented the position before the repositioning, made the code assume that a page of interest is still in the buffer, which in the reported case triggered buffer manager's structure consistency checks and led to the DSNB1GNV abend. Code has been changed to reset spanned record positioning fields in the CUB when the internal no-more-rows-found condition is returned from data manager. Additional keywords: SQLUNION SQLUNIONALL SQLJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81077 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWNRF PM81077 DSNWDFDM PM81077 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81077 DSNIWNRF DSNWDFDM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWNRF DSNWDFDM LISTEND UK92956 COVER LETTER END UK92961 COVER LETTER START PROBLEM DESCRIPTION(S): PM82961 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of the NULLIF built-in function. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * an SQL statement that contains the * * NULLIF built-in function. * **************************************************************** * RECOMMENDATION: * **************************************************************** The NULLIF built-in function with a VARBINARY argument incorrectly returns the empty string if the two arguments are not equal. The following example illustrates a simple failing case. CREATE TABLE T1 (VB4 VARBINARY(4)); 1 INSERT INTO T1 VALUES(BX'F2F5F9F9'); SELECT NULLIF(VB4,BX'F1F5F9F9') AS NULLIFV FROM T1; The empty string '' is incorrectly returned from this SELECT statement instead of the expected NULL value. This problem occurs because DB2 doesn't handle the length for the argument correctly. The code in DB2 is modified to handle the length of the argument properly for the NULLIF built-in function. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLNULLIF COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82961 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRNUL PM82961 DSNXRNU9 PM82961 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82961 DSNXRNUL DSNXRNU9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRNUL DSNXRNU9 LISTEND UK92961 COVER LETTER END UK92963 COVER LETTER START PROBLEM DESCRIPTION(S): PM82035 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of Partition by * * Growth (PBG) Universal Table Spaces * **************************************************************** * PROBLEM DESCRIPTION: GRECP recovery of a user PBG object * * times out trying to get a claim on * * DSNDB01.DSNDB01X, resulting in slow * * GRECP recovery of the user object * * * * MSGDSNT376I MSGDSNT501I RC00C900BA * * TYPE00002003 * **************************************************************** * RECOMMENDATION: * **************************************************************** Object DSNDB01.DSNDB01X went into a group buffer pool recovery pending state (GRECP) - MSGDSNB323I. The GRECP recovery process acquired a drain on DSNDB01.DSNDB01X as expected and was 1 applying log records. During a GRECP recovery of a user PBG object, the GRECP recovery processing was trying to acquire a claim on DSNDB01.DSNDB01X, specifically as part of internal DBET processing for this user PBG object, which involves DBD lookup. However, the claim attempt was timing out (00C900BA) due to the aforementioned drainer. Then another GRECP recovery of a different PBG object tried to acquire a claim on DSNDB01.DSNDB01X as well, but was also timing out for the same reason (the drainer was still active). However, during GRECP recovery of a user PBG object, there should be no need to access DSNDB01.DSNDB01X as part of internal DBET processing. DB2 has been modified to limit access to DBD during GRECP or LPL recovery of a user object, so as to avoid acquiring a claim on DSNDB01.DSNDB01X. Additional keywords: SQLPBG COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82035 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBGA PM82035 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82035 DSNIDBGA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBGA LISTEND UK92963 COVER LETTER END UK92971 COVER LETTER START PROBLEM DESCRIPTION(S): PM83179 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of COPY utility * * on compressed objects with reset RBA * * enabled on a non-data sharing system. * **************************************************************** * PROBLEM DESCRIPTION: COPY FULL YES with DSNZPARM, SPRMRRBA, * * enabled did not reset the dictionary * * version for the dictionary pages in * * the DB2 data. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * 1 **************************************************************** COPY FULL YES with DSNZPARM, SPRMRRBA, enabled did not reset the dictionary version for the dictionary pages in the DB2 data on a non data sharing system. SPRMRRBA should only be enabled to reset the RBA as a process to handle DB2 subsystems that are approaching the end of the log RBA range as described in DB2 Administration Guide, in the section titled "Resetting the log RBA value in a non-data sharing environment". When SPRMRRBA is enabled, the COPY utility with the FULL YES option should reset the dictionary version number in the DB2 dictionary pages. Additional symptoms: ASN0011E 00C90064 during IFI log reads after SPRMRRBA is enabled Additional keywords: MSGASN0011E RC00C90064 COPY FULL YES with DSNZPARM, SPRMRRBA, enabled has been modified to reset the dictionary version number for DB2 dictionary pages on non data sharing systems. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83179 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBASA PM83179 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83179 DSNUBASA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBASA LISTEND UK92971 COVER LETTER END UK92981 COVER LETTER START PROBLEM DESCRIPTION(S): PM83144 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries * * utilizing multi-index access. * **************************************************************** * PROBLEM DESCRIPTION: DB2 10 for z/OS may incorrectly discard * * a viable multi-index access path. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 for z/OS may incorrectly discard a viable multi-index access path. This problem occurs because DB2 incorrectly references undefined storage. As a result, the problem may be intermittent as the decision to discard the multi-index 1 access path depends on the contents of the random storage accessed. Additional keywords: SQLACCESSPATH SQLPERFORMANCE SQLMIX MIX DB2 has been corrected to avoid accessing random storage. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83144 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM83144: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83144 corrects a problem in which DB2 could incorrectly discard an multi-index access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM81295: See PM81295 APAR/PTF text for additional information about why a REBIND is necessary. PM81295 corrects a problem of poor query performance for a query containing OR predicates that map to a single index. The poor performance can occur when a range-list index access plan may not be assigned the lowest cost of any plan it beats. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCSC PM83144 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83144 DSNXOCSC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCSC LISTEND UK92981 COVER LETTER END UK92982 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM84864 - **************************************************************** * USERS AFFECTED: All data sharing users of the IFI READS for * * IFCID 306 facility to read log data from * * DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: A small timing window can result in * * log records being returned to the * * IFI READS for IFCID 306 application * * with an LRSN value that is beyond the * * end-of-scope LRSN for the requested * * F-call, N-call sequence. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNJR001 can incorrectly update the end-LRSN value in the log read cursor for the host member with a value that is higher than the requested LRSN range. This can occur if the log writer is updating the high written LRSN value in the LMB block in a very small window when DSNJR001 is validating the requested LRSN range. This can cause IFI to return some log records with an LRSN value that is higher than the end-of-scope LRSN value (QW0306ES). When running QREP Capture, this can result in MSGASN0633W and possible missing log data. The incorrect code in DSNJR001 has been corrected to close this timing window. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84864 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJR001 PM84864 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84864 DSNJR001 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJR001 LISTEND UK92982 COVER LETTER END UK93127 COVER LETTER START PROBLEM DESCRIPTION(S): PM80371 - **************************************************************** * USERS AFFECTED: All DB2 users of trace IFCID400 or IFCID401. * **************************************************************** * PROBLEM DESCRIPTION: When trace IFCID400 or IFCID401 is * 1 * active, customer could receive ABEND04E * * RC00E2000C at DSNXEDS1 DSNSVSVB +0AC2, * * because the statement cache blocks 2G * * pool runs out of storage. * **************************************************************** * RECOMMENDATION: * **************************************************************** When trace IFCID400 or IFCID401 is active, DB2 could fail to release the storage for the internal data structure. This apar provides serviceability to diagnose storage leak problems when IFCID400 or IFCID401 is active. Additional Keywords: DB2STGLK/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80371 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEFSP PM80371 DSNGEGBK PM80371 DSNGEPER PM80371 DSNGEPLC PM80371 DSNGEPSH PM80371 DSNXECLF PM80371 DSNXECW PM80371 DSNXECWA PM80371 DSNXELX PM80371 DSNXERDS PM80371 DSNXEUFP PM80371 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80371 DSNGEFSP DSNGEGBK DSNGEPER DSNGEPLC DSNGEPSH DSNXECLF DSNXECW DSNXECWA DSNXELX DSNXERDS DSNXEUFP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFSP DSNGEGBK DSNGEPER DSNGEPLC DSNGEPSH DSNXECLF DSNXECW DSNXECWA DSNXELX DSNXERDS DSNXEUFP LISTEND UK93127 COVER LETTER END UK93128 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM81317 - **************************************************************** * USERS AFFECTED: All DB2 V10 package users. * **************************************************************** * PROBLEM DESCRIPTION: After the execution of a package was * * cancelled, customer might receive * * ABEND0C4 with RC00000038 * * at DSNGEFSP+BB6 during * * package deallocation. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 has a bug which could results in accessing an invalid internal control block during the cleanup of the package execution. It is a very rare case to have this bug triggered. DB2 code has been changed to avoid accessing the invalid control block. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81317 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEFSP PM81317 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81317 DSNGEFSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFSP LISTEND UK93128 COVER LETTER END UK93160 COVER LETTER START PROBLEM DESCRIPTION(S): PM83587 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: The following conditions are reported: * * o When DB2 (DDF) is operating in a * * TCP/IP Single Mode stack environment * * and (DSN6SYSP) MAXDBAT is online * * changed to zero, connection attempts * * to remote severs may fail with one * * or more of the following messages: * * . Message DSNL511I DSNLIENO * * IPADDR=::FFFF:nnn.nnn.nnn.nnn * * SOCKET=SOCKET RETURN CODE=1114 * * REASON CODE=112B0000 * 1 * . Message DSNL511I DSNLIENO * * IPADDR=::FFFF:nnn.nnn.nnn.nnn * * SOCKET=CLOSE RETURN CODE=113 * * REASON CODE=0523011C * * . Message DSNL512I DSNLIAAC * * MAXFILEPROC RETURN CODE=1114 * * REASON CODE=00D31206 * * Users may also observe an abend * * 0C4-00000038 DSNLTRAG+1568. * * o The DSNL512I DSNLIAAC * * MAXFILEPROC message may contain * * residual data in positions 14 * * and 15 ("MAXFILEPROC xx"). * * Example: * * DSNL512I -DBC DSNLIAAC TCP/IP * * MAXFILEPROC GE FAILED WITH ... * * ** * **************************************************************** * RECOMMENDATION: * **************************************************************** The following conditions are reported: o When the DSNZPARM (DSN6SYSP) MAXDBAT value is set to zero, DB2 (DDF) should prevent inbound network traffic (from remote requester systems) but still allow outbound network traffic (to remote server systems). However, when the MAXDBAT value is changed online to zero after DDF has been started, DB2 (DDF) will incorrectly cripple the ability to create outbound TCP/IP connections if the TCP/IP stack is operating in a single mode (IPv4 only) environment. Symptoms may include: . Message DSNL511I DSNLIENO PADDR=::FFFF:nnn.nnn.nnn.nnn SOCKET=SOCKET RETURN CODE=1114 REASON CODE=112B0000 . Message DSNL511I DSNLIENO IPADDR=::FFFF:nnn.nnn.nnn.nnn SOCKET=CLOSE RETURN CODE=113 REASON CODE=0523011C The condition will continue until MAXDBAT is changed online to be greater than zero, or until DDF is stopped and restarted (even with MAXDBAT=0). As these DSNL511I message conditions continue to accumulate, users may also eventually see: . Message DSNL512I DSNLIAAC MAXFILEPROC RETURN CODE=1114 REASON CODE=00D31206. DDF must be stopped and restarted to relieve the condition. Users may also notice an abend 0C4-00000038 DSNLTRAG+1568 if DB2 happens to receive an automatic indoubt thread (resync) request from a remote system after MAXDBAT is online changed to zero. The abend will likely repeat until MAXDBAT is raised back to a positive value or DDF is stopped. o If a DSNL512I DSNLIAAC MAXFILEPROC message occurs, the MAXFILEPROC portion of the message may contain residual data in positions 14 and 15, such as "MAXFILEPROC GE". DSNLILNR has been changed to properly recognize the TCP/IP stack (single-mode, IPv4 only, or dual-mode) environment when the (DSN6SYSP) MAXDBAT value is change online to zero. DSNLTRAG has been changed to tolerate failures, early in its processing, when receiving resync requests from remote 1 partners. DSNLIAAC has been changed to issue the DSNL512I MAXFILEPROC message with a fully blank padded MAXFILEPROC value. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83587 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLIAAC PM83587 DSNLILNR PM83587 DSNLTRAG PM83587 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83587 DSNLIAAC DSNLILNR DSNLTRAG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIAAC DSNLILNR DSNLTRAG LISTEND UK93160 COVER LETTER END UK93177 COVER LETTER START PROBLEM DESCRIPTION(S): PM81671 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where: * * * DB2 is a member of a data sharing group * * and is configured with a MAX REMOTE * * CONNECTED (DSN6SYSP CONDBAT) value of 0, * * and/or * * * DB2 is utilized as a server, via a * * TCP/IP connection, on behalf of a * * remote DB2 for z/OS requester. * * * DB2 is a member of a data sharing group * * and is accessed by remote client * * environments which utilize the * * KeepDynamic Refresh capability * * (introduced by DB2 9 APAR PK69339). * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: After PTF UK90325 (APAR PM43293) is * * applied, the following conditions may * * be observed: * * * Abend 0C9-00000009 DSNLEDDA+345A. * * * A DRDA AGNPRMRM reply is returned * * to remote DB2 for z/OS requester * * systems. * * DB2 for z/OS requester system * 1 * symptoms may include: * * . Message DSNL031I displayed * * instead of DSNL511I. * * . An application may receive SQLCODE * * -30020 instead of SQLCODE -30081. * * . Message DSNL413I, which may result * * in message DSNV460I (V460) being * * issued in the -DISPLAY THREAD(*) * * TYPE(INDOUBT) command report. * * * Distributed client applications * * may receive SQLCODE -1224 errors. * **************************************************************** * RECOMMENDATION: * **************************************************************** As part of the new support introduced by PTF UK90325 (APAR PM43293), the following problems may be observed: * If DDF has been started when the subsystem is a member of a data sharing group, DDF will periodically notify z/OS Work Load Manager (WLM) of a change in the subsystem's health value as the number of remote client connections approaches the value specified for the MAX REMOTE CONNECTED (DSN6SYS CONDBAT) subsystem parameter. DDF can be started with a set of subsystem parameters or a different set of subsystem parameters can be loaded (online changed) where the value of CONDBAT is 0. When CONDBAT is 0, remote clients cannot connect to this DB2 subsystem because the DDF server capability is disabled. However, the new (APAR PM43293) DB2 system health notification capability did not consider the condition where CONDBAT is 0 which results in a divide by 0 exception (abend 0C9-00000009). * DB2 for z/OS requesters do not expect a DRDA AGNPRMRM (Agent Permanent Error reply message) to be returned from a DB2 for z/OS server when the server agent abnormally terminates. Thus, once PTF UK90324 is applied to a DB2 for z/OS server, a server agent abend condition will be reported as a DRDA AGNPRMRM (Agent Permanent Error) reply message rather than a connection failure. When a DB2 for z/OS requester sees this condition, it will issue message DSNL031I (REASON=00D351FF, ERROR ID=DSNLZRPA0001) instead of message DSNL511I, and return SQLCODE -30020 instead of SQLCODE -30081 to an application. Additionally, if the server agent abend is detected during commit processing, the DB2 for z/OS requester may also issue message DSNL413I in conjunction with message DSNL031I. This will result in the -DISPLAY THREAD INDOUBT command reporting a thread requiring manual intervention (RESET=YES and message DSNV460I) to resolve. * Distributed applications using the IBM Data Server Driver or Client product family that have been configured to utilize the KeepDynamic Refresh capability (introduced by DB2 9 APAR PK69339) do not expect a DRDA AGNPRMRM to be returned from a DB2 for z/OS server when the server has determined that the thread/connection should be refreshed. As such, the client application may now receive a SQLCODE -1224. DB2 has been changed as follows: 1 * DB2 will now ensure that the MAX REMOTE CONNECTED (DSN6SYSP CONDBAT) subsystem parameter is not 0 before determining whether or not WLM must be notified of a change in the subsystem's health. If CONDBAT is 0, no notification of the subsystem's health will be made to WLM because no remote client work can be accepted by the member. This means that the WLMHEALTH value displayed in message DSNL094I, issued as a result of the -DISPLAY DDF DETAIL command, will be 0. The subsystem health value will still be reported by message DSNV507I, which is issued for the ACTIVE MONITOR as a result of the -DISPLAY THREAD(*) TYPE(SYSTEM) command. * DB2 will no longer return an AGNPRMRM to a DB2 for z/OS requester. That is, relative to remote DB2 for z/OS requester systems only, DB2 server AGNPRMRM reply behavior introduced by APAR PM43293 has been restored to prior behavior. Users should be aware that if symptoms are observed on DB2 for z/OS requester systems, the solution is to apply this change to the associated DB2 10 for z/OS server system. * DB2 will no longer return an AGNPRMRM to a distributed client being terminated for KeepDynamic Refresh purposes. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81671 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLAGNT PM81671 DSNLAGNX PM81671 DSNLCTRC PM81671 DSNLDALB PM81671 DSNLEDDA PM81671 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81671 DSNLAGNT DSNLAGNX DSNLCTRC DSNLDALB DSNLEDDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLAGNT DSNLAGNX DSNLCTRC DSNLDALB DSNLEDDA LISTEND UK93177 COVER LETTER END UK93178 COVER LETTER START PROBLEM DESCRIPTION(S): PM84581 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** 1 * PROBLEM DESCRIPTION: The following intermittent abends are * * reported: * * o 04E-00E20006 DSNLZRTM.DSNSVBK +096A * * or various other offsets (V9). * * o 04E-00E2000F DSNLZRTM.DSNSVSFB+0858 * * or various other offsets (V10). * * In either case, DB2 will likely * * abnormally terminate with message * * DSNV086E and reason 00D94001. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 for z/OS allied thread happened to be abnormally terminated, in this case via a U0999-00000000 abend, while CSECT DSNLZRTM was in the process of freeing DDF related storage. As a result of the abend, the allied thread enters abort processing but a residual pointer value causes the storage to be freed again. The erroneous double free of the storage is detected in the form of an abend 04E-00E20006 DSNLZRTM.DSNSVBK (V9) or 04E-00E2000F DSNLZRTM.DSNSVSFB (V10). The abend during abort processing causes the subsystem to be terminated with message DSNV086E and reason code 00D94001. DB2 has been changed to anticipate that its processing may be interrupted and hence clear pointer references to its storage as the storage is being freed. This ensures that a free of the storage cannot be repeated if processing is interrupted. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84581 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXCMT PM84581 DSNLXRCL PM84581 DSNLXRDT PM84581 DSNLXROP PM84581 DSNLXRSQ PM84581 DSNLXRUW PM84581 DSNLZRTM PM84581 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84581 DSNLXCMT DSNLXRCL DSNLXRDT DSNLXROP DSNLXRSQ DSNLXRUW DSNLZRTM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXCMT DSNLXRCL DSNLXRDT DSNLXROP DSNLXRSQ DSNLXRUW DSNLZRTM 1 LISTEND UK93178 COVER LETTER END UK93212 COVER LETTER START PROBLEM DESCRIPTION(S): PM85928 - **************************************************************** * USERS AFFECTED: All users of DB2 for zOS Version 10.1. * **************************************************************** * PROBLEM DESCRIPTION: Possible one word overlay of E/CSA * * subpool 231 key 7 storage during DB2 * * abnormal termination. A word beyond * * the end of a 12 byte LMCT block is * * being set to zero. * **************************************************************** * RECOMMENDATION: * **************************************************************** During DB2 abnormal termination (with MSGDSNV086E ), DSNYESTS may attempt to store a word of zeros beyond the end of an empty, 12 byte LMCT block. This normally will overlay the header of another LMCT block, which does not cause a problem. But it is possible that it could overlay another allocated block of storage in the same key 7 SP231 page. There are currently no 'empty' LMCT blocks in DB2 Version 9.1 so the problem will not occur in Version 9.1. The v9.1 code is being corrected anyway in case things change in the future. DB2OVRLAY/K The control block addressability error in DSNYESTS has been corrected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85928 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNYESTS PM85928 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85928 DSNYESTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNYESTS LISTEND UK93212 COVER LETTER END UK93226 COVER LETTER START PROBLEM DESCRIPTION(S): PM81308 - **************************************************************** 1 * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E50077 occurred when a * * thread running under a DB2 * * authorization service task tried to * * switch to another service task. An * * ABEND04E RC00F30411 then occurred when * * cancelling the originating thread. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E50077 may occur when a thread running under a DB2 authorization service task attempts to execute on another authorization service task. If the first thread is cancelled an ABEND04E RC00F30411 may occur. Module DSN3AUCX and DSN3SSLM have been updated to avoid the ABEND04E RC00E50077 that occurs when switching authorization service tasks. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81308 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3AUCX PM81308 DSN3SSLM PM81308 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81308 DSN3AUCX DSN3SSLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3AUCX DSN3SSLM LISTEND UK93226 COVER LETTER END UK93239 COVER LETTER START PROBLEM DESCRIPTION(S): PM83077 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of ALTER INDEX * * GBPCACHE in a data sharing environment * **************************************************************** * PROBLEM DESCRIPTION: After an index GBPCACHE value is * * altered in a data sharing environment, * * an INSERT can hit ABEND04E RC00C90101 * * in DSNKNXT2. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the customer attempts to insert data into a table, DB2 1 might issue an ABEND04E RC00C90101 in DSNKNXT2 if the INSERT happens to use an index whose GBPCACHE value has been previously altered in a data sharing environment. ALTER INDEX GBPCACHE in a data sharing environment requires the index to be stopped. If not, then any use of this index can hit this ABEND or other problems. DB2 code has been fixed. SQLCODE626 will be issued when an index GBPCACHE value is altered in a data sharing system if the index is not stopped. This fix does not fix the existing broken index with inconsistent GBPCACHE value across different DB2 members. If the customer ran into such ABEND before this APAR is applied, the following steps are suggested: 1. STOP / START the index 2. Run a CHECK INDEX 3. Run a REBUILD INDEX if needed. ADDITIONAL KEYWORDS: SQLINSERT SQLALTER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83077 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDAIP PM83077 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83077 DSNGDAIP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDAIP LISTEND UK93239 COVER LETTER END UK93250 COVER LETTER START PROBLEM DESCRIPTION(S): PM84045 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of packages bound * * on DB2 for z/OS v8 or DB2 9 for z/OS that * * contain queries accessing Table UDFs. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 rc38 can occur at location * 1 * DSNXRINS +05C2 or OFFSET05C2 when * * executing a package that was bound on * * DB2 v8 or DB2 v9 that contains a query * * that accesses a Table UDF (User Defined * * Function). The failure can occur even * * with apar PM54525 applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 rc38 can occur at location DSNXRINS +05C2 when executing a package that was bound on DB2 v8 or DB2 v9 that contains a query that accesses a Table UDF (User Defined Function). The failure can occur even with apar PM54525 applied. The problem occurs during runtime or at execution time when DB2 doesn't take the proper code path for a package that was bound on DB2 v8 or DB2 v9 that contains a query that accesses a Table UDF. Because an improper code path is taken, an incorrect module is accessed which leads to the ABEND0C4 during processing. In the reported case, the failure occurred when executing a package that originated on a DB2 v9 subsystem. The following simple example illustrates how this failure can occur. Given: A DB2 9 subsystem in COEXISTENCE mode with a DB2 10 subsystem. Step 1. Create a Table T1 on the DB2 v9 subsystem as follows. CREATE TABLE T1 (ID INT, ID2 INT); INSERT INTO T1 VALUES(1, 11); INSERT INTO T1 VALUES(1, 12); INSERT INTO T1 VALUES(1, 13); INSERT INTO T1 VALUES(1, 14); INSERT INTO T1 VALUES(2, 21); INSERT INTO T1 VALUES(2, 22); INSERT INTO T1 VALUES(2, 23); INSERT INTO T1 VALUES(2, 24); Step 2. Create an external Table UDF whose body contains a dynamic prepare for an SQL statement which performs a fetch into some host variables. Create this UDF on the DB2 v9 subsystem. CREATE FUNCTION SCE92101.UFE921X4(P1 INT) RETURNS TABLE(C1 INT, C2 INT) PARAMETER CCSID EBCDIC PARAMETER STYLE DB2SQL SPECIFIC UDFE9X4 LANGUAGE C 1 FENCED WLM ENVIRONMENT WLMENV3 COLLID PKE921X4 EXTERNAL NAME PKE921X4 PROGRAM TYPE MAIN; ... SELECT ID, ID2 FROM T1 WHERE ID = ?; Step 3. Prepare and bind an application which invokes this Table UDF as follows on the DB2 v9 subsystem. EXEC SQL DECLARE CS1 CURSOR FOR SELECT * FROM TABLE (SCE92101.UFE921X4(1)) AS TB; Step 4. Execute the bound package on the DB2 v10 subsystem. The above abend can occur when DB2 enters the wrong module after incorrectly checking the Table UDF package level. Additionally, please note that it was reported that an incorrect result can be returned instead of an abend. The code in DB2 runtime is modified to take the proper code path for a DB2 v8 or DB2 v9 bound package that contains queries that can access a Table UDF. Additional Keywords: SQLUDF SQLTUDF SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84045 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRGPL PM84045 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84045 DSNXRGPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRGPL LISTEND UK93250 COVER LETTER END UK93300 COVER LETTER START PROBLEM DESCRIPTION(S): PM81692 - **************************************************************** 1 * USERS AFFECTED: All users of DB2 10 for z/OS who use * * partitioned tables partitioned by TIMESTAMP * **************************************************************** * PROBLEM DESCRIPTION: Mismatched TIMESTAMP precision causes * * range and BETWEEN predicates to not use * * page range screening. * **************************************************************** * RECOMMENDATION: * **************************************************************** This fix improves the evaluation of range and BETWEEN predicates with mismatched TIMESTAMP precision so that page range screening may be applied. The predicates that are affected are: 1, < 2, <= 3, > 4, >= 5, BETWEEN AND DB2 code has been modified to support this. The change adds an online-changeable subsystem parameter in DSN6SPRM called PGRNGSCR that specifies whether to enable page range pruning in order to improve performance of queries that contain one or more of the following predicates: < <= > >= BETWEEN AND Valid settings are: - NO : Do not enable this optimizer change. ==> This is the default setting - YES: Enable the change. Do not use this setting unless advised to do so by IBM service. Special attention for data sharing customers: * Do not specify PGRNGSCR=YES on any member of the group until the fixing PTF for this APAR has been applied to all members. Otherwise, DB2 can experience abend 04E-00E70005 at DSNXRTIM:P017 * If you specify PGRNGSCR=YES on any member, it is recommended that you specify it on all members. Not specifying the same option on all members may result in member flip-flop behavior. Additional keywords: SQLTIMESTAMP SQLACCESSPATH SQLPERFORMANCE PAGERANGE SQLBETWEEN SQLLT SQLGT ABEND04E RC00E70005 DSNXRTIM P017 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81692 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75486: See PM75486 APAR/PTF text for additional information about why a REBIND is necessary. PM75486 corrects a problem that incorrect output could happen for an SQL statement that satisfies all of the following conditions: 1. It contains a table expression or view with a set operator, and the table expression or view is materialized. 2. It contains a LIKE predicate that can be pushed down to the materialized table expression or view. 3. After push down, the LIKE predicate contains an expression, which matches to an index on expression. 4. The expressions in the different set branches return data with different nullability. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM70345: See PM70345 APAR/PTF text for additional information about why a REBIND is necessary. PM70345 corrects a problem that performance regression could happen for a static SQL statement that has a non-boolean term predicate with Timestamp column. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM53364: See PM53364 APAR/PTF text for additional information about why a REBIND is necessary. PM53364 corrects a problem that An incorrout may occur when the query satisfies all of below conditions: 1,A String representation of timestamp value is used as one parameter of a scalar function. 2,Above scalar function is referenced in the user query's predicate. 3,The result of the scalar function is used to compare with 1 another timestamp value. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM47894: See PM47894 APAR/PTF text for additional information about why a REBIND is necessary. PM47894 corrects a problem that an incorrout may occur when user's SQL statement satisfies all of following conditions: 1, The SQL statement contains a BETWEEN predicate which references a CASE expression in its low or high operator. 2, The CASE expression references a scalar fullselect in its searched-when clause. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. ACTION: ***Actions for APAR PM81692 (V10) This PTF adds an online-changeable subsystem parameter in DSN6SPRM called PGRNGSCR that specifies whether to enable page range pruning in order to improve performance of queries that contain one or more of the following predicates: < <= > >= BETWEEN AND Valid settings are: - NO : Do not enable this optimizer change. ==> This is the default setting - YES: Enable the change. Do not use this setting unless advised to do so by IBM service. Special attention for data sharing customers: * Do not specify PGRNGSCR=YES on any member of the group until this PTF has been applied to all members. Otherwise, DB2 can experience abend 04E-00E70005 at DSNXRTIM:P017 * If you specify PGRNGSCR=YES on any member, it is recommended that you specify it on all members. Not specifying the same option on all members may result in member flip-flop behavior. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: 1 (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Rebind any applications using one or more of the aforementioned predicates. Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter PGRNGSCR=, where is NO or YES, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding PGRNGSCR here, the value will be set to the default of NO when you assemble the DSNZPxxx module. Special attention for data sharing customers: - Do not specify PGRNGSCR=YES on any member of the group until this PTF has been applied to all members. Otherwise, DB2 can experience abend 04E-00E70005 at DSNXRTIM:P017 - If you specify PGRNGSCR=YES on any member, it is recommended that you specify it on all members. Not specifying the same option on all members may result in member flip-flop behavior. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ==> This action is required for all customers This PTF adds an entry for PGRNGSCR to the CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP 1 target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following lines: PGRNGSCR CHAR M NO YES Change to the value you specified for PGRNGSCR in step (2), above. ---------------------------------------------------------------- (4) Rebind any applications using one or more of the aforementioned predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. End of actions for APAR PM81692 (V10) ACTION: ***Action for PM79804 (V10) This PTF modifies the DB2 installation CLIST to correct errors in the migration handling of the DSN6SPRM.LRDRTHLD parameter. Actions for current DB2 10 customers: ------------------------------------ This PTF modifies CLIST member DSNTINST only in the prefix.SDSNCLST target library. After applying the PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM81692 DSNDQWPZ PM81692 DSNDSPRM PM81692 DSNTIDXA PM81692 DSNTIDXB PM81692 DSNTIJUZ PM81692 DSNTINST PM81692 DSNTXAZP PM81692 DSNWZIFA PM81692 DSNXGSFN PM81692 DSNXOEXF PM81692 DSNXOMPS PM81692 DSNXOSCD PM81692 DSNXOW2C PM81692 DSNXOW2D PM81692 DSNXRTIM PM81692 DSN6SPRM PM81692 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81692 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSNXGSFN DSNXOEXF DSNXOMPS 1 DSNXOSCD DSNXOW2C DSNXOW2D DSNXRTIM DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP DSNWZIFA DSNXGSFN DSNXOEXF DSNXOMPS DSNXOSCD DSNXOW2C DSNXOW2D DSNXRTIM MACROS DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSN6SPRM LISTEND UK93300 COVER LETTER END UK93302 COVER LETTER START PROBLEM DESCRIPTION(S): PM82655 - **************************************************************** * USERS AFFECTED: All DB2 users who assemble DSNDQWAS * * or DSNDQWST or the macros included by them * **************************************************************** * PROBLEM DESCRIPTION: ASMA043E , ASMA012S , or ASMA017W * * messages on assembly of application * * programs that invoke either macro * * DSNDQWAS or DSNDQWST with the * * DSECT=[YES|NO] parameter. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DSECT=[YES|NO] parameter is used to control whether the structures defined in the macros DSNDQWAS and DSNDQWST are defined as DSECTs or as program storage. This apar corrects several assembly errors related to DSECT=[YES|NO] parameter for several macros. 1. Use of the DSECT parameter caused several assembly warnings ASMA017W (Undefined keyword parameter) to be generated. 2. Use of DSECT=NO caused assembly errors ASMA043E (Previously defined symbol) and ASMA012S (Undefined 1 sequence symbol) and some structures were still defined as DSECTs. 3. The high-level structure which contains the substructure QSST did not have a name. 1.,2. DSECT=[YES|NO] support has been added or corrected and the assembly errors are corrected for DSNDQWAS and DSNDQWST and structures are defined as specified by the parameter value. 3. The high-level structure which includes substructure QSST has been given the name DSNDQSST. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82655 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQBAC PM82655 DSNDQBST PM82655 DSNDQDBP PM82655 DSNDQIST PM82655 DSNDQJST PM82655 DSNDQLES PM82655 DSNDQMDA PM82655 DSNDQPKG PM82655 DSNDQSST PM82655 DSNDQTST PM82655 DSNDQTXA PM82655 DSNDQVAS PM82655 DSNDQXPK PM82655 DSNDQXST PM82655 DSNDQ9ST PM82655 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82655 DSNDQBAC DSNDQBST DSNDQDBP DSNDQIST DSNDQJST DSNDQLES DSNDQMDA DSNDQPKG DSNDQSST DSNDQTST DSNDQTXA DSNDQVAS DSNDQXPK DSNDQXST DSNDQ9ST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNDQBAC DSNDQBST DSNDQDBP DSNDQIST DSNDQJST DSNDQLES DSNDQMDA DSNDQPKG DSNDQSST DSNDQTST DSNDQTXA DSNDQVAS 1 DSNDQXPK DSNDQXST DSNDQ9ST LISTEND UK93302 COVER LETTER END UK93322 COVER LETTER START PROBLEM DESCRIPTION(S): PM72052 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of null * * indicator for in Stored Procedure for * * Distributed Data Facility (DDF) users, DDF * * users using IBM Data Server Driver for JDBC, * * SQLJ Type 4 Connectivity to access a DB2 for * * z/OS data sharing group and the IBM Data * * Server Driver for non-JAVA client with the * * DDF_COMPATIBILITY ZPARM. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect null indicator output -1 can * * be returned when data conversion * * exception occurs. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect null indicator output -1 can be returned in distributed bind out process when data conversion exception occurs. The expected null indicator value is -2 for such conversion exception cases. This incorrect output problem happens because DB2 moves an internal variable incorrectly. DB2 has been changed to handle the null indicator variable correctly. Additional keywords : DB2INCORR/K SQLINCORROUT SQLINCORR INCORROUT SQLCODE304 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72052 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXROE9 PM72052 DSNXROHE PM72052 DSNXROHS PM72052 DSNXROH2 PM72052 DSNXROS9 PM72052 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72052 DSNXROE9 DSNXROHE DSNXROHS DSNXROH2 DSNXROS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXROE9 DSNXROHE DSNXROHS DSNXROH2 DSNXROS9 LISTEND UK93322 COVER LETTER END UK93373 COVER LETTER START PROBLEM DESCRIPTION(S): PM81922 - **************************************************************** * USERS AFFECTED: DB2 users of segmented or linear table * * space. * **************************************************************** * PROBLEM DESCRIPTION: When create index on table T1 and * * insert into a table T2 where T1 and T2 * * are on the same table space, deadlock * * could occur. * * * * SNT501I -SGA1 DSNILMCL RESOURCE * * UNAVAILABLE 364 * * CORRELATION-ID=D30DIA004 * * CONNECTION-ID=SERVER * * LUW-ID=GA11C873.PAAF.130107114525= * * 115840 * * REASON 00C90088 * * TYPE 00000D01 * * NAME 00010273.00014302 * **************************************************************** * RECOMMENDATION: * **************************************************************** When a thread A is creating an index, DB2 holds IX lock (commit duration) on the table and waits for x lock (commit duration) on the database. At the same time a thread B is inserting into a table, DB2 needs hold x lock (commit duration) on the database and wait for S lock (commit duration) on all the tables on the table space. Thread A and B deadlock with each other. When insert into a table, DB2 does not need to hold S lock on all tables in the table space, which avoids the above deadlock. Additional Keywords: RC00C90088 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81922 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDCOB PM81922 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81922 DSNGDCOB 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDCOB LISTEND UK93373 COVER LETTER END UK93392 COVER LETTER START PROBLEM DESCRIPTION(S): PM83457 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users joining 3 or more * * tables in a query block. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may select an inefficient join * * sequence for a query if the query has * * a query block with a join of 3 or * * more tables. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may select an inefficient join sequence for a query if the query has a query block with a join of 3 or more tables. In particular, when there are multiple tables joined, the tables joined via indexes may be joined at a later position in the inefficient access path while joining them earlier may provide better performance. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE Code has been modified to correct the problem described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83457 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM83457: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83457 corrects a problem that the DB2 optimizer may select an inefficient join sequence for a query if the query has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM73214: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM73214 corrects a problem of inaccurate cost estimation for a query when the query contains a view or table expression with UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM72676: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM72676 corrects a problem of inaccurate cost estimation for a query when the query contains nested non-correlated subqueries. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM58932: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM58932 corrects a problem that DB2 may choose an inefficient join sequence for a query joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM34814: See PM34814 APAR/PTF text for additional information about why a REBIND is necessary. PM34814 corrects a problem that DB2 may select an inefficient join sequence for a query if a declared global temporary table is involved or statistics on join columns are not collected. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPKN PM83457 DSNXOTS PM83457 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83457 DSNXOPKN DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPKN DSNXOTS LISTEND UK93392 COVER LETTER END UK93436 COVER LETTER START PROBLEM DESCRIPTION(S): PM74659 - **************************************************************** * USERS AFFECTED: ALL DB2 for z/OS V10 users * **************************************************************** * PROBLEM DESCRIPTION: The DB2 directory data base (DSNDB01) * * could experience significant space * * growth resulting from BIND/REBIND * * operations, DDL or Utility activity * **************************************************************** * RECOMMENDATION: * **************************************************************** The BIND/REBIND operation involves the need to delete the existing old package and reinsert the new package in the SPT01 table space. The deleted space within the same UR that is performing a REBIND operation can not be reused until the UR is committed. In addition, the subsequent insert of the new package may not reuse the committed delete space promptly due to the clustering order of the record within the table space. As a result, the SPT01 table space could experience significant space growth resulting from a large volume of concurrent BIND/REBIND operations. DB2 has been modified to allow a UR to reuse its own deleted space within the same commit scope if it has exclusive control of the page. In additional, the search algorithm has also been changed to reuse the deleted space sooner. These changes only apply to the DB2 directory data base (DSNDB01). PM81485 - **************************************************************** * USERS AFFECTED: ALL DB2 for z/OS V10 users * **************************************************************** * PROBLEM DESCRIPTION: The DB2 directory data base (DSNDB01) * * could experience significant space * * growth resulting from BIND/REBIND * * operations, DDL or Utility activity. * **************************************************************** * RECOMMENDATION: * * * * * * * 1 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * **************************************************************** The BIND/REBIND operation involves the need to delete the existing old package and reinsert the new package in the SPT01 table space. The deleted space within the same UR that is performing a REBIND operation can not be reused until the UR is committed. In addition, the subsequent insert of the new package may not reuse the committed delete space promptly due to the clustering order of the record within the table space. As a result, the SPT01 table space could experience significant space growth resulting from a large volume of concurrent BIND/REBIND operations. DB2 has been modified to allow a UR to reuse its own deleted space within the same commit scope if it has exclusive control of the page. In additional, the search algorithm has also been changed to reuse the deleted space sooner. In any case if the UR doing BIND/REBIND process needs to roll back, the log apply phase will process the log record by redoing the change physically instead of pseudo delete process. These changes only apply to the UTS table space created in the DB2 directory data base (DSNDB01). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74659,PM81485 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBHUN PM74659 PM81485 DSNIREPR PM74659 PM81485 DSNISGRT PM74659 PM81485 DSNISGSC PM74659 PM81485 DSNISUPI PM74659 PM81485 1 DSNKPOSI PM74659 PM81485 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74659 DSNIBHUN DSNIREPR DSNISGRT DSNISGSC DSNISUPI DSNKPOSI PM81485 DSNIBHUN DSNIREPR DSNISGRT DSNISGSC DSNISUPI DSNKPOSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBHUN DSNIREPR DSNISGRT DSNISGSC DSNISUPI DSNKPOSI LISTEND UK93436 COVER LETTER END UK93437 COVER LETTER START PROBLEM DESCRIPTION(S): PM81848 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who have * * queries containing ORDER BY, GROUP BY, or * * set function DISTINCT with an index matching * * the ORDER BY, GROUP BY, or set function * * DISTINCT columns. * **************************************************************** * PROBLEM DESCRIPTION: Possible incorrect output for a * * query containing ORDER BY, GROUP BY, * * or set function DISTINCT when hybrid * * join is chosen with SORTN_JOIN=N, an * * index matches the ORDER BY, GROUP BY, * * or set function DISTINCT columns, and * * no extra sort is added to handle this * * sorting. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output may occur for a query containing ORDER BY, GROUP BY, or set function DISTINCT when hybrid join is chosen with SORTN_JOIN=N, an index matches the ORDER BY, GROUP BY, or set function DISTINCT columns, and no extra sort is added to handle this sorting. The chosen access path included a RID list scan which did not preserve the order provided by the index. Additional Keywords: INCORROUT SQLINCORROUT SQLINCORR DB2INCORR/K SQLORDERBY SQLGROUPBY SQLDISTINCT SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN Code is added to include the extra sort in the situation described above. If the estimated cost of the new access path with the extra sort is higher than a different access path, an 1 access path without hybrid join may be chosen. An access path with an extra sort may be chosen if it is determined that the sort is needed to prevent incorrect output. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81848 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM81848 corrects a problem of possible incorrect output for a query containing ORDER BY, GROUP BY, or set function DISTINCT when hybrid join is chosen with SORTN_JOIN=N, an index matches the ORDER BY, GROUP BY, or set function DISTINCT columns, and no extra sort is added to handle this sorting. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTS1 PM81848 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81848 DSNXOTS1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTS1 LISTEND UK93437 COVER LETTER END UK93439 COVER LETTER START PROBLEM DESCRIPTION(S): PM75509 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS New Function Mode (NFM) * * users of Universal Table Space (UTS) * **************************************************************** * PROBLEM DESCRIPTION: Unexpected space growth due to * * unnecessary overflowing or double- * * overflowing of records during SQL * * UPDATE against UTS in DB2 10 NFM * **************************************************************** * RECOMMENDATION: * **************************************************************** For an SQL UPDATE, if the new record length is larger than the old record length, DB2 will check the current page if there is enough room to hold the new record. If there is not, DB2 needs to move the record to a new page called overflow page. Prior to 1 this fix, DB2 might use an incorrect old length of record to check the room and might move the record to an overflow page even though there is enough room on the base page to contain the new record. Two symptoms can be observed: (1) Unnecessary overflowing of record in base page (2) Unnecessary double-overflowing Sample recreation: ------------------ 1. Create a table space with 32K pages. 2. Create a table therein with a maximum record size on the order of 20,000 bytes. Commit. 3. Insert a 17,000-byte record. Commit. 4. Update the record (new length is 17,003). . A pointer record plus an overflow record are created even though the record should have stayed on the same page. The problem equally applies to cases when there are multiple records on a page, e.g. 100 bytes are still left at the end of the page and a record in the middle of the page is extended by 3 bytes. DB2 code has been modified to make sure that the correct old length of a record is used when checking for free space. Additional keywords: SQLUPDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75509 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIREPR PM75509 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75509 DSNIREPR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIREPR LISTEND UK93439 COVER LETTER END UK93522 COVER LETTER START PROBLEM DESCRIPTION(S): PM82279 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of UPDATE and * * SELECT statements * **************************************************************** 1 * PROBLEM DESCRIPTION: SELECT statements bound with ISO(UR) * * running concurrently with UPDATE may * * produce an incorrect output * **************************************************************** * RECOMMENDATION: * **************************************************************** In today's DB2, SELECT query bound with ISO(UR) can access uncommitted data row because there is no serialization between the SELECT and UPDATE. Therefore, there is a chance for the SELECT not see the data row due to a timing windows. Such timing window intervals increase for a record overflow case in the data-sharing environment since multiple data pages must be written-out/read-in to/from Global Buffer pool in synchronous way which may not be true in today's DB2. DB2 is modified to provide a relief for SELECT bound with ISO(UR) that is concurrently run with UPDATEs. The fix is not a complete solution which will synchronously write out an overflow page to GBP. This is to ensure an overflow page will arrive GBP early than the base pointer page. When SELECT fetches the base row, it would either see an 'old' record or a 'new' pointer record where its overflow data page should contain the new data row. There is a negative performance impact to UPDATE under this fixes since a synchronous write forces the UPDATE to wait until its page write I/O is complete. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82279 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISGRT PM82279 DSNISMRT PM82279 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82279 DSNISGRT DSNISMRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGRT DSNISMRT LISTEND UK93522 COVER LETTER END UK93532 COVER LETTER START PROBLEM DESCRIPTION(S): PM77111 - **************************************************************** * USERS AFFECTED: All DB2 for zOS users * **************************************************************** * PROBLEM DESCRIPTION: Collecting documentation for problems * * associated with RID POOL exhausting * * available storage is very difficult. A * 1 * easy, non-disruptive solution is * * needed. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 encounters problems due to exhausted available storage in the RID Pool, it is very difficult to collect the documentation needed to analyze the cause. By the time a console dump can be taken, the needed data may not be in memory. A real time solution is needed to address this. A new serviceability IFCID0375 is introduced. If this IFCID is active and a RID Pool out of storage condition is encountered, a trace will be written. DSN1SDMP job can be used to promptly take a dump of a system of analysis. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77111 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWHS PM77111 DSNDQW05 PM77111 DSNIREFS PM77111 DSNIREPR PM77111 DSNIRIDL PM77111 DSNIRIDR PM77111 DSNISRTI PM77111 DSNIXLDR PM77111 DSNURBXA PM77111 DSNWVINT PM77111 DSNXRRID PM77111 DSNXRRI9 PM77111 DSNXSFIN PM77111 DSNXSFML PM77111 DSNXSFPR PM77111 DSNXSFUN PM77111 DSNXSMIN PM77111 DSNXSMRL PM77111 DSNXSMUN PM77111 DSNXSPRM PM77111 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77111 DSNDQWHS DSNDQW05 DSNIREFS DSNIREPR DSNIRIDL DSNIRIDR DSNISRTI DSNIXLDR DSNURBXA DSNWVINT DSNXRRID DSNXRRI9 DSNXSFIN DSNXSFML DSNXSFPR DSNXSFUN DSNXSMIN DSNXSMRL DSNXSMUN DSNXSPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIREFS DSNIREPR DSNIRIDL DSNIRIDR DSNISRTI 1 DSNIXLDR DSNURBXA DSNWVINT DSNXRRID DSNXRRI9 DSNXSFIN DSNXSFML DSNXSFPR DSNXSFUN DSNXSMIN DSNXSMRL DSNXSMUN DSNXSPRM MACROS DSNDQWHS DSNDQW05 LISTEND UK93532 COVER LETTER END UK93545 COVER LETTER START PROBLEM DESCRIPTION(S): PM85792 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using varying * * length NOT PADDED indexes and columns * * defined NOT NULL * **************************************************************** * PROBLEM DESCRIPTION: SQLINCORROUT occurred for query using * * index access path with predicate * * push-down and NOT PADDED index defined * * on varying length NOT NULL columns * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLINCORROUT occurred while evaluating predicate for empty string. When empty string was detected, data was not moved to be evaluated; causing predicate to be evaluated based on residual data that had already been evaluated. The length of the string should always be moved, but skipped for empty strings. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLINDEX DB2 has been modified to correctly evaluate empty string data. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85792 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKMVKY PM85792 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85792 DSNKMVKY THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKMVKY LISTEND UK93545 COVER LETTER END UK93546 COVER LETTER START PROBLEM DESCRIPTION(S): PM83072 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: The following may occur when running * * multiple SQL/XML statements in the same * * application: * * * * ABEND04E RC00E20005 in module * * DSNNXCMT DSNSVSVB offset +08F2 * * * * ABEND0C4 RC00000038 in module * * DSNNXML DSNNORES offset +43C0 * **************************************************************** * RECOMMENDATION: * **************************************************************** When running multiple SQL/XML statements that require in memory copy of the documents, DB2 will re-use the working buffer. However, when the current document is 2 or more times bigger than the previous document, there is a logic error in extending the buffer which causes insufficient storage allocation. Below is an example of such SQL/XMl statement: SELECT XMLQUERY('$doc/a/b/c' PASSING XMLPARSE(DOCUMENT CAST(? AS BLOB(20000))) AS "doc") FROM SYSIBM.SYSDUMMY1; Within the same application, the above statement is first executed with a 4K XML document. Then, when re-executed, the same statement has a 12K XML document and an abend may occur. The above DB2 9 and 10 for z/OS problem was fixed to ensure there is sufficient storage for big documents. Additional keywords: SQLXML DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83072 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOBXI PM83072 DSNNOCCN PM83072 DSNNORCN PM83072 DSNNORES PM83072 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83072 DSNNOBXI DSNNOCCN DSNNORCN DSNNORES THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOBXI DSNNOCCN DSNNORCN DSNNORES LISTEND UK93546 COVER LETTER END UK93552 COVER LETTER START PROBLEM DESCRIPTION(S): PM83772 - **************************************************************** * USERS AFFECTED: All DB2 users in a data sharing environment. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C202AA in DSNB1PER. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the structure castout engine is active on a partition, and the same partition is getting physically opened by another agent concurrently, the castout process does not serialize with the physical open process correctly and encounters an abend during a page set P-lock request as it is already acquired and held by the other agent. DB2 structure castout engine has been fixed to correctly serialize with the physical open process through an Open/Close lock on a partitioned object. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83772 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5PCI PM83772 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83772 DSNB5PCI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNB5PCI LISTEND UK93552 COVER LETTER END UK93556 COVER LETTER START PROBLEM DESCRIPTION(S): PM62042 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS data sharing users with * * indexes. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKFTCH * * ERQUAL5004 occurred during index * * access. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 DSNKFTCH ERQUAL5004 occurred during index access due to an index page regression. The index page regression was introduced by a timing window during a Group Buffer pool page access where an update to an index page went undetected. Code has been modified to do additional page update detection during Group Buffer pool page access. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62042 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1SWS PM62042 DSNKDLE PM62042 DSNKINSL PM62042 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62042 DSNB1SWS DSNKDLE DSNKINSL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1SWS DSNKDLE DSNKINSL LISTEND UK93556 COVER LETTER END UK93589 COVER LETTER START PROBLEM DESCRIPTION(S): PM83613 - **************************************************************** 1 * USERS AFFECTED: DB2 10 for z/OS users who run ALTER TABLE * * ALTER COLUMN subsequent to RUNSTATS on the * * containing partitioned table space. * **************************************************************** * PROBLEM DESCRIPTION: Users may experience poor * * performance on ALTER TABLE ALTER * * COLUMN when RUNSTATS has been run * * on the containing partitioned table * * space. * **************************************************************** * RECOMMENDATION: * **************************************************************** Users may experience poor performance on ALTER TABLE ALTER COLUMN when RUNSTATS has been run on the containing paritioned table space. More specifically, when there are many SYSIBM.SYSCOLDISTSTATS with TYPE = 'C' associated with the table. This is because DB2 does not optimize when cleaning up the statistics records in SYSCOLDISTSTATS table. Clean up of the statistics records in SYSIBM.SYSCOLDISTSTATS has been optimized for ALTER TABLE ALTER COLUMN. ADDITIONAL KEYWORDS: SQLALTER SQLPERFORMANCE PERFM SQLSTATS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83613 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIALC PM83613 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83613 DSNXIALC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIALC LISTEND UK93589 COVER LETTER END UK93592 COVER LETTER START PROBLEM DESCRIPTION(S): PM83759 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of DECLARE GLOBAL * * TEMPORARY TABLE. * **************************************************************** * PROBLEM DESCRIPTION: DECLARE GLOBAL TEMPORARY TABLE may * * result in slow performance due to * 1 * excessive getpages. * **************************************************************** * RECOMMENDATION: * **************************************************************** DECLARE GLOBAL TEMPORARY TABLE may result in excessive getpages because DB2 is using a suboptimal index to fetch records from SYSIBM.SYSCOLUMNS. DECLARE GLOBAL TEMPORARY TABLE has been modified to use an optimal index to fetch records from SYSIBM.SYSCOLUMNS. ADDITIONAL KEYWORDS: SQLDGTT PERFM SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83759 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIDCL PM83759 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83759 DSNXIDCL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIDCL LISTEND UK93592 COVER LETTER END UK93614 COVER LETTER START PROBLEM DESCRIPTION(S): PM82708 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDM.DSNIUNCA * * ERQUAL5006 occurred when running REORG * * utility with DIAGNOSE TYPE(677). * **************************************************************** * RECOMMENDATION: * **************************************************************** When running REORG utility with DIAGNOSE TYPE(677), index manager code is called to write diagnostic log records during REORG BUILD phase. An internal error was encountered by REORG utility and the diagnostic log records were processed by the cleanup routine, caused ABEND04E RC00C90101 DSNIDM.DSNIUNCA ERQUAL5006. The diagnostic log records written during REORG utility should not be processed by DB2 log apply routines. Index manager code has been modified to write the diagnostic log 1 records properly during REORG BUILD phase so these log records won't be processed by the cleanup routine. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82708 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKFRMT PM82708 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82708 DSNKFRMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKFRMT LISTEND UK93614 COVER LETTER END UK93651 COVER LETTER START PROBLEM DESCRIPTION(S): PM81978 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users with the access * * control authorization exit * **************************************************************** * PROBLEM DESCRIPTION: Message ICH408I or an ABEND0C4 in * * the access control authorization exit * * may occur when DB2 commands are * * issued from a remote application. * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying PM53629 (PTF UK77576 in DB2 9, PTF UK77576 in DB2 10) message ICH408I or an ABEND0C4 in DSNX@XAC may occur if the access control authorization exit is being used and DB2 commands are issued from a remote connection. DB2 should ensure that a DB2 managed ACEE is available to process authorization of DB2 commands which have been issued from a remote application. This MSGICH408I or ABEND0C4 will occur at each DB2 for z/OS where the data base access command is processed. This APAR should be installed on each DB2 in the data sharing group for the fix to be fully effective. It is not required that this APAR be installed on all DB2 subsystems simultaneously. DB2 has been updated to avoid the ICH408I or ABEND0C4 in the access control authorization exit when processing DB2 commands which are issued from remote connections. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM81978 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWAAPI PM81978 DSNWACDF PM81978 DSN9SCNP PM81978 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM81978 DSNWAAPI DSNWACDF DSN9SCNP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWAAPI DSNWACDF DSN9SCNP LISTEND UK93651 COVER LETTER END UK93660 COVER LETTER START PROBLEM DESCRIPTION(S): PM83202 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG utility * * with FlashCopy image copies. * **************************************************************** * PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE with * * a FlashCopy only image copy failed * * with ABEND0C4 RC00000004 DSNURLGD + * * x'03E0' after termination in the LOG * * phase. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a REORG TABLESPACE SHRLEVEL CHANGE utility with FlashCopy as the only image copy. Following a TERM UTIL in the LOG phase, the REORG utility failed with ABENDS0C4 RC4 at DSNURLGD OFFSET03E0 when it attempted to write to low core storage with a zero pointer to a control block that had not been allocated. REORG TABLESPACE utility code has been modified to check to see if the block exists before updating it. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83202 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURLGD PM83202 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83202 DSNURLGD 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURLGD LISTEND UK93660 COVER LETTER END UK93661 COVER LETTER START PROBLEM DESCRIPTION(S): PM82500 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (NFM) users of RUNSTATS * * with TABLESAMPLE SYSTEM option against a * * compressed partitioned table space (classic * * or universal) whose partition 1 is empty * **************************************************************** * PROBLEM DESCRIPTION: During RUNSTATS with TABLESAMPLE SYSTEM * * running on compressed partitioned table * * space (classic or universal) whose * * partition 1 is empty, the following * * symptoms can occur: * * * * ABEND04E RC00C90101 DSNIZLDR ERQUAL5004 * * * * ABEND0C7 DSNIRFNX+B49A with MSGDSNU017I * * REASON=X'00C7' in the RUNSTATS joblog * * * * ABEND0C7 DSNUSTBL+657E with MSGDSNU017I * * RC00E40347 in the RUNSTATS joblog * * * * ABEND0C4 DSNIMOFR+02D8 with overlay, * * followed by ABEND04E RC00E20005 during * * thread deallocation * **************************************************************** * RECOMMENDATION: * **************************************************************** While running RUNSTATS with TABLESAMPLE SYSTEM (where the sampling value is not 100) on a compressed partitioned table space (classic or universal) whose partition 1 is empty, the aforementioned abends could occur during row decompression stage of the RUNSTATS page sampling scan. In the 04E DSNIZLDR:5004 case, DB2 attempted to decompress a row from partition 2 using partition 1's compression dictionary, which did not exist. In the 0C7 DSNIRFNX+B49A and 0C7 DSNUSTBL+657E cases, DB2 attempted to decompress a row from partition 2 using partition 1's compression dictionary, which existed from the time when partition 1 had some data. However, the dictionary did not match this partition 2 row, hence the abend. In the 0C4 DSNIMOFR+02D8 case (followed by 04E RC00E20005 1 DSNUGSTA.DSNSVBK+1AB6 during thread deallocation), the abends occurred because the internal MSIB and USBL structures were overlaid given that DB2 tried to decompress a row from partition 2 using partition 1's compression dictionary. Due to the incorrect dictionary used as well as row conversion to the latest OBD format, the row was now bigger than the maximum possible row size for the table, exceeding into surrounding memory areas used by MSIB and USBL. Other, unpredictable memory areas can theoretically be overlaid also. The root cause of the abends is that the TABLESAMPLE code set an internal partition indicator to 1, incorrectly assuming that partition 1 would always participate in page sampling. However, this was not the case when partition 1 was empty. Code has been changed to ensure that the internal partition indicator always reflects the partition covering the pages being sampled. Additional keywords: ABENDS0C7 OFFSETB49A OFFSET657E OFFSET02D8 SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82500 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIPGSP PM82500 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82500 DSNIPGSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIPGSP LISTEND UK93661 COVER LETTER END UK93669 COVER LETTER START PROBLEM DESCRIPTION(S): PM86543 - **************************************************************** * USERS AFFECTED: All users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: DB2 restart fails with ABEND04E * * RC00D1032A after the log RBA has * * advanced into the CRITICAL range. * * The ENDRBA of the current active log * * data set was incorrectly set lower than * * the STARTRBA of the log data set. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 The current log RBA was approaching the end of the log RBA range and DB2 was issuing MSGDSNJ032I and MSGDSNJ033E. This continued until the log RBA advanced into the CRITICAL range (RBA value greater than x'FFFF00000000') and DB2 had switched to an active log pair that would have contained the end of the RBA range. The log switch correctly set the ENDRBA value of the log pair to x'FFFFFFFFFFFF'. But a subsequent restart incorrectly updated the ENDRBA to the STARTRBA of the log data sets plus the high-used RBA and did not detect the RBA 'wrap'. This resulted in the ENDRBA value being set lower than the STARTRBA value for the current active log pair which caused an ABEND04E RC00D1032A as the checkpoint RBA could not be located. DSNJW009 and DSNJW007 have been corrected to detect this log 'wrap' situation and to not update the ENDRBA value of a log data set to an RBA value less than the STARTRBA value. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86543 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJW007 PM86543 DSNJW009 PM86543 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86543 DSNJW007 DSNJW009 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJW007 DSNJW009 LISTEND UK93669 COVER LETTER END UK93713 COVER LETTER START PROBLEM DESCRIPTION(S): PM79551 - **************************************************************** * USERS AFFECTED: (1) All users of the DB2 10 for z/OS feature * * CONCENTRATE STATEMENTS WITH LITERALS * * for the DB2 Dynamic Statement Cache, and * * with either of the following: * * - The IBM Data Server Driver for JDBC * * and SQLJ or The IBM Data for ODBC and * * CLI, where the Driver's DB2 * * packages are bound KEEPDYNAMIC(YES) * * and the Driver connection or * * datasource property * * 'statementConcentrator' is used to * * request the DB2 feature * * CONCENTRATE STATEMENTS WITH LITERALS * 1 * - or, any application bound as * * KEEPDYNAMIC(YES) that issues dynamic * * SQL using EXECUTE IMMEDIATE * * * * (2) All DB2 users of the IBM Data Server * * Driver for JDBC and SQLJ or the IBM Data * * Server Driver for ODBC and CLI, where * * the Driver's DB2 packages are bounds as * * KEEPDYNAMIC(YES) or * * REOPT(VARS | ALWAYS | ONCE | AUTO) * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -803 issued for dynamic * * SET CURRENT SQLID after a previous * * dynamic statement received SQLCODE -803 * * * * Other unexpected -SQLCODEs are possible * * and for other SQL statements. * * See APAR text below for details. * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem #1 (DB2 10 only): ------------------------- Customer reported that DB2 invalidly issued SQLCODE -803 for a dynamic SET CURRENT SQLID statement. The customer was using DB2 10 with IBM Data Server Driver for JDBC and SQLJ (aka JCC Driver) and the Driver connection or datasource property statementConcentrator to request the DB2 10 feature CONCENTRATE STATEMENTS WITH LITERALS for dynamic SQL prepared for the DB2 Dynamic Statement Cache (DSC). Prior to the SET CURRENT SQLID statement, the user submitted an SQL INSERT statement containing literals to DB2 via the JCC Driver and that INSERT statement failed the execution step with SQLCODE -803 (attempt to insert a duplicate row). The user then submitted the SET CURRENT SQLID statement also via the JCC Driver and DB2 incorrectly failed it with the same SQLCODE803 as for the INSERT (with same error token values). SQLCODE803 does not of course apply to a SET CURRENT SQLID statement, and DB2 should not have failed the SET statement. . The invalid SQLCODE803 on SET SQLID occurred when the JCC Driver used the 'same' EXECUTE IMMEDIATE package/program section to send both the INSERT and the SET SQLID statements to DB2 for execution. To show how this can be done, a simple example is as follows, however, this example is not intended to show what the JCC Driver does: . DO I = 1 TO 2; IF I = 1 THEN stmttext = 'INSERT INTO TABLE1 VALUES (1,2,3)'; ELSE stmttext = 'SET CURRENT SQLID = ''USERT001'' '; EXEC SQL EXECUTE IMMEDIATE :stmttext; END; . 1 The INSERT contained literals, DSC was active, and the JCC Driver flowed the user's request for CONCENTRATE STATEMENTS WITH LITERALS behavior, so DB2 replaced the literals in the INSERT statement then prepared and executed the INSERT. In addition, because the JCC Driver package was bound KEEPDYNAMIC(YES), during the prepare DB2 saved in this DB2 thread's storage a special copy of the original INSERT text (without literals replaced) to be used for KEEPDYNAMIC implicit-prepare of this particular INSERT. This is done because the INSERT text that would normally be used for the implicit-prepare is the cached statement text which now has the literals replaced. . When the JCC Driver reused the 'same' EXECUTE IMMEDIATE section to send the SET CURRENT SQLID statement to DB2 to be prepared and executed, DB2 still had the special saved INSERT text for this section because of CONCENTRATE STATEMENTS WITH LITERALS and incorrectly used that saved text to prepare and execute, instead of using the new SET CURRENT SQLID text. This of course resulted in the same SQLCODE803 being returned by DB2. . DB2 should have discarded the special saved INSERT text when the JCC Driver submitted the SET CURRENT SQLID using the same EXECUTE IMMEDIATE section that was used for the previous INSERT statement. Moreover, for EXECUTE IMMEDIATE saving a special copy of the original INSERT statement text for KEEPDYNAMIC is not necessary because EXECUTE IMMEDIATE is a one-time only PREPARE+EXECUTE function, and the statement will not remain prepared at COMMIT time (when the KEEPDYNAMIC(YES) function is in effect). So KEEPDYNAMIC(YES) behavior will not actually be done for the EXECUTE IMMEDIATE section. . This specific problem with CONCENTRATE STATEMENTS WITH LITERALS, EXECUTE IMMEDIATE, and KEEPDYNAMIC(YES) can also occur 'without' using the JCC Driver (or ODBC and CLI Driver) if a user application reuses the same EXECUTE IMMEDIATE program section to execute SQL (similar to the example shown previously). The problem is not limited to INSERT or SET CURRENT SQLID, and does not require that the previous SQL statement using the same EXECUTE IMMEDIATE section fail (i.e., the previous INSERT need not fail). This failing scenario may not result in -SQLCODES, depending upon what occurred for the previous SQL statement executed by the EXECUTE IMMEDIATE. DB2 can return SQLCODE0 but that does not mean that the problem did not occur. The failing scenario may also result in various INCORROUTs or unexpected behavior when DB2 prepares and executes the wrong SQL statement text for the EXECUTE IMMEDIATE request. . . Problem #2 (DB2 9 and DB2 10): ------------------------------ While resolving problem #1, DB2 Development discovered that another similar problem of DB2 executing the wrong SQL stmt text for an EXECUTE IMMEDIATE request may occur 'without' using the DB2 feature CONCENTRATE STATEMENT WITH LITERALS, but when 1 using either the IBM Data Server Driver for JDBC and SQLJ or the IBM Data Server Driver for ODBC and CLI, where the Driver's DB2 packages are bound as KEEPDYNAMIC (YES) or REOPT ( VARS | ALWAYS | ONCE | AUTO ). Problem #2 also involves saving SQL statement text during a PREPARE and could have similar or same symptoms as Problem #1, but only occurs when using these IBM Data Server Drivers to submit dynamic SQL statements to DB2 due to the particular Driver architecture for issuing SQL PREPARE and SQL EXECUTE IMMEDIATE requests to DB2. Problem #2 does not occur with a user application scenario (unlike the reported problem #1). For both problem #1 and #2, DB2 was modified to not save the SQL statement text submitted under EXECUTE IMMEDIATE with KEEPDYNAMIC(YES), because it is not used or necessary. This change also helps to reduce storage in the DB2 storage pool ' STMT CACHE BLOCKS 2G ' when using KEEPDYNAMIC(YES) + EXECUTE IMMEDIATE + Dynamic Statement Caching. . In addition, for problem #2 DB2 was also changed to discard any saved statement text for an EXECUTE IMMEDIATE program section when a new EXECUTE IMMEDIATE request is submitted for that section. . Additional search keywords: INCORROUT SQLCODE803 SQLKEEPDYNAMIC JCCSQLJ JCCT2ZOS JCCT4 SQLDYNSTMTCACHE SQLREOPTAUTO SQLREOPTONCE SQLREOPTALWAYS SQLREOPTVARS SQLSTORAGE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79551 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEDSC PM79551 DSNXERT2 PM79551 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79551 DSNXEDSC DSNXERT2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEDSC DSNXERT2 LISTEND UK93713 COVER LETTER END UK93716 COVER LETTER START PROBLEM DESCRIPTION(S): PM82999 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 Users * **************************************************************** * PROBLEM DESCRIPTION: With Zparm EVALUNC in effect, * * when some applications query * * non-UTS rows, uncommitted deleted * * rows were skipped. If those * * uncommitted deleted rows were * * rolled back, the application * * would not be able to return them * * back to the user. * **************************************************************** * RECOMMENDATION: * **************************************************************** System zparm EVALUNC controls whether predicate evaluation is to be allowed on uncommitted data. When zparm EVALUNC was set to YES, Data that did not satisfy the predicate during evaluation but then, because of undo processing (ROLLBACK or statement failure), reverted to a state that did satisfy the predicate was missing from the answer set. Since EVALUNC is a system option, individual query statement is not able to turn it off. DB2 provides the ability to override ZPARM EVALUNC for individual remote statements via IBM Data Server Driver for ODBC and CLI. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82999 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PK71143 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PK71143 corrects a problem that can cause RS00C90096 (number of page locks reached numlkus install limit) being issued for an update/delete/merge statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIACCH PM82999 DSNIONX2 PM82999 DSNIOST2 PM82999 DSNIRNXT PM82999 DSNIRPRE PM82999 DSNISFRL PM82999 DSNISFS PM82999 DSNISRID PM82999 DSNKCKOP PM82999 DSNKFLST PM82999 DSNKFPRV PM82999 DSNKFTCH PM82999 1 DSNKINSL PM82999 DSNKNXT2 PM82999 DSNLXPRS PM82999 DSNLXRSS PM82999 DSNXERT2 PM82999 DSNXOMI PM82999 DSNXOMS PM82999 DSNXOUID PM82999 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82999 DSNIACCH DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNISFRL DSNISFS DSNISRID DSNKCKOP DSNKFLST DSNKFPRV DSNKFTCH DSNKINSL DSNKNXT2 DSNLXPRS DSNLXRSS DSNXERT2 DSNXOMI DSNXOMS DSNXOUID THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIACCH DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNISFRL DSNISFS DSNISRID DSNKCKOP DSNKFLST DSNKFPRV DSNKFTCH DSNKINSL DSNKNXT2 DSNLXPRS DSNLXRSS DSNXERT2 DSNXOMI DSNXOMS DSNXOUID LISTEND UK93716 COVER LETTER END UK93719 COVER LETTER START PROBLEM DESCRIPTION(S): PM80227 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and 10 for z/OS who are * * also using IBM DB2 Analytics Accelerator. * **************************************************************** * PROBLEM DESCRIPTION: This APAR contains the following fixes * * for DB2 accelerator support: * * * * (1) A query is incorrectly offloaded * * when the right hand side of a * * predicate contains a date, time or * 1 * timestamp duration. * * * * (2) A query that contains built-in * * string functions with CODEUNITS as * * one of the arguments or the cast * * specification may be incorrectly * * offloaded or incorrectly blocked for * * offloading in DB2 10. * * * * (3) A query that contains an IN list * * may be incorrectly blocked from * * offload. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** (1) A query is incorrectly offloaded when the right hand side of a predicate contains a date, time or timestamp duration. The results returned from the accelerator may not match the results when the same query is executed on DB2. For example: WHERE YEAR(L_SHIPDATE) = 1995-0 (2) A query that contains built-in string functions with CODEUNITS as one of the arguments or the cast specification may be incorrectly offloaded or incorrectly blocked for off- loading in DB2 10. These functions include CHAR, VARCHAR, LEFT, RIGHT, LOCATE, LOCATE_IN_STRING, POSITION, SUBSTRING, CHARACTER_LENGTH, etc. (3) A query that contains an IN list may be incorrectly blocked from offload. EXPLAIN of the query will show a value of 900 for DSN_QUERYINFO_TABLE.REASON_CODE. (1) Code is fixed to properly block offload of date, time and timestamp duration. (2) Code is fixed to properly handle built-in string functions with CODEUNITS as one of the arguments and the cast specifica- tion as far as query offloading is concerned. (3) Code is fixed to offload a query with an IN list. Additional Search Keywords: IDAAV3R1/K IDAAV2R1/K SQLINLIST SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM80227 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCF PM80227 DSNXOEX1 PM80227 DSNXOOS1 PM80227 1 DSNXOW1 PM80227 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM80227 DSNXOCF DSNXOEX1 DSNXOOS1 DSNXOW1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCF DSNXOEX1 DSNXOOS1 DSNXOW1 LISTEND UK93719 COVER LETTER END UK93725 COVER LETTER START PROBLEM DESCRIPTION(S): PM79556 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of row change timestamp column. * **************************************************************** * PROBLEM DESCRIPTION: UNLOAD FROMCOPY gets ABEND0C4 * * RC00000038 in DSNUULCA OFFSET55A2 * * when a row change timestamp column * * was added to the table. * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran an UNLOAD FROMCOPY on an image copy of a table space that had a table with an alter added row change timestamp column. The UNLOAD utility failed with ABEND0C4 The cause is that DB2 referred to an internal control block that was not available. For the case when the internal control block is not available, DB2 code has been modified to use other means to acquire a value to use to initialize the row change timestamp value when the column is missing from the row. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79556 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICOFS PM79556 DSNICUMW PM79556 DSNIDIFS PM79556 DSNIDLER PM79556 DSNIETRV PM79556 DSNIIDIS PM79556 DSNIKDEF PM79556 DSNILREP PM79556 DSNIMOFR PM79556 1 DSNIREFS PM79556 DSNIRELK PM79556 DSNIRFNX PM79556 DSNIRLPG PM79556 DSNISRTI PM79556 DSNITDLE PM79556 DSNIZMOS PM79556 DSNUULCA PM79556 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79556 DSNICOFS DSNICUMW DSNIDIFS DSNIDLER DSNIETRV DSNIIDIS DSNIKDEF DSNILREP DSNIMOFR DSNIREFS DSNIRELK DSNIRFNX DSNIRLPG DSNISRTI DSNITDLE DSNIZMOS DSNUULCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICOFS DSNICUMW DSNIDIFS DSNIDLER DSNIETRV DSNIIDIS DSNIKDEF DSNILREP DSNIMOFR DSNIREFS DSNIRELK DSNIRFNX DSNIRLPG DSNISRTI DSNITDLE DSNIZMOS DSNUULCA LISTEND UK93725 COVER LETTER END UK93759 COVER LETTER START PROBLEM DESCRIPTION(S): PM85238 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS version 10 users of SQL * * statements with range list access and one * * of the non-boolean term predicates under * * OR is not the matching predicate. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may be returned when * * a range list access path is chosen for * * the table and one of non-boolean term * * predicates under OR is not the matching * * predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 An example for incorrect output is shown below: index I1 on T1(C1,C2) (C1 = ? AND C2 > ?) OR (C1 > ? AND C2 = ?) In the second branch,c2 = ? is not the matching predicate, but was incorrectly chosen.Since the path was not re-evaluated as it should have been,incorrect output may occur. DB2 has been modified to correctly process the aforementioned SQL statement,so there will be no incorrect output. Additional Keywords: SQLINCORR SQLINCORROUT DB2INCORR/K SQLRANGELIST SQLOR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85238 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM85238: See PM85238 APAR/PTF text for additional information about why a REBIND is necessary. PM85238 corrects a problem of incorrect output may be returned when a range list access path is chosen for the table and one of non-boolean term predicates under OR is not the matching predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM57955: See PM57955 APAR/PTF text for additional information about why a REBIND is necessary. PM57955 corrects a problem of ABEND04E RC00E70005 in DSNXORGL P130 when query with range list access (ACCESSTYPE = 'NR' in PLAN_TABLE) participated in parallel sort-merge join group. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXORGL PM85238 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85238 DSNXORGL 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXORGL LISTEND UK93759 COVER LETTER END UK93800 COVER LETTER START PROBLEM DESCRIPTION(S): PM82954 - **************************************************************** * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of LOAD * * RESUME on compressed pageset or partition * * (whose compression dictionary was generated * * by insert), where at the time of LOAD RESUME * * the compression dictionary is at current end * * of data in the pageset or partition * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNI010I - BROKEN PAGE ACCESSED * * TYPE00000302 MODNAME DSNILPG and * * MSGDSNT500I - RESOURCE UNAVAILABLE * * RC00C90087 issued during LOAD RESUME * * on COMPRESS on INSERT table space * * whose current end of data (highest page * * in pageset or partition) is a * * dictionary page, corrupting this * * dictionary page * * * * Then, potentially followed by * * MSGDSNB209I - BUFFER MANAGER CLEANUP * * ROUTINE (DSNB1CFC) HAS BEEN SCHEDULED * * and MSGDSNB221I - BUFFER MANAGER * * CLEANUP PROCESS WAS NOT REQUIRED * * * * In addition to the dictionary page * * being protected by broken page status, * * the pageset or partition is left in * * RECP status * **************************************************************** * RECOMMENDATION: * **************************************************************** During LOAD RESUME into a compressed table space whose compression dictionary was built during the INSERT process (new in DB2 10 NFM) and dictionary pages are at the current end of data (meaning, page number HPGZ4PNO is the highest page in the pageset or partition), DB2 mistakenly attempted to load rows into the highest dictionary page, resulting in the symptoms mentioned above. In the affected code path, DB2 code did not account for the possibility that when a dictionary is built by the INSERT process, the dictionary pages need not be at the beginning of the pageset or partition. In this case, when looking for the 1 current end of data for the LOAD to resume into, there were no pages after the dictionary pages and so DB2 mistakenly picked the final physical dictionary page as the resumption point. Given that this final physical dictionary page was being treated as a data page, the space search for a new row was relying on wrong information (scanning through a page "ID-map" which was not really an ID-map). As a result, the row was loaded into the dictionary page, corrupting the page's functional content. The aforementioned broken page-related messages were issued and the broken page status was turned on for protection, along with the RECP status on the pageset or partition. If this problem occurs, until the fix is available, the compression dictionary page shown in the message DSNI010I BROKEN PAGE ACCESSED should be recovered (e.g. from image copy), followed by REORG on the pageset or partition (regardless of whether KEEPDICTIONARY is specified or not). The REORG will move the compression dictionary pages to the beginning of the pageset/partition, in which case this problem does not exist. If this problem has not occurred and yet HPGZ4PNO happens to be the current end of data, until the fix is available, a REORG can be run on the pageset or partition (regardless of whether KEEPDICTIONARY is specified or not). The REORG will move the compression dictionary pages to the beginning of the pageset/ partition, in which case this problem does not exist. Code has been changed for LOAD RESUME to tolerate compression dictionary pages being at current end of data. Additional keywords: SQLINSERT SQLMERGE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82954 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIHLOD PM82954 DSNILPG PM82954 DSNIRLPG PM82954 DSNURWBF PM82954 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82954 DSNIHLOD DSNILPG DSNIRLPG DSNURWBF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIHLOD DSNILPG DSNIRLPG DSNURWBF LISTEND 1UK93800 COVER LETTER END UK93802 COVER LETTER START PROBLEM DESCRIPTION(S): PM85466 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users (CM and above) of * * declared global temporary tables (including * * the internal kind built during static * * scrollable cursors or INSTEAD OF triggers) * * when they are stored in DB2 STOGROUP-managed * * workfile table spaces (not user-managed) * **************************************************************** * PROBLEM DESCRIPTION: High page latch contention on workfile * * table space's space map pages (e.g. * * page 1) during concurrent declared * * global temporary table processing * * (either external DGTTs or internal * * DGTTs built during static scrollable * * cursor or INSTEAD OF trigger activity), * * when the DGTT is stored in DB2 STOGROUP * * -managed table space (not user-managed) * **************************************************************** * RECOMMENDATION: * **************************************************************** High space map page latch contention was observed during DGTT activity. The root cause of this issue is that DB2 did not correctly maintain workfile table space usage counts, which mistakenly made DB2 choose a small subset of workfile table spaces, when instead the workload should have been spread out across all workfile table spaces that DGTTs typically go into. Code has been changed to properly maintain workfile table space usage counts during DGTT activity. Additional keywords: SQLDGTT SQLTRIGGER SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85466 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISEGF PM85466 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85466 DSNISEGF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISEGF LISTEND UK93802 COVER LETTER END 1 UK93882 COVER LETTER START PROBLEM DESCRIPTION(S): PM84232 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * native SQL procedure and non-inline SQL * * scalar function. * **************************************************************** * PROBLEM DESCRIPTION: INCORRECT OUTPUT may occur when an * * SQL variable or SQL parameter of the * * character string data type is * * referenced in the datetime comparison * * inside a native SQL procedure or * * non-inline SQL scalar function. * **************************************************************** * RECOMMENDATION: * **************************************************************** INCORRECT OUTPUT may occur when an SQL variable or SQL parameter of character string data type is referenced in datetime comparison in basic predicate, BETWEEN predicate, IN predicate, or search-condition in any SQL control statements such as IF statement inside a native SQL procedure or non-inline SQL scalar function. Depending on how predicate is written in the query, it could return wrong rows, too few rows, or too many rows. Here are detailed conditions for each type of predicate: 1. Basic predicate, BETWEEN predicate, search-condition in SQL control statements SQL variable or SQL parameter of character string data type is compared with the expression of datetime data type and the expression is not a column, SQL variable or SQL parameter. 2. IN predicate SQL variable or SQL parameter of character string data type is compared with a datetime column in the select list of a fullselect as right hand side of the predicate. EXAMPLE ======= CREATE TABLE T1 (TSCOL TIMESTAMP, DATECOL DATE)! INSERT INTO T1 VALUES ('2009-10-10-01.02.02.123456', '2011-10-10')! CREATE PROCEDURE MYPROC() LANGUAGE SQL BEGIN DECLARE V1 VARCHAR(10); DECLARE V2 INTEGER; 1 DECLARE V3 VARCHAR(10); SET V1 = CURRENT_DATE; SELECT 1 INTO V2 FROM SYSIBM.SYSDUMMY1 WHERE V1 = CURRENT_DATE; SET V1 = '2010-10-10'; SET V3 = '2011-10-10'; SELECT 1 INTO V2 FROM T1 WHERE V1 BETWEEN DATE(TSCOL) AND V3; SET V1 = '2011-10-10'; SELECT 1 INTO V2 FROM SYSIBM.SYSDUMMY1 WHERE V1 IN (SELECT DATECOL FROM T1); END! DB2 is updated to evaluate datetime comparison correctly in SQL native procedure and non-inline SQL scalar function. Additional Keywords: SQLNATIVESQLPL INCORROUT SQLINCORR DB2INCORR/K SQLINCORROUT SQLIN SQLBETWEEN SQLEQUAL SQLLT SQLGT SQLDATE SQLTIME SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84232 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: PM84232 corrects a problem of incorrect output when a native SQL procedure or a non-inline SQL scalar function contains an SQL statement that evaluates a datetime comparison with SQL variable or SQL parameter of the character string data type. type. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected, or ALTER FUNCTION REGENERATE is required for each non-inline SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure or non-inline SQL scalar function could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODTV PM84232 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84232 DSNXODTV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXODTV LISTEND UK93882 COVER LETTER END UK93910 COVER LETTER START PROBLEM DESCRIPTION(S): PM84091 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of IFI 306 with * * compressed data rows. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNIOPPZ 5001 (ERQUAL5001) * * when IFC 306 read on one of undo/redo * * log records with compress attribute. * **************************************************************** * RECOMMENDATION: * **************************************************************** While IFC 306 readers working on one of undo/redo log records with compress attribute, the database that is associated with the object of any undo/redo log could have been dropped. DB2 would memorize the drop state if it finds the database indeed had been dropped and should not try to reference this database again, otherwise, a unnecessary abend would occur. DB2 code is modified to skip the access of any database that had been dropped already. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84091 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBCTD PM84091 DSNIOPPZ PM84091 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84091 DSNIBCTD DSNIOPPZ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBCTD DSNIOPPZ LISTEND UK93910 COVER LETTER END UK93912 COVER LETTER START PROBLEM DESCRIPTION(S): PM84810 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with applications * * that use SQL TRUNCATE Table statement and * * bound with RELEASE(DEALLOCATE). * **************************************************************** * PROBLEM DESCRIPTION: After TRUNCATE Table, DB2 keeps the * * gross lock even after Commit if the * * application is bound with * * RELEASE(DEALLOCATE). This causes * * other applications to be timed out * * with RC00C9008E when trying to access * * this table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 will acquire a gross lock on the table space for Truncate table. If the application is bound with RELEASE(DEALLOCATE), then DB2 mistakenly keeps the gross lock across Commit and will not release it until this thread is deallocated. This causes other applications to be timed out when trying to access this table space with reason code 00C9008E. A fix is made in DB2 to release the gross lock on the table space at Commit. This will allow other applications to access this table space after Truncate table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84810 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICMT2 PM84810 DSNILKDY PM84810 DSNIPSFI PM84810 DSNISDLE PM84810 DSNISEGD PM84810 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84810 DSNICMT2 DSNILKDY DSNIPSFI DSNISDLE DSNISEGD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICMT2 DSNILKDY DSNIPSFI DSNISDLE DSNISEGD LISTEND UK93912 COVER LETTER END UK93918 COVER LETTER START PROBLEM DESCRIPTION(S): PM83600 - 1 **************************************************************** * USERS AFFECTED: All DB2 users of DELETE statement with AFTER * * DELETE Trigger and ALTER TABLE with ADD * * COLUMN clause. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90D01 in DSNONLLE+19F8 * * on an INSERT statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** After a base table is altered to add a new LOB column, if the table is defined with an AFTER-DELETE trigger, then DB2 mistakenly handled the missing LOB column with a wrong default indicator value. DB2 code is fixed to handle the default value for the newly added LOB column under AFTER-DELETE trigger. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83600 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICUMW PM83600 DSNIDLER PM83600 DSNILREP PM83600 DSNIMOFR PM83600 DSNIRELK PM83600 DSNIRFNX PM83600 DSNITDLE PM83600 DSNIZMOS PM83600 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83600 DSNICUMW DSNIDLER DSNILREP DSNIMOFR DSNIRELK DSNIRFNX DSNITDLE DSNIZMOS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICUMW DSNIDLER DSNILREP DSNIMOFR DSNIRELK DSNIRFNX DSNITDLE DSNIZMOS LISTEND UK93918 COVER LETTER END UK93951 COVER LETTER START PROBLEM DESCRIPTION(S): PM84852 - **************************************************************** 1 * USERS AFFECTED: All users of package accounting on DB2 10 * * for zOS with PTF UK83463 (APAR PM72274) * * installed. * **************************************************************** * PROBLEM DESCRIPTION: Long names values are incorrect in * * IFCID239 when UK83463 (APAR PM72274) * * is installed. * **************************************************************** * RECOMMENDATION: * **************************************************************** UK83463 traces a section DSNDQPAC with an incorrect length in the IFCID239. As a result, calculation of all offsets to long name values at the end of the QPAC section is incorrect. This leads to the incorrect values in the following fields: QPACLOCN_Off, QPACCOLN_Off, QPACPKID_Off, QPACASCH_Off, QPACAANM_Off. Correctly trace the DSNDQPAC section. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84852 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The value of QWHSSUBV has been increased to 3. If this value is greater or equal to 3, DSNDQPAC section of IFCID239 contains class 3 times for IDAA offload. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWVTIT PM84852 DSNWVZPS PM84852 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84852 DSNWVTIT DSNWVZPS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWVTIT DSNWVZPS LISTEND UK93951 COVER LETTER END UK93952 COVER LETTER START PROBLEM DESCRIPTION(S): PM83906 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS sers of packages that * * are in NFM or complete step ENFM0037 of * * ENFM. * **************************************************************** * PROBLEM DESCRIPTION: Customer could receive ABEND04E * * RC00E2000C at DSNGEPLC.DSNSVSVB * * OFFSET0AC2. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** When reading package directory from SPT01, an internal buffer is allocated, which is not freed and causes the storage full. DB2 has been changed to free the buffer after the package directory is read in. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83906 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGEFLC PM83906 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83906 DSNGEFLC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFLC LISTEND UK93952 COVER LETTER END UK93989 COVER LETTER START PROBLEM DESCRIPTION(S): PM82438 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who use * * IBM DB2 Analytics Accelerator and LOCAL * * DATE FORMAT of dd/mm/yyyy * **************************************************************** * PROBLEM DESCRIPTION: Queries referencing an expression that * * returns a LOCAL DATE format cannot * * be offloaded * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR provides support for locally-defined DATE format of dd/mm/yyyy for users of IBM DB2 Analytics Accelerator so that queries referencing an expression that return a DATE data type are eligible for query offload. The new DATE format to be allowed is dd/mm/yyyy. The new support for LOCAL DATE format is enabled using a new option, 4, to the DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used to specify additional types of SQL queries to be included in query offloading. The new option is: * 4 : The queries that reference an expression with a DATE data type that 1 uses a LOCAL format are not blocked from executing on IBM DB2 Analytics Accelerator. IBM DB2 Analytics Accelerator will use the dd/mm/yyyy format as LOCAL format. The option 4 should be specified only when the DATE FORMAT field of install panel DSNTIP4 specifies LOCAL or when application programs that process SQL on DB2 have been precompiled with the DATE(LOCAL) option. In either case, the LOCAL date exit routine must also define the specific 'dd/mm/yyyy' date format. If the LOCAL format is not defined as 'dd/mm/yyyy', the query may return unpredictable results. If option 4 is specified on any member in a data sharing environment, it is recommended to specify it on all members. See the HOLD information for additional details on this option. This APAR also adds a new reason code value 19 to indicate that the accelerator server driver level is downlevel for a specific function in the SQL statement. The proper action is to update the accelerator server driver to the correct level to utilize the function in the SQL statement. New value for DSN_QUERYINFO_TABLE column REASON_CODE : 19 --------------------------------------------------------- The accelerator server is not at the correct level and does not support a function in the SQL statement. The column QI_DATA contains the function text or expression text that is using the unsupported function for the given accelerator server level. Update the accelerator server to enable offload of the SQL statement that contains the function text or expression text. Existing -4742 SQLCODE with a new reason code 19 ------------------------------------------------ The accelerator server is not at the correct level and does not support a function in the SQL statement. Update the accelerator server to enable offload of the SQL statement that contains the function text or expression text. Additional Keywords: IDAAV3R1/K SQLDATE Code has been added to support locally-defined DATE format of the form dd/mm/yyyy when option 4 is specified for DSN6SPRM.QUERY_ACCEL_OPTIONS, and the DATE FORMAT field of install panel DSNTIP4 specifies LOCAL or when application programs that process SQL on DB2 have been precompiled with the DATE(LOCAL) option. In either case, the LOCAL date exit routine must also define the specific 'dd/mm/yyyy' date format. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM82438 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM82438 (V10) System Requirements: To take advantage of the new LOCAL date format support for 'dd/mm/yyyy' on IBM DB2 Analytics Accelerator, the following fixes are needed in conjunction with this PTF: For IBM DB2 Analytics Accelerator, PM80112/UK93624 must be applied. For Netezza, level NZ 6.0.8 P-6 or higher is needed. This PTF adds a new option, 4, to the DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used to specify additional types of SQL queries to be included in query offloading. The new option is: * 4 : The queries that reference an expression with a DATE data type that uses a LOCAL format are not blocked from executing on IBM DB2 Analytics Accelerator. IBM DB2 Analytics Accelerator will use the dd/mm/yyyy format as LOCAL format. The option 4 should be specified only when the DATE FORMAT field of install panel DSNTIP4 specifies LOCAL or when application programs that process SQL on DB2 have been precompiled with the DATE(LOCAL) option. In either case, the LOCAL date exit routine must also define the specific 'dd/mm/yyyy' date format. If the LOCAL format is not defined as 'dd/mm/yyyy', the query may return unpredictable results. If option 4 is specified on any member of a data sharing environment, it is recommended to specify it on all members. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is mutually exclusive from all other settings. The options can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=3 QUERY_ACCEL_OPTIONS=(1,2) QUERY_ACCEL_OPTIONS=(1,3) QUERY_ACCEL_OPTIONS=(1,2,4) No action is required after applying this PTF unless both of the following are true: * The DSN6SPRM.ACCEL parameter is set to AUTO or COMMAND to enable query acceleration. * The DSNHDECP.DATE parameter is set to LOCAL and the LOCAL date exit defines the specific dd/mm/yyyy date format. 1 In that case, you need to take the following actions after applying this PTF: (1) Update your customized copy of job DSNTIJUZ (2) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is optional Update your customized copy of job DSNTIJUZ as follows: * Add or update the keyword parameter QUERY_ACCEL_OPTIONS= where is 4 or a list form such as (1,2,3,4) to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If your DSNTIJUZ job does not include QUERY_ACCEL_OPTIONS, that parameter will be set to the default of NONE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (2) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required only if you added or updated the setting for QUERY_ACCEL_OPTIONS in the previous step. If you added or modified the setting for QUERY_ACCEL_OPTIONS, you need to add or update the entry for it in all private copies of your CLIST output DSNTIDxx member. In each such copy, add or update the following line: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value you specified for QUERY_ACCEL_OPTIONS above in DSNTIJUZ. If you do not add QUERY_ACCEL_OPTIONS to a DSNTIDxx member, the DB2 installation CLIST will assume QUERY_ACCEL_OPTIONS=NONE when run with that member as input. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWPZ PM82438 DSNDSPRM PM82438 DSNLDUMP PM82438 DSNLTEX1 PM82438 DSNLTGBK PM82438 DSNLTMIN PM82438 DSNLTSET PM82438 DSNLXRSQ PM82438 1 DSNWDFDI PM82438 DSNWZIFA PM82438 DSNXOD5 PM82438 DSNXOEX1 PM82438 DSNXONZA PM82438 DSNXONZQ PM82438 DSNXONZS PM82438 DSNXOOS1 PM82438 DSNXROHB PM82438 DSNX8API PM82438 DSNX8EKG PM82438 DSNX8INI PM82438 DSNX8STA PM82438 DSN6SPRM PM82438 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM82438 DSNDQWPZ DSNDSPRM DSNLDUMP DSNLTEX1 DSNLTGBK DSNLTMIN DSNLTSET DSNLXRSQ DSNWDFDI DSNWZIFA DSNXOD5 DSNXOEX1 DSNXONZA DSNXONZQ DSNXONZS DSNXOOS1 DSNXROHB DSNX8API DSNX8EKG DSNX8INI DSNX8STA DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLDUMP DSNLTEX1 DSNLTGBK DSNLTMIN DSNLTSET DSNLXRSQ DSNWDFDI DSNWZIFA DSNXOD5 DSNXOEX1 DSNXONZA DSNXONZQ DSNXONZS DSNXOOS1 DSNXROHB DSNX8API DSNX8EKG DSNX8INI DSNX8STA MACROS DSNDQWPZ DSNDSPRM DSN6SPRM LISTEND UK93989 COVER LETTER END UK94011 COVER LETTER START PROBLEM DESCRIPTION(S): PM84869 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of parallel in-list (PLAN_TABLE * * ACCESSTYPE='N' and ACCESS_PGROUP_ID > 0 on * * the same row). * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result set or an ABEND0C4 * * RC38 at location DSNXOLDL offset 0C0C, * * offset 0C10, or offset 0BC6 can be * * returned for a query that includes a * * parallel in-list group with the in-list * * predicate containing a host variable or * * parameter marker if it is executed * * multiple times in a statement cache * * enabled system (CACHEDYN = YES) or in a * * statically bound application. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result set or an ABEND0C4 RC38 (at location DSNXOLDL OFFSET0C0C, OFFSET0C10, or OFFSET0BC6) can be returned for a query that includes a parallel in-list group with the in- list predicate containing a host variable or parameter marker if it is executed multiple times in a statement cache enabled system or in a statically bound application. Once the value of the host variable or parameter marker from the in-list predicate is known at execution time, it should be sorted before the parallel in-list group starts. However, the "sorting" action does not happen before the parallel group starts. Hence, the in-list elements are not in proper sequence. Any residual information from a previous execution can impact the parallel group as to how a 'current un-sorted in-list value' is interpreted causing an incorrect result or abend. The following complex query is an example of such a failing query. Step 1. Define a cursor which contains an INLIST with host variables. EXEC SQL DECLARE CS1 CURSOR FOR SELECT L.C1, COALESCE(I.C2, IP.C2) as C2, L.C4, COALESCE(I.C5, IP.C5) as C5, L.C9 FROM A left outer join M on a.C11=m.C11 left outer join H on a.C11=h.C11 left outer join I on I.C2 = h.C2 left outer join L on L.C1 = coalesce(I.C1, M.C1) left outer join IP on IP.C1 = L.C1 WHERE A.C15 in ('S', 'P' ) 1 AND COALESCE(I.C2, IP.C2) = :HV01 AND A.C11 IN (:HV2, :HV3, :HV4, :HV5, :HV6, :HV7, :HV8, :HV9, :HV10, :HV11, :HV12, :HV13, :HV14) AND ( L.C9 IS NULL OR L.C9 > CURRENT DATE) ORDER BY C4 ASC ; Step 2. Execute the cursor multiple times. DO I = 1 TO 2 WHILE (SQLCODE >= 0); CALL GET_HOST_VAR_VALUE; EXEC SQL OPEN CS1; EXEC SQL FETCH CS1 INTO :HCHAR; EXEC SQL CLOSE CS1; END; DB2 is modified to sort the IN-LIST elements first if it contains a host variable or parameter marker before the parallel group starts. Additional Keywords: SQLIN PARALLELISM SQLPARALLELISM SQLHOSTVAR PARAMETERMARKER SQLMARKER SQLPMK SQLDYNSTMTCACHE SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84869 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM84869: See PM84869 APAR/PTF text for additional information about why a REBIND is necessary. PM84869 corrects a problem of incorrect output or an ABEND at DSNXOLDL OFFSET 0C0C, DSNXOLDL OFFSET 0C10, or DSNXOLDL OFFSET 0BC6 when a query contains a parallel IN-LIST group with a host variable or parameter marker and the IN-LIST predicate runs multiple times in a statement cache enabled system (CACHEDYN = YES) or in a statically bound application. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM80679: See PM80679 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM80679 corrects a problem of an ABEND0C4 at DSNXRIPE +1DF6 may occur when a query contains a VIEW, Table Expression or CTE table in a correlated sub-select runs in parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM63687: See PM63687 APAR/PTF text for additional information about why a REBIND is necessary. PM63687 corrects a problem of ABEND0C4-00000004 in dsnxripe +1DEA when a correlated subquery contains an IN-LIST table ( PLAN_TABLE ACCESSTYPE = 'IN') and the parent query block of the correlated subquery is running in parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGPGR PM84869 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84869 DSNXGPGR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGPGR LISTEND UK94011 COVER LETTER END UK94060 COVER LETTER START PROBLEM DESCRIPTION(S): PM74595 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of data sharing * * that are in ENFM or NFM. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNGEPUF ERQUAL500A * * when a DBD is loaded on one member * * and updated on another. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E in DSNGEPUF:500A RC00C90101 was received when a large DBD was being loaded on one member and being updated on a different member at the same time. The second member could 1 update the DBD before the first member completed the read, which caused the reported abend or other unpredictable results. The code has been updated to insure that a member completes a DBD read before another member can update the DBD. Additional keywords: DB2DSHR SYSPLEXDS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74595 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGECHK PM74595 DSNGEDLC PM74595 DSNICPOS PM74595 DSNICREL PM74595 DSNIDBGA PM74595 DSNITCUS PM74595 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74595 DSNGECHK DSNGEDLC DSNICPOS DSNICREL DSNIDBGA DSNITCUS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGECHK DSNGEDLC DSNICPOS DSNICREL DSNIDBGA DSNITCUS LISTEND UK94060 COVER LETTER END UK94068 COVER LETTER START PROBLEM DESCRIPTION(S): PM83534 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS subsystems running * * the DSNTIJEN job and MODIFY RECOVERY utility * * against directory LOB table space SYSDBDXA. * **************************************************************** * PROBLEM DESCRIPTION: Two problems were reported. * * * * 1 - MODIFY RECOVERY utility issued * * message MSGDSNU573I for new DB2 * * directory table space SYSDBDXA * * and returned RC4. * * * * 2 - DB2 directory table space SYSUTILX * * changes page sizes in V10 during * * the ENFM process (job DSNTIJEN). * * An attempt was made to use the * 1 * RECOVER utility to recover SYSUTILX * * to a point in time that preceded * * the page size change and it failed * * with RC8 along with message * * MSGDSNU1407I. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** Problem 1 - During the DB2 10 for z/OS ENFM process (job DSNTIJEN) the SYSDBDXA table space is created and populated. SYSDBDXA is the LOB table space for DB2 directory table space DSNDB01.DBD01. Some SYSCOPY records for SYSDBDXA were being placed in the SYSCOPY catalog table space when they should have been placed on the DB2 log like we do for the DBD01 directory table space. As a result, the MODIFY RECOVER utility on DSNDB01.SYSDBDXA received message DSNU573I indicating that no backup copies were found for the table space or dataset. This was unexpected. Problem 2 - During the DB2 10 for z/OS ENFM process the SYSUTILX directory table space changes from a 4K page size to a 32K page size. An attempt was made to run the RECOVER utility on DSNDB01.SYSUTILX using an image copy from when SYSUTILX was in a 4K page. That recovery failed (RC=8) because of the change in pagesize. MSGDSNU1407I was displayed to indicate the problem: DSNU1407I DSNUCBMD - MISMATCH BETWEEN THE NUMBER OF PAGES READ=x AND THE NUMBER OF PAGES ORIGINALLY COPIED=y FOR INPUT DATA SET OBJECT NAME TABLESPACE DSNDB01.SYSUTILX Problem 1 - DB2 utility ENFM processing code has been changed so that the SYSDBDXA SYSCOPY records will now be placed on the DB2 log instead of in the SYSCOPY catalog table. as they should be. With this APAR, MODIFY RECOVERY can be used to clean up SYSCOPY table rows for SYSDBDXA. Problem 2 - DB2 utility ENFM processing code has been changed to prevent a point in time recovery of SYSUTILX to a time that precedes the ENFM page size change. To prevent the PIT recovery we will write a SYSCOPY record (ICTYPE = 'W' and STYPE = 'S') to the DB2 log. When this type of SYSCOPY record is encountered we will prevent PIT recoveries to times that precede the timestamps in these records. When a PIT recovery is prevented DB2 utility code will issue 1 MSGDSNU556I (RECOVER CANNOT PROCEED) and the job will complete with RC=8. This APAR code also ensures that we write this same type of SYSCOPY (ICTYPE = 'W' and STYPE = 'S') records for the following directory objects during the ENFM process: - SPT01 - SYSSPUXA - SYSSPUXB - DBD01 (written to DB2 LOG) - SYSDBDXA (written to DB2 LOG) Having these SYSCOPY records will prevent point in time recoveries to times that precede their ENFM changes. ================================================================ ++HOLD for APAR PM83534 ================================================================ This PTF adds a new job step, ENFM0019, to DSNTIJEN, the job for enabling new-function mode (ENFM). The new job step copies the SYSUTILX table space after it has been converted for ENFM. ---------------------------------------------------------------- (1) Update your customized copy of job DSNTIJEN ---------------------------------------------------------------- ==> This action is required for all DB2 10 customers who maintain a customized copy of DSNTIJEN This PTF modifies DSNTIJEN in the SDSNSAMP target library only. After applying this PTF, update your copy of DSNTIJEN as follows: (a) Copy the new job step, ENFM0019, from prefix.SDSNSAMP(DSNTIJEN) into your copy of DSNTIJEN, directly after the ENFM0010 job step. When copying, be sure to include the CHCK0010 check steps that precede and follow job step ENFM0019. (b) In the ENFM0019 PARM string, change 'DSN' to your subsystem name. (c) In the ENFM0019 TEMPLATE statement, change 'DSN!!0' to the prefix you use for DSNTIJEN image copy data sets. Also make other modifications as required, such as for device type, SMS classes, and volume/serial name. Tip: Use the TEMPLATE statement in job step ENFM0027 as a model (d) Save your changes. Do not run DSNTIJEN except for the ENFM process. ---------------------------------------------------------------- (2) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required for all DB2 10 customers This PTF modifies CLIST member DSNTINS3 in the SDSNCLST target library only. 1 You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83534 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ================================================================ ++HOLD for APAR PM83534 ================================================================ This PTF adds a new job step, ENFM0019, to DSNTIJEN, the job for enabling new-function mode (ENFM). The new job step copies the SYSUTILX table space after it has been converted for ENFM. ---------------------------------------------------------------- (1) Update your customized copy of job DSNTIJEN ---------------------------------------------------------------- ==> This action is required for all DB2 10 customers who maintain a customized copy of DSNTIJEN This PTF modifies DSNTIJEN in the SDSNSAMP target library only. After applying this PTF, update your copy of DSNTIJEN as follows: (a) Copy the new job step, ENFM0019, from prefix.SDSNSAMP(DSNTIJEN) into your copy of DSNTIJEN, directly after the ENFM0010 job step. When copying, be sure to include the CHCK0010 check steps that precede and follow job step ENFM0019. (b) In the ENFM0019 PARM string, change 'DSN' to your subsystem name. (c) In the ENFM0019 TEMPLATE statement, change 'DSN!!0' to the prefix you use for DSNTIJEN image copy data sets. Also make other modifications as required, such as for device type, SMS classes, and volume/serial name. Tip: Use the TEMPLATE statement in job step ENFM0027 as a model (d) Save your changes. Do not run DSNTIJEN except for the ENFM process. ---------------------------------------------------------------- (2) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required for all DB2 10 customers This PTF modifies CLIST member DSNTINS3 in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. COMMENTS: 1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTIJEN PM83534 DSNTINS3 PM83534 DSNUBINS PM83534 DSNUCASA PM83534 DSNUECM2 PM83534 DSNULOG1 PM83534 DSNURSWD PM83534 DSNURWT PM83534 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83534 DSNTIJEN DSNTINS3 DSNUBINS DSNUCASA DSNUECM2 DSNULOG1 DSNURSWD DSNURWT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBINS DSNUCASA DSNUECM2 DSNULOG1 DSNURSWD DSNURWT MACROS DSNTIJEN DSNTINS3 LISTEND UK94068 COVER LETTER END UK94121 COVER LETTER START PROBLEM DESCRIPTION(S): PM83838 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: 1. Messages DSNT375I and DSNT376I can * * display incorrect statement type. * * * * 2. An expected ABEND in CSECT DSNTLDEA, * * can lead to subsystem termination. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. DSNT375I and DSNT376I messages that are written to the console may report an incorrect statement type. A static statement can be marked DYNAMIC, and dynamic statement can be marked STATIC. 2. During DEADLOCK processing, an expected abend may occur, and CSECT DSNTLDEA must tolerate that abend by retrying it. There is a timing window when an abend will be percolated to IRLM, causing IRLM to terminate. 1 1. Correctly externalize statement type in DSNT375I and DSNT376I messages. 2. Correct the logic to correctly retry expected abends in CSECT DSNTLDEA. Messages Affected: MSGDSNT375I and MSGDSNT376I COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83838 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTLDEA PM83838 DSNTLSUS PM83838 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83838 DSNTLDEA DSNTLSUS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLDEA DSNTLSUS LISTEND UK94121 COVER LETTER END UK94174 COVER LETTER START PROBLEM DESCRIPTION(S): PM87568 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: Intermittent abend 0C4-00000004 * * EZBRESRV (no dump). This may * * potentially be followed by a binary * * zero overlay of DB2 stack storage * * which may lead to unpredictable * * symptoms including: * * o Abend 0C1-00000001. * * o Abend 04E-00E50053 DSNSVSTK+05D2. * * o DB2 termination with message * * DSNV086E and reason code 00E50727. * **************************************************************** * RECOMMENDATION: * **************************************************************** When initializing the OMVS/USS and TCP/IP communications environment, DB2 (DDF) must invoke the USS BPX4GNI callable service to obtain the domain (host) name. A service name buffer area and its associated length are two other required parameters of this service. DB2 (DDF) is not concerned with obtaining the service name but failed to initialize its service name length parameter value to zero to 1 reflect its disinterest. Depending on the residual contents of this service name length parameter value, an 0C4-00000004 EZBRESRV abend may be detected. This may also cause an overlay of DB2 stack storage, potentially massive, which may lead to unpredictable symptoms that may ultimately result in a termination of DB2. DB2 has been changed to invoke the BPX4GNI callable service with a Service_Buffer_Length parameter value of zero to reflect its disinterest in obtaining the service name. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87568 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLILNR PM87568 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87568 DSNLILNR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLILNR LISTEND UK94174 COVER LETTER END UK94179 COVER LETTER START PROBLEM DESCRIPTION(S): PM85976 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of the * * CURRENT OPTIMIZATION HINT and CURRENT SQLID * * special registers. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC4 at DSNXEBR OFFSET441C * * or an ABEND04E RC00E70005 at location * * DSNXESX4 M999 can occur when executing * * special register statements SET CURRENT * * OPTIMIZATION HINT = '' or SET CURRENT * * SQLID = '' with a UNICODE encoding * * scheme. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC4 at DSNXEBR OFFSET441C or an ABEND04E RC00E70005 at location DSNXESX4 M999 can occur when executing the SET CURRENT OPTIMIZATION HINT = '' or the SET CURRENT SQLID = '' special register statements. These failures can occur from dynamic or static SQL when a UNICODE encoding scheme is employed. 1 The following example illustrates a failing case. SET CURRENT OPTIMIZATION HINT = ''; If this statement is executed from a dynamic java application, the ABEND0C4 at DSNXEBR can occur. If this statement is executed from within a static package bound with the ENCODING(UNICODE) bind option, the ABEND04E at DSNXESX4 can occur. The problem occurs because DB2 doesn't handle the length of the empty string correctly. The code in DB2 is modified to process the length of an empty string properly when used in the CURRENT OPTIMIZATION HINT or the CURRENT SQLID special register statement. Additional Keywords: N/A COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85976 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM85976: See PM85976 APAR/PTF text for additional information about why a REBIND is necessary. PM85976 corrects an ABEND0C4 at DSNXEBR OFFSET 441C or an ABEND04E RC00E70005 at location DSNXESX4 M999 can occur when executing the SET CURRENT OPTIMIZATION HINT = '' or the SET CURRENT SQLID = '' statements. These failures can occur from dynamic or static SQL when a UNICODE encoding scheme is employed. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGRTM PM85976 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85976 DSNXGRTM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGRTM LISTEND UK94179 COVER LETTER END 1UK94239 COVER LETTER START PROBLEM DESCRIPTION(S): PM83853 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of current * * TIMESTAMP with TIME ZONE data in * * an SQLPL Procedure. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result set can be returned * * from an SQLPL Procedure which * * references TIMESTAMP with TIMEZONE * * data. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result set can be returned from an SQLPL Procedure which references TIMESTAMP with TIME ZONE data. The following example illustrates such a failing case. STEP 1. Create an SQLPL Procedure that references TIMESTAMP with TIME ZONE data. CREATE PROCEDURE SC167601.SP_UNTYPEBU2 ( OUT RESULT VARCHAR(32672), OUT P1 INT, OUT P2 CHAR(5), OUT P3 VARCHAR(32672)) BEGIN DECLARE SQLSTATE CHAR(5); DECLARE SQLCODE INT; DECLARE STMT VARCHAR(32672); DECLARE C1 CURSOR FOR STMT1 ; DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN GET DIAGNOSTICS CONDITION 1 P1 = DB2_RETURNED_SQLCODE, P2 = RETURNED_SQLSTATE, P3 = MESSAGE_TEXT; END; SET P3 = ''; SET RESULT = ''; SET STMT = 'SELECT CAST(''9999-12-31 16:59:58.999999999999-07:00'' '|| ' AS TIMESTAMP(12) WITH TIMEZONE) '|| 'FROM SYSIBM.SYSDUMMY1'; PREPARE STMT1 FROM STMT; OPEN C1; FETCH C1 INTO RESULT; 1 CLOSE C1; SET P1 = SQLCODE; SET P2 = SQLSTATE; SET P3 = ''; END! STEP 2. Create a User-Defined Function (UDF) which calls the SQLPL Procedure. CREATE FUNCTION SC167601.UF_CALLSP2() RETURNS VARCHAR(32672) MODIFIES SQL DATA WLM ENVIRONMENT FOR DEBUG MODE WLMENV1 BEGIN DECLARE P1 INT DEFAULT 999; DECLARE P2 CHAR(5) DEFAULT ''; DECLARE P3 VARCHAR(32672) DEFAULT ''; DECLARE CHECK INT; DECLARE RESULT VARCHAR(32672); CALL SC167601.SP_UNTYPEBU2(RESULT, P1, P2, P3); SELECT LENGTH(RESULT) INTO CHECK FROM SYSIBM.SYSDUMMY1; IF CHECK <> 0 THEN RETURN RESULT; ELSE RETURN 'SQLCODE: '||CHAR(P1)||' SQLERR: '||P3; END IF; END! STEP 3. Declare a Temporary Table and import data using the UDF. DECLARE GLOBAL TEMPORARY TABLE TBQATEMP (C1 VARCHAR(32672)); INSERT INTO SESSION.TBQATEMP VALUES ( SC167601.UF_CALLSP2()) STEP 4. Select from the Temporary Table. SELECT * FROM SESSION.TBQATEMP; An incorrect result (of zero) is returned. +------------------------------------------------------------ | +------------------------------------------------------------ | SQLCODE: 0 SQLERR: +------------------------------------------------------------ The correct or expected result to be returned. 1 +------------------------------------------------------------ | +------------------------------------------------------------ | 9999-12-31-16.59.58.999999999999-07:00 +------------------------------------------------------------ The code in DB2 has been modified to return the proper or expected result when referencing TIMESTAMP with TIME ZONE data. Additional Keywords : SQLNATIVESQLPL SQLTIMESTAMPTZ SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83853 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXROHB PM83853 DSNXROHR PM83853 DSNXROHS PM83853 DSNXROH2 PM83853 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83853 DSNXROHB DSNXROHR DSNXROHS DSNXROH2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXROHB DSNXROHR DSNXROHS DSNXROH2 LISTEND UK94239 COVER LETTER END UK94265 COVER LETTER START PROBLEM DESCRIPTION(S): PM78193 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: A DB2 address space received an * * ABEND04E RSN00F3040F because ACEs were * * chained in a loop on a EOT queue. * * This resulted in several CICS ABEND * * U999. * * RC00F3040F RSN00F3040F ABEND999 * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 address space received an ABEND04E RSN00F3040F because 1 ACEs were chained in a loop on a EOT queue. Module DSN3EOT0 has been updated to avoid the ABEND04E RSN00F3040F. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78193 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3EOT0 PM78193 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78193 DSN3EOT0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3EOT0 LISTEND UK94265 COVER LETTER END UK94283 COVER LETTER START PROBLEM DESCRIPTION(S): PM85619 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of SET CURRENT * * PACKAGESET. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 rc38 is incorrectly issued at * * DSNXRIHB OFFSET 01A0 when SET CURRENT * * PACKAGESET is executed with host * * variable as the input. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 rc38 is incorrectly issued at DSNXRIHB OFFSET 01A0 when SET CURRENT PACKAGESET is executed with host variable as the input. The following example illustrates the problem. Write an application SET CURRENT PACKAGESET DCL HCHAR CHAR(100) VARYING; HCHAR = 'TESTPATH'; EXEC SQL SET CURRENT PACKAGESET = :HCHAR; The ABEND0C4 occurs when the SET statement is executed. DB2 code does not handle the internal structure correctly, and it leads to the ABEND. 1 Please note, the following statements will also cause the similar ABEND above. EXEC SQL CONNECT TO STLEC1; EXEC SQL SET CURRENT ENCODING SCHEME = :HV; EXEC SQL SET CURRENT PACKAGE PATH = :HV; DB2 code has been fixed to address this problem. Additional Keywords: ABEND0C4 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85619 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOLTD PM85619 DSNXRBIN PM85619 DSNXRBI9 PM85619 DSNXRDBC PM85619 DSNXRDB9 PM85619 DSNXRIB9 PM85619 DSNXRID9 PM85619 DSNXRIHB PM85619 DSNXRIHD PM85619 DSNXRIHR PM85619 DSNXRIHS PM85619 DSNXRIS9 PM85619 DSNXRSBC PM85619 DSNXRSB9 PM85619 DSNXRTIM PM85619 DSNXRTI9 PM85619 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85619 DSNXOLTD DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 DSNXRSBC DSNXRSB9 DSNXRTIM DSNXRTI9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLTD DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS 1 DSNXRIS9 DSNXRSBC DSNXRSB9 DSNXRTIM DSNXRTI9 LISTEND UK94283 COVER LETTER END UK94308 COVER LETTER START PROBLEM DESCRIPTION(S): PM86393 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA utility on XML data may hang * * when the XML document is big. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running the CHECK DATA Utility on XML data, there is a logic error in extending the storage during processing of some large XML documents. This causes a storage overlay and the CHECK DATA thread to hang. This problem may occur when the size of an XML document is bigger than 10M bytes. The DB2 10 for z/OS code was modified to fix the logic error for processing large XML documents while running the CHECK DATA Utility. Additional keywords: XMLALL DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86393 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOCHX PM86393 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86393 DSNNOCHX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOCHX LISTEND UK94308 COVER LETTER END UK94311 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM84468 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users using indexes. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101,LOC=DSNIDM.DSNICMT2 * * ERQUAL0000 during thread rollback. * **************************************************************** * RECOMMENDATION: * **************************************************************** Index manager allocates index look aside buffer when traversing the index tree. A soft cancel occurred right after the index look aside buffer storage was allocated but before it was initialized. During abort processing, ABEND04E RC00C90101 LOC=DSNIDM.DSNICMT2 ERQUAL0000 occurred when index manager was called to free cached index page using the uninitialized index look aside structure. Index manager code is changed to tolerate the uninitialized index look aside information during thread rollback. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84468 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This fix corrects an SQLCODE20356 error when a TRUNCATE TABLE operation is run on a parent table that is defined with an informational referential constraint by use of the NOT ENFORCED keywords on the references-clause of the CREATE or ALTER TABLE statement. Note that if TRUNCATE TABLE is run on parent tables for which all constraints are informational (NOT ENFORCED), the TRUNCATE will no longer be blocked. Such a condition should have been ignored by TRUNCATE TABLE. Customers making use of TRUNCATE TABLE can verify whether an object has only informational constraints defined by examining the ENFORCED column of the DB2 Catalog table SYSIBM.SYSRELS for the object being truncated. The DB2 Version 10 SQL REFERENCE manual under TRUNCATE statement "NOTES Rules and restrictions" will be changed approximately as follows: "Rules and Restrictions: The truncate operation cannot be executed if the table is a parent table in an enforced referential constraint". COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICLCU PM84468 DSNICMT2 PM84468 DSNICUB PM84468 DSNIDALC PM84468 DSNIRSVP PM84468 DSNISDLE PM84468 DSNISRTI PM84468 1 DSNITCUS PM84468 DSNIXMDE PM84468 DSNKUNR2 PM84468 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84468 DSNICLCU DSNICMT2 DSNICUB DSNIDALC DSNIRSVP DSNISDLE DSNISRTI DSNITCUS DSNIXMDE DSNKUNR2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICLCU DSNICMT2 DSNICUB DSNIDALC DSNIRSVP DSNISDLE DSNISRTI DSNITCUS DSNIXMDE DSNKUNR2 LISTEND UK94311 COVER LETTER END UK94344 COVER LETTER START PROBLEM DESCRIPTION(S): PM85226 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of REORG * * SHRLEVEL CHANGE and REBUILD INDEX SHRLEVEL * * CHANGE in data sharing environment. * **************************************************************** * PROBLEM DESCRIPTION: Following are possible symptoms * * 1.ABEND04E RC00E4D5D2 AT DSNURLAP * * OFFSET3FEC during log apply phase * * 2.Data loss or data corruption after * * REORG or REBUILD INDEX SHRLEVEL CHANGE. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a narrow timing window in the transition state between GBP dependant and non-GBP dependant in a data sharing environment that UPDATE transaction does not generate log records that contain entire data row information. This is only an issue if in this timing window that UPDATE transaction is running with REORG SHRLEVEL CHANGE or REBUILD INDEX SHRLEVEL CHANGE utility concurrently. As a result, if this none full logged update data row record is used during the log applying phase of these utilities, an unforeseeable abend, data loss or data corruption can occur. DB2 code is changed to ensure full logging information updated on the header page is written out to either DASD or group buffer pool. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM85226 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIHPGM PM85226 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85226 DSNIHPGM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIHPGM LISTEND UK94344 COVER LETTER END UK94426 COVER LETTER START PROBLEM DESCRIPTION(S): PM85237 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users utilizing sparse index * * access. * **************************************************************** * PROBLEM DESCRIPTION: Sometimes DB2 may generate the * * following access path: * * * * 1. Sparse index access is used * * on a table, and * * 2. Not all the applicable join * * predicates are used for the * * sparse index access in step 1. * * * * When the conditions above are * * met, incorrect output may occur * * because the join predicates * * described in step 2 may be * * ignored sometimes due to dirty * * storage. * * * * INCORROUT SQLINCORR * * SQLINCORROUT DB2INCORR/K * * SQLSPARSEINDEX SPARSEINDEX * **************************************************************** * RECOMMENDATION: Sometimes DB2 may generate the following * * access path. * * * * 1. Sparse index access is used on a table * * 2. Not all the applicable join predicates * * are used for the sparse index access in * * step 1. * * * * When the conditions above are met, * 1 * incorrectout may occur because the join * * predicates described in step 2 may be * * ignored sometimes due to dirty storage. * * * * For example, * * * * SELECT * * * FROM T1, T2 * * WHERE T1.C1 = T2.C1 AND * * T1.C2 = T2.C2; * * * * * * INCORRECTOUT may occur when the following * * conditions are met. * * 1. Sparse index access is used on the 2nd * * table in the join sequence * * 2. Only one predicate is used for the * * sparse index access. * * * * When the conditions above are met, the * * remaining predicate that is not used in * * step 2 may be ignored by DB2 due to * * dirty storage sometimes. * **************************************************************** Sometimes DB2 may generate the following access path: 1. Sparse index access is used on a table, and 2. Not all the applicable join predicates are used for the sparse index access in step 1. When the conditions above are met, incorrect output may occur because the join predicates described in step 2 may be ignored sometimes due to dirty storage. The incorrect output problem described above is fixed by marking the join predicates that are not used for the sparse index access as stage-2 predicates so that they will not be ignored. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85237 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM85237 APAR/PTF text for additional information about why a REBIND is necessary. PM85237 corrects an incorrect output problem that may occur when (1) sparse index access is used on a table, and (2) not all the eligible join predicates are used for the sparse index key. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. APAR PM75619 corrects two problems. The first problem occurs on both V9 and V10. A query may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. The second problem occurs on V10 only. DB2 may not issue a REORG suggestion as it should. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM63095 corrects a problem of ABEND04E RC00C90101 in DSNIPSFI :5007 when executing an SQL statement containing a User Defined Function (UDF) with the DISALLOW PARALLEL parameter while parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGP PM85237 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85237 DSNXOGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGP LISTEND UK94426 COVER LETTER END UK94460 COVER LETTER START PROBLEM DESCRIPTION(S): PM86225 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * REMOTE BIND/REBIND across different * * subsystem versions. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * ABEND0C4 RC00000010 * * CSECT DSNSVBK OFFSET0E16 * 1 * * * also possible is * * * * Incorrect error messages when * * using a new V10 function on a * * previous version subsystem * * like V9 * * * * PROBLEM SCENARIO: * * * * The reported error occurred when * * attempting a REMOTE BIND from a V10 * * subsystem to a V9 subsystem. An * * overlay can occur causing the said * * abend. * * * * Additionally, an incorrect error * * message can occur when using a new * * V10 bind parameter with a previous * * version subsystem. * * Here is an example: * * * * Binding from a V10 subsystem to a * * V9 subsystem using the 'APCOMPARE' * * parameter might give you an 'invalid * * keyword' error instead of message * * DSNT263I - csect-name bind-type FOR * * object-type = object-name FAILED * * BECAUSE THE bind-type DEPENDS ON * * FUNCTIONS IN A LATER DB2 RELEASE * * WITH MARK release-dependency-mark * * OR HIGHER. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: When executing the BIND from a V10 subsystem, DB2 used storage in a control block that was not a compatible size with the V9 DB2 subsystem and subsequently overlaid other storage causing the abend. Additionally, DB2 could use the wrong message handler when a new bind parameter from V10 is passed to a subsystem on a previous DB2 release. PROBLEM CONCLUSION: DB2 V9 is fixed so that the control block used for the BIND/REBIND is now a compatible size across subsystems. Also, in V10, the error messages have been changed to display the correct message when a new V10 bind parameter is used on a subsystem running a previous release of DB2. ADDITIONAL KEYWORDS: BIND REBIND SQLSTORAGE DB2COEXIST/K DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86225 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This fix should be applied to V10 subsystems to handle the problem where inaccurate error messages could be issued when attempting to use new V10 bind parameters on previous version subsystems. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNECP40 PM86225 DSNECP41 PM86225 DSNECP44 PM86225 DSNECP45 PM86225 DSNECP47 PM86225 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86225 DSNECP40 DSNECP41 DSNECP44 DSNECP45 DSNECP47 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNECP40 DSNECP41 DSNECP44 DSNECP45 DSNECP47 LISTEND UK94460 COVER LETTER END UK94462 COVER LETTER START PROBLEM DESCRIPTION(S): PM87084 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users whose query contains * * ORDER BY and an OMNIFIND function. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may meet incorrect output if the * * query satisfies the following * * conditions: * * * * 1. The query refers to a table with an * * OMNIFIND function. * * 2. The table with OMNIFIND function is * * the leading table with a unique * * index. * * 3. The columns for ORDER BY are from * * this table. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may meet incorrect output when the query with an ORDER BY clause refers to a table with an OMNIFIND function. ADDITIONAL KEYWORDS: 1 SQLORDERBY SQLOMNIFIND SQLINCORROUT SQLINCORR INCORROUT DB2INCORR/K The problems mentioned above are fixed so that DB2 will not meet incorrect output again. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87084 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM87084: See PM87084 APAR/PTF text for additional information about why a REBIND is necessary. PM87084 corrects a problem of incorrect output for a query with an ORDER BY clause that refers to a table with an OMNIFIND function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTS PM87084 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87084 DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTS LISTEND UK94462 COVER LETTER END UK94466 COVER LETTER START PROBLEM DESCRIPTION(S): PM85939 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS or DB2 10 for z/OS users of * * REORG and LOAD RESUME utilities against * * classic partitioned table space with Member * * Cluster, who have applied APAR PM76363 and * * PTF UK90660/UK90661. * **************************************************************** * PROBLEM DESCRIPTION: Following problems could occur during * * or after REORG or LOAD RESUME utility * * when PM76363 has been applied: * * -ABEND04E RC00C90101 DSNIPPS ERQUAL2003 * * -ABEND04E RC00C90101 DSNIBMCL * * ERQUAL500B * * -ABEND04E RC00E20001 DSNIROBD.DSNSVBK * 1 * -Data loss * **************************************************************** * RECOMMENDATION: * **************************************************************** Before PM76363/UK90660(UK90661), LOAD RESUME utility against classic partitioned TS with Member Cluster could fail with abend ABEND04E RC00C90101 at DSNIDLOD ERQUAL500A. This issue only happens when there are zero data pages between the last two space map pages, and data pages covered by the last space map page are empty. PM76363 is to let LOAD RESUME tolerate the zero data pages. After PM76363/UK90660(UK90661) is applied, REORG utility or LOAD RESUME utility against classic partitioned table space with Member Cluster might corrupt system page. As a consequence, later access to down level records could fail with aforementioned abends. For LOAD RESUME utility, data covered by the space map page second to the last one could be overwritten if all data pages covered by the last space map page happen to be empty pages. DB2 code is modified to prevent the system page or data page corruption by REORG or LOAD RESUME utility against classic partitioned table space with Member Cluster. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85939 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDLOD PM85939 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85939 DSNIDLOD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDLOD LISTEND UK94466 COVER LETTER END UK94483 COVER LETTER START PROBLEM DESCRIPTION(S): PM86984 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users using index insert * * I/O parallelism. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90206 DSNIIDIS ERQUAL5002 * * happened during SQL DELETE operation. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 During SQL INSERT execution, index I/O parallelism could be used when there are three or more indexes defined on the table being inserted into. When index insert I/O parallelism is in use, if I/O wait is encountered on the clustering index get page request, index tree traversal will exit early without fully populating the index look aside buffer with correct information. In a very small timing window, the index look aside buffer already contains residual information before the index tree traversal starts. Index insert I/O parallelism will leave residual information in the index look aside buffer after the insert finishes. The subsequent SQL INSERT using the index look aside buffer causes the index key to be inserted into the wrong leaf page. This problem only happens when inserting into the clustering index. Later on, SQL DELETE detects the problem by issuing ABEND04E RC00C90206 DSNIIDIS ERQUAL5002. CHECK INDEX utility can also detect the error if it is run with DIAGNOSE TYPE(70,71). Index needs to be rebuilt to correct the error. DB2 code was modified to make sure there is no residual information left in the index look aside buffer after SQL INSERT when index insert I/O parallelism is in use. Additional keywords: SQLINSERT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86984 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKTRAV PM86984 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86984 DSNKTRAV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKTRAV LISTEND UK94483 COVER LETTER END UK94559 COVER LETTER START PROBLEM DESCRIPTION(S): PM86559 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of input host * * variables with implicit cast in a * * distributed environment. * 1 **************************************************************** * PROBLEM DESCRIPTION: An incorrect value is returned when a * * little endian small or big integer * * input host variable takes part in an * * implicit cast operation to a character * * data type (e.g. CHAR, VARCHAR, GRAPHIC, * * VARGRAPHIC, etc.) on a remote server. * **************************************************************** * RECOMMENDATION: * **************************************************************** The result (value) returned from an implicit cast can be incorrect if and only if the following 3 conditions are true: 1. The input host variable is defined as a small integer or a big integer in little endian format. 2. The host variable is implicitly cast to a character data type (e.g. CHAR, VARCHAR, GRAPHIC, VARGRAPHIC, etc.). 3. The implicit cast is executed at the remote server. The following example illustrates the problem. 1. Create a table with a VARCHAR column on a remote server. CREATE TABLE T1 (C1 VARCHAR(20)); 2. Write a CLI dynamic application and run it against a remote server. # make a connection to remote DB2 server # define a small integer host variable getmem 1 1 SQL_C_SHORT 2 updatemem 1 sql_c_short value 25 # bind the small integer host variable as small integer SQL # type sqlbindparameter 1 1 SQL_PARAM_INPUT SQL_C_SHORT SQL_SMALLINT 0 0 1 sqlprepare 1 "INSERT INTO T1(C1) VALUES( ? )" -3 sqlexecute 1 sqltransact 1 1 sql_commit When the CLI application is passing a small integer value in little endian format to a DB2 for z/OS server, and implicit cast is used to bind in the value, DB2 does not handle the little endian format conversion correctly. Following the operation, the incorrect value can be inserted into C1. Instead, a numeric string of 25 is expected to be inserted into C1. Please note. The incorrect value which can result from the conversion of a little endian format could result in an 1 unexpected SQLCODE433 (SQLCODE -433) being issued. The code in DB2 has been modified to correct the implicit cast problem. Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT SQLCAST SQLCODE433 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86559 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRIHB PM86559 DSNXRIHD PM86559 DSNXRIHR PM86559 DSNXRIHS PM86559 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86559 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS LISTEND UK94559 COVER LETTER END UK94568 COVER LETTER START PROBLEM DESCRIPTION(S): PM88799 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who have * * queries with a LIKE predicate on a * * partitioning column defined as CHAR * * and use REOPT(ALWAYS) * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output can occur for a query * * with a LIKE predicate on a partitioning * * column defined as CHAR when * * REOPT(ALWAYS) is used and page range * * screening is chosen * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output can occur for a query containing a LIKE predicate on a partitioning column defined as CHAR (character data type) when REOPT(ALWAYS) is used and page range screening is chosen (PAGE_RANGE='Y' in the PLAN_TABLE). Also, the LIKE predicate uses a host variable or parameter marker. The data type of the LIKE pattern string can be mistakenly 1 interpreted as CHAR rather than VARCHAR when the column is defined as CHAR. The mismatched data type leads to an incorrect translation of the LIKE pattern string, which can result in the wrong partitions to be qualified for page range screening. Additional Keywords: INCORROUT SQLINCORROUT SQLINCORR DB2INCORR/K PAGERANGE SQLLIKE SQLCHAR SQLREOPT SQLHOSTVAR SQLPMK PARAMETERMARKER SQLPMARKER Code is changed to correct the data type for interpreting LIKE pattern strings in the situation described above, so that the correct partitions can be qualified. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88799 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74543: See PM74543 APAR/PTF text for additional information about why a REBIND is necessary. PM74543 corrects a problem of choosing a poorly performing access path for a partitioned table when queries involve partitioned tables, and EQUAL with host variables or parameter markers, and a DPSI (Data Partitioned Secondary Index). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM74152: A rebind is necessary for static applications to rebuild internal structures used at runtime based on the changes in this APAR. PM74152 corrects a problem in which DB2 may incorrectly return no rows for a query using page range access where a range predicate exists on a partitioning column defined as CHAR(1). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM52548: See PM52548 APAR/PTF text for additional information about why a REBIND is necessary. PM52548 fixes an abend 0C4 RC00000038 DSNISPBM + 1A64 that can 1 occur during query execution for queries containing IS NULL or LIKE predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM38082: See PM38082 APAR/PTF text for additional information about why a REBIND is necessary. PM38082 corrects a query performance problem involving significant loss of page range screening for queries with multi-column partitioning keys and predicates with host variables or parameter markers on those columns. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: See PM25059 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM25059 corrects a problem where the page range reduction is done incorrectly. It may cause DB2 to choose a plan with an extra GROUP BY / ORDER BY sort where it is not needed. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPG1 PM88799 DSNXOPG2 PM88799 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88799 DSNXOPG1 DSNXOPG2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPG1 DSNXOPG2 LISTEND UK94568 COVER LETTER END UK94590 COVER LETTER START PROBLEM DESCRIPTION(S): PM83559 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users of utilities. * **************************************************************** * PROBLEM DESCRIPTION: ABENDU2022 at DXRRL010 OFFSET0FFA and * * ABENDS0071 RC00000030 at IXLR1GLC * * during a QUIESCE utility running on a * * large object list defined by a LISTDEF, * * resulting in ABEND04E RC00E40020. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A QUIESCE ran on a large object list defined by a LISTDEF which contained more than 10000 table spaces. ABENDU2022 at DXRRL010 + x'0FFA' and ABEND0071 RC00000030 at IXLR1GLC occurred during the serialization processing of the QUIESCE utility, resulting in ABEND04E RC00E40020. This problem occurred because a lock used for utility serialization was requested without a hash value, causing IRLM to scan a large resource list and cause the abends. This problem could also occur for any DB2 z/OS utility operating on a large list of objects. Additional Symptom: ABENDS0071 RC00000038/RC00000010 ABEND026 RC0C3E0101 PM83559 is a pre-conditioning APAR that includes changes to support the fix for the reported problem, which will be enabled via another APAR at a later date. Changes in PM83559 should be generally transparent to users. In a data sharing group, the fix for this pre-conditioning APAR must be applied to all members before the later enabling APAR, when available, is applied to any member. The fix for the reported problem will not be effective until it is enabled by the follow-on APAR. Collectively, the APARs change utilities code to obtain the lock(s) used to serialize utilities with an appropriate hash value. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83559 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM MULTSYS: PM83559 is a pre-conditioning APAR that includes changes to support the fix for the reported problem, which will be enabled via another APAR at a later date. Changes in PM83559 should be generally transparent to users. In a data sharing group, the fix for this pre-conditioning APAR must be applied to all members before the later enabling APAR, when available, is applied to any member. The fix for the reported problem will not be effective until it is enabled by the follow-on APAR. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGUOL PM83559 DSNWDFDM PM83559 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM83559 DSNUGUOL DSNWDFDM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGUOL DSNWDFDM LISTEND UK94590 COVER LETTER END UK94618 COVER LETTER START PROBLEM DESCRIPTION(S): PM84501 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using IFCID 361 * * or AUDIT CLASS(11) and PM60855 (UK78544) * * applied. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E20009 at DSNSVSFB+0806 * * occurred while running a QUIESCE * * utility statement longer than 4000 * * bytes with IFCID361 or AUDIT CLASS(11) * * trace started. * **************************************************************** * RECOMMENDATION: * **************************************************************** With PM60855 (UK78544) applied, during execution of QUIESCE utility, when IFCID361 trace is turned on, an abend ABEND04E RC00E20009 at DSNXA02 .DSNSVSFB+0806 occurred while writing the trace record. The abend occurred because of invalid length being passed to storage manager to obtain storage for writing the trace record. The above issue can also result in an abend ABEND04E with RC00E2000F reason code. It can occur during any utility execution where utility statement is longer than 4000 bytes and IFCID361 or AUDIT CLASS(11) is turned on. DB2 code has been changed to pass the length correctly during IFCID361 trace record processing for utilities. Additional keywords: OFFSET0806 IFCID361 AUDTPLCY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84501 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXA02 PM84501 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84501 DSNXA02 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXA02 LISTEND UK94618 COVER LETTER END UK94648 COVER LETTER START PROBLEM DESCRIPTION(S): PM85052 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E50097 may occur in * * CSECT DSNB5RAP after an agent is * * cancelled during agent allocation * * while suspended in buffer manager. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an agent is cancelled during allocation while suspended in buffer manager and does not drive a Unit of Recovery, recovery actions for buffer manager do not resume the suspended agent correctly. Agent deallocation has been modified to drive buffer manager clean up if the agent was active in buffer manager when it was cancelled. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85052 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTADL PM85052 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85052 DSNTADL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTADL LISTEND UK94648 COVER LETTER END UK94661 COVER LETTER START PROBLEM DESCRIPTION(S): PM88765 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using indexes * * created on varying length graphic columns * 1 * (VARGRAPHIC) * **************************************************************** * PROBLEM DESCRIPTION: SQLINCORROUT occurred for query using * * index access path with index defined on * * varying length graphic columns * * (VARGRAPHIC) * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLINCORROUT occurred for query using index access path with index defined on varying length graphic columns (VARGRAPHIC). Key comparison routine failed to compare remainder of key with the padding character(s). An incorrect displacement was used causing the key to be rejected from the result set. Following are two examples that produce incorrect results: PADDED INDEX: CREATE TABLE T1 (C1 VARGRAPHIC(255) NOT NULL, C2 CHAR(10) WITH DEFAULT NULL) CCSID UNICODE; CREATE INDEX IX1 ON T1 (C2,C1) PADDED; INSERT INTO T1 (C1) VALUES ('DB2'); COMMIT; SELECT COUNT(*) FROM T1 WHERE C1 = 'DB2'; -- expect value of 1. NOT PADDED INDEX: CREATE TABLE T1 (C1 VARGRAPHIC(255) NOT NULL, C2 CHAR(10) WITH DEFAULT NULL) CCSID UNICODE; CREATE INDEX IX1 ON T1 (C2,C1) NOT PADDED; INSERT INTO T1 (C1) VALUES ('DB2'||REPEAT(' ', 200)); COMMIT; SELECT COUNT(*) FROM T1 WHERE C1 = 'DB2'; -- expect value of 1. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLINDEX DB2 has been modified to correctly compare varying length graphic keys with padding character(s). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88765 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKFNCS PM88765 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM88765 DSNKFNCS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKFNCS LISTEND UK94661 COVER LETTER END UK94695 COVER LETTER START PROBLEM DESCRIPTION(S): PM84536 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL * * statement containing multiple set operators * * (SETOPs). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E72018 at location * * DSNXGRDS.DSNXSINE: 1342 may occur when * * an SQL statement satisfies all of the * * following conditions: * * 1. a table expression or VIEW (VW#1) * * is defined with multiple SETOPs; * * 2. another table expression or VIEW * * referenced in VW#1 is also defined * * with multiple SETOPs. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following example helps to illustrate the problem: DDL: CREATE TABLE T1(C1 CHAR(1), C2 VARCHAR(1), C3 INT); CREATE TABLE T2(C1 CHAR(1), C2 VARCHAR(1), C3 INT); INSERT INTO T1 VALUES('A', 'B', 12); INSERT INTO T2 VALUES('A', 'B', 12); CREATE VIEW V1(C11, C2, C3) AS SELECT C1, C2, C3 FROM T1 UNION ALL SELECT C1, C2, C3 FROM T2; SQL: SELECT DISTINCT 1 FROM (SELECT '' AS C11, C2, RAND() FROM T1 UNION SELECT C1 AS C11, C2, RAND() FROM T2 UNION SELECT C11, C2, C3 FROM V1 UNION ALL SELECT C1 AS C11, C2, C3 FROM T1 UNION ALL SELECT '' AS C11, C2, C3 FROM T2 ) AS TX ; 1 DB2 didn't transform SQL statement by UNION distribution correctly and caused ABEND. DB2 has been modified correctly to handle the ABEND in aformentioned SQL statement. Keyword: SQLUNION SQLUNIONALL SQLVIEW SQLTABLEEXPR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84536 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM84536: See PM84536 APAR/PTF text for additional information about why a REBIND is necessary. PM84536 corrects a problem of ABEND04E RC00E72018 at location DSNXGRDS.DSNXSINE: 1342 when an SQL statement satisfies all of the following conditions: 1. a table expression or VIEW (VW#1) is defined with multiple SETOPs; 2. another table expression or VIEW referenced in VW#1 is also defined with multiple SETOPs. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODSO PM84536 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84536 DSNXODSO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODSO LISTEND UK94695 COVER LETTER END UK94697 COVER LETTER START PROBLEM DESCRIPTION(S): PM86838 - **************************************************************** * USERS AFFECTED: All LOB table space of DB2 for z/OS V10 * * with GBPCHCHE SYSTEM * **************************************************************** * PROBLEM DESCRIPTION: Various 00C90101 abends may occur * * on a LOB table space running under * * Data Sharing using GBPCAHE SYSTEM. * 1 * Possible abends are: * * * * RC00C90101 DSNODAL1:5003 * * RC00C90101 DSNOALLO:5022 * * RC00C90101 DSNODEAL:501C * **************************************************************** * RECOMMENDATION: * **************************************************************** When inserting LOB data bigger than 2M in size, DB2 may determine to process the entire data with a smaller subset of it. In this situation, the LOB map page is being updated several time until the entire LOB data is inserted. The LOB map page should be always processed as a non-system page, but repeated updates against the same LOB map page, could result in it being processed as either a system page or non-system when GBPCACHE is set to SYSTEM. Therefore, the final LOB map page written to DASD could be down level. As a result, the query UR that selects this LOB object after it has been inserted, could possibly get a down level LOB map page and thus cause data corruption. DB2 code is modified to ensure a LOB map page is always processed as a non-system page. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM86838 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOFLMP PM86838 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM86838 DSNOFLMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOFLMP LISTEND UK94697 COVER LETTER END UK94713 COVER LETTER START PROBLEM DESCRIPTION(S): PM74267 - **************************************************************** * USERS AFFECTED: All Users of DB2 * **************************************************************** * PROBLEM DESCRIPTION: ENABLE FAST LOG APPLY IN ALL CASES * * DURING DB2 RESTART. * **************************************************************** * RECOMMENDATION: * **************************************************************** Today, Fast Log Apply (FLA) is not always enable during DB2 restart. This is because, unlike, DB2 main-line data recovery 1 which enables FLA based on either external ZPARM (DB2 V9) setting or internal zparm setting (DB2 V10), restart is using work load manager token to enable FLA function. However, the work load manager connection token (ASCECTKN) being used is always zero since the connection token was not calculated correctly. The Data Manager restart logic is changed so that the determination of enabling FLA will not depend on work load manager being initialized. FLA will be always active during restart. This should help improve the over all performance of DB2 restart. DB2 restart logic is changed so that it will always used FLA during the forward log recovery phase. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74267 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIARPL PM74267 DSNIECUR PM74267 DSNIFLAA PM74267 DSNIFLAR PM74267 DSNILHIS PM74267 DSNILOGA PM74267 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74267 DSNIARPL DSNIECUR DSNIFLAA DSNIFLAR DSNILHIS DSNILOGA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIARPL DSNIECUR DSNIFLAA DSNIFLAR DSNILHIS DSNILOGA LISTEND UK94713 COVER LETTER END UK94729 COVER LETTER START PROBLEM DESCRIPTION(S): PM85433 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML * * publishing function. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 LOC=DSNNXML.DSNNOSCO+C2A2 and * * DB2 termination may occur when the XML * * publishing function is processing a * * zero length LOB data. * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** ABEND0C4 LOC=DSNNXML.DSNNOSCO+C2A2 and DB2 termination may occur when the XML publishing function is processing a zero length LOB data. For example: Following statements will create two tables, T1 and T2. CREATE TABLE T1 (C1 CHAR(10)); CREATE TABLE T2 (X1 XML); Following INSERT statements insert some data into the tables. INSERT INTO T1 VALUES('DATA1'); INSERT INTO T1 VALUES('DATA2'); INSERT INTO T2 VALUES ('35'); In the following query, the XMLSERIALIZE function will return zero length LOB data. SELECT XMLDOCUMENT( XMLELEMENT(NAME "E1", XMLELEMENT(NAME "E2", STRIP(T1.C1)), XMLSERIALIZE( XMLQUERY('$doc/x' PASSING T2.X1 AS "doc") AS CLOB) ) ) FROM T1, T2; When DB2 is processing the query, the ABEND0C4 LOC=DSNNXML. DSNNOSCO+C2A2 and DB2 termination may occur. DB2 is modified to process the zero length LOB data correctly. Additional keywords: SQLXML XMLALL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85433 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOBSC PM85433 DSNNOCCN PM85433 DSNNOSCO PM85433 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85433 DSNNOBSC DSNNOCCN DSNNOSCO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOBSC DSNNOCCN DSNNOSCO 1 LISTEND UK94729 COVER LETTER END UK94765 COVER LETTER START PROBLEM DESCRIPTION(S): PM83933 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of ALTER TABLE * * ALTER COLUMN SET DATA TYPE when the data * * type of the specified column is TIMESTAMP * * and the column is part of the partitioning * * key. * **************************************************************** * PROBLEM DESCRIPTION: SYSIBM.SYSINDEXPART field, LIMITKEY, * * may contain incorrect values as a * * result of a TIMESTAMP column alter- * * ation. * **************************************************************** * RECOMMENDATION: * **************************************************************** The internal limit key value may be stored incorrectly as a result of a TIMESTAMP column alteration when the column is part of the partitioning key. The internal limit key value is stored in SYSINDEXPART.LIMITKEY for index-controlled partitioning and SYSTABLEPART.LIMITKEY_INTERNAL for table-controlled partitioning. This may result in limit keys that are out of order, or if the partitioning key consists of only TIMESTAMP columns which have been altered, then all partitions wil have the same incorrect limit key values. Incorrect output, data loss, or other unexpected results may occur on subsequent operations on the table. For example, SELECT may fail to retrieve all rows. DELETE, and UPDATE may fail to find rows to delete or update respectively. Additionally, data loss may occur when REORG is run while the limit key values are incorrect if there is data that is greater than the last partitioning key. DB2 has been modified to correctly update SYSINDEXPART.LIMITKEY and SYSTABLEPART.LIMITKEY_INTERNAL when altering a TIMESTAMP column that is part of the limit key. This apar does not fix existing incorrect SYSINDEXPART.LIMITKEY or SYSTABLEPART.LIMITKEY_INTERNAL values. Additionally, this does not restore lost data. To fix affected tables, alter the limit keys to the desired values followed by REORG. ADDITIONAL KEYWORDS: SQLALTER DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT 1 SQLTIMESTAMP SQLALTER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM83933 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXISB5 PM83933 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM83933 DSNXISB5 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXISB5 LISTEND UK94765 COVER LETTER END UK94814 COVER LETTER START PROBLEM DESCRIPTION(S): PM87677 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of DBCLOB Large * * Objects in a distributed environment with * * progressive streaming option. * **************************************************************** * PROBLEM DESCRIPTION: When running DB2 applications in a * * distributed environment with the * * progressive streaming option, DB2 can * * return an incorrect result for queries * * that contain a nested loop join with an * * outer table containing a DBCLOB column. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running DB2 applications in a distributed environment with the progressive streaming option, DB2 can return an incorrect result for queries that involve a nested loop join if the outer table contains a DBCLOB column. The incorrect result occurs because DB2 inadvertently modifies an internal persistent length field for generating the character length. In fact, DB2 should perform this calculation for character length in a separate local variable. The following JAVA snippet serves as an example which might generate an incorrect result. Step 1. Define two tables, one which contains a DBCLOB column. CREATE DATABASE MYDBASE CCSID UNICODE; 1 CREATE TABLE Primary(id integer NOT NULL, short_string vargraphic(16) , long_string dbclob(16)) IN DATABASE MYDBASE; CREATE TABLE Secondary(parent_id integer NOT NULL , ordinal integer NOT NULL ) IN DATABASE MYDBASE; Step 2. Insert data into the two tables. INSERT INTO Primary(id, short_string, long_string) VALUES(1, 'short string a', 'long string a'); INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 1); INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 2); INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 3); INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 4); Step 3. Perform a query containing an inner join with the progressive streaming option enabled. try { String sql="SELECT id, ordinal, short_string,long_string "+ "FROM Primary p INNER JOIN Secondary s " + "ON p.id = s.parent_id;"; stmt = con.prepareStatement(sql); stmt.execute(); ResultSet rs = stmt.executeQuery(); while (rs.next()) { System.out.println(rs.getInt(1) + "," + rs.getInt(2)+","+ rs.getString(3) + "," + rs.getString(4)); } rs.close(); con.commit(); } catch (SQLException e) { System.out.println("**SQLException in CALL simple proc!"+e); System.out.println("***SQLCODE = " + e.getErrorCode()); System.out.println("***SQLSTATE = " + e.getSQLState()); System.out.println("***Text of Error Message = " + e.getMessage()); } The code in DB2 has been modified to prevent returning an incorrect result for the case described. Additional Keywords: SQLLOB SQLDDF SQLNLJ SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87677 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOLMAT PM87677 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87677 DSNOLMAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOLMAT LISTEND UK94814 COVER LETTER END UK94845 COVER LETTER START PROBLEM DESCRIPTION(S): PM84153 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users whose queries utilize * * table expressions. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may occur if an ORDER * * BY expression with DESC is specified * * inside a table expression and the * * table expression is materialized for * * merge scan join. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the query specifies an ORDER BY expression with DESC inside a table expression and the table expression is materialized for merge scan join, incorrect output may occur. For example, incorrect output may occur for the following query if the table expression T3 is materialized and merge scan joins to table T4: SELECT T3.C1, T4.C1 FROM (SELECT C1||' ' FROM ((SELECT T1.C1||' ' FROM T1 ) UNION ALL (SELECT T11.C1||' ' FROM T11 ) ) AS T2(C1) ORDER BY C1||' ' DESC GROUP BY C1||' ' )AS T3(C1), T4 WHERE T3.C1 = T4.C1 1 GROUP BY T3.C1, T4.C1; Additional Keywords: SQLTABLEEXPR SQLORDERBY SQLACCESSPATH SQLPERFORMANCE SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLSMJ SQLMSJ SMJ MSJ Code is changed to correct the incorrect output problem for the situation described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84153 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM84153: See PM84153 APAR/PTF text for additional information about why a REBIND is necessary. PM84153 corrects a problem that incorrect output may occur if an ORDER BY expression with DESC is specified in a table expression and the table expression is materialized for merge scan join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPCO PM84153 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84153 DSNXOPCO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPCO LISTEND UK94845 COVER LETTER END UK94861 COVER LETTER START PROBLEM DESCRIPTION(S): PM88703 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the RANK and * * DENSE_RANK window functions in the OLAP * * specification. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * an SQL statement that contains the * 1 * RANK and DENSE_RANK window functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** The RANK and DENSE_RANK window functions can return an incorrect result set when the argument contains a padded string. The following simple example illustrates a failing case. Step 1. Create Table T1 and insert three rows. CREATE TABLE T1(C_CHA CHAR(2), C_VARC VARCHAR(2)); INSERT INTO T1 VALUES('A','AA'); INSERT INTO T1 VALUES('A','AA'); INSERT INTO T1 VALUES('AA','A'); Step 2. Select from Table T1 using the RANK and DENSE_RANK OLAP functions. SELECT C_CHA AS OBY, C_VARC||C_CHA AS PBY, RANK() OVER( PARTITION BY C_VARC||C_CHA ORDER BY C_CHA ) AS RANK1, DENSE_RANK() OVER( PARTITION BY C_VARC||C_CHA ORDER BY C_CHA ) AS DENSE_RANK1 FROM T1; Step 3. Check the results. The following incorrect result is returned. The 3rd row is not as expected. The RANK1 and DENSE_RANK1 values for the 3rd row should be 3 and 2. +-------------------------------------------------- | OBY | PBY | RANK1 | DENSE_RANK1 | +-------------------------------------------------- 1_| A | AAA | 1 | 1 | 2_| A | AAA | 1 | 1 | 3_| AA | AAA | 1 | 1 | +-------------------------------------------------- This problem occurs because DB2 doesn't handle the padding character properly for the input argument to the RANK and DENSE_RANK window functions. DB2 code is modified to use correct padding character for the argument for RANK and DENSE_RANK window functions. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLRANK SQLDENSERANK 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88703 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRWND PM88703 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88703 DSNXRWND THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRWND LISTEND UK94861 COVER LETTER END UK94868 COVER LETTER START PROBLEM DESCRIPTION(S): PM84206 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: After canceling a job which updates a * * GBP-dependent LOB space, a page of the * * LOB may be put into LPL by DSNB5SCM. * * The page later gets put into the write * * error page range (WEPR), so LPL * * recovery cannot repair it. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an application is canceled while updating a GBP-dependent LOB page, and the LOB page is marked "broken", the begin-abort processing will schedule online page recovery asynchronously. This process will have to wait for the application to commit since it requires a drain. Meanwhile, the application's commit processing cannot write the broken page and puts it into LPL. Then the online recovery gets control, but cannot recover the page since it is now in LPL. So the failed recovery puts it into the write error page range, which requires the RECOVER utility to fix it. The begin-abort processing for a broken LOB page has been modified to perform the online recovery synchronously, as is done for non-LOB objects. This will prevent having the broken page put into LPL and WEPR. The online recovery logic has been modified to handle LOB objects correctly for the synchronous case (needs to preserve the invoker's write intent). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM84206 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CFC PM84206 DSNB1RTR PM84206 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM84206 DSNB1CFC DSNB1RTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CFC DSNB1RTR LISTEND UK94868 COVER LETTER END UK94997 COVER LETTER START PROBLEM DESCRIPTION(S): PM88442 - **************************************************************** * USERS AFFECTED: All DB2 10 (CM or NFM) for z/OS users of * * SQL UPDATE of parent key in a referential * * integrity (RI) relationship * **************************************************************** * PROBLEM DESCRIPTION: After applying APAR PM62834 (UK90995), * * SQLCODE531 -531 issued on SQL UPDATE of * * parent key in referential integrity * * relationship, even though all rows in * * dependent table still had valid parent * * rows in parent table * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying APAR PM62834/PTF UK90995 in DB2 10 CM or NFM, when a single SQL UPDATE statement updated several parent keys, if the parent key values being updated had any dependent rows in a dependent table, SQLCODE -531 was issued even when by the end of the SQL UPDATE the parent keys were still present. Example: ---------------------------------------------------------------- CREATE TABLE PARENT_TB ( C1 CHAR(10) NOT NULL, PRIMARY KEY (C1) ) CREATE UNIQUE INDEX PARENT_IX ON PARENT_TB (C1) INSERT INTO PARENT_TB (C1) VALUES ('1') INSERT INTO PARENT_TB (C1) VALUES ('2') 1 CREATE TABLE DEPENDENT_TB ( C1 CHAR(10) NOT NULL, FOREIGN KEY REL01 (C1) REFERENCES PARENT_TB ON DELETE CASCADE ) INSERT INTO DEPENDENT_TB (C1) VALUES ('1') INSERT INTO DEPENDENT_TB (C1) VALUES ('2') UPDATE PARENT_TB SET C1 = ( CASE C1 WHEN '1' THEN '2' WHEN '2' THEN '1' ELSE C1 END ) WHERE C1 IN ('1', '2') This SQL UPDATE failed with SQLCODE -531 when it should have been successful (by the end of the update, the parent key values being updated were still present). ---------------------------------------------------------------- It should be noted that even though the bad APAR PM62834 was documenting a fix for DB2 10 NFM's INCLUDE column index function, the scenario that exposes the APAR need not be related to that function at all and can happen in DB2 10 CM as well. The root cause of this problem is an incorrect assumption in the DB2 deferred key processing code, which bypassed the checking of parent key index that finds out if the pre-update parent key values are still present in the parent table. The incorrect code proceeded to check for dependents as if the pre-update parent key values were no longer present. Code has been changed to properly check for the presence of old parent keys during SQL UPDATE with referential integrity implications. Additional keywords: SQLUPDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88442 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRICH PM88442 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88442 DSNIRICH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNIRICH LISTEND UK94997 COVER LETTER END UK95006 COVER LETTER START PROBLEM DESCRIPTION(S): PM87388 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of SCA rebuild * * and partitioned table spaces that have over * * 64 partitions created, including data * * partitioned secondary indexes (DPSI) and * * nonpartitioned secondary indexes (NPSI) on * * such table spaces * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBMF ERQUAL5321 * * ABEND04E RC00C90101 DSNIDBMF ERQUAL5320 * * ABEND04E RC00C90101 DSNIDBDF ERQUAL5321 * * or similar abends may occur soon after * * DB2 restart (bringing member down), * * when the system has recently gone * * through SCA rebuild * **************************************************************** * RECOMMENDATION: * **************************************************************** The aforementioned DBET-related abends may occur in data sharing at some point after restart, under the following conditions: - A partitioned object exists with over 64 created partitions (could be a DPSI or NPSI index as well). - The object was processed during backward log recovery in a prior restart (e.g. a crashed utility on the object was being backed out during that phase) and at least one data sharing member was already up while this backout was being performed. - Later on, SCA rebuild took place, for example: SETXCF START, REBUILD,STRNM=DSNCAT_SCA. - Now a restart takes place, followed by one of the mentioned abends after the restart, bringing the member back down. The abend after restart need not be immediately after restart. Instead, the abend could occur whenever the object happens to be the target of an exception state change (e.g. issuing the -STOP DATABASE SPACENAM command against it, or running another utility against it). More specifically, during the backward recovery phase, the member was creating a non-collapsed internal DBET structure for the object, while members that were up were receiving notifies and building a collapsed DBET structure. This is normal, however if a SCA rebuild was issued later on, if the member with the non-collapsed DBET structure was processed last by the SCA rebuild, an orphan DBET SCA record was produced, which during 1 a subsequent restart helped build a structurally incorrect DBET entry (resulting in abend at some point after restart, which brought the member down). Until this fix is applied, the only known bypass to this problem would be to perform group restart, which will rebuild the group DBET in SCA from the logs. DB2 restart processing has been modified to detect orphaned group DBET records in SCA and erase these orphans. This cleaned up SCA-record set will then be used by DB2 to correctly build the local DBET structure for the object. Additional keywords: DB2DSHR SYSPLEXDS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87388 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBGC PM87388 DSNIDBGN PM87388 DSNIDBNI PM87388 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87388 DSNIDBGC DSNIDBGN DSNIDBNI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBGC DSNIDBGN DSNIDBNI LISTEND UK95006 COVER LETTER END UK95009 COVER LETTER START PROBLEM DESCRIPTION(S): PM88519 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNKINSL:5004 * * for duplicate key found during DB2 log * * apply. MSGDSNB250E for LPL may appear * * for LOGAPPLY. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** ABEND04E RC00C90101 may be issued during DB2 log apply process. This may happen in certain timing window where an Inserter is able to update using the same key that was deleted by the Deleter while the Deleter has not committed yet. If the Deleter 1 rolls back, it may get the duplicate key error and abend. Insert/update from another member should not happen until the Deleter commits the delete. There is a timing error where Inserter asking for an S lock request with pseudo delete check, will not know that a Deleter exists in the group, because the pseudo-delete feedback (RLPRCB10) is not always correctly set by IRLM when the lock request completes and returns to the caller. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR closes a timing window where pseudo-deleter feedback was not set by IRLM/XES Contention Exit code when there was a request from another member for the same lock, already waiting in the contention exit. IRLM will set RLPRCB10 correctly upon return to the lock requester/Inserter member to inform about a Deleter in the group. The Inserter will wait for the Deleter side to commit first, instead of going ahead itself with updates. Note PM80714 fixes a another timing exposure where there was an earlier waiting request for the same lock on the Inserter side. Please apply both apars(PM80714 & PM88519) to avoid the problem. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM88519 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL7B1 PM88519 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88519 DXRRL7B1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL7B1 LISTEND UK95009 COVER LETTER END UK95038 COVER LETTER START PROBLEM DESCRIPTION(S): PM89692 - **************************************************************** * USERS AFFECTED: All users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00D92023 in DSNRPLCS * * during DB2 restart. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 A POSTPONED ABORT unit of recovery (UR) for a thread that owned the only UR in a global transaction completed the backout process and an END-UNDO log record was written by DSNRPBUP to complete the UR. DSNRPBUP then attempted to remove the GXID for the global transaction from the GXID table without holding the correct latch to serialize the hash anchor chains. This resulted in the GXID block being left on the GXID chain without any URs. The global transaction information for the orphaned GXID was written to the log during the subsequent checkpoints. The next restart then failed with an ABEND04E RC00D92023 in DSNRPLCS as no URs were found for the checkpointed global transaction. A conditional restart specifying a CHKPTRBA prior to the END-UNDO log record RBA was required to restart DB2. DSNRPBUP has been changed to obtain the GXID latch when removing a completed GXID block from the GXID table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM89692 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRPBUP PM89692 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM89692 DSNRPBUP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRPBUP LISTEND UK95038 COVER LETTER END UK95206 COVER LETTER START PROBLEM DESCRIPTION(S): PM74874 - **************************************************************** * USERS AFFECTED: All DB2 10 z/OS users of Partition By * * Growth table spaces with and without * * MEMBER CLUSTER. * **************************************************************** * PROBLEM DESCRIPTION: When using PBG table spaces it is * * possible to see only the first page * * in a segment being used before going * * to another new segment. This caused * * rapid growth of the table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the non MEMBER CLUSTER case a small timing window could cause getting a new segment to occur multiple times consecutively, which would result in just the first page of the new segment to 1 be used. This would then leave the rest of the segment empty. In the MEMBER CLUSTER case, during an UPDATE operation if there was no room for the newly updated record in its current partition, it would then search the first Space Map page of the next partition before it asked for a new segment. When multiple updates occur at the same time, each update would ask for a new segment resulting in only the 1st page of each segment being used. In the non MEMBER CLUSTER case the timing window has been shortened so that this scenario is less likely to occur. In the MEMBER CLUSTER case after searching the 1st Space Map page we will search the last segment before asking for a new segment. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74874 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISGNS PM74874 DSNISGSC PM74874 DSNISUPI PM74874 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74874 DSNISGNS DSNISGSC DSNISUPI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGNS DSNISGSC DSNISUPI LISTEND UK95206 COVER LETTER END UK95210 COVER LETTER START PROBLEM DESCRIPTION(S): PM87166 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * constant <> constant predicates * * with PM80911 applied * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may occur with * * UK92607 (V10) or UK92608 (V9). * * The non correlated SQL * * statement that uses constant <> * * constant predicate where the * * constants are integer, bigint or * * binary and the length of the * * constants are different may * 1 * receive incorrect output. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output may occur with UK92607 (V10) or UK92608 (V9). The non correlated SQL statement that uses constant <> constant predicate where the constants are integer, bigint or binary and the length of the constants are different may receive incorrect output. For Example, SELECT 1 FROM SYSIBM.SYSDUMMY1 WHERE 1 <> 10; DB2 was fixed to process the statement that contains a constant <> constant predicate where the length of the constants are different correctly. Additional Keywords: SQLPRUNE SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87166 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM87166: See PM87166 APAR/PTF text for additional information about why a REBIND is necessary. PM87166 corrects a problem of Incorrect output may occur with UK92607 (V10) or UK92608 (V9). The non correlated SQL statement that uses constant <> constant predicate where the constants are integer, bigint or binary and the length of the constants are different may receive incorrect output. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM80911: See PM80911 APAR/PTF text for additional information about why a REBIND is necessary. PM80911 enhances the performance of a non correlated SQL statements with predicates involving constant comparisons. The performance of a non correlated SELECT statement can be improved if it has a predicate that always evaluates to false because it is a not equal comparison between two constants that have the same values. The query can be executed 1 without accessing the tables in the FROM clause because the predicate is always evaluated to false To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM76608: See PM76608 APAR/PTF text for additional information about why a REBIND is necessary. PM76608 corrects a problem that incorrect output could happen for an SQL statement that contains FETCH FIRST n ROWS ONLY in a table expression, on which there is a predicate. The access path of the SQL statement maybe changed after applying PM76608, as predicates will not be push down to the table expression that contains FETCH FIRST n ROWS ONLY. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPRU PM87166 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87166 DSNXOPRU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRU LISTEND UK95210 COVER LETTER END UK95240 COVER LETTER START PROBLEM DESCRIPTION(S): PM90486 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: AE PM85944 FIX COMPLETION * **************************************************************** * RECOMMENDATION: * **************************************************************** AE PM85944 FIX COMPLETION AE PM85944 FIX COMPLETION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM90486 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1DVP PM90486 DSNB1FBS PM90486 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM90486 DSNB1DVP DSNB1FBS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1ABS DSNB1CPS DSNB1DVP DSNB1FBS DSNB1PMT LISTEND UK95240 COVER LETTER END UK95271 COVER LETTER START PROBLEM DESCRIPTION(S): PM87560 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND026 in IXLE1CRW after a buffer * * pool has had its VPSIZE reduced, either * * due to the buffer pool having the * * AUTOSIZE attribute set to YES, or by * * use of the -ALT BPOOL VPSIZE command. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a buffer pool has its size reduced, and it is connected to the Group Buffer Pool, DB2 may reduce the size of the pool's Local Valid Bit Vector to reflect the new highest used slot number. However, the pool contraction logic may fail to deregister pages using higher slot numbers. If that happens, and a later cross-invalidation request is sent for one of those still-registered pages, an ABEND026 in IXLE1CRW may occur due to the use of an invalid vector index. The buffer pool contraction logic has been modified to ensure that pages being contracted out of the pool are properly deregistered. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM87560 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNB1CBP PM87560 DSNB1FBS PM87560 DSNB1REL PM87560 DSNB1RWI PM87560 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM87560 DSNB1CBP DSNB1FBS DSNB1REL DSNB1RWI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CBP DSNB1FBS DSNB1REL DSNB1RWI LISTEND UK95271 COVER LETTER END UK95295 COVER LETTER START PROBLEM DESCRIPTION(S): PM88758 - **************************************************************** * USERS AFFECTED: DB2 V9 data sharing users with UK82634 * * applied. * * DB2 V10 data sharing users with UK82633 * * or UK93475 applied. * **************************************************************** * PROBLEM DESCRIPTION: Castout I/O errors, as shown by message * * MSGDSNB225I with CSECT name DSNB5PCO * * and MM error code 00140408, along with * * ABEND04E RC00C200A4 in DSNB5PCO. * * * * Various symptoms of regressed pages, * * including: * * - Incorrect output, INCORROUT. * * - ABEND04E RC00C90101, RC00C90102, * * RC00C90105, or RC00C902xx in * * various CSECTs. * * - Data/index inconsistencies reported * * by the CHECK INDEX utility. * * - Page regression reported by the * * DSN1LOGP utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** For both DB2 V9 and DB2 V10, the process of purging pages from the group buffer pool after an object has become non-GBP- dependent does not correctly detect the "changed page found" condition which may arise when the GBP is allocated in a CFLEVEL 17 coupling facility. If this happens, DB2 leaves changed pages in the GBP, which may be encountered again when the object once more becomes GBP-dependent. This can result in page regression problems if those pages are no longer current, or in castout I/O errors if those pages no longer exist on DASD. 1 For DB2 V9, there are a couple of conditions in which a page is not properly registered when a buffer pool scan is performed in response to a change in the object's P-lock state. This can result in a down-level page being assumed to be current. The code which deletes pages from the GBP has been modified to correctly detect the "change page encountered" situation (by checking only the significant bytes of the reason code). The buffer pool scan logic for P-lock transitions has been modified to correctly handle registering pages with a read I/O in progress. The pageset P-lock exit has been modified to ensure that if a failure occurs in a buffer pool scan, a re-drive of the exit will no longer skip the registration process. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88758 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM70981 introduces the following changes to externals: Changed messages or codes: description of change DSNB411I: Page read statistics When you specify the DETAIL option, the output includes the page read statistics for the buffer pool. DSNB411I - RANDOM GETPAGE = rgp SYNC READ I/O (R) = srr SEQ. GETPAGE = sgp SYNC READ I/O (S) = srs DMTH HIT = dmt PAGE-INS REQ = pir SEQUENTIAL = seq VPSEQT HIT = vsh RECLASSIFY = rcy RANDOM GETPAGE = rgp The number of nonsequential GETPAGE requests. SYNC READ I/O (R) = srr The number of synchronous read I/O operations for nonsequential GETPAGE requests. SEQ. GETPAGE = sgp The number of sequential GETPAGE requests. SYNC READ I/O (S) = srs The number of synchronous read I/O operations for sequential GETPAGE requests. DMTH HIT = dmt The number of times that the data management threshold was reached. PAGE-INS REQ = pir The number of page-in operations that are required for read 1 I/O. SEQUENTIAL = seq The number of buffers on the sequential least-recently-used (SLRU) chain. VPSEQT HIT = vsh The number of times that the size of the SLRU chain reached the sequential steal threshold (the VPSEQT value) for the buffer pool. RECLASSIFY = rcy A statistic that is used by IBM® for serviceability. Information about this changed message 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. ACTION: In order for DB2 to use "suppress cross-invalidation" enhancement for DELETE_NAME, all of the following must be true: - This PTF must be applied to the DB2 member that performs castout - The GBP must be allocated in a coupling facility of CFLEVEL=17 or higher. The following CFCC release supports the "suppress cross-invalidation" functionality: - z114 (2818) DR93G CFCC EC N48162 CFCC Release 17 at the requisite microcode load (MCL) level - z196 (2817) DR93G CFCC EC N48162 CFCC Release 17 at the requisite microcode load (MCL) level - zEC12 (2827) CFCC Release 18 - The DB2 member that performs castout must be running on z114 or z196 that supports the "suppress cross-invalidation" functionality or a zEC12. The following z/OS releases support the "suppress cross-invalidation" functionality: - z/OS V1R12 and above with APAR OA38419 installed AO: PM70981 introduces the following changes to externals: Changed messages or codes: description of change DSNB411I: Page read statistics When you specify the DETAIL option, the output includes the page read statistics for the buffer pool. DSNB411I - RANDOM GETPAGE = rgp SYNC READ I/O (R) = srr SEQ. GETPAGE = sgp SYNC READ I/O (S) = srs DMTH HIT = dmt PAGE-INS REQ = pir SEQUENTIAL = seq VPSEQT HIT = vsh RECLASSIFY = rcy 1 RANDOM GETPAGE = rgp The number of nonsequential GETPAGE requests. SYNC READ I/O (R) = srr The number of synchronous read I/O operations for nonsequential GETPAGE requests. SEQ. GETPAGE = sgp The number of sequential GETPAGE requests. SYNC READ I/O (S) = srs The number of synchronous read I/O operations for sequential GETPAGE requests. DMTH HIT = dmt The number of times that the data management threshold was reached. PAGE-INS REQ = pir The number of page-in operations that are required for read I/O. SEQUENTIAL = seq The number of buffers on the sequential least-recently-used (SLRU) chain. VPSEQT HIT = vsh The number of times that the size of the SLRU chain reached the sequential steal threshold (the VPSEQT value) for the buffer pool. RECLASSIFY = rcy A statistic that is used by IBM® for serviceability. Information about this changed message 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5DEL PM88758 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88758 DSNB5DEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1ABP DSNB1AEX DSNB1AGB DSNB1BVP DSNB1CBP DSNB1CMD DSNB1CNE DSNB1CPX DSNB1DBP DSNB1DVP DSNB1GBR DSNB1GC1 DSNB1GD1 DSNB1GET DSNB1GWB 1 DSNB1IOR DSNB1LRR DSNB1PCD DSNB1PMI DSNB1REL DSNB1RWI DSNB1TSD DSNB5CMX DSNB5COM DSNB5DEL DSNB5PCO DSNB5RAP DSNB5RDP DSNB5STS DSNB5ULK DSNFBDIR MACROS DSNDQBST LISTEND UK95295 COVER LETTER END UK95350 COVER LETTER START PROBLEM DESCRIPTION(S): PM88804 - **************************************************************** * USERS AFFECTED: All DB2 10 users. * **************************************************************** * PROBLEM DESCRIPTION: Frequent thread terminations without * * re-use may result in significant CPU * * consumption as 64bit thread pool * * storage is freed and REAL frames are * * unbacked. * **************************************************************** * RECOMMENDATION: * **************************************************************** When threads terminate, their pool storage may either be completely freed if the thread is not cached for reuse, or a portion may be freed. In either case, storage which is only virtually freed by DB2 since it is submanaged, will have its REAL frames unbacked in many cases. This unbacking requires RSM latch serialization and also results in a pagefault when those pages are again used. This whole process can show significant CPU usage depending on the number of threads and their allocation/deallocation frequency. Similarly, thread contraction which may occur at specific commit frequencies, also may result in pool storage being virtually freed with the REAL frames unbacked. REALSTORAGE_MANAGEMENT which has default of AUTO, should not result in the discard of REAL frames unless the LPAR comes under stress and begins paging or nears the REALSTORAGE_MAX value if specified. This apar changes the way 64 bit Above-the-bar (ATB) real storage frames are managed by DB2 based on the DB2 zparms REALSTORAGE_MANAGEMENT,REALSTORAGE_MAX and general RSM LPAR 1 storage monitor fields. DB2 ATB storage management is changed to no longer issue an IARV64 DISCARDDATA request to free real storage frames unless the DB2 storage monitor has detected that DISCARD MODE should be turned ON. When DISCARD MODE is ON the member will return to the same behavior it had prior to PM88804 and issue an IARV64 DISCARDDATA request when freeing storage. Not freeing the real storage frames can improve system performance due to a significant reduction in first reference page faults, RSM lock contention, and uncaptured CPU time. *** NOTE *** PM88804 may result in higher REAL FRAME counts being reported by DB2 monitor reports and RMF, especially in environments that never page to aux. For those customers who experience frequent or periodic paging, the counts may not be significantly higher but will likely still be higher than before PM88804. PM88804 reverses some of the affect of PK25427. The major reporting fields for 64 bit storage are: qw0225ShrStg_Real - Shared storage most heavily used for threads will likely show the most increase. qw0225ComStg_Real - High Common qw0225PriStg_Real - High address space private COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM88804 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNSCON2 PM88804 DSNSVSFM PM88804 DSNSVSPC PM88804 DSNSVSVP PM88804 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM88804 DSNSCON2 DSNSVSFM DSNSVSPC DSNSVSVP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNSCON2 DSNSVSFM DSNSVSPC DSNSVSVP LISTEND UK95350 COVER LETTER END UK95781 COVER LETTER START PROBLEM DESCRIPTION(S): PM89367 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using LOBs or XML and * 1 * DRDA encryption is enabled. * **************************************************************** * PROBLEM DESCRIPTION: High enclave CPU utilization occurs * * in the DIST address space. * **************************************************************** * RECOMMENDATION: * **************************************************************** Normally, LOB/XML data being returned to a client is sent as multiple 32767-byte size piece messages. Each piece of the LOB/XML string is retrieved from the database manager and then sent to the client. However, when a client requests that DRDA data encryption be performed on the connection, the entire LOB/XML string must be fully materialized into the server agent storage prior to the encryption of the data. Once encryption is complete, the data is then sent as multiple 32767-byte size piece messages. APAR PM79540 was implemented to address a problem with the LOB/XML data materialization by first utilizing the entire currently allocated send buffer as the initial target of the LOB/XML data retrieval. DB2 would then allocate a larger area to hold the fully materialized LOB/XML string if the currently allocated send buffer was not large enough. APAR PM79540 introduced a logic error that miscalculated the size of area required to hold the fully materialized LOB/XML string. Depending on the size of the the LOB/XML data, a condition may result where DB2 repeatedly requests the next piece of the LOB/XML string from the database manager, hence resulting in the DB2 server thread looping indefinitely. The server thread will hang as a result of the loop and since a DB2 server thread runs under a WLM enclave, excessive enclave CPU utilization may be observed in the ssnmDIST address space. DB2 has been changed to correctly calculate the size of the area required to hold the fully materialized LOB/XML string. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM89367 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLCBFM PM89367 DSNLCMSL PM89367 DSNLIINI PM89367 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM89367 DSNLCBFM DSNLCMSL DSNLIINI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLCBFM DSNLCMSL DSNLIINI LISTEND 1UK95781 COVER LETTER END UK95806 COVER LETTER START PROBLEM DESCRIPTION(S): PM91930 - **************************************************************** * USERS AFFECTED: All DB2 10 for zOS users. * **************************************************************** * PROBLEM DESCRIPTION: AE PM80779 fix completion * **************************************************************** * RECOMMENDATION: * **************************************************************** AE PM80779 fix completion AE PM80779 fix completion COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM91930 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: APAR PM45561 fixes a problem that causes incorrect output for readers of XML data that use ISOLATION LEVEL(UR) and and potentially allows DB2 to cause the readers of XML data to wait for a lock, even though ISO(UR) is specified. The situation usually occurs during heavy concurrent insert, update, or delete activity. The incorrect output problem is fixed by requiring ISOLATION(UR) readers to wait for XML locks. As a result, ISOLATION(UR) readers that access XML data might see increased wait time for locks. The additional wait time for unconditional locks sometimes result in deadlocks or timeouts(SQLCODE -911 or -913),therefore, application logic may need to change to accommodate SQLCODEs -911 and -913. ACTION: TYPE: DB2 This fix corrects a problem with Compensation Log Records (CLRs) built for compression dictionary pages for classic (non-segmented) partitioned table spaces during insert. The problem is limited to classic partitioned table spaces that have an insert-generated compression dictionary and have been RECOVERED with log-apply. A dictionary page log record may not get applied correctly due to incorrect DBID/OBID, which happens under limited circumstances. Compression dictionaries built by DB2 LOAD or DB2 REORG are not affected. You can identify an insert-generated dictionary by checking the HPGZLD field in the page header of the header-page of each pageset/partition. HPGZLD would be = 'F' for an insert-generated dictionary. The symptoms of the problem include abends and/or error return codes in/from modules that try to use the dictionary pages, 1 and/or DSNT501I RESOURCE UNAVAILABLE messages on the console with DB2 reason code = 00C9007F. The fix will correct the problem but it will not correct the log records already written with the error. So, after applying the fix, establishing new recovery bases for the table spaces which have the conditions specified above is advised. Forward log apply processes for such table spaces should not be performed against image copies taken prior to the application of the fix. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNILSTS PM91930 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM91930 DSNILSTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CLM DSNB1CNE DSNB1CPS DSNB1DCM DSNB1DDN DSNB1DRA DSNB1LCM DSNB1LDA DSNB1LDN DSNB1OPL DSNB1OPP DSNB1OPS DSNB1PMT DSNB1PM2 DSNB1POC DSNB1RCM DSNB1RRR DSNB1WFO DSNB5RAP DSNGDCOB DSNIACCH DSNIADR DSNICABS DSNICHLK DSNICLPM DSNICMT2 DSNICPOS DSNICREL DSNICRFT DSNICSEC DSNICTAC DSNICUMW DSNIDILS DSNIDLER DSNIESEN DSNIFDPO 1 DSNIHDUP DSNIHSET DSNIIEPL DSNILCLO DSNILKES DSNILREP DSNILSMG DSNILSTS DSNIMNEX DSNIMSAR DSNIMSCU DSNIMSRI DSNIMS1W DSNIONXP DSNIONX2 DSNIOST2 DSNIOW DSNIOWRE DSNIPOCH DSNIPOCR DSNIPOSP DSNIPOSS DSNIRDCU DSNIRELD DSNIRELK DSNIRELS DSNIRELU DSNIRFNX DSNIRIDL DSNIRNXT DSNIRPRE DSNIRPRV DSNIRRCU DSNIRSET DSNIRSVP DSNISELL DSNISFRL DSNISFS DSNISFX2 DSNISGFO DSNISGRT DSNISHPI DSNISMEX DSNISMRT DSNISNPG DSNISRID DSNISRTI DSNISUPI DSNISVPT DSNITCUS DSNITDLE DSNIXLDI DSNIZLDL DSNKCKOP DSNKDLE DSNKFLRR 1 DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKINSL DSNKISPL DSNKMSAX DSNKNXT2 DSNKPOSI DSNKUNR2 DSNNOLCK DSNOALLO DSNOCHLO DSNODCRL DSNOFRLC DSNOLDEL DSNOTCSO DSNTSTRT DSNUKIFK DSNUKNFK DSNUULXA LISTEND UK95806 COVER LETTER END UK96219 COVER LETTER START PROBLEM DESCRIPTION(S): PM85936 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS who use DSNADMSB * * and/or the stored procedure * * ADMIN_INFO_SQL who have PM73555 applied * * (UK83945 for V10; UK83946 for V9) * **************************************************************** * PROBLEM DESCRIPTION: THIS FIX ADDRESSES SEVERAL ISSUES * * RELATED TO OUTPUT FROM ADMIN_INFO_SQL * * FOR DDL AND STATISTICS. THE SYMPTOMS * * USUALLY ARE INCORRECT OUTPUT WHEN * * BUILDING THE DDL AND STATS OUTPUT * * FILES OR CAN RELATE TO LONG * * PROCESSING TIME. * **************************************************************** * RECOMMENDATION: * **************************************************************** ADMIN_INFO_SQL was sometimes not producing the correct output when creating DDL and STATS output files to be used for DB2 problem analysis. Here is a list of reported issues: - Ignore DB errors from Accelerator tables - Check ZPARM ACCEL for Accelerator existence - Bad input parameter message now in the log - Zero out error msg_var when DSNADMMW is called - PLAN_TABLE APPLNAME column from 9 to 24 bytes 1 - Business time check constraint display problem - Remove duplicate call to SYSTABLES to get Clone/Base relationship - SQLCODE514 problems for V10 CM8 ADMIN_INFO_SQL has several new features added: - Allow Test for input parameters - Collect DSN_FILTER_TABLE collection - Collect PACKAGE information from BIND collection - Collect Synonym info for Views - Added check for alias PLAN_TABLE input - Recoded ZPARM collection for speed - Collect QUERYINFO table only when accelerator is on The reported ADMIN_INFO_SQL problems are now corrected. ADDITIONAL KEYWORDS: SQLSP SQLSTOREDPROC ADMININFOSQL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85936 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. These instructions supersede any previous PTF instructions. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers. This PTF updates programs modules DSNADMSB and DSNADMSS plus the DBRM for DSNADMSS (the DBRM for DSNADMSB is not updated). After applying this PTF, proceed as follows to bind a package from the updated DSNADMSS DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2-supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. 1 After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF. Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Update your customized copy of job DSNTEJ6I --------------------------------------------------------------- ==> All DB2 V10 customers who maintain a customized copy of DSNTEJ6I need to take this action after applying the PTF. The change affects the default input for the following parameters: Change COLLECT_COLUMN_STATS to N Change EDIT_DDL to Y These default changes are made to minimize the amount of data that is collected. Column statistics can be abundant, but are not always required for analysis. Edit mode will help create DDL in a format that can be more easily applied to a service environment. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMSB PM85936 DSN@DMSS PM85936 DSNADMSB PM85936 DSNADMSS PM85936 HDBAA10J PM85936 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85936 DSN@DMSB DSN@DMSS DSNADMSB DSNADMSS HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMSB DSNADMSS MACROS DSN@DMSB DSN@DMSS 1 LISTEND UK96219 COVER LETTER END UK96335 COVER LETTER START PROBLEM DESCRIPTION(S): PM85432 - **************************************************************** * USERS AFFECTED: All DB2 9 z/OS and DB2 10 z/OS users who * * specify the KEEPDICTIONARY option during * * a REORG with EDITPROCS on the table. * **************************************************************** * PROBLEM DESCRIPTION: DB2 was incorrectly writing out * * compressed records which had not been * * EDITPROC encoded during a REORG when * * the KEEPDICTIONARY option was * * specified. * **************************************************************** * RECOMMENDATION: * **************************************************************** After PM44787/UK73145/UK73146 or PM65869/UK83961/UK83962 is applied and KEEPDICTIONARY is specified during a REORG with an EDITPROC on the table, the EDITPROC decoded record could be used for compression instead of the EDITPROC encoded record. When this occurs, the compressed EDITPROC decoded record is written out to the page. Afterwards, when trying to access that record, DB2 decompresses and decodes the record, which leads to incorrect results. Code has been changed so that if we do have an EDITPROC encoded record we will use that to compress the record instead of the decoded and decompressed record. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM85432 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: PM85432 does not fix existing data which has been affected by this problem, it does prevent future data from becoming corrupted by this issue. The user must identify the objects which have been affected and bring the data back to a consistent state. Objects that are affected must have the following conditions met: - The table must have an EDITPROC. - The table space or partition must have COMPRESS YES. - REORG with KEEPDICTIONARY must have been run with a dictionary present after PM44787/UK73145/UK73146 had been applied. The following SELECT statement can be used to determine if the first two conditions were met: SELECT TB.CREATOR, TB.NAME, TB.DBNAME, TB.TSNAME, TP.PARTITION FROM SYSIBM.SYSTABLES TB, SYSIBM.SYSTABLEPART TP WHERE TB.EDPROC <> ' ' AND 1 TB.DBNAME = TP.DBNAME AND TB.TSNAME = TP.TSNAME AND TP.COMPRESS = 'Y'; A REPORT RECOVERY can identify the names of the REORG job(s) that were run after the PTF was applied, however it cannot indicate if the KEEPDICTIONARY keyword was used during the REORG at the time. Because EDITPROCs can manipulate the data in many different ways, below are just a few methods for possibly identifying which tables may have corrupted data if it is not possible to determine whether or not the above conditions were all met: - A table space scan (SELECT * FROM XYZ) can be used to check if every record in the table can be EDITPROC decoded and displayed in the output, however even if the display is successful it is possible the actual output of the data is not correct and therefore corrupted. An ABEND can also occur if the data after the EDITPROC decoding cannot be properly formatted. - If an index is present on the data/column that has been EDITPROC encoded then a CHECK INDEX could detect the data corruption with an index/data mismatch if it has not been rebuilt after the data was corrupted. An ABEND can also occur if the data after the EDITPROC decoding cannot be properly formatted. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRLPG PM85432 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM85432 DSNIRLPG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRLPG LISTEND UK96335 COVER LETTER END UK96595 COVER LETTER START PROBLEM DESCRIPTION(S): PM91546 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS data sharing users with * * PM53155 that need to apply its PE fixing * * APAR PM77066 without applying enabling * * APAR PM74803. * * * * PTFs for the above mentioned APARs: * * PM53155 / UK77362 for DB2 10 for z/OS * * PM53155 / UK77364 for DB2 9 for z/OS * * PM53155 / UK77363 for DB2 V8 for z/OS * * * * PM77066 / UK91321 for DB2 10 for z/OS * 1 * PM77066 / UK91323 for DB2 9 for z/OS * * PM77066 / UK91322 for DB2 V8 for z/OS * * * * PM74803 / UK90830 for DB2 10 for z/OS * * PM74803 / UK90832 for DB2 9 for z/OS * * PM74803 / UK90831 for DB2 V8 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBHK ERQUAL500C * * during several data sharing members' * * DB2 checkpoint after group restart, * * leading to their DB2 crash with * * MSGDSNV086E RC00D95001 * **************************************************************** * RECOMMENDATION: * **************************************************************** During group restart, while updating the group DBET in SCA, a subset of the DBET base SCA record(s) for an object was accidentally deleted, which resulted in local DBET entry for the object being built incorrectly. In this case, there were more than 200 partitions with diverse exception states such that the DBET entry for this object had multiple DBET blocks. During internal DBET rectify, at the beginning of forward log apply phase, the group DBET in SCA needed to be updated since local DBET had to reset an internal extend-in-progress state. However, when copying the local DBET blocks to the group DBET in SCA, by mistake not all the DBET blocks were copied. This resulted in an incomplete group DBET in SCA for this object. When other members of the data sharing group came up, their local DBET was built incorrectly, eventually leading to the aforementioned ABEND04E. The first member that performed the rectify was able to come up successfully because his local DBET was not corrupted. Any subsequent DBET updates that this member performed after the group restart automatically cleaned up the group DBET in SCA, which is why the originally failed members were able to restart on their second restart attempt. DB2 code has been modified such that the group DBET in SCA is updated correctly during DBET rectify. Upcoming APAR, PM91547 will enable APAR PM69760. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM91546 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM MULTSYS: ***Action for PM74803: PM74803 is an APAR that includes changes to support a functional code change that will be enabled once this APAR is applied. Earlier, a pre-conditioning APAR PM69760 was delivered. In a 1 data sharing group, this pre-conditioning APAR should be applied to all members before applying this enabling APAR to any member. The code change is enabled once this enabling APAR is applied. The following APAR enables the fix for the problem of timeout by SCA REBUILD when a concurrent mainline DBET updater happens to be in the notify exit path. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBEL PM91546 DSNIDBGN PM91546 DSNIDBGR PM91546 DSNIDBNG PM91546 DSNIDBNI PM91546 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM91546 DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG DSNIDBNI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG DSNIDBNI LISTEND UK96595 COVER LETTER END READY END