1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES READY %COVRLETR WDB2I.R.DB2101S.SMPPTS IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED UK73587 COVER LETTER START PROBLEM DESCRIPTION(S): PM46544 - **************************************************************** * USERS AFFECTED: DB2 SYSPLEX query parallelism users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC0000003B IN DSNSVSVB * * OFFSET +0DA2 can occur when DB2 * * serializes storage requests of * * multiple SYSPLEX parallel * * tasks. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 allocates storage for the workfile OBD in the accumlating agent's pool. If the accumulating agent is another parallel task, not the parent task, DB2 hit the above abend, because the accumlating agent storage pool can not be shared with other parallel tasks. DB2 has been changed to allocate storage for the workfile OBD from the correct agent pool for a parallel task on the assistant DB2 member. additional keyword: SYSPLEX PARALLEL SQLPARALLELISM DB2PARALL/K PM51843 - **************************************************************** * USERS AFFECTED: AE PM46544 fix completion * **************************************************************** * PROBLEM DESCRIPTION: AE PM46544 fix completion * **************************************************************** * RECOMMENDATION: * **************************************************************** AE PM46544 fix completion AE PM46544 fix completion COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM46544,PM51843 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDCDB PM46544 PM51843 DSNGDCII PM51843 DSNGDCOB PM46544 DSNGDCOI PM46544 DSNGDDRT PM46544 DSNGDLOG PM46544 DSNTTRUN PM51843 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM46544 DSNGDCDB DSNGDCOB DSNGDCOI DSNGDDRT DSNGDLOG PM51843 DSNGDCDB DSNGDCII DSNTTRUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDCDB DSNGDCII DSNGDCOB DSNGDCOI DSNGDDRT DSNGDLOG DSNTTRUN LISTEND UK73587 COVER LETTER END UK74491 COVER LETTER START PROBLEM DESCRIPTION(S): PM53780 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of declared global * * temporary tables(DGTTs) or created global * * temporary tables(CGTTs) * **************************************************************** * PROBLEM DESCRIPTION: DB2 may use incorrect table statistics * * for access path selection when a DGTT * * or CGTT is empty. * **************************************************************** * RECOMMENDATION: * **************************************************************** If statistics show that a table has zero rows, DB2 will use CARDF and NPAGES statistics from real time statistics (RTS) to validate the number of rows in the table. Access path selection will then be based on the statistics reported by RTS. In the case of a DGTT or CGTT, the statistics tracked by RTS do not accurately represent a single instance of the temporary table and should not be used for access path selection. This problem may result in poor performance due to a poor access path choice. Additional keywords: SQLACCESSPATH SQLPERFORMANCE SQLSTATS SQLDGTT SQLGTT Query optimization does not use statistics from RTS for DGTTs and CGTTs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53780 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM53780: 1 A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM53780 corrects a problem in which incorrect statistics are used for a DGTT or CGTT when the table is empty. 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 PM50507: See PM50507 APAR/PTF text for additional information about why a REBIND is necessary. PM50507 corrects a problem of the DB2 optimizer in calculating the cost of hash access for a hash-organized table. The fix will get a more accurate estimation of hash access, and enable the DB2 optimizer to choose hash access methods over other suboptimal method(s). 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 the changes in this APAR. PM45292 corrects a problem in which a DB2 intentional abend may occur when a query contains the RID 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 DSNXOPRS PM53780 DSNXORTS PM53780 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53780 DSNXOPRS DSNXORTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRS DSNXORTS LISTEND UK74491 COVER LETTER END 1UK74560 COVER LETTER START PROBLEM DESCRIPTION(S): PM51625 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS and DB2 * * 10 for z/OS who are using the DB2- * * supplied user-defined function * * DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY). * **************************************************************** * PROBLEM DESCRIPTION: DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) * * abends with 0C4 while processing a * * DB2 scheduler task that has multiple * * execution statuses. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) saves a task's information it read from SYSIBM.ADMIN_TASKS in a local variable. Since a local variable is used, the task information is not preserved between the function's FETCH operations when more than one execution status has to be returned for this task. Therefore, subsequent FETCH operations can result in an 0C4 abend. DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) is modified to save a task's information which it read from SYSIBM.ADMIN_TASKS in the scratchpad, thereby increasing the scratchpad length of this function from 16 to 8208. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51625 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF fixes an 0C4 abend in the user-defined function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) when it is processing a DB2 scheduler task that has multiple execution statuses. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** *********************************************************** * This action is required for all V10 customers *********************************************************** Run your customized copy of job DSNTIJRT with MODE(INSTALL) to alter the scratchpad length of the modified user-defined function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) from 16 to 8208 and to bind this function's DBRM. 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMTH PM51625 DSN@RIN PM51625 DSNADMTH PM51625 DSNTESR PM51625 DSNTRIN PM51625 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51625 DSN@DMTH DSN@RIN DSNADMTH DSNTESR DSNTRIN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMTH DSNTRIN MACROS DSN@DMTH DSN@RIN DSNTESR LISTEND UK74560 COVER LETTER END UK75539 COVER LETTER START PROBLEM DESCRIPTION(S): PM53303 - **************************************************************** * USERS AFFECTED: All DB2 UDB for z/OS V8, DB2 9 for z/OS, * * and DB2 10 for z/OS users of the DB2 * * scheduler for administrative tasks * **************************************************************** * PROBLEM DESCRIPTION: In z/OS 1.13, the DB2 scheduler cannot * * find the JES2 command character used * * to issue the cancel command to purge * * the job output of a task it executed. * * The following message is returned by * * DSNADM.ADMIN_TASK_STATUS in the MSG * * column: * * DSNA631I DSNA6THJ THE JES00000002 * * COMMAND PURGE WAS ISSUED * * BUT NOT ACCEPTED * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** The scheduler checks the HCCT CCTVRSN value to determine the offset of the JES2 command character field CCTCOMCH from the start of HCCT. Since z/OS 1.13 changed the CCTVRSN value to X'0D', it is not recognized by the scheduler. Therefore, the scheduler is unable to find the JES2 command character when running under z/OS 1.13. 1 The scheduler assumes that the JES2 SSCVT control block is always the first SSCVT on the SSCVT chain. Therefore, when the JES2 SSCVT control block is not the first on the chain, the scheduler will be accessing the wrong control block to access the HCCT control block where the JES2 command character is located. The JES version in message DSNA631I is defined in the message repository as short int instead of long int. This caused the jes-version in DSNA631I to display as JES00000002, instead of JES2. Beginning with z/OS 1.7, we can find the command character by invoking SSI 54. Therefore, for DB2 9 for z/OS and higher, the scheduler is modified to invoke SSI 54 to find the command character. For DB2 for z/OS V8, the scheduler is changed to access each SSCVT in the chain until the JES2 SSCVT control block is found or the end of the SSCVT chain is reached. It is also changed to accept CCTVRSN X'0D' as a valid HCCT control block version. The JES version in DSNA631I is changed to long int in the message repository. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53303 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM53303 (DB2 10 for z/OS) This PTF modifies the DB2 scheduler for administrative tasks so that it can purge the job output of a JCL task it executed on z/OS 1.13. 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 DSNADMMG PM53303 DSNADMMW PM53303 DSNA6THJ PM53303 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM53303 DSNADMMG DSNADMMW DSNA6THJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMMG DSNADMMW DSNA6THJ LISTEND UK75539 COVER LETTER END UK75943 COVER LETTER START PROBLEM DESCRIPTION(S): PM51826 - **************************************************************** * USERS AFFECTED: DB2 for z/os V10 with Hash Table Space * **************************************************************** * PROBLEM DESCRIPTION: The Hash Chain on the hash home pgae * * is broken after SQL INSERT, * * therefore ABEND04E RC00C90105 * * DSNISGRT ERQUAL0C44 is triggered * **************************************************************** * RECOMMENDATION: * **************************************************************** When a record can not be inserted into the hash home page, this record must be inserted into the hash overflow area. During space search of the hash overflow pages, another hash home page was found and processed as a hash overflow page incorrectly, which result in a broken hash chain on the page. Therefore, the sanity check of the page was triggered and the transaction abended with 04E-00C90105 & erqual code 0C44. DB2 code was modified to ensure only non-hash home page is used for hash over flow area. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51826 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 PM51826 DSNISGSU PM51826 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51826 DSNISGNS DSNISGSU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGNS DSNISGSU LISTEND 1UK75943 COVER LETTER END UK75949 COVER LETTER START PROBLEM DESCRIPTION(S): PM50451 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users who run query with groupby clause * * and parallelism enabled. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E72018 at CSECT DSNXSBUC * * offset 3E7A may happen when running * * query with groupby clause and * * parallelism enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND at location DSNXGRDS.DSNXSBUC may occur when running query with groupby clause and parallelism enabled. The following query is an example of this case. SET CURRENT DEGREE='ANY'; SELECT V1.C1 FROM (SELECT 'A' FROM T1 UNION ALL SELECT DISTINCT TX.C1 FROM (SELECT C1 FROM T2 UNION ALL SELECT C1 FROM T3) TX(C1) ) AS V1(C1) WHERE V1.C1 LIKE 'A%' UNION ALL SELECT V1.C1 FROM (SELECT 'A' FROM T1 UNION ALL SELECT DISTINCT TX.C1 FROM (SELECT C1 FROM T2 UNION ALL SELECT C1 FROM T3) TX(C1) ) AS V1(C1) WHERE V1.C1 > 'A' GROUP BY V1.C1 ; An ABEND04E may occur with the SELECT statement. The code in DB2 is modified to correct the failing condition. Additional keyword: SQLPARALLELISM SQLGROUPBY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM50451 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 DB2BIND: ***Action for PM50451: See PM50451 APAR/PTF text for additional information about why a REBIND is necessary. PM50451 corrects a problem of ABEND04E RC00E72018 at CSECT DSNXSBUC offset 3E7A may happen when running query with groupby clause and parallelism 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 PM45209: See PM45209 APAR/PTF text for additional information about why a REBIND is necessary. PM45209 corrects a problem of incorrect output on query containing aggregate function distinct w/o group by and running with dpsi index and 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: ***Action for PM43740: See PM43740 APAR/PTF text for additional information about why a REBIND is necessary. PM43740 corrects a problem of ABEND04E RC00E70005 in DSNXGDT2 M201 may occur when one of the following condition met: 1. a UNION/INTERSECT/EXCEPT query with COUNT COLUMN function, MIN/MAX aggregate function in the selection list and the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 2. Or a UNION ALL/INTERSECT ALL/EXCEPT ALL query with ORDER BY clause and COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also,the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 3. Or a query with ORDER BY clause and a COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also, the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 4. Or a SELECT DISTINCT statement with COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also, the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it 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 1 letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM39444: See PM39444 APAR/PTF text for additional information about why a REBIND is necessary. PM39444 corrects a problem of ABEND04E RC00E72018 at DSNXSTSE offset 0A9C may occur when a query contains a column function in the selection list and its result data type is a LOB 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. DB2BIND: ***Action for PM36118: See PM36118 APAR/PTF text for additional information about why a REBIND is necessary. PM36118 corrects a problem of ABEND0C4 RC00000011 DSNXRSGB offset 5E5C may occur when view has duplicate group by 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGSGP PM50451 DSNXOCON PM50451 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM50451 DSNXGSGP DSNXOCON THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSGP DSNXOCON LISTEND UK75949 COVER LETTER END UK76112 COVER LETTER START PROBLEM DESCRIPTION(S): PM51825 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of COPY utility * * with the FLASHCOPY option. * **************************************************************** 1 * PROBLEM DESCRIPTION: COPY with FLASHCOPY option does not * * properly detect a duplicate output * * data set and creates a new one * * with the same name instead. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a COPY utility with FLASHCOPY option on a tablespace using a TEMPLATE for FCCOPYDDN, then ran the COPY utility again using the same TEMPLATE for FCCOPYDDN. The second COPY utility deleted the existing data sets generated from TEMPLATE and created new ones successfully instead of reporting an error. COPY utility is missing check for duplicate data sets for COPY with FLASHCOPY. This problem can also occur for FLASHCOPY when the output data set is not a TEMPLATE. COPY utility is modified to issue MSGDSNU407I - 'DATA SET ALREADY USED FOR PREVIOUS IMAGE COPY' and MSGDSNU408I - 'dsn EXISTS WITH....' and return RC8 when duplicate data sets are found for FLASHCOPY. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51825 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBCKD PM51825 DSNUGFCB PM51825 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51825 DSNUBCKD DSNUGFCB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBCKD DSNUGFCB LISTEND UK76112 COVER LETTER END UK76162 COVER LETTER START PROBLEM DESCRIPTION(S): PM49443 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of LIKE predicates that contain the UPPER * * scalar function. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses the problem of * * LIKE predicates containing the UPPER * * scalar function that are non-indexable. * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** When a query contains a LIKE predicate with the UPPER scalar function, the predicate cannot become indexable. With this apar, this predicate can now become indexable. The following example shows an EXPLAIN for a query containing a LIKE predicate with the UPPER scalar function. EXPLAIN ALL SET QUERYNO = 1 FOR SELECT FIRSTNME FROM EMP WHERE LASTNAME LIKE UPPER(CAST(? AS VARCHAR(200))); On running the above EXPLAIN statement, the result would show the KEYFIELD column of the DSN_PREDICAT_TABLE to contain a 'Y' if there is a suitable INDEX available for the LASTNAME column. Please note that the LIKE predicate must be a boolean term predicate to become indexable. Also, the argument to the UPPER scalar function must be simple, i.e. a literal, a host variable, or a parameter marker with an allowable string data type. DB2 has been modified to allow LIKE predicates that contain the UPPER scalar function to become indexable. Please note that this apar is the forward fit of apar PM45033 for DB2 for z/OS V8. Additional Keywords: SQLINDEX SQLLIKE SQLUPPER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM49443 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM49443: See PM49443 APAR/PTF text for additional information about why a REBIND is necessary. PM49443 allows LIKE predicates with the UPPER scalar function to become indexable. 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 PM48939: See PM48939 APAR/PTF text for additional information about why a REBIND is necessary. PM48939 corrects a problem of incorrect output may occur when a pair-wise join query uses a multi-column index between dimension table and Fact table and there is a Fact table local predicate 1 covered by the same multi-column 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 DSNXGRM1 PM49443 DSNXGSFN PM49443 DSNXOAF PM49443 DSNXOBM PM49443 DSNXOMEX PM49443 DSNXORHV PM49443 DSNXOW2D PM49443 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM49443 DSNXGRM1 DSNXGSFN DSNXOAF DSNXOBM DSNXOMEX DSNXORHV DSNXOW2D THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGRM1 DSNXGSFN DSNXOAF DSNXOBM DSNXOMEX DSNXORHV DSNXOW2D LISTEND UK76162 COVER LETTER END UK76249 COVER LETTER START PROBLEM DESCRIPTION(S): PM54095 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS and DB2 9 for * * z/OS * **************************************************************** * PROBLEM DESCRIPTION: 1. Documented offsets for IFCA fields * * IFCAR0 and IFCAR15 are incorrect. * * * * 2. Documented description of field * * QW0199BP is incorrect. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. Offsets to fields IFCAR0 and IFCAR15 in DSNDIFCA are only correct for READS request for IFCID129. For IFI commands, these offsets are incorrect. 2. Contents of field QW0199BP is the bufferpool ID. However, that ID is represented differently if the IFCID199 is obtained 1 via an IFI READS request as opposed to IFCID199 that is written as part of a statistics trace to all other destinations. 1. Define 2 new fields IFCACR0 and IFCACR15 to store the return and reason codes for an IFI command. 2. Correctly describe the contents of QW0199BP. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM54095 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDIFCA PM54095 DSNDQW02 PM54095 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM54095 DSNDIFCA DSNDQW02 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNDIFCA DSNDQW02 LISTEND UK76249 COVER LETTER END UK76309 COVER LETTER START PROBLEM DESCRIPTION(S): PM38329 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of LOAD INCURSOR * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNL406I is issued during -STOP DDF * * processing for each LOAD INCURSOR * * utility that had been previously * * executed that loaded data from a remote * * location. MSGDSNL423I is then issued * * during a subsequent -START DDF. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD INCURSOR specifying a SELECT from a table from a remote site and utilizing TCP/IP completes with RC0 and the table is loaded correctly. However, when a -STOP DDF command is issued, one DSNL406I message (THREAD luwid=token AT PARTICIPANT location MAY BE INDOUBT BECAUSE OF A COMMUNICATION FAILURE. DB2 COMMITTED THE THREAD. INFORMATION RECORDED IN TRACE RECORD WITH IFCID=209 AND IFCID SEQUENCE NUMBER=seq-no) is issued for each of the above utilities executed due to DDF considering them indoubt threads. 1 During a subsequent -START DDF command, DDF indoubt thread processing handled each of the above and issued one DSNL423I - message (AUTOMATIC RESOLUTION OF luwid=token WITH PARTICIPANT location RESULTED IN COMMIT) for each one of them. This problem occurs due to an inconsistency between DDF and LOAD INCURSOR processing in conjunction with a two-phase commit optimization technique utilized by DDF. Note that this problem only occurs if the Communications Data Base is configured to access the remote location via TCP/IP connections. LOAD INCURSOR utility code and DDF processing code have been changed to coordinate the two-phase commit processing in order to eliminate the potential of a DDF related indoubt thread. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM38329 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM38329 has modified CSECTs in both the DSNUT101 and DSNLDTML load modules, affecting the utility batch and DB2 DDF 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 DDF 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 DDF address spaces, the problem the PTF addresses will not be resolved. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLCMT2 PM38329 DSNUGSIT PM38329 DSNURILD PM38329 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM38329 DSNLCMT2 DSNUGSIT DSNURILD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLCMT2 DSNUGSIT DSNURILD LISTEND UK76309 COVER LETTER END 1UK76370 COVER LETTER START PROBLEM DESCRIPTION(S): PM55991 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of utility inline statistics * * processing and RUNSTATS utility. * **************************************************************** * PROBLEM DESCRIPTION: A REORG utility with inline statistics * * ended with a RC8 after a message * * MSGDSNU622I. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A REORG with STATISTICS option issued a message DSNU622I - ... CATALOG UPDATE FOR ... NOT SUCCESSFUL, REASON = 00C9008E, because of the catalog table access failure. Then the utility failed with a RC8. The problem occurred because the return code from the catalog table access was saved directly for the statistics update. DSNU622I is a warning message and should cause a RC4 instead of a RC8. This message may be issued for the following catalog tables: SYSCOLUMS SYSCOLUMS_HIST SYSINDEXES SYSINDEXES_HIST The code has been modified to return RC4 when DSNU622I is issued. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55991 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 PM55991 DSNUSEOF PM55991 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55991 DSNUSEF2 DSNUSEOF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSEF2 DSNUSEOF LISTEND UK76370 COVER LETTER END UK76480 COVER LETTER START PROBLEM DESCRIPTION(S): PM49449 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users of * * DSN_COLDIST_TABLE * **************************************************************** * PROBLEM DESCRIPTION: DSN_COLDIST_TABLE may contain the * * following incorrect values: * * 1. The FREQUENCYF column may display * * a frequency greater than 100% * * 2. The LOWVALUE and HIGHVALUE columns * * may be prefixed by garbage values, * * and may be truncated. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSN_COLDIST_TABLE may sometimes contain incorrect values in the following fields: 1. The FREQUENCYF column may display a value over 100% (e.g., 1.0000002393535539E+00), or the sum of the frequencies for each COLVALUE in the table exceed 100% even after taking rounding error into consideration. 2. The LOWVALUE and HIGHVALUE columns may be prefixed by some garbage data when the data type of the column is VARCHAR, VARGRAPHIC or VARBINARY. Also, the end of the data may be truncated. (e.g., HIGHVALUE='0010FFFFFFFFFFFFFFFFFFFFFFFFFFFF' garbage value of '0010' precedes the actual high value.) The FREQUENCYF column error can occur because of the inaccurate precision of variables used to store the value. The LOWVALUE/HIGHVALUE columns can contain garbage values because of improper handling of the values for the specified data types. Additional Keywords: SQLEXPLAIN Code is corrected to address the problems described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM49449 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM53062: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM53062 corrects a problem that incorrect output may be returned by a query with GROUP BY clause and a set function with DISTINCT. 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 PM38744: 1 A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM38744 corrects a problem of inaccurate cost estimation for an index on the inner table in a 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 DSNXOD16 PM49449 DSNXOGBM PM49449 DSNXOPRP PM49449 DSNXOPRS PM49449 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM49449 DSNXOD16 DSNXOGBM DSNXOPRP DSNXOPRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOD16 DSNXOGBM DSNXOPRP DSNXOPRS LISTEND UK76480 COVER LETTER END UK76615 COVER LETTER START PROBLEM DESCRIPTION(S): PM56419 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of REORG * * SHRLEVEL CHANGE * **************************************************************** * PROBLEM DESCRIPTION: Applications receive MSGDSNT501I with * * RC00C900BA when REORG SHRLEVEL CHANGE * * holds the table space drain lock while * * in the UTILTERM phase. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** Applications timeout with message DSNT501I and RC00C900BA due to a claim failure because a REORG SHRLEVEL CHANGE of an entire partitioned table space still held the drain while in the UTILTERM phase. When a REORG of an entire partitioned table space is run, a drain is acquired on the entire table space. When the REORG attempts to de-drain, the de-drain occurs one partition at a time but fails to release the table space lock. 1 REORG code has been changed to de-drain the partitioned table space as a single entity when the REORG is on the entire table space. PM60722 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: AE PM56419 FIX COMPLETION * **************************************************************** * RECOMMENDATION: * **************************************************************** AE PM56419 FIX COMPLETION AE PM56419 FIX COMPLETION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56419,PM60722 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 PM60722 DSNURDRN PM56419 PM60722 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56419 DSNURDRN PM60722 DSNB1DRA DSNURDRN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DRA DSNURDRN LISTEND UK76615 COVER LETTER END UK76645 COVER LETTER START PROBLEM DESCRIPTION(S): PM56542 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with zparm NPGTHRSH * * set to a non-zero value or executing * * queries containing either ... * * * VOLATILE tables * * * Predicates for which optimizer * * estimates zero rows will qualify. * **************************************************************** * PROBLEM DESCRIPTION: DB2 10 for z/OS may incorrectly use the * * index probing feature. This could lead * * to increased prepare times and/or * * inefficient access paths. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 for z/OS may use index probing under any of the 1 following conditions: * Zparm NPGTHRSH is set to a non-zero value. * A query references a table defined as VOLATILE. * DB2 determines that no rows will qualify based on a predicate or index. In the process of index probing, DB2 could incorrectly... * Probe the index when no search value is available (either from the query text or via REOPT). * Determine that all rows qualify for the predicate or index when there are zero rows in the table. The increased prepare time and/or inefficient access paths resulting from this problem could lead to poor performance. Additional keywords: SQLPERFORMANCE SQLACCESSPATH DB2 will only perform an index probe when a probe value is provided either as a literal in the query or via REOPT. Also, if the index probe determines the table has zero rows, DB2 will determine the filter factor based on catalog statistics. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56542 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGBM PM56542 DSNXOIXP PM56542 DSNXOPRP PM56542 DSNXOPRS PM56542 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56542 DSNXOGBM DSNXOIXP DSNXOPRP DSNXOPRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGBM DSNXOIXP DSNXOPRP DSNXOPRS LISTEND UK76645 COVER LETTER END UK76698 COVER LETTER START PROBLEM DESCRIPTION(S): PM51913 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with user * * defined indexes on DB2 catalog. * 1 **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90110 with ERQUAL5004 * * in DSNICTBU when creating a user table. * **************************************************************** * RECOMMENDATION: * **************************************************************** "DROP INDEX" of a user defined index on a catalog table and "CREATE TABLE" of a user table were running concurrently when "CREATE TABLE" encountered ABEND04E RC00C90110 with ERQUAL5004 in DSNICTBU. Investigation shows that there is a timing window where "CREATE TABLE" still references the old OBD (object description) of the user defined index on the catalog, even though it has already been successfully dropped. This timing window is closed by proper serialization between jobs that intend to update DB2 catalog. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51913 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 PM51913 DSNICUBC PM51913 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51913 DSNIBCTD DSNICUBC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBCTD DSNICUBC LISTEND UK76698 COVER LETTER END UK76782 COVER LETTER START PROBLEM DESCRIPTION(S): PM49346 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE551 received when a user with * * system DBADM authority tried to * * create a table for another user * * involving a user defined data type. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE551 received when a user with system DBADM tried to create a table for another user involving a user defined data type even though system DBADM authority implicitly 1 has usage on user defined types. SQLCODE551 can also be received while using system DBADM authority for creating or altering a table or view for another user involving a user defined type or a user defined function. When user defined function is involved, system DBADM authority needs to have execute on the function. Authorization did not take into consideration the creator having system DBADM authority and USAGE on user defined types or EXECUTE on user defined functions. DB2 code is changed to allow system DBADM authority to behave correctly in the above stated scenarios. Additional keywords: SYSDBADM SQLCODE551 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM49346 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The "RACF Access Control Module Guide" (SC19-2982-01) is updated with the changes below. Chapter 14: RACF authorization checking reference - In "System privileges" section, a note is added for SYSDBADM. SYSDBADM XAPLPRIV value: DB2AAUTHU Privcode 287 (x'11F') The user must have sufficient authority to: One of these resources: In class: ------------------------------------------------------------ DB2-subsystem.SYSDBADM MDSNSM or GDSNSM DB2-subsystem.SYSCTRL DSNADM DB2-subsystem.SYSADM DSNADM Note: DB2® turns on bit 7 of the XAPLFLG1 field for a user table that includes user defined data type or user defined function. If this bit is on, the RACF® access control module bypasses checking for the SYSCTRL authority. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXA02 PM49346 DSNXA2UM PM49346 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM49346 DSNXA02 DSNXA2UM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXA02 DSNXA2UM LISTEND UK76782 COVER LETTER END UK76808 COVER LETTER START PROBLEM DESCRIPTION(S): PM56036 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: Execution of a dynamic statement * * results in an intermittent SQLCODE -518 * * when connected to a DB2 10 for z/OS * * intermediate server. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application requester at Site 1 connects to a DB2 10 for z/OS intermediate server at Site 2. The application's package was previously bound at Site 2 with the REOPT(ONCE) option which results in deferred prepare behavior. The application issues a PREPARE for a dynamic statement that contains a 3-part name or alias reference to a downstream server at Site 3. The intermediate server at Site 2 receives the PREPARE request from Site 1, but erroneously did not forward the PREPARE to Site 3. When the subsequent EXECUTE for the dynamic statement is received, Site 2 forwards it to Site 3. The Site 3 server attempts to EXECUTE the unprepared statement resulting in SQLCODE -518. NOTE: This problem occurs for DB2 10 for z/OS intermediate servers, and when the application package is bound DEFER(PREPARE) or REOPT(ONCE|AUTO|ALWAYS). DB2 has been corrected to always forward the PREPARE statement to a downstream server regardless of how the application's package was bound at the intermediate server. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56036 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXPRS PM56036 DSNLZD00 PM56036 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56036 DSNLXPRS DSNLZD00 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXPRS 1 DSNLZD00 LISTEND UK76808 COVER LETTER END UK76865 COVER LETTER START PROBLEM DESCRIPTION(S): PM55921 - **************************************************************** * USERS AFFECTED: All users of IFC on DB2 10 on z/OS and DB2 * * 9 on z/OS. * **************************************************************** * PROBLEM DESCRIPTION: DSNW140I message is missing when -START * * TRACE command cannot find an available * * OP destination and destination OPX is * * specified. * **************************************************************** * RECOMMENDATION: * **************************************************************** When -START TRACE command specifies DEST(OPX) option, IFC will look for the first available OP destination. If no available OP destination exists, the -START TRACE command should fail and message DSNW140I should be written to the console. Due to an error in start trace logic, -START TRACE succeeds and no error message is written. Such a trace would have no valid destination and will not produce any IFCIDs. Correct the error in start trace logic to fail the -START TRACE command when no valid OP destination is found. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55921 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWVCM1 PM55921 DSNWVCST PM55921 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55921 DSNWVCM1 DSNWVCST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWVCM1 DSNWVCST LISTEND UK76865 COVER LETTER END UK76986 COVER LETTER START PROBLEM DESCRIPTION(S): PM56893 - 1 **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of JCC T2 z/OS driver * * and limited block fetch. * **************************************************************** * PROBLEM DESCRIPTION: There was extraneous processing done * * when executing limited block fetch * * under JCC T2 z/OS driver. This may * * cause higher CPU usage. * **************************************************************** * RECOMMENDATION: * **************************************************************** There was a potentially redundant block of code that was executed on limited block fetch under JCC T2 z/OS driver. This may cause higher CPU usage. The affected code is modified to remove the redundancy. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56893 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECP PM56893 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56893 DSNXECP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECP LISTEND UK76986 COVER LETTER END UK77001 COVER LETTER START PROBLEM DESCRIPTION(S): PM55933 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of pureXML. * **************************************************************** * PROBLEM DESCRIPTION: This APAR adds XML storage * * serviceability trace. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR adds XML storage serviceability trace. IFCID 367 is enabled to support XML storage serviceability trace. Additional keywords: IFCID367 XMLALL SQLXML COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55933 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 DSNDQWHS PM55933 DSNDQW05 PM55933 DSNWVINT PM55933 DSNXMLSM PM55933 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55933 DSNDQWHS DSNDQW05 DSNWVINT DSNXMLSM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWVINT DSNXMLSM MACROS DSNDQWHS DSNDQW05 LISTEND UK77001 COVER LETTER END UK77003 COVER LETTER START PROBLEM DESCRIPTION(S): PM55479 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of DECIMAL data * * type. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 in DSNXOGBM OFFSET * * BE2C may occur or an inefficient access * * path may be chosen for a query with * * a predicate on a DECIMAL column. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 incorrectly handles the length of histogram statistics of a DECIMAL column. This problem may result in either of the following symptoms: 1. Inefficient access path may be chosen for a query with a predicate on a DECIMAL column if histogram statistics is collected on this DECIMAL column or multi-column histogram statistics is collected on a COLGROUP including this DECIMAL column. 2. An ABEND0C4 RC00000010 in DSNXOGBM OFFSET BE2C may occur if the DECIMAL column is a leading key of an index and index probing is used for the query. Index probing is applicable for DB2 10 for z/OS only and may be used under any of the following conditions: 1 * Zparm NPGTHRSH is set to a non-zero value. * A query references a table defined as VOLATILE. * DB2 determines that no rows will qualify based on a predicate or index. Additional Keywords: ABEND0C4 RC00000010 in DSNXOGBM SQLACCESSPATH SQLPERFORMANCE DECIMAL Code has been modified to handle the length of histogram statistics of a DECIMAL column correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55479 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM55479: See PM55479 APAR/PTF text for additional information about why a REBIND is necessary. PM55479 corrects a problem that DB2 incorrectly handles the length of histogram statistics of a DECIMAL 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 PM50516: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM50516 corrects a problem in which an incorrect compound filter factor is computed when there is data skew and that data skew is represented by frequency statistics. 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 PM55479 DSNXOGNC PM55479 DSNXOPRS PM55479 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55479 DSNXOGBM DSNXOGNC DSNXOPRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGBM DSNXOGNC 1 DSNXOPRS LISTEND UK77003 COVER LETTER END UK77007 COVER LETTER START PROBLEM DESCRIPTION(S): PM56814 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the MODIFY * * RECOVERY utility. * **************************************************************** * PROBLEM DESCRIPTION: MODIFY RECOVERY executed on a V10 NFM * * data sharing system receives ABEND04E * * RC00E40190 RC00C900BF (IRLM out of * * storage condition). * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** The MODIFY RECOVERY utility executed on a V10 NFM data sharing system receives ABEND04E 00E40190 00C900BF (IRLM out of storage condition) when there are a very large number of SYSIBM.SYSLGRNX records to delete. In V10 NFM, locksize for SYSLGRNX has been changed from page level locking to row level locking, so the number of total locks requested by MODIFY RECOVERY can increase dramatically. The MODIFY RECOVERY utility has been changed to commit more aggressively during the deletion of SYSLGRNX records so that the row level locks are released more frequently. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56814 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBCOP PM56814 DSNUMDEL PM56814 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56814 DSNUBCOP DSNUMDEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBCOP DSNUMDEL LISTEND UK77007 COVER LETTER END UK77039 COVER LETTER START PROBLEM DESCRIPTION(S): PM59740 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of LISTDEF * * utility with the PARTLEVEL keyword. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E4D5D2 in DSNUGSTA when * * using LISTDEF lists on multiple * * utilities in the same job step. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer defined multiple LISTDEF lists with the PARTLEVEL keyword and then used two or more of those lists in the same job step. PARTLEVEL structures for all LISTDEFs were freemained after the first utility, resulting in ABEND04E RC00E4D5D2 in DSNUGSTA when the next utility tried to use that storage. The same failure may occur if the same LISTDEF list is used more than once in the job step. This failure occurs only when PARTLEVEL is specified with a non-zero operand and may occur in any utility which uses LISTDEF lists. The specific symptom of this failure may vary greatly, with abends in different modules and at various offsets. The structures created for the LISTDEF PARTLEVEL keyword are no longer freemained between utilities. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59740 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGPPE PM59740 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59740 DSNUGPPE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGPPE LISTEND UK77039 COVER LETTER END UK77097 COVER LETTER START PROBLEM DESCRIPTION(S): PM56541 - **************************************************************** * USERS AFFECTED: All DB2 parallelism users. * **************************************************************** * PROBLEM DESCRIPTION: Distributed thread could not be * * cancelled. The thread is looping. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** Distributed thread could not be cancelled, thread is looping. The problem happens when DB2 is running in parallelism. One parallel thread is inside a loop waiting for updates from other parallel threads, but those threads have been cancelled already. In consequence, this thread will loop indefinitely. This problem only happens for certain timing window when the thread is running inside the loop we mentioned above, and it is not query specific. DB2 has been fixed to check the status of the thread inside a DO WHILE loop, so when the thread is cancelled, DB2 can respond and stop running indefinitely. Additional keywords: PARALLELISM SQLPARALLELISM LOOPING DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56541 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXPRE2 PM56541 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56541 DSNXPRE2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXPRE2 LISTEND UK77097 COVER LETTER END UK77119 COVER LETTER START PROBLEM DESCRIPTION(S): PM55586 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically when a remote application * * accesses Binary, Decimal Floating Point, or * * XML data types at a DB2 for z/OS server. * **************************************************************** * PROBLEM DESCRIPTION: A remote application receives SQLCODE * * -804 when accessing Binary, Decimal * * Floating Point, or XML data at a DB2 * * for z/OS server. * * This can happen when: * * 1. an existing connection is being * * reused for a new request. * * 2. a DB2 10 for z/OS system is running * * in Enabling New Function Mode * * (ENFM) after being migrated from * 1 * DB2 9 for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following conditions are reported: 1. A remote application is connected to a DB2 for z/OS server and performs an SQL statement that contains an output of Binary, Decimal Floating Point, or XML data. Due to residual information, DB2 incorrectly determined that the remote client was downlevel and did not support the data types so an SQLCODE -804 was erroneously issued. The residual information occurs when an existing connection is reused to service a subsequent request because connection reuse processing did not clean up the residual information related to the prior use of the connection. 2. A remote application is connected to a DB2 10 for z/OS server and performs an SQL statement that contains an output of Binary, Decimal Floating Point, or XML data. Due to an internal error in logic related to "DB2 10 ENFM migration from DB2 9" environments, DB2 10 for z/OS incorrectly determined that the remote client was downlevel and did not support Binary, Decimal Floating Point, or XML data types so an SQLCODE -804 was erroneously issued. DB2 for z/OS server processing has been changed to correctly handle the SQL request that accesses Binary, Decimal Floating Point, or XML data for the connection reusing case, as well as in a DB2 10 ENFM migration environment from DB2 9 for z/OS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55586 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTMIN PM55586 DSNLZRPY PM55586 DSNLZR00 PM55586 DSNLZSRM PM55586 DSNLZSR2 PM55586 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55586 DSNLTMIN DSNLZRPY DSNLZR00 DSNLZSRM DSNLZSR2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTMIN DSNLZRPY DSNLZR00 DSNLZSRM DSNLZSR2 LISTEND UK77119 COVER LETTER END 1 UK77130 COVER LETTER START PROBLEM DESCRIPTION(S): PM54015 - **************************************************************** * USERS AFFECTED: Users of CREATE TABLE or ALTER TABLE ADD * * COLUMN where the table name is less than * * three bytes and defines an XML column. * **************************************************************** * PROBLEM DESCRIPTION: CREATE TABLE with an XML column may * * result in ABEND04E RC00E70005 * * DSNXICDX:P042 when the table name is * * less than three bytes and X'7B' is not * * the '#' in the SBCS EBCDIC CCSID being * * used, such as CCSID 278/1143. * **************************************************************** * RECOMMENDATION: * **************************************************************** CREATE TABLE and ALTER TABLE ADD COLUMN which specifies an XML column may result in ABEND04E RC00E70005 DSNXICDX:P042 when the table name is less than three bytes and X'7B' is not the '#' in the SBCS EBCDIC CCSID being used, such as CCSID 278/1143. If the table name specified is shorter than three bytes, part of the implicit XML table space name is padded with'#'. The ABEND occurs during processing of the implicit XML table space name which includes a '#' which is represented by X'7B'. Implicitly created XML table space names will be Xyyynnnn, where yyy is the first three bytes of the base table name. With PM54014, if the table name is shorter than three bytes, the implicitly created XML table space name will be padded with 'X' instead of '#'. For example,if we create table named 'T' which included an XML column, the implicitly created XML table space will be named XTXX0000 instead of XT##0000. This apar will not affect existing XML table space names. The approximate text is to be added to the DB2 SQL Reference manual. This text is subject to change. CREATE TABLE Naming convention for implicitly created XML objects: Implicitly created XML table space names will be Xyyynnnn, where yyy is derived from the first three bytes of the base table name (if the name is shorter than 3, yyy is padded | with X ). nnnn is a numeric string that will start at 0000 and be incremented by 1 until a unique number is found. ADDITIONAL KEYWORDS: SQLCREATE SQLALTER SQLXML COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM54015 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: Implicitly created XML table space names will be Xyyynnnn, where yyy is the first three bytes of the base table name. With PM54014, if the table name is shorter than three bytes, the implicitly created XML table space name will be padded with 'X' instead of '#'. For example,if we create table named 'T' which included an XML column, the implicitly created XML table space will be named XTXX0000 instead of XT##0000. This apar will not affect existing XML table space names. The approximate text is to be added to the DB2 SQL Reference manual. This text is subject to change. CREATE TABLE Naming convention for implicitly created XML objects: Implicitly created XML table space names will be Xyyynnnn, where yyy is derived from the first three bytes of the base table name (if the name is shorter than 3, yyy is padded | with X ). nnnn is a numeric string that will start at 0000 and be incremented by 1 until a unique number is found. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXICDX PM54015 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM54015 DSNXICDX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICDX LISTEND UK77130 COVER LETTER END UK77170 COVER LETTER START PROBLEM DESCRIPTION(S): PM40724 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the following * * built-in functions: * * * * 1. LTRIM * * 2. RTRIM * * 3. REPLACE * * 4. ROUND * * 5. STRIP * * 6. TRIM * * 7. TRUNCATE or TRUNC * **************************************************************** * PROBLEM DESCRIPTION: The following built-in functions are * 1 * being extended with this apar to accept * * optional parameters. * * * * 1. LTRIM * * 2. RTRIM * * 3. REPLACE * * 4. ROUND * * 5. TRUNCATE or TRUNC * * * * Also, the TRIM function is being * * introduced and documentation changes * * are needed for the STRIP function as a * * result of adding the new TRIM function. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. The following built-in functions are being extended to accept optional parameters in DB2 NFM (New Function Mode). LTRIM and RTRIM Extend the functions to accept a second (optional) parameter (trim-characters). REPLACE Extend the function to make the third parameter (replace-string) optional. If replace-string is not specified, the default is an empty string, and nothing replaces the string that is removed from the source string. ROUND Extend the function to make the second parameter (numeric-expression-1) optional and in the syntax diagram show zero above the line as the default. TRUNCATE or TRUNC Extend the function to make the second parameter (numeric-expression-1) optional and in the syntax diagram show zero above the line as the default. 2. Introduce a new built-in function, TRIM, which is very similar to the STRIP function which has been supported by DB2 for z/OS for several releases. A sourced function cannot be defined on the TRIM function. 3. Documentation changes are needed for the STRIP built-in function as a result of adding the new TRIM function. The details will be described under the TRIM function and the STRIP function will point to the description for the TRIM 1 function. 4. Correct the execution for an SQL statement that invokes the STRIP built-in function using a single multi-byte mixed data strip-character. Previously an SQLCODE -171 was returned for this kind of query. This apar is the enabling APAR for APAR PM38326, the pre- conditioning apar. Together, these two apars are extending the following built-in functions to accept optional parameters in DB2 NFM (New Function Mode). 1. LTRIM 2. RTRIM 3. REPLACE 4. ROUND 5. TRUNCATE or TRUNC Also, the TRIM function is being introduced. Please note. As a result of this apar, please note that documentation changes are being made to the "DB2 10 for z/OS SQL Reference" as well to further describe the use of these functions. Please reference the included ++HOLD, or the recently updated publication for details and specifics. ADDITIONAL KEYWORDS: SQLLTRIM SQLRTRIM SQLREPLACE SQLROUND SQLSTRIP SQLTRIM SQLTRUNCATE SQLCODE171 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM40724 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM40724 APAR/PTF text for additional information about why a REBIND is necessary. APAR PM38326 is the necessary pre-conditioning apar for this APAR. PM40724 corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character. 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. MULTSYS: PM40724 is an APAR that includes changes to support functional extensions to the existing built-in functions and to introduce a new built-in function that will be enabled once this APAR is applied in DB2 NFM (New Function Mode). Earlier, pre-conditioning APAR PM38326 was delivered. In a data sharing group, the pre-conditioning APAR should be applied to all members before applying this enabling APAR to any 1 member. The code change is enabled once this enabling APAR is applied. The functional extensions to the following existing built-in functions are enabled by APAR PM40724. 1. LTRIM 2. RTRIM 3. REPLACE 4. ROUND 5. STRIP 6. TRUNCATE The new built-in function called, TRIM, is introduced by APAR PM40724. This APAR also corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character. DOCUMENTATION: See PM40724 APAR/PTF text for additional information. PM40724 introduces the following changes to externals: LTRIM The LTRIM function removes bytes from the beginning of a string expression based on the content of a trim expression. >>--LTRIM--(--string-expression---+--------------------+-)->< '-,--trim-expression-' The LTRIM function removes all of the characters that are contained in trim-expression from the beginning of string-expression. The search is done by comparing the binary representation of each character (which consists of one or more bytes) in trim-expression to the bytes at the beginning of string-expression. If the string-expression is defined as FOR BIT DATA, the search is done by comparing each byte in trim-expression to the byte at the beginning of string-expression. string-expression An expression that specifies the source string. The argument must be an expression that returns a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. If string-expression is not FOR BIT DATA, trim-expression must not be FOR BIT DATA. trim-expression An expression that specifies the characters to remove from the 1 beginning of string-expression. The expression must return a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. The default for trim-expression depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. Otherwise, a single byte blank. For EBCDIC, X'40' represents a blank. If not EBCDIC, X'20' represents a blank. string-expression and trim-expression must have compatible data types. If string-expression and trim-expression have different CCSID sets, trim-expression is converted to the CCSID of string-expression. The result of the function depends on the data type of string-expression. VARCHAR if string-expression is a character string. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. VARGRAPHIC if string-expression is a graphic string. VARBINARY if string-expression is a binary string. The length attribute of the result is the same as the length attribute of string-expression. The actual length of the result for a character or binary string is the length of string-expression minus the number of bytes that are removed. The actual length of the result for a graphic string is the length (in the number of double byte characters) of string-expression minus the number of double byte characters removed. If all of the characters are removed, the result is an empty string (the length is zero). If any argument can be null, the result can be null; if any argument is null, the result is the null value. The CCSID of the result is the same as that of string-expression 1 Refer to LTRIM section in the DB2 10 for z/OS SQL Reference for more information. RTRIM The RTRIM function removes bytes from the end of a string expression based on the content of a trim expression. >>--RTRIM--(--string-expression---+--------------------+-)->< '-,--trim-expression-' The RTRIM function removes all of the characters contained in trim-expression from the end of string-expression. The search is done by comparing the binary representation of each character (which consists of one or more bytes) in trim-expression to the bytes at the end of string-expression. If the string-expression is defined as FOR BIT DATA, the search is done by comparing each byte in trim-expression to the byte at the end of string-expression. string-expression An expression that specifies the source string. The argument must be an expression that returns a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. If string-expression is not FOR BIT DATA, trim-expression must not be FOR BIT DATA. trim-expression An expression that specifies the characters to remove from the end of string-expression. The expression must return a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. The default for trim-expression depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. 1 Otherwise, a single byte blank. For EBCDIC, X'40' represents a blank. When not EBCDIC, X'20' represents a blank. string-expression and trim-expression must have compatible data types. If string-expression and trim-expression have different CCSID sets, trim-expression is converted to the CCSID of string-expression. The result of the function depends on the data type of string-expression. VARCHAR if string-expression is a character string. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. VARGRAPHIC if string-expression is a graphic string. VARBINARY if string-expression is a binary string. The length attribute of the result is the same as the length attribute of string-expression. The actual length of the result for a character or binary string is the length of string-expression minus the number of bytes removed. The actual length of the result for a graphic string is the length (in number of double byte characters) of string-expression minus the number of double byte characters removed. If all of the characters are removed, the result is an empty string (the length is zero). If any argument can be null, the result can be null; if any argument is null, the result is the null value. The CCSID of the result is the same as that of string-expression Refer to RTRIM section in the DB2 10 for z/OS SQL Reference for more information. REPLACE >>-REPLACE-(-source-string-,-search-string-+-----------------+-> ',-replace-string-' >-)->< replace-string An expression that specifies the replacement string. The expression must return a value that is a built-in character string, graphic string, or binary string data type that is not a LOB. The argument can also be a numeric data type. The numeric argument is implicitly cast to a VARCHAR data type. If replace-string is not specified or is an empty string, 1 nothing replaces the string that is removed from the source string. Refer to REPLACE section in the DB2 10 for z/OS SQL Reference for more information. ROUND .-,--0-------------------. >>-ROUND-(--numeric-expression-1-+------------------------+-)->< '-,-numeric-expression-2-' Refer to ROUND section in the DB2 10 for z/OS SQL Reference for more information. TRUNCATE or TRUNC .-,--0------------------. >>-+TRUNCATE-+-(-numeric-expression1-+-----------------------+-> '-TRUNC---' '-,-numeric-expression2-' >-)->< Refer to TRUNCATE section in the DB2 10 for z/OS SQL Reference for more information. STRIP The STRIP function is similar to the TRIM scalar function. Refer to TRIM section in the DB2 10 for z/OS SQL Reference for more information. TRIM The TRIM function removes bytes from the beginning, from the end, or from both the beginning and end of a string expression. >>--TRIM--(--+----------------------------------------+--> | .-BOTH-----. | '-+----------+--+----------------+--FROM-' |-B--------| '-trim-constant--' |-LEADING--| |-L--------| |-TRAILING-| '-T--------' >--string-expression---)-------------------------------->< The schema is SYSIBM. The first argument, if specified, indicates whether characters 1 are removed from the end or the beginning of the string. If the first argument is not specified, the characters are removed from both the end and the beginning of the string. trim-constant Specifies a constant that indicates the binary, SBCS, or DBCS character that is to be removed. If string-expression is a character string, trim-constant must be an SBCS or DBCS single-character (2 bytes) constant. If string-expression is a binary string, trim-constant must be a single-byte binary string constant. If string-expression is a DBCS graphic or DBCS-only string, trim-constant must be a graphic constant that consists of a single DBCS character. The default for trim-constant depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. Otherwise, a single byte blank. For EBCDIC, X'40' represents a blank. When not EBCDIC, X'20' represents a blank. string-expression An expression that returns a value that is a built-in character string data type, graphic data type, binary string data type, or numeric data type. string-expression must not be a LOB. If string-expression is numeric, it is cast to a character string before the function is evaluated. For more information about converting numeric to a character string, see VARCHAR. string-expression and trim-expression must have compatible data types. The data type of the result depends on the data type of string-expression: If string-expression is a character string data type, the result is VARCHAR. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. If string-expression is a graphic string data type, the result is VARGRAPHIC. 1 If string-expression is a binary string data type, the result is VARBINARY. The length attribute of the result is the same as the length attribute string-expression. The actual length of the result is the length of string-expression minus the number of characters removed. If all of the characters are removed, the result is an empty string. If string-expression can be null, the result can be null; if string-expression is null, the result is the null value. The CCSID of the result is the same as that of string-expression Example: Assume the host variable HELLO of type CHAR(9) has a value of 'Hello '. SELECT TRIM(:HELLO), TRIM(TRAILING FROM :HELLO) FROM SYSIBM.SYSDUMMY1 Results in 'Hello' and ' Hello' respectively. Example: Assume the host variable BALANCE of type CHAR(9) has a value of '000345.50'. SELECT TRIM(L '0' FROM :BALANCE) FROM SYSIBM.SYSDUMMY1 Results in '345.50' Refer to TRIM section in the DB2 10 for z/OS SQL Reference. ACTION: This PTF corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character. If after applying both apars PM38326 and PM40724, the failing query still returns an SQLCODE -171 or for a static query a rebind does not resolve the problem, one or more of the following actions may need to be performed depending on the makeup of the query. 1. Views. Regenerate views using the ALTER VIEW REGENERATE statement. 2. Materialized query tables (MQT). Drop and recreate the MQTs. 3. SQL table UDFs. Drop and recreate the UDFs. 4. SQL scalar UDFs. 1 Regenerate functions using the ALTER FUNCTION REGENERATE. statement. 5. SQL native procedures. Regenerate procedures using the ALTER PROCEDURE REGENERATE statement. 6. Row permissions and column masks. Regenerate using the ALTER PERMISSION REGENERATE or ALTER MASK REGENERATE statement. 7. Indexes with key expressions. Regenerate indexes using the ALTER INDEX REGENERATE statement. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHSMF2 PM40724 DSNXGSFN PM40724 DSNXOBFA PM40724 DSNXOBFF PM40724 DSNXOBF3 PM40724 DSNXOBF4 PM40724 DSNXODTR PM40724 DSNXOFN2 PM40724 DSNXOW2D PM40724 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM40724 DSNHSMF2 DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 DSNXODTR DSNXOFN2 DSNXOW2D THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHSMF2 DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 DSNXODTR DSNXOFN2 DSNXOW2D LISTEND UK77170 COVER LETTER END UK77227 COVER LETTER START PROBLEM DESCRIPTION(S): PM58616 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 users of remote BIND PACKAGE * * with bind option SQLERROR(CONTINUE) * 1 **************************************************************** * PROBLEM DESCRIPTION: After a RESOURCE UNAVAILABLE condition * * occurred at the target DB2 server * * during a remote BIND PACKAGE with bind * * options SQLERROR(CONTINUE) and EXPLAIN * * one of the following abends occurred: * * ABEND0C4 DSNXGRDS . DSNXESX +3B64 or * * ABEND0C4 DSNXGRDS . DSNXESX +3B6A * * * * Other DSNXESX abend offsets are * * possible depending on DB2 PTF * * maintenance level. * **************************************************************** * RECOMMENDATION: * **************************************************************** During a remote BIND PACKAGE with bind options SQLERROR ( CONTINUE ) and EXPLAIN , a RESOURCE UNAVAILABLE condition occurred during bind-time EXPLAIN processing when using the DB2 access path tables (e.g., PLAN_TABLE ). After the resource unavailable condition , one of the following abends occurred during the remote BIND process: ABEND0C4 RC00000038 DSNXGRDS . DSNXESX +3B64 or ABEND0C4 RC00000038 DSNXGRDS . DSNXESX +3B6A . Other DSNXESX abend offsets are possible depending on DB2 PTF maintenance level of csect DSNXESX. . The DSNXESX abend occurred during the remote BIND PACKAGE because after the 'resource unavailable' happened, DB2 did not properly terminate the BIND PACKAGE process. Instead, DB2 attempted to continue building a package as directed by specified bind option SQLERROR(CONTINUE), and the abend occurred because DB2 did not have a complete package to store. Even when SQLERROR(CONTINUE) is specified, this type of RESOURCE UNAVAILABLE error is an exception to SQLERROR(CONTINUE) behavior and is not an error that qualifies for continuing the BIND process; DB2 should "fail" the BIND instead and not attempt to build a package. . The abend can only occur when doing a remote BIND PACKAGE with bind option SQLERROR(CONTINUE). In addition to the bind option EXPLAIN, the abend may be possible when using other access path management bind options such as APCOMPARE , APRETAINDUP , APREUSE all of which use DB2 access path tables. The abend does not occur when using SQLERROR(NOPACKAGE) or when doing a local BIND PACKAGE. . You can avoid a repeat of the DSNXESX abend during the remote BIND PACKAGE by doing one of the following: (1) Use bind option SQLERROR(NOPACKAGE) instead of CONTINUE (2) Resolve the RESOURCE UNAVAILABLE condition that is described either by console messages displayed at the target remote DB2 subsystem whose location name is specified in the remote BIND PACKAGE command, or described in the job output for the remote BIND PACKAGE job. Afterwards, retry the remote BIND PACKAGE. 1 DB2 remote BIND PACKAGE process was changed to fail the BIND after RESOURCE UNAVAILABLE and not build a package even though SQLERROR(CONTINUE) is specified, just as is done when SQLERROR(NOPACKAGE) is specified. . Additional search keywords: OFFSET3B64 OFFSET3B6A DB2DDF AB0C4 00000038 DEADLOCK TIMEOUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58616 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXERBP PM58616 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58616 DSNXERBP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERBP LISTEND UK77227 COVER LETTER END UK77248 COVER LETTER START PROBLEM DESCRIPTION(S): PM56084 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the JCC Type 2 * * Driver (JCCT2ZOS) Limited Block Fetch. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses the following four * * issues for DB2 V10 z/OS users connected * * from the JCC Type 2 Driver when using * * Limited Block Fetch. * * * * 1. DB2 incorrectly issues an SQLCODE423 * * for a LOB Locator when a null LOB * * value is previously fetched. * * * * 2. Incorrect output happens when a not * * NULL XML column is fetched. * * * * 3. DB2 incorrectly issues an SQLCODE303 * * when the XML (binary XML) and LOB * * data types are fetched. * * * * 4. DB2 incorrectly returns * * non-progressiveStreaming for a LOB * * data type when a * * progressiveStreaming format is * * requested using a static SQLJ * 1 * statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** This apar addresses the following four issues for DB2 V10 z/OS users connected from the JCC Type 2 Driver (JCCT2ZOS) when using Limited Block Fetch. 1. DB2 incorrectly issues an SQLCODE423 for a LOB Locator when a NULL LOB value is previously fetched. This problem occurs when both progressiveStreaming and FullyMaterializeLobData are disabled for the JCC Type 2 Driver, and a NULL LOB value is previously fetched. When the first not NULL LOB value is retrieved and used through a LOB Locator, DB2 incorrectly issues an SQLCODE423 because it does not handle the LOB value and LOB Locator value properly.. 2. Incorrect output happens when a not NULL XML column is fetched. DB2 does not set the nullability information properly at bind time. This leads to an incorrect value written for the NULL byte when retrieving a not NULL XML column via Limited Block Fetch for the JCC Type 2 Driver. 3. DB2 incorrectly issues an SQLCODE303 when an XML (binary XML) and LOB data type are fetched. DB2 does not handle the data type conversion properly when both XML (binary XML) and LOB data are fetched with progressiveStreaming ON and FullyMaterialzeLobData OFF in the JCC Type 2 Driver Release 4 (JCCV4). 4. DB2 incorrectly returns non-progressiveStreaming for a LOB data type when a progressiveStreaming format is requested for a static SQLJ statement. A static SQLJ statement is used to fetch a LOB data type and non-progressiveStreaming is requested for LOB Locator format from a JCC Type 2 connection with Limited Block Fetch. The connection is reset using sqlj.runtime.ConnectionContext.KEEP_CONNECTION. If the same SQLJ statement is executed again, this time progressiveStreaming is requested for LOB data format if there is no COMMIT statement between these two SQLJ statements but DB2 returns the incorrect non-progressiveStreaming format. The code in DB2 has been modified to correct the four problems mentioned. Additional Keywords: JCCT2ZOS SQLCODE303 SQLCODE423 SQLLOB SQLXML SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM56084 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM56084: See PM56084 APAR/PTF text for additional information about why a REBIND is necessary. Please note that the second problem addressed by PM56084 is required to have the static application rebound. Incorrect output can occur when a not NULL XML column is fetched. DB2 does not set the nullability information properly at bind time which leads to an incorrect value written for the NULL byte when retrieving a not NULL XML column for the JCC Type 2 Driver with Limited Block Fetch. 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 PM38688: See PM38688 APAR/PTF text for additional information about why a REBIND is necessary. PM38688 corrects a problem of incorrect out when query contains EXCEPT and UNION 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 DSNXGOU2 PM56084 DSNXGRTM PM56084 DSNXROH2 PM56084 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56084 DSNXGOU2 DSNXGRTM DSNXROH2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGOU2 DSNXGRTM DSNXROH2 LISTEND UK77248 COVER LETTER END 1 UK77298 COVER LETTER START PROBLEM DESCRIPTION(S): PM56725 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: Excessive dataset open/close activity, * * resulting in increased CPU time for the * * DBM1 address space. * **************************************************************** * RECOMMENDATION: * **************************************************************** The deferred close process (responsible for closing excess data sets when DSMAX has been exceeded) builds a large candidate list which it may continue using for a long period of time (several hours). Since this list is ordered by last-referenced time at the time the list was built, and the closing of candidates does not check to see if the reference time has changed, the order of closing datasets becomes less and less an LRU process the longer the list remains active. This may result in incorrectly closing datasets which are currently being frequently accessed, rather than others which are not currently being used. This may be particularly noticable if the list is built while one type of workload is being run (e.g. overnight batch jobs) but is still being used while another type of workload is being run (e.g. daytime online transactions). The deferred close process has been modified to skip datasets on its candidate list which have been referenced since the time the list was built. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56725 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1DRN PM56725 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56725 DSNB1DRN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DRN LISTEND UK77298 COVER LETTER END UK77336 COVER LETTER START PROBLEM DESCRIPTION(S): PM46707 - **************************************************************** 1 * USERS AFFECTED: DB2 9 and 10 z/OS users of dynamic statement * * caching and lock timeout. * **************************************************************** * PROBLEM DESCRIPTION: ALTER TABLE ROTATE PARTITION does not * * wait for the expected amount of time * * and receives SQLCODE904 RC00E70081. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a DDL statement is run concurrently with DML statements and dynamic statement caching is in effect, the DDL statement does not honor the timeout multiplier value set in DDLTOX if the value is set to a valid number higher than 1, indicating a longer wait for the resource. Users may see SQLCODE -904 earlier than expected for DDL statements. The timeout factor for DDL statements has been taken into account when they are run concurrently with DML statements and dynamic statement caching is on, when users specify a valid value higher than 1 for ZPARM SPRMDDLTO. Additional Keywords: SQLCODE904 SQLALTER SQLCREATE SQLDROP SQLDYNSTMTCACHE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM46707 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEIST PM46707 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM46707 DSNXEIST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEIST LISTEND UK77336 COVER LETTER END UK77343 COVER LETTER START PROBLEM DESCRIPTION(S): PM56355 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: DB2 may favor regular index scan over * * range list index scan while range list * * index scan is a more efficient access * 1 * method for a query with data-dependent * * pagination. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may favor regular index scan over range list index scan while range list index scan is a more efficient access method for a query with data-dependent pagination. In particular, the optimizer may improperly favor regular index scan when the matching range of the range list index scan is a subset of the matching range of the regular index scan. For example, SELECT * FROM T1 WHERE C1>=1 AND (C1>1 OR (C1=1 AND C2>1)) ORDER BY C1,C2 OPTIMIZE FOR 20 ROWS; There is an index created on T1(C1,C2). For the above query, there is a candidate access path with regular index scan which can match the predicate "C1>=1" and a candidate access path with range list index scan which can match the predicates "C1>1" and "C1=1 AND C2>1". Range list index scan is more efficient than regular index scan because the matching range of the range list index scan is covered by the matching range of the regular index scan. But the optimizer may improperly prefer the regular index scan. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE SQLRANGELIST SQLOR Code has been modified to favor range list index scan over regular single index scan in the scenario described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56355 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM56355: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM56355 corrects a problem that DB2 may favor regular index scan over range list index scan while range list index scan is a more efficient access method for a query with data-dependent pagination. 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. DB2BIND: ***Action for PM55976: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM55976 corrects a problem in which the most appropriate index only access may not be selected. 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 PM52549: See PM52549 APAR/PTF text for additional information about why a REBIND is necessary. PM52549 corrects a problem of SQLCODE=-510 when doing a BIND/REBIND on a FOR UPDATE cursor and IN-list direct table access is attempted. 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 PM56355 DSNXOGBM PM56355 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56355 DSNXOCSC DSNXOGBM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCSC DSNXOGBM LISTEND UK77343 COVER LETTER END UK77373 COVER LETTER START PROBLEM DESCRIPTION(S): PM58772 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of LOAD FORMAT INTERNAL * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU256I - INVALID PARTITION * * SPECIFICATION and RC8 for a LOAD FORMAT * 1 * INTERNAL INTO TABLE PART x utility. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A LOAD FORMAT INTERNAL INTO TABLE PART x utility was run on a partitioned table space with table partitioning using an IDENTITY column as the partition by range key. The LOAD ended with RC8 issuing DSNU256I - INVALID PARTITION SPECIFICATION. The message was issued because there was no IDENTITYOVERRIDE specified and the IDENTITY column was part of the partitioning key. However, this is not a concern for FORMAT INTERNAL and can be ignored. The same problem can occur when a ROWID column is used as part of the partitioning key. Code has modified to avoid issuing the DSNU256I message for the aformentioned case. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58772 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 PM58772 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58772 DSNUROFL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUROFL LISTEND UK77373 COVER LETTER END UK77375 COVER LETTER START PROBLEM DESCRIPTION(S): PM58497 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of EXPLAIN or the * * WITH EXPLAIN option in a CREATE FUNCTION * * or CREATE PROCEDURE statement. * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes a problem where an * * abend may occur during EXPLAIN: * * * * ABEND0C4 RC00000038 in DSNXOSUD +03CE * * * * This APAR also fixes a problem where * * EXPLAIN output may be missing when the * * WITH EXPLAIN option is specified on a * * CREATE FUNCTION or CREATE PROCEDURE * * statement. * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** This APAR fixes a problem where an abend may occur during EXPLAIN: ABEND0C4 RC00000038 in DSNXOSUD +03CE This APAR also fixes a problem where EXPLAIN output may be missing when the WITH EXPLAIN option is specified on a CREATE FUNCTION or CREATE PROCEDURE statement. Example statements are shown below: CREATE FUNCTION UDF_EMPNM ( EMPNO CHAR(6) ) RETURNS VARCHAR(12) LANGUAGE SQL CONTAINS SQL NO EXTERNAL ACTION DETERMINISTIC WITH EXPLAIN RETURN ( SELECT A.FIRSTNME FROM DSN81010.EMP A WHERE A.EMPNO = UDF_EMPNM.EMPNO ) CREATE PROCEDURE PRC_EMPNM () LANGUAGE SQL WITH EXPLAIN RETURN ( SELECT 1 FROM DSN81010.EMP A WHERE A.EMPNO = 2) The abend was caused by accessing invalid storage. The missing EXPLAIN output was caused by not handling the statement properly. Additional keywords: ABEND0C4 RC00000038 OFFSET03CE SQLEXPLAIN SQLUDF SQLNATIVESQLPL DB2 code has now been changed to fix the problems and avoid the abend. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58497 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOASG PM58497 DSNXOOP PM58497 DSNXOTS PM58497 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58497 DSNXOASG DSNXOOP DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXOASG DSNXOOP DSNXOTS LISTEND UK77375 COVER LETTER END UK77398 COVER LETTER START PROBLEM DESCRIPTION(S): PM57643 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of IBM * * DB2 Analytics Accelerator. * **************************************************************** * PROBLEM DESCRIPTION: A DB2 for z/OS system receives the * * following abend during a query offload: * * . ABEND0C4-00000004 DSNLXRSQ+5596 when * * DB2 9 for z/OS * * . ABEND0C4-00000004 DSNLXRSQ+5622 when * * DB2 10 for z/OS * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 z/OS application executes a query which is offloaded to the IBM DB2 Analytics Accelerator. Due to a user mis-configuration, the location name in the row defining the accelerator in the SYSACCEL.SYSACCELERATORS table was set to the local DB2 location instead of the accelerator's location. This eventually led to ABEND0C4-00000004 DSNLXRSQ+5596 for DB2 9, or a ABEND0C4-00000004 DSNLXRSQ+5622 for DB2 10, when DB2 tried to offload the query. DB2 has changed the -START ACCEL command to detect when the location column in the SYSACCEL.SYSACCELERATORS table has been mis-configured with the local DB2 location name. DB2 will now prevent the accelerator from starting and will issue message DSNX880I - DSNX8EKG DDF CONNECT FAILED WITH RETURN CODE=8 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 defining 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 defining the accelerator in SYSACCEL.SYSACCELERATORS is a valid accelerator location name. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57643 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX8EKG PM57643 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57643 DSNX8EKG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX8EKG LISTEND UK77398 COVER LETTER END UK77407 COVER LETTER START PROBLEM DESCRIPTION(S): PM55788 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B at DSNXCEET+01A4 * * may occur when DB2 thread is cancelled. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a thread that requires LE environment within DB2 subsystem is cancelled ABEND 0C4 at DSNXCEET+01A4 may occur. The abend occurs when DB2 is attempting to free the un-freed LE 1 environment token that was left over due to the abnormal thread termination. DB2 code was changed to properly free LE token. ADDITIONAL KEYWORDS: SQLLE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55788 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXCEES PM55788 DSNXCEET PM55788 DSNXINIT PM55788 DSNXLEBS PM55788 DSNXLEDL PM55788 DSNXLEFS PM55788 DSNXLEGS PM55788 DSNXLEII PM55788 DSNXLELD PM55788 DSNXLEMS PM55788 DSNXLEPE PM55788 DSNXLESL PM55788 DSNXLEST PM55788 DSNXLETI PM55788 DSNXLEUE PM55788 DSNXRLE PM55788 DSNXRLEI PM55788 DSNXRLET PM55788 DSNXRLE9 PM55788 DSNXRLI9 PM55788 DSNXRLNU PM55788 DSNXRLT9 PM55788 DSNXRLU9 PM55788 DSNXRUFS PM55788 DSNXRUS9 PM55788 DSNXTERM PM55788 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55788 DSNXCEES DSNXCEET DSNXINIT DSNXLEBS DSNXLEDL DSNXLEFS DSNXLEGS DSNXLEII DSNXLELD DSNXLEMS DSNXLEPE DSNXLESL DSNXLEST DSNXLETI DSNXLEUE DSNXRLE DSNXRLEI DSNXRLET DSNXRLE9 DSNXRLI9 DSNXRLNU DSNXRLT9 DSNXRLU9 DSNXRUFS DSNXRUS9 DSNXTERM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXCEES DSNXCEET DSNXINIT DSNXLEBS DSNXLEDL DSNXLEFS DSNXLEGS 1 DSNXLEII DSNXLELD DSNXLEMS DSNXLEPE DSNXLESL DSNXLEST DSNXLETI DSNXLEUE DSNXRLE DSNXRLEI DSNXRLET DSNXRLE9 DSNXRLI9 DSNXRLNU DSNXRLT9 DSNXRLU9 DSNXRUFS DSNXRUS9 DSNXTERM LISTEND UK77407 COVER LETTER END UK77452 COVER LETTER START PROBLEM DESCRIPTION(S): PM56677 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS RUNSTATS or inline * * STATISTICS utility users * * collecting index statistics. * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT cardinalities in SYSCOLDIST * * catalog table. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** When the user migrated to DB2 10 CM mode, the key cardinality statistics collected in SYSCOLDIST catalog table were incorrect. The default KEYCARD processing incorrectly gathered the keycard statistics and reported those statistics in MSGDSNU616I. The SYSIBM.SYSCOLDIST catalog table was updated with those incorrect statistics. This problem can also occur during inline STATISTICS collection of index statistics. Code was modified to correctly gather the key cardinalities during default index statistics processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56677 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 DSNUSIIX PM56677 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56677 DSNUSIIX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSIIX LISTEND UK77452 COVER LETTER END UK77461 COVER LETTER START PROBLEM DESCRIPTION(S): PM54590 - **************************************************************** * USERS AFFECTED: All DB2 z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E80150 occurred when a * * corrupted load module was used in DB2 * * startup. However, register 9 at the * * time of the abend does not contain the * * pointer to the corrupted load module * * name as documented in the DB2 Codes * * manual. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an ABEND04E RC00E80150 is issued by DSNYSIRM, register 9 does not point to the address of the name of the failing load module. DB2 Codes indicates that as a diagnostic aid, register 9 should point to the failing load module name. Module DSNYSIRM has been updated so register 9 contains the address of a field that holds the failing load module name. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM54590 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNYSIRM PM54590 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM54590 DSNYSIRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNYSIRM 1 LISTEND UK77461 COVER LETTER END UK77462 COVER LETTER START PROBLEM DESCRIPTION(S): PM54615 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of workfiles in * * applications that run concurrently with DDL * * against a workfile table space (CREATE * * TABLESPACE or DROP TABLESPACE) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIBCTD ERQUAL5007 * * on an application using workfiles (not * * DGTT), when some DDL on a workfile * * table space is running concurrently * * from the same data sharing member (or * * in non-data sharing) * **************************************************************** * RECOMMENDATION: * **************************************************************** The aforementioned abend occurred because an application was in the middle of allocating a workfile, yet some concurrent DDL on a workfile table space was being run, which deleted the internal WACT table. The abending application abended during the OBD create path because a garbage DBID was passed to DBDM. The garbage DBID was picked up because the code thought it was accessing a valid WACT when it really was not (WACT did not exist so the pointer to WACT was zero). Code has been changed to save the DBID value earlier in the path instead of relying on the internal WACT table to get the DBID from. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM54615 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWKFL PM54615 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM54615 DSNIWKFL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWKFL LISTEND UK77462 COVER LETTER END 1UK77494 COVER LETTER START PROBLEM DESCRIPTION(S): PM59942 - **************************************************************** * USERS AFFECTED: Users of the LIKE predicate in DB2 for z/OS * * V10.1. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE132 is returned for a nested * * CONCAT operator used in the LIKE * * predicate. * * The precompiler returns message * * DSNH132I for the same syntax. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following illustrates the problem: For the following two queries, DB2 returns SQLCODE -132: SELECT COL1 FROM T1 WHERE COL2 LIKE CONCAT('A',CONCAT('B','%')); SELECT COL1 FROM T1 WHERE COL2 LIKE CONCAT('A',CHAR('%')); SQLCODE = -132, ERROR: AN OPERAND OF LIKE IS NOT VALID SQLSTATE = 42824 SQLSTATE RETURN CODE SQLERRP = DSNHSM2P SQL PROCEDURE DETECTING ERROR There is a rule that the pattern-expression in the LIKE predicate must not contain a nested function invocation, but CONCAT should be treated as an operator, not as a function invocation, and therefore SQLCODE -132 should not be issued for the above queries. The following query receives SQLCODE132 because of the nested function invocation in the LIKE predicate, which is correct, and will not be changed by this APAR: SELECT COL1 FROM T1 WHERE COL2 LIKE MYUDF1(MYUDF2('B'),1); Additional keywords: MSGDSNH132I SQLCODE132 DB2 code is corrected so that SQLCODE -132 is no longer issued for a nested CONCAT in the pattern-expression of the LIKE predicate. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59942 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHSM2P PM59942 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM59942 DSNHSM2P THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHSM2P LISTEND UK77494 COVER LETTER END UK77496 COVER LETTER START PROBLEM DESCRIPTION(S): PM57162 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: Excessive DSNB260I messages for a * * client that is no longer active * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 thread is started and this thread is to remain active. Then a client that utilizes this DB2 thread is executed. After the threshold for readers holding claims has been reached, a DSNB260I message was displayed on the console log. However, the DSNB260I messages continued to be displayed even after the client that utilized the DB2 thread has been stopped. Further investigation shows that the DB2 thread still holds read claims on a catalog index - in this case, DSNDB06.DSNAPH01 (an index of SYSIBM.SYSPLANAUTH). DB2 was modified to ensure all claims on a Universal Table SPACE (UTS) and its index are released when the UTS is unlocked prior to commit. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57162 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIPSUL PM57162 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57162 DSNIPSUL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIPSUL LISTEND UK77496 COVER LETTER END 1UK77501 COVER LETTER START PROBLEM DESCRIPTION(S): PM55458 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: A remote requester connecting to a * * DB2 9 for z/OS server results in * * ABEND0C4-RC00000004 DSNXELX+0312 * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote requester connects to a DB2 9 for z/OS server. During the connection process, the DB2 server thread terminates with ABEND0C4-RC00000004 DSNXELX+0312 due to an incorrectly initialized internal control block. DB2 has been changed to correctly initialize the internal control block. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55458 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXALC PM55458 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55458 DSNLXALC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXALC LISTEND UK77501 COVER LETTER END UK77512 COVER LETTER START PROBLEM DESCRIPTION(S): PM58179 - **************************************************************** * USERS AFFECTED: All users of the DSNTXTA REXX exec and job * * DSNTIJXA in * * * DB2 UDB for z/OS Version 8 * * * DB2 Version 9.1 for z/OS * * * DB2 10 for z/OS * * are affected by this change. * **************************************************************** * PROBLEM DESCRIPTION: Job DSNTIJXA job step DSNTXTA ends with * * return code 8 due to SQLCODE +100 in * * standardizeDSN_FUNCTION_TABLE routine. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 DB2 REXX exec DSNTXTA can be used to alter all explain tables in a specified schema into current release format, meaning that they have all columns supported in the release and that all columns have the appropriate data type and length. Sample job DSNTIJXA shows how to execute DSNTXTA. Currently, DSNTXTA ends with return code 8 and the following messages when the schema specified for processing does not contain a DSN_FUNCTION_TABLE table. ** Error SQL statement - standardizeDSN_FUNCTION_TABLE: FETCH FROM C3 SQLCODE =100 SQLERRMC= SQLERRP =DSNXRFF SQLERRD =-110,0,0,-1,0,0 SQLWARN = , , , , , , , , , , SQLSTATE=02000 In response, DSNTXTA is modified to handle the SQLCODE +100 so that processing of other explain tables can continue. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58179 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTXTA PM58179 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58179 DSNTXTA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTXTA LISTEND UK77512 COVER LETTER END UK77517 COVER LETTER START PROBLEM DESCRIPTION(S): PM56256 - **************************************************************** * USERS AFFECTED: Users of external SQL procedures on DB2 10 * * for z/OS. All users of the DB2 SQL * * Procedure Processor DSNTPSMP. * **************************************************************** * PROBLEM DESCRIPTION: Deployment of an external SQL Procedure * * on DB2 10 for z/OS running in CM8 mode * * and using the DB2 SQL procedure * * processor DSNTPSMP fails with SQLCODE * * -20283. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** The build of an external SQL procedure on DB2 10 for z/OS fails with SQLCODE -20283 when using the DB2 SQL procedure processor DSNTPSMP. The problem occurs when DB2 is running in CM8 mode and the caller of DSNTPSMP, such as Data Studio, has set the CURRENT SCHEMA register. Additional keywords: SQLPL SQLSTOREDPROC SQLPROC SQLCODE20283 The DB2 SQL procedure processor DSNTPSMP is updated on V10 to avoid SQLCODE -20283 when the DB2 server is running in CM8 mode. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56256 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTPSMP PM56256 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56256 DSNTPSMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTPSMP LISTEND UK77517 COVER LETTER END UK77552 COVER LETTER START PROBLEM DESCRIPTION(S): PM59833 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 z/OS users of subqueries. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may select an inefficient access * * path for a query with a subquery * * having multiple-table join when * * subsystem parameter OPTXQB is ON. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may select an inefficient access path for a query with a subquery when subsystem parameter OPTXQB is ON and the subquery contains multiple-table join. ON is the default setting for OPTXQB. The problem was caused by improper variable reinitialization. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE SQLSUBQUERY SQLGLOBALOPT 1 Code has been modified to reinitialize the variables correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59833 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM59833: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM59833 corrects a problem that DB2 may select an inefficient access path for a query with a subquery having multiple-table join when subsystem parameter OPTXQB is ON. 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 PM55941: See PM55941 APAR/PTF text for additional information about why a REBIND is necessary. PM55941 corrects a problem of a query with OPTIMIZE FOR n ROWS or FETCH FIRST n ROWS ONLY where DB2 chooses the non-correlated subquery access path instead of the correlated subquery 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 DSNXOCS PM59833 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59833 DSNXOCS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCS LISTEND UK77552 COVER LETTER END UK77557 COVER LETTER START PROBLEM DESCRIPTION(S): PM57820 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 * 1 * z/OS users who uses complex * * statement with a large number * * of predicates * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -101 with return code * * RC00E20002 may be issued * * for a complex SQL statement * * which contains a large number * * of predicates because numerous * * SPACEBLK are allocated by * * DSNXOPRU and they are not * * deallocated. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -101 with return code RC00E20002 may be issued for a complex SQ L statement which contains a large number of predicates because numerous SPACEBLK are allocated by DSNXOPRU and they are not deallocated. DB2 issued SQLCODE -101 because it ran out of storage. DB2 was fixed to free the storage thus eliminate SQLCODE -101. Additional Keywords: SQLSTOR SQLPRUN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57820 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPRU PM57820 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57820 DSNXOPRU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRU LISTEND UK77557 COVER LETTER END UK77559 COVER LETTER START PROBLEM DESCRIPTION(S): PM59756 - **************************************************************** * USERS AFFECTED: All DB2 z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC 11 occurred in module * * DSN3RRSM while it was processing a * 1 * RRSAF Only Agent exit. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC 11 occurred in module DSN3RRSM while it was processing a RRSAF Only Agent exit. Module DSN3RRSM obtained an invalid EB when trying to process the exit. This affects DB2 RRSAF connected applications which are only using DB2 resources when they invoke a z/OS RRS coordinated commit. Module DSNRUB01, DSN3SQLF and DSN3RRSM have been updated to avoid the ABEND0C4 in DSN3RRSM. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59756 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRUB01 PM59756 DSN3RRSM PM59756 DSN3SQLF PM59756 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59756 DSNRUB01 DSN3RRSM DSN3SQLF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRUB01 DSN3RRSM DSN3SQLF LISTEND UK77559 COVER LETTER END UK77567 COVER LETTER START PROBLEM DESCRIPTION(S): PM58749 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the DB2 stored procedure * * SYSPROC.ADMIN_COMMAND_UNIX * **************************************************************** * PROBLEM DESCRIPTION: The stored procedure * * SYSPROC.ADMIN_COMMAND_UNIX failed * * with the following error message: * * DSNA626I DSNADMCU THE chdir() * * FUNCTION CALL IS UNSUCCESSFUL, * * DIRECTORY=, EDC5129I No such file * * or directory. (errno2=0x0594004D) * * although the specified user has * * a home directory. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** 1 The stored procedure SYSPROC.ADMIN_COMMAND_UNIX calls the C function getpwuid(uid), to get the home directory of a user whose user ID=uid. Since multiple user names can share the same user ID (uid) but maintain different home directories, the intended home directory may not be used. When the home directory of the specified user is not found or the specified user does not have a home directory, ADMIN_COMMAND_UNIX aborts. To get the home directory of the specified user, the C function getpwnam() is called, instead of getpwuid(). This allows SYSPROC.ADMIN_COMMAND_UNIX to always use the home directory of the specified user, rather than using the the home directory of a random user who happens to share the UID of the specified user. In order for ADMIN_COMMAND_UNIX to continue processing even though the home directory of the specified user does not exist or the specified user does not have a home directory, the stored procedure caller can specify a default home directory. To minimize the impact to existing users, ADMIN_COMMAND_UNIX extends the use of the existing OUTPUT_LAYOUT input parameter to specify the default home directory with the new keyword DEFAULT_HOME_DIR, which has the following syntax: DEFAULT_HOME_DIR=home_directory where home_directory is the default home directory. The maximum length of home_directory is 1007. Currently, the following strings are valid OUTPUT_LAYOUT values: o OUTMODE=LINE o OUTMODE=BLK If both OUTMODE and DEFAULT_HOME_DIR must be specified, they can be specified as follows: OUTMODE=LINE,DEFAULT_HOME_DIR=/tmp or DEFAULT_HOME_DIR=/tmp,OUTMODE=LINE If ADMIN_COMMAND_UNIX switches to the default home directory, (e.g., /tmp), it returns RETURN_CODE = 4 to warn the user that the default home directory is used. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58749 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58749 (DB2 10 for z/OS) This PTF modifies the stored procedure SYSPROC.ADMIN_COMMAND_UNIX to execute the specified z/OS UNIX System Services command in the home directory of the specified user, instead of the home directory of a user who happened to share the same UID as the specified user. 1 Therefore, for users that called ADMIN_COMMAND_UNIX specifying a user with a unique UID, the outcome of the command is the same as before this PTF is applied. However, for users that called ADMIN_COMMAND_UNIX specifying a user with shared UIDs, the command outcome depends on whether the home directory of the shared UID is also the home directory of the specified user: o If the home directory of the shared UID is also the home directory of the specified user, the command outcome is the same as before this PTF is applied. o Otherwise, the command is executed under the home directory of the specified user, instead of the home directory of the shared UID. This PTF also modifies the stored procedure SYSPROC.ADMIN_COMMAND_UNIX to allow the user to specify a default home directory in the input parameter OUTPUT_LAYOUT. Instead of aborting when the home directory of the specified user does not exist or the specified user does not have a home directory, ADMIN_COMMAND_UNIX will execute the specified command in the default home directory specified. If this happens, ADMIN_COMMAND_UNIX will return RETURN_CODE = 4 to warn the user that the default home directory is used. See the PTF cover letter for more information. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMCU PM58749 DSNADMCU PM58749 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58749 DSN@DMCU DSNADMCU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMCU MACROS DSN@DMCU LISTEND UK77567 COVER LETTER END UK77628 COVER LETTER START PROBLEM DESCRIPTION(S): PM58206 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of UNLOAD utility which uses a * * TEMPLATE to define the SYSREC data set. * **************************************************************** * PROBLEM DESCRIPTION: An UNLOAD utility which was using a * * TEMPLATE with option NBRSECND to define * * the SYSREC data set estimated excessive * 1 * secondary space allocation. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** An UNLOAD utility using a TEMPLATE with the PCTPRIME and NBRSECND option to define the SYSREC data set overestimated the secondary space allocation, which was equal to the primary quantity of the space requirement. This problem occurred because the UNLOAD utility estimated excessive space for the secondary quantity. The UNLOAD code has been modified to reduce the secondary space requirement. The UNLOAD utility estimates the space requirement for the SYSREC data set based on the statistics from catalog tables. A RUNSTATS against the target table space is recommended prior to the UNLOAD to ensure the accurate estimation for space requirement. This APAR also requires a documentation change in Utility Guide and Reference: Changed option for utility TEMPLATE: NBRSECND integer Specifies the division of secondary space allocations. After the primary space is allocated, an amount of space equal to the estimated required space is divided into the specified | number of secondary allocations. Individual utilities may | request larger secondary extents to compensate for localized | uncertainty in the space estimations. The integer value must be in the range from 1 to 10. The default value is 10. Changed text for utility TEMPLATE: Extent allocation for disk data sets By default, for data sets on disk, 100 percent of the required space that is estimated by DB2 is allocated as a primary quantity. If this amount of space is typically not available on a single volume, specify the PCTPRIME option with a value lower than 100. Alternatively, if you want the upper limit of the primary quantity based on size instead of percentage, use the MAXPRIME option. After the primary space is allocated, a secondary quantity that is equal to the estimated required space is divided into | the specified number of secondary extents. Individual | utilities may request larger secondary extents to compensate | for localized uncertainty in the space estimations. This number is identified by the NBRSECND option. If you specify either PCTPRIME or MAXPRIME, any secondary allocation requests are limited to the size of the primary allocation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58206 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 DOCUMENTATION: PM58206 introduces the following changes to externals: Changed option for utility TEMPLATE: NBRSECND integer Specifies the division of secondary space allocations. After the primary space is allocated, an amount of space equal to the estimated required space is divided into the specified | number of secondary allocations. Individual utilities may | request larger secondary extents to compensate for localized | uncertainty in the space estimations. The integer value must be in the range from 1 to 10. The default value is 10. Changed text for utility TEMPLATE: Extent allocation for disk data sets By default, for data sets on disk, 100 percent of the required space that is estimated by DB2 is allocated as a primary quantity. If this amount of space is typically not available on a single volume, specify the PCTPRIME option with a value lower than 100. Alternatively, if you want the upper limit of the primary quantity based on size instead of percentage, use the MAXPRIME option. After the primary space is allocated, a secondary quantity that is equal to the estimated required space is divided into | the specified number of secondary extents. Individual | utilities may request larger secondary extents to compensate | for localized uncertainty in the space estimations. This number is identified by the NBRSECND option. If you specify either PCTPRIME or MAXPRIME, any secondary allocation requests are limited to the size of the primary allocation. ACTION: *** Action for PM58206 *** The UNLOAD utility estimates the space requirement for the SYSREC data set based on the statistics from catalog tables. A RUNSTATS against the target table space is recommended prior to the UNLOAD to ensure the accurate estimation for space requirement. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUULDB PM58206 DSNUULPB PM58206 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58206 DSNUULDB DSNUULPB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULDB DSNUULPB LISTEND UK77628 COVER LETTER END 1 UK77652 COVER LETTER START PROBLEM DESCRIPTION(S): PM53042 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 users of CP parallelism. * **************************************************************** * PROBLEM DESCRIPTION: Insufficient information present in * * dumps while diagnosing CP parallelism- * * related problems. * **************************************************************** * RECOMMENDATION: * **************************************************************** Insufficient information present in dumps while diagnosing CP parallelism-related problems. Code has been added to enhance serviceability in the CP parallelism area. Additional Keywords: SQLCPUP SQLPARALLELISM SQLCPUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53042 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTTTC PM53042 DSNTTTGC PM53042 DSNXECLN PM53042 DSNXEUFP PM53042 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53042 DSNTTTC DSNTTTGC DSNXECLN DSNXEUFP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTTTC DSNTTTGC DSNXECLN DSNXEUFP LISTEND UK77652 COVER LETTER END UK77691 COVER LETTER START PROBLEM DESCRIPTION(S): PM59485 - **************************************************************** * USERS AFFECTED: DB2 V10 users. * **************************************************************** * PROBLEM DESCRIPTION: Adjust dataset allocation * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 Adjust dataset allocation COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59485 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNALLOC PM59485 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59485 DSNALLOC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNALLOC LISTEND UK77691 COVER LETTER END UK77693 COVER LETTER START PROBLEM DESCRIPTION(S): PM59950 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who using * * UPDATE ... WHERE CURRENT OF. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC38 at DSNXGTRE+0346 may * * occur on UPDATE WHERE CURRENT OF * * if the SET clause contains a CASE * * expression with an EXISTS subquery * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC38 at DSNXGTRE+0346 on UPDATE WHERE CURRENT OF may occur if the SET clause of the UPDATE contains a CASE expression with an EXISTS subquery. A plan may not be built for the query block containing the EXISTS subquery, which leads to the abend. Additional Keywords: SQLUPDATE WCO SQLCASE SQLEXISTS SQLSUBQUERY Code is changed to allow the plan for the EXISTS subquery to be built. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59950 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM52694 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. 1 PM52694 fixes a query costing problem when the query has outer join and FETCH FIRST n ROWS ONLY or OPTIMIZE FOR n ROWS. 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 PM59950 DSNXOPB PM59950 DSNXOPCO PM59950 DSNXOPLM PM59950 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59950 DSNXOGP DSNXOPB DSNXOPCO DSNXOPLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGP DSNXOPB DSNXOPCO DSNXOPLM LISTEND UK77693 COVER LETTER END UK77697 COVER LETTER START PROBLEM DESCRIPTION(S): PM53033 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who utilize BIND * * QUERY command with LOB_INLINE_LENGTH * * zparm having a non-zero value. * **************************************************************** * PROBLEM DESCRIPTION: Sometimes ABEND 0C4 DSNISELL +79C * * may occur during the BIND QUERY process * * when IN-LINE LOBS are activated * * for the CLOB column of QUERY_TEXT in * * the DSN_USERQUERY_TABLE through * * setting zparm LOB_INLINE_LENGTH * * with a non-zero value. * **************************************************************** * RECOMMENDATION: Sometimes ABEND 0C4 DSNISELL +79C * * may occur during BIND QUERY process * * when IN-LINE LOBS are activated * * for the CLOB column, QUERY_TEXT in * * the DSN_USERQUERY_TABLE through * * setting zparm LOB_INLINE_LENGTH * * with a non-zero value. * * * * The DSN_USERQUERY_TABLE is a critical * * table used in the BIND QUERY process. * * DB2 expects a fixed format of the * 1 * table. It's important for the users * * to follow the steps documented in * * the DSNTESH sample file to create * * the table. * **************************************************************** Sometimes ABEND0C4 RC04 in DSNISELL +79C may occur during BIND QUERY when IN-LINE LOBS are activated for the CLOB column of QUERY_TEXT in the DSN_USERQUERY_TABLE through setting subsystem parameter LOB_INLINE_LENGTH to a non-zero value. The abend occurs because DB2 enforces a fixed format of the DSN_USERQUERY_TABLE used in the BIND QUERY process. The inline LOB was not expected by DB2 for the QUERY_TEXT column. Additional Keywords: ABEND0C4 RC04 The abend described above is fixed by the APAR by tolerating both INLINE CLOB and non-INLINE CLOB format for the QUERY_TEXT column of the DSN_USERQUERY_TABLE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53033 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 PM53033 DSNXOD0Z PM53033 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53033 DSNXOBNQ DSNXOD0Z THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBNQ DSNXOD0Z LISTEND UK77697 COVER LETTER END UK77704 COVER LETTER START PROBLEM DESCRIPTION(S): PM57734 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Full Outer * * Join. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 from DSNXRRP * * location M700 can occur for a query * * using full outer join. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 from DSNXRRP location M700 can occur for 1 a query using full outer join if the outer table encounters an end-of-file (EOF) condition before the inner table. The abend occurs because DB2 does not handle an internal sanity check properly. The following query is an example of the kind of query that could result in this failure. SELECT A.C1, X.C1 FROM T1 X FULL OUTER JOIN T2 A ON X.C1 = A.C1 WHERE A.C1 IS NULL OR X.C1 IS NULL; The code in DB2 is modified to handle the internal sanity check correctly. ADDITIONAL KEYWORDS: SQLOUTERJOIN SQLCODE100 SQLFULLJOIN SQLOUTER SQLFULL SQLJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57734 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRRP PM57734 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57734 DSNXRRP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRRP LISTEND UK77704 COVER LETTER END UK77705 COVER LETTER START PROBLEM DESCRIPTION(S): PM53327 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the DB2 stored procedure * * SYSPROC.ADMIN_INFO_SYSLOG * **************************************************************** * PROBLEM DESCRIPTION: SYSPROC.ADMIN_INFO_SYSLOG is flooding * * the dynamic statement cache with SQL * * statements invoking DB2 functions * * like TIME, HOUR, MINUTE, SECOND, * * DATE, YEAR, MONTH, DAY, and DAYOFYEAR * * when it is called repeatedly. * * * 1 * Sample SQL statements flooding the * * dynamic statement cache: * * SELECT (TIME('08.15.14') * * - TIME('08.15.14')) * * FROM SYSIBM.SYSDUMMY1 * * SELECT (HOUR('08.15.14')) * * FROM SYSIBM.SYSDUMMY1 * * SELECT (MINUTE('08.15.14')) * * FROM SYSIBM.SYSDUMMY1 * * SELECT (SECOND('08.15.14')) * * FROM SYSIBM.SYSDUMMY1 * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** SYSPROC.ADMIN_INFO_SYSLOG issues dynamic SQL statements invoking DB2 datetime-related functions to validate the START_DATE, START_TIME, END_DATE, and END_TIME input parameters and to extract the different parts of these DATE and TIME values. When the stored procedure is called repeatedly, these SQL statements flood the dynamic statement cache. SYSPROC.ADMIN_INFO_SYSLOG is modified to replace all dynamic SQL calls to DB2 datetime-related functions with REXX instructions and functions. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53327 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNADMIL PM53327 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53327 DSNADMIL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNADMIL LISTEND UK77705 COVER LETTER END UK77712 COVER LETTER START PROBLEM DESCRIPTION(S): PM59265 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of datetime * * arithmetic. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 at DSNXRBND +189A * * may occur for a query using datetime * * arithmetic in an 'OR' predicate. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000004 at DSNXRBND +189A may occur for a query with datetime arithmetic. The datetime arithmetic must be in a predicate which is part of an OR predicate for the problem to occur. The following example may cause the reported abend : CREATE TABLE T1(C1 TIMESTAMP); INSERT INTO T1 VALUES('2012-04-03-11.37.35.519649'); INSERT INTO T1 VALUES('2012-04-03-11.48.43.301871'); COMMIT; Using the following values for the host variables: '2012-04-03-11.37.35.519649' '2012-04-03-11.37.35.519649' '2012-04-03-11.48.43.301871' '2012-04-03-11.48.43.301871' SELECT * FROM T1 WHERE C1 BETWEEN (CAST(? AS TIMESTAMP) - 10 SECOND) AND (CAST(? AS TIMESTAMP) + 10 SECOND) OR C1 BETWEEN (CAST(? AS TIMESTAMP) - 10 SECOND) AND (CAST(? AS TIMESTAMP) + 10 SECOND); Please note: the abend may only occur when there is an OR predicate. The correct result should be: +----------------------------+ | C1 | +----------------------------+ 1_| 2012-04-03-11.37.35.519649 | 2_| 2012-04-03-11.48.43.301871 | +----------------------------+ DB2 code has been changed to fix ABEND0C4 RC00000004 at DSNXRBND +189A ADDITIONAL KEYWORDS :SQLOR SQLDATE SQLTIME SQLTIMESTAMP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59265 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM59265: See PM59265 APAR/PTF text for additional information about why a REBIND is necessary. PM59265 corrects a problem of ABEND0C4 RC00000004 IN DSNXRBND OFFSET189A 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 DSNXGSC2 PM59265 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59265 DSNXGSC2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSC2 LISTEND UK77712 COVER LETTER END UK77739 COVER LETTER START PROBLEM DESCRIPTION(S): PM57878 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XQuery * * constructor expressions. * **************************************************************** * PROBLEM DESCRIPTION: When the XQuery constructor * * expressions are nested in the FLWOR * * expression, the performance can be * * improved. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the XQuery constructor expressions are nested in the FLWOR expression, the performance can be improved by deferring the construction of the XQuery constructor expressions after all the data has been evaluated and do the construction once. For example: In the following query, the element constructor for element node c is nested in the FLWOR expression. SELECT XMLQUERY( ' { for $a in $X/a/b return { $a } } ' PASSING XMLCOL AS X) FROM T1; Currently, DB2 will construct the element constructor for element node c in each loop when the return clause is evaluated. Assume that the FLWOR expression loops 10 times, then the element constructor for element node c will be 1 constructed 10 times. DB2 is modified to defer the construction until later when the XML data is referenced, so we can do the construction only once and improve performance. Additional keywords: SQLXML XMLXQUERY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57878 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 PM57878 DSNNOBSE PM57878 DSNNOBXI PM57878 DSNNOCCN PM57878 DSNNORCN PM57878 DSNNORES PM57878 DSNNORSQ PM57878 DSNNOSCO PM57878 DSNNOSER PM57878 DSNNOXMV PM57878 DSNNQFLR PM57878 DSNNQOB PM57878 DSNNQOPM PM57878 DSNNQTOP PM57878 DSNNQXCA PM57878 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57878 DSNNOBSC DSNNOBSE DSNNOBXI DSNNOCCN DSNNORCN DSNNORES DSNNORSQ DSNNOSCO DSNNOSER DSNNOXMV DSNNQFLR DSNNQOB DSNNQOPM DSNNQTOP DSNNQXCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOBSC DSNNOBSE DSNNOBXI DSNNOCCN DSNNORCN DSNNORES DSNNORSQ DSNNOSCO DSNNOSER DSNNOXMV DSNNQFLR DSNNQOB DSNNQOPM DSNNQTOP DSNNQXCA LISTEND UK77739 COVER LETTER END 1 UK77742 COVER LETTER START PROBLEM DESCRIPTION(S): PM58575 - **************************************************************** * USERS AFFECTED: All DB2 users who allow automatic rebind. * **************************************************************** * PROBLEM DESCRIPTION: When a package is being automatically * * rebound, autobind may deadlock with * * other DB2 internal service tasks on * * SYSIBM.SYSPACKAGE table. * **************************************************************** * RECOMMENDATION: * **************************************************************** Internally DB2 maintains a list of real time statistics (RTS) control blocks to keep track of the execution of packages. The RTS service task wakes up periodically to externalize the last used information to SYSIBM.SYSPACKAGE table. However, the automatic rebind process does not properly acquire an update lock before updating SYSIBM.SYSPACKAGE, which causes a deadlock with the process for collection of real time statistics. DB2 has been fixed to acquire an update lock on SYSIBM.SYSPACKAGE during the automatic rebind process. KEYWORDS: DEADLOCK, AUTOBIND COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58575 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 PM58575 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58575 DSNTBAB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBAB2 LISTEND UK77742 COVER LETTER END UK77745 COVER LETTER START PROBLEM DESCRIPTION(S): PM59280 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 users with "alias * * resolution enabled" for applications bound * * with REOPT bind option and that issue * * distributed dynamic SQL statements that * * specify an ALIAS to refer to remote objects * * at a remote Application Server (AS), where * * "alias resolution enabled" is defined as * 1 * follows: * * * * For DB2 9, * * DB2 subsystem parameter * * DSN6SPRM.DRDA_RESOLVE_ALIAS = YES * * * * For DB2 10, * * alias resolution enabled by default * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -104 issued by an Application * * Server (AS) for an inbound dynamic SQL * * statement that originally used an alias * * to refer to a remote table at that * * server. At the DB2 9 or 10 for z/OS * * Application Requester (AR) where the * * distributed dynamic SQL statement * * originated, * * - the application is bound with option * * REOPT(ONCE|AUTO|VARS|ALWAYS), and * * - "alias resolution enabled" * **************************************************************** * RECOMMENDATION: * **************************************************************** On a DB2 9 or 10 for z/OS Application Requester (AR) where alias resolution is enabled, an application bound with bind option REOPT( ONCE | AUTO | VAR | ALWAYS ) issued a distributed dynamic SQL statement that used an ALIAS to refer to a remote object at an Application Server (AS). At that target AS, the dynamic SQL statement failed with SQLCODE -104 during the prepare of the dynamic statement, and the SQLCODE104 was returned to the user application at the DB2 9 or 10 for z/OS AR. The target remote AS may or may not be a DB2 for z/OS AS. The dynamic statement should not have have failed with SQLCODE104. . Note that enabling alias resolution means that the DB2 AR should resolve any aliases specified in distributed SQL statements before the SQL statements are sent outbound to the target remote AS, so DB2 performs the alias resolution using values defined for that ALIAS at the DB2 AR, not at the target AS. So the DB2 AR modifies the outbound SQL statement text by replacing the alias with the associated DB2 AR defined value, therefore the alias is no longer part of the outbound statement text sent to the target AS and the alias is not resolved there. . The SQLCODE -104 occurred at the target remote AS because the DB2 9 or 10 for z/OS AR passed an incorrect CCSID to the target AS for this modified outbound dynamic SQL statement, when the DB2 AR application issuing the dynamic SQL statement is bound REOPT(ONCE|AUTO|VARS|ALWAYS). . This SQLCODE -104 failure when using aliases does not occur when either the DB2 AR application is bound REOPT( NONE ), which is the DB2 default, or when alias resolution is disabled. DB2 9 and 10 for z/OS AR code has been changed to pass the correct statement CCSID to the target remote AS for the dynamic SQL scenario described above. 1 . ************************************************************* * The PTF for PM59280 *must* be applied to the DB2 for z/OS * * Application Requester subsystem in order to resolve * * the SQLCODE104 that occurs at the target remote AS. * * There is no PTF change to apply to the target remote AS * * where the SQLCODE104 occurred. * ************************************************************* . Additional Search Keywords: SQLCODE104 SQLDRDA DB2DDF COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59280 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: *** Action for PM59280 *** This fix corrects a SQLCODE104 symptom observed at the server site (site2), but to correct the problem this fix must be applied to the DB2 for z/OS requester site (site1) where alias resolution is enabled. Review the PTF cover letter for further explanation of the requester (site1) applications that are affected. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEDP PM59280 DSNXEDS1 PM59280 DSNXEPM PM59280 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59280 DSNXEDP DSNXEDS1 DSNXEPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEDP DSNXEDS1 DSNXEPM LISTEND UK77745 COVER LETTER END UK77746 COVER LETTER START PROBLEM DESCRIPTION(S): PM53450 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where a DB2 10 for z/OS server * * is accessed by remote clients using SSL * * client (mutual) authentication. * **************************************************************** * PROBLEM DESCRIPTION: Additional enhancements to * * DB2 10 for z/OS digital certificate * * authentication support. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 for z/OS APAR/PTF PM37057/UK73180 provided additional enhancements to support remote clients accessing DB2 using digital certificates. In order for remote clients to utilize this kind of digital certificate authentication, the remote client system would need to present its user ID (at a minimum) in order to access DB2. However, there are some client drivers (such as IBM Data Server Driver for ODBC and CLI) that do not have the capability to support a user ID only security mechanism. Therefore, the IBM Data Server Driver clients will implement a new DRDA security mechanism that allows the remote client system to access DB2 using the SSL mutual authentication security protocol without the presence of a user ID and/or password. This APAR will provide the necessary support by DB2 to support this new digital certificate authentication method. DB2 10 for z/OS remote connection authentication processing has been enhanced to support the DRDA TLS Client Certificate Authentication Security (TLSCCASEC) mechanism for those remote client drivers that support it. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53450 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM37057 (V10): This APAR/PTF provides additional enhancements to the DB2 10 for z/OS support for client access using a digital certificate. DB2 10 for z/OS remote connection authentication processing has been enhanced to ensure remote client's that accesses DB2 using a digital certificate are properly authenticated when the remote client user ID is different from the certificate user ID. To implement client access to DB2 using a digital certificate, users need to define a trusted context at the DB2 server where the system authorization ID is set to the value of the user ID associated with the client certificate. The trusted context would need to include all the user IDs that are allowed to use it (such as, remote client user IDs or the mapped user IDs if z/OS identity name filtering is configured). Example: A client certificate is registered to RACF and it is associated with user ID, CERTID01. A remote client application is configured to access DB2 using a digital certificate and its user ID provided to DB2 is USER01. To define the trusted context at the DB2 server, users might consider the following sample DDL: CREATE TRUSTED CONTEXT CTXT1 BASED UPON CONNECTION USING CERTID01 NO DEFAULT ROLE ENABLE ATTRIBUTES(ADDRESS '1.2.3.4') WITH USE FOR USER01; 1 See PM37057 APAR/PTF text for additional information. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTSEC PM53450 DSNLZSAS PM53450 DSNLZSPA PM53450 DSNLZSR2 PM53450 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53450 DSNLTSEC DSNLZSAS DSNLZSPA DSNLZSR2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTSEC DSNLZSAS DSNLZSPA DSNLZSR2 LISTEND UK77746 COVER LETTER END UK77758 COVER LETTER START PROBLEM DESCRIPTION(S): PM56424 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * with queries containing multiple local * * predicates on the same column. * **************************************************************** * PROBLEM DESCRIPTION: DB2 does not recognize the relationship * * between multiple local predicates on * * the same column when computing * * atomic filter factors. * **************************************************************** * RECOMMENDATION: * **************************************************************** In certain cases, DB2 can use not equals or NOT IN local predicates to make the atomic filter factor on another local predicate more accurate. Consider the following query... SELECT COUNT(*) FROM T1 WHERE C1 = ? AND C1 <> 0 If the column cardinality of C1 is 100, DB2 determines that the filter factor of 'C1 = ?' is 1/100 = 1% without regard to frequency statistics. With this APAR, DB2 recognizes that a frequency statistic on column C1, value 0 can be excluded from the filter factor of 'C1 = ?'. All of the following conditions must be true for DB2 to 1 adjust the filter factor in this way. * The predicate to be adjusted must... * Be an equals or IN list predicate. * Contain only host variables or parameter markers. * The predicate that provides the value(s) to exclude must... * Be a not equals or NOT IN list predicate. * Contain only literal values with each value matching either a frequency statistic or a histogram statistic with cardinality 1. * Reference the same column as the predicate to be adjusted. This APAR also resolves a DB2 10 for z/OS only problem in which the atomic filter factor may be incorrectly calculated for a not equal or NOT IN predicate referencing a column with a null frequency or null histogram statistic. Additional keywords: SQLACCESSPATH SQLPERFORMANCE DB2 has been modified to provide more accurate filter factors in these specific scenarios. Additionally, the DB2 10 for z/OS only problem related to filter factor calculation for a not equals or NOT IN predicate referencing a column with a null frequency or null histogram statistic has been resolved. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56424 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM56424: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM56424 allows DB2 to more accurately estimate atomic predicate filter factors when multiple local predicates exist on the same column. PM56424 also resolves a problem in which the null frequency was not taken into account for not equal and NOT IN 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODF PM56424 DSNXODFE PM56424 DSNXODFT PM56424 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM56424 DSNXODF DSNXODFE DSNXODFT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODF DSNXODFE DSNXODFT LISTEND UK77758 COVER LETTER END UK77770 COVER LETTER START PROBLEM DESCRIPTION(S): PM58932 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of queries * * joining 3 or more tables. * **************************************************************** * PROBLEM DESCRIPTION: An inefficient join sequence may be * * chosen for a query joining 3 or more * * tables. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may select an inefficient join sequence for a query joining 3 or more tables. For example, DB2 may select a large table as the leading table while a more efficient join sequence is to choose a small table as the leading table which could provide join filtering to the large table. Additional Keywords: SQLACCESSSPATH SQLPERFORMANCE Code has been modified to improve DB2's ability to select a good join sequence for a query joining 3 or more tables. 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: PM58932 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 1 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 PM58932 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58932 DSNXOPKN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPKN LISTEND UK77770 COVER LETTER END UK77786 COVER LETTER START PROBLEM DESCRIPTION(S): PM59502 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of IN * * predicate. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at * * DSNXGRDS.DSNXGINB:M621 could occur when * * a SQL statement satisfies the following * * conditions: * * 1.It contains a IN predicate with * * standalone hostvar or parameter * * markers in the INLIST,left side * * column of IN predicate is nullable, * * 2.An internal IN predicate is generated * * by DB2 for the IN predicate describe * * in 1, * * 3.The internal generated IN predicate * * left side is not nullable, the length * * is longer than the original IN * * predicate left side. * * * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** ABEND04E RC00E70005 at DSNXGRDS.DSNXGINB:M621 could occur when a SQL statement satisfies the following conditions: 1.It contains a IN predicate with standalone hostvar or parameter markers in the INLIST,left side column of IN predicate is nullable, 2.An internal IN predicate is generated by DB2 for the IN predicate describe in 1, 3.The internal generated IN predicate left side is not nullable, the length is longer than the original IN predicate left side. The following example could recreate the abend: CREATE TABLE T1(C1 INTEGER , C2 VARCHAR(10)); CREATE TABLE T2(C3 INTEGER NOT NULL, C4 VARCHAR(18) NOT NULL); SELECT C4 FROM T1, T2 WHERE T1.C2=T2.C4 AND T1.C2 IN ( :HV,:HV, :HV); Since DB2 does not handle the internal generated transitive closure predicate correctly, it causes abend. DB2 is updated to handle the internal generated IN predicate correctly. Additional keywords: SQLIN SQLTRANSITIVE SQLPREDPUSHDOWN SQLHOSTVAR PARAMETERMARKER SQLPMARKER SQLPMK SQLNULL SQLNOTNULL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59502 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCAT PM59502 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59502 DSNXOCAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCAT LISTEND UK77786 COVER LETTER END UK77806 COVER LETTER START PROBLEM DESCRIPTION(S): PM58607 - NONE PM63585 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of CHECK INDEX * **************************************************************** 1 * PROBLEM DESCRIPTION: AE PM58607 fix completion * * * * CHECK INDEX failed to detect an * * inconsistency on a nonleaf page. * **************************************************************** * RECOMMENDATION: * **************************************************************** AE PM58607 fix completion CHECK INDEX verifies that the index keys are consistent with the data in the corresponding table space. It also performs some validation on the structure of the index itself. In the case of this APAR, CHECK INDEX failed to detect an inconsistency in the index. Completed fix for AE PM58607. Modified CHECK INDEX to detect certain inconsistencies in the index. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58607,PM63585 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKUSET PM58607 PM63585 DSNUKIKI PM58607 PM63585 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58607 DSNKUSET DSNUKIKI PM63585 DSNKUSET DSNUKIKI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKUSET DSNUKIKI LISTEND UK77806 COVER LETTER END UK77815 COVER LETTER START PROBLEM DESCRIPTION(S): PM53385 - **************************************************************** * USERS AFFECTED: All DB2 z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND30D occurred in module DSN3SSI2 * * and then an ABEND0C4 in DSNVCRTH * * occurred after a -STOP DB2 MODE(FORCE) * * command was entered. There was no * * prior -STOP DB2 MODE(QUIESCE) command * * before forcing DB2. * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** An ABEND30D occurred in module DSN3SSI2 and then an ABEND0C4 in DSNVCRTH occurred after a -STOP DB2 MODE(FORCE) command was entered. DB2 recovery for the ABEND30D ought to relocate the appropriate DB2 address space control block before proceeding with recovery processing. DSN3SSES has been updated to perform a new search for the DB2 address space control block. This will prevent the ABEND0C4 in module DSNVCRTH. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53385 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3SSES PM53385 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53385 DSN3SSES THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3SSES LISTEND UK77815 COVER LETTER END UK77831 COVER LETTER START PROBLEM DESCRIPTION(S): PM59638 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * native CREATE PROCEDURE command. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * -567 error message displayed an * * incorrect owner * * * * PROBLEM SCENARIO: * * * * The reported error occurred when * * attempting a CREATE PROCEDURE of a * * native stored procedure. A SET * * CURRENT SQLID was executed just prior * * to executing the CREATE PROCEDURE. * * The package owner did not have CREATEIN * * privilege. When the -567 error message * * displayed it had the SQLID instead of * * the package owner in the auth-id part * * of the message. * * * 1 * * * THIS IS THE ERROR MESSAGE FROM THE * * DOCUMENTATION * * * * -567 bind-type AUTHORIZATION ERROR * * USING auth-id AUTHORITY PACKAGE * * = package-name PRIVILEGE = privilege * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: DB2 was attempting an authority check of the SQLID owner when executing a native CREATE PROCEDURE. The package owner did not have the CREATEIN privilege, the SQLID owner did not have SYSADM, and a -567 error message was output. The variable which contains the package owner was overwritten by the previous SQLID auth check and never restored. As a result, the auth-id in the message was the SQLID instead of the package owner. EXAMPLE.... SET CURRENT SQLID = 'USRT002'! CREATE PROCEDURE USRT003.TESTIT (VARNAME VARCHAR(128), OUT VARCOUNT INTEGER) VERSION V1 ISOLATION LEVEL CS PACKAGE OWNER USRT003 ALLOW DEBUG MODE LANGUAGE SQL BEGIN SELECT COUNT(*) INTO VARCOUNT FROM SYSIBM.SYSDUMMY1; END ! RESULTED IN.... DSNT408I SQLCODE = -567, ERROR: REBIND AUTHORIZATION ERROR USING USRT002 AUTHORITY PACKAGE = STLEC1.USRT003.TESTIT.(V1) PRIVILEGE = CREATE IN PROBLEM CONCLUSION: DB2 has been fixed to restore the variable to the package owner and now the -567 error message will be correct. ADDITIONAL KEYWORDS: SQLCREATE SQLNATIVESQLPL SQLCODE567 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59638 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBSPL PM59638 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM59638 DSNTBSPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBSPL LISTEND UK77831 COVER LETTER END UK77857 COVER LETTER START PROBLEM DESCRIPTION(S): PM58732 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who * * are also using IDAA ( IBM DB2 Analytics * * Accelerator ) * **************************************************************** * PROBLEM DESCRIPTION: This APAR contains the following fixes * * for DB2 IDAA support: * * * * 1. Before this APAR, a query with at * * least one common table expression * * (CTE) and converted query length * * greater than 32K bytes would return * * SQLCODE -901 when offloaded to IDAA. * * * * 2.Before this APAR, a query with at * * least one UNION, UNION ALL, * * INTERSECT, INTERSECT ALL, EXCEPT, * * EXCEPT ALL with a SELECT list item * * that involves an aggregate function * * for a decimal, date, time, or * * timestamp result column would * * return SQLCODE -904 when offloaded to * * IDAA. * * * * 3. When user requests DB2 IDAA offload * * for a query run from a DB2 package * * that is bound REOPT(AUTO) and * * the query validly does not qualify * * for IDAA offload but is run in DB2 * * instead, the following DB2 application * * abend is possible during a second or * * later OPEN cursor when DB2 does an * * implicit reoptimization re-prepare of * * the query for the Dynamic Statement * * Cache: * * ABEND04E RC00E70005 at DSNXERT :P115 * * * * 4. When using DB2 DSNTEP4 to run * * dynamic SQL queries and user requested * * IDAA offload for those queries, and * * Dynamic Statement Caching is not * * active, the following SQL error * 1 * invalidly occurred: * * SQLCODE -249 SQLERRP = DSNLXRSQ * * * * 5. DB2 does not support IDAA offload * * for a dynamic SQL query that is * * on the same input line that begins * * with an SQL simple comment (--) * * and a linefeed is used to separate * * the SQL simple comment from the * * SQL query. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR contains the following fixes for DB2 IDAA offload support of queries: . 1. Before this APAR, a query with at least one common table expression (CTE) and converted query length greater than 32K bytes would return SQLCODE -901 when offloaded to IDAA. To determine the converted query length, EXPLAIN the query and select LENGTH(QI_DATA) from DSN_QUERYINFO_TABLE. . 2.Before this APAR, a query with at least one UNION, UNION ALL, INTERSECT, INTERSECT ALL, EXCEPT, EXCEPT ALL with a SELECT list item that involves an aggregate function for a decimal, date, time, or timestamp result column would return SQLCODE -904 when offloaded to IDAA. For a date, time or timestamp result column, the SQLCODE -904 is returned when offloaded to IDAA only if one of the SELECT list items invovles a constant. For example: SELECT MAX('02/24/2012') FROM T1 UNION ALL SELECT MAX(C15DATE) FROM T2; For a decimal result column, the SQLCODE -904 is always returned when offloaded to IDAA. For example: SELECT MAX(C8DECIMAL) FROM T1 UNION ALL SELECT MAX(C8DECIMAL) FROM T2; . 3. The user requested DB2 IDAA offload for a query from a DB2 package that is bound with bind option REOPT(AUTO) and DB2 Dynamic Statement Caching ( DSC ) is active. For whatever valid reason the query is not eligible for IDAA offload and is cached in the DSC and run in DB2 instead. During the second or later OPEN cursor for the query running in DB2, the following DB2 application abend is possible when DB2 does an implicit reoptimization re-prepare of the query for the DB2 DSC (due to the REOPT(AUTO) behavior): ABEND04E RC00E70005 at DSNXGRDS . DSNXERT :P115 1 The DB2 abend occurred because DB2 did not correctly handle the implicit reopt re-prepare for this query that was not offloaded to IDAA. This REOPT(AUTO) problem only occurs when the user has requested IDAA offload and DB2 validly does not offload the query. . 4. When using DB2 DSNTEP4 to run dynamic SQL queries and user requested IDAA offload for those queries, and Dynamic Statement Caching (DSC) is not active, the following SQL error occurred: DSNT408I SQLCODE = -249, ERROR: DEFINITION OF ROWSET ACCESS FOR CURSOR IS INCONSISTENT WITH THE FETCH ORIENTATION CLAUSE SPECIFIED DSNT418I SQLSTATE = 24523 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNLXRSQ SQL PROCEDURE DETECTING ERROR . This error is issued by DB2. The error does not occur when DSC is active. . DSNTEP4 default cursor behavior is ROWSET and 100 rows for a fetch. DB2 IDAA offload is not supported for ROWSET queries and multi-row fetching, so DB2 does not offload such queries (by design). Instead, DB2 runs the query in DB2. However, the query should not have failed with SQLCODE249 but should have run successfully in DB2. If DSC is active in this scenario, the query runs successfully. The SQLCODE249 occurred invalidly because, when DSC is not active DB2 did not correctly handle the ROWSET query and the SQLCODE249 resulted. It is not a TEP4 error or problem. . This SQLCODE249 can also occur if another application or vendor product attempted to run a query with ROWSET in this same IDAA offload request scenario. . 5. An SQL simple comment starts with the characters '--', and any characters that follow '--' on the same input line are considered as a comment, even if what follows is an SQL statement. However, if a linefeed character is embedded or used on that input line to separate the comment from the SQL statement specified, then the SQL statement is not considered part of the SQL simple comment. In this linefeed case, if that simple comment line is input for a dynamic SQL statement and the SQL statement specified is a query, DB2 does not consider the dynamic query for IDAA offload. 1. Code is fixed to offload a query with at least one CTE and converted query length greater than 32K bytes if there are no other restrictions preventing the query from offloading. . 2. Code is fixed to offload a query involving a UNION, UNION ALL, INTERSECT, INTERSECT ALL, EXCEPT, EXCEPT ALL with a SELECT list item that is a decimal, date, time, or timestamp result column. . 3. DB2 REOPT(AUTO) support was changed to correctly handle the DB2 implicit reoptimization re-prepare on OPEN for a query that did not qualify for DB2 IDAA offload. 1 . 4. DB2 was changed to correctly run a ROWSET query in DB2 when the user requested IDAA offload and Dynamic Statement Caching is not active. The ROWSET query is correctly *not* offloaded to IDAA. . 5. DB2 now supports IDAA offload for a dynamic SQL query that is on the same input line that begins with an SQL simple comment (--) and a linefeed is used to separate the SQL simple comment from the SQL query. . Additional Search Keywords: IDAAV2R1/K SQLCODE904 SQLCODE901 SQLUNION SQLUNIONALL SQLINTERSECT SQLINTERSECTALL SQLEXCEPT SQLEXCEPTALL REOPT AUTO SQLDYNSTMTCACHE AB04E OFFSETP115 00E70005 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58732 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEDP PM58732 DSNXONZC PM58732 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58732 DSNXEDP DSNXONZC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEDP DSNXONZC LISTEND UK77857 COVER LETTER END UK77865 COVER LETTER START PROBLEM DESCRIPTION(S): PM59283 - **************************************************************** * USERS AFFECTED: All DB2 users who run a package bound in * * V10. * **************************************************************** * PROBLEM DESCRIPTION: When cleaning up storage for a package * * an abend0c4 in DSNGEFSP could be * * received. * **************************************************************** * RECOMMENDATION: * **************************************************************** During the clean up for a package the abend ABEND0C4 in DSNGEFSP + 0B90 was received. The abend occurred because a latch was not held when internal control blocks were checked. The code has been updated to get the latch before checking the control blocks. 1 Additional keywords: +0B90 +B90 OFFSET0B90 OFFSETB90 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59283 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 PM59283 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59283 DSNGEFSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFSP LISTEND UK77865 COVER LETTER END UK77874 COVER LETTER START PROBLEM DESCRIPTION(S): PM58523 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users * * executing a REBIND on a package. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * DSNT226I message is received * * but the RC returns 0 instead of 4 * * * * * * PROBLEM SCENARIO: * * * * The reported error occurred when a * * customer was executing a REBIND on a * * package and noticed that the respective * * DSNT226I warning message was returning * * an RC = 0 instead of RC = 4. * * * * DSNT226I warning message... * * * * DSNT226I bind-type WARNING FOR * * object-type object-name. bind-option * * OPTION IS NOT RECOMMENDED WHEN * * BINDING PLANS OR PACKAGES * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: The variable in DB2, that holds the return code, was 1 inadvertently overwritten during internal processing. PROBLEM CONCLUSION: DB2 has been fixed to correctly set this variable and not overwrite it after it has been set. ADDITIONAL KEYWORDS: REBIND MSGDSNT226I COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58523 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Since the problem that occurred could leave incorrect RELEASE values in SYSIBM.SYSPACKAGE table, and the PTF only corrects problem in future rebinds, if there are packages that have been rebound prior to applying this PTF, and show a blank value in SYSPACKAGE.RELEASE column other than the intended RELEASE value, a manual REBIND with the correct RELEASE OPTION specified is required. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBCM5 PM58523 DSNTBRB2 PM58523 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58523 DSNTBCM5 DSNTBRB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBCM5 DSNTBRB2 LISTEND UK77874 COVER LETTER END UK77877 COVER LETTER START PROBLEM DESCRIPTION(S): PM58723 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM 220) and HIR2230 (IRLM230) * * users DATASHARING SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: Raise the limit of number of Lock Table * * Entries (LTEs) in the CF lock structure * * to the maximum (2G) supported by XES. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM limits the number of CF lock structure table entries (LTEs) to a maximum value of 1G. Since the maximum LTEs supported by XES is 2G, IRLM should not limit the LTEs and let it expand if the lock structure size could support a bigger lock table size. 1 IRLM may not be able to start if the lock structure size in the CFRM policy is set to a value greater than 4G. IRLM global initialization may timeout and ABENDU2025 in DXRRL732. MSGDXR133I is also issued by IRLM for global initialization timeout. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** IRLM will support up to 2G Lock Tables Entries for the CF lock structure. IRLM will also support lock structure SIZE/INITSIZE greater than 4G as specified in the CFRM policy for the lock structure. Following references in the DB2 books will be updated: 1. IRLM Messages and Codes: Explanation of DXR177I message F irlmproc,SET,TRACE=nnn LTE When nnnnnnnn is LTE, xxxx is a value between 0 and 2048 and represents the number of Lock Table Entries available in the Coupling Facility. The value must be either zero or a power of two with each increment representing 1048576 entries. 2. DB2 Commands Start irlmproc LTE= nnnn Specifies the number of lock table entries that are required in the units of 1048576 entries. LTE= can have a value of blank,zero, or any exact power of two up to 2048(inclusive). COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM58723 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL010 PM58723 DXRRL020 PM58723 DXRRL1S1 PM58723 DXRRL240 PM58723 DXRRL710 PM58723 DXRRL712 PM58723 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58723 DXRRL010 DXRRL020 DXRRL1S1 DXRRL240 DXRRL710 DXRRL712 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DXRRL010 DXRRL020 DXRRL1S1 DXRRL240 DXRRL710 DXRRL712 LISTEND UK77877 COVER LETTER END UK77883 COVER LETTER START PROBLEM DESCRIPTION(S): PM59506 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for * * z/OS who use DSNTEP2 or DSNTEP4 with the * * SQLTERM parameter. * **************************************************************** * PROBLEM DESCRIPTION: DSNTEP2 and DSNTEP4 do not correctly * * verify the SQLTERM parameter. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNTEP2 and DSNTEP4 are DB2 supplied PL/I sample application programs that can be used to perform dynamic SQL statement processing in the batch mode. Results are written to the SYSPRINT DD. Each input SQL statement needs to be ended with a terminator character. This character is a semicolon (';') by default. When the SQLTERM parameter is used to specify an alternate statement terminator, DSNTEP2 and DSNTEP4 do not correctly verify the specified value. This can result in: (1) DSNTEP2 or DSNTEP4 halting execution with a RC=8 and an error message indicating an invalid terminator character: DSNT499I ERROR IN INPUT PARAMETER LIST or (2) an invalid terminator character being treated as valid (results are unpredictable). This APAR modifies DSNTEP2 and DSNTEP4 to correctly verify the terminator character specified in a SQLTERM parameter. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59506 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM59506 (V10) (1) A DSNTEP2 or DSNTEP4 job that uses the parameter SQLTERM 1 to specify an invalid terminator character will need to be modified to specify a valid terminator character. Any character is valid except a blank, comma, single or double quote, underscore, or parenthesis. (2) This PTF updates the source code for DSNTEP2 and DSNTEP4 plus the shipped object decks (DSNTEP2L and DSNTEP4L) and shipped DBRMs (DSN@EP2L and DSN@EP4L). These changes do not become effective until you rebuild the load modules and rebind the plans. * On DB2 V10 systems running in conversion mode (CM) or enabling-new-function mode (ENFM), no further action is required after applying this PTF. The updates will be used when you run the V10 IVP jobs after DB2 V10 enters new-function mode. * On DB2 V10 systems in new-function mode, proceed as follows: (a) If you use DSNTEP2 or DSNTEP4 (or both) as supplied by DB2, run IVP job DSNTEJ1L to relink the load modules from the shipped object modules and bind the plans from the shipped DBRMs. (b) If you use a modified version of DSNTEP2 or DSNTEP4 (or both) redo your modifications and then run IVP job DSNTEJ1P to recompile and link-edit the load modules and bind the plans for DSNTEP2 and DSNTEP4. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@EP2L PM59506 DSN@EP4L PM59506 DSNTEP2 PM59506 DSNTEP2L PM59506 DSNTEP4 PM59506 DSNTEP4L PM59506 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59506 DSN@EP2L DSN@EP4L DSNTEP2 DSNTEP2L DSNTEP4 DSNTEP4L THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSN@EP2L DSN@EP4L DSNTEP2 DSNTEP2L DSNTEP4 DSNTEP4L LISTEND UK77883 COVER LETTER END UK77886 COVER LETTER START PROBLEM DESCRIPTION(S): PM58684 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users whose SQL * * contains outer join queries with a * * combination of OR and AND predicates. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 in DSNXGOJ may * * occur for outer join queries * * containing a combination of OR and AND * * predicates in DB2 V10. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000038 in DSNXGOJ may occur for outer join queries containing a combination of OR and AND predicates in V10. A sample query that fails looks like this: SELECT ... FROM T1 LEFT OUTER JOIN T2 ON (T1.C1=1 AND T2.C1=1) OR (T1.C1=2 AND T2.C1=2) Some predicates are generated incorrectly by predicate localization. This may result in the ABEND problem. Additional Keywords: SQLACCESSPATH SQLOR SQLAND ABEND0C4 SQLOUTER SQLOUTERJOIN Code has been changed to disable predicate localization for predicates in the ON clause of outer join queries. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58684 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPPD PM58684 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58684 DSNXOPPD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPPD LISTEND UK77886 COVER LETTER END UK77888 COVER LETTER START PROBLEM DESCRIPTION(S): PM60143 - **************************************************************** * USERS AFFECTED: All DB2 10 and 9 for z/OS users of triggers * * with transition tables when trace IFCID 311 * * is on * 1 **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B DSNIWTTC+0F72 after * * MSGDSNT501I RC0000006C TYPE00000D02 is * * issued for an application that is using * * a trigger transition table * **************************************************************** * RECOMMENDATION: * **************************************************************** The aforementioned abend happened because after a failure to create a workfile CUB in DSNIWTTC, the code was trying to write trace IFCID 311, which requires a valid CUB. This APAR does not deal with the reasons why the message DSNT501I was issued, it only deals with the subsequent 0C4 abend. The reasons behind DSNT501I REASON 0000006C TYPE 00000D02 are typically under user control. Code has been changed to not write IFCID 311 in DSNIWTTC when there is no valid CUB. Additional keywords: SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60143 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWTTC PM60143 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60143 DSNIWTTC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWTTC LISTEND UK77888 COVER LETTER END UK77893 COVER LETTER START PROBLEM DESCRIPTION(S): PM60357 - **************************************************************** * USERS AFFECTED: Internal dump formatting enhancements * * for DBD/OBD (serviceability) * **************************************************************** * PROBLEM DESCRIPTION: Internal dump formatting enhancements * * for DBD/OBD * **************************************************************** * RECOMMENDATION: * **************************************************************** Internal dump formatting enhancements for DBD/OBD. Internal dump formatting enhancements for DBD/OBD. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM60357 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWDFDB PM60357 DSNWDPRD PM60357 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60357 DSNWDFDB DSNWDPRD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWDFDB DSNWDPRD LISTEND UK77893 COVER LETTER END UK77917 COVER LETTER START PROBLEM DESCRIPTION(S): PM59964 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries that can * * perform index screening on an OR predicate. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0CF at DSNXGRDS.DSNXOGCX +4B86 or * * ABEND0CF at DSNXGRDS.DSNXOCCX +0F38 or * * poor query performance for a query that * * can perform index screening on an OR * * predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** An abend or poor query performance may occur for a query that can perform index screening on an OR predicate. In order for DB2 to consider index screening on an OR predicate, all columns referenced in the OR clause must exist on the same table and in the same index. The following abends may be observed... ABEND0CF at location DSNXGRDS.DSNXOGCX +4B86 ABEND0CF at location DSNXGRDS.DSNXOCCX +0F38 ABEND0CF at location DSNXGRDS.DSNXOGCX +4A9C The direct cause of the abend is referencing undefined storage. As a result, the abends may be intermittent. In those cases in which an abend does not occur, a rare situation may arise which will result in an inefficient access path and poor query performance. Additional keywords: ABEND0CF SQLOR SQLACCESSPATH SQLPERFORMANCE DSNXOGCX DSNXOCCX 1 DB2 code has been modified to avoid referencing undefined storage to resolve both the abends and performance problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59964 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM55938: See PM55938 APAR/PTF text for additional information about why a REBIND is necessary. PM55938 corrects a problem of choosing an inefficient access path instead of a DPSI index access path for a query with an EXISTS 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 affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCCX PM59964 DSNXOGCX PM59964 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59964 DSNXOCCX DSNXOGCX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCCX DSNXOGCX LISTEND UK77917 COVER LETTER END UK77920 COVER LETTER START PROBLEM DESCRIPTION(S): PM52237 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS XML users of * * the XMLTABLE function. * **************************************************************** * PROBLEM DESCRIPTION: An SQLCODE904 (or -904) with reason * * code rc00D50001 or rc00D50002 can be * * issued from DSNXRXML when using an * * XMLTABLE function, such as XMLPARSE, as * * the argument of the XMLTABLE. * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQLCODE904 (or -904) with reason code rc00D50001 or rc00D50002 can be issued from DSNXRXML when using the XMLTABLE 1 function, such as XMLPARSE, as the argument of the XMLTABLE function. The following example can illustrate the problem. SELECT X.* FROM T1, XMLTABLE('/a/b' PASSING XMLPARSE(C1) COLUMNS C INTEGER PATH 'c') AS X ; For each row returned from XMLTABLE, the XMLPARSE function will be called to parse the XML document (C1) which can utilize a lot of storage. However, for each XML document, we only need to parse once. The argument of the XMLTABLE function should be called only once for each row in T1. But currently it is called for each row returned by XMLTABLE. Please note. The amount of storage used is dependent on the size of the XML document and how many rows are returned from the XMLTABLE function. The code in DB2 which processes the XMLTABLE function is modified to parse the XML document only once. This can significantly lessen the amount of storage the XMLTABLE function utilizes. This will reduce the chance of receiving a 'resource unavailable' condition, i.e. an SQLCODE -904, with reason code rc00D50001 or rc00D50002. Additional Keywords: SQLXML SQLXMLTABLE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM52237 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM52237 See PM52237 APAR/PTF text for additional information about why a REBIND is necessary. Apar PM52237 reduces the XML storage usage so as not to exceed the specified zparm limit. As a result, this will reduce the chance of receiving an SQLCODE904 (or SQLCODE -904), a Resource Unavailable condition with reason code rc00D50001 or rc00D50002, which means excessive storage used for XMLTABLE. 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 DSNXEMG1 PM52237 1 DSNXGRTS PM52237 DSNXREOJ PM52237 DSNXREO9 PM52237 DSNXRFN PM52237 DSNXRFN9 PM52237 DSNXROJ1 PM52237 DSNXROJ9 PM52237 DSNXRSFN PM52237 DSNXRSGB PM52237 DSNXRSG9 PM52237 DSNXRSN9 PM52237 DSNXRT1J PM52237 DSNXRT19 PM52237 DSNXSBUC PM52237 DSNXSIND PM52237 DSNXSING PM52237 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM52237 DSNXEMG1 DSNXGRTS DSNXREOJ DSNXREO9 DSNXRFN DSNXRFN9 DSNXROJ1 DSNXROJ9 DSNXRSFN DSNXRSGB DSNXRSG9 DSNXRSN9 DSNXRT1J DSNXRT19 DSNXSBUC DSNXSIND DSNXSING THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEMG1 DSNXGRTS DSNXREOJ DSNXREO9 DSNXRFN DSNXRFN9 DSNXROJ1 DSNXROJ9 DSNXRSFN DSNXRSGB DSNXRSG9 DSNXRSN9 DSNXRT1J DSNXRT19 DSNXSBUC DSNXSIND DSNXSING LISTEND UK77920 COVER LETTER END UK77951 COVER LETTER START PROBLEM DESCRIPTION(S): PM60766 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL * * statement using index defined on expression. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC00000004 at location * * DSNXGRDS.DSNXOZAT OFFSET187C may occur * 1 * when a SQL statement contains * * predicates and indexes are defined on * * the expressions of these predicates. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC00000004 at location DSNXGRDS.DSNXOZAT OFFSET187C may occur when an SQL statement contains predicates and indexes are defined on the expressions of these predicates. . The following example helps to illustrate problem. CREATE TABLE TEST.TAB (C1 INT, C2 CHAR(5), C3 FLOAT, C4 VARCHAR(10)); . CREATE INDEX IDX1 ON TEST.TAB (C1+C3); CREATE INDEX IDX2 ON TEST.TAB (C2||C4); . DELETE FROM TEST.TAB WHERE C1+C3 = 15 AND C2||C4 = 'ABC'; . DB2 didn't process the index on expression(IOE) correctly and caused ABEND0C4. The code in DB2 has been modified correctly to process the index defined on expression. . Additional keywords: SQLINDEXONEXP SQLDELETE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60766 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. 1 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. 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 PM60766 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60766 DSNXOZAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOZAT LISTEND UK77951 COVER LETTER END UK77953 COVER LETTER START PROBLEM DESCRIPTION(S): PM51171 - **************************************************************** * USERS AFFECTED: All users of IFCID 58 on DB2 10 (for z/OS) * **************************************************************** * PROBLEM DESCRIPTION: 1. Some execution statistics are not * * recorded for statement-level * 1 * performance metrics pointed to by * * QWT02R30 in IFCID58. * * . * * 2. IFCID 59 was not being cut on * * certain EXEC SQL OPEN DRDA scenarios. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. IFCID 58 reports execution statistics for statement level traces. In several SQL statements, certain execution statistics reported for the following IFCID058 fields in the QWT02R30 data block were not being recorded. The statements affected were the SELECT, INSERT, UPDATE, and MERGE SQL statements for the following QWT02R30 fields. . QW0058ST (number of sorts) QW0058IS (number of index scans) QW0058TB (number of table space scans) . 2. DB2 10 for z/OS RDA protocol bundles the initial SQL FETCH query block within the SQL OPEN statement. For this bundled SQL FETCH statement, an IFCID 59 trace record was not recorded. Instead, DB2 may record the following trace records: . Scenario 1: IFCID65 OPEN (bundled SQL FETCH) IFCID58 END . Scenario 2: IFCID65 OPEN (bundled SQL FETCH) IFCID66 CLOSE IFCID58 END DB2 code has been modified to update the QWT02R30 fields stated in the PROBLEM SUMMARY section reported by the IFCID 58 trace record. . DB2 code has been modified to record an IFCID 59 trace record when the DRDA protocol has determined to bundle the SQL FETCH query block within the SQL OPEN statement. . RELATED KEYWORDS: PERFM SQLSTATS IFCID58 IFCID59 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51171 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 PM51171 DSNXSFTP PM51171 DSNXSORI PM51171 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM51171 DSNXERT DSNXSFTP DSNXSORI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERT DSNXSFTP DSNXSORI LISTEND UK77953 COVER LETTER END UK77981 COVER LETTER START PROBLEM DESCRIPTION(S): PM47330 - **************************************************************** * USERS AFFECTED: All users of DB2 z/OS who issue the * * -START DATABASE SPACENAM ACCESS(FORCE) * * command * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C20305 DSNB1LDN may happen * * during START DATABASE command with * * ACCESS(FORCE) specified against * * a NPSI (nonpartitioned secondary index) * **************************************************************** * RECOMMENDATION: * **************************************************************** The -START DATABASE SPACENAM ACCESS(FORCE) command was trying to do a drain operation on a nonpartitioned secondary index(NPSI) but passed mismatched parameters to the drain function. This may result in the 00C20305 abend. DB2 code has been changed to use the matching parm for the drain call during processing of the -START DATABASE SPACENAM ACCESS(FORCE) command. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM47330 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISTFO PM47330 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM47330 DSNISTFO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISTFO LISTEND UK77981 COVER LETTER END 1UK77987 COVER LETTER START PROBLEM DESCRIPTION(S): PM55821 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: 1. An ABEND0C4 in CSECT DSNTLTIM * * or DSNTLDEA * * * * 2. An ABNEND04E RC0070005 in CSECT * * DSNXVTRS * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. When an agent is involved in a timeout or deadlock in IRLM it will be reported on by IFCID196 (timeout) or by IFCID172 (deadlock). There is a window where that agent may be deallocated by DB2 prior to IRLM reporting on it and the freed storage for that agent be placed on the relevant free chain by DB2. The first 8 bytes will be used as an internal pointer and if that pointer starts with '2015'X, IRLM sanity check will mistake this freed storage for allocated CUB and use it, resulting in an ABEND0C4 in CSECT DSNTLDEA (deadlock) or CSECT DSNTLTIM (timeout). 2. When an agent with role id is timed out, an incorrect call to UTF to EBCDIC conversion routine will result in ABEND04E RC0070005 in CSECT DSNXVTRS 1. Enhance the validation of what is valid storage in DSNTLDEA and DSNTLTIM 2. Correctly call UTF to EBCDIC conversion in CSECT DSNTLSUS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55821 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 PM55821 DSNTLSUS PM55821 DSNTLTIM PM55821 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55821 DSNTLDEA DSNTLSUS DSNTLTIM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLDEA DSNTLSUS DSNTLTIM LISTEND UK77987 COVER LETTER END 1 UK77992 COVER LETTER START PROBLEM DESCRIPTION(S): PM59835 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of OLAP MIN and * * MAX specifications * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXGRDS * * DSNXRWND M190 for an OLAP specification * * moving MIN or MAX * * * **************************************************************** * RECOMMENDATION: * **************************************************************** The ABEND04E RC00E70005 at DSNXGRDS DSNXRWND M190 for the OLAP specification moving MAX can occur when the first value in the window is the smallest possible value for the input expression's data type. For example, the smallest DATE value is '0001-01-01' : CREATE TABLE T1 (DATECOL DATE, C2 INT); INSERT INTO T1 VALUES('0001-01-01',1); SELECT MAX(DATECOL) OVER(ORDER BY C2) FROM T1; The abend can occur for OLAP moving MIN when the first value in the window is the largest possible value for the input expression's data type. For example, the largest DATE value is '9999-12-31' : CREATE TABLE T1 (DATECOL DATE, C2 INT); INSERT INTO T1 VALUES('9999-12-31',1); SELECT MIN(DATECOL) OVER(ORDER BY C2) FROM T1; The abend may occur for any of the following input expression data types: CHAR, GRAPHIC, DATE, TIME, TIMESTAMP, BINARY, SMALLINT, DECFLOAT, DECIMAL, VARCHAR and VARGRAPHIC DB2 has been corrected to set an internal field correctly for the OLAP specifications MIN and MAX. This will prevent the abend. Additional keywords : SQLMIN SQLMAX COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59835 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRCSF PM59835 DSNXRGBJ PM59835 DSNXRRSQ PM59835 DSNXRSFJ PM59835 1 DSNXRSFN PM59835 DSNXRSGB PM59835 DSNXRSJ PM59835 DSNXRWND PM59835 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59835 DSNXRCSF DSNXRGBJ DSNXRRSQ DSNXRSFJ DSNXRSFN DSNXRSGB DSNXRSJ DSNXRWND THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRCSF DSNXRGBJ DSNXRRSQ DSNXRSFJ DSNXRSFN DSNXRSGB DSNXRSJ DSNXRWND LISTEND UK77992 COVER LETTER END UK77998 COVER LETTER START PROBLEM DESCRIPTION(S): PM60558 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * RUNSTATS or inline stats utility users * * collecting index statistics. * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT FIRSTKEYCARDF in MSGDSNU617I * * and in catalog table SYSIBM.SYSINDEXES * * during RUNSTATS utility execution. * * INCORROUT COLCARDF in MSGDSNU615I * * and in catalog table SYSIBM.SYSCOLUMNS * * during RUNSTATS utility execution. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When a user executed RUNSTATS utility on a partitioned index after an ALTER ROTATE was performed, incorrect FIRSTKEYCARDF values were reported in MSGDSNU617I and those values were updated in SYSIBM.SYSINDEXES. The values reported in DSNU615I for the leading column of the indexes were also incorrect and those values were updated in SYSIBM.SYSCOLUMNS. During aggregation of the partition level statistics, rollup was done based on the physical order of parts instead of the logical order causing the statistics to be incorrect. Code was modified to aggregate the index statistics 1 in the logical order of partitions after an ALTER ROTATE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60558 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSACO PM60558 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60558 DSNUSACO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSACO LISTEND UK77998 COVER LETTER END UK78029 COVER LETTER START PROBLEM DESCRIPTION(S): PM59440 - **************************************************************** * USERS AFFECTED: DB2 for z/OS version 10 CM8 and CM9 users of * * REORG on LOB TABLESPACE with SHRLEVEL NONE * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 in DSNIXTND OFFSET * * 01AA. * **************************************************************** * RECOMMENDATION: * **************************************************************** When utility REORG LOB TABLESPACE SHRLEVEL NONE was run, lob manager uses a 31-bit pointer to request data set extension where a 64-bit pointer is expected. As the result, the ABEND0C4 RC00000038 occurred during the process. DB2 code has been modified to use a 64-bit pointer when requesting data set extension. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59440 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNORCHU PM59440 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59440 DSNORCHU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNORCHU LISTEND UK78029 COVER LETTER END UK78034 COVER LETTER START PROBLEM DESCRIPTION(S): PM60975 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -805 is erroneously returned * * for remote statements when connected to * * a DB2 10 for z/OS server. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application requester at Site 1 connects to a DB2 10 for z/OS server at Site 2. The collection id for the remote packages for this application consist of a single character. The application issues a SQL request that contains a 3-part name or alias reference to a downstream server at Site 3. The requester at Site 1 correctly sends the request along with the single character collection id to Site 2. The server at Site 2 receives the SQL request from Site 1, but fails to correctly propagate the single character collection id to Site 3. The server at Site 3 receives the SQL request from Site 2 but cannot find the package associated with the request because the collection id received is invalid, and thus issues SQLCODE -805 for the request. DB2 server code at Site 2 has been changed to correctly propagate the collection id for SQL requests to the downstream server. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60975 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZHC1 PM60975 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60975 DSNLZHC1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZHC1 LISTEND UK78034 COVER LETTER END UK78035 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM59134 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * * of RLF reactive governing. * **************************************************************** * PROBLEM DESCRIPTION: The ASUTIME limit from the most * * qualified row based on LUNAME column * * is not used for RLF reactive * * governing. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the multiple rows with the same values in AUTHID, RLFCOLLN, RLFPKG columns exist in the DSNRLSTxx table for reactive governing, the best matching row for ASUTime limit is chosen based on the value in LUNAME column. For reactive governing, the LUNAME is searched in the following order. For a local thread: 1. the matching LUNAME 2. 3. PUBLIC For a distributed thread: 1. the matching LUNAME 2. PUBLIC In the reported case, when a row with in LUNAME column and a row with 'PUBLIC' in LUNAME column exist with the same values in AUTHID, RLFCOLLN, and RLFPKG columns, the ASUTime limit was incorrectly chosen from the row with 'PUBLIC' value in LUNAME column for a local thread. In addition, the ASUTime limit can be incorrectly chosen from the row with 'PUBLIC' in LUNAME column for both local and remote threads, when there exists a row with thread's matching LUNAME which alphabetically comes earlier than 'PUBLIC' string. DB2 has been changed to correctly choose the ASUTIME from the best qualified row. Additional keywords: RLST RLIMIT LU name SUTIMELIMIT TIMEUSEDSOFAR SQLCODE905 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59134 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 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 PM59134 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59134 DSNTCPRE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTCPRE LISTEND UK78035 COVER LETTER END UK78046 COVER LETTER START PROBLEM DESCRIPTION(S): PM57958 - **************************************************************** * USERS AFFECTED: DB2 9 users of WITH RETURN attribute for * * stored procedure dynamic result sets and * * DB2 Dynamic Statement Cache , and * * DB2 10 users of WITH RETURN TO CLIENT * * attribute for stored procedure dynamic * * result sets and DB2 Dynamic Statement Cache * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE0 returned on a CALL stored * * procedure when SQLCODE466 is expected * * because the stored procedure returned * * a dynamic cursor result set defined * * as WITH RETURN (for DB2 9) or WITH * * RETURN TO CLIENT (for DB2 10) on * * the DECLARE CURSOR statement, and * * DB2 Dynamic Statement Caching is active * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 Dynamic Statement Caching (DSC) is active, SQLCODE0 is unexpectedly returned on an SQL CALL stored procedure when -- (1) the stored procedure should return SQLCODE466 and a dynamic result set because a dynamic cursor query is defined as WITH RETURN (for DB2 9) or WITH RETURN TO CLIENT (for DB2 10) on the SQL DECLARE CURSOR statement, and is left OPEN by the stored procedure, *and* (2) the same exact query but without WITH RETURN or WITH RETURN TO CLIENT is already cached in the Dynamic Statement Cache 1 ( DSC ). . The expected stored procedure result set was not returned when DB2 cache matched the dynamic cursor WITH RETURN result set with a non-WITH RETURN dynamic cursor query that was already cached in the DSC. The cache match occurred because the WITH RETURN (for DB2 9) or WITH RETURN TO CLIENT (for DB2 10) specified on the SQL DECLARE CURSOR was not included as a cache match criteria, so the non-result set version of the query was executed; resulting in no result set being returned from the stored procedure. . This cache match error does not occur when the WITH RETURN or WITH RETURN TO CLIENT is specified in the PREPARE ATTRIBUTES host-variable instead of on the SQL DECLARE CURSOR statement, because the PREPARE ATTRIBUTES values become part of the cache match criteria for the dynamic SQL query. . Note that DB2 10 does not have the problem for the WITH RETURN on DECLARE CURSOR, only for the WITH RETURN TO CLIENT on the DECLARE CURSOR. . When only one result set was expected, other symptoms of the problems are as follows: (1) The SQL ASSOCIATE LOCATOR statement fails with SQLCODE -482 / SQLCODE482 (2) The SQL DESCRIBE PROCEDURE statement does not populate the target SQLDA with result set information (3) The client doesn't receive the result set it expects . If more than one result set is expected to be returned by the stored procedure, other symptoms of the problems are as follows: (1) The SQL ASSOCIATE LOCATOR / LOCATORS statement may not assign locator values to all specified locator host- variables, then the SQL ALLOCATE CURSOR statement specifying the locator variable fails with SQLCODE -423 / SQLCODE423 (2) A DESCRIBE PROCEDURE does not populate the target SQLDA with information for all expected result sets. . DB2 9 was modified to include WITH RETURN from the DECLARE CURSOR statement as a cache match criteria for dynamic queries in the DB2 Dynamic Statement Cache. . DB2 10 was modified to include WITH RETURN TO CLIENT from the DECLARE CURSOR statement as a cache match criteria for for dynamic queries in the DB2 DSC. Note that DB2 10 already does this for the WITH RETURN attribute from DECLARE CURSOR. . Additional Search Keywords: DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT SQLDESCRIBE SQLDYNSTMTCACHE SQLSP SQLSTOREDPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57958 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 DSNXEDSC PM57958 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57958 DSNXEDSC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEDSC LISTEND UK78046 COVER LETTER END UK78076 COVER LETTER START PROBLEM DESCRIPTION(S): PM56113 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: Inconsistent SQL results after a LOAD * * on an entire partitioned table space * * has failed due to the existence of one * * or more claimers. * * * * Although the failed LOAD leaves all * * partitions in UTUT state, SQL access * * from some members may be successful, * * while access from other members fails * * with a "resource unavailable" reason * * code RC00C90082. * **************************************************************** * RECOMMENDATION: * **************************************************************** Certain utilities, including LOAD, when operating on an entire partitioned table space or index, will request a drain on "part zero" to gain control of the entire object. As part of this, every part needs to be marked as "drain in control" so that any subsequent SQL operation will perform a dbet check. However, the setting of "drain in control" is happening too late in the process. If the drain fails early, perhaps due to the existence of claimers on another member, this status does not get set and an SQL job may subsequently gain access to a partition in spite of the existence of an exceptional dbet state such as UTUT. The logic for a "part zero" drain has been modified to ensure that the "drain in control" status is set for all parts early in the process (before any wait for claimers on any member). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56113 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 DSNB1DDN PM56113 DSNB1DRA PM56113 DSNB1LDA PM56113 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56113 DSNB1DDN DSNB1DRA DSNB1LDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DDN DSNB1DRA DSNB1LDA LISTEND UK78076 COVER LETTER END UK78080 COVER LETTER START PROBLEM DESCRIPTION(S): PM59543 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS user of SQL * * statement containing IN predicate with host * * variables or parameter markers, rewritten by * * materialized query table(MQT). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04C RC00000038 at location * * DSNXGRDS.DSNXOXPM OFFSET334A may occur * * when an SQL statement satisfies all of * * the following conditions: * * * * 1. an IN predicate with host variables * * or parameter markers is referenced * * in the SQL; * * 2. an IN predicate is contained in the * * definition of materialized query * * table(MQT); * * 3. the SQL mentioned in condition #1 * * is rewritten by the MQT in #2. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04C RC00000038 at location DSNXGRDS.DSNXOXPM OFFSET334A may occur when an SQL statement satisfies all of the following conditions: 1. an IN predicate with host variables or parameter markers is referenced in SQL; 2. an IN predicate is contained in definition of materialized query table(MQT); 3. the SQL mentioned in condition #1 is rewritten by the MQT in condition #2. 1 An example helps to illustrate the problem: CREATE TABLE TEST.T1 (COL11 INT, COL12 CHAR(5)); CREATE TABLE TEST.T2 (COL21 INT, COL22 CHAR(5)); CREATE TABLE TEST.MQT1(C1, C2) AS (SELECT COL21, COL12 FROM TEST.T1, TEST.T2 WHERE COL11 = COL21 AND COL12 IN ('A', 'B', 'C')) DATA INITIALLY DEFERRED REFRESH DEFERRED MAINTAINED BY USER; SET CURRENT REFRESH AGE = ANY; SET CURRENT MAINTAINED TYPES = ALL; EXPLAIN ALL SET QUERYNO = 1000 FOR SELECT COL21, COL12 FROM TEST.T1, TEST.T2 WHERE COL11 = COL21 AND COL12 IN (?, 'B', ?); DB2 didn't handle IN predicate in aforementioned SQL correctly during the process rewritten with MQT, which caused an ABEND. Code in DB2 has been modified correctly to handle IN predicate with host variables or parameter markers during aforementioned SQL rewritten with MQT. Additional keywords: SQLMQT SQLIN SQLPMARKER SQLPMK SQLHOSTVAR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59543 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM47092: See PM47092 APAR/PTF text for additional information about why a REBIND is necessary. PM47092 corrects a problem of an incorrect output when an SQL statement satisfies all of the following conditions: 1. a BETWEEN predicate is referenced in the definition of one MQT; 2. an IN predicate or multiple OR predicates are referenced in in one SQL statement, and the value of some expressions from IN predicate or OR predicate exceed the value of low bound or 1 high bound from the BETWEEN predicate in #1; 3. the SQL statement in #2 is rewritten to the MQT in #1 by DB2. 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 DSNXOXPM PM59543 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59543 DSNXOXPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOXPM LISTEND UK78080 COVER LETTER END UK78114 COVER LETTER START PROBLEM DESCRIPTION(S): PM59157 - **************************************************************** * USERS AFFECTED: All users of DB2 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: Serviceability enhancement. * **************************************************************** * RECOMMENDATION: * **************************************************************** Serviceability enhancement. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59157 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN1LOGP PM59157 DSN1LOUT PM59157 DSN1LPAR PM59157 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59157 DSN1LOGP DSN1LOUT DSN1LPAR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN1LOGP DSN1LOUT DSN1LPAR 1 LISTEND UK78114 COVER LETTER END UK78127 COVER LETTER START PROBLEM DESCRIPTION(S): PM61082 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where DB2 is configured with * * DDF THREADS=INACTIVE specified * * (DSN6FAC CMTSTAT INACTIVE). * **************************************************************** * PROBLEM DESCRIPTION: Connection/DBAT remains active even * * though it had only processed non SQL * * related events, such as a DRDA Ping * * and/or XA_Recover sequence. * **************************************************************** * RECOMMENDATION: * **************************************************************** After servicing a DRDA Ping and/or XA_Recover sequence, the associated connection/DBAT remains active even though no actual SQL related transaction (Unit of Work, UOW) exists. This causes an unnecessary utilization of a DBAT that remains dedicated to the connection and therefore cannot be used (pooled) to service work on other connections. Potential symptoms may include: o Over utilization of DBATs, perhaps leading to an erroneous MAXDBAT limit reached condition. o Erroneous DSNL027I/DSNL028I message condition with a 00D3003B (Idle Thread Time-out exceeded) reason code. o A quiesce stop of DDF may not complete due to the erroneous presence of an active DBAT. A -STOP DDF MODE(FORCE) may be necessary in order for DDF to complete its stop processing. DB2 has been changed to recognize a DRDA Ping or XA_Recover sequence that is not part of a UOW and allow inactivation of the connection and pooling of the DBAT. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61082 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLQDIS PM61082 DSNLTDSR PM61082 DSNLTEXC PM61082 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61082 DSNLQDIS DSNLTDSR DSNLTEXC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLQDIS 1 DSNLTDSR DSNLTEXC LISTEND UK78127 COVER LETTER END UK78133 COVER LETTER START PROBLEM DESCRIPTION(S): PM61423 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS Conversion Mode * * LOB users who are migrating from DB2 for * * z/OS v8. * **************************************************************** * PROBLEM DESCRIPTION: An SQLCODE -904 with reason code * * RC00C90096 or 00C90096 occurs on SELECT * * of LOB data using isolation level UR * * (uncommitted read). * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE904 with RC00C90096 and TYPE OF RESOURCE 00000F01 may occur on select of LOB data with ISO(UR). The SQLCODE904 occurs because LOB locks are acquired and are not released until commit. These accumulated LOB locks can cause NUMLKUS to be exceeded. Please note that -904 only occurs for any customers migrating from DB2 for z/OS v8 to DB2 10 for z/OS. Code has been changed to ensure that LOB locks acquired for ISO(UR) applications will not cause NUMLKUS or NUMLKTS to be exceeded. Please note that the fix for this problem for DB2 for z/OS V8 and DB2 9 for z/OS is apar PK80165. Additional Keywords: SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61423 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 PM61423 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61423 DSNODCRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNODCRL 1 LISTEND UK78133 COVER LETTER END UK78148 COVER LETTER START PROBLEM DESCRIPTION(S): PM59659 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of LOB * * datatype and multiple CCSIDs. * **************************************************************** * PROBLEM DESCRIPTION: 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** 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. The following example could recreate the abend in DB2 10. CREATE TABLE TT1(C1 INTEGER, C2 CLOB(100)) CCSID UNICODE; CREATE TABLE TT2(C1 INTEGER, C2 CHAR(50)); INSERT INTO TT1 VALUES(1000, CLOB('THIS IS A CLOB')); INSERT INTO TT2 VALUES(2000, 'THIS IS A CHAR'); SELECT C1,C2 FROM TT1 UNION ALL SELECT C1,C2 FROM TT2 ORDER BY 1; DB2 did not handle the EBCDIC CHAR datatype with UNICODE CLOB data type correctly causing an abend in DSNXIDM .DSNXOTFLA:5009. There are multiple abends, but only one is mentioned here. DB2 is updated to handle the LOB datatype with multiple CCSID correctly. Additional Keywords: SQLLOB SQLCCSID SQLUNIONALL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59659 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM59659: See PM59659 APAR/PTF text for additional information about why a REBIND is necessary. 1 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 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 PM59659 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59659 DSNXOCT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCT LISTEND UK78148 COVER LETTER END UK78170 COVER LETTER START PROBLEM DESCRIPTION(S): PM59155 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of DATE and TIME exits. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E rc00E40340 can occur at * * location DSNUTILA.DSNURWBG+61A0 * * (OFFSET61A0) when using the DB2 LOAD * * utility and a DATE exit. * * * * An SQLCODE185 can be issued from * * DSNXOLTD location -320 for an SQL * * INSERT statement when using a DATE * * exit. * * * * An unexpected SQLCODE -181 (SQLCODE181) * 1 * can occur from DSNXRTIM location 116 * * when using a DATE exit. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E rc00E40340 can occur at location DSNUTILA DSNURWBG +61A0 (OFFSET61A0) when using the DB2 LOAD utility and a DATE exit. In the reported case an EBCDIC DATE exit DSNXVDTX was installed. An unexpected SQLCODE185 is returned to DB2 utilities prior to the abend. Also, an SQLCODE185 (or SQLCODE -185) can be issued from DSNXOLTD location -320 for an SQL INSERT statement when using a DATE exit. The problem is contingent on employing a DATE exit, and populating a table that has at least a DATE and TIME column defined as DATE WITH DEFAULT NULL TIME WITH DEFAULT NULL For both problems, the failure occurs because DB2 incorrectly checks a DECP DATE exit specification in a cast character-to- time conversion routine instead of a DECP TIME exit specification. As a result, the default EBCDIC time exit DSNXVTMX is invoked when it should not be since no time exit was installed. The exit returns a rc16 and the conversion routine then incorrectly returns a false SQLCODE185 or -185. The following simple example can illustrate how the failure can occur for an SQL INSERT statement. Step 1. Specify the following DSNHDECP settings SCCSID=277 DATE=LOCAL DATELEN=10 TIME=ISO TIMELEN=0 Step 2. Setup and install local DATE exits. Step 3. Define the following simple Table. CREATE TABLE TABLE1 (STATUS_DATE DECIMAL(8 , 0) NOT NULL ,STATUS_TYPE CHARACTER(1) FOR SBCS DATA NOT NULL ,PROCESS_DATE DATE WITH DEFAULT NULL ,PROCESS_TIME TIME WITH DEFAULT NULL ) CCSID EBCDIC ; 1 Step 4. Insert the following two rows into Table TABLE1. INSERT INTO TABLE1 VALUES (0,'D','20110307',' '); INSERT INTO TABLE1 VALUES (0,'D','20110513','16.03.46'); Step 5. An SQLCODE -185 can occur from DSNXOLTD location -320. Please note that the same problem is likely to occur if using an ASCII (DSNXVDTA) or UNICODE (DSNXVDTU) DATE exit. Additionally, for DB2 10 for z/OS users, an unexpected SQLCODE -181 (SQLCODE181) can occur from DSNXRTIM location 116 when using a DATE exit. This error does not occur in v9. The failure occurs because DB2 is not checking the converted source length properly following the DATE exit invocation. As a result, an incorrect length is checked leading to an unexpected SQLCODE. The following examples illustrate some simple failing cases. When using DSNXVDTX the EBCDIC DATE exit. SELECT DATE('1-02-12') FROM SYSIBM.SYSDUMMY1; SELECT DATE('01-2-12') FROM SYSIBM.SYSDUMMY1; Result: SQLCODE -181 DSNXRTIM loc 116 When using DSNXVDTA the ASCII DATE exit. SELECT DATE('1-02-12') FROM SYSIBM.SYSDUMMYA; SELECT DATE('01-2-12') FROM SYSIBM.SYSDUMMYA; Result: SQLCODE -181 DSNXRTIM loc 116 In each of the above cases, if the DATE exit works properly to validate the input DATE format, DB2 should support the desired format and check the proper converted source length according to the DECP specification. The code in DB2 v10 is modified to correct the checking of the DECP specifications for TIME exits in the cast character-to-time routine. This will prevent the incorrect SQLCODE185 from being issued for both the DB2 LOAD utility and the SQL INSERT statement. Also, corrections are made to a few other cast character-to-time routines for both DB2 v9 and v10 to check DECP specifications for TIME exits (instead of for DATE exits) to prevent false 1 SQLCODE185 or SQL code -185 errors. Additionally, in DB2 v10, DB2 will check the proper source length after the DATE exit validates the input date and a successful conversion has occurred. This will prevent the error path from being taken resulting in an unexpected SQLCODE181 or -181. Additional Keywords: SQLDATE SQLTIME SQLINSERT SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59155 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Please note. If you are using DATE exits, this concerns you. If you are using a DATE exit, specifically an EBCDIC, ASCII, or UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make sure it is functioning properly. If it is, a query referencing the TIMESTAMP built-in function should work correctly and no action is necessary. If however the exit is not working properly and the query referencing the TIMESTAMP built-in function worked in DB2 9 but is now not working in DB2 10 (i.e. it does not return the expected result), then please ensure that the exit is coded and working properly. ACTION: The following behavior difference may be noticed with the application of this apar. Please note that this apar corrects an instance where an incorrect SQLCODE180 could be issued. Instead, an SQLCODE181 should be issued. So, any static applications that check for an SQLCODE180 (or -180) should also be checking for an SQLCODE181 (or -181). COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDEC PM59155 DSNXRDE9 PM59155 DSNXRGPL PM59155 DSNXRIB9 PM59155 DSNXRID9 PM59155 DSNXRIHB PM59155 DSNXRIHD PM59155 DSNXRIHR PM59155 DSNXRIHS PM59155 DSNXRINT PM59155 DSNXRIS9 PM59155 DSNXRITV PM59155 DSNXRIT9 PM59155 DSNXRLET PM59155 DSNXRNT9 PM59155 DSNXRPL9 PM59155 DSNXRSBC PM59155 DSNXRSPL PM59155 1 DSNXRTIM PM59155 DSNXRTI9 PM59155 DSNXVDTT PM59155 DSNXVDT2 PM59155 DSNXVT29 PM59155 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59155 DSNXRDEC DSNXRDE9 DSNXRGPL DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRINT DSNXRIS9 DSNXRITV DSNXRIT9 DSNXRLET DSNXRNT9 DSNXRPL9 DSNXRSBC DSNXRSPL DSNXRTIM DSNXRTI9 DSNXVDTT DSNXVDT2 DSNXVT29 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDEC DSNXRDE9 DSNXRGPL DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRINT DSNXRIS9 DSNXRITV DSNXRIT9 DSNXRLET DSNXRNT9 DSNXRPL9 DSNXRSBC DSNXRSPL DSNXRTIM DSNXRTI9 DSNXVDTT DSNXVDT2 DSNXVT29 LISTEND UK78170 COVER LETTER END UK78174 COVER LETTER START PROBLEM DESCRIPTION(S): PM60148 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of COPY utility. * **************************************************************** * PROBLEM DESCRIPTION: COPY utility does not report broken * * system pages in table spaces. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** DSN1COPY with CHECK option reported a broken page with the 1 following message: DSN1990I DSN1CPGD BROKEN PAGE. PAGE NUMBER = 00000002. REASON: RECORDS AND HOLES OVERLAP WITH ID MAP. SERVICE INFO: CODE= 'C2C'X XFREEP='00023E52'X XFRSTMAP='00022FFC'X However, although CHECKPAGE is the default for table spaces, COPY utitily run on the same object did not report any broken page. This is because the broken page is a system page and COPY utility does not check the validity of the contents of system pages. COPY utility is modified to perform validity checking on system pages. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60148 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 PM60148 DSNUBASA PM60148 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60148 DSNUBAID DSNUBASA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBAID DSNUBASA LISTEND UK78174 COVER LETTER END UK78177 COVER LETTER START PROBLEM DESCRIPTION(S): PM58492 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures * * and User Defined Functions (UDFs). * **************************************************************** * PROBLEM DESCRIPTION: Stored procedure thread suspended for * * a long time after a 04E/00E50013 soft * * cancel abend. Also a latch hang is * * detected. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a missing serialization during stored procedure recovery and that results in the incorrect suspension of the stored procedure thread. Since latch is held during the process and the suspension will never be resumed, latch hang occurs. Missing serialization in the stored procedure recovery has been 1 added and DB2 code has been changed to ensure no latch is held during suspension. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58492 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9MON PM58492 DSNX9WCA PM58492 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58492 DSNX9MON DSNX9WCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9MON DSNX9WCA LISTEND UK78177 COVER LETTER END UK78180 COVER LETTER START PROBLEM DESCRIPTION(S): PM58294 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of REORG TABLESPACE utility with DISCARD * **************************************************************** * PROBLEM DESCRIPTION: A REORG TABLESPACE DISCARD of a table * * with a LOB column which is greater * * than 32k failed with MSGDSNU297I and * * ended with RC8, even though user * * omitted both DISCARDDN option and the * * SYSDISC DD statement in the input JCL. * **************************************************************** * RECOMMENDATION: * **************************************************************** A REORG TABLESPACE DISCARD was run on a table with a LOB column which was defined greater than 32k. The REORG failed with message DSNU297I - COMPOSITE RECORD SIZE TOO LARGE FOR xxx.xxx, even though DISCARDDN and SYSDISC DD statement were omitted. REORG DISCARD without DISCARDDN option and SYSDISC DD statement will not discard records into a data set, so the message DSNU297I should be skipped in this case. The REORG code has been modified to avoid issuing DSNU297I if DISCARD is specified without DISCARDDN option and SYSDISC DD statement. And the REORG will discard records without saving them in a data set. This APAR also requires a documentation change in Utility Guide and Reference: 1 Changed option for utility REORG: DISCARD Specifies that records that meet the specified WHEN conditions are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD statement in the JCL, discarded records are saved in the | associated data set. Otherwise, the utility discards records | without saving them in a data set. You can specify any SHRLEVEL option with DISCARD; however, if you specify SHRLEVEL CHANGE, modifications that are made during the reorganization to data rows that match the discard criteria are not permitted. In this case, REORG TABLESPACE terminates with an error. If you specify DISCARD, rows are decompressed and edit routines are decoded. If you also specify DISCARD to a file, rows are decoded by field procedure, and the following columns are converted to DB2 external format: (1)SMALLINT (2)INTEGER (3)FLOAT (4)DECIMAL (5)TIME (6)TIMESTAMP Otherwise, edit routines or field procedures are bypassed on both the UNLOAD and RELOAD phases for table spaces. Validation procedures are not invoked during either phase. Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY option. | You cannot specify DISCARD for a base table with LOB columns | unless the discard records are less than 32k or you want to | discard records without saving them in a data set. You cannot specify DISCARD for a base table with XML columns or for an XML table space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58294 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM58294 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference: Changed option for utility REORG: DISCARD Specifies that records that meet the specified WHEN conditions are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD statement in the JCL, discarded records are saved in the | associated data set. Otherwise, the utility discards records | without saving them in a data set. 1 You can specify any SHRLEVEL option with DISCARD; however, if you specify SHRLEVEL CHANGE, modifications that are made during the reorganization to data rows that match the discard criteria are not permitted. In this case, REORG TABLESPACE terminates with an error. If you specify DISCARD, rows are decompressed and edit routines are decoded. If you also specify DISCARD to a file, rows are decoded by field procedure, and the following columns are converted to DB2 external format: (1)SMALLINT (2)INTEGER (3)FLOAT (4)DECIMAL (5)TIME (6)TIMESTAMP Otherwise, edit routines or field procedures are bypassed on both the UNLOAD and RELOAD phases for table spaces. Validation procedures are not invoked during either phase. Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY option. | You cannot specify DISCARD for a base table with LOB columns | unless the discard records are less than 32k or you want to | discard records without saving them in a data set. You cannot specify DISCARD for a base table with XML columns or for an XML table space. REORG TABLESPACE DISCARD cannot be specified on a system-maintained temporal table space when versioning is active. When versioning is active and DISCARD is specified, REORG TABLESPACE fails with message DSNU076I and return code 8. ACTION: The PTF for APAR PM58294 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 DSNURFTB PM58294 DSNURORG PM58294 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM58294 DSNURFTB DSNURORG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURFTB DSNURORG LISTEND UK78180 COVER LETTER END UK78184 COVER LETTER START PROBLEM DESCRIPTION(S): PM59276 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users whose * * application has REOPT(AUTO) option. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXGRDS.DSN P000 * * when SELECT with option REOPT(AUTO). * * The actual module that issues this * * abend is DSNXOPFF. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 DSNXGRDS.DSNXOPFF when SELECT with REOPT(AUTO). When DB2 saves the bound SQL statement with REOPT(AUTO) option, the information needed to load the application at execution time is not saved correctly. So, later when the statement is loaded for execution, part of the REOPT structure is corrupted. This will cause the ABEND observed. DB2 has been fixed to save the bound statement with REOPT (AUTO) option correctly, the ABEND no longer occurs after the fix. Additional keywords: SQLREOPTAUTO REOPTAUTO SQLREOPT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59276 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM59276 APAR/PTF text for additional information about why a REBIND is necessary. APAR PM59276 fixes a REOPT AUTO problem that may not save the bound application correctly. As a result, later at execution time, certain fields in the structure of REOPT AUTO function contain bad values. DB2 will get ABEND when those bad fields in REOPT AUTO structure were referenced. 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 DSNXEMG1 PM59276 DSNXOPFF PM59276 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59276 DSNXEMG1 DSNXOPFF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEMG1 DSNXOPFF LISTEND UK78184 COVER LETTER END UK78201 COVER LETTER START PROBLEM DESCRIPTION(S): PM55333 - **************************************************************** * USERS AFFECTED: All users that need to select from * * SYSLGRNX or SYSUTIL. * **************************************************************** * PROBLEM DESCRIPTION: Some of the catalog rows representing * * the objects in the Directory are * * incorrect. This does not affect any * * function. * **************************************************************** * RECOMMENDATION: * **************************************************************** Apar PM35190 added the ability to select from some Directory objects like SYSIBM.SYSLGRNX and SYSIBM.SYSUTIL by inserting rows in to the catalog to describe the objects. It was discovered that some of the columns like the CREATEDTS column in SYSCOLUMNS were not initialized correctly. This does not cause any problems or affect the ability to select from Directory objects. DB2 code has been updated to properly initialize the catalog columns that are inserted for directory objects. The inserts occurs when the system enters NFM or when the job CATMAINT UPDATE UNLDDN PM55333 is run. This job will invalidate any plans or packages dependent on the Directory objects, delete the rows if they have already been inserted and then insert the updated rows. If you have rows that are incorrect before this apar is applied the job must be run to correct the rows. The following query will return 0 rows when the catalog rows are correct. SELECT NAME,CREATEDTS FROM SYSIBM.SYSCOLUMNS 1 WHERE TBCREATOR = 'SYSIBM' AND TBNAME = 'SYSLGRNX' AND NAME = 'LGRDBID' AND CREATEDTS NOT IN('0001-01-01-00.00.00.000000'); ++HOLD PM55333 This apar does not correct rows that where inserted into the catalog for the directory objects before the apar was applied. To see if you have rows that need to be updated run the query: SELECT NAME,CREATEDTS FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'SYSIBM' AND TBNAME = 'SYSLGRNX' AND NAME = 'LGRDBID' AND CREATEDTS NOT IN('0001-01-01-00.00.00.000000'); If this query returns rows you have rows that need to be corrected by running the utility job CATMAINT UPDATE UNLDDN PM55333 This job will invalidate packages that are dependent on the directory tables, delete the catalog rows and then insert the correct rows. If the following query returns 0 rows SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1; The rows have not been added and they can be added using the same job. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55333 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This apar does not correct rows that where inserted into the catalog for the directory objects before the apar was applied. To see if you have rows that need to be updated run the query: SELECT NAME,CREATEDTS FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'SYSIBM' AND TBNAME = 'SYSLGRNX' AND NAME = 'LGRDBID' AND CREATEDTS NOT IN('0001-01-01-00.00.00.000000'); If this query returns rows you have rows that need to be corrected by running the utility job CATMAINT UPDATE UNLDDN PM55333 This job will invalidate packages that are dependent on 1 the directory tables, delete the catalog rows and then insert the correct rows. If the following query returns 0 rows SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1; The rows have not been added and they can be added using the same job. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUECM0 PM55333 DSNUECM5 PM55333 DSNUECSE PM55333 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55333 DSNUECM0 DSNUECM5 DSNUECSE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUECM0 DSNUECM5 DSNUECSE LISTEND UK78201 COVER LETTER END UK78204 COVER LETTER START PROBLEM DESCRIPTION(S): PM60939 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users. * **************************************************************** * PROBLEM DESCRIPTION: Running a REORG INDEX using the name * * of a catalog index that does not yet * * exist may fail with the following * * abend: * * * * ABEND04E RC00C90110 DSNUFOBD+09A6 * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** During the DB2 10 for z/OS ENFM process DB2 creates new indexes on new and existing catalog tables. If these new index names are specified with DB2 utilities prior to index creation then DB2 processing may abend as it did during REORG INDEX: ABEND04E RC00E40417 RC00C90110 DSNUFOBD OFFSET09A6 This problem would typically happen in V10 CM and in the ENFM process until the indexes are created. DB2 code has been updated to prevent future occurrences of the reported problem. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM60939 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGMAP PM60939 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60939 DSNUGMAP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGMAP LISTEND UK78204 COVER LETTER END UK78206 COVER LETTER START PROBLEM DESCRIPTION(S): PM57645 - **************************************************************** * USERS AFFECTED: All IRLM230 (HIR2230) users. * **************************************************************** * PROBLEM DESCRIPTION: IRLM abendS0C4 in DXRRL400 while trying * * to free a variable length storage. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM storage manager is called to release the storage of a variable length QE. The address of this QE in the register contains invalid value in its high-half causing the S0C4 abend. GEN: KEYWORDS: *** END IMS KEYWORDS *** The high-halves of registers are cleared before calling storage manager to release variable length storage. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM57645 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL710 PM57645 DXRRL711 PM57645 DXRRL712 PM57645 DXRRL720 PM57645 DXRRL730 PM57645 DXRRL731 PM57645 DXRRL750 PM57645 DXRRL790 PM57645 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57645 DXRRL710 DXRRL711 DXRRL712 DXRRL720 DXRRL730 DXRRL731 DXRRL750 DXRRL790 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL710 DXRRL711 DXRRL712 DXRRL720 DXRRL730 DXRRL731 DXRRL750 DXRRL790 LISTEND UK78206 COVER LETTER END UK78213 COVER LETTER START PROBLEM DESCRIPTION(S): PM51831 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of RESTORE SYSTEM utility with * * FROMDUMP * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DURING RESTORE SYSTEM UTILITY * * WHEN BACKUP IS ON TAPE * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran RESTORE SYSTEM utility with FROMDUMP (or equivalently, with zparm SPRMRRFD) to restore a system level backup on tape. The job abended with ABENDS0C4 in DSNUGDFE upon a subtask's return from DFSMSdss. RESTORE SYSTEM invokes DFSMSdss to process backups that are dumped to tape. When control is passed back to DB2, a special interface is used. This interface does not support parallel subtasks executing its code at the same time, and since subtasking is possible for RESTORE SYSTEM, the abend occurred. To avoid this problem, the DFSMSdss interface used by RESTORE SYSTEM utility was removed and replaced with a different one. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM51831 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUVBRD PM51831 DSNUVBUM PM51831 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM51831 DSNUVBRD DSNUVBUM 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUVBRD DSNUVBUM LISTEND UK78213 COVER LETTER END UK78215 COVER LETTER START PROBLEM DESCRIPTION(S): PM60820 - **************************************************************** * USERS AFFECTED: All IBM DB2 Analytics Accelerator (IDAA) * * using DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: 1. Message DSNT758I was incorrectly * * issued when the -DISPLAY ACCEL DB2 * * command was issued at a * * DB2 10 for z/OS (NFM) system. * * 2. Accelerator servers failed to start * * automatically during DB2 startup * * when DB2 10 for z/OS is operating * * in CM9 mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. When the IBM DB2 Analytics Accelerator (IDAA) is operating in a DB2 10 for z/OS (NFM) environment, which was migrated from DB2 for z/OS V8 (NFM), issuing the -DISPLAY ACCEL (DB2) command in this case would incorrectly cause a message DSNT758I condition to occur. The message DSNT758I is incorrectly issued because the -DISPLAY ACCEL command processor failed to consider the migration path that includes a DB2 for z/OS V8 (NFM) migrating to a DB2 10 for z/OS (NFM). Note: This problem also applies to the -START ACCEL (DB2) and -STOP ACCEL (DB2) commands. Note: This problem would not occur if DB2 10 for z/OS (NFM) was migrated from DB2 9 for z/OS (NFM). 2. When the DSN6SPRM ACCEL DB2 subsystem parameter is set to the value, "AUTO" (ie., ACCEL=AUTO), this specifies the accelerator servers are automatically enabled and started during DB2 startup. However, if the DB2 10 for z/OS system is operating in CM9 mode (not NFM), the accelerator startup process would not honor the auto start request during DB2 startup. This occurs because the accelerator startup processor was only honoring the auto start request if DB2 was operating in NFM. DB2 10 for z/OS has been changed to correctly determine the mode of operation for DB2 commands related to accelerator services, and automatically enabling and starting the accelerator servers (DSN6SPRM ACCEL=AUTO) during DB2 startup. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60820 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTMIN PM60820 DSNX8CMD PM60820 DSNX8IN2 PM60820 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60820 DSNLTMIN DSNX8CMD DSNX8IN2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTMIN DSNX8CMD DSNX8IN2 LISTEND UK78215 COVER LETTER END UK78230 COVER LETTER START PROBLEM DESCRIPTION(S): PM60499 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS or DB2 10 for z/OS users * * of the REORG TABLESPACE utility with the * * PART keyword. * **************************************************************** * PROBLEM DESCRIPTION: This is the DB2 Utilities Suite * * companion APAR to DB2 for z/OS * * APAR PM55051. The two APAR fixes * * must be applied at the same time. * **************************************************************** * RECOMMENDATION: * **************************************************************** Failure to apply this APAR fix with PM55051 will cause the new SORTNPSI keyword for REORG TABLESPACE PART to be rejected as invalid. Apply the PTF for PM60499 at the same time the PTF for PM55051 is applied. COMPONENT: 5740-XYR00-JDBAA1K APARS FIXED: PM60499 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for PM60499 is a companion fix and requires the fix for APAR PM55051 for FMID HDBAA10 to be applied. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUFFMM PM60499 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60499 DSNUFFMM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUFFMM LISTEND UK78230 COVER LETTER END UK78234 COVER LETTER START PROBLEM DESCRIPTION(S): PM61436 - **************************************************************** * USERS AFFECTED: Users of CROSS JOIN in a query with DB2 for * * z/OS Version 10.1. * **************************************************************** * PROBLEM DESCRIPTION: A query using the CROSS JOIN syntax to * * join more than two tables may result * * in one or more tables being omitted * * in the join operation. * * * * There is no problem if only two tables * * are being joined. * **************************************************************** * RECOMMENDATION: * **************************************************************** The CROSS JOIN syntax was added to DB2 for z/OS Version 10.1 via new function APAR PM29900. The following examples illustrate the problem, which is ONLY with the CROSS JOIN syntax. Join operations using INNER or LEFT/RIGHT OUTER JOIN syntax are not affected. CREATE TABLE T1 (T1C1 INT); CREATE TABLE T2 (T2C1 CHAR(1)); CREATE TABLE T3 (T3C1 DECIMAL(3,1)); INSERT INTO T1 VALUES (1); INSERT INTO T1 VALUES (2); INSERT INTO T2 VALUES ('A'); INSERT INTO T2 VALUES ('B'); INSERT INTO T3 VALUES (4.1); INSERT INTO T3 VALUES (5.2); The following joins of the three tables using the CROSS JOIN syntax result in table T2 being omitted from the join operation: SELECT * FROM T1 CROSS JOIN T2 CROSS JOIN T3; 1 +------------------------------------------+ | T1C1 | T3C1 | +------------------------------------------+ 1_| 1 | 4.1 | 2_| 1 | 5.2 | 3_| 2 | 4.1 | 4_| 2 | 5.2 | +------------------------------------------+ SELECT * FROM T1 CROSS JOIN T2, T3; +------------------------------------------+ | T1C1 | T3C1 | +------------------------------------------+ 1_| 1 | 4.1 | 2_| 1 | 5.2 | 3_| 2 | 4.1 | 4_| 2 | 5.2 | +------------------------------------------+ If only two tables are joined, there is no problem: SELECT * FROM T1 CROSS JOIN T2; +-----------------------+ | T1C1 | T2C1 | +-----------------------+ 1_| 1 | A | 2_| 1 | B | 3_| 2 | A | 4_| 2 | B | +-----------------------+ If the tables are joined using multiple tables in the table-reference list in the FROM clause, then all tables are included with no error: SELECT * FROM T1, T2, T3; +--------------------------------------------+ | T1C1 | T2C1 | T3C1 | +--------------------------------------------+ 1_| 1 | A | 4.1 | 2_| 1 | A | 5.2 | 3_| 1 | B | 4.1 | 4_| 1 | B | 5.2 | 5_| 2 | A | 4.1 | 6_| 2 | A | 5.2 | 7_| 2 | B | 4.1 | 8_| 2 | B | 5.2 | +--------------------------------------------+ Additional keywords: SQLCROSSJOIN SQLACCESSPATH SQLINCORROUT DB2INCORR/K DB2 code is corrected so that multiple tables referenced in 1 a CROSS JOIN operation are all included in the join operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61436 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHSM10 PM61436 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61436 DSNHSM10 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHSM10 LISTEND UK78234 COVER LETTER END UK78235 COVER LETTER START PROBLEM DESCRIPTION(S): PM58420 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: High class 14 latch (LC14) contention, * * on BMVTPBXL latch. * **************************************************************** * RECOMMENDATION: * **************************************************************** Latch contention may exist on the BMVTPBXL latch, which serializes the pageset hash chains, if there are a large number of concurrent jobs either starting up or committing concurrently. To reduce LC14 contention, the single BMVTPBXL latch has been replaced by multiple latches (one for each pageset hash chain). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58420 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CPS PM58420 DSNB1LRR PM58420 DSNB1OFA PM58420 DSNB1OPS PM58420 DSNB1PMI PM58420 DSNB1PMT PM58420 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58420 DSNB1CPS DSNB1LRR DSNB1OFA DSNB1OPS DSNB1PMI DSNB1PMT 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CPS DSNB1LRR DSNB1OFA DSNB1OPS DSNB1PMI DSNB1PMT LISTEND UK78235 COVER LETTER END UK78243 COVER LETTER START PROBLEM DESCRIPTION(S): PM60824 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of RECOVER utility. * **************************************************************** * PROBLEM DESCRIPTION: A RECOVER utility restored an empty * * image copy to a table space without * * error. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A RECOVER utility ran on a table space. It restored an image copy which was an empty data set but had the same name as a vaild image copy without error. It cleared all the data from the table in that table space. The problem occurred because the RECOVER utility mistakenly treated the empty data set as an end of file condition, and not an error. The RECOVER code has been modified to issue the message DSNU1408I if the image copy data set is empty. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60824 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCBAL PM60824 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60824 DSNUCBAL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBAL LISTEND UK78243 COVER LETTER END 1 UK78247 COVER LETTER START PROBLEM DESCRIPTION(S): PM60056 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Code is being added to support a future * * function of DB2. * **************************************************************** * RECOMMENDATION: * **************************************************************** Code is being added to support a future function of DB2. The function being added will be enabled at a later date. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60056 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFMDIR PM60056 DSNF7DIR PM60056 DSN7GCHK PM60056 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60056 DSNFMDIR DSNF7DIR DSN7GCHK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNF7DIR DSN7GCHK LISTEND UK78247 COVER LETTER END UK78263 COVER LETTER START PROBLEM DESCRIPTION(S): PM60937 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: A CONNECT statement on a DB2 for z/OS * * requester abends with: * * ABEND0C4-RC00D3440B DSNLXRCN:000F * **************************************************************** * RECOMMENDATION: * **************************************************************** An application executes a Type 2 CONNECT statement after it has previously executed a Type 1 CONNECT statement. This is an invalid request and should fail with SQLCODE -808. Instead, DB2 incorrectly abends: 1 ABEND0C4-RC00D3440B DSNLXRCN:000F. DB2 has been changed to return SQLCODE -808 instead of abending. NOTE: A work-around to this problem would be to release all connections and issue a COMMIT prior to switching connect types. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60937 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXRCN PM60937 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60937 DSNLXRCN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXRCN LISTEND UK78263 COVER LETTER END UK78270 COVER LETTER START PROBLEM DESCRIPTION(S): PM57955 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of parallel sort- * * merge join with range list table access * * type. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 in DSNXORGL * * P130 may occur when a query with range * * list access type (ACCESSTYPE = 'NR' in * * PLAN_TABLE) table participated in a * * parallel sort-merge join group. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 in DSNXORGL P130 may occur when a query with range list access type (ACCESSTYPE = 'NR' in PLAN_TABLE) table participated in a parallel sort-merge join group. It is because the sanity check condition is not set up properly. Following is an example of such failing query: SELECT COUNT ( * ) FROM T1, T2, T3 WHERE T1.C1 = T2.C1 AND T2.C1 = T3.C1 AND T1.C2 = T2.C2 AND T2.C3 = T3.C3 1 AND T1.C4 = ' ' AND T1.C1 = ? AND T1.C5 = ? AND T1.C6 = 'S' AND ( ( T3.C7 = ? AND T3.C8 = ? AND T3.C4 = ? ) OR ( T3.C7 = ' ' ) ) AND T1.C9 = ? ; Note: T3 index IDX01 is picked as the range list access index CREATE INDEX IDX01 ON T3 (C1, C7, C4, C8, CX, C3) ; DB2 is modified to refine the sanity check condition to eliminate the false alarm. Additional Keywords: PARALLELISM SQLPARALLELISM SQLSMJ SQLMSJ SMJ MSJ SQLRANGELIST ABEND04E RC00E70005 DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57955 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 PM57955 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57955 DSNXORGL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXORGL LISTEND UK78270 COVER LETTER END UK78271 COVER LETTER START PROBLEM DESCRIPTION(S): PM56300 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using timestamp * * data type in between predicate in one check * * constraint. * **************************************************************** * PROBLEM DESCRIPTION: A SQLCODE -546 may be incorrectly * * issued for CREATE TABLE or ALTER TABLE * * statement that satisfies all of the * * following conditions: * * * * 1. the CHECK CONSTRAINT clause contains * * a BETWEEN predicate; * * * * 2. TIMESTAMP data is referenced in * * aforementioned BETWEEN predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** A SQLCODE -546 may be incorrectly issued for CREATE TABLE or ALTER TABLE statement that satisfies all of the following conditions: 1. the CHECK CONSTRAINT clause contains a BETWEEN predicate; 2. TIMESTAMP data is referenced in aforementioned BETWEEN predicate. Example: ============================================================ CREATE TABLE T1 ( C1 TIMESTAMP NOT NULL WITH DEFAULT, CONSTRAINT TESTCON CHECK (C1 BETWEEN '1995-01-01-00.00.00.000000' AND '2059-12-31-24.00.00.000000' ) ) SQLCODE -546 may be incorrectly issued because DB2 did not not process the BETWEEN predicate with TIMESTAMP data type correctly, and wrongly issued SQLCODE -546. The code in DB2 has been modified correctly to handle the aforementioned BETWEEN predicate with TIMESTAMP data type in constraint of DDL. additional Keywords: SQLTIMESTAMP SQLBETWEEN SQLCODE546 SQLCONSTRAINT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56300 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM47894: See PM47894 APAR/PTF text for additional information about why a REBIND is necessary. 1 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOW2C PM56300 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56300 DSNXOW2C THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOW2C LISTEND UK78271 COVER LETTER END UK78286 COVER LETTER START PROBLEM DESCRIPTION(S): PM61161 - **************************************************************** * USERS AFFECTED: DB2 9 and DB2 10 for z/OS users of hybrid * * join and varbinary data * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may be returned for a * * query that references varbinary data * * and involves a hybrid join access path. * * The value of the varbinary column has * * the same value instead of the value * * for each row. * **************************************************************** * RECOMMENDATION: * **************************************************************** The incorrect output may occur for a query using hybrid join which references varbinary data. The inner table has an index which is clustered and no sort is needed (hybrid join case 2). The varbinary column is selected from the outer table. The problem occurs when the internal buffer for the varbinary data is greater than 256 bytes. The buffer length includes the declared length of the column plus 2 bytes for length and 1 byte for null if the data type is nullable. 1 For example, the following query uses hybrid join where T1 is the outer table and T2 is the inner table. CREATE TABLE T1 (C1 INT, C2 VARBINARY(254)); CREATE TABLE T2 (C1 INT, C2 VARBINARY(254)); CREATE UNIQUE INDEX IX1 ON T1(C1); CREATE UNIQUE INDEX IX2 ON T2(C1) CLUSTER; INSERT INTO T1 VALUES(1,VARBINARY('11111')); INSERT INTO T1 VALUES(2,VARBINARY('22222')); INSERT INTO T1 VALUES(3,VARBINARY('33333')); INSERT INTO T2 VALUES(1,VARBINARY('44444')); INSERT INTO T2 VALUES(2,VARBINARY('55555')); INSERT INTO T2 VALUES(3,VARBINARY('66666')); SELECT A.C1, A.C2, B.C2 FROM T1 A, T2 B WHERE A.C1 = B.C1 The value returned for A.C2 may be incorrect if the length of the varbinary column buffer is more than 256 bytes. The following is the incorrect data returned: C1 A.C2 B.C2 -- ----- ----- 1 33333 44444 2 33333 55555 3 33333 66666 The result should be : C1 A.C2 B.C2 -- ----- ----- 1 11111 44444 2 22222 55555 3 33333 66666 DB2 has been fixed to correctly move the varbinary data using the actual length instead of the declared length. This will prevent the incorrect output. Additional keywords : SQLHYBRIDJOIN SQLVARBINARY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61161 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRFHJ PM61161 DSNXRFH9 PM61161 DSNXRFJ9 PM61161 DSNXRGBJ PM61161 DSNXRGB9 PM61161 1 DSNXRSFJ PM61161 DSNXRT3J PM61161 DSNXRT39 PM61161 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61161 DSNXRFHJ DSNXRFH9 DSNXRFJ9 DSNXRGBJ DSNXRGB9 DSNXRSFJ DSNXRT3J DSNXRT39 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRFHJ DSNXRFH9 DSNXRFJ9 DSNXRGBJ DSNXRGB9 DSNXRSFJ DSNXRT3J DSNXRT39 LISTEND UK78286 COVER LETTER END UK78310 COVER LETTER START PROBLEM DESCRIPTION(S): PM61001 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using profile tables * * facility to monitor threads and connections * * for TCP/IP access to a DB2 server. * **************************************************************** * PROBLEM DESCRIPTION: The IFCID 402 QW0402TQ may report an * * inaccurate value over time, when DB2 * * determines to queue or suspend a * * server thread due to a system profile * * monitoring exception. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a defined system profile monitoring threshold is exceeded, a system profile monitoring exception condition occurs. When it occurs, DB2 attempts to queue or suspend the server thread, if the total number of server threads queued or suspended does not exceed the defined profile exception threshold value. When the server thread is queued or suspended, DB2 should update the IFCID402 QW0402TQ accumulated counter to report the total number of times this event occurred for the defined profile. However, in the reported problem DB2 failed to update the IFCID402 QW0402TQ accumulated counter when a server thread is either queued or suspended and thus reports an inaccurate QW0402TQ value over time. DB2 System Profile Monitor processing has been changed to properly increment the accumulated statistical counter, 1 QW0402TQ, whenever a system profile monitor exception threshold is exceeded and the server thread is determined to be queued or suspended. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61001 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLQDIS PM61001 DSNLTACT PM61001 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61001 DSNLQDIS DSNLTACT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLQDIS DSNLTACT LISTEND UK78310 COVER LETTER END UK78338 COVER LETTER START PROBLEM DESCRIPTION(S): PM58427 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: Following a DROP TABLESPACE and a * * CREATE TABLESPACE DEFINE NO without a * * COMMIT in between, an SQL INSERT may * * fail with SQLCODE-904 RC00D70004 * * indicating drop list pending. It is * * accompanied with console message * * MSGDSNP016I DSNPCPS0 RC00D70004. * **************************************************************** * RECOMMENDATION: * **************************************************************** Processing of CREATE TABLESPACE checks the drop pending state for DEFINE YES but not for DEFINE NO. The first INSERT which creates the data set will check the drop pending state. If exists, an error RC00D70004 is returned. DB2 user requests to block at CREATE TABLESPACE DEFINE NO instead of waiting until INSERT. The code is changed to check drop pending state at CREATE TABLESPACE DEFINE NO and CREATE INDEX DEFINE NO. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58427 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 DSNPCPS0 PM58427 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58427 DSNPCPS0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNPCPS0 LISTEND UK78338 COVER LETTER END UK78343 COVER LETTER START PROBLEM DESCRIPTION(S): PM57851 - **************************************************************** * USERS AFFECTED: All users of DB2 sample job DSNTEJ67 in DB2 * * 9.1 for z/OS and DB2 10 for z/OS are * * affected by this change. * **************************************************************** * PROBLEM DESCRIPTION: Job DSNTEJ67 job step PH067S04 ends * * with return code 8 and these messages: * * * * Setting up the native SQL PL helper * * routine... * * *CRSQLPL* Deploying SP: * * "DSN8"."DSN8EN1" * * *CRSQLPL* Error * * SQLCODE = * * . . . * * DSNTEJ67 cannot deploy the native SP * * used for migration. * * * * where is -104 or -20071. * * * * In V10 only, these SQLCODEs may also * * be received when processing native SQL * * function DSN8.DSN8EF1. * **************************************************************** * RECOMMENDATION: Apply the fixing PTF for this APAR. * **************************************************************** DB2 job DSNTEJ67 demonstrates a way to convert an external SQL procedure to a native SQL procedure. Currently, depending on local DB2 configuration, DSNTEJ67 can terminate in job step PH067S04 with return code 8 and these messages: Setting up the native SQL PL helper routine... *CRSQLPL* Deploying SP: "DSN8"."DSN8EN1" *CRSQLPL* Error SQLCODE = . . . DSNTEJ67 cannot deploy the native SP used for migration. 1 due to one of the following errors: (1) SQLCODE -104 when DB2 uses DSNHDECP.DECIMAL=COMMA. This error can occur because some coding in sample native SQL procedure DSN8.DSN8EN1 (which is prepared by job DSNTEJ67) contains tokens separated by commas that are not immediately followed by a blank. Such coding, when processed by a DB2 that uses the comma as the decimal point indicator (in other words uses DSNHDECP.DECIMAL=COMMA), is interpreted as an invalid numeric value and rejected with SQLCODE -104. In V10 only, this error can also be encountered when processing sample native SQL function DSN8.DSN8EF1. (2) SQLCODE -20071 when DB2 uses DSN6SYSP.WLMENV set to blank and native SQL debugging is not DISABLED. Currently, the CREATE PROCEDURE statement for DSN8.DSN8EN1 does not specify the DEBUG MODE clause, thus the DEBUG MODE default is determined from the value of the CURRENT DEBUG MODE special register. The CREATE PROCEDURE statement for DSN8.DSN8EN1 also does not specify the WLM ENVIRONMENT FOR DEBUG MODE clause, thus the default is determined using the value of the DSN6SYSP.WLMENV subsystem parameter. If the value of DSN6SYSP.WLMENV is blank when debugging is activated, processing of DSN8.DSN8EN1 fails with SQLCODE -20071 because no default WLM environment is defined. In V10 only, this error can also be encountered when processing sample native SQL function DSN8.DSN8EF1. Additional keywords: SQLPL SQLNATIVESQLPL SQLPROC SQLSCALARUDF SQLCODE104 SQLCODE20071 In response, this APAR makes the following changes to DSN8EN1, the source code for DSN8.DSN8EN1 and (in V10 only) to DSN8EF1, the source code for the sample native SQL function, DSN8.DSN8EF1: (1) To resolve the SQLCODE -104 error, all SQL statements that are not compatible with use of the DSNHDECP.DECIMAL=COMMA option are corrected. (2) To resolve the SQLCODE -20071 error, the DISABLE DEBUG MODE clause is added to the CREATE statements to ensure that a default WLM environment name is never required. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57851 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN8EF1 PM57851 DSN8EN1 PM57851 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57851 DSN8EF1 DSN8EN1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS 1 DSN8EF1 DSN8EN1 LISTEND UK78343 COVER LETTER END UK78358 COVER LETTER START PROBLEM DESCRIPTION(S): PM58947 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS OF RECOVER UTILITY WHEN RECOVERING A * * PARTITIONED OBJECT TO A PRIOR POINT AND A * * SYSTEM LEVEL BACKUP IS USED TO RESTORE THE * * OBJECT * **************************************************************** * PROBLEM DESCRIPTION: RESIDUAL DATA EXISTS IN PARTITIONED * * OBJECT AFTER BEING RECOVERED BY * * RECOVER UTILITY WITH DSNUM ALL AND * * TO A POINT IN TIME BEFORE PARTITIONS * * WERE ADDED AND A SYSTEM LEVEL * * BACKUP WAS USED AS A BASE FOR * * RECOVERY * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran the following scenario on a PBG (partitioned by growth) table space with 4 partitions: 1. BACKUP SYSTEM utility was run, establishing a system-level backup (SLB) for use as a recovery base. 2. rows were inserted which caused the table space to grow from 4 partitions to 5. (Note that using the ALTER command to add a 5th part explicitly to a non-PBG object would be equivalent to this step and such a scenario is also addressed by this apar.) 3. RECOVER utility DSNUM ALL with TORBA or TOLOGPOINT was run to a point before the 5th part was added. The SLB was correctly used as a recovery base. The RECOVER job appeared to complete successfully, but it was later found that the newly added partition (part 5) was not reset by the utility, and the data in this partition effectively remained in the table space. This led also to unexpected error ranges (WEPR) and pending status issues for the affected object. The reason this happened is that when an SLB was used as a recovery base, the partitions added after the SLB was made were not properly reset. Code was changed in RECOVER utility to reset added parts when using an SLB as a recovery base and recovering to a point in time before the parts were added. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58947 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 DSNUCALA PM58947 DSNUCARS PM58947 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58947 DSNUCALA DSNUCARS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCALA DSNUCARS LISTEND UK78358 COVER LETTER END UK78360 COVER LETTER START PROBLEM DESCRIPTION(S): PM57346 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * external Stored Procedures that are * * written in language PLI. * **************************************************************** * PROBLEM DESCRIPTION: PL/I PUT DATA can display undesired * * characters in the PL/I Character * * Descriptor Field for a PL/I input * * parameter of an external Stored * * Procedure. * **************************************************************** * RECOMMENDATION: * **************************************************************** The PL/I PUT DATA can display undesired characters in the PL/I Character Descriptor Field for a PL/I input parameter of an external Stored Procedure. The following example illustrates the problem. 1. Create an external Stored Procedure in PL/I. CREATE PROCEDURE SPF6 (IN_PARM CHAR(10) IN) LANGUAGE PLI EXTERNAL SPF6 WLM ENVIRONMENT WLMENV2 PROGRAM TYPE MAIN RESULT SETS 1; SPF6: PROC(IN_PARM) OPTIONS(MAIN NOEXECOPS ); //include SQLCA, SQLDA, and variable declaration ...... PUT SKIP DATA(IN_PARM); 1 //EXEC any SQL statement here ...... END SPF6; 2. Create a calling application. DCL HCHAR CHAR(10); HCHAR = 'TEST'; EXEC SQL CALL SPF6(:HCHAR); When the calling application is executed, character string 'TEST' is passed to Stored Procedure SPF6. The PUT SKIP DATA inside SPF6 is expected to display as IN_PARM='TEST '. However, some undesired characters could be displayed instead because DB2 does not initialize the PL/I Descriptor Fields before passing it to SPF6. The code in DB2 has been modified to initialize the PL/I Character Descriptor Field before passing it to the Stored Procedure as the input parameter. Additional Keywords: SQLSTOREDPROC SQLSP DB2SP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57346 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRPPL PM57346 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57346 DSNXRPPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPPL LISTEND UK78360 COVER LETTER END UK78396 COVER LETTER START PROBLEM DESCRIPTION(S): PM62051 - **************************************************************** * USERS AFFECTED: All DB2 users who use remote BIND PACKAGE * * command. * **************************************************************** * PROBLEM DESCRIPTION: When doing a remote BIND PACKAGE, DB2 * * tries to acquire an exclusive lock on * 1 * the local package, which may result in * * a timeout on other applications. * **************************************************************** * RECOMMENDATION: * **************************************************************** During a remote BIND PACKAGE, DB2 unnecessarily tries to acquire an exclusive lock on a package residing on the requester side, which may cause a timeout on the BIND job or other applications. DB2 has been fixed to not acquire an exclusive lock on packages at the requester side during remote BIND PACKAGE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62051 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBCM2 PM62051 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62051 DSNTBCM2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBCM2 LISTEND UK78396 COVER LETTER END UK78401 COVER LETTER START PROBLEM DESCRIPTION(S): PM52083 - **************************************************************** * USERS AFFECTED: DB2 for z/OS Version 8 users of CREATE * * PROCEDURE * **************************************************************** * PROBLEM DESCRIPTION: User receives ABEND04E at location * * DSNXICRT:P155 on CREATE PROCEDURE. * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 for z/OS Version 8 on CREATE PROCEDURE, users may receive ABEND04E RC00E70006 during DB2 processing for the case where users have already created procedures defined with WLM ENVIRONMENT names greater than 18 EBCDIC bytes in DB2 9 or 10 for z/OS conversion mode (CM), and then attempt to CREATE PROCEDURE after falling back to DB2 for z/OS Version 8. The same abend may occur for CREATE FUNCTION or CREATE DISTINCT TYPE, also due to procedures already created and defined with WLM ENVIRONMENT names greater than 18 EBCDIC bytes. DB2 for z/OS Version 8 CREATE PROCEDURE has been fixed. In DB2 9 and 10 for z/OS conversion mode (CM8 only), for new 1 CREATE PROCEDURE statements, SQLCODE -107 will now be issued if the WLM ENVIRONMENT name specified is longer than 18 EBCDIC bytes to remain compatible for any fallback to or coexistance with DB2 Version 8. This APAR does not fix any existing cases where WLM ENVIRONMENT name is longer than 18 EBCDIC bytes. Once in DB2 9 or 10 for z/OS new function mode, there will no longer be an 18 EBCDIC byte restriction for WLM ENVIRONMENT name. ++HOLD COMMENT FOR RELEASE A10, TYPE DOC: PM52083 introduces the following changes to externals and the approximate text will be added to the V10 DB2 SQL Codes. This text is subject to change. Explanation added to SQLCODE -107: THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size Explanation: In V9 CM and V10 CM8, WLM ENVIRONMENT names must not exceed 18 EBCDIC bytes. 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. ++HOLD COMMENT FOR RELEASE 910, TYPE DOC: PM52083 introduces the following changes to externals and the approximate text will be added to the V9 DB2 SQL Codes. This text is subject to change. Explanation added to SQLCODE -107: THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size Explanation: In V9 CM, WLM ENVIRONMENT names must not exceed 18 EBCDIC bytes. 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. Additional Keywords: SQLCODE107 SQLEXTERNALSQLPL SQLPROCEDURE SQLCREATE SQLPL DB2SP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM52083 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 DOCUMENTATION: PM52083 introduces the following changes to externals and the approximate text will be added to the V10 DB2 SQL Codes. This text is subject to change. Explanation added to SQLCODE -107: THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size Explanation: In V9 CM and V10 CM8, WLM ENVIRONMENT names must not exceed 18 EBCDIC bytes. 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 DSNXIVNO PM52083 DSNXIVRO PM52083 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM52083 DSNXIVNO DSNXIVRO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIVNO DSNXIVRO LISTEND UK78401 COVER LETTER END UK78421 COVER LETTER START PROBLEM DESCRIPTION(S): PM62295 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of Spatial support. * **************************************************************** * PROBLEM DESCRIPTION: This apar provides the following new * * sample functions: * * * * * * DB2GSE.IDXKEY2DG * * * * This function has 2 inputs: a Spatial * * object type ST_POINT and a gridSize * * type DOUBLE. It returns a grid * * cell type BIGINT. * * * * DB2GSE.GETGRIDMBR * * * * This function has 2 inputs: a grid * * cell type BIGINT (a value returned by * * the above function) and a grid size * 1 * type DOUBLE. It returns a table of * * 6 values of the x, y cells and the * * MBR values. * **************************************************************** * RECOMMENDATION: * **************************************************************** This apar provides the following two new sample functions. DB2GSE.IDXKEY2DG and DB2GSE.GETGRIDMBR The user can use these functions in two steps: 1. Get the grid cell from DB2GSE.IDXKEY2DG. 2. Get the values of the x, y cells and the MBR values from DB2GSE.GETGRIDMBR. Here is an example of using these two functions. SELECT DB2GSE.IDXKEY2DG( DB2GSE.ST_POINT( 1,1 ,1003) , 1) , FROM SYSADM.SYSDUMMY1 ; -------------------- 4294967297 SELECT T.XCELL, T.YCELL, T.MINX, T.MINY, T.MAXX, T.MAXY FROM TABLE (DB2GSE.GETGRIDMBR( 4294967297, 1) ) T ; XCELL YCELL MINX MINY ----- ----- ---------------------- ---------------------- 1 1 +1.00000000000000E+000 +1.00000000000000E+000 MAXX MAXY ---------------------- ---------------------- +2.00000000000000E+000 +2.00000000000000E+000 This apar provides two new sample functions DB2GSE.IDXKEY2DG and DB2GSE.GETGRIDMBR which can be used to retrieve grid cells. The user can use these functions in two steps: 1. Get the grid cell from DB2GSE.IDXKEY2DG. 2. Get the values of the x, y cells and the MBR values from DB2GSE.GETGRIDMBR. Here is an example of using these two functions. SELECT DB2GSE.IDXKEY2DG( DB2GSE.ST_POINT( 1,1 ,1003) , 1) , FROM SYSADM.SYSDUMMY1 ; -------------------- 1 4294967297 SELECT T.XCELL, T.YCELL, T.MINX, T.MINY, T.MAXX, T.MAXY FROM TABLE (DB2GSE.GETGRIDMBR( 4294967297, 1) ) T ; XCELL YCELL MINX MINY ----- ----- ---------------------- ---------------------- 1 1 +1.00000000000000E+000 +1.00000000000000E+000 MAXX MAXY ---------------------- ---------------------- +2.00000000000000E+000 +2.00000000000000E+000 Additional Keywords: SQLSPATIAL PM64616 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of Spatial support. * **************************************************************** * PROBLEM DESCRIPTION: Complete the fix for apar PM62295. * **************************************************************** * RECOMMENDATION: * **************************************************************** Complete the fix for apar PM62295. Complete the fix for apar PM62295. COMPONENT: 5655-R1402-J2AG210 APARS FIXED: PM62295,PM64616 SPECIAL CONDITIONS: COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This apar provides two new sample functions. 1. Function DB2GSE.IDXKEY2DG Function is used to retrieve the current grid cells from the starting point. 2. Function DB2GSE.GETGRIDMBR Function is used to retrieve the x and y cells and the MBR values. For existing users, to be able to use these functions, please submit the last two steps (CREATE02 and BINDSK19) of the DSN5SENB job. For new users, please follow the instructions contained in the publication "IBM Spatial Support for DB2 z/OS" to enable Spatial functionality. The warning message GIM43401W can be received when applying this apar. It can be ignored. ACTION: 1 This APAR is a replacement for apar PM47333, ptf UK72946. This apar provides the function to retrieve the current and surrounding grid cells from a starting point. For existing users, if they would like to use this function, please submit the last two steps (CREATE01 and BINDSK19) of the DSN5SENB job. For new users, please follow the instructions contained in the publication "IBM Spatial Support for DB2 z/OS" to enable Spatial functionality. ACTION: This apar provides the functions to retrieve the current and surrounding grid cells from a starting point. For the existing users, if they like to use this function then submit 2 last steps: CREATE01 and BINDSK19 of DSN5SENB job. For the new users should follow the instructions contained in the book IBM Spatial Support for DB2 z/OS to enable Spatial functionality. DELETE: ++MOD TO BE REMOVED FROM USER'S MVS SYSTEM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@SK19 PM62295 PM64616 DSN5SDEN PM62295 PM64616 DSN5SENB PM62295 PM64616 DSN5SK20 PM64616 DSN5SK21 PM64616 DSN5SK28 PM64616 DSN5SK29 PM62295 PM64616 DSN5SK30 PM64616 DSN5SK40 PM62295 PM64616 DSN5SK41 PM62295 PM64616 DSN5SK42 PM62295 PM64616 J2AG210J PM62295 PM64616 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62295 DSN@SK19 DSN5SDEN DSN5SENB DSN5SK29 DSN5SK40 DSN5SK41 DSN5SK42 J2AG210J PM64616 DSN@SK19 DSN5SDEN DSN5SENB DSN5SK20 DSN5SK21 DSN5SK28 DSN5SK29 DSN5SK30 DSN5SK40 DSN5SK41 DSN5SK42 J2AG210J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN5SDEN DSN5SK20 DSN5SK21 DSN5SK28 DSN5SK29 DSN5SK30 DSN5SK40 DSN5SK41 1 DSN5SK42 MACROS DSN@SK19 DSN5SENB LISTEND UK78421 COVER LETTER END UK78426 COVER LETTER START PROBLEM DESCRIPTION(S): PM57441 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of utilities. * **************************************************************** * PROBLEM DESCRIPTION: THIS IS A SERVICEABILITY APAR WHICH * * DOES NOT AFFECT ANY EXTERNAL FUNCTION. * * NO PROBLEM IS FIXED BY THIS APAR. * **************************************************************** * RECOMMENDATION: * **************************************************************** This is a serviceability apar for DB2 for z/OS utilities. No problem is fixed by this apar. Serviceability apar only. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57441 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBBCD PM57441 DSNUGFCB PM57441 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57441 DSNUBBCD DSNUGFCB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBBCD DSNUGFCB LISTEND UK78426 COVER LETTER END UK78452 COVER LETTER START PROBLEM DESCRIPTION(S): PM56466 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for * * z/OS who use DSNREXX. * **************************************************************** * PROBLEM DESCRIPTION: One or both of the following may occur: * 1 * (1) DB2 ABENDS0C4 when using DSNREXX * * (2) corrupted DSNREXX SQLCA values * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** (1) When a rexx variable's contents start with an invalid number and is passed to DSNREXX as an SQL statement, a DSNREXX stored procedure may abend with ABEND0C4 RC16. (2) When an SQL Error or Warning occurs and the resulting message token exceeds 70 bytes, the DSNREXX SQLCA values may be corrupted. DSNREXX is updated to prevent both problems. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56466 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTZAAA PM56466 DSNTZALI PM56466 DSNTZALO PM56466 DSNTZASO PM56466 DSNTZCAL PM56466 DSNTZCLS PM56466 DSNTZCOM PM56466 DSNTZCON PM56466 DSNTZDCL PM56466 DSNTZDSC PM56466 DSNTZEXE PM56466 DSNTZFET PM56466 DSNTZFRE PM56466 DSNTZNTO PM56466 DSNTZOPN PM56466 DSNTZPRP PM56466 DSNTZRLS PM56466 DSNTZROL PM56466 DSNTZSET PM56466 DSNTZTOK PM56466 DSNTZUSI PM56466 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56466 DSNTZAAA DSNTZALI DSNTZALO DSNTZASO DSNTZCAL DSNTZCLS DSNTZCOM DSNTZCON DSNTZDCL DSNTZDSC DSNTZEXE DSNTZFET DSNTZFRE DSNTZNTO DSNTZOPN DSNTZPRP DSNTZRLS DSNTZROL DSNTZSET DSNTZTOK DSNTZUSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTZAAA DSNTZALI DSNTZALO DSNTZASO DSNTZCAL 1 DSNTZCLS DSNTZCOM DSNTZCON DSNTZDCL DSNTZDSC DSNTZEXE DSNTZFET DSNTZFRE DSNTZNTO DSNTZOPN DSNTZPRP DSNTZRLS DSNTZROL DSNTZSET DSNTZTOK DSNTZUSI LISTEND UK78452 COVER LETTER END UK78455 COVER LETTER START PROBLEM DESCRIPTION(S): PM57347 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V10 users of Universal * * Table space or Segmented table space * **************************************************************** * PROBLEM DESCRIPTION: Insert statement results in ABEND04E * * at DSNISGSC ERQUAL5002. * **************************************************************** * RECOMMENDATION: * **************************************************************** A sanity check of DSNISGSC:5002 was triggered falsely when the space search process encounters a dictionary segment during the search for available segments. DB2 code has been fixed to tolerate the dictionary segment in the sanity checking when locating free space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57347 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISGSC PM57347 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57347 DSNISGSC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGSC LISTEND 1UK78455 COVER LETTER END UK78467 COVER LETTER START PROBLEM DESCRIPTION(S): PM60188 - **************************************************************** * USERS AFFECTED: All DB2 users in a non-data-sharing * * environment. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNB1DRA * **************************************************************** * RECOMMENDATION: * **************************************************************** When -ACCESS DATABASE( ) SPACENAM( ) MODE(NGBPDEP) command is issued in a non-data-sharing environment to perform an operation that is only applicable to a data sharing environment (to convert a specified page set or partition to non-group-buffer- pool-dependent), DB2 encounters an abend when an invalid pointer is used. DB2 has been fixed to correctly set the pointer before its use. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60188 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 PM60188 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60188 DSNB1DRA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DRA LISTEND UK78467 COVER LETTER END UK78472 COVER LETTER START PROBLEM DESCRIPTION(S): PM56612 - **************************************************************** * USERS AFFECTED: DB2 9 and DB2 10 users of native SQL * * procedures and Bind Deploy. * **************************************************************** * PROBLEM DESCRIPTION: When a user is doing a Bind Deploy * * of a native SQL procedure to a * * data sharing system while at the * * period of time where the Bind * * Deploy has not finished yet, SQL * * Call statements are being made to * * that particular procedure in the * 1 * same system the SQL Call statements * * may get SQLCODE440 and subsequent * * SQL Call statements to that procedure * * may keep getting intermittent * * SQLCODE440 even after the Bind Deploy * * has successfully finished. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** This issue is caused by a timing window in the stored procedure resolution cache invalidation during commit processing. At end of Bind Deploy processing, the cache is invalidating an entry and at the same time an SQL Call statement comes and add another entry resulting in cached information that is inconsistent with the catalog information. Cache entry invalidation process is improved to eliminate timing window that can result in cache inconsistencies. Additional Keywords: SQLPL SQLNATVESQLPL SQLPROCEDURE SQLSP SQLSTOREDPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56612 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECW PM56612 DSNXECWA PM56612 DSNXECWU PM56612 DSNXIART PM56612 DSNXICRT PM56612 DSNXIDRT PM56612 DSNXI14 PM56612 DSNXMIT2 PM56612 DSNX9CCM PM56612 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56612 DSNXECW DSNXECWA DSNXECWU DSNXIART DSNXICRT DSNXIDRT DSNXI14 DSNXMIT2 DSNX9CCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECW DSNXECWA DSNXECWU DSNXIART DSNXICRT DSNXIDRT DSNXI14 DSNXMIT2 DSNX9CCM 1 LISTEND UK78472 COVER LETTER END UK78476 COVER LETTER START PROBLEM DESCRIPTION(S): PM58562 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of alter table functions (data Versioning). * **************************************************************** * PROBLEM DESCRIPTION: Serviceability APAR for an ABEND04E * * RC00c90101 in DSNISUPI 2002 vrace2002. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a specific table version record is inserted to a system page of a partition, the RID of the record is updated to the header page of that partition. This code is added to aid in diagnose of a problem that the incorrect header page is being updated with the RID of the record. This code will not solve the reported abend, but will detect the incorrect header page problem at an early stage. DB2 code is changed to have a sanity check on the partition number of the header page and system page. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58562 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 PM58562 DSNISMRS PM58562 DSNISRTI PM58562 DSNIVOBD PM58562 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58562 DSNIFOD DSNISMRS DSNISRTI DSNIVOBD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIFOD DSNISMRS DSNISRTI DSNIVOBD LISTEND UK78476 COVER LETTER END UK78479 COVER LETTER START PROBLEM DESCRIPTION(S): PM58838 - 1 **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of the DB2 command * * DISPLAY GROUP. * **************************************************************** * PROBLEM DESCRIPTION: While running the DB2 command DISPLAY * * GROUP,the follow error message may * * appear in place of the usual XFC and * * STRUCTURE information. * * * * XCF OR STRUCTURE INFORMATION NOT * * AVAILABLE * * MVS IXLMG RETURN CODE = 00000008 * * MVS IXLMG REASON CODE = 0000080E * * * **************************************************************** * RECOMMENDATION: * **************************************************************** During the processing of the DB2 command DISPLAY GROUP, an internal DB2 field was set incorrectly in some cases, causing the error message noted above. The internal DB2 field is now set correctly for the conditions under which the original problem occurred. Additional Keywords: RC0000080E DISPLAYGROUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58838 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: After applying the PTF for PM35195, DISPLAY GROUP's MODE output will only consider ACTIVE and FAILED members when determining whether a data sharing group is in coexistence. If there are any ACTIVE or FAILED members with a DB2 release level different from the level of the member processing the DISPLAY GROUP command, then a MODE of X will be displayed. Applications that read the MODE output for DISPLAY GROUP may need to change as a result of the new behavior above. For more information, refer to the closing text for PM35195. ACTION: Under certain conditions, DB2 may output '***' for a member's DB2 LVL in the DISPLAY GROUP command output. After applying the PTF for PM34600, such members will be ignored when considering the data sharing group members' levels to determine whether the data sharing group is in coexistence. Accordingly, the MODE output may change to no longer display X in data sharing groups where such members exist. Applications that use the MODE output may need to be changed as a result. For more information, please refer to the closing text. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS 1 DSNB1DGB PM58838 DSN7GCMD PM58838 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58838 DSNB1DGB DSN7GCMD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DGB DSN7GCMD LISTEND UK78479 COVER LETTER END UK78514 COVER LETTER START PROBLEM DESCRIPTION(S): PM53243 - **************************************************************** * USERS AFFECTED: All DB2 users who use DB2 instrumentation * * for Stored Procedure and User-Defined * * Function performance and tuning analysis. * **************************************************************** * PROBLEM DESCRIPTION: Stored Procedure (SP) and User-Defined * * Function (UDF) performance and tuning * * analysis is difficult when multiple * * procedures or functions are involved. * **************************************************************** * RECOMMENDATION: * **************************************************************** Stored Procedure (SP) and User-Defined Function (UDF) performance and tuning analysis has typically been performed via a combination of IFCID3 and IFCID239. IFCID3 provides plan level information and aggregates all executions of SPs or UDFs into common fields. This can create difficulty when tuning multiple procedures or functions that are executed in a given transaction. IFCID239 is also used for performance and tuning analysis at the package level. This provides better granularity than IFCID3 but still may not be sufficient for all transactions. If a procedure or function is executed multiple times, the variation between executions cannot be identified. Instrumentation enhancements are needed. Multiple IFCID enhancements are implemented to provide more effective performance and tuning analysis of Stored Procedures and User-Defined Functions. * IFCID233 is written at the beginning and end of a Stored Procedure or User-Defined Function invocation. This record is enhanced with the invoking statement ID, the invoking statement type, the version ID (applies only to versioned procedures), and the routine ID. Note: The routine ID may be zero if a REBIND is not performed for packages containing CALL statements where the stored procedure name is a literal. 1 See DSNDQW02 for mapping details. * New IFCIDs 380 and 381 are created for Stored Procedure and User-Defined Function detail respectively. These records have two data sections. Data section 1 is mapped by QW0233. Data section 2 is mapped by QW0380 which includes CP, specialty engine, and elapsed time details for nested activity. A series of 380 and/or 381 records can be used to determine the amount of class 1 and class 2 CP, specialty engine, and elapsed time relative to the execution of a given Stored Procedure or User-Defined Function. See DSNDQW05 for mapping details. * New IFCIDs 497, 498, and 499 are created for statement level detail. These records track dynamic and static DML statements executed by a transaction, including those executed within a Stored Procedure or User-Defined Function. A series of IFCID 497, 498, and/or 499 records can be used to determine the statements executed for a given transaction. Note: Any packages containing static SQL statements that existed prior to DB2 10 must be rebound in DB2 10 NFM (not necessarily with this APAR applied) in order to obtain a valid statement ID. See DSNDQW05 for mapping details. * A new performance class 24 is created to encapsulate IFCID380 and IFCID499 for stored procedure detail analysis. For users who are interested in exploiting the functions provided via this APAR, the following actions need to be considered: * For a CALL statement to a DB2 for z/OS Stored Procedure, the Stored Procedure name can be identified via a literal or by using a host variable or parameter marker. When using a literal for the stored procedure name, and in order to benefit from the enhancement that provides a valid routine ID in various IFCID records, the packages that contain the CALL statement must be rebound after this APAR is applied. * For an SQL statement that invokes a DB2 for z/OS User-Defined Function, and in order to benefit from the enhancement to provide a valid routine ID in various IFCID records, the packages that contain the SQL statement must be rebound after this APAR is applied. * The mapping of IFCID233 remains compatible with prior versions and no immediate change is required. However, applications that parse this record will need to be changed in order to exploit the new fields. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53243 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM53243 (V10): For users who are interested in exploiting the functions provided via this PTF, the following actions need to be considered: * For a CALL statement to a DB2 for z/OS Stored Procedure, the 1 Stored Procedure name can be identified via a literal or by using a host variable or parameter marker. When using a literal for the stored procedure name, and in order to benefit from the enhancement that provides a valid routine ID in various IFCID records, the packages that contain the CALL statement must be rebound after this PTF is applied. * For an SQL statement that invokes a DB2 for z/OS User-Defined Function, and in order to benefit from the enhancement to provide a valid routine ID in various IFCID records, the packages that contain the SQL statement must be rebound after this PTF is applied. * The mapping of IFCID233 remains compatible with prior versions and no immediate change is required. However, applications that parse this record will need to be changed in order to exploit the new fields. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWAC PM53243 DSNDQWHS PM53243 DSNDQW02 PM53243 DSNDQW03 PM53243 DSNDQW05 PM53243 DSNLCDG2 PM53243 DSNLCMSL PM53243 DSNLXOQS PM53243 DSNLXPRS PM53243 DSNLXXSS PM53243 DSNLZMON PM53243 DSNTXSTA PM53243 DSNTXSTB PM53243 DSNWVINT PM53243 DSNWVZSA PM53243 DSNXEDP PM53243 DSNXERT PM53243 DSNXERT2 PM53243 DSNXGCAL PM53243 DSNXGUDF PM53243 DSNXRCUF PM53243 DSNXRRTN PM53243 DSNXRUC9 PM53243 DSNXRUFC PM53243 DSNXRUFM PM53243 DSNXRUF9 PM53243 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53243 DSNDQWAC DSNDQWHS DSNDQW02 DSNDQW03 DSNDQW05 DSNLCDG2 DSNLCMSL DSNLXOQS DSNLXPRS DSNLXXSS DSNLZMON DSNTXSTA DSNTXSTB DSNWVINT DSNWVZSA DSNXEDP DSNXERT DSNXERT2 DSNXGCAL DSNXGUDF DSNXRCUF DSNXRRTN DSNXRUC9 DSNXRUFC DSNXRUFM DSNXRUF9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLCDG2 DSNLCMSL 1 DSNLXOQS DSNLXPRS DSNLXXSS DSNLZMON DSNTXSTA DSNTXSTB DSNWVINT DSNWVZSA DSNXEDP DSNXERT DSNXERT2 DSNXGCAL DSNXGUDF DSNXRCUF DSNXRRTN DSNXRUC9 DSNXRUFC DSNXRUFM DSNXRUF9 MACROS DSNDQWAC DSNDQWHS DSNDQW02 DSNDQW03 DSNDQW05 LISTEND UK78514 COVER LETTER END UK78542 COVER LETTER START PROBLEM DESCRIPTION(S): PM63485 - **************************************************************** * 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: * **************************************************************** This APAR provides the following versions of the DB2 Diagnosis Guide and Reference in PDF format: V9: LY37-3218-07 V10: LY37-3220-04 These are the same versions of these documents that are available on the latest DB2 for z/OS licensed library collection. This APAR provides the following versions of the DB2 for z/OS Diagnosis Guide and Reference in PDF format: V9: LY37-3218-07 V10: LY37-3220-04 1 To read these documents, download them as binary to your PC or other system that has a PDF reader, such as the Adobe Acrobat Reader. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63485 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 PM63485 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63485 DSNDR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNDR LISTEND UK78542 COVER LETTER END UK78558 COVER LETTER START PROBLEM DESCRIPTION(S): PM58970 - **************************************************************** * USERS AFFECTED: All DB2 customers using the -ACCESS DATABASE * * MODE(OPEN) command. * **************************************************************** * PROBLEM DESCRIPTION: While executing a -ACCESS DATABASE * * MODE(OPEN) command, when the data sets * * opened by the ACCESS command reach the * * MAXIMUM OPEN DATA SETS(DSMAX) limit, * * the command still tries to open the * * remaining data sets in the object list * * and continuous msgDSNI045I messages * * are issued on the console. * **************************************************************** * RECOMMENDATION: * **************************************************************** -ACCESS DATABASE MODE(OPEN) command continues to send msgDSNI045I warning messages to the console when the number of open data sets exceed the DSMAX limit. The -ACCESS DATABASE MODE(OPEN) command will stop processing when it reaches DSMAX with reason code. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58970 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 PM58970 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58970 DSNILSTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILSTS LISTEND UK78558 COVER LETTER END UK78575 COVER LETTER START PROBLEM DESCRIPTION(S): PM61434 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * EXISTS predicates and the XMLTABLE function. * **************************************************************** * PROBLEM DESCRIPTION: DB2 returns an incorrect result for a * * query that contains a SELECT statement * * with an EXISTS predicate and uses the * * XMLTABLE function in a subquery. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 returns an incorrect result for a query that contains a SELECT statement with an EXISTS predicate and uses the XMLTABLE function in a subquery. The following example can illustrate the problem. 1. Create two tables and populate them. CREATE TABLE T1 (C1 INTEGER, X1 XML); INSERT INTO T1 (C1,X1) VALUES (20,'21'); INSERT INTO T1 (C1,X1) VALUES (20,'20'); CREATE TABLE T2 (C1 INTEGER, C2 INTEGER); INSERT INTO T2 (C1, C2) VALUES (20, 20); INSERT INTO T2 (C1, C2) VALUES (20, 21); 2. Issue a SELECT statement that uses an EXISTS predicate and the XMLTABLE function is in the subquery. 1 SELECT C1,C2 FROM T2 WHERE EXISTS (SELECT * FROM T1, XMLTABLE('/a' PASSING X1 COLUMNS "C2" INTEGER path 'c' ) AS X WHERE T2.C1 = T1.C1 AND T2.C2 = X.C2) OR C2 = 100; The query returns this result. +---------------------------------+ | C1 | C2 | +---------------------------------+ 1_| 20 | 20 | +---------------------------------+ However, the following result is expected. +---------------------------------+ | C1 | C2 | +---------------------------------+ 1_| 20 | 20 | 2_| 20 | 21 | +---------------------------------+ DB2 code does not handle the XMLTABLE function for an EXISTS predicate properly. This leads to an incorrect result when a subsequent row is fetched to qualify. The code in DB2 has been modified to not return an incorrect result in the scenario described. Additional Keywords: SQLXMLTABLE SQLEXISTS SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61434 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNQMD PM61434 DSNNQTOP PM61434 DSNXRBND PM61434 DSNXRBN9 PM61434 DSNXRDOC PM61434 DSNXRDO9 PM61434 DSNXRPUF PM61434 DSNXRXML PM61434 DSNXRXM9 PM61434 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61434 DSNNQMD DSNNQTOP DSNXRBND DSNXRBN9 DSNXRDOC DSNXRDO9 DSNXRPUF DSNXRXML DSNXRXM9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNQMD DSNNQTOP DSNXRBND DSNXRBN9 DSNXRDOC DSNXRDO9 DSNXRPUF DSNXRXML DSNXRXM9 LISTEND UK78575 COVER LETTER END UK78578 COVER LETTER START PROBLEM DESCRIPTION(S): PM60832 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * * of CASE expression and SET functions. * **************************************************************** * PROBLEM DESCRIPTION: Abend at DNXGRDS.DSNXGMVE:M628 * * may occur for an SQL statement * * that satisfies the following * * conditions: * * 1. The statement contains a CASE * * expression in the HAVING clause. * * 2. The CASE expression contains a * * set function COUNT or COUNT_BIG * * and its argument's data type * * is not numeric. * **************************************************************** * RECOMMENDATION: * **************************************************************** Abend at DNXGRDS.DSNXGMVE:M628 may occur for an SQL statement that satisfies the following conditions: 1. The statement contains a CASE expression in the HAVING clause. 2. The CASE expression contains a set function COUNT or COUNT_BIG and its argument's data type is not numeric. For Example, CREATE TABLE T1 (C1 DATE, C2 INTEGER); SELECT C2 FROM T1 GROUP BY C2 HAVING CASE WHEN C2 = 1 THEN DAYS COUNT(C1) ELSE 0 END >= 0; The abend may occur for the above statement because DB2 did 1 not correctly handle the SET function COUNT whose argument's data type is not numeric. DB2 was fixed to handle the SET functions COUNT and COUNT_BIG correctly in the CASE expression. Additional Keywords: SQLCASE SQLCOUNT SQLCOUNTBIG COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60832 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEXE PM60832 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60832 DSNXOEXE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXE LISTEND UK78578 COVER LETTER END UK78581 COVER LETTER START PROBLEM DESCRIPTION(S): PM55928 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: This is a preconditioning APAR for the * * APAR PM56631, which is a new function * * APAR that introduces new built-in * * functions PACK and UNPACK. * **************************************************************** * RECOMMENDATION: * **************************************************************** New built-in functions PACK and UNPACK are introduced to DB2 10 via two APARs: PM55928 (preconditioning APAR) and PM56631 (enabling APAR). Please refer to the PM56631 closing text for the description of the new functions. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55928 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM51654: See PM51654 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM51654 corrects a problem when incorrect output could happen for a complex SQL statement or view with an outer join and a correlated sub-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 PM47058: See PM47058 APAR/PTF text for additional information about why a REBIND is necessary. PM47058 corrects a problem of incorrect output when an SQL statement satisfies all of the following conditions: 1. table expression with sideway reference is defined in this SQL statement; 2. LEFT OUTER JOIN is involved in this SQL statement; 3. CPU parallelism setting 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 PM41296: See PM41296 APAR/PTF text for additional information about why a REBIND is necessary. PM41296 corrects a problem of an SQL statement which defines a table expression one the preserved side of LEFT OUTER JOIN, and a CASE statement or non-column expression is defined in the SELECT list of the table expression and is referenced in the SQL statement. Performance may regress when a SQL statement satisfies all of the following conditions: 1. OUTER JOIN is contained, and the preserved side is defined with table expression; 2. a CASE statement or non-column expression is defined in the SELECT list of the above table expression; 3. a table expression column which corresponds to the CASE statement or non-column expression from condition #2 is referenced in predicate of the SQL 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. MULTSYS: ***Action for PM55928: 1 PM55928 is a pre-conditioning APAR that includes changes to support a new function that will be enabled via another APAR PM56631. 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 later enabling APAR PM56631 is applied to any member. The new function is not enabled until the enabling APAR PM56631 is applied. If the new function will not be used, then there is no need to take precautions for rolling through the pre-conditioning PTF ahead of the enabling PTF. Instead, both pre-conditioning PTF and enabling PTF can be rolled through together. In addition, because the new function can only be used in DB2 10 New Function Mode (NFM), both pre-conditioning PTF and enabling PTF can be rolled through together on DB2 10 CM subsystems. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEBR PM55928 DSNXGRTM PM55928 DSNXGSFN PM55928 DSNXOBFA PM55928 DSNXOBFF PM55928 DSNXOBF3 PM55928 DSNXOBF4 PM55928 DSNXODSO PM55928 DSNXODTR PM55928 DSNXODTX PM55928 DSNXOFN2 PM55928 DSNXOMTX PM55928 DSNXOOS1 PM55928 DSNXOP0 PM55928 DSNXOSCF PM55928 DSNXOVP PM55928 DSNXRBIN PM55928 DSNXRNUL PM55928 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55928 DSNXEBR DSNXGRTM DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 DSNXODSO DSNXODTR DSNXODTX DSNXOFN2 DSNXOMTX DSNXOOS1 DSNXOP0 DSNXOSCF DSNXOVP DSNXRBIN DSNXRNUL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEBR DSNXGRTM DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4 DSNXODSO DSNXODTR DSNXODTX DSNXOFN2 1 DSNXOMTX DSNXOOS1 DSNXOP0 DSNXOSCF DSNXOVP DSNXRBIN DSNXRNUL LISTEND UK78581 COVER LETTER END UK78584 COVER LETTER START PROBLEM DESCRIPTION(S): PM60806 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of SQL Scalar * * function. * **************************************************************** * PROBLEM DESCRIPTION: Missing SQLCODE -312 could happen * * when 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** Missing SQLCODE -312 could happen when 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. The following CREATE FUNCTION statement expects to issue SQLCODE -312, but it is created successfully. CREATE FUNCTION MYTESTFUN() RETURNS INTEGER MODIFIES SQL DATA WLM ENVIRONMENT FOR DEBUG MODE WLMENV1 BEGIN DECLARE P1 INT; SET P1 = 100; RETURN SQLCODE; END ! 1 DB2 is updated to issue SQLCODE -312 for CREATE FUNCTION statement describes as above. Additional Keywords: SQLCODE312 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60806 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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. 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOYP1 PM60806 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60806 DSNXOYP1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOYP1 LISTEND UK78584 COVER LETTER END UK78604 COVER LETTER START PROBLEM DESCRIPTION(S): PM61247 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of recursive SQL * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIWSET 5008 * * or 500D when executing a recursive * * SQL query. * **************************************************************** * RECOMMENDATION: * **************************************************************** Abend 04E with return code 00C90101 is issued from DSNIWSET when processing recursive SQL. The problem occurs 1 intermittently when the workfile used for the recursive SQL has extensions. Recursive SQL is done via a common table expression (CTE). Example of a recursive SQL: WITH SRC(N) AS (SELECT 1 FROM SYSIBM.SYSDUMMY1 UNION ALL SELECT N+1 FROM SRC WHERE N < 10000 ) SELECT COUNT(N) from SRC; DB2 code was changed to prevent the intermittent abend. The code change is the same as Version 9 APAR PK40784 and PK49963. ADDITIONAL KEYWORDS: SQLUNIONALL SQLCTE SQLRECURSIVE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61247 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRUNA PM61247 DSNXRUN9 PM61247 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61247 DSNXRUNA DSNXRUN9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRUNA DSNXRUN9 LISTEND UK78604 COVER LETTER END UK78606 COVER LETTER START PROBLEM DESCRIPTION(S): PM62787 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users DATASHARING SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: 1. ABEND0C9 in DXRRL732 during IRLM * * startup while IRLM lock structure * * rebuild was going on. * * * * 2. In IRLM 230 (only) * 1 * --------------------- * * - ABENDu2025 in DXRRL2U0 on starting * * IRLM member due to incorrect IRLM ID * * usage may also trigger lock structure * * rebuild as it may max out available * * connections to the lock strcuture. * * * * * * - ABENDB78-14 in DXRRL070 on FREEMAIN * * call just after initialization failure * * DXR116E IRL1001 INITIALIZATION FAILED, * * CODE=09 DETECTED BY DXRRL0C0 * * * * - ABEND0C4-10 in * * COMPON=TIMER SUPERVISION,COMPID=SC1CV, * * ISSUER=IEAVRTI1,TIMER FRR * * after attempt to start IRLM several * * times on a system. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** 1. During IRLM startup, DXRRL732 may do calculations to check the lock structure usage and incorrectly run into a divide by zero error causing DXRRL732 to issue ABEND0C9. It may happen while this member is disconnected from the group and waiting for IRLM lock structure rebuild to be over. There is a timing window between IRLM health check run and IRLM trying re-connect to the lock structure. IRLM health check logic may find RLE usecount (RLMRLEUS) being non-zero before reconnect is done and total RLE count (RHTLKRLE) being set. 2. In IRLM 230 (only) ------------------ - Attempt to start IRLM with an IRLM ID already in use by another IRLM member results in ABENDu2025. This leaves the new connection to the lock structure in 'Failed Persistent' state. The increased connection count may also result in reaching the threshold set for IRLM to rebuild lock structure to allow more connections. This rebuild can be avoided. IRLM should not leave the failed persistent connection for duplicated IRLM id failure around. - During a restart failure IRLM may see ABENDB78-14 in DXRRL070 on a FREEMAIN request for IRLM branch vector table as it did not get the CML lock to perform the FREEMAIN operation. - During a restart failure IRLM may not have obtained the deadlock work area when IRLM ESATE in DXRRL070 gets driven. IRLM may pick up low core storage to issues DEQ TQE for Deadlock TQE. This could result in ABEND0C4-10 in TIMER FRR routine in MVS. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** 1 This APAR provids following solutions: For IRLM 220 and IRLM 230: ------------------------- A timing window between IRLM health check and IRLM re-connect to the lock structure is corrected to avoid ABEND0C9 in DXRRL732. For IRLM 230 (only): -------------------- - IRLM will force clear the failed persistent connection when it disconnects and ABENDu2025 due to duplicate IRLM id. - IRLM will get the CML lock before calling FREEMAIN to free the storage for branch vector table (RLMFBTA), to prevent the ABENDB78-14 in DXRRL070. - IRLM will ensure that deadlock TQE was obtained before it attempts to Dequeue the TQE, to prevent ABEND0C4-10 in timer FRR routine. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM62787 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL070 PM62787 DXRRL711 PM62787 DXRRL732 PM62787 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62787 DXRRL070 DXRRL711 DXRRL732 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL070 DXRRL711 DXRRL732 LISTEND UK78606 COVER LETTER END UK78632 COVER LETTER START PROBLEM DESCRIPTION(S): PM57632 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users * **************************************************************** * PROBLEM DESCRIPTION: Serviceability * **************************************************************** * RECOMMENDATION: Apply PTF when available. * **************************************************************** Serviceability. Serviceability. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM57632 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM57632 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 addresses will not be enabled. The fix for APAR PM57632 is a companion fix. It requires the fix for APAR PM60438, for FMID JDBAA1K to be applied. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFMDIR PM57632 DSNFUDRD PM57632 DSNUGBPL PM57632 DSNUGEPL PM57632 DSNUGPPF PM57632 DSNUGPRS PM57632 DSNUGRAR PM57632 DSNUGRSO PM57632 DSNUGSUG PM57632 DSNUGSUU PM57632 DSNUIEPL PM57632 DSNUMSGD PM57632 DSNURCON PM57632 DSNURELD PM57632 DSNURILD PM57632 DSNURPLD PM57632 DSNURPLL PM57632 DSNURPPD PM57632 DSNURPPI PM57632 DSNURWBF PM57632 DSNURWI PM57632 DSNURWIF PM57632 DSNURWRF PM57632 DSNURWT PM57632 HDBAA10J PM57632 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57632 DSNFMDIR DSNFUDRD DSNUGBPL DSNUGEPL DSNUGPPF DSNUGPRS DSNUGRAR DSNUGRSO DSNUGSUG DSNUGSUU DSNUIEPL DSNUMSGD DSNURCON DSNURELD DSNURILD DSNURPLD DSNURPLL DSNURPPD DSNURPPI DSNURWBF DSNURWI DSNURWIF DSNURWRF DSNURWT HDBAA10J 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFUDRD DSNUGBPL DSNUGEPL DSNUGPPF DSNUGPRS DSNUGRAR DSNUGRSO DSNUGSUG DSNUGSUU DSNUIEPL DSNUMSGD DSNURCON DSNURELD DSNURILD DSNURPLD DSNURPLL DSNURPPD DSNURPPI DSNURWBF DSNURWI DSNURWIF DSNURWRF DSNURWT LISTEND UK78632 COVER LETTER END UK78633 COVER LETTER START PROBLEM DESCRIPTION(S): PM60438 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users * **************************************************************** * PROBLEM DESCRIPTION: Serviceability. * **************************************************************** * RECOMMENDATION: Apply PTF when available. * **************************************************************** Serviceability. Serviceability. The fix for APAR PM60438 is a companion fix. It requires the fix for APAR PM57632, for FMID HDBAA10 to be applied. COMPONENT: 5740-XYR00-JDBAA1K APARS FIXED: PM60438 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The fix for APAR PM60438 is a companion fix. It requires the fix for APAR PM57632, for FMID HDBAA10 to be applied. ACTION: 1 The fix for APAR PM42560 is a companion fix. It requires the fix for APAR PM27962, for FMID HDBAA10 to be applied. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUFFMF PM60438 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60438 DSNUFFMF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUFFMF LISTEND UK78633 COVER LETTER END UK78649 COVER LETTER START PROBLEM DESCRIPTION(S): PM59499 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of a COMMON TABLE EXPRESSION containing a * * UNION ALL and FETCH FIRST N ROWS. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at * * location DSNXGRM1:M266 when a COMMON * * TABLE EXPRESSION contains a UNION ALL * * and the FETCH FIRST N ROWS clause. The * * CTE is non-recursive. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 can occur at location DSNXGRM1 M266 when a non-recursive COMMON TABLE EXPRESSION (CTE) contains a UNION ALL and the FETCH FIRST N ROWS clause. The following example illustrates a failing case. Step 1. Create Tables T1 and T2. CREATE TABLE T1 (C1 CHAR(1)); CREATE TABLE T2(C1 CHAR(1)); Step 2. Insert into Table T1. INSERT INTO T1 VALUES('A'); INSERT INTO T1 VALUES('B'); Step 3. Perform the following Insert using a CTE. INSERT INTO T2(C1) 1 WITH CTE (CTE_COL) AS (SELECT C1 FROM T1 UNION ALL SELECT C1 FROM T1 FETCH FIRST 1 ROWS ONLY ) (SELECT * FROM CTE UNION ALL SELECT * FROM CTE); Step 4. The above statement can produce the above mentioned failure. If the Insert completed successfully, the expected result or contents of Table T2 should be as follows. SELECT * FROM T2; +----+ | C1 | +----+ 1_| A | 2_| A | +----+ The code in DB2 has been modified to prevent the failure for a non-recursive CTE that contains a UNION ALL with a FETCH FIRST N ROWS clause. Additional Keywords: SQLCTE SQLUNIONALL SQLFFNR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59499 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 PM59499 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59499 DSNXGRM1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGRM1 LISTEND UK78649 COVER LETTER END UK78692 COVER LETTER START PROBLEM DESCRIPTION(S): PM62377 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of EXPLAIN PACKAGE. * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes a problem where rows * 1 * may be missing from PLAN_TABLE after * * running EXPLAIN PACKAGE on a package * * that contains multiple statements and * * the same QUERYNO value is used for two * * or more statements. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes a problem where rows may be missing from PLAN_TABLE after running EXPLAIN PACKAGE on a package that contains multiple statements and the same QUERYNO value is used for two or more statements. An example set of statements that exhibit the problem: EXEC SQL DECLARE C1 CURSOR WITH HOLD FOR SELECT COUNT(*) FROM SYSIBM.SYSDUMMY1 QUERYNO 1; EXEC SQL DECLARE C2 CURSOR WITH HOLD FOR SELECT COUNT(*) FROM SYSIBM.SYSTABLES QUERYNO 1; Querying catalog table SYSIBM.SYSPACKSTMT shows the same QUERYNO for both statements: QUERYNO STMTNO SECTNO SEQNO ----------- ------ ------ ----------- -1 0 0 0 1 27 1 1 1 125 2 2 In this scenario, PLAN_TABLE rows may be missing after running EXPLAIN PACKAGE. Additional keywords: SQLEXPLAIN DB2 code has now been changed to fix the problem. In the example above, both statements now have corresponding PLAN_TABLE output after applying the fix. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62377 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOD15 PM62377 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62377 DSNXOD15 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOD15 1 LISTEND UK78692 COVER LETTER END UK78700 COVER LETTER START PROBLEM DESCRIPTION(S): PM60533 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users (CM and above) of * * ALTER TABLE ADD COLUMN on tables used by * * bound application plans * **************************************************************** * PROBLEM DESCRIPTION: The APAR addresses two problems: * * * * 1. Incorrect output is possible on * * tables which have gone through ALTER * * TABLE ADD COLUMN since arrival to 10 * * CM or higher, without a subsequent * * rebind on plans/packages using such * * tables. * * * * 2. ABEND04E RC00E20003 * * DSNIGSEL.DSNSVBK+070E due to storage * * leak in the internal DB2 storage pool * * that is used for P Procs. * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem 1: In DB2 10 CM or higher, incorrout is possible for a table that has gone through ALTER TABLE ADD COLUMN in 10 and a REORG, but no rebind has been done on plans/packages using that table. In DB2 10, a new, faster predicate evaluation mechanism takes over - the Predicate Proc (P Proc). The P Proc gets built at bind time as long as the selection expression does not involve host variables with LIKE / NOT LIKE predicate. DDL ALTER TABLE ADD COLUMN will not invalidate bound plans/packages containing the P Proc. If a REORG is run after the DDL ALTER ADD COLUMN and then the plan/package itself, the plan/package may get incorrect output because the P Proc in it may be affected by the change in positions of columns after REORG and all rows are currentlevel-versioned. The following is a sample scenario that exposes this problem: (1) Populate the table with some rows (2) BIND an SQL SELECT application that does not use host variables with LIKE/NOT LIKE (3) ALTER TABLE ADD COLUMN (rows now become downlevel-versioned) (4) REORG (rows now become currentlevel-versioned) (5) Run the SQL SELECT application -> Incorrout 1 Problem 2: Storage leak may occur in internal DB2 pool CTLNGSTP, with the pool showing a large number of P Procs built (eyecatcher 'Selp') for the same MSIB block, when rows are downlevel- versioned. This is not OK because there should be only one P Proc per MSIB. The symptom of this second problem is ABEND04E RC00E20003 DSNIGSEL.DSNSVBK+070E. The root cause for the storage leak is that DB2 forgets to reset an internal record counter for P Proc building. The counter keeps incrementing and overflows, leading to a new P Proc being built every 65,000+ rows. The following is a sample scenario that exposes this second problem: (1) Populate the table with a very large number of rows (e.g. 70,000+) (2) BIND an SQL SELECT application that does not use host variables with LIKE/NOT LIKE (3) ALTER TABLE ADD COLUMN (rows now become downlevel-versioned) (4) Run the SQL SELECT application -> Storage leak with Selp's DB2 code is fixed to associate the table version with the P Proc that was built at bind time. At execution time, DB2 will compare the versions of the evaluated row and the bind-time P Proc. If they match, the code will use the bind-time P Proc, otherwise it will build a new P Proc on the fly. Due to this building of P Proc at execution time, after applying this PTF, applications that have not been rebound since ALTER TABLE ADD COLUMN might experience performance degradation. To improve the performance of these applications, they can be rebound. For any table that has gone through ALTER TABLE ADD COLUMN since arrival in 10, a query such as this one can be used to identify any plans/packages that use the table but have not been rebound since the ALTER: SELECT PKG.COLLID, PKG.NAME, PKG.TYPE FROM SYSIBM.SYSPACKAGE PKG, SYSIBM.SYSPACKDEP PKD, SYSIBM.SYSTABLES TAB, SYSIBM.SYSCOLUMNS COL WHERE PKG.COLLID = PKD.DCOLLID AND PKG.NAME = PKD.DNAME AND PKG.CONTOKEN = PKD.DCONTOKEN AND TAB.CREATOR = PKD.BQUALIFIER AND TAB.NAME = PKD.BNAME AND PKD.BTYPE = 'T' AND TAB.CREATOR = COL.TBCREATOR AND TAB.NAME= COL.TBNAME AND TAB.CREATEDTS < COL.CREATEDTS 1 AND COL.CREATEDTS > PKG.BINDTIME; Additional keywords: DB2INCORR/K SQLINCORR SQLINCORROUT DB2STGLK/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60533 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM60533: See PM60533 APAR/PTF text for additional information about why a REBIND is recommended. After you apply this PTF, some applications might experience performance degradation. To improve the performance of those applications, rebind their plans and packages. 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 PM60533 DSNIADR PM60533 DSNICRFT PM60533 DSNIESEN PM60533 DSNIGSEL PM60533 DSNIHSET PM60533 DSNIMNEX PM60533 DSNIONX2 PM60533 DSNIOST2 PM60533 DSNIRNXT PM60533 DSNIRPRE PM60533 DSNIRSET PM60533 DSNISFRL PM60533 DSNISFS PM60533 DSNISFWL PM60533 DSNISFX2 PM60533 DSNISRID PM60533 DSNIWNRF PM60533 DSNUUSEL PM60533 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60533 DSNIACCH DSNIADR DSNICRFT DSNIESEN DSNIGSEL DSNIHSET DSNIMNEX DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNIRSET DSNISFRL DSNISFS DSNISFWL DSNISFX2 DSNISRID DSNIWNRF DSNUUSEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIACCH DSNIADR DSNICRFT DSNIESEN 1 DSNIGSEL DSNIHSET DSNIMNEX DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNIRSET DSNISFRL DSNISFS DSNISFWL DSNISFX2 DSNISRID DSNIWNRF DSNUUSEL LISTEND UK78700 COVER LETTER END UK78726 COVER LETTER START PROBLEM DESCRIPTION(S): PM59927 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of remote Stored * * Procedures, particularly those which invoke * * other remote native language procedures. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC4 can occur at location * * DSNXROHS +2F26 or OFFSET2F26 when an * * SQL statement is executed from a remote * * stored procedure which invokes another * * remote native procedure which executes * * the same SQL statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an SQL statement is executed (with bindout) from a remote stored procedure which invokes another remote native procedure which executes (with bindout) the same SQL statement, an ABEND0C4 RC4 can occur at location DSNXROHS +2F26. The following PLI example helps to illustrate this problem scenario. 1. Create a simple Table T1 and populate it on a remote server, STLEC1B. CREATE TABLE T1 (C1 VARCHAR(20)); INSERT INTO T1 VALUES('TEST'); 2. Create an external Stored Procedure on STLEC1B, the same remote server. 1 CREATE PROCEDURE SPF6 () LANGUAGE PLI EXTERNAL NAME SPF6 WLM ENVIRONMENT WLMENV2 PROGRAM TYPE MAIN RESULT SETS 1; SPF6: PROC OPTIONS(MAIN NOEXECOPS ); // include SQLCA, SQLDA and variables DCL SPF6PRG EXTERNAL ENTRY; DISPLAY (' IN SPF6 BODY'); CALL SPF6PRG(); <=== call remote procedure // EXEC SQL any SQL statement END SPF6; Please note. Inside external stored procedure SPF6, we call another remote procedure SPF6PRG. It is defined as follows. SPF6PRG: PROC OPTIONS(MAIN); //include SQLCA, SQLDA, and global variable DCL HV1 CHAR(20); EXEC SQL SELECT C1 INTO :HV1 FROM T1; END SPF6PRG; 3. Create a calling application which makes an EXEC CALL to the Stored Procedure SPF6 and a PLI language CALL to procedure SPF6PRG. DCL SPF6PRG EXTERNAL ENTRY; EXEC SQL CONNECT TO STLEC1B; EXEC SQL CALL SPF6(); CALL SPF6PRG(); When DB2 processes the remote EXEC SQL to Stored Procedure SPF6, DB2 internal structures are modified for procedure SPF6PRG inside the stored procedure. Later, when a remote PLI native language CALL to SPF6PRG is made, DB2 finds that the package has been reused and DB2 internal structures contain some residual 1 information from a previous CALL. This eventually leads to the ABEND0C4. The code in DB2 has been modified to correctly rebuild the necessary internal structures to prevent the ABEND0C4 from occurring. Additional Keywords: SQLSTOREDPROC SQLSP SQLPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59927 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXESET PM59927 DSNXROB9 PM59927 DSNXROE9 PM59927 DSNXROHB PM59927 DSNXROHE PM59927 DSNXROHR PM59927 DSNXROHS PM59927 DSNXROH2 PM59927 DSNXROS9 PM59927 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59927 DSNXESET DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS DSNXROH2 DSNXROS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXESET DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS DSNXROH2 DSNXROS9 LISTEND UK78726 COVER LETTER END UK78731 COVER LETTER START PROBLEM DESCRIPTION(S): PM58335 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS RUNNING CONCURRENT COPY UTILITY AS * * A STORED PROCEDURE * **************************************************************** * PROBLEM DESCRIPTION: CONCURRENT COPY UTILITY LEAVES ITS * * OUTPUT DATA SETS ALLOCATED * * INDEFINITELY TO THE WLM ADDRESS SPACE * 1 * WHEN RUN UNDER STORED PROCEDURES * * DSNUTILS OR DSNUTILU AND TEMPLATES * * ARE USED * **************************************************************** * RECOMMENDATION: * **************************************************************** User observed that after successful completion of CONCURRENT COPY utility when run under stored procedure DSNUTILS or DSNUTILU, output data sets defined by TEMPLATE utility remained allocated to the WLM address space for as long as that address space remained up, even after the utility job and the batch address space were gone. This can lead to the possibility that the maximum number of dynamically allocated data sets could be exceeded. CONCURRENT COPY utility code was changed to deallocate dynamically allocated output data sets defined by TEMPLATE utility. Some users of CONCURRENT COPY who run their jobs on very large lists of objects without the use of FILTERDDN may find that the region size of their CONCURRENT COPY jobs might need to be increased as a result of applying this fix. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58335 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUBBCR PM58335 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58335 DSNUBBCR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBBCR LISTEND UK78731 COVER LETTER END UK78737 COVER LETTER START PROBLEM DESCRIPTION(S): PM58842 - **************************************************************** * 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 issues are addressed in * * this APAR: * * * 1 * 1. DB2 supplied Database Metadata * * stored procedure SYSIBM.SQLCOLUMNS * * does not handle the escape * * character (\) correctly * * when it is used before the * * underscore (_) character when * * running on a DB2 subsystem that has the * * DSNHDECP.MIXED parameter set to YES * * (MIXED=YES subsystem) * * * * 2. The following DB2 supplied Database * * Metadata stored procedures returned * * incorrect results when the character * * percent sign(%) is used as a literal * * instead of a wildcard in parameter * * values. * * * * SYSIBM.SQLCOLPRIVILEGES * * SYSIBM.SQLCOLUMNS * * SYSIBM.SQLFUNCTIONCOLS * * SYSIBM.SQLFUNCTIONS * * SYSIBM.SQLPRIMARYKEYS * * SYSIBM.SQLPROCEDURECOLS * * SYSIBM.SQLPROCEDURES * * SYSIBM.SQLTABLEPRIVILEGES * * SYSIBM.SQLTABLES * **************************************************************** * RECOMMENDATION: Apply PTF * **************************************************************** 1. DB2 supplied stored procedure SYSIBM.SQLCOLUMNS does not correctly handle an escape character (\) before an underscore (_) character when running on a DB2 that uses a mixed-byte character set for EBCDIC or ASCII data, that is, a DB2 that has the DSNHDECP.MIXED parameter set to YES. An empty result set could occur when underscore (_) character is used as a literal value. 2. The following Database Metadata stored procedures did not correctly handle the percent sign (%) character when it is used as a literal instead of a wildcard. An incorrect result set could occur when the percent sign (%) is used as a literal value. SYSIBM.SQLCOLPRIVILEGES SYSIBM.SQLCOLUMNS SYSIBM.SQLFUNCTIONCOLS SYSIBM.SQLFUNCTIONS SYSIBM.SQLPRIMARYKEYS SYSIBM.SQLPROCEDURECOLS SYSIBM.SQLPROCEDURES SYSIBM.SQLTABLEPRIVILEGES SYSIBM.SQLTABLES The stored procedure SYSIBM.SQLCOLUMNS was fixed to correctly handle the escape character (\) before the underscore (_). 1 The following stored procedures were fixed to correctly handle the percent sign (%) when it is used as a literal. SYSIBM.SQLCOLPRIVILEGES SYSIBM.SQLCOLUMNS SYSIBM.SQLFUNCTIONCOLS SYSIBM.SQLFUNCTIONS SYSIBM.SQLPRIMARYKEYS SYSIBM.SQLPROCEDURECOLS SYSIBM.SQLPROCEDURES 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 fix: (1) Run installation job DSNTIJRT to rebind DBRM DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. (2) Refresh the WLM environment Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRMs DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. 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 1 where is the name of the WLM application environment in which the Database Metadata stored procedures SYSIBM.SQLCOLPRIVILEGES, SYSIBM.SQLCOLUMNS SYSIBM.SQLFUNCTIONCOLS, SYSIBM.SQLFUNCTIONS, SYSIBM.SQLPRIMARYKEYS, SYSIBM.SQLPROCEDURECOLS, SYSIBM.SQLPROCEDURES, SYSIBM.SQLTABLEPRIVILEGES and SYSIBM.SQLTABLES are running. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58842 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM58842 (V10): See PTF cover letter for additional information. This PTF updated the following Database Metadata stored procedures: SYSIBM.SQLCOLPRIVILEGES (DSNACPRU) SYSIBM.SQLCOLUMNS (DSNACOLU) SYSIBM.SQLFUNCTIONCOLS (DSNAFCOU) SYSIBM.SQLFUNCTIONS (DSNAFUNU) SYSIBM.SQLPRIMARYKEYS (DSNAPRKU) SYSIBM.SQLPROCEDURECOLS (DSNAPCOU) SYSIBM.SQLPROCEDURES (DSNAPRCU) SYSIBM.SQLTABLEPRIVILEGES (DSNATBPU) SYSIBM.SQLTABLES (DSNATBLU) *************************************************************** 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 DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. (2) Refresh the WLM environment Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRMs DSNACPRU, DSNACOLU, DSNAFCOU, DSNAFUNU, DSNAPRKU, DSNAPCOU, DSNAPRCU, DSNATBPU and DSNATBLU. 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 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.SQLFUNCTIONCOLS, SYSIBM.SQLFUNCTIONS, SYSIBM.SQLPRIMARYKEYS, SYSIBM.SQLPROCEDURECOLS, SYSIBM.SQLPROCEDURES, SYSIBM.SQLTABLEPRIVILEGES and SYSIBM.SQLTABLES are running. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@COLU PM58842 DSN@CPRU PM58842 DSN@FCOU PM58842 DSN@FUNU PM58842 DSN@PCOU PM58842 DSN@PRCU PM58842 DSN@PRKU PM58842 DSN@TBLU PM58842 DSN@TBPU PM58842 DSNACOLU PM58842 DSNACPRU PM58842 DSNAFCOU PM58842 DSNAFUNU PM58842 DSNAPCOU PM58842 DSNAPRCU PM58842 DSNAPRKU PM58842 DSNATBLU PM58842 DSNATBPU PM58842 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58842 DSN@COLU DSN@CPRU DSN@FCOU DSN@FUNU DSN@PCOU DSN@PRCU DSN@PRKU DSN@TBLU DSN@TBPU DSNACOLU DSNACPRU DSNAFCOU DSNAFUNU DSNAPCOU DSNAPRCU DSNAPRKU DSNATBLU DSNATBPU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACOLU 1 DSNACPRU DSNAFCOU DSNAFUNU DSNAPCOU DSNAPRCU DSNAPRKU DSNATBLU DSNATBPU MACROS DSN@COLU DSN@CPRU DSN@FCOU DSN@FUNU DSN@PCOU DSN@PRCU DSN@PRKU DSN@TBLU DSN@TBPU LISTEND UK78737 COVER LETTER END UK78756 COVER LETTER START PROBLEM DESCRIPTION(S): PM62822 - **************************************************************** * USERS AFFECTED: All DB2 10 and 9 for z/OS * * of native SQL procedure. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect qualifier is displayed * * for the native SQL procedure * * information in the DSNX908I message. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a native SQL procedure consumes more CPU service units than its allowed ASUTIME, which is specified in the procedure's definition, during its execution, DSNX908I message is issued along with SQLCODE -905. . In the reported case, the current schema information was displayed as a part of the native SQL procedure information instead of the procedure's qualifier in the DSNX908I message. DB2 has been modified to display the correct qualifier of a native SQL procedure in the DSNX908I message. Related keywords: SQLNATIVESQLPL SQLCODE905 SQLPL SQLSTOREDPROC SQLPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62822 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 DSNXRPL9 PM62822 DSNXRSPL PM62822 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62822 DSNXRPL9 DSNXRSPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPL9 DSNXRSPL LISTEND UK78756 COVER LETTER END UK78762 COVER LETTER START PROBLEM DESCRIPTION(S): PM62118 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of an SQL * * statement with a built-in function that * * should run into SQLCODE -206. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B at the location * * DSNXGRDS.DSNXOOS1 OFFSET2DCE may happen * * when running an SQL statement that * * meets all of the following conditions: * * * * 1. It contains a built-in function. * * 2. The first parameter of the built-in * * function is a keyword. * * 3. The SQL statement should run into * * SQLCODE -206. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC0000003B at the location DSNXGRDS.DSNXOOS1 OFFSET2DCE may happen when running an SQL statement that meets all of the following conditions: 1. It contains a built-in function. 2. The first parameter of the built-in function is a keyword. 3. The SQL statement should run into SQLCODE -206. An example is shown below: SELECT COUNT(ISO) FROM SYSIBM.SYSTABLES 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 the ABEND. 1 Additional keywords: SQLCODE206 SQLFUNCTION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62118 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 PM62118 DSNXOBFF PM62118 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62118 DSNXOBFA DSNXOBFF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOBFA DSNXOBFF LISTEND UK78762 COVER LETTER END UK78763 COVER LETTER START PROBLEM DESCRIPTION(S): PM62974 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using the * * DB2-supplied stored procedures. * **************************************************************** * PROBLEM DESCRIPTION: When running the DB2-supplied stored * * procedure installation job DSNTIJRT * * a bind error DSNT243I might occur * * on the package DSNX7MON. * **************************************************************** * RECOMMENDATION: * **************************************************************** While the DB2-supplied stored procedure installation job DSNTIJRT is being executed, a bind error DSNT243I might occur: DSNT243I -xxxx BIND ERROR FOR PACKAGE = xxxx.DSNAUTON.DSNX7MON.(UK75581) CONTOKEN = '0E4D2F6F09F6F9F7'X IS NOT UNIQUE SO IT CANNOT BE CREATED DSNT233I -xxxx UNSUCCESSFUL BIND FOR PACKAGE = xxxx.DSNAUTON.DSNX7MON.(UK75581) LEVEL and VERSION of the DSNX7MON DBRM have been corrected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62974 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: *************************************************************** 1 Actions for customers who are already using DB2 10: *************************************************************** Run installation job DSNTIJRT to bind modified stored procedures packages *********************************************************** * This action is required for all V10 customers *********************************************************** Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the stored procedure SYSPROC.ADMIN_UTL_MONITOR. 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. ACTION: The PTF for PM54759 fixes the stored procedure SYSPROC.ADMIN_UTL_MONITOR so that the task it adds to the DB2 scheduler task list to execute the stored procedure SYSPROC.ADMIN_UTL_EXECUTE can be executed by the DB2 scheduler when DECIMAL=COMMA is enabled in DSNHDECP. See the PTF cover letter for more information. *************************************************************** Actions for DB2 10 for z/OS customers who are using the DB2-supplied stored procedures SYSPROC.ADMIN_UTL_MONITOR and SYSPROC.ADMIN_UTL_EXECUTE in conjunction with the DB2 administrative task scheduler *************************************************************** After applying this PTF, you need to remove the task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list. This action is detailed below: (1) Ensure that the DB2 scheduler is up and running. If scheduler is not running, execute the following console command: START DSNADMT where DSNADMT is the name of the scheduler. (2) Invoke the user-defined function ADMIN_TASK_LIST to determine if the task 'DB2 AUTO PROCEDURE EXECUTE' is in the DB2 scheduler task list, by issuing the following SQL statement: SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE'; 1 A JOB example for this action is given below in the JOB EXAMPLES section. When no such task exists proceed to step (4). Otherwise, proceed to step (3), below. (3) Remove task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list by invoking the DB2-supplied stored procedure SYSPROC.ADMIN_TASK_REMOVE: CALL SYSPROC.ADMIN_TASK_REMOVE (task-name, return-code, message) with the input parameter 'task-name' set to 'DB2 AUTO PROCEDURE EXECUTE'. 'return-code' and 'message' are output parameters. A JOB example of using DB2 REXX Language Support for this action is given below in the JOB EXAMPLES section. (4) If the DB2 scheduler was started in step (1), stop the scheduler by executing the following console command: MODIFY DSNADMT,APPL=SHUTDOWN where DSNADMT is the name of the scheduler. *************************************************************** JOB EXAMPLES *************************************************************** Prior to running any example, customize it for your system by adding a valid job card and modifying the examples as indicated below. *************************************************************** STEP (2) EXAMPLE QUERY DSNADM.ADMIN_TASK_LIST Required actions: 1. In lines 1-3,14 replace 'DSN!!0' with the prefix of the target library for DB2 V10 2. In line 12 replace '!DSN!' with your DB2 subsystem name 3. In line 13 replace 'DSNTEP!!' with the plan name for DSNTEP2 on your DB2 *************************************************************** //JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR // DD DSN=DSN!!0.SDSNLOAD,DISP=SHR // DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR //DSNTEP2 EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20 //SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //CEEDUMP DD SYSOUT=* //SYSUDUMP DD SYSOUT=* 1 //SYSOUT DD SYSOUT=* //SYSTSIN DD * DSN SYSTEM(!DSN!) RUN PROGRAM(DSNTEP2) PLAN(DSNTEP!!) - LIB('DSN!!0.RUNLIB.LOAD') PARMS('/ALIGN(MID)') END //SYSIN DD * SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE' *************************************************************** STEP (3) EXAMPLE CALL SYSPROC.ADMIN_TASK_REMOVE Required actions: 1. In lines 1-3 replace 'DSN!!0' with the prefix of the target library for DB2 V10 2. In line 10 replace '#' with a forward slash '/'. Closing comment sequence is not allowed within ++HOLD text. 3. In line 11 replace '!DSN!' with your DB2 subsystem name *************************************************************** //JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR // DD DSN=DSN!!0.SDSNLOAD,DISP=SHR // DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR //REXX EXEC PGM=IEBUPDTE,PARM='NEW' //SYSPRINT DD SYSOUT=* //SYSUT2 DD DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(2,1,1)), // DSORG=PO,BLKSIZE=0,RECFM=FB,LRECL=80 //SYSIN DD * ./ ADD NAME=CALLSP /* REXX *# SSID = !DSN! TASKNAME = 'DB2 AUTO PROCEDURE EXECUTE' RETCODE = 12 MESSAGE = COPIES(' ',1332) "SUBCOM DSNREXX" IF RC <> 0 THEN S_RC = RXSUBCOM('ADD','DSNREXX','DSNREXX') ADDRESS DSNREXX "CONNECT" SSID IF SQLCODE = 0 THEN DO SAY 'CONNECTED TO ' SSID ADDRESS DSNREXX "EXECSQL CALL ", "SYSPROC.ADMIN_TASK_REMOVE(", ":TASKNAME, :RETCODE, :MESSAGE)" IF SQLCODE <> 0 THEN SAY 'FAILURE DURING SP CALL SQLCODE =' SQLCODE SQLERRMC ELSE DO IF RETCODE <> 0 THEN SAY 'FAILURE RETURNED FROM SP.' RETCODE ' ' MESSAGE ELSE SAY 'TASK WAS REMOVED' 1 END ADDRESS DSNREXX "DISCONNECT" END ELSE SAY 'CONNECTION FAILED' S_RC = RXSUBCOM('DELETE','DSNREXX','DSNREXX') EXIT RETCODE /* //CALL EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20, // PARM='%CALLSP' //SYSPROC DD DSN=*.REXX.SYSUT2,DISP=(OLD,DELETE) //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DUMMY *************************************************************** END OF JOB EXAMPLES *************************************************************** COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@7MON PM62974 DSNX7MON PM62974 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62974 DSN@7MON DSNX7MON THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX7MON MACROS DSN@7MON LISTEND UK78763 COVER LETTER END UK78774 COVER LETTER START PROBLEM DESCRIPTION(S): PM59393 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users * **************************************************************** * PROBLEM DESCRIPTION: An application executing a query * * that is offloaded to the IBM DB2 * * Analytics Accelerator for z/OS (IDAA) * * abends with code ABND=04E-00D35011 * * at LOC=DSNLZGLM.DSNLZRPA:0049. * **************************************************************** * RECOMMENDATION: * **************************************************************** When parsing the DRDA query reply objects returned by the IDAA server, DB2 encounters a DRDA object (TYPDEFOVR) in a context that it did not expect. This is treated as 1 an internal error and DB2 abends as reported. DB2 has been corrected to handle the TYPDEFOVR object. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59393 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZRPA PM59393 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59393 DSNLZRPA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZRPA LISTEND UK78774 COVER LETTER END UK78779 COVER LETTER START PROBLEM DESCRIPTION(S): PM57348 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) * * users DATASHARING SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABENDU2025 in DXRRL732 for IRLM startup * * failure in data sharing. This abend is * * issued following MSGDXR133I messages * * for timeout during IRLM initialization. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** During IRLM restart and global initialization, all existing IRLM members get a notification for the new connection from XES. They issue IXCQUERY for the new member information. If this query fails, no message is sent to the restarting member. The member which is in restart waits, issues message DXR133I and may finally abendu2025. This failure is very rare and its likely due to some timing window when a member connects to the group and when NewConn events are sent out in the group. We need some indication if this error happened on the member which did not respond after receiving the new connection event from XES. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR provides a serviceability change. If a member gets a failure return code from XES query to obtain the new member's connecttion information, it will issue DXR139E message on the 1 console. For example, DXR139E IRLM001 IXCQUERY$JRLM002 REQUEST FAILED, RETURN=08 REASON=0010 If this message appears in the console log and the restarting IRLM member times out for global initialization, then starting the failed member again should work. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM57348 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL711 PM57348 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57348 DXRRL711 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL711 LISTEND UK78779 COVER LETTER END UK78783 COVER LETTER START PROBLEM DESCRIPTION(S): PM59272 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: During start up of DB2 V10 for z/OS, an * * ABEND0C4 may occur in module DSN3RRSX * * and consequently DB2 cannot resolve an * * Indoubt UR associated with an RRSAF * * application. * **************************************************************** * RECOMMENDATION: * **************************************************************** During start up of DB2 V10 for z/OS, an ABEND0C4 may occur in module DSN3RRSX and consequently DB2 cannot resolve an Indoubt UR associated with an RRSAF application. The ABEND0C4 in module DSN3RRSX may be found in LOGREC. This ABEND0C4 does not produce an SVC dump. Module DSN3RRSX has been updated to fix the ABEND0C4 during RRS exit processing. COMPONENT: 5740-XYR01-HIZAA10 APARS FIXED: PM59272 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF requires either an ERLY code refresh or a re-IPL of zOS. 1 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 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 PM59272 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59272 DSN3RRSX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3RRSX LISTEND 1UK78783 COVER LETTER END UK78787 COVER LETTER START PROBLEM DESCRIPTION(S): PM60674 - **************************************************************** * USERS AFFECTED: All DB2 z/OS V10 users of Universal Table * * Space or Segmented table spaces. * **************************************************************** * PROBLEM DESCRIPTION: High latch contention on the space * * map page when batch job scales * * workload to approximately 130 * * concurrent processes running in a * * one-way data sharing environment. * **************************************************************** * RECOMMENDATION: * **************************************************************** A S or X page latch is acquired to update the space map page. The high volume of parallel concurrent insert transactions can increase the frequency of space map page latch contention within the same data sharing member. As a result, insert performance is degraded. DB2 code is modified to classify the update activities of a space map page into critical and non-critical updates. The data page space setting from empty to non-empty or non-full to full are considered as critical updates. Any other data page space class updates are considered non-critical updates. As a result, a conditional s-latch is used to perform a non-critical update. If the s-latch can not be obtained, then the information on the space map page will still be updated except there is the possibility this information will not be written out to the group buffer pool or DASD. In addition, the data page in the buffer pool will not be released until the subsequent insert for compressed table space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60674 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 PM60674 DSNISGSU PM60674 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60674 DSNISGRT DSNISGSU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGRT DSNISGSU 1 LISTEND UK78787 COVER LETTER END UK78806 COVER LETTER START PROBLEM DESCRIPTION(S): PM56909 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users that have index * * keys that contain column data of type * * TIMESTAMP WITH TIME ZONE. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90105 DSNIDM.DSNKINSN * * ERQUAL0D4F was issued when inserting * * a row after an SQL ALTER TABLE * * STATEMENT. * **************************************************************** * RECOMMENDATION: * **************************************************************** Module DSNKCHKP, to prepare for key comparisons called macro DSNKMOVK. The macro DSNKMOVK incorrectly expanded a truncated and versioned index key because it contained a column of data type TIMESTAMP WITH TIME ZONE. Macro DSNKMOVK has been modified to correctly expand truncated and versioned keys that contain columns of data type TIMESTAMP WITH TIME ZONE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56909 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKCHKP PM56909 DSNKISPN PM56909 DSNKLFPR PM56909 DSNKTRAV PM56909 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56909 DSNKCHKP DSNKISPN DSNKLFPR DSNKTRAV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKCHKP DSNKISPN DSNKLFPR DSNKTRAV LISTEND UK78806 COVER LETTER END UK78868 COVER LETTER START PROBLEM DESCRIPTION(S): PM63055 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of migrated * * packages, bound prior to DB2 v10, that * * contain Large Objects or LOBs. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at DSNOTFLA:500E * * (ERQUAL500E) or at DSNOTFLA:5004 * * (ERQUAL5004) can occur in DB2 10 for * * z/OS when running a migrated package * * that references LOBs. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOTFLA:500E (ERQUAL500E) or at location DSNOTFLA:5004 (ERQUAL5004) when running a package that was bound prior to DB2 v10 which references LOB objects. The abend occurs because DB2 uses an invalid mapping structure on migrated packages. As a result, the storage allocated was not sufficient when LOB objects were inserted into a workfile. The following two examples help illustrate failing scenarios. 1. ABEND04E RC00C90101 at DSNOTFLA:5004 (ERQUAL5004). CREATE TABLE MYTB(ROW_ID ROWID NOT NULL GENERATED ALWAYS, COLCLOB CLOB(1G), COLCHAR CHAR(4) ) IN MYDB1.MYTS; INSERT INTO MYTB(COLCLOB, COLCHAR) VALUES ('CLOB','CHAR'); DCL HBLOB1 SQL TYPE IS BLOB(100K); EXEC SQL DECLARE S1 CURSOR FOR SELECT BLOB(COLCHAR,4) FROM MYTB ORDER BY COLCHAR; EXEC SQL OPEN S1; EXEC SQL FETCH S1 INTO :HBLOB1; 2. ABEND04E RC00C90101 at DSNOTFLA:500E (ERQUAL500E). CREATE TABLE TABLE1 (X1 XML, I1 INTEGER); INSERT INTO TABLE1 VALUES (XMLPARSE (DOCUMENT 'B1C'), 1) ; DCL HCLOB1 SQL TYPE IS CLOB(100K); EXEC SQL DECLARE S1 CURSOR FOR SELECT I1, XMLSERIALIZE(X1 AS CLOB(125) INCLUDING XMLDECLARATION) FROM TABLE1 ORDER BY I1; 1 EXEC SQL OPEN S1; EXEC SQL FETCH S1 INTO :HYEAR, :HCLOB1; The code in DB2 is modified to correct the problem which leads to the abend for a migrated package. Additional Keywords: SQLLOB SQLORDERBY SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63055 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOPUFF PM63055 DSNOTFLA PM63055 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63055 DSNOPUFF DSNOTFLA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOPUFF DSNOTFLA LISTEND UK78868 COVER LETTER END UK78870 COVER LETTER START PROBLEM DESCRIPTION(S): PM61832 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures and * * User Defined Functions (UDFs). * **************************************************************** * PROBLEM DESCRIPTION: Abend 0C4 occurs in DSNX9WLM after * * a prior abend. * **************************************************************** * RECOMMENDATION: * **************************************************************** The abend in the ESTAE was caused by an invalid base register. The register was set in ESTAE but got lost during retry and we don't have code to re-establish the base register in the retry exit so the register got lost and results in the 0C4 abend. Code has been added to the stored procedure recovery to restore the base register in the retry exit. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61832 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: A new option to be specified on the parameter to DSNX9WLM on the WLM startup JCL is introduced so user can specify a minimum number of address spaces to be kept for that particular environment. If this parameter is not specified, existing behavior prior to this change applies and WLM controls how many WLM-SPAS to keep. This new option will be implemented as new parameter to DSNX9WLM to the WLM start up JCL. For example: //DSN8WLMP PROC DB2SSN=DSN,NUMTCB=5,APPLENV=WLMTPSMP,MNSPAS=3 ... //WLMTPSMP EXEC PGM=DSNX9WLM,TIME=1440, // PARM='&DB2SSN,&NUMTCB,&APPLENV,&MNSPAS', // REGION=0M In the above example, a minimum of 3 WLM-SPAS will be started each with NUMTCB = 5. WLM will start the minimum number of address spaces on the first stored procedure request on that WLM environment. The valid number specified for the values of MNSPAS is between 0 to 50. A value of 0 means no minimum is specified and old behavior will apply. If the value of MNSPAS is invalid, message DSNX981E will be issued. If the new parameter is not specified, there will be no impact to the existing user base. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9WLM PM61832 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61832 DSNX9WLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9WLM LISTEND UK78870 COVER LETTER END UK78929 COVER LETTER START PROBLEM DESCRIPTION(S): PM60130 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS internal testing users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 INTERNAL SERVICEABILITY CHANGE. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 INTERNAL SERVICEABILITY. 1 Code change for DB2 INTERNAL SERVICEABILITY. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60130 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 PM60130 DSNICPGE PM60130 DSNIDILS PM60130 DSNILREP PM60130 DSNISGRT PM60130 DSNISMRT PM60130 DSNWVINT PM60130 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60130 DSNDQWHS DSNICPGE DSNIDILS DSNILREP DSNISGRT DSNISMRT DSNWVINT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICPGE DSNIDILS DSNILREP DSNISGRT DSNISMRT DSNWVINT MACROS DSNDQWHS LISTEND UK78929 COVER LETTER END UK78996 COVER LETTER START PROBLEM DESCRIPTION(S): PM61903 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users of Access Control * * Authorization Exit (DSNX@XAC) * * * **************************************************************** * PROBLEM DESCRIPTION: Documentation error in DSNXAPRV macro * * for XAPLPRIV values 289 and 229. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 for z/OS: In DSNXAPRV macro, XAPLPRIV value 289 (ACNTLAUTU) is not documented and XAPLPRIV value 229 (SUBPKAUTK) is documented incorrectly. 1 DB2 9 for z/OS: In DSNXAPRV macro, XAPLPRIV value 229 (SUBPKAUTK) is documented incorrectly. DSNXAPRV macro is updated to correct the above documentation errors. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61903 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXACAE PM61903 DSNXAPRV PM61903 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61903 DSNXACAE DSNXAPRV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXACAE MACROS DSNXAPRV LISTEND UK78996 COVER LETTER END UK78998 COVER LETTER START PROBLEM DESCRIPTION(S): PM62540 - **************************************************************** * USERS AFFECTED: All data sharing users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: Group restart can stall during the * * peer CSR phase if a lock structure * * rebuild is done after some of the * * members have completed the CSR * * phase of restart. * **************************************************************** * RECOMMENDATION: * **************************************************************** A group restart was started for a 10 member data sharing group with a new SCA and LOCK structure. Some of the BSDS data sets had been updated with DSNJU003 prior to the group restart. This resulted in peer CSR (Current Status Rebuild) issuing: DSNR021I DSNRRGRC DB2 SUBSYSTEM MUST PERFORM GROUP RESTART FOR PEER MEMBERS DSNJ700I DSNJPB01 ERROR ATTEMPTING TO ACCESS BSDS FOR PEER MEMBER ID= 2, MEMBER NAME= V91B, REASON-CODE= 00D10906. *22 DSNR020I DSNRRUTT START MEMBER V91B, OR REPLY 'NO' OR 'QUIESCED' 1 Peer CSR then waits for a reply or for the member to restart. The IRLM MAXUSRS parm was not defined correctly for 10 members, which resulted in a lock structure rebuild after the 8th member connected to the lock structure. DXR144I REBUILDING LOCK STRUCTURE BECAUSE ALL CONNECTIONS TO IT ARE IN USE This resulted in some members recording a new lock structure version ID (VID) in the SCA, while some members had the prior VID. The lock VID mismatch resulted in a stall of the peer CSR synchronization code in DSNRRGRC. Group Restart processing has been changed to refresh the the lock structure version IDs (VIDs) in the SCA when a lock structure rebuild occurs during peer CSR processing. This will indicate to other members that the CSR (and HSR) phase has completed for this member of the data sharing group. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62540 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRNTFY PM62540 DSNRRGRC PM62540 DSNRRGRH PM62540 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62540 DSNRNTFY DSNRRGRC DSNRRGRH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRNTFY DSNRRGRC DSNRRGRH LISTEND UK78998 COVER LETTER END UK79004 COVER LETTER START PROBLEM DESCRIPTION(S): PM61555 - **************************************************************** * USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) * * SYSPLEXDS DATASHARING users. * **************************************************************** * PROBLEM DESCRIPTION: IRLM issued message: * * * * DXR139E IRLMxxx IXLREBLD(STOP) REQUEST * * FAILED, RETURN=0C REASON=020C0C36 * * * * then abended U2022 while joining the * * data sharing group. * * * 1 **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** The structure was in duplexing mode. A member with a lower function level tried to join the group. IRLM initiated a lock structure rebuild to bring the whole group to the same function level. In order to start a coexist rebuild, IRLM stopped the on-going duplex rebuild, built and queued a rebuild QE. Before the stop duplex rebuild was completed, the rebuild start QE was processed. This caused the IXLREBLD START failed with RC=0C and REASON=020C0C36. Also, message MSGDXR139E had the incorrect IXLREBLD request. The request type should be IXLREBLD START instead of IXLREBLD STOP. GEN: KEYWORDS: *** END IMS KEYWORDS *** Code is added to prevent the queueing of the rebuild QE before the structure falls back to simplex mode. Also, the IXLREBLD request type in message DXR139E is corrected from IXLREBLD(STOP) to IXLREBLD(START). COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM61555 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL070 PM61555 DXRRL710 PM61555 DXRRL712 PM61555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61555 DXRRL070 DXRRL710 DXRRL712 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL070 DXRRL710 DXRRL712 LISTEND UK79004 COVER LETTER END UK79005 COVER LETTER START PROBLEM DESCRIPTION(S): PM63697 - **************************************************************** 1 * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using the -MODIFY DDF * * command with the ALIAS option to specify * * dynamic location alias IP addresses. * **************************************************************** * PROBLEM DESCRIPTION: Dynamic location alias IP addresses * * are lost after DB2 is recycled. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a user specifies dynamic location alias IP addresses using the -MODIFY DDF command with the ALIAS and either the IPV4 or IPV6 options, the values of these IP addresses are inserted into the DB2 Bootstrap data set (BSDS) and also loaded into memory. However, when DB2 is restarted, the values are not reloaded back into memory causing them to be not usable by DB2. DB2 startup processing has been changed to load the dynamic location alias IP addresses (IPV4 and IPV6) into memory if they are present in the DB2 BSDS. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63697 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTSTR PM63697 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63697 DSNLTSTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTSTR LISTEND UK79005 COVER LETTER END UK79007 COVER LETTER START PROBLEM DESCRIPTION(S): PM63890 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using profile tables to * * monitor threads and connections that access * * a DB2 10 for z/OS server via TCP/IP. * **************************************************************** * PROBLEM DESCRIPTION: The following conditions are reported: * * 1. A remote client application may * * incorrectly receive SQLCODE -30041 * * with reason 00E30507 or 00E30508. * * 2. The DSNL092I message of the * * -DISPLAY DDF DETAIL command report * 1 * may indicate an inaccurate INADBAT * * value. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following conditions are reported: 1. When a defined system profile monitoring threshold is exceeded, a system profile monitoring exception condition occurs and DB2 will attempt to queue (suspend) the server thread if the total number of server threads already queued does not exceed the defined profile exception threshold value. In the reported case, a server thread was queued (due to a system profile monitoring exception) but before it could be resumed, the remote client connection, associated with the server thread, terminated. As a result, the (suspended) server thread terminates but DB2 failed to adjust its internal counter that tracks the current number of threads that are being queued due to a system profile monitoring exception. As this condition repeats over time, DB2 system profile monitoring will eventually incorrectly reject the remote request (instead of queuing it) and return SQLCODE -30041 back to the remote client. 2. When a server thread becomes inactive due to MAXDBAT being reached or a defined system profile monitoring threshold is exceeded, and the inactive DBAT is abnormally terminated (eg., remote client terminates its connection with DB2), DB2 failed to decrement its internal counter that tracks the current number of inactive DBATs in the system. As a result, the -DISPLAY DDF DETAIL command may report an incorrect (too high) DSNL092I INADBAT value. DB2 has been changed to properly decrement its internal counters when a (system profile monitoring induced) queued DBAT terminates abnormally. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63890 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTACT PM63890 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63890 DSNLTACT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTACT LISTEND UK79007 COVER LETTER END 1 UK79008 COVER LETTER START PROBLEM DESCRIPTION(S): PM61349 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of DECRYPT built-in functions. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 rc4 can occur at location * * DSNXRSBC+4F8E OFFSET4F8E or at * * DSNXRSBC+7842 OFFSET7842 (v9 offsets) * * when using a DECRYPT built-in function. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 rc4 can occur at location DSNXRSBC+4F8E when using the DECRYPT_CHAR built-in function or at location DSNXRSBC+7842 when using the DECRYPT_BIT built-in function. The failure occurs when DB2 tries to set a null byte for a non-nullable result when trying to setup issuing an SQLCODE20224 (SQL code +20224) WARNING. A null byte should not be set if the result is non-nullable. Instead, an SQLCODE -20224 should be expected. The problem was reported using a CTE query but the problem can occur otherwise. The following examples help to illustrate the problem. EXAMPLE 1. Step 1. Create the following Table. CREATE TABLE T1_PRICE ( PRICE_DATE DATE NOT NULL, LAST_CHANGED TIMESTAMP NOT NULL, LAST_UPDATED_BY VARBINARY(48) NOT NULL ) CCSID EBCDIC ; Step 2. Perform the following insert using an ENCRYPTION password. SET ENCRYPTION PASSWORD 'DOGCAT'; INSERT INTO T1_PRICE VALUES ('2007-02-09', '2007-02-08-09.23.14.340567', ENCRYPT_TDES(CAST('TechBBB' AS BINARY))); Step 3. Perform the following query which will result in an ABEND0C4 rc4 at location DSNXRSBC+4F8E. SELECT DECRYPT_CHAR(LAST_UPDATED_BY) FROM T1_PRICE T1 ; 1 Since the first argument can't be null, the result can't be null so an SQLCODE20224 (or -20224) is the expected result. SQLCODE = -20224, ERROR: ENCRYPTED DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING EXAMPLE 2. If in the first example, column LAST_UPDATED_BY is defined as VARBINARY(48), the query SELECT DECRYPT_CHAR(LAST_UPDATED_BY) FROM T1_PRICE T1 ; does not result in an ABEND. However, the expected result is an SQLCODE20224 (or +20224) because since the first argument can be null, the result can be null. EXAMPLE 3. When using a CTE, these two cases result in an abend. ENCRYPT can be specified as a synonym for ENCRYPT_TDES. Case 1. This query referencing the DECRYPT_CHAR function results in an ABEND0C4 rc4 at location DSNXRSBC+4F8E. WITH ENCR AS ( SELECT ENCRYPT( CAST ('F53F47DA-ED1C-E8C9-47C9-369C7418D3B2' AS BINARY ), 'MSTAR ' ) AS CRYPVAL FROM SYSIBM.SYSDUMMY1 ) SELECT DECRYPT_CHAR ( CRYPVAL,'MSTAR ') FROM ENCR; Case 2. This query referencing the DECRYPT_BIT function results in an ABEND0C4 rc4 at location DSNXRSBC+7842. WITH ENCR AS ( SELECT ENCRYPT( CAST ('F53F47DA-ED1C-E8C9-47C9-369C7418D3B2' AS BINARY ), 'MSTAR ' ) AS CRYPVAL FROM SYSIBM.SYSDUMMY1 ) SELECT DECRYPT_BIT ( CRYPVAL,'MSTAR ') FROM ENCR; Since the first argument can't be null, the result can't be null so an SQLCODE20224 (or -20224) is the expected result. SQLCODE = -20224, ERROR: ENCRYPTED DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING In the error case, since the result cannot be nullable, DB2 should not be trying to issue an +20224 WARNING. Instead, an SQLCODE -20224 ERROR should be issued. 1 If the result can be nullable, an SQLCODE +20224 WARNING will be issued with a friendly null. If the result is not-nullable, an SQLCODE -20224 ERROR will be issued. Additionally, please note the following. 1. Similar failures can occur when using the DECRYPT_DB built-in function. 2. The same problems described above when using the DECRYPT_CHAR or DECRYPT_BIT built-in functions can also occur when an SQLCODE331 condition is detected. If the result can be nullable, an SQLCODE +331 WARNING will be issued with a friendly null. If the result is not-nullable, an SQLCODE -331 ERROR will be issued. The code in DB2 runtime is modified to set the null byte properly for the result of one of the DECRYPT functions, DECRYPT_CHAR, DECRYPT_BIT, or DECRYPT_DB. This will prevent the abend from occurring and allow the proper SQLCODE20224 to be issued as expected. That is, a +20224 is issued for a nullable result with a friendly null or a -20224 is issued for a not nullable result. The same condition is corrected for SQLCODE331. Additional Keywords: SQLDECRYPT SQLENCRYPT SQLCODE20224 SQLCODE331 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61349 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDBC PM61349 DSNXRDB9 PM61349 DSNXRSBC PM61349 DSNXRSB9 PM61349 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61349 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB9 LISTEND UK79008 COVER LETTER END UK79013 COVER LETTER START PROBLEM DESCRIPTION(S): PM64065 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of utilities. * **************************************************************** * PROBLEM DESCRIPTION: THIS IS A FLASHCOPY SERVICEABILITY * * ENHANCEMENT WHICH DOES NOT AFFECT * * ANY EXTERNAL FUNCTION. * * NO PROBLEM IS FIXED BY THIS APAR. * **************************************************************** * RECOMMENDATION: * **************************************************************** This is a serviceability enhancement for DB2 for z/OS Flashcopy utilities. Serviceability apar only. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64065 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM64065 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: After applying the fix for PM31180 in DB2 10 for z/OS, FLASHCOPY IMAGE COPIES of partitioned objects with more than one partition or of linear objects containing more than one piece will insert a string of the form database-name.space-name into the DSNAME (data set name) column of the SYSCOPY record it writes for the FLASHCOPY record with DSNUM 0, similar to SYSCOPY records that are currently written for various types of non-backup activity. This is done to prevent invalid data set names from being written in these records. Users or automated programs sensitive to the contents of SYSIBM.SYSCOPY are advised. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCASA PM64065 DSNUGFCB PM64065 DSNUGFCR PM64065 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64065 DSNUCASA DSNUGFCB DSNUGFCR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNUCASA DSNUGFCB DSNUGFCR LISTEND UK79013 COVER LETTER END UK79015 COVER LETTER START PROBLEM DESCRIPTION(S): PM62096 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of LOAD SHRLEVEL * * CHANGE loading LOB data with file reference * * variables (FRV). * **************************************************************** * PROBLEM DESCRIPTION: A LOAD RESUME SHRLEVEL CHANGE with FRV * * LOB data abended with ABEND04E * * RC00E40350 DSNURWBF OFFSETE87C after a * * duplicate index key was detected. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LOAD RESUME SHRLEVEL CHANGE was loading LOB data with an FRV into a table which has only one LOB column. A duplicate index key was detected and message DSNU1117I was issued. The LOAD utility abended with ABEND04E RC00E40350 at DSNURWBF + x'E87C' with RC00C90077. This problem occurred because the LOAD utility was trying to release the storage of a non-existent LOB locator during the clean up processing. The same abend would occur when processing an empty FRV LOB. The code has been changed to check if the LOB locator exists before releasing it. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62096 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 PM62096 DSNURWBG PM62096 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62096 DSNURWBF DSNURWBG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWBF DSNURWBG LISTEND 1UK79015 COVER LETTER END UK79017 COVER LETTER START PROBLEM DESCRIPTION(S): PM62825 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of UNLOAD utility * **************************************************************** * PROBLEM DESCRIPTION: 1. UNLOAD DELIMITED of a table with a * * DECFLOAT column results in INCORROUT * * in DB2 9. * * * * 2. UNLOAD of a table with a nullable * * varying length column results in * * INCORROUT in DB2 10. * * * * 3. UNLOAD of a table with a DECFLOAT * * column followed by a character column * * results in INCORROUT in both DB2 9 and * * DB2 10. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. INCORROUT happened when executing UNLOAD DELIMITED against a table with a DECFLOAT column in DB2 9. The problem happened because a local variable was not set properly for DECFLOAT columns. 2. INCORROUT happened when executing UNLOAD against a table that was in basic row format (BRF) and contained a nullable varying length column in DB2 10. The problem happened because the output pointer was not set properly for nullable varying length columns. 3. INCORROUT happened when executing UNLOAD against a table that was in basic row format and contained a DECFLOAT column followed by a character column (including varying length column). This error occurs in both DB2 9 and DB2 10. The internal length of a DECFLOAT column is one more than the defined/external length. UNLOAD used the internal length instead of the external length causing the output record to be formatted incorrectly. Additional Keywords: DB2INCORR/K 1. UNLOAD has been changed to correctly set the variable for DECFLOAT columns in DB2 9. 2. UNLOAD has been changed to correctly set the output pointer for nullable varying length columns in DB2 10. 3. UNLOAD has been changed to format an output row containing a 1 DECFLOAT column followed by a character column correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62825 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUULCA PM62825 DSNUULXA PM62825 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62825 DSNUULCA DSNUULXA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULCA DSNUULXA LISTEND UK79017 COVER LETTER END UK79050 COVER LETTER START PROBLEM DESCRIPTION(S): PM56555 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS data * * sharing users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBDF ERQUAL5321 * * during SETXCF REBUILD of SCA structure * * potentially followed by DB2 crash * **************************************************************** * RECOMMENDATION: * **************************************************************** While executing a SETXCF REBUILD of SCA structure, ABEND04E RC00C90101 in LOC=DSNIDM.DSNIDBDF:5321 was encountered, due to a structurally incorrect-looking DBET entry in the local (member) DBET. Investigation showed that during an earlier SCA update (during a typical mainline DBET operation such as during utility, database command, etc.), DBET code had not deleted all the required group DBET records in SCA, since the check that controls the looping through SCA records was incorrect, ending the loop prematurely and leaving behind the last DBET base SCA record when it should have been deleting it. Then through a subsequent restart (non-group restart), the DBET entry in local DBET was built using the excessive SCA record. When eventually the SETXCF REBUILD of SCA structure was run, the SETXCF REBUILD tried to rebuild the SCA structure using this inconsistent local DBET entry, leading to DSNIDBDF:5321. 1 In the reported case it was the SETXCF REBUILD that exposed the incorrect-looking local DBET entry, however the abend could happen even during mainline DBET updates. DB2 has been modified to correct the loop which left the last DBET base SCA record present when it should have deleted it. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56555 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBAB PM56555 DSNIDBMS PM56555 DSNIDBPL PM56555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56555 DSNIDBAB DSNIDBMS DSNIDBPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBAB DSNIDBMS DSNIDBPL LISTEND UK79050 COVER LETTER END UK79062 COVER LETTER START PROBLEM DESCRIPTION(S): PM62259 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of OLAP * * specifications. * **************************************************************** * PROBLEM DESCRIPTION: (1) V9 and V10: * * Incorrect output may occur for a query * * that contains an OLAP specification and * * a subquery predicate. * * (2) V10: * * ABENDOC4 RC00000038 DSNXOWIN+104A may * * occur when a query contains multiple * * OLAP specifications other than RANK, * * DENSE_RANK, and ROW_NUMBER. * **************************************************************** * RECOMMENDATION: * **************************************************************** (1) V9 and V10: Incorrect output may occur for a query that contains an OLAP specification and a subquery predicate. The following is an example of such a failing scenario: SELECT ROW_NUMBER() OVER(ORDER BY C1) FROM T1 1 WHERE T1.C2 IN (SELECT ...) Note: There is an index on T1.C1 and no sort miniplan for the OLAP specification. The subquery is transformed into a correlated virtual table. (2) V10: OC4 ABEND RC00000038 DSNXOWIN+104A may occur when a query contains multiple OLAP specifications other than RANK, DENSE_RANK, and ROW_NUMBER. The following is an example of such a failing scenario: SELECT SUM(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), AVG(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), MIN(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), MIN(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), MAX(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), MAX(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..), .... FROM (SELECT ...) TX; DB2 is modified to process OLAP specifications correctly. Additional keywords: SQLSUBQUERY SQLRANK SQLDENSERANK SQLROWNUMBER SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLOLAP ABENDOC4 RC00000038 in DSNXOWIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62259 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM62259: See PM62259 APAR/PTF text for additional information about why a REBIND is necessary. PM62259 corrects a problem of incorrect output when a query contains OLAP specifications and a subquery predicate. This APAR also corrects ABENDOC4 RC00000038 DSNXOWIN+104A when a query contains multiple OLAP specifications other than RANK, DENSE_RANK, and ROW_NUMBER. 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 DSNXOGA PM62259 DSNXOWIN PM62259 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62259 DSNXOGA DSNXOWIN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXOGA DSNXOWIN LISTEND UK79062 COVER LETTER END UK79064 COVER LETTER START PROBLEM DESCRIPTION(S): PM59815 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of INSTEAD OF * * TRIGGERs. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at * * location DSNXRTC9 offset M111 * * (OFFSETM111) when inserting into a view * * which involves an INSTEAD OF TRIGGER * * that was created prior to DB2 V10. * * * * If the trigger package is rebound on * * DB2 V10, the abend occurs at location * * DSNXRCTC offset M111. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 can occur at location DSNXRTC9 offset M111 (OFFSETM111) when inserting into a view which involves an INSTEAD OF TRIGGER that was created prior to DB2 V10. If the trigger package is rebound on DB2 V10, the abend occurs at location DSNXRCTC offset M111. The abends occur because DB2 doesn't handle the internal structure between the triggering statement and the trigger statement following a migration. The following example illustrates the problem. 1. Create a Table, a View, and an INSTEAD OF TRIGGER in DB2 V9. CREATE TABLE T1(C1 INTEGER); CREATE VIEW V1 AS (SELECT C1 FROM T1); CREATE TRIGGER TRIG1 INSTEAD OF INSERT ON V1 REFERENCING NEW_TABLE AS N FOR EACH ROW MODE DB2SQL BEGIN ATOMIC INSERT INTO T1 SELECT * FROM N; END! 2. Migrate DB2 V9 to DB2 V10. 1 3. Running the following insert statement will result in the failure, ABEND04E at DSNXRTC9:M111. INSERT INTO V1 VALUES(1)! 4. If an insert application which invokes the trigger via the same insert statement is migrated, and the trigger package is rebound, the failure will occur at DSNXRCTC:M111 instead. The code in DB2 has been modified to handle the triggering statement and the trigger body correctly following a DB2 migration. Additional Keywords: SQLVIEW SQLTRIGGER SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59815 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRCTC PM59815 DSNXRTC9 PM59815 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59815 DSNXRCTC DSNXRTC9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRCTC DSNXRTC9 LISTEND UK79064 COVER LETTER END UK79117 COVER LETTER START PROBLEM DESCRIPTION(S): PM53161 - **************************************************************** * USERS AFFECTED: 1. All DB2 10 for z/OS Using Universal * * table space or segmented table space. * * 2. All DB2 user of z/OS V9 and V10 * * Utility with inline copy. * **************************************************************** * PROBLEM DESCRIPTION: 1. Insert may fail with ABEND code * * 0C4-00000038,DSNIDM.DSNISGRT+8DDE * * due to invalid space map page * * pointer. * * 2. Unpredictable error due to broken * * segment chain when inline copy is * * used. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** 1. An invalid pointer to a space map page was referenced to when updating space map page during insert. As the result, insert abended at DSNISGRT. 2. A DWORD partition number was passed as parameter to inline copy, while the called module declared the parameter as WORD, so, the input parameter was truncated. As the result, inline copy might skip some pages and cause unpredictable result if the inline copyis used. DB2 code is fixed to use correct pointer to space map page and proper-length parameter as partition number. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53161 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 PM53161 DSNISGNS PM53161 DSNISGRT PM53161 DSNOPPLS PM53161 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53161 DSNISEGF DSNISGNS DSNISGRT DSNOPPLS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISEGF DSNISGNS DSNISGRT DSNOPPLS LISTEND UK79117 COVER LETTER END UK79120 COVER LETTER START PROBLEM DESCRIPTION(S): PM59746 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of LISTDEF utility with COPY keyword. * **************************************************************** * PROBLEM DESCRIPTION: LISTDEF with COPY and ALL keyword * * resulted in incorrect list. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LISTDEF was used to define a list of index spaces similar to the following: LISTDEF list 1 INCLUDE INDEXSPACES TABLESPACE DBxxxxx.TSyyyyy ALL EXCLUDE INDEXSPACES COPY NO TABLESPACE DBxxxxx.TSyyyyy ALL The resulting list should include COPY YES indexes, but it did not. COPY YES indexes were erroneously being excluded when BASE|LOB|XML|ALL specified. LISTDEF utility is modified to include COPY YES indexes. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59746 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 PM59746 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59746 DSNUILSA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUILSA LISTEND UK79120 COVER LETTER END UK79161 COVER LETTER START PROBLEM DESCRIPTION(S): PM62121 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of CREATE TABLESPACE where * * NUMPARTS is specified with a value * * greater than 254 and is the only option * * specified that applies to the entire * * table space. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 IN DSNXICTS+B3F2 on * * CREATE TABLESPACE when NUMPARTS * * value is greater than 254 and * * is the only option specified that * * applies to the entire table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 IN DSNXICTS+B3F2 on CREATE TABLESPACE when NUMPARTS value is greater than 254 and is the only option specified that applies to the entire table space. CREATE TABLESPACE has been modified to properly handle the case where NUMPARTS is specified and is the only option specified that applies to the entire table space. ADDITIONAL KEYWORDS: 1 SQLCREATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62121 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 PM62121 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62121 DSNXICTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICTS LISTEND UK79161 COVER LETTER END UK79174 COVER LETTER START PROBLEM DESCRIPTION(S): PM64423 - **************************************************************** * USERS AFFECTED: All data sharing users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: A postponed abort UR (Unit of Recovery) * * can become active again after the * * backout has completed if DB2 terminates * * before a system checkpoint is taken in * * a data sharing environment. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a data sharing environment, DB2 restart does not remove the postponed abort RURE when an END-UNDO log record is processed during the CSR (Current Status Rebuild) phase of restart. This will make the postponed abort UR active again, and will require another -RECOVER POSTPONED backout to remove the RURE. This can occur if DB2 terminates before a system checkpoint is taken following the completion of the postponed abort backout. (ref: 159051 ) DSNRRAUB has been changed to remove the RURE in this situation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64423 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNRRAUB PM64423 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM64423 DSNRRAUB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNRRAUB LISTEND UK79174 COVER LETTER END UK79230 COVER LETTER START PROBLEM DESCRIPTION(S): PM48742 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and 10 for z/OS users of * * pureXML. * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes two problems: * * 1.Incorrect output may be obtained when * * an XML value index with key type of * * SQL DECFLOAT is used. * * 2.SQLCODE -16061 is incorrectly issued * * (on DB2 10) and incorrect output or * * DSNXGRDS.DSNXEFDA:M120 abend may * * occur (on DB2 9) for implicit casting * * of invalid format of special values * * to numeric type in XPath predicates * * for general comparison when no * * matching index found. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes two problems: 1.Incorrect output may be obtained when an XML index with key type of SQL DECFLOAT is used. There are two possible causes: a. On DB2 9, there is a logic error in generating index key values for floating point data that conforms to the pattern (0-9)*.0+(1-9)+E... (* means 0 or more, + means 1 or more). In other words, the pattern has one or more 0s following . and then followed by non-zero digit(s) and then E. For example, wrong key values would be generated for 1.05E20, 123.000078E-1 etc. but not for 1.00E3. b. NaN, INF and -INF are special values that are valid in XML value space while other variations such as nan, nAN, iNf, +NaN, -NaN, +INF are not valid. On DB2 9, decfloat index entries for valid special values INF and -INF are missed to be created. While on DB2 10, decfloat index entries for invalid format of INF such as inf, InF, +INF, etc. are wrongly created with the same value as INF and decfloat index entries for -iNf, -Inf etc. are also wrongly created with the same value as -INF. For example, an XML index with SQL DECFLOAT type is created CREATE TABLE T1 (ID INTEGER, DOC XML); CREATE INDEX INDX1 ON T1 (DOC) 1 GENERATE KEY USING XMLPATTERN '/a/b' AS SQL DECFLOAT ; Suppose four rows are inserted INSERT INTO T1 (ID, DOC) VALUES(1,'1.0E20'); INSERT INTO T1 (ID, DOC) VALUES(2,'1.05E20'); INSERT INTO T1 (ID, DOC) VALUES(3,'iNf'); INSERT INTO T1 (ID, DOC) VALUES(4,'INF'); If user has a query below SELECT ID FROM T1 WHERE XMLEXISTS('/a[b>10000]' PASSING DOC); The corrct output should have 3 rows returned with IDs 1,2 and 4. On DB2 9, only 1 row is returned with ID 1. The ID 2 row is missing due to cause a and ID 4 row is missing due to cause b. On DB2 10, all 4 rows are returned with IDs 1,2,3 and 4. The ID 3 row is incorrectly output due to cause b. 2.When performing general comparison of a node with a numeric value in XPath predicates while there is no matching index, implicit casting is carried out first to try to convert the node's value to numeric type. On DB2 9, DSNXGRDS.DSNXEFDA:M120 may occur when the node's value is some invalid format of special values such as iNf, NAN. For some other invalid format such as +INF, it is treated as INF and incorrect output may be obtained. As stated above, only NaN, INF and -INF are valid special values in XML while other variations are invalid. On DB2 10, SQLCODE -16061 is incorrectly issued for implicit casting of invalid format of special values to numeric type in XPath predicates for general comparison. The correct way is to ignore invalid format of special values just as ignoring a random string when casting them to numeric type. In doing so, the query result is consistent with when there is a matching index ("aaa", "-NaN" are ignored at index creation time with no corresponding index entries created). Suppose we have the same DDL as above but the index INDX1 is dropped. For the same above query, DB2 9 gets DSNXGRDS.DSNXEFDA:M120 abend since the error handling is not handled correctly. DB2 10 issues SQLCODE -16061. The correct output should be consistent with when INDX1 is present. DB2 is changed to have correct decfloat index entries created for XML values; It is also changed to ignore the implicit casting error of invalid format of special values to XML numeric values when performing general comparison in XPath predicates. Additional Keywords: XMLALL XMLINDEX SQLDECFLOAT SQLXML INCORROUT DB2INCOR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM48742 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: See PM48742 APAR/PTF text in the PTF cover letter for 1 additional information about this APAR. This APAR fixes two problems - one is incorrect index entries created for an XML value index with key type SQL DECFLOAT; another is incorrectly issuing SQLCODE -16061 when performing general comparison of invalid format of special values to numeric type in XPath predicates when no matching index exists. To make this fix effective for an application, users need to check if there is any XML value index with key type SQL DECFLOAT in use. If so, users need to run CHECK INDEX on such index after the application of this PTF to see it reports any data/index mismatch. REBUILD INDEX needs to be done for index with mismatch issue. 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 DSNNKGEN PM48742 DSNNQDTM PM48742 DSNNQIV PM48742 DSNNQOPM PM48742 DSNNQOPN PM48742 DSNNQOPR PM48742 DSNNQOPS PM48742 DSNNQRES PM48742 DSNNQTOP PM48742 DSNNQXCA PM48742 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM48742 DSNNKGEN DSNNQDTM DSNNQIV DSNNQOPM DSNNQOPN DSNNQOPR DSNNQOPS DSNNQRES DSNNQTOP DSNNQXCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNKGEN DSNNQDTM DSNNQIV DSNNQOPM DSNNQOPN DSNNQOPR DSNNQOPS DSNNQRES DSNNQTOP DSNNQXCA LISTEND UK79230 COVER LETTER END UK79236 COVER LETTER START PROBLEM DESCRIPTION(S): PM58185 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS using * * optimization hints * 1 **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC11 in DSNXOMS +20FC may * * occur when using optimization hints * * to change a correlated subquery into * * a noncorrelated subquery * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC11 in DSNXOMS +20FC may occur when using optimization hints to change a correlated subquery into a noncorrelated subquery. While checking the predicates within the subquery to see if decorrelation is possible, one of the predicates was incorrectly marked. Hence, no decorrelated plan was chosen, leading to the abend. Additional Keywords: OPTHINT OPTHINTS HINT HINTS SQLNONCORRSUBQ SQLCORRSUBQ Code was added to mark the predicate properly so that the subquery could be decorrelated. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58185 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTCP PM58185 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58185 DSNXOTCP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTCP LISTEND UK79236 COVER LETTER END UK79241 COVER LETTER START PROBLEM DESCRIPTION(S): PM61565 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL * * statement containing 'simple-when' CASE * * expression where columns defined with field * * procedure. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect output may occur when an * * SQL statement satisfies all of the * * following conditions: * * * * 1. SQL contains 'simple-when' CASE * * expression; * * 2. the column which is under CASE * 1 * clause is defined with field * * procedure; * * 3. constants are under WHEN clause. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect output may occur when an SQL statement satisfies all of the following conditions: 1. SQL contains 'simple-when' CASE expression; 2. the column which is under CASE clause is defined with field procedure; 3. constants are under WHEN clause. The following examples help to illustrate the problem: CREATE TABLE TEST.T1 (COL1 VARCHAR(5) FIELDPROC FPCVD4); INSERT INTO TEST.T1 VALUES('ABC'); Query #1: SELECT CASE COL1 WHEN 'ABC' THEN '+' ELSE '?' END FROM TEST.T1; The result '?' instead of '+' is returned, which is incorrect. Query #2: SELECT 1 FROM TEST.T1 WHERE CASE COL1 WHEN 'ABC' THEN '+' ELSE '?' END = '+'; No row is returned, which is also incorrect. DB2 didn't handle the column defined with field procedure in 'simple-when' CASE expression correctly, and caused incorrect output. The code in DB2 has been modified correctly to handle the column defined with field procedure in 'simple-when' CASE expression. Additional keywords: SQLCASE SQLWHEN SQLFIELDPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61565 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM61565: See PM61565 APAR/PTF text for additional information about 1 why a REBIND is necessary. PM61565 corrects a problem of incorrect output when an SQL statement satisfies all of the following conditions: 1. SQL contains 'simple-when' CASE expression; 2. the column which is under CASE clause is defined with field procedure; 3. constants are under 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEXC PM61565 DSNXOEXG PM61565 DSNXOOSG PM61565 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61565 DSNXOEXC DSNXOEXG DSNXOOSG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXC DSNXOEXG DSNXOOSG LISTEND UK79241 COVER LETTER END UK79243 COVER LETTER START PROBLEM DESCRIPTION(S): PM56631 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: This APAR is the enabling APAR for new * * function introducing built-in functions * * PACK and UNPACK. This new function will * * be available starting with DB2 10 NFM. * **************************************************************** * RECOMMENDATION: * **************************************************************** New built-in functions PACK and UNPACK are introduced via this APAR. Following is a short description of these functions. Please refer to the DB2 10 SQL Reference for more details. PACK ---- The PACK function returns a binary string that represents all input arguments packed together according to their data type. 1 .-----------------. | | V | >>--- PACK ---(CCSID 1208, expression ---.-------------.--)--->< | | '-,expression-' The schema is SYSIBM. The PACK function returns a varying-length binary string containing the data type information (the data type array) and data values for the arguments. The result data type is VARBINARY, and the maximum length is calculated based on the data types of the arguments. The result cannot be null. The VARBINARY result is constructed as follows: The first byte is a flag byte, reserved for future use. The following two bytes is an integer value set to the number of packed items (number of arguments). Following the data type array are the encoded values for the arguments in sequence specified on the function invocation. Example: SELECT PACK(CCSID 1208, 'Alina', DATE'1977-08-01', DOUBLE(0.5)) FROM SYSIBM.SYSDUMMYU; UNPACK ------ The UNPACK function returns a row of values unpacked from the contents of a binary string input. .-------------------. | | V | >>--UNPACK(expr).*--AS(--name--datatype-.-----------------.-)->< | | '-,name--datatype-' The schema is SYSIBM. The UNPACK function returns a set of values (a row) unpacked from the varbinary string input. The AS clause specifies the data type, length, and encoding for the unpacked items. UNPACK is a "companion" function for PACK, in a sense that, the arguments that were packed using the PACK function can be unpacked back using the UNPACK function. UNPACK function can be used in a SELECT list only and must be followed by ".*" to flatten the row into a list of columns. Furthermore, the AS clause is required for identifying the column names and data types. UNPACK cannot be referenced in a View. Example: SELECT T1.C1, T1.C2, T1.C3, T1.C4, UNPACK( UDF_SCORE( PACK(CCSID 1208, T1.C1, T1.C2, T1.C3)) 1 ).* AS (ID INT, SCORE DOUBLE, CONF DOUBLE) FROM T1; COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56631 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM MULTSYS: ***Action for PM56631: PM56631 is the enabling APAR that introduces the new function support for PACK/UNPACK. Earlier, a pre-conditioning APAR PM55928 was delivered that will be needed. In a data sharing group, the PM55928 pre-conditioning APAR should be applied to all members before applying this ENABLING APAR to any member. The new function will be enabled once this ENABLING APAR is applied. If the new function will not be used, then there is no need to take precautions for rolling through the pre-conditioning PTF ahead of the enabling PTF. Instead, both PTFs can be rolled through together. In addition, because the new function can only be used in DB2 10 New Function Mode (NFM), both pre-conditioning PTF and enabling PTF can be rolled through together on DB2 10 CM subsystems. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHAPLY PM56631 DSNHPTAB PM56631 DSNHSMF2 PM56631 DSNHSMF3 PM56631 DSNHSM5 PM56631 DSNHSM5T PM56631 DSNHSYMH PM56631 DSNXEBR PM56631 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56631 DSNHAPLY DSNHPTAB DSNHSMF2 DSNHSMF3 DSNHSM5 DSNHSM5T DSNHSYMH DSNXEBR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHAPLY DSNHPTAB DSNHSMF2 DSNHSMF3 DSNHSM5 DSNHSM5T DSNHSYMH DSNXEBR LISTEND 1UK79243 COVER LETTER END UK79272 COVER LETTER START PROBLEM DESCRIPTION(S): PM63884 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: The following conditions are reported: * * o Abend 04E-00D30014 DSNLTBST:000A * * o Orphaned DDF related indoubt thread. * * A DDF indoubt (participant) thread * * is holding database resources, and * * thus interfering (lock timeouts, * * etc.) with other work, but DDF * * knowledge of the indoubt thread has * * been lost. The indoubt thread will * * not be visible to the Display Thread * * Indoubt command report, thus no * * heuristic decision can be rendered * * by the Recover Indoubt command. A * * DB2 conditional restart must be * * performed to eliminate the indoubt * * thread (DSNJU003 Forward=NO, * * Backout=NO). * * o Incorrect RESET INDOUBT * * IPADDR(ipaddr..port) FORCE behavior. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following conditions have been reported after using the RESET INDOUBT IPADDR(ipaddr..port / *) FORCE command. o Abend 04E-00D30014 DSNLTBST:000A The user has multiple distinct remote databases, at different IP addresses, that happen to have the same DRDA Two Phase Commit "log name". A RESET INDOUBT IPADDR(ipaddr..port) FORCE command is issued relative to one of the databases and the associated log name information (LNTD) is correctly purged because no connections currently exist with that remote database instance. However, Reset Indoubt command processing also notices another instance of the same log name at a different IP address and incorrectly purges that information even though active connections do exist with the other database instance. The reported abend occurs when the DB2 thread (application) associated with the active connection attempts to commit. o Orphaned DDF related indoubt thread. A problem has been discovered where DDF related knowledge (RLE) associated to an indoubt thread is incorrectly absent. The absence of this DDF indoubt knowledge prevents the indoubt thread from being reported in the Display Thread Indoubt command report. Hence the absence of the knowledge also prevents the thread from being resolved by "automatic indoubt thread resolution" (resync) processing or via the DB2 Recover Indoubt command. The problem is related to the use of 1 some form of DRDA Two Phase Commit protected connections, including XA, which occurs only when using TCP/IP connections to access a DB2 z/OS server. The problem occurs due to incorrect DB2 processing with respect to "prepared", or "pending indoubt", threads. That is, if a remote coordinator drives commit phase 1 "prepare" processing and the connection with the remote coordinator has not yet been terminated by the by the remote client system, then the thread is not considered to be indoubt by DB2 (DB2 perceives this as "pending indoubt"). If a Reset Indoubt Ipaddr Force command is issued while a "pending indoubt" thread exists and happens to be transitioning to the indoubt state, the indoubt thread may be incorrectly purged. This effectively results in an orphaned indoubt thread. The only option to remove the indoubt thread is through some form of DB2 conditional restart via the DB2 Change Log Inventory (DSNJU003) utility. o Incorrect RESET INDOUBT IPADDR(ipaddr..port) FORCE behavior. When a RESET INDOUBT IPADDR(ipaddr..port) FORCE command is entered, as opposed to IPADDR(*), and XA related information is encountered, the command will incorrectly start operating on the XA ipaddr..port information instead of continuing to operate on the information provided to the command. The problem occurs because an internal variable, reflecting actual command input, is incorrectly changed to reflect the XA related information that was encountered. DB2 RESET INDOUBT IPADDR FORCE command processing is changed as follows: o DB2 is changed to maintain log name knowledge relative to IP addresses that are not specified in the Reset Indoubt Ipaddr Force command, even when duplicate log names at different IP addresses are encountered. o DB2 is changed to tolerate a timing condition where the Reset Indoubt Ipaddr Force command is issued as the thread is transitioning from the "Pending Indoubt" to the "Indoubt" state. Orphaned indoubt threads can have a pervasive impact because they cannot be resolved, and can only be eliminated via some form of DB2 cold start. As a result, serviceability changes are also being implemented in an effort to detect and expose other potential logic errors that may occur in the future which would otherwise lead to an orphaned indoubt thread. This new detection logic prevents the indoubt knowledge from being orphaned and results in an abend dump with the following symptom: 04E-00D30014 DSNLTRSI:000F o Incorrect RESET INDOUBT IPADDR(ipaddr..port) FORCE behavior. DB2 is changed to maintain awareness of the ipaddr..port information provided in the command. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63884 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 DSNLTRSI PM63884 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63884 DSNLTRSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTRSI LISTEND UK79272 COVER LETTER END UK79286 COVER LETTER START PROBLEM DESCRIPTION(S): PM62223 - **************************************************************** * USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 * * (HIR2230) users. * **************************************************************** * PROBLEM DESCRIPTION: Dump of IRLM will be skipped if the * * capture phase of another dump is in * * progress. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Either IRLM abends or detects some abnormal conditions, it issues SDUMP or SDUMPX to request dump. If the capture phase of another dump is in progress, the dump request will be skipped. GEN: KEYWORDS: *** END IMS KEYWORDS *** Logic is added to retry issuing dump request. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM62223 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL070 PM62223 DXRRL187 PM62223 DXRRL272 PM62223 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62223 DXRRL070 DXRRL187 DXRRL272 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL070 DXRRL187 DXRRL272 LISTEND UK79286 COVER LETTER END UK79291 COVER LETTER START PROBLEM DESCRIPTION(S): PM62495 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 module DSNAPRHX creates an * * unnecessary dump for an ABEND0D6 * * RC27. * **************************************************************** * RECOMMENDATION: * **************************************************************** Module DSNAPRHX creates an unnecessary dump for an ABEND0D6 RC27. Various recovery or termination cases may result in PCs which are no longer valid. PC interfaces will be restored when DB2 resyncs with RRS or when DB2 is restarted. Module DSNAPRHX has been updated to avoid taking a dump for an ABEND0D6. COMPONENT: 5740-XYR01-HIZAA10 APARS FIXED: PM62495 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 1 -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: ***Action for PM57744: This PTF requires either an EARLY 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAPRHX PM62495 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62495 DSNAPRHX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAPRHX LISTEND UK79291 COVER LETTER END UK79295 COVER LETTER START PROBLEM DESCRIPTION(S): PM61972 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an SQL * * statement that contains a * * TIMESTAMP/DATE/TIME subtraction expression * * in a CASE expression, and the right side of * * the subtraction contains a host variable or * * parameter marker. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location * * DSNXGRDS.DSNXGRM1:P301 may happen when * * running an SQL statement that contains * * a TIMESTAMP/DATE/TIME subtraction * * expression in a CASE expression, and * * the right side of the subtraction * * contains a host variable or parameter * 1 * marker. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 at the location DSNXGRDS.DSNXGRM1:P301 may happen when running an SQL statement that contains a TIMESTAMP/DATE/TIME subtraction expression in a CASE expression, and the right side of the subtraction contains a host variable or parameter marker. An example is shown below: SELECT CASE WHEN 1 > 0 THEN TIMESTAMP('2012-04-16-11.42.00.000000') - CAST(? AS CHAR (26)) END FROM SYSIBM.SYSDUMMY1; 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 the ABEND. Additional keywords: SQLCASE SQLTIMESTAMP SQLTIME SQLDATE SQLHOSTVAR PARAMETERMARKER SQLPMARKER SQLPMK COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61972 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEXG PM61972 DSNXOOSG PM61972 DSNXOSDA PM61972 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61972 DSNXOEXG DSNXOOSG DSNXOSDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXG DSNXOOSG DSNXOSDA LISTEND UK79295 COVER LETTER END UK79299 COVER LETTER START PROBLEM DESCRIPTION(S): PM59864 - **************************************************************** 1 * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS LOG NO * * non-LOB table space * **************************************************************** * PROBLEM DESCRIPTION: A diagnostic compaction log record * * was generated for LOG NO table space. * **************************************************************** * RECOMMENDATION: * **************************************************************** A page compaction process failed to validate the logging attributes on the table space and generated a diagnostic log record for LOG no table space DB2 code is modified to verify the logging attribute on the table space before writing a diagnostic log record during the page compaction process. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59864 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISMCP PM59864 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59864 DSNISMCP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISMCP LISTEND UK79299 COVER LETTER END UK79316 COVER LETTER START PROBLEM DESCRIPTION(S): PM55239 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * * of IBM Text Search. * **************************************************************** * PROBLEM DESCRIPTION: This apar provides the new release * * IBM TextSearch for DB2 for * * z/OS and a new Text Search * * stored procedure: SYSTS_ALTER. * **************************************************************** * RECOMMENDATION: This apar provides the new release IBM Text * * Search that replaces for Omnifind * * Text Search. All the users of Text * * Search for DB2 z/OS need to install or * * migrate to the new server. * * * * The user needs to follow ++HOLD * * instructions to download, install or * * migrate the new release IBM Text Search. * 1 * * * This apar also provides the new stored * * procedure, SYSTS_ALTER, that can modify * * the options of existing index which was * * created by SYSTS_CREATE. * * * * More information about using SYSTS_ALTER in * * "IBM Text Search for DB2 for z/OS" book at * * "chapter 5 Administration stored procedures * * for Text Search". * **************************************************************** For using the new features of IBM Text Search, the user needs to apply this apar, follow instructions in ++HOLD and the IBM Text Search document to install, migration to the new server and bind the Text Search packages. Here are the links of IBM Text Search documents: V1R2: http://publib.boulder.ibm.com/epubs/pdf/dsntsk16.pdf V1R3: http://publib.boulder.ibm.com/epubs/pdf/dsntsm03.pdf COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55239 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM56722 (V10) This PTF modifies program DSNTRIN to install and configure the SYSPROC.ADMIN_INFO_SQL stored procedure in all modes of DB2 10 for z/OS. Previously, ADMIN_INFO_SQL (which is useful for gathering DB2 diagnostic and tuning data) was not installed in conversion mode after migration from DB2 UDB for z/OS Version 8. If you migrated to DB2 V10 from DB2 V8 and DB2 is not yet in new-function mode then after applying this PTF you need to take the following action: Run your copy of job DSNTIJRT with MODE(INSTALL) to install and configure SYSPROC.ADMIN_INFO_SQL. 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 ACTION: This PTF provides two new features: -- The Omnifind Text Search is moving to a new release, IBM Text Search for DB2 z/OS (IBMTS). -- A new stored procedure, SYSPROC.SYSTS_ALTER, can be used to modify the options of an existing IBM Text Search index. 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 (6) Run installation job DSNTIJRV to validate new objects Detailed guidance for these actions is given further below. If you currently use or want to use IBM Text Search for DB2 for z/OS, you need to perform these additional actions: (I) Download the most current version of IBMTS (II) New IBMTS users: Install the IBMTS server (III) Existing users: Migrate to IBMTS from OmniFind server (IV) Add the new stored procedure SYSPROC.SYSTS_ALTER. (V) Where to find more information Detailed guidance for these actions is given further below. ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Actions for all customers ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ---------------------------------------------------------------- (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 DSNTIPRJ in the prefix.SDSNSPFP target library. 1 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 add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSPROC.SYSTS_ALTER WLMENV(DSNWLM_GENERAL) GRANTTO(PUBLIC) Notes: (a) Always leave a blank line between each configuration control statement (b) Inspect each of the new configuration control statement and if required: - Change the WLMENV parameter settings to the names of the WLM environment you use to run these routines at your site - Change the GRANTTO parameter setting to the authorization IDs that need access to the routines - Optionally add the PKGOWNER option ---------------------------------------------------------------- (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: - RTJ09ACL: GRANT EXECUTE setting for SYSPROC.SYSTS_ALTER - RTJ09PKO: PACKAGE OWNER setting for SYSPROC.SYSTS_ALTER - RTJ09WLM: WLM ENV NAME setting for SYSPROC.SYSTS_ALTER 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: RTJ09ACL CHAR M NONE NONE PUBLIC RTJ09PKO CHAR M NONE NONE NULL RTJ09WLM 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. ---------------------------------------------------------------- 1 (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.SYSTS_ALTER, and to rebind the packages for the IBM Text Search routines. ---------------------------------------------------------------- (6) Run installation job DSNTIJRV to validate new objects *********************************************************** * This action is optional for V10 customers *********************************************************** After you have completed the above actions, run your customized copy of job DSNTIJRV to validate installation and configuration of SYSPROC.SYSTS_ALTER. ---------------------------------------------------------------- ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Additional actions for Text Search customers ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| The users need to follow the instructions in the "IBM Text Search for DB2 for z/OS" book to define the Text Search stored procedures and enable Text Search. The following information will refer to the "IBM Text Search for DB2 for z/OS" book. ---------------------------------------------------------------- (I) Download the most current version of IBMTS *********************************************************** * This action is required for Text Search customers *********************************************************** Download the most current version which is FIX R1L5 from the following Web site: http://www.ibm.com/software/data/db2/zos/downloads/oftss.html On this Web site, download the zip file and the readme file for IBMTS Text Search for DB2 for z/OS. The following shows the names of the zip files of IBMTS Text Search Servers: Linux32 - TextSearchServer_setuplinux32.zip Linux64 - TextSearchServer_setuplinux64.zip Window32 - TextSearchServer_setupwin32.zip Window64 - TextSearchServer_setupwin64.zip zLinux - TextSearchServer_setupzlinux.zip For Window32/64: right click the zip then choose extract option 1 For Linux32/Linux64/zlinux: chmod 755 TextSearchServer_setupxxxx.zip unzip TextSearchServer_setupxxxx.zip To install or update the IBMTS server, please refer to the following publications: --readme.html: document that accompanies the installation file. --"Installation, Administration, and Reference": the product documentation for the IBM Text Search for DB2 z/OS. ---------------------------------------------------------------- (II) New IBMTS users: Install the IBMTS server *********************************************************** * This action is required for Text Search customers *********************************************************** To install the IBMTS server, the user needs to follow: Chapter 4. Installing and configuring text search functions --Installing IBM Text Search for DB2 z/OS. (for the new installation). or --Installing fixes on top of the current server. (install IBMTS server on the existing server). ---------------------------------------------------------------- (III) Existing users: Migrate to IBMTS from OmniFind server *********************************************************** * This action is required for Text Search customers *********************************************************** For existing users to migrate IBMTS from OmniFind server they need to follow: Chapter 4. Installing and configuring text search functions --Migrating to IBM Text Search for DB2 for z/OS from OmniFind Text Search. ---------------------------------------------------------------- (IV) Add the new stored procedure SYSPROC.SYSTS_ALTER. *********************************************************** * This action is required for Text Search customers *********************************************************** Refer to steps (5) and (6) of the section above titled "Actions for all customers" ---------------------------------------------------------------- (V) Where to find more information ---------------------------------------------------------------- The user can look for more information for the new SYSTS_ALTER stored procedure at: Chapter 5. Administration stored procedures for text search SYSPROC.SYSTS_ALTER. ACTION: Please note that the following ACTIONS need to be performed with respect to this apar: 1 1. Run your copy of job DSNTIJRT with MODE(INSTALL) to bind, and grant access to the Text Search stored procedures. 2. Refresh WLM environment defined for Text Search stored procedures: v wlm,applenv=wlmname,refresh 3. Refresh DB2 to make sure it will pick up the new Text Search modules. 4. This apar introduces the text search server level R2L11. To update the text search server, download the most current version which is FIX R2L11, from the following Web site: http://www.ibm.com/software/data/db2/zos/downloads/oftss.html From this Web site, click Download OmniFind Text Search Server for DB2 for z/OS. The following shows the names of the files that start the silent installation or update of a Text Search server. 1. Linux - TS_fixR2L11linux_i586.bin 2. zLinux - TS_fixR2L11zlinux.bin 3. Windows - TS_fixR2L11win32.exe To install or update the server, please reference the following publications: "Instructions for installing": readme.html document that accompanies the installation file. "Installation, Administration, and Reference": The product documentation for the IBM Text Search for DB2 z/OS and the IBM OmniFind Text Search Server. 5. This apar provides the fix related to the backup index table. After applying this APAR the users should run SYSTS_UPDATE with ALLROWS options for all the indexes aready created with option UPDATEWITHBACKUP = 1 to make sure the backup index table refreshed with the full collection. Note that UPDATEWITHBACKUP = 1 is default option for SYSTS_CREATE, there for all most the indexes are created with this option. The users can use the following SQL statement to look for the indexes created before applying this APAR with UPDATEWITHBACKUP = 1 select a.indexid, indexschema, indexname, parameter, value from sysibmts.systextindexes a, sysibmts.systextconfiguration 1 where a.indexid = b.indexid and parameter = 'UPDATEWITHBACKUP' and value = '1' Assume that the index SCHEMA1.IVC2 has UPDATEWITHBACKUP = 1 then the users need to run SYSTS_UPDATE with option ALLROWS for this index: CALL SYSPROC.SYSTS_UPDATE('SCHEMA1','IVC2','ALLROWS') COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@O001 PM55239 DSN@O002 PM55239 DSN@O004 PM55239 DSN@O005 PM55239 DSN@O007 PM55239 DSN@O008 PM55239 DSN@O009 PM55239 DSN@O011 PM55239 DSN@O012 PM55239 DSN@O013 PM55239 DSN@O014 PM55239 DSN@O015 PM55239 DSN@O016 PM55239 DSN@O017 PM55239 DSN@O019 PM55239 DSN@O021 PM55239 DSN@RIN PM55239 DSN@RVFY PM55239 DSN@XAZP PM55239 DSNTESR PM55239 DSNTIDXA PM55239 DSNTIDXB PM55239 DSNTIJRT PM55239 DSNTINST PM55239 DSNTINSV PM55239 DSNTINS1 PM55239 DSNTIPRA PM55239 DSNTIPRJ PM55239 DSNTRIN PM55239 DSNTRVFY PM55239 DSNTXAZP PM55239 DSNXRCUF PM55239 DSNXRRTN PM55239 DSN5OCA3 PM55239 DSN5OCA6 PM55239 DSN5OCO3 PM55239 DSN5OCO6 PM55239 DSN5OCU3 PM55239 DSN5OCU6 PM55239 DSN5OPAL PM55239 DSN5OPCR PM55239 DSN5OPDR PM55239 DSN5OPMS PM55239 DSN5OPRE PM55239 DSN5OPSD PM55239 DSN5OPSP PM55239 1 DSN5OPST PM55239 DSN5OPTO PM55239 DSN5OPUP PM55239 DSN5OTMS PM55239 DSN5OTS PM55239 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55239 DSN@O001 DSN@O002 DSN@O004 DSN@O005 DSN@O007 DSN@O008 DSN@O009 DSN@O011 DSN@O012 DSN@O013 DSN@O014 DSN@O015 DSN@O016 DSN@O017 DSN@O019 DSN@O021 DSN@RIN DSN@RVFY DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRJ DSNTRIN DSNTRVFY DSNTXAZP DSNXRCUF DSNXRRTN DSN5OCA3 DSN5OCA6 DSN5OCO3 DSN5OCO6 DSN5OCU3 DSN5OCU6 DSN5OPAL DSN5OPCR DSN5OPDR DSN5OPMS DSN5OPRE DSN5OPSD DSN5OPSP DSN5OPST DSN5OPTO DSN5OPUP DSN5OTMS DSN5OTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTRIN DSNTRVFY DSNTXAZP DSNXRCUF DSNXRRTN MACROS DSN@O001 DSN@O002 DSN@O004 DSN@O005 DSN@O007 DSN@O008 DSN@O009 DSN@O011 DSN@O012 DSN@O013 DSN@O014 DSN@O015 DSN@O016 DSN@O017 DSN@O019 DSN@O021 DSN@RIN DSN@RVFY DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRJ DSN5OCA3 1 DSN5OCA6 DSN5OCO3 DSN5OCO6 DSN5OCU3 DSN5OCU6 DSN5OPAL DSN5OPCR DSN5OPDR DSN5OPMS DSN5OPRE DSN5OPSD DSN5OPSP DSN5OPST DSN5OPTO DSN5OPUP DSN5OTMS DSN5OTS LISTEND UK79316 COVER LETTER END UK79324 COVER LETTER START PROBLEM DESCRIPTION(S): PM61658 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users whose queries utilize * * DB2 global query optimization. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may choose an inefficient access * * path using a correlated subquery * * when a non-correlated subquery may * * have better performance. This may be * * the result of over-estimated correlated * * subquery cardinality when global * * query optimization is enabled and there * * are materialized views involved in the * * join between the parent query block and * * the correlated subquery. * **************************************************************** * RECOMMENDATION: * **************************************************************** When global query optimization is enabled (subsystem parameter OPTXQB=ON) and there are materialized views involved in the join between the parent query block and the correlated subquery, the correlated subquery cardinality may be over-estimated. As a result, DB2 may choose an inefficient access path using the correlated subquery when an access path using a non-correlated subquery may have better performance. For example, if global query optimization is enabled, the DB2 optmizer considers both correlated and non-correlated subquery context for the following query: SELECT C1,C2 FROM V1 1 WHERE V1.C1 IN (SELECT DISTINCT V2.C1 FROM V2, T1 WHERE V2.C2=T1.C1 ); When the optimizer considers the correlated subquery, a join predicate V1.C1=V2.C1 is added by the optimizer. However, since both tables of the added join predicates are materialized views, the estimated filter factor of this join predicate may not be accurate. This may result in an inaccurate estimate of the correlated subquery cardinality and thus an inefficient access path. Additional Keywords: SQLSUBQUERY SQLNONCORRSUBQ SQLCORRSUBQ SQLGLOBALOPT SQLACCESSPATH SQLPERFORMANCE Code is changed to correct the subquery cardinality estimation 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: PM61658 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM61658: See PM61658 APAR/PTF text for additional information about why a REBIND is necessary. PM61658 corrects a problem of over-estimated correlated subquery cardinality when global query optimization is enabled (OPTXQB=ON) and there are materialized views involved in the join between the parent query block and the correlated subquery. This 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. DB2BIND: ***Action for PM44942: See PM44942 APAR/PTF text for additional information about why a REBIND is necessary. PM44942 corrects a problem of a poorly performing access path caused by incorrect filter factor estimation for a compound predicate when frequency or histogram statistics exist, or column cardinality is 1 or 2. 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 PM32384: See PM32384 APAR/PTF text for additional information about why a REBIND is necessary. PM32384 corrects a problem of inaccurate index filter factor estimate when multi-column cardinality exists in some cases 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 DSNXOCCF PM61658 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61658 DSNXOCCF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCCF LISTEND UK79324 COVER LETTER END UK79327 COVER LETTER START PROBLEM DESCRIPTION(S): PM65485 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users that * * ordered and installed DB2 Accessories Suite * * Version 2 Release 2. * **************************************************************** * PROBLEM DESCRIPTION: This PTF will replace member * * DSN5NOT1 in the SDSNNOTC target * * library. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** This PTF should be applied only by customers that ordered and installed DB2 Accessories Suite Version 2 Release 2, as it replaces member DSN5NOT1 in the SDSNNOTC target library, and this notices file should reflect the components/functions received with your order/maintenance of DB2 Accessories Suite. 1 COMPONENT: 5655-R1403-H2AF210 APARS FIXED: PM65485 SPECIAL CONDITIONS: COPYRIGHT: 5655-R1403 COPYRIGHT IBM CORP. 2006 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF should be applied only by customers that ordered and installed DB2 Accessories Suite Version 2 Release 2, as it replaces member DSN5NOT1 in the SDSNNOTC target library, and this notices file should reflect the the components/functions received with your order/maintenance of DB2 Accessories Suite. Do not apply this PTF unless you are a licensed customer of DB2 Accessories Suite Version 2 Release 2. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN5NOT1 PM65485 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65485 DSN5NOT1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSN5NOT1 LISTEND UK79327 COVER LETTER END UK79348 COVER LETTER START PROBLEM DESCRIPTION(S): PM61956 - **************************************************************** * USERS AFFECTED: All users of DB2 dump formatter. * **************************************************************** * PROBLEM DESCRIPTION: The save area chain for the abending * * agent could be incorrect. * **************************************************************** * RECOMMENDATION: * **************************************************************** The formatting logic could incorrectly use the save area back chain pointer for a PC-entered module. This may result in incorrect save areas being reported. Additional checking has been added to stop formatting save areas at the last known PC-entered module. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61956 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWDFSK PM61956 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61956 DSNWDFSK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWDFSK LISTEND UK79348 COVER LETTER END UK79353 COVER LETTER START PROBLEM DESCRIPTION(S): PM62375 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * Created Global Temporary Tables (CGTT) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNITLPE ERQUAL501D * * during CGTT application when the CGTT * * is spread across more than one workfile * * table space * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** While inserting into a CGTT, internal rollbacks to savepoints may occur, which clean up data in the CGTT. In the case of this APAR, there was a main CUB and an extension CUB for the CGTT, since the CGTT was spread across different workfile table spaces. During an internal rollback of the extension CUB, the main CUB was mistakenly used for calculating a space map page number (should have used the extension CUB instead), which had the effect of a wrong space map page being held for later insert into the CGTT. ABEND04E RC00C90101 DSNITLPE ERQUAL501D occurred due to this wrong space map page number. Code has been fixed to use the right CGTT CUB when calculating the space map page number during the internal rollback to savepoint. Additional keywords: SQLCGTT SQLINSERT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62375 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWTTD PM62375 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62375 DSNIWTTD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNIWTTD LISTEND UK79353 COVER LETTER END UK79364 COVER LETTER START PROBLEM DESCRIPTION(S): PM64088 - **************************************************************** * USERS AFFECTED: All HIR2220 (IRLM2.2) and HIR2230 (IRLM2.3) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: Serviceability: Get diagnostic dumps of * * peer IRLM members when DB2 Restart lock * * is rejected due to an incompatible * * holder in a data sharing group. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** DB2 may ABEND04E-00C202AA in DSNB1PER during restart because of rejection of a Restart Lock request with RC=08 and RSN=0400 from IRLM. This may happen if that Restart lock was held incompatibly on some other member in the group. IRLM should collect dumps of peer member(s) to find out how a peer member held that lock. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR adds serviceability in DXRRL2T0 to collect dumps of peer IRLM member(s) when a DB2 Restart lock request gets denied in XES Contention Exit. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM64088 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL187 PM64088 DXRRL2T0 PM64088 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64088 DXRRL187 DXRRL2T0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL187 DXRRL2T0 LISTEND UK79364 COVER LETTER END 1 UK79368 COVER LETTER START PROBLEM DESCRIPTION(S): PM63219 - **************************************************************** * USERS AFFECTED: All DB2 V10 data sharing users SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: 1. DB2 stats provided in IFCID 2 * * reports, in the field QTGSFLMG, * * could be inaccurate. * * 2. During DB2 restart, lock requests * * may timeout prematurely if they wait * * for retained locks (RETLWAIT is set). * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. DB2 statistical data for reporting false XES contentions in the field QTGSFLMG, are incorrectly summed together in the field QTGSFLSE. This field, QTGSFLSE, is the count of sync to async heuristic conversions for LOCK requests in XES. As a result of this error, a monitoring tool may report inaccurate False Contention rate observed in DB2. 2. During DB2 restart, a lock request in IRLM may get timeout before IRLMRWT threshold is reached where RETLWAIT is 1. As a result, the request waiting for held retain locks, may fail sooner with reason RESOURCE UNAVAILABLE waiting for held locks. This APAR corrects the count of False XES Contentions recorded in the field QTGSFLMG of IFCID2 reports. This APAR also corrects DB2 Timeout logic for threads waiting for incompatible retained locks held in the system. DB2 threads will not timeout before the IRLMRWT interval when RETLWAIT is set. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63219 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 PM63219 DSNTLTIM PM63219 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63219 DSNTLSUS DSNTLTIM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLSUS DSNTLTIM LISTEND 1UK79368 COVER LETTER END UK79373 COVER LETTER START PROBLEM DESCRIPTION(S): PM63986 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML * * index * **************************************************************** * PROBLEM DESCRIPTION: For some XML documents, the XML index * * key entries might be missing. This * * causes incorrect results when the XML * * index is used by XMLEXISTS or XMLTABLE * * functions. * **************************************************************** * RECOMMENDATION: * **************************************************************** For some XML documents, the XML index key entries might be missing. This causes incorrect results when the XML index is used by XMLEXISTS or XMLTABLE functions. When the XML document is inserted into an XML column, the XML document is converted into XML records and inserted into the XML table. The XML index key entries are generated based on the XML data in each XML record. It is possible that the top element node is placed in a different record from the record that contains the document node. In this case, the matching of the XMLPATTERN will fail and index key entries are not generated. Incorrect output will occur when the index is used. DB2 is modified to ensure that the XML index key entries are inserted when the top element node is not in the same record as the document node. Additional keywords: XMLALL XMLINDEXES XMLINCORR DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63986 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: See PM63986 APAR/PTF text in the PTF cover letter for additional information about this APAR. PM63986 fixes the problem that the XML index key entry might not be inserted for some XML document. This may cause incorrect output when the index is used. To make this fix effective for the existing XML index, please run CHECK INDEX on the XML index after application of this PTF and rebuild the XML index if there is any data/index mismatch. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNKGEN PM63986 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM63986 DSNNKGEN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNKGEN LISTEND UK79373 COVER LETTER END UK79376 COVER LETTER START PROBLEM DESCRIPTION(S): PM60279 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS and DB2 10 for * * z/OS who have star join enabled * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC38 at DSNXOGP+03F0 when * * star join is enabled and a query * * qualifying for star join contains * * predicates from two dimension tables * * overlapping on the same fact table * * column * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC38 at DSNXOGP+03F0 can occur when star join is enabled and a query qualifying for star join contains predicates from two dimension tables overlapping on the same fact table column. For example: SELECT T0.C1, T1.C2, T2.C3 FROM T0 INNER JOIN T1 ON T1 . C1 = 1 AND T1 . C2 = T0 . C2 <--- AND T1 . C3 = T0 . C3 INNER JOIN T2 ON T2 . C1 = 1 AND T2 . C2 = T0 . C2 <--- AND T2 . C4 = T0 . C4 WHERE . . . T0 is the fact table, and dimension tables T1 and T2 are joined to the same fact table column T0.C2 , as indicated by the arrows. Additional Keywords: SQLSTARJOIN Code has been changed to correct the abend for the situation described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60279 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 DSNXOSJO PM60279 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60279 DSNXOSJO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSJO LISTEND UK79376 COVER LETTER END UK79381 COVER LETTER START PROBLEM DESCRIPTION(S): PM64399 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: The IMS default end user application * * name does not match the correlation ID * * for the IMS transaction. * **************************************************************** * RECOMMENDATION: * **************************************************************** The IMS default end user application name may not match the correlation ID for that transaction in DB2 messages DSNT375I, DSNT376I and DSNV402I. MSGDSNT375I MSGDSNT376I MSGDSNV402I Modules DSN3CT30 and DSN3SI30 have been updated to correct the IMS default end user application name. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64399 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The DB2 Administration Guide will be updated to state that IMS transactions can exploit RACF authorization of DB2 objects if the following tasks are completed. - IMS must be configured to use APPC/OTMA security full or use the Build Security Environment DFSBSEX0 security exit to return RC04 in register 15 to tell IMS to create the ACEE in the dependent region. - The RACF DB2 security exit DSNX@XAC must be installed. - DB2 resources accessed by IMS transactions must be defined in a RACF profile and RACF permits must be created for IMS authorization IDs. 1 The DB2 Administration Guide, Appendix A 'Consideration for the access control authorization routine. When DB2 cannot provide an ACEE' will have the following sentence added - An ACEE is available to DB2 for an IMS transaction if IMS has been configured to use APPC/OTMA security full or the DFSBSEX0 security exit has been configured to return RC04 in register 15 to tell IMS to create the ACEE in the dependent region. The RACF Access Control Module Guide, Chapter 10 section 'When DB2 cannot provide an ACEE' contains this restriction. 1. The ACEE address is not passed for IMS transactions. This restriction will be changed to say - The ACEE may not be available for IMS transactions unless IMS has been configured to use APPC/OTMA security full or the DFSBSEX0 security exit has been configured to return RC04 in register 15 to tell IMS to create the ACEE in the dependent region. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3CT30 PM64399 DSN3SI30 PM64399 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64399 DSN3CT30 DSN3SI30 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3CT30 DSN3SI30 LISTEND UK79381 COVER LETTER END UK79382 COVER LETTER START PROBLEM DESCRIPTION(S): PM63860 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG * * TABLESPACE PART against a rotated tablespace * **************************************************************** * PROBLEM DESCRIPTION: A REORG TABLESPACE PART(m:n) SCOPE ALL * * against a partition by range table * * space failed with RC8. MSGDSNU271I was * * incorrectly issued specifying a * * partition number that was included in * * the REORG TABLESPACE statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an ALTER ROTATE PARTITION FIRST or integer TO LAST followed by several ALTER TABLE ALTER PARTITION n ENDING AT was executed against a partition by range table (PBR), a subsequent REORG TABLESPACE with a part range failed with 1 DSNU271I - REORG PENDING ON TABLE SPACE xxx.xxx PART n PROHIBITS PROCESSING. However, part n was included in the REORG statement. The problem can happen after any rotate because REORG used an incorrect mapping structure to map physical to logical partition numbers. The REORG utility code has been modified to correct the reported problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63860 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURRNG PM63860 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63860 DSNURRNG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURRNG LISTEND UK79382 COVER LETTER END UK79393 COVER LETTER START PROBLEM DESCRIPTION(S): PM64327 - **************************************************************** * USERS AFFECTED: ALL DB2 10 for z/OS users that have indexes * * defined on ROWID columns * **************************************************************** * PROBLEM DESCRIPTION: Incorrect results can occur when a * * ROWID predicate is evaluated during * * index access for an SQL query, DELETE * * or UPDATE. * **************************************************************** * RECOMMENDATION: * **************************************************************** Comparison between internal and external formats of ROWID failed because incorrect lengths were compared. This caused incorrect results to be returned. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLINDEX DB2 has been modified to make sure ROWID comparisons are done with correct lengths - based on the ROWID format. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64327 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 DSNIGSEL PM64327 DSNKBIDP PM64327 DSNKFIDP PM64327 DSNKGSEL PM64327 DSNKIXDB PM64327 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64327 DSNIGSEL DSNKBIDP DSNKFIDP DSNKGSEL DSNKIXDB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIGSEL DSNKBIDP DSNKFIDP DSNKGSEL DSNKIXDB LISTEND UK79393 COVER LETTER END UK79404 COVER LETTER START PROBLEM DESCRIPTION(S): PM60170 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who * * use IDAA (IBM DB2 Analytics Accelerator) * **************************************************************** * PROBLEM DESCRIPTION: 1. Queries that include data encoded by * * multi-byte character set EBCDIC * * encoding scheme are now allowed to * * execute on IDAA. * * * * 2. DDL is added for creating the * * DSN_QUERYINFO_TABLE explain table * * and its containing table spaces and * * indexes to installation job DSNTIJSG * * and sample part DSNTESC. * * * * 3. Multiple accelerator query * * offloading is added * * * * 4. CPU reduction for query when a * * table is not defined on the accelerator * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. Queries that include data encoded by multi-byte character set EBCDIC encoding scheme will now be allowed to execute on IDAA. However, since IDAA encodes the same data in the UTF-8 Unicode encoding scheme, the different collating sequences can cause a difference in result sets. The collating sequence for Unicode is numeric, uppercase 1 characters, and then lower case characters (1, 2, 3, ..., A, B, C, ..., a, b, c, ...). In EBCDIC, the collating sequence is lower case, upper case, and then numeric (a, b, c, ..., A, B, C, ..., 1, 2, 3, ...). There are also differences in collating for the national characters. This affects both data ordering and the results from range predicates. Therefore, if the tables include character columns where more than one of these groups can be found in the column values and the SQL statements include range predicates or ordering on these columns, a query executed in DB2 may return a different result set than the same query executed in IDAA. 2. In V10 this APAR adds DDL for creating DSN_QUERYINFO_TABLE explain table and its containing table spaces and indexes to installation job DSNTIJSG and sample part DSNTESC. This table contains information about the eligibility of query blocks for automatic query rewrite, information about the materialized query tables that are considered for eligible query blocks, reasons why ineligible query blocks are not eligible, and information about acceleration of query blocks. 3. If there is more than one accelerator qualified to offload a particular query, the first qualified accelerator will now be chosen. A "qualified" accelerator is one that is active and contains all referenced tables in the query. 4. When DB2 is enabled for IDAA offload and the DB2 dynamic statement cache (DSC) is active, for a query that is not offloaded to IDAA because the referenced tables are not defined on IDAA, after the initial PREPARE and insert into the DSC DB2 will no longer automatically re-evaluate the query for potential IDAA offload on each PREPARE of that query before searching the DSC for a query match. Instead, DB2 will consider this case a 'never offload to IDAA' situation, and after the initial PREPARE and insert into the DSC, DB2 will always search for a query match in the DB2 DSC first, as DB2 currently does for other queries that can 'never offload to IDAA'. Therefore, after applying this fix, if the user at some point wants DB2 to re-evaluate for IDAA offload those cached queries whose table(s) are not defined on IDAA, the user must take explicit action to remove the cached query from the DSC. Additional Keywords: IDAAV2R1/K SQLEXPLAIN 1. To enable the offloading to IDAA of queries that include data encoded by multi-byte character set EBCDIC encoding scheme, the new subsystem parameter QUERY_ACCEL_OPTIONS should be set to 1. The default of this new subsystem parameter is NONE. See the HOLD data for more information on setting this parameter. Items 2 through 4 do not require any changes to subsystem parameters. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60170 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM60170 (V10): This PTF adds an online-changeable subsystem parameter in DSN6SPRM called QUERY_ACCEL_OPTIONS that can be used to specify additional types of SQL queries to be included in query offloading. Valid options for QUERY_ACCEL_OPTIONS are: * 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 although IDAA encodes the same data in the UTF-8 Unicode encoding scheme. Note that EBCDIC and Unicode implement different collating sequences. The collating sequence for Unicode is numeric, uppercase characters, and then lower case characters (1, 2, 3, ..., A, B, C, ..., a, b, c, ...). In EBCDIC, the collating sequence is lower case, upper case, and then numeric (a, b, c, ..., A, B, C, ..., 1, 2, 3, ...). There are also differences in collating for the national characters. This affects both data ordering and the results from range predicates. Therefore, if the tables include character columns where more than one of these groups can be found in the column values and the SQL statements include range predicates or ordering on these columns, a query executed in DB2 may return a different result set than the same query executed in IDAA. This PTF also adds DDL for creating the DSN_QUERYINFO_TABLE explain table and its containing table spaces and indexes to installation job DSNTIJSG and sample part DSNTESC. This table contains information about the eligibility of query blocks for automatic query rewrite, information about the materialized query tables that are considered for eligible query blocks, reasons why ineligible query blocks are not eligible, and information about acceleration of query blocks. 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 installation job DSNTIJSG (5) Create the SYSIBM.DSN_QUERYINFO_TABLE explain table (6) Update your customized copy of sample DDL part DSNTESC (7) Create the sample DSN_QUERYINFO_TABLE explain table 1 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 members DSNTINST and 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 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) 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 QUERY_ACCEL_OPTIONS=, where is either NONE or 1 to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding QUERY_ACCEL_OPTIONS here, the value 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 for all customers This PTF adds an entry for QUERY_ACCEL_OPTIONS to the CLIST default input members 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: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value specified for QUERY_ACCEL_OPTIONS in step (2), above. 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. ---------------------------------------------------------------- (4) Update your customized copy of installation job DSNTIJSG ---------------------------------------------------------------- ==> This action is required for all customers 1 Edit your customized copy of DSNTIJSG and locate job step DSNTIJQ. Append the following DDL to the existing in-stream input under the CREATE DD: CREATE LOB TABLESPACE DSNOQIL1 IN DSNOPTDB BUFFERPOOL BP8K0 USING STOGROUP DSNOPTSG; CREATE LOB TABLESPACE DSNOQIL2 IN DSNOPTDB BUFFERPOOL BP8K0 USING STOGROUP DSNOPTSG; CREATE TABLE SYSIBM.DSN_QUERYINFO_TABLE ( "QUERYNO" INTEGER NOT NULL WITH DEFAULT , "QBLOCKNO" SMALLINT NOT NULL WITH DEFAULT , "QINAME1" VARCHAR(128) NOT NULL WITH DEFAULT , "QINAME2" VARCHAR(128) NOT NULL WITH DEFAULT , "APPLNAME" VARCHAR(24) NOT NULL WITH DEFAULT , "PROGNAME" VARCHAR(128) NOT NULL WITH DEFAULT , "VERSION" VARCHAR(122) NOT NULL WITH DEFAULT , "COLLID" VARCHAR(128) NOT NULL WITH DEFAULT , "GROUP_MEMBER" VARCHAR(24) NOT NULL WITH DEFAULT , "SECTNOI" INTEGER NOT NULL WITH DEFAULT , "SEQNO" INTEGER NOT NULL WITH DEFAULT , "EXPLAIN_TIME" TIMESTAMP NOT NULL WITH DEFAULT , "TYPE" CHAR(8) NOT NULL WITH DEFAULT , "REASON_CODE" SMALLINT NOT NULL WITH DEFAULT , "QI_DATA" CLOB(2M) NOT NULL WITH DEFAULT , "SERVICE_INFO" BLOB(2M) NOT NULL WITH DEFAULT , "QB_INFO_ROWID" ROWID NOT NULL GENERATED ALWAYS ) IN DSNOPTDB.DSNOPTTS CCSID UNICODE; CREATE AUX TABLE SYSIBM.DSN_QUERYINFO_AUX IN DSNOPTDB.DSNOQIL1 STORES SYSIBM.DSN_QUERYINFO_TABLE COLUMN "QI_DATA"; CREATE INDEX SYSIBM.DSN_QUERYINFO_AUXINX ON SYSIBM.DSN_QUERYINFO_AUX; 1 CREATE AUX TABLE SYSIBM.DSN_QUERYINFO_AUX2 IN DSNOPTDB.DSNOQIL2 STORES SYSIBM.DSN_QUERYINFO_TABLE COLUMN "SERVICE_INFO"; CREATE INDEX SYSIBM.DSN_QUERYINFO_AUXINX2 ON SYSIBM.DSN_QUERYINFO_AUX2; ---------------------------------------------------------------- (5) Create the SYSIBM.DSN_QUERYINFO_TABLE explain table ---------------------------------------------------------------- ==> This action is required for all customers Use SPUFI or similar SQL processor to process the SQL statements listed in the previous step. ---------------------------------------------------------------- (6) Update your customized copy of sample DDL part DSNTESC ---------------------------------------------------------------- ==> This action is required for all customers who maintain a customized copy of job DSNTESC (a) Edit your customized copy of job DSNTESC (b) Append the following to the list of DROP TABLESPACE statements: --DROP TABLESPACE DSN8D10A.DSN8S10Q; --DROP TABLESPACE DSN8D10A.DSN8L10Q; --DROP TABLESPACE DSN8D10A.DSN8L10R; (c) Append the following to the list of CREATE TABLE SPACE statements: CREATE TABLESPACE DSN8S10Q IN DSN8D10A BUFFERPOOL BP0 CCSID UNICODE USING STOGROUP DSN8G100 PRIQTY 30 SEGSIZE 16 CLOSE NO; CREATE LOB TABLESPACE DSN8L10Q IN DSN8D10A IN DSN8D10A BUFFERPOOL BP8K0 USING STOGROUP DSN8G100; CREATE LOB TABLESPACE DSN8L10R IN DSN8D10A BUFFERPOOL BP8K0 USING STOGROUP DSN8G100; (d) Add the following after the CREATE TABLE statement for DSN_KEYTGTDIST_TABLE: CREATE TABLE DSN81010.DSN_QUERYINFO_TABLE ( "QUERYNO" INTEGER NOT NULL WITH DEFAULT 1 , "QBLOCKNO" SMALLINT NOT NULL WITH DEFAULT , "QINAME1" VARCHAR(128) NOT NULL WITH DEFAULT , "QINAME2" VARCHAR(128) NOT NULL WITH DEFAULT , "APPLNAME" VARCHAR(24) NOT NULL WITH DEFAULT , "PROGNAME" VARCHAR(128) NOT NULL WITH DEFAULT , "VERSION" VARCHAR(122) NOT NULL WITH DEFAULT , "COLLID" VARCHAR(128) NOT NULL WITH DEFAULT , "GROUP_MEMBER" VARCHAR(24) NOT NULL WITH DEFAULT , "SECTNOI" INTEGER NOT NULL WITH DEFAULT , "SEQNO" INTEGER NOT NULL WITH DEFAULT , "EXPLAIN_TIME" TIMESTAMP NOT NULL WITH DEFAULT , "TYPE" CHAR(8) NOT NULL WITH DEFAULT , "REASON_CODE" SMALLINT NOT NULL WITH DEFAULT , "QI_DATA" CLOB(2M) NOT NULL WITH DEFAULT , "SERVICE_INFO" BLOB(2M) NOT NULL WITH DEFAULT , "QB_INFO_ROWID" ROWID NOT NULL GENERATED ALWAYS ) IN DSN8D10A.DSN8S10Q CCSID UNICODE; CREATE AUX TABLE DSN81010.DSN_QUERYINFO_AUX IN DSN8D10A.DSN8L10Q STORES DSN81010.DSN_QUERYINFO_TABLE COLUMN "QI_DATA"; CREATE INDEX DSN81010.DSN_QUERYINFO_AUXINX ON DSN81010.DSN_QUERYINFO_AUX; CREATE AUX TABLE DSN81010.DSN_QUERYINFO_AUX2 IN DSN8D10A.DSN8L10R STORES DSN81010.DSN_QUERYINFO_TABLE COLUMN "SERVICE_INFO"; CREATE INDEX DSN81010.DSN_QUERYINFO_AUXINX2 ON DSN81010.DSN_QUERYINFO_AUX2; ---------------------------------------------------------------- (7) Create the sample DSN_QUERYINFO_TABLE explain table ---------------------------------------------------------------- ==> This action is optional Use SPUFI or similar SQL processor to process the SQL statements listed in the previous step. 1 End of ***Action for PM60170 (V10). COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM60170 DSNDQWPZ PM60170 DSNDSPRM PM60170 DSNTESC PM60170 DSNTIDXA PM60170 DSNTIDXB PM60170 DSNTIJSG PM60170 DSNTIJUZ PM60170 DSNTINST PM60170 DSNTINS3 PM60170 DSNTXAZP PM60170 DSNWZIFA PM60170 DSNXOALS PM60170 DSNXOEX1 PM60170 DSNXOMPS PM60170 DSNXONZA PM60170 DSNXONZC PM60170 DSNXONZO PM60170 DSNXONZS PM60170 DSNXOOS1 PM60170 DSN6SPRM PM60170 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60170 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTESC DSNTIDXA DSNTIDXB DSNTIJSG DSNTIJUZ DSNTINST DSNTINS3 DSNTXAZP DSNWZIFA DSNXOALS DSNXOEX1 DSNXOMPS DSNXONZA DSNXONZC DSNXONZO DSNXONZS DSNXOOS1 DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP DSNWZIFA DSNXOALS DSNXOEX1 DSNXOMPS DSNXONZA DSNXONZC DSNXONZO DSNXONZS DSNXOOS1 MACROS DSN@XAZP DSNDQWPZ DSNDSPRM DSNTESC DSNTIDXA DSNTIDXB DSNTIJSG DSNTIJUZ DSNTINST 1 DSNTINS3 DSN6SPRM LISTEND UK79404 COVER LETTER END UK79406 COVER LETTER START PROBLEM DESCRIPTION(S): PM57206 - **************************************************************** * USERS AFFECTED: All users of DB2 accounting records with * * work eligible to run on an IBM specialty * * engine. * **************************************************************** * PROBLEM DESCRIPTION: IBM specialty engine eligible work may * * run on a general purpose CP if an IBM * * specialty engine is not available. The * * time a given thread runs on a general * * purpose CP while eligible to run on an * * IBM specialty engine is not available * * in DB2 accounting records in DB2 10. * **************************************************************** * RECOMMENDATION: * **************************************************************** IBM specialty engine eligible time that runs on a general purpose CP will be reported in a serviceability field in DB2 accounting records. The field QWACZIIP_ELIGIBLE is reintroduced in IFCID3 in DB2 10 as a serviceability field. The field captures the IBM specialty engine eligible time that is run on a general purpose CP for a subset of IBM specialty engine eligible processing. More specifically, the time will reflect the eligible time for: 1. distributed DBATs 2. parallel query parent threads and 3. zIIP eligible utilities All other cases of IBM specialty engine offload are NOT reflected in this serviceability field. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57206 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWAC PM57206 DSNLIRTR PM57206 DSNTTENE PM57206 DSNTTNOT PM57206 DSNTTNO3 PM57206 DSNTTRUN PM57206 DSNTTTC PM57206 DSNTTTGE PM57206 DSNVSDC0 PM57206 DSNWACDF PM57206 1 DSNWDFIF PM57206 DSNWDMPS PM57206 DSNWVSMT PM57206 DSNWVSR1 PM57206 DSNWVZCK PM57206 DSNWVZIT PM57206 DSNWVZPS PM57206 DSNWVZSA PM57206 DSNWVZSS PM57206 DSNXEET PM57206 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57206 DSNDQWAC DSNLIRTR DSNTTENE DSNTTNOT DSNTTNO3 DSNTTRUN DSNTTTC DSNTTTGE DSNVSDC0 DSNWACDF DSNWDFIF DSNWDMPS DSNWVSMT DSNWVSR1 DSNWVZCK DSNWVZIT DSNWVZPS DSNWVZSA DSNWVZSS DSNXEET THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIRTR DSNTTENE DSNTTNOT DSNTTNO3 DSNTTRUN DSNTTTC DSNTTTGE DSNVSDC0 DSNWACDF DSNWDFIF DSNWDMPS DSNWVSMT DSNWVSR1 DSNWVZCK DSNWVZIT DSNWVZPS DSNWVZSA DSNWVZSS DSNXEET MACROS DSNDQWAC LISTEND UK79406 COVER LETTER END UK79431 COVER LETTER START PROBLEM DESCRIPTION(S): PM61609 - **************************************************************** * 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 * 1 * related to output from stored procedure * * ADMIN_INFO_SQL for DDL and catalog * * statistics. The symptoms usually are * * incorrect output when building the DDL * * and statistics output files or can * * relate to long processing time. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF ADMIN_INFO_SQL EVENTS: ADMIN_INFO_SQL was sometimes not producing the correct output when creating DDL and STATS output files or taking a long time to process the output. Here are a list of reported issues: - DSNADMSB not returning correct error return code causing JCL step code to always be zero. - ADMIN_INFO_SQL running a long time when collecting information in an environment that has a lot of views. - Use the DSN_VIEWREF_TABLE if available. - Could attempt to process a view several times. Now will only process views once. - Eliminated upward view dependencies as the default. Now a switch is added in the DDL input parameters. - Do not issue an error if PROFILE or IDAA tables are not available. Now will ignore. ADMIN_INFO_SQL had several new features added: - Added collection of IDAA V2 tables. - Added DBID/OBID into the DDL for the table, database, index, table space. - Enhanced PLAN_TABLE collection. - Can now use ALIASES as input. - Get MEPL for only RDS to minimize output size. - Add Views, Databases and Tablespaces to report in EXPL. PROBLEM CONCLUSION: The reported ADMIN_INFO_SQL problems are now corrected. ADDITIONAL KEYWORDS: SQLSP SQLSTOREDPROC ADMININFOSQL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61609 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 1 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. --------------------------------------------------------------- (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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMSB PM61609 DSN@DMSS PM61609 DSNADMSB PM61609 DSNADMSS PM61609 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61609 DSN@DMSB DSN@DMSS DSNADMSB DSNADMSS 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMSB DSNADMSS MACROS DSN@DMSB DSN@DMSS LISTEND UK79431 COVER LETTER END UK79433 COVER LETTER START PROBLEM DESCRIPTION(S): PM63211 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * BIND EXPLAIN(YES) on SQL that * * contains a VIEW or MQT and have * * DSN_VIEWREF_TABLE defined. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * DSN_VIEWREF_TABLE is not * * populated when executing a * * BIND with EXPLAIN(YES) on * * SQL that contains VIEW(s) * * or MQT(s). * * * * PROBLEM SCENARIO: * * * * The reported problem occurs when * * executing a BIND EXPLAIN(YES) of an * * SQL statement that contains VIEW(s) * * or MQT(s). The referenced VIEW/MQT * * should be added to the * * DSN_VIEWREF_TABLE so that it * * can be linked to the PLAN_TABLE. The * * PLAN_TABLE will only contain the base * * tables used for the query. Any VIEW(s) * * or MQT(s) referenced should appear in * * the DSN_VIEWREF_TABLE. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: A variable in DB2 that is used to turn on collection for DSN_VIEWREF_TABLE was not set correctly and not populating the table during BIND with EXPLAIN(YES). PROBLEM CONCLUSION: DB2 has been fixed to populate DSN_VIEWREF_TABLE during BIND with EXPLAIN(YES) 1 ADDITIONAL KEYWORDS: BIND SQLVIEW SQLMQT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63211 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM63211: See PM63211 APAR/PTF text for additional information about why a REBIND is necessary. PM63211 corrects a problem with inserts into the DSN_VIEWREF_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 DSNXOMRG PM63211 DSNXOOP PM63211 DSNXOQ1 PM63211 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63211 DSNXOMRG DSNXOOP DSNXOQ1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMRG DSNXOOP DSNXOQ1 LISTEND UK79433 COVER LETTER END UK79447 COVER LETTER START PROBLEM DESCRIPTION(S): PM61976 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and DB2 * * 10 for z/OS REORG SORTDATA NO utility users * * with table partitioned objects when the * * REORG uses a clustering NPI (nonpartitioned * * index) to unload data, whose columns match * * the columns of the PARTITION BY clause of * * the table * **************************************************************** * PROBLEM DESCRIPTION: After applying APAR PM44475 (UK73344 in * * V10, UK73346 in V9, UK73345 in V8) * * REORG SORTDATA NO on a table-controlled * 1 * table space unloads all data into * * partition 1 when the utility uses a * * nonpartitioned clustering index whose * * columns match the columns of the * * PARTITION BY clause of the table * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying APAR PM44475, a REORG TABLESPACE SORTDATA NO on a table controlled partitioned table space with a nonpartitioned index (NPI) as the clustering index, defined on the same columns and in the same order as the limit key, may unload all data into partition 1. Investigation showed that the PM44475 APAR logic was missing the code to determine which partition the row should be loaded into when the NPI is used to unload data in the context of that APAR. Without that missing code the partition determination always defaulted to partition 1. In the reported scenario, this problem was exposed by SQL SELECT COUNT(*) with the predicate using the partitioning key, however other incorrect output symptoms are possible also. Code has been added to the data manager component of DB2 to return the correct partition number to the utility, ensuring that data is reloaded into correct partitions. Additional keywords: DB2INCORR/K SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61976 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: APAR PM58177 has enabled REORG TABLESPACE SHRLEVEL CHANGE to accept a user defined mapping table created in a partition-by-growth ( PBG ) table space. The Utility Guide and Reference has been updated with the following information, under the REORG TABLESPACE utility in section titled 'Mapping table and SHRLEVEL CHANGE' : Before running REORG TABLESPACE with SHRLEVEL CHANGE on a table space with non-LOB data, you must create a mapping table and index for the table space. The table space that | contains the mapping table must be either classic segmented | or a partition-by-growth table space, and cannot be the table space to be reorganized. DOCUMENTATION: See PM47356 APAR/PTF text for additional information. This APAR/PTF modifies the DB2 Utility Guide and Reference and the Messages manual. The change will be documented in the DB2 Utility Guide and Reference and Messages, and in the Information Management Software for z/OS Solutions Information Center. 1 The change is as follows. In the Utility Guide and Reference, under REORG TABLESPACE, Option descriptions, SORTDATA option: SORTDATA NO Specifies that the data is to be unloaded in the order of the clustering index. SORTDATA NO cannot be specified | with SHRLEVEL CHANGE or if the table space is in REORG- | PENDING. Specify SORTDATA NO if one of the following conditions is true: * The data is in or near perfect clustering order, the | table space is not in REORP, and the REORG utility is used to reclaim space from dropped tables. * The data is very large, an insufficient amount of disk | space is available for sorting, and the table space is not in REORP. In the Messages manual, under DSNU messages: DSNU070I csect-name KEYWORD OR OPERAND x INVALID WITH y Explanation: The use of a keyword or operand is | inconsistent with another keyword, operand or condition. | x and y The keywords, operands or conditions that cannot be used together. System action: The control statement in error is rejected and processing is halted. User response: Correct the control statement in error and resubmit the job. | Problem determination: The REORG TABLESPACE | utility issues this message when the keywords, operands or | conditions are not allowed to be used in combination. ACTION: ***Action for PM59605 This PTF modifies the DB2 installation CLIST member DSNTINST to fix a bug that causes it to ignore the NEWFUN setting specified in the DSNTIDxx input member when the CLIST is run in UPDATE mode. This PTF modifies DSNTINST in the SDSNCLST target library only. If you have already installed or migrated to this version of DB2 then after applying this 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. 1 ACTION: The PTF for APAR PM55051 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. PM55051 provides support for REORG TABLESPACE PART SORT NPSIs (Non-partitioned Secondary Indexes). This is a performance enhancement to part-level REORG involving NPSIs intended to improve elapsed time. Since the removal of the BUILD2 phase for partition-level REORG in DB2 9, the performance of REORG was degraded in some cases due to the cost of building shadow NPSIs. Shadow NPSIs are populated initially with keys of parts which are not in the scope of the REORG during the UNLOAD phase. Then keys from parts within the scope of the REORG are sorted and inserted into the shadow NPSI during the SORT and REBUILD phases, respectively. Significant performance improvement can be achieved by sorting all keys of the NPSI in the same sort operation and rebuilding the index from the entire set of sorted keys. This APAR will add functionality to improve performance while leaving the old behavior intact and allow the customer to control the behavior through the installation panel and a keyword. This APAR modifies the processing of non-partitioned secondary indexes for REORG TABLESPACE PART SHRLEVEL CHANGE/REFERENCE when NPSIs are defined on the table space. Processing of NPSIs in this case will now be done in one of two ways as documented in the UNLOAD phase section of Execution Phase of REORG TABLESPACE in the Utility Guide and Reference. 1. During UNLOAD, one or more subtasks unload NPSI keys from parts not within the scope of the REORG and build the shadow NPSI. Keys from parts within the scope of the REORG are generated from the reorganized data rows, sorted, and inserted in the shadow index. 2. During UNLOAD, one or more subtasks processes NPSI keys from parts not within the scope of the REORG. These keys are routed to a sort process to be sorted with the keys from parts within the scope of the REORG. The shadow NPSI is built from this sorted set of keys. A new message is issued when all keys of an NPSI are sorted during a part-level REORG TABLESPACE. A new keyword is added on REORG to control the sorting of all NPSI keys during a 1 part-level REORG TABLESPACE. The zparm controlling the sorting of all NPSI keys during a part-level REORG is extended to allow more options. ---------------------------------------------------------------- Changes to Messages and Codes DSNU1242I csect-name ALL KEYS OF A NON-PARTITIONED SECONDARY INDEX WILL BE SORTED Explanation During a part-level REORG all keys of a non-partitioned secondary index will be sorted before rebuilding the index. This is controlled by the keyword SORTNPSI and the zparm REORG_PART_SORT_NPSI. When SORTNPSI is specified as YES or AUTO all keys may be sorted. When SORTNPSI is not specified, and REORG_PART_SORT_NPSI is set to YES or AUTO, all keys may be sorted. System action Processing is continues. Severity 0 (informational) ---------------------------------------------------------------- Changes to Utility Guide and Reference A new keyword SORTNPSI is added to control the method of building an NPSI during REORG TABLESPACE PART. Options of AUTO, YES, and NO are available on the keyword. A default is not applicable in this case because the value will be determined by zparm REORG_PART_SORT_NPSI if the keyword is not specified. .-FORCE--NONE----. (3) >--+----------------+--------+-----------------+---------------> +-FORCE--READERS-+ +-SORTNPSI AUTO---+ '-FORCE--ALL-----' '-SORTNPSI YES----' '-SORTNPSI NO-----' 3. The default for SORTNPSI is the value of the REORG_PART_SORT_NPSI subsystem parameter. SORTNPSI Specifies when REORG TABLESPACE PART should sort all keys of a non-partitioned secondary index. This keyword is ignored for a REORG that is not partition-level or a REORG with no non-partitioned secondary indexes. If SORTNPSI is not specified the value will be determined by zparm REORG_PART_SORT_NPSI. The benefit of sorting all keys of a non-partitioned secondary index increases as the ratio of data reorganized to total data in the table space increases. AUTO Specifies that if sorting all keys of the non-partitioned 1 secondary indexes improves the elapsed time and CPU performance, all keys are sorted. YES Specifies that if sorting all keys of the non-partitioned secondary indexes improves the elapsed time, all keys are sorted. NO Specifies that only keys of the non-partitioned secondary indexes that are in the scope of the REORG are sorted. The default value is the value of subsystem parameter REORG_PART_SORT_NPSI. ---------------------------------------------------------------- Changes to DB2 Installation This APAR modifies the DSN6SPRM.REORG_PART_SORT_NPSI subsystem parameter. REORG_PART_SORT_NPSI specifies the default method of building an NPSI during REORG TABLESPACE PART when the SORTNPSI keyword is not provided in the utility control statement. Valid settings for REORG_PART_SORT_NPSI are AUTO, NO, and YES. The default setting is NO. REORG_PART_SORT_NPSI is online changeable and has member scope in data sharing. DSN6SPRM: The REORG_PART_SORT_NPSI parameter is added with a range of AUTO, NO, and YES. The default setting is NO. DSNTIJUZ: The REORG_PART_SORT_NPSI parameter is added under the DSN6SPRM invocation with a default setting of NO. ---------------------------------------------------------------- Changes to DB2 instrumentation DSNDQWPZ: Field QWP4RPSNE is modified to trace the REORG_PART_SORT_NPSI internal setting: . . . QWP4RPSN DS CL1 REORG_PART_SORT_NPSI * * A=AUTO, N=NO, Y=YES . . . The IFCID 106 formatter stored procedures, SYSPROC.DSNWZP and SYSPROC.ADMIN_INFO_SYSPARM are updated to report the REORG_PART_SORT_NPSI setting. ---------------------------------------------------------------- This PTF adds an online-changeable subsystem parameter in DSN6SPRM called REORG_PART_SORT_NPSI that can be used to specify 1 the default method of building a non-partitioned secondary index (NPSI) during REORG TABLESPACE PART. This setting will be used when the SORTNPSI keyword is not provided in the utility control statement. The SORTNPSI keyword specifies whether REORG TABLESPACE PART should decide to sort all keys of a NPSI and how to make that decision. The setting is ignored for a REORG which is not part-level or a REORG with no NPSIs. Valid settings for this parameter are: * AUTO: Specifies that if sorting all keys of the NPSI(s) improves the elapsed time and CPU performance, all keys are sorted. * YES : Specifies that if sorting all keys of the NPSI(s) improves the elapsed time, all keys are sorted. * NO : Specifies that only keys of the NPSI(s) that are in the scope of the REORG are sorted. => This is the default setting 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 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 REORG_PART_SORT_NPSI=, where is AUTO, 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 REORG_PART_SORT_NPSI here, the value will be set to the default of NO 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 ---------------------------------------------------------------- 1 ==> This action is required for all customers This PTF adds an entry for REORG_PART_SORT_NPSI to the CLIST default input members 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: REORG_PART_SORT_NPSI CHARR M AUTO YES$ Change to the value you specified for REORG_PART_SORT_NPSI in step (2), above. If you do not add REORG_PART_SORT_NPSI to a DSNTIDxx member, the DB2 installation CLIST will assume REORG_PART_SORT_NPSI=NO when run with that member as input. ACTION: APAR PM54727 has corrected an issue where REORG REBALANCE on a partitioned table space with an editproc defined can result in corrupted limit key values in the DB2 catalog and directory. In the event that the above limit key corruption has occurred, user can repair the catalog/directory by manually altering the limit keys to the correct value on the affected table space / partitions, and then run a REORG TABLESPACE utility to remove the restrictive REORP status. ACTION: Action for PM53254: The PTF of PM53254 adds a new system parameter called REORG_IGNORE_FREESPACE, which specifies whether the REORG TABLESPACE utility should ignore the PCTFREE and FREEPAGE values when reloading data rows into a Partition By Growth (PBG) table space in the following circumstances: - When reorganizing a subset of the PBG partition(s) - When the table in the PBG table space has LOB column(s) Valid settings for REORG_IGNORE_FREESPACE are NO and YES. The default is NO, meaning that the PCTFREE and FREEPAGE values will be honored by the REORG TABLESPACE utility. To incorporate this fix the DB2 initialization parameter module, DSNZPARM, will need to be reassembled and re-linked by running the DB2 install clist DSNTINST using UPDATE mode. Insure that the output sample library name specified in panel DSNTIPT is not the same as an existing library name from a previous execution of the DSNTINST clist as the clist processing will delete all members delete all members of the data set name specified. Note: Customers who receive return code 8 and message "ASMA939U Unable to load external function module - DSNTIXL" when applying this PTF need to refer to Info APAR II13979. If you have already installed or migrated to this release of 1 DB2, you need to take the following actions after applying this PTF: (1) Optional: Update your DB2 subsystem parameter (DSNZPxxx) modules: * Add the keyword parameter REORG_IGNORE_FREESPACE=, where is either NO or YES (NO is recommended) to the invocation of the DSN6SPRM macro in your customized version of the installation job DSNTIJUZ. Make sure to add a continuation character in column 72 if needed. If you omit adding REORG_IGNORE_FREESPACE here, the value will be set to the default of NO when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified, to assemble and link the load module. * After the job completes, you must either use the SET SYSPARM command or stop and start DB2 for the change to take effect. (2) Required: Update your private copies of the CLIST defaults (DSNTIDxx) member: This PTF adds an entry for REORG_IGNORE_FREESPACE to the CLIST default input member, DSNTIDXA, in the SDSNSAMP target library. You need to add this entry to all private copies of your CLIST output (DSNTIDxx) member for DB2. In each such copy, add the following line: REORG_IGNORE_FREESPACE CHAR M NO YES where is the value you specified for REORG_IGNORE_FREESPACE when you modified DSNTIJUZ in step (1), above. Specify NO for if you bypassed step (1). (3) Required: Update customized copies of installation CLIST member DSNTINST: 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. ACTION: *** Action for PM47659 *** This APAR has changed the UNLOAD utility to utilize the RUNSTATS NPAGES statistic from SYSIBM.SYSTABLES to estimate the space needed for the SYSREC data set. A RUNSTATS against the target table space is recommended prior to the UNLOAD to ensure the accurate estimation for space requirement. ACTION: The PTF for APAR PM47356 has modified the REORG TABLESPACE utility to issue the following message and end with RC8 when REORG TABLESPACE SORTDATA NO is run against a non-Partition- By-Growth (non-PBG) partitioned table space in REORG-PENDING (REORP). A REORG TABLESPACE SORTDATA YES is required to remove the REORP state. 1 MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH 'TABLE SPACE IN REORG PENDING' COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIONX2 PM61976 DSNIOST2 PM61976 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61976 DSNIONX2 DSNIOST2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFUDRD DSNIONX2 DSNIOST2 DSNIRLPG DSNISRTI DSNTXAZP DSNUCINM DSNUCINT DSNUCLGR DSNUCRUL DSNUGPPM DSNUGPRS DSNUGPRT DSNUGRST DSNUKINM DSNUKINT DSNUKIUL DSNUKSRI DSNUKXCH DSNUMSGD DSNURBXA DSNURBXD DSNURBXE DSNURFBR DSNURFIT DSNURILD DSNURLXL DSNURORG DSNURPCT DSNURPIB DSNURPLD DSNURPLI DSNURPPL DSNURPRD DSNURPTB DSNURPUI DSNURSCN DSNURSWD DSNURULN DSNURWBF DSNURWI 1 DSNURWIK DSNUSITS DSNUSTBL DSNUULJA DSNUULXA DSNWZIFA MACROS DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSN6SPRM LISTEND UK79447 COVER LETTER END UK79502 COVER LETTER START PROBLEM DESCRIPTION(S): PM61898 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: When running online REORG, the console * * message msgDSNP007I for extend error * * RC00D70011 on shadow page set seems * * unnecessary. * **************************************************************** * RECOMMENDATION: * **************************************************************** After PM18390, customer requested to furthur suppress console msgDSNP007I for the extend error RC00D70011 on shadow page set during online REORG. The code is changed to suppress msgDSNP007I RC00D70011 on extending a shadow page set. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61898 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNPXTN0 PM61898 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61898 DSNPXTN0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNPXTN0 1 LISTEND UK79502 COVER LETTER END UK79505 COVER LETTER START PROBLEM DESCRIPTION(S): PM62673 - **************************************************************** * USERS AFFECTED: All users of CHECK DATA on a hash table in * * a PBG table space where the table has a * * LOB column. * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA utility erroneously reports * * missing entries in AUX index for a LOB * * table space * **************************************************************** * RECOMMENDATION: * **************************************************************** When CHECK DATA processes a row in a table with a LOB column, it needs to know the partition number of the row so that it can locate the correct auxiliary index for the LOB data. For rows in a PBG table space that are overflow rows, the row may reside in a different partition from the pointer subrecord. The LOB table space is associated with the partition of the overflow row. When processing a hash table in a PBG table space, CHECK DATA was using the partition number of the pointer subrecord instead of the partition number of the overflow row to try to locate the LOB data. Code is changed such that CHECK DATA uses the partition number of the overflow record to find the auxiliary index associated with the LOB table space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62673 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIACCH PM62673 DSNIOST2 PM62673 DSNIRFNX PM62673 DSNUKSCT PM62673 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62673 DSNIACCH DSNIOST2 DSNIRFNX DSNUKSCT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIACCH DSNIOST2 DSNIRFNX DSNUKSCT LISTEND UK79505 COVER LETTER END 1 UK79551 COVER LETTER START PROBLEM DESCRIPTION(S): PM62565 - **************************************************************** * USERS AFFECTED: All DB2 Users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIBHRE * * ERQUAL500E during RECOVER * * log-apply process. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the COPY utility was running concurrently with INSERT, UPDATE or DELETE transactions (DML), the COPY utility turned off the dirty bit on the page that had been copied. Later, the DML transaction rolled back the changes and did not turn on the dirty bit on the page and caused COPY utility not to recognize the page being changed again since the last full image copy. As a result, the modified page was not picked up by the incremental copy and this caused data inconsistencies. DB2 log-apply undo process is modified to make sure the space map page is updated properly so the page's dirty bit is turned on to reflect any data changes that occurred. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62565 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 PM62565 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62565 DSNIBHUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBHUN LISTEND UK79551 COVER LETTER END UK79559 COVER LETTER START PROBLEM DESCRIPTION(S): PM61906 - **************************************************************** * USERS AFFECTED: All DB2 V9 V10 users when running query * * COUNT ( DISTINCT (COL) ) and parallelism * * enabled. * **************************************************************** 1 * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXESX2 may * * occur when running query with * * COUNT ( DISTINCT (COL) ) and * * parallelism enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 at DSNXESX2 may occur when running query with COUNT ( DISTINCT (COL) ) and parallelism enabled. The following query is an example of this case. SET CURRENT DEGREE = 'ANY'; SELECT C1, COUNT(DISTINCT (C2)) FROM T1 GROUP BY C1; The bindtime code in DB2 is modified to correct the failing condition. Additional keyword: SQLPARALLELISM SQLPARA SQLSETFN SQLDISTINCT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61906 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM61906: See PM61906 APAR/PTF text for additional information about why a REBIND is necessary. PM61906 corrects a problem of ABEND04E at DSNXESX2 when running query with COUNT ( DISTINCT (COL) ) and parallelism 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 DSNXOSSF PM61906 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61906 DSNXOSSF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSSF LISTEND UK79559 COVER LETTER END UK79619 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM64166 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of UNLOAD utility with file reference * * variables (FRV). * **************************************************************** * PROBLEM DESCRIPTION: 1. UNLOAD LOB/XML data with FRV * * encountered multiple ABENDSE37 RC4 * * due to a full FRV data set and a high * * MAXERR value. UNLOAD issued MSGDSNU283I * * with SQLCODE452 for each failed record * * until the MAXERR value was reached. The * * multiple errors led to abends: * * ABEND04E RC00E40020 * * ABENDSB14 RC8 * * ABEND016 RC4 * * Subsequently, DB2 might terminate with * * MSGDSNV086E RC00E80100. * * 2. MSGDSNU283I specifies LOB ERROR * * when the error is for an XML column. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** An UNLOAD utility with MAXERR set to a high value was unloading LOB or XML data with an FRV (File Reference Variable). When the output LOB/XML data set was full, UNLOAD continued attempting to write more members to that data set because MAXERR was set to a high value. This resulted in multiple ABENDSE37 RC4 abends and MSGDSNU283I messages being issued. UNLOAD then issued ABEND04E RC00E40020 and ABENDSB14 RC8 and finally DB2 abnormally terminated with ABEND016 RC4 and ABEND04F. A second problem was found where 'LOB ERROR' was stated in the MSGDSNU283I message but the column was actually an XML column. UNLOAD code has been changed to indicate the FRV data set is full and will ignore the MAXERR value and terminate with RC8. UNLOAD code has been changed to correctly issue XML ERROR in MSGDSNU283I when the column type is XML during UNLOAD XML data with FRV. After the application of this APAR, the ABENDSE37 RC4 and ABENDSB14 RC8 may still show up once on the console at the end of the UNLOAD job. This APAR also requires a documentation change in Utility Guide and Reference: Changed option for utility UNLOAD: MAXERR integer Specifies the maximum number of records in error that are to be allowed; the unloading process terminates when this value is reached. integer 1 Specifies the number of records in error that are allowed. When the error count reaches this number, the UNLOAD utility issues message DSNU1219 and terminates with return code 8. The default value is 1, which indicates that UNLOAD stops when the first error is encountered. If you specify 0 or any negative number, execution continues regardless of the number of records that are in error. If multiple table spaces are being processed, the number of records in error is counted for each table space. If the LIST option is used, you can add OPTION utility control statement (EVENT option with ITEMERROR) before the UNLOAD statement to specify that the table space in error is to be skipped and the subsequent table spaces are to be processed. | MAXERR option would be ignored when getting message DSNU283I | with SQLCODE -452 REASON CODE 7 during UNLOAD LOB or XML data | with FRV, and the UNLOAD would be terminated with | return code 8. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64166 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM64166 introduces the following changes to externals: Changed option for utility UNLOAD: MAXERR integer Specifies the maximum number of records in error that are to be allowed; the unloading process terminates when this value is reached. integer Specifies the number of records in error that are allowed. When the error count reaches this number, the UNLOAD utility issues message DSNU1219 and terminates with return code 8. The default value is 1, which indicates that UNLOAD stops when the first error is encountered. If you specify 0 or any negative number, execution continues regardless of the number of records that are in error. If multiple table spaces are being processed, the number of records in error is counted for each table space. If the LIST option is used, you can add OPTION utility control statement (EVENT option with ITEMERROR) before the UNLOAD statement to specify that the table space in error is to be skipped and the subsequent table spaces are to be processed. | MAXERR option would be ignored when getting message DSNU283I | with SQLCODE -452 REASON CODE 7 during UNLOAD LOB or XML data 1 | with FRV, and the UNLOAD would be terminated with | return code 8. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOLFRV PM64166 DSNUULVA PM64166 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64166 DSNOLFRV DSNUULVA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOLFRV DSNUULVA LISTEND UK79619 COVER LETTER END UK79633 COVER LETTER START PROBLEM DESCRIPTION(S): PM63439 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: A DB2 subsystem may hang with threads * * looping in CSECTs DSNVSRBW and * * DSNSTKGG waiting for 64-bit stack * * segments to be allocated. Systems * * with few available CPs are most * * susceptible to this condition. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the 64-bit stack cache is exhausted, threads may enter a timed wait while a system task is posted to allocate additional segments. If too many SRBs exit this timed wait and then are made dispatchable, it is possible the system thread stack allocation task is never eligible to be dispatched. The timed wait logic has been modified to increase the wait time if no stack has been allocated after several timed wait events have completed. This should ensure that even on systems with limited processing capacity, the stack allocation thread should be dispatched and able to complete stack allocation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63439 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNSTKGG PM63439 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM63439 DSNSTKGG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNSTKGG LISTEND UK79633 COVER LETTER END UK79635 COVER LETTER START PROBLEM DESCRIPTION(S): PM64012 - **************************************************************** * USERS AFFECTED: DB2 for z/OS version 9 and version 10 users * * of Utility REORG KEEPDICTIONARY against * * compressed table space when system parameter * * HONOR_KEEPDICTIONARY is turned on. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIMOFR * * ERQUAL5006. * **************************************************************** * RECOMMENDATION: * **************************************************************** During the UNLOAD phase of REORG KEEPDICTIONARY that converts the rows in a compressed table space from Basic Row Format (BRF) to Reordered Row Format (RRF), and system parameter HONOR_KEEPDICTIONARY is turned on, DB2 failed to correctly determine the location of the end of the row. As a result, it appeared that the row was missing column values,and DB2 attemped to determine a default value for a column that did not have a default value. As the consequence, Abend DSNIMOFR:5006 happened. DB2 code has been fixed to correctly determine the location of the end of the row. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64012 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIMOFR PM64012 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64012 DSNIMOFR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIMOFR LISTEND UK79635 COVER LETTER END 1UK79652 COVER LETTER START PROBLEM DESCRIPTION(S): PM65596 - **************************************************************** * USERS AFFECTED: All users of external stored procedure or * * user defined functions. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 at * * DSNXGRDS . DSNXERD +0210 * * when processing an SQL request from * * a stored procedure or user defined * * function. * **************************************************************** * RECOMMENDATION: * **************************************************************** When processing a request for an SQL statement from inside an external stored procedure or user defined package, DB2 incorrectly took a path related to WLM execution delay monitoring services, DB2 encountered the subject abend because this code path is not valid while executing under a stored procedure or user defined function. DB2 code has been changed to avoid taking the path related to WLM execution delay monitoring services while executing SQL under external stored procedure and user defined functions. . ADDITIONAL KEYWORDS: sqludf sqlscalarudf sqlexternalsqlpl sqlsp sqlstoredproc PB Performance Block DBPB WLM IWWMRELP IWWMRELA Workload Manager Relate Unrelate COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65596 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXERD PM65596 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65596 DSNXERD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXERD LISTEND UK79652 COVER LETTER END UK79654 COVER LETTER START PROBLEM DESCRIPTION(S): PM65927 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 10 for z/OS only. * 1 **************************************************************** * PROBLEM DESCRIPTION: Null characters, rather than blank * * characters, may be displayed for the * * PRDID value in the DSNL200I Display * * Location command message. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 for z/OS enhanced the information gathered and displayed about remote locations that the subsystem had accessed. Under certain circumstances where DB2 is acting as a requester to a DB2 data sharing group, the Product-specific Identifier (PRDID) will not be known. In this case, the -DISPLAY LOCATION command will incorrectly report binary zeroes instead of blanks. DB2 10 for z/OS -DISPLAY LOCATION command processing has been changed to ensure that blank characters are now displayed for the PRDID valid, in message DSNL200I, when no actual PRDID has yet been received from a remote location. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65927 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLDL PM65927 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65927 DSNLDL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLDL LISTEND UK79654 COVER LETTER END UK79681 COVER LETTER START PROBLEM DESCRIPTION(S): PM64538 - **************************************************************** * USERS AFFECTED: DB2 users of static SQL EXPLAIN STMTCACHE * **************************************************************** * PROBLEM DESCRIPTION: User issued static EXPLAIN STMTCACHE * * STMTID which failed with SQLCODE20248 , * * even though the user's authID had * * SYSADM or SQLADM authorization and * * the dynamic statement with specified * * STMTID does exist in the Dynamic * * Statement Cache. * * * * This failure may also occur for * * static EXPLAIN STMTCACHE STMTTOKEN . * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** User issued static SQL EXPLAIN STMTCACHE STMTID to explain/ retrieve a specific dynamic statement with STMTID n/:host-var from the DB2 Dynamic Statement Cache (DSC) into the user's target DSN_STATEMENT_CACHE_TABLE. The authorization IDs of the process issuing the static EXPLAIN had either SYSADM, SQLADM, or DBADM authorization and the dynamic stmt with the specified STMTID does exist in the DSC, however, DB2 failed the static EXPLAIN STMTCACHE STMTID request with SQLCODE20248 and the following SQLCA contents: . SQLCODE : -20248 SQLERRM : n.01 (where 'n'= specified STMTID 01 = reason token) SQLERRP : DSNXEXPL (DB2 csect) SQLERRD : -30 (DSNXEXPL error location) . Reason token '01' means that the cached dynamic statement with the STMTID n was found in the DSC, but the user does not have the proper authorization to issue EXPLAIN STMTCACHE for it. . DB2 Development determined that DB2 invalidly failed the static EXPLAIN STMTCACHE request, and that the runner's authIDs of the application process did have the correct authorization for issuing the static EXPLAIN STMTCACHE STMTID request. . The same failure can occur for a static SQL EXPLAIN STMTCACHE STMTTOKEN statement. . For static SQL EXPLAIN STMTCACHE ALL stmt, instead of SQLCODE -20248 the failure is that DB2 may not explain/retrieve all dyn cached statements from the DSC, but instead retrieves only those dynamic statements that were previously cached using the same runner's authID that is being used to run the static SQL EXPLAIN STMTCACHE ALL statement. The runner's authIDs of the process for the static EXPLAIN had the proper authorization (either SYSADM , SQLADM , or DBADM), so for static SQL EXPLAIN STMTCACHE ALL, DB2 should have explained/retrieved all currently cached dynamic statements. . The failures previously described do not occur for "dynamic" form of EXPLAIN STMTCACHE STMTID / STMTTOKEN / ALL . DB2 code for handling static SQL EXPLAIN STMTCACHE was corrected to not fail the static EXPLAIN STMTCACHE statement when the runner's authID has the proper authorization. . Additional search keywords: SQLEXPLAIN SQLDYNSTMTCACHE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64538 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 DSNXEXPL PM64538 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64538 DSNXEXPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEXPL LISTEND UK79681 COVER LETTER END UK79701 COVER LETTER START PROBLEM DESCRIPTION(S): PM65236 - **************************************************************** * USERS AFFECTED: DB2 users of bind option RELEASE(DEALLOCATE) * * with searched SQL UPDATE or DELETE statement * **************************************************************** * PROBLEM DESCRIPTION: An application program bound with bind * * option RELEASE(DEALLOCATE) and * * containing a program loop that issued * * the same 'searched' SQL UPDATE / DELETE * * statement followed by COMMIT for 1000s * * of iterations, eventually hit * * the following or similar out-of-storage * * condition for a long running thread: * * . * * AB04E RC00E20016 IN DSNSVSTK +0656 * * . * **************************************************************** * RECOMMENDATION: * **************************************************************** An application program repeatedly issued the same 'searched' SQL UPDATE / DELETE statement followed by COMMIT within a program loop for 1000s of iterations. Note that for 'searched' UPDATE / DELETE , the WHERE predicate does NOT specify a cursor name. The following is a simplified example of the scenario described: . DO I = 1 to 5000; . EXEC SQL UPDATE TABLE1 SET COL1 = COL1 + 1 WHERE COL2 = 123 AND COL3 < 9999; . EXEC SQL COMMIT; . END; . The application program was bound with bind option RELEASE ( DEALLOCATE ). The application program was in a long- running thread that eventually hit the following or similar out-of-storage condition: 1 . ABEND04E RC00E20016 in DSNSVSTK at offset 0656 After reviewing the storage pools in the dump, IBM saw that this DB2 thread's ADMF Agent Local Pools ( AGL VL and AGL 31 ) were unusually large. Further examination of the storage segments of these two AGL pools showed an excessive amount of DB2 control blocks with eyecatchers CU and SMSB . . IBM DB2 Development determined that the storage leaks for these two blocks were the result of DB2 not properly reusing the CU block (aka CUB) after a COMMIT for repeated execution of the same searched SQL UPDATE / DELETE when bind option RELEASE(DEALLOCATE) is in effect. RELEASE(DEALLOCATE) behavior means that DB2 should not free some program and statement-level blocks at COMMIT, but instead keep them and reuse them for next execution of the same statement or program following the COMMIT. In this CUB and SMSB leak case, DB2 did not properly reuse these blocks after COMMIT for the 'searched' UPDATE and DELETE , but instead allocated new CUB and SMSB blocks for these stmts following the COMMIT. This then resulted in the excessive number of these blocks in the AGL 31 and AGL VL pools , followed by the 'DB2 out-of-storage' abend/s. . Other out-of-storage abends reported for the same pblm are -- ABEND04E RC00E20003 DSNGEPLC . DSNSVBK +061A ABEND04E RC00E20003 DSNB1DRN . DSNSVBK +061A ABEND04E RC00E20003 DSNICUBD . DSNSVBK +061A ABEND04E RC00E20013 DSNSLD1 . DSNSGMN +05E6 . This problem does NOT occur for the 'positioned' UPDATE/DELETE . For a 'positioned' UPDATE/DELETE , the WHERE predicate specifies a cursor name. . To circumvent this storage leak, REBIND the application as RELEASE(COMMIT) so that the storage for the DB2 thread's CUB and SMSB blocks are freed at the COMMIT. . DB2 COMMIT and Thread-reuse/NEWUSER cleanup code for searched UPDATE/DELETE and MERGE statements was modified to honor the RELEASE(DEALLOCATE) behavior semantic for the DB2 internal CUB block that is used for the actual update/delete/merge operation. . Additional search keywords: SQLSTORAGE SQLLEAK GROWTH SQLUPDATE SQLDELETE SQLMERGE OFFSET0656 OFFSET061A OFFSET05E6 OFFSET COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65236 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECLF PM65236 DSNXECLN PM65236 1 DSNXECW PM65236 DSNXECWA PM65236 DSNXECWU PM65236 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65236 DSNXECLF DSNXECLN DSNXECW DSNXECWA DSNXECWU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECLF DSNXECLN DSNXECW DSNXECWA DSNXECWU LISTEND UK79701 COVER LETTER END UK79706 COVER LETTER START PROBLEM DESCRIPTION(S): PM60248 - **************************************************************** * USERS AFFECTED: DB2 data sharing users, with table spaces or * * indexes with DSSIZE or PIECESIZE greater * * than 64GB. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C20263 in DSNB5PCO. * **************************************************************** * RECOMMENDATION: * **************************************************************** In data sharing, a page in the group buffer pool is tracked by a resource name which includes a 3-byte relative page number (i.e. page number within the partition). For a table space or index with a 4K page size and a DSSIZE or PIECESIZE greater than 64GB, or for a table space or index with an 8K page size and a DSSIZE or PIECESIZE greater than 128GB, the relative page number can become too large to fit in 3 bytes. Therefore a page beyond the 64GB or 128GB boundary will be written to the group buffer pool with a resource name which does not match its internal page number. This will result in an ABEND04E RC00C20263 in DSNB5PCO when DB2 attempts to cast that page out to DASD. DB2 has been modified to handle objects which may exceed a 3-byte relative page number, by using a 4-byte page number in the group buffer pool resource name and in the page P-lock resource name. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60248 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 DSNB1CNE PM60248 DSNB1DUP PM60248 DSNB1FBS PM60248 DSNB1GRC PM60248 DSNB1GWB PM60248 DSNB1NOT PM60248 DSNB1OPP PM60248 DSNB1PCO PM60248 DSNB1PER PM60248 DSNB1PLK PM60248 DSNB1PPG PM60248 DSNB1RWI PM60248 DSNB1ULT PM60248 DSNB5BPL PM60248 DSNB5CMX PM60248 DSNB5DEL PM60248 DSNB5GGP PM60248 DSNB5PCI PM60248 DSNB5PCO PM60248 DSNB5PGB PM60248 DSNB5SCO PM60248 DSNB5SC1 PM60248 DSNB5SC2 PM60248 DSNB5WCS PM60248 DSNDQW00 PM60248 DSNDQW02 PM60248 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60248 DSNB1CNE DSNB1DUP DSNB1FBS DSNB1GRC DSNB1GWB DSNB1NOT DSNB1OPP DSNB1PCO DSNB1PER DSNB1PLK DSNB1PPG DSNB1RWI DSNB1ULT DSNB5BPL DSNB5CMX DSNB5DEL DSNB5GGP DSNB5PCI DSNB5PCO DSNB5PGB DSNB5SCO DSNB5SC1 DSNB5SC2 DSNB5WCS DSNDQW00 DSNDQW02 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CNE DSNB1DUP DSNB1FBS DSNB1GRC DSNB1GWB DSNB1NOT DSNB1OPP DSNB1PCO DSNB1PER DSNB1PLK DSNB1PPG DSNB1RWI DSNB1ULT DSNB5BPL DSNB5CMX DSNB5DEL DSNB5GGP DSNB5PCI DSNB5PCO 1 DSNB5PGB DSNB5SCO DSNB5SC1 DSNB5SC2 DSNB5WCS MACROS DSNDQW00 DSNDQW02 LISTEND UK79706 COVER LETTER END UK79707 COVER LETTER START PROBLEM DESCRIPTION(S): PM61026 - **************************************************************** * USERS AFFECTED: All DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: After MSGDSNB325I is issued for a * * secondary group buffer pool, once * * the secondary group buffer pool size * * is altered to a larger size, * * MSGDSNB327I may be missing. * **************************************************************** * RECOMMENDATION: * **************************************************************** When MSGDSNB325I is issued for a secondary group buffer pool to indicate a critical shortage of space, MSGDSNB327I may be missing after the space shortage is resolved due to insufficient space tracking information. DB2 has been fixed to keep more group buffer pool space tracking information in order to issue MSGDSNB327I message correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61026 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CNE PM61026 DSNB1GBR PM61026 DSNB1GD1 PM61026 DSNB1PMT PM61026 DSNB5SCO PM61026 DSNB5STS PM61026 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61026 DSNB1CNE DSNB1GBR DSNB1GD1 DSNB1PMT DSNB5SCO DSNB5STS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CNE DSNB1GBR 1 DSNB1GD1 DSNB1PMT DSNB5SCO DSNB5STS LISTEND UK79707 COVER LETTER END UK79718 COVER LETTER START PROBLEM DESCRIPTION(S): PM62914 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XMLMODIFY * * function * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNOWRT:M240 may * * occur when partially UPDATE a * * validated XML document with XMLMODIFY * * function in an XML column without type * * modifier. * **************************************************************** * RECOMMENDATION: * **************************************************************** When updating a validated XML document, if the XML column does not have a type modifier, DB2 does not validate the document after update and marks it as not validated. As in the following example, the XML column COL1 is created without type modifier, then one row is inserted with DSN_XMLVALIDATE for schema validation, and XMLMODIFY is applied on that validated document. In this case, XMLMODIFY will mark the updated document as not validated. Logic error in the XMLMODIFY function causes abend ABEND04E RC00E70005 DSNNOWRT:M240 to occur. Example: CREATE TABLE T1 (ID INTEGER, COL1 XML); INSERT INTO T1 (ID, COL1) VALUES (1, DSN_XMLVALIDATE(:xmlhv, 'SYSXSR.MYSCHEMA')); UPDATE T1 SET COL1 = XMLMODIFY('delete nodes /a/b') WHERE ID = 1; DB2 code has been modified so that ABEND04E RC00E70005 DSNNOWRT:M240 will not occur when marking the updated XML document as not validated. Additional keywords: XMLALL XMLUPDATE XMLSCHEMA COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62914 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 DSNNOAPU PM62914 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62914 DSNNOAPU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOAPU LISTEND UK79718 COVER LETTER END UK79719 COVER LETTER START PROBLEM DESCRIPTION(S): PM61991 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users. * **************************************************************** * PROBLEM DESCRIPTION: Message DSNI031I shows incorrect * * statement number when the correct * * number is greater than 32767. * **************************************************************** * RECOMMENDATION: * **************************************************************** Message DSNI031I shows incorrect statement number when the correct number is greater than 32767 because the variable for the statement number is incorrectly defined. DB2 code was changed to correctly defined the variable for the statement number. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61991 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNILKES PM61991 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61991 DSNILKES THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILKES LISTEND UK79719 COVER LETTER END UK79723 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM61290 - **************************************************************** * USERS AFFECTED: All DB2 V10 Compatibility Mode users of the * * -ACCESS, -DISPLAY, -START, -STOP * * DB(DSNDB01) commands. * **************************************************************** * PROBLEM DESCRIPTION: The -ACCESS, -DISPLAY, -START, -STOP * * DB(DSNDB01) commands did not correctly * * process all DSNDB01 objects in V10 * * Compatibility Mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** In V10 Compatibility Mode the -ACCESS, -DISPLAY, -START, -STOP DB(DSNDB01) commands incorrectly attempted to process V10 New Funcion only DSNDB01 objects and when not located the commands would terminate and fail to process any subsequent DSNDB01 objects. The V10 DSNDB01 catalog object lookup was corrected to return V10 Compatibility Mode objects while in V10 Compatibility Mode and V10 New Function Mode objects while in V10 New Function Mode. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61290 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTDCAT PM61290 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61290 DSNTDCAT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTDCAT LISTEND UK79723 COVER LETTER END UK79729 COVER LETTER START PROBLEM DESCRIPTION(S): PM62106 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of File * * Reference Variables (FRV). * **************************************************************** * PROBLEM DESCRIPTION: An SQLCODE -452 is issued unexpectedly * * from DSNOLFRV, location 340, when the * * BSAM file name in a File Reference * * Variable contains a special character * * '-'. This character is allowed for * * valid BSAM file names in a File * 1 * Reference Variable. * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQLCODE -452 is issued unexpectedly from DSNOLFRV, location 340, when the BSAM file name in a File Reference Variable contains a special character '-'. This character is allowed for valid BSAM file names in a File Reference Variable. The following example helps to illustrate the problem. 1. Create a Table with a LOB column and populate it. CREATE TABLE T1 ( C1 INT, C2 CLOB(1K) ); INSERT INTO T1 VALUES(1,'12'); INSERT INTO T1 VALUES(2,'23'); INSERT INTO T1 VALUES(3,'34'); 2. UNLOAD the Table to a File Reference Variable that contains a BSAM file name with a special character '-'. TEMPLATE DCLOBVC3 UNIT(SYSDA) DISP(NEW,CATLG,CATLG) DSN(DK15701.UNL-AD1) DSNTYPE(PDS) DIR(15) VOLUMES(SCR03) SPACE(1,1) TRK UNLOAD DATA FROM TABLE T1 (C1 INT, C2 VARCHAR(255) CLOBF DCLOBVC3) 3. An SQLCODE -452 (SQLCODE452) will result as mentioned above. The code in DB2 has been modified to allow the special character '-' to be contained in a BSAM file name for a File Reference Variable when performing an UNLOAD. This will prevent the SQLCODE -452 from being issued. Additional Keywords: SQLCODE452 SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62106 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOLFRV PM62106 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62106 DSNOLFRV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNOLFRV LISTEND UK79729 COVER LETTER END UK79738 COVER LETTER START PROBLEM DESCRIPTION(S): PM41083 - **************************************************************** * 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 issues are reported: * * * * 1. DB2 10 for z/OS does not support * * the JDBC 4.1 metadata API * * getPseudoColumns. * * * * Additionally, the DB2 supplied * * Database Metadata stored procedure * * SYSIBM.SQLCOLUMNS fails to return * * the correct result set to JDBC 4.1. * * * * 2. The following DB2 supplied Database * * Metadata stored procedures may * * return SQLCODE -330 with reason * * code 16. * * -SYSIBM.SQLCOLUMNS * * -SYSIBM.SQLPROCEDURES * * -SYSIBM.SQLTABLES * **************************************************************** * RECOMMENDATION: Apply PTF * **************************************************************** The following issues are reported: 1. JDBC 4.1 introduced a new getPseudoColumnsmetadata API but DB2 10 for z/OS lacks an associated DB2 supplied Database Metadata stored procedure to support this JDBC 4.1 feature. Additionally, in JDBC 4.1, the metadata API getColumns is changed in two ways. The result column SCOPE_CATLOG is changed to SCOPE_CATALOG and a new result column IS_GENERATEDCOLUMN is added. The DB2 supplied Database Metadata stored procedure SYSIBM.SQLCOLUMNS fails to return the correct result sets to JDBC 4.1 due to this new change. 2. The following DB2 supplied Database Metadata stored procedures return SQLCODE -330 with reason code 16 when the 254th byte of the REMARKS column falls between a double byte character representation, thus the stored procedures truncate the REMARKS column at the 254th byte. - SYSIBM.SQLCOLUMNS 1 - SYSIBM.SQLPROCEDURES - SYSIBM.SQLTABLES DB2 now provides a new DB2 supplied Database Metadata stored procedure SYSIBM.SQLPSEUDOCOLUMNS to be used by the JDBC metadata API. SYSIBM.SQLPseudoColumns(CatalogName varchar(128), SchemaName varchar(128), TableName varchar(128), ColumnsName varchar(128), Options varchar(4000)) The DB2 supplied Database Metadata stored procedure SYSIBM.SQLCOLUMNS is modified to tolerate the JDBC 4.1 changes. The following DB2 supplied Database Metadata stored procedures have been modified to return REMARKS as VARCHAR(762) when PATCH2=2 is specified in the OPTIONS parameter. SYSIBM.SQLCOLUMNS SYSIBM.SQLPROCEDURES SYSIBM.SQLTABLES 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 APAR: (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 and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU. (6) Run installation job DSNTIJRV to validate new objects (7) Refresh the WLM environment These actions are detailed below: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members * This action is required for all V10 customers This APAR 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 APAR modifies the DB2 installation panels DSNTIPRA and DSNTIPRK in the prefix.SDSNSPFP target library. If you keep the DB2 installation panels in a different library then after applying this APAR, you need to copy the updated panels to that library. ---------------------------------------------------------------- 1 (3) Update customized copies of installation job DSNTIJRT * This action is required for all V10 customers This APAR modifies installation job DSNTIJRT in the prefix.SDSNSAMP target library. After you apply this APAR, you need to add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSIBM.SQLPSEUDOCOLUMNS WLMENV(DSNWLM_GENERAL) GRANTTO(PUBLIC) Notes: (a) Always leave a blank line between each configuration control statement (b) Inspect each of the new configuration control statement and if required: - Change the WLMENV parameter settings to the names of the WLM environment you use to run these routines at your site - Change the GRANTTO parameter setting to the authorization IDs that need access to the routines - Optionally add the PKGOWNER option ---------------------------------------------------------------- (4) Update private copies of the DSNTIDxx CLIST input member * This action is required for all V10 customers This APAR adds entries to store values entered into new fields on installation panel DSNTIPRK: - RTK16ACL: GRANT EXECUTE setting for SYSIBM.SQLPSEUDOCOLUMNS - RTK16PKO: PACKAGE OWNER setting for SYSIBM.SQLPSEUDOCOLUMNS - RTK16WLM: WLM ENV NAME setting for SYSIBM.SQLPSEUDOCOLUMNS 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: RTK16ACL CHAR M NONE NONE PUBLIC RTK16PKO CHAR M NONE NONE NULL RTK16WLM 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 and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU. * This action is required for all V10 customers After you have completed the above actions, run your updated copy of job DSNTIJRT with MODE(INSTALL) to install and grant access to the new routine, SYSIBM.SQLPSEUDOCOLUMNS, and the new created global temporary table SYSIBM.SQTPSEUDOCOLUMNS, 1 and to modify the existing CGTT, SYSIBM.SQTCOLUMNS, and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU. 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 SYSIBM.SQLPSEUDOCOLUMNS. ---------------------------------------------------------------- (7) Refresh the WLM environment * This action is required for all V10 customers 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.SQLCOLUMNS, SYSIBM.SQLPROCEDURES and SYSIBM.SQLTABLES are running. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM41083 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM41083 (V10): See PTF cover letter for additional information. This PTF adds a new DB2-supplied stored procedure called SYSIBM.SQLPSEUDOCOLUMNS that returns a result set having a description of the pseudo or hidden columns available in a given table within a specified catalog and schema. This PTF also adds a related created global temporary table (CGTT) called SYSIBM.SQTPSEUDOCOLUMNS. This PTF modifies an existing CGTT called SYSIBM.SQTCOLUMNS: It changes the REMARKS column from VARCHAR(254) to VARCHAR(762) and adds a new column, IS_GENERATEDCOLUMN of VARCHAR(128). Finally, this PTF updates the following DB2-supplied Database Metadata stored procedures: SYSIBM.SQLCOLUMNS (DSNACOLU) SYSIBM.SQLPROCEDURES (DSNAPRCU) SYSIBM.SQLTABLES (DSNATBLU) 1 **************************************************************** 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) 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 and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU (6) Run installation job DSNTIJRV to validate new objects (7) Refresh the WLM environment 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 DSNTIPRK 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 add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSIBM.SQLPSEUDOCOLUMNS WLMENV(DSNWLM_GENERAL) GRANTTO(PUBLIC) Notes: 1 (a) Always leave a blank line between each configuration control statement (b) Inspect each of the new configuration control statement and if required: - Change the WLMENV parameter settings to the names of the WLM environment you use to run these routines at your site - Change the GRANTTO parameter setting to the authorization IDs that need access to the routines - Optionally add the PKGOWNER option ---------------------------------------------------------------- (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 DSNTIPRK: - RTK16ACL: GRANT EXECUTE setting for SYSIBM.SQLPSEUDOCOLUMNS - RTK16PKO: PACKAGE OWNER setting for SYSIBM.SQLPSEUDOCOLUMNS - RTK16WLM: WLM ENV NAME setting for SYSIBM.SQLPSEUDOCOLUMNS 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: RTK16ACL CHAR M NONE NONE PUBLIC RTK16PKO CHAR M NONE NONE NULL RTK16WLM 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 and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU. ************************************************************ * This action is required for all V10 customers ************************************************************ After you have completed the above actions, run your updated copy of job DSNTIJRT with MODE(INSTALL) to install and grant access to the new routine, SYSIBM.SQLPSEUDOCOLUMNS, and the new created global temporary table SYSIBM.SQTPSEUDOCOLUMNS, and to modify the existing CGTT, SYSIBM.SQTCOLUMNS, and to rebind the DBRM DSNACOLU, DSNAPRCU and DSNATBLU. 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 1 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 SYSIBM.SQLPSEUDOCOLUMNS. ---------------------------------------------------------------- (7) Refresh the WLM environment ************************************************************ * This action is required for all V10 customers ************************************************************ 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.SQLCOLUMNS, SYSIBM.SQLPROCEDURES, SYSIBM.SQLPSEUDOCOLUMNS and SYSIBM.SQLTABLES are running. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@COLU PM41083 DSN@PCLU PM41083 DSN@PRCU PM41083 DSN@RIN PM41083 DSN@RVFY PM41083 DSN@TBLU PM41083 DSN@XAZP PM41083 DSNACOLU PM41083 DSNAPCLU PM41083 DSNAPRCU PM41083 DSNATBLU PM41083 DSNTESR PM41083 DSNTIDXA PM41083 DSNTIDXB PM41083 DSNTIJRT PM41083 DSNTINST PM41083 DSNTINSV PM41083 DSNTINS1 PM41083 DSNTIPRA PM41083 DSNTIPRK PM41083 DSNTRIN PM41083 DSNTRVFY PM41083 DSNTXAZP PM41083 HDBAA10J PM41083 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM41083 DSN@COLU DSN@PCLU DSN@PRCU DSN@RIN DSN@RVFY DSN@TBLU DSN@XAZP DSNACOLU DSNAPCLU DSNAPRCU DSNATBLU DSNTESR 1 DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRK DSNTRIN DSNTRVFY DSNTXAZP HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNACOLU DSNAPCLU DSNAPRCU DSNATBLU DSNTRIN DSNTRVFY DSNTXAZP MACROS DSN@COLU DSN@PCLU DSN@PRCU DSN@RIN DSN@RVFY DSN@TBLU DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRK LISTEND UK79738 COVER LETTER END UK79761 COVER LETTER START PROBLEM DESCRIPTION(S): PM63670 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DB2 Dynamic * * Statement Cache with trace IFCID 316 active * * or with trace monitor class 29 active * **************************************************************** * PROBLEM DESCRIPTION: During PREPARE of a dynamic statement * * for insertion into the DB2 Dynamic * * Statement Cache and trace IFCID 316 * * is active, the following abend occurred * * * * ABEND04E, RC00E70005 * * at DSNXGRDS . DSNXVTRS M420 * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 10 when IFCID 316 is active, DB2 traces certain information about a dynamic statement when that statement is 1 purged or removed from the DB2 Dynamic Statement Cache ( DSC ). . In this reported failure case, during the PREPARE of a new dynamic statement for insertion into the DSC, the DSC did not have space for this new dynamic stmt and DB2 had to LRU (Least Recently Used) remove/purge one or more cached dyn statements from the DSC to make room for this new dyn statement. During the purge process DB2 was building the IFCID 316 trace record for the dyn statement being removed, but certain IFCID316 information is optional and did not apply for this specific dyn statement so validly had no value. However, DB2 assumed this IFCID 316 field had a value and attempted to translate it into external format for the the IFCID 316 trace record, resulting in the reported ABEND04E during this translation process. . This abend does not occur if trace IFCID 316 is not active, also does not occur when using an IFI application to issue READS requests for IFCID 316 for cached statements active in the DSC. DB2 has been modified to verify that the optional IFCID 316 data has a value before trying to translate it into external format for the IFCID 316 trace built when purging cached statements from the Dynamic Statement Cache (DSC). . Additional keyword: IFCID316 IFCID0316 0316 SQLDYNSTMTCACHE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63670 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEIST PM63670 DSNXEUCS PM63670 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63670 DSNXEIST DSNXEUCS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEIST DSNXEUCS LISTEND UK79761 COVER LETTER END UK79770 COVER LETTER START PROBLEM DESCRIPTION(S): PM63979 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of UNLOAD with FROMCOPY/FROMCOPYDDN option. * **************************************************************** 1 * PROBLEM DESCRIPTION: Message spool flooded by MSGDSNU1239I * * and MSGDSNU1219I messages during an * * UNLOAD FROMCOPYDDN, and abended with * * ABENDS0C4 RC00000038 at DSNUULCA * * OFFSET7074 if MAXERR integer(>=2) was * * specified, and then the DB2 subsystem * * abended with ABEND04E RC00E20028 along * * with the message DSNV086E - DB2 * * ABNORMAL TERMINATION REASON=00F30801. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User procedures caused DSNU1239I - VERSION version-number OBDREC WAS NOT FOUND IN OBID object-id during an UNLOAD FROMCOPYDDN. This message along with DSNU1219I - THE NUMBER OF RECORDS IN ERROR REACHED THE LIMIT nnnn were issued too many times and flooded the message spool if no MAXERR specified or MAXERR 1. If MAXERR integer(>=2), the UNLOAD abended with ABEND0C4 RC38 at DSNUULCA + x'7074' on DB2 9 for z/OS and ABEND0C4 RC11 at DSNUULCA + x'3B4A' on DB2 10. It may lead to the DB2 subsystem abnormally terminated with ABEND04E RC00E20028 and MSGDSNV086E - DB2 ABNORMAL TERMINATION REASON=00F30801. This problem occurred because UNLOAD was not handling the return code correctly and issuing messages for every single record, including beyond the MAXERR value. UNLOAD code has been modified to correct the reported problems. And if MAXERR is 0 or greater than 2000, UNLOAD will now stop issuing the DSNU1239I message once 2000 of them have been issued and issue MSGDSNU1140I stating this fact but will still continue processing until MAXERR has been reached. 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 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. | Example 1: The LOAD utility issues message DSNU1140I after 2000 instances of any of the following messages: DSNU313I, 1 DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have triggered the suppressed message are still discarded. | Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message | DSNU1140I after 2000 instances of message DSNU1239I, when | MAXERR is specified to greater than 2000 or 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: PM63979 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM63979 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 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. | Example 1: The LOAD utility issues message DSNU1140I after 2000 instances of any of the following messages: DSNU313I, DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have triggered the suppressed message are still discarded. | Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message | DSNU1140I after 2000 instances of message DSNU1239I, when 1 | MAXERR is specified to greater than 2000 or 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 ACTION: The PTF for APAR PM63979 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. To make this fix effective for a static application, it must be 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: The PTF for APAR PM50005 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: ***Action for PM50006: It should be noted that the removal of these UNLOAD restrictions will now allow clone and/or base table data to be UNLOADed using image copy data sets from the other table in the clone relationship as follows: 1 - UNLOAD from base table using a clone table image copy. 2 - UNLOAD from clone table using a base table image copy. 1 And in these cases the MSGDSNU1227I and MSGDSNU1408I messages will no longer be issued and the return codes will be zero with this APAR fix. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUULCA PM63979 DSNUULCB PM63979 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63979 DSNUULCA DSNUULCB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULCA DSNUULCB LISTEND UK79770 COVER LETTER END UK79786 COVER LETTER START PROBLEM DESCRIPTION(S): PM61345 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B in DSNB1VCU * **************************************************************** * RECOMMENDATION: * **************************************************************** When a page set is opened in read only mode for a long period of time, the DB2 pseudo-close processor will update its VSAM catalog last-reference timestamp. There is a timing window between a concurrent DDL CREATE operation and the pseudo close processor. An abend is encountered during the page set timestamp update while the same page set gets closed by the CREATE operation. DB2 has been fixed by updating the VSAM catalog last-reference timestamp when a page set is opened. This will allow the pseudo close processor to skip any page set with a current timestamp and avoid the abend. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61345 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 PM61345 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61345 DSNB1OPP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNB1OPP LISTEND UK79786 COVER LETTER END UK79794 COVER LETTER START PROBLEM DESCRIPTION(S): PM65111 - **************************************************************** * USERS AFFECTED: All DB2 users of CP query parallelism in a * * data-sharing environment. * **************************************************************** * PROBLEM DESCRIPTION: AB04E RC00E70005 DSNXOGP1 :M010 while * * executing a query that runs in parallel * **************************************************************** * RECOMMENDATION: * **************************************************************** An internal data-sharing control block was not initialized properly, leading to incorrect CP parallelism information. This resulted in the symptom ABEND when a parallel query executed. The internal field is now initialized correctly. Additional Keywords: SQLPARALLELISM SQLCPUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65111 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN7LST3 PM65111 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65111 DSN7LST3 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN7LST3 LISTEND UK79794 COVER LETTER END UK79815 COVER LETTER START PROBLEM DESCRIPTION(S): PM66139 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * RUNSTATS utility users collecting * * distribution statistics on COLGROUPs. * **************************************************************** * PROBLEM DESCRIPTION: RUNSTATS COLGROUP FREQVAL on a * * LARGE table space abends with * 1 * ABEND04E RC00E20013 DSNSGMN OFFSET05CA * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When the user executed RUNSTATS TABLESPACE TABLE COLGROUP FREQVAL on a LARGE table space, the utility abended with ABEND04E RC00E20013 at DSNSGMN +X'05CA' due to local storage shortage. The user specified a high FREQVAL COUNT value. Since the table space was a large tablespace, it resulted in getting a very large workarea below the bar for the purpose of frequency aggregation. This resulted in the local storage shortage causing the storage abend. Code was changed to get the workarea storage above the bar. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66139 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSAF1 PM66139 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66139 DSNUSAF1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSAF1 LISTEND UK79815 COVER LETTER END UK79821 COVER LETTER START PROBLEM DESCRIPTION(S): PM64354 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of the * * LOAD utility * **************************************************************** * PROBLEM DESCRIPTION: LOAD SHRLEVEL NONE at the table space * * level encountered ABEND04E RC00C90099 * * when loading a COMPRESS YES classic * * partitioned or partition by range * * table space * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD SHRLEVEL NONE at the table space level encountered ABEND04E RC00C90099 when loading a COMPRESS YES classic partitioned or partition by range table space. LOAD built a single compression dictionary for all partitions resulting in a poor compression ratio. 1 LOAD SHRLEVEL NONE at the table space level has been changed to build a unique compression dictionary for each partition when loading a table space with less than or equal to 254 partitions and when COPYDICTIONARY is not specified. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64354 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 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 DSNURWI PM64354 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64354 DSNURWI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWI LISTEND UK79821 COVER LETTER END UK79825 COVER LETTER START PROBLEM DESCRIPTION(S): PM61727 - **************************************************************** * USERS AFFECTED: DB2 users of RENAME TABLE, RENAME INDEX, or * * ALTER TABLE RENAME COLUMN. * **************************************************************** * PROBLEM DESCRIPTION: 1. SYSTABLES.ALTEREDTS is not updated * * on RENAME TABLE * * 2. SYSINDEXES.ALTEREDTS is not updated * * on RENAME INDEX * * 3. SYSCOLUMNS.ALTEREDTS is not updated * * on ALTER TABLE RENAME COLUMN * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 The ALTEREDTS value is not being updated for some catalog tables on RENAME: 1. SYSTABLES.ALTEREDTS is not updated on RENAME TABLE 2. SYSINDEXES.ALTEREDTS is not updated on RENAME INDEX 3. SYSCOLUMNS.ALTEREDTS is not updated on ALTER TABLE RENAME COLUMN DB2 code has been fixed to do the following: 1. Update SYSTABLES.ALTEREDTS on RENAME TABLE 2. Update SYSINDEXES.ALTEREDTS on RENAME INDEX 3. Update SYSCOLUMNS.ALTEREDTS on ALTER TABLE RENAME COLUMN Applying this APAR will not fix existing ALTEREDTS values that were not updated on RENAME. These values have no known impact to DB2 functionality. ADDITIONAL KEYWORDS: SQLALTER SQLRENAME COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61727 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIRCO PM61727 DSNXIRIX PM61727 DSNXIRTB PM61727 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61727 DSNXIRCO DSNXIRIX DSNXIRTB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIRCO DSNXIRIX DSNXIRTB LISTEND UK79825 COVER LETTER END UK79829 COVER LETTER START PROBLEM DESCRIPTION(S): PM63574 - **************************************************************** * USERS AFFECTED: All users of the installation CLIST for DB2 * * Version 9.1 for z/OS and DB2 10 for z/OS are * * affected by this change. * **************************************************************** * PROBLEM DESCRIPTION: IRLM APAR PM58723 (fixed by PTF UK77876 * * for IRLM 2.2 and UK77877 for IRLM 2.3) * * has increased the maximum size for * * coupling facililty lock structure table * * entries (LTEs) from 1024 MB to 2048 MB. * 1 * This change needs to be supported by * * the DB2 installation CLIST and panels. * **************************************************************** * RECOMMENDATION: Apply the fixing PTF for this APAR. * **************************************************************** DB2 for z/OS installation job DSNTIJMV provies an optional IRLM address space proc, IRLMPROC, that is customized by the DB2 installation CLIST using entries gathered by DB2 installation panels DSNTIPI and DSNTIPJ. In particular, panel DSNTIPJ, field NUMBER OF LOCK ENTRIES collects the desired setting for the LTE parameter of IRLMPROC. The LTE parameter specifies the number of lock table entries that are to be in the coupling facility lock structure. IRLM APAR PM58723 has increased the maximum LTE size from 1048 MB to 2048 MB. See the fixing PTFs, UK77876 (for IRLM 2.2) and UK77877 (for IRLM 2.3) for additional information. The DB2 installation CLIST and panels need to be updated to support this change. This APAR modifies installation panel DSNTIPJ, increasing the maximum entry in the NUMBER OF LOCK ENTRIES field to 2048 (megabytes). The minimum and default entry both remain 0. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63574 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM63574 (V10) This PTF modifies the DB2 installation CLIST to support changes by IRLM 2.3 PTF UK77877 (fixes APAR PM58723) which increased the maximum size for the IRLM LTE parameter from 1024 MB to 2048 MB. Before applying this PTF, verify that you have already applied PTF UK77877 to your DB2 V10 system. If you have already installed or migrated to DB2 V10 then after applying this PTF, you need to take the following actions: (1) Copy updated DB2 installation panels to alternate libraries (2) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) 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 DB2 installation panel DSNTIPJ 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 DSNTIPJ 1 panel to that library. ---------------------------------------------------------------- (2) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all V10 customers This PTF modifies IRLMLTE, the entry for the IRLM LTE parameter in DB2 CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP target library. You need to update this entry in all private copies of your CLIST output (DSNTIDxx) member. In each such copy, locate the entry for IRLMLTE and change the fifth field from 1024 to 2048 IRLMLTE NUM M 0 1024 x | | | +- local setting +- change for IRLM LTE this to 2048 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM63574 DSNTIDXA PM63574 DSNTIDXB PM63574 DSNTIPJ PM63574 DSNTXAZP PM63574 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63574 DSN@XAZP DSNTIDXA DSNTIDXB DSNTIPJ DSNTXAZP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP MACROS DSN@XAZP DSNTIDXA DSNTIDXB DSNTIPJ LISTEND UK79829 COVER LETTER END UK79832 COVER LETTER START PROBLEM DESCRIPTION(S): PM57166 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of REORG TABLESPACE SHRLEVEL * * CHANGE utilizing parallel index build * **************************************************************** * PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE abends * * in the SORTBLD phase with ABEND0C4 RC4 * * at DSNURBXA+x'E71A' while processing * 1 * duplicate keys * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** REORG TABLESPACE SHRLEVEL CHANGE was run on a partitioned table space containing multiple unique indexes. While processing duplicate keys in the SORTBLD phase, REORG suffered an ABENDS0C4 RC4 at DSNURBXA+x'E71A' which was followed by an ABEND04E RC00E40322 in DSNURBXA. The utility was finally abended with an an ABEND04E RC00E40347 from DSNURPTB. The ABEND0C4 was the result of multiple index build subtasks attempting to read from, and write into, the same location in a buffer whose access was not serialized. Additional Keyword: OFFSETE71A REORG TABLESPACE has been changed to acquire a latch before accessing the RID list buffer while processing duplicate keys. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57166 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGRAR PM57166 DSNURBXA PM57166 DSNURBXC PM57166 DSNURFBR PM57166 DSNURSCN PM57166 DSNUSIDX PM57166 DSNUSLTS PM57166 DSNUSTBL PM57166 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57166 DSNUGRAR DSNURBXA DSNURBXC DSNURFBR DSNURSCN DSNUSIDX DSNUSLTS DSNUSTBL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGRAR DSNURBXA DSNURBXC DSNURFBR DSNURSCN DSNUSIDX DSNUSLTS DSNUSTBL LISTEND UK79832 COVER LETTER END UK79834 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM63835 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS, and DB2 * * 10 for z/OS utility users of LOAD ENFORCE NO * **************************************************************** * PROBLEM DESCRIPTION: LOAD INTO TABLE PART n REPLACE ENFORCE * * NO of a parent table followed by a LOAD * * INTO TABLE PART n REPLACE ENFORCE NO * * into the child table changes the STATUS * * column in SYSTABLESPACE from 'P' to 'S' * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD INTO TABLE PART n REPLACE ENFORCE NO was run on a parent table. This placed all of the partitions of the child table into CHKP (check pending) and properly set the STATUS column in SYSIBM.SYSTABLESPACE for the child table to 'P'. When a partition of that child table was loaded with LOAD INTO TABLE PART n REPLACE ENFORCE NO, the entire table space was correctly left in CHKP but the STATUS column was incorrectly modified to 'S'. For clarity, a STATUS of 'P' signifies that ALL of the partitions in that table are in CHKP. A STATUS of 'S' signifies that only SOME of the partitions in that table are in CHKP. LOAD code has been changed to not change the STATUS column from 'P' to 'S' in SYSIBM.SYSTABLESPACE when a partition of a child table has been loaded with LOAD INTO TABLE PART n REPLACE ENFORCE NO. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63835 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: With the application of the PTF for PM63835, because the STATUS column in SYSIBM.SYSTABLESPACE will now be correct when loading a partitioned table space with RI, it is possible that a CHECK DATA PART or a CHECK DATA SCOPE PENDING utility run on a child table space after being loaded might take longer to complete. This would be due to the utility reading the now correct STATUS column and deciding that all partitions for that child table space needed to be checked rather than just specfic or specified partitions. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGCKP PM63835 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63835 DSNUGCKP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGCKP 1 LISTEND UK79834 COVER LETTER END UK79844 COVER LETTER START PROBLEM DESCRIPTION(S): PM65332 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of OPTIONS PREVIEW with UNLOAD. * **************************************************************** * PROBLEM DESCRIPTION: Expansion of data set name using * * OPTIONS PREVIEW is different from * * actual execution of UNLOAD utility * * when data set is defined by a TEMPLATE * * using &PA with a substring. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User defined a TEMPLATE using &PA/&PART with substring as '&PA(x)/&PART(x)' for UNLDDN for UNLOAD utility on a partitioned table space. OPTIONS PREVIEW delivered multiple data set names for UNLDDN while UNLOAD would unload a single data set in execution. OPTIONS PREVIEW is changed to deliver the same data set name for UNLOAD UNLDDN data set as the full execution. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65332 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGPVV PM65332 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65332 DSNUGPVV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGPVV LISTEND UK79844 COVER LETTER END UK79870 COVER LETTER START PROBLEM DESCRIPTION(S): PM64732 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of query parallelism. * **************************************************************** * PROBLEM DESCRIPTION: When query parallelism is enabled with * * multiple CPUs, a user may get SQLCODE * 1 * -904 with reason 00C90089 and resource * * type 00000603 while running a query. * **************************************************************** * RECOMMENDATION: * **************************************************************** When query parallelism is enabled with multiple CPUs, a user may get SQLCODE -904 with reason 00C90089 and resource type 00000603 while running a query. An example query that may exhibit this problem: SELECT C1 FROM T1 WHERE C1 IN (SELECT C2 FROM T2 WHERE C2 IN (SELECT C3 FROM T3 WHERE C3 IN (SELECT C4 FROM T4 WHERE C4 IN (SELECT C5 FROM T5 WHERE C5 IN (SELECT C6 FROM T6 WHERE C6 IN (SELECT C7 FROM T7 WHERE C7 IN (SELECT C8 FROM T8 WHERE C8 IN (SELECT C9 FROM T9 WHERE C9 = '061000') ) ) ) ) ) ) ) The problem was caused by following an invalid pointer in storage. Since this problem is dependent on the contents of storage at the time, the symptoms may happen intermittently or not at all. Additional keywords: SQLPARALLELISM SQLCPUP DB2PARALL/K SQLCODE904 RC00C90089 DB2 code has now been changed to fix the problem. The SQLCODE -904 will no longer occur for this scenario. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64732 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOLM1 PM64732 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64732 DSNXOLM1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLM1 LISTEND 1UK79870 COVER LETTER END UK79871 COVER LETTER START PROBLEM DESCRIPTION(S): PM62786 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of LOAD with TRUSTED CONTEXT * **************************************************************** * PROBLEM DESCRIPTION: LOAD with TRUSTED CONTEXT results in * * storage growth of subpool 231 in the * * DBM1 address space * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD with TRUSTED CONTEXT results in subpool 231 storage growth in the DBM1 address space. This is due to LOAD subtasks overlaying the address of one of their control blocks with the address of a control block from the LOAD main task. This caused the storage of the original control block to not be freed when the subtask went through deallocation which, in turn, resulted in the DBM1 address space running low on storage. LOAD code has been modified to save the pointer for the subtask control block before overlaying it with the pointer from the main task control block. Subsystem Services code has been changed to make sure pointers are set up correctly so the utility subtask control blocks can be deallocated correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62786 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM62786 has modified CSECTs in both the DSNUT101 and DSN3AMGP load modules, affecting the utility batch and DB2 MSTR 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 MSTR 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 MSTR address spaces, the problem the PTF addresses will not be resolved. ACTION: The PTF for APAR PM25135 has modified CSECTs in both the DSNUT101 and DSN3AMGP load modules, affecting the utility batch and DB2 MSTR 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 MSTR 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 MSTR address spaces, the problem the PTF addresses will not be resolved. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGSIT PM62786 DSN3EOT0 PM62786 DSN3ID30 PM62786 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62786 DSNUGSIT DSN3EOT0 DSN3ID30 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGSIT DSN3EOT0 DSN3ID30 LISTEND UK79871 COVER LETTER END UK79881 COVER LETTER START PROBLEM DESCRIPTION(S): PM60866 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users. * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes various RTS issues: * * * * 1. Column LASTUSED in table * * SYSIBM.SYSINDEXSPACESTATS is not * * updated correctly for referential * * integrity checks. * * * * In DB2 10 only: * * * * 2. After a mass delete on a * * multi-table table-space all * * real-time statistics counters are * * NULL. * * * * 3. Some real-time statistics counters * * for workfile objects might be * * invalid. * **************************************************************** * RECOMMENDATION: APPLY PTF. * **************************************************************** 1. The LASTUSED column in SYSIBM.SYSINDEXSPACESTATS is not updated when the index is used to look-up a foreign key that does not exist. 1 2. A mass delete operation on a table space containing multiple tables sets all RTS counters to NULL even though several columns remain valid. 3. The real-time statistics counters TOTALROWS, DATASIZE, UNCOMPRESSEDDATASIZE and NPAGES might be invalid for workfile table spaces. 1. Real-time statistics logic was changed, so that the LASTUSED column in SYSIBM.SYSINDEXSPACESTATS is also maintained for foreign key look-ups that did not find the key. 2. Real-time statistics logic was changed, so that in case of a mass delete on a multi-table table-space only the counters TOTALROWS, DATASIZE, UNCOMPRESSEDDATASIZE and NPAGES are set to NULL. 3. Real-time statistics logic was changed, so that the counters TOTALROWS, DATASIZE, UNCOMPRESSEDDATASIZE and NPAGES are set to NULL for workfile table spaces when any real-time statistics update is performed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60866 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRELI PM60866 DSNIRTSU PM60866 DSNIRTSX PM60866 DSNISEGD PM60866 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60866 DSNIRELI DSNIRTSU DSNIRTSX DSNISEGD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRELI DSNIRTSU DSNIRTSX DSNISEGD LISTEND UK79881 COVER LETTER END UK79896 COVER LETTER START PROBLEM DESCRIPTION(S): PM62928 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * parallelism. * **************************************************************** * PROBLEM DESCRIPTION: VARIOUS ABENDS MAY OCCUR FOR QUERY * * CONTAINING A TABLE EXPRESSION OR VIEW * 1 * WITH DUPLICATE COLUMNS ON THE SELECT * * LIST WHEN RUN IN PARALLEL. * **************************************************************** * RECOMMENDATION: * **************************************************************** VARIOUS ABENDS MAY OCCUR FOR A QUERY CONTAINING A TABLE EXPRESSION OR VIEW WITH DUPLICATE COLUMNS ON THE SELECT LIST WHEN RUN IN PARALLEL. THE FOLLOWING IS AN EXAMPLE OF SUCH FAILING SCENARIO: SELECT SUM(T1.C1), SUM(T1.C2), TX.* FROM (SELECT DISTINCT TA.C1 AS TX1, TB.C1 AS TX2, TA.C1 AS TX3, TA.C2 AS TX4, TB.C2 AS TX5, TA.C3 AS TX6,... FROM TA LEFT OUTER JOIN TB ON TA.C2 = TB.C2) TX LEFT OUTER JOIN T1 ON T1.C3 = TX.TX2 GROUP BY TX.TX1, TX.TX3, TX.TX4, TX.TX5, TX.TX6 TX1 and TX3 are the same column in the table expression. The bindtime code in DB2 is modified to correct the conditions leading to the ABEND. Additional keywords:SQLTABLEEXPR SQLVIEW DB2PARALL/K PARALLELISM SQLPARALLELISM SQLCPUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62928 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM62928: See PM62928 APAR/PTF text for additional information about why a REBIND is necessary. PM62928 corrects a problem where various abends can occur for a query containing a table expression or view with duplicate columns on the select list when run 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: See PM56548 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM56548 corrects a problem that can cause an abend for a DELETE statement when it contains more than one subquery predicates and more than one subquery to join transformation occurs. 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 See PM53481 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM53481 corrects problems that can cause an incorrect sort order for a query with group by case expression and order by accending on the same 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: See PM30196 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM30196 corrects problems that can cause an incorrect output for a query using a set function like COUNT with DISTINCT on a DECFLOAT 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPTT PM62928 DSNXOSR PM62928 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62928 DSNXOPTT DSNXOSR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPTT DSNXOSR LISTEND UK79896 COVER LETTER END UK79898 COVER LETTER START PROBLEM DESCRIPTION(S): PM64602 - **************************************************************** * USERS AFFECTED: None. This fix is for objects started as * * read-only (RO)-related undocumented * * serviceability item. * **************************************************************** * PROBLEM DESCRIPTION: Serviceability enhancement. * **************************************************************** * RECOMMENDATION: * **************************************************************** Serviceability enhancement. Serviceability enhancement. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM64602 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWPZ PM64602 DSNDSPRM PM64602 DSNILKDY PM64602 DSNILRBK PM64602 DSNIPSFN PM64602 DSNZOVTB PM64602 DSN6SPRC PM64602 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64602 DSNDQWPZ DSNDSPRM DSNILKDY DSNILRBK DSNIPSFN DSNZOVTB DSN6SPRC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNILKDY DSNILRBK DSNIPSFN DSNZOVTB MACROS DSNDQWPZ DSNDSPRM DSN6SPRC LISTEND UK79898 COVER LETTER END UK79980 COVER LETTER START PROBLEM DESCRIPTION(S): PM63669 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: "Buffer pool full" condition hit, with * * message MSGDSNB601I and applications * * failing with resource unavailable * * reason code 00C200E9. * **************************************************************** * RECOMMENDATION: * **************************************************************** Processes in DB2 may access buffer pool pages but then fail to release them. One of these is the process which builds a compression dictionary during INSERT processing, which fails to release the header page and possibly a spacemap page. Once such a process performs a logical close on the object for which it is holding pages, it is no longer possible to find and free them. Over time, these orphan pages can end up filling the entire buffer pool. 1 The page set logical close logic has been modified to detect if pages are still held for this object, and if so to release them. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63669 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CPS PM63669 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63669 DSNB1CPS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CPS LISTEND UK79980 COVER LETTER END UK79982 COVER LETTER START PROBLEM DESCRIPTION(S): PM64741 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of trigger * * transition variables in Conversion * * Mode (CM). * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNOLLE ERQUAL5001 when an * * empty BLOB is used as a trigger * * transition variable in DB2 V10 * * Conversion Mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOLLE ERQUAL5001 when an empty BLOB is used as a trigger transition variable in DB2 V10 Conversion Mode. The following example illustrates the problem. 1. Create two tables T1 and T2. Populate T1 with an empty BLOB. CREATE TABLE T1 ( ID INT, B1 BLOB(256K) )! CREATE TABLE T2 ( 1 ID INT, B1 BLOB(256K) ) INSERT INTO T1 VALUES(1, BLOB(''))! INSERT INTO T1 VALUES(2, BLOB('T2'))! 2. Create an AFTER UPDATE TRIGGER on Table T1. CREATE TRIGGER T1_TRIG AFTER UPDATE ON T1 REFERENCING OLD AS ALT FOR EACH ROW MODE DB2SQL INSERT INTO T2(ID, B1) VALUES (ALT.ID, ALT.B1)! 3. Write an application which updates Table T1. DCL I BIN FIXED(15); I = 1; DO WHILE (SQLCODE >= 0 & i ¬= 3); EXEC SQL UPDATE T1 SET ID = :I+10 WHERE ID = :I; I = I + 1; END; 4. The application is bound on a pre-v10 DB2 z/OS system and DB2 is migrated to DB2 V10 Conversion Mode. When the application is executed, the trigger T1_TRIG is fired for the update on T1, but the DB2 LOB manager component does not handle the empty BLOB value as a transition variable properly. So, during the trigger process, the ABEND04E at DSNOLLE ERQUAL5001 occurs. Please note. The problem does not occur if an empty CLOB or DBCLOB is used. The code in DB2 has been modified to process an "empty BLOB as a transition variable" properly which will avoid the abend. Addtional Keywords: SQLTRIGGER SQLLOB CM8 CM9 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64741 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRIT9 PM64741 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM64741 DSNXRIT9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRIT9 LISTEND UK79982 COVER LETTER END UK80003 COVER LETTER START PROBLEM DESCRIPTION(S): PM64864 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users * * specifically those using TCP/IP. * **************************************************************** * PROBLEM DESCRIPTION: ABEND 04E-00D3111C, * * LOC=DSNLILLM.DSNLIDNS:0002 * **************************************************************** * RECOMMENDATION: * **************************************************************** The SYSIBM.LOCATIONS table is used to associate a remote server's LOCATION name with its network attributes, like the port. A user can either specify the port number or its equivalent service name. When a user attempts to connect to the server using a service name, DB2 intended to convert it to a port number using the TCP/IP getservbyname service but DB2 incorrectly invokes the wrong TCP/IP service. The abend occurs because the port was not determined. DB2 has changed its TCP/IP service name lookup processing to use the proper TCP/IP service. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64864 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLILE PM64864 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64864 DSNLILE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLILE LISTEND UK80003 COVER LETTER END UK80018 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM62607 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REPAIR VERSIONS utility. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIOST2:5050 * * during an SQL query running * * concurrently with REPAIR VERSIONS * * utility on the same table space. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** An SQL query with a CS READ claim class was running concurrently with a REPAIR VERSIONS TABLESPACE utility on the same object. The SQL query abended with an ABEND04E RC00C90101 DSNIOST2 ERQUAL5050. The REPAIR utility had a drain on the writers of the object, but not on readers, and performed a physical close of the table space, impacting the concurrent readers. REPAIR VERSIONS utility code has been modified to drain both readers and writers (ALL). 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 is allowed and should therefore block all readers and writers during the REPAIR operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62607 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 DSNUCBVR PM62607 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62607 DSNUCBVR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBVR 1 LISTEND UK80018 COVER LETTER END UK80020 COVER LETTER START PROBLEM DESCRIPTION(S): PM65983 - **************************************************************** * USERS AFFECTED: Users of the DB2 for z/OS precompiler * * Versions 9.1 and 10.1 * **************************************************************** * PROBLEM DESCRIPTION: Calling the precompiler load module * * DSNHPC with no PARM input, or with a * * PARM input of length 0 causes DSNHPC * * to abend with 0C4 REASON CODE=00000011 * **************************************************************** * RECOMMENDATION: * **************************************************************** Calling the precompiler load module DSNHPC with no PARM input or PARM input of length 0 results in the following abend: SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011 TIME=10.31.47 SEQ=00055 CPU=0000 ASID=002C PSW AT TIME OF ERROR 078D2001 98500DEE ILC 4 INTC 11 ACTIVE LOAD MODULE ADDRESS=18400000 OFFSET=00100DEE NAME=DSNHPC DATA AT PSW 18500DE8 - 000341F0 B1684400 B210E300 GR 0: 00000000 1: 00007000 2: 00000000 3: 00000000 4: 00000000 5: 00000000 6: 006B4FC8 7: 18503070 8: 00000000 9: 00000000 A: 1850304C B: 185917F0 C: 834B0022 D: 185917F0 E: 00000001 F: 18591968 Examples of JCL that result in the abend: //PC EXEC PGM=DSNHPC,PARM='' //PC EXEC PGM=DSNHPC Additional keywords: ABEND0C4 DB2PRECOMPILER DB2 precompiler code is modified so that the abend no longer occurs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65983 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHMAIN PM65983 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65983 DSNHMAIN 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHMAIN LISTEND UK80020 COVER LETTER END UK80030 COVER LETTER START PROBLEM DESCRIPTION(S): PM64901 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users having queries for which * * a multi-index access plan over index on * * expression (IOE) might be considered in * * bind/prepare. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC10 at DSNXOGCM+2E2E may * * occur on V10 or ABEND0C4 RC3B at * * DSNXOGCM+2A72 may occur on V9 when * * DB2 binds/prepares a query for which * * a multi-index access plan containing * * an index-on-expression is considered * * in the bind/prepare process. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may hit ABEND0C4 RC10 at DSNXOGCM+2E2E on V10 or ABEND0C4 RC3B at DSNXOGCM+2A72 on V9 during bind/prepare of a query when the following conditions are met: A. The query contains multiple predicates joined by AND inside an OR clause. B. DB2 may consider building a multi-index access plan for the query during the bind/prepare process. C. One of the indexes in the multi-index access plan is an index-on-expression. The ABEND is caused by following an invalid pointer in the storage. Solution: DB2 code has been fixed to use a valid pointer, in order to fix the ABEND0C4 RC10 on V10 and ABEND0C4 RC3B on V9. Additional keywords : SQLINDEX SQLINDEXONEXP SQLOR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64901 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGCM PM64901 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64901 DSNXOGCM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGCM LISTEND UK80030 COVER LETTER END UK80032 COVER LETTER START PROBLEM DESCRIPTION(S): PM64970 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of queries that * * involve Pair-wise join (JOIN_TYPE = 'P') * **************************************************************** * PROBLEM DESCRIPTION: ABEND 0C4 RC00000038 may occur in * * DSNXGRDS.DSNXSFRT when query with the * * Pair-wise join is processed. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND 0C4 RC00000038 may occur in DSNXGRDS.DSNXSFRT+0234 when query with the Pair-wise join is processed. Abend occurs when Sort attempts to free a RID list which was already (prematurely) freed and the RIDMAP block was re-used for another query. DB2 code was changed to correct the timing of freeing a RID list ADDITIONAL KEYWORDS: SQLPARALLELISM SQLPAIRWISEJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64970 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRRID PM64970 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64970 DSNXRRID THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRRID LISTEND UK80032 COVER LETTER END UK80068 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM53282 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: XML schema validation performance * * may be improved when XML data is sent * * in Extensible Dynamic Binary XML * * DB2 Client/Server Binary XML * * Format (IBM defined binary XML * * format). * **************************************************************** * RECOMMENDATION: * **************************************************************** When binary XML data is sent to DB2 for XML schema validation, DB2 needs to convert the binary XML to textual XML before executing XML schema validation. This extra conversion impacts validation performance. With z/OS PTF UA63422 or PTF UA65591 and this DB2 PTF, DB2 will no longer convert binary XML data to textual XML for schema validation under the following conditions: 1. the XML schema name is explicitly specified in the DSN_XMLValidate function OR 2. there is only one XML schema in the XML type modifier of the target column for LOAD or INSERT. Additional keywords: XMLALL SQLXML XMLSCHEMA COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53282 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This DB2 PTF requires z/OS XML System Services PTF UA63422 or PTF UA65591. If UA63422 or PTF UA65591 is not applied, DB2 will convert the binary XML data to textual XML before executing XML schema validation. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNLEPL PM53282 DSNNOBXI PM53282 DSNNOBXV PM53282 DSNNOIRT PM53282 DSNNOPAR PM53282 DSNXINIT PM53282 HDBAA10J PM53282 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53282 DSNNLEPL DSNNOBXI DSNNOBXV DSNNOIRT DSNNOPAR DSNXINIT HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNLEPL DSNNOBXI 1 DSNNOBXV DSNNOIRT DSNNOPAR DSNXINIT LISTEND UK80068 COVER LETTER END UK80106 COVER LETTER START PROBLEM DESCRIPTION(S): PM64230 - **************************************************************** * USERS AFFECTED: DB2 for z/OS of V9 or V10 users who * * operates Mass Delete on segmented or * * Universal Table space * **************************************************************** * PROBLEM DESCRIPTION: The table space keeps growing with * * the same repeated work load that * * contains the operation of * * insert, mass delete, insert, mass * * delete in the same commit scope. * **************************************************************** * RECOMMENDATION: * **************************************************************** The deleted spaces can not be reused before commit when there are mass delete and insert operations in the same commit scope. The other flavor of mass delete is TRUNCATE TABLE with REUSE STORAGE option. Since TRUNCATE TABLE with REUSE STORAGE option has slightly different syntax and process, the delete logic was not able to distinguish the different between them. Therefore, when this work load runs repeatedly, the mass deleted space from the prior commit scope was treated as a reserved space from TRUNCATE TABLE with REUSE STORAGE option and it was prohibited to be reused by subsequent insert. As a result, the table space keeps growing after running the same work load repeatedly. DB2 code has been modified to ensure the deleted space can be reused after commit regardless of whether the space was deleted by TRUNCATE TABLE or the mass delete operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64230 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 PM64230 DSNISEGD PM64230 DSNISGSS PM64230 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64230 DSNICMT2 DSNISEGD DSNISGSS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNICMT2 DSNISEGD DSNISGSS LISTEND UK80106 COVER LETTER END UK80113 COVER LETTER START PROBLEM DESCRIPTION(S): PM52724 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of SQL mass delete * * and the RECOVER utility with the BACKOUT * * YES option. * **************************************************************** * PROBLEM DESCRIPTION: After the application of PTF UK66327 * * (APAR PM30991), an application issuing * * millions of SQL mass deletes on a * * user table without commits caused * * lock escalation to occur on catalog * * table space DSNDB06.SYSCOPY resulting * * in contention for COPY utility jobs * * executing at the same time. * **************************************************************** * RECOMMENDATION: * **************************************************************** After the application of PTF UK66327 (APAR PM30991), an application issuing millions of SQL mass deletes on a user table without any commits caused lock escalation to occur on catalog table space DSNDB06.SYSCOPY resulting in timeouts for COPY utility jobs executing at the same time. PTF UK66327/APAR PM30991, added code to insert a SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' (L-M) when a SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION is executed on a segmented or universal table space. This SYSCOPY record was used to prohibit a subsequent RECOVER BACKOUT YES since the deleted data is not logged for these activities. See the closing text of PM30991 for more details. The insert of the L-M SYSCOPY record can cause problems for some customers, if SQL mass deletes are heavily used without commits. In addition to contention on SYSCOPY, the large number of SYSCOPY records inserted will cause the SYSCOPY table space to grow. The L-M SYSCOPY record will no longer be inserted for SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION on segmented or UTS tables spaces. The RECOVER utility will continue to check for the L-M SYSCOPY record and issue msgDSNU556I (RECOVER CANNOT PROCEED FOR... BECAUSE A SYSCOPY RECORD HAS BEEN ENCOUNTERED...) if found. A new diagnostic log record is written for SQL mass delete, TRUNCATE TABLE, and DROP TABLE. DSN1LOGP has been modified to format the new diagnostic log record. The RECOVER utility with the BACKOUT YES option will issue 1 a new message, msgDSNU1544I, if the diagnostic log record is encountered during the LOGCSR or LOGUNDO phase: .. DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER TABLE ACTIVITY .. Explanation: BACKOUT YES was specified for the RECOVER utility, but it cannot proceed because a prior SQL mass DELETE, TRUNCATE TABLE, or DROP TABLE occurred on the object. The deleted data for these activities are not logged, hence cannot be backed out. The recovery is prohibited when this kind of activity has occurred between the recovery point (specified by TOLOGPOINT or TORBA) and the current time. .. System action: The utility terminates processing. .. User response: Remove the BACKOUT YES option from the RECOVER utility statement and resubmit the job. This will recover the list of objects by restoring a backup then applying the logs forward to the recovery point. .. Severity: 8 (error) .. Note that if the table space has indexes or auxiliary objects (LOB or XML table spaces and all auxiliary indexes) RECOVER BACKOUT YES is not supported on these objects when SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION has occurred on the base table space. The new diagnostic log record is not needed for the ALTER TABLE ROTATE PARTITION case because a SYSCOPY record with ICTYPE='A' and STYPE='R' is already inserted. In this case, RECOVER with the BACKOUT YES option will be prohibited with msgDSNU556I. A change has been made to the RECOVER utility with the BACKOUT YES option to delay the setting of RECP on the target objects. The setting of RECP on the target objects has been moved from the LOGCSR phase to the beginning of the LOGUNDO phase, because the objects are not updated until the LOGUNDO phase. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM52724 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: With the PTF for PM52724, a new DB2 message, DSNU1544I, will be issued during the RECOVER utility with the BACKOUT YES option if the recovery cannot proceed: .. DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER TABLE ACTIVITY 1 .. Explanation: BACKOUT YES was specified for the RECOVER utility, but it cannot proceed because a prior SQL mass DELETE, TRUNCATE TABLE, or DROP TABLE occurred on the object. The deleted data for these activities are not logged, hence cannot be backed out. The recovery is prohibited when this kind of activity has occurred between the recovery point (specified by TOLOGPOINT or TORBA) and the current time. .. System action: The utility terminates processing. .. User response: Remove the BACKOUT YES option from the RECOVER utility statement and resubmit the job. This will recover the list of objects by restoring a backup then applying the logs forward to the recovery point. .. Severity: 8 (error) .. See the closing text of PM52724 for details. ACTION: After the application of the PTF for APAR PM52724, the SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will no longer be inserted for SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION on segmented or universal table spaces (UTS). .. A new DB2 message, DSNU1544I, will now be issued during the RECOVER utility with the BACKOUT YES option if the recovery cannot proceed: .. DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER TABLE ACTIVITY .. Explanation: BACKOUT YES was specified for the RECOVER utility, but it cannot proceed because a prior SQL mass DELETE, TRUNCATE TABLE, or DROP TABLE occurred on the object. The deleted data for these activities are not logged, hence cannot be backed out. The recovery is prohibited when this kind of activity has occurred between the recovery point (specified by TOLOGPOINT or TORBA) and the current time. .. System action: The utility terminates processing. .. User response: Remove the BACKOUT YES option from the RECOVER utility statement and resubmit the job. This will recover the list of objects by restoring a backup then applying the logs forward to the recovery point. .. Severity: 8 (error) 1 .. See the closing text of PM52724 for details. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFMDIR PM52724 DSNFUDRE PM52724 DSNILDOR PM52724 DSNIRCSR PM52724 DSNISEGD PM52724 DSNIUNDO PM52724 DSNKMDEL PM52724 DSNODALN PM52724 DSNUADP1 PM52724 DSNUBINS PM52724 DSNUCALA PM52724 DSNUCALC PM52724 DSNUCALU PM52724 DSNUCASA PM52724 DSNUMSGE PM52724 DSNUYAS2 PM52724 DSN1LDET PM52724 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM52724 DSNFMDIR DSNFUDRE DSNILDOR DSNIRCSR DSNISEGD DSNIUNDO DSNKMDEL DSNODALN DSNUADP1 DSNUBINS DSNUCALA DSNUCALC DSNUCALU DSNUCASA DSNUMSGE DSNUYAS2 DSN1LDET THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFUDRE DSNILDOR DSNIRCSR DSNISEGD DSNIUNDO DSNKMDEL DSNODALN DSNUADP1 DSNUBINS DSNUCALA DSNUCALC DSNUCALU DSNUCASA DSNUMSGE DSNUYAS2 DSN1LDET LISTEND UK80113 COVER LETTER END UK80114 COVER LETTER START PROBLEM DESCRIPTION(S): PM66159 - **************************************************************** 1 * USERS AFFECTED: All users of DB2 9 and 10 for z/OS * * of Profile Manager. * **************************************************************** * PROBLEM DESCRIPTION: A profile attribute entry in the * * SYSIBM.DSN_PROFILE_ATTRIBUTES table * * is rejected by START PRFOILE process * * showing * * 'REJECTED - INVALID KEYWORD SPECIFIED' * * in the STATUS column of the * * SYSIBM.DSN_PROFILE_ATTRIBUTES_HISTORY * * table when a valid keyword is specified * * with trailing blanks for the attribute * * entry. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a valid keyword is specified with trailing blanks for a profile attribute entry in the SYSIBM.DSN_PROFILE_ATTRIBUTES, the keyword of the entry was not recognized as a valid keyword during START PROFILE process since a keyword was expected to be specified in the exactly matching string as a valid keyword. This resulted in rejecting the attribute entry during START PROFILE process. DB2 has been modified to support trailing blanks in the KEYWORD column for a profile attribute entry in the SYSIBM.DSN_PROFILE_ATTRIBUTES table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66159 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 PM66159 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66159 DSNT1RSP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNT1RSP LISTEND UK80114 COVER LETTER END UK80132 COVER LETTER START PROBLEM DESCRIPTION(S): PM65945 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS and DB2 10 for * * z/OS who have parallelism and IN list * * predicate on index key column. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 in DSNXOLDL :M030 * 1 * when running an SQL statement with an * * IN list predicate on index key column * * and the query is running in parallel * * with host variables present. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 in DSNXOLDL :M030 when running an SQL statement with an IN list predicate on index key column and the query is running in parallel with host variables. The problem is DB2 sorts the INLIST too early. The IN list is modified afterward, so the order is no longer preserved. But DB2 still assumes IN list is sorted. This causes the abend when DB2 uses the IN list value to do the partition of parallel processing. A sample query is as follows: SELECT * FROM T1, T2 WHERE T1.C1 = T2.C1 AND T1.C2 IN ('BBB','AAA','FFF' 'RT.GOV.CT','GGG') AND T2.C2 = ? ; When index access has been used on T1.C2 which has an IN list predicate, DB2 does not process the sort of IN list correctly, which causes the reported problem. DB2 has been fixed to process the sort of the IN list in correct order so that the abend no longer occurs. Additional keywords: SQLIN SQLPARALLELISM PARALLELISM DB2PARALL/K SQLHOSTVAR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65945 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: This PTF corrects an abend problem that occurs when DB2 processes a parallel query with INLIST containing host variables The execution structures are not built in a correct order which causes the abend. To make this fix effective for static applications, you need to rebind the affected applications after you apply this PTF. DB2BIND: ***Action for PM56830: See PM56830 APAR/PTF text for additional information about why a REBIND is necessary. PM56830 corrects a problem of ABEND04E RC00C90101 CSECT DSNIWSET when running SQL statement containing recursive CTEs. 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 DSNXGPGR PM65945 DSNXGRTS PM65945 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65945 DSNXGPGR DSNXGRTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGPGR DSNXGRTS LISTEND UK80132 COVER LETTER END UK80166 COVER LETTER START PROBLEM DESCRIPTION(S): PM62468 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS NFM users running REORG * * on directory table space DBD01. * **************************************************************** * PROBLEM DESCRIPTION: ABND04E RC00C90101 DSNILGCL ERQUAL5003. * **************************************************************** * RECOMMENDATION: * **************************************************************** After migrating to DB2 V10 NFM, a REORG of DBD01 experienced 00C90101 failure in log manager logic. The log work area in the cursor table (CT) overlaid storage by an additional eight bytes. The log parameter area had grown by eight bytes and no longer correctly mapped to the cursor table work area storage. In the case where an overlay of the cursor table work area is likely to occur, DB2 will now make use of a local storage area when performing updates to the Header page for directory table space DBD01. The header page update flags in the log record have also been corrected. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62468 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 PM62468 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62468 DSNIHPGM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIHPGM 1 LISTEND UK80166 COVER LETTER END UK80178 COVER LETTER START PROBLEM DESCRIPTION(S): PM64225 - **************************************************************** * USERS AFFECTED: All V10 DB2 for z/OS users of LOB table * * space. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNOGLOB:5008 * **************************************************************** * RECOMMENDATION: * **************************************************************** The LOB data does not get inserted into LOB map page if the LOB streaming process was used to insert multiple pieces of LOB data from the input. The LOB data page pointer was set incorrectly when the LOB data fits into one data page and it is not the first piece of the entire LOB input. As a result the loss of data occurred. DB2 code is fixed to set the LOB data page pointer correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64225 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 PM64225 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64225 DSNOFLMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOFLMP LISTEND UK80178 COVER LETTER END UK80179 COVER LETTER START PROBLEM DESCRIPTION(S): PM61736 - **************************************************************** * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of declared * * global temporary tables (DGTT) who employ * * partition-by-growth table spaces in Workfile * * database * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DSNUGACC+12F8 during DGTT * * application that uses a partition-by- * * growth workfile table space (PBG) * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** During a partition-growing insert into a DGTT which was residing in a partition-by-growth workfile table space, the 0C4 abend occurred because the insert driver module was looking at the old (pre-growth) OBDPSET structure while thinking that it was looking at the new (post-growth) one. Specifically, in the old OBDPSET, the OBDPSP2L array slot did not exist for the newly grown partition and therefore the module was looking at a memory contents that is unaccounted for. This made the module go to a wrong code path, which resulted in the aforementioned abend. Code has been changed to make sure that the OBDPSET structure is refreshed after growing a new partition, so that the insert driver module will have the latest structure at its disposal. Additional keywords: SQLPBG SQLDGTT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61736 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISGPI PM61736 DSNITLPE PM61736 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61736 DSNISGPI DSNITLPE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGPI DSNITLPE LISTEND UK80179 COVER LETTER END UK80180 COVER LETTER START PROBLEM DESCRIPTION(S): PM55092 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of RECOVER utility that restore system level * * backups. * **************************************************************** * PROBLEM DESCRIPTION: RECOVER with PARALLEL specified will * * serially restore objects when a * * System Level Backup on DASD is used * * as the recovery base. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 User ran RECOVER utility with parallel specified to restore a lot of objects from a SLB(System Level Backup) on dasd. These recoveries took longer than expected to complete because RECOVER didn't perform the restores of the objects in parallel. RECOVER utility was changed to support parallel restore when the recovery base is a system level backup on DASD. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM55092 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 PM55092 DSNUCBRT PM55092 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55092 DSNUCBMT DSNUCBRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBMT DSNUCBRT LISTEND UK80180 COVER LETTER END UK80192 COVER LETTER START PROBLEM DESCRIPTION(S): PM55998 - **************************************************************** * USERS AFFECTED: All DB2 V10 HDBAA10 users. * **************************************************************** * PROBLEM DESCRIPTION: 1. Sumlist entry storage may fill up * * before summary dump storage, resulting * * in truncated summary information. * * 2. Sumlist entries are not always * * merged together correctly to optimize * * the use of a limited number of entries. * * 3. The chaining of variable phb onto * * the hashed array slots, is incorrect * * making them all chain to anchor one. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. Increase the amount of storage to be used for summary list entries. 2. Merge contiguous storage requests into a single sumlist entry to conserve entry slots. 3. Correct the hashing calculation for the variable pool phb for both common and private phb addresses. none COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM55998 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNSVPL PM55998 DSNWDFDS PM55998 DSNWDLOD PM55998 DSNWDLSR PM55998 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM55998 DSNSVPL DSNWDFDS DSNWDLOD DSNWDLSR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNSVPL DSNWDFDS DSNWDLOD DSNWDLSR LISTEND UK80192 COVER LETTER END UK80230 COVER LETTER START PROBLEM DESCRIPTION(S): PM64111 - **************************************************************** * USERS AFFECTED: ALL DB2 10 for z/OS users of * * UPDATE SYMMETRIC VIEW * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE161 issued when * * UPDATE SYMMETRIC VIEW uses * * IN-list index access * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE161 is issued when UPDATE SYMMETRIC VIEW uses IN-list index access. A symmetric view is a view defined with the CHECK OPTION parameter. The problem can occur if the column in a predicate in the symmetric view is part of the index key, and IN-list access is chosen. The following example illustrates the failing case: CREATE TABLE A(COL1 INTEGER,COL2 INTEGER,COL3 CHAR(3)); CREATE INDEX A1 ON A(COL2,COL3); INSERT INTO A VALUES(0,3,'AAA'); CREATE VIEW VB AS (SELECT * FROM A WHERE COL2 = 3 ) 1 WITH LOCAL CHECK OPTION; UPDATE VB SET COL1 = 1 WHERE COL2 = 3 AND COL3 IN ('AAA','BBB','CCC','EEE'); When the above update uses IN-list index access, we may hit SQLCODE161. We should update 1 row. The code in DB2 has been modified to prevent SQLCODE161 from being issued for the case described above. Additional Keywords : SQLCODE161 SQLIN SQLUPDATE SQLVIEW COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64111 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM64111: See PM64111 APAR/PTF text for additional information about why a REBIND is necessary. PM64111 corrects a problem where SQLCODE -161 is issued incorrectly when UPDATE SYMMETRIC VIEW is used with IN-list 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 affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOJW PM64111 DSNXRUP2 PM64111 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64111 DSNXOJW DSNXRUP2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOJW DSNXRUP2 LISTEND UK80230 COVER LETTER END UK80234 COVER LETTER START PROBLEM DESCRIPTION(S): PM61731 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: When INSERT/UPDATE an XML document * * after a previous XML schema validation, * * the unvalidated XML document may be * * marked incorrectly as validated. * **************************************************************** * RECOMMENDATION: * **************************************************************** The residual XML schema validation information from the previous XML schema validation is not cleaned up. This causes the unvalidated XML document to be marked incorrectly as validated. For example, in DB2 V10 SELECT XMLXSROBJECTID(XMLCOL) FROM T1; XMLCOL in T1 is not assoicated with any XML schema, but the above SELECT statement might return a non zero schema id. The above DB2 9 and 10 for z/OS problem was fixed to clean up the residual XML schema validation information. Additional keywords: SQLXML XMLSCHEMA XMLINSERT XMLUPDATE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61731 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOIRT PM61731 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61731 DSNNOIRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOIRT LISTEND UK80234 COVER LETTER END UK80236 COVER LETTER START PROBLEM DESCRIPTION(S): PM61553 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 may occur in module * * DSNNOBXI offset300 when INSERT/LOAD/ * * UPDATE an XML documnt of zero length * * using Extensible Dynamic Binary XML * 1 * DB2 Client/Server Binary XML format * * (IBM defined binary XML format). * **************************************************************** * RECOMMENDATION: * **************************************************************** When INSERT/UPDATE/LOAD an XML document with zero length using IBM binary XML format, ABEND04E RC00E70005 may occur. DB2 code has been modified so that ABEND04E RC00E70005 will not occur for a zero length XML document. Instead, SQLCODE20465 will be issued. Additional keywords: XMLALL SQLXML SQLCODE20465 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61553 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOBXI PM61553 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61553 DSNNOBXI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOBXI LISTEND UK80236 COVER LETTER END UK80242 COVER LETTER START PROBLEM DESCRIPTION(S): PM66482 - **************************************************************** * USERS AFFECTED: Users of DB2 Coprocessor for DB2 10 for * * z/OS A10 * **************************************************************** * PROBLEM DESCRIPTION: DB2 Coprocessor abends with RC00C89029 * * when trying to convert error message, * * DSNH104I, from unicode to source CCSID * * when the buffer for token-list * * contains garbage. * **************************************************************** * RECOMMENDATION: * **************************************************************** For the following SQL statement that contains a syntax error: EXEC SQL UPDATE T1 , SET col1 = :hvs1; DSNH104I should be issued because the ',' is unexpected on the first line. 1 While processing the error message and when the buffer for token-list contains garbage, conversion error might occur which is causing the intentional 00C8C9029 abend when using the DB2 Coprocessor. PSW AT TIME OF ERROR 078D1001 9A8482A2 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=1A802000 OFFSET=000462A2 NAME=DSNHPSRV DATA AT PSW 1A84829C - 5810A1E0 0A0DA7F4 F939EBEC AR/GR 0: 97B4347A/00000000_0000000C 1: 00000000/00000000_8404E000 2: 00000000/00000000_00000072 3: 00000000/00000000_1AC689E4 4: 00000000/00000000_00000008 5: 00000000/00000000_0000000C 6: 00000000/00000000_0000000C 7: 00000000/00000000_1A9B8B6F 8: 00000000/C4E2D5C8_D3C9E2E3 9: 00000000/00000000_1A9B8A80 A: 00000000/00000000_1A8482F0 B: 00000000/00000000_1A9B8850 C: 00000000/00000000_1A9B62B0 D: 00000000/00000000_1A9B8850 E: 00000000/00000000_1A9B8B62 F: 00000000/00000000_00C89029 END OF SYMPTOM DUMP IEF450I PM58160 PC STEPPROC - ABEND=S04E U0000 REASON=00C89029 SMF000I PM58160 PC CCNDRVR 004E With the fix, the buffer for token-list will no longer contain garbage and the conversion error will no longer occur. Below is a sample of the expected DSNH104I message for the above SQL statement with the invalid syntax. DSNH104I DSNHPARS LINE xx COL yy ILLEGAL SYMBOL ",". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: . INCLUDE SET WHERE QUERYNO SKIP FOR Fix provided such that the proper error message, DSNH104I will be issued/printed instead of the intentional conversion error abend, ABEND04E RC00C89029. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66482 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHPARS PM66482 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66482 DSNHPARS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHPARS LISTEND UK80242 COVER LETTER END 1UK80259 COVER LETTER START PROBLEM DESCRIPTION(S): PM63638 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with * * USECURRENTLYCOMMITTED bind option. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C200B001 at DSNB1REL+0E1A * * while running an SELECT SQL statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** While running a SELECT SQL statement which is bound with Current Commit option, an ABEND04E RC00C200B1 at DSNB1REL+0E1A was issued when trying to free an overflow page. The abend occurs because the page to be freed is a wrong page. DB2 code was changed to set a correct page block when an overflow page is acquired to prevent unnecessary abend later. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63638 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIONX2 PM63638 DSNIOST2 PM63638 DSNIRNXT PM63638 DSNIRPRE PM63638 DSNISFRL PM63638 DSNISFS PM63638 DSNISFX2 PM63638 DSNISRID PM63638 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63638 DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNISFRL DSNISFS DSNISFX2 DSNISRID THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNISFRL DSNISFS DSNISFX2 DSNISRID LISTEND UK80259 COVER LETTER END UK80263 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM66570 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where a DB2/LUW Connect server * * with the connection concentrator enabled * * accesses a DB2 for z/OS server. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -904 with reason code 00D31052 * * is erroneously, and intermittently, * * returned by a DB2 for z/OS server. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote (DB2/LUW Connect server based) application commits its SQL work to a DB2 for z/OS server and then executes more SQL to the DB2 for z/OS server. An intermittent SQLCODE -904 00D31052 condition may be detected by the DB2 for z/OS server if the SQL refers (causes a hop) to yet another remote server. The erroneous detection of the 00D31052 condition may occur if the remote (adjacent) client is a DB2/LUW Connect server with the connection concentrator enabled. This kind of unique remote client system environment may open multiple connections that use the same application ID (or LUWID) for a single application accessing a DB2 for z/OS server. Therefore, if an existing connection, conn1 (for LUWID1), already exists to the DB2 server and a new connection, conn2 (with LUWID1), is established to the same DB2 server, a -904 00D31052 condition may be detected because a connection, conn1 (for LUWID1), already exists in DB2. DB2 SQLCODE -904 00D31052 detection processing has been changed to recognize that it's possible to have multiple connections that share the same application ID (or LUWID) when the remote (adjacent) client is a DB2/LUW Connect server with connection concentrator enabled. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66570 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTSET PM66570 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66570 DSNLTSET THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTSET LISTEND UK80263 COVER LETTER END 1UK80266 COVER LETTER START PROBLEM DESCRIPTION(S): PM63687 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of correlated query * * with in-list table (PLAN_TABLE ACCESSTYPE * * = 'IN') running in parallel. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4-00000004 in dsnxripe +1DEA * * may occur 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4-00000004 in dsnxripe +1DEA may occur 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. The problem occurs when processing the parent query block's parallel group and the IN-LIST table object. Following is an example of such failing query: WITH CTE AS (SELECT ..... FROM P1, PS1 WHERE P1.C1 = PS1.C2) SELECT ..... FROM P2, (SELECT CTE.* FROM CTE WHERE (DOUBLE(CTE.C3), DOUBLE(CTE.C4)) IN (SELECT P2.C3, PS2.C4 -- NOTE 2 FROM P2, PS2 WHERE P2.NC1 = PS2.C5 AND ( P2.C3 = ? -- NOTE 1 OR P2.C3 = ?) AND P2.C6 > ? AND CTE.C3 = P2.C3 AND CTE.C7 = PS2.C7 AND CTE.C6 = P2.C6) AND CTE.C3 IN (?,?,?,?,?,?,?,?,?,?,?) AND CTE.NC1 > ?) AS TAB2 ; NOTE 1: The predicate (P2.C3 = ? OR P2.C3 = ?) is replaced as the IN-LIST predicate (P2.C3 IN (?, ?)). Later on, this IN-LIST predicate will be transformed as IN-LIST table NOTE 2: This IN subquery is a correlated subquery DB2 is modified to process the IN-LIST table information in a correlated subquery correctly in such scenario. 1 Additional Keywords: PARALLELISM SQLPARALLELISM SQLSUBQUERY SQLCORRSUBQ SQLINLISTTABLE DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63687 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 PM63687 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63687 DSNXGPGR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGPGR LISTEND UK80266 COVER LETTER END UK80291 COVER LETTER START PROBLEM DESCRIPTION(S): PM65871 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of IFCID 361 * * and UNICODE tracing. * **************************************************************** * PROBLEM DESCRIPTION: The command text in the IFCID 361 * * trace record is not displayed correctly * * when traced in UNICODE. * **************************************************************** * RECOMMENDATION: * **************************************************************** When IFCID 361 trace is turned on and system parameter UIFCIDS is ON, the command text is not displayed correctly when commands are audited. This is because DB2 code did not take into consideration the length of the command text during 1 UNICODE conversion. DB2 code is updated to include the command text length during UNICODE conversion for IFCID 361 trace records. Additional keywords: IFCID361 UIFCIDS COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65871 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 PM65871 DSNUECM4 PM65871 DSNUVARS PM65871 DSNXACKP PM65871 DSNXAMAP PM65871 DSNXA02 PM65871 DSNZCMD1 PM65871 DSN9SCNP PM65871 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65871 DSNTDMI DSNUECM4 DSNUVARS DSNXACKP DSNXAMAP DSNXA02 DSNZCMD1 DSN9SCNP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTDMI DSNUECM4 DSNUVARS DSNXACKP DSNXAMAP DSNXA02 DSNZCMD1 DSN9SCNP LISTEND UK80291 COVER LETTER END UK80310 COVER LETTER START PROBLEM DESCRIPTION(S): PM65665 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of COPYTOCOPY utility. * **************************************************************** * PROBLEM DESCRIPTION: COPYTOCOPY failed with message * * MSGDSNU030I when the input COPY * * data set used 76 tape volumes. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a COPYTOCOPY utility on an input date set which used 76 tape volumes. COPYTOCOPY failed with message DSNU030I because 1 the size of the workarea holding the volser information is too small to hold all information for 76 or more tape volumes. COPYTOCOPY is changed to use a big enough workarea which can hold volser information for 255 tape volumes. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65665 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 PM65665 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65665 DSNUGQSV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGQSV LISTEND UK80310 COVER LETTER END UK80324 COVER LETTER START PROBLEM DESCRIPTION(S): PM64010 - **************************************************************** * USERS AFFECTED: Users of the RACF/DB2 Access Control * * Module (DSNXRXAC) * * * **************************************************************** * PROBLEM DESCRIPTION: XAPLPRIV values 229 (SUBPKAUTK) and * * 289 (ACNTLAUTU) are not supported by * * DSNXRXAC. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** XAPLPRIV value 289 (ACNTLAUTU) and XAPLPRIV value 229 (SUBPKAUTK) allow administrators to revoke privileges granted by others. DSNXRXAC does not support these XAPLPRIV values. DSNXRXAC has been changed to support XAPLPRIV values 289 (ACNTLAUTU) and 229 (SUBPKAUTK). COMPONENT: 5740-DRE00-HDREA10 APARS FIXED: PM64010 SPECIAL CONDITIONS: COPYRIGHT: 5740-DRE00 COPYRIGHT IBM CORP. 2006 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM EXIT: Installation of this PTF requires that you: 1 1. Verify that the exit options in the exit are set to values that are appropriate for your installation. 2. Assemble and link-edit the exit and place the load module into the APF-authorized DB2 exit load library. After you complete these steps, the RACF access control module will be initialized the next time the DB2 subsystem is started. Further information may be found in "RACF Access Control Module Guide" (SC19-2982). EXIT: Installation of this PTF requires that you: 1. Verify that the exit options in the exit are set to values that are appropriate for your installation. 2. Assemble and link-edit the exit and place the load module into the APF-authorized DB2 exit load library. After you complete these steps, the RACF access control module will be initialized the next time the DB2 subsystem is started. Further information may be found in "RACF Access Control Module Guide" (SC19-2982). EXIT: Installation of this PTF requires that you: 1. Verify that the exit options in the exit are set to values that are appropriate for your installation. 2. Assemble and link-edit the exit and place the load module into the APF-authorized DB2 exit load library. After you complete these steps, the RACF access control module will be initialized the next time the DB2 subsystem is started. Further information may be found in "RACF Access Control Module Guide" (SC19-2982). DOCUMENTATION: The "RACF Access Control Module Guide" (SC19-2982-01) is updated with the changes below. Chapter 14: RACF authorization checking reference - In the "Package Privileges" section, update SUBPKAUTK. 1 XAPLPRIV value: SUBPKAUTK Privcode 229 (x'E5') The user must have sufficient authority to: ------------------------------------------------------- | One of these resources: | In class: | ------------------------------------------------------- |DB2-subsystem.collection-ID.PACKADM | DSNADM | |The user has authority to collection-ID.| | | | | |DB2-subsystem.ACCESSCTRL | DSNADM | | | | |DB2-subsystem.SYSCTRL | DSNADM | |Bypass if Separate Security = Yes | | | | | |DB2-subsystem.SYSADM | DSNADM | |Bypass if Separate Security = Yes | | | | | |DB2-subsystem.SECADM | DSNADM | ------------------------------------------------------- - In the "System Privileges" section, add ACNTLAUTU. XAPLPRIV value: ACNTLAUTU Privcode 289 (x'121') The user must have sufficient authority to: ------------------------------------------------------- | One of these resources: | In class: | ------------------------------------------------------- |DB2-subsystem.ACCESSCTRL | DSNADM | | | | |DB2-subsystem.SYSCTRL | DSNADM | |Bypass if Separate Security = Yes | | | | | |DB2-subsystem.SYSADM | DSNADM | |Bypass if Separate Security = Yes | | | | | |DB2-subsystem.SECADM | DSNADM | ------------------------------------------------------- DOCUMENTATION: The "RACF Access Control Module Guide" (SC19-2982-01) is updated with the changes below. Chapter 14: RACF authorization checking reference - In the "System privileges" section, the system DBADM authority is removed from the STOPALL (CHKSUBSU) and the "CANCEL | START |STOP DDF" (CHKDDFU, CHKSTARTU, CHKSTOPU) privilege set checks. - In the "Buffer Pool Privileges" section, the system DBADM authority is removed from the USE (USEAUTB) privilege. 1 - In the "Storage Group Privileges" section, the system DBADM authority is removed from the USE (USEAUTS) privilege. DOCUMENTATION: The "RACF Access Control Module Guide" (SC19-2982) is updated with the changes below. Chapter 5: Protecting DB2 Objects - table-qualifier.table-name.view-qualifier.view-name is added to the table "DB2 object name qualifiers for RACF resources" for views. Chapter 10: Special Considerations - A new section "Authorization checking for operations on views" is added. For most operations on views, the RACF access control module checks for authorization on the view. Authorization checking for INSERT, DELETE, and UPDATE are different because the operations on views can affect the underlying tables for the views. In general, three types of views can be defined: - Updatable view: For example, a view that is defined with simple column references in the SELECT list of the view definition, and a single table in the FROM clause of the view definition. An INSERT, DELETE, or UPDATE operation to the view is reflected to the underlying table. - Read-only view: For example, a view created from multiple tables. The INSERT, DELETE, and UPDATE operations fail for these views. - INSTEAD OF trigger view: The privilege is checked on the view, but the SQL in the trigger package can update the underlying table or tables. For INSERT, DELETE, and UPDATE operations on updatable views, the RACF access control module checks for authorization to resource name which includes both the underlying table information (qualifier and name) and view information (qualifier and name) and not to the view itself. For INSERT, DELETE, and UPDATE operations on read-only and INSTEAD OF trigger views, the RACF access control module checks for authorization on the view. 1 If a view is created on another view, during view creation the RACF access control module does authorization checks for INSERT, DELETE, and UPDATE. These checks are done on the base view. Chapter 14: The DELETE, INSERT, and UPDATE privilege for views is updated: - If the view is updatable (for example, a view created from a single table), then the ownership check is done on the base table only if SETR MLS is not in effect. - For a DELETE (DELETAUT) operation on an updateable view, the first resource name which is checked is now: - db2-subsystem.table-qualifier.table-name.view-qualifier. view-name.DELETE - For an INSERT (INSRTAUT) operation on an updateable view, the first resource name which is checked is now: - db2-subsystem.table-qualifier.table-name.view-qualifier. view-name.INSERT - For an UPDATE (UPDTEAUT) operation on an updateable view, the first and second resource names which are checked are now: - db2-subsystem.table-qualifier.table-name.view-qualifier. view-name.UPDATE - db2-subsystem.table-qualifier.table-name.column-name. view-qualifier.view-name.UPDATE For all of these resource names, the view and table information is truncated according to these rules: - table-qualifier and view-qualifier are truncated at 32 characters - Table-name and view-name are truncated at 64 characters. ACTION: The application of this PTF changes the RACF resources which are checked when a view is used in an INSERT, UPDATE, or DELETE operation. Application plans and packages that were bound with the RACF Access Control Module controlling access to views which are used for INSERT, UPDATE, or DELETE must be rebound. Details on the actions required can be found at: ftp://public.dhe.ibm.com/eserver/zseries/zos/racf/pdf /pm25823_act.pdf 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRXAC PM64010 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64010 DSNXRXAC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNXRXAC LISTEND UK80324 COVER LETTER END UK80349 COVER LETTER START PROBLEM DESCRIPTION(S): PM67612 - **************************************************************** * USERS AFFECTED: All users of DB2 Version 10.1 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: A canceled DB2 job remains suspended * * in the FRR in DSNJR007. The FORCE * * command must be used to terminate * * the job. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 job was canceled while suspended for an active log read IO request during restore to savepoint processing. A timing window in the cancel recovery path resulted in a SUSPEND in the DSNJR007 FRR that was never RESUMED. DSNJR007 has been changed to correct the cancel recovery problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67612 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 PM67612 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67612 DSNJR007 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJR007 LISTEND UK80349 COVER LETTER END 1UK80359 COVER LETTER START PROBLEM DESCRIPTION(S): PM65252 - **************************************************************** * USERS AFFECTED: DB2 V10 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C202AA in DSNB1PER in * * data sharing. * * * * ABEND04E RC00E50079 in DSNB1RRR (or in * * various other CSECTs), along with DB2 * * abnormal subsystem termination * * RC00E50054. * **************************************************************** * RECOMMENDATION: * **************************************************************** The ABEND04E RC00C202AA in DSNB1PER is due to a timing window in which multiple pageset control blocks may be built for the same object, leading to DB2 requesting multiple pageset P-locks with the same resource name. The ABEND04E RC00E50079 is due to a cancel window while an agent is holding a latch on one page while waiting for an I/O on another page. The latch recovery code incorrectly resets a tracking flag which indicates that the buffer manager ROB is in an "indoubt" state, which allows the ROB to be freed by agent deallocation. When the I/O is complete the ROB will be resumed and an abend may result because the ROB has been freed. The exposure to multiple pageset control blocks for the same object has been eliminated. Code exists in two modules which determines whether an existing block can be updated or must be replaced based on attributes changing, and this checking has been made consistent. The page latch recovery routine has been modified to no longer invalidly reset the "buffer manager ROB indoubt" tracking flag. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65252 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1OFA PM65252 DSNB1RTR PM65252 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65252 DSNB1OFA DSNB1RTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1OFA DSNB1RTR LISTEND 1UK80359 COVER LETTER END UK80363 COVER LETTER START PROBLEM DESCRIPTION(S): PM61093 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who use * * EDITPROCS together with HASH organized * * tables. * **************************************************************** * PROBLEM DESCRIPTION: When trying to locate a row for a * * HASH organized table, the encoded * * record was being used resulting in * * incorrect output. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a HASH organized table the row in question was retrieved from the page and decoded with the EDITPROC. However, DB2 continued using the encoded record for its filtering criteria resulting in not finding rows and incorrect outputs. ADDITIONAL KEYWORDS: INCORROUT SQLINCORROUT Code has been changed so that after the record is decoded, the decoded record is used in the filtering criteria, instead of the encoded record. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61093 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIACCH PM61093 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61093 DSNIACCH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIACCH LISTEND UK80363 COVER LETTER END UK80364 COVER LETTER START PROBLEM DESCRIPTION(S): PM67988 - **************************************************************** * USERS AFFECTED: All users of the -DISPLAY THREAD command * * in a data-sharing environment. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00F9000C in CSECT * * DSN9SCNP may occur after issuing a * 1 * -DISPLAY THREAD SCOPE(GROUP) TYPE(*) * * command that does not request * * unlimited output via the LIMIT(*) * * keyword. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a data-sharing environment with 3 or more members, -DISPLAY THREAD output from a remote member may be truncated due to the LIMIT keyword. If this output is followed by a remote member with no threads to display, the DSNV433I message may incorrectly be marked as a multi-line WTO message. This results in an abend in DSN9SCNP when validating multi-line WTO message chains. After message chain truncation due to the LIMIT keyword, all state variables will be reset such that additional messages will be properly formatted. This will prevent an ABEND04E RC00F9000C upon issuing -DISPLAY THREAD SCOPE(GROUP) TYPE(*). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67988 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: In version 10 coexistence mode, all active version 8 and version 9 members MUST apply this APAR before any version 10 member with this APAR applied is restarted. If not applied properly, -DISPLAY THREAD SCOPE(GROUP) commands will not return valid data from remote version 8 and version 9 members which may result in a large amount of invalid output on the version 10 member. In addition, an ABEND0C4 in CSECT DSNVDTT may be encountered on the version 10 member. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNVDTT PM67988 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67988 DSNVDTT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNVDTT LISTEND UK80364 COVER LETTER END UK80366 COVER LETTER START PROBLEM DESCRIPTION(S): PM66611 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of pair-wise join query. * **************************************************************** * PROBLEM DESCRIPTION: The pair-wise join query thread * 1 * may not be able cancelled when one * * of the pair-wise join leg returns * * sqlcode error (i.e. sqlcode = -904) * * and one of the pair-wise join leg is * * suspended when the sqlcode error is * * returned. * **************************************************************** * RECOMMENDATION: * **************************************************************** The pair-wise join query thread may not be able cancelled when one of the pair-wise join leg returns sqlcode error (i.e. sqlcode = -904) and one of the pair-wise join leg is suspended when the sqlcode error is returned. It is because when one of the pair-wise join leg returns sqlcode error, the suspended leg can not be resumed successfully. This problem could happen in any pair-wise join query. DB2 is modified to handle the pair-wise join sqlcode error returns correctly. Additional Keywords: SQLPAIRWISEJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66611 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 PM66611 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66611 DSNXRPJP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPJP LISTEND UK80366 COVER LETTER END UK80384 COVER LETTER START PROBLEM DESCRIPTION(S): PM66957 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RSN00E70005 may occur in * * module DSN3AUCN when DB2 is started * * with ACCESS(MAINT). * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RSN00E70005 may occur in module DSN3AUCN when DB2 1 for z/OS is started with ACCESS(MAINT). DB2 attachments, for example CICS and IMS Attachment, which request limited connection processing may encounter this ABEND if the trace data area contains residual information. RC00E70005 RSN00E70005 Module DSN3AUCN has been updated to initialize the trace data area. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66957 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3AUCN PM66957 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66957 DSN3AUCN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3AUCN LISTEND UK80384 COVER LETTER END UK80387 COVER LETTER START PROBLEM DESCRIPTION(S): PM65771 - **************************************************************** * USERS AFFECTED: All DB2 users of CP query parallelism. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 IN DSNTTRUN +1B7A * **************************************************************** * RECOMMENDATION: * **************************************************************** A parent task cancel occurred while a parallel task was in the middle of clean-up processing. This caused some internal control blocks of the parallel task to be freed earlier than expected, leading to the symptom ABEND. DB2 code has been corrected to not free the internal control block noted above, even when the parent task is cancelled during clean-up processing. Additional Keywords: SQLPARALLELISM SQLCPUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65771 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTTNO3 PM65771 DSNTTREB PM65771 1 DSNTTTGE PM65771 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65771 DSNTTNO3 DSNTTREB DSNTTTGE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTTNO3 DSNTTREB DSNTTTGE LISTEND UK80387 COVER LETTER END UK80389 COVER LETTER START PROBLEM DESCRIPTION(S): PM63596 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (NFM) users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNOMAPX ERQUAL5007 * * while trying to access DSNDB01.SYSDBDXA * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 in DSNOMAPX with ERQUAL5007 was encountered during select from a user table. As part of internal processing, this select was accessing information from the Directory LOB table space DSNDB01.SYSDBDXA, however the abend then occurred because DSNDB01.SYSDBDXA was being accessed without a necessary internal structure built for it. Investigation showed that during data space manager reset of a user-defined page set that had occurred during a LOAD utility run earlier, the directory LOB table space had gone through physical open without building the internal structure when one should have been built. The reason the structure was not built at that juncture was that a relevant input flag was passed to the DMBA component as off when it should have been on. This meant that the header page for DSNDB01.SYSDBDXA would not be accessed and the internal structure not built. Note that in the reported case the victim was a select against a user table but the abend is also possible during other operations that might need access to the Directory LOB table space. At the time of writing though, no case other than select has been reported. DB2 has been modified to turn on the appropriate DMBA input flag during physical open of the Director LOB object. Additional keywords: DB2LOB SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63596 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 DSNISELL PM63596 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63596 DSNISELL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISELL LISTEND UK80389 COVER LETTER END UK80407 COVER LETTER START PROBLEM DESCRIPTION(S): PM66042 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the XMLTABLE * * function when migrating from DB2 9 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * a query that contains a SELECT from * * XMLTABLE statement when migrated from * * DB2 9 for z/OS to DB2 10 for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result can be returned for a query that contains a SELECT from XMLTABLE statement when migrated from DB2 9 for z/OS to DB2 10 for z/OS. The following example illustrates the problem. 1. Create an application that contains the following SELECT from XMLTABLE statement on DB2 9 for z/OS. DECLARE V_IND CHAR(1) DEFAULT 'N'; SELECT DISTINCT Y.P_PWAInd INTO :V_IND FROM XMLTABLE( '//PWAInd' passing XMLPARSE('B') COLUMNS P_PWAInd CHAR(1) PATH '.' ) AS Y ; 2. Migrate the application to DB2 10 for z/OS. Now, when the application is executed on DB2 10 for z/OS, a DB2 internal structure might contain some residual information so 1 that an incorrect value might be returned. In this case, DB2 returns "row not found" but a value of 'B' is expected. Please note. 1. Depending on the residual value inside the internal structure, DB2 might ABEND instead of returning an incorrect result. 2. The incorrect result or possible ABEND problem can be resolved if the pre-v10 bound package is rebound on DB2 10 for z/OS. The code in DB2 has been modified to return a correct result for a query that contains a SELECT from XMLTABLE statement when migrated from DB2 9 to DB2 10 for z/OS. Additional Keywords: SQLXMLTABLE SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66042 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEBR9 PM66042 DSNXRDWC PM66042 DSNXRDW9 PM66042 DSNXREO9 PM66042 DSNXRFF9 PM66042 DSNXRFJ9 PM66042 DSNXRFN9 PM66042 DSNXRGB9 PM66042 DSNXROJ9 PM66042 DSNXRRC9 PM66042 DSNXRRI9 PM66042 DSNXRSG9 PM66042 DSNXRSJ9 PM66042 DSNXRSN9 PM66042 DSNXRSTD PM66042 DSNXRT19 PM66042 DSNXRT39 PM66042 DSNXRUWC PM66042 DSNXRUW9 PM66042 DSNXSBUC PM66042 DSNXSIFF PM66042 DSNXSIFG PM66042 DSNXSIND PM66042 DSNXSINE PM66042 DSNXSING PM66042 DSNXSZK PM66042 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66042 DSNXEBR9 DSNXRDWC DSNXRDW9 DSNXREO9 DSNXRFF9 DSNXRFJ9 DSNXRFN9 DSNXRGB9 DSNXROJ9 DSNXRRC9 DSNXRRI9 DSNXRSG9 DSNXRSJ9 DSNXRSN9 DSNXRSTD DSNXRT19 DSNXRT39 DSNXRUWC DSNXRUW9 DSNXSBUC DSNXSIFF DSNXSIFG DSNXSIND DSNXSINE DSNXSING DSNXSZK 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEBR9 DSNXRDWC DSNXRDW9 DSNXREO9 DSNXRFF9 DSNXRFJ9 DSNXRFN9 DSNXRGB9 DSNXROJ9 DSNXRRC9 DSNXRRI9 DSNXRSG9 DSNXRSJ9 DSNXRSN9 DSNXRSTD DSNXRT19 DSNXRT39 DSNXRUWC DSNXRUW9 DSNXSBUC DSNXSIFF DSNXSIFG DSNXSIND DSNXSINE DSNXSING DSNXSZK LISTEND UK80407 COVER LETTER END UK80412 COVER LETTER START PROBLEM DESCRIPTION(S): PM65883 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries * * involving push down (or pushed down) * * predicates. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at location * * DSNKMVKY:5004 (ERQUAL5004) or at * * location DSNIMSAR:1001 (ERQUAL1001) can * * occur when a query contains a push down * * (or pushed down) predicate. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 at location DSNKMVKY:5004 (ERQUAL5004) or at location DSNIMSAR:1001 (ERQUAL1001) can occur when a query containing a predicate which involves a CCSID cast is pushed down to the Index Manager or Data Manager subcomponents for evaluation. 1 Please note that the PUSHDOWN column of the DSN_FILTER_TABLE (an EXPLAIN table) shows whether the predicate is "pushed down" to the Index Manager or Data Manager subcomponents for evaluation. The code in DB2 was modified to not push down predicates for queries involving a CCSID cast to prevent the above abends. Additional Keywords: SQLPREDPUSHDOWN SQLCCSID SQLCAST COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65883 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM65883 APAR/PTF text for additional information about why a REBIND is necessary. PM65883 prevents abend which might occur when a query involves push down 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: See PM63440 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM63440 corrects problems that can cause abend for a query with range list index scan. 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 DSNXOPB PM65883 DSNXORES PM65883 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65883 DSNXOPB DSNXORES THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPB DSNXORES LISTEND UK80412 COVER LETTER END UK80413 COVER LETTER START PROBLEM DESCRIPTION(S): PM66091 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of COPYTOCOPY * * utility. * **************************************************************** * PROBLEM DESCRIPTION: 1.ABEND04E RC00E40070 with message * * MSGDSNU030I during COPYTOCOPY * * FROMLASTFULLCOPY on more than 33 * * table spaces. * * 2.ABEND0E0 RC00000028 during COPYTOCOPY * * FROMLASTFULLCOPY on more than 1042 * * table spaces. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** 1.User ran COPYTOCOPY utility with FROMLASTFULLCOPY on more than 33 table spaces and received ABEND04E RC00E40070 and MSGDSNU030I. 2.User ran COPYTOCOPY utility with FROMLASTFULLCOPY on more than 1042 table spaces and received ABEND0E0 RC00000028. Both problems were caused by an overlay of storage due to incorrect logic in COPYTOCOPY code. COPYTOCOPY utility is modified to avoid storage overlays. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66091 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNU2ASR PM66091 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66091 DSNU2ASR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNU2ASR LISTEND UK80413 COVER LETTER END UK80459 COVER LETTER START PROBLEM DESCRIPTION(S): PM60933 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * workfiles (e.g. during sort) * **************************************************************** * PROBLEM DESCRIPTION: RC00C90085 encountered during large * * sort (in an SQL query) even though * * there was plenty of space in workfile * * table spaces left * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** During query execution that involves a large sort, DB2 issued reason code 00C90085, implying that there was no space left in workfile table space. However, this was done even though there was plenty of space left. DB2 issues this reason code due to internal reasons: when it internally tries to break up a large logical workfile into over 255 internal extensions, each one represented by a separate internal CUB structure. DB2 does this kind of workfile breakup when a single workfile table space (even at its typical 2 GB limit - e.g. PRIQTY 2096512 SECQTY 0 for a 32K page size table space) is not sufficient to house such a big logical workfile. In the reported case, DB2 issued 00C90085 at a 115 GB workfile space usage mark, even though there were several hundred GB available in 200+ workfile table spaces. Based on internal workfile table space usage counts, DB2 tried tried to place the entire logical workfile in only a subset of the available table spaces, which kept creating the aforementioned internal extensions, leading to the 255 internal limit being reached prematurely. For workfiles that start spanning multiple workfile table spaces, code has been changed to ensure that all available workfile table spaces get a chance to be used equally, thus lowering the chance of failing with 00C90085. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60933 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBWAC PM60933 DSNIGWAC PM60933 DSNISEGD PM60933 DSNISEGF PM60933 DSNISGAU PM60933 DSNISGNS PM60933 DSNITNPG PM60933 DSNXSMRE PM60933 DSNXSMRG PM60933 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60933 DSNIBWAC DSNIGWAC DSNISEGD DSNISEGF DSNISGAU DSNISGNS DSNITNPG DSNXSMRE DSNXSMRG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBWAC DSNIGWAC DSNISEGD 1 DSNISEGF DSNISGAU DSNISGNS DSNITNPG DSNXSMRE DSNXSMRG LISTEND UK80459 COVER LETTER END UK80464 COVER LETTER START PROBLEM DESCRIPTION(S): PM68131 - **************************************************************** * USERS AFFECTED: All users of DB2 for z/OS Explain table * * DSN_DETCOST_TABLE * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC10 in DSNXOD7+09E4 may occur * * when running Explain on a query * * containing a very large number of * * tables and DSN_DETCOST_TABLE is defined * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC10 in DSNXOD7+09E4 may occur when running Explain on a query containing a very large number of tables and Explain table DSN_DETCOST_TABLE is defined. Indexing into an array used for DSN_DETCOST_TABLE can go out of bounds when there are a large number of tables in the query. Additional Keywords: SQLEXPLAIN Code is updated to correct the indexing into the affected array. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68131 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOD7 PM68131 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68131 DSNXOD7 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOD7 LISTEND UK80464 COVER LETTER END UK80472 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM63125 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and 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: PM63125 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGLGR PM63125 DSNUGSUU PM63125 DSNURLOG PM63125 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63125 DSNUGLGR DSNUGSUU DSNURLOG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGLGR DSNUGSUU DSNURLOG LISTEND UK80472 COVER LETTER END UK80474 COVER LETTER START PROBLEM DESCRIPTION(S): PM59847 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: DB2 10 for z/OS problems related with * * XML: * * 1. Space in the XML table space is * * not reused because rows for * * unneeded XML versions are not * * deleted efficiently. * * * * 2. ABEND04E RC00E70005 * * in DSNNOPMV M100 while * * executing an SQL UPDATE on a * * row with an XML column. * * * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** 1. After an SQL statement updates or deletes an XML column that supports multiple XML versions, rows for old versions of the XML document still exist in the XML table space. When the rows for the old versions of the XML document are no longer needed, a background task in DB2 deletes these rows. The background task uses the Node ID index to find the rows that can be deleted. The logic used to find the rows to be deleted needed to be corrected to avoid unnecessary scans using the Node ID index. 2. The ABEND04E RC00E70005 DSNNXML.DSNNOPMV:M100 occurred when executing an SQL UPDATE statement on a row with an XML column. For the problem to occur, the table must be in a partitioned table space, and the SQL UPDATE must update a column that causes the row to be moved to another partition. The ABEND04E occurred because a control block needed to move rows in the XML table space to another partition was not created correctly. To delete rows in the XML table space more efficiently, the logic used by the background task was modified. To fix the ABEND04E RC00E70005 in DSNNOPMV M100, the logic for moving XML documents to different partitions was modified. Additional keywords: SQLXML XMLALL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM59847 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 PM59847 DSNNOPMV PM59847 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM59847 DSNNOCLN DSNNOPMV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOCLN DSNNOPMV LISTEND UK80474 COVER LETTER END UK80506 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM68810 - **************************************************************** * USERS AFFECTED: All IRLM users (IRLM 2.1, 2.2 and 2.3) * * running with IMS in data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: IRLM ABENDU2019 RC05 in DXRRL200 or * * ABENDU2027 in DXRRL150, right after * * IRLM lock structure rebuild completes. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IMS issues lock requests with FORCE attribute to cause modify locks held by that owning work-unit to be sent to XES to build record list entries. Some of the lock requests sent to XES may complete asynchronously and if so, the original lock request gets suspended in IRLM to be resumed by the last XES Complete event exit drive for this request. There is a small timing window where a lock structure rebuild could occur before that IMS lock request is resumed. This may result in IRLM having the same request QE, queued twice. If this happens, either of these two abends may occur after the structure rebuild completes. This additional resume by IRLM may try to free a queue element which has already been freed, ending in ABENDu2019 in DXRRL200 or ABENDU2027 in DXRRL150 when the second resume finds incorrect bits set. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM68810 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL2T0 PM68810 DXRRL754 PM68810 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68810 DXRRL2T0 DXRRL754 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL2T0 DXRRL754 LISTEND UK80506 COVER LETTER END UK80559 COVER LETTER START PROBLEM DESCRIPTION(S): PM68678 - **************************************************************** * USERS AFFECTED: All users of DB2 Data Sharing * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 IN DSNIBHIS+0DB6 DURING DB2 * 1 * GROUP RESTART * **************************************************************** * RECOMMENDATION: * **************************************************************** During the peer restart, for some unknown reason, Data Base Restart Table (DBRT) entry for the Unit of Recovery (UR) object was corrupted which results in program exception failure which abnormally terminates DB2 member. The reason for a one bit overlay is unknown at this time. However, this apar will avoid bringing down DB2 member because of the address of one of the DBRT objects was corrupted. The objective is to isolate the object and keep the DB2 up. DB2 restart logic is modified to avoid termination of DB2 member due to program exception failures. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68678 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBHIS PM68678 DSNICLPA PM68678 DSNICLTO PM68678 DSNIECUR PM68678 DSNIERST PM68678 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68678 DSNIBHIS DSNICLPA DSNICLTO DSNIECUR DSNIERST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBHIS DSNICLPA DSNICLTO DSNIECUR DSNIERST LISTEND UK80559 COVER LETTER END UK80577 COVER LETTER START PROBLEM DESCRIPTION(S): PM61872 - **************************************************************** * USERS AFFECTED: DB2 V10 users of stored procedures or * * User Defined Functions (UDFs). * **************************************************************** * PROBLEM DESCRIPTION: In DB2 V10, when stored procedure hits * * ASUTIME limit or gets detached, * * the DDF thread that runs * * the stored procedure gets the following * * abend: * * ABND=04E-00D30002 , * 1 * LOC=DSNLDTML.DSNLAGNT+2642 * **************************************************************** * RECOMMENDATION: * **************************************************************** If the stored procedure that goes outbound to a remote server is detached in the middle of execution, DB2 recovery is expected to issue an re-abend so that the DDF recovery can handle the failure. However, DB2 recovery doesn't re-abend if the abend code is '33E'x and therefore, DDF recovery cannot process the abend properly and that results in the later ABEND04E-00D30002. DB2 code has been changed to issue re-abend if the stored procedure that goes outbound DDF gets detached in the middle of execution. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM61872 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 PM61872 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM61872 DSNX9WCA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9WCA LISTEND UK80577 COVER LETTER END UK80612 COVER LETTER START PROBLEM DESCRIPTION(S): PM66958 - **************************************************************** * USERS AFFECTED: All users of IFCID148 on DB2 10 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: IFCID148 record may have incorrect * * values in the DSNDQLAC section for * * DDF/RRSAF rollup records. * **************************************************************** * RECOMMENDATION: * **************************************************************** For DDF/RRSAF IFCID148 records, QLAC counters are not transferred to the record. All QLAC counters are now correctly externalized for DDF/RRSAF rollup IFCID148 records. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66958 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 DSNDQWHS PM66958 DSNWAACT PM66958 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66958 DSNDQWHS DSNWAACT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWAACT MACROS DSNDQWHS LISTEND UK80612 COVER LETTER END UK80613 COVER LETTER START PROBLEM DESCRIPTION(S): PM64631 - **************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNB5GGP * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 logic to de-register a page unnecessarily access a page set level control block. The access causes an 0C4 abend because the page set the de-registered page belongs to may already be closed and its control block is freed. DB2 page de-registration logic has been modified to not access the page set level control block. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64631 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5GGP PM64631 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64631 DSNB5GGP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB5GGP LISTEND UK80613 COVER LETTER END 1UK80614 COVER LETTER START PROBLEM DESCRIPTION(S): PM67434 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of OLAP * * specifications * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXGRDS * * DSNXGSAF M110 occurs for an SQL * * statement with an OLAP specification * * using both RANGE and ROWS options * **************************************************************** * RECOMMENDATION: * **************************************************************** The abend occurs if all of the following are true: - there are two OLAP specifications in the same SQL statement - the OLAP specifications use the same window specification - one OLAP specification use the ROWS option and the other uses the RANGE option. The window specification is the same if the PARTITION BY and ORDER BY clauses are the same. For example the following SQL abends : CREATE TABLE T1 (C1 INT, C2 DATE,C3 INT); SELECT C3,C2,C1, SUM(C1) OVER(PARTITION BY C3 ORDER BY C2 ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING), AVG(C1) OVER(PARTITION BY C3 ORDER BY C2 RANGE BETWEEN 00000002. PRECEDING AND CURRENT ROW) FROM T1; DB2 has been fixed to handle ROWS and RANGE with the same window specification. The SQL no longer abends. Additional keywords : SQLOLAP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67434 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGSAF PM67434 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67434 DSNXGSAF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSAF LISTEND 1UK80614 COVER LETTER END UK80615 COVER LETTER START PROBLEM DESCRIPTION(S): PM65113 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS installation * * job DSNTIJSG are affected by this change. * **************************************************************** * PROBLEM DESCRIPTION: DSNTIJSG terminates with return code 8 * * in job step DSNTIJQ due to message * * DSNT408I SQLCODE = -204, ERROR: * * DSNOPTDB IS AN UNDEFINED * * NAME * * when attempting to create tables: * * SYSIBM.DSN_COLDIST_TABLE * * SYSIBM.DSN_KEYTGTDIST_TABLE * **************************************************************** * RECOMMENDATION: Apply the fixing PTF * **************************************************************** Job DSNTIJSG is used to bind the packages and plans and create user-maintained databases for various DB2-supplied facilities. Job step DSNTIJQ creates the DB2 query optimization database, a collection of system profile and explain tables, in the SYSIBM schema. When run in MIGRATE mode, the DB2 installation CLIST assumes that this database exists in the previous release, and therefore edits job step DSNTIJQ so that it will create only two tables (SYSIBM.DSN_COLDIST_TABLE and SYSIBM.DSN_KEYTGTDIST_TABLE) that were added in V10. The CLIST also adds comments that describe how to easily modify DSNTIJQ to create all of the tables. Currently, when edited for migration, job step DSNTIJQ will terminate with return code 8 due to SQLCODE -204 and message DSNT408I DSNOPTDB IS AN UNDEFINED NAME. This error occurs because the CREATE TABLE statements for the two new tables specify a non-existent database (DSNOPTDB) and table space (DSNOPTT8). In response, this APAR modifies the DB2 installation CLIST and job DSNTIJSG so that job step DSNTIJQ will create the missing database and table space before creating the two new tables. DSNTIJQ will also create a DB2 stogroup, DSNOPTSG, to contain the new table space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65113 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM65113 (V10) This PTF modifies the DB2 installation CLIST and job DSNTIJSG 1 to prevent job step job DSNTIJQ from failing due to SQLCODE -204 when DSNTIJSG is customized in MIGRATE mode. 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) Update customized copies of job DSNTIJSG 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 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 job DSNTIJSG *********************************************************** * This action is required only if you ran the DB2 V10 * installation CLIST in MIGRATE mode *********************************************************** This PTF modifies DSNTIJSG in the prefix.SDSNSAMP library only. After applying it, edit your customized copy of DSNTIJSG and update job step DSNTIJQ as follows: (a) Locate and change these lines: //SYSIN DD DDNAME=DUMMY //* DD DDNAME=CLEANUP //* DD DDNAME=CREATE // DD DDNAME=CREATENT //DUMMY DD * to: //SYSIN DD DDNAME=DUMMY //* DD DDNAME=CLEANUP // DD DDNAME=CREATE //* DD DDNAME=CREATEPT // DD DDNAME=CREATENT //DUMMY DD * (b) Locate and change these lines: CREATE TABLESPACE DSNOPTTS IN DSNOPTDB LOCKSIZE ROW LOCKMAX SYSTEM CLOSE NO CCSID UNICODE USING STOGROUP DSNOPTSG; CREATE TABLESPACE DSNOPTT8 IN DSNOPTDB BUFFERPOOL BP8K0 LOCKSIZE ROW LOCKMAX SYSTEM CLOSE NO 1 CCSID UNICODE USING STOGROUP DSNOPTSG; to: CREATE TABLESPACE DSNOPTT8 IN DSNOPTDB BUFFERPOOL BP8K0 LOCKSIZE ROW LOCKMAX SYSTEM CLOSE NO CCSID UNICODE USING STOGROUP DSNOPTSG; //CREATEPT DD * CREATE TABLESPACE DSNOPTTS IN DSNOPTDB LOCKSIZE ROW LOCKMAX SYSTEM CLOSE NO CCSID UNICODE USING STOGROUP DSNOPTSG; (Notice that the order of the two CREATE TABLESPACE statements has been reversed). (c) Save your changes COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTIJSG PM65113 DSNTINS1 PM65113 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65113 DSNTIJSG DSNTINS1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTIJSG DSNTINS1 LISTEND UK80615 COVER LETTER END UK80616 COVER LETTER START PROBLEM DESCRIPTION(S): PM67136 - **************************************************************** * USERS AFFECTED: All non-data sharing DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: Issuing -DISPLAY GROUP command on * * non-data sharing DB2 subsystem running * * in new function mode (NFM) shows that * * locking protocol 3 (LP3), displayed as * * PROTOCOL LEVEL(3), is in effect. * **************************************************************** * RECOMMENDATION: * **************************************************************** Locking protocol 3 (LP3) support was deprecated in APAR PK62027 1 for data-sharing subsystems, but the support was not removed for non-data sharing subsystems. Running in LP3 does not cause problems as DB2 treats locking protocols higher than 2 as locking protocol 2. However, this does result in -DISPLAY GROUP command to show PROTOCOL LEVEL(3) is in effect for the non-data sharing subsystem running in new function mode. This APAR removes LP3 support for non-data sharing subsystems. DB2 has been modified to set locking protocol to 2 on non-data sharing subsystems. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67136 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTRSTE PM67136 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67136 DSNTRSTE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTRSTE LISTEND UK80616 COVER LETTER END UK80665 COVER LETTER START PROBLEM DESCRIPTION(S): PM68030 - **************************************************************** * USERS AFFECTED: All DB2 users * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNR035I UNCOMMITTED UR PLAN NAME * * DSNUTIL displayed on system console. * * It is associated with an add volume log * * record on a mapping table index from * * online REORG processing. * **************************************************************** * RECOMMENDATION: * **************************************************************** Writing an add volume log record on mapping table index under online REORG is not necessary because it is opened as non-recoverable page set. The code is changed to avoid writing any add volume log for the mapping table index during online REORG. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68030 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 DSNPADDV PM68030 DSNPXTN0 PM68030 DSNPXTRC PM68030 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68030 DSNPADDV DSNPXTN0 DSNPXTRC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNPADDV DSNPXTN0 DSNPXTRC LISTEND UK80665 COVER LETTER END UK80675 COVER LETTER START PROBLEM DESCRIPTION(S): PM66546 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users that are in * * Compatibility mode. * **************************************************************** * PROBLEM DESCRIPTION: In DB2 V10 Compatibility mode, * * a referential integrity check on the * * parent table failed with an ABEND 04E * * RC00C90101 in DSNIPSFI ERQUAL5020. * **************************************************************** * RECOMMENDATION: * **************************************************************** Improper checking of the Compatibility mode caused DB2 to skip acquiring a mass delete lock on the table. Later, a sanity check if holding a mass delete lock failed and this resulted in an abend. DB2 V10 has been corrected to properly check for the compatibility mode, so that the mass delete lock on the table will be acquired correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66546 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIPSFI PM66546 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66546 DSNIPSFI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIPSFI 1 LISTEND UK80675 COVER LETTER END UK80677 COVER LETTER START PROBLEM DESCRIPTION(S): PM68013 - **************************************************************** * USERS AFFECTED: All Version 10.1 users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00D1F001 in DSNJC005 * * processing an -ARCHIVE LOG command. * * The abend may also occur in module * * DSNJC007. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00D1F001 may be issued by module DSNJC005 or DSNJC007 processing an -ARCHIVE LOG command. The abends are being issued incorrectly when a non-zero buffer use count is detected and the log-write latch is not held. The -ARCHIVE LOG command modules have been changed to only verify the buffer use counts when the log-write latch is held. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68013 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJC005 PM68013 DSNJC007 PM68013 DSNJC05A PM68013 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68013 DSNJC005 DSNJC007 DSNJC05A THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJC005 DSNJC007 DSNJC05A LISTEND UK80677 COVER LETTER END UK80684 COVER LETTER START PROBLEM DESCRIPTION(S): PM63028 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of CHECK DATA * **************************************************************** 1 * PROBLEM DESCRIPTION: ABEND04E RC00C20305 DSNISRTI + x'2666' * * on DB2 9 for z/OS or XML data inserted * * to a wrong partition of the exception * * table on DB2 10 for z/OS during CHECK * * DATA with the FOR EXCEPTION option * * specified on a partitioned table space * * which contained a table with an XML * * column * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User was running CHECK DATA against a partitioned table space which contained a table with an XML column and a check constraint defined. The FOR EXCEPTION keyword specified the exception table which was also in a partitioned table space and contained an XML column. The ABEND04E RC00C20305 at DSNISRTI OFFSET2666 on DB2 9 for z/OS or XML data inserted to wrong partition of the exception XML table on DB2 10 for z/OS occurred as the partition number was not calculated correctly when CHECK DATA attempted to copy XML data into the exception table. The problem can also occur for partition-by-range (PBR) universal table spaces. CHECK DATA utility was changed to calculate the partition number correctly when copying XML data into the exception table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63028 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKRDY PM63028 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63028 DSNUKRDY THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKRDY LISTEND UK80684 COVER LETTER END UK80686 COVER LETTER START PROBLEM DESCRIPTION(S): PM66406 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of LOAD * * FORMAT SPANNED YES * **************************************************************** * PROBLEM DESCRIPTION: LOAD FORMAT SPANNED YES may issue * * message DSNU1256I incorrectly when * * loading XML data and end with RC8. * 1 **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LOAD FORMAT SPANNED YES into a table with an XML column incorrectly issued MSGDSNU1256I - VIRTUAL STORAGE REQUIRED FOR SPANNED RECORDS EXCEEDS DEFINED LIMIT. The LOAD job terminated with return code 8. The problem was intermittent and happened because the maximum virtual storage allowed for spanned records with XML data was not calculated correctly. LOAD utility was modified to calculate the storage limit correctly. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66406 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURELD PM66406 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66406 DSNURELD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURELD LISTEND UK80686 COVER LETTER END UK80701 COVER LETTER START PROBLEM DESCRIPTION(S): PM66948 - **************************************************************** * USERS AFFECTED: DB2 9 and DB2 10 for z/OS users of histogram * * statistics. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may produce an inaccurate filter * * factor estimation for a predicate if * * the predicate references a nullable * * column on which histogram statistics * * exist. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may produce an inaccurate filter factor estimation for a predicate if the predicate references a nullable column on which histogram statistics exist. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE FILTERFACTOR NULLABLE HISTOGRAM SQLSTATS Code has been modified to correct the filter factor estimation for the predicates described as above. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66948 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66948: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM66948 corrects a problem of inaccurate filter factor estimation for a predicate if the predicate references a nullable column on which histogram statistics exist. 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. PM49539 corrects an ABEND 0CF when incorrect internal values may be used to recalculate the filter factor of the related RANGE or BETWEEN predicates at execution time. The incorrect internal values may be saved by DB2 at BIND/PREPARE time if the package is bound with REOPT(AUTO), and one or more queries in the package contain RANGE or BETWEEN predicate(s). 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 DSNXODFB PM66948 DSNXODFE PM66948 DSNXODFR PM66948 DSNXODFT PM66948 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66948 DSNXODFB DSNXODFE DSNXODFR DSNXODFT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODFB DSNXODFE DSNXODFR DSNXODFT LISTEND UK80701 COVER LETTER END 1UK80772 COVER LETTER START PROBLEM DESCRIPTION(S): PM62052 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS * * parallelism users. * * * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -904 may occur when a select * * statement repeatedly runs in I/O * * parallelism. * * * * * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -904 may occur when a select statement repeatedly runs in I/O parallelism. DB2 did not clean up the workfiles correctly during the query run in I/O parallelism. The workfile database resources unavailable will happen if the query is repeatedly executed so many times and issue the SQLCODE -904. SOLUTION: DB2 has been fixed to clean up the workfiles correctly during the query runs in I/O parallelism,the -904 no longer occurs. Additional Keywords: SQLPARALLELISM SQLCODE904 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62052 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXPDST PM62052 DSNXRRC PM62052 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62052 DSNXPDST DSNXRRC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXPDST DSNXRRC LISTEND UK80772 COVER LETTER END UK80780 COVER LETTER START PROBLEM DESCRIPTION(S): PM67542 - 1 **************************************************************** * USERS AFFECTED: All DB2 users using buffer pools with * * AUTOSIZE(YES). * **************************************************************** * PROBLEM DESCRIPTION: When Workload Manager (WLM) notifies * * DB2 to adjust the size of a buffer pool * * multiple times within seconds, * * MSGDSNB555I message may show the same * * value for the old and new sizes. * **************************************************************** * RECOMMENDATION: * **************************************************************** When WLM notifies DB2 to alter the size of a buffer pool many times within seconds, WLM is likely to notify DB2 to make the same adjustment because WLM does not know that the previous request is not complete yet. Once the previous request is done, the next request of the same adjustment will cause MSGDSNB555I to show that the old and new sizes have the same value. DB2 has been fixed to suppress MSGDSNB555I message if the old and new sizes are the same. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67542 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 PM67542 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67542 DSNB1ABP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1ABP LISTEND UK80780 COVER LETTER END UK80787 COVER LETTER START PROBLEM DESCRIPTION(S): PM64287 - **************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: New function: enable enhanced restart * * token in castout * **************************************************************** * RECOMMENDATION: * **************************************************************** Using enhanced restart token can improve castout performance. DB2 castout logic has been modified to use enhanced restart token. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM64287 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5BPL PM64287 DSNB5PCO PM64287 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64287 DSNB5BPL DSNB5PCO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB5BPL DSNB5PCO LISTEND UK80787 COVER LETTER END UK80791 COVER LETTER START PROBLEM DESCRIPTION(S): PM65876 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users with a * * query that contains multiple table joins * * with over 510 columns put into a sort * * workfile. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E20001 at * * DSNXOSR.DSNSVSVB +01FC can occur for * * multiple table joins with over 510 * * columns put into an intermediate * * sort workfile. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E20001 at DSNXOSR.DSNSVSVB +01FC can occur for a query with multiple table joins with over 510 columns put into an intermediate sort workfile. The problems mentioned above are fixed. ADDITIONAL KEYWORDS: ABEND04E SQLJOIN SQLSMJ SQLMSJ SMJ MSJ. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65876 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM65876 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM65876 corrects problems that may cause a storage abend 1 with over 510 columns put into a sort workfile. 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 PM65289 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM65289 corrects problems that can cause abend for Hybrid join without cluster index, and lob column(s) is selected out. 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 PM57118: See PM57118 APAR/PTF text for additional information about why a REBIND is necessary. PM57118 corrects a problem of ABEND0C4 in DSNXOSRD may happen when running query with hybrid join on multiple 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 PM27253: See PM27253 APAR/PTF text for additional information about why a REBIND is necessary. PM27253 corrects a problem of an incorrect output for a query which contains a sideway reference predicate in a table expression and the table expression may contain UNION/ UNION ALL/ EXCEPT/EXCEPT ALL/INTERSECT/INTERSECT ALL in it 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. DB2BIND: ***Action for PM25378: See PM25378 APAR/PTF text for additional information about why a REBIND is necessary. PM25378 corrects a problem of A query may get incorrout (no row found) when there is sideway reference predicate in one leg of UNION/UNION ALL/EXCEPT/EXCEPT ALL/INTERSECT/INTERSECT ALL with parallelism enabled. 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 DSNXOGRL PM65876 DSNXOJW PM65876 DSNXOSR PM65876 DSNXOSRD PM65876 DSNXOWIN PM65876 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65876 DSNXOGRL DSNXOJW DSNXOSR DSNXOSRD DSNXOWIN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGRL DSNXOJW DSNXOSR DSNXOSRD DSNXOWIN LISTEND UK80791 COVER LETTER END UK80819 COVER LETTER START PROBLEM DESCRIPTION(S): PM64394 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the compress * * on INSERT feature. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIZLDR:5003 and * * ABENDS0C4 DSNUZLCR OFFSET2A76 during * * compress on INSERT. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** An ABEND04E RC00C90101 DSNIZLDR ERQUAL5003 occurred during compress on INSERT, in a data sharing environment, during the dictionary build processing. Analysis of the problem showed that the table space had been closed. Additional Symptom: ABEND0C4 DSNUZLCR +x'2A76' OFFSET2A76 Code has been modified to prevent the table space from being closed by requesting a CLAIM during the building of the dictionary which was driven by SQL INSERT processing (compress on INSERT). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64394 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 DSNUZLCR PM64394 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64394 DSNUZLCR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUZLCR LISTEND UK80819 COVER LETTER END UK80820 COVER LETTER START PROBLEM DESCRIPTION(S): PM64542 - **************************************************************** * USERS AFFECTED: All DB2 user of PBG table space in a work * * file database. * **************************************************************** * PROBLEM DESCRIPTION: For PBG table space in a work file * * database, when a new partition is * * created, a new row is inserted in * * SYSIBM.SYSCOPY with TYPE=A and STYPE=A. * * Since work file table space is not * * recoverable, there is no need to have * * SYSCOPY records for the work file and * * there is no way to remove these * * records. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a PBG table space of the work file database grows a new part, DB2 incorrectly inserts a SYSCOPY record which is never used later on. DB2 code has been changed to not insert SYSCOPY records when a work file PBG table space grows a new part. Applying this apar does not delete the SYSCOPY records which were already inserted. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64542 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDAPT PM64542 DSNGDART PM64542 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64542 DSNGDAPT DSNGDART 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDAPT DSNGDART LISTEND UK80820 COVER LETTER END UK80823 COVER LETTER START PROBLEM DESCRIPTION(S): PM66983 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who are also * * using IDAA ( IBM DB2 Analytics Accelerator ) * **************************************************************** * PROBLEM DESCRIPTION: (1) Query offload to an accelerator * * fails when a GROUP BY expression does * * not match the corresponding SELECT list * * expression. * * * * (2) Query offload to an accelerator * * fails when there are multiple views * * in a complex query. * **************************************************************** * RECOMMENDATION: * **************************************************************** (1) Query offload to an accelerator fails with SQLCODE -904 when a GROUP BY expression does not match the corresponding SELECT list expression. For example: SELECT 3+(C1+C2),C4 FROM T1 WHERE C3 >1 GROUP BY (C1+C2)+3,C4 ORDER BY 2,1; (2) Query offload to an accelerator fails with SQLCODE -901 when for a complex query with multiple views. Additional keywords: SQLCODE904 IDAAV2R1/K SQLGROUPBY SQLCODE901 SQLVIEW (1) The converted query text used for offload is fixed so that the GROUP BY expression matches the SELECT list expression. (2) The converted query text used for offload is fixed so that the complex query with multiple views executes successfully. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66983 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 DSNXONZC PM66983 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66983 DSNXONZC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXONZC LISTEND UK80823 COVER LETTER END UK80828 COVER LETTER START PROBLEM DESCRIPTION(S): PM67558 - **************************************************************** * USERS AFFECTED: DB2 user of real time statistics for * * last used information to SYSPACKAGE * **************************************************************** * PROBLEM DESCRIPTION: Customer may hit high CPU usage from * * real time statistics (RTS) * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 maintains a list of real time statistic (RTS) control blocks to keep track of package execution. The RTS service task periodically externalizes the last used information to the SYSPACKAGE table. If the table SYSPACKAGE is accessed by another job concurrently, updating the last used information may not be successful, as a result, the RTS control blocks can accumulate, which could cause high CPU usage. DB2 has been changed to purge RTS control blocks if the total number reach the threshold. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67558 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 PM67558 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67558 DSNGERTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGERTS LISTEND UK80828 COVER LETTER END 1UK80838 COVER LETTER START PROBLEM DESCRIPTION(S): PM66216 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of a native * * SQL procedure that contains a graphic string * * SQL statement used in a statement PREPARE or * * EXECUTE IMMEDIATE. * **************************************************************** * PROBLEM DESCRIPTION: 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** 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. An example is shown below: CREATE PROCEDURE SP1( OUT P1 VARGRAPHIC(10) CCSID UNICODE) APPLICATION ENCODING SCHEME UNICODE BEGIN DECLARE stmt1 VARGRAPHIC(100); DECLARE c1 CURSOR FOR s1; SET stmt1 = VARGRAPHIC('SELECT DBNAME FROM SYSIBM.SYSTABLES WHERE NAME = "SYSTABLES"'); PREPARE s1 FROM stmt1; OPEN c1; FETCH c1 INTO P1; CLOSE c1; END! DB2 did not correctly process the aforementioned SQL statement in graphic string, which caused the ABEND04E. DB2 has been modified to correctly process the aforementioned SQL statement in graphic string, so there will be no the ABEND04E. Additional keywords: SQLSP SQLSTOREDPROC SQLNATIVESQLPL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66216 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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. 1 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOYDA PM66216 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66216 DSNXOYDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOYDA LISTEND UK80838 COVER LETTER END UK80858 COVER LETTER START PROBLEM DESCRIPTION(S): PM69267 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: SQL Interrupt processing from remote * * client systems may fail if DB2 is * * associated to an IPv6 address. * **************************************************************** * RECOMMENDATION: * **************************************************************** In this case, DB2 operates in an environment where it is associated to an IPv6 address, and this is evident from a DSNL085I message of the DISPLAY DDF command report. Even though remote client systems connect to the DB2 for z/OS server via an IPv4 address, DB2 for z/OS incorrectly returns its IPv6 address as the address that the client system should use when/if it attempts to interrupt an SQL statement. If the client system does not operate in an environment that also supports IPv6, the client system will receive a communication error when it attempts to contact the DB2 for z/OS server (via the IPv6 address) for the purpose of interrupting an SQL statement that is actively executing at the DB2 for z/OS server. This prevents the SQL statement from being interrupted. The remote client application SQL statement will therefore incorrectly run to completion instead of receiving a -952 SQLCODE. DB2 has been changed to return an SQL interruption IP address that is consistent with the IP address that is being used by the client system when connecting to the DB2 for z/OS server. That is, if the client application connects to the DB2 for z/OS server via an IPv4 address, DB2 will return an SQL interrupt token that also refers to its IPv4 address. Similarly for IPv6. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM69267 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLTACC PM69267 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69267 DSNLTACC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLTACC LISTEND UK80858 COVER LETTER END UK80881 COVER LETTER START PROBLEM DESCRIPTION(S): PM67049 - **************************************************************** * USERS AFFECTED: ALL DB2 810, DB2 9 and DB2 10 for z/OS users * * of CALL statement. * **************************************************************** * PROBLEM DESCRIPTION: Memory leak of a DB2 internal * * structure could occur for CALL * * statements when the CALL statement is * * CALL unqualified procedure name. * **************************************************************** * RECOMMENDATION: * **************************************************************** Memory leak of a DB2 internal structure could occur for a CALL statement when the CALL statement is CALL unqualified procedure name. For this issue to manifest itself, more than one stored procedure with the same name under different schemas must exist. The following scenario illustrates how one could recreate the memory leak . 1.Stored procedures USR01.STP1 and USR02.STP1 created. 2.USRT001 is granted execute auth for USR02.STP1. 3.USRT001 running the SQL SET CURRENT PATH = USR01,USR02; and followed by CALL STP1; (with USRT001) will cause internal structure for USR01.STP1 to be orphaned. DB2 is updated to handle the CALL unqualified procedure name statement correctly to avoid the memory leak. Additional Keywords: SQLCALL SQLSP SQLSTOREDPROC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67049 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 DSNXOSTP PM67049 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67049 DSNXOSTP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSTP LISTEND UK80881 COVER LETTER END UK80900 COVER LETTER START PROBLEM DESCRIPTION(S): PM68695 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: A CPU spike may occur for a DB2 * * system TCB after an MVS cancel of * * a user thread. This increased CPU * * consumption will not be relieved * * until DB2 is restarted. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an MVS cancel occurs just after a thread has queued work to a DB2 service task, that service task may be resumed twice. The second resume occurs in execution unit switch recovery because it believes the resume for the work queued has not been issued. Once the work request is processed by the system TCB, it will bypass its suspend logic because of this second resume. It will attempt to dequeue a non-existent work request indefinitely. System TCB queue logic has been changed to tolerate a zero work queue. This should avoid the infinite attempt to dequeue a non-existent work request even when multiple resumes are issued against the task. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68695 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNVEUS3 PM68695 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68695 DSNVEUS3 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNVEUS3 LISTEND UK80900 COVER LETTER END UK80924 COVER LETTER START PROBLEM DESCRIPTION(S): PM62119 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of data definition control support. * **************************************************************** * PROBLEM DESCRIPTION: Starting DB2 may result in ABEND04E * * RC00E70014 DSNXGRDS.DSNXLDDL+2234 * * when definition control support is * * enabled and an error is encountered * * as a result of accessing a catalog * * index * **************************************************************** * RECOMMENDATION: * **************************************************************** Starting DB2 may result in ABEND04E RC00E70014 DSNXGRDS.DSNXLDDL+2234 when definition control support is enabled and an error is encountered as a result of accessing a catalog index. DB2 has been modified to tolerate errors instead of abending when an error is encountered when accessing catalog objects or resources. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62119 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXLDDL PM62119 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62119 DSNXLDDL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXLDDL LISTEND UK80924 COVER LETTER END UK80926 COVER LETTER START PROBLEM DESCRIPTION(S): PM66150 - **************************************************************** 1 * USERS AFFECTED: Users of DB2 9 for z/OS and DB2 10 for * * z/OS with data definition control enabled. * **************************************************************** * PROBLEM DESCRIPTION: REPAIR DBD may result in ABEND04E * * RC00E40601 DSNUEXDL+113C when * * the database contains a table * * with a check constraint and data * * definition control is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** REPAIR DBD may result in ABEND04E RC00E40601 DSNUEXDL+113C when the database contains a table with a check constraint and data definition control is enabled. REPAIR DBD has been modified to support databases which contain tables with check constraints when data definition control is enabled. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66150 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXI14 PM66150 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66150 DSNXI14 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXI14 LISTEND UK80926 COVER LETTER END UK80931 COVER LETTER START PROBLEM DESCRIPTION(S): PM67539 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (CM and above) users of * * created global temporary tables (CGTT) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E DSNSVBK RC00E20003 RC00E20004 * * on ADMF AGL 31 pool while running CGTT * * application * **************************************************************** * RECOMMENDATION: * **************************************************************** Storage leak may occur in the ADMF AGL 31 storage pool (CTLNGSTP) after continued runs of queries that use CGTTs. The leak involves the so-called P Procs or PProcs (predicate procs), new in V10 CM and higher, when they are built for CGTT. 1 The eyecatcher in the dump was 'SelP'. The particular reported case for this APAR involved the CGTT application going through bind or dynamic prepare processing. Even though a P Proc, as expected, was not built at bind time/ dynamic prepare time, a bit in the internal MSIB structure remained on by mistake through runtime, implying that it is OK to build the P Proc. However, P Procs are not supported for CGTTs as there is no freeing infrastructure in place for such cases. Code has been changed to ensure that the internal MSIB bit which affects P Proc building is not left on past bindtime/dynamic prepare time for CGTTs. In addition, code has been added for execution time (runtime) to ensure that P Procs are not built for CGTTs, so that a rebind is not necessary for this APAR to become effective. Additional keywords: DB2STGLK/K SQLCGTT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67539 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 PM67539 DSNXOMI PM67539 DSNXOMS PM67539 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67539 DSNIIMSI DSNXOMI DSNXOMS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIIMSI DSNXOMI DSNXOMS LISTEND UK80931 COVER LETTER END UK80983 COVER LETTER START PROBLEM DESCRIPTION(S): PM67568 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REPAIR VERSIONS TABLESPACE. * **************************************************************** * PROBLEM DESCRIPTION: A REPAIR DBD TEST DATABASE after a * * REPAIR VERSIONS TABLESPACE detected * * different oldest version from the * * catalog table and directory and issued * * MSGDSNU901I and MSGDSNU920I, then * 1 * ended with RC8. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A REPAIR VERSIONS utility ran on a non-partitioned table space after a DSN1COPY utility to update the oldest version in the catalog tables and directory. A subsequent REPAIR DBD TEST on the target database detected different oldest version from catalog and DBD, and issued message DSNU901I and DSNU920I - OBDS DIFFER AT OFFSET offset OBDPS_LOW_VER(1). This problem occurred because REPAIR VERSIONS skipped the update of the OLDEST_VERSION column of SYSTABLEPART for non-partitioned table spaces. This was because it was using an invalid part number to get the low version number from the DBD which led to the inconsistency between the catalog table and the directory. The REPAIR VERSIONS code has been modified to use a valid part number to get the low version number from the DBD. The correct low version number is now used to determine if it needs to update the OLDEST_VERSION column of SYSTABLEPART for a non-partitioned table space. This apar also corrects data version updating for the MODIFY RECOVERY utility on a non-partitioned table space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67568 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 PM67568 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67568 DSNUGUVR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGUVR LISTEND UK80983 COVER LETTER END UK80999 COVER LETTER START PROBLEM DESCRIPTION(S): PM70171 - **************************************************************** * USERS AFFECTED: All Version 10.1 users of DB2 for zOS. * **************************************************************** * PROBLEM DESCRIPTION: Active log status in the DSNJU004 * * output may display as: * * STATUS=NEW, NOTREUSABLE * * after becoming the current active log * * data set when the log data set has * 1 * been added to the BSDS log inventory * * with the -SET LOG NEWLOG command. * **************************************************************** * RECOMMENDATION: * **************************************************************** When new log data sets are formatted with DSNJLOGF and added to the BSDS inventory with the -SET LOG NEWLOG command, the DSNJU004 output may display the log status as STATUS=NEW, NOTREUSABLE when the new log data set becomes the current active log. Although this does not cause any processing problems within DB2, a request was received to remove the 'NEW' status in the BSDS when the active log becomes the current active log, which is consistent with new log data sets added with the DSNJU003 utility. DSNJW106 has been changed to correct the BSDS status for the new log data sets added by the -SET LOG NEWLOG command. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70171 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNJW106 PM70171 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70171 DSNJW106 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJW106 LISTEND UK80999 COVER LETTER END UK81022 COVER LETTER START PROBLEM DESCRIPTION(S): PM69270 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of pureXML. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXGRDS. * * DSNXRXML:P018 may occur when the * * following conditions are both true: * * 1. The query contains the COALESCE or * * VALUE function which has input * * expressions of XML datatype. * * 2. An XML function, such as XMLFOREST, * * is preceding the COALESCE or VALUE * * function. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 DSNXGRDS.DSNXRXML:P018 may occur when the 1 following conditions are both true: 1. The query contains the COALESCE or VALUE function which has input expressions of XML datatype. 2. An XML function, such as XMLFOREST, is preceding the COALESCE or VALUE function. For example: In the following query, there is a COALESCE function with the input expressions return XML datatype. There is an XMLFOREST function preceding the COALESCE function. SELECT XMLCONCAT( XMLFOREST(T1.DEPT AS "DEPT"), COALESCE( XMLELEMENT(NAME "FN", T1.FNAME OPTION NULL ON NULL), XMLELEMENT(NAME "FN", '?'))) FROM T1; When this query is run on DB2 V10, ABEND 04E-00E70005, LOC=DSNXGRDS.DSNXRXML:P018 will occur. DB2 is modified so the ABEND will not occur. Additional keywords: SQLXML XMLALL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69270 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRPUF PM69270 DSNXRXML PM69270 DSNXRXM9 PM69270 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69270 DSNXRPUF DSNXRXML DSNXRXM9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPUF DSNXRXML DSNXRXM9 LISTEND UK81022 COVER LETTER END UK81026 COVER LETTER START PROBLEM DESCRIPTION(S): PM67759 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of CHECK DATA utility * **************************************************************** 1 * PROBLEM DESCRIPTION: CHECK DATA SHRLEVEL CHANGE against a * * partitioned table space with * * referential constraint violations reset * * CHECK PENDING for the partitions * * without violations. * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran a CHECK DATA SHRLEVEL CHANGE utility against a partitioned table space which had referential constraint violations and was in a CHECK PENDING(CHKP) state. The CHECK DATA utility erroneously reset the CHKP status for the partitions without violations. CHECK DATA SHRLEVEL CHANGE operates on shadow copies and should not reset any pending states. CHECK DATA has been modified to avoid resetting CHKP during CHECK DATA SHRLEVEL CHANGE. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67759 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKNFK PM67759 DSNUKSCT PM67759 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67759 DSNUKNFK DSNUKSCT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKNFK DSNUKSCT LISTEND UK81026 COVER LETTER END UK81046 COVER LETTER START PROBLEM DESCRIPTION(S): PM69181 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries which * * contain a FETCH FIRST clause for GROUP BY * * and a column function with a floating-point * * argument. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result set can be returned * * for a query that contains a FETCH FIRST * * clause for GROUP BY and includes a * * column function with a floating-point * * argument. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** An incorrect result set can be returned for a query that contains a FETCH FIRST clause for GROUP BY and includes a column function with a floating-point column as an argument. The problem is caused by the conversion of the FLOAT column which can overlay storage following it by 4 bytes since the float conversion assumes the output length is 8 bytes. However, in some situations, the output length may only be 4 bytes. The problem has been masked for many releases of DB2 because the storage contents gets processed from left-to-right; the following columns or other sort information would have overwritten this area that would have been overlaid. But for the new processing of the FETCH FIRST for GROUP BY, this may not be the case because the latter area may be placed in the buffer ahead of the float conversion and could now be overlaid by the float conversion. DB2 has been modified to check the final output length of the float conversion and move the appropriate length. This will prevent the overlay from occurring. Additional Keywords: SQLGROUPBY SMCOVERLAY DB2OVRLAY/K SQLFLOAT SQLINCORR SQLINCORROUT DB2INCORR/K INCORROUT SQLFFNR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69181 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSIFG PM69181 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69181 DSNXSIFG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSIFG LISTEND UK81046 COVER LETTER END UK81047 COVER LETTER START PROBLEM DESCRIPTION(S): PM62797 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: Performance analysis often requires * * the aggregation of accounting data * * over an interval. Aggregating * 1 * accounting data for analysis is a * * manual, time consuming process. * **************************************************************** * RECOMMENDATION: * **************************************************************** Automated aggregation of accounting data is desired. New accounting aggregation functionality is introduced in this APAR giving DB2 the ability to aggregate accounting data into an IFC statistics record. To enable the new function, IFCID3 and IFCID369 must be enabled on the system. When both of these IFCIDs are ON, DB2 will aggregate QWAC and QWAX data for each transaction grouped by connection type. This statistics information will then be externalized in an IFCID369 at the statistics interval or via an IFCID READS call. It should be noted that the statistics interval for IFCID369 is fixed at 1 minute. A new statistics class 9 is created to encapsulate IFCID369. See DSNDQW05 macro for the mapping of IFCID369. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62797 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWAC PM62797 DSNDQWAX PM62797 DSNDQW05 PM62797 DSNTXSTA PM62797 DSNTXSTB PM62797 DSNWARDS PM62797 DSNWVCSP PM62797 DSNWVCST PM62797 DSNWVINT PM62797 DSNWVZCK PM62797 DSNWVZIT PM62797 DSNWVZPS PM62797 DSNWVZSA PM62797 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62797 DSNDQWAC DSNDQWAX DSNDQW05 DSNTXSTA DSNTXSTB DSNWARDS DSNWVCSP DSNWVCST DSNWVINT DSNWVZCK DSNWVZIT DSNWVZPS DSNWVZSA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXSTA DSNTXSTB DSNWARDS DSNWVCSP DSNWVCST DSNWVINT 1 DSNWVZCK DSNWVZIT DSNWVZPS DSNWVZSA MACROS DSNDQWAC DSNDQWAX DSNDQW05 LISTEND UK81047 COVER LETTER END UK81050 COVER LETTER START PROBLEM DESCRIPTION(S): PM66142 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E DSNNXML DSNNOLCK M220 * * or * * ABEND04E DSNNXML DSNNOLCK M230 * * * * occurred while executing a FETCH * * statement when there was an XML column * * in the SELECT list and the cursor was * * declared with WITH HOLD. * **************************************************************** * RECOMMENDATION: * **************************************************************** The ABEND04E DSNNXML.DSNNOLCK:M220 or the ABEND04E DSNNXML.DSNNOLCK:M230 occurs when an XML column is in the select list of a SELECT statement for a cursor declared with WITH HOLD. An ABEND occurs during the FETCH if a commit occurred after the cursor was opened. The problem does not occur if the XML column is an argument to a function. In the following example: DECLARE C1 CURSOR WITH HOLD FOR SELECT INT1, XML1 FROM T1 ORDER BY INT1 XML1 is the XML column in the select list. The problem is more likely to occur if the SELECT statement causes rows to be inserted into a workfile at OPEN cursor time. In the example, the ORDER BY clause could cause rows to be sorted into a workfile. The ABENDs occur because there was an error when acquiring an XML lock. The problem does not occur if the XML column supports multiple XML versions because the XML locks are not needed. DSNNOLCK was modified to fix the ABENDs. 1 Additional keywords: SQLXML XMLALL XMLLOCK SQLLOCK COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66142 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOLCK PM66142 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66142 DSNNOLCK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOLCK LISTEND UK81050 COVER LETTER END UK81051 COVER LETTER START PROBLEM DESCRIPTION(S): PM67892 - **************************************************************** * USERS AFFECTED: DB2 V10 CM8 users of built-in * * stored procedures: * * SQLJ.DB2_REPLACE_JAR * * SQLJ.REPLACE_JAR * **************************************************************** * PROBLEM DESCRIPTION: When SQLJ.DB2_REPLACE_JAR or * * SQLJ.REPLACE_JAR is invoked in * * DB2 V10 Compatibility Mode (CM) * * that is migrated from DB2 V8, * * the caller will get the following * * sqlcode and sqlerrmc: * * * * SQLCODE=-443, SQLSTATE=00000, * * SQLERRMC=DB2_REPLACE_JAR; * * DB2_REPLACE_JAR; * * M702 SQLCODE=-4700; * **************************************************************** * RECOMMENDATION: * **************************************************************** The authority check was enhanced in V9 for SQLJ.REPLACE_JAR and SQLJ.DB2_REPLACE_JAR. But the new authority check function is in V9 New Function Mode (NFM). That caused the sqlcode -4700 (SRCN4700) to be returned when the procedure is invoked in V10 CM if it is migrated from DB2 V8. The code for SQLJ.REPLACE_JAR and SQLJ.DB2_REPLACE_JAR is changed so that it can handle the new function that is not available in the V10 CM if it is migrated from V8. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM67892 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: **Action for PM67892 (V10 CM8) Process the following commands to bind the packages that updated as a result of installing this PTF: BIND PACKAGE(DSNJAR) MEMBER(DSNX9INJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9RPJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9RMJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9DIJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9DPJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9DRJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9DUJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') BIND PACKAGE(DSNJAR) MEMBER(DSNX9AJP) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') Note: is the data set prefix of your DB2 V10 target libraries COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@9AJP PM67892 DSN@9DIJ PM67892 DSN@9DPJ PM67892 DSN@9DRJ PM67892 DSN@9DUJ PM67892 DSN@9INJ PM67892 DSN@9RMJ PM67892 DSN@9RPJ PM67892 DSNX9AJP PM67892 DSNX9DIJ PM67892 DSNX9DPJ PM67892 DSNX9DRJ PM67892 DSNX9DUJ PM67892 DSNX9INJ PM67892 DSNX9RMJ PM67892 DSNX9RPJ PM67892 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67892 DSN@9AJP DSN@9DIJ DSN@9DPJ DSN@9DRJ DSN@9DUJ DSN@9INJ DSN@9RMJ DSN@9RPJ DSNX9AJP DSNX9DIJ DSNX9DPJ DSNX9DRJ DSNX9DUJ DSNX9INJ DSNX9RMJ DSNX9RPJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9AJP DSNX9DIJ DSNX9DPJ DSNX9DRJ DSNX9DUJ DSNX9INJ DSNX9RMJ DSNX9RPJ MACROS DSN@9AJP DSN@9DIJ DSN@9DPJ DSN@9DRJ DSN@9DUJ DSN@9INJ DSN@9RMJ DSN@9RPJ LISTEND UK81051 COVER LETTER END UK81058 COVER LETTER START PROBLEM DESCRIPTION(S): PM64089 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users who * * use the utility FlashCopy functions. * **************************************************************** * PROBLEM DESCRIPTION: Fast replication didn't take place * * during Online REORG with inline * * Flashcopy Image copy * **************************************************************** * RECOMMENDATION: * **************************************************************** During online REORG, DFSMSdss makes a choice not to use fast replication because there is 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. Following utilities will be affected: COPY, REORG TABLESPACE, REORG INDEX, REBUILD INDEX, LOAD, RECOVER New parameters are added in the DFSMSdss COPY command when DB2 utility uses FLASHCOPY function,so that fast replication will 1 likely to be taken. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64089 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 PM64089 DSNUGFCD PM64089 DSNUGFUM PM64089 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64089 DSNUCBMT DSNUGFCD DSNUGFUM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCBMT DSNUGFCD DSNUGFUM LISTEND UK81058 COVER LETTER END UK81065 COVER LETTER START PROBLEM DESCRIPTION(S): PM68367 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of SQL DELETE on an index entry on a single * * DECIMAL column. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90206 DSNIIDIS ERQUAL5002 * * or DSNIDIFS ERQUAL5007 during SQL * * DELETE on an index entry on a single * * DECIMAL column. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90206 DSNIIDIS ERQUAL5002 or DSNIDIFS ERQUAL5007 occurred during SQL DELETE on a row which has a Negative representation of ZERO stored in a DECIMAL column and an index is created on this DECIMAL column. A negative zero decimal value can be represented in a DB2 column as X'0FFFFFFFFFFFFFFF'. Whereas a positive zero decimal value in a DB2 column can be represented as X'F000000000000000'. Negative zero values are not allowed in a DB2 index. The abend occurred because the negative zero key was not found in the index page during the key deletion. DB2 code was changed to convert the negative representation of ZERO to positive ZERO when the key was extracted from the row. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68367 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 DSNIDIFS PM68367 DSNIIDIS PM68367 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68367 DSNIDIFS DSNIIDIS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDIFS DSNIIDIS LISTEND UK81065 COVER LETTER END UK81070 COVER LETTER START PROBLEM DESCRIPTION(S): PM68369 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those where DB2 is configured * * with DDF THREADS=INACTIVE (DSN6FAC CMTSTAT * * INACTIVE). DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: ABND=0C4-00000011 DSNSFBK +07F4 * **************************************************************** * RECOMMENDATION: * **************************************************************** During processing related to the DSN6FAC POOLINAC (DSNTIP5 POOL THREAD TIMEOUT) subsystem parameter value, a pool thread (disconnected DBAT) is terminated because the thread remained unused for the specified period. In this case, the pool thread was also simultaneously soft canceled (such as via the Cancel Thread command) which causes DB2 to clean up an internal control block related to the (soft canceled) pool thread. This led to the abend 0C4-00000011 because DB2 incorrectly attempted to free the internal control block storage as Below the Bar related storage. The abend only occurs in DB2 10 for z/OS since the control block was redefined to reside Above the Bar. DB2 POOLINAC processing has been changed to refer to the Above the Bar definition of the storage. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68369 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLEDDA PM68369 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68369 DSNLEDDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLEDDA LISTEND UK81070 COVER LETTER END UK81071 COVER LETTER START PROBLEM DESCRIPTION(S): PM64997 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of an SQL * * statement with multiple outer joins * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -338 may be issued * * incorrectly for an SQL statement * * that contains multiple outer * * joins. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -338 may be issued incorrectly when preparing a SELECT statement with an outer join that has an ON clause predicate that references only one of the table operands. An example of a failing query is the following: SELECT * FROM T1 WHERE T1.C1 IS NOT DISTINCT FROM ( SELECT TY.C1 FROM T2 LEFT JOIN ( SELECT * FROM T3 WHERE T3.C2 = T1.C2) TX ON TX.C1 = T2.C2 LEFT JOIN ( SELECT * FROM T3 WHERE T3.C2 = T1.C2)TY ON TY.C1 IS NULL ) ; SQLCODE -338 is issued incorrectly for the SELECT statement above because DB2 did not handle the ON clause that references only one of the table operands in a left outer join correctly. DB2 was fixed to correctly handle the ON clause that references only one of the table operands in a left outer join. Additional keywords: SQLOUTERJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64997 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 DSNXOMQB PM64997 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64997 DSNXOMQB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMQB LISTEND UK81071 COVER LETTER END UK81134 COVER LETTER START PROBLEM DESCRIPTION(S): PM65046 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users whose applications * * use XML value index and were bound to V9 * * package without being re-bound to V10. * **************************************************************** * PROBLEM DESCRIPTION: When customers have applications that * * use XML index and were bound to DB2 9 * * package without being rebound to DB2 * * 10, they may encounter ABEND0C4 at * * DSNNXML.DSNNQTOP OFFSET840E. * **************************************************************** * RECOMMENDATION: * **************************************************************** When users applications were bound to DB2 9 package and run on DB2 10 without being rebound, control blocks used for XML index were not properly setup to handle the new DB2 10 structures. Thus ABEND0C4 RC00000038 at DSNNXML.DSNNQTOP may occur. More specifically, the above mentioned abend may occur when users application contains a query that 1.exploits XML index for predicate in XMLEXISTS or XMLTABLE, and 2.the right hand side of predicate is a longer string constant (longer than the index key length) or a variable bound to a host variable, parameter marker, XML-typed item sequence, scalar fullselect subquery result, etc. For example, a user created a table T1 as described in DDL below and his/her application contains a query with the above characteristics - the right hand side in the XMLEXISTS predicate is an XML-typed item sequence generated by an XMLQUERY function. If this application is bound to DB2 9 package and runs on DB2 10 without being rebound to DB2 10, then the above mentioned abend may occur. 1 CREATE TABLE T1 (ID INTEGER, DATA XML); CREATE INDEX T1I1 ON T1(DATA) GENERATE KEY USING XMLPATTERN '/a/b/c' AS SQL VARCHAR(3); SELECT ID FROM T1 WHERE XMLEXISTS('/a/b[c>=$x]' PASSING DATA, XMLQUERY('"333"') AS "x"); Additional keywords: SQLXML XMLALL XMLINDEXES SQLMIGRATION DB2 10 is modified to properly set up the control blocks used for XML index to handle new DB2 10 structures. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65046 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNQTOP PM65046 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65046 DSNNQTOP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNQTOP LISTEND UK81134 COVER LETTER END UK81135 COVER LETTER START PROBLEM DESCRIPTION(S): PM67274 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * RUNSTATS utility users collecting * * HISTOGRAM statistics on partitioned * * indexes after an ALTER ROTATE PARTITION. * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT MSGDSNU632I during RUNSTATS * * HISTOGRAM causes SQL bad access path. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When the user executed RUNSTATS TABLESPACE INDEX HISTOGRAM, the utility reported a LOWVALUE greater than HIGHVALUE in a quantile of a histogram for the index. This statistic was reported in MSGDSNU632I and stored in the SYSIBM.SYSCOLDIST catalog table. 1 The user had performed an ALTER ROTATE PARTITION prior to executing the RUNSTATS utility. The incorrect LOWVALUE and HIGHVALUE in the quantile was caused by an incorrect aggregation algorithm. ADDITIONAL SYMPTOMS: The values in the quantiles were not in the correct sequential order. The highest value and the lowest value quantiles of the histogram were not reported correctly. Code was modified to aggregate the HISTOGRAM statistics correctly into the SYSIBM.SYSCOLDIST catalog table after an ALTER ROTATE PARTITION is performed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67274 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 PM67274 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67274 DSNUSAH1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSAH1 LISTEND UK81135 COVER LETTER END UK81139 COVER LETTER START PROBLEM DESCRIPTION(S): PM63606 - **************************************************************** * USERS AFFECTED: Vendor applications that want access to DB2 * * agent and statement-level storage. * **************************************************************** * PROBLEM DESCRIPTION: Vendor applications would like an * * interface to anchor control blocks * * associated with a given DB2 agent * * or an executing SQL statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** An enhancement is required. A new assembler macro DSNWVENC has been created. DSNWVENC can be invoked to access storage associated with the currently executing DB2 agent or SQL statement. All exploiters of this macro interface must first register with the DB2 subsystem to obtain an access token. This token is used on subsequent agent and statement access invocations. All applications exploiting 1 the storage access interface should deregister when the application no longer needs access to agent and statement- level storage. Detailed interface documentation is available upon request. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63606 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDIFCC PM63606 DSNDQWSD PM63606 DSNWVENC PM63606 DSNWVEND PM63606 DSNWVTIT PM63606 DSNWVZPS PM63606 DSNWZDG2 PM63606 HDBAA10J PM63606 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63606 DSNDIFCC DSNDQWSD DSNWVENC DSNWVEND DSNWVTIT DSNWVZPS DSNWZDG2 HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWVEND DSNWVTIT DSNWVZPS DSNWZDG2 MACROS DSNDIFCC DSNDQWSD DSNWVENC LISTEND UK81139 COVER LETTER END UK81146 COVER LETTER START PROBLEM DESCRIPTION(S): PM67304 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of a native SQL * * procedure that contains an SQL statement * * that issues a warning SQLCODE when creating * * or regenerating the native SQL procedure. * **************************************************************** * PROBLEM DESCRIPTION: Unexpected SQLCODE -104, -313 or -206 * * could be issued when running a native * * SQL procedure if both of the following * * conditions are satisfied. * * * 1 * 1. The native SQL procedure contains a * * FOR loop or any statement that * * references a DGTT (declare global * * temp table). * * 2. A warning was issued during creating * * or regenerating the native SQL * * procedure. * **************************************************************** * RECOMMENDATION: * **************************************************************** Unexpected SQLCODE -104, -313 or -206 could be issued when running a native SQL procedure if both of the following conditions are satisfied. 1. The native SQL procedure contains a FOR loop or any statement that references a DGTT (declare global temp table). 2. A warning was issued during creating or regenerating the native SQL procedure. Some examples are shown below. Example 1: SQLCODE -104 could be incorrectly issued for the SQL statement that references a DGTT in a native SQL procedure. CREATE PROCEDURE SP1() WITH EXPLAIN L1: BEGIN NOT ATOMIC DECLARE v_count BIGINT; DECLARE GLOBAL TEMPORARY TABLE SESSION.TEMPTAB (RECNO INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1), MESSAGE_TEXT VARCHAR(90)) ON COMMIT PRESERVE ROWS; SELECT COUNT(*) INTO v_count FROM SESSION.TEMPTAB; END L1 ! If there is any warning issued during creating the above procedure, SQLCODE -104 could be incorrectly issued. For example, if the EXPLAIN tables are in V9 format, SQLCODE 20520 will be issued for the SELECT COUNT statement when creating the native SQL procedure. SQLCODE -104 will be issued when running this native SQL procedure. Example 2: SQLCODE -313 could be incorrectly issued for the native SQL procedure contains a FOR loop. CREATE TABLE T1(C1 VARCHAR(10))! CREATE PROCEDURE SP2 () P1:BEGIN DECLARE VAR1 INTEGER DEFAULT 0; DECLARE VAR2 VARCHAR(10); FOR CUR01 CURSOR FOR WITH CTE (C1) AS 1 (SELECT 1 FROM SYSIBM.SYSDUMMY1 UNION ALL SELECT C1 + 1 FROM CTE WHERE C1 - 5 < 0 ) SELECT C1 FROM CTE WHERE VAR1 = 0 DO SELECT C1 INTO VAR2 FROM T1; END FOR; END P1! There is a warning SQLCODE 347 when creating the above procedure because of the recursive common table expression in the FOR loop statement. SQLCODE -313 will be issued when running this native SQL procedure. Example 3: SQLCODE -206 could be incorrectly issued for the native SQL procedure contains a FOR loop. After creating the procedure as in the Example 2, drop the table T1, and create the table T1 again, then running this procedure will cause an SQLCODE -206. DB2 did not correctly process the aforementioned native SQL procedure when there is a warning SQLCODE, which caused the unexpected SQLCODE. DB2 has been modified to correctly process the aforementioned native SQL procedure, so there will be no the unexpected SQLCODE. Additional keywords: SQLSP SQLSTOREDPROC SQLNATIVESQLPL SQLCODE104 SQLCODE313 SQLCODE206 SQLCODE20520 SQLCODE347 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67304 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: PM67304 corrects a problem that unexpected SQLCODE -104, -313 or -206 could be issued when running a native SQL procedure if both of the following conditions are satisfied. 1. The native SQL procedure contains a FOR loop or any statement that references a DGTT (declare global temp table). 2. A warning was issued during creating or regenerating the native SQL procedure. 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 1 SQL procedure could be affected by this change. The query below helps to identify the qualified procedures. While more rows may be returned because of the keywords FOR or SESSION may exist elsewhere. Also the keywords FOR and SESSION are case sensitive in the LIKE predicates, so they need to change according the case they are used in the native SQL procedures. SELECT SUBSTR(SCHEMA, 1, 8), SUBSTR(NAME, 1, 18) FROM SYSIBM.SYSROUTINES WHERE TEXT LIKE '%FOR%' OR TEXT LIKE '%SESSION%' OR TEXT LIKE '%for%' OR TEXT LIKE '%session%'; DB2BIND: PM60625 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS.DSNXRLOB:P017 could happen after rebinding and then running a native SQL procedure containing an SELECT...INTO statement that selects CLOB or DBCLOB data into CHAR or VARCHAR variables with different CCSIDs. 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOOP PM67304 DSNXOYPL PM67304 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67304 DSNXOOP DSNXOYPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOOP DSNXOYPL LISTEND UK81146 COVER LETTER END UK81149 COVER LETTER START PROBLEM DESCRIPTION(S): PM67972 - **************************************************************** * USERS AFFECTED: DB2 for z/OS version 9 and version 10 users * * of Partition By Range (PBR) table spaces. * **************************************************************** * PROBLEM DESCRIPTION: The following error can occur during * * insert or update to table in PBR table * * space * * ABEND04E RC00E70005 at DSNXEFDAM500. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** During insert or update to a PBR table space, if it's the first time that update or insert is issued to the target partition after Alter statement changing the table schema, DB2 needs to insert a new OBD record to a new system page on the partition. But if there is no room for the new system page on the partition, DB2 didn't format a correct return code. As the result, abend happend at DSNXEFDA:M500. DB2 code has been modified to format a correct return code, and the insert or update statement will fail with expected SQLCODE -904. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67972 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 PM67972 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67972 DSNISEGF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISEGF LISTEND UK81149 COVER LETTER END UK81171 COVER LETTER START PROBLEM DESCRIPTION(S): PM69542 - **************************************************************** * 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 SQLCODE807 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, servers identify all requesters by their IP addresses (or luname). BIND PACKAGE and REBIND PACKAGE options 1 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 SQLCODE807 because the connection validation fails trying to compare IP addresses against location names. 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. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69542 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM69542 introduces the following changes to externals: DB2 10 for z/OS has been changed to disregard the REMOTE(location-name,...,,...) bind option when it allocates packages for an application. DB2 will continue to validate all remote connections if ENABLE(REMOTE) or DISABLE(REMOTE) is specified. If REMOTE(location-name,...,< luname>,...) is also specified, it is ignored during package allocation. Information about this change 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 DSNTAAL PM69542 DSNXEAAL PM69542 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69542 DSNTAAL DSNXEAAL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTAAL DSNXEAAL LISTEND UK81171 COVER LETTER END UK81177 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM64646 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users performed insert * * operations to DGTT tables. * **************************************************************** * PROBLEM DESCRIPTION: Various abends occurred while doing the * * insert operations, such as ABEND04E * * RC00E20003 DSNSVBK +070E or ABEND04E * * RC00E20013 DSNSGMN +1104. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 experienced storage shortage and caused the DB2 system to crash. The storage shortage is caused by excessive number of IPROC blocks being accumulated due to previous insert operations to many DGTT tables. DB2 did not release or reuse those IPROC storage at a proper time. DB2 code is fixed to properly release the IPROC storage and reuse it when the next new IPROC is to be allocated. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64646 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 PM64646 DSNICMT2 PM64646 DSNICPOS PM64646 DSNICREL PM64646 DSNICUBC PM64646 DSNICUBD PM64646 DSNIDALC PM64646 DSNIRSVP PM64646 DSNISRTI PM64646 DSNITCUS PM64646 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64646 DSNICINV DSNICMT2 DSNICPOS DSNICREL DSNICUBC DSNICUBD DSNIDALC DSNIRSVP DSNISRTI DSNITCUS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICINV DSNICMT2 DSNICPOS DSNICREL DSNICUBC DSNICUBD DSNIDALC DSNIRSVP DSNISRTI DSNITCUS LISTEND 1UK81177 COVER LETTER END UK81186 COVER LETTER START PROBLEM DESCRIPTION(S): PM68029 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where a DB2 for z/OS system is * * used to access remote servers. * **************************************************************** * PROBLEM DESCRIPTION: Intermittent SQLCODE -904 00D30112 may * * occur when a DB2 for z/OS system * * attempts to access a remote server. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a DB2 for z/OS system attempts to access a remote server, an SQLCODE -904 00D30112 condition may intermittently occur. The DB2 Communication Data Base (CDB) was configured to utilize userid/password authentication with the remote system. DB2 attempts to encrypt the userid/password but an encryption error occurred. As a result, DB2 sends the userid/password to the remote system in clear text and the connection was successfully established. Once the connection has been successfully established with the remote server, DB2 caches information, such as the security mechanism, related to the connection. In this case, the userid/password security mechanism is cached. When the DB2 system attempts to access the remote server again, DB2 reuses the security mechanism that was cached (ie., userid/password authentication). The encryption of the userid/password failed due to an encryption error so DB2 again attempts to send the userid/password to the remote server in clear text. However, the CDB security option has since been changed to utilize another security mechanism (something other than userid/password authentication, such as, RACF PassTickets) that is inconsistent with the cached mechanism, and this leads to the reported SQLCODE -904 00D30112 error condition. DB2 for z/OS outbound connection processing has been changed to favor the CDB security option when the cached security mechanism is different. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68029 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 PM68029 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68029 DSNLTCCN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNLTCCN LISTEND UK81186 COVER LETTER END UK81195 COVER LETTER START PROBLEM DESCRIPTION(S): PM63688 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of sysplex parallelism or * * pair-wise join. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses the following two * * problems. * * * * 1. An ABEND04E RC00E70005 can occur at * * DSNXRBND:M666 or at DSNXEBR :M666 * * when a query contains a sysplex * * parallel group. * * * * 2. An ABEND0C4 RC38 can occur at * * DSNIWKFT offset 01F2 when a query * * uses the pair-wise join method. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following two problems are being addressed by this apar. PROBLEM 1. An ABEND04E RC00E70005 can occur at location DSNXRBND :M666 or at DSNXEBR :M666 when a query runs in sysplex parallelism and a remote DB2 child task returns an SQLCODE error (i.e. sqlcode = -904). The failure occurs on behalf of the remote DB2's child task SQLCODE error handling. The SQLCODE error is not passed back to the parent task. PROBLEM 2. An ABEND0C4 RC38 can occur at location DSNIWKFT OFFSET01F2 when a query uses the pair-wise join method and the leg returns a "resource unavailable" condition along with a positive residual SQLCODE. This residual information allows DB2 to bypass issuing a "resource unavailable" message which leads to the abend. Please note that these two scenarios are not query dependent. The code in DB2 is modified to handle a sysplex remote DB2's child task SQLCODE error message and a pair-wise join leg's SQLCODE error message properly. Additional Keywords: DB2PARALL/K PARALLELISM SQLPARALLELISM 1 SQLCPUP SQLSYSPLEXP SQLPAIRWISEJOIN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63688 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXREOJ PM63688 DSNXRFF PM63688 DSNXRFN PM63688 DSNXROJ1 PM63688 DSNXRSFN PM63688 DSNXRSGB PM63688 DSNXRTSC PM63688 DSNXRT1J PM63688 DSNXSBUC PM63688 DSNXSIND PM63688 DSNXSING PM63688 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63688 DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1 DSNXRSFN DSNXRSGB DSNXRTSC DSNXRT1J DSNXSBUC DSNXSIND DSNXSING THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1 DSNXRSFN DSNXRSGB DSNXRTSC DSNXRT1J DSNXSBUC DSNXSIND DSNXSING LISTEND UK81195 COVER LETTER END UK81203 COVER LETTER START PROBLEM DESCRIPTION(S): PM67860 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of BIND DEPLOY * **************************************************************** * PROBLEM DESCRIPTION: User incorrectly receives SQLCODE -4705 * * on BIND DEPLOY of a native SQLPL * * procedure. * **************************************************************** * RECOMMENDATION: * **************************************************************** On BIND DEPLOY of a native SQLPL procedure, user may incorrectly 1 receive SQLCODE4705 if the source procedure was created with any of the following options: - STAY RESIDENT - PROGRAM TYPE - RUN OPTIONS - NO DBINFO - COLLID or NO COLLID - SECURITY - PARAMETER STYLE GENERAL WITH NULLS - STOP/CONTINUE AFTER FAILURES BIND DEPLOY has now been fixed to issue SQL warning +434 instead, to indicate that the clause is deprecated. In order to see the warning, this fix needs to be applied to the target location of the BIND DEPLOY. Additional Keywords: sqlnativesqlpl sqlprocedure SQLCODE434 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67860 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIVNO PM67860 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67860 DSNXIVNO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIVNO LISTEND UK81203 COVER LETTER END UK81264 COVER LETTER START PROBLEM DESCRIPTION(S): PM66043 - **************************************************************** * USERS AFFECTED: All users of DSNTIJPA, a premigration health * * check job for DB2 Version 10 for z/OS that * * is shipped in DB2 UDB for z/OS Version 8 and * * DB2 Version 9.1 for z/OS, are affected by * * this change. * * * * All users of DSNTIJPM, a premigration health * * check job for DB2 Version 10 for z/OS that * * is shipped in DB2 Version 10, are affected * * by this change. * **************************************************************** 1 * PROBLEM DESCRIPTION: The following concerns pertain to the * * DB2 10 for z/OS premigration report * * jobs: * * * DSNTIJPM in V10 * * * DSNTIJPA in V8 and V9 * * * * (1) Report 25 can flag valid package * * and collection-ID names as having * * inconsistent UTF-8 encoding. * * * * (2) Report 29 can flag fully-authorized * * packages and plans as lacking * * SELECT privilege on * * self-referencing SQL statements. * * Also, report 29 performance can * * be improved. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** Two equivalent premigration checkout jobs are provided for DB2 for z/OS Version 10: * DSNTIJPA is shipped with DB2 Versions 8 and 9 in order to provide you the ability to begin checking the catalog and directory for concerns that must be remedied before commencing migration to DB2 Version 10. * The DSNTIJPM job shipped with DB2 Version 10 is equivalent to and serves the same purpose as DSNTIJPA. This APAR corrects various problems with DSNTIJPA and DSNTIJPM: (1) Report 25 can flag valid package and collection-ID names as having inconsistent UTF-8 encoding. Report 25 identifies inconsistent UTF-8 encoding of the collection IDs and the package names that were bound by a remote client system. Currently, it can return incorrect results because the code ignores use of mixed case in names. (2) Report 29 can flag fully-authorized packages and plans as lacking SELECT privilege on self-referencing SQL statements. Report 29 identifies packages and plans that contain self-referencing SQL statements on tables and views on which the package or plan owner lacks the SELECT privilege. Currently, it can return extraneous results because it does not exclude cases where the owner is an installation system administrator or such access has been granted to PUBLIC AT ALL LOCATIONS. Also, report 29 performance can be improved by modifying its SQL queries. In response, DSNTIJPM and DSNTIJPA are modified as follows: (1) Report 25 logic is modified to preserve the case of package names and collection-IDs being evaluated. (2) Report 29 is modified to exclude packages and plans owned by 1 a DB2 installation system administrator or when the SELECT privilege on a self-referenced table or view is granted to PUBLIC AT ALL LOCATIONS. Report 29 performance is also improved by query modifications. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66043 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 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 PM66043 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66043 DSNTIJPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTIJPM LISTEND UK81264 COVER LETTER END UK81296 COVER LETTER START PROBLEM DESCRIPTION(S): PM62298 - 1 **************************************************************** * USERS AFFECTED: All DB2 users of the -ACCESS, DISPLAY, * * START, STOP DATABASE commands. * **************************************************************** * PROBLEM DESCRIPTION: The -ACCESS, DISPLAY, START, STOP * * DATABASE(* name) commands generated * * ABEND04E RC00E30077 rather than * * DSN9006I message. * **************************************************************** * RECOMMENDATION: * **************************************************************** The -ACCESS, DISPLAY, START, STOP DATABASE(* name) commands incorrectly generated ABEND04E RC00E30077 rather than DSN9006I message. The -ACCESS, DISPLAY, START, STOP DATABASE(* name) commands were changed to generate DSN9006I message rather than ABEND04E RC00E30077. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62298 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTDDIS PM62298 DSNTDMSG PM62298 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62298 DSNTDDIS DSNTDMSG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTDDIS DSNTDMSG LISTEND UK81296 COVER LETTER END UK81299 COVER LETTER START PROBLEM DESCRIPTION(S): PM68572 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of COMMENT ON COLUMN or LABEL ON COLUMN. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 AT DSNXI14:P038 * * may occur when executing COMMENT ON * * COLUMN or LABEL ON COLUMN * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 AT DSNXI14:P038 may occur when executing COMMENT ON COLUMN or LABEL ON COLUMN when an error is encountered upon updating SYSIBM.SYSCOLUMNS. 1 LABEL ON COLUMN and COMMENT ON COLUMN have been modified to issue a proper SQLCODE if an error is encountered upon updating SYSIBM.SYSCOLUMNS ADDITIONAL KEYWORDS: SQLCOMMENTON SQLLABELON COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68572 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXICMT PM68572 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68572 DSNXICMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICMT LISTEND UK81299 COVER LETTER END UK81302 COVER LETTER START PROBLEM DESCRIPTION(S): PM70279 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of DSNAIMS * * and DSNAIMS2 stored procedures. * **************************************************************** * PROBLEM DESCRIPTION: DSNAIMS and DSNAIMS2 are prelinked with * * the current DFSYCRET module. * **************************************************************** * RECOMMENDATION: * **************************************************************** DSNAIMS and DSNAIMS2 are prelinked with the new DFSYCRET level so that the new MS Dump Formatter for OTMA can be used. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70279 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAIMS PM70279 DSNAIMS2 PM70279 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70279 DSNAIMS DSNAIMS2 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAIMS DSNAIMS2 LISTEND UK81302 COVER LETTER END UK81304 COVER LETTER START PROBLEM DESCRIPTION(S): PM69067 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of stored * * procedures written in JAVA with a package * * bound prior to DB2 for z/OS V8. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at DSNIDM DSNB1REL * * offset 02B2 may occur when a JAVA * * stored procedure is executed on V10 * * and its package was bound on a * * release prior to DB2 for z/OS V8. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000038 at DSNIDM DSNB1REL offset 02B2 may occur for a JAVA stored procedure application bound prior to DB2 for z/OS V8 and executed on a DB2 10 for z/OS system. The following example illustrates the problem. 1. Create a JAVA stored procedure on a DB2 release such as Version 7. CREATE PROCEDURE SPTEST(IN SPSCHEMA VARCHAR(31), OUT STATUS VARCHAR(50)) EXTERNAL NAME 'JDBCHPJ.SPTEST:JDBCHPJ.SPTEST. sptest(STRING,STRING)' LANGUAGE JAVA PARAMETER STYLE JAVA NOT DETERMINISTIC COLLID NULLID WLM ENVIRONMENT WLMENVJ Please note, in the above JAVA stored procedure definition, JAR SCHEMA value is JDBCHPJ, JAR ID value is SPTEST, and JAVA SIGNATURE value is (STRING, STRING). 2. Create a calling application and bind it on the DB2 V7 system EXEC CALL SPTEST(:HV1, :HV2); 3. Migrate the system to DB2 10 for z/OS and run the calling application DB2 code does not correctly puff an internal structure to the 1 corresponding V10 structure for JAR SCHEMA, JAR ID and JAVA SIGNATURE. This may result in a memory overlay or the ABEND0C4 described above. Please note, depending on the overlay location other symptoms are possible. DB2 code has been fixed to puff the internal structure correctly when a JAVA stored procedure is invoked. Additional Keywords: SQLSP SQLSTOREDPROC SQLMIGRATION OFFSET02B2 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69067 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRPUF PM69067 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69067 DSNXRPUF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRPUF LISTEND UK81304 COVER LETTER END UK81306 COVER LETTER START PROBLEM DESCRIPTION(S): PM68706 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS using PLANMGMT * * or APCOMPARE * **************************************************************** * PROBLEM DESCRIPTION: Storage leak can occur when using * * PLANMGMT or APCOMPARE * **************************************************************** * RECOMMENDATION: * **************************************************************** A storage leak can occur when using PLANMGMT or APCOMPARE. The blocks being leaked do not have an eyecatcher, but the blocks are allocated from DSNXOPLM+0D20 and can remain unfreed. These blocks could accumulate, consuming storage. Additional Keywords: SQLSTORAGE DB2STGLK/K Code is added to free the storage mentioned above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68706 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 DSNXOPLM PM68706 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68706 DSNXOPLM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPLM LISTEND UK81306 COVER LETTER END UK81314 COVER LETTER START PROBLEM DESCRIPTION(S): PM66977 - **************************************************************** * USERS AFFECTED: All DB2 users in the data sharing * * environment who run automatic or manual * * GRECP and LPL recovery. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C202B1 DSNB1PER+036C or * * ABEND04E RC00C202B2 DSNB1PPP+0F0A * * in a data sharing environment after * * the completion of the GRECP or LPL * * recovery process. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C202B1 DSNB1PER+036C OR RC00C202B2 DSNB1PPP+0F0A is caused by the GRECP and LPL recovery process leaving page sets open as non-recoverable, and may cause problems when these page sets are subsequently accessed. Page sets opened by DSNISREC are physically closed at the completion of the recovery process. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66977 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISREC PM66977 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66977 DSNISREC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISREC LISTEND 1UK81314 COVER LETTER END UK81331 COVER LETTER START PROBLEM DESCRIPTION(S): PM68293 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users whose package * * is bound on previous DB2 release with * * SET CURRENT PATH statement. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC38 at DSNXGRDS.DSNXVAV9 * * offset 4448 * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC38 at DSNXGRDS.DSNXVAV9 offset 4448 occurs when a SET CURRENT PATH statement is processed inside a DB2 9 bound package migrated to DB2 10. When a subroutine is invoked, a 31 bit variable is passed in as a 64 bit parameter. This will cause the observed abend. DB2 has been fixed to handle the parameter passing correctly when a SET CURRENT PATH statement is processed. After the fix, the abend no longer occurs. Additional keywords: DB2MIGV10/K SETCURRENTPATH COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68293 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXVAV9 PM68293 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68293 DSNXVAV9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXVAV9 LISTEND UK81331 COVER LETTER END UK81332 COVER LETTER START PROBLEM DESCRIPTION(S): PM66953 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * 1 * using table expressions or views. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E 00C90101 AT * * DSNIDM.DSNIIMSI:5014 * * may occur for an SQL statement * * that satisfies the following * * conditions: * * 1. The statement references to a * * table expression or view. * * 2. The statement contains a predicate * * that can be push down into the table * * expression or materialized view. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E 00C90101 AT DSNIDM.DSNIIMSI:5014 may occur for an SQL statement that satisfies the following conditions: 1. The statement references to a table expression or view 2. The statement contains a predicate that can be push down into the table expression or materialized view. For Example, SELECT * FROM ( SELECT DATA2 FROM T1 UNION SELECT DATA2 FROM ( SELECT DATA2 FROM T3 UNION SELECT DATA2 FROM T2) TX(DATA2) ) TX(TXCOL) WHERE TX.TXCOL < '2'; The abend may occur for the above statement because DB2 did not push down the predicate TX.TXCOL correctly into the table expression. DB2 was fixed to push down the predicate into the table expression or materialized view correctly. Additional Keywords: SQLVIEW SQLTABLEEXPR SQLPREDPUSHDOWN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66953 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66953: See PM66953 APAR/PTF text for additional information about why a REBIND is necessary. PM66953 corrects a problem of ABEND04E 00C90101 AT DSNIDM.DSNIIMSI:5014 may occur for an SQL statement that satisfies the following conditions: 1. The statement references to a table expression or view 2. The statement contains a predicate that can be push down 1 into the table expression or materialized 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMS PM66953 DSNXOPAC PM66953 DSNXQMCH PM66953 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66953 DSNXOMS DSNXOPAC DSNXQMCH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMS DSNXOPAC DSNXQMCH LISTEND UK81332 COVER LETTER END UK81340 COVER LETTER START PROBLEM DESCRIPTION(S): PM65767 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (NFM) users of Workfile * * database with partition-by-growth (PBG) * * workfile table spaces in it * **************************************************************** * PROBLEM DESCRIPTION: In DB2 10 NFM, workfile table space * * selection algorithm is not selecting * * workfile PBG table spaces in an * * expected manner * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 10 NFM allows for creation of partition-by-growth (PBG) table spaces in Workfile database. However, in particular scenarios, DB2 was not selecting these table spaces in a manner that it should. Specifically: 1. DGTT, when the zparm WFDBSEP value is YES, should select PBG as the top choice (regardless of its SECQTY, so even if the PBG has a zero SECQTY), as opposed to the top choice being any non-zero SECQTY table space (classic-segmented or PBG). This is already followed today for the case of DGTT with WFDBSEP=NO. 2. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value is NO, should select PBG as the last resort (regardless of its SECQTY, so even if the PBG has a zero SECQTY). 1 3. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value is YES, should never select PBG (regardless of its SECQTY, so even if the PBG has a zero SECQTY). Code has been changed in the workfile table space selection algorithm to select PBG workfile table spaces in the following manner: 1. DGTT, when the zparm WFDBSEP value is YES, will select PBG as the top choice (regardless of its SECQTY, so even if the PBG has a zero SECQTY). This is already followed today for the case of DGTT with WFDBSEP=NO. 2. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value is NO, will select PBG as the last resort (regardless of its SECQTY, so even if the PBG has a zero SECQTY). 3. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value is YES, will never select PBG (regardless of its SECQTY, so even if the PBG has a zero SECQTY). Additional keywords: SQLPBG SQLDGTT SQLCGTT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65767 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Any automated operations or applications that monitor space use in Workfile database may need to be aware of the table space allocation type-related adjustment that this PTF provides with regard to the workfile table space selection approach. Please see PM65767 APAR/PTF text for additional information. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBWAC PM65767 DSNIGWAC PM65767 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65767 DSNIBWAC DSNIGWAC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBWAC DSNIGWAC LISTEND UK81340 COVER LETTER END UK81341 COVER LETTER START PROBLEM DESCRIPTION(S): PM66756 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 and 9 for z/OS users of LOAD with * * after insert trigger * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 DSNIWCUB+062A during LOAD * * executing on table with after insert * * trigger * **************************************************************** * RECOMMENDATION: * **************************************************************** While executing LOAD on a table with an after insert trigger, a commit was issued as part of trigger flow under the LOAD, which zeroed out a pointer to and freed the internal structure SLTE, which had been set up earlier in processing. The code was then trying to access this structure even though it no longer existed. Code has been changed to ensure that the internal structure SLTE exists before trying to access it. Additional keyword: SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66756 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWCUB PM66756 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66756 DSNIWCUB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWCUB LISTEND UK81341 COVER LETTER END UK81367 COVER LETTER START PROBLEM DESCRIPTION(S): PM53502 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of REPAIR LOCATE RID DELETE. * **************************************************************** * PROBLEM DESCRIPTION: REPAIR DELETE utility failed with an * * ABENDS0C7 RC0 DSNICUMW when * * decompression failed. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** REPAIR DELETE utility is enhanced: 1. It will tolerate an error when it can not decompress the data record and will continue deleting the compressed data 1 row, but not the related index entry and the associated objects. REPAIR DELETE utility will issue a message MSGDSNU677I indicating that the data row had been deleted, but the related index entry and the associated objects are not deleted. 2. A new keyword for REPAIR DELETE statement, DATAONLY, which will allow only the data record specified in the REPAIR LOCATE statement to be deleted. As with any REPAIR utility, REPAIR DELETE should be used with caution since it may cause further damage. It is up to the user to ensure that the data and the indexes are consistent. In the case where REPAIR DELETE is only deleting the data row, the indexes will not be placed in REBUILD PENDING. DB2 for z/OS Utility Guide and Reference is updated to add a new optional keyword, DATAONLY, to the delete statement of REPAIR LOCATE. delete statement: >>-DELETE---+----------+------------------------------------>< |    |     '-DATAONLY-' DATAONLY Specifies that REPAIR should only DELETE the data record specified by the REPAIR LOCATE RID statement. DATAONLY can only be specified when locating a single row with RID. After using this option, if the the table has indexes or contains LOB or XML columns, the user needs to ensure the data is consistent with the other associated objects. A new message, DSNU677I is added to DB2 Messages manual: DSNU677I csect-name DELETE OPERATION CANNOT DELETE RELATED INDEX ENTRIES OR OTHER ASSOCIATED OBJECTS Explanation: A REPAIR control statement specified a DELETE operation for row in a table that has indexes, LOB columns, XML columns, or referential integrity constraints. REPAIR could only delete the table row. Severity: 4 (warning) System Action: The data record that is specified in the LOCATE block is deleted. However, any related index entries or associated objects are not deleted. System Programmer Response: Run the appropriate CHECK utilities to ensure that the data is consistent with the other associated objects, and follow the recommended actions. 1 REPAIR LOCATE RID DELETE code is enhanced to support the new feature. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM53502 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The fix for APAR PM53502 added a new function to REPAIR LOCATE DELETE. DB2 for z/OS Utility Guide and Reference is updated to add a new optional keyword, DATAONLY, to the delete statement of REPAIR LOCATE. delete statement: >>-DELETE---+----------+------------------------------------>< |    |     '-DATAONLY-' DATAONLY Specifies that REPAIR should only DELETE the data record specified by the REPAIR LOCATE RID statement. DATAONLY can only be specified when locating a single row with RID. After using this option, if the the table has indexes or contains LOB or XML columns, the user needs to ensure the data is consistent with the other associated objects. A new message, DSNU677I is added to DB2 Messages manual: DSNU677I csect-name DELETE OPERATION CANNOT DELETE RELATED INDEX ENTRIES OR OTHER ASSOCIATED OBJECTS Explanation: A REPAIR control statement specified a DELETE operation for row in a table that has indexes, LOB columns, XML columns, or referential integrity constraints. REPAIR could only delete the table row. Severity: 4 (warning) System Action: The data record that is specified in the LOCATE block is deleted. However, any related index entries or associated objects are not deleted. System Programmer Response: Run the appropriate CHECK utilities to ensure that the data is consistent with the other associated objects, and follow the recommended actions. ACTION: The PTF for APAR PM53502 has modified CSECTs in both the DSNUT910/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 1 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 DSNFMDIR PM53502 DSNFUDRC PM53502 DSNICUMW PM53502 DSNIDILS PM53502 DSNIREDR PM53502 DSNITDLE PM53502 DSNUCDEL PM53502 DSNUFCMN PM53502 DSNUGDDN PM53502 DSNUGPPN PM53502 DSNUGPRT PM53502 DSNUMSGC PM53502 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM53502 DSNFMDIR DSNFUDRC DSNICUMW DSNIDILS DSNIREDR DSNITDLE DSNUCDEL DSNUFCMN DSNUGDDN DSNUGPPN DSNUGPRT DSNUMSGC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFUDRC DSNICUMW DSNIDILS DSNIREDR DSNITDLE DSNUCDEL DSNUFCMN DSNUGDDN DSNUGPPN DSNUGPRT DSNUMSGC LISTEND UK81367 COVER LETTER END UK81373 COVER LETTER START PROBLEM DESCRIPTION(S): PM69073 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the REORG * * TABLESPACE utility on partition-by-growth * * (PBG) objects. * **************************************************************** 1 * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIRFNX:5362 * * during a REORG TABLESPACE SHRLEVEL * * REFERENCE with pending ALTERs and * * PBG growth. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A REORG TABLESPACE SHRLEVEL REFERENCE was run on a partition- by-growth tablespace (PBG), with all partitions defined in Reordered Row Format (RRF), with the DB2 subsystem parameter RRF=DISABLE, and pending ALTERs against the table space. During the RELOAD phase of the REORG, a new PBG partition was created in Basic Row Format (BRF), resulting in a BRF PBG part, with rows in RRF format. A subsequent REORG TABLESPACE utility abended with an ABEND04E RC00C90101 DSNIRFNX:5362 due to the inconsistent row format. REORG TABLESPACE SHRLEVEL REFERENCE and CHANGE utility code has been modified to create new PBG partitions in the correct format, regardless of the ZPARM subsystem value. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69073 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURLOG PM69073 DSNURWIR PM69073 DSNXIPGA PM69073 DSNXISTK PM69073 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69073 DSNURLOG DSNURWIR DSNXIPGA DSNXISTK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURLOG DSNURWIR DSNXIPGA DSNXISTK LISTEND UK81373 COVER LETTER END UK81377 COVER LETTER START PROBLEM DESCRIPTION(S): PM67885 - **************************************************************** * USERS AFFECTED: DB2 users who ALTER TABLESPACE MAXPARTITIONS * * of a table space that has a table created * * before DB2 V5. * **************************************************************** * PROBLEM DESCRIPTION: Customer could receive ABEND04E at * * DSNGDARA ERUQAL5001 or * 1 * DSNGDADP ERUQAL5036 * **************************************************************** * RECOMMENDATION: * **************************************************************** For the table created before DB2 V5, the internal structure does not have an extension. Accessing the extension results the above abend. DB2 has been changed to not access the extension if it does not exist to avoid the abend. Additional keyword: SQLALTER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67885 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDADP PM67885 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67885 DSNGDADP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDADP LISTEND UK81377 COVER LETTER END UK81384 COVER LETTER START PROBLEM DESCRIPTION(S): PM69269 - **************************************************************** * USERS AFFECTED: All DB2 Version 8, DB2 Version 9 and DB2 * * Version 10 for z/OS users who execute SQL * * optimization hints using page range * * (PAGE_RANGE='Y' in PLAN_TABLE output). * **************************************************************** * PROBLEM DESCRIPTION: DB2 Version 8 and DB2 Version 9 might * * block page range when a user issues a * * query that satisfies one of the * * following conditions below: * * * * 1. Index only access (INDEXONLY = 'Y') * * 2. Clustering index * * * * DB2 Version 10 might incorrectly allow * * page range when a user issues a query * * which is accessed by the partitioning * * index. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 When executing or binding SQL with page range by using optimization hints, DB2 Version 8 and DB2 9 may block page range in one of the following conditions below: 1. Index only access (INDEXONLY = 'Y') 2. Clustering index DB2 10 might incorrectly allow page range when a user issues a query which is accessed by the partitioning index. The problems mentioned above are fixed so that DB2 will block page range in either of the following conditions: 1. Index only and the index is not DPSI; or 2. Partitioning index ADDITIONAL KEYWORDS: OPTHINT OPTHINTS PAGERANGE INDEXONLY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69269 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM69269: See PM69269 APAR/PTF text for additional information about why a REBIND is necessary. PM69269 corrects a problem of allowing page range in some cases when using optimization hints where page range would not be allowed if hints were not used. 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 PM65757: See PM65757 APAR/PTF text for additional information about why a REBIND is necessary. PM65757 corrects a problem that an ABEND04E RC00E70005 in DSNXOBM P030 may occur or incorrect output may be produced if an optimization hint is used. 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 1 DSNXOPTH PM69269 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69269 DSNXOPTH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPTH LISTEND UK81384 COVER LETTER END UK81388 COVER LETTER START PROBLEM DESCRIPTION(S): PM69079 - **************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: Drain fails with timeout * **************************************************************** * RECOMMENDATION: * **************************************************************** When the structure castout owner member of a group buffer pool (GBP) does GBP checkpoint, if a pageset's castout owner member is not the structure castout owner and is unavailable to do castout, a special castout process starts. This process may physically open the pageset. If the open fails, the special castout process may not clean up claims held during the open. Following drainers can fail since the claimers never go away. The special castout logic has been modified to do cleanup when the physical open fails. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69079 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB5SPC PM69079 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69079 DSNB5SPC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB5SPC LISTEND UK81388 COVER LETTER END UK81415 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM69866 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of LOBs * * (large objects) with isolation level UR * * (Uncommitted Read). * **************************************************************** * PROBLEM DESCRIPTION: An unexpected SQLCODE100 (SQLCODE +100) * * or no records found is returned for an * * ISO(UR) reader when fetching LOB * * columns. * **************************************************************** * RECOMMENDATION: * **************************************************************** An unexpected SQLCODE100 (SQLCODE +100) or no records found can be returned for an ISO(UR) reader when fetching LOB columns. Apar PM18903 (v9 ptf UK60323) intended to close a small serialization window to avoid LOB corruption in a data sharing environment when a LOB updater and a LOB UR reader are accessing the same LOBs. At the time, it was thought that the fix provided in PM18903 (which was not to read a pseudo deleted LOB) might close the serialization window. Unfortunately, it was later discovered that this was not the case for v9. As a result, an SQLCODE +100 could be returned as now reported. In summary, PM18903 did not correct the inconsistency involving the read LRSN problem but did restore code that always requests a pseudo delete. The following paragraph provides additional information about the serialization which could lead to this LOB inconsistency. Today, when a LOB is deleted, DB2 always does a pseudo delete on both the LOB data storage and its associated Aux index. DB2 deploys a read LRSN to claim the LOB data storage and its Aux index entry when there is no active thread to access the data. In the past, due to an inconsistent read LRSN value, DB2 could mistakenly lose both the LOB data storage and its Aux index when there is still an active thread accessing the data. The code in DB2 is modified to prevent the SQLCODE +100 or no records found condition for ISO(UR) readers of LOB columns. Additional Keywords: SQLCODE100 SQLLOB INCORROUT SQLINCORR SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69866 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 PM69866 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69866 DSNODCRL 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNODCRL LISTEND UK81415 COVER LETTER END UK81419 COVER LETTER START PROBLEM DESCRIPTION(S): PM68787 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS users of large XML * * objects in a distributed environment. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses the following two * * problems. * * * * Problem 1. * * DB2 issues an ABEND04E at * * DSNOPGNX:5001 when processing * * XML data with a large size in * * a distributed environment. * * * * Problem 2. * * DB2 returns corrupted XML data * * when XML data with a large * * size is returned from a remote * * server to client when streaming * * is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** This apar addresses the following two problems. Problem 1. DB2 issues an ABEND04E at location DSNOPGNX:5001 (ERQUAL5001) when processing XML data with a certain large size in a distributed environment. Problem 2. DB2 returns corrupted XML data when XML data with a certain large size is returned from a remote server to client when streaming is enabled. The above two problems can occur because the DB2 LOB manager does not handle the length for an intermediate buffer of XML data properly. The code in DB2 has been modified to correct the length discrepancy that exists for intermediate buffers of XML data when the XML data is a large size. Additional Keywords: SQLXML 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68787 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOPGNX PM68787 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68787 DSNOPGNX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOPGNX LISTEND UK81419 COVER LETTER END UK81424 COVER LETTER START PROBLEM DESCRIPTION(S): PM68414 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with applications * * that have held cursors and bound with * * RELEASE(DEALLOCATE). * **************************************************************** * PROBLEM DESCRIPTION: For applications with held cursors and * * bound with RELEASE(DEALLOCATE), * * following abend may happen during * * update or insert due to missing * * tablespace or table lock : * * * * ABEND04E RC00C90101 DSNILREP ERQUAL5060 * * ABEND04E RC00C90101 DSNISRTI ERQUAL5003 * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** DB2 mistakenly downgraded a tablespace/table lock from ALLOCATION duration to COMMIT duration during its commit process, even though the application was bound with RELEASE(DEALLOCATE). This may cause the tablespace/table lock to be freed at commit and lead to the ABEND at DSNILREP ERQUAL5060 or DSNISRTI ERQUAL5003 on its next update or insert into this table. Fixes made in DB2 so that it won't downgrade a tablespace/table lock from ALLOCATION duration to COMMIT duration if the application is bound with RELEASE(DEALLOCATE). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68414 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 DSNICMTC PM68414 DSNICUBC PM68414 DSNILRBK PM68414 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68414 DSNICMTC DSNICUBC DSNILRBK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICMTC DSNICUBC DSNILRBK LISTEND UK81424 COVER LETTER END UK81425 COVER LETTER START PROBLEM DESCRIPTION(S): PM64753 - **************************************************************** * USERS AFFECTED: DB2 users that use Katakana EBCDIC * * CCSIDs. * **************************************************************** * PROBLEM DESCRIPTION: If DB2 Japanese Katakana CCSID is used * * in the DECP (290, 930, 5026, 1390 or * * 8482), SQLCODE922 is issued when JCC T2 * * driver is used to connect to DB2 with * * userid or password that contains * * lower case charaters. This occurs when * * using JCC driver version 3.61.84 or * * later (JDBC 3.0) or 4.11.86 or later * * (JDBC 4.0). * * SQLCODE922 may also occurs if an * * application uses the SQL statement * * 'CONNECT TO USER * * USING ' to connect to DB2 * * with the above CCSIDs and lower case * * characters in the userid or password. * **************************************************************** * RECOMMENDATION: * **************************************************************** During authorization checking, DB2 folds the userid and password string to upper case in CCSID 500. Because Japanese Katakana CCSIDs have different code points for their lower case characters, prior to this APAR the folding results may be incorrect causing authorization to fail. With this APAR, DB2 code checks for these Japanese Katakana CCSIDs and folds lower case characters in the userid and password to upper case correctly in these CCSIDs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64753 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Prior to the application of this PTF, on the 'CONNECT TO USER USING ' SQL statement, lower case characters in the userid and password in Japanese Katakana CCSIDs (290, 930, 5026, 1390 or 8482) were sent to System Authorization Facility (SAF) interface unchanged. With the application of this PTF, the lower case characters will be folded to upper case before the ID and password are given to the SAF interface. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECNT PM64753 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64753 DSNXECNT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECNT LISTEND UK81425 COVER LETTER END UK81434 COVER LETTER START PROBLEM DESCRIPTION(S): PM67529 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of query * * containing scrollable cursor with order by * * and outer join reduction. The reduction * * table has FIELDPROC defined on a not-null * * column. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E 00C90101 at DSNIBNRF 5003 or * * DSNISRTI 53D0 for scrollable cursor * * with order by and outer join reduction. * * The reduction table has FIELDPROC * * defined on a not-nullalbe column. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E 00C90101 at DSNIBNRF 5003 or DSNISRTI 53D0 for scrollable cursor with order by and outer join reduction. The reduction table has FIELDPROC defined on a not-null column. The following example illustrates an error case. DECLARE T1_CURSOR INSENSITIVE SCROLL CURSOR FOR SELECT T1.C1,T3.C2,T2.C2 FROM T1 LEFT OUTER JOIN T2 ON T1.C2 = T2.C2 LEFT JOIN T3 1 ON T3.C1 = T1.C1 LEFT JOIN T4 ON T4.C1 = T1.C1 WHERE (T2.c1 is not null AND 3=3) AND (T1.C1 IS NULL OR T1.C1 > 0) ORDER BY 3,1,2; T2.C2 is not nullable column with a FIELDPROC defined. he bindtime code in DB2 is modified to correct the conditions leading to the ABEND. Additional Keywords: ABEND04E SQLORDERBY SQLFIELDPROC SQLOUTERJOIN SQLOUTER SQLLEFTJOIN SQLLEFT SQLRIGHT SQLSCROLL RC00C90101 DSNIBNRF ERQUAL5003 DSNISRTI ERQUAL53D0 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67529 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM67529 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM67529 corrects problems that can cause abends for scrollable cursor with reduced outer join and FIELDPROC. 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 DSNXOSCR PM67529 DSNXOSOB PM67529 DSNXOSOC PM67529 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67529 DSNXOSCR DSNXOSOB DSNXOSOC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSCR DSNXOSOB DSNXOSOC LISTEND UK81434 COVER LETTER END UK81436 COVER LETTER START PROBLEM DESCRIPTION(S): PM70113 - **************************************************************** * USERS AFFECTED: All DB2 users of indexes over the child * 1 * table. * **************************************************************** * PROBLEM DESCRIPTION: Customer may receive the ABEND04E at * * DSNGEPUF ERQUAL500A. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 has a bug in error recovery for dropping index. When there are indexes defined on the child table, i.e., ix1 and ix2, DROP INDEX IX1 ROLLBACK DROP INDEX IX1 COMMIT after running the above SQL, the fanset OBD for index IX2 can be incorrectly deleted which causes the above abend late on. DB2 error recovery code has been changed so that it will not incorrectly delete index fanset OBD. Applying this apar will not fix the missing index fanset OBD which is introduced before. REPAIR DBD REBUILD can correct the broken OBD. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70113 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDDIX PM70113 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70113 DSNGDDIX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDDIX LISTEND UK81436 COVER LETTER END UK81439 COVER LETTER START PROBLEM DESCRIPTION(S): PM64101 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using UNIQUE * * INDEXES with INCLUDE columns. * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA utility reported message * * MSGDSNU733I after ALTER ADD INCLUDE * * column to a unique index that was * * involved in a REFERENTIAL CONSTRAINT. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect comparison routine was used to compare the ordering columns of a truncated index key which contained one or more INCLUDE columns. DB2 has been modified to use the correct comparison routine to compare truncated keys with INCLUDE columns. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64101 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKGCMP PM64101 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64101 DSNKGCMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKGCMP LISTEND UK81439 COVER LETTER END UK81450 COVER LETTER START PROBLEM DESCRIPTION(S): PM68086 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users collecting * * multi-column frequency statistics. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may overestimate the compound * * filter factor of a set of predicates * * when multiple sets of multi-column * * frequency statistics exist. * **************************************************************** * RECOMMENDATION: * **************************************************************** When determining the combined filter factor for a set of predicates, DB2 may take into account available multi-column cardinality, frequency, and histogram statistics. If multiple sets of multi-column statistics exist that partially or completely cover the columns involved in the set of predicates DB2 may overestimate the combined filtering. For example, SELECT ... FROM T1 WHERE C1 = '0015' AND C2 = '0075' 1 AND C3 = '300' AND C4 = '01875467' With a multi-column frequency statistic on column set (C1,C2,C3) that exactly matches the values in the predicates above, DB2 will use that statistic as the combined filter factor of the predicates on C1, C2, and C3. If there is another multi-column statistic on column set (C1,C2,C3,C4) DB2 will neglect to include filtering from the predicate on C4 in the total filter factor. If C4 provides good filtering this could impact DB2's access path choice and result in poor query performance. Additional Keywords: SQLPERFORMANCE SQLACCESSPATH FILTERFACTOR SQLSTATS DB2 has been modified to properly compute the compound filter factor. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68086 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM68086: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM68086 corrects a problem in which compound filter factor may be overestimated, potentially resulting in a suboptimal access path and poor performance. 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 DSNXOGNC PM68086 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68086 DSNXOGNC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGNC LISTEND UK81450 COVER LETTER END UK81451 COVER LETTER START PROBLEM DESCRIPTION(S): PM65764 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -330 issued by UNLOAD utility * * when unloading XML data. * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE -330 was issued by the UNLOAD utility when converting XML data from UNICODE to an EBCDIC mixed CCSID. The conversion failed because the character conversion caused the length of an output buffer to be exceeded. This problem only occurs when running the UNLOAD utility with SPANNED YES specified. DB2 was fixed to handle the conversion of UNICODE XML data to the target CCSID when the conversion requires a larger output buffer. Additional keywords: XMLALL SQLCODE330 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65764 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 PM65764 DSNNOBSE PM65764 DSNNOCCN PM65764 DSNNOGET PM65764 DSNNOSCO PM65764 DSNNOSER PM65764 DSNNOSRT PM65764 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65764 DSNNOBSC DSNNOBSE DSNNOCCN DSNNOGET DSNNOSCO DSNNOSER DSNNOSRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOBSC DSNNOBSE DSNNOCCN DSNNOGET DSNNOSCO DSNNOSER DSNNOSRT LISTEND UK81451 COVER LETTER END UK81454 COVER LETTER START PROBLEM DESCRIPTION(S): PM70547 - **************************************************************** * USERS AFFECTED: All DB2 V10 users of IRLM230 (HIR2230) * 1 * data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: DB2 Class 2 Elapsed time is reported * * higher during certain intervals where * * DB2 is running light load or the rate * * of suspension in IRLM is low. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** DB2 V10 may experience periodic slowdowns with higher class 2 elapsed time seen in performance reports. Users migrating from DB2 V9 to V10 may observe transactions taking more time to run in V10, causing more timeouts. This slowdown may occur when the DB2 subsystem is running light or lock requests to IRLM are mostly getting processed synchronously without any suspension. During these periods, an error in IRLM logic to process work on the ordered queue may result in a failure to schedule an SRB to process asynchronous complete or notifies from XES. If these requests on the ordered queue are deferred due to IRLM internal usecount being non-zero, they will not be processed until some event happens to schedule an SRB to the irlm request handler. Events such as deadlock or healthcheck timer pop, XES EXIT is driven or a DB2 request is suspended for any reason. This delay results in higher suspend time on this or peer member which is waiting a response. GEN: KEYWORDS: *** END IMS KEYWORDS *** This APAR fixes a problem in scheduling IRLM SRBs to pickup any work left on its work queues when the request holding irlm usecount is completed and decrements the usecount. Performance data should not show abnormally high class 2 suspend time when there is low activity and CPU time is not high. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM70547 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 PM70547 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70547 DXRRL109 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL109 LISTEND UK81454 COVER LETTER END 1UK81460 COVER LETTER START PROBLEM DESCRIPTION(S): PM67642 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of ALTER TABLESPACE which results in * * package invalidation. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000010 DSNIPPHO OFFSET17B0 * * may result after ALTER TABLESPACE * * SEGSIZE when running REORG and DML * * concurrently * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC0000010 DSNIPPHO OFFSET17B0 may result after ALTER TABLESPACE SEGSIZE which causes conversion to UTS, when running REORG and DML concurrently because DB2 fails to invalidate the packages dependent on the table space. Other unpredictable results may occur. DB2 has been modified to correctly invalidate packages dependent on the table space during REORG as a result of pending ALTER TABLESPACE which requires invalidation. Packages dependent on table spaces with pending alters that were materialzed prior to applying this apar will not be fixed. Affected packages can be manually rebound. ADDITIONAL KEYWORDS: SQLALTER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67642 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 PM67642 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67642 DSNXIDPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIDPM LISTEND UK81460 COVER LETTER END UK81462 COVER LETTER START PROBLEM DESCRIPTION(S): PM69060 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with functions * 1 * or procedures where the parameter is a * * transition table and the table or view * * referenced contains a decimal or * * timestamp column. * **************************************************************** * PROBLEM DESCRIPTION: SYSPARMS.LENGTH and SYSPARMS.SCALE * * may contain incorrect values for * * a function or procedure where the * * parameter is a transition table and * * the table or view referenced contains * * a decimal or timestamp column. * **************************************************************** * RECOMMENDATION: * **************************************************************** SYSPARMS.LENGTH and SYSPARMS.SCALE may contain incorrect values for a function or procedure where the parameter is a transition table and the table or view referenced contains a decimal or timestamp column. As a result, users may encounter an unexpected error such as SQLCODE -302 when the expected input parameters are passed in when invoking a routine. Inversely, calling the routine with the incorrect parameters may be successful when they match the definition in SYSIBM.SYSPARMS. The following example shows incorrect values for SYSPARMS.SCALE for procedure SAMP01PR for the timestamp and decimal parameter. CREATE TABLE SAMP01TB ( COL1 DECIMAL(13) NOT NULL, COL2 TIMESTAMP NOT NULL, COL3 CHAR NOT NULL ); CREATE PROCEDURE SAMP01PR (IN ACTION_TYPE CHAR(1), IN TABLE LIKE SAMP01TB AS LOCATOR ) RESULT SET 0 EXTERNAL NAME 'SAMPPROC' LANGUAGE COBOL PARAMETER STYLE DB2SQL DETERMINISTIC NULL CALL FENCED MODIFIES SQL DATA NO DBINFO COLLID SYSADM; SELECT SUBSTR(TYPENAME,1,10) TYPENAME, TABLE_COLNO, LENGTH, SCALE FROM SYSIBM.SYSPARMS WHERE NAME = 'SAMP01PR'; 1 +------------------------------------------+ | TYPENAME | TABLE_COLNO | LENGTH | SCALE | +------------------------------------------+ 1_| CHAR | 0 | 1 | 0 | 2_| DECIMAL | 1 | 13 | 13 |<- 0 expected 3_| TIMESTAMP | 2 | 10 | 10 |<- 6 expected 4_| CHAR | 3 | 1 | 0 | +------------------------------------------+ DB2 has been modified to store the correct value for SYSPARMS.LENGTH and SYSPARMS.SCALE for routines where the parameter is a transition table and the table or view referenced contains a decimal or timestamp column. This apar does not fix existing procedures with an incorrect SYSPARMS.LENGTH and SYSPARMS.SCALE value. Routines defined incorrectly may be dropped and recreated. ADDITIONAL KEYWORDS: SQLCREATE SQLALTER SQLPROCEDURE SQLFUNCTION SQLUDF SQLCODE302 SQLCODE440 SQLCODE20314 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69060 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXISB2 PM69060 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69060 DSNXISB2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXISB2 LISTEND UK81462 COVER LETTER END UK81466 COVER LETTER START PROBLEM DESCRIPTION(S): PM66149 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of CHECK * * DATA SHRLEVEL CHANGE * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA SHRLEVEL CHANGE INCLUDE XML * 1 * TABLESPACES ALL ends with RC4 and * * issues multiple DSNU844I and DSNU845I * * messages * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** CHECK DATA SHRLEVEL CHANGE INCLUDE XML TABLESPACES ALL was run on a partitioned table space containing an XML column. After serializing on the base table space, another process caused the XML table space (a partition-by-growth table space (PBG)) to grow. Since this growth occurred after serialization, the growth of the XML table space was not known to the utility. When CHECK looked for an XML document that had moved into the new partition and could not find it, either message MSGDSNU844I (corrupted XML document) or MSGDSNU845I (XML document missing) is erroneously issued. CHECK SHRLEVEL CHANGE code has been changed to get a drain during the initialization phase while control blocks and shadow data sets are being built. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66149 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUKINP PM66149 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66149 DSNUKINP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKINP LISTEND UK81466 COVER LETTER END UK81467 COVER LETTER START PROBLEM DESCRIPTION(S): PM68236 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of LOAD * * when loading a BITEMPORAL table * **************************************************************** * PROBLEM DESCRIPTION: LOAD of a BITEMPORAL table specifying * * PERIODOVERRIDE results in ABEND0C4 from * * DSNURCLP+x'0112' * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** LOAD INTO TABLE PERIODOVERRIDE of a BITEMPORAL table specifying the period_begin column in the field-specification but not the period_end column results in ABENDS0C4 RC11 at DSNURCLP 1 OFFSET0112. The error occurred because during utility initialization, LOAD process was checking the wrong variable for the existence of the period_end column when building it's control structure. Later when another control block needed to be attached to the above structure, the ABEND0C4 occurred on an attempt to write into unallocated storage. Another abend that could occur is ABEND04E RC00E20005 from DSNSVBK. LOAD code has been changed to use the correct variable when checking for the existence of the period_end column in the input field-specification. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68236 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURWUF PM68236 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68236 DSNURWUF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWUF LISTEND UK81467 COVER LETTER END UK81472 COVER LETTER START PROBLEM DESCRIPTION(S): PM64805 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of DSN1COPY * **************************************************************** * PROBLEM DESCRIPTION: When running DSN1COPY CHECK against * * SYSDBASE, SYSPLAN, or SYSVIEWS, * * the following may occur: * * + garbled tokens in message DSN1991I * * + unexpected message DSN1984I, * * followed by message DSN1993I * * + an incorrect print control * * character in output blank lines * * When running DSN1COPY RESET against * * SYSDBASE, SYSPLAN, or SYSVIEWS, * * the following may occur: * * + unexpected message DSN1948I * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** When DSN1COPY CHECK is run against the system catalog tablespaces SYSDBASE, SYSPLAN, or SYSVIEWS, users may see: (1) Message MSGDSN1991I is produced if DSN1COPY CHECK finds unclustered data in system catalog tablespaces SYSDBASE, SYSPLAN, or SYSVIEWS: DSN1991I UNCLUSTERED DATA DETECTED. RID: record-ID TABLE: table-name INDEX KEY: key-name This message may contain garbled values for key-name or an incorrect value for record-ID. (2) One or more unexpected message MSGDSN1984I DSN1984I UNEXPECTED PAGE NUMBER, EXPECTING: expected-page-number FOUND: page-number-found These may be followed by message MSGDSN1993I DSN1993I DSN1COPY TERMINATED, page-count PAGES PROCESSED (3) An invalid print control character in column 0 may occur when DSN1COPY prints a blank line to the job output. When DSN1COPY RESET is run against the system catalog tablespaces SYSDBASE, SYSPLAN, or SYSVIEWS, users may see: (4) Unexpected message MSGDSN1948I DSN1948I DSN1COPY UNABLE TO RESET DICTIONARY VERSION. As the system catalog tablespaces SYSDBASE, SYSPLAN and SYSVIEWS do not exist in V10 NFM, these problems will not occur in V10 NFM. DSN1COPY has been modified to correct tokens in DSN1991I message, to correct the print control character in blank lines, and to prevent unexpected DSN1984I and DSN1948I messages. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64805 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN1COPY PM64805 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64805 DSN1COPY THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN1COPY 1 LISTEND UK81472 COVER LETTER END UK81474 COVER LETTER START PROBLEM DESCRIPTION(S): PM69859 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who have queries * * containing a GROUP BY clause within a * * table expression or materialized view * * running in parallel. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC04 IN DSNIWNRF+1EBE MAY * * OCCUR FOR A QUERY CONTAINING GROUP * * BY WITHIN TABLE EXPR/MATERIALIZED * * VIEW AND RUNS PARALLEL. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC04 in DSNIWNRF+1EBE may occur for a query containing GROUP BY within TABLE EXPR/MATERIALIZED VIEW and runs in parallel. The following is an example of such failing scenario: SELECT .... FROM T1 LEFT OUTER JOIN (SELECT ... FROM T2 RIGHT OUTER JOIN (SELECT ... FROM T3 INNER JOIN (SELECT ... FROM T4, ... WHERE ... GROUP BY ... ORDER BY ...) AS TAB2 ON TAB2.C1 = T3.C1 GROUP BY TAB2.C2,...) AS TAB3 ON TAB3.C1 = T2.C1) AS TAB4 ON TAB4.C1 = T1.C1 GROUP BY ... DB2 is fixed to process the GROUP BY within table expression or materialized view correctly when the query runs in parallel. Additional keywords: SQLGROUPBY SQLVIEW SQLTABLEEXPR PARALLELISM SQLPARALLELISM DEGREEANY DB2PARALL/K ABEND0C4 RC00000004 DSNIWNRF+1EBE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69859 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM69859: 1 See PM69859 APAR/PTF text for additional information about why a REBIND is necessary. PM69859 corrects a problem of ABEND0C4 RC04 IN DSNIWNRF+1EBE when query contains a GROUP BY clause within a table expression or materialized view and 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOMW PM69859 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69859 DSNXOMW THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOMW LISTEND UK81474 COVER LETTER END UK81511 COVER LETTER START PROBLEM DESCRIPTION(S): PM63698 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users using the BIND * * QUERY command and using an ALIAS on the * * DSN_USERQUERY_TABLE. * **************************************************************** * PROBLEM DESCRIPTION: There are two problems fixed by this * * APAR. * * * * Problem 1. * * * * When an user in a RACF group issues the * * BIND QUERY command, it may fail as * * follows: * * * * 1. The RACF group has the SYSADM / * * SYSCTRL / SQLADM authority. * * 2. Create the DSN_USERQUERY_TABLE * * under the RACF group. * * 3. The user creates an alias on * * the DSN_USERQUERY_TABLE described * * in step 2. * * 4. When the user submits a BIND * * QUERY command, it may fail with * * message DSNT291I saying the user * * does not have the privilege to * 1 * perform operation insert on * * object DSN_USERQUERY_TABLE. * * * * Problem 2. * * When the BIND QUERY command is issued * * with the LOOKUP(YES) option from a * * stored procedure, message DSNT289I may * * not be issued upon the successful * * processing of the command. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a user in a RACF group issues the BIND QUERY command, it may fail as follows: 1. The RACF group has the SYSADM / SYSCTRL / SQLADM authority. 2. Create the DSN_USERQUERY_TABLE under the RACF group. 3. The user creates an alias on the DSN_USERQUERY_TABLE described in step 2. 4. When the user submits a BIND QUERY command, it may fail with message DSNT291I saying the user does not have the privilege to perform operation insert on object DSN_USERQUERY_TABLE. The problem is that the secondary IDs are not checked in the authority checking routines. The APAR also makes the fix to issue message DSNT289I upon the successful processing of the BIND QUERY LOOKUP(YES) command from a stored procedure. The APAR fixes the problem by checking the secondary IDs when checking whether the user who issues the BIND QUERY command has the privilege to perform operation INSERT on the DSN_USERQUERY_TABLE under the RACF group ID. The APAR also fixes the problem to issue message DSNT289I upon successful processing of the BIND QUERY LOOKUP(YES) command issued from a stored procedure. Additional Keywords: BINDQUERY MSGDSNT289I MSGDSNT291I COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63698 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 PM63698 DSNXOD0Z PM63698 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63698 DSNXOBNQ DSNXOD0Z THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXOBNQ DSNXOD0Z LISTEND UK81511 COVER LETTER END UK81517 COVER LETTER START PROBLEM DESCRIPTION(S): PM66536 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries * * containing joins. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may produce an inaccurate filter * * factor estimation for a join predicate * * if index probing is used. * **************************************************************** * RECOMMENDATION: * **************************************************************** Index probing can help the optimizer better estimate the filter factor of local predicates. But a problem was found that DB2 might produce an inaccurate filter factor estimation of a join predicate if index probing is used. For example, SELECT * FROM T1 ,T2 WHERE T1.C1=T2.C1 AND T1.C1 BETWEEN 100 AND 200 AND T2.C1 BETWEEN 100 AND 200; If an index IX1 is defined on T1.C1 and an index IX2 is defined on T2.C1 and index probing is triggered to improve filter factor estimation of "T1.C1 BETWEEN 100 AND 200" and "T2.C1 BETWEEN 100 AND 200", the filter factor of "T1.C1=T2.C1" may be estimated inaccurately. Besides equal join predicates, the filter factor of range or between join predicates may be estimated inaccurately too if index probing is triggered for both sides of the join predicates. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE INDEX PROBING FILTERFACTOR Code has been corrected to produce an accurate filter factor estimation for a join predicate in a case described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66536 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: 1 ***Action for PM45048: See PM45048 APAR/PTF text for additional information about why a REBIND is necessary. PM45048 corrects a problem of a wrong filter factor for the DISTINCT FROM predicate if COLCARDF of the column is 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 PM31741: See PM31741 APAR/PTF text for additional information about why a REBIND is necessary. PM31741 corrects a problem that DB2 may intermittently produce an inaccurate filter factor of an equal join predicate when the columns on both sides have histogram statistics. 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 DSNXOCMP PM66536 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66536 DSNXOCMP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCMP LISTEND UK81517 COVER LETTER END UK81520 COVER LETTER START PROBLEM DESCRIPTION(S): PM69522 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users who wish to use IBM DB2 Sort * * for z/OS V1.3 * **************************************************************** * PROBLEM DESCRIPTION: Enable DB2 utilities to benefit from * * performance improvements provided with * * IBM DB2 Sort for z/OS V1.3. * **************************************************************** * RECOMMENDATION: Apply PTF when available * **************************************************************** 1 This PTF enables DB2 utilities to benefit from performance improvements in DB2 Sort for z/OS V1.3. Code has been changed to support new function in DB2 Sort for z/OS V1.3. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69522 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCRIB PM69522 DSNUCSRT PM69522 DSNUGALC PM69522 DSNUGLSR PM69522 DSNUGMRP PM69522 DSNUGSOR PM69522 DSNUGSRP PM69522 DSNUGSRT PM69522 DSNUKPIK PM69522 DSNUKXSR PM69522 DSNURPCT PM69522 DSNURPIB PM69522 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69522 DSNUCRIB DSNUCSRT DSNUGALC DSNUGLSR DSNUGMRP DSNUGSOR DSNUGSRP DSNUGSRT DSNUKPIK DSNUKXSR DSNURPCT DSNURPIB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCRIB DSNUCSRT DSNUGALC DSNUGLSR DSNUGMRP DSNUGSOR DSNUGSRP DSNUGSRT DSNUKPIK DSNUKXSR DSNURPCT DSNURPIB LISTEND UK81520 COVER LETTER END UK81537 COVER LETTER START PROBLEM DESCRIPTION(S): PM70083 - **************************************************************** * USERS AFFECTED: All DB2 10 for Z/OS users of XMLTABLE * * function * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXMLSM:M098 * 1 * occurred when XMLTABLE function has * * parent axis in its column expression * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E70005 at DSNXMLSM:M098 might occur when XMLTABLE function has parent axis in its column expression. DB2 abends because logic error exists when handling XML storage. For example, the following query has parent axis ('../e') in the column L_shipmode of XMLTABLE X2, and may cause the abend: SELECT X2.L_shipmode FROM T1 as C, T2 as D, XMLTABLE('/a/b/c' PASSING C.DOC1 COLUMNS L_shipmode CHAR(20) PATH '.' ) X1 , XMLTABLE('/a/b/c' PASSING D.DOC2 COLUMNS L_shipmode char(20) path '../e' ) X2; DB2 was fixed to handle the XML storage correctly. Additional keywords: XMLALL SQLXML COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70083 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNOCCN PM70083 DSNNOGET PM70083 DSNNQIV PM70083 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70083 DSNNOCCN DSNNOGET DSNNQIV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOCCN DSNNOGET DSNNQIV LISTEND UK81537 COVER LETTER END UK81542 COVER LETTER START PROBLEM DESCRIPTION(S): PM67713 - **************************************************************** 1 * USERS AFFECTED: All DB2 users who run REPAIR DBD against a * * database which has trigger defined. * **************************************************************** * PROBLEM DESCRIPTION: REPAIR DBD REBUILD could hit * * ABEND04E RC00E30001 in DSNTLDU * * OFFSET06CC * **************************************************************** * RECOMMENDATION: * **************************************************************** When there is a trigger defined in the database, REPAIR DBD needs to rebuild the trigger OBD which could cause the reported abend. DB2 code has been changed to avoid the abend. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67713 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUEXDL PM67713 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67713 DSNUEXDL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUEXDL LISTEND UK81542 COVER LETTER END UK81543 COVER LETTER START PROBLEM DESCRIPTION(S): PM69145 - **************************************************************** * USERS AFFECTED: All DB2 users who explicitly create an * * index over an AUXILIARY TABLE. * **************************************************************** * PROBLEM DESCRIPTION: Customer may hit ABEND04E at DSNGDVUT * * ERQUAL50C8 and REPAIR DBD DIAGNOSE * * could report the following errors, * * * * DSNU920I DSNUEDRA - OBDS DIFFER AT * * OFFSET X'0000005C' OBDAFS(1) * * DSNU904I DSNUEDRA - EXISTING VALUE * * X'01C5' * * DSNU905I DSNUEDRA - REBUILT VALUE * * X'0000' * * DSNU920I DSNUEDRA - OBDS DIFFER AT * * OFFSET X'00000060' OBDAIPS(1) * * DSNU904I DSNUEDRA - EXISTING VALUE * * X'01EC' * * DSNU905I DSNUEDRA - REBUILT VALUE * 1 * X'0000' * * * * Also: * * DSNU915I DSNUEDLO - OBD X'0175' * * E-X'00007574' R-X'00007574' AN AUX. * * RELATIONS * * DSNU915I DSNUEDLO - OBD X'01C5' * * E-X'00000000' R-X'00000000' - OBID * * NOT ASSIGN * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 does not write the correct log record when creating an auxiliary index, which causes the above problems if the create is roll back. DB2 has been changed so that the correct log record is written out. Applying this apar will not fix the broken OBD which is introduced before. REPAIR DBD REBUILD can fix the broken OBD. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69145 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDARA PM69145 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69145 DSNGDARA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDARA LISTEND UK81543 COVER LETTER END UK81546 COVER LETTER START PROBLEM DESCRIPTION(S): PM67208 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users of * * INSTEAD OF TRIGGERS * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output on INSERT with INSTEAD * * OF TRIGGERs * **************************************************************** * RECOMMENDATION: * **************************************************************** Users may experience incorrect output in a Unicode or ASCII table that contains character columns upon INSERT when an INSTEAD OF trigger is defined on a view referencing that table. 1 A sample scenario would be: CREATE TABLESPACE TSP1U CCSID UNICODE; CREATE TABLE TAB1U ( ID SMALLINT GENERATED BY DEFAULT AS IDENTITY, DESC CHAR(38), COL3 CHAR(1) NOT NULL WITH DEFAULT ) IN TSP1U; CREATE VIEW VW1 AS SELECT * FROM TAB1U; CREATE TRIGGER TRG1 INSTEAD OF INSERT ON VW1 REFERENCING NEW AS NEW_B FOR EACH ROW MODE DB2SQL BEGIN ATOMIC INSERT INTO TAB1U ( ID, DESC, COL3 ) VALUES ( NEW_B.ID, NEW_B.DESC, NEW_B.COL3 ) ; END? INSERT INTO VW1 (DESC) VALUES ('Insert via trigger on view'); SELECT ID, DESC AS DESCRIPTION, COL3 AS C3, HEX(COL3) AS H3 FROM TAB1U; +-------------------------------------------------------------+ | ID | DESCRIPTION | C3 | H3 | +-------------------------------------------------------------+ | 0 | Insert via trigger on view | . | 00 | +-------------------------------------------------------------+ The select reveals that C3 should be blank and H3 should be 20 to represent the hex unicode value. DB2 has been fixed to insert the correct values for character columns in the Unicode or ASCII table. This will not fix current wrong values. Users can DELETE the affected rows and rerun the triggering action once this fix is applied. Additional Keywords: SQLINCORR SQLINCORROUT DB2INCORR/K SQLTRIGGER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67208 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 DSNXISCR PM67208 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67208 DSNXISCR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXISCR LISTEND UK81546 COVER LETTER END UK81581 COVER LETTER START PROBLEM DESCRIPTION(S): PM66095 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of decimal data * * with the VARCHAR function or CAST * * specification * **************************************************************** * PROBLEM DESCRIPTION: In Version 10, the formatting of * * decimal data has changed for the * * VARCHAR function and the CAST * * specification with decimal input * * and VARCHAR or CHAR output. * * * * There are two changes: * * * * 1. Leading zeroes are removed * * from the input decimal value. * * * * 2. The decimal point is not returned * * if the scale of the decimal value * * is zero. * **************************************************************** * RECOMMENDATION: * **************************************************************** After application of this PTF, the default behavior for the VARCHAR function and CAST specification with decimal input will revert to the DB2 9 for z/OS result if the BIF_COMPATIBILITY system parameter is set to the new value V9_DECIMAL_VARCHAR. Please refer to the DB2 9 for z/OS SQL Reference for documentation of the formatting of decimal data. Following are examples of the differences in the output of VARCHAR and CAST between V9 and V10 : - Remove leading zero VARCHAR(00.10) or CAST(00.10 AS VARCHAR(4)) or 1 CAST(00.10 AS CHAR(4)) V10 result is '.10' V9 result is '0.10' - No trailing decimal point VARCHAR(1.) CAST(1. AS VARCHAR(2)) or CAST(1. AS CHAR(2)) V10 result is '1' V9 result is '1.' To help with migration to DB2 10 for z/OS and the impact of this change on DB2 applications, the following support is added: 1. This PTF adds a new setting to DB2 subsystem parameter BIF_COMPATIBILITY. The new value is V9_DECIMAL_VARCHAR. APAR PM29124 provided relief for the CHAR function incompatibility and provided a DB2 subsystem parameter, BIF_COMPATIBILITY with options V9 and CURRENT, to enable and disable it. This PTF increases the scope of DB2 subsystem parameter BIF_COMPATIBILITY to include VARCHAR, CAST( dec AS CHAR) and CAST( dec AS VARCHAR). It also adds a third option, V9_DECIMAL_VARCHAR. These settings allow you to specify whether: * The current-release format should be returned by all of these expressions (BIF_COMPATIBILITY=CURRENT) * The V9 format should be returned by all of these expressions (BIF_COMPATIBILITY=V9_DECIMAL_VARCHAR) * The current release format should be used by all of these expressions except the CHAR function which should return the V9 format (BIF_COMPATIBILITY=V9) +-------------------------------------------------+ | BIF_- | Example inputs and results (1) | | COMPAT- |---------------------------------------| | IBILITY | CHAR(000.1) | CHAR(1000.) | CHAR(1.1) | |---------|-------------|-------------|-----------| | CURRENT | '.1' | '1000' | '1.1' | |---------|-------------|-------------|-----------| | V9 | ' 000.1' | ' 1000.' | ' 1.1' | |---------|-------------|-------------|-----------| | V9_DEC- | | | | | IMAL_- | ' 000.1' | ' 1000.' | ' 1.1' | | VARCHAR | | | | +-------------------------------------------------+ +-------------------------------------------------+ | BIF_- | Example inputs and results (2) | | COMPAT- |---------------------------------------| | IBILITY | VARCHAR('00.10') | VARCHAR('1.') | |---------|--------------------|------------------| | CURRENT | '.10' | '1' | |---------|--------------------|------------------| 1 | V9 | '.10' | '1' | |---------|--------------------|------------------| | V9_DEC- | | | | IMAL_- | '0.10' | '1.' | | VARCHAR | | | +-------------------------------------------------+ For DB2 data sharing it is recommended that all members use the same setting. After applying this PTF, please refer to the ++HOLD directions to set the zparm value to V9_DECIMAL_VARCHAR if V9 results are desired. a. Static SQL If a package has been bound on V10 with static SQL then it must be rebound to pick up the new zparm value and return V9 results. If a package has been bound on V9 with static SQL then it will return V9 results. No rebind is necessary. b. Dynamic SQL Dynamic SQL will return V9 results once the new zparm value is set. Views, materialized query tables(MQTs),and index on expressions (IOEs) created before Version 10 will continue to get V9 behavior. 2. DB2 will write an IFCID 366 trace record when the V9 format is returned on DB2 10. The trace will be written out once per thread for a particular SQL statement. The trace record will help identify which applications need to be changed to support the new behavior. Note that if an index on expression(IOE) is created with VARCHAR/CAST in the index key, that the trace will be written during the execution of the INSERT SQL statement that inserts into the index. Likewise for a materialized query table (MQT), the trace record will be written on REFRESH TABLE. The trace can be started using the command: -start trace(p) class(32) ifcid(366) IFCID 366 was added by apar PM29124. This apar adds a new value for QW0366FN to indicate VARCHAR or CAST executed using the V9 semantics. QW0366FN F The value '1' indicates that the DB2 9 for z/OS SYSIBM.CHAR(decimal-expr) function has been executed. The value '2' indicates that the DB2 for z/OS Version 9 SYSIBM.VARCHAR(decimal-expr) function, CAST (decimal AS CHAR) or CAST (decimal AS VARCHAR) expression has been executed. 1 3. System schemas, SYSCOMPAT_V9 and SYSCURRENT, can be used in the current path special register or PATH bind option. These schemas can be used to override the zparm behavior for a particular application. The VARCHAR function has been added to these schemas by this PTF. Currently the CHAR function only exists in these schemas. The new schema names must be in front of SYSIBM in the path to be effective. The schemas and zparm value are used during function resolution to determine which CHAR or VARCHAR function will be invoked (V10 or V9). A bind, rebind, prepare or create must be done to change any existing application or object (MQT or IOE ) to use the new CHAR or VARCHAR function. The CAST specifications will only be controlled by the zparm. The schemas do not apply to CAST. --------------------------------------------------------------- To switch to new behavior in V10 : 1. Specify BIF_COMPATIBILITY zparm as V9_DECIMAL_VARCHAR 2. Monitor the 366 trace records to identify applications that may need changes for the new V10 behavior. 3. Change any affected applications to handle the new V10 VARCHAR and CHAR behavior. For CAST, rewrite it using the appropriate CHAR or VARCHAR function and a CAST to the correct length if needed. 4. Rebind/Prepare the package using the PATH with SYSCURRENT to use the new V10 CHAR and VARCHAR built-in functions. SYSCURRENT does not apply to CAST so CAST needs to be rewritten using one of the built-in functions. Note : For native stored procedures (SQLPL) and non-inline SQL scalar functions, follow the directions in bullet 3 for a package. 5. For views referencing these functions/casts, determine if the view needs to be changed to get the desired output. Drop and recreate the view using the path bind option with SYSCURRENT only if necessary. Then rebind any applications referencing the view using the path bind option with SYSCURRENT to use the new V10 CHAR or VARCHAR built-in functions. Note : For inline SQL scalar functions, follow the directions in bullet 4 for views. 6. For MQTs or IOEs referencing these functions/casts, drop and recreate the MQT or IOE using the path bind option with SYSCURRENT. Execute REFRESH TABLE for MQTs. Then rebind any applications referencing the MQT or IOE using the path bind option with SYSCURRENT to use the new V10 CHAR or VARCHAR built-in function. 7. Change the BIF_COMPATIBILITY zparm to CURRENT when all applications have been changed. New applications, rebinds, creates will use the new VARCHAR or CHAR or 1 CASTs. Additional keywords : SQLMIGRATION SQLVARCHAR SQLCAST SQLDECIMAL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66095 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66095: See PM66095 APAR/PTF text for additional information about why a REBIND is necessary. PM66095 adds BIF_COMPATIBILITY support for VARCHAR(decimal) function, the CAST(decimal AS CHAR(n)) and CAST(decimal AS VARCHAR(n)) specifications. If V9 results are desired for these expressions then a rebind must be done if a package meets the following criteria: 1- The package has been bound on V10 2- The package contains static SQL using VARCHAR(decimal) or CAST(decimal AS CHAR(n)) or CAST(decimal AS VARCHAR(n)) To make this fix effective for a static application, it must be rebound after application of this PTF. The BIF_COMPATIBILITY system parameter should be set to V9_DECIMAL_VARCHAR before rebinding. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: ***Action for PM62940: See PM62940 APAR/PTF text for additional information about why a REBIND is necessary. PM62940 corrects a problem of incorrectly issued SQLCODE 445 for an INSERT statement whose source column is a table expression or view column. This column is CAST and derived from the NULLIF function which has an empty string as the 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. DB2BIND: ***Action for PM55452: See PM55452 APAR/PTF text for additional information about 1 why a REBIND is necessary. PM55452 corrects a problem that ABEND0C7 RC00000000 at the location DSNXGRDS.DSNXRFN OFFSET80DE (OFFSET80BE, or OFFSET85FE) could happen when an static sensitive scrollable for update cursor is defined for a SELECT statement where an OLAP function is used. 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 PM66095 This PTF adds a new setting to DB2 subsystem parameter BIF_COMPATIBILITY. V9_DECIMAL_VARCHAR ---------------------------------------------------------------- DB2 Version 10 introduced an incompatible change in the formatting of decimal data by the CHAR, VARCHAR, CAST( ... AS CHAR) and CAST( ... AS VARCHAR) built-in functions (BIFs). Beginning in V10, when the input data is decimal, these functions no longer return: * leading zeros * the trailing decimal point character * leading blanks for positive decimal values (CHAR only) APAR PM29124 provided relief for the CHAR function incompatibility and provided a DB2 subsystem parameter, BIF_COMPATIBILITY with options V9 and CURRENT, to enable and disable it. This PTF increases the scope of DB2 subsystem parameter BIF_COMPATIBILITY to include VARCHAR, CAST( ... AS CHAR) and CAST( ... AS VARCHAR) BIFs. It also adds a third option, V9_DECIMAL_VARCHAR. These settings allow you to specify whether: * The current-release format should be returned by all of these functions (BIF_COMPATIBILITY=CURRENT) * The V9 format should be returned by all of these functions (BIF_COMPATIBILITY=V9_DECIMAL_VARCHAR) * The current release format should be used by all of these functions except the CHAR function which should return the V9 format (BIF_COMPATIBILITY=V9) +-------------------------------------------------+ | BIF_- | Example inputs and results (1) | | COMPAT- |---------------------------------------| | IBILITY | CHAR(000.1) | CHAR(1000.) | CHAR(1.1) | |---------|-------------|-------------|-----------| | CURRENT | '.1' | '1000' | '1.1' | |---------|-------------|-------------|-----------| | V9 | ' 000.1' | ' 1000.' | ' 1.1' | |---------|-------------|-------------|-----------| | V9_DEC- | | | | 1 | IMAL_- | ' 000.1' | ' 1000.' | ' 1.1' | | VARCHAR | | | | +-------------------------------------------------+ +-------------------------------------------------+ | BIF_- | Example inputs and results (2) | | COMPAT- |---------------------------------------| | IBILITY | VARCHAR('00.10') | VARCHAR('1.') | |---------|--------------------|------------------| | CURRENT | '.10' | '1' | |---------|--------------------|------------------| | V9 | '.10' | '1' | |---------|--------------------|------------------| | V9_DEC- | | | | IMAL_- | '0.10' | '1.' | | VARCHAR | | | +-------------------------------------------------+ For DB2 data sharing it is recommended but not required that all members use the same setting. BIF_COMPATIBILITY is externalized on installation panel DSNTIPX as BIF COMPATIBILITY. 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) Copy updated DB2 installation panels to alternate libraries (3) Update your customized copy of job DSNTIJUZ (4) Update private copies of the DSNTIDxx CLIST input member (5) Modify and rebind any applications that use the VARCHAR(decimal), CAST( decimal AS CHAR) and CAST( decimal AS VARCHAR) 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) 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 DB2 installation panels DSNTIPX in the 1 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 DSNTIP8 panel to that library. ---------------------------------------------------------------- (3) 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 or update the keyword parameter BIF_COMPATIBILITY= (where is CURRENT, V9, or V9_DECIMAL_VARCHAR), to the invocation of the DSN6SPRM macro in your customized copy of installation job DSNTIJUZ. Make sure to add a continuation character in column 72 if needed. If you omit adding BIF_COMPATIBILITY here, the value will be set to the default of CURRENT 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. ---------------------------------------------------------------- (4) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF adds an entry for BIF_COMPATIBILITY 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: BIF_COMPATIBILITY CHAR G NONE NONE Change to the value you specified for BIF_COMPATIBILITY in step (3), above. ---------------------------------------------------------------- (5) Application and object changes may be needed when applying this PTF. The actions depend on the value of the BIF_COMPATIBILITY system parameter. Please read the applicable section below. ---------------------------------------------------------------- ACTION: ***Action for PM63892 (V10) 1 This PTF fixes a bug in the DB2 installation CLIST that can cause it to store more than one entry for subsystem parameter DSN6FAC.DDF_COMPATIBILITY to the CLIST output (DSNTIDxx) member. This PTF also fixes the installation CLIST not to force EN_PJSJ=ON in job DSNTIJUZ when the CLIST is run in MIGRATE mode with an INPUT MEMBER NAME of DSNTIDXA or DSNTIDXB. 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) Update private copies of the DSNTIDxx CLIST input member 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 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 private copies of the DSNTIDxx CLIST input member *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF fixes a bug in the DB2 installation CLIST that can cause it to store more than one entry for subsystem parameter DSN6FAC.DDF_COMPATIBILITY to the CLIST output (DSNTIDxx) member. This PTF also fixes the installation CLIST not to force EN_PJSJ=ON in job DSNTIJUZ when the CLIST is run in MIGRATE mode with an INPUT MEMBER NAME of DSNTIDXA or DSNTIDXB. You need to verify that private copies of your DSNTIDxx member contain at most one entry for DDF_COMPATIBILITY. Delete any duplicate entries, then verify that in the remaining entry, the last (rightmost) field contains the setting you use for DDF_COMPATIBILITY (either NONE or SP_PARMS_NJV). If you run DB2 with the DSN6SPRM.EN_PJSJ parameter set to OFF, you also need to verify that the entry for EB_PJSJ is correct in your DSNTIDxx member. If the setting (which is stored in the 6th field of the entry) is ON, you need to change it to OFF as shown below: EN_PJSJ CHAR M OFF ON OFF | EN_PJSJ setting --+ ACTION: 1 ***Action for PM63753 (V10) This PTF fixes a bug in DB2 subsystem parameter macro DSN6SPRM that causes it to increase SRTPOOL parameter settings of less than 10000 to 10000. SRTPOOL, which specifies the amount of storage in kilobytes that is needed for the DB2 sort pool, can range from 240 to 128000. When this PTF is applied, SRTPOOL settings between 240 and 9999 will again be honored when you assemble the DB2 subsystem parameter (DSNZPxxx) module. If you have already installed or migrated to DB2 10 then, after applying this PTF, review your current setting for the SRTPOOL parameter. If that setting is less than 10000, be aware that the amount of storage available for the DB2 sort pool will be reduced from 10000 kilobytes to the specified setting (in kilobytes) the next time you assemble the DB2 subsystem parameter (DSNZPxxx) module. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQW05 PM66095 DSNTINST PM66095 DSNTIPX PM66095 DSNWZIFA PM66095 DSNXGSFN PM66095 DSNXOCF PM66095 DSNXODTR PM66095 DSNXODTX PM66095 DSNXOEX1 PM66095 DSNXOFN2 PM66095 DSNXONZQ PM66095 DSNXONZS PM66095 DSNXOOS1 PM66095 DSNXOOS2 PM66095 DSNXORFN PM66095 DSNXOSCF PM66095 DSNXOV0 PM66095 DSNXOXEX PM66095 DSNXRSBC PM66095 DSNXRSB9 PM66095 DSN6SPRM PM66095 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66095 DSNDQW05 DSNTINST DSNTIPX DSNWZIFA DSNXGSFN DSNXOCF DSNXODTR DSNXODTX DSNXOEX1 DSNXOFN2 DSNXONZQ DSNXONZS DSNXOOS1 DSNXOOS2 DSNXORFN DSNXOSCF DSNXOV0 DSNXOXEX DSNXRSBC DSNXRSB9 DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWZIFA DSNXGSFN DSNXOCF DSNXODTR DSNXODTX DSNXOEX1 1 DSNXOFN2 DSNXONZQ DSNXONZS DSNXOOS1 DSNXOOS2 DSNXORFN DSNXOSCF DSNXOV0 DSNXOXEX DSNXRSBC DSNXRSB9 MACROS DSNDQW05 DSNTINST DSNTIPX DSN6SPRM LISTEND UK81581 COVER LETTER END UK81612 COVER LETTER START PROBLEM DESCRIPTION(S): PM66237 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users of * * SYSPROC.XSR_COMPLETE stored procedure. * **************************************************************** * PROBLEM DESCRIPTION: When executing SYSPROC.XSR_COMPLETE * * procedure to complete the registration * * of an XML Schema, SQLCODE -443 may * * occur with SQLCODE -302 in its * * diagnostic text. * **************************************************************** * RECOMMENDATION: * **************************************************************** SYSPROC.XSR_COMPLETE procedure uses integer STRINGID values from SYSIBM.SYSXMLSTRINGS table and converts them into character strings. The size of character datatype used inside the procedure is only big enough to store 5 digits (CHAR(5)). If the STRINGID value is larger that 99999, the SQL statement inside the procdure will fail with SQLCODE -302 and the CALL statement to the procedure will fail with SQLCODE -443. The size of character datatype inside the SYSPROC.XSR_COMPLETE procedure is increased to be able to contain conversion of STRINGID values from SYSIBM.SYSXMLSTRINGS table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66237 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Users need to process the following commands to bind the packages that are updated as a result of installing this PTF: 1 BIND PACKAGE(SYSXSR) MEMBER(DSNNVXCM) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(UNICODE) - LIBRARY('.SDSNDBRM') BIND PACKAGE(SYSXSR) MEMBER(DSNNVXCV) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(UNICODE) - LIBRARY('.SDSNDBRM') Note: is the data set prefix of your DB2 10 target libraries COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@VXCM PM66237 DSN@VXCV PM66237 DSNX9SPJ PM66237 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66237 DSN@VXCM DSN@VXCV DSNX9SPJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSN@VXCM DSN@VXCV DSNX9SPJ LISTEND UK81612 COVER LETTER END UK81618 COVER LETTER START PROBLEM DESCRIPTION(S): PM70086 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: Packages may run with incorrect * * isolation level. * **************************************************************** * RECOMMENDATION: * **************************************************************** When binding packages without specifying ISOLATION bind option, a default of the plan value is used. At runtime, the ISOLATION value bound with the plan is used. There is a code bug which results in these packages picking up the current plan isolation value instead of the isolation value bound with the plan. As the current plan isolation value and the isolation value bound with the plan could be different, these packages may run with the incorrect isolation value. DB2 has been corrected to pick up the isolation value bound with the plan when running packages with an isolation default of the plan value. Additional Keywords: SRCN904, TIMEOUT, DEADLOCK, RC00C90088, RC00C9008E, MSGDSNT501I 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70086 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEAAL PM70086 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70086 DSNXEAAL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEAAL LISTEND UK81618 COVER LETTER END UK81641 COVER LETTER START PROBLEM DESCRIPTION(S): PM71586 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users with queries * * containing LIKE predicates with * * an escape-expression. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E7005 IN DSNXOIXP :M888 * * may occur on a bind of a query * * containing a LIKE predicate with * * an escape-expression. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E7005 IN DSNXOIXP :M888 may occur on a bind of a query containing a LIKE predicate with an escape-expression due to uninitialized storage. For example... SELECT ... FROM T1 WHERE T1.C1 LIKE 'ABC' ESCAPE '\' Additional Keywords: ABEND04E SQLLIKE SQLESCAPE The problem is fixed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71586 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 DSNXOIXP PM71586 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71586 DSNXOIXP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOIXP LISTEND UK81641 COVER LETTER END UK81668 COVER LETTER START PROBLEM DESCRIPTION(S): PM68576 - **************************************************************** * USERS AFFECTED: DB2 users of stored procedures and * * User Defined Functions (UDFs). * **************************************************************** * PROBLEM DESCRIPTION: Stored procedure thread hangs after * * the stored procedure timed out. * * * * ABEND0C4 at DSNVGEPL.DSNVRDAG+1B38 * * at UK62436 level followed by * * RC00E20017 at DSNSTACK * * and DB2 abnormally terminated with * * RC00F30420. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. An incorrect serialization was used in processing the stored procedure or UDF thread that was timed out. 2. A WLM service macro was invoked in an incorrect amode. 3. Stored procedure thread was terminated by CALLRTM while it was still in the processing of terminating other execution unit. 1. Incorrect serialization is fixed. 2. Code has been changed so that WLM service macro can be invoked in the correct mode. 3. Stored procedure recovery has been fixed so that it won't terminate the stored procedure thread aggressively while other recovery is still going on. This will protect DB2 subsystem from abnormal termination. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68576 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNX9EMR PM68576 DSNX9GPL PM68576 DSNX9MON PM68576 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68576 DSNX9EMR DSNX9GPL DSNX9MON THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNX9EMR DSNX9GPL DSNX9MON LISTEND UK81668 COVER LETTER END UK81677 COVER LETTER START PROBLEM DESCRIPTION(S): PM65999 - **************************************************************** * USERS AFFECTED: All DB2 Users of the -STOP DATABASE * * command. * **************************************************************** * PROBLEM DESCRIPTION: Threads could be held suspended * * waiting for -STOP DATABASE command * * completion and could prevent SHUTDOWN * * CHECKPOINT from completing. * **************************************************************** * RECOMMENDATION: * **************************************************************** The -STOP DATABASE command incorrectly handled checking the STOP PENDING status for tasks that could end during the processing of the -STOP DATABASE command. The STOP PENDING check in the -STOP DATABASE command was changed to account for the possibility of tasks ending during the processing of the -STOP DATABASE command. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65999 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 PM65999 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65999 DSNTADL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTADL LISTEND UK81677 COVER LETTER END UK81679 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM66628 - **************************************************************** * USERS AFFECTED: All DB2 Users of the -DISPLAY DATABASE(*) * * SPACENAM(*) RESTRICT/ADVISORY command. * **************************************************************** * PROBLEM DESCRIPTION: The -DISPLAY DATABASE(*) SPACENAM(*) * * RESTRICT/ADVISORY command displayed * * '***psid' in some circumstances where * * the space name was available. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the case of GRECP or other STATUS conditions that could hold locks on the space the -DISPLAY DATABASE(*) SPACENAM(*) RESTRICT/ADVISORY command displayed '***psid' where the space name was available. The -DISPLAY DATABASE(*) SPACENAM(*) RESTRICT/ADVISORY command was updated to attempt a second catalog lookup of the space name when the initial internal report of RESTRICT or ADVISORY objects returned unknown space names. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66628 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTDMST PM66628 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66628 DSNTDMST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTDMST LISTEND UK81679 COVER LETTER END UK81685 COVER LETTER START PROBLEM DESCRIPTION(S): PM69802 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS data sharing users with * * PM56555 / UK79050 applied and DB2 9 for z/OS * * data sharing users with PM56555 / UK79051 * * applied * **************************************************************** * PROBLEM DESCRIPTION: Remote possibility for triggering an * * infinite loop exists in data sharing * * after applying APAR PM56555 (V10 PTF * * UK79050 / V9 PTF UK79051), leading to * * a very high percentage of CPU usage * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** With APAR PM56555 applied (V10 PTF UK79050 / V9 PTF UK79051), theoretically, under some error conditions where a DBET entry is already broken, a tight loop could be triggered, causing a very high percentage of CPU usage. This tight loop has not actually been exposed and there is no known way to expose it under normal conditions. However, to be on the side of caution, the APAR PM56555 fix needs to be changed to avoid the possibility of infinite looping. DB2 code has been updated to correct said loop. Additional keywords: DB2DSHR SYSPLEXDS LOOPDSNIDBPL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69802 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBLG PM69802 DSNIDBPL PM69802 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69802 DSNIDBLG DSNIDBPL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBLG DSNIDBPL LISTEND UK81685 COVER LETTER END UK81688 COVER LETTER START PROBLEM DESCRIPTION(S): PM68271 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Common Table * * Expression. * **************************************************************** * PROBLEM DESCRIPTION: Unexpected SQLCODE -206 could be issued * * when an SQL statement satisfied the * * following conditions: * * 1. Common table expression has no * * column name list specified, and * * the fullselect used to define the * * common table expression has star * * in its select list, * * 2. SQL statement references above * * common table expression more than * * once, and there is star in the * 1 * select list of the common table * * expression reference . * **************************************************************** * RECOMMENDATION: * **************************************************************** Unexpected SQLCODE -206 could be issued when an SQL statement satisfied the following conditions: 1. Common table expression has no column name list specified, and the fullselect used to define the common table expression has star in its select list, 2. SQL statement references above common table expression more than once, and there is star in the select list of the common table. The following example could recreate the problem, CREATE TABLE T1(C1 INTEGER, C2 VARCHAR(15)); WITH MYCTE AS (SELECT C.* FROM T1 C) SELECT B.C2 FROM MYCTE A LEFT JOIN (SELECT * FROM MYCTE ) B ON A.C1=B.C1 ; DB2 is updated correctly to handle the SQL statement with common table expression correctly. Additional Keywords: SQLCTE SQL206 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68271 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66232: See PM66232 APAR/PTF text for additional information about why a REBIND is necessary. PM66232 corrects a problem of incorrect output for an SQL statement that references to a CTE with ORDER BY clause and the order by column is not on the SELECT list of the CTE. The CTE contains a subquuery. To make this fix effective for a static application, it must be rebound after application of this PTF. Views or MQTs with the above symptom need to be dropped and recreated. Review the PTF cover letter to determine which, if any, applications could be affected by this change. DB2BIND: PM63969 corrects a problem where malformed text may appear in the TEXT column of DSN_PREDICAT_TABLE and/or NODE_DATA column of DSN_QUERY_TABLE. A rebind is necessary for static applications to pick up the correct text. 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 DSNXOP0 PM68271 DSNXOTDA PM68271 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68271 DSNXOP0 DSNXOTDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOP0 DSNXOTDA LISTEND UK81688 COVER LETTER END UK81697 COVER LETTER START PROBLEM DESCRIPTION(S): PM70567 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of REORG TABLESPACE SHRLEVEL NONE utility * **************************************************************** * PROBLEM DESCRIPTION: Extra DBET TABLE ENTRY locks (DBALLOC) * * acquired during REORG TABLESPACE * * SHRLEVEL NONE utility against a * * partitioned table space with at least * * one NPSI defined on it * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When a REORG TABLESPACE SHRLEVEL NONE utility was executed on a partitioned table space with at least one non-partitioned secondary index (NPSI) defined on it, there were many extra DBET DBALLOC type locks acquired during REORG for setting and resetting page set rebuild pending (PSRBDP) state for the NPSIs. The problem happened because REORG requests DBET to set and reset PSRBDP for each logical partition of the NPSIs but without passing the partition number, so that DBET processes the whole index space and requests DBALLOC locks for all logical partitions for each logical partition processed. REORG TABLESPACE SHRLEVEL NONE utility code is changed to avoid duplication of requesting DBALLOC lock for NPSIs when setting or resetting PSRBDP state for NPSIs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70567 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 DSNUGRST PM70567 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70567 DSNUGRST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGRST LISTEND UK81697 COVER LETTER END UK81719 COVER LETTER START PROBLEM DESCRIPTION(S): PM70181 - **************************************************************** * USERS AFFECTED: All DB2 users of RECOVER BACKOUT YES * * Utility. * **************************************************************** * PROBLEM DESCRIPTION: PERFORMANCE ENHANCEMENT FOR THE RECOVER * * WITH BACKOUT YES UTILITY. * **************************************************************** * RECOMMENDATION: * **************************************************************** Today, LOG UNDO phase of the RECOVER utility with BACKOUT YES, periodically commits the data changes. This commit was intended to restart the utility, in case of log apply failure during UNDO phase. However, today, restart of the RECOVER BACKOUT YES is not supported. i.e. if RECOVER BACKOUT YES fails in any phase, it must be restarted from the beginning. Therefore, periodic commit serves no purpose. The cost of periodic commit is high since it involves forcing out data changes to DASD. This write I/Os are expensive. This APAR will avoid performing periodic commits during LOG UNDO phase which may significantly improve the performance of UNDO phase. DB2 logic of RECOVER utility with BACKOUT YES option is modified to improve the performance of LOG UNDO phase which in turns improves the over all performance of RECOVER BACKOUT YES utility. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70181 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIUNDO PM70181 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70181 DSNIUNDO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNIUNDO LISTEND UK81719 COVER LETTER END UK81720 COVER LETTER START PROBLEM DESCRIPTION(S): PM68842 - **************************************************************** * USERS AFFECTED: DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: Lost 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: * **************************************************************** There are timing windows in which DB2 may fail to register a page for a pageset which is becoming GBP-dependent. This may lead to a missed cross-invalidation and subsequent loss of data. Code has been modified to detect an unregistered page and to either register it or assume that the cached version is invalid. DB2 Log is enhanced by including page p-lock information. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68842 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 PM68842 DSNB1GFP PM68842 DSNB1GRA PM68842 DSNB1LTS PM68842 DSNB1LTX PM68842 DSNB1SWS PM68842 DSNB5CMX PM68842 DSNB5SCM PM68842 DSNB5SC1 PM68842 DSNB5SC2 PM68842 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68842 DSNB1GET DSNB1GFP DSNB1GRA DSNB1LTS DSNB1LTX DSNB1SWS DSNB5CMX DSNB5SCM DSNB5SC1 DSNB5SC2 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1GET DSNB1GFP DSNB1GRA DSNB1LTS DSNB1LTX DSNB1SWS DSNB5CMX DSNB5SCM DSNB5SC1 DSNB5SC2 LISTEND UK81720 COVER LETTER END UK81723 COVER LETTER START PROBLEM DESCRIPTION(S): PM71413 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS RUNSTATS utility * * users collecting HISTORY SPACE statistics * * on indexes. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIBNRF during * * RUNSTATS INDEX UPDATE NONE HISTORY ALL * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When the user executed RUNSTATS INDEX UPDATE NONE HISTORY ALL, the utility ended with ABEND04E RC00C90101 in DSNIBNRF ERQUAL 5002 during an insert into the SYSIBM.SYSINDEXPART_HIST catalog table. MSGDSNT501I and MSGDSNT376I were issued on the console. The problem was caused by a LOCK REQUEST TIMEOUT that occurred during the previous fetch from the catalog. This resulted in the statistics not being set for the insert and thereby causing the abend. The code was modified to force the utility to terminate with ABEND04E RC00E40208 if the fetch to SYSIBM.SYSINDEXPART fails. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71413 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUSUIP PM71413 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71413 DSNUSUIP 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUSUIP LISTEND UK81723 COVER LETTER END UK81725 COVER LETTER START PROBLEM DESCRIPTION(S): PM70302 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the -DISPLAY * * UTILITY, -ALTER UTILITY, and -TERM UTILITY * * utility commands * **************************************************************** * PROBLEM DESCRIPTION: -DIS UTIL, -ALTER UTIL, and -TERM UTIL * * Utility commands are leaving storage * * allocated resulting in the DBM1 address * * space running low on below the bar * * storage. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** Due to a logic error affecting DB2 10 for z/OS New Function Mode only, utility commands acquire the UTEXEC lock but don't free the storage for it when the lock is released. This results in the DB2 DBM1 address space running low on below the bar storage. If the DBM1 address gets to the point that processes cannot acquire more, two of the known abends are ABEND04E RC00E20013 from DSNSGMN and ABEND04E RC00E20003 from DSNSVBK. Utility code has been changed to free the control block used for the lock acquisition. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70302 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGDIS PM70302 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70302 DSNUGDIS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGDIS LISTEND UK81725 COVER LETTER END 1UK81726 COVER LETTER START PROBLEM DESCRIPTION(S): PM65743 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of CHECK DATA on tables with RI * * relationships with PM58793 / UK76910 / * * UK76911 applied. * **************************************************************** * PROBLEM DESCRIPTION: After applying PM58793/UK76910/UK76911, * * CHECK DATA on a child table results * * in ABEND04E RC00E4D5D2 DSNUKIFK+143E * * when the child table is defined but * * the parent table primary key index is * * not defined. Another symption * * ABEND0C4 RC00000011 may occur if the * * number of inconsistencies detected is * * high. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** With the PTF for PM58793 applied (UK76910 or UK76911), CHECK DATA results in ABEND04E RC00E4D5D2 DSNUKIFK OFFSET143E when the child table is defined and the parent table index is not defined. Necessary information can not be obtained from the parent table primary key index's data set because it does not exist. The primary key index was created DEFINE NO and no data was inserted into the parent table yet. The abend could occur if the child table is empty or contains data. The child table might contain data if it was loaded with ENFORCE NO to defer the enforcement of the foreign key relationship. Another symption ABEND0C4 RC00000011 at PSW=077c0001fffff000 may occur if the number of inconsistencies detected is high. Modified CHECK DATA logic to avoid certain unnecessary logic when the parent table primary key index is not defined. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65743 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 PM65743 DSNUKREL PM65743 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65743 DSNUKIFK DSNUKREL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUKIFK DSNUKREL LISTEND UK81726 COVER LETTER END 1 UK81728 COVER LETTER START PROBLEM DESCRIPTION(S): PM70182 - **************************************************************** * USERS AFFECTED: Users of the DSNTESQ samples. * **************************************************************** * PROBLEM DESCRIPTION: Running DSNTESQ samples failed with * * SQLCODE -798 or SQLCODE -747. * **************************************************************** * RECOMMENDATION: * **************************************************************** There are lob columns, rowid columns and auxiliary objects added to the SYSINDEXES and SYSVIEWS catalog tables in DB2 10 for z/OS. The original DSNTESQ samples failed with SQLCODE -798 or SQLCODE -747. The original DSNTESQ samples prior to this PTF: CREATE TABLE SYSINDEXES LIKE SYSIBM.SYSINDEXES IN DSNTESQ.DSNQDBS; INSERT INTO SYSINDEXES SELECT * FROM SYSIBM.SYSINDEXES; CREATE TABLE SYSVIEWS LIKE SYSIBM.SYSVIEWS IN DSNTESQ.DSNQVWS; INSERT INTO SYSVIEWS SELECT * FROM SYSIBM.SYSVIEWS; The insert statements listed above failed with 1: SQLCODE -798 Reason: There are rowid columns defined as GENERATED ALWAYS in the implicit column list in the insert statement Correction: Specify "OVERRIDING USER VALUE" in the insert statement, such as INSERT INTO SYSINDEXES OVERRIDING USER VALUE SELECT * FROM SYSIBM.SYSINDEXES; INSERT INTO SYSVIEWS OVERRIDING USER VALUE SELECT * FROM SYSIBM.SYSVIEWS; 2: SQLCODE -747 Reason: The necessary auxiliary objects are not available. Correction: Make sure the auxiliary objects are created. One way to do that is to use 'STD' as the CURRENT RULES when running the CREATE TABLE statement, such as: SET CURRENT RULES = 'STD'; 1 CREATE TABLE SYSINDEXES LIKE SYSIBM.SYSINDEXES IN DSNTESQ.DSNQDBS; SET CURRENT RULES = 'STD'; CREATE TABLE SYSVIEWS LIKE SYSIBM.SYSVIEWS IN DSNTESQ.DSNQVWS; DSNTESQ has been updated to correct the problem. Additional Keywords: SQLCODE747 SQLCODE798 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70182 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 PM70182 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70182 DSNTESQ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MACROS DSNTESQ LISTEND UK81728 COVER LETTER END UK81730 COVER LETTER START PROBLEM DESCRIPTION(S): PM66732 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * referential integrity rule ON DELETE SET * * NULL when there is an index on expression * * defined on the child table * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNKEDLE:5378 * * ERQUAL5378 may occur when executing SQL * * DELETE against a parent table and these * * conditions exist: * * * * - the child table is ON DELETE SET NULL * * - there is an index on expression * * defined on the child table and has * * at least one variable length field * * key column * * - the child table has been altered * * and the delete is processing a * * down-level versioned record * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 at DSNKEDLE:5378 may occur when executing SQL DELETE against a parent table, which causes nullification of foreign key in records in an ON DELETE SET NULL child table. The abend occurred because an internal flag for down-level versioning was incorrectly set. As a result, a key length field for index on expression processing went negative and caused the the aforementioned abend. DB2 code was changed to handle the internal flag for down-level versioning correctly when nullifying for ON DELETE SET NULL. Additional keywords: SQLDELETE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66732 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIIDIS PM66732 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66732 DSNIIDIS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIIDIS LISTEND UK81730 COVER LETTER END UK81732 COVER LETTER START PROBLEM DESCRIPTION(S): PM71018 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of REORG REBALANCE and * * DECIMAL=COMMA in DSNHDECP * **************************************************************** * PROBLEM DESCRIPTION: REORG REBALANCE does not place a comma * * in the external limit key value for a * * DECIMAL column when DSNHDECP shows * * DECIMAL=COMMA * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** REORG REBALANCE is not placing a comma in place of the period for a DECIMAL column when building the external limit key value for the limitkey column in SYSIBM.SYSTABLEPART and SYSIBM.SYSINDEXPART and DSNHDECP specifies DECIMAL=COMMA. The actual LIMITKEY INTERNAL value is in internal form (without 1 a decimal point) and is correct. Only the external value is incorrect. REORG REBALANCE code has been changed to use the comma in place of the period when building the external form of the limit key when DSNHDECP says DECIMAL=COMMA and the column type is DECIMAL. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71018 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 PM71018 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71018 DSNUDALT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUDALT LISTEND UK81732 COVER LETTER END UK81737 COVER LETTER START PROBLEM DESCRIPTION(S): PM71468 - **************************************************************** * USERS AFFECTED: User of the SET CURRENT MAINTAINED TABLE * * TYPES FOR OPTIMIZATION statement with * * DB2 for z/OS Version 10.1 * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -713 when specifying * * SESSION_USER in the SET CURRENT * * MAINTAINED TYPES statement * **************************************************************** * RECOMMENDATION: * **************************************************************** The following statement results in an error, and should be 1 successful: SET CURRENT MAINTAINED TABLE TYPES = SESSION_USER ; SQLCODE = -713, ERROR: THE REPLACEMENT VALUE FOR CURRENT MAINTAINED TYPES IS INVALID SQLSTATE = 42815 SQLSTATE RETURN CODE SQLERRP = DSNXRSPG SQL PROCEDURE DETECTING ERROR SQLERRD = -131 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION Additional keywords: SQLCODE713 SQLMQT DB2 code is changed so that the invalid error no longer occurs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71468 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNHSM2V PM71468 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71468 DSNHSM2V THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHSM2V LISTEND UK81737 COVER LETTER END UK81757 COVER LETTER START PROBLEM DESCRIPTION(S): PM69316 - **************************************************************** * USERS AFFECTED: All DB2 9, DB2 10 for z/OS users of OLAP * * specification with window order clause. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 at DSNXGRDS.DSNXOEM * * +01AC could occur when an SQL statement * * satisfies the following conditions: * * 1. There are more than one OLAP * * specifications with window order * * clause referenced, * * 2. In the window order clause, there * * is datetime arithmetic expression * * referenced. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000011 at DSNXGRDS.DSNXOEM+01AC could occur when an SQL statement satisfies the following conditions: 1. There are more than one OLAP specifications with window order clause referenced, 1 2. In the window order clause, there is datetime arithmetic expression referenced. The following example could recreate the problem: CREATE TABLE PM69316(C1 TIMESTAMP, C2 INTEGER); SELECT C2, ROW_NUMBER() OVER ( ORDER BY CASE WHEN C1 < CURRENT TIMESTAMP - 5 MINUTES THEN 100 ELSE 200 END ) AS CC1, RANK() OVER ( ORDER BY CASE WHEN C1 < CURRENT TIMESTAMP - 5 MINUTES THEN 100 ELSE 200 END ) AS CC2 FROM PM69316; DB2 abends since the datetime arithmetic expression in window order clause is not handled correctly. DB2 is updated to handle the datetime arithmetic expression correctly. Additional keywords: SQLDATE SQLTIME SQLOLAP SQLORDER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69316 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOSDA PM69316 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69316 DSNXOSDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSDA LISTEND UK81757 COVER LETTER END UK81759 COVER LETTER START PROBLEM DESCRIPTION(S): PM70343 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of compression * * on INSERT * **************************************************************** * PROBLEM DESCRIPTION: INSERT processing is not freeing all * * storage used during processing causing * 1 * the DBM1 address space to run low on, * * and then out of, below the bar storage. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** INSERT processing is not freeing all control blocks allocated during processing. This build-up of non-freed control blocks results in the DB2 DBM1 address space running out of below the bar storage. This can result in various abends but two of the more common ones are ABEND04E RC00E20013 from DSNSGMN and ABEND04E RC00E20003 from DSNSVBK. This problem could also occur for LOAD SHRLEVEL CHANGE utilties and for LOAD SHRLEVEL NONE with XML columns. Utility code has been changed to free the storage allocated during processing. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70343 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUZLCR PM70343 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70343 DSNUZLCR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUZLCR LISTEND UK81759 COVER LETTER END UK81763 COVER LETTER START PROBLEM DESCRIPTION(S): PM69637 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of REORG TABLESPACE SHRLEVEL CHANGE utility * **************************************************************** * PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE missed * * applying insert log records for a user * * table with table OBID = 1. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User ran a REORG TABLESPACE SHRLEVEL CHANGE against a table space containing a table with OBID = 1. Upon successful REORG completion, it was found that REORG did not apply any insert log records against the table with OBID = 1, resulting in a data loss. 1 The reported problem is caused by incorrect program logic in REORG on skipping insert log records with table OBID = 1. Code has been modified to prevent the aforementioned data loss by having REORG properly handle the insert log records of a table with OBID = 1. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69637 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGLGR PM69637 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69637 DSNUGLGR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGLGR LISTEND UK81763 COVER LETTER END UK81765 COVER LETTER START PROBLEM DESCRIPTION(S): PM69139 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users whose queries utilize * * RANGE predicates. * **************************************************************** * PROBLEM DESCRIPTION: The compound filter factor of two RANGE * * predicates against the same table * * column could be under-estimated, which * * may result in an inefficient access * * path. * **************************************************************** * RECOMMENDATION: * **************************************************************** The compound filter factor of two RANGE predicates against the same column could be under-estimated, which may result in an inefficient access path. For example: The compound filter factor of the following two RANGE predicates: C1 >= ? AND C1 <= ? should be the same as the equivalent BETWEEN predicate: C1 BETWEEN ? and ?. 1 However, the compound filter factor of two RANGE predicates is currently under-estimated and lower than the filter factor of the equivalent BETWEEN predicate, which may cause DB2 to choose an inefficient access path. Additional Keywords: SQLLT SQLGT FILTERFACTOR SQLACCESSPATH SQLPERFORMANCE 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: PM69139 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM69139: See PM69139 APAR/PTF text for additional information about why a REBIND is necessary. PM69139 corrects a problem of inaccurate compound filter factor of two range predicates on the same column 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. DB2BIND: ***Action for PM64315: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM64315 corrects a problem in which the filter factor for a compound predicate containing an OR predicate could be overestimated. The incorrect compound filter factor could result in an inefficient access path and resulting poor query performance. 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 PM61658: See PM61658 APAR/PTF text for additional information about why a REBIND is necessary. PM61658 corrects a problem of over-estimated correlated 1 subquery cardinality when global query optimization is enabled (OPTXQB=ON) and there are materialized views involved in the join between the parent query block and the correlated subquery. This 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. DB2BIND: ***Action for PM56435: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM56435 corrects a problem in which DB2 could compute an incorrect compound filter factor. This could lead to an inefficient access path and poor query performance. 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 PM44942: See PM44942 APAR/PTF text for additional information about why a REBIND is necessary. PM44942 corrects a problem of a poorly performing access path caused by incorrect filter factor estimation for a compound predicate when frequency or histogram statistics exist, or column cardinality is 1 or 2. 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 PM32384: See PM32384 APAR/PTF text for additional information about why a REBIND is necessary. PM32384 corrects a problem of inaccurate index filter factor estimate when multi-column cardinality exists in some cases 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 DSNXOCCF PM69139 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69139 DSNXOCCF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCCF LISTEND UK81765 COVER LETTER END UK81767 COVER LETTER START PROBLEM DESCRIPTION(S): PM67124 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users whose * * SQL uses an index on expression. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may occur when a user * * issues a query that satisfies the * * conditions below: * * 1. Query is accessed by an index on * * expression. * * 2. A key expression also has its source * * column as one of the index keys. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may give incorrect output when an index on expression is used on a query, and the index on expression has the source column of a key expression as one of the index keys. For example, Index on (RTRIM(C1), C1) SELECT C1, STRIP(C1) FROM T WHERE RTRIM(C1) LIKE '%ABC'; RTRIM(C1) is in the index on expression, and its source column C1 is one of the index keys. PROBLEM CONCLUSION: The problems mentioned above are fixed so that DB2 will not give incorrect output in that situation. ADDITIONAL KEYWORDS: SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLINDEXONEXP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67124 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM67124: See PM67124 APAR/PTF text for additional information about why a REBIND is necessary. PM67124 corrects a problem of incorrect output when an index on expression has the source column of a key-expression as one of the index keys. 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 DSNIIMSI PM67124 DSNXOGP PM67124 DSNXOPRS PM67124 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67124 DSNIIMSI DSNXOGP DSNXOPRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIIMSI DSNXOGP DSNXOPRS LISTEND UK81767 COVER LETTER END UK81769 COVER LETTER START PROBLEM DESCRIPTION(S): PM62583 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of APREUSE(ERROR) and * * REOPT(ALWAYS). * **************************************************************** * PROBLEM DESCRIPTION: DB2 may improperly ignore bind/rebind * * option REOPT(ALWAYS) if the option * * APREUSE(ERROR) is specified too. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a package is bound or rebound with option APREUSE(ERROR) and REOPT(ALWAYS), the statements in the package may use the access paths chosen at the prior bind time rather than determine the access paths at the execution time. The problem could also happen when a package is bound or rebound with option APREUSE(ERROR) and inherits the option REOPT(ALWAYS). Additional Keywords: 1 SQLACCESSPATH SQLPERFORMANCE APREUSE REOPT Code has been modified to honor the option REOPT(ALWAYS) in the cases described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62583 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM62583: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM62583 corrects a problem that DB2 may improperly ignore bind/rebind option REOPT(ALWAYS) if the option APREUSE(ERROR) is specified too. 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 DSNXOOP PM62583 DSNXOPCO PM62583 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62583 DSNXOOP DSNXOPCO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOOP DSNXOPCO LISTEND UK81769 COVER LETTER END UK81770 COVER LETTER START PROBLEM DESCRIPTION(S): PM60921 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who use * * IDAA (IBM DB2 Analytics Accelerator). * **************************************************************** * PROBLEM DESCRIPTION: Currently, the fullselect portion of * * INSERT statements cannot be offloaded * * to IDAA. This APAR adds the option and * * support to allow the fullselect portion * * of INSERT statements to execute on * * IDAA. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 Currently, the fullselect portion of INSERT statements that use a fullselect to specify the data to be inserted cannot be offloaded to IDAA. This APAR adds the option and support to allow the fullselect portion of INSERT statements to execute on IDAA. A new option, 2, is added to DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS. This parameter is used to specify additional types of SQL statements to be included in query offloading. The new option, 2, specifies that: * 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 query, except that DB2 will not offload the fullselect statement if the target table has a different encoding scheme than any table referenced in the fullselect statement. If option 2 is not specified on subsystem parameter QUERY_ACCEL_OPTIONS, then no part of INSERT statements using a fullselect to specify the source data will be offloaded. Additional Keywords: IDAAV2R1/K SQLINSWSELECT Code is added to include the option and support for offloading INSERT statements using a fullselect to specify the source data. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60921 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: ***Action for PM60921: This PTF adds a new option, 2, to 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 two 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. The new option, 2, specifies that: * 2 : For INSERT statements where a fullselect specifies the data to be inserted, the fullselect part is not 1 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 table referenced in the fullselect. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is mutually exclusive from all other settings. Options 1 and 2 can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=2 QUERY_ACCEL_OPTIONS=(1,2) 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 target library only. You need to redo any record format changes and reapply any tailoring you have done to your copy 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 optional After applying this PTF, if you want to specify that, for queries that include an INSERT from SELECT statement, the SELECT part is not blocked from executing on IDAA, you need to update your customized copy of DSNTIJUZ as follows: * Add or update the keyword parameter QUERY_ACCEL_OPTIONS= where is 2 or (1,2) 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 1 ---------------------------------------------------------------- ==> This action is required only if you added or updated the setting for QUERY_ACCEL_OPTIONS in the previous step. In that case, you need to add or update the entry for that parameter in all private copies of your CLIST output DSNTIDxx member. In each such copy, add or modify the following line: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value specified for QUERY_ACCEL_OPTIONS in step (2), above. 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 PM60921 DSNDSPRM PM60921 DSNHSMUT PM60921 DSNHSM1 PM60921 DSNLXRBF PM60921 DSNLXROP PM60921 DSNLXRSQ PM60921 DSNLXRUW PM60921 DSNLXSET PM60921 DSNLZR00 PM60921 DSNWZIFA PM60921 DSNXEDP PM60921 DSNXEPM PM60921 DSNXERT PM60921 DSNXGRTM PM60921 DSNXGRTS PM60921 DSNXODML PM60921 DSNXOD1 PM60921 DSNXOD3 PM60921 DSNXOD5 PM60921 DSNXOEX1 PM60921 DSNXOFF PM60921 DSNXOGP PM60921 DSNXOIN PM60921 DSNXOMD PM60921 DSNXONZA PM60921 DSNXONZO PM60921 DSNXONZQ PM60921 DSNXOOP PM60921 DSNXOOS1 PM60921 DSNXOQ2 PM60921 DSNXOSSC PM60921 DSNXOTF PM60921 DSNXRFF PM60921 DSNXRFN PM60921 DSNXRIWS PM60921 1 DSNXROHB PM60921 DSN6SPRM PM60921 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60921 DSNDQWPZ DSNDSPRM DSNHSMUT DSNHSM1 DSNLXRBF DSNLXROP DSNLXRSQ DSNLXRUW DSNLXSET DSNLZR00 DSNWZIFA DSNXEDP DSNXEPM DSNXERT DSNXGRTM DSNXGRTS DSNXODML DSNXOD1 DSNXOD3 DSNXOD5 DSNXOEX1 DSNXOFF DSNXOGP DSNXOIN DSNXOMD DSNXONZA DSNXONZO DSNXONZQ DSNXOOP DSNXOOS1 DSNXOQ2 DSNXOSSC DSNXOTF DSNXRFF DSNXRFN DSNXRIWS DSNXROHB DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHSMUT DSNHSM1 DSNLXRBF DSNLXROP DSNLXRSQ DSNLXRUW DSNLXSET DSNLZR00 DSNWZIFA DSNXEDP DSNXEPM DSNXERT DSNXGRTM DSNXGRTS DSNXODML DSNXOD1 DSNXOD3 DSNXOD5 DSNXOEX1 DSNXOFF DSNXOGP DSNXOIN DSNXOMD DSNXONZA DSNXONZO DSNXONZQ DSNXOOP DSNXOOS1 DSNXOQ2 DSNXOSSC DSNXOTF DSNXRFF DSNXRFN DSNXRIWS DSNXROHB MACROS DSNDQWPZ DSNDSPRM DSN6SPRM 1 LISTEND UK81770 COVER LETTER END UK81819 COVER LETTER START PROBLEM DESCRIPTION(S): PM67270 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of input * * host variables whose type is DATE, TIME or * * TIMESTAMP in SQLDA. * **************************************************************** * PROBLEM DESCRIPTION: DB2 incorrectly issues an SQLCODE -301 * * (SQLCODE301) when an SQLTYPE of DATE, * * TIME, or TIMESTAMP is used in the input * * SQLDA and is bound to a VARCHAR, CHAR, * * VARGRAPHIC, or GRAPHIC target datatype. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 incorrectly issues an SQLCODE -301 when an SQLTYPE of DATE, TIME, or TIMESTAMP is used in the input SQLDA and is bound to a VARCHAR, CHAR, VARGRAPHIC, or GRAPHIC target datatype. Instead, DB2 should allow this kind of conversion for data compatibility. The following example illustrates the problem. 1. Create a simple table with a VARCHAR column. CREATE TABLE T1 (C1 VARCHAR(10)); 2. Write an insert application in C and set the SQLTYPE for the host variable as DATE in the SQLDA. // define a CHAR host variable for DATE input char hdate??(10??); memcpy(hdate,"2012-06-18",sizeof(hdate)); struct sqlda *sqlda1; struct sqlvar *varptr1; sqlda1 = (struct sqlda *) malloc (1 * 44 + 16); strcpy(sqlda1->sqldaid,"SQLDA"); sqlda1->sqldabc = 60; sqlda1->sqln = 1; sqlda1->sqld = 1; varptr1 = sqlda1->sqlvar; // application can set SQLTYPE to DATE (384) even // though the real host variable data type is CHAR(10) varptr1->sqltype = 384; varptr1->sqllen = 10; varptr1->sqldata = hdate; varptr1->sqlind = NULL; EXEC SQL 1 SET :SQLSTMT='INSERT INTO T1 VALUES(?)'; EXEC SQL PREPARE my_insert FROM :SQLSTMT; EXEC SQL EXECUTE my_insert USING DESCRIPTOR :*sqlda1; 3. Execute the application. The application inserts the DATE value into a VARCHAR column by setting the SQLTYPE (from CHAR) to DATE. DB2 does not handle this conversion properly and as a result, issues an SQLCODE -301 for an incompatible datatype. The conversion should be allowed because a conversion from DATE to VARCHAR is considered to be 'data compatible'. Please note, An SQLCODE -301 might also be issued when a TIME or TIMESTAMP SQLTYPE is used to insert into a VARCHAR, CHAR, GRAPHIC, or VARGRAPHIC column in the above application. The code in DB2 has been modified to not issue an SQLCODE -301 when the SQLTYPE is set as DATE, TIME, or TIMESTAMP in the input SQLDA when the target datatype is CHAR, GRAPHIC, VARCHAR, or VARGRAPHIC. In other words, DB2 will no longer perform DATE, TIME, or TIMESTAMP validation if the SQLTYPE is DATE, TIME, or TIMESTAMP in the SQLDA when the target datatype is not a DATE, TIME, or TIMESTAMP column. Additional Keywords: SQLDATE SQLTIME SQLTIMESTAMP SQLCODE301 SQLGRAPHIC COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67270 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRIB9 PM67270 DSNXRID9 PM67270 DSNXRIHB PM67270 DSNXRIHD PM67270 DSNXRIHR PM67270 DSNXRIHS PM67270 DSNXRIS9 PM67270 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67270 DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRIB9 DSNXRID9 1 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9 LISTEND UK81819 COVER LETTER END UK81822 COVER LETTER START PROBLEM DESCRIPTION(S): PM69710 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of GET * * DIAGNOSTICS for MESSAGE_TEXT. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 RC10 can occur at location * * DSNSVBK OFFSET 100A (or OFFSET100A) * * when DB2 retrieves a condition for * * MESSAGE_TEXT when using GET * * DIAGNOSTICS. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND0C4 RC10 can occur at location DSNSVBK OFFSET 100A when using GET DIAGNOSTICS to retrieve a condition for MESSAGE_TEXT. The problem occurs if the MESSAGE_TEXT contains more than 32672 characters. As a result, DB2 does not handle the GET DIAGNOSTICS statement correctly and can overlay the storage for MESSAGE_TEXT which leads to the ABEND0C4. Please note. A different error can occur depending on the nature of the MESSAGE_TEXT overlay. The code in DB2 has been modified to truncate the MESSAGE_TEXT in a GET DIAGNOSTICS statement when 32672 characters have been written out. Additional Keywords: SQLGETDIAG SQLCODE445 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69710 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 PM69710 DSNXRGD9 PM69710 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69710 DSNXRGD DSNXRGD9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNXRGD DSNXRGD9 LISTEND UK81822 COVER LETTER END UK81826 COVER LETTER START PROBLEM DESCRIPTION(S): PM71687 - **************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: Abend0C4 in DSNIWCKP+036E when writing * * Unit of Recovery (UR) checkpoint log * * record. * **************************************************************** * RECOMMENDATION: * **************************************************************** During system checkpoint time when Data Manager is about to begin writing of the UR summary checkpoint log record and at the same time, end of restart auto-GRECP is active and performing the end of auto-GRECP processing, it is possible that end of the auto-GRECP gets control before system checkpoint. In this case both of them are serialized with a DBRT (Data Base Restart Table) latch. So checkpoint process will wait until end of auto-GRECP completes. However, checkpoint processing logic should check again for the existence of DBRT table. It could have been freed by auto-GRECP process. This APAR only addresses the serialization window between auto-GRECP and checkpoint. This window is fairly small so the likelihood of hitting this problem should not be very frequent. However, when this problem occurs, it will bring down DB2. When DB2 is abnormally terminated, user should be able to restart failed member successfully. The DB2 Data Manager's checkpoint logic is modified to avoid program exception error while auto-GRECP is active. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71687 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIWCKP PM71687 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71687 DSNIWCKP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIWCKP LISTEND UK81826 COVER LETTER END 1 UK81851 COVER LETTER START PROBLEM DESCRIPTION(S): PM68139 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries * * containing multiple local predicates on the * * same column. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may produce inaccurate filter * * factor estimation of local predicates * * if multiple local predicates reference * * the same column and index probing is * * used in filter factor estimation of * * these predicates. * **************************************************************** * RECOMMENDATION: * **************************************************************** Index probing can help the DB2 optimizer better estimate the filter factor of local predicates. But a problem was found that DB2 might produce inaccurate filter factor estimation of local predicates if multiple local predicates reference the same column and index probing is used in filter factor estimation of these predicates. For example, SELECT * FROM T1 WHERE T1.C1 BETWEEN 101 AND 200 OR T1.C1 BETWEEN 201 AND 300 OR T1.C1 BETWEEN 301 AND 400; If an index IX1 is defined on T1.C1 and and index probing is used to improve filter factor estimation of "T1.C1 BETWEEN 101 AND 200", the subsequent local predicates on the column C1 "T1.C1 BETWEEN 201 AND 300" and "T1.C1 BETWEEN 301 AND 400" may be estimated inaccurately. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE INDEXPROBING FILTERFACTOR NPGTHRSH VOLATILE Code has been corrected to produce accurate filter factor estimation for the local predicates in a case described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68139 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66948: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. 1 PM66948 corrects a problem of inaccurate filter factor estimation for a predicate if the predicate references a nullable column on which histogram statistics exist. 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 PM64871: See PM64871 APAR/PTF text for additional information about why a REBIND is necessary. PM64871 corrects a problem of inaccurate filter factor estimation of an IN-subquery 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. DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM49539 corrects an ABEND 0CF when incorrect internal values may be used to recalculate the filter factor of the related RANGE or BETWEEN predicates at execution time. The incorrect internal values may be saved by DB2 at BIND/PREPARE time if the package is bound with REOPT(AUTO), and one or more queries in the package contain RANGE or BETWEEN predicate(s). 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 PM37547: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM37547 corrects a problem in which DB2 may calculate an incorrect filter factor for an after join predicate on a column defined as NOT NULL. 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 PM36392: See PM36392 APAR/PTF text for additional information about 1 why a REBIND is necessary. PM36392 corrects a problem that the filter factor of an equal predicate may be inaccurate if histogram statistics exist on a column of that 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 PM26521: See PM26521 APAR/PTF text for additional information about why a REBIND is necessary. PM26521 corrects a problem where the filter factor of an IS NULL predicate is underestimated as 1E-9 if there is a NULL value in the column, histogram statistics exist, but frequency statistics do not exist. 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 PM23073 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM23073 fixes a filter factor estimation problem for a LIKE predicate with MIXED data. The filter factor estimation problem could lead to a poor 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. ACTION: ***Action for PM65872: See PM65872 APAR/PTF text for additional information about why a REBIND is necessary. PM65872 corrects a problem of infinite loop that can occur when there are a very large number of predicates, and items in the SELECT list, and at least one predicate is an equal-, ANY-, or IN-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 affected by this change. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODFB PM68139 DSNXODFE PM68139 1 DSNXODFR PM68139 DSNXODFT PM68139 DSNXOINQ PM68139 DSNXOPRS PM68139 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68139 DSNXODFB DSNXODFE DSNXODFR DSNXODFT DSNXOINQ DSNXOPRS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODFB DSNXODFE DSNXODFR DSNXODFT DSNXOINQ DSNXOPRS LISTEND UK81851 COVER LETTER END UK81878 COVER LETTER START PROBLEM DESCRIPTION(S): PM66235 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of DB2 packages * * containing static SQL and COMMIT / ROLLBACK, * * bound RELEASE(DEALLOCATE) and run with * * either DB2 trace IFCID 400 or trace monitor * * class 29 active * **************************************************************** * PROBLEM DESCRIPTION: DB2 storage shortage in ACOMDSC2GP / * * STMT CACHE BLOCKS 2G pool where the * * pool contains an excessive number of * * blocks with eye catcher 'SHTE', * * resulting in DB2 out-of-storage * * ABEND04E RC00E2000C * * at DSNGEPLC . DSNSVSVB +0AC2 * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 10 when either DB2 trace IFCID400 or trace monitor class 29 is active, DB2 collects statement level statistics for each static SQL executed in a DB2 package. These statement level statistics are stored in DB2 internal block SHTE in the DB2 STMT CACHE BLOCKS 2G pool during the SQL stmt execution (note that when IFCID400 is active, both static and cached dynamic SQL share usage of this pool). This pool is shared across DB2 threads. There is one SHTE block per static SQL statement, and the different running copies of that static SQL statement used by different DB2 threads share that single SHTE block. The lifetime of this SHTE block used for static SQL statement level statistics is directly tied to the lifetime of both the running copies of the static SQL statement and the master copy of its DB2 package in the 1 EDM POOL. When all of the running copies of the static SQL statement are freed and the master copy of the DB2 package in the EDM POOL is also LRU'd out when more EDM POOL space is needed for other packages, the internal SHTE block for the static SQL statement is also freed. If there is at least one copy of the static SQL statement still active for a DB2 package, the SHTE block for that static SQL statement is not freed. . In the reported DB2 storage shortage case, a significant number of static SQL executions were from DB2 packages bound RELEASE(DEALLOCATE) and run while trace IFCID400 was active. A DB2 thread's copy of a package bound as RELEASE(DEALLOCATE) and its static SQL statements will remain allocated until that DB2 thread is terminated. This means that the internal SHTE block will also remain allocated until all of the associated running copies of the RELEASE(DEALLOCATE) packages are freed at DB2 thread termination and the packages' master copies are LRU'd out of the EDM POOL. However, in this case, even though the DB2 threads were terminated, and the packages bound REL(DEALLOCATE) and their copies of the static SQL statements were freed, the internal SHTE blocks for these static SQL statements were not freed. . DB2 Development determined that when the application program was bound REL(DEALLOCATE) and issued multiple COMMITs/ ROLLBACKs (or single COMMIT/ROLLBACK followed by a DB2 implicit ending COMMIT), at DB2 thread termination/deallocation DB2 did not consider the static SQL that were run and COMMITed in the previous units-of-work (UOW). So at deallocation time DB2 did not 'de-register' the static SQL statement's usage of the internal SHTE block used for that statement. Therefore, many SHTE blocks accumulated in the DB2 STMT CACHE BLOCKS 2G pool as if they were still in use by active static SQL statements, resulting in the DB2 storage shortage and the reported DB2 abend. SOLUTION: DB2 thread termination/deallocation code has been changed to consider static SQL that were run and COMMITed in any previous UOW when either DB2 trace IFCID400 or trace monitor class 29 was active, and to 'de-register' those static SQL statements' usage of the internal SHTE block for statement level statistics. RELATED KEYWORDS: 04E AB04E IFCID400 0400 OFFSET0AC2 SQLSTORAGE GROWTH LEAK DB2STGLK/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66235 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEUFP PM66235 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66235 DSNXEUFP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEUFP LISTEND UK81878 COVER LETTER END UK81899 COVER LETTER START PROBLEM DESCRIPTION(S): PM69176 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: When performing a SELECT or an * * INSERT via SELECT on an XML document * * from an XML column in the XMLTABLE * * function, DB2 may issue SQLCODE -904 * * if the use of XML virtual storage * * reaches the limit set by the * * subsystem parameters XMLVALA and * * XMLVALS. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may issue SQLCODE -904 (RC00D50001 or RC00D50002, TYPE OF RESOURCE 0000090A), if the use of XML virtual storage reaches the limit set by the subsystem parameters XMLVALA and XMLVALS. This APAR optimizes the reuse of XML virtual storage for each row of the XMLTABLE function with an output column of XML data type, and it alleviates the accumulated use of XML virtual storage. The following examples illustrate the reuse of XML virtual storage for the XMLTABLE function in SELECT and INSERT via SELECT statement. SELECT X.C1 FROM T1, XMLTABLE('/a/b' PASSING T1.DOC COLUMNS C1 XML PATH 'c') X; INSERT INTO T2 (ID, DOC) SELECT T1.ID, XMLDOCUMENT(X.DOC) FROM T1, XMLTABLE('/a/b' PASSING T1.DOC COLUMNS DOC XML PATH 'c') AS X WHERE T1.ID > 0; DB2 code is modified to reuse the XML virtual storage for the XMLTABLE function with an output column of XML data type, so as to reduce the use of XML virtual storage. Additional keywords: SQLXML XMLINSERT SQLCODE904 SQLXMLTABLE COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM69176 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM69176 APAR/PTF text for additional information about why a REBIND is necessary. PM69176 improves the XML virtual storage use for queries or INSERT via SELECT statements that use the XMLTABLE function with an output column of XML data type. To make the storage enhancement effective for a static application, it must be rebound after application of this PTF. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEMG1 PM69176 DSNXGRTM PM69176 DSNXOGA1 PM69176 DSNXOOS2 PM69176 DSNXOPB PM69176 DSNXRBND PM69176 DSNXRIWS PM69176 DSNXRXML PM69176 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69176 DSNXEMG1 DSNXGRTM DSNXOGA1 DSNXOOS2 DSNXOPB DSNXRBND DSNXRIWS DSNXRXML THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEMG1 DSNXGRTM DSNXOGA1 DSNXOOS2 DSNXOPB DSNXRBND DSNXRIWS DSNXRXML LISTEND UK81899 COVER LETTER END UK81900 COVER LETTER START PROBLEM DESCRIPTION(S): PM69968 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: An application on a requester system * * (Site 1) calls a remote stored * * procedure on a DB2 10 for z/OS server * * (Site 2), where the stored procedure * 1 * returns a static cursor retrieving * * data from a DB2 i server (Site 3). * * DB2 10 (Site 2) abends as follows: * * 04E-00E2000F DSNLZS00.DSNSVSFB+0858 * * This causes DB2 to terminate as a * * result. The problem occurs after APAR * * PM51918 (PTF UK76107) is applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application on a remote requester system (Site 1) calls a stored procedure on a DB2 10 for z/OS server (Site 2). The stored procedure OPENs a static cursor WITH RETURN on a remote DB2 i server (Site 3). As part of the DRDA OPEN request (OPNQRY), the DB2 10 for z/OS (Site 2) server specifies the return of column information for the result set (SQLDARD) but the DB2 i (Site 3) server does not return this requested information. Because of this missing information, the DB2 10 for z/OS (Site 2) server incorrectly computes the amount of storage needed for its processing. The allocated storage is too small and a storage overlay occurs as a result. This overlay is subsequently detected, in the form of an abend 04E-00E2000F during DB2 must-complete thread termination processing, causing the DB2 10 for z/OS subsystem to terminate abnormally. The problem occurs after APAR PM51918 (PTF UK76107) is applied. DB2 10 for z/OS, when processing a stored procedure invoked by an application on a remote requester, has been changed to compute the correct amount of storage needed for the processing of static result sets returning data from remote DB2 i servers. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69968 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXGVR PM69968 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69968 DSNLXGVR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXGVR LISTEND UK81900 COVER LETTER END UK81931 COVER LETTER START PROBLEM DESCRIPTION(S): PM67895 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS RUNSTATS utility users * * collecting table space statistics using * * TABLESAMPLE SYSTEM keywords. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E40214 DSNUSUPT * * OFFSET14CA during RUNSTATS TABLESPACE * * TABLESAMPLE SYSTEM. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A RUNSTATS TABLESPACE TABLESAMPLE SYSTEM resulted in an ABEND04E in DSNUSUPT + x'14CA' during the update of . SYSIBM.SYSTABSTATS catalog table. The abend occurred when a negative value in Real Time statistics (RTS) npages was encountered. Code was modified to check for negative values in the variable for NPAGES. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67895 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRTSX PM67895 DSNURFIT PM67895 DSNUSEF2 PM67895 DSNUSITS PM67895 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67895 DSNIRTSX DSNURFIT DSNUSEF2 DSNUSITS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRTSX DSNURFIT DSNUSEF2 DSNUSITS LISTEND UK81931 COVER LETTER END UK81944 COVER LETTER START PROBLEM DESCRIPTION(S): PM70285 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKINSL ERQUAL * * 5033 occurred during skip migration * * from DB2 for z/OS Version 8 to DB2 10 * * for z/OS. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** During system migration from DB2 for z/OS Version 8 to DB2 10 for z/OS, changes to SYSIBM.SYSCOLUMNS started with exclusive access. Later, within the same transaction, exclusive access was lost. As the transaction aborted, indexes DSNDCX01 and DSNDCX02 were left in an inconsistent state causing duplicate key errors. DB2 erroneously down graded the drain lock, which caused exclusive access to be lost. The following abends may also be seen: ABEND04E RS00C90101 DSNKDLE ERQUAL 500A ABEND04E RS00C90101 DSNKUNR2 ERQUAL 5016 Additional keywords: DB2MIGV9/K DB2MIGV10/K DB2 has been modified not to down grade the drain lock when the current drain lock is held at a higher state. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70285 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICLDR PM70285 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70285 DSNICLDR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICLDR LISTEND UK81944 COVER LETTER END UK81946 COVER LETTER START PROBLEM DESCRIPTION(S): PM69992 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * DECFLOAT datatype. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2000F at * * DSNXEFB.DSNSVSFB offset 0858 or * * memory overlay could occur when an SQL * * statement references a constant which * * is resolved as DECFLOAT datatype. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E2000F at DSNXEFB.DSNSVSFB offset 0858 or 1 memory overlay could occur when an SQL statement references a constant which is resolved as DECFLOAT datatype. The following example could shows a memory overlay. CREATE TABLE PM69992(C1 DECFLOAT, C2 INTEGER); SELECT C1 + 1, C2 FROM PM69992; DB2 is not handled the DECFLOAT constant buffer correctly, it causes memory overlay. DB2 is updated to handle the DECFLOAT constant correctly. Additional Keywords: SQLDECFLOAT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69992 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM69992: See PM69992 APAR/PTF text for additional information about why a REBIND is necessary. PM69992 corrects a problem of ABEND04E RC00E2000F at DSNXEFB.DSNSVSFB offset 0858 or memory overlay when an SQL statement references a constant which is resolved as DECFLOAT datatype. 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 DSNXOLTX PM69992 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69992 DSNXOLTX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLTX LISTEND UK81946 COVER LETTER END UK81960 COVER LETTER START PROBLEM DESCRIPTION(S): PM69511 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: An overlay may occur starting at * * offset 0x33C into a 31-bit page after * * a soft cancel of a SUSPENDed agent. * 1 * This may result in numerous abends * * and possible DB2 termination. An * * example of such an abend is an * * ABEND0C4 in CSECT DSNB1REL. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an agent is using the SUSPEND/RESUME protocol, a 31-bit parameter is required upon resume. The 31-bit area is incorrectly obtained from the suspended agent's stack. This will result in an overlay if a cancelling agent is attempting to wake up an agent suspended in another address space. Most often the suspended agent will be in DIST and the cancelling agent will either be in MSTR or DBM1. The parameter list is now obtained from stack local to the cancelling agent rather than the suspended agent. This will prevent an overlay during the resume of the suspended agent. Additional Keywords: SMCOVERLAY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69511 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNVSRX PM69511 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69511 DSNVSRX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNVSRX LISTEND UK81960 COVER LETTER END UK82006 COVER LETTER START PROBLEM DESCRIPTION(S): PM70173 - **************************************************************** * USERS AFFECTED: All DB2 users of queries that contain the * * UNION or UNION ALL operator with dynamic * * statement cache is enabled. * **************************************************************** * PROBLEM DESCRIPTION: When a cursor, containing a query with * * a UNION or UNION ALL operator, is * * opened for the first and second time, * * DB2 returns an SQLCODE -904 * * (SQLCODE904) as expected for error path * * testing. However, when the same cursor * * is opened a third time, DB2 does not * * return an error. An SQLCODE -904 is * 1 * expected. Dynamic statement caching is * * enabled. * * * * This could also happen for other SET * * operations. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a cursor, containing a query with a UNION or UNION ALL operator, is opened for the first and second time, DB2 returns an SQLCODE -904 (SQLCODE904) as expected for error path testing. However, when the same cursor is opened a third time, DB2 does not return an error SQLCODE -904 to the application as expected when dynamic statement caching is enabled. The following scenario summarizes the error situation. 1, A cursor C1 is declared with a UNION or UNION ALL operator. 2, Stop the tablespace for the table referenced in C1. 3, OPEN cursor C1 the first time, DB2 will issue a -904. 4, OPEN cursor C1 the second time, DB2 will issue a -904. 5, OPEN cursor C1 a third time, DB2 will return with no SQLCODE. DB2 does not handle the error path properly for a UNION or UNION ALL operator when dynamic statement caching is enabled and the same statement is invoked multiple times. The code in DB2 has been modified to process the error path properly for a UNION or UNION ALL operator when dynamic statement caching is enabled. This includes issuing an SQLCODE as needed. Additional keywords: SQLUNION SQLUNIONALL SQLDYNSTMTCACHE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70173 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: This PTF corrects a query clean up problem that occurs when the query contains a UNION or UNION ALL operator and dynamic statement caching is enabled. In order to expose the problem, same statement needs to be invoked multiple times. To make this fix effective for static applications, you need to rebind the affected applications after you apply this PTF. DB2BIND: ***Action for PM34291: See PM34291 APAR/PTF text for additional information about why a REBIND is necessary. PM34291 corrects a problem that can result in an SQLCODE -327 on behalf of MERGE processing because of an invalid sort input. This error may follow numerous SQLCODE -254 errors. 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 DSNXGOSQ PM70173 DSNXGRSR PM70173 DSNXGSOR PM70173 DSNXGTRE PM70173 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70173 DSNXGOSQ DSNXGRSR DSNXGSOR DSNXGTRE THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGOSQ DSNXGRSR DSNXGSOR DSNXGTRE LISTEND UK82006 COVER LETTER END UK82010 COVER LETTER START PROBLEM DESCRIPTION(S): PM69129 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of UNLOAD utility unloading data to a * * different CCSID and specifying TRUNCATE for * * one of the columns * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT or MSGDSNU1237I issued during * * an UNLOAD utility unloading data to a * * different CCSID and specifying TRUNCATE * * for one of the columns * **************************************************************** * RECOMMENDATION: * **************************************************************** INCORROUT or DSNU1237I during an UNLOAD utility of a UNICODE table converting to EBCDIC with the TRUNCATE option on at least one of the columns. This problem can occur during MIXED CCSID or DBCS CCSID conversion. The problem happened because UNLOAD utility incorrectly truncated the source data before the conversion and a wrong encoding scheme was referenced to truncate the converted data. UNLOAD utility code has been modified to apply the TRUNCATE option after CCSID conversion and use the right encoding scheme to truncate the converted data. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69129 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 DSNUULIA PM69129 DSNUULJA PM69129 DSNUULVA PM69129 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69129 DSNUULIA DSNUULJA DSNUULVA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULIA DSNUULJA DSNUULVA LISTEND UK82010 COVER LETTER END UK82042 COVER LETTER START PROBLEM DESCRIPTION(S): PM69237 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries * * containing predicates on timestamp columns * **************************************************************** * PROBLEM DESCRIPTION: For a query containing a predicate on * * a timestamp column, DB2 may choose * * an inefficient access path if one of * * following conditions also exists. * * * * 1. The timestamp column is eligible * * for index matching on multiple * * predicates. * * * * 2. The timestamp column is listed * * in the ORDER BY clause AND there * * is a 'COL=value' such that the * * ORDER BY sort could be avoided. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a query contains a predicate on a timestamp column, DB2 may choose an inefficient access path for one of two reasons. 1. Multiple predicates are eligible for index matching on the timestamp column. The most efficient choice is a predicate of the form 'COL=value'. DB2 may neglect to choose this predicate as matching and instead match on a less efficient predicate such as a join predicate. For example... 1 SELECT COUNT(*) FROM T1 ,T2 WHERE T1.C1 = '9999-12-31-00.00.00.000000' AND T1.C1 = T2.C1 If T1.C1 and T2.C1 are timestamp columns and there exists an index on either table on column C1, DB2 may choose to perform the index matching with predicate "T1.C1 = T2.C1" instead of the predicate "T1.C1 = '9999-12-31-00.00.00.000000'. This may lead to poor query performance. 2. The timestamp column is listed in the ORDER BY clause and there is a predicate of the form 'COL=value' in the query. In this case, DB2 should recognize that the timestamp column doesn't have any impact on the order of the results. If there is no other reason to sort, DB2 will incorrectly add a sort for the ORDER BY. For example... SELECT COUNT(*) FROM T1 WHERE C1 = :HV ORDER BY C1 If C1 is a timestamp column, DB2 will incorrectly add a sort for the ORDER BY. Additional keywords: SQLPERFORMANCE SQLACCESSPATH SQLORDERBY SQLTIMESTAMP DB2 has been fixed to properly handle these two cases when a timestamp column is involved. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69237 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM69237: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM69237 corrects a problem in which an inefficient access path may be selected for a query containing a predicate on a 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: 1 ***Action for PM60422: See PM60422 APAR/PTF text for additional information about why a REBIND is necessary. PM60422 corrects a problem of abend may occur for a query selected by mutiple rowset cursor and for update cursor, and also contains IN subquery predicate on the target 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. DB2BIND: ***Action for PM58612: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM58612 corrects the incorrect setting of an index screening predicate which may cause an ABEND when the query uses Hybrid 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 DSNXOGBM PM69237 DSNXOQ2 PM69237 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69237 DSNXOGBM DSNXOQ2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGBM DSNXOQ2 LISTEND UK82042 COVER LETTER END UK82045 COVER LETTER START PROBLEM DESCRIPTION(S): PM63980 - **************************************************************** * USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) * * users in data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: Long running IRLM deadlock cycles, * * delays observed when there are large * * number of resource lock waiters in a * * data sharing group. MSGDXR167E for * 1 * MAIN_SRB shows up on console. Timeouts * * may take longer than expected. DB2 * * members may appear slow or non- * * responsive. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Due to a large number of waiters on multiple IRLM members in a data sharing group, IRLM deadlock detection and Timeout processing may take more time to process all the waiters. Deadlock detection process may take very long if the wait-for relationship of waiters in the group becomes very complex. Longer running detection cycles delay timeout processing of the waiters in the group. As a result it takes longer to timeout waiters. Running deadlock detection for long time under the IRLM mainlatch causes slowdown in as a whole in IRLM. IRLM may issue DXR167E for MAIN_SRB messages. Dumps taken at the very end of the delay cycle are not very helpful for diagnostics to analyze which part of the deadlock cycle contributed to the major part of the overall delay. Additional diagnostic traces and dump is needed to debug problems in this area. This APAR adds additional diagnostic traces in IRLM deadlock processing. IRLM will record start-time and end-time for a deadlock cycle. It will monitor the elapsed time since the beginning of the deadlock cycle. For DB2, if it takes more than IRLMRWT timeout interval to run the detection process, or it has been over 30 seconds since the beginning of a deadlock cycle, IRLM will skip/abort running the deadlock detection and will just do the timeout processing in that cycle. This may continue until the number of waiters in the group drops to a smaller number that can be processed timely. After that IRLM will resume normal deadlock detection process again. This is done to relieve the group from delays and get the waiters timeout properly. IRLM has also added trap to bring a member down with ABENDu2025 in DXRRL750 if it detects that some mainlatch requests has been running in IRLM over 5 minutes. Taking a member off-line should resolve hung situation in a group because of that single member. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM63980 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL240 PM63980 DXRRL241 PM63980 DXRRL750 PM63980 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63980 DXRRL240 DXRRL241 DXRRL750 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DXRRL240 DXRRL241 DXRRL750 LISTEND UK82045 COVER LETTER END UK82115 COVER LETTER START PROBLEM DESCRIPTION(S): PM63078 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: During abort a DB2 thread may hang * * waiting for DSM DSST service task. * **************************************************************** * RECOMMENDATION: * **************************************************************** Currently with only one DSM DSST service task, DB2 thread may hang waiting for the service task. Increase the number of DSM DSST service tasks to 20. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM63078 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM64195: See PM64195 APAR/PTF text for additional information about why a REBIND is necessary. PM64195 corrects a problem of over estimated value for column CARDF in EXPLAIN table DSN_COLDIST_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 DSNGDAIP PM63078 DSNIERST PM63078 DSNKCEST PM63078 DSNPHLRH PM63078 DSNTSTOP PM63078 DSNTSTRT PM63078 DSNUBCKD PM63078 DSNUCARS PM63078 DSNUCASA PM63078 DSNUGSPC PM63078 DSNUKDRN PM63078 DSNUMDEL PM63078 DSNURFIJ PM63078 DSNURRNM PM63078 1 DSNURSWD PM63078 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM63078 DSNGDAIP DSNIERST DSNKCEST DSNPHLRH DSNTSTOP DSNTSTRT DSNUBCKD DSNUCARS DSNUCASA DSNUGSPC DSNUKDRN DSNUMDEL DSNURFIJ DSNURRNM DSNURSWD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDAIP DSNIERST DSNKCEST DSNPHLRH DSNTSTOP DSNTSTRT DSNUBCKD DSNUCARS DSNUCASA DSNUGSPC DSNUKDRN DSNUMDEL DSNURFIJ DSNURRNM DSNURSWD LISTEND UK82115 COVER LETTER END UK82131 COVER LETTER START PROBLEM DESCRIPTION(S): PM69475 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of time arithmetic * * using labeled duration SECONDS. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned * * for datetime arithmetic when the value * * for the SECONDS time duration is * * negative. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result can be returned from datetime arithmetic that uses the labeled time duration SECONDS. The incorrect result occurs because DB2 does not set an internal variable correctly when the 'seconds' operand (or duration value) is negative. The following example illustrates the problem. SELECT TIME('08:09:10') + (- 1 SECONDS) AS PLUS_MINUS FROM SYSIBM.SYSDUMMY1; 1 The result of this query is as follows. +------------+ | PLUS_MINUS | +------------+ 1_| 08.09.11 | +------------+ The expected time result value is 08.09.09. DB2 has been modified to set the internal variable correctly. Additional Keywords: SQLTIME DB2INCORR/K SQLINCORROUT SQLINCORR INCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69475 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDTF PM69475 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69475 DSNXRDTF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDTF LISTEND UK82131 COVER LETTER END UK82163 COVER LETTER START PROBLEM DESCRIPTION(S): PM66487 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users (CM and above) of * * static SQL INSERT statements, when the SQL * * INSERT uses default values of USER or * * CURRENT SQLID special registers (impacts all * * encoding schemes - ASCII, UNICODE or EBCDIC) * **************************************************************** * PROBLEM DESCRIPTION: Problem 1: * * ---------- * * After applying PM63849 (UK79943), * * ABEND04E DSNISRTI ERQUAL5363 or * * ABEND04E DSNIRNXT ERQUAL53CD or other * * symptoms may occur, due to a one-byte * * overlay * * * * Problem 2: * * ---------- * * After applying PM63849 (UK79943), * * ABEND0C1 RC00000001 IN DSNISRTI * 1 * * * Problem 3: * * ---------- * * Unrelated to PM63849 (UK79943) or * * any of the problems described above, * * value overlay or truncation is possible * * if SQL INSERT fills columns with * * default value USER or CURRENT SQLID and * * the table is in EBCDIC scheme. Various * * symptoms may occur, such as ABEND04E * * DSNISRTI ERQUAL5363, ABEND04E DSNIRNXT * * ERQUAL53CD and/or incorrect output * **************************************************************** * RECOMMENDATION: * **************************************************************** ---------- Problem 1: ---------- With APAR PM63849 (UK79943) applied, when SQL INSERT is filling a column with the default value of USER / CURRENT SQLID special register, a one-byte overlay can occur. The overlay can happen only if the column being filled is the last fixed-length column of a variable-length table. The overlay value is either '40'x or '20'x, depending on the encoding scheme that the table is defined with. The root cause of this overlay is that the code was by mistake performing a move of length N+1, when it should have been N. If the table is in Reordered Row Format (RRF), the one-byte overlay will be on the first byte of the offset field of the first variable-length column. The SQL INSERT itself will likely succeed, but a later retrieval of the first variable-length column will abend due to its overlaid offset field. If the table is of Basic Row Format (BRF), the SQL INSERT itself is expected to abend. Here is a DDL example of a table that is affected: CREATE TABLE USR1.TBL1 (C1 INTEGER NOT NULL, C2 VARCHAR(3200), C3 CHAR(8) NOT NULL DEFAULT USER ); ... unlike the following DDL, where the table is not affected: CREATE TABLE USR1.TBL1 (C1 CHAR(8) NOT NULL DEFAULT USER, C2 VARCHAR(3200), C3 INTEGER NOT NULL ); 1 ---------- Problem 2: ---------- DB2 10 introduced bind time Insert Procs (IProcs) in plans/ packages (before, they were only built at runtime). If the following conditions are true, a DSNISRTI 0C1 abend can happen: 1. Some package with a static SQL INSERT statement was bound in DB2 10, prior to applying PM63849 (UK79943). Let's call this a 'down-level' IProc. 2. A dynamic SQL INSERT statement was filling the default value for a table with USER or CURRENT SQLID. Let's call this a 'current-level' IProc. (Alternatively, a static SQL INSERT package bound after applying PM63849 (UK79943) would also contain a 'current-level' IProc.) 3. In the same thread, both the 'down-level' IProc and the 'current-level' IProc were used. Specifically, the problem was that the 'current-level' IProc would refer to a residual control block from the 'down-level' IProc, which was not set correctly. As a consequence, the 0C1 abend occurred. Here is a sample scenario for Problem 2: In an embedded application, there is a static SQL INSERT statement (regardless of whether it targets a table with USER / CURRENT SQLID default columns) as well as a dynamic SQL INSERT statement. The package was bound in DB2 10 before applying PM63849 (UK79943) and run after applying PM63849 (UK79943). Note: Should the Problem 2 occur (0C1 abend), until this APAR PM66487 is applied, a bypass would be to rebind the abending package. Once the APAR is applied, a rebind is not necessary. ---------- Problem 3: ---------- If the following conditions are true, an incorrect bind time IProc could be built: 1. The table's encoding scheme is EBCDIC 2. The table has column(s) with default value USER or CURRENT SQLID The bind time IProc would be incorrect in the sense that it would contain the bind time values of special registers USER and CURRENT SQLID, when it should have had their runtime values. The bind time length of USER and CURRENT SQLID registers is 1 different from runtime, so the IProc might populate the default value with an incorrect length, which during SQL INSERT could cause column overlay or truncation if the insert populates such columns with their default values. If the SQL INSERT does not abend and goes through, subsequently incorrout is possible though no such case has actually been reported at the time of writing. Regarding Problem 1 with the bad APAR PM63849 (UK79943), code has been changed to perform the move with a correct length. Regarding Problem 2 with the bad APAR PM63849 (UK79943), code has been changed to make sure the control block from a 'down-level' IProc is set correctly. Regarding Problem 3 with the EBCDIC table, DB2 code has been modified to build bind time IProcs in a way that they do not pick up the USER or CURRENT SQLID register values until runtime (execution time). Additional keywords: SQLINSERT SMCOVERLAY DB2OVRLAY/K SQLINCORR SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM66487 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM66487: See PM66487 APAR/PTF text for additional information about why a REBIND is necessary. PM66487 corrects a problem of column value overlay or truncation while executing a static insert statement, if the column has default value of USER or CURRENT SQLID. 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 PM63849: See PM63849 APAR/PTF text for additional information about why a REBIND is necessary. PM63849 corrects a problem of column value overlay or truncation while executing a static insert statement, if the column has default value of USER or CURRENT SQLID, and the table's encoding schema is UNICODE or ASCII, and the table is in Reordered Record Format (RRF). 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 DSNIRLPG PM66487 DSNISRTI PM66487 DSNIZAZM PM66487 DSNIZAZ2 PM66487 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66487 DSNIRLPG DSNISRTI DSNIZAZM DSNIZAZ2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRLPG DSNISRTI DSNIZAZM DSNIZAZ2 LISTEND UK82163 COVER LETTER END UK82190 COVER LETTER START PROBLEM DESCRIPTION(S): PM69147 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 terminates with an ABEND04E * * RC00E50705 in DSNVEUS2 if a DB2 agent * * receives an abend while connected to * * DB2. In this case the DB2 agent * * received an ABEND13E. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a DB2 agent is abended, recovery processing in module DSNAPRHX may fail to set status bits correctly and an additional ABEND04E RC00E50705 in DSNVEUS2 may occur. Module DSNAPRHX has been updated to correctly set status. COMPONENT: 5740-XYR01-HIZAA10 APARS FIXED: PM69147 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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. 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: 1 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: ***Action for PM57744: This PTF requires either an EARLY 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAPRHX PM69147 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69147 DSNAPRHX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAPRHX LISTEND UK82190 COVER LETTER END UK82218 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM60726 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of queries that use index access with the * * VARCHAR function on a large column in the * * SELECT and GROUP BY list. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at * * location DSNXGDT2:M111 during prepare * * or bindtime for a query that chooses * * index access and contains the VARCHAR * * function on a large column in the * * SELECT and GROUP BY list. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E70005 can occur at location DSNXGDT2 M111 during prepare or bindtime for a query that chooses index access and contains the VARCHAR function on a large column in the select and GROUP BY list which can become larger due to the use of the VARCHAR function, i.e. using VARCHAR(column_name,32767). The failing query produces an SQLCODE670 or SQLCODE -670 from DSNXOSEP loc -300 in DB2 for z/OS V8, in DB2 9 for z/OS, and DB2 10 for z/OS when index access is not chosen to support the GROUP BY. In DB2 9 for z/OS and DB2 10 for z/OS, if a unique index is chosen to support the GROUP BY and a sort is avoided because the unique index covers a subset of the GROUP BY columns, the failure occurs when a few internal variables become extended beyond their defined scope. The following example illustrates a failing case. Step 1. Create a Table TEST with a unique index. CREATE TABLE TEST (TEST_MY_INT INTEGER NOT NULL, TEST_MY_TS TIMESTAMP NOT NULL, TEST_MY_CHAR CHAR (20) NOT NULL, TEST_MY_VC VARCHAR (2000) WITH DEFAULT NULL, TEST_MY_CL CLOB (1048576) WITH DEFAULT NULL, TEST_MY_DEC DECIMAL (1,0) NOT NULL WITH DEFAULT 0, PRIMARY KEY (TEST_MY_INT, TEST_MY_TS) ) CCSID EBCDIC ; CREATE UNIQUE INDEX TESTX01 ON TEST( TEST_MY_CHAR ASC, TEST_MY_TS DESC ) ; Step 2. Populate catalog tables with statistics so that this index will be chosen (i.e. index access). 1 Step 3. Execute the following query. SELECT T1.TEST_MY_TS, T1.TEST_MY_CHAR, VARCHAR(T1.TEST_MY_VC,32767), T1.TEST_MY_DEC FROM TEST T1 WHERE T1.TEST_MY_CHAR = 'XXXXXXXX' GROUP BY T1.TEST_MY_TS, T1.TEST_MY_CHAR, VARCHAR(T1.TEST_MY_VC,32767), T1.TEST_MY_DEC; Please note that VARCHAR(T1.TEST_MY_VC,32767) can be replaced with VARCHAR(T1.TEST_MY_CL,32767) to use a LOB column to get the same failure. Step 4. The above failure can occur because the GROUP BY list contains a large element which can cause an internal variable to extend beyond its scope when processing GROUP BY lengths. A GROUP BY list length of 32K will be enforced during access path selection for queries where a unique index on a subset of the GROUP BY columns can support the GROUP BY. If the length is exceeded, an SQLCODE -134 will be issued, to prevent incorrect output for the query and to avoid the potential abend. Additional Keywords: SQLLOB SQLVARCHAR SQLGROUPBY SQLINDEX SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLCODE134 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM60726 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM67731 See PM67731 APAR/PTF text for additional information about why a REBIND is necessary. PM67731 corrects a problem that can return an incorrect result for a query that contains a SCALAR FULLSELECT on a select list involving a stage 2 predicate with a column that is also in the query's 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. DB2BIND: ***Action for PM60726: See PM60726 APAR/PTF text for additional information about 1 why a REBIND is necessary. PM60726 corrects a problem that can result in an ABEND04E RC00E70005 at location DSNXGDT2 M111 or incorrect output for queries that contain a GROUP BY with large columns where a unique index provides the support for the GROUP BY. 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 PM60726 DSNXOGP PM60726 DSNXOPB PM60726 DSNXRGBJ PM60726 DSNXRSGB PM60726 DSNXRSJ PM60726 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60726 DSNXGSGP DSNXOGP DSNXOPB DSNXRGBJ DSNXRSGB DSNXRSJ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGSGP DSNXOGP DSNXOPB DSNXRGBJ DSNXRSGB DSNXRSJ LISTEND UK82218 COVER LETTER END UK82225 COVER LETTER START PROBLEM DESCRIPTION(S): PM69226 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of host * * variable * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 CSECT DSNXROB9 can * * occur when using DOUBLE host variable * * to hold integer column data. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000010 CSECT DSNXROB9 can occur when using DOUBLE host variable to hold integer column data. An internal variable is overlaid and the overlay content causes the abend. This problem happens because DB2 doesn't define an internal variable longer enough for integer to DOUBLE conversion. 1 The following example can demonstrate this problem. 1. CREATE TABLE TB (C1 INTEGER); 2. Define a DOUBLE host variable named HV. 3. Declare cursor using the DOUBLE host variable to hold integer data and open,fetch cursor. EXEC SQL DECLARE C1 CURSOR FOR SELECT C1 FROM TB; EXEC SQL OPEN C1; EXEC SQL FETCH INTO :HV; The above abend can happen during the host variable binding process. This abend happens in V10 for V9 bound package. The same issue can happen in V10 for V10 bound package. DB2 is modified to define the internal variable correctly. ADDITIONAL KEYWORDS: SQLHOSTVAR ABEND0C4 FLOAT DOUBLE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69226 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXROB9 PM69226 DSNXROE9 PM69226 DSNXROHB PM69226 DSNXROHE PM69226 DSNXROHR PM69226 DSNXROHS PM69226 DSNXROH2 PM69226 DSNXROS9 PM69226 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69226 DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS DSNXROH2 DSNXROS9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS DSNXROH2 DSNXROS9 LISTEND UK82225 COVER LETTER END UK82304 COVER LETTER START 1 PROBLEM DESCRIPTION(S): PM70724 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: An MVS cancel during a * * service task create may result in * * an DB2 termination with * * RC00E50703. Utility jobs may be * * more prone to encounter this * * error. * **************************************************************** * RECOMMENDATION: * **************************************************************** Create service task processing may not recover an interruption during the resumption of the service task controller. If an MVS cancel interrupts processing just before or after calling DSNVSRX, DB2 will be terminated. The indoubt resume will be reissued by recovery. The service task controller will tolerate a double resume in the case that the resume was already issued. This avoids the need to terminate DB2 should an MVS cancel occur in this window. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70724 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNVCST0 PM70724 DSNVEUS4 PM70724 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70724 DSNVCST0 DSNVEUS4 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNVCST0 DSNVEUS4 LISTEND UK82304 COVER LETTER END UK82331 COVER LETTER START PROBLEM DESCRIPTION(S): PM69673 - **************************************************************** * USERS AFFECTED: All DB2 users of DB2 Dynamic Statement Cache * * and static SQL that fire DB2 triggers that * * invoke stored procedures containing dynamic * * SQL * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE904 RC00E70081 received when * * user attempted to issue DDL statement * 1 * for an object used by dynamic SQL that * * was cached in the DB2 Dynamic Statement * * Cache * **************************************************************** * RECOMMENDATION: * **************************************************************** SQLCODE904 RC00E70081 returned by DB2 for DDL statement when Dynamic Static Caching (DSC) is/was active and ALL of the following apply: 1 - a previously run transaction issued static SQL that caused an SQL trigger to fire and the trigger invoked a stored procedure that opens a dynamic WITH HOLD cursor, and 2 - the only dynamic SQL that qualified for statement caching on that DB2 connection / thread was issued by that stored procedure, and no other dynamic SQL was issued on that DB2 thread 'before' the trigger was fired. . If the DB2 transaction was cancelled, then in the above scenario the SQLCODE -904 can occur if the stored procedure issues ANY dynamic SQL, not just a dynamic cursor WITH HOLD. . DB2 Development determined that the problem occurred because when the trigger ended, DB2 did not maintain the internal indicator that tracked that a dynamic statement was cached while under the trigger execution. Therefore, when the transaction and DB2 thread ended, DB2 did not reset this DB2 thread's usage registration of the cached dynamic SQL statement. This resulted in the invalid SQLCODE -904 being received on a later attempt to perform DDL on an object referenced by that dyn SQL statement. . The problem does NOT occur if either of the following are true for the above described trigger scenario: - the SQL stmt causing the trigger to be fired is dynamic SQL that was cached in the DSC. - at least one dynamic SQL was cached in the DSC 'before' the trigger was fired or cached later 'outside' of trigger. - in the non-cancel scenario, the dynamic cursor is NOT defined as WITH HOLD . Note that a SQLCODE -904 RC00E70081 occurring for DDL on an object referenced by a cached dyn SQL statement that is still 'in use' by a currently active DB2 thread is a valid SQLCODE904, and this apar does not prevent that. DB2 code was changed to, when the trigger ends in the previously described scenario, maintain the DB2 internal indicator that Dynamic Statement Caching was done while executing the trigger. For this specific scenario, this prevents the SQLCODE904 from occurring when DDL is later attempted on an object associated with a cached dyn SQL statement in this scenario. . For future diagnostic purposes, DB2 code was also changed to mark an existing internal statement control block when a cached dyn SQL statement is used specifically while executing under a stored procedure, SQLPL procedure, UDF, or trigger. . Additional search keywords: sqldynstmtcache sqltrigger sqlsp 1 sqlstoredproc sqlprocedure 00E70081 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69673 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 PM69673 DSNXEDS1 PM69673 DSNXESTR PM69673 DSNXEXAT PM69673 DSNXEXBT PM69673 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69673 DSNXEDSC DSNXEDS1 DSNXESTR DSNXEXAT DSNXEXBT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEDSC DSNXEDS1 DSNXESTR DSNXEXAT DSNXEXBT LISTEND UK82331 COVER LETTER END UK82333 COVER LETTER START PROBLEM DESCRIPTION(S): PM58600 - **************************************************************** * USERS AFFECTED: All users of Distributed Data Facility (DDF) * * and DB2 Resource Limit Facility. * **************************************************************** * PROBLEM DESCRIPTION: DB2 uses the wrong resource limits to * * control resource usage for remote * * dynamic SQL statements. * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote client application connects to a DB2 for z/OS server and sends client information special registers such as application name, userid, and workstation name. These client information special registers are used by DB2 in conjunction with the resource limit specification table to determine what resource limits govern the processing of SQL statements. However, DB2 does not always correctly use updated special registers sent by the client to look up the resource limit table at the start of a new transaction. This resulted in DB2 using incorrect resource limits to govern subsequent SQL statements. If a client application sets or changes client information special registers before a new transaction executes SQL 1 statements, the DB2 server ensures that the updated client information is used to determine the correct resource limits in effect for the SQL requests executed by the transaction. Prior to this change, DB2 only considered client information supplied when the connection is first used. With this change, DB2 allows better control and limiting of the amount of processor resources for remote queries when connections are reused by different clients, applications, and users. See "DB2 for z/OS Managing Performance, Chapter 15 Settings limits for system resource usage by using the resource limit facility, Limiting resource usage by client information for middleware servers" for more details. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58600 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The following text is added to DB2 for z/OS Managing Performance, Chapter 15 Setting limits for system resource usage by using the resource limit facility, Limiting resource usage by client information for middleware servers: . The values for the client information that are found at the start of a new unit-of-work are used to determine which row of the RLMT table controls the processing of dynamic requests for the duration of the unit-of-work. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLXPCA PM58600 DSNLXRSS PM58600 DSNLXSR PM58600 DSNLXSRL PM58600 DSNLXSRP PM58600 DSNXEDP PM58600 DSNXEDSC PM58600 DSNXEDS1 PM58600 DSNXEET PM58600 DSNXERT PM58600 DSNXERT2 PM58600 DSNXRSTP PM58600 DSNXRSTS PM58600 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58600 DSNLXPCA DSNLXRSS DSNLXSR DSNLXSRL DSNLXSRP DSNXEDP DSNXEDSC DSNXEDS1 DSNXEET DSNXERT DSNXERT2 DSNXRSTP DSNXRSTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLXPCA DSNLXRSS DSNLXSR DSNLXSRL DSNLXSRP DSNXEDP 1 DSNXEDSC DSNXEDS1 DSNXEET DSNXERT DSNXERT2 DSNXRSTP DSNXRSTS LISTEND UK82333 COVER LETTER END UK82335 COVER LETTER START PROBLEM DESCRIPTION(S): PM64914 - **************************************************************** * USERS AFFECTED: All users of DB2 10 and 9 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: While searching for free space to * * insert the record, an incorrect * * segment number could have been used * * to cause the following: * * -ABEND04E RC00C90101 at DSNISUPI 5008 * * -ABEND04E RC00C90101 at DSNISGSS 5004 * **************************************************************** * RECOMMENDATION: * **************************************************************** When calculating the segment number to find free space a zero value would be calculated if an error occurred and would be treated as a valid segment number. This eventually resulted in the ABENDS: -ABEND04E RC00C90101 at DSNISUPI 5008 -ABEND04E RC00C90101 at DSNISGSS 5004 Code has been changed such that when a zero valued segment number is calculated it would be ignored and not used when determining where there is free space. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64914 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISUPI PM64914 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64914 DSNISUPI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISUPI LISTEND UK82335 COVER LETTER END 1 UK82365 COVER LETTER START PROBLEM DESCRIPTION(S): PM68895 - **************************************************************** * USERS AFFECTED: All DB2 10 NFM for z/OS users of UTS table * * spaces where an UPDATE SQL statement is * * executed. * **************************************************************** * PROBLEM DESCRIPTION: Various abends occurred as below: * * ABEND04E RC00C90105 in DSNIREPR * * ERQUAL0C32 or ABEND04E RC00C90102 in * * DSNIBHRE ERQUAL0C30 while running with * * an UPDATE SQL statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** When one of partitions in the PBG UTS table space is full and DB2 requires to insert a system record into this partition due to the table has been previously altered. While executing an UPDATE SQL statement, DB2 detects the data set full status and requests both system records and the newly updated row being inserted into a different partition. DB2 mistakenly treats this pseudo delete as an old delete scheme which thereafter caused the data inconsistency. DB2 code is modified to correctly treats this delete as a new pseudo delete scheme to avoid the data inconsistency. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68895 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 PM68895 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68895 DSNIREPR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIREPR LISTEND UK82365 COVER LETTER END UK82379 COVER LETTER START PROBLEM DESCRIPTION(S): PM67626 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in CSECT DSNTLDEA. * **************************************************************** 1 * RECOMMENDATION: * **************************************************************** Abend0C4 in CSECT DSNTLDEA occurred when IRLM reported deadlock between two units of recovery at DB2 restart. IRLM code incorrectly accessed an internal control block and incurred ABEND0C4. This APAR corrects the code in Deadlock Exit to avoid ABEND0C4 when deadlock is involved between two units of recovery at DB2 restart. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM67626 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 PM67626 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM67626 DSNTLDEA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLDEA LISTEND UK82379 COVER LETTER END UK82384 COVER LETTER START PROBLEM DESCRIPTION(S): PM68130 - **************************************************************** * USERS AFFECTED: All users of DB2 9 for z/OS and DB2 10 for * * z/OS RECOVER utility on objects with * * referential integrity (RI) relationships. * **************************************************************** * PROBLEM DESCRIPTION: RECOVER TABLESPACE db-name.ts-name * * DSNUM n TOLOGPOINT on a partition of * * a table space that contains a * * dependent table with two or more * * parents: * * - issued msgDSNU535I incorrectly * * - left the table space in R/W status * * instead of CHKP (check-pending) * * status * **************************************************************** * RECOMMENDATION: * **************************************************************** A user recovered one partition of a table space that contains a dependent table to a point in time. The dependent table has two parent tables. The recovery did not include the rest of the objects in the RI set. In this case: -msgDSNU535I (FOLLOWING TABLESPACES RECOVERED TO A CONSISTENT POINT) is issued incorrectly 1 -the table space is left in R/W status instead of CHKP status The RECOVER utility was not detecting that a partial RI set was recovered to a point in time when a partition of a table space that contains a table with two or more parents is recovered. Additional keywords: TORBA DSNU535I The RECOVER utility has been modified to correctly detect that a partial RI set was recovered to a point in time. For the reported scenario, msgDSNU535I is no longer issued, msgDSNU561I (TABLESPACE PARTITION n IS IN CHECK PENDING) is issued, and the table space with the dependent table is left in the CHKP state. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68130 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCATM PM68130 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68130 DSNUCATM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCATM LISTEND UK82384 COVER LETTER END UK82408 COVER LETTER START PROBLEM DESCRIPTION(S): PM68447 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * SQL statements that reference to * * view or table expressions and SET * * function. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0038 in * * DSNXGRDS.DSNXOEX1:22DE * * may occur for an SQL statement * * that satisfies the following * * conditions: * * 1. The statement references to a * * table expression or view * * 2. The table expression or view * * is merged. * * 3. The table expression or view column * * appears in a predicate and is an * * argument of a SET function. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 ABEND0C4 RC0038 in DSNXGRDS.DSNXOEX1:22DE may occur for an SQL statement that satisfies the following conditions: 1. The statement references to a table expression or view 2. The table expression or view is merged. 3. The table expression or view column appears in a predicate and is an argument of a SET function. For Example, SELECT * FROM (SELECT MAX(COL1) FROM (SELECT 2 AS COL1 FROM SYSIBM.SYSDUMMY1 )T1(COL1) )T2(COL1) WHERE T2.COL1 > 10; The SELECT statement above may cause an abend since the column T2.COL1 in the predicate is not merged correctly. DB2 was fixed to merge the table expression or view that contains a SET function correctly. Additional Keywords: SQLVIEW SQLTABLEEXPR SQLSETFUNCTION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68447 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOEX1 PM68447 DSNXOMTX PM68447 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68447 DSNXOEX1 DSNXOMTX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEX1 DSNXOMTX LISTEND UK82408 COVER LETTER END UK82421 COVER LETTER START PROBLEM DESCRIPTION(S): PM71856 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: DB2 z/OS threads may not terminate * * after being cancelled if the thread * * is waiting for a reply from a remote * * downstream location (via a TCP/IP * * connection). * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PM54383 introduced support to allow thread cancel events to be honored when the thread is cancelled while waiting for a TCP/IP reply from a remote downstream location. This function utilizes a TCP/IP Drop API, implemented via APAR PM48851, which requires DB2 to determine the TCP/IP connection number associated with the downstream connection. In environments where DB2 may be associated with multiple IP addresses, such as DB2 data sharing environments where DVIPAs are defined, DB2 may not be able to determine the TCP/IP connection number because TCP/IP may associate the connection to a local IP address that DB2 is unaware of (and which is not reflected in DB2 Display DDF command report). The absence of the TCP/IP connection number knowledge prevents DB2 from being able to successfully Drop the connection during cancel events and hence the cancel event will not be fully honored. To allow the thread termination to complete, intervention will be required to terminate the TCP/IP connection to the remote downstream location. This intervention procedure is currently documented in the "Usage notes" section of the DB2 for z/OS "CANCEL THREAD" command in the DB2 for z/OS Command Reference manual. DB2 has been changed to obtain the correct local IP address associated with the downstream connection. This allows the associated connection number to also be obtained and hence allows cancel events to be fully honored. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71856 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 PM71856 DSNLIRQP PM71856 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71856 DSNLIAAC DSNLIRQP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIAAC DSNLIRQP LISTEND UK82421 COVER LETTER END UK82457 COVER LETTER START PROBLEM DESCRIPTION(S): PM58555 - **************************************************************** 1 * USERS AFFECTED: All DB2 for z/OS data sharing users * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBHK ERQUAL5453 * * or * * ABEND04E RC00E20005 DSNSVBK * * or * * ABEND04E RC00C90101 DSNIDBNG ERQUAL5006 * * during RECOVER Utility or DROP of an * * object or rebuild of SCA (i.e. SETXCF) * **************************************************************** * RECOMMENDATION: * **************************************************************** During execution of RECOVER TABLESPACE utility, DBET was invoked to reset the GRECP/LPL state from a large number of partitions of an object. However, DBET did not allocate sufficient storage to process this request. DBET used more storage than allocated and caused an overlay. As a result, different abends were encountered. In another scenario, DBET also did not allocate sufficient storage during DDL DROP of an object, when the object had a large number of partitions in an exception state. The DDL DROP caused a storage overlay. DB2 has been updated to allocate sufficient storage. Additional keyword: SMCOVERLAY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM58555 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBDF PM58555 DSNIDBNG PM58555 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM58555 DSNIDBDF DSNIDBNG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBDF DSNIDBNG LISTEND UK82457 COVER LETTER END UK82460 COVER LETTER START PROBLEM DESCRIPTION(S): PM71756 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * perform sort for data that contains a * * variable length field. * 1 **************************************************************** * PROBLEM DESCRIPTION: An incorrect result set can be returned * * for a query that contains a variable * * length field that is part of the 'final * * sorted in-memory workfile' if the * * consumer of this workfile does not * * recognize that a variable length field * * is included. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result can be returned for a query if sort decides to create an in-memory workfile which contains variable length fields if the consumer of this in-memory workfile does not recognize that variable length fields are included in the data. The following sample query, which uses the VARCHAR_FORMAT function, can cause this 'confusion for the consumer' when it contains an expression. SELECT INTEGER (SUM(C1)) FROM TBL1 GROUP BY VARCHAR_FORMAT(0+C2); The code in DB2 has been modified to check if there is a mismatch in the 'variable length bit' for the consumer and for sort. If there is a mismatch, then sort will not create an in- memory workfile. This will prevent an incorrect result from being returned. Additional Keywords: SQLSORT SQLINCORROUT DB2INCORR SQLINCORR INCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71756 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRSOR PM71756 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71756 DSNXRSOR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRSOR LISTEND UK82460 COVER LETTER END UK82494 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM70389 - **************************************************************** * USERS AFFECTED: All users of the DSNTXAZP tool and of * * stored procedures SYSPROC.DSNWZP and * * SYSPROC.ADMIN_INFO_SYSPARM are affected by * * this change. * **************************************************************** * PROBLEM DESCRIPTION: One or more of the following problems * * occurs when DB2 specifies one or more * * databases, table spaces, or index * * spaces that are to be restarted or * * deferred at startup time: * * (1) DSNTXAZP records an invalid setting * * for DBSTARTM when refreshing a DB2 * * installation CLIST settings * * (DSNTIDxx) member * * (2) SYSPROC.ADMIN_INFO_SYSPARM and * * SYSPROC.DSNWZP return an invalid * * value for the RESTART DEF setting * **************************************************************** * RECOMMENDATION: Apply the fixing PTF for this APAR * **************************************************************** This APAR addresses the following errors that occur when the subsystem parameter (DSNZPxxx) module for DB2 specifies one or more databases, table spaces, or index spaces that are to be restarted or deferred when DB2 starts: (1) DSNTXAZP records an invalid setting for DBSTARTM when refreshing a DB2 installation CLIST settings (DSNTIDxx) member (2) SYSPROC.ADMIN_INFO_SYSPARM and SYSPROC.DSNWZP return an invalid value for the RESTART DEF setting DSNTXAZP is a DB2-supplied program that can be used to refresh a DB2 installation CLIST settings (DSNTIDxx) member with DB2's current subsystem parameter, DSNHDECP, and buffer pool settings. SYSPROC.ADMIN_INFO_SYSPARM and SYSPROC.DSNWZP are DB2-suppplied stored procedures that return DB2's current subsystem parameter and DSNHDECP settings. Currently, a bug in a common module shared by these programs causes them to return unexpected results as noted. In response, this APAR fixes the bug so that the correct values are returned. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70389 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNWZIFA PM70389 DSNWZIF9 PM70389 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70389 DSNWZIFA DSNWZIF9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNWZIFA DSNWZIF9 LISTEND UK82494 COVER LETTER END UK82510 COVER LETTER START PROBLEM DESCRIPTION(S): PM70190 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: For non-UTS objects, possible S0C4 * * abends can occur in code that address * * beyond the range of a page in * * DSNIMSMC, DSNISFRL, DSNISFS, DSNISRID * * and DSNIRPRE. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 code that use a deleted idmap entry for a non-UTS object to set an offset into a data page can inadvertently address beyond the data page boundary. The IDMAP entry may have its PGMNREUS bit set which leads to this incorrect offset. This may cause 0C4 or other abends when addressing out of bounds storage areas. DB2 code has been corrected to prevent the 0C4 abends. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70190 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIONX2 PM70190 DSNIOST2 PM70190 DSNIRPRE PM70190 DSNISFRL PM70190 DSNISFS PM70190 DSNISFX2 PM70190 DSNISRID PM70190 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70190 DSNIONX2 DSNIOST2 DSNIRPRE DSNISFRL DSNISFS DSNISFX2 DSNISRID THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNIONX2 DSNIOST2 DSNIRPRE DSNISFRL DSNISFS DSNISFX2 DSNISRID LISTEND UK82510 COVER LETTER END UK82535 COVER LETTER START PROBLEM DESCRIPTION(S): PM71120 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of query parallelism * * and OmniFind Text Search. * **************************************************************** * PROBLEM DESCRIPTION: When query parallelism is enabled and * * the query has a CONTAINS or SCORE * * function, an abend may occur during * * prepare or bind: * * * * ABEND04E RC00E70005 in DSNXOSR :P016 * * * **************************************************************** * RECOMMENDATION: * **************************************************************** When query parallelism is enabled and the query has a CONTAINS or SCORE function, an abend may occur during prepare or bind: ABEND04E RC00E70005 in DSNXOSR :P016 An example query that exhibits the problem: SELECT A.INT1, B.INT2 FROM T1 A, T2 B WHERE A.INT1 = B.INT2 AND CONTAINS(A.VC2, 'TEXT') = 1 AND CONTAINS(B.VC2, 'TEXT') = 1; The abend was caused by program error. Additional keywords: ABEND04E RC00E70005 SQLPARALLELISM DB2PARALL/K SQLCONTAINS SQLSCORE DB2 code has been changed to fix the problem. The abend no longer occurs for this scenario. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71120 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 DSNXOLAP PM71120 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71120 DSNXOLAP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLAP LISTEND UK82535 COVER LETTER END UK82538 COVER LETTER START PROBLEM DESCRIPTION(S): PM54599 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS who have a query that * * has a scalar full select predicate, or has * * a prediate which has a CASE expression * * that contains a subquery. There is also an * * index created on the column expression * * that matches the predicate. * **************************************************************** * PROBLEM DESCRIPTION: If a predicate contains scalar full * * select or an CASE expression that has * * a subquery, then it is not indexable. * * But if there is an index created * * on the column expression, the optimizer * * may select the predicate as matching * * or screening by mistake, which may * * result in incorrect output. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a predicate contains scalar full select, or contains a CASE expression which has a subquery, then it is not indexable. But if there is an index created on the column expression, the optimizer may select the predicate as matching or screening by mistake, which may result in incorrect output. Example 1: SELECT * FROM T1 WHERE YEAR(C1) BETWEEN 1992 AND (SELECT MAX(YEAR) FROM T2) The BETWEEN predicate contains a scalar full select, and there is also an index created on column expression YEAR(C1). The optimizer may select this index and use the BETWEEN predicate as a matching predicate, which may get incorrect output. Example 2: SELECT * FROM T1 WHERE YEAR(C1) IN 1 ( CASE WHEN EXISTS(SELECT 1 FROM T2) THEN 2011 ELSE 2012 END ); For the above query, the IN predicate contains a CASE expression, and there is a subquery in the CASE expression. There is also an index created on column expression YEAR(C1). The optimizer may select this index and use the IN predicate as a matching predicate, which may get incorrect output. ADDITIONAL KEYWORDS: SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLSUBQUERY SQLSCALAR SQLFULLSELECT SQLSCALARFULSEL SQLCASE Code is changed to fix the problem above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM54599 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM65851: See PM65851 APAR/PTF text for additional information about why a REBIND is necessary. PM65851 corrects a problem that incorrect output or SQLCODE -180 could happen for an SQL statement that satisfies all of the following conditions: 1. It contains UNION ALL and union distribution applies to the SQL statement. 2. It contains a predicate with an SQL scalar function, and the predicate is distributed to the UNION ALL branches. 3. The scalar function has an input parameter that is referenced multiple times in the RETURN statement of the function, and the input for this parameter contains host variables or parameter markers. 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 PM54599: See PM54599 APAR/PTF text for additional information about why a REBIND is necessary. PM54599 corrects a problem that incorrect output may be returned if a predicate containing scalar full select or containing CASE expression which has a subquery, and optimizer selects it as a matching or screening predicate for an index on expression 1 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 PM52371: See PM52371 APAR/PTF text for additional information about why a REBIND is necessary. PM52371 corrects a problem of unexpected SQLCODE -161 issued for an INSERT into SYMMETRIC view 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 DSNXOEXC PM54599 DSNXOGBM PM54599 DSNXOW2F PM54599 DSNXOW2G PM54599 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM54599 DSNXOEXC DSNXOGBM DSNXOW2F DSNXOW2G THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOEXC DSNXOGBM DSNXOW2F DSNXOW2G LISTEND UK82538 COVER LETTER END UK82555 COVER LETTER START PROBLEM DESCRIPTION(S): PM70270 - **************************************************************** * USERS AFFECTED: All DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: A lower buffer pool hit ratio or more * * synchronous I/O. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a random GetPage operation steals a buffer from the sequential LRU (SLRU) chain, DB2 does not reclassify the stolen buffer. In rare cases, it may result in a lower buffer pool hit ratio or more synchronous I/O. 1 DB2 has been fixed to reclassify a buffer that is stolen from the SLRU chain for a random GetPage operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70270 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1CMS PM70270 DSNB1GET PM70270 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70270 DSNB1CMS DSNB1GET THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1CMS DSNB1GET LISTEND UK82555 COVER LETTER END UK82575 COVER LETTER START PROBLEM DESCRIPTION(S): PM73376 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * involve pushed down predicates which * * reference LOBs. * **************************************************************** * PROBLEM DESCRIPTION: An incorrect result can be returned for * * a query that contains a pushed down * * predicate which references a LOB. * **************************************************************** * RECOMMENDATION: * **************************************************************** An incorrect result can be returned for a query that contains a pushed down predicate which references a LOB. The following query is an example which could return an incorrect result. SELECT * FROM TB1 WHERE CAST(CAST(COL1 AS CLOB(100)) AS CHAR(1)) LIKE 'S'; This query contains a pushed down predicate. COL1 is defined as a CHAR(20). When casting the CLOB to a CHAR(1), LOB manager issued an SQLCODE +445 (A VALUE HAS BEEN TRUNCATED) and set an internal reason code to non-zero. However, the row qualifies the residual predicate (Runtime returns return code 0 to Data Manager). If an index scan was chosen as the access type, Data Manager maps the non-zero reason code to return code 4 indicating that no qualified row was found (or no rows qualify) 1 causing an incorrect result to be returned. The code in DB2 was modified so that a correct result is returned. Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLPREDPUSHDOWN SQLLOB COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73376 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIONX2 PM73376 DSNIOST2 PM73376 DSNIRIDL PM73376 DSNIRNXT PM73376 DSNISFX2 PM73376 DSNISRID PM73376 DSNIWNRF PM73376 DSNIXLDI PM73376 DSNKFLRR PM73376 DSNKFLST PM73376 DSNKFPRV PM73376 DSNKFTCH PM73376 DSNKFTRR PM73376 DSNKNXT2 PM73376 DSNOLDEL PM73376 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73376 DSNIONX2 DSNIOST2 DSNIRIDL DSNIRNXT DSNISFX2 DSNISRID DSNIWNRF DSNIXLDI DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIONX2 DSNIOST2 DSNIRIDL DSNIRNXT DSNISFX2 DSNISRID DSNIWNRF DSNIXLDI DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL LISTEND UK82575 COVER LETTER END 1 UK82610 COVER LETTER START PROBLEM DESCRIPTION(S): PM70315 - **************************************************************** * USERS AFFECTED: All DB2 users of CP query parallelism. * **************************************************************** * PROBLEM DESCRIPTION: The WSTRAN, WSNAME & WSUSER fields * * on the DB2 Query Monitor were empty * * when the monitor displays the * * parallel tasks. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 did not set the WSTRAN, WSNAME & WSUSER fields for a parallel task. DB2 has been corrected to set the WSTRAN, WSNAME and WSUSER fields correctly, so these fields can be externalized on query monitor. sqlparallelism DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70315 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTTRUN PM70315 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70315 DSNTTRUN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTTRUN LISTEND UK82610 COVER LETTER END UK82637 COVER LETTER START PROBLEM DESCRIPTION(S): PM72718 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of UNLOAD * * WHEN with partition parallelism active and * * with PM65550 / UK80678 applied. * **************************************************************** * PROBLEM DESCRIPTION: After applying PM65550 / UK80678, * * an ABEND0C4 DSNUUSEL OFFSET0142 can * * occur when running an UNLOAD with a * * WHEN clause and partition parallelism * * active. * **************************************************************** 1 * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** After applying PM65550 / UK80678 an ABENDS0C4 DSNUUSEL + x'0142' can occur when running an UNLOAD with a WHEN clause and partition parallelism active. The problem occurs when the number of subtasks does not match the number of partitions being unloaded, resulting in an internal control structure not getting setup correctly. UNLOAD WHEN with partition parallelism active has been changed to initialize the internal control structure for all partitions being unloaded. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72718 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: The REORG TABLESPACE utility on DSNDB06.SYSTSSTG or DSNDB06.SYSTSVOL with the SHRLEVEL NONE option will issue MSGDSNU1152I during the UTILINIT phase if there are any user defined indexes managed by DB2 storage groups. The explanation of DSNU1152I is modified .. DSNU1152I csect-name utility-name SHRLEVEL option OF object-type object-qualifier.object-name Explanation The SHRLEVEL option was specified incorrectly for a utility. csect-name The name of the control section that issued the message. utility-name The name of the utility: REORG TABLESPACE, REORG INDEX, or REBUILD INDEX. option The SHRLEVEL option: CHANGE, REFERENCE, or NONE. The combination of option and utility-name indicates what has occurred. CHANGE If utility is REORG TABLESPACE: SHRLEVEL CHANGE was specified when REORG TABLESPACE was run on a NOT LOGGED table space, or on a LOB table space for which the base table space is a NOT LOGGED table space. If utility is REBUILD INDEX or REORG INDEX: SHRLEVEL CHANGE was specified when REBUILD INDEX or REORG INDEX was run on an index that is defined on a NOT LOGGED table space. REFERENCE SHRLEVEL REFERENCE was specified when REORG TABLESPACE with PART was run on a NOT LOGGED table space on which nonpartitioned indexes are defined. 1 NONE SHRLEVEL NONE cannot be specified for a table space with hash organization. | SHRLEVEL NONE cannot be specified with REORG TABLESPACE | against either DSNDB06.SYSTSVOL or DSNDB06.SYSTSSTG when | there are any user defined indexes which are stogroup | defined. object-type The type of object: INDEX, INDEXSPACE, or TABLESPACE. object-qualifier.object-name The name of the object, as a qualified name. System action If the utility was operating on a list of objects and OPTIONS EVENT(ITEMERROR,SKIP) was specified, then processing continues to the next object in the list. Otherwise, processing terminates. Operator response Take the appropriate action for the object-type value: NOT LOGGED TABLESPACE Remove the SHRLEVEL(CHANGE) or SHRLEVEL(REFERENCE) option from the utility statement. HASH TABLESPACE Specify either SHRLEVEL(CHANGE) or SHRLEVEL(REFERENCE) option in the utility statement. |CATALOG TABLESPACE DSNDB06.SYSTSVOL and DSNDB06.SYSTSSTG | Specify either SHRLEVEL(CHANGE) or SHRLEVEL(REFERENCE) | option in the utility statement Severity 8 (error) COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURFBR PM72718 DSNURFIT PM72718 DSNURPUI PM72718 DSNURSCN PM72718 DSNUUGMS PM72718 DSNUULCA PM72718 DSNUULJA PM72718 DSNUULXA PM72718 DSNUUSEL PM72718 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72718 DSNURFBR DSNURFIT DSNURPUI DSNURSCN DSNUUGMS DSNUULCA DSNUULJA DSNUULXA DSNUUSEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNURFBR DSNURFIT DSNURPUI DSNURSCN DSNUUGMS DSNUULCA DSNUULJA DSNUULXA DSNUUSEL LISTEND UK82637 COVER LETTER END UK82643 COVER LETTER START PROBLEM DESCRIPTION(S): PM73000 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS utility users of REORG * * DISCARD WHEN, REORG UNLOAD EXTERNAL WHEN, * * and UNLOAD WHEN * **************************************************************** * PROBLEM DESCRIPTION: REORG DISCARD WHEN discarded more rows * * than expected when the selection clause * * contained ANDs and ORs at the same * * level without parentheses to specify * * the order of precedence * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** REORG DISCARD WHEN discarded more rows than expected when the selection clause contained ANDs and ORs at the same level without parentheses to specify the order of precedence. The utility selection clause processing incorrectly evaluated the precedence of the ANDs and ORs at the same level. The same problem can occur for REORG UNLOAD EXTERNAL WHEN and UNLOAD WHEN. Example of error case: ((COL1<>'ABC') OR (COL1 IN ('DEF', 'GHI')) AND (COL2<100)) Example of a workaround (case that is working): ((COL1<>'ABC') OR ((COL1 IN ('DEF', 'GHI')) AND (COL2<100))) Additional keywords: DB2INCORR/K REORG and UNLOAD code have been changed to process the selection clause correctly when there are ANDs and ORs at the same level. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73000 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 DSNUUGMS PM73000 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73000 DSNUUGMS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUUGMS LISTEND UK82643 COVER LETTER END UK82645 COVER LETTER START PROBLEM DESCRIPTION(S): PM57440 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of utilities with OPTIONS EVENT(ITEMERROR, * * SKIP) * **************************************************************** * PROBLEM DESCRIPTION: 1. ABEND04E RC00C90101 DSNIBHUN * * ERQUAL500C during the LOGUNDO phase of * * RECOVER BACKOUT YES on a list of * * objects with OPTIONS EVENT(ITEMERROR, * * SKIP) when a previous invocation of the * * same utility received MSGDSNU180I * * (UTILITY IS NOT COMPATIBLE) on some * * objects * * * * 2. COPY utility against a partitioned * * table space with OPTIONS * * EVENT(ITEMERROR,SKIP) continued copy * * processing for some of partitions even * * though the whole table space was in * * RECOVER PENDING state * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** 1. In DB2 10, RECOVER BACKOUT YES on a list of objects with OPTIONS EVENT(ITEMERROR,SKIP) was executed and received message DSNU180I (UTILITY IS NOT COMPATIBLE WITH THE utility-name UTILITY UTILID= utility-id, OBJECT = space-name.object-name) on some of the objects in the list. Due to a code error in utility serialization processing, the RECOVER utility continued without checking for prohibitive DBET status, and without setting UTUT on the objects that did not receive the DSNU180I message. The serialization error also caused processing to be skipped in the UTILTERM phase. When the same RECOVER BACKOUT YES utility was submitted again, it should not have been allowed to execute because multiple RECOVER BACKOUT YES invocations that process the same log ranges are not allowed. However, because the previous invocation incorrectly skipped 1 the UTILTERM phase, it was allowed to execute and received the ABEND04E RC00C90101 in DSNIBHUN with ERQUAL500C in the LOGUNDO phase. The utility serialization error that incorrectly skips the checking for prohibitive DBET statuses and skips the setting of the utility in progress state (UTUT,UTRW,UTRO) when a compatibility error (MSGDSNU180I) is detected for some of the objects in a list exists in DB2 9 and also affects these utilities: COPY, QUIESCE, REBUILD INDEX, COPYTOCOPY, RUNSTATS and CHECK INDEX. 2. When a COPY utility with OPTIONS EVENT(ITEMERROR,SKIP) ran against a partitioned table space in which all partitions were in RECOVER PENDING state, the COPY was not prohibited completely in checking prohibitive DBET states processing, leaving some of partitions to continue processing. The problem happened because after issuing message DSNU202I for the first partition, the skip flags for the rest of partitions were not set properly. The same problem also exists in these utilities: QUIESCE, RECOVER BACKOUT YES, REBUILD INDEX, CHECK INDEX and RUNSTATUS. 1. The utility serialization code has been modified to correctly handle the scenario where some of the objects in the list receives a compatibility error and OPTIONS EVENT(ITEMERROR,SKIP) has been specified 2. The utility serialization code has been modified to correctly handle the restricted DBET states for the partitioned table space when OPTIONS EVENT(ITEMERROR,SKIP) has been specified. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM57440 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGDTC PM57440 DSNUGSRI PM57440 DSNUGUCC PM57440 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM57440 DSNUGDTC DSNUGSRI DSNUGUCC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGDTC DSNUGSRI DSNUGUCC LISTEND UK82645 COVER LETTER END 1UK82672 COVER LETTER START PROBLEM DESCRIPTION(S): PM69812 - **************************************************************** * USERS AFFECTED: DB2 users using scrollable cursor on DGTT * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 at DSNB1RLS * **************************************************************** * RECOMMENDATION: * **************************************************************** A chain of reader threads is maintained for a page set. When a thread registers its read interest in a page set, the thread is chained; when a thread does de-register, it is de-chained. When a scrollable cursor is defined on a DGTT, the DGTT can be registered. However, the de-chain process is missed for a DGTT so a de-allocated thread may still be chained. This leads to an 0C4 abend when a new thread registers its interest. The de-chain logic has been added for DGTT. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69812 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1DCM PM69812 DSNB1OFA PM69812 DSNB1OPS PM69812 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69812 DSNB1DCM DSNB1OFA DSNB1OPS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DCM DSNB1OFA DSNB1OPS LISTEND UK82672 COVER LETTER END UK82674 COVER LETTER START PROBLEM DESCRIPTION(S): PM73365 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 users of CP Query * * Parallelism. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B DSNSVSFB +0698 * * with CP parallelism * **************************************************************** * RECOMMENDATION: * **************************************************************** 1 During cleanup processing for CP query parallelism tasks, if an ABEND occurred within a timing window, a pointer to a freed control block that represented a parallel task would remain pointing to freed storage. This pointer was later referenced, and caused the symptom ABEND. DB2 code has been modified to correctly zero the pointer noted above, when its storage was freed. Additional keywords: SQLPARALLELISM DB2PARALL/K SQLCPUP COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73365 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECLN PM73365 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73365 DSNXECLN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECLN LISTEND UK82674 COVER LETTER END UK82678 COVER LETTER START PROBLEM DESCRIPTION(S): PM71335 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an SQL * * statement that contains table expressions or * * views with UNION ALL and special register in * * predicate. * **************************************************************** * PROBLEM DESCRIPTION: 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output could happen for an SQL statement that satisfies all of the following conditions: 1 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. An example is shown below: SET CURRENT SCHEMA = 'ABC'; CREATE TABLE T1( C1 INT, C2 CHAR(8)); CREATE TABLE T2( C1 INT, C2 CHAR(8)); INSERT INTO T1 VALUES(11, 'XYZ'); INSERT INTO T1 VALUES(12, 'ABC'); INSERT INTO T2 VALUES(21, 'XYZ'); INSERT INTO T2 VALUES(22, 'ABC'); SELECT TX.C1, TX.C2 FROM (SELECT C1, C2 FROM T1 UNION SELECT C1, C2 FROM T2) TX(C1, C2), (SELECT C2 FROM T1 UNION ALL SELECT C2 FROM T2) TY(C2) WHERE TX.C2 = CURRENT SCHEMA; The query above should return 8 rows, while incorrectly returned 0 rows. 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 SQLVIEW SQLUNIONALL SQLPREDPUSHDOWN SQLSPECIALREG SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71335 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 1 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXODSO PM71335 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71335 DSNXODSO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXODSO LISTEND UK82678 COVER LETTER END UK82706 COVER LETTER START PROBLEM DESCRIPTION(S): PM68109 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of ALTER FUNCTION DROP * * VERSION * **************************************************************** * PROBLEM DESCRIPTION: User receives SQLCODE -204 on ALTER * * FUNCTION DROP VERSION. * **************************************************************** * RECOMMENDATION: * **************************************************************** Users may incorrectly receive SQLCODE204 while DB2 tries to drop the corresponding package on ALTER FUNCTION DROP VERSION of an SQL scalar function and the SPECIFIC name specified on the CREATE FUNCTION is different from the function name. Other symptoms of the ALTER FUNCTION DROP VERSION may include incorrectly dropping the wrong package due to package naming resolution with the function's SPECIFIC name. For example, with the following steps: (1) Function 1 has two versions. Schema: SCH1 Name: DUMMYFUNC1 Specific name: DummyFunc2 (2) Function 2 has two versions. Schema: SCH1 1 Name: DUMMYFUNC2 Specific name: DummyFunc1 (3) ALTER FUNCTION SCH1.DUMMYFUNC1 DROP VERSION V2 would result in dropping the package from Function 2. Subsequent symptoms from these missing packages may also include SQLCODE601 for CREATE FUNCTION or SQLCODE204 on DROP FUNCTION. DB2 has been fixed to find and drop the correct packages. ++HOLD, TYPE ACT: 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 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. Additional Keywords: SQLALTER SQLFUNCTION SQLSCALARUDF COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68109 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 1 ( SELECT * FROM SYSIBM.SYSPACKAGE P 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 DSNXIANR PM68109 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68109 DSNXIANR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIANR LISTEND UK82706 COVER LETTER END UK82714 COVER LETTER START PROBLEM DESCRIPTION(S): PM69183 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * with queries containing many predicates * * and/or referencing many columns. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may loop during prepare of a query * * if that query contains more than 32767 * * predicates or references more than * * 32767 columns. * **************************************************************** * RECOMMENDATION: * **************************************************************** During prepare of a query, DB2 uses arrays to represent each predicate in the query and each column referenced by the query. In some cases, access to these arrays was via half-word counters which will overflow at 32767 and become negative. Depending on the contents of the storage that happens to be referenced by the incorrect negative counter, this could cause DB2 to enter a loop. Additional Keywords: SQLLOOP INFINITE ENDLESS LOOPING DSNXOCN DSNXOGA DSNXOGP DSNXOOFP DSNXOPCO DSNXOPG3 DSNXOSF DB2 has been changed to use full-word counters to avoid the overflow and the resulting looping. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69183 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM61426: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM61426 corrects a problem in which frequency and histogram statistics will not be used for expressions when in conversion mode from DB2 9 (CM9). When index on expressions are used, this may lead to inefficient access path choices and poor query performance. 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 PM42686: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM42686 corrects a problem in which an incorrect filter factor may be selected for a predicate on a column with a COLCARDF of 1 or 2. The incorrect filter factor may result in a poor performing 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 DSNXOCN PM69183 DSNXOGA PM69183 DSNXOGP PM69183 DSNXOOFP PM69183 DSNXOPCO PM69183 DSNXOPG3 PM69183 DSNXOSF PM69183 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69183 DSNXOCN DSNXOGA DSNXOGP DSNXOOFP DSNXOPCO DSNXOPG3 DSNXOSF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCN DSNXOGA DSNXOGP DSNXOOFP DSNXOPCO DSNXOPG3 1 DSNXOSF LISTEND UK82714 COVER LETTER END UK82733 COVER LETTER START PROBLEM DESCRIPTION(S): PM72910 - **************************************************************** * USERS AFFECTED: DB2 data sharing users, with table spaces or * * indexes with DSSIZE or PIECESIZE greater * * than 64GB. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2000F in DSNSVSFB, called * * by DSNB5PCO. * **************************************************************** * RECOMMENDATION: * **************************************************************** For table spaces or indexes whose data set size allows page numbers greater than 3 bytes long (4K page size and data set size greater than 64GB, or 8K page size and data set size greater than 128GB), there is a possibility that a castout page list sent in a notify message may be truncated in a way which will cause the storage block trailer to become corrupted when the page list is sorted. This results in an ABEND04E RC00E2000F in DSNSVSFB when the list is freed. The code which sends castout page lists in notify messages has been modified to ensure that the list length is correct for objects with large DSSIZE or PIECESIZE values. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72910 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1PCO PM72910 DSNB5PCI PM72910 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72910 DSNB1PCO DSNB5PCI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1PCO DSNB5PCI LISTEND UK82733 COVER LETTER END UK82752 COVER LETTER START PROBLEM DESCRIPTION(S): PM73076 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS users and * * All DB2 10 for z/OS users * * who ALTER ADD COLUMN to table and index * * in the same commit scope. * **************************************************************** * PROBLEM DESCRIPTION: ALTER ADD COLUMN CHAR(1) WITH DEFAULT * * caused ABEND04E RC00C90101 DSNKIXDB * * ERQUAL5042 * **************************************************************** * RECOMMENDATION: * **************************************************************** ALTER ADD COLUMN CHAR(1) WITH DEFAULT to table and index under same commit scope caused ABEND04E RC00C90101 DSNKIXDB ERQUAL5042 and possibly add index pages to the Logical Page List (LPL). An unexpected default length was detected and caused abend. Additional Keywords: SQLALTER DB2 has been modified to validate DEFAULT length. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73076 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKIXDB PM73076 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73076 DSNKIXDB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKIXDB LISTEND UK82752 COVER LETTER END UK82764 COVER LETTER START PROBLEM DESCRIPTION(S): PM69141 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: Provide support for DB2 to issue an * * automatic refresh of a WLM environment * * if z/RRS is stopped and started but DB2 * * is not stopped. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 has been updated to support an automatic refresh of the WLM 1 application environment for WLM established stored procedures address space which are active. The automatic refresh will be issued if z/OS RRS is stopped and started while DB2 is continuously active (i.e. DB2 was not restarted while RRS was inactive). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69141 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: To use this new function to automatically issue a V WLM,APPLENV=applenvname,REFRESH when z/OS RRS is recycled, you must: . Add a //AUTOREFR DD DUMMY to the WLM established stored procedure startup proc that you require to be automatically refreshed. Note that the V WLM command has a Sysplex scope, so it will refresh the same WLM application environment on other MVS machines. . If a security product is configured to authorize MVS console commands, you must grant authorization for the DB2 ssnmMSTR address space to issue a MVS command. . The DB2 Administration Guide has been updated with the following information: . Refreshing WLM environments for stored procedures automatically . You can enable automatic refreshes for WLM environments for stored procedures. . Procedure . To enable automatic refreshes of WLM environments for stored procedures: Add the following DD statement to the startup procedure for the WLM established stored procedure address space: //AUTOREFR DD DUMMY DB2 saves the environment name in a list of environments to refresh automatically. If the z/OS Resource Recovery Services environment is recycled, but DB2 and its associated WLM established stored procedures address spaces are not restarted, DB2 issues the following z/OS command to refresh each environment that is named in the list: VARY WLM,APPLENV=environment-name,REFRESH . Recommendation: To prevent the automatic issuing of duplicate and unnecessary VARY WLM,APPLENV=applenvname commands, limit the number of startup procedures that contain the //AUTOREFR DD statement. The WLM,APPLENV=applenvname command has a Sysplex scope, which means that it affects all servers of an application environment on all systems in the Sysplex. The result is that every DB2 subsystem issues its own 1 WLM,APPLENV=applenvname command for each application environment that is nominated by the //AUTOREFR DD statement in its startup procedure. . Before you begin . If a security product is configured to authorize MVS console commands, you must grant authorization for the DB2 ssnmMSTR address space to issue MVS commands. ACTION: A new option to be specified on the parameter to DSNX9WLM on the WLM startup JCL is introduced so user can specify a minimum number of address spaces to be kept for that particular environment. If this parameter is not specified, existing behavior prior to this change applies and WLM controls how many WLM-SPAS to keep. This new option will be implemented as new parameter to DSNX9WLM to the WLM start up JCL. For example: //DSN8WLMP PROC DB2SSN=DSN,NUMTCB=5,APPLENV=WLMTPSMP,MNSPAS=3 ... //WLMTPSMP EXEC PGM=DSNX9WLM,TIME=1440, // PARM='&DB2SSN,&NUMTCB,&APPLENV,&MNSPAS', // REGION=0M In the above example, a minimum of 3 WLM-SPAS will be started each with NUMTCB = 5. WLM will start the minimum number of address spaces on the first stored procedure request on that WLM environment. The valid number specified for the values of MNSPAS is between 0 to 50. A value of 0 means no minimum is specified and old behavior will apply. If the value of MNSPAS is invalid, message DSNX981E will be issued. If the new parameter is not specified, there will be no impact to the existing user base. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNARA00 PM69141 DSNX9WLM PM69141 DSN3AUWL PM69141 DSN3ID30 PM69141 DSN3RRRS PM69141 DSN3RRSI PM69141 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69141 DSNARA00 DSNX9WLM DSN3AUWL DSN3ID30 DSN3RRRS DSN3RRSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNARA00 DSNX9WLM DSN3AUWL DSN3ID30 1 DSN3RRRS DSN3RRSI LISTEND UK82764 COVER LETTER END UK82765 COVER LETTER START PROBLEM DESCRIPTION(S): PM70719 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS with queries * * containing GROUP BY and/or ORDER BY * * with IN-lists and IN-subqueries * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output can occur for a * * query containing IN-lists and * * IN-subqueries with GROUP BY or * * ORDER BY when 'IN' access is chosen * * (ACCESSTYPE='IN' in the PLAN_TABLE) * * and a sort for GROUP BY/ORDER BY is * * avoided. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output can occur for a query containing IN-lists and IN-subqueries with GROUP BY or ORDER BY when 'IN' access is chosen (ACCESSTYPE='IN' in the PLAN_TABLE) and a sort for GROUP BY/ORDER BY is avoided. Rows are returned in the wrong order. Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLGROUPBY SQLORDERBY SQLIN INLIST SQLINSUBQ IN-LIST DIRECT TABLE ACCESS Code is changed to add the sort for GROUP BY and/or ORDER BY when required in the case described above to ensure the correct output. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70719 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM70719 APAR/PTF text for additional information about why a REBIND is necessary. PM70719 corrects a problem of possible incorrect output for a query containing IN-lists and IN-subqueries with GROUP BY or ORDER BY. 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 ***Action for PM67984: See PM67984 APAR/PTF text for additional information about why a REBIND is necessary. PM67984 corrects a problem of incorrectly ordered output from a query with an order by, group by and 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: ***Action for PM66684: See PM66684 APAR/PTF text for additional information about why a REBIND is necessary. PM66684 corrects a problem of possible incorrect output for a query using Omnifind and ORDER BY, GROUP BY, RANK, DENSE_RANK, or ROW_NUMBER. 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 PM60664: See PM60664 APAR/PTF text for additional information about why a REBIND is necessary. PM60664 corrects a problem of ABEND0C4 RC38 in DSNXRSGB+0AFC on a query with GROUP BY in a subquery when the first join in the subquery is hybrid join without sort new and the sort for GROUP BY is avoided. 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 PM54468: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM54468 corrects a problem in which an unnecessary sort was added for a query containing both ORDER BY and GROUP BY when IN list table access was chosen (ACCESSTYPE='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: 1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOGBM PM70719 DSNXOTS1 PM70719 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70719 DSNXOGBM DSNXOTS1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOGBM DSNXOTS1 LISTEND UK82765 COVER LETTER END UK82781 COVER LETTER START PROBLEM DESCRIPTION(S): PM70561 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of a * * scalar subselect that contains the COUNT * * aggregate function. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output may be returned for * * the COUNT aggregate function when it is * * used in a scalar subselect. * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQL statement that contains the COUNT function in a scalar subselect may return incorrect output. The problem occurs if the scalar subselect result set is the empty set. The COUNT function should return the value 0 instead of the null value for the empty set. Following is an example of the problem : CREATE TABLE T1 (T1C1 INT); CREATE TABLE T2 (T2C1 INT); CREATE TABLE T3 (T3C1 INT); INSERT INTO T1 VALUES (1); INSERT INTO T1 VALUES (NULL); INSERT INTO T2 VALUES (1); INSERT INTO T3 VALUES (1); SELECT TAB2.T2C1, TAB1.T1C1 , ( SELECT COUNT (*) FROM T3 TAB3 WHERE TAB3.T3C1 = TAB1.T1C1 ) AS T3_COUNT FROM T2 AS TAB2, T1 AS TAB1; The null value for T3_COUNT is incorrect. The value should be 0. +--------------------------------------------------+ | T2C1 | T1C1 | T3_COUNT | 1 +--------------------------------------------------+ 1_| 1 | 1 | 1 | 2_| 1 | ? | ? | ---> 0 +--------------------------------------------------+ DB2 has been changed to process the aggregrate functions for the scalar subselect when the result set is empty. Additional keywords : SQLCOUNT SQLSUBQUERY DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70561 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXREMC PM70561 DSNXREMS PM70561 DSNXREM9 PM70561 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70561 DSNXREMC DSNXREMS DSNXREM9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXREMC DSNXREMS DSNXREM9 LISTEND UK82781 COVER LETTER END UK82787 COVER LETTER START PROBLEM DESCRIPTION(S): PM56429 - **************************************************************** * USERS AFFECTED: All DB2 V9 and V10 for z/OS users of * * Universal Table space or a single * * table in a segmented table space. * **************************************************************** * PROBLEM DESCRIPTION: Unexpected space growth and results * * in SQLCODE904 with reason code C9009C. * **************************************************************** * RECOMMENDATION: * **************************************************************** During the exhaustive space search of a Universal Table space or a case where a single segmented table exists with page level locking, the locking failure threshold applies to the entire exhaustive search algorithm. Therefore, if a large number 1 of data pages locking failures occur, then it is possible that the locking failure threshold would reach its limit before the entire space map pages have been searched. As a result, the exhaustive search step is ended and DB2 will attempt to extend the physical space and cause growth of table space. This growth of the table space can cause a SQL -904 with RC00C9009C to be issued prematurely. code 00C9009C was issued prematurely. DB2 space search algorithm is modified to allow locking failure threshold applies to each space map page instead of the entire algorithm during the exhaustive search before issuing SQL -904 with reason code 00C9009C message. This change affects all the type of UTS table space and segmented table space has single table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM56429 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 PM56429 DSNISGRT PM56429 DSNISGSC PM56429 DSNISUPI PM56429 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM56429 DSNISGNS DSNISGRT DSNISGSC DSNISUPI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGNS DSNISGRT DSNISGSC DSNISUPI LISTEND UK82787 COVER LETTER END UK82797 COVER LETTER START PROBLEM DESCRIPTION(S): PM71859 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS users * * going through package autobind (or bind or * * free) while that same package is running * * concurrently * **************************************************************** * PROBLEM DESCRIPTION: With APAR PM51083/PM54671 applied * * (V10 PTF UK77633 / V9 PTF UK77635), * * MSGDSNT375I deadlock or MSGDSNT376I * * timeout for CORRELATION-ID of * * 020.AUTBNDxx accompanied by MSGDSNT501I * * with RC00C90088 or RC00C9008E with * 1 * resource name DSNDB01.SPT01 during * * autobind of a package while that same * * package was running concurrently * **************************************************************** * RECOMMENDATION: * **************************************************************** After a DB2 object was altered or drop/re-created, packages which reference the object were invalidated. Executing these packages triggered automatic rebind (autobind). With APAR PM51083/PM54671 applied (V10 PTF UK77633 / V9 PTF UK77635), the autobind process on such package failed to release a DSNDB01.SPT01 page/row S-lock after reading the package from DASD, and if another thread was running the same package concurrently, deadlock or timeout on said S-lock occurred. The deadlock/timeout is also possible on bind or free of a package instead of autobind. DB2 has been changed to make sure the DSNDB01.SPT01 page/row S-lock is released after reading the package from DASD, which fixes the deadlock and timeout problems. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71859 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 PM71859 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71859 DSNGEFLC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGEFLC LISTEND UK82797 COVER LETTER END UK82799 COVER LETTER START PROBLEM DESCRIPTION(S): PM69433 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of DB2 Web * * Services Consumer functions. * **************************************************************** * PROBLEM DESCRIPTION: The length of the ENDPOINT_URL and * * SOAP_ACTION parameters for the * * DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC * * Web Services Consumer Functions is too * * short. * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** The length of the ENDPOINT_URL and SOAP_ACTION parameters for the DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC Web Services Consumer Functions is too short. Currently the datatype for ENDPOINT_URL and SOAP_ACTION parameters is VARCHAR(256). There are cases that the ENDPOINT_URL or SOAP_ACTION is longer then 256 characters. The datatype of the ENDPOINT_URL and SOAP_ACTION parameters for the DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC Web Services Consumer functions has been changed to VARCHAR(4096). These parameters remain as VARCHAR(256) for the DB2XML.SOAPHTTPC and DB2XML.SOAPHTTPV functions. It is not required to drop and recreate the DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC functions unless you want to specify ENDPOINT_URL and SOAP_ACTION settings of more than 256 single-byte characters. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69433 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: See PM69433 APAR/PTF text in the PTF cover letter for additional information about this APAR. This APAR changed the datatype for ENDPOINT_URL and SOAP_ACTION parameters for the DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC Web Services Consumer functions to VARCHAR(4096). For the DB2XML.SOAPHTTPC and DB2XML.SOAPHTTPV functions, these parameters remain as VARCHAR(256). To make the fix effective, the DB2 Web Services consumer functions need to be dropped and recreated. It is not required to drop and recreate these functions unless you want to specify ENDPOINT_URL and SOAP_ACTION settings of more than 256 single-byte characters. However, the WLM environment needs to be refreshed. In datasharing environment, the PTF needs to be applied to all members before the dropping and recreating of the UDFs. To recreate the functions, proceed as follows: (1) Drop the DB2 Web Services/SOAP routines DROP SPECIFIC FUNCTION DB2XML.SOAPHTTPNCICO RESTRICT; DROP SPECIFIC FUNCTION DB2XML.SOAPHTTPNCIVO RESTRICT; DROP SPECIFIC FUNCTION DB2XML.SOAPHTTPNVICO RESTRICT; DROP SPECIFIC FUNCTION DB2XML.SOAPHTTPNVIVO RESTRICT; (2) Run your customized copy of job DSNTIJRT with MODE(INSTALL) to recreate the DB2 Web Services/SOAP routines. Note: If you have previously run DSNTIJRT, rerunning with 1 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. All customers who use DB2 Web Services/SOAP functions need to refresh the WLM environment for running these functions after applying this PTF. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@RIN PM69433 DSNTESR PM69433 DSNTRIN PM69433 DSNWSCCC PM69433 DSNWSCCV PM69433 DSNWSCVC PM69433 DSNWSCVV PM69433 DSNWSHLP PM69433 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69433 DSN@RIN DSNTESR DSNTRIN DSNWSCCC DSNWSCCV DSNWSCVC DSNWSCVV DSNWSHLP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTRIN DSNWSCCC DSNWSCCV DSNWSCVC DSNWSCVV DSNWSHLP MACROS DSN@RIN DSNTESR LISTEND UK82799 COVER LETTER END UK82805 COVER LETTER START PROBLEM DESCRIPTION(S): PM69619 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users * * of PBR(partitioned by range) tablespace * * and bind option REOPT(ALWAYS) or * * REOPT(VARS). * **************************************************************** 1 * PROBLEM DESCRIPTION: Incorrect output may happen for * * a static SQL statement that * * satisfies all of the 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output may happen for a static SQL statement that satisfies all of the 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. An example is shown below: CREATE TABLE TBL1 ( INTCOL INT, L_VARCHAR VARCHAR(10), L_VARBIN VARBINARY(100), L_COMMENT VARCHAR(44) NOT NULL) PARTITION BY RANGE(L_VARCHAR ASC, L_COMMENT) (PARTITION 1 ENDING AT ('AIR', 'ep quickly') INCLUSIVE, PARTITION 2 ENDING AT ('AIR', 'long') INCLUSIVE, PARTITION 3 ENDING AT ('AIR', 'theodolites') INCLUSIVE, PARTITION 4 ENDING AT ('AIR', 'ZZZZZZ') INCLUSIVE, PARTITION 5 ENDING AT ('CAR', 'ep quickly') INCLUSIVE, PARTITION 6 ENDING AT ('CAR', 'long') INCLUSIVE, PARTITION 7 ENDING AT ('CAR', 'theodolites') INCLUSIVE, PARTITION 8 ENDING AT ('CAR', 'ZZZZZZ') INCLUSIVE ); SELECT L_VARCHAR FROM TBL1 WHERE L_VARCHAR = :hostvar; DB2 did not correctly process the aforementioned SQL statements, which caused incorrect output. DB2 has been modified to correctly process the aforementioned SQL statements,so there will be no incorrect output. Additional keywords:SQLINCORR INCORROUT SQLINCORROUT SQLHOSTVAR SQLREOPTALWAYS DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69619 1 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 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 PM69619 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69619 DSNXORHV THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXORHV LISTEND UK82805 COVER LETTER END UK82853 COVER LETTER START PROBLEM DESCRIPTION(S): PM71479 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users with applications * * bound with Release=DeAllocation option and * * their tables involve with RI (Referential * * Integrity) relationship. * **************************************************************** * PROBLEM DESCRIPTION: RI checking caused DDL on other tables * * to be timed out. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 does its RI checking, it acquired a DBD lock based on how this application was bound. If it's bound with Release = DeAllocation option, the lock will be acquired with deallocation duration. This could cause DDL on other tables to be timed out. 1 For RI checking purpose, DB2 changed to acquire the DBD lock in commit duration, so it can be released at commit and DDL can break in after the application commits. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71479 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRELD PM71479 DSNIRELI PM71479 DSNIRELU PM71479 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71479 DSNIRELD DSNIRELI DSNIRELU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRELD DSNIRELI DSNIRELU LISTEND UK82853 COVER LETTER END UK82889 COVER LETTER START PROBLEM DESCRIPTION(S): PM74403 - **************************************************************** * USERS AFFECTED: All HIR2220(IRLM220) and HIR2230(IRLM230) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABENDU2025 in DXRRL2S0 after IMS member * * was quiesced. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** ABENDu2025 was issued from DXRRL2S0 when IRLM was processing its QUIT request response received from a peer IRLM member. The peer IRLM member incorrectly set a bad return code indicating error during retain lock processing. Upon receiving this error during global quit processing IRLM issued ABENDu2025 in DXRRL2S0. This abend is issued only in the case where IRLM was started with SCOPE=NODISCON option in the IRLM startup proc. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR correctly initializes the storage in IRLM before sending the QUIT request response to a peer member and will prevent ABENDu2025 in DXRRL2S0 on the member which issued QUIT. COMPONENT: 5695-16401-HIR2230 1 APARS FIXED: PM74403 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL221 PM74403 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74403 DXRRL221 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL221 LISTEND UK82889 COVER LETTER END UK82964 COVER LETTER START PROBLEM DESCRIPTION(S): PM74279 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * scalar fullselect with AGGREGATE function. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C7 at DSNXGRDS.DSNXRSBC+8086 * * or incorrect output could occur for an * * SQL statement that satisfies the * * following conditions: * * 1. contains a scalar fullselect, * * 2. the scalar fullselect contains an * * aggregate function in the select * * list and it involves invalid * * syntax. SQLCODE -122 is expected * * for this case, but no error message * * is issued and the query completes * * successfully or abends. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C7 at DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur for an SQL statement that satisfies the following conditions: 1. contains a scalar fullselect, 2. the scalar fullselect contains an aggregate function in the select list and it involves invalid syntax. SQLCODE -122 is expected for this case, but no error message is issued and the query completes successfully or abends. The following example could recreate the abend: SET :H=(SELECT CX FROM (SELECT C1, SUM(C1) FROM TT) AS TX(CX,CY)); 1 The following example could recreate incorrout: CREATE TABLE TT(C1 INTEGER); INSERT INTO TT VALUES(100); INSERT INTO TT VALUES(200); CREATE FUNCTION UDF13635() RETURNS INTEGER VERSION V1 VALIDATE BIND ASUTIME LIMIT 5000 NO EXTERNAL ACTION RETURN(SELECT CX+CY FROM (SELECT C1, SUM(C1) FROM TT) AS TX(CX,CY)); SELECT UDF13635() FROM SYSIBM.SYSDUMMY1; DB2 doesn't handle the scalar fullselect with AGGREGATE function correctly which cause the above abend and incorrout. DB2 is updated to handle the scalar fullselect with aggregate function correctly. Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLSCALAR SQLFULLSELECT SQLSCALARFULSEL SQLCODE122 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74279 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM74279: See PM74279 APAR/PTF text for additional information about why a REBIND is necessary. PM74279 corrects a problem of ABEND0C7 at DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur for an SQL statement that satisfies the following conditions: 1. contains a scalar fullselect, 2. the scalar fullselect contains an aggregate function in the select list, it involves invalid syntax. SQLCODE -122 is expected for this case. 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 PM74279: TYPE: ACT PM74279 corrects a problem of ABEND0C7 at DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur for an SQL statement that satisfies the following conditions: 1. contains a scalar fullselect, 2. the scalar fullselect contains an aggregate function in the select list and it involves invalid syntax. SQLCODE -122 is expected for this case, but no error message is issued 1 and the query completes successfully or abends. After the application of this PTF, ALTER PROCEDURE REGENERATE, ALTER FUNCTION REGENERATE is required for each native SQL procedure or SQL scalar function that contains a scalar fullselect statement described as above. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOASG PM74279 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74279 DSNXOASG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOASG LISTEND UK82964 COVER LETTER END UK82977 COVER LETTER START PROBLEM DESCRIPTION(S): PM71952 - **************************************************************** * USERS AFFECTED: All DB2 users of dynamic SQL bound with * * REOPT(VARS | ALWAYS) * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E20003 in DSNSVBK occurred * * for a long-running DB2 connection / * * thread that repeatedly invoked many * * times a DB2 package that was bound * * REOPT(VARS|ALWAYS) RELEASE(COMMIT) and * * executed non-cached dynamic SQL * * statements followed by a COMMIT. * * Prior to the abend occurring, large * * consumption of DB2 below-the-bar * * storage can be observed with storage * * monitors. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00E20003 in DSNSVBK occurred for DB2 out-of-storage condition for the DB2 thread's ADMF AGL storage pool. The DB2 connection/thread was long-running and repeatedly invoked many times a DB2 package that was bound REOPT ( VARS | ALWAYS ) RELEASE ( COMMIT ) and executed non-cached dynamic SQL followed by COMMIT. The bind option REOPT values VARS and ALWAYS are synonyms. Prior to the abend, large consumption of DB2 below- the-bar ( BTB ) storage may be observed via storage monitors. Dynamic SQL in a package bound REOPT(VARS|ALWAYS) are not cached in the DB2 Dynamic Statement Cache (DSC), so this storage growth is not related to the DB2 DSC. . A review of the formatted DB2 thread's ADMF AGL storage pool in 1 the DB2 dump showed many dynamic SQL statement text strings allocated by DB2 csect DSNXERT . In this scenario, the excessive storage growth is attributed to copies of the SQL statement text strings (needed for REOPT (VARS|ALWAYS) processing of dyn SQL) temporarily kept in the DB2 thread's AGL storage pool but not being freed at COMMIT when the dyn SQL statement's associated DB2 package was freed (RELEASE(COMMIT) and no OPEN+HOLD statements at COMMIT). Even after the package was freed, the associated REOPT(VARS|ALWAYS) dyn SQL text storage remained allocated in the DB2 thread's AGL storage pool. This process was repeated each time the DB2 package was re-invoked after the COMMIT on this DB2 thread/connection, thus resulting in the DB2 out-of-storage condition for the BTB storage pool. . This storage growth under REOPT(VARS|ALWAYS) only occurs for dynamic SQL statements, not for static SQL in that package. The storage growth can also occur if ROLLBACK is used instead of COMMIT in this scenario. For dynamic SQL queries, the storage growth happens when the query cursor is CLOSEd by application or implicitly closed by DB2 'before' the COMMIT or ROLLBACK. For non-query dynamic SQL stmts, simply repeatedly running the sequence of executing the statement followed by a COMMIT or ROLLBACK can expose the problem. . The storage eventually is freed when the DB2 connection / thread is terminated. However, prior to that DB2 thread termination, the storage growth can occur resulting in the DB2 storage shortage. . DB2 COMMIT and ROLLBACK processing was changed to free REOPT(VARS|ALWAYS) dynamic SQL statement text storage when the associated DB2 package is freed. In addition, DB2 NEWUSER / thread-reuse processing was also modified to free the REOPT(VARS|ALWAYS) dynamic SQL text storage. . Additional search keywords: DB2STGLK/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71952 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXECW PM71952 DSNXECWA PM71952 DSNXECWU PM71952 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71952 DSNXECW DSNXECWA DSNXECWU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECW DSNXECWA 1 DSNXECWU LISTEND UK82977 COVER LETTER END UK83061 COVER LETTER START PROBLEM DESCRIPTION(S): PM71866 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS (CM and above) users of * * non-segmented table spaces (simple table * * spaces or classic-partitioned table spaces) * **************************************************************** * PROBLEM DESCRIPTION: Non-segmented table space may grow * * rapidly due to insert failing to reuse * * deleted space * **************************************************************** * RECOMMENDATION: * **************************************************************** In DB2 10, for non-segmented table spaces, the first SQL DELETE against a full page mistakenly skip to update the space map page. According to the non-updated space map page, the data page still remain full incorrectly. As a result, a subsequent insert looked for space in a different page, resulting in unnecessary growth to the table space. If after the first SQL DELETE against a full page came another SQL DELETE, depending on the space situation on the page, the second SQL DELETE may or may not drive update of the space map page. Therefore, the problem of 'unupdated' space map page could continue even through several SQL DELETEs. The problem is more likely to happen in table spaces that have a lower MAXROWS value and small row sizes. DB2 code has been modified to make sure that the first SQL DELETE against a full page properly updates the space map page so that a subsequent insert can reuse the deleted space. Additional keywords: SQLDELETE SQLINSERT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71866 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDILS PM71866 DSNIDLEO PM71866 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71866 DSNIDILS DSNIDLEO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNIDILS DSNIDLEO LISTEND UK83061 COVER LETTER END UK83088 COVER LETTER START PROBLEM DESCRIPTION(S): PM70908 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DECIMAL * * function with character input that have * * PTF UK79144 applied. * **************************************************************** * PROBLEM DESCRIPTION: After the application of PTF UK79144, * * SQLCODE420 may be incorrectly returned * * for an SQL statement using the DECIMAL * * function with character input. * * Incorrect output is another possible * * symptom. * **************************************************************** * RECOMMENDATION: * **************************************************************** An SQL statement containing the DECIMAL built-in function can return incorrect output if all of the following conditions are true: 1. the input expression is character 2. the input expression contains a decimal character 3. the decimal character is a comma 4. the input expression is referenced elsewhere in the SQL statment. DB2 incorrectly modifies the input expression and replaces the comma with a period. SQLCODE -420 or incorrect output may occur if the input expression is used again in the SQL statement. The problem can also occur for the syntax CAST(string AS DECIMAL). Some examples of the problem follow: CREATE TABLE T1 (C1 CHAR(3) NOT NULL); INSERT INTO T1 VALUES ('1,1'); SELECT C1 FROM T1 WHERE DECIMAL(C1) > 0 ; The value '1.1' is incorrectly returned for C1 instead of '1,1' for this SQL statement. SELECT C1 FROM T1 WHERE DECIMAL(C1) > 0 1 AND DECIMAL(C1, 1, 0, ',') > 0 ; SQLCODE -420 is incorrectly returned for this SQL statement because DB2 modifies the input value for C1 and the second invocation of the DECIMAL function fails. DB2 code has been changed to use a temporary buffer for the input expression before modifying the decimal character so that other references to the expression are not affected. Additional keywords : SQLDECIMAL SQLCAST DB2INCORR/K SQLINCORR SQLINCORROUT INCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70908 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDEC PM70908 DSNXRGPL PM70908 DSNXRIHB PM70908 DSNXRIHD PM70908 DSNXRIHR PM70908 DSNXRIHS PM70908 DSNXROHB PM70908 DSNXROHR PM70908 DSNXROHS PM70908 DSNXROH2 PM70908 DSNXRSPG PM70908 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70908 DSNXRDEC DSNXRGPL DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXROHB DSNXROHR DSNXROHS DSNXROH2 DSNXRSPG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDEC DSNXRGPL DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXROHB DSNXROHR DSNXROHS DSNXROH2 DSNXRSPG LISTEND UK83088 COVER LETTER END UK83093 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM71949 - **************************************************************** * USERS AFFECTED: All users of Native SQL procedures bound in * * DB2 9 and executed in DB2 10. * **************************************************************** * PROBLEM DESCRIPTION: Overlay may occur if allocated storage * * is exceeded when converting SQL * * statement to be prepared to UTF-8. * * The following abend may occur: * * ABEND04E RC00E20005 LOC= DSNXESP9 * * LOC= DSNXESP9 DSNSVBK +1AB6. * **************************************************************** * RECOMMENDATION: * **************************************************************** During a PREPARE within a native SQL procedure, the SQL text was converted to UTF-8 from its original EBCDIC format. The expansion of characters, due to an in-place conversion, exceeded the storage allocated. This can introduce a storage overlay if the allocated storage is exceeded. Performing an ALTER REGENERATE of the DB2 9 native SQL procedure on the DB2 10 system can mitigate this problem. DB2 was changed to allocate three times the usual storage amount to accomodate the possible expansion of SQL text characters from in-place EBCDIC conversion to UTF-8. Additional keywords: SQLNATIVESQLPL SQLSP SQLSTOREDPROC SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71949 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 PM71949 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71949 DSNXESP9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXESP9 LISTEND UK83093 COVER LETTER END UK83110 COVER LETTER START PROBLEM DESCRIPTION(S): PM70217 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of Partition by Growth (PBG) Universal Table * * Spaces * **************************************************************** 1 * PROBLEM DESCRIPTION: MSGDSNT501I RC00C200EA with MSGDSNI005I * * RC00C200EA - GRECP recovery process on * * index pageset DSNDB01.DSNDB01X fails * * because of inability to obtain a drain * * on it * **************************************************************** * RECOMMENDATION: * **************************************************************** During restart, indoubt thread resolution that involved a PBG user object internally obtained a claim on index pageset DSNDB01.DSNDB01X, specifically as part of internal DBET processing for this PBG user object. Later on during restart, DSNDB01.DSNDB01X went into group buffer pool recovery pending state (GRECP). However, any automatic or explicit attempts to recover DSNDB01.DSNDB01X from GRECP failed because the claim obtained earlier by the indoubt thread resolution processing was never released. In fact, the claim would never get released for the life of DB2 being up. This meant that any process that needed a drain on DSNDB01.DSNDB01X would fail to get it. Internal DBET processing during restart also left a claim on DSNDB01.DBD01 unreleased, but it was not a significant issue in the reported scenario because DSNDB01.DBD01 did not enter GRECP and therefore it did not have to be recovered. Until this fix is available, a restart of DB2 would release the claim, after which the GRECP object DSNDB01.DSNDB01X can be recovered. In DB2 9, index DSNDB01.DSNDB01X does not exist, so the issue is limited to DSNDB01.DBD01 (if DSNDB01.DBD01 were to enter GRECP). DB2 has been modified to limit the access to DBD during restart so as to avoid acquiring a claim on the DBD and its indexes. Additional keywords: SQLPBG COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70217 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 PM70217 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70217 DSNIDBGA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBGA LISTEND 1UK83110 COVER LETTER END UK83114 COVER LETTER START PROBLEM DESCRIPTION(S): PM64376 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 10 for z/OS only. * **************************************************************** * PROBLEM DESCRIPTION: Various 04E-00E2000C abends may occur. * * Symptoms include: * * o 04E-00E2000C,DSNLTACC.DSNSVSVB+0AC2 * * o 04E-00E2000C,DSNLILNR.DSNSVSVB+0AC2 * * This condition will result in the * * abnormal termination of DDF. * * o 04E-00E2000C,DSNLIRTR.DSNSVSVB+0AC2 * **************************************************************** * RECOMMENDATION: * **************************************************************** When remote client applications connect to a DB2 10 for z/OS server via TCP/IP, new System Profile Monitoring (SPM) support in DB2 10 for z/OS monitors events related to the different remote client applications that access DB2, even if SPM is not enabled. If the behavior or processing of the remote applications are such that unique (monitored) values are always encountered, storage (SPME control blocks) utilization accumulates over time which can eventually lead to 04E-00E2000C abend conditions. The entire DB2 subsystem must be stopped and restarted to relieve the storage condition. The unique SPM (monitored) values that are typically observed include: o End Client UserID. o End Client Application Name. o End Client Workstation Name. o Collection ID. o Package name. DB2 10 for z/OS server processing has been changed to reuse the available DB2 (SPME) control blocks when they no longer reflect active usage. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64376 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 PM64376 DSNLCTRC PM64376 DSNLEDDA PM64376 DSNLILNR PM64376 DSNLIRTR PM64376 DSNLQDIS PM64376 DSNLQINA PM64376 1 DSNLSSST PM64376 DSNLTACC PM64376 DSNLTACT PM64376 DSNLTEXC PM64376 DSNTSTRT PM64376 DSNT1MST PM64376 DSNT1RSP PM64376 DSNWVZCK PM64376 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64376 DSNLAGNT DSNLCTRC DSNLEDDA DSNLILNR DSNLIRTR DSNLQDIS DSNLQINA DSNLSSST DSNLTACC DSNLTACT DSNLTEXC DSNTSTRT DSNT1MST DSNT1RSP DSNWVZCK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLAGNT DSNLCTRC DSNLEDDA DSNLILNR DSNLIRTR DSNLQDIS DSNLQINA DSNLSSST DSNLTACC DSNLTACT DSNLTEXC DSNTSTRT DSNT1MST DSNT1RSP DSNWVZCK LISTEND UK83114 COVER LETTER END UK83168 COVER LETTER START PROBLEM DESCRIPTION(S): PM70046 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS using the * * subsystem parameter (ZPARM) OPTIOWGT * * and/or using OPTIOWGT in the * * DSN_PROFILE_ATTRIBUTES table. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * Performance regression after * * migration to V10 when * * subsystem parameter OPTIOWGT * * is set to DISABLE * * * * PROBLEM SCENARIO: * * * 1 * The reported performance issue occurred * * after several users migrated to V10 * * from V8 of DB2. The subsystem parameter * * OPTIOWGT was left disabled causing * * performance regression. Since the * * documentation has this parameter as * * deprecated, it was thought that it * * no longer was used or effective. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: Even though the subsystem parameter OPTIOWGT was deprecated in the documentation for V10, the parameter still allows DISABLE/ENABLE to be set. Both values have effect on the I/O weighting used in the calculation of the best access path. By leaving it disabled, there will be a degradation of performance. PROBLEM CONCLUSION: DB2 has changed the subsystem parameter OPTIOWGT DISABLE value to equal ENABLE thereby preventing future performance problems. In addition and for consistency, the DSN_PROFILE_ATTRIBUTES table values for OPTIOWGT have also changed where DISABLE is the same as ENABLE. ADDITIONAL KEYWORDS: SQLPERFORMANCE OPTIOWGT SQLMIGRATION COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70046 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: This PTF modifies DSN6SPRM.OPTIOWGT, a DB2 subsystem parameter that specifies how the DB2 optimizer should balance I/O cost and CPU cost estimation when selecting an access path. OPTIOWGT is deprecated in DB2 10, meaning that it is still supported but will be eliminated in a future release of DB2. Prior to this PTF, OPTIOWGT can be set to either ENABLE or DISABLE, where: - ENABLE indicates to use weights for I/O and CPU that better reflect improved I/O response and caching of newer hardware. In DB2 10, this is the default setting and should be used unless directed otherwise by IBM service. - DISABLE indicates to use weights for I/O and CPU that reflect I/O and CPU capabilities of older hardware. In DB2 V8 only, DISABLE is the default setting. However, in DB2 10, use of OPTIOWGT=DISABLE can result in degraded query performance and should be avoided. To ensure that customers who migrate to V10 avoid performance degradation through inadvertent use of OPTIOWGT=DISABLE, this PTF modifies OPTIOWGT as follows: * The existing settings of ENABLE and DISABLE are made equivalent. Specifying OPTIOWGT=DISABLE now has the same effect as specifying OPTIOWGT=ENABLE, which is that DB2 uses 1 weights for I/O and CPU that better reflect improved I/O response and caching of newer hardware. The purpose of this change is to ensure that your DB2 subsystem can perform optimally with the hardware that it runs on. * A new setting, OFF, is added for cases where DB2 needs to use weights for I/O and CPU that reflect I/O and CPU capabilities of older hardware. This is the behavior that was previously given by specifying OPTIOWGT=DISABLE. You should use OPTIOWGT=OFF only when advised to do so by IBM Service. 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 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 who use OPTIOWGT=DISABLE: This PTF modifies OPTIOWGT so that the DISABLE setting is equivalent to the ENABLE setting. If you use currently use OPTIOWGT=DISABLE, you are strongly recommended to use OPTIOWGT=ENABLE instead. Note that OPTIOWGT=ENABLE behavior will be activated on DB2 the next time you rebuild your DB2 subsystem (DSNZPxxx) module, even if you continue to use OPTIOWGT=DISABLE. Use the new OPTIOWGT=OFF setting only when specifically advised to do so by IBM Service. After applying this PTF, modify your customized copy of job DSNTIJUZ as follows: * Add or update the keyword parameter OPTIOWGT= (where is ENABLE, DISABLE, or OFF) to the invocation of the DSN6SPRM macro in your customized copy of installation job DSNTIJUZ. Make sure to add a continuation character in column 72 if needed. If you omit adding OPTIOWGT here, the value will be set to the recommended default of ENABLE when you assemble the DSNZPxxx module. 1 * 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 modifies the entry for OPTIOWGT in the CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP target library. You need to modify this entry in all private copies of your CLIST output DSNTIDxx member. In each such copy, change the following line: OPTIOWGT CHAR M DISABLE ENABLE to OPTIOWGT CHAR M NONE NONE Change to the value you specify for OPTIOWGT in your private copy of the DSNTIJUZ job. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@XAZP PM70046 DSNTIDXA PM70046 DSNTIDXB PM70046 DSNTINST PM70046 DSNTXAZP PM70046 DSNT1RSP PM70046 DSNWZIFA PM70046 DSNXOMPS PM70046 DSN6SPRM PM70046 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70046 DSN@XAZP DSNTIDXA DSNTIDXB DSNTINST DSNTXAZP DSNT1RSP DSNWZIFA DSNXOMPS DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP DSNT1RSP DSNWZIFA DSNXOMPS MACROS DSN@XAZP DSNTIDXA DSNTIDXB DSNTINST DSN6SPRM 1 LISTEND UK83168 COVER LETTER END UK83171 COVER LETTER START PROBLEM DESCRIPTION(S): PM71114 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users * **************************************************************** * PROBLEM DESCRIPTION: This PTF ships a new DB2-supplied * * stored procedure, * * SYSPROC.ADMIN_UPDATE_SYSPARM * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** The SYSPROC.ADMIN_UPDATE_SYSPARM stored procedure changes the value of one or more DB2 subsystem parameters located in one of these macros: DSN6SPRM, DSN6ARVP, DSN6LOGP, DSN6SYSP, DSN6FAC, and DSN6GRP. It builds a subsystem paramters load module, and if requested by the user, loads it into storage by issuing the DB2 command -SET SYSPARM command with the LOAD option. If not all of the subsystem parameters modified are online updatable, -SET SYSPARM command with the LOAD option will not be performed. A summary of these enhancements is described in this Techdoc: http://www-01.ibm.com/support/docview.wss?uid=swg21611646 In DB2 9 for z/OS, a DDDEF statement for SCEECPP is also added to DB2 sample SMP/E set up job DSNDDEF1. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71114 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.ADMIN_UPDATE_SYSPARM that can be used to change the value of one or more DB2 subsystem parameters. *************************************************************** 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) 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) Create the customized DSNADMZW library member (7) Update customized copies of installation job DSNTIJMV (8) Update the DB2 REXX WLM environment address space proc (9) Refresh the WLM environment 1 (10) 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, DSNTINS2, and DSNTINS3 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 add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSPROC.ADMIN_UPDATE_SYSPARM WLMENV(DSNWLM_REXX) GRANTTO(PUBLIC) Notes: (a) Always leave a blank line between each configuration control statement (b) Inspect each of the new configuration control statement and if required: - Change the WLMENV parameter settings to the name of the WLM environment you use to run DB2 REXX routines at your site. Specify WLMENV(DSNWLM_NOT_ENABLED) to exclude this routine from validation by job DSNTIJRV. - Change the GRANTTO parameter setting to the authorization IDs that need access to this routine. ---------------------------------------------------------------- 1 (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: - RTL38ACL: GRANT EXECUTE setting for SYSPROC.ADMIN_UPDATE_SYSPARM - RTL38WLM: WLM ENV NAME setting for SYSPROC.ADMIN_UPDATE_SYSPARM 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: RTL38ACL CHAR M NONE NONE PUBLIC RTL38WLM CHAR M NONE NONE DSNWLM_REXX 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 install and grant access to the new routine, SYSPROC.ADMIN_UPDATE_SYSPARM, and the new created global temporary tables SYSIBM.SYSPARM_SETTINGS and SYSIBM.UPDSYSPARM_MSG. ---------------------------------------------------------------- (6) Create the customized DSNADMZW library member *********************************************************** * All V10 customers who want to use the stored procedure * SYSPROC.ADMIN_UPDATE_SYSPARM need to perform this step. *********************************************************** This PTF adds a member called DSNADMZW to the prefix.SDSNSAMP target library. This member contains a template for specifying the names of libraries and disk devices to be allocated by SYSPROC.ADMIN_UPDATE_SYSPARM. (a) Copy this member to a partitioned data set that can be allocated by the address space proc for the WLM environment for SYSPROC.ADMIN_UPDATE_SYSPARM. This data set must be a PDS/PDSE with LRECL=80 and RECFM=FB. (b) Edit your copy and customize and change the data set names as appropriate for your system, for example by changing 'DSN!!0' to the prefix of your DB2 target libraries. Note that DSN!!0.SRCLIB.DATA must be a PDS/PDSE with LRECL=80 and RECFM=FB. (c) Create the DSN!!0.SRCLIB.DATA library if it does not exist. ---------------------------------------------------------------- (7) Update customized copies of installation job DSNTIJMV 1 *********************************************************** * All V10 customers who want to use the stored procedure * SYSPROC.ADMIN_UPDATE_SYSPARM 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 modify the WLMR address space proc generated by job step DSNTIMP (where is the name of the DB2 subsystem or data sharing group) to allocate the DSNADMZW library member you created in the previous step. (a) Edit your customized DSNTIJMV job and locate the WLMR address space proc. (b) Add the following statements //**** Data sets required by ADMIN_UPDATE_SYSPARM //ZPMDFLTS DD DISP=SHR, // DSN=DSN!!0.NEW.SDSNSAMP(DSNADMZW) and change DSN!!0.NEW.SDSNSAMP to the name of the data set that contains the DSNADMZW member that you created in the previous step. (c) Save your changes. ---------------------------------------------------------------- (8) Update the DB2 REXX WLM environment address space proc *********************************************************** * All V10 customers who want to use the stored procedure * SYSPROC.ADMIN_UPDATE_SYSPARM need to perform this step. *********************************************************** The address space proc for the DB2 REXX WLM environment specified for SYSPROC.ADMIN_UPDATE_SYSPARM in step (3) above requires a DD statement to allocate the DSNADMZW library member you created in step (6). (a) Edit the address space proc and add these statements: //**** Data sets required by ADMIN_UPDATE_SYSPARM //ZPMDFLTS DD DISP=SHR, // DSN=DSN!!0.NEW.SDSNSAMP(DSNADMZW) and change DSN!!0.NEW.SDSNSAMP to the name of the data set that contains the DSNADMZW member that you created in the step (6). (b) Save your changes. If you need to create an address space proc for a DB2 REXX WLM environment, use the following procedure: (a) Copy member DSN8WLMP from the prefix.SDSNSAMP library to a system proclib. (b) Edit this copy and customize it according to the instructions in the PROC prolog (c) Save your changes ---------------------------------------------------------------- (9) Refresh the WLM environment *********************************************************** * All V10 customers who want to use the stored procedure * SYSPROC.ADMIN_UPDATE_SYSPARM need to perform this step. *********************************************************** Issue the following VARY MVS command from the console to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH 1 where is the name of the WLM application environment for running the ADMIN_UPDATE_SYSPARM stored procedure. ---------------------------------------------------------------- (10) Run installation job DSNTIJRV to validate new objects *********************************************************** * All V10 customers who want to use the stored procedure * SYSPROC.ADMIN_UPDATE_SYSPARM need to perform this step. *********************************************************** After you have completed the above actions, run your customized copy of job DSNTIJRV to validate installation and configuration of SYSPROC.ADMIN_UPDATE_SYSPARM. ---------------------------------------------------------------- ACTION: ***Actions for PM70897 This PTF adds a new optional configuration parameter called INDEXSTOG to DSNTRIN, the program for installing and configuring DB2-supplied routines and their supporting DB2 objects. You can use INDEXSTOG to specify the name of the DB2 storage group for indexes created by DSNTRIN. DSNTRIN assumes that the specified storage group already exists. When INDEXSTOG is not given, DSNTRIN creates indexes in the SYSDEFLT storage group. After applying this PTF, you can optionally add the INDEXSTOG parameter to the DB2OPT DD of your private copy of job DSNTIJRT. The example below shows how to use INDEXSTOG to specify a storage group called IXSTOGRP: //DB2OPT DD * STOGROUP(TSSTOGRP) INDEXSTOG(IXSTOGRP) BP4K(BP0) BP8K(BP8K0) BP16K(BP16K0) BP32K(BP32K) LOBBP8K(BP8K0) LOBBP16K(BP16K0) //CFIGIN DD * COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN@DMCD PM71114 DSN@RIN PM71114 DSN@RVFY PM71114 DSN@XAZP PM71114 DSNADMCC PM71114 DSNADMCD PM71114 DSNADMUZ PM71114 DSNADMZW PM71114 DSNTESR PM71114 DSNTIDXA PM71114 DSNTIDXB PM71114 DSNTIJMV PM71114 DSNTIJRT PM71114 1 DSNTINST PM71114 DSNTINSV PM71114 DSNTINS1 PM71114 DSNTINS2 PM71114 DSNTINS3 PM71114 DSNTIPRA PM71114 DSNTIPRL PM71114 DSNTRIN PM71114 DSNTRVFY PM71114 DSNTWINF PM71114 DSNTXAZP PM71114 DSN8WLMP PM71114 HDBAA10J PM71114 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71114 DSN@DMCD DSN@RIN DSN@RVFY DSN@XAZP DSNADMCC DSNADMCD DSNADMUZ DSNADMZW DSNTESR DSNTIDXA DSNTIDXB DSNTIJMV DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTINS2 DSNTINS3 DSNTIPRA DSNTIPRL DSNTRIN DSNTRVFY DSNTWINF DSNTXAZP DSN8WLMP HDBAA10J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNADMCC DSNADMCD DSNTRIN DSNTRVFY DSNTWINF DSNTXAZP MACROS DSN@DMCD DSN@RIN DSN@RVFY DSN@XAZP DSNADMUZ DSNADMZW DSNTESR DSNTIDXA DSNTIDXB DSNTIJMV DSNTIJRT DSNTINST DSNTINSV DSNTINS1 DSNTINS2 DSNTINS3 DSNTIPRA DSNTIPRL DSN8WLMP LISTEND UK83171 COVER LETTER END 1UK83173 COVER LETTER START PROBLEM DESCRIPTION(S): PM69104 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those using profile tables * * facility to monitor threads and connections * * for TCP/IP access to a DB2 10 for z/OS * * server. * **************************************************************** * PROBLEM DESCRIPTION: Message DSNT772I or DSNT771I contains * * a negative value in the "number" * * token. * * Example: * * csect A MONITOR PROFILE EXCEPTION * * CONDITION OCCURRED * * -5835 TIME(S) * * IN PROFILE ID=xx * * WITH PROFILE FILTERING SCOPE=IPADDR * * WITH REASON=00E30504 * **************************************************************** * RECOMMENDATION: * **************************************************************** When a system profile monitor warning or exception condition has been detected by a DB2 10 for z/OS server, DB2 issues message DSNT772I on the system console. The number of times a warning or exception condition occurs is reflected by the "number" token in this message. Over an extended period of time, if the accumulated number of warning or exception condition exceeds the value of 61,439 ('EFFF'X) DB2 incorrectly displays the next value (61,440/ 'F000'X) as a negative number. This error occurs because DB2 message generation processing treated the value as a signed number and thus displayed the number as a negative value. DB2 10 for z/OS has been changed to treat the value of the "number" token in messages DSNT772I and DSNT771I as unsigned numbers. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69104 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNFMDIR PM69104 DSNFTDIR PM69104 DSNLAGNT PM69104 DSNLCTRC PM69104 DSNLEDDA PM69104 DSNLILNR PM69104 DSNLIRTR PM69104 DSNLQDIS PM69104 DSNLQINA PM69104 DSNLTACC PM69104 DSNLTACT PM69104 1 DSNLTEXC PM69104 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69104 DSNFMDIR DSNFTDIR DSNLAGNT DSNLCTRC DSNLEDDA DSNLILNR DSNLIRTR DSNLQDIS DSNLQINA DSNLTACC DSNLTACT DSNLTEXC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNFMDIR DSNFTDIR DSNLAGNT DSNLCTRC DSNLEDDA DSNLILNR DSNLIRTR DSNLQDIS DSNLQINA DSNLTACC DSNLTACT DSNLTEXC LISTEND UK83173 COVER LETTER END UK83174 COVER LETTER START PROBLEM DESCRIPTION(S): PM72784 - **************************************************************** * USERS AFFECTED: Users in DB2 10 CM8* or ENFM8* running * * ALTER TABLE ADD COLUMN. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90216 at DSNIOST2 * * OFFSET5380 may occur on DML * * subsequent to an ALTER TABLE ADD * * COLUMN executed during DB2 10 ENFM8* * **************************************************************** * RECOMMENDATION: * **************************************************************** ALTER TABLE ADD COLUMN may fail to generate a new version in DB2 CM8* and ENFM8* after falling back from DB2 10 NFM. Subsequent DMLs referencing the altered table may result in ABEND04E RC00C90216 at DSNIOST2 OFFSET5380, overlays and other unexpected results may occur if the table's containing table space is in Reordered Row Format (RRF). ALTER TABLE ADD COLUMN has been modified to generate a new version when appropriate in DB2 CM8* and ENFM8* after falling back from DB2 10 NFM. This APAR does not fix existing table spaces. Affected table spaces will need to be dropped and recreated. ADDITIONAL KEYWORDS: SQLALTER SMCOVERLAY 1 DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72784 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIAB3 PM72784 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72784 DSNXIAB3 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIAB3 LISTEND UK83174 COVER LETTER END UK83176 COVER LETTER START PROBLEM DESCRIPTION(S): PM74406 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those where DB2 is configured * * with (DSNTIPR) DDF THREADS INACTIVE * * (DSN6FAC CMTSTAT=INACTIVE) and (DSNTIP5) * * POOL THREAD TIMEOUT 0 (DSN6FAC POOLINAC=0). * * DB2 10 for z/OS users only. * **************************************************************** * PROBLEM DESCRIPTION: Massive accumulation of DB2 DDF server * * threads, DBATs, in termination * * processing. The excessive number of * * DBATs causes a very high utilization * * of ssnmDIST private (autodata/stack) * * storage, (above the line) ECSA, and * * potentially (below the line) CSA. The * * excessive ECSA and CSA utilization may * * impact the entire z/OS host, even to * * the point of requiring an IPL. * * The problem only occurs if DB2 is * * configured with DSN6FAC POOLINAC=0. * **************************************************************** * RECOMMENDATION: * **************************************************************** New function provided in DB2 10 for z/OS may lead to a condition where DDF server threads (DBATs) can be created and then immediately terminated. Each terminating DBAT will schedule the creation of a replacement DBAT which in turn immediately terminates. This process continues and results in an accumulation of DBATs. The accumulation of DBATs causes a high utilization of sssnDIST private storage and may also cause a high utilization of ECSA and, potentially, CSA 1 storage. The high utilization of ECSA and CSA may ultimately impact all activity on the z/OS host which may require an IPL. The condition only occurs in DB2 10 for z/OS and only if "DDF Threads" Inactive (DSN6FAC CMTSTAT=INACTIVE) is specified in conjunction with a "Pool Thread Timeout" (DSN6FAC POOLINAC) value of zero. DB2 DDF Inactive Thread support processing, operating in a POOLINAC=0 environment, has been changed to recognize a replacement DBAT and allow the newly created DBAT to be suspended (rather than allowing it be immediately terminated). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74406 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLQDIS PM74406 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74406 DSNLQDIS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLQDIS LISTEND UK83176 COVER LETTER END UK83214 COVER LETTER START PROBLEM DESCRIPTION(S): PM66486 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of parallelism * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC04 at DSNXOLM1+9E9C can * * occur for a query containing an * * IN-subquery that is run with * * parallelism * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC04 at DSNXOLM1+9E9C can occur for a query containing an IN-subquery that is run with parallelism. Storage that was freed and reused was being accessed during parallelism processing when multi-index access was chosen, resulting in an abend. Additional Keywords: SQLPARALLELISM DB2PARALL/K SQLINSUBQ Code is added to prevent the storage from being freed if it could be accessed later when using parallelism. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM66486 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 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. 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 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOCSC PM66486 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM66486 DSNXOCSC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOCSC 1 LISTEND UK83214 COVER LETTER END UK83215 COVER LETTER START PROBLEM DESCRIPTION(S): PM64226 - **************************************************************** * USERS AFFECTED: All DB2 V10 for z/os datasharing users * **************************************************************** * PROBLEM DESCRIPTION: The LOB table spaces associated with * * the DB2 directory data base (DSNDB01) * * could experience significant space * * growth resulting from BIND/REBIND * * operations, DDL, utility activity * * such as REORG or other symptoms such * * as : * * 1. ABEND04E RC00D79999 of DSNPXTN1 * * 2. zero pages * * 3. RC00C90101 DSNOALLO ERQUAL5002 * **************************************************************** * RECOMMENDATION: * **************************************************************** The lowest read claim LRSN value from all data sharing members is used to determine whether deleted LOB space can be reused. When the read claim value is being updated frequently during the BIND/REBIND processing, or as a result of DDL or REORG activity, delays may occur in broadcasting this value to other data sharing members. Therefore, the deleted space within directory LOB pagesets may not be reused soon enough, causing space growth. DB2 code is changed to allow the deleted LOB space to more quickly be reused by an inserter that is running in the same data sharing member without dependence upon the global read read claim LRSN. This change is limited to LOB table spaces residing within the DB2 directory data base (DSNDB01), i.e. DSNDB01.SYSDBDXA, DSNDB01.SYSSPUXA, DSNDB01.SYSSPUXB. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64226 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: APAR PM64226 provides improved space reuse capability for directory LOB table spaces, specifically DSNDB01.SYSSPUXA, DSNDB01.SYSSPUXB and DSNDB01.SYSDBDXA. A secondary problem resolved by this APAR is LOB space allocation abends due to unformatted low level space map pages. This APAR will limit further space growth and prevent creation of additional unformatted low level space map page within directory LOB table spaces. The REORG utility may be used to reclaim existing space and remove unformatted space map pages within these table spaces. 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNOALLO PM64226 DSNODALN PM64226 DSNODEAL PM64226 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64226 DSNOALLO DSNODALN DSNODEAL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNOALLO DSNODALN DSNODEAL LISTEND UK83215 COVER LETTER END UK83220 COVER LETTER START PROBLEM DESCRIPTION(S): PM70287 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users of UNLOAD FORMAT INTERNAL * **************************************************************** * PROBLEM DESCRIPTION: Rows unloaded do not have default * * values for ALTER ADDed columns when * * unloaded via UNLOAD FORMAT INTERNAL * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** UNLOAD FORMAT INTERNAL was run on a table defined previous to DB2 V8 and contained ALTER ADDed columns. However, a REORG utility had not been run on the table space since the ALTER ADD had been done. The result was that the rows being unloaded did not contain the default value for the additional columns which in turn results in LOAD FORMAT INTERNAL to not load the rows correctly. UNLOAD FORMAT INTERNAL code has been modified to verify if the table being unloaded falls into the aforementioned situation and if so, correctly unload the rows. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70287 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The APAR for PM70287 allows a table space created before DB2 for z/OS V8 that has ALTER ADDed columns and that has not had a REORG and a MODIFY RECOVERY utility run to clear the ALTER flag, to be unloaded correctly with UNLOAD FORMAT INTERNAL. However, even after the application of this APAR, certain UNLOAD performance improvements cannot be taken advantage of if the REORG and MODIFY RECOVERY utilities have not been run on those 1 table spaces. It is highly suggested that in order to take advantage of those UNLOAD performance improvements that a REORG and a MODIFY RECOVERY utility be run on table spaces that fall into the above situation. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUULIA PM70287 DSNUULJA PM70287 DSNUULXA PM70287 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70287 DSNUULIA DSNUULJA DSNUULXA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUULIA DSNUULJA DSNUULXA LISTEND UK83220 COVER LETTER END UK83248 COVER LETTER START PROBLEM DESCRIPTION(S): PM74851 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E2000C can occur at * * location DSNIWCUB.DSNSVSVB+0AC2 for * * processing that involves an intensive * * use of sort workfiles for a very large * * sort. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E2000C can occur at location DSNSVSVB +0AC2 for processing that involves an intensive use of sort workfiles for a very large sort. In the reported error case, the number of sort workfiles exceeded 300k. During the input phase of sort, there can be a large amount of data to sort. This can trigger the generation of multiple workfiles. As more and more workfiles are created (which accumulate), more storage is needed (and used) to keep track of this information. If this amount gets very large, it can exhaust the storage allotted for this administration. The code in DB2 has been modified to perform intermediate merges of the input data as the number of workfiles increases. This should prevent the storage abend and other possible 'resource unavailable' conditions from occurring. 1 Additional Keywords: SQLSORT DB2STGLK/K OFFSET0AC2 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74851 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSRCY PM74851 DSNXSTSD PM74851 DSNXSTSE PM74851 DSNXSTSG PM74851 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74851 DSNXSRCY DSNXSTSD DSNXSTSE DSNXSTSG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSRCY DSNXSTSD DSNXSTSE DSNXSTSG LISTEND UK83248 COVER LETTER END UK83279 COVER LETTER START PROBLEM DESCRIPTION(S): PM69696 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users that * * run a query with parallelism and a table * * has a decimal column defined as part of its * * primary key. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C7 at DSNXVCDF +2E4 may occur * * when running a query with parallelism * * and the table has a decimal column * * defined as part of the primary key. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C7 at DSNXVCDF +2E4 may occur when running a query with parallelism and the table has a decimal column defined as part of the primary key. The following example illustrates an error case. CREATE TABLE T1 ( C1 DECIMAL(15, 0) NOT NULL, C2 SMALLINT NOT NULL, C3 INTEGER NOT NULL, C4 DATE NOT NULL , 1 C5 FLOAT NOT NULL, PRIMARY KEY (C1,C2,C3)); CREATE UNIQUE INDEX I1 ON T1 (C1,C2,C3); SELECT C1,C2,C3 FROM T1; The bindtime code in DB2 is modified to correct the conditions leading to the ABEND. Additional Keywords: ABEND0C7 SQLSELECT PARALLELISM SQLPARALLELISM OFFSET2E4 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69696 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM72671: See PM72671 APAR/PTF text for additional information about why a REBIND is necessary. PM72671 corrects a problem of an incorrect filter factor for a range predicate referencing a column whose data type is in a double-byte character set. 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 PM69696 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM69696 corrects problems that can cause abend for a query running with parallelism and the table has a decimal column defined as part of primary 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: ***Action for PM60914: See PM60914 APAR/PTF text for additional information about why a REBIND is necessary. PM60914 corrects a problem for: ABEND 04E-00E70005 at DSNXOINL:M100 will occur when a select statement runs in parallelism and contains a in-subquery predicate. 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 PM60536: See PM60536 APAR/PTF text for additional information about why a REBIND is necessary. PM60536 corrects two problems : 1.Incorrect no row found will occur when a query runs in I/O parallelism and involves the index on expression. 2.Abend 0C7-00000000 at DSNXRSFN+9694 will occur when a query runs in parallelism and contains set function in the select 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. DB2BIND: See PM49532 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM49532 fixes ABEND04E RC00E72018 in DSNXSZK+2DBA or ABEND0CF RC0F in DSNXOLM1+C714 when a query is run in 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 PM41582 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM41582 fixes an incorrect output problem when a query is run in parallelism with partition on the inner table (PART_INNER = 'Y' in DSN_PGROUP_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 DSNXOCL PM69696 DSNXODFB PM69696 DSNXODFR PM69696 DSNXOLCM PM69696 DSNXOLM1 PM69696 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69696 DSNXOCL DSNXODFB DSNXODFR DSNXOLCM DSNXOLM1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXOCL DSNXODFB DSNXODFR DSNXOLCM DSNXOLM1 LISTEND UK83279 COVER LETTER END UK83312 COVER LETTER START PROBLEM DESCRIPTION(S): PM72026 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * queries containing a non-Boolean term * * uncorrelated subquery predicate. The left * * side of the subquery predicate is a not null * * column, and the subquery select column is * * also a not null column. The subquery * * predicate is ANDing with a stage 2 * * predicate. * **************************************************************** * PROBLEM DESCRIPTION: APAR PM72026 provides support for * * multiple index access on some non- * * Boolean term uncorrelated subquery * * predicates. The left side of the * * subquery predicate is a not null * * column, and the subquery select column * * is also a not null column. The * * comparison operator of the subquery * * predicate can be >, >=, =, <, <=. The * * subquery predicate is ANDing with a * * stage 2 predicate. * * * * APAR PM72026 adds online-changeable * * subsystem parameter in DSN6SPRM called * * SUBQ_MIDX that can be used to enable * * this performance improvement. The * * default value is DISABLE. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PM72026 provides support for multiple index access on some non-Boolean uncorrelated subquery predicates.The left side of the subquery predicate is a not null column, and the subquery select column is also a not null column. The comparison operator of the subquery predicate can be >, >=, =, <, <=. The subquery predicate is ANDing with a stage 2 predicate. The following example illustrates such a case. 1 CREATE TABLE T1 (T1C1 INT, T1C2 VARCHAR(5) NOT NULL, T1C3 CHAR(5) NOT NULL); CREATE TABLE T2 (T2C1 INT, T2C2 VARCHAR(5) NOT NULL, T2C3 CHAR(5) NOT NULL); CREATE INDEX I1 ON T1 (T1C2); CREATE INDEX I2 ON T1 (T1C3); SELECT T1C2, T1C3 FROM T1 WHERE T1C2='AAAAA' OR (T1C3 = (SELECT T2C3 FROM T2 WHERE T2C1=3) AND T1C1=T1C1); The subquery predicate is non-Boolean term, and it is stage 2 because it ANDs with a residual predicate T1C1=T1C1. With this PTF, multiple index access could be chosen for this subquery predicate on indexes I1 and I2: T1C2='AAAAA' OR T1C3 = (SELECT T2C3 FROM T2 WHERE T2C1=3) The whole predicate will be re-applied again afterwards as residual predicate. WHERE T1C2='AAAAA' OR (T1C3 = (SELECT T2C3 FROM T2 WHERE T2C1=3) AND 1=1); APAR PM72026 adds online-changeable subsystem parameter in DSN6SPRM called SUBQ_MIDX that can be used to enable this performance improvement. The default value is DISABLE. The DB2 code is modified to support this performance enhancement. Additional Keywords: SQLSUBQUERY SQLINDEX MIDX SQLLT SQLGT SQLEQ SQLGE SQLLE SQLNOTNULL SQLNONCORRSUBQ SQLACCESSPATH SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72026 1 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: See PM72026 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM72026 provides support for multiple index access on some non-Boolean term subquery predicates. APAR PM72026 adds online-changeable subsystem parameter in DSN6SPRM called SUBQ_MIDX that can be used to enable this performance improvement. The default value is DISABLE. 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) 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 SUBQ_MIDX=, 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 SUBQ_MIDX here, the value will be set to the default of DISABLE 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. ---------------------------------------------------------------- 1 (3) Update private copies of the DSNTIDxx CLIST input member ==> This action is required for all customers This PTF adds an entry for SUBQ_MIDX 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: SUBQ_MIDX CHAR M DISABLE ENABLE Change to the value you specified for SUBQ_MIDX in step (2), above. ---------------------------------------------------------------- (4) Rebind static applications that are affected by this change ==> This action is required for all customers 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 PM65041: See PM65041 APAR/PTF text for additional information about why a REBIND is necessary. PM65041 corrects an incorrect output problem where NOT IN predicates contain a NULL 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 PM60565: See PM60565 APAR/PTF text for additional information about why a REBIND is necessary. PM60565 corrects a problem of More rows may be returned when running query using parallelism on tables with null values. 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 PM52539: See PM52539 APAR/PTF text for additional information about why a REBIND is necessary. PM52539 corrects a problem of less rows returned when subquery containing UNION ALL in IN predicate. 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 PM33908: See PM33908 APAR/PTF text for additional information about why a REBIND is necessary. PM33908 corrects a problem of incorrect number of rows are retrieved for query containing multiple boolean term 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 DSN@XAZP PM72026 DSNDQWPZ PM72026 DSNDSPRM PM72026 DSNTIDXA PM72026 DSNTIDXB PM72026 DSNTIJUZ PM72026 DSNTINST PM72026 DSNTXAZP PM72026 DSNWZIFA PM72026 DSNXEMG1 PM72026 DSNXGINB PM72026 DSNXGOSQ PM72026 DSNXGTBC PM72026 DSNXOBM PM72026 DSNXOGA1 PM72026 DSNXOMIS PM72026 DSNXOMPS PM72026 DSNXOW2A PM72026 DSNXRBND PM72026 DSNXRBN9 PM72026 DSN6SPRM PM72026 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72026 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSNXEMG1 DSNXGINB DSNXGOSQ DSNXGTBC DSNXOBM DSNXOGA1 DSNXOMIS DSNXOMPS DSNXOW2A DSNXRBND DSNXRBN9 DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTXAZP DSNWZIFA DSNXEMG1 DSNXGINB DSNXGOSQ DSNXGTBC 1 DSNXOBM DSNXOGA1 DSNXOMIS DSNXOMPS DSNXOW2A DSNXRBND DSNXRBN9 MACROS DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSN6SPRM LISTEND UK83312 COVER LETTER END UK83315 COVER LETTER START PROBLEM DESCRIPTION(S): PM73314 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of queries that contain decimal arithmetic * * with system zparm DECDIV3 set to YES or * * specified via SET CURRENT PRECISION. * **************************************************************** * PROBLEM DESCRIPTION: When using the DECDIV3 (minimum divide * * scale) subsystem parameter (zparm) for * * decimal division or special register * * SET CURRENT PRECISION = 'D31.3', a * * query which contains decimal division * * can return an unexpected SQLCODE -406 * * or SQLCODE406 from module DSNXRDEC * * location 511. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using the DECDIV3 (minimum divide scale) subsystem parameter (zparm) or special register SET CURRENT PRECISION = 'D31.3', a query which contains decimal division can return an unexpected SQLCODE -406 or SQLCODE406 from module DSNXRDEC location 511. The problem was reported for DB2 v10 and is not likely to occur for DB2 v9. The following example illustrates the problem. Step 1. Ensure that DECP sets DECARTH=DEC15 and that zparm DECDIV3=YES or that special register SET CURRENT PRECISION = 'D31.3' is specified. 1 Step 2. Create the following Table T1. CREATE TABLE T1 (C1 DECIMAL(18 , 3) NOT NULL ,C2 DECIMAL(15 , 6) NOT NULL ,C3 DECIMAL(18 , 3) NOT NULL ) CCSID EBCDIC ; Step 3. Insert the following row of data into Table T1. INSERT INTO T1 VALUES(630104.780, 1.000000, 37500000.000) ; Step 4. Perform one of the following queries. SELECT A.* , (C1 * C2)/(C3 + 0.00000000001) AS CALCOL FROM T1 A; SELECT A.* , (C1 * C2)/(C3 + 0.00000000001)/0.01 AS CALCOL FROM T1 A; Step 5. The query returns an SQLCODE -406 from DSNXRDEC location 511 but should not. The problem occurs because of a one-byte overlay of the result buffer internally when performing the decimal division when DECDIV3 or decimal precision is set. It does not occur for all values. Also, in DB2 v9, the overlay can occur but since it is not known to impact critical storage (or the internal result buffer as in v10), the failure does not occur. Please note that if the DECDIV3 parm is set to NO, an SQLCODE -419 (or SQLCODE419) should occur from DSNXOBFF location 910. The code in DB2 is modified to prevent the one-byte overlay when processing a decimal division if DECDIV3 or SET CURRENT PRECISION = 'D31.3' are set. This will prevent the SQLCODE -406 and allow the proper result to be returned. Additional Keywords: SQLSTORAGE DB2OVRLAY/K SQLDIVIDE SQLDECIMAL SQLCODE406 SQLCODE419 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73314 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 DSNXRDEC PM73314 DSNXRDE9 PM73314 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73314 DSNXRDEC DSNXRDE9 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDEC DSNXRDE9 LISTEND UK83315 COVER LETTER END UK83318 COVER LETTER START PROBLEM DESCRIPTION(S): PM70792 - **************************************************************** * USERS AFFECTED: All DB2 users with RID list processing * * failures. * **************************************************************** * PROBLEM DESCRIPTION: Abend in some DB2 components when RID * * list processing fails due to the * * internal control block being freed * * prematurely. * **************************************************************** * RECOMMENDATION: * **************************************************************** During RID list processing, various abends can occur in different DB2 components because an internal control block which contains the RIDs, is being freed prematurely. This APAR does not fix the premature freeing of the control block. It is purely adding the serviceability traces and will take dumps to find out why the internal control blocks are being freed prematurely. DB2 code was changed to add serviceability traces and dumps to find out why the internal control block has been freed prematurely. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70792 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRIDL PM70792 DSNIRIDR PM70792 DSNISRID PM70792 DSNITCUS PM70792 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM70792 DSNIRIDL DSNIRIDR DSNISRID DSNITCUS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRIDL DSNIRIDR DSNISRID DSNITCUS LISTEND UK83318 COVER LETTER END UK83371 COVER LETTER START PROBLEM DESCRIPTION(S): PM68934 - **************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS OF RECOVER UTILITY AND SYSTEM LEVEL * * BACKUPS * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU512I DURING RECOVER UTILITY * * ON PARTITIONED OBJECTS WHEN SYSTEM * * LEVEL BACKUPS ARE USED AS A RECOVERY * * BASE * **************************************************************** * RECOMMENDATION: * **************************************************************** User ran BACKUP SYSTEM utility to create a system level backup (SLB) to be used later as a base for recovery by RECOVER utility. After the SLB was taken, one or more partitions were added (Partitioned By Growth (PBG) table spaces were used in the reported case) and later RECOVER was run on that object with DSNUM ALL to a prior point after the SLB was taken but before the extra parts were added. The job failed with DSNU512I - DATA SET LEVEL RECOVERY IS REQUIRED because this type of recovery was restricted. In this situation, users were required to run RECOVER separately on each partition they wished to recover using DSNUM n. Code was changed in RECOVER utility to allow a point-in-time recovery with DSNUM ALL to a point before partitions were added to a partitioned object using an SLB as a recovery base. In such a situation, data set level recovery is no longer required. APAR PM68934 also makes a change to DB2 Messages similar to the following: Under message DSNU512I, the clause, "or a system-level backup was to be restored which was created prior to partitions being added to the object" is deleted from the explanation, so the explanation now reads as follows: 1 Recovery was requested for an entire object. However, there is an image copy made for a specific data set associated with the object. Hence, the object must be recovered by data set. Additional keywords: TORBA TOLOGPOINT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68934 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCALA PM68934 DSNUCASA PM68934 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68934 DSNUCALA DSNUCASA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCALA DSNUCASA LISTEND UK83371 COVER LETTER END UK83402 COVER LETTER START PROBLEM DESCRIPTION(S): PM71930 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who * * are also using IDAA ( IBM DB2 Analytics * * Accelerator ) * **************************************************************** * PROBLEM DESCRIPTION: Refine heuristics for IDAA. * **************************************************************** * RECOMMENDATION: * **************************************************************** Refine heuristics for IDAA to improve the ability of DB2 to determine when a query should be offloaded to IDAA for faster processing. Heuristics code is updated. Keywords: IDAAV2R1/K IDAAV3R1/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71930 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXONZH PM71930 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71930 DSNXONZH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXONZH LISTEND UK83402 COVER LETTER END UK83405 COVER LETTER START PROBLEM DESCRIPTION(S): PM71248 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of LOCK TABLE on tables involved in * * clone relationships * **************************************************************** * PROBLEM DESCRIPTION: LOCK TABLE may result in an unexpected * * SQLCODE904 when the specified table * * is a base table involved in a clone * * relationship and the clone table * * status is STOP. * **************************************************************** * RECOMMENDATION: * **************************************************************** LOCK TABLE may either fail to issue an error or incorrectly isssue an error, such as SQLCODE -904, when the table specified is involved in clone relationship. This may occur when the base table is stopped and the corresponding clone table is specified in the LOCK TABLE statement or when the clone table is stopped and the corresponding base table is specified in the LOCK TABLE statement. LOCK TABLE has been fixed to correctly issue SQLCODE -904 when the table specified is involved in a clone relationship. ADDITIONAL KEYWORDS: SQLALTER SQLCLONE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71248 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXI15 PM71248 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71248 DSNXI15 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXI15 LISTEND UK83405 COVER LETTER END UK83424 COVER LETTER START PROBLEM DESCRIPTION(S): PM70915 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS utility users with * * PM52891 (UK77196) applied and DB2 10 * * for z/OS utility users with PM52891 * * (UK77195) applied. * * * * All DB2 9 for z/OS utility users of the * * TEMPLATE utility specifying GDG data sets. * **************************************************************** * PROBLEM DESCRIPTION: Two errors in this apar: * * * * 1. During execution of DSNTEJ1 an * * ABEND0C4 occurred at DSNUGSDA+x'55CA' * * * * 2. MSGDSNU1031I erroneously issued when * * specifying a GDG data set name in a * * TEMPLATE * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** 1. During execution of DSNTEJ1, an ABENDS0C4 RC10 occurred at DSNUGSDA OFFSET55CA trying to access a control block. This control block can reside either above or below the line and is accessed via one of two pointer variables. This error was the result of using the wrong pointer variable to access that control block. While this error occurred during a DSNTEJ1 job, it can occur during any utility. 2. Only in DB2 9 for z/OS, a TEMPLATE specifying a GDG data set name resulted in message DSNU1031I "DSN datasetname TOO LONG" being issued. This was caused by an uninitialized variable being used for the length of the data set name. 1. Code has been changed to access the control block in question by using the correct pointer variable. 2. TEMPLATE code in DB2 9 for z/OS has been change to initialize the variable in question. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM70915 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 DSNUBCDA PM70915 DSNUBCKB PM70915 DSNUGDYN PM70915 DSNUGSDA PM70915 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM70915 DSNUBCDA DSNUBCKB DSNUGDYN DSNUGSDA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUBCDA DSNUBCKB DSNUGDYN DSNUGSDA LISTEND UK83424 COVER LETTER END UK83426 COVER LETTER START PROBLEM DESCRIPTION(S): PM74152 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users with queries * * containing a range predicate on a * * partitioning column defined as CHAR(1) * * NOT NULL. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output with no rows found * * may occur for queries with a >, >=, * * <, or <= range predicate on a CHAR(1) * * NOT NULL partitioning column. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may produce incorrect output such that no rows qualify when qualified rows exist. This problem can occur when both of the following are true... * A partitioned tablespace uses a column defined as CHAR(1) NOT NULL as a partitioning column. * A query contains a >, >=, <, <= range predicate on the partitioning column defined as CHAR(1) NOT NULL. Additional Keywords: SQLINCORR DB2INCORR/K PAGERANGE SQLGT SQLGE SQLLT SQLLE SQLINCORROUT INCORROUT DB2 has been modified to correctly determine the qualified partitions and return the correct result. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74152 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 1 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 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. 1 COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPG2 PM74152 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74152 DSNXOPG2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPG2 LISTEND UK83426 COVER LETTER END UK83436 COVER LETTER START PROBLEM DESCRIPTION(S): PM75276 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * can use a sparse index. * **************************************************************** * PROBLEM DESCRIPTION: A performance degradation (in query * * execution time) can occur when the * * result of a sparse index is directed to * * a physical workfile. This can create * * an excessive amount of GetPages and * * increase CPU when attempting to probe * * the sparse index. * **************************************************************** * RECOMMENDATION: * **************************************************************** A performance degradation (in query execution time) is possible when the result of a sparse index is directed to a physical workfile. This can create an excessive amount of GetPages and CPU when attempting to probe the sparse index. When computing the 'skip factor' when there are more records than can fit in the available storage, there are certain conditions that can affect the result of the internal formula used. The result of the formula can be incorrect which can lead to using all of the available storage while leaving a large number of records in the physical workfile yet to be scanned. This extra scanning can cause additional Getpages and increase CPU. The 'skip factor' is supposed to take into account the maximum number of records that can actually be placed in the sparse index and then distribute the data evenly so that no large chunk of storage remains. The code in DB2 has been modified to re-calculate the skip factor (correctly) for a sparse index that is to be placed into a physical workfile. Additional Keywords: SQLSPARSEINDEX SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM75276 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 PM75276 DSNXSMRG PM75276 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75276 DSNXSMRE DSNXSMRG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSMRE DSNXSMRG LISTEND UK83436 COVER LETTER END UK83458 COVER LETTER START PROBLEM DESCRIPTION(S): PM71471 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who have a query * * with a combination of OR and AND predicates, * * and the query has a CASE expression with * * an EXISTS subquery in the select list. * **************************************************************** * PROBLEM DESCRIPTION: If there is a CASE expression with an * * EXISTS subquery in the select list, * * and the query contains a combination * * of OR and AND predicates, there may be * * an error when a predicate is replicated * * through localization, causing an abend. * **************************************************************** * RECOMMENDATION: * **************************************************************** If there is a CASE expression with an EXISTS subquery in the select list, and the query contains a combination of OR and AND predicates, there may be an error when a predicate is replicated through localization, causing an abend. Instead of an abend, poor query performance or incorrect output is also possible. For example: SELECT (CASE WHEN ( EXISTS ( SELECT 1 FROM T1 A, T2 B WHERE A.C2 = 2 AND A.C2 = B.C2 ) ) 1 THEN 'T' ELSE 'F' END) AS STATUS FROM T1, T2 WHERE T1.C1 = 1 AND T2.C1 > 2 OR T1.C2 = 2 AND T2.C2 < 4; There is a CASE expression in the select list which contains an EXISTS subquery, and there are AND predicates under an OR predicate. The DB2 optimizer may improperly replicate a predicate for localization, leading to the error. Additional Keywords: SQLACCESSPATH SQLOR SQLAND SQLCASE SQLEXISTS SQLPERFORMANCE SQLINCORROUT INCORROUT SQLINCORR DB2INCORR/K Code is changed to fix the problem above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71471 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71471: See PM71471 APAR/PTF text for additional information about why a REBIND is necessary. PM71471 corrects a predicate localization problem when there is an EXISTS subquery in the CASE expression of the select 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 DSNXOPPD PM71471 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71471 DSNXOPPD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPPD LISTEND UK83458 COVER LETTER END UK83462 COVER LETTER START PROBLEM DESCRIPTION(S): PM72265 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who use * 1 * IBM DB2 Analytics Accelerator * **************************************************************** * PROBLEM DESCRIPTION: Two new settings, ALL and ELIGIBLE, are * * added for special register CURRENT * * QUERY ACCELERATION. * **************************************************************** * RECOMMENDATION: * **************************************************************** Two new settings, ALL and ELIGIBLE, are added for the DSN6SPRM.QUERY_ACCELERATION parameter and special register CURRENT QUERY ACCELERATION. The new settings are: * ALL : Indicates that any given query will be accelerated if it is eligible for acceleration without heuristics and costing, and queries that are not eligible will not be executed in DB2, but will raise SQL error -4742 instead. There is no failback with this option. * ELIGIBLE: Indicates that any given query will be accelerated if it is eligible for acceleration without heuristics and costing. Queries that are not eligible will be executed in DB2. There is no failback with this option. The ALL and ELIGIBLE settings are added to the existing settings of ENABLE, ENABLE_WITH_FAILBACK, and NONE (which is the default setting). See the DB2 Installation Guide for more information about these existing settings. New SQL code -4742 is added. See HOLD data for more information on this SQL code. Additional Keywords: IDAAV2R1/K IDAAV3R1/K SQLCODE4742 Two new settings, ALL and ELIGIBLE, are added for the DSN6SPRM.QUERY_ACCELERATION parameter and special register CURRENT QUERY ACCELERATION. The DB2 V9 support for ALL/ELIGIBLE is provided via APAR PM72264. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72265 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: New SQL code -4742 is added. The approximate description in the DB2 Codes manual for SQL code -4742 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. 1 The statement cannot be executed by DB2 for the following reason: . 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. reason-code A numeric value that provides additional information about why the statement cannot be executed in the accelerator server. Possible values are: 1 No active accelerator server was found when the statement was executed. 2 The special register CURRENT QUERY ACCELERATION is set to NONE. 4 The query is not read-only. 6 The cursor is defined as scrollable or is a rowset- positioned cursor. 7 The query uses multiple encoding schemes. 8 The FROM clause of the query specifies a data-change-table-reference. 9 The query contains a nested table expression. 10 The query contains a recursive reference to a common table expression. 11 The query contains an unsupported expression. 12 The query references a table that has any of the following characteristics: - Is not defined in the accelerator server - Is defined in a different accelerator server from another table in the query - Is defined in the accelerator server, but is not enabled for query acceleration 13 The accelerator server that contains the tables that are referenced in the query is not started. 14 A column that is referenced in the query was altered in DB2 after the data was loaded in the accelerator server. 15 The query uses functionality that is available only in DB2 for z/OS Version 10 new-function mode or later. 17 The query is an INSERT from SELECT statement. Subsystem parameter QUERY_ACCEL_OPTIONS does not specify option 2 to enable the acceleration of INSERT from SELECT statements. System Action: The statement cannot be processed. Programmer Response: Use the reason code to determine the cause of the failure, and take the appropriate action: 1 Start the accelerator server. 2 Set special register CURRENT QUERY ACCELERATION to ENABLE, ENABLE WITH FAILBACK, ELIGIBLE, or ALL. 1 4 Ensure that the query meets the criteria for a read-only query. See the information on read-only cursors in "DECLARE CURSOR". 6 Remove the SCROLL clause or WITH ROWSET POSITIONING clause from the cursor declaration. 7 Ensure that all objects to which the query refers have the same encoding scheme. 8 Rewrite the FROM clause of the query so that it does not include a data-change-table-reference clause. 9 Ensure that the FROM clause of the query does not contain a subquery. 10 Ensure that the FROM clause of the query does not reference a common table expression. 11 Remove the unsupported expression from the query. 12 Ensure that all tables that are referenced by the query are in the same accelerator server, and that all tables are enabled for query acceleration. 13 Start the accelerator server that contains the tables that are referenced in the query. 14 Load the altered table into the accelerator server again. 15 Ensure that the query does not use any functionality that is available in DB2 for z/OS Version 10 new-function mode or later. 17 Enable the acceleration of INSERT from SELECT statements by updating subsystem parameter QUERY_ACCEL_OPTIONS to include option 2. SQLSTATE: 560D5 ACTION: This PTF introduces two additional settings, ALL and ELIGIBLE, for the DSN6SPRM.QUERY_ACCELERATION parameter. This parameter specifies the default value for the CURRENT QUERY ACCELERATION special register. The new settings are: * ALL : Indicates that any given query will be accelerated if it is eligible for acceleration without heuristics and costing, and queries that are not eligible will not be executed in DB2, but will raise an SQL error instead. There is no failback with this option. * ELIGIBLE: Indicates that any given query will be accelerated if it is eligible for acceleration without heuristics and costing. Queries that are not eligible will be executed in DB2. There is no failback with this option. The ALL and ELIGIBLE settings join the existing settings of ENABLE, ENABLE_WITH_FAILBACK, and NONE (which is the default setting). See the DB2 Installation Guide for more information about these existing settings. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF if you want to specify QUERY_ACCELERATION=ALL or ELIGIBLE: 1 (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 ---------------------------------------------------------------- To modify the QUERY_ACCELERATION setting, you need to update your customized copy of this job as follows: * Add or update the keyword parameter QUERY_ACCELERATION= (where is ALL, ELIGIBLE, ENABLE, ENABLE_WITH_FAILBACK, or NONE) to the invocation of the DSN6SPRM macro in your customized copy of installation job DSNTIJUZ. Make sure to add a continuation character in column 72 if needed. If you omit adding QUERY_ACCELERATION here, the value 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 ---------------------------------------------------------------- If you added or modified the QUERY_ACCELERATION parameter in step (1) above, you also 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_ACCELERATION CHAR M NONE NONE Change to the value you specified for QUERY_ACCELERATION in step (1), above. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNDQWPZ PM72265 DSNDSPRM PM72265 DSNHAPLY PM72265 DSNHPTAB PM72265 DSNHSM2V PM72265 DSNHSM7 PM72265 DSNHSYMH PM72265 DSNLXSR PM72265 DSNLZOSR PM72265 DSNTIAM PM72265 DSNTIA1 PM72265 DSNWZIFA PM72265 DSNXEDP PM72265 DSNXEDSC PM72265 1 DSNXESQL PM72265 DSNXESSR PM72265 DSNXGRTM PM72265 DSNXODML PM72265 DSNXOEX1 PM72265 DSNXOIN PM72265 DSNXONZA PM72265 DSNXONZO PM72265 DSNXOOS1 PM72265 DSNXRBN9 PM72265 DSNXRRSP PM72265 DSNXRSPG PM72265 DSNXRSP9 PM72265 DSN6SPRM PM72265 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72265 DSNDQWPZ DSNDSPRM DSNHAPLY DSNHPTAB DSNHSM2V DSNHSM7 DSNHSYMH DSNLXSR DSNLZOSR DSNTIAM DSNTIA1 DSNWZIFA DSNXEDP DSNXEDSC DSNXESQL DSNXESSR DSNXGRTM DSNXODML DSNXOEX1 DSNXOIN DSNXONZA DSNXONZO DSNXOOS1 DSNXRBN9 DSNXRRSP DSNXRSPG DSNXRSP9 DSN6SPRM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNHAPLY DSNHPTAB DSNHSM2V DSNHSM7 DSNHSYMH DSNLXSR DSNLZOSR DSNTIAM DSNTIA1 DSNWZIFA DSNXEDP DSNXEDSC DSNXESQL DSNXESSR DSNXGRTM DSNXODML DSNXOEX1 DSNXOIN DSNXONZA DSNXONZO DSNXOOS1 DSNXRBN9 DSNXRRSP DSNXRSPG DSNXRSP9 MACROS DSNDQWPZ DSNDSPRM DSN6SPRM 1 LISTEND UK83462 COVER LETTER END UK83482 COVER LETTER START PROBLEM DESCRIPTION(S): PM71826 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of data sharing * **************************************************************** * PROBLEM DESCRIPTION: Serviceability needed to produce a * * diagnostic dump for inconsistent DBET * * structure with regard to piece-level * * states * **************************************************************** * RECOMMENDATION: * **************************************************************** Serviceability is needed for inconsistent DBET structure for an object, specifically for the case where a piece level state exists (e.g. LPL, GRECP, extend-in-progress). Such serviceability already exists today for DBET notify exit path - symptom ABEND04E DSNIDBEL ERQUAL5222. This APAR adds the same serviceability to mainline DBET path - the new symptom will be ABEND04E DSNIDBEL ERQUAL5221. Code has been changed to add serviceability for inconsistent DBET structure for an individual object (for piece -level states). The new symptom will be ABEND04E DSNIDBEL ERQUAL5221. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71826 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIDBEL PM71826 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71826 DSNIDBEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIDBEL LISTEND UK83482 COVER LETTER END UK83499 COVER LETTER START PROBLEM DESCRIPTION(S): PM74459 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * materialized query tables and an SQL * * statement that contains an EXISTS predicate. * **************************************************************** 1 * PROBLEM DESCRIPTION: Wrong materialized query table could be * * used for an SQL statement that contains * * an EXISTS predicate resulting in * * incorrect output. * **************************************************************** * RECOMMENDATION: * **************************************************************** Wrong materialized query table could be used for an SQL statement that contains an EXISTS predicate resulting in incorrect output. An example is shown below: CREATE TABLE T1(C1 INT, C2 CHAR(3), C3 INT); CREATE TABLE AST1 (C1, C2, C3) AS( SELECT C1, C2, C3 FROM T1 WHERE C1 = C3 AND C2 = 'ABC') DATA INITIALLY DEFERRED REFRESH DEFERRED MAINTAINED BY USER ENABLE QUERY OPTIMIZATION; SELECT C1, C2, C3 FROM T1 WHERE EXISTS (SELECT 1 FROM SYSIBM.SYSDUMMY1) AND C1 = C3 AND C2 = '123' FOR FETCH ONLY; The query above should not use the materialized query table AST1 because the predicate C2 = '123' in the query does not match to the predicate C2 = 'ABC' in AST1, while it incorrectly uses AST1 and returns incorrect data. DB2 did not correctly process the aforementioned SQL statement, so the wrong materialized query table could be used. DB2 has been modified to correctly process the aforementioned SQL statement, and the wrong materialized query table will not be used. Additional keywords: SQLMQT SQLEXISTS SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74459 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOXMT PM74459 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES 1 PM74459 DSNXOXMT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOXMT LISTEND UK83499 COVER LETTER END UK83506 COVER LETTER START PROBLEM DESCRIPTION(S): PM71787 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of RESTORE SYSTEM utility. * **************************************************************** * PROBLEM DESCRIPTION: RESTORE SYSTEM FROMDUMP failed with * * message MSGDSNU030I when OA39917 was * * previously applied. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran RESTORE SYSTEM FROMDUMP to restore copy pool from tape with OA39917 applied. The restore failed with message MSGDSNU030I because OA39917 modified the format for COPY POOL output to allow more than 99 dump tape volumes, which led to the failure. RESTORE SYSTEM utility was changed to support both the old and the new format for COPY POOL output. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71787 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUVBLC PM71787 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71787 DSNUVBLC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUVBLC LISTEND UK83506 COVER LETTER END UK83524 COVER LETTER START PROBLEM DESCRIPTION(S): PM73888 - **************************************************************** 1 * USERS AFFECTED: All DB2 10 for z/OS users of the STRIP * * built-in function with Unicode graphic * * data. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXVTRS M420 * * for an SQL statement using the STRIP * * or TRIM function on Unicode graphic * * data * **************************************************************** * RECOMMENDATION: * **************************************************************** The abend occurs when the STRIP or TRIM function specifies the BOTH keyword and the result is the empty string because all the characters have been removed from the input string expression. The string expression data must be Unicode graphic for the problem to occur. The input string expression contains characters that are all the same as the trim-constant. Following is an example of the problem where input string and the trim-constant are blank. CREATE TABLE TEST1 (COL1 GRAPHIC(100) ) CCSID UNICODE; INSERT INTO TEST1 VALUES (' ') SELECT STRIP(COL1,BOTH,' ') FROM TEST1; - abend occurs The abend is intermittent depending on the storage accessed. It is also possible to get incorrect output instead of an abend. In this case, the trim-constant may not be trimmed from the left. For example: INSERT INTO TEST1 VALUES (' A'); SELECT STRIP(COL1,BOTH,' ') FROM TEST1; The incorrect result ' A' may be returned instead of the correct result 'A'. The process of removing the trim character from the left has been fixed so that it correctly removes the characters. The problem was storage dependent and intermittent. Additional keywords : SQLGRAPHIC SQLTRIM SQLSTRIP DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73888 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRDBC PM73888 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73888 DSNXRDBC 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRDBC LISTEND UK83524 COVER LETTER END UK83527 COVER LETTER START PROBLEM DESCRIPTION(S): PM65750 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Edit Procedures * * or EDITPROCs. * **************************************************************** * PROBLEM DESCRIPTION: Due to the restrictions associated with * * the current type of edit procedures * * (EDITPROCs), DB2 10 for z/OS will now * * support a new type of EDITPROC with * * fewer restrictions. * **************************************************************** * RECOMMENDATION: * **************************************************************** Some of the restrictions associated with current EDITPROCs make using newer data types and adding columns not possible. This enhancement for EDITPROCs will allow newer data types and also allow the ability to perform ALTER TABLE ADD COLUMN for tables using the new style EDITPROCs (edit procedures). A new syntax is being provided for the CREATE TABLE EDITPROC clause. The SQL Reference has already been updated with these changes and can be found in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic). If a user specifies EDITPROC WITH ROW ATTRIBUTES, then the behavior remains the same. This means the table may not contain any identity, LOB, XML, ROWID, or SECURITY LABEL columns. This is the default. If a user specifies EDITPROC WITHOUT ROW ATTRIBUTES, the users may create tables containing identity, XML, ROWID, or SECURITY LABEL columns. You must not specify any edit procedure for a table with a LOB column. For more information on writing an EDITPROC, see DB2 Administration Guide. If you omit EDITPROC, the table has no edit procedure. For the ALTER TABLE ADD COLUMN case, if a table has been defined with an EDITPROC WITHOUT ROW ATTRIBUTES, then users may alter add identity, XML, ROWID, or SECURITY LABEL columns. This enhancement does not allow users to alter EDITPROCs between 1 WITH or WITHOUT ROW ATTRIBUTES. If a table has EDITPROC WITHOUT ROW ATTRIBUTES defined, users will no longer see the following SQLCODEs: (1) SQLCODE668 on ALTER TABLE ADD COLUMN (2) SQLCODE148 on ALTER TABLE ALTER COLUMN, except for LOBs (3) SQLCODE350 on CREATE TABLE for the newer data types (4) SQLCODE876 for a column name greater than 18 EBCDIC bytes (5) SQLCODE20240 on ALTER or CREATE TABLE for a SECURITY LABEL column (6) SQLCODE771 on ALTER or CREATE TABLE for a ROWID column (7) SQLCODE750 on ALTER TABLE RENAME COLUMN Additional Keywords: SQLEDITPROC SQLALTER COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65750 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE is specified with OBID 1. The approximate text will be updated in the DB2 SQL Reference and Codes manual. This text is subject to change. ============= SQL Reference ============= CREATE TABLE->OBID integer Identifies the OBID to be used for this table. An OBID is the identifier for an object's internal descriptor. The | integer must be greater than 1 and not identify an existing or previously used OBID of the database. If you omit OBID, DB2 generates a value. ===== Codes ===== -736 The specified OBID does not fall within the acceptable range | for OBIDs, which is 2 to 32767. ACTION: With the application of the PTF for PM63835, because the STATUS column in SYSIBM.SYSTABLESPACE will now be correct when loading a partitioned table space with RI, it is possible that a CHECK DATA PART or a CHECK DATA SCOPE PENDING utility run on a child table space after being loaded might take longer to complete. This would be due to the utility reading the now correct STATUS column and deciding that all partitions for that child table space needed to be checked rather than just specfic or specified partitions. ACTION: PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE is specified with OBID 1. Existing tables with OBID 1 should be dropped and recreated with a different OBID. 1 A query, such as the sample query below may be used to identify tables with OBID 1. SELECT * FROM SYSIBM.SYSTABLES WHERE OBID = 1 AND ( TYPE = 'T' OR TYPE = 'M' OR TYPE = 'H' ) ; COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNGDART PM65750 DSNGDBRT PM65750 DSNGDVAR PM65750 DSNGDVRT PM65750 DSNHSM5 PM65750 DSNIDCML PM65750 DSNIENSR PM65750 DSNILEDR PM65750 DSNILREP PM65750 DSNIMOFR PM65750 DSNIONX2 PM65750 DSNIOST2 PM65750 DSNIREDR PM65750 DSNIRFNX PM65750 DSNIRNXT PM65750 DSNIRSET PM65750 DSNISFX2 PM65750 DSNISRTI PM65750 DSNITEDI PM65750 DSNUCLGR PM65750 DSNUEXDB PM65750 DSNUGCKP PM65750 DSNURFBR PM65750 DSNURLAP PM65750 DSNURLXL PM65750 DSNURSCN PM65750 DSNURWBF PM65750 DSNUSINI PM65750 DSNUSTBL PM65750 DSNUULCA PM65750 DSNXIAB3 PM65750 DSNXIATB PM65750 DSNXICB1 PM65750 DSNXICB3 PM65750 DSNXICB8 PM65750 DSNXICTB PM65750 DSNXIRCO PM65750 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65750 DSNGDART DSNGDBRT DSNGDVAR DSNGDVRT DSNHSM5 DSNIDCML DSNIENSR DSNILEDR DSNILREP DSNIMOFR DSNIONX2 DSNIOST2 DSNIREDR DSNIRFNX DSNIRNXT DSNIRSET DSNISFX2 DSNISRTI DSNITEDI DSNUCLGR DSNUEXDB DSNUGCKP DSNURFBR DSNURLAP DSNURLXL DSNURSCN DSNURWBF DSNUSINI DSNUSTBL DSNUULCA DSNXIAB3 DSNXIATB DSNXICB1 DSNXICB3 DSNXICB8 DSNXICTB DSNXIRCO 1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNGDART DSNGDBRT DSNGDVAR DSNGDVRT DSNHSM5 DSNIDCML DSNIENSR DSNILEDR DSNILREP DSNIMOFR DSNIONX2 DSNIOST2 DSNIREDR DSNIRFNX DSNIRNXT DSNIRSET DSNISFX2 DSNISRTI DSNITEDI DSNUCLGR DSNUEXDB DSNUGCKP DSNURFBR DSNURLAP DSNURLXL DSNURSCN DSNURWBF DSNUSINI DSNUSTBL DSNUULCA DSNXIAB3 DSNXIATB DSNXICB1 DSNXICB3 DSNXICB8 DSNXICTB DSNXIRCO LISTEND UK83527 COVER LETTER END UK83543 COVER LETTER START PROBLEM DESCRIPTION(S): PM75197 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a read * * only query with a FOR UPDATE clause with * * isolation level other than CS * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * 1 * * * INEFFICIENT ACCESS PATH * * * * PROBLEM SCENARIO: * * * * The reported problem occurs when * * executing a read only query that has * * a FOR UPDATE clause and also uses an * * isolation level other than CS * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: DB2 was restricting certain join sequences for read-only queries that have a FOR UPDATE clause. DB2 should have ignored the FOR UPDATE but did not. As a result, an inefficient access path was selected. This affects queries that have an isolation level other than CS. PROBLEM CONCLUSION: DB2 has been fixed to ignore the FOR UPDATE on such read-only queries described above. ADDITIONAL KEYWORDS: SQLUPDATE SQLSELWUPDATE SQLACCESSPATH SQLPERFORMANCE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75197 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM75197: See PM75197 APAR/PTF text for additional information about why a REBIND is necessary. PM75197 corrects a problem of inefficient access path for read only queries with FOR UPDATE. 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 PM32404: See PM32404 APAR/PTF text for additional information about why a REBIND is necessary. PM32404 corrects a problem of inaccurate filter factor estimation for a predicate that is generated by global optimization for an IN subquery or EXISTS subquery if there are multiple IN or EXISTS subqueries in the same query block. 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 PM29262: See PM29262 APAR/PTF text for additional information about why a REBIND is necessary. PM29262 corrects a problem of inaccurate output in DSN_DETCOST_TABLE when a materialized query block occurs. 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 PM25629: See PM25629 APAR/PTF text for additional information about why a REBIND is necessary. PM25629 resolves a case in which an inefficient join sequence could be chosen for a query block with four or fewer 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 PM17234: See PM17234 APAR/PTF text for additional information about why a REBIND is necessary. PM17234 will allow more join permutations to be considered when there are a high number of query blocks, but each query block contains less than or equal to four 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOSJO PM75197 DSNXOTS PM75197 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75197 DSNXOSJO DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSJO DSNXOTS LISTEND 1UK83543 COVER LETTER END UK83547 COVER LETTER START PROBLEM DESCRIPTION(S): PM74903 - **************************************************************** * USERS AFFECTED: DB2 10 users of Native SQL Procedures * * migrated from DB2 9. * **************************************************************** * PROBLEM DESCRIPTION: After calling a Native SQL Procedure * * that was created on V9 and which * * contains use of LOB variables or data * * or contains any dynamic sql statements, * * the following may occur * * . * * 1. DSNT501I DSNOTCSO RESOURCE * * UNAVAILABLE REASON 00C900D1 * * and/or * * DSNT501I DSNOTCSO RESOURCE * * UNAVAILABLE REASON 00C900D3 * * and/or * * SQLCODE -904 returned to * * the application * * . * * If the procedure is called remotely * * on a DB2 that is configured with * * (DSNTIPR) DDF THREADS INACTIVE * * (DSN6FAC CMTSTAT=INACTIVE) then * * a number of unpredictable operational * * errors are possible including * * . * * 2. DSNL027I 00D3003B Idle Thread * * Timeout conditions * * and/or * * Unexpectedly high utilization of * * DDF DBATs. * * . * * Other symptoms are possible and are * * listed below. * * . * **************************************************************** * RECOMMENDATION: * **************************************************************** Native SQL Procedures may acquire and hold lob locator resources when the procedure references lob variables or lob data or when the procedure runs the SQL PREPARE or SQL EXECUTE IMMEDIATE statements. These resources are normally freed when the procedure terminates. However, an error prevented DB2 from freeing these resources upon termination of migrated Native SQL Procedures. . The error only occurs for Native SQL Procedures that were created in V9 and migrated or deployed to V10. Procedures that are created in V10, or which have been ALTER REGENERATEd in V10, are not exposed to this error. 1 . The error may result in excessive growth and proliferation of LOB storage ( resource code 907 ) and may cause DB2 to issue a DSNT501I DSNOTCSO RESOURCE UNAVAILABLE message with REASON 00C900D1 or 00C900D3. Applications may also fail with SQLCODE -904. The amount of available LOB storage per user is governed the DSNTIP7 install panel parameter LOBVALA . The amount of available LOB storage for the subsystem is governed by the DSNTIP7 install panel parameter LOBVALS . . In addition to the LOB storage leak, there are additional consequences for DB2 subsystems that are configured with DDF THREADS=INACTIVE specified (DSN6FAC CMTSTAT INACTIVE) or those with remote client systems (such as DB2/LUW or JCC) that pool/re-use connections among numerous client applications. The leaked lob resources, which are held across units of work, do not allow the Distributed Data Facility (DDF) to inactivate the application's (network) connection. Basically, the operational impact of this error 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 DDF-related symptoms include: . High rate of unexpected "Idle Thread Time-out" conditions (message DSNL030I with reason code 00D3003B) that may result in unexpected remote application failures. The "Idle Thread Time-out" is controlled by the DSN6FAC install panel parameter IDTHTOIN . . 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. . Reduced number of IFCID 3 accounting records are written. . Remote client "connection concentrator" environments may also be adversely affected as a result of their inability to pool connections on a transaction (commit) boundary. . DB2 code has changed to correctly free held Lob Locator resources when the migrated Native SQL Procedure terminates. . . Additional Keywords: SQLNATIVESQLPL SQLSP SQLSTOREDPROC SQLPREPARE DB2STGLK/K SQLLOB RC00C900D1 RC00C900D3 SQLCODE904 DB2DDF DB2INACTIVE RC00D3003B SQLCODE30080 SQLCODE30081 MSGDSNT501I MSGDSNL027I COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74903 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 DSNXECL PM74903 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74903 DSNXECL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXECL LISTEND UK83547 COVER LETTER END UK83630 COVER LETTER START PROBLEM DESCRIPTION(S): PM64898 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of REORG TABLESPACE SHRLEVEL CHANGE utility. * **************************************************************** * PROBLEM DESCRIPTION: Optimize space usage for REORG * * TABLESPACE SHRLEVEL CHANGE PART of a * * PBG table space in the LOG phase * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User ran a REORG TABLESPACE PART SHRLEVEL CHANGE against a subset of partitions of a partition-by-growth table space. The utility failed with MSGDSNU1170I and RC8 in the LOG phase, when it was unable to insert a record into the partition indicated by the log record because it was full. However, as there were other non-full partition being reorganized, REORG could have prevented this failure if it chooses to insert into another partition, in the event that the data records can be moved across the PBG partitions. Code has been modified for REORG TABLESPACE PART SHRLEVEL CHANGE to choose another non-full PBG partition for insert in the LOG phase, when a target partition is full and data can be moved across the PBG partitions. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM64898 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURLAP PM64898 DSNURLOG PM64898 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM64898 DSNURLAP DSNURLOG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNURLAP DSNURLOG LISTEND UK83630 COVER LETTER END UK83632 COVER LETTER START PROBLEM DESCRIPTION(S): PM74469 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of REORG * * TABLESPACE SHRLEVEL CHANGE utility. * **************************************************************** * PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE with * * DRAIN WRITERS gets ABEND04E RC00E40006 * * in DSNUGUIP OFFSET16CC on a table space * * in transition to hash organization * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User ran a REORG TABLESPACE SHRLEVEL CHANGE on a table space that was in transition to hash organization. The utility failed with ABEND04E RC00E40006 in DSNUGUIP + x'16CC' in the LOG phase, when it tried to set an incompatible Utility-In-Progress ( UIP ) status on the database object after a previous drain failure. The reported problem was caused by incorrect program logic where database objects were deserialized incorrectly when the DRAIN WRITERS option is specified or defaulted. A residual UTRO UIP status was left from a previous drain failure, causing the subsequent RETRY processing to fail. Code has been modified to correct the aforementioned problem by enforcing DRAIN ALL on a REORG TABLESPACE SHRLEVEL CHANGE on a table space in transition to hash organization. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74469 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 PM74469 DSNURLOG PM74469 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74469 DSNURFIT DSNURLOG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURFIT DSNURLOG LISTEND 1UK83632 COVER LETTER END UK83642 COVER LETTER START PROBLEM DESCRIPTION(S): PM75021 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of BIND/REBIND * * PACKAGE and bind options EXPLAIN(YES) or * * EXPLAIN(ONLY) where an index with key * * expression is defined on * * the package-owner.PLAN_TABLE * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -219 occurred during BIND / * * REBIND PACKAGE EXPLAIN(YES|ONLY) as DB2 * * attempted to update binder.PLAN_TABLE * * instead of the expected * * package-owner.PLAN_TABLE, when * * an index with a key-expression is * * defined on package-owner.PLAN_TABLE * **************************************************************** * RECOMMENDATION: * **************************************************************** During BIND / REBIND PACKAGE EXPLAIN ( YES ) a SQLCODE -219 occurred with message tokens showing that DB2 attempted to update binder.PLAN_TABLE for an explainable static SQL statement, instead of updating the expected package-owner.PLAN_TABLE. DB2 csect DSNXOD0Z issued SQLCODE219 indicating that the "REQUIRED EXPLANATION TABLE binder.PLAN_TABLE DOES NOT EXIST", however, the SQLCODE219 was invalidly issued by DB2 because DB2 should have used package-owner.PLAN_TABLE instead. The user had created package-owner.PLAN_TABLE and defined an index with key-expression (aka index on expression ) on the PLAN_TABLE. . The SQLCODE219 occurred for the second or later explainable static SQL statement being bound during the bind package process, following DB2's invocation of the PLAN_TABLE index key expression when DB2 correctly updated package-owner.PLAN_TABLE for the first static SQL statement. When DB2 executed the PLAN_TABLE index key-expression, the authorization ID used was validly changed to the primary auth ID value -- this is normal, expected behavior when executing an index key expression. In this SQLCODE219 case, the primary auth ID was the binder (user auth ID performing the BIND/REBIND PACKAGE), and after executing the index key-expression DB2 did not restore the auth ID back to the package owner, leaving the binder as the auth ID for the remainder of the bind package process. Package owner is the standard auth ID used for the bind package process and is the auth ID / qualifier that DB2 uses for the PLAN_TABLE when 'explaining' static SQL statements during the bind package. . As a result of DB2's failure to restore the auth ID to package owner, for the second and later explainable static SQL 1 statements DB2 attempted to update binder.PLAN_TABLE instead of package-owner.PLAN_TABLE. This resulted in invalid SQLCODE219 during the bind package process for those subsequent static SQL statements. . The problem can also occur when bind option EXPLAIN( ONLY ) is used. . To temporarily avoid the SQLCODE219 on the BIND/REBIND PACKAGE, drop the INDEX on the package-owner.PLAN_TABLE. . DB2 was changed to, after completing execution of the index key- expression, restore the original authorization in use 'before' the index with key-expression was invoked. This applies for an index with key-expression used during a BIND / REBIND PACKAGE or also another DB2 operation. . Additional search keywords: SQLEXPLAIN . COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75021 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIKESR PM75021 DSNKEDLE PM75021 DSNKEINS PM75021 DSNKSDLE PM75021 DSNKSINS PM75021 DSNKSKYG PM75021 DSNUCINT PM75021 DSNUCLGR PM75021 DSNUCRUL PM75021 DSNUKINT PM75021 DSNUKIUL PM75021 DSNURFBR PM75021 DSNURFIT PM75021 DSNURLXL PM75021 DSNURPUI PM75021 DSNURSCN PM75021 DSNURWBF PM75021 DSNURWIK PM75021 DSNUSTBL PM75021 DSNUULXA PM75021 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75021 DSNIKESR DSNKEDLE DSNKEINS DSNKSDLE DSNKSINS DSNKSKYG DSNUCINT DSNUCLGR DSNUCRUL DSNUKINT DSNUKIUL DSNURFBR DSNURFIT DSNURLXL DSNURPUI DSNURSCN DSNURWBF DSNURWIK DSNUSTBL DSNUULXA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES 1 DSNIKESR DSNKEDLE DSNKEINS DSNKSDLE DSNKSINS DSNKSKYG DSNUCINT DSNUCLGR DSNUCRUL DSNUKINT DSNUKIUL DSNURFBR DSNURFIT DSNURLXL DSNURPUI DSNURSCN DSNURWBF DSNURWIK DSNUSTBL DSNUULXA LISTEND UK83642 COVER LETTER END UK83648 COVER LETTER START PROBLEM DESCRIPTION(S): PM72168 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users (both CM and NFM) of * * data partitioned secondary indexes (DPSI) * * used with residual predicate pushdown scan * * by data manager subcomponent - EXPLAIN * * table DSN_FILTER_TABLE shows PUSHDOWN = 'D' * * - and the table has versioned data due to * * some versioning ALTER TABLE * **************************************************************** * PROBLEM DESCRIPTION: Incorrout is possible when data * * partitioned secondary index (DPSI) is * * used with residual predicate pushdown * * scan by data manager subcomponent - * * EXPLAIN table DSN_FILTER_TABLE shows * * PUSHDOWN = 'D' - and the table has * * versioned data due to some versioning * * ALTER TABLE run earlier * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output is possible when data partitioned secondary index (DPSI) is used with residual predicate pushdown by data manager subcomponent - EXPLAIN table DSN_FILTER_TABLE shows PUSHDOWN = 'D' - and the table has downlevel rows, meaning it has gone through some kind of versioning ALTER such as ALTER TABLE ADD COLUMN, ALTER TABLE ALTER COLUMN SET DATA TYPE etc. The root cause of this problem is that a DPSI scan module 1 mistakenly set a bit in the internal MSIB structure, which led to garbage being returned or other unpredictable result. Code has been changed to ensure that the aforementioned bit is set correctly when performing residual predicate pushdown by data manager subcomponent in DPSI scan. Additional keywords: SQLINCORROUT DB2INCORR/K SQLINCORR SQLPREDPUSHDOWN COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72168 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIFDPO PM72168 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72168 DSNIFDPO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIFDPO LISTEND UK83648 COVER LETTER END UK83679 COVER LETTER START PROBLEM DESCRIPTION(S): PM74783 - **************************************************************** * USERS AFFECTED: All DB2 users who use BIND PACKAGE command. * **************************************************************** * PROBLEM DESCRIPTION: Unauthorized BIND PACKAGE request may * * cause other processes to time out. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 acquires an x-lock on SKPT before performing an authorization check during the bind package process, which may cause other requests to time out. Additional Keywords: TIMEOUT DSNT376I 00C9008E SQLCODE911 00C90088 RC00C90088 DB2 has been fixed to check bind authorization before acquiring an x-lock on the package. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74783 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBCM2 PM74783 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74783 DSNTBCM2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBCM2 LISTEND UK83679 COVER LETTER END UK83718 COVER LETTER START PROBLEM DESCRIPTION(S): PM76861 - **************************************************************** * USERS AFFECTED: All users of RESTORE SYSTEM Utility. * **************************************************************** * PROBLEM DESCRIPTION: Abend0c4 in dsnb1ofa+0B0A or RC00E50001 * * in dsnb1ofa during Disaster Recovery. * **************************************************************** * RECOMMENDATION: * **************************************************************** During RESTORE SYSTEM log apply, DBD01 header page is accessed to update HPGRBLP (Recovery Based Log Point). z/OS for DB2 10 defines DBD01 as PBG. However, it still has only one partition. Data Manager (DM) log apply routine defines piece size as 32 for DBD01. However, the calculation for the user suffix area for PBG is based on 1 partition NOT 32 partitions. This results in storage overlay trying to format (initialize) user suffix area for partition 2 through 32. To avoid this storage overlay during physical open, DBD01 piece size will always define as 1 NOT 32. DB2 Restore System log apply logic is modified to use correct piece size for DBD01 table space to avoid storage overlay condition. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76861 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRSTR PM76861 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76861 DSNIRSTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRSTR LISTEND UK83718 COVER LETTER END 1 UK83726 COVER LETTER START PROBLEM DESCRIPTION(S): PM72660 - **************************************************************** * USERS AFFECTED: DB2 users using partitioned page sets * **************************************************************** * 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: * **************************************************************** Turbo drain logic acquires a write drain lock of part 0 in share mode for a partition level drain, either blocked or non-blocked. The drain lock is released during de-drain. Since non-block partition level drain does not acquire partition level drain locks and not set the drain-in-control bit, no de-drain is needed and the drain lock of part 0 is not released. The following write drain requests may not acquire the drain lock of part 0 in update mode since the drain lock has been held. As a result, other jobs can acquire write claims, make updates, and cause data corruption. The turbo drain logic has been modified to not acquire drain locks for part 0 if this is a non-block drain request. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72660 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 PM72660 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72660 DSNB1DRA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1DRA LISTEND UK83726 COVER LETTER END UK83731 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM72885 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and 10 for z/OS users * * with SYSPLEX parallelism enabled. * **************************************************************** * PROBLEM DESCRIPTION: ECSA storage leak after SYSPLEX query * * parallel thread is soft cancelled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ECSA storage leak after SYSPLEX query parallelism thread is soft cancelled. After DB2 parallel thread acquires ECSA storage, it is cancelled and DB2 does not handle this error situation correctly. The problem is not query specific and the problem can be avoided by turning off the SYSPLEX parallelism support. DB2 has been fixed to release acquired ECSA storage after the SYSPLEX parallel thread has been cancelled, so that after the fix, the storage leak problem will be fixed. Additional Keywords: PARALLELISM SYSPLEX SQLSYSPLEXP DB2PARALL/K SQLSTORAGE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72885 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXPSEN PM72885 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72885 DSNXPSEN THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXPSEN LISTEND UK83731 COVER LETTER END UK83742 COVER LETTER START PROBLEM DESCRIPTION(S): PM69950 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * contain a HAVING clause, but without a group * * by and set function, running with * * parallelism. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at * * location DSNOTCSO:5020 when executing a * * query that contains a select that * * references a HAVING clause with a LOB, * 1 * but without a group by and set * * function, running with parallelism. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOTCSO ERQUAL5020 when executing a query with parallelism that contains a select that references a HAVING clause with a LOB, but without a group by and set function. The following example illustrates an error case. SELECT DBCLOB(CAST('N' AS CHAR(1 CODEUNITS32) CCSID 367), 4,CODEUNITS32) FROM V1 HAVING DBCLOB('001') LIKE GRAPHIC('001'); The bindtime code in DB2 has been modified to correct the conditions which can lead to the abend. Additional Keywords: SQLHAVING SQLLOB PARALLELISM DB2PARALL/K SQLPARALLELISM COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69950 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 PM69950 DSNXOLM1 PM69950 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69950 DSNXOLCM DSNXOLM1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOLCM DSNXOLM1 LISTEND 1UK83742 COVER LETTER END UK83757 COVER LETTER START PROBLEM DESCRIPTION(S): PM76248 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN * * job and ENFM process. * **************************************************************** * PROBLEM DESCRIPTION: When ENFM processing the SYSPKAGE * * table space (the ENFM0097 step of * * the DSNTIJENjob ) the user gets the * * following abend: * * * * ABEND04E RC00E40353 at DSNUECMI +0CAA * * RC00C90072 * * * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** The DB2 10 for z/OS ENFM process is abending because it is encountering bad data in the SYSPACKSTMT.STMT column. There was a precompiler bug in a much earlier release of DB2 and this is when the bad data was inserted into the statement zero records. The SYSPACKAGE.PCTIMESTAMP column values in these bad rows were at least 25 years old in both of the reported cases. The ENFM process was trying to use this data ('4040'X) as a CCSID value in CLOB character conversions. Since the CCSID was invalid the character conversions fail and we get the noted abend (ABND=04E-00E40353 LOC=DSNUTILA.DSNUECMI +0CAA). DSNUECMI +OCAA OFFSET0CAA DB2MIGV10/K SQLCA shows SQLCODE332 from DSNXEASC loc -100 with message tokens: 16448.1208.DSNOGETD The following query can be used to determine if a subsystem has one or more rows with the problem noted in this APAR: SELECT NAME, COLLID, CONTOKEN FROM SYSIBM.SYSPACKSTMT WHERE STMTNO = 0 AND SECTNO = 0 AND STMTNOI = 0 AND SECTNOI = 0 AND SUBSTR(STMT,48,1) IN (X'00', X'40') AND SUBSTR(STMT,39,2) = X'4040' WITH UR; The DB2 10 for z/OS ENFM processing code has been modified to recognize the problem data and correct it. This will 1 eliminate the aforementioned problem. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76248 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUECML PM76248 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76248 DSNUECML THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUECML LISTEND UK83757 COVER LETTER END UK83767 COVER LETTER START PROBLEM DESCRIPTION(S): PM73195 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * utility users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 at DSNUGSTB + x'1AD6' occurred * * when the first character of the SYSIN * * data set was an EBCDIC (code page 500) * * left parenthesis (x'4D') and the * * control statements were in EBCDIC. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User submitted utility control statements with EBCDIC (code page 500) in the SYSIN data set and the first character of the data set happened to be a left parenthesis (x'4D), which could also be recognized as a Unicode UTF-8 upper case letter 'M'. The control statements in the SYSIN data set were thus processed as Unicode UTF-8. A storage overlay happened when the utility parser tried to process those EBCDIC statements as UTF-8, which led to the ABENDS0C4 at DSNUGSTB OFFSET1AD6. Although in this case the control statements in the SYSIN data set ought to be processed as UTF-8, DB2 should fail the utility job with return code 8 instead of abending. Utility parser code was modified not to overlay storage when processing utility control statements containing unexpected data. This APAR also introduces the following changes to 1 DB2 10 for z/OS Utility Guide and Reference and DB2 Version 9.1 for z/OS Utility Guide and Reference, under the topic 'Utility control statements' (changes listed below are not final, the final changes in publication could be different): Control statement coding rules DB2 typically reads utility control statements from the SYSIN data set. DB2 can read LISTDEF control statements from the SYSLISTD data set and TEMPLATE control statements from the SYSTEMPL data set. The statements in these data sets must obey the following rules: *If the records are 80-character fixed-length records, DB2 ignores columns 73 through 80. *The records are concatenated before they are parsed; therefore, a statement or any of its syntactical constructs can span more than one record. No continuation character is necessary. However, if the input data set contains variable-length records, DB2 might interpret the part of a statement that is in column 1 as the continuation of the statement from the previous record. To avoid syntax errors, ensure that all syntactical constructs in utility control statements are properly delimited. Doing so is especially important for the first character in each record of a data set with variable-length records. *All control statements in a given data set must be written entirely in a single character set. Two character sets are supported, EBCDIC (code page 500) or Unicode UTF-8 (code page 1208). DB2 automatically detects and processes Unicode UTF-8 control statements if the first character of the data set is: A Unicode UTF-8 blank (x'20') A Unicode UTF-8 dash (x'2D') A Unicode UTF-8 upper case A through Z (x'41' through x'5A') In all other cases, the control statement data set is processed as EBCDIC. An informational message is issued to identify the character set that is being processed. | The following EBCDIC characters have the same hexadecimal | code point value as the Unicode UTF-8 characters J to P: | Hex Value EBCDIC character | 4A cent sign | 4B period | 4C less-than sign | 4D left parenthesis | 4E plus sign | 4F logical OR | 50 ampersand | If any of these characters are the first character in the | input data set, the control statement can be misinterpreted | as Unicode. This error is a utility syntax error. However, 1 | these characters might cause Unicode to EBCDIC translation | errors and abends before the syntax error is detected. After | the syntax error is detected, message DSNU005I might contain | indecipherable statements and message DSNU082I might identify | an indecipherable keyword. *The utility statement must start with the syntax for a utility. *Other syntactical constructs in the utility control statement describe options; you can separate these constructs with an arbitrary number of blanks. *The SYSIN stream can contain multiple utility control statements. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73195 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUGLDA PM73195 DSNUGLDB PM73195 DSNUGTIS PM73195 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73195 DSNUGLDA DSNUGLDB DSNUGTIS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGLDA DSNUGLDB DSNUGTIS LISTEND UK83767 COVER LETTER END UK83776 COVER LETTER START PROBLEM DESCRIPTION(S): PM77302 - **************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4-00000038 IN DSNTFRCV+09E4 * * DURING LPL RECOVERY. * **************************************************************** * RECOMMENDATION: * **************************************************************** During LPL/ GRECp recovery, If csect dsnibmoc is invoked, it may not always free the Program Recovery routine Entry (PRE). This results in orphan PRE remains in the PRE chain. if any subsequent 04Eabend occurred during log apply (or later) may results in program exception (Abend0C4) in DSNTFRCV because of 1 the orphan PRE entry. If the orphan PRE does not stay around then the original 04EAbend would be reported instead of this secondary 0C4Abend in DSNTFRCV. Since the secondary abend occurred in Funtional Recovery Routine (FRR), it results in abnormal termination of DB2 subsytem. DB2 LPL/GRECP log apply logic is modified so that each csect makes sure that it removes the Program Recovery Entry from the stack at the end of each csect. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77302 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIBMOC PM77302 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77302 DSNIBMOC THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIBMOC LISTEND UK83776 COVER LETTER END UK83784 COVER LETTER START PROBLEM DESCRIPTION(S): PM74501 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users * * of ALTER TABLE ALTER COLUMN SET DEFAULT * * and the current user-defined default * * constant(UDDC) is being altered to a new * * UDDC. * **************************************************************** * PROBLEM DESCRIPTION: ALTER TABLE ALTER COLUMN SET DEFAULT * * will result in a no operation when * * altering the default value from a * * zero-length string ('') to a blank * * string (' '). The resulting UDDC * * will be a zero-length string instead * * of a blank string. * **************************************************************** * RECOMMENDATION: * **************************************************************** ALTER TABLE ALTER COLUMN SET DEFAULT incorrectly ignores trailing blanks when comparing the current and new UDDC. For example, DB2 will not change the default value when altering the value from a zero-length string ('') to a blank string (' '). The resulting UDDC will be a zero-length string instead of the expected blank string. As a result, rows may contain unexpected values on subsequent INSERTs that 1 do not specify values for the altered column. ALTER TABLE ALTER COLUMN SET DEFAULT will be sensitive to trailing blanks when determining whether the current and new default constants are the same. The workaround is to first alter the default value to a constant having a non-blank character that is different from the current default constant. Then alter to the desired default value. Applying this APAR will not fix existing rows which contain the unexpected values as a result of the unchanged default value. Those rows may be updated with the correct value. ADDITIONAL KEYWORDS: SQLALTER INCORROUT SQLINCORR SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74501 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 PM74501 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74501 DSNXISB5 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXISB5 LISTEND UK83784 COVER LETTER END UK83787 COVER LETTER START PROBLEM DESCRIPTION(S): PM72655 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users that run mass * * delete followed by INSERT operations with * * no intervening COMMIT in the same unit of * * work on a COMPRESS YES table space may be * * exposed to this problem. * **************************************************************** * PROBLEM DESCRIPTION: RC00C9007E DSNIZLDR ERQUAL5004 * * RC00C90101 DSNIZLDR:5004 * * RC00C90101 DSNIRFNX ERQUAL5016 * **************************************************************** * RECOMMENDATION: * 1 **************************************************************** For users that perform mass deletes on a table which is eligible for data compression using COMPRESS ON INSERT logic, subsequent INSERTs may trigger the build of the compression dictionaries. When there is no COMMIT done after the mass delete, the object is essentially in drained state and the dictionary build proceeds synchronously under that unit of work. A subsequent rollback will undo updates to the header and dictionary pages on disk but the in memory copy of the compression dictionaries are still available. A following INSERT will make use of this dictionary copy to compress the data row. When the object is stopped and restarted there is no longer a dictionary available to decompress any such compressed rows. This leads to the RC00C9007E RC00C90101 ERQUAL5004 failures in DSNIZLDR. For this mass delete scenario, DB2 code has been corrected to disallow the backout of the compression build updates to the header, space map and dictionary pages. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72655 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIZLDL PM72655 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72655 DSNIZLDL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIZLDL LISTEND UK83787 COVER LETTER END UK83810 COVER LETTER START PROBLEM DESCRIPTION(S): PM69885 - **************************************************************** * USERS AFFECTED: ALL DB2 V10 z/OS users of Universal * * Table Space. * **************************************************************** * PROBLEM DESCRIPTION: Insert process encounters * * DSNT501I RC00C9009C (partition is * * full) message but the last physical * * page of the partition has not been * * used. * **************************************************************** * RECOMMENDATION: * * * **************************************************************** The insert transaction detects the end of partition prematurely before the actual end of the partition is 1 reached. As the result the INSERT PROCESS was terminated and the 00C9009C (Partition is full) message was issued before reaching the physical end of the partition. DB2 code is fixed to ensure available DASD space is properly utilized first, before the determination is made that the partition is full. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69885 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISUPI PM69885 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69885 DSNISUPI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISUPI LISTEND UK83810 COVER LETTER END UK83888 COVER LETTER START PROBLEM DESCRIPTION(S): PM74866 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and 10 for z/OS * * users with parallelism enabled. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E70005 in DSNXRBND M666 * * or DSNXEBR M662 when a query runs * * in parallel and when an error occurs. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E at DSNXEBR M662 or DSNXRBND M666 could happen when a query is running in parallel, and an error has occurred. In this case, DB2 should issue the appropriate SQLCODE, but DB2 abends instead. When a parallel child task need to report an SQLCODE, DB2 has a mechanism to have child tasks post the error in a common area. Later, when the parallel parent task checks the status of the child tasks, it should copy the SQLCODE over to parent task, so that DB2 can return this error to application. But for certain cases, DB2 did not copy the information from child tasks, yet just exited abnormally, which will cause the observed abend. DB2 has been fixed to handle the error case correctly by copying error SQLCA information from parallel child tasks to the parent task, so that later the error SQLCODE can be 1 propagated to application by parent. The observed abend no longer occurs. Additional Keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74866 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXREOJ PM74866 DSNXRFF PM74866 DSNXRFN PM74866 DSNXROJ1 PM74866 DSNXRSFN PM74866 DSNXRSGB PM74866 DSNXRT1J PM74866 DSNXSBUC PM74866 DSNXSIND PM74866 DSNXSING PM74866 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74866 DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1 DSNXRSFN DSNXRSGB DSNXRT1J DSNXSBUC DSNXSIND DSNXSING THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1 DSNXRSFN DSNXRSGB DSNXRT1J DSNXSBUC DSNXSIND DSNXSING LISTEND UK83888 COVER LETTER END UK83891 COVER LETTER START PROBLEM DESCRIPTION(S): PM73384 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of ROWSET cursor * * using RID list processing. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNICUMW:1002 * * occurred when a DELETE WHERE CURRENT OF * * rowset cursor is executed. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 DSNICUMW:1002 happened during DELETE WHERE CURRENT OF rowset cursor. The following scenario shows the abend case : . DECLARE CURSOR01 CURSOR WITH ROWSET POSITIONING WITH HOLD FOR SELECT DB2TIME FROM TABLEA WHERE DB2TIME <= : H FOR UPDATE OF DB2TIME ; . DELETE FROM TABLEA WHERE CURRENT OF CURSOR01; The reason for the abend because one row from the current rowset released its lock during the FETCH. This happened when the cursor was using RID list access and the RID list was stored in a workfile. When a FETCH finished with a RID list record and went to the next record, the last row in the previous RID list record released its lock when the first row in the next RID list was fetched. The lock was released due to an internal flag not being set correctly for the specified row. DB2 code was changed to make sure the lock was held for the specified row by correctly setting the internal flag. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73384 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNICREL PM73384 DSNXREOJ PM73384 DSNXRFF PM73384 DSNXRFN PM73384 DSNXRGBJ PM73384 DSNXROJ1 PM73384 DSNXRSFJ PM73384 DSNXRSFN PM73384 DSNXRSGB PM73384 DSNXRT1J PM73384 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73384 DSNICREL DSNXREOJ DSNXRFF DSNXRFN DSNXRGBJ DSNXROJ1 DSNXRSFJ DSNXRSFN DSNXRSGB DSNXRT1J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNICREL DSNXREOJ DSNXRFF DSNXRFN DSNXRGBJ DSNXROJ1 1 DSNXRSFJ DSNXRSFN DSNXRSGB DSNXRT1J LISTEND UK83891 COVER LETTER END UK83920 COVER LETTER START PROBLEM DESCRIPTION(S): PM71850 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS * * users of ROW CHANGE TIMESTAMP column when * * defined as GENERATED BY DEFAULT and * * CURRENT TIMESTAMP special register is * * specified in the insert VALUES clause * **************************************************************** * PROBLEM DESCRIPTION: When a ROW CHANGE TIMESTAMP column with * * GENERATED BY DEFAULT is populated from * * the CURRENT TIMESTAMP special register * * specified in the insert VALUES clause, * * DB2 mistakenly generates a new value * * for the column when it should be using * * the CURRENT TIMESTAMP value * **************************************************************** * RECOMMENDATION: * **************************************************************** When a ROW CHANGE TIMESTAMP column (RCTC) defined as GENERATED BY DEFAULT was populated from the CURRENT TIMESTAMP special register that was specified in the insert VALUES clause, DB2 mistakenly generated a new value for the column when it should have honored the CURRENT TIMESTAMP value. A sample recreation of this problem is shown below: CREATE TABLE TB1 ( TS1 TIMESTAMP NOT NULL GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP, TS2 TIMESTAMP NOT NULL ) INSERT INTO TB1 (TS1, TS2 ) VALUES (CURRENT TIMESTAMP, CURRENT TIMESTAMP) SELECT * FROM TB1 shows that the value in the TS1 RCTC column is slightly higher than that in TS2 (a non-RCTC column), because a value in the RCTC column was mistakenly regenerated by DB2. +---------------------------------------------------------+ | TS1 | TS2 | +---------------------------------------------------------+ | 2012-10-31-13.24.04.686109 | 2012-10-31-13.24.04.685998 | +---------------------------------------------------------+ 1 The root cause of this problem is a code bug in the insert path where DB2 was not differentiating the processing of GENERATED BY DEFAULT RCTC column when CURRENT TIMESTAMP is supplied by insert in the VALUES clause as opposed to when no column value is supplied. It should be mentioned that this problem of unnecessary timestamp regeneration for the RCTC column is theoretically also possible in the case where some supplied value in the insert for the GENERATED BY DEFAULT RCTC column happens to be exactly the same as the value of CURRENT TIMESTAMP at that instant. Code has been changed in the insert path to always honor CURRENT TIMESTAMP for the ROW CHANGE TIMESTAMP GENERATED BY DEFAULT column, when supplied in the insert VALUES clause. Additional keywords: SQLTIMESTAMP DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM71850 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISRTI PM71850 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM71850 DSNISRTI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISRTI LISTEND UK83920 COVER LETTER END UK83955 COVER LETTER START PROBLEM DESCRIPTION(S): PM75296 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DSNILDVC, DSNIPPHO, * * DSNIPTYM, or other DSNI* modules, after * * doing an ALTER SEGSIZE and running a * * REORG to convert a table space to a * * Universal Table Space (UTS). * **************************************************************** * RECOMMENDATION: * **************************************************************** When converting a table space to a UTS, the existing page set control blocks are assumed valid to continue using since no 1 attributes are changing which are considered "critical". However, a UTS requires a larger user suffix area, and the failure to switch to a new page set control block can result in various 0C4 abends in DSNI* modules. These abends may cause DB2 subsystem termination RC00D94001. Ordinarily, the reuse of the page set control block is not an issue since it typically gets freed when the table space is physically closed. One situation in which the block cannot be freed is when a notify exit is driven to load a compression dictionary - in this case, the exit fails to perform a logical close of the table space, so it retains a non-zero use count which prevents it from being freed. The code which determines whether an existing page set control block can continue to be used, even though some attributes have changed, has been modified to no longer allow the use of such a block if the required user suffix length is greater than the length of the one allocated. Additionally, the compression dictionary notify exit logic has been modified to ensure that a logical close of the table space is done, so that its control blocks can be freed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75296 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1OFA PM75296 DSNB1OPS PM75296 DSNIZLDR PM75296 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75296 DSNB1OFA DSNB1OPS DSNIZLDR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1OFA DSNB1OPS DSNIZLDR LISTEND UK83955 COVER LETTER END UK83961 COVER LETTER START PROBLEM DESCRIPTION(S): PM65869 - **************************************************************** * USERS AFFECTED: All users of REORG with KEEPDICTIONARY on * * table spaces with COMPRESSION and tables * * with EDITPROCS for DB2 10 and 9 for z/OS * * and have applied PM44787/UK73146/UK73145. * **************************************************************** 1 * PROBLEM DESCRIPTION: An ABEND04E RC00E4030F at * * DSNURLOG '3DE0'X or an INCORROUT can * * occur when running or having ran a * * REORG with the KEEPDICTIONARY option * * on table spaces with COMPRESSION and * * tables with EDITPROCS if * * PM44787/UK73146/UK73145 is applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** After PM44787/UK73146/UK73145 is applied the workarea for the compression of the data could be the same one that is used for decompressing the record in some cases. This would result in an overlay. Code has been changed so that the compressed record is not built in the same workarea as the decompressed record. Additional Keywords: INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM65869 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRLPG PM65869 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM65869 DSNIRLPG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRLPG LISTEND UK83961 COVER LETTER END UK83963 COVER LETTER START PROBLEM DESCRIPTION(S): PM75288 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of cascade * * delete rule, where there is after delete * * trigger on dependant table. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2005 when DSNITDLEtries * * to free a workarea during a delete to * * partent table. * **************************************************************** * RECOMMENDATION: * **************************************************************** During cascade delete process against child table, if the child table has After Delete trigger defined on and the trigger refers to old tranisition table or variables, a work file could be 1 created on the fly if total size of deleted records of child table was larger than a certain threshold. If the child table has columns of type LOB or ROWID, internal working area for the work file was not allocated with adequant size. As the consequnce, overlay mighthappen while moving transition record from the workfile to the working area. DB2 code is fixed to make sure working area is allocated with adequent size for transition record from the work file. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75288 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIATPR PM75288 DSNILTTV PM75288 DSNITCU PM75288 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75288 DSNIATPR DSNILTTV DSNITCU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIATPR DSNILTTV DSNITCU LISTEND UK83963 COVER LETTER END UK83995 COVER LETTER START PROBLEM DESCRIPTION(S): PM75590 - **************************************************************** * USERS AFFECTED: Users of DB2 for z/OS executing a * * BIND DEPLOY of a native SQL procedure * * who have PM53740/UK75385 applied. * **************************************************************** * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE * * FOLLOWING REPORTED SYMPTOMS: * * * * ABEND0C4 RC00000010 * * CSECT DSNSVSFB OFFSET0656 * * * * OR * * * * ABEND0C4 RC00000010 * * CSECT DSNTBAS2 OFFSET207C * * * * * * * * PROBLEM SCENARIO: * * * 1 * The reported error occurred when * * attempting a BIND DEPLOY of a * * native SQL procedure from a DB2 * * V10 subsystem to another V10 * * subsystem. The problem occurs when * * the first statement of the native * * SQL procedure is greater than two * * meg and PM53740/UK75385 is applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** SUMMARY OF DB2 EVENTS: DB2 was attempting to acquire more storage to accommodate the size of a large statement that is greater than two meg. This resulted in an error as the storage release mechanism was pointing to an incorrect address. The error will only occur when the first native SQL procedure statement is greater than 2 meg and PM53740/UK75385 is applied. PROBLEM CONCLUSION: DB2 has been fixed to point to the correct address when releasing storage acquired for large native SQL procedure statement usage. ADDITIONAL KEYWORDS: BIND DEPLOY SQLSTORAGE SQLSP SQLSTOREDPROC SQLNATIVESQLPL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75590 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTBAS2 PM75590 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75590 DSNTBAS2 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTBAS2 LISTEND UK83995 COVER LETTER END UK90054 COVER LETTER START PROBLEM DESCRIPTION(S): PM73175 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * pureXML. * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT may occur with XPATH when it * * uses the position predicate, //, along * * with repeated element names, such as * 1 * //b/b[1]. * **************************************************************** * RECOMMENDATION: * **************************************************************** For XPATH with position predicate, // and repeated element names, such as //b/b[1], a logic error occurs to associate the position counter with a wrong data node. This may result in more data nodes to be evaluated satisfying the position predicate and hence are returned in the output incorrectly. For example, suppose we have the following query SELECT XMLQUERY('$doc//b/b[1]' PASSING XMLPARSE(DOCUMENT '1 2 ') as "doc") FROM SYSIBM.SYSDUMMYU; Before this APAR fix, the result has two nodes 12. After this APAR fix, the result includes only one node 1. DB2 is fixed to correctly evaluate the position predicate in an XPATH that has // and repeated element names. Keywords: DB2INCORR/K SQLXML SQLINCORROUT SQLINCORR COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73175 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNNQOPM PM73175 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73175 DSNNQOPM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNQOPM LISTEND UK90054 COVER LETTER END UK90078 COVER LETTER START PROBLEM DESCRIPTION(S): PM76268 - **************************************************************** * USERS AFFECTED: All DB2 users using buffer pools with * * AUTOSIZE=YES attribute. * **************************************************************** * PROBLEM DESCRIPTION: Many MSGDSNB555I messages are generated * * when a buffer pool size is adjusted too * 1 * frequently by DB2. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a buffer pool is defined with AUTOSIZE=YES and the number of buffers needed is beyond the VPSIZE, DB2 may expand the buffer pool without waiting for Work Load Manager (WLM) to make the VPSIZE adjustment. This may cause the buffer pool size to be adjusted too frequently with many MSGDSNB555I messages. For a buffer pool with AUTOSIZE=YES, when DB2 needs more buffers than the defined VPSIZE, DB2 will search for buffers that are available for reuse instead of expanding the buffer pool. DB2 will allow WLM to be the only one to make automatic adjustments to the buffer pool size. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76268 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1GWB PM76268 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76268 DSNB1GWB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1GWB LISTEND UK90078 COVER LETTER END UK90088 COVER LETTER START PROBLEM DESCRIPTION(S): PM74019 - **************************************************************** * 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 RC00C90216 DSNIWNRF ERQUAL5380 * * 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: * 1 **************************************************************** While inserting into a spanned records workfile (record size exceeding 32706 bytes), an internal field representing record length overflowed and essentially became negative. As a result, the record was not correctly inserted - it was missing a variable length column. This missing portion was accidentally placed elsewhere in memory, potentially causing an overlay. This incorrect record was exposed during fetch from the workfile, which resulted in the aforementioned 04E abend. Other unpredictable abend symptoms are possible (either due to the possibility of overlay, or based on the incorrectly inserted record). Code has been changed to properly insert into spanned records workfiles. Additional keywords: SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM74019 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXSORI PM74019 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74019 DSNXSORI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXSORI LISTEND UK90088 COVER LETTER END UK90094 COVER LETTER START PROBLEM DESCRIPTION(S): PM75487 - **************************************************************** * USERS AFFECTED: All DB2 for z/OS users of RRSAF connected * * applications who have applied PE PTFs * * UK81228 or UK81229. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 in module DSN3RRSM may * * occur when an application connected to * * DB2 via RRSAF is cancelled or timed * * out. This ABEND0C4 is followed by an * * ABEND0C4 in DSNVEUS2 and DB2 may * * terminate with RC00E50702. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an application connected to DB2 with RRSAF is cancelled or 1 initiates time out abends while a z/OS RRS UR is still active, MVS context services and RRS will drive a DB2 RRSAF backout exit. An ABEND0C4 may occur in module DSN3RRSM. A subsequent ABEND0C4 may occur in DSNVEUS2 and DB2 may terminate with RC00E50702. This problem occurs when PTFs UK81228 or UK81229 for APAR PM70056 are installed. If DB2 commit or abort processing was interrupted by the application cancel or time out abend of the thread, DB2 requires an explicit commit or abort of the DB2 UR to release resources associated with the UR. With this APAR fix, there will be an opportunity for the application to abort the UR, or for MVS context end processing to abort the UR, or for DB2 deferred end of task processing to abort the UR. Additional symptoms: ATR306I msgATR306I Module DSN3RRSM has been updated to avoid this ABEND0C4 in DSN3RRSM. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75487 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSN3RRSF PM75487 DSN3RRSM PM75487 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75487 DSN3RRSF DSN3RRSM THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSN3RRSF DSN3RRSM LISTEND UK90094 COVER LETTER END UK90215 COVER LETTER START PROBLEM DESCRIPTION(S): PM75486 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of an SQL * * statement that contains a table expression * * or view with a set operator and a LIKE * * predicate matching to an index on * * expression. * **************************************************************** * PROBLEM DESCRIPTION: 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 * 1 * 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. * **************************************************************** * RECOMMENDATION: * **************************************************************** 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. An examples is shown below: CREATE TABLE T1 ( C1 VARCHAR(10) NOT NULL, C2 VARCHAR(10) ) CCSID UNICODE VOLATILE; CREATE INDEX IX1 ON T1 ( LOWER(C1, 'De_DE') ) NOT PADDED; INSERT INTO T1 VALUES('ABC', 'ABC'); INSERT INTO T1 VALUES('ABC', 'ABC'); SELECT * FROM (SELECT LOWER(C1, 'De_DE'), 1 FROM T1 UNION SELECT LOWER(C2, 'De_DE'), 2 FROM T1 ) TX(C1, C2) WHERE TX.C1 LIKE 'abc'; The query above should return 2 rows, while it only returns 1 row. 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. 1 Additional keywords: SQLUNION SQLPREDPUSHDOWN SQLINDEXONEXP SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLLIKE SQLINTERSECT SQLINTERSECTALL SQLEXCEPT SQLEXCEPTALL SQLUNIONALL SQLTABLEEXPR SQLVIEW SQLCTE COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75486 SPECIAL CONDITIONS: 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOW2D PM75486 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75486 DSNXOW2D THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: 1 MODULES DSNXOW2D LISTEND UK90215 COVER LETTER END UK90219 COVER LETTER START PROBLEM DESCRIPTION(S): PM73214 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of queries with * * UNION ALL. * **************************************************************** * PROBLEM DESCRIPTION: The total cost of an access path may * * not be accurately estimated for a query * * when the query contains a view or * * table expression with UNION ALL. * **************************************************************** * RECOMMENDATION: * **************************************************************** The total cost of an access path may not be accurately estimated for a query when the query contains a view or table expression with UNION ALL and the view or table expression satisfies all the following conditions: 1. The parent query block of the view or table expression requires a sort operation; for example, it contains an ORDER BY or GROUP BY clause. 2. The parent query block of the view or table expression references this view or table expression only. 3. There is no local predicate in the parent query block of the view or table expression or all the local predicates in the parent query block of the view or table expression can be pushed down into the view or table expression. For example, SELECT A.C1, A.C2, A.C3 FROM (SELECT C1, C2, C3 FROM T1 UNION ALL SELECT C1, C2, C3 FROM T2) A ORDER BY A.C1, A.C2, A.C3; The cost of the table expression A may not be rolled up into the total cost of the above query. The problem may prevent a query from being offloaded to IBM DB2 Analytics Accelerator. Additional keywords: 1 SQLACCESSPATH SQLPERFORMANCE SQLEXPLAIN SQLUNIONALL IDAAV2R1/K IDAAV3R1/K Code has been modified to correct the cost estimation of the queries described as above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM73214 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOTS PM73214 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73214 DSNXOTS THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOTS LISTEND UK90219 COVER LETTER END UK90237 COVER LETTER START PROBLEM DESCRIPTION(S): PM75927 - **************************************************************** * USERS AFFECTED: All IRLM220(HIR2220) and IRLM230(HIR2230) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DXRRL2E0 after termination * * of another IRLM in the group. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** IRLM may ABEND0C4 in DXRRL2E0 while processing a failed connection event for a peer member in a data sharing group. Recovery for the peer connection involves cleaning up waiting requests/structures in the deadlock workarea. An IRLM member may have residual information in its deadlock workarea if it was 1 the Global Deadlock Manager(GDM) before, and failed to cleanup properly due to a small timing window where disconnect from the Lock Structure is processed right before the deadlock GDM cleanup runs. Note: - This problem can happen in DB2 or IMS environments where IRLM is started manually (without ARM control). In those cases IRLM stays up (disconnected from the group) even after DB2 or all IMS subsystems have terminated. - This problem does not happen where IRLM is started with SCOPE=NODISCON option. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR prevents the ABEND0C4 in DXRRL2E0 while accessing Deadlock control block information for cleaning up a failed connections information. The 'waiting for' structures in the deadlock workarea (DLW0306I,DLW0307Q and DLW0308I) are cleaned correctly when the Global Deadlock Manager disconnects from a data sharing group. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM75927 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL2E0 PM75927 DXRRL2E1 PM75927 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75927 DXRRL2E0 DXRRL2E1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL2E0 DXRRL2E1 LISTEND UK90237 COVER LETTER END UK90271 COVER LETTER START PROBLEM DESCRIPTION(S): PM68704 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of XML. * **************************************************************** * PROBLEM DESCRIPTION: The following may occur when running * * CHECK DATA utility on XML data: * * * * ABEND0C4 RC00000004 in module DSNUKXCH * * offset2EE8 or offset1FE6 * 1 * * * ABEND04E RC00E70100 in module DSNNOCHX * * offsetM150 * **************************************************************** * RECOMMENDATION: * **************************************************************** When running CHECK DATA Utility on XML data, there is logic error in processing complex and large XML document which causes abend and DSNU017I message. This problem is more likely to occur when the size of an XML document is bigger than 1M bytes. The DB2 10 for z/OS code was modified to fix the logic error for processing complex and large XML document during CHECK DATA utiltiy. Additional keywords: XMLALL DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM68704 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 PM68704 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM68704 DSNNOCHX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNNOCHX LISTEND UK90271 COVER LETTER END UK90307 COVER LETTER START PROBLEM DESCRIPTION(S): PM76798 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of type 1 join * * and RID access * **************************************************************** * PROBLEM DESCRIPTION: Less rows than expected may be returned * * for a query using RID access on the * * outer table of a type 1 join and a sort * * is needed for the inner table * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output may be returned for a query that meets the following criteria. Less rows are returned than expected. 1. The table expression result is written to a workfile 1 for each outer table row. 2. A sort is needed for the table expression 3. RID access is used on the outer table. The PLAN_TABLE column PREFETCH shows 'L' for list prefetch. 4. The join is type 1 (inner or outer join using nested loop join) The problem is also dependent on the data in the tables. The following is an example where the problem may occur. CREATE TABLE T1 (C1 INT,C2 INT, C3 INT); CREATE TABLE T2 (C1 INT,C2 INT, C3 INT); CREATE INDEX IX1 ON T1(C1); CREATE INDEX IX2 ON T2(C1); INSERT INTO T1 VALUES (4,1,1); INSERT INTO T1 VALUES (5,2,2); INSERT INTO T2 VALUES (5,2,2); SELECT * FROM T1 INNER JOIN TABLE ( SELECT DISTINCT C1,C2,C3 FROM T2 WHERE T1.C1 = T2.C1 AND T1.C3 = T2.C3 AND T1.C2 = T2.C2) X ON 1 = 1 WHERE T1.C1 = 5 ; The problem occurs if the row from the outer table does not have a matching row from the table expression. DB2 has been fixed to reset the end of file correctly for each inner table workfile. The correct number of rows is returned. Additional keywords : SQLTABLEEXPR SQLJOIN SQLNLJ DB2INCORR/K INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76798 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXRBND PM76798 DSNXROJ1 PM76798 DSNXRT1J PM76798 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76798 DSNXRBND DSNXROJ1 DSNXRT1J THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXRBND DSNXROJ1 DSNXRT1J LISTEND UK90307 COVER LETTER END 1 UK90373 COVER LETTER START PROBLEM DESCRIPTION(S): PM72999 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI. * **************************************************************** * PROBLEM DESCRIPTION: SQLCODE -805 after applying UK79001 * * (V10) without binding the CLI/ODBC * * packages. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR reships the V10 fix for PM60340 and completes the HOLD information that was missing from APAR PM60340/PTF UK79001. PTF UK79001 was packaged to supersede UK72803, but the ++HOLD specified for UK72803 was not included in the HOLD ACTION SUMMARY REPORT. Hence, a separate ++HOLD ACTION is needed for UK79001. A ++Hold has been included with the PTF for this APAR. COMPONENT: 5740-XYR02-JDBAA17 APARS FIXED: PM72999 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DOCUMENTATION: This PTF introduces the following changes to DB2 ODBC externals: New DB2 ODBC for z/OS initialization keywords described as follows. LIMITEDBLOCKFETCH = 0 | 1 This keyword is a performance optimization keyword that specifies whether DB2 ODBC is to attempt limited block fetch when fetching result sets from the connected data source. 0 = Limited block fetch is not used. 0 is the default. 1 = DB2 ODBC attempts to use limited block fetch. If blocking is supported at the server for the result set that is being fetched, DB2 ODBC retrieves as many rows as it can fit in a query data block in a single fetch request. QUERYDATASIZE = integer This keyword specifies the amount of query data, in bytes, that DB2 returns on each FETCH operation when limited block fetch is enabled. The default value is 32767. Possible values are: 32767 294911 557055 819199 65535 327679 589823 851967 98303 360447 622591 884735 131071 393215 655359 917503 163839 425983 688127 950271 196607 458751 720895 983039 229375 491519 753663 1015807 262143 524287 786431 1048575 If you specify a value that is not a valid value, DB2 ODBC sets QUERYDATASIZE to the nearest valid value. Information about the new DB2 ODBC initialization keywords 1 and DB2 ODBC limited block fetch 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. DOCUMENTATION: *** Documentation for PM25678 (Version 10) A new initialization keyword, INTERRUPT, has been added to allow you to specify the interrupt processing mode when SQLCancel() is called to cancel the processing on a statement. Complete documentation for the SQLCancel() API will be provided in the DB2 10 for z/OS ODBC Guide and Reference and in the Information Management Software for z/OS Solutions Information Center. ACTION: *** Action for PM72999 (Version 10) This PTF includes the following updated DBRMs for the ODBC executable modules DSNAOCLI, DSNAOCLX, and DSNAO64C: DSNCLINF DSNCLIC1 DSNCLIMS DSNCLIQR DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only) After applying the PTF, all customers who use these modules need to bind a package from each of the DBRMs listed above. For example: BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLINF) ACTION(ADD) ENCODING(EBCDIC) BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIC1) ACTION(ADD) ENCODING(EBCDIC) BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIMS) ACTION(ADD) ENCODING(EBCDIC) BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIQR) ACTION(ADD) ENCODING(EBCDIC) BIND PACKAGE (.DSNAOCLI) MEMBER(DSNCLIV1) 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 packages 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. 1 ACTION: *** Action for PM32032 (Version 10) The following database request module (DBRM) is updated by this PTF: DSNCLIQR Application of this PTF requires a BIND PACKAGE for the above package. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site. ACTION: The following database request modules (DBRMs) are updated by this PTF: DSNCLINF DSNCLIC1 DSNCLIMS DSNCLIQR DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only) Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site. This PTF introduces two new DB2 ODBC initialization keywords LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block fetch. Limited block fetch is a performance optimization that enables applications to improve the performance of FETCH operations when connected to a local DB2 for z/OS server. If limited block fetch is not desired, no further action is necessary other than rebinding the DBRMs listed above; otherwise please note the following. When you enable limited block fetch, the data that is returned to your application might not reflect the data that has been committed to the source table. If your application fetches data from tables that are updated by other users, or if your application uses savepoints and issues ROLLBACK TO SAVEPOINT to manage transactions, you should disable limited block fetch. ACTION: This PTF updates DB2 ODBC for z/OS database request module (DBRM) DSNCLIC1. After you apply this PTF, you need to run the BIND PACKAGE command to recreate the package for DSNCLIC1. Failure to bind 1 the required package could result in SQLCODE -805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the prefix.SDSNSAMP data set for an example of how to perform the BIND command. ACTION: The following database request modules (DBRMs) for ODBC DB2 for z/OS are updated by this PTF: DSNCLIMS DSNCLIC1 Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the SDSNSAMP dataset for an example of how to perform the BIND command. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAOG0J PM72999 DSNAOCLI PM72999 DSNAOSDK PM72999 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72999 DSNAOG0J DSNAOCLI DSNAOSDK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAOC24 DSNAOC03 DSNAOC06 DSNAOC28 CLIMVSF6 DSNAOC27 DSNAOC22 DSNAOC14 DSNAOC15 DSNAOC1U DSNAOG02 DSNAOG24 DSNAOG03 DSNAOG04 DSNAOG1R DSNAOG05 DSNAOG06 DSNAOG28 DSNAOG08 DSNAOG0A DSNAOG1Q DSNAOG1S DSNAOG0C DSNAOG0E 1 DSNAOG0I DSNAOG0J DSNAOG0O DSNAOG1W DSNAOG25 DSNAOG0Q DSNAOG0R DSNAOG27 DSNAOG0S DSNAOG0T DSNAOG26 DSNAOG0U DSNAOG22 DSNAOG0W DSNAOG13 DSNAOG14 DSNAOG15 DSNAOG16 DSNAOG1V DSNAOG17 DSNAOG1U DSNAOCLI DSNAOTRC DSNAOC0G DSNAOC0F DSNAOC21 DSNAOC0P DSNAOC07 DSNAOG0G DSNAOG0F DSNAOG21 DSNAOG0P DSNAOG07 DSNAOC1L DSNAOG1L MACROS DSN@LIC1 DSN@LIMS DSN@LINF DSN@LIQR DSN@LIV1 DSNAOSDK LISTEND UK90373 COVER LETTER END UK90444 COVER LETTER START PROBLEM DESCRIPTION(S): PM72913 - **************************************************************** * USERS AFFECTED: All users of DB2 for z/OS who use IDAA * * (IBM DB2 Analytics Accelerator). * **************************************************************** * PROBLEM DESCRIPTION: DSNX890I message is encountered with * 1 * REASON 00C90614 when DB2 is started * * in ACCESS(MAINTENANCE) mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** During DB2 start-up processing in maintenance mode, DB2 attempts to start accelerator services. This leads to console message DSNX890I and DB2 accelerator services are not started. DB2 has been changed to disable accelerator services when DB2 is started in maintenance mode. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72913 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNTRSTE PM72913 DSNTSTRT PM72913 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72913 DSNTRSTE DSNTSTRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTRSTE DSNTSTRT LISTEND UK90444 COVER LETTER END UK90477 COVER LETTER START PROBLEM DESCRIPTION(S): PM72525 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users of * * plan table hints. * **************************************************************** * PROBLEM DESCRIPTION: DB2 may loop in DSNXOGP when a hint is * * provided that specifies * * QBLOCK_TYPE='CORSUB' in the child query * * block and a row in the parent query * * block with an ACCESSTYPE other than * * 'O'. * **************************************************************** * RECOMMENDATION: * **************************************************************** In order for DB2 to correctly process a subquery, the parent query block plan must agree with the child query block plan. Either both must specify correlated access or both must specify non-correlated access. 1 If an invalid hint is specified with QBLOCK_TYPE='CORSUB' in the subquery query block, and a row in the parent query block with ACCESSTYPE other than 'O', DB2 may loop in DSNXOGP. Additional Keywords: LOOP INFINITE ENDLESS SQLHINT SQLSUBQUERY SQLCORRSUBQ DB2 has been corrected to issue a +395 SQLCODE indicating the hint is invalid and proceed through regular query optimization to select the access path. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72525 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOPCO PM72525 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72525 DSNXOPCO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPCO LISTEND UK90477 COVER LETTER END UK90628 COVER LETTER START PROBLEM DESCRIPTION(S): PM74504 - **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of a * * classic partitioned table space under heavy * * insert operations in Datasharing * * environment. * **************************************************************** * PROBLEM DESCRIPTION: DB2 ABEND04E with RC00C90101 failure in * * DSNISMRS with ERQUAL5003 while * * performing INSERT statements from * * different DB2 members. * **************************************************************** * RECOMMENDATION: * **************************************************************** A spacemap page was regressed after lock escalation occurred on working partitions. The regression happens on a spacemap page which is chosen from a new partition which DB2 had not acquired the lock yet, but DB2 skipped to acquire the page plock on this spacemap page due to a misleading indication about the global lock state on the new partition. DB2 has been updated to independently determine the global lock state on the new partition before deciding to acquire the plock on the working spacemap page. COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM74504 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISMEX PM74504 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM74504 DSNISMEX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISMEX LISTEND UK90628 COVER LETTER END UK90637 COVER LETTER START PROBLEM DESCRIPTION(S): PM79150 - **************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: DB2 terminated with RC00D10251 after * * the offload task abended when all the * * active logs were full. * **************************************************************** * RECOMMENDATION: * **************************************************************** New archive parms in DSNZPARM were implemented which resulted in an ABEND837 RC08 during every log offload attempt. This continued until all the active logs were full and DB2 logging stopped with MSGDSNJ111E. When all the logs are full, the log writer does a synchronous, related task switch to the offload task (normally it is asynchronous). If the sync offload request abends, the estae in DSNJOFF6 will attempt to RETRY from the abend and re-drive the offload task. An -ARCHIVE LOG CANCEL OFFLOAD command was issued while the DSNJOFF6 estae was processing an ABEND837. The command abended the estae, which prevented the RETRY. This secondary abend was then returned to the log writer with an ABEND04E RC00E50013 as the request was synchronous, related. The log writer abend then caused DB2 to terminate with RC00D10251. DSNJW307 has been changed to issue a synchronous, unrelated task switch to the log offload task when all the active logs are full. If the log offload task abends and can not RETRY, the log writer will not be abended and will re-drive the offload task. New archive DSNZPARM values can be implemented with the -SET SYSPARM command and will be picked up during the next log offload attempt. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79150 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 DSNJW307 PM79150 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79150 DSNJW307 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNJW307 LISTEND UK90637 COVER LETTER END UK90642 COVER LETTER START PROBLEM DESCRIPTION(S): PM76697 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of universal * * tables space (UTS) with row level locking * **************************************************************** * PROBLEM DESCRIPTION: Table space scan with isolation level * * UR or with gross lock results in data, * * loss, such as online REORG, UNLOAD with * * shrlevel reference, etc. * **************************************************************** * RECOMMENDATION: * **************************************************************** When escalation occurred on the UTS table space with row level locking, the logging of data row and its space map update was not consistent. The space map page update log record generated under the lock escalation was in redo format which direct roll back process to update space map page based on the activities of data row. However, the log record generated from the data row was set up to direct roll back process to process space map page update based on the log record of space map page itself. As a result, the space map page status was not changed through roll back process. For the case that all the rows were deleted from the page can still have empty page status on the space map page after roll back process even all the data rows are reinserted back to the page. Utilities such as REORG SHRLEVEL REFERENCE with SORTDATA NO option will not unload thus page and data lost will occurred. The CHECK INDEX utility can detect those inconsistency in the space map page, and REORG with SORTDATA NO can fix the inconsistency plus avoid the data loss. Alter Tablespace Lockmax 0 to disable lock escalation is a workaround, to prevent the problem from happening. DB2 code is modified to make sure UNDO/REDO log records is 1 written for space map page update if there is lock escalation occurs. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76697 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNISGSU PM76697 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76697 DSNISGSU THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISGSU LISTEND UK90642 COVER LETTER END UK90662 COVER LETTER START PROBLEM DESCRIPTION(S): PM77518 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS who have * * queries containing OR predicates where * * range-list index scan is chosen * * (ACCESSTYPE='NR' in the PLAN_TABLE) * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output (no rows or fewer * * than expected rows returned) can occur * * for a query containing OR predicates * * where the predicates are all on the * * same table and map to the same index * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output (no rows or fewer than expected rows returned) can occur for a query containing OR predicates where the predicates are all on the same table and map to the same index. When multiple overlapping ranges reference some of the same literal values but have different operators, incorrect output can occur. For example: SELECT C1, C2, C3, C4 FROM T1 WHERE C1 = 100 AND C2 = 'A' AND ((C3 >= 'TEST' AND C3 < 'ZZZZ') OR (C3 > 'TEST' AND 1 C3 <= 'ZZZZ')) An index exists on (C1,C2,C3). Ranges (C3 >= 'TEST' AND C3 < 'ZZZZ') and (C3 > 'TEST' AND 'C3 <= 'ZZZZ') both reference literal values 'TEST' and 'ZZZZ' but use different operators. The operators are not handled properly in this situation. Additional Keywords: DB2INCORR/K SQLINCORR SQLINCORROUT INCORROUT RANGELIST SQLOR SQLGT SQLGE SQLLT SQLLE Code is changed to handle the operators correctly in the situation described above. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77518 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXOSRL PM77518 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77518 DSNXOSRL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOSRL LISTEND UK90662 COVER LETTER END UK90663 COVER LETTER START PROBLEM DESCRIPTION(S): PM69713 - **************************************************************** * USERS AFFECTED: All users of DB2 for z/OS who have queries * * containing a join, OR predicates, and * * multiple IN-list predicates on the same * * column * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output can occur for a query * * containing a join, OR predicates, and * * multiple IN-list predicates on the same * * column * **************************************************************** * RECOMMENDATION: * **************************************************************** Incorrect output can occur for a query containing a join and multiple IN-list predicates on the same column that are part of OR compound predicates involving columns from multiple tables. If the IN-lists contain only literals and start with the same value, but the IN-lists are not identical, then incorrect output may occur. DB2 may incorrectly determine 1 during predicate localization that the predicates are the same and could remove one of those predicates. For example: SELECT T1.C1, T1.C2, T1.C3, T2.C1, T2.C2, T2.C3 FROM T1, T2 WHERE T1.C1 = T2.C1 AND ((T2.C2 = 'AA' AND T1.C3 NOT IN (5,6,9) AND T1.C3 < 50) OR (T2.C2 = 'BB' AND T1.C3 NOT IN (5,7,11) AND T1.C3 < 50)) The two IN-list predicates (in this case, NOT IN) both begin with literal value '5', but the IN-lists are not the same. Additional Keywords: DB2INCORR/K SQLINCORROUT SQLINCORR INCORROUT SQLIN INLIST SQLOR Code is added to compare each IN-list element when the IN-lists contain all literal values before assuming that two IN-list predicates are identical. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM69713 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM71904: See PM71904 APAR/PTF text for additional information about why a REBIND is necessary. PM71904 corrects a problem of poor query performance for a query with a predicate or predicates on a timestamp column inside an OR 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 PM71471: See PM71471 APAR/PTF text for additional information about why a REBIND is necessary. PM71471 corrects a predicate localization problem when there is an EXISTS subquery in the CASE expression of the select 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 1 affected by this change. DB2BIND: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM69713 corrects a problem where incorrect output can occur on a query if there are: 1. two or more predicates with IN-lists on the same column; 2. the predicates are involved in compound OR predicates; and 3. the OR predicates involve columns from more than 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 DSNXOPPD PM69713 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM69713 DSNXOPPD THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPPD LISTEND UK90663 COVER LETTER END UK90674 COVER LETTER START PROBLEM DESCRIPTION(S): PM77557 - **************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS * * users of the LOAD utility with delimited * * input and vargraphic unicode columns. * **************************************************************** * PROBLEM DESCRIPTION: In DB2 V9 ABEND04E RC00E20005 DSNSVBK * * OFFSET09AC and in DB2 V10 ABENDS0C4 * * DSNSCON2 OFFSET15A4 when using the * * LOAD utility with delimited input * * on a unicode table with nullable * * vargraphic columns. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** A LOAD DATA FORMAT DELIMITED on a unicode table with a nullable vargraphic column abended with an ABEND04E RC00E20005 DSNSVBK +x'09AC' (V9) or an ABEND0C4 DSNSCON2 +x'15A4' (V10). The LOAD utility was interpreting the length of the nullable vargraphic field incorrectly because it was not recognizing the delimited input data, causing a storage overlay. In some cases, the overlay caused DB2 to crash with MSGDSNV086E RC00D94001. 1 Additional Keywords: DB2OVRLAY/K DB2OVRLAY/M Code has been modified to correctly process delimited data for nullable vargraphic columns in a unicode table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77557 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNURWBG PM77557 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77557 DSNURWBG THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNURWBG LISTEND UK90674 COVER LETTER END UK90677 COVER LETTER START PROBLEM DESCRIPTION(S): PM73348 - **************************************************************** * USERS AFFECTED: All users of DB2 UDB for z/OS Version 9 * * ODBC/CLI and DB2 10 for z/OS ODBC/CLI. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 or SIGABRT from * * SQLDisconnect() following * * SQLCODE -924 RC00F30018. * **************************************************************** * RECOMMENDATION: * **************************************************************** If SQLFreeStmt(SQL_DROP) fails with SQLCODE -924 RC00F30018, all storage acquired for the statement handle will be released, but the statement handle itself will remain allocated until the connection with which the statement is associated is disconnected. When the statement handle is deallocated during disconnect, the driver code does not always check for NULL pointers for storage that had already been freed, resulting in ABEND0C4 or SIGABRT. When deallocating a statement handle, code has been modified to always check for null pointers and bypass cleanup if pointer is set to null. COMPONENT: 5740-XYR02-JDBAA17 APARS FIXED: PM73348 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAOG02 PM73348 1 DSNAOCLI PM73348 DSNAOSDK PM73348 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM73348 DSNAOG02 DSNAOCLI DSNAOSDK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAOG02 DSNAOCLI MACROS DSNAOSDK LISTEND UK90677 COVER LETTER END UK90699 COVER LETTER START PROBLEM DESCRIPTION(S): PM75165 - **************************************************************** * USERS AFFECTED: All DB2 9 and 10 users. * **************************************************************** * PROBLEM DESCRIPTION: Storage overlaid with the string * * '3FDA4'x. This can result in ABENDs * * such as * * * * ABEND0C4 RC38 AT DSNSCON2 OFFSET 1608 * * * * Other ABEND symptoms possible * **************************************************************** * RECOMMENDATION: * **************************************************************** When a remote statement encounters an SQL condition, the SQL connection information (of the condition) is appended to the diagnostics block at the requester. Normally, only the connection from the previous statement is saved, but in the error case, the connections accumulated in the diagnostics block across statements. This eventually caused an internal field to wrap and become negative, which in turn lead to a storage overlay that resulted in an ABEND. Example: CONNECT TO LOCATION2; SELECT * FROM LOCATION1.USER01.TABLE01; [SELECT1] SELECT * FROM LOCATION1.USER01.TABLE01; [SELECT2] 1 In the example above, [SELECT1] encounters SQLCODE -204, and the connection (LOCATION2) is appended to LOCATION1's diagnostics block. However, the LOCATION1 connection from [SELECT1] is preserved when [SELECT2] again encounters SQLCODE -204, and the internal field recording the number of connections recorded thus far is incremented to 2. When a large number of such statements are executed in succession, the internal counter continues to be incremented and eventually wraps to become negative, leading to a storage overlay. DB2 code has been corrected to no longer preserve the SQL connections in the diagnostics block across SQL statements at the requester site. The internal field in question will therefore not become negative due to wrapping. ADDITIONAL KEYWORDS: SMCOVERLAY DB2OVRLAY/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75165 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 PM75165 DSNXEADW PM75165 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75165 DSNLZRCD DSNXEADW THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZRCD DSNXEADW LISTEND UK90699 COVER LETTER END UK90722 COVER LETTER START PROBLEM DESCRIPTION(S): PM75154 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of ALTER TABLE with * * multiple ADD COLUMN clauses specified * * in one statement. * **************************************************************** * PROBLEM DESCRIPTION: ALTER TABLE may result in ABEND04E * * RC00E2000F AT DSNXIATB.DSNSVSFB * * OFFSET0858 when the statement * * contains more than one ADD COLUMN * * clause. * 1 **************************************************************** * RECOMMENDATION: * **************************************************************** ALTER TABLE may result in ABEND04E RC00E2000F AT DSNXIATB.DSNSVSFB OFFSET0858 when the statement contains more than one ADD COLUMN clause. Other unpredictable results, such as storage overlays, may occur. The error is due to insufficient storage allocated for an internal control block. Sufficient storage has been allocated for the internal control block to prevent the reported problem when adding multiple columns in one ALTER TABLE statement. ADDITIONAL KEYWORD: SQLALTER DB2OVRLAY/K SMCOVERLAY COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75154 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIATB PM75154 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75154 DSNXIATB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIATB LISTEND UK90722 COVER LETTER END UK90725 COVER LETTER START PROBLEM DESCRIPTION(S): PM77236 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users of segmented * * tablespaces who has a specified MAXROWS * * under row-level locking. * **************************************************************** * PROBLEM DESCRIPTION: Unexpected Growth of segmented * * tablespaces under massive concurrent * * delete and update operations. * **************************************************************** * RECOMMENDATION: * **************************************************************** Under the following combination, the segmented TS can grow: (1) The TS object is a Classic segmented TS (2) Row-Level-Locking is in affect 1 (3) Multiple units-of-work are updating the same page at the same time and the total RIDs aready reached the MAXROWS limit which in this customer case is 9 rows in them. (4) Some change must be affected holes to shrink or to delete row in combination with record grows Today, DB2 code verified the MAXROWS limit and took an overflow path without fully using the adequate CFS storage. DB2 code is modified to ignore the maxrows checking for UPDATE operation. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77236 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 PM77236 DSNISGRT PM77236 DSNISMRT PM77236 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77236 DSNIREPR DSNISGRT DSNISMRT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIREPR DSNISGRT DSNISMRT LISTEND UK90725 COVER LETTER END UK90728 COVER LETTER START PROBLEM DESCRIPTION(S): PM78210 - **************************************************************** * USERS AFFECTED: DB2 10 for z/OS users in new function mode * * when all of the following conditions are * * true: * * o DSNZPARM SPRMRRF is set to DISABLE * * o The CREATE TABLE statement is specified * * with the BUFFERPOOL clause * * o The CREATE TABLE statement defines an * * inline LOB column * **************************************************************** * PROBLEM DESCRIPTION: DELETE of a row containing an inline * * DBCLOB may result in ABEND04E 00C90101 * * DSNOLDEL 5005. * **************************************************************** * RECOMMENDATION: * **************************************************************** DELETE may result in ABEND04E 00C90101 DSNOLDEL 5005 when the row being deleted contains an inline LOB column. Other 1 operations such as DML, LOAD, REORG and REPAIR may also result in incorrect output, abends, or other unexpected results when the implicit base table space is incorrectly defined with SYSTABLEPART.FORMAT set to blank, indicating Basic Row Format (BRF). The base table space for tables containing inline LOBs should always be Reordered Row Format(RRF). However DB2 may have incorrectly defined the table space as BRF when all of the following are true: o DSNZPARM SPRMRRF is set to DISABLE o The CREATE TABLE statement is specified with the BUFFERPOOL clause o The CREATE TABLE statement defines an inline LOB column PM78210 fixes CREATE TABLE to define implicit table spaces as RRF when all of the following conditions are true: o DSNZPARM SPRMRRF is set to DISABLE o The CREATE TABLE statement is specified with the BUFFERPOOL clause o The CREATE TABLE statement defines an inline LOB column This APAR does not fix existing objects. A query, such as the sample query below may be used to determine whether table spaces containing tables with inline LOB columns have partitions which are in BRF. Affected table spaces must be dropped and recreated after this apar is applied. SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION FROM SYSIBM.SYSCOLUMNS COL, SYSIBM.SYSTABLES TAB, SYSIBM.SYSTABLEPART TPT WHERE ( ( COL.DATATYPEID = 404 OR COL.DATATYPEID = 408 OR COL.DATATYPEID = 412 OR COL.SOURCETYPEID = 404 OR COL.SOURCETYPEID = 408 OR COL.SOURCETYPEID = 412 ) AND COL.TBCREATOR = TAB.CREATOR AND COL.TBNAME = TAB.NAME AND TAB.DBNAME = TPT.DBNAME AND TAB.TSNAME = TPT.TSNAME AND COL.LENGTH > 4 AND TPT.FORMAT = ' ' ); ADDITIONAL KEYWORDS: RC00C90101 ABNDID5005 DB2LOB SQLLOB INCORROUT SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78210 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: PM78210 fixes CREATE TABLE to define implicit table spaces in reordered row format(RRF) when all of the following conditions are true: o DSNZPARM SPRMRRF is set to DISABLE o The CREATE TABLE statement is specified with the BUFFERPOOL clause o The CREATE TABLE statement defines an inline LOB column This APAR does not fix existing objects. A query, such as the sample query below may be used to determine whether table spaces containing tables with inline LOB columns have partitions which are in basic row format (BRF). Affected table spaces must be dropped and recreated after this apar is applied. SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION FROM SYSIBM.SYSCOLUMNS COL, SYSIBM.SYSTABLES TAB, SYSIBM.SYSTABLEPART TPT WHERE ( ( COL.DATATYPEID = 404 OR COL.DATATYPEID = 408 OR COL.DATATYPEID = 412 OR COL.SOURCETYPEID = 404 OR COL.SOURCETYPEID = 408 OR COL.SOURCETYPEID = 412 ) AND COL.TBCREATOR = TAB.CREATOR AND COL.TBNAME = TAB.NAME AND TAB.DBNAME = TPT.DBNAME AND TAB.TSNAME = TPT.TSNAME AND COL.LENGTH > 4 AND TPT.FORMAT = ' ' ); COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXICTB PM78210 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78210 DSNXICTB THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXICTB LISTEND UK90728 COVER LETTER END UK90746 COVER LETTER START PROBLEM DESCRIPTION(S): PM77100 - **************************************************************** * USERS AFFECTED: All DB2 10 users of CP parallelism and * * performance trace IFCID 222. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 DSNXPDST 0C06 when * 1 * when running CP parallelism queries * * with performance trace IFCID 222 on * **************************************************************** * RECOMMENDATION: * **************************************************************** If performance trace IFCID 222 is turned on during package-level cleanup processing for packages with CP parallelism queries, DB2 will write the package name in IFCID 222. In the error case, a pointer referencing the package was not set properly, leading to the symptom ABEND. The pointer in question is now set correctly for the cases where it was previously not set. Additional Keywords: SQLPARALLELISM DB2PARALL/K SQLCPUP IFCID222 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77100 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXEUF0 PM77100 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77100 DSNXEUF0 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXEUF0 LISTEND UK90746 COVER LETTER END UK90797 COVER LETTER START PROBLEM DESCRIPTION(S): PM77488 - **************************************************************** * USERS AFFECTED: All DB2 V10 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4-04 in DSNTLDEA. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may terminate with ABEND0C4-04 in DSNTLDEA when a deadlock between two work units is reported and the victim thread control block storage is not valid any more at that time when deadlock Exit is driven. A Functional Recovery Routine (FRR) in DSNTLDEA stored register13 incorrectly causing ABEND0C4 in the FRR and resulting in DB2 termination with RC00E80100. This APAR corrects the recovery logic in DSNTLDEA to handle any abends in the Deadlock reporting section in the Deadlock Exit. This APAR also corrects the logic to reference agent control block storage while validating a DB2 agent, to avoid ABEND0C4 in DSNTLDEA. 1 COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77488 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 PM77488 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77488 DSNTLDEA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNTLDEA LISTEND UK90797 COVER LETTER END UK90811 COVER LETTER START PROBLEM DESCRIPTION(S): PM77997 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users who have applied * * PM64195 / UK82056 * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C9 RC00000009 DSNKCEST OFFSET3B2C * * occurred during BIND or PREPARE of an * * SQL statement involving a large index * * and PM64195 / UK82056 was previously * * applied. * **************************************************************** * RECOMMENDATION: Apply the corrective PTF when available. * **************************************************************** After PM64195 / UK82056 is applied, ABEND0C9 RC00000009 may occur when SQL statement, which involves a large index, is bound or prepared. Division overflow occurred because the quotient exceeded 32 bit storage. PM64195 fixed index probing algorithm to provide more accurate estimates, as noted by Column CARDF in EXPLAIN table DSN_COLDIST_TABLE. Additional Keywords: SQLACCESSPATH SQLPERFORMANCE DB2 has been updated to use 64 bit division. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77997 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKCEST PM77997 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77997 DSNKCEST THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKCEST LISTEND UK90811 COVER LETTER END UK90833 COVER LETTER START PROBLEM DESCRIPTION(S): PM76888 - **************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C20304 in DSNB1WFO when * * running a LOAD or REORG utility with * * the PREFORMAT option. * **************************************************************** * RECOMMENDATION: * **************************************************************** When run with the PREFORMAT option, the LOAD and REORG utilities will issue a force-write request. For a non-partitioned pageset with multiple data sets, the force-write logic will make an invalid check for a held write drain, which results in an ABEND04E RC00C20304 in DSNB1WFO. The force-write logic has been modified to correctly check for a write drain when the object is a multi-piece non-partitioned table space or index. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76888 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNB1WFO PM76888 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76888 DSNB1WFO THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNB1WFO LISTEND UK90833 COVER LETTER END UK90840 COVER LETTER START PROBLEM DESCRIPTION(S): PM60449 - 1 **************************************************************** * USERS AFFECTED: All HIR2220(IRLM220) and HIR2230(IRLM230) * * users data sharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: ABEND178 IN IXLM1REC MODULE=IXLR1BUN * * issued and XCF group members stalled. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** when a DBMS thread is going through commit/de-allocation, it will result in UNLOCK request sent by IRLM to XES for all locks currently being held by that thread. IRLM does batch unlock processing where it calls IXLLOCK(PROCESSMULT) request with MODE(NORESPONSE) to XES. If a thread was holding millions of locks, IRLM SRBs running non-preemptible mode could occupy a processor for long time. In a uni-processor environment this could result in lot of suspensions and storage backup in XES to process those multiple batches of unlocks. It can cause ABEND178 in RSM cannot run its own work to get or replenish real storage frames. GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR changes IRLM batch unlock processing when a thread is holding more than 128K locks. The unlock request will run as a queued request under IRLM SRB and would do status STOP SRB after running for some time. This SRB will continue when this SRB is resumed again. This will let other higher priority work from RSM and XES to run, which should improve conditions that results in a hang. COMPONENT: 5695-16401-HIR2230 APARS FIXED: PM60449 SPECIAL CONDITIONS: COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DXRRL130 PM60449 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM60449 DXRRL130 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DXRRL130 LISTEND UK90840 COVER LETTER END UK90883 COVER LETTER START PROBLEM DESCRIPTION(S): PM76889 - 1 **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of RECOVER * * TABLESPACE TORBA or TOLOGPOINT with DSNUM * * or using LISTDEF with PARTLEVEL. * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU556I, ABEND04E RC00E40100, * * ABENDS0C4 RC0000003A or other * * unpredictable results during a part * * level point in time (PIT) RECOVER on a * * partitioned table space after a new * * partition was added. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A new partition was added to a classic partitioned table space or a partition-by-range table space (PBR) by an ALTER ADD PART, or to a partition-by-growth table space (PBG) by partition growth. A PIT RECOVER with DSNUM or using LISTDEF with PARTLEVEL recovered this table space to a point before the partition was added. The RECOVER failed with message DSNU556I - RECOVER CANNOT PROCEED FOR TABLESPACE ... or abended with ABEND04E RC00E40100 at DSNUCACR OFFSET3128 or ABEND0C4 RC0000003A at DSNB1DCM OFFSET0902, or other unpredictable results due to a logic error when searching the SYSIBM.SYSCOPY table. The problem would also occur for PIT RECOVER to a point after the partition was added and no full image copy was taken for this new part. The RECOVER code has been modified to improve the handling of added partitions when they are recovered to a prior point in time. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM76889 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNUCASA PM76889 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM76889 DSNUCASA THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUCASA LISTEND UK90883 COVER LETTER END UK90966 COVER LETTER START PROBLEM DESCRIPTION(S): PM77332 - 1 **************************************************************** * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of * * spatial support. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output for a row not found * * might happen, when a spatial UDF is * * used in a SELECT statement after this * * SELECT statement had successfully * * returned a row from previous fetch. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following example can illustrate the problem. A spatial UDF is used in the following simple query. Table T1 has two columns ID and SHAPE, and it only contains one row which qualifies the following predicate when HV1 is set to 61.0 and HV2 is set to 63.0. EXEC SQL DECLARE W_CSR CURSOR FOR SELECT ID FROM T1 WHERE DB2GSE.ST_CONTAINS( SHAPE,DB2GSE.ST_POINT ( :HV1, :HV2, 1)) = 1 FETCH FIRST 1 ROWS ONLY WITH UR ; I = 1; DO WHILE ( I<=2 ); EXEC SQL OPEN W_CSR ; EXEC SQL FETCH W_CSR INTO :HID; PUT SKIP LIST ('MESSAGE HERE', HID, SQLCODE); EXEC SQL CLOSE W_CSR ; I = I + 1 ; END; Inside the loop, the first iteration returns a correct value for column ID, but the second iteration returns SQLCODE +100 for row not found incorrectly when the same HV1 and HV2 input are used. DB2 does not handle the spatial UDF properly during the CLOSE W_CSR cursor time after the first iteration is finished. A residual value inside the internal structure of the spatial UDF makes the second iteration return row not found incorrectly. DB2 code has been changed to address this incorrout issue when a spatial UDF is used in a query. Additional Keywords: DB2INCORR/K SQLINCORR INCORROUT SQLINCORROUT SQLSPATIAL COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77332 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM DB2BIND: ***Action for PM77332: PM77332 corrects a problem of incorrout when spatial UDF is used in a 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. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXGUDF PM77332 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77332 DSNXGUDF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXGUDF LISTEND UK90966 COVER LETTER END UK90990 COVER LETTER START PROBLEM DESCRIPTION(S): PM62002 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN * * job for ENFM processing. * **************************************************************** * PROBLEM DESCRIPTION: During the DB2 10 for z/OS ENFM process * * (job DSNTIJEN) the ENFM REORGs issue * * DSNU428I messages indicating that image * * copies were taken. Following DSNU400I * * messages indicate that zero pages were * * copied. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** During the DB2 10 for z/OS ENFM process we process many catalog and directory table spaces via an ENFM REORG. These REORGs do not take inline image copies but messages MSGDSNU428I and MSGDSNU400I are issued indicating that we do. The DSNTIJEN ENFM*7 steps do the ENFM REORG processing. During the REORG SWITCH phase MSGDSNU428I is issued to indicate that the image copy was successful. A following MSGDSNU400I message says that zero pages were processed for the COPY that was taken. The DSNTIJEN ENFM*9 steps that follow the ENFM*7 steps are there to image copy all of the necessary table spaces to 1 ensure recoverability. Code has been modified so that it will no longer issue the DSNU428I and DSNU400I messages during the ENFM REORGs (the ENFM*7 steps of the DSNTIJEN job). COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62002 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: The PTF for APAR PM62002 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 DSNTIJEN PM62002 DSNUGUCA PM62002 DSNURORG PM62002 DSNURSWD PM62002 DSNURSWT PM62002 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62002 DSNTIJEN DSNUGUCA DSNURORG DSNURSWD DSNURSWT THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNUGUCA DSNURORG DSNURSWD DSNURSWT MACROS DSNTIJEN LISTEND UK90990 COVER LETTER END UK90993 COVER LETTER START PROBLEM DESCRIPTION(S): PM72492 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of the RESTORE * * SYSTEM utility. * **************************************************************** 1 * PROBLEM DESCRIPTION: 1. The RESTORE SYSTEM utility * * incorrectly caused table space * * DSNDB01.SPT01 to be put into * * advisory REORG-pending(AREOR) status. * * 2. The RESTORE SYSTEM utility failed * * with MSGDSNU1631I. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** This APAR addresses the following problems which are caused by premature access of DB2 data by DB2 system tasks when the system has been brought up in system recover pending mode in preparation for the RESTORE SYSTEM utility: 1. RESTORE SYSTEM completes successfully but incorrectly places directory table space DSNDB01.SPT01 in advisory REORG-pending (AREOR) status. 2. RESTORE SYSTEM fails with MSGDSNU1631I (RESTORE SYSTEM UTILITY FAILED BECAUSE THE CALL TO DFSMSHSM FAILED) and RC8. The HSM activity logs show that the restore of one of the volumes in the data copy pool failed (because it had been allocated by DB2) with the following message: ARC1803E THE FOLLOWING VOLUME(S) FAILED DURING FAST REPLICATION RECOVERY OF COPY POOL Additional keywords: DSNU1631I MSGARC1803E RC08 The DB2 system tasks have been corrected to avoid premature access of DB2 data when the system has been brought up in system recover pending mode in preparation for the RESTORE SYSTEM utility. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM72492 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ACTION: Prior to the application of this PTF, on the 'CONNECT TO USER USING ' SQL statement, lower case characters in the userid and password in Japanese Katakana CCSIDs (290, 930, 5026, 1390 or 8482) were sent to System Authorization Facility (SAF) interface unchanged. With the application of this PTF, the lower case characters will be folded to upper case before the ID and password are given to the SAF interface. COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNIRTSU PM72492 DSNIRTSX PM72492 DSNLTACC PM72492 DSNLTSEC PM72492 DSNUGUCA PM72492 DSNXACTM PM72492 DSNXECNT PM72492 DSN3ID30 PM72492 DSN3TC30 PM72492 1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72492 DSNIRTSU DSNIRTSX DSNLTACC DSNLTSEC DSNUGUCA DSNXACTM DSNXECNT DSN3ID30 DSN3TC30 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIRTSU DSNIRTSX DSNLTACC DSNLTSEC DSNUGUCA DSNXACTM DSNXECNT DSN3ID30 DSN3TC30 LISTEND UK90993 COVER LETTER END UK90995 COVER LETTER START PROBLEM DESCRIPTION(S): PM62834 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of Referential * * Integrity (RI) in conjunction with index * * include column * **************************************************************** * PROBLEM DESCRIPTION: When Referential Integrity in * * conjunction with index included column * * is being used, the following symptoms * * may occur, * * 1. SQLCODE -531 when attempting to * * update the index included column; * * 2. ABEND04E RC00C90101 DSNIRELU * * ERQUAL5007 * * 3. SQLCODE -531 is expected, but get 0 * * return code and leave orphan rows * * in child table when updating parent * * key. * * Other related symptoms are also * * possible. * **************************************************************** * RECOMMENDATION: * **************************************************************** When doing SQL statement like UPDATE which involves RI process with index include column, several symptoms may occur due to DB2's erroneously handling the processing behavior with the included column. DB2 has been fixed in several paths of handling RI processing in conjunction with index include column. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM62834 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 DSNIKESR PM62834 DSNIREFS PM62834 DSNIRELU PM62834 DSNIRELV PM62834 DSNIRICH PM62834 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM62834 DSNIKESR DSNIREFS DSNIRELU DSNIRELV DSNIRICH THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIKESR DSNIREFS DSNIRELU DSNIRELV DSNIRICH LISTEND UK90995 COVER LETTER END UK91030 COVER LETTER START PROBLEM DESCRIPTION(S): PM72201 - **************************************************************** * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS * * users of ALTER INDEX ALTER BUFFERPOOL. * **************************************************************** * PROBLEM DESCRIPTION: ALTER INDEX ALTER BUFFERPOOL may * * result in ABEND04E RC00C200BB AT * * DSNB1OPP OFFSET 57F6 when executed * * concurrently with ALTER TABLESPACE * * ALTER BUFFERPOOL. * **************************************************************** * RECOMMENDATION: * **************************************************************** ALTER INDEX ALTER BUFFERPOOL may result in ABEND04E RC00C200BB AT DSNB1OPP OFFSET 57F6 when executed concurrently with ALTER TABLESPACE ALTER BUFFERPOOL because ALTER INDEX ALTER BUFFERPOOL fails to quiesce packages dependent on the index. Other operations may also result in abends or other unpredictable results when run concurrently with ALTER INDEX ALTER BUFFERPOOL. ALTER INDEX ALTER BUFFERPOOL has been modified to quiesce packages dependent on the index. Additionally, ALTER INDEX ALTER BUFFERPOOL has been modified to invalidate dynamically cached statements dependent on the index. ADDITIONAL KEYWORDS: SQLDYNSTMTCACHE SQLALTER COMPONENT: 5740-XYR00-HDBAA10 1 APARS FIXED: PM72201 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNXIAIX PM72201 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM72201 DSNXIAIX THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXIAIX LISTEND UK91030 COVER LETTER END UK91051 COVER LETTER START PROBLEM DESCRIPTION(S): PM75358 - **************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI. * **************************************************************** * PROBLEM DESCRIPTION: SQLDescribeCol() incorrectly returns * * ODBC 2.0 datetime values while the * * environment attribute * * SQL_ATTR_ODBC_VERSION is set to * * SQL_OV_ODBC3. * **************************************************************** * RECOMMENDATION: * **************************************************************** When environment attribute SQL_ATTR_ODBC_VERSION is set to SQL_OV_ODBC3, calling SQLDescribeCol() for a datetime column may return an ODBC 2.0 datetime value when running in a multi-threaded environment and another thread simultaneously tries to execute SQLGetTypeInfo() with a data type of SQL_DATE, SQL_TIME, or SQL_TIMESTAMP Code has been changed so that SQLDescribeCol() returns correct datetime values when SQL_ATTR_ODBC_VERSION = SQL_OV_ODBC3. COMPONENT: 5740-XYR02-JDBAA17 APARS FIXED: PM75358 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNAOC14 PM75358 DSNAOC15 PM75358 DSNAOG0Q PM75358 DSNAOG13 PM75358 DSNAOG14 PM75358 DSNAOG15 PM75358 DSNAOCLI PM75358 1 DSNAOSDK PM75358 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75358 DSNAOC14 DSNAOC15 DSNAOG0Q DSNAOG13 DSNAOG14 DSNAOG15 DSNAOCLI DSNAOSDK THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNAOC14 DSNAOC15 DSNAOG0Q DSNAOG13 DSNAOG14 DSNAOG15 DSNAOCLI MACROS DSNAOSDK LISTEND UK91051 COVER LETTER END UK91063 COVER LETTER START PROBLEM DESCRIPTION(S): PM77653 - **************************************************************** * USERS AFFECTED: DB2 9 and 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: DB2 crashed by an ABEND during ABORT * * because DSNILABR called unexpected * * module for an incorrect log. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a UR involving page compaction after data set extension failure was cancelled, DB2 might crash by ABEND during ABORT for the UR. From output of DSN1LOGP of the UR, we could see there is a log record of page compaction, by data manager CSECT DSNISMCP, following a log record by DSM (Data Space Manager) and we could see the log record for DSNISMCP used a residual flag from the preceding DSM log, which meant the flag marked the page compaction log record by DSNISMCP as a none data manager one. As a consequence, DB2 abort process tried to undo the DSNISMCP log record as a none data manager one erroneously and caused DB2 to crash. DB2 code is modified to clear the residual flag during writing log record for DSNISMCP. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM77653 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 DSNISMCP PM77653 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM77653 DSNISMCP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNISMCP LISTEND UK91063 COVER LETTER END UK91069 COVER LETTER START PROBLEM DESCRIPTION(S): PM78070 - **************************************************************** * USERS AFFECTED: DB2 for z/OS users with a query which * * contains UNION, EXCEPT, EXCEPT ALL or ORDER * * BY and whose top query block has exactly * * one table. * **************************************************************** * PROBLEM DESCRIPTION: A query may give incorrect output when * * the query satisfies the conditions * * below: * * * * 1.Top query block has exactly one * * table. * * 2.The query contains UNION, EXCEPT, * * EXCEPT ALL or ORDER BY. * **************************************************************** * RECOMMENDATION: * **************************************************************** A query may give incorrect output when the query contains UNION, EXCEPT, EXCEPT ALL or ORDER BY and its top query block has exactly one table. For example, SELECT * FROM (SELECT C1 FROM T1 UNION SELECT C1 FROM T2) AS T3 The problems mentioned above are fixed so that DB2 will return correct results in that situation. ADDITIONAL KEYWORDS: SQLUNION SQLEXCEPT SQLEXCEPTALL SQLORDERBY SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM78070 SPECIAL CONDITIONS: 1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM 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 PM78070 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM78070 DSNXOPRP THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNXOPRP LISTEND UK91069 COVER LETTER END UK91089 COVER LETTER START PROBLEM DESCRIPTION(S): PM79377 - **************************************************************** * USERS AFFECTED: All users of DB2 9 and 10 for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C4 may occur in CSECT * * DSNVCFRR after an agent has been * * cancelled during allocation in CSECT * * DSNVGACE. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 may reference storage in the wrong storage protection key during the recovery of an agent cancelled during agent allocation. DB2 Agent allocation recovery has been modified to access the storage in the correct storage protection key. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79377 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 DSNVCFRR PM79377 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79377 DSNVCFRR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNVCFRR LISTEND UK91089 COVER LETTER END UK91121 COVER LETTER START PROBLEM DESCRIPTION(S): PM79521 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 10 for z/OS only. * **************************************************************** * PROBLEM DESCRIPTION: Various 04E-00E2000C abends may occur * * after installing APAR PM64376 (PTF * * UK83114). * * Symptoms may include: * * o 04E-00E2000C,DSNLILNR.DSNSVSVB+0AC2 * * o 04E-00E2000C,DSNLTACC.DSNSVSVB+0AC2 * * o 04E-00E2000C,DSNLIRTR.DSNSVSVB+0AC2 * **************************************************************** * RECOMMENDATION: * **************************************************************** When remote client applications connect to a DB2 10 for z/OS server via TCP/IP, System Profile Monitoring (SPM) support in DB2 10 for z/OS monitors events related to the different remote client applications that access DB2, even if SPM is not enabled. The storage utilization accumulates over time due to processing and monitoring the remote applications. The changes provided by PM64376 address a storage accumulation issue by allowing DB2 to reuse available DB2 (SPME) control blocks when they no longer reflect active usage. However when reusing the SPME control blocks, a separate control block, that stores the information about the remote application, is not freed. Over time, this can eventually lead to the reported symptoms. This problem only occurs after the installation of APAR PM64376 (PTF UK83114). The entire DB2 subsystem must be stopped and restarted to relieve the storage condition. DB2 10 for z/OS server processing has been changed to free the control block that is no longer needed. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79521 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 DSNLIRTR PM79521 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79521 DSNLIRTR THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLIRTR LISTEND UK91121 COVER LETTER END UK91122 COVER LETTER START PROBLEM DESCRIPTION(S): PM75921 - **************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: Table inserts can experience longer * * than expected space search times. * * Which can lead to longer than expected * * overall insert performance. * **************************************************************** * RECOMMENDATION: * **************************************************************** Table inserts can experience longer than expected space search times. This can occur when the clustering index does not provide an adequate position for insert within the table. Module DSNKPOSI, has been modified to more exhaustively search for an actual position for insertion within the table. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75921 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNKPOSI PM75921 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75921 DSNKPOSI THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNKPOSI LISTEND UK91122 COVER LETTER END UK91142 COVER LETTER START PROBLEM DESCRIPTION(S): 1 PM75999 - **************************************************************** * USERS AFFECTED: All DB2 10 and DB2 9 for z/OS users of * * PADDED indexes that include one or more * * nullable VARCHAR columns * **************************************************************** * PROBLEM DESCRIPTION: In the reported case in DB2 10 (which * * can happen in either DB2 10 CM or DB2 * * NFM but not in DB2 9), -START PROFILE * * command fails to insert into table * * SYSIBM.DSN_PROFILE_HISTORY if index * * SYSIBM.DSN_PROFILE_TABLE_IX2_ALL on * * table SYSIBM.DSN_PROFILE_TABLE is * * padded, and the row value of indexed * * column GROUP_MEMBER VARCHAR(24) for * * SYSIBM.DSN_PROFILE_TABLE happens to be * * null * * * * In DB2 10 or DB2 9, incorrout is * * possible on any index scan on a padded * * index where the predicate on a VARCHAR * * column specifies NULL * **************************************************************** * RECOMMENDATION: * **************************************************************** An index scan driven internally by the -START PROFILE command against padded index SYSIBM.DSN_PROFILE_TABLE_IX2_ALL (index on SYSIBM.DSN_PROFILE_TABLE) failed to find a row that was present, which in turn resulted in the command's lack of insert into table SYSIBM.DSN_PROFILE_HISTORY. The affected skipped row had a null value for the indexed column GROUP_MEMBER and the scan was checking for NULL in the predicate. The reason for the unsuccessful index scan was an incorrect comparison code in the index selection expression code in the data manager subcomponent, which used a wrong comparison length for null-value VARCHARs. With regard to -START PROFILE, this problem can only happen in DB2 V10 CM and above and not in DB2 9. The reason for this is that the definition of index SYSIBM.DSN_PROFILE_TABLE_IX2_ALL is different in DB2 9 such that column GROUP_MEMBER is not part of the index. Although this problem was exposed by DB2 10 -START PROFILE, the problem can theoretically exist in any DB2 10 or DB2 9 selection expression-based fetch on a padded index when the scan checks for NULL against a null-value VARCHAR column (e.g. SELECT... WHERE C1 IS NULL and value of C1 in the row (index) is null). The reported DB2 10 -START PROFILE problem can be recreated as follows, assuming the index SYSIBM.DSN_PROFILE_TABLE_IX2_ALL is padded: ---------------------------------------------------------------- INSERT INTO SYSIBM.DSN_PROFILE_TABLE 1 ( ROLE, AUTHID, LOCATION, PRDID, COLLID, PKGNAME, PROFILEID, PROFILE_ENABLED ) VALUES ( NULL, NULL, '*', NULL, NULL, NULL, 1, 'Y' ) INSERT INTO SYSIBM.DSN_PROFILE_ATTRIBUTES ( PROFILEID, KEYWORDS, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3 ) VALUES ( 1, 'MONITOR CONNECTIONS', 'EXCEPTION', 0, NULL ) -START PROFILE Given that -START PROFILE did not insert into table SYSIBM.DSN_PROFILE_HISTORY when it should have, a SELECT * FROM SYSIBM.DSN_PROFILE_HISTORY will not show any rows representing the SYSIBM.DSN_PROFILE_TABLE row we inserted above. ---------------------------------------------------------------- Code has been changed to correctly evaluate null-value VARCHAR columns during selection expression on a padded index. Additional keywords: DB2INCORR/K SQLINCORR SQLINCORROUT COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM75999 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 DSNIONX2 PM75999 DSNIOST2 PM75999 DSNIRIDL PM75999 DSNISFX2 PM75999 DSNIXLDI PM75999 DSNKFLRR PM75999 DSNKFLST PM75999 DSNKFPRV PM75999 DSNKFTCH PM75999 DSNKFTRR PM75999 DSNKNXT2 PM75999 DSNOLDEL PM75999 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM75999 DSNIONX2 DSNIOST2 DSNIRIDL DSNISFX2 DSNIXLDI DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNIONX2 DSNIOST2 DSNIRIDL DSNISFX2 DSNIXLDI DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL LISTEND UK91142 COVER LETTER END UK91146 COVER LETTER START PROBLEM DESCRIPTION(S): PM79161 - **************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * DB2 10 for z/OS only. * **************************************************************** * PROBLEM DESCRIPTION: The following abend may occur at a DB2 * * 10 for z/OS system: * * 0C4-00000038,DSNLZLLM.DSNLZINF+0974 * **************************************************************** * RECOMMENDATION: * **************************************************************** A remote requester connects to DB2 10 for z/OS server. The 1 remote requester is operating at a higher DRDA level such as SQLAM 11 or higher. Due to an internal processing error in the DB2 10 for z/OS server, the reported abend was issued and the request was failed. DB2 10 for z/OS server processing has been changed to tolerate remote requesters operating at a higher DRDA SQLAM level. COMPONENT: 5740-XYR00-HDBAA10 APARS FIXED: PM79161 SPECIAL CONDITIONS: COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM COMMENTS: CROSS REFERENCE-MODULE/MACRO NAMES TO APARS DSNLZINF PM79161 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES PM79161 DSNLZINF THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: MODULES DSNLZINF LISTEND UK91146 COVER LETTER END READY END