1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES READY %HOLDDATA WDB2I.R.DB2101S.SMPPTS IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED UI11697 HOLD DATA START UI11697 HOLD DATA END UI11767 HOLD DATA START UI11767 HOLD DATA END UI11775 HOLD DATA START UI11775 HOLD DATA END UI11780 HOLD DATA START ++ HOLD(UK96273) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13301) COMMENT (***Action for PM92597: See PM92597 APAR/PTF text for additional information about why a REBIND is necessary. PM92597 corrects a problem of incorrect output for a query containing NOT DISTINCT predicate with correlated 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.). ++ HOLD(UK95370) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13301) COMMENT (***Action for PM89230: See PM89230 APAR/PTF text for additional information about why a REBIND is necessary. PM89230 corrects a problem of an ABEND04E RC00E70005 at location DSNXGRDS DSNXGRM1 M258 for an SQL statement containing a graphic or vargraphic host variable which can be deleted. 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.). ++ HOLD(UK94179) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13301) COMMENT (***Action for PM85976: See PM85976 APAR/PTF text for additional information about why a REBIND is necessary. PM85976 corrects an ABEND0C4 at DSNXEBR OFFSET 441C or an ABEND04E RC00E70005 at location DSNXESX4 M999 can occur when 1 executing the SET CURRENT OPTIMIZATION HINT = '' or the SET CURRENT SQLID = '' statements. These failures can occur from dynamic or static SQL when a UNICODE encoding scheme is employed. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI11780) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(13301) COMMENT (***Action for PM94911: PM94911 is a pre-conditioning APAR that includes changes to support a functional code change that will be enabled via APAR PM73542 at a later date. At this time, all of the changes are transparent to the user. In a data sharing group, this pre-conditioning APAR(PM94911) should be applied to all members before the later enabling APAR PM73542 is applied to any member. The code change is not enabled until the enabling APAR PM73542 is applied. PM73542 corrects a problem of performance regression for static SQL queries on tables that use a range partitioning scheme and have equal predicate on timestamp column and string host variable.). ++ HOLD(UI11780) SYS FMID(HDBAA10) REASON(ACTION) DATE(13301) COMMENT (***Action for PM94911: Please note that the following action needs to be performed along with the application of this apar/ptf. Please note that the application of this apar/ptf needs to be applied to all DB2 members in a datasharing environment. This will allow all members to include both the needed bindtime and runtime code changes.). UI11780 HOLD DATA END UI11793 HOLD DATA START UI11793 HOLD DATA END UI11797 HOLD DATA START UI11797 HOLD DATA END UI11880 HOLD DATA START UI11880 HOLD DATA END UI11907 HOLD DATA START UI11907 HOLD DATA END UI11909 HOLD DATA START ++ HOLD(UI11909) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13303) 1 COMMENT (***Action for PM95677: See PM95677 APAR/PTF text for additional information about why a REBIND or recreate view is necessary. PM95677 corrects a problem that incorrect output, ABEND04E RC00C90101 at the location DSNGD001 DSNGDVRT 500B, or ABEND0C7 RC00000000 at the location DSNXGRDS DSNXRTIM OFFSET7120(or OFFSET6B98) could happen for an SQL statement that has a '*' in the SELECT list and contains multiple outer joins with one of them as a nested outer join. To make the fix effective for a view that contains such an SQL statement, the view must be dropped and then created. 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.). UI11909 HOLD DATA END UI12034 HOLD DATA START UI12034 HOLD DATA END UI12048 HOLD DATA START UI12048 HOLD DATA END UI12050 HOLD DATA START UI12050 HOLD DATA END UI12055 HOLD DATA START UI12055 HOLD DATA END UI12103 HOLD DATA START UI12103 HOLD DATA END UI12184 HOLD DATA START UI12184 HOLD DATA END UI12197 HOLD DATA START UI12197 HOLD DATA END UI12219 HOLD DATA START UI12219 HOLD DATA END UI12259 HOLD DATA START 1UI12259 HOLD DATA END UI12392 HOLD DATA START UI12392 HOLD DATA END UI12398 HOLD DATA START ++ HOLD(UI12398) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13316) COMMENT (See PM96918 APAR/PTF text for additional information about why a REBIND is necessary. PM96918 corrects a problem where more rows may be returned when a spatial index is used on the inner table of an access plan. 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.). UI12398 HOLD DATA END UI12614 HOLD DATA START UI12614 HOLD DATA END UI12639 HOLD DATA START UI12639 HOLD DATA END UI12644 HOLD DATA START UI12644 HOLD DATA END UI12646 HOLD DATA START UI12646 HOLD DATA END UI12648 HOLD DATA START UI12648 HOLD DATA END UI12699 HOLD DATA START UI12699 HOLD DATA END UI12795 HOLD DATA START UI12795 HOLD DATA END UI12801 HOLD DATA START UI12801 HOLD DATA END 1UI12977 HOLD DATA START UI12977 HOLD DATA END UI13035 HOLD DATA START ++ HOLD(UI13035) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(13331) COMMENT (See PM97952 APAR/PTF text for additional information. PM97952 is a pre-conditioning APAR that includes changes to enhance XMLTABLE performance which will be enabled via APAR PM98160 later. At this time, all 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 is applied to any member. The performance enhancement is not enabled until the enabling APAR PM98160 is applied.). UI13035 HOLD DATA END UI13153 HOLD DATA START UI13153 HOLD DATA END UI13278 HOLD DATA START UI13278 HOLD DATA END UI13283 HOLD DATA START ++ HOLD(UI13283) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13339) COMMENT (See PM98842 APAR/PTF text for additional information about why a REBIND is necessary. PM98842 corrects an incorrect output problem with DEGREE(ANY) when a parallel pairwise join plan is degenerated to a sequential plan. 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.). UI13283 HOLD DATA END UI13364 HOLD DATA START UI13364 HOLD DATA END UI13455 HOLD DATA START UI13455 HOLD DATA END UI13461 HOLD DATA START UI13461 HOLD DATA END 1UI13510 HOLD DATA START UI13510 HOLD DATA END UI13513 HOLD DATA START UI13513 HOLD DATA END UI13796 HOLD DATA START UI13796 HOLD DATA END UI13841 HOLD DATA START ++ HOLD(UI13841) SYS FMID(HDBAA10) REASON(DOC) DATE(13358) COMMENT (PM97985 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference (SC19-4067). 1. Under the chapter for LOAD, Table 37. Maximum delimiter values for different encoding schemes: Encoding scheme Maximum allowable value EBCDIC SBCS None | EBCDIC DBCS/MBCS X'3F' (X'7F', X'4B', X'6B' also allowed) ASCII/Unicode SBCS None ASCII/Unicode MBCS X'7F' 2. Under the chapter for UNLOAD, Table 127. Maximum delimiter values for different encoding schemes: Encoding scheme Maximum allowable value EBCDIC SBCS None | EBCDIC DBCS/MBCS X'3F' (X'7F', X'4B', X'6B' also allowed) ASCII/Unicode SBCS None ASCII/Unicode MBCS X'7F'). ++ HOLD(UI13841) SYS FMID(HDBAA10) REASON(ACTION) DATE(13358) COMMENT (The PTF for APAR PM97985 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. See PM97985 APAR/PTF text for additional information. After applying the PTF for PM79448, UNLOAD DELIMITED of an EBCDIC table containing DBCS/MBCS data and using the default delimiters, ends with RC8 and issues MSGDSNU1141I - INVALID DELIMITER CHARACTER ',' (X'6B') for an invalid column delimiter. 1 This same error would have occurred if the default value for the character delimiter (X'7F') had been specified and if the column delimiter had been a valid one. In order to allow the specific UNLOAD case to succeed and at the same time ensure the LOAD utility can process the unloaded data, we are adding x'0E'/x'0F' (shift-out/shift-in) around the GRAPHIC and VARGRAPHIC unloaded data for the case where the default delimiters are used when defaulting to unloading the table space in EBCDIC. UNLOAD already does this when the UNLOAD statement explicitly states EBCDIC and LOAD will load the data correctly. Code is being added for the case when we default to unloading DBCS data (GRAPHIC/VARGRAPHIC) in the format of the table space when that table space is defined as EBCDIC. Without the Shift-out/shift-in characters, any operation processing the delimited data would not be able to determine the end of a DBCS column if the delimiters were contained in the DBCS characters. That could lead to possible data integrity problems. LOAD FORMAT DELIMITED already has the code to be able to correctly load the graphic data when surrounded by x'0E'/x'0F'. In summary, this fix will undo the changes made by PM79448. However, it will also change the SYSREC dataset output to ensure consistency between implicit and explicit specification of the EBCDIC parameter and ensure data integrity is not compromised.). UI13841 HOLD DATA END UI14060 HOLD DATA START UI14060 HOLD DATA END UI14250 HOLD DATA START UI14250 HOLD DATA END UI14357 HOLD DATA START UI14357 HOLD DATA END UK79840 HOLD DATA START ++ HOLD(UK79840) SYS FMID(HDBAA10) REASON(DOC) DATE(12178) COMMENT (Since the -DISPLAY DATABASE command could have displayed INCORROUT STATUS field values for the final summary line of partitioned objects any programs or processes that use that field need to understand that the only valid or relevant STATUS field values for the entire final summary line of partitioned object are: blank, DBETE or DBETE,RECP The DSNT397I message was updated to describe the final summary line for partitioned objects and their possible valid or relevant STATUS field values: blank, DBETE or DBETE,RECP.). 1++ HOLD(UK66610) SYS FMID(HDBAA10) REASON(DOC) DATE(12178) COMMENT (The fix for APAR PM25652, introduces a new special option, RRTHashOvrFlwRatio. The Utility Guide and Reference and The Application Programming Guide documentation on DSNACCOX will have a new description of RRTHashOvrFlwRatio as follows: Syntax: -|---+---' '--------------+---|- +-RRTHashOvrFlwRatio-+ '- -1 ---------------' Description: RRTHashOvrFlwRatio Specifies a criterion for recommending that the REORG utility is run on a table space. If the following conditions are true, DSNACCOX recommends running REORG: - The hash access overflow index is being used for access. - The number of hash access overflow index entries divided by the total number of rows (expressed as a percentage) is greater than RRTHashOvrFlwRatio. RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The default value is ' 15'. A plus sign (+) preceding or following the value, or a plus sign by itself indicates that the DSNACCOX stored procedure returns the calculated ratio value in the result set. A negative value indicates that the criterion is not used. The ratio of hash access overflow index entries to the total number of rows is returned in column RRTHashOvrFlwRatPCT of the result set. Figure 4. DSNACCOX formula for recommending a REORG on a table space has an additional criteria: (((QueryType='REORG' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL')) AND (REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR (NACTIVE IS NULL OR NACTIVE > 5) AND ((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND REORGINSERTS > RRTInsertsAbs) OR (((REORGDELETE x 100) / TOTALROWS > RRTDeletesPct) AND REORGDELETE > RRTDeleteAbs) OR (REORGCLUSTERSENS > 0 AND (REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR ((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR | (Object is not using hash organization and ((SPACE x 1024) / RRTDataSpaceRat)) OR ((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS > RRTIndRefLimit) OR REORGMASSDELETE > RRTMassDelLimit OR EXTENTS > ExtentLimit) OR | ((QueryType='REORG' OR QueryType='ALL') AND | ObjectType='ALL' * AND 1 | Overflow index hash access is used**, AND | ((overflow index TOTALENTRY x 100) / TOTALROWS > RRTHashOvrFlwRatio)) OR ((QueryType='RESTRICT' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL') AND The table space is in advisory or informational reorg pending status) |Note: | * ObjectType='ALL' must be specified to use this criteria. | for this criterion to be used. If ObjectType='TS' or | ObjectType='IX' is specified, and '+' is specified for | RRTHashOvrFlwRatio, an error message is issued. If | ObjectType='TS' or ObjectType='IX' is specified, and | '+' is not specified for RRTHashOvrFlwRatio, this | criterion is not used. | ** The overflow index is used when SYSINDEXES.HASH ='Y' AND | SYSINDEXSPACESTATS.REORGINDEXACCESS > 0. Add the following table entry to table for the "DSNACCOX OUTPUT" section. Result set row for second DSNACCOX result set ---------------------------------------------------------------- |Column name | Data type |Description | ---------------------------------------------------------------- |RRTHashOvrFlwRatPCT| Double |This is an optional column, | | | |and it is being returned when | | | |there is a plus (+) sign in | | | |the RRTHashOverFlwRatio. | | | | | | | |If OBJECTTYPE is ALL and REORG| | | |is YES, the ratio of Hash | | | |Access overflow index entries | | | |to the total number of rows, | | | |expressed as a percentage. | | | |Otherwise null. | | | | | | | |If the ratio of Hash Access | | | |overflow index entries to the | | | |total number of rows does not | | | |exceed the value specified for| | | |RRTHashOvrFlwRatio or meet the| | | |criteria requirement, this | | | |value is null. | ----------------------------------------------------------------). ++ HOLD(UK65635) SYS FMID(HDBAA10) REASON(ACTION) DATE(12178) COMMENT ( ***Action for PM28652: See PM28652 APAR/PTF text for additional information. <<<<<<> Post-apply actions after applying the fix for APAR PM28652: (a) STOP PROC(SYSPROC.DSNACCOR) to suspend DSNACCOR activity (b) Rebind package for DSNACCOR. An example on how to do this is 1 BIND PACKAGE(DSNACCOR) MEMBER(DSNACCOR) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOR) to resume DSNACCOR activity). ++ HOLD(UK66610) SYS FMID(HDBAA10) REASON(ACTION) DATE(12178) COMMENT (Post-apply actions after applying the fix for APAR PM25652: (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity (b) Rebind package for DSNACCOX. An example on how to do this is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). UK79840 HOLD DATA END UK81198 HOLD DATA START UK81198 HOLD DATA END UK83237 HOLD DATA START UK83237 HOLD DATA END UK91351 HOLD DATA START ++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(DOC) DATE(13032) COMMENT (PM74794 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference - Appendix B. DB2-supplied stored procedures for utility operations Section - DSNACCOX stored procedure Chapter - DSNACCOX output Table 145 - Result set row for second DSNACCOX result set | NAME VARCHAR(128) Table space name, index name, or | index space name. Index space | name is used if the row is added | as a result of checking a | restricted state and the index | name is not available at the time. Information about this changed information will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). ++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(ACTION) DATE(13032) COMMENT 1 ( ***Action for PM74794: See PM74794 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PM74794: (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity (b) Rebind package for DSNACCOX. An example on how to do this is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). ++ HOLD(UK79842) SYS FMID(HDBAA10) REASON(ACTION) DATE(13032) COMMENT (After you apply the PTF for APAR PM61574, Non Partitioned Index is no longer recommended for reorg or runstats when chklevel 32 is specified and any of the ts partitioned is recommended for reorg or runstats.). UK91351 HOLD DATA END UK91533 HOLD DATA START UK91533 HOLD DATA END UK91974 HOLD DATA START ++ HOLD(UK91974) SYS FMID(HDBAA10) REASON(ACTION) DATE(13056) COMMENT (This PTF writes the message DSNA679I to the console as a multi-line message, instead of two single-line messages. Before this PTF, DSNA679I is split into two parts, each part written as a single-line message. For example: N ... DSNA679I DSNA6BUF THE ADMIN SCHEDULER DSNADMT CANNOT ACCESS TASK LIST S ... SYSIBM.ADMIN_TASKS, REASON= N ... SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS where: o the first part of the message ends at REASON=, and is displayed with log record types 'N' (single-line message) and 'S' (continuation of a previous line) o the second part of the message contains the text that follows REASON=, and is displayed with log record type 'N' and if necessary, another record with log record type 'S' (continuation of a previous line) With this PTF, DSNA679I is written to the console as a multi- line message. For example: M ... DSNA679I DSNA6BUF THE ADMIN SCHEDULER DSNADMT D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS, E ... REASON=SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS where: o the first line ends with the name of the scheduler, and 1 is displayed with log record type 'M' (first line of a multi-line message) o the second line ends with the name of the scheduler task list and is displayed with log record type 'D' (data line of a multi-line message) o the third line starts with REASON=, and is displayed with log record type 'D' or 'E' (end line of a multi-line message), depending on whether the text that follows REASON= will wrap o the last line is displayed with log record type 'E' As a multi-line message, DSNA679I is subdivided differently from how it was subdivided as two single-line messages. Therefore, any application that parses DSNA679I based on how this message was subdivided and displayed on the console must be modified. In addition, when this PTF is applied on a member by member basis to a DB2 data sharing group, all applications that parse DSNA679I for the schedulers of other members must be modified to check the log record type of DSNA679I first before parsing: o If log record type='N', parse DSNA679I as two single-line messages. o If log record type='M', parse DSNA679I as a multi-line message. 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.). UK91974 HOLD DATA END UK92534 HOLD DATA START UK92534 HOLD DATA END UK92537 HOLD DATA START UK92537 HOLD DATA END UK92588 HOLD DATA START UK92588 HOLD DATA END UK92609 HOLD DATA START ++ HOLD(UK92609) SYS FMID(HDBAA10) REASON(DOC) DATE(13077) 1 COMMENT (PM71744 introduces the following changes to externals: A new MODE "STATS" is added to the ACCESS DATABASE command. .-,-------------. V | >>-ACCESS--DATABASE(-+---database-name-+-----+-)---------------> +-*---------------------+ +-dbname1:dbname2-------+ +-dbname*---------------+ +-*dbname---------------+ +-*dbname*--------------+ '-*dbstring1*dbstring2*-' .-,----------. V | >--SPACENAM--(--+---space-name-+--------------+--)-------------> +-*---------------------------+ +-spacename1:spacename2-------+ +-spacename*------------------+ +-*spacename------------------+ +-*spacename*-----------------+ '-*spacestring1*spacestring2*-' >--+---------------------------------------+-------------------> | .-,---------------------. | | V | | '-PART--(----+-integer-----------+-+--)-' '-integer1:integer2-' >--MODE--(--+-OPEN----+--)------------------------------------>< +-NGBPDEP-+ '-STATS---' New option description: MODE( mode-value ) STATS: Externalizes the in-memory real-time statistics to the appropriate catalog tables. In data sharing environments, the in-memory statistics are externalized for all members. This mode does not physically open the page sets or change the states of the page sets. Information about this new command option will be included in the Information Management Software for z/OS Solutions Information Center (http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp) at a later date.). UK92609 HOLD DATA END 1 UK92645 HOLD DATA START ++ HOLD(UK92645) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13078) COMMENT (***Action for PM81200: See PM81200 APAR/PTF text for additional information about why a REBIND is necessary. PM81200 corrects a problem of ABEND04E RC00C90101 at DSNIBNRF:5007 when a query's selection list contains a scalar full-select item participated in arithmetic calculation 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.). UK92645 HOLD DATA END UK92649 HOLD DATA START ++ HOLD(UK92649) SYS FMID(HIZAA10) REASON(ACTION) DATE(13078) COMMENT (***Action for PM83982: 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.). ++ HOLD(UK82190) SYS FMID(HIZAA10) REASON(ACTION) DATE(13078) COMMENT (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.). ++ HOLD(UK79291) SYS FMID(HIZAA10) REASON(ACTION) DATE(13078) COMMENT (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=... 1 These commands are not necessary if you re-IPL after applying the PTF.). ++ HOLD(UK77481) SYS FMID(HIZAA10) REASON(ACTION) DATE(13078) COMMENT (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.). ++ HOLD(UK78499) SYS FMID(HIZAA10) REASON(ACTION) DATE(13078) COMMENT (***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.). UK92649 HOLD DATA END UK92651 HOLD DATA START UK92651 HOLD DATA END UK92704 HOLD DATA START UK92704 HOLD DATA END UK92705 HOLD DATA START UK92705 HOLD DATA END UK92791 HOLD DATA START ++ HOLD(UK92791) SYS FMID(HIYAA10) REASON(ACTION) DATE(13080) COMMENT (This APAR provides changes to support IMS APARs PM69915 (V11), PM70167 (V12) or PM79247 (V13). The fix for this APAR PM82151 should be installed to obtain 1 the full benefit of the changes provided in these IMS APARs.). UK92791 HOLD DATA END UK92801 HOLD DATA START UK92801 HOLD DATA END UK92833 HOLD DATA START ++ HOLD(UK92833) SYS FMID(HDBAA10) REASON(ACTION) DATE(13081) COMMENT (***Action for PM83176 TYPE: ACT PM83176 corrects a problem of sqlcode -199 issued during rebind when a native SQL procedure or a non-inline SQL scalar function contains an SQL statement with a single SQL valiable in the select list with parentheses around it. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected, or ALTER FUNCTION REGENERATE is required for each non-inline SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure could be affected by this change.). UK92833 HOLD DATA END UK92837 HOLD DATA START ++ HOLD(UK92837) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13081) COMMENT (***Action for PM82351: See PM82351 APAR/PTF text for additional information about why a REBIND is necessary. PM82351 corrects a problem where rowid index may not be used to evaluate omnifind function in a predicate when it should. It may cause performance problem for queries with omnifind function in a 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.). UK92837 HOLD DATA END UK92838 HOLD DATA START UK92838 HOLD DATA END UK92843 HOLD DATA START UK92843 HOLD DATA END 1UK92851 HOLD DATA START ++ HOLD(UK92851) SYS FMID(HDBAA10) REASON(ACTION) DATE(13084) COMMENT (The fix for PM80291 enforces the documented requirement that when the utility is invoked from a stored procedure, NUMTCB=1 must be specified in the proc that started the WLM managed address space where the utility is running. PM80291 introduces the following message to the DB2 10 for z/OS Messages: DSNU022I csect-name - A UTILITY RUNNING UNDER A STORED PROCEDURE REQUIRES A WLM ENVIRONMENT WITH NUMTCB=1. UTILID utility-ID IS RUNNING WITH NUMTCB = tcb-number. Explanation When the utility stored procedure invoked a utility, the stored procedure was running in a stored procedure address space that was started with NUMTCB>1. The stored procedure address space in which the utility stored procedure runs must be started with NUMTCB=1. csect-name The name of the control section that issued the message. utility-ID The utility identifier or the UID parameter that was used in the job step. tcb-number The NUMTCB parameter of the job that started the WLM-managed stored procedure address space. The NUMTCB value represents the maximum number of task control blocks (TCBs) that can run concurrently in an address space that is initiated by the WLM environment. System action Execution of the utility is stopped. System programmer response Change the PROCLIB member that was used to start the WLM-managed stored procedure address space to specify NUMTCB=1. Then, refresh the WLM environment and run the utility again. Severity 8 (error) Information about this new message, DSNU022I, 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.). UK92851 HOLD DATA END 1UK92861 HOLD DATA START UK92861 HOLD DATA END UK92863 HOLD DATA START UK92863 HOLD DATA END UK92875 HOLD DATA START ++ HOLD(UK92875) SYS FMID(HDBAA10) REASON(DOC) DATE(13084) COMMENT (The PTF for APAR PM76266 has added a new message MSGDSNU3346I to the Messages manual. DSNU3346I REAL-TIME STATISTICS INFORMATION MISSING FOR obj-type obj-qual.obj-name. SAMPLING RATE CHANGED TO 100. Explanation: The utility could not read necessary information from real-time statistics tables for the object. obj-type: The type of object. obj-qual.obj-name: The name of the object,as a qualified name. System action: RUNSTATS sets the sampling rate to 100, and continues to run. System programmer response: If a sampling rate of 100 is appropriate, no action is required. Otherwise, run the REORG TABLESPACE utility on the specified object to re-establish values in the real-time statistics tables. Then run RUNSTATS with TABLESAMPLE SYSTEM n again. Severity: 4 (warning) Information about the new message DSNU3346I 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.). UK92875 HOLD DATA END UK92878 HOLD DATA START UK92878 HOLD DATA END UK92899 HOLD DATA START ++ HOLD(UK92899) SYS FMID(HDBAA10) REASON(ACTION) DATE(13085) COMMENT (***Action for PM81926: Users should be aware that the format of the Display Thread command report, specifically the DSNV485I (V485) message, has been changed which may impact automation that interprets the result. Before applying this change, users should identify any automation that may be affected and adapt this automation to 1 tolerate the new form. Data Sharing users should be aware that group members may report different forms of the message until this change is fully deployed to all members of the group.). UK92899 HOLD DATA END UK92913 HOLD DATA START UK92913 HOLD DATA END UK92979 HOLD DATA START UK92979 HOLD DATA END UK92987 HOLD DATA START UK92987 HOLD DATA END UK93011 HOLD DATA START UK93011 HOLD DATA END UK93023 HOLD DATA START UK93023 HOLD DATA END UK93041 HOLD DATA START ++ HOLD(UK93041) SYS FMID(HDBAA10) REASON(DOC) DATE(13088) COMMENT (The fix for APAR PM77340 has an associated change to the DB2 documentation, similar to the following: Under Section "Defining the SQL communications area, SQLSTATE, and SQLCODE in REXX", the following text: If you use the ADDRESS DSNREXX "CONNECT" ssid syntax to connect to DB2, the SQLCA variables are a set of simple variables. If you use the CALL SQLDBS "ATTACH TO" syntax to connect to DB2, the SQLCA variables are compound variables that begin with the stem SQLCA. is changed to the following: The SQLCA has the following forms: A set of simple variables A set of compound variables that begin with the stem SQLCA The simple variables is the default form of the SQLCA. Using CALL SQLEXEC results in the compound stem variables. Otherwise, the attachment command used determines the form of the SQLCA. If you use the ADDRESS DSNREXX 'CONNECT' ssid syntax to connect to DB2, the SQLCA variables are a set of simple variables. If you use the CALL SQLDBS 'ATTACH TO' syntax to connect to DB2, the SQLCA variables are compound 1 variables that begin with the stem SQLCA. Switching forms of the SQLCA within an application is not recommended. Under section "Accessing the DB2 REXX language support application programming interfaces" The SQLDBS and SQLEXEC forms of the DSNREXX commands were described as: CALL SQLDBS 'ATTACH TO' ssid is equivalent to ADDRESS DSNREXX 'CONNECT' ssid. CALL 'SQLEXEC' "SQL-statement" is equivalent to ADDRESS DSNREXX 'EXECSQL' "SQL-statement". CALL SQLDBS 'DETACH' is equivalent to ADDRESS DSNREXX 'DISCONNECT'. These are changed to the following: CALL SQLDBS 'ATTACH TO' ssid is an alternative to ADDRESS DSNREXX 'CONNECT' ssid. CALL 'SQLEXEC' "SQL-statement" is an alternative to ADDRESS DSNREXX 'EXECSQL' "SQL-statement". CALL SQLDBS 'DETACH' is an alternative to ADDRESS DSNREXX 'DISCONNECT'.). UK93041 HOLD DATA END UK93064 HOLD DATA START UK93064 HOLD DATA END UK93078 HOLD DATA START UK93078 HOLD DATA END UK93083 HOLD DATA START UK93083 HOLD DATA END UK93116 HOLD DATA START UK93116 HOLD DATA END UK93117 HOLD DATA START ++ HOLD(UK93117) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM79265 corrects a problem where an asensitive scrollable 1 cursor defined with FETCH FIRST n ROWS ONLY in the outermost fullselect gets SQLCODE -243. 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.). ++ HOLD(UK78004) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (***Action for PM57420: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM57420 corrects a problem where lock avoidance is being used for a singleton, non-cursor SELECT when ISOLATION(CS) is used with CURRENTDATA(YES). Concurrent updates may yield inconsistent results for the SELECT. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77847) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (***Action for PM56626: See PM56626 APAR/PTF text for additional information about why a REBIND is necessary. PM56626 allows users to define a dynamic scroll cursor whose SELECT statment contains a subquery such that the base object of the outer subselect, and of the subquery, is the same, but with the conditions that (1) FOR FETCH ONLY is specified in the SELECT statement, and (2) the base object is accessed via the index to avoid any sort or materialization. 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.). ++ HOLD(UK75154) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (***Action for PM51623: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM51623 corrects a problem that an inefficient access path may be chosen for a DELETE statement against a VIEW on which an INSTEAD OF DELETE trigger is defined. 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++ HOLD(UK65223) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (***Action for PM30690: See PM30690 APAR/PTF text for additional information about why a REBIND is necessary. PM30690 corrects a problem of an infinite loop for a MERGE statement with 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.). UK93117 HOLD DATA END UK93125 HOLD DATA START ++ HOLD(UK93125) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13093) COMMENT (***Action for PM81000: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM81000 corrects a problem of inaccurately estimated I/O and CPU of a parent query block table in hybrid join when parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK93125 HOLD DATA END UK93150 HOLD DATA START UK93150 HOLD DATA END UK93153 HOLD DATA START ++ HOLD(UK93153) SYS FMID(HDBAA10) REASON(DOC) DATE(13094) COMMENT (The PTF for APAR PM73758 adds a new error message that will be issued by the RECOVER utility with the BACKOUT YES option when the recovery point is not contained within the most recent DB2 system checkpoints that are recorded in the BSDS for each member. .. Documentation change to the DB2 Messages manual: DSNU1545I csect-name RECOVER WITH BACKOUT YES CANNOT PROCEED. THE RECOVERY POINT IS OLDER THAN THE EARLIEST CHECKPOINT IN THE BSDS. Explanation: The recovery point that is identitied by TOLOGPOINT or TORBA is not contained within 1 the most recent DB2 system checkpoints that are recorded in the BSDS for each member. RECOVER with the BACKOUT YES option cannot proceed, because the checkpoint RBA that is before the recovery point for each member is required for backout processing. csect-name: The name of the control section that issued the message. System action: The RECOVER utility ends with return code 8 and does not process any of the objects. The objects are left in the state that they were in before the RECOVER operation. System programmer response: Remove the BACKOUT YES option and resubmit the RECOVER job. This revised job recovers the objects to the same point in time. However, the data is recovered by using a recovery base and applying the logs rather than using backout processing. Recommendation: Use the output from the REPORT utility with the RECOVERY option for all of the objects to ensure that a valid recovery base exists before you run RECOVER. Severity: 8 (error) .. Documentation change to the Utility Guide and Reference manual, Chapter 23 RECOVER utility. A new paragraph is added under the BACKOUT YES option: If you specify BACKOUT YES, the recovery point must be within the most recent DB2 system checkpoints that are recorded in the BSDS for each member. Otherwise, the recovery cannot proceed and returns an error.). UK93153 HOLD DATA END UK93162 HOLD DATA START UK93162 HOLD DATA END UK93187 HOLD DATA START UK93187 HOLD DATA END UK93191 HOLD DATA START UK93191 HOLD DATA END UK93202 HOLD DATA START ++ HOLD(UK93202) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13096) COMMENT (See PM74904 APAR/PTF text for additional information about why a REBIND is necessary. PM74904 corrects a problem that ABEND0C4 PIC11 at the location DSNIDM DSNOPUFF OFFSET02BA could happen for an SQL statement that contains a recursive common table expression with a LOB expression in the SELECT list. 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. With this APAR applied, more storage will be used to store LOB values for the recursive common table expression.). UK93202 HOLD DATA END UK93217 HOLD DATA START UK93217 HOLD DATA END UK93224 HOLD DATA START UK93224 HOLD DATA END UK93229 HOLD DATA START UK93229 HOLD DATA END UK93238 HOLD DATA START UK93238 HOLD DATA END UK93245 HOLD DATA START UK93245 HOLD DATA END UK93249 HOLD DATA START UK93249 HOLD DATA END UK93300 HOLD DATA START ++ HOLD(UK90215) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13100) COMMENT (***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. 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.). ++ HOLD(UK82227) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13100) COMMENT (***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.). ++ HOLD(UK76115) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13100) COMMENT (***Action for PM53364: See PM53364 APAR/PTF text for additional information about why a REBIND is necessary. PM53364 corrects a problem that An incorrout may occur when the query satisfies all of below conditions: 1,A String representation of timestamp value is used as one parameter of a scalar function. 2,Above scalar function is referenced in the user query's predicate. 3,The result of the scalar function is used to compare with another timestamp value. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK73883) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13100) COMMENT (***Action for PM47894: See PM47894 APAR/PTF text for additional information about why a REBIND is necessary. PM47894 corrects a problem that an incorrout may occur when user's SQL statement satisfies all of following conditions: 1, The SQL statement contains a BETWEEN predicate which references a CASE expression in its low or high operator. 1 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.). ++ HOLD(UK93300) SYS FMID(HDBAA10) REASON(ACTION) DATE(13100) COMMENT (***Actions for APAR PM81692 (V10) This PTF adds an online-changeable subsystem parameter in DSN6SPRM called PGRNGSCR that specifies whether to enable page range pruning in order to improve performance of queries that contain one or more of the following predicates: < <= > >= BETWEEN AND Valid settings are: - NO : Do not enable this optimizer change. ==> This is the default setting - YES: Enable the change. Do not use this setting unless advised to do so by IBM service. Special attention for data sharing customers: * Do not specify PGRNGSCR=YES on any member of the group until this PTF has been applied to all members. Otherwise, DB2 can experience abend 04E-00E70005 at DSNXRTIM:P017 * If you specify PGRNGSCR=YES on any member, it is recommended that you specify it on all members. Not specifying the same option on all members may result in member flip-flop behavior. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Rebind any applications using one or more of the aforementioned predicates. Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the 1 prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter PGRNGSCR=, where is NO or YES, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding PGRNGSCR here, the value will be set to the default of NO when you assemble the DSNZPxxx module. Special attention for data sharing customers: - Do not specify PGRNGSCR=YES on any member of the group until this PTF has been applied to all members. Otherwise, DB2 can experience abend 04E-00E70005 at DSNXRTIM:P017 - If you specify PGRNGSCR=YES on any member, it is recommended that you specify it on all members. Not specifying the same option on all members may result in member flip-flop behavior. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ==> This action is required for all customers This PTF adds an entry for PGRNGSCR to the CLIST default input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following lines: PGRNGSCR CHAR M NO YES Change to the value you specified for PGRNGSCR in step (2), above. ---------------------------------------------------------------- (4) Rebind any applications using one or more of the aforementioned predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change. 1 End of actions for APAR PM81692 (V10)). ++ HOLD(UK91971) SYS FMID(HDBAA10) REASON(ACTION) DATE(13100) COMMENT (***Action for PM79804 (V10) This PTF modifies the DB2 installation CLIST to correct errors in the migration handling of the DSN6SPRM.LRDRTHLD parameter. Actions for current DB2 10 customers: ------------------------------------ This PTF modifies CLIST member DSNTINST only in the prefix.SDSNCLST target library. After applying the PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside.). UK93300 HOLD DATA END UK93369 HOLD DATA START UK93369 HOLD DATA END UK93392 HOLD DATA START ++ HOLD(UK93392) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13102) COMMENT (***Action for PM83457: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83457 corrects a problem that the DB2 optimizer may select an inefficient join sequence for a query if the query has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90219) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13102) COMMENT (***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.). ++ HOLD(UK90222) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13102) 1 COMMENT (***Action for PM72676: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM72676 corrects a problem of inaccurate cost estimation for a query when the query contains nested non-correlated subqueries. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77770) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13102) COMMENT (***Action for PM58932: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM58932 corrects a problem that DB2 may choose an inefficient join sequence for a query joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK68201) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13102) COMMENT (***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.). UK93392 HOLD DATA END UK93422 HOLD DATA START UK93422 HOLD DATA END UK93436 HOLD DATA START UK93436 HOLD DATA END UK93442 HOLD DATA START UK93442 HOLD DATA END 1 UK93469 HOLD DATA START UK93469 HOLD DATA END UK93476 HOLD DATA START UK93476 HOLD DATA END UK93481 HOLD DATA START UK93481 HOLD DATA END UK93488 HOLD DATA START UK93488 HOLD DATA END UK93532 HOLD DATA START UK93532 HOLD DATA END UK93554 HOLD DATA START UK93554 HOLD DATA END UK93556 HOLD DATA START UK93556 HOLD DATA END UK93558 HOLD DATA START UK93558 HOLD DATA END UK93559 HOLD DATA START UK93559 HOLD DATA END UK93596 HOLD DATA START UK93596 HOLD DATA END UK93614 HOLD DATA START UK93614 HOLD DATA END UK93629 HOLD DATA START UK93629 HOLD DATA END UK93641 HOLD DATA START UK93641 HOLD DATA END UK93644 HOLD DATA START UK93644 HOLD DATA END 1 UK93648 HOLD DATA START UK93648 HOLD DATA END UK93653 HOLD DATA START UK93653 HOLD DATA END UK93662 HOLD DATA START UK93662 HOLD DATA END UK93671 HOLD DATA START UK93671 HOLD DATA END UK93678 HOLD DATA START UK93678 HOLD DATA END UK93682 HOLD DATA START ++ HOLD(UK93682) SYS FMID(J2AG210) REASON(ACTION) DATE(13129) COMMENT (For existing users, to be able to use the functions: DB2GSE.IDXKEY2DG, DB2GSE.GETGRIDMBR 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.). UK93682 HOLD DATA END UK93705 HOLD DATA START UK93705 HOLD DATA END UK93709 HOLD DATA START UK93709 HOLD DATA END UK93711 HOLD DATA START UK93711 HOLD DATA END UK93716 HOLD DATA START ++ HOLD(UK82112) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13113) COMMENT (See PK71143 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. 1 APAR PK71143 corrects a problem that can cause RS00C90096 (number of page locks reached numlkus install limit) being issued for an update/delete/merge statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK93716 HOLD DATA END UK93725 HOLD DATA START UK93725 HOLD DATA END UK93753 HOLD DATA START ++ HOLD(UK93753) SYS FMID(HDBAA10) REASON(ACTION) DATE(13114) COMMENT (**Action for PM83778: Process the following command to bind the packages that updated as a result of installing this PTF: BIND PACKAGE(DSNJAR) MEMBER(DSNX9AJP) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') Note: is the data set prefix of your DB2 V9/V10 target libraries). UK93753 HOLD DATA END UK93800 HOLD DATA START UK93800 HOLD DATA END UK93810 HOLD DATA START ++ HOLD(UK93810) SYS FMID(HDBAA10) REASON(ACTION) DATE(13115) COMMENT (This APAR does not fix the existing bad values that are currently in the catalog. The following query can be used to see if there are any bad values in the catalog table. SELECT COUNT(*) FROM SYSIBM.SYSPACKDEP WHERE HEX(DOWNERTYPE) <> '20' AND HEX(DOWNERTYPE) <> '4C'; If the result number is greater than zero, there are bad values in the table. To fix the bad values, the user can take one of the following actions. 1. DROP/FREE the packages with the bad values and issue a new BIND PACKAGE command 2. Contact DB2 for z/OS Service to get the CATMAINT job to fix the bad values). UK93810 HOLD DATA END 1UK93840 HOLD DATA START UK93840 HOLD DATA END UK93907 HOLD DATA START UK93907 HOLD DATA END UK93911 HOLD DATA START UK93911 HOLD DATA END UK93912 HOLD DATA START UK93912 HOLD DATA END UK93918 HOLD DATA START UK93918 HOLD DATA END UK93936 HOLD DATA START UK93936 HOLD DATA END UK93941 HOLD DATA START UK93941 HOLD DATA END UK93943 HOLD DATA START UK93943 HOLD DATA END UK93953 HOLD DATA START UK93953 HOLD DATA END UK93957 HOLD DATA START ++ HOLD(UK93957) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13120) COMMENT (See PM82533 APAR/PTF text for additional information about why a REBIND is necessary. PM82533 corrects a problem of an SQL statement which contains a table expression, CTE or view that is used on the preserved side of OUTER JOIN, and this table expression, CTE or view contains a correlated IN subquery. DB2 may not choose to correlate/de- correlate the IN subquery due to aggressive table expression/ view merge, which may cause performance regression. After application of the PTF, when an internal serviceability feature is disabled on your system under the suggestion of DB2 service, the aggressive table expression/view merge will not happen for a table expression, CTE or view on the preserved side of OUTER JOIN that contains a correlated IN subquery. To make this fix effective for a static application, it must be rebound after application of this PTF and the internal 1 serviceability feature is disabled on your system. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK93957 HOLD DATA END UK93974 HOLD DATA START UK93974 HOLD DATA END UK93975 HOLD DATA START ++ HOLD(UK93975) SYS FMID(HDBAA10) REASON(ACTION) DATE(13121) COMMENT (This apar provides the ability to update the catalog to allow selects from the directory tables DBDR and SPTR. To verify if the catalog has already been updated run the query: SELECT * FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB01' AND NAME='DBD01'; The query will return one row if the catalog has been updated and zero rows if it has not been updated. If the query returns zero rows the catalog can be updated by running the utility job CATMAINT UPDATE UNLDDN PM80685 The job will replace any existing catalog rows for directory objects that existed before the job is run. This will invalidate packages that are dependent on the directory tables. The job is very quick and can be run at any time after applying the apar. Running the job multiple times will not cause any problems.). UK93975 HOLD DATA END UK93989 HOLD DATA START ++ HOLD(UK93989) SYS FMID(HDBAA10) REASON(ACTION) DATE(13121) COMMENT (***Action for PM82438 (V10) System Requirements: To take advantage of the new LOCAL date format support for 'dd/mm/yyyy' on IBM DB2 Analytics Accelerator, the following fixes are needed in conjunction with this PTF: For IBM DB2 Analytics Accelerator, PM80112/UK93624 must be applied. For Netezza, level NZ 6.0.8 P-6 or higher is needed. This PTF adds a new option, 4, to the DB2 subsystem parameter DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used to specify additional types of SQL queries to be included in query offloading. The new option is: * 4 : The queries that reference an expression with a DATE data type that 1 uses a LOCAL format are not blocked from executing on IBM DB2 Analytics Accelerator. IBM DB2 Analytics Accelerator will use the dd/mm/yyyy format as LOCAL format. The option 4 should be specified only when the DATE FORMAT field of install panel DSNTIP4 specifies LOCAL or when application programs that process SQL on DB2 have been precompiled with the DATE(LOCAL) option. In either case, the LOCAL date exit routine must also define the specific 'dd/mm/yyyy' date format. If the LOCAL format is not defined as 'dd/mm/yyyy', the query may return unpredictable results. If option 4 is specified on any member of a data sharing environment, it is recommended to specify it on all members. NONE remains the default setting for QUERY_ACCEL_OPTIONS and is mutually exclusive from all other settings. The options can be specified individually or together. Examples: QUERY_ACCEL_OPTIONS=NONE QUERY_ACCEL_OPTIONS=1 QUERY_ACCEL_OPTIONS=3 QUERY_ACCEL_OPTIONS=(1,2) QUERY_ACCEL_OPTIONS=(1,3) QUERY_ACCEL_OPTIONS=(1,2,4) No action is required after applying this PTF unless both of the following are true: * The DSN6SPRM.ACCEL parameter is set to AUTO or COMMAND to enable query acceleration. * The DSNHDECP.DATE parameter is set to LOCAL and the LOCAL date exit defines the specific dd/mm/yyyy date format. In that case, you need to take the following actions after applying this PTF: (1) Update your customized copy of job DSNTIJUZ (2) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is optional Update your customized copy of job DSNTIJUZ as follows: * Add or update the keyword parameter QUERY_ACCEL_OPTIONS= where is 4 or a list form such as (1,2,3,4) to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If your DSNTIJUZ job does not include QUERY_ACCEL_OPTIONS, that parameter will be set to the default of NONE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. 1 * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (2) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required only if you added or updated the setting for QUERY_ACCEL_OPTIONS in the previous step. If you added or modified the setting for QUERY_ACCEL_OPTIONS, you need to add or update the entry for it in all private copies of your CLIST output DSNTIDxx member. In each such copy, add or update the following line: QUERY_ACCEL_OPTIONS CHAR M NONE NONE Change to the value you specified for QUERY_ACCEL_OPTIONS above in DSNTIJUZ. If you do not add QUERY_ACCEL_OPTIONS to a DSNTIDxx member, the DB2 installation CLIST will assume QUERY_ACCEL_OPTIONS=NONE when run with that member as input.). UK93989 HOLD DATA END UK93990 HOLD DATA START ++ HOLD(UK93309) SYS FMID(HDBAA10) REASON(ACTION) DATE(13121) COMMENT (***Action for PM82100 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it your DB2 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration.). ++ HOLD(UK93990) SYS FMID(HDBAA10) REASON(ACTION) DATE(13121) COMMENT (***Action for PM81189 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it your DB2 1 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration.). UK93990 HOLD DATA END UK94034 HOLD DATA START ++ HOLD(UK94034) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13122) COMMENT (***Action for PM85671: See PM85671 APAR/PTF text for additional information about why a REBIND is necessary. PM85671 corrects a problem of a poorly performing access path for a partitioned table when: 1. DB2 uses an EQUAL predicate with host variables or parameter markers to limit the partitions for page range access, 2. The PLAN_TABLE shows PAGE_RANGE='Y', 3. There is at least one DPSI on the table, and 4. There is a GROUP BY or ORDER BY in the query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK94034 HOLD DATA END UK94056 HOLD DATA START UK94056 HOLD DATA END UK94063 HOLD DATA START ++ HOLD(UK94063) SYS FMID(HDBAA10) REASON(ACTION) DATE(13123) COMMENT ( After applying the fix for PM81712, specifying VERIFYSET will not be allowed for RECOVER utility using the keywords TOCOPY, TOLASTCOPY, or TOLASTFULLCOPY. Doing so will result in error message MSGDSNU052I (KEYWORD INCOMPATIBLE WITH OTHER KEYWORDS OR OPERANDS). This is because these kinds of RECOVER invocations each allow only one object to be recovered, so in most cases it would not be possible to recover a set of objects in this way. Users are advised that RECOVER jobs with TOCOPY, TOLASTCOPY, or TOLASTFULLCOPY will now fail if VERIFYSET is specified.). UK94063 HOLD DATA END UK94064 HOLD DATA START ++ HOLD(UK81474) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13123) COMMENT (***Action for PM69859: See PM69859 APAR/PTF text for additional information about why a REBIND is necessary. 1 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.). UK94064 HOLD DATA END UK94071 HOLD DATA START UK94071 HOLD DATA END UK94086 HOLD DATA START ++ HOLD(UK70649) SYS FMID(HDBAA10) REASON(ACTION) DATE(13126) COMMENT (***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.). UK94086 HOLD DATA END UK94092 HOLD DATA START UK94092 HOLD DATA END UK94094 HOLD DATA START UK94094 HOLD DATA END UK94099 HOLD DATA START UK94099 HOLD DATA END UK94119 HOLD DATA START UK94119 HOLD DATA END UK94142 HOLD DATA START UK94142 HOLD DATA END 1UK94148 HOLD DATA START UK94148 HOLD DATA END UK94150 HOLD DATA START UK94150 HOLD DATA END UK94222 HOLD DATA START UK94222 HOLD DATA END UK94230 HOLD DATA START ++ HOLD(UK94230) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13133) COMMENT (See PM83404 APAR/PTF text for additional information about why a REBIND is necessary. PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC P016 when the GETHINT built-in function is used to retrieve the hint for the password with which the data of a NOT NULL column were encrypted but there was no hint specified during data encryption. 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.). ++ HOLD(UK94230) SYS FMID(HDBAA10) REASON(ACTION) DATE(13133) COMMENT (PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC P016 when the GETHINT built-in function is used to retrieve the hint for the password with which the data of a NOT NULL column were encrypted but there was no hint specified during data encryption. To make this fix effective for any view, column mask, or row permission defined on expressions that contain the GETHINT function, the object must be regenerated using the ALTER VIEW REGENERATE, ALTER MASK REGENERATE, or ALTER PERMISSION REGENERATE statement, respectively, or dropped and recreated after application of this PTF. To make this fix effective for any MQT, SQL scalar UDF, or index defined on expressions that contain the GETHINT function, the object must be dropped and recreated after application of this PTF. After application of the PTF, the nullability of the GETHINT scalar function may be different. Applications using DESCRIBE may be impacted. Proper actions should be taken if such impact is observed. If the DSNTIAUL sample program is used correctly to generate a LOAD utility control statement, then after application of this PTF, the new control statement generated may not match the 1 nullability of the GETHINT scalar functions from the previous control statement. Proper action should be taken if such mismatch is observed. This PTF affects the nullability of the GETHINT built-in scalar function returned by dynamic SQL processing programs, such as SPUFI, DSNTEP2, and DSNTEP4. Proper actions should be taken if such change is observed.). UK94230 HOLD DATA END UK94232 HOLD DATA START UK94232 HOLD DATA END UK94239 HOLD DATA START UK94239 HOLD DATA END UK94265 HOLD DATA START UK94265 HOLD DATA END UK94283 HOLD DATA START UK94283 HOLD DATA END UK94311 HOLD DATA START ++ HOLD(UK69378) SYS FMID(HDBAA10) REASON(ACTION) DATE(13135) COMMENT (This fix corrects an SQLCODE20356 error when a TRUNCATE TABLE operation is run on a parent table that is defined with an informational referential constraint by use of the NOT ENFORCED keywords on the references-clause of the CREATE or ALTER TABLE statement. Note that if TRUNCATE TABLE is run on parent tables for which all constraints are informational (NOT ENFORCED), the TRUNCATE will no longer be blocked. Such a condition should have been ignored by TRUNCATE TABLE. Customers making use of TRUNCATE TABLE can verify whether an object has only informational constraints defined by examining the ENFORCED column of the DB2 Catalog table SYSIBM.SYSRELS for the object being truncated. The DB2 Version 10 SQL REFERENCE manual under TRUNCATE statement "NOTES Rules and restrictions" will be changed approximately as follows: "Rules and Restrictions: The truncate operation cannot be executed if the table is a parent table in an enforced referential constraint".). UK94311 HOLD DATA END UK94312 HOLD DATA START 1UK94312 HOLD DATA END UK94352 HOLD DATA START UK94352 HOLD DATA END UK94355 HOLD DATA START UK94355 HOLD DATA END UK94357 HOLD DATA START UK94357 HOLD DATA END UK94358 HOLD DATA START UK94358 HOLD DATA END UK94359 HOLD DATA START UK94359 HOLD DATA END UK94383 HOLD DATA START UK94383 HOLD DATA END UK94397 HOLD DATA START UK94397 HOLD DATA END UK94399 HOLD DATA START UK94399 HOLD DATA END UK94424 HOLD DATA START UK94424 HOLD DATA END UK94426 HOLD DATA START ++ HOLD(UK94426) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13137) COMMENT (See PM85237 APAR/PTF text for additional information about why a REBIND is necessary. PM85237 corrects an incorrect output problem that may occur when (1) sparse index access is used on a table, and (2) not all the eligible join predicates are used for the sparse index key. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK91647) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13137) COMMENT 1 (A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. APAR PM75619 corrects two problems. The first problem occurs on both V9 and V10. A query may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. The second problem occurs on V10 only. DB2 may not issue a REORG suggestion as it should. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92086) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13137) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM63095 corrects a problem of ABEND04E RC00C90101 in DSNIPSFI :5007 when executing an SQL statement containing a User Defined Function (UDF) with the DISALLOW PARALLEL parameter while parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK94426 HOLD DATA END UK94446 HOLD DATA START UK94446 HOLD DATA END UK94457 HOLD DATA START UK94457 HOLD DATA END UK94459 HOLD DATA START UK94459 HOLD DATA END UK94460 HOLD DATA START ++ HOLD(UK94460) SYS FMID(HDBAA10) REASON(ACTION) DATE(13140) COMMENT (This fix should be applied to V10 subsystems to handle the problem where inaccurate error messages could be issued when attempting to use new V10 bind parameters on previous version subsystems.). UK94460 HOLD DATA END UK94462 HOLD DATA START ++ HOLD(UK94462) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13140) COMMENT 1 (***Action for PM87084: See PM87084 APAR/PTF text for additional information about why a REBIND is necessary. PM87084 corrects a problem of incorrect output for a query with an ORDER BY clause that refers to a table with an OMNIFIND function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK94462 HOLD DATA END UK94483 HOLD DATA START UK94483 HOLD DATA END UK94499 HOLD DATA START UK94499 HOLD DATA END UK94503 HOLD DATA START ++ HOLD(UK82322) SYS FMID(HDBAA10) REASON(DOC) DATE(13142) COMMENT (PM63884 adds a documentation change in Utility Guide and Reference like the following: In Chapter 28. RESTORE SYSTEM,Utility Guide and Reference V10. Under the section "Authorization required": This RACF authority is required, because the RESTORE SYSTEM utility invokes DFSMSdss when tape is the input | and z/OS level is 1.11(or lower). However, when you | restore database copy pools from tape when z/OS level is | 1.12(or higher) or from a FlashCopy on disk, the RESTORE SYSTEM utility invokes DFSMShsm, which does not require Operations or DASDVOL authority. Chapter 28. RESTORE SYSTEM Under the section "How to determine which system-level backups DB2 restores": | The RESTORE SYSTEM utility invokes DFSMShsm to restore the database copy pool volumes from a system-level backup on | tape when running z/OS 1.12 or above. Otherwise, it invokes | DFSMSdss.). ++ HOLD(UK82322) SYS FMID(HDBAA10) REASON(ACTION) DATE(13142) COMMENT (After applying the fix for PM63384, users are advised that the job output of RESTORE SYSTEM utility from tape might not include DFSMSdss messages in cases where DFSMShsm is now called instead. This PTF has changed RESTORE SYSTEM to call DFSMShsm to 1 invoke DFSMSdss in its own address space (cross memory mode, XM) instead of DFSMShsm's address space when z/OS level is 1.12 or later. THE FOLLOWING IMPORTANT ACTION IS REQUIRED: APPLY HSM APAR OA40046 BEFORE OR AT THE SAME TIME PM63384 IS APPLIED. FAILURE TO DO SO CAN RESULT IN A FAILURE OF RESTORE SYSTEM IF PM63384 IS APPLIED AND ACTIVE ON DB2 BUT OA40046 IS NOT APPLIED AND ACTIVE ON HSM.). UK94503 HOLD DATA END UK94511 HOLD DATA START UK94511 HOLD DATA END UK94512 HOLD DATA START UK94512 HOLD DATA END UK94519 HOLD DATA START ++ HOLD(UK94462) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***Action for PM87084: See PM87084 APAR/PTF text for additional information about why a REBIND is necessary. PM87084 corrects a problem of incorrect output for a query with an ORDER BY clause that refers to a table with an OMNIFIND function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK94519) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***Action for PM85160: See PM85160 APAR/PTF text for additional information about why a REBIND is necessary. PM85160 corrects a problem of SQL performance when queries contain join predicates involving column expressions or queries joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK93392) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***Action for PM83457: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. 1 PM83457 corrects a problem that the DB2 optimizer may select an inefficient join sequence for a query if the query has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83543) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). ++ HOLD(UK90219) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). ++ HOLD(UK90222) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***Action for PM72676: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM72676 corrects a problem of inaccurate cost estimation for a query when the query contains nested non-correlated subqueries. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77770) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***Action for PM58932: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM58932 corrects a problem that DB2 may choose an inefficient join sequence for a query joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK68201) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). ++ HOLD(UK68203) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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 affected by this change.). ++ HOLD(UK66477) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). 1++ HOLD(UK66093) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). ++ HOLD(UK67419) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13149) COMMENT (***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.). UK94519 HOLD DATA END UK94558 HOLD DATA START UK94558 HOLD DATA END UK94559 HOLD DATA START UK94559 HOLD DATA END UK94562 HOLD DATA START ++ HOLD(UK94562) SYS FMID(HDBAA10) REASON(ACTION) DATE(13143) COMMENT (This PTF provides the new index configuration options for SYSTS_CREATE, SYSTS_UPDATE and SYSTS_ALTER stored procedures: UPDATEAUTOCOMMIT, COMMITTYPE and COMMITCYCLES. *************************************************************** Actions for customers who are already using DB2 10: *************************************************************** If you have already installed or migrated to DB2 10 then, after applying this PTF, you need to take the following action if you use the IBM Text Search for DB2 z/OS: Run your copy of job DSNTIJRT with MODE(INSTALL) to add new 1 rows to table SYSIBMTS.SYSTEXTSDEFAULTS and to refresh the packages for the IBM Text Search. 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. *************************************************************** *************************************************************** The following information will refer to the "IBM Text Search for DB2 for z/OS" book. (1) Download the most current version of IBMTS *********************************************************** * This action is required for Text Search customers *********************************************************** Download the most current version which is FIX R1L5.1 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 - TS_fixR1L5.1_linux32.zip Linux64 - TS_fixR1L5.1_linux64.zip Window32 - TS_fixR1L5.1_win32.zip Window64 - TS_fixR1L5.1_win64.zip zLinux - TS_fixR1L5.1_zlinux.zip For Window32/64: right click the zip then choose extract option For Linux32/Linux64/zlinux, change mode and unzip the files. Example: chmod 755 TS_fixR1L5.1_linux32.zip unzip TS_fixR1L5.1_linux32.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 1 product documentation for the IBM Text Search for DB2 z/OS. (2) 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. (3) 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. or --Installing fixes on top of the current server. (install IBMTS server on the existing server). (4) Where to find more information ---------------------------------------------------------------- The user can look for more information at: Installation, Administration, and Reference IBM Text Search for DB2 for z/OS: http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/ com.ibm.db2z10.doc.srchz/src/srchz/dasz_srchz.htm Administration stored procedures for text search: http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/ com.ibm.db2z10.doc.srchz/src/tpc/tsrch_storedpro.htm). ++ HOLD(UK93073) SYS FMID(HDBAA10) REASON(ACTION) DATE(13143) COMMENT (Please note that the following ACTIONS need to be performed with respect to this apar: 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.). 1++ HOLD(UK91455) SYS FMID(HDBAA10) REASON(ACTION) DATE(13143) COMMENT (***Action for PM72982 (V10) This PTF modifies DB2 installation program DSNTRIN to create the LOB table spaces in the DB2 XML Schema Registration (DSNXSR) database as LOGGED (by default) rather than NOT LOGGED. The affected table spaces are: SYSXSRA1, SYSXSRA2, SYSXSRA3, and SYSXSRA4. Use of the LOGGED attribute facilitates rollback and recovery by ensuring that changes made to the data in these table spaces are recorded in the DB2 log. This change has no effect on existing instances of these table spaces. If you have already created the DSNXSR database, you can alter these table spaces from NOT LOGGED to LOGGED by means of the following SQL statements: ALTER TABLESPACE DSNXSR.SYSXSRA1 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA2 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA3 LOGGED; ALTER TABLESPACE DSNXSR.SYSXSRA4 LOGGED; Because altering the logging attribute of a table space from NOT LOGGED to LOGGED can place the table space in COPY-pending status, you might need to copy the table spaces after completing this operation.). UK94562 HOLD DATA END UK94568 HOLD DATA START ++ HOLD(UK83996) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (***Action for PM74543: See PM74543 APAR/PTF text for additional information about why a REBIND is necessary. PM74543 corrects a problem of choosing a poorly performing access path for a partitioned table when queries involve partitioned tables, and EQUAL with host variables or parameter markers, and a DPSI (Data Partitioned Secondary Index). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83426) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (***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 1 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.). ++ HOLD(UK74779) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (***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.). ++ HOLD(UK71244) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (***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.). ++ HOLD(UK64444) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (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.). UK94568 HOLD DATA END UK94569 HOLD DATA START UK94569 HOLD DATA END 1 UK94585 HOLD DATA START UK94585 HOLD DATA END UK94588 HOLD DATA START UK94588 HOLD DATA END UK94591 HOLD DATA START UK94591 HOLD DATA END UK94593 HOLD DATA START UK94593 HOLD DATA END UK94599 HOLD DATA START UK94599 HOLD DATA END UK94613 HOLD DATA START UK94613 HOLD DATA END UK94635 HOLD DATA START ++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(13148) COMMENT (***Action for PM58951 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58951 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier.). UK94635 HOLD DATA END UK94639 HOLD DATA START ++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(13148) COMMENT (***Action for PM58952 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the 1 SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58952 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier.). UK94639 HOLD DATA END UK94648 HOLD DATA START UK94648 HOLD DATA END UK94651 HOLD DATA START UK94651 HOLD DATA END UK94661 HOLD DATA START UK94661 HOLD DATA END UK94683 HOLD DATA START ++ HOLD(UK94683) SYS FMID(HDBAA10) REASON(DOC) DATE(13149) COMMENT (PM81419 introduces the following changes to externals: DB2 calls z/OS XMLSS for XML parsing and validation. When the z/OS XMLSS function calls end abnormally(e.g. abend), DB2 is modified to issue SQLCODE -20101 with new reason code token instead of issuing SQLCODE -904. Five new reason codes are added to SQLCODE -20101. -20101 THE FUNCTION function-name FAILED WITH REASON reason-code reason-code 00D50006 The z/OS XMLSS function, GXL4INI call ended abnormally. This reason code may also be issued when the XMLPARSE or DSN_XMLVALIDATE functions are implicitly invoked. 00D50007 The z/OS XMLSS function, GXL4CTL call ended abnormally. This reason code may also be issued when the XMLPARSE or DSN_XMLVALIDATE functions are implicitly invoked. 00D50008 The z/OS XMLSS function, GXL4PRS call ended abnormally. This reason code may also be issued when the XMLPARSE or DSN_XMLVALIDATE functions are implicitly invoked. 00D50009 The z/OS XMLSS function, GXL4QXD call ended abnormally. This reason code may also be issued when the XMLPARSE or DSN_XMLVALIDATE functions are implicitly invoked. 1 00D5000A The z/OS XMLSS function, GXL4TRM call ended abnormally. This reason code may also be issued when the XMLPARSE or DSN_XMLVALIDATE functions are implicitly invoked. Programmer response 00D50006 to 00D5000A If you determine that your application is not the source of the error, contact IBM Software Support. 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.). UK94683 HOLD DATA END UK94695 HOLD DATA START ++ HOLD(UK94695) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13155) COMMENT (***Action for PM84536: See PM84536 APAR/PTF text for additional information about why a REBIND is necessary. PM84536 corrects a problem of ABEND04E RC00E72018 at location DSNXGRDS.DSNXSINE: 1342 when an SQL statement satisfies all of the following conditions: 1. a table expression or VIEW (VW#1) is defined with multiple SETOPs; 2. another table expression or VIEW referenced in VW#1 is also defined with multiple SETOPs. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK94695 HOLD DATA END UK94697 HOLD DATA START UK94697 HOLD DATA END UK94713 HOLD DATA START UK94713 HOLD DATA END UK94727 HOLD DATA START UK94727 HOLD DATA END UK94729 HOLD DATA START UK94729 HOLD DATA END 1UK94763 HOLD DATA START UK94763 HOLD DATA END UK94764 HOLD DATA START UK94764 HOLD DATA END UK94765 HOLD DATA START UK94765 HOLD DATA END UK94766 HOLD DATA START ++ HOLD(UK94766) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13151) COMMENT (***Action for PM86374 (DB2 10) This PTF adds a new option, DISABLE_IMPCAST_NJV, to the DB2 subsystem parameter DSN6FAC.DDF_COMPATIBILITY. You can use the DDF_COMPATIBILITY parameter to enable DB2 10 DDF compatibility with older client drivers. The new DDF_COMPATIBILITY option is: - DISABLE_IMPCAST_NJV: Use the pre-V10 server compatibility behavior which is not to implicitly cast input host variables during server host variable bind-in processing. This option provides such compatibility only for non-Java IBM Data Server drivers at or below Version 10.5. It is ignored for any non-Java IBM Data Server driver at any higher level. This option is deprecated in DB2 10. If the DISABLE_IMPCAST_NJV option is specified on any member of a data sharing environment, it is recommended to specify it on all members. DDF_COMPATIBILITY options can be specified individually or together. Examples: DDF_COMPATIBILITY= DDF_COMPATIBILITY=DISABLE_IMPCAST_NJV DDF_COMPATIBILITY=SP_PARMS_NJV DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_NJV) The default for DDF_COMPATIBILITY remains null (as shown in the first example above) meaning that DB2 10 DDF behavior is maintained with all clients. 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 1 (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 who want to use the DISABLE_IMPCAST_NJV option of the DDF_COMPATIBILITY parameter, with or without the SP_PARMS_NJV option After applying this PTF, edit your customized copy of job DSNTIJUZ as follows: * Add or update the DDF_COMPATIBILITY keyword parameter in one of the following formats: DDF_COMPATIBILITY=DISABLE_IMPCAST_NJV, DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_NJV), to the invocation of the DSN6FAC macro. Make sure to add a continuation character in column 72 if needed. If you omit adding DDF_COMPATIBILITY here, the value will be set to the default of null 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 modifies the entry for DDF_COMPATIBILITY in the CLIST default input members in the SDSNSAMP target library. You need to add or update this entry in all private copies of your CLIST output DSNTIDxx member. In each such copy, convert any existing DDF_COMPATIBILITY entry in this format DDF_COMPATIBILITY CHARR M NONE NONE to the format below. If no entry for DDF_COMPATIBILITY is present, add one that is in the format below. DDF_COMPATIBILITY STR M Change to NULL if you skipped step (2), above. Otherwise, change to one of the following: 1 SP_PARMS_NJV, DISABLE_IMPCAST_NJV SP_PARMS_NJV,DISABLE_IMPCAST_NJV If you do not add DDF_COMPATIBILITY to a DSNTIDxx member, the DB2 installation CLIST will assume 'DDF_COMPATIBILITY=,' when run with that member as input.). UK94766 HOLD DATA END UK94778 HOLD DATA START UK94778 HOLD DATA END UK94786 HOLD DATA START UK94786 HOLD DATA END UK94806 HOLD DATA START ++ HOLD(UK94806) SYS FMID(HDBAA10) REASON(ACTION) DATE(13161) COMMENT (The PTF for APAR PM73034 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.). UK94806 HOLD DATA END UK94814 HOLD DATA START UK94814 HOLD DATA END UK94828 HOLD DATA START UK94828 HOLD DATA END UK94837 HOLD DATA START UK94837 HOLD DATA END UK94845 HOLD DATA START ++ HOLD(UK94845) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13162) COMMENT (***Action for PM84153: See PM84153 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM84153 corrects a problem that incorrect output may occur if an ORDER BY expression with DESC is specified in a table expression and the table expression is materialized for merge scan join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK94845 HOLD DATA END UK94861 HOLD DATA START UK94861 HOLD DATA END UK94868 HOLD DATA START UK94868 HOLD DATA END UK94915 HOLD DATA START UK94915 HOLD DATA END UK94916 HOLD DATA START ++ HOLD(UK94916) SYS FMID(HDBAA10) REASON(ACTION) DATE(13157) COMMENT (PM85880 fixes a timing window which may result in the following orphaned rows: o SYSIBM.SYSPACKDEP and SYSIBM.SYSPLANDEP records if DB2 fails to invalidate dependent plans and packages when DROP ALIAS is run concurrently with DML referencing the same alias. o SYSIBM.SYSDEPENDENCIES records when DROP ALIAS is run concurrently with CREATE MASK or CREATE PERMISSION referencing the same alias. With PM85880 applied, concurrently running statements referencing the alias being dropped may result in SQLCODE -911 or SQLCODE -904. This apar does not fix existing orphaned SYSIBM.SYPACKDEP, SYSIBM.SYSPLANDEP or SYSIBM.SYSDEPENDENCIES records. If orphaned SYSIBM.SYPACKDEP or SYSIBM.SYSPLANDEP rows are identified, remove any reference of the dropped alias and rebind plans and packages. If SYSIBM.SYSDEPENDENCIES rows are identified, the dependent mask or permission will need to be dropped and recreated without referencing the dropped alias. The following queries are provided as examples of how to identify the orphaned records. QUERY1 ------ 1 SYSPLANDEP records the dependencies that a given plan has on other DB2 objects. For every row in SYSPLANDEP that indicates a dependency upon an alias, there should be a corresponding row in SYSTABLES. SELECT BNAME, BCREATOR, BTYPE, DNAME FROM SYSIBM.SYSPLANDEP PD WHERE BTYPE IN ('A') AND NOT EXISTS (SELECT * FROM SYSIBM.SYSTABLES WHERE CREATOR = PD.BCREATOR AND NAME = PD.BNAME AND TYPE = PD.BTYPE); QUERY2 ------ SYSPACKDEP records the dependencies that a given package has on other DB2 objects. For every row in SYSPACKDEP that indicates a dependency upon an alias, there should be a corresponding row in SYSTABLES. SELECT BNAME, BQUALIFIER, BTYPE, DNAME FROM SYSIBM.SYSPACKDEP PD WHERE BTYPE IN ('A') AND NOT EXISTS (SELECT * FROM SYSIBM.SYSTABLES WHERE CREATOR = PD.BQUALIFIER AND NAME = PD.BNAME AND TYPE = PD.BTYPE ); QUERY3 ------ SYSDEPENDENCIES records the dependencies between objects. For every row in SYSDEPENDENCIES that indicates a dependency upon an alias, there should be a corresponding row in SYSTABLES. SELECT * FROM SYSIBM.SYSDEPENDENCIES DEP WHERE BTYPE IN ('A') AND NOT EXISTS (SELECT * FROM SYSIBM.SYSTABLES WHERE CREATOR = DEP.BSCHEMA AND NAME = DEP.BNAME AND TYPE = DEP.BTYPE);). UK94916 HOLD DATA END UK94918 HOLD DATA START UK94918 HOLD DATA END UK94919 HOLD DATA START UK94919 HOLD DATA END 1 UK94920 HOLD DATA START UK94920 HOLD DATA END UK94931 HOLD DATA START UK94931 HOLD DATA END UK94952 HOLD DATA START ++ HOLD(UK94952) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***Action for PM87836: See PM87836 APAR/PTF text for additional information about why a REBIND is necessary. PM87836 corrects problems of incorrect UNCERTAINTY values in DSN_PREDICAT_TABLE and incorrect cost fields in DSN_DETCOST_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.). ++ HOLD(UK81765) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***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.). ++ HOLD(UK79977) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***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 1 letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK79324) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***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.). ++ HOLD(UK79618) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***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.). ++ HOLD(UK71709) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***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.). ++ HOLD(UK69998) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13158) COMMENT (***Action for PM32384: See PM32384 APAR/PTF text for additional information about 1 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.). ++ HOLD(UK94952) SYS FMID(HDBAA10) REASON(ACTION) DATE(13158) COMMENT (PM87836 does not correct the incorrect values that are already in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE. The incorrect values may or may not be readily identifiable as incorrect by simple visual inspection. To get the correct values, apply this fix. Then, delete the old rows in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE. EXPLAIN the statements again to re-populate the DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE with the correct values.). UK94952 HOLD DATA END UK94967 HOLD DATA START UK94967 HOLD DATA END UK94999 HOLD DATA START ++ HOLD(UK94999) SYS FMID(HDBAA10) REASON(ACTION) DATE(13161) COMMENT (***Action for PM85375 (V10) 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 10 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 DB2 10 IVP jobs after DB2 enters new-function mode. * On DB2 10 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.). ++ HOLD(UK77883) SYS FMID(HDBAA10) REASON(ACTION) DATE(13161) COMMENT 1 (***Action for PM59506 (V10) (1) A DSNTEP2 or DSNTEP4 job that uses the parameter SQLTERM 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.). UK94999 HOLD DATA END UK95001 HOLD DATA START UK95001 HOLD DATA END UK95005 HOLD DATA START ++ HOLD(UK95005) SYS FMID(HDBAA10) REASON(ACTION) DATE(13162) COMMENT (***Action for PM88761 (DB2 10) This PTF modifies the DCLGEN tool to prevent failures caused by SQLCODE -495 (resource limit restrictions). If you have already installed or migrated to DB2 10 for z/OS then after applying this PTF, you need to rebind the DCLGEN package. You can use the following command: BIND PACKAGE(DSNEDCL) MEMBER(DSNECP68) - ACTION(ADD) ISOLATION(CS) ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where prefix is the prefix of your DB2 10 target libraries.). UK95005 HOLD DATA END 1UK95006 HOLD DATA START UK95006 HOLD DATA END UK95009 HOLD DATA START UK95009 HOLD DATA END UK95026 HOLD DATA START ++ HOLD(UK94845) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13163) COMMENT (***Action for PM84153: See PM84153 APAR/PTF text for additional information about why a REBIND is necessary. PM84153 corrects a problem that incorrect output may occur if an ORDER BY expression with DESC is specified in a table expression and the table expression is materialized for merge scan join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77552) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13163) COMMENT (***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.). ++ HOLD(UK76589) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13163) COMMENT (***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.). 1++ HOLD(UK75906) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13163) COMMENT (See PM53285 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM53285 fixes an execution time abend when a query contains a user-defined function and 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.). UK95026 HOLD DATA END UK95038 HOLD DATA START UK95038 HOLD DATA END UK95040 HOLD DATA START UK95040 HOLD DATA END UK95042 HOLD DATA START UK95042 HOLD DATA END UK95045 HOLD DATA START UK95045 HOLD DATA END UK95047 HOLD DATA START UK95047 HOLD DATA END UK95057 HOLD DATA START UK95057 HOLD DATA END UK95082 HOLD DATA START ++ HOLD(UK95082) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13164) COMMENT (See PM89112 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM89112 corrects a problem that can cause an abend at DSNIIMSI:5008 for a query containing CTE. 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.). ++ HOLD(UK92492) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13164) COMMENT (***Action for PM79464: 1 See PM79464 APAR/PTF text for additional information about why a REBIND is necessary. PM79464 corrects a problem of ABEND04E RC00E70005 DSNXOSR:P014 when a query has one miniplan with PARALLELISM ON and MERGC = YES and SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T' and the query has a GROUP BY clause. 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.). UK95082 HOLD DATA END UK95094 HOLD DATA START UK95094 HOLD DATA END UK95131 HOLD DATA START UK95131 HOLD DATA END UK95132 HOLD DATA START UK95132 HOLD DATA END UK95141 HOLD DATA START ++ HOLD(UK95141) SYS FMID(HDBAA10) REASON(DOC) DATE(13165) COMMENT (***Documentation for PM81247: See UK95141 HOLD data for additional information. In DB2 10 for z/OS, a user with EXPLAIN privilege, running an application attempting to execute an SQL statement that he does not have authority to execute will receive warning message with SQLCODE +4726, SQLSTATE 0168Z followed by SQLCODE -551, SQLSTATE 42501 instead of SQLCODE -514 or SQLCODE -518. The documentation for following SQL codes are updated to remove the reference to EXPLAIN privilege from SQLCODE -514 and -518 as below: -514: THE CURSOR cursor-name IS NOT IN A PREPARED STATE Explanation: The application program has tried to use a cursor, 'cursor-name' that is not in a prepared state. The cursor is associated with a statement that: 1. Was never prepared. 2. Was invalidated by a commit or rollback operations System action: The statement cannot be processed. 1 Programmer response: For case 1, ensure that you prepare the statement that is named in the DECLARE CURSOR statement for 'cursor-name' before you try to open the cursor. For case 2, take one of the following actions: - Use the WITH HOLD option of DECLARE CURSOR. - Do not execute a commit or rollback operation until you are finished using the cursor. - Prepare the statement again after the commit or rollback. SQLSTATE 26501 -518: THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT. Explanation: One of the following conditions exists: - The statement identified in the EXECUTE statement has not been prepared. - The statement identified in the EXECUTE statement identifies a SELECT, or ASSOCIATE LOCATORS statement. - The statement identified in the EXECUTE IMMEDIATE statement identifies a SELECT or ASSOCIATE LOCATORS statement. System action: The statement cannot be processed. Programmer response: Ensure that you prepare the statement prior to EXECUTE. Also, ensure that the statement prepared is not: - A SELECT statement. - An ASSOCIATE LOCATORS statement. SQLSTATE 07003). UK95141 HOLD DATA END UK95142 HOLD DATA START UK95142 HOLD DATA END UK95148 HOLD DATA START ++ HOLD(UK94681) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13166) COMMENT (***Action for PM84178: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM84178 corrects a problem of poor performance of a query if the query selects an index which matches multiple IN-subquery predicates and there are many records qualified from these subqueries. 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.). ++ HOLD(UK81384) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13166) COMMENT (***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.). ++ HOLD(UK80981) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13166) COMMENT (***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.). UK95148 HOLD DATA END UK95172 HOLD DATA START UK95172 HOLD DATA END UK95190 HOLD DATA START UK95190 HOLD DATA END UK95238 HOLD DATA START UK95238 HOLD DATA END UK95240 HOLD DATA START UK95240 HOLD DATA END UK95251 HOLD DATA START UK95251 HOLD DATA END 1 UK95252 HOLD DATA START UK95252 HOLD DATA END UK95255 HOLD DATA START UK95255 HOLD DATA END UK95264 HOLD DATA START ++ HOLD(UK95264) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13170) COMMENT (***Action for PM88763: See PM88763 APAR/PTF text for additional information about why a REBIND is necessary. PM88763 corrects a problem of an ABEND04E RC00E70005 in DSNXGRDS.DSNXRTIM:P008 occured when running a Native SQL procedure which contains timestamp data type SQL variable, this procedure is created in DB2 9 for z/OS, rebound in DB2 10 for z/OS. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK95264 HOLD DATA END UK95265 HOLD DATA START UK95265 HOLD DATA END UK95271 HOLD DATA START UK95271 HOLD DATA END UK95283 HOLD DATA START ++ HOLD(UK95283) SYS FMID(HDBAA10) REASON(ACTION) DATE(13171) COMMENT (***Action for PM88612: This apar corrects rows for the SYSIBM.SYSLGRNX table in SYSIBM.SYSCOLUMNS table. To verify if the catalog has already been updated run the query: SELECT * FROM SYSIBM.COLUMNS WHERE COL.TBNAME='SYSLGRNX' AND FOREIGNKEY='B' The query will return seven rows if the catalog has been updated and zero rows if it has not been updated. If the query returns zero rows the catalog can be updated by running the utility job CATMAINT UPDATE UNLDDN PM88612 1 The job will replace any existing catalog rows for directory objects that existed before the job is run. This will invalidate packages that are dependent on the directory tables. The job is very quick and can be run at any time after applying the apar. Running the job multiple times will not cause any problems.). ++ HOLD(UK93975) SYS FMID(HDBAA10) REASON(ACTION) DATE(13171) COMMENT (This apar provides the ability to update the catalog to allow selects from the directory tables DBDR and SPTR. To verify if the catalog has already been updated run the query: SELECT * FROM SYSIBM.SYSTABLESPACE WHERE DBNAME='DSNDB01' AND NAME='DBD01'; The query will return one row if the catalog has been updated and zero rows if it has not been updated. If the query returns zero rows the catalog can be updated by running the utility job CATMAINT UPDATE UNLDDN PM80685 The job will replace any existing catalog rows for directory objects that existed before the job is run. This will invalidate packages that are dependent on the directory tables. The job is very quick and can be run at any time after applying the apar. Running the job multiple times will not cause any problems.). UK95283 HOLD DATA END UK95285 HOLD DATA START UK95285 HOLD DATA END UK95292 HOLD DATA START UK95292 HOLD DATA END UK95295 HOLD DATA START ++ HOLD(UK94096) SYS FMID(HDBAA10) REASON(DOC) DATE(13171) COMMENT (PM70981 introduces the following changes to externals: Changed messages or codes: description of change DSNB411I: Page read statistics When you specify the DETAIL option, the output includes the page read statistics for the buffer pool. DSNB411I - RANDOM GETPAGE = rgp SYNC READ I/O (R) = srr SEQ. GETPAGE = sgp 1 SYNC READ I/O (S) = srs DMTH HIT = dmt PAGE-INS REQ = pir SEQUENTIAL = seq VPSEQT HIT = vsh RECLASSIFY = rcy RANDOM GETPAGE = rgp The number of nonsequential GETPAGE requests. SYNC READ I/O (R) = srr The number of synchronous read I/O operations for nonsequential GETPAGE requests. SEQ. GETPAGE = sgp The number of sequential GETPAGE requests. SYNC READ I/O (S) = srs The number of synchronous read I/O operations for sequential GETPAGE requests. DMTH HIT = dmt The number of times that the data management threshold was reached. PAGE-INS REQ = pir The number of page-in operations that are required for read I/O. SEQUENTIAL = seq The number of buffers on the sequential least-recently-used (SLRU) chain. VPSEQT HIT = vsh The number of times that the size of the SLRU chain reached the sequential steal threshold (the VPSEQT value) for the buffer pool. RECLASSIFY = rcy A statistic that is used by IBM® for serviceability. Information about this changed message will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). ++ HOLD(UK82633) SYS FMID(HDBAA10) REASON(ACTION) DATE(13171) COMMENT (In order for DB2 to use "suppress cross-invalidation" enhancement for DELETE_NAME, all of the following must be true: - This PTF must be applied to the DB2 member that performs castout - The GBP must be allocated in a coupling facility of CFLEVEL=17 or higher. The following CFCC release supports the "suppress cross-invalidation" functionality: - z114 (2818) DR93G CFCC EC N48162 CFCC Release 17 at the requisite microcode load (MCL) level - z196 (2817) DR93G CFCC EC N48162 CFCC Release 17 at the requisite microcode load (MCL) level - zEC12 (2827) CFCC Release 18 - The DB2 member that performs castout must be running on z114 1 or z196 that supports the "suppress cross-invalidation" functionality or a zEC12. The following z/OS releases support the "suppress cross-invalidation" functionality: - z/OS V1R12 and above with APAR OA38419 installed). ++ HOLD(UK94096) SYS FMID(HDBAA10) REASON(AO) DATE(13171) COMMENT (PM70981 introduces the following changes to externals: Changed messages or codes: description of change DSNB411I: Page read statistics When you specify the DETAIL option, the output includes the page read statistics for the buffer pool. DSNB411I - RANDOM GETPAGE = rgp SYNC READ I/O (R) = srr SEQ. GETPAGE = sgp SYNC READ I/O (S) = srs DMTH HIT = dmt PAGE-INS REQ = pir SEQUENTIAL = seq VPSEQT HIT = vsh RECLASSIFY = rcy RANDOM GETPAGE = rgp The number of nonsequential GETPAGE requests. SYNC READ I/O (R) = srr The number of synchronous read I/O operations for nonsequential GETPAGE requests. SEQ. GETPAGE = sgp The number of sequential GETPAGE requests. SYNC READ I/O (S) = srs The number of synchronous read I/O operations for sequential GETPAGE requests. DMTH HIT = dmt The number of times that the data management threshold was reached. PAGE-INS REQ = pir The number of page-in operations that are required for read I/O. SEQUENTIAL = seq The number of buffers on the sequential least-recently-used (SLRU) chain. VPSEQT HIT = vsh The number of times that the size of the SLRU chain reached the sequential steal threshold (the VPSEQT value) for the buffer pool. RECLASSIFY = rcy A statistic that is used by IBM® for serviceability. Information about this changed message will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). UK95295 HOLD DATA END 1 UK95318 HOLD DATA START ++ HOLD(UK95318) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13172) COMMENT (***Action for PM86069: See PM86069 APAR/PTF text for additional information about why a REBIND is necessary. PM86069 corrects a problem of An ABEND04E RC00E2000F at location DSNXEFB.DSNSVSFB: 0858 may occur when a SQL statement satisfies all of the following conditions: 1. a table expression is defined with set operation (such as: UNION ALL); 2. a column defined with fieldproc and a constant are referenced in different SELECT list of full-select under the set operation from step #1 3. an aggregate function with parameter which is from the table expression defined in step #1 and corresponds to the column defined with fieldproc; 4. a GROUP BY clause 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.). ++ HOLD(UK94695) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13172) COMMENT (***Action for PM84536: See PM84536 APAR/PTF text for additional information about why a REBIND is necessary. PM84536 corrects a problem of ABEND04E RC00E72018 at location DSNXGRDS.DSNXSINE: 1342 when an SQL statement satisfies all of the following conditions: 1. a table expression or VIEW (VW#1) is defined with multiple SETOPs; 2. another table expression or VIEW referenced in VW#1 is also defined with multiple SETOPs. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK95318 HOLD DATA END UK95334 HOLD DATA START UK95334 HOLD DATA END UK95336 HOLD DATA START UK95336 HOLD DATA END 1 UK95350 HOLD DATA START UK95350 HOLD DATA END UK95354 HOLD DATA START ++ HOLD(UK63680) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13175) COMMENT (See PM22534 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM22534 corrects a storage overlay problem when star join is enabled and the number of internal tables created by star join processing exceeds the max number of tables supported by DB2. After the overlay occurs, various abends can happen. 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.). UK95354 HOLD DATA END UK95360 HOLD DATA START ++ HOLD(UK95360) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13178) COMMENT (See PM82487 APAR/PTF text for additional information about why a REBIND is necessary. PM82487 corrects an ABEND04E RC00D31108 problem which can occur at location DSNLILLM.DSNLCCLO:0004 when the following conditions are met for a given query. 1. When a LOB data type is used as an input host variable or parameter marker. 2. When REOPT(AUTO) is specified. 3. When DB2 is distributed (DRDA). The abend can occur because DB2 may try to pull the LOB data twice. 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.). ++ HOLD(UK82805) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13178) COMMENT (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 1 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.). ++ HOLD(UK69694) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13178) COMMENT (***Action for PM35294: See PM35294 APAR/PTF text for additional information about why a REBIND is necessary. PM35294 corrects a problem where incorrect output may occur if a query contains a host variable or a parameter marker, and a special register: CURRENT TIMESTAMP, CURRENT TIME or CURRENT DATE, with BIND option REOPT(AUTO). 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.). ++ HOLD(UK70107) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13178) COMMENT (***Action for PM34595: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM34595 corrects a problem that an ABEND0C4 RC00000038 in DSNXORRA OFFSET 0DF2 may occur when binding a package or plan with bind option REOPT(AUTO) and the package or plan contains a query with special register CURRENT DATE, CURRENT TIME or CURRENT TIMESTAMP. 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.). UK95360 HOLD DATA END UK95365 HOLD DATA START UK95365 HOLD DATA END UK95368 HOLD DATA START UK95368 HOLD DATA END UK95371 HOLD DATA START UK95371 HOLD DATA END 1UK95375 HOLD DATA START UK95375 HOLD DATA END UK95379 HOLD DATA START ++ HOLD(UK95379) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13176) COMMENT (***Action for PM88698: See PM88698 APAR/PTF text for additional information about why a REBIND is necessary. PM88698 corrects a problem that incorrect output could happen for an SQL statement that contains special registers in GRPOUP BY and 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.). UK95379 HOLD DATA END UK95412 HOLD DATA START ++ HOLD(UK95412) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13193) COMMENT (***Action for PM90480: See PM90480 APAR/PTF text for additional information about why a REBIND is necessary. PM90480 corrects a problem of inaccurate compound filter factor of two RANGE predicates on the same column 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.). UK95412 HOLD DATA END UK95443 HOLD DATA START UK95443 HOLD DATA END UK95466 HOLD DATA START UK95466 HOLD DATA END UK95475 HOLD DATA START UK95475 HOLD DATA END UK95476 HOLD DATA START UK95476 HOLD DATA END 1 UK95478 HOLD DATA START UK95478 HOLD DATA END UK95479 HOLD DATA START ++ HOLD(UK71132) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13177) COMMENT (A rebind is necessary to rebuild package and/or plan structure based on the changes in this APAR. PM42530 corrects a problem that an ABEND0CF RC0000000F in DSNXORRA OFFSET 0B74 may occur when executing a package or plan with bind option REOPT(AUTO) and the plan used has a R-scan with cost of 7FFFFFFF. 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.). UK95479 HOLD DATA END UK95484 HOLD DATA START UK95484 HOLD DATA END UK95494 HOLD DATA START UK95494 HOLD DATA END UK95495 HOLD DATA START UK95495 HOLD DATA END UK95497 HOLD DATA START UK95497 HOLD DATA END UK95511 HOLD DATA START UK95511 HOLD DATA END UK95538 HOLD DATA START UK95538 HOLD DATA END UK95544 HOLD DATA START ++ HOLD(UK95544) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13179) COMMENT (***Action for PM89078: See PM89078 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM89078 corrects incorrect output for an SQL statement with inlist table access and field proc 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.). UK95544 HOLD DATA END UK95551 HOLD DATA START UK95551 HOLD DATA END UK95553 HOLD DATA START UK95553 HOLD DATA END UK95633 HOLD DATA START ++ HOLD(UK95633) SYS FMID(HDBAA10) REASON(ACTION) DATE(13188) COMMENT (The PTF for APAR PM80707 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.). UK95633 HOLD DATA END UK95655 HOLD DATA START UK95655 HOLD DATA END UK95657 HOLD DATA START UK95657 HOLD DATA END UK95658 HOLD DATA START UK95658 HOLD DATA END UK95661 HOLD DATA START UK95661 HOLD DATA END UK95681 HOLD DATA START UK95681 HOLD DATA END 1 UK95718 HOLD DATA START ++ HOLD(UK81171) SYS FMID(HDBAA10) REASON(DOC) DATE(13191) COMMENT (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.). UK95718 HOLD DATA END UK95721 HOLD DATA START ++ HOLD(UK95721) SYS FMID(HDBAA10) REASON(ACTION) DATE(13191) COMMENT (***Action for PM88656 (DB2 10 for z/OS) This PTF adds statements to job DSNTIJSG to bind and grant access on DSNX9LDJ, the package for the DB2 stored procedures Java class loader. If you have already installed or migrated to DB2 10 then you need to take the following actions after applying this PTF: (1) Update private copies of the installation CLIST (2) Update your customized copy of job DSNTIJSG (3) Grant execute access on package DSNX9LDJ Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update private copies of the installation CLIST *********************************************************** * All customers need to perform this step *********************************************************** This PTF modifies the DB2 installation CLIST member DSNTINS1 in the prefix.SDSNCLST target library. After applying this PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of DSNTINS1. 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 DSNTIJSG *********************************************************** * All customers who maintain a private copy of DSNTIJSG 1 * need to perform this step *********************************************************** (a) Add the following in job step DSNTIRU: BIND PACKAGE(DSNJAR) MEMBER(DSNX9LDJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) - ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where is the high-level qualifier for the target DB2 subsystem. (b) Add the following GRANT statement in step DSNTIJG GRANT EXECUTE ON PACKAGE DSNJAR.DSNX9LDJ TO PUBLIC; and optionally change PUBLIC to one or more authorization IDs that need to use Java stored procedures. ---------------------------------------------------------------- (3) Grant execute access on package DSNX9LDJ *********************************************************** * All customers who use Java stored procedures need to * perform this step. *********************************************************** Submit a job that contains the following GRANT statement: GRANT EXECUTE ON PACKAGE DSNJAR.DSNX9LDJ TO PUBLIC; after optionally changing PUBLIC to one or more authorization IDs that need to use Java stored procedures. The user ID for this job must have authorization to grant this authority on the package. Note: It is presumed that a package for DSNX9LDJ in collection ID DSNJAR already exists. If the above GRANT request fails with SQLCODE -204 then submit a job that contains the following BIND statement BIND PACKAGE(DSNJAR) MEMBER(DSNX9LDJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) - ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where is the high-level qualifier for the target DB2 subsystem. Then rerun the GRANT statement.). ++ HOLD(UK80615) SYS FMID(HDBAA10) REASON(ACTION) DATE(13191) COMMENT (***Action for PM65113 (V10) This PTF modifies the DB2 installation CLIST and job DSNTIJSG 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 1 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 CCSID UNICODE USING STOGROUP DSNOPTSG; to: 1 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). UK95721 HOLD DATA END UK95726 HOLD DATA START UK95726 HOLD DATA END UK95752 HOLD DATA START ++ HOLD(UK95752) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13192) COMMENT (***Action for PM90152: See PM90152 APAR/PTF text for additional information about why a REBIND is necessary. PM90152 corrects a problem of incorrect output (less rows than expected) when SELECT with GROUPBY with DECFLOAT column is in an expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92118) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13192) COMMENT (***Action for PM79782: See PM79782 APAR/PTF text for additional information about why a REBIND is necessary. PM79782 corrects a problem of ABEND0C4 at DSNXRWND OFFSET 0338 in DB2 V9 for z/OS or ABEND04E at DSNSVSFB OFFSET 0858 in DB2 V10 for z/OS. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change.). ++ HOLD(UK79559) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13192) COMMENT (***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.). UK95752 HOLD DATA END UK95781 HOLD DATA START UK95781 HOLD DATA END UK95795 HOLD DATA START ++ HOLD(UK95795) SYS FMID(HDBAA10) REASON(ACTION) DATE(13193) COMMENT (***Action for PM67806: This PTF adds an online-changeable subsystem parameter in DSN6SPRM called CACHE_DEP_TRACK_STOR_LIM that specifies the amount of storage in gigabytes that DB2 will allocate for hashing entries in the dynamic statement cache. Valid setting are integers in the range of 2 to 10. The default is 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 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 1 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 CACHE_DEP_TRACK_STOR_LIM=, where is an integer from 2 to 10, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding CACHE_DEP_TRACK_STOR_LIM here, the value will be set to the default of 2 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 CACHE_DEP_TRACK_STOR_LIM 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. In each such copy, add the following line: CACHE_DEP_TRACK_STOR_LIM NUM M 2 10 Change to the value you specified for CACHE_DEP_TRACK_STOR_LIM in step (2), above.). UK95795 HOLD DATA END UK95804 HOLD DATA START UK95804 HOLD DATA END UK95806 HOLD DATA START ++ HOLD(UK73621) SYS FMID(HDBAA10) REASON(ACTION) DATE(13197) COMMENT (APAR PM45561 fixes a problem that causes incorrect output for readers of XML data that use ISOLATION LEVEL(UR) and and potentially allows DB2 to cause the readers of XML data to wait for a lock, even though ISO(UR) is specified. The situation usually occurs during heavy concurrent insert, update, or delete activity. The incorrect output problem is fixed by requiring ISOLATION(UR) readers to wait for XML locks. As a result, ISOLATION(UR) readers that access XML data might see increased wait time for locks. The additional wait time for unconditional locks sometimes result in deadlocks or timeouts(SQLCODE -911 or -913),therefore, application logic may need to change to accommodate SQLCODEs -911 and -913.). ++ HOLD(UK63153) SYS FMID(HDBAA10) REASON(ACTION) DATE(13197) 1 COMMENT (TYPE: DB2 This fix corrects a problem with Compensation Log Records (CLRs) built for compression dictionary pages for classic (non-segmented) partitioned table spaces during insert. The problem is limited to classic partitioned table spaces that have an insert-generated compression dictionary and have been RECOVERED with log-apply. A dictionary page log record may not get applied correctly due to incorrect DBID/OBID, which happens under limited circumstances. Compression dictionaries built by DB2 LOAD or DB2 REORG are not affected. You can identify an insert-generated dictionary by checking the HPGZLD field in the page header of the header-page of each pageset/partition. HPGZLD would be = 'F' for an insert-generated dictionary. The symptoms of the problem include abends and/or error return codes in/from modules that try to use the dictionary pages, and/or DSNT501I RESOURCE UNAVAILABLE messages on the console with DB2 reason code = 00C9007F. The fix will correct the problem but it will not correct the log records already written with the error. So, after applying the fix, establishing new recovery bases for the table spaces which have the conditions specified above is advised. Forward log apply processes for such table spaces should not be performed against image copies taken prior to the application of the fix.). UK95806 HOLD DATA END UK95825 HOLD DATA START UK95825 HOLD DATA END UK95830 HOLD DATA START UK95830 HOLD DATA END UK95832 HOLD DATA START UK95832 HOLD DATA END UK95836 HOLD DATA START UK95836 HOLD DATA END UK95853 HOLD DATA START UK95853 HOLD DATA END UK95879 HOLD DATA START UK95879 HOLD DATA END 1 UK95893 HOLD DATA START UK95893 HOLD DATA END UK95915 HOLD DATA START UK95915 HOLD DATA END UK95923 HOLD DATA START ++ HOLD(UK95923) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13203) COMMENT (***Action for PM89798: See PM89798 APAR/PTF text for additional information about why a REBIND is necessary. PM89798 corrects a problem that incorrect output could happen for an SQL statement that satisfied all of the following conditions: 1. It contains multiple outer joins; 2. It contains a table expression that referencing a column out side of the table expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK82964) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13203) COMMENT (***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.). ++ HOLD(UK82964) SYS FMID(HDBAA10) REASON(ACTION) DATE(13203) COMMENT (***Action for PM74279: TYPE: ACT PM74279 corrects a problem of ABEND0C7 at DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur 1 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. 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.). UK95923 HOLD DATA END UK95925 HOLD DATA START UK95925 HOLD DATA END UK95950 HOLD DATA START UK95950 HOLD DATA END UK95953 HOLD DATA START UK95953 HOLD DATA END UK95971 HOLD DATA START UK95971 HOLD DATA END UK95978 HOLD DATA START UK95978 HOLD DATA END UK96041 HOLD DATA START UK96041 HOLD DATA END UK96043 HOLD DATA START UK96043 HOLD DATA END UK96045 HOLD DATA START ++ HOLD(UK70405) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13203) COMMENT (See PM43078 APAR/PTF text in the PTF cover letter for additional information about why REBIND PLAN is necessary. PM43078 fixes an unexpected SQLCODE -104 during REBIND PLAN in DB2 V10 NFM mode, or SQLCODE -924 with reason code 00E30302 during execution in V10 NFM mode if the PLAN is bound directly with DBRMs in DB2 V8. To make this fix effective for plans already been executed once, a REBIND PLAN is required after application of this PTF. Review the PTF cover letter to determine which, if any, plans 1 could be affected by this change.). ++ HOLD(UK70428) SYS FMID(HDBAA10) REASON(ACTION) DATE(13203) COMMENT (Since the problem that occurred could leave incorrect SYSENTRIES values in SYSIBM.SYSPACKAGE table, if you discover the number in the SYSENTRIES column for a package does not match the number of entries in SYSIBM.SYSPKSYSTEM, you will need to manually correct the SYSENTRIES column. Please contact IBM Service for assistance in correcting those records.). UK96045 HOLD DATA END UK96055 HOLD DATA START UK96055 HOLD DATA END UK96056 HOLD DATA START UK96056 HOLD DATA END UK96072 HOLD DATA START UK96072 HOLD DATA END UK96085 HOLD DATA START UK96085 HOLD DATA END UK96107 HOLD DATA START ++ HOLD(UK96107) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13207) COMMENT (See PM92612 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM92612 corrects a problem that can cause an ABEND04E at DSNIDM.DSNIWKFL:5009 when running a query that contains an OLAP function and select list that involves VARCHAR and TIMESTAMP WITH TIME ZONE 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.). ++ HOLD(UK83553) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13207) COMMENT (See PM72976 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM72976 corrects a problem that can cause an ABEND04E RC00C90101 at DSNIDM.DSNONLLE:5003 when running a query that contains an OLAP function and a group by clause that references a LOB column. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change.). UK96107 HOLD DATA END UK96120 HOLD DATA START UK96120 HOLD DATA END UK96122 HOLD DATA START UK96122 HOLD DATA END UK96141 HOLD DATA START UK96141 HOLD DATA END UK96165 HOLD DATA START UK96165 HOLD DATA END UK96169 HOLD DATA START UK96169 HOLD DATA END UK96177 HOLD DATA START UK96177 HOLD DATA END UK96186 HOLD DATA START ++ HOLD(UK94149) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13211) COMMENT ( See PM83987 APAR/PTF text for additional information about why a REBIND is necessary. PM83987 corrects a problem of non-optimal access path may be selected when an SQL statement satisfies all of the following conditions: 1. EXISTS predicate is used in WHEN clause of CASE expression; 2. multiple tables are referenced in FROM 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.). ++ HOLD(UK96186) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13211) COMMENT (***Action for PM82908: See PM82908 APAR/PTF text for additional information about why a REBIND is necessary. PM82908 corrects a problem of non optimal performance may occur for an SQL statement that references to an SQL table function that contains a range or between predicate that references to an SQL table function parameter. Such predicate may result in a 1 stage 2 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.). ++ HOLD(UK93203) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13211) COMMENT (***Action for PM81762: See PM81762 APAR/PTF text for additional information about why a REBIND is necessary. PM81762 corrects a problem that ABEND04E RC00E72088 at the location DSNXGRDS DSNXSINE OFFSET3196 could happen for an INSERT with SELECT statement that contains ORDER BY and a LOB column 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.). UK96186 HOLD DATA END UK96187 HOLD DATA START UK96187 HOLD DATA END UK96188 HOLD DATA START ++ HOLD(UK96188) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13207) COMMENT (***Action for PM90902: See PM90902 APAR/PTF text for additional information about why a REBIND is necessary. PM90902 corrects a problem of a SQLCODE -180 is issued when a query contains a scalar function in the selection list which is also be referenced in ORDER BY clause running on 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.). ++ HOLD(UK92645) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13207) COMMENT (***Action for PM81200: See PM81200 APAR/PTF text for additional information about why a REBIND is necessary. PM81200 corrects a problem of ABEND04E RC00C90101 at DSNIBNRF:5007 when a query's selection list contains a scalar full-select item participated in arithmetic calculation and runs in parallel. 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.). UK96188 HOLD DATA END UK96195 HOLD DATA START UK96195 HOLD DATA END UK96203 HOLD DATA START UK96203 HOLD DATA END UK96212 HOLD DATA START ++ HOLD(UK91895) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (***Action for PM79005: See PM79005 APAR/PTF text for additional information about why a REBIND is necessary. PM79005 corrects a problem that incorrect output could happen for a MERGE SQL statement with a parameter marker that exists in the USING clause and compares with a constant in a predicate or in a search condition of a CASE expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83082) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (***Action for PM71068: See PM71068 APAR/PTF text for additional information about why a REBIND is necessary. PM71068 corrects a problem of ABEND04E RC00C90101 DSNIBNRF 5003 or ERQUAL5003 that may occur for an SQL statement that satisfies the following conditions: 1. The SQL statement references to a recursive common table expression. 2. The common table expression contains a UNION ALL and outer join. 3. The select list of the one branch of the UNION ALL references to a not null column which came from the preserving side table of the outer join. The select list of the other branch references to a not null value. 4. The values on both select list have different types or length To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change.). ++ HOLD(UK82118) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (***Action for PM69519: See PM69519 APAR/PTF text for additional information about why a REBIND is necessary. PM69519 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS.DSNXORLI:M111 may happen for an SQL statement that ORDER BY any empty string constant and parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK78148) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (***Action for PM59659: See PM59659 APAR/PTF text for additional information about why a REBIND is necessary. PM59659 corrects a problem of ABEND04E RC00C90101 at DSNXIDM .DSNXOTFLA:5009 (in DB2 10) , ABEND04E RC00C900D0 at DSNXGRDS.DSNXROHB+9FF6(in DB2 10) or unexpected SQLCODE -404 (in DB2 9) could occur when a SQL statement references a LOB datatype and a different CCSID non LOB datatype in an UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK96212) SYS FMID(HDBAA10) REASON(ACTION) DATE(13210) COMMENT (PM87039 corrects a problem where SQLCODE904 RC00C900D1 may occur when an SQL variable of LOB type is used in a native SQL procedure or non-inline SQL scalar function and there is CCSID conversion needed to process the SQL statement where the LOB SQL variable is referenced. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected, or ALTER FUNCTION REGENERATE is required for each non-inline SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure or non-inline SQL scalar function could be affected by this change.). ++ HOLD(UK69753) SYS FMID(HDBAA10) REASON(ACTION) DATE(13210) COMMENT (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 1 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.). UK96212 HOLD DATA END UK96217 HOLD DATA START ++ HOLD(UK96217) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM89605 corrects a problem where ABEND0CC RC0C in DSNXOCCX+0F74 or poor query performance could occur for a query with an IS NULL on a column with histogram statistics collected on it and there is only a single quantile. Also, the single quantile represents the NULL frequency. 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.). ++ HOLD(UK95956) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (***Action for PM89036: See PM89036 APAR/PTF text for additional information about why a REBIND is necessary. PM89036 corrects a problem of SQL performance for a user whose queries contain join predicates with histogram statistics on both of the join 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.). ++ HOLD(UK92539) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (***Action for PM80699: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM80699 corrects a problem that incorrect output may be returned for a query with a GROUP BY list which has a SUBSTR or YEAR function as well as the column referenced by the function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK91069) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (***Action for PM78070: 1 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.). ++ HOLD(UK90090) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (***Action for PM75364: See PM75364 APAR/PTF text for additional information about why a REBIND is necessary. PM75364 corrects a problem of inaccurate filter factor estimate of an IS NOT DISTINCT FROM predicate that may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90518) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13212) COMMENT (***Action for PM74991: See PM74991 APAR/PTF text for additional information about why a REBIND is necessary. PM74991 corrects a problem of choosing a poorly performing access path for queries containing predicates on columns where frequency or histogram statistics have been collected. The predicate is a range predicate with parameter marker (or parameter markers) or host variable (or host variables), or the predicate refers to a subquery (except an EQUAL or NOT EQUAL subquery). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK96217 HOLD DATA END UK96219 HOLD DATA START ++ HOLD(UK96219) SYS FMID(HDBAA10) REASON(ACTION) DATE(13210) COMMENT (This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. These instructions supersede any previous PTF instructions. 1 If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers. This PTF updates programs modules DSNADMSB and DSNADMSS plus the DBRM for DSNADMSS (the DBRM for DSNADMSB is not updated). After applying this PTF, proceed as follows to bind a package from the updated DSNADMSS DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2-supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF. Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Update your customized copy of job DSNTEJ6I --------------------------------------------------------------- ==> All DB2 V10 customers who maintain a customized copy of DSNTEJ6I need to take this action after applying the PTF. The change affects the default input for the following parameters: Change COLLECT_COLUMN_STATS to N Change EDIT_DDL to Y 1 These default changes are made to minimize the amount of data that is collected. Column statistics can be abundant, but are not always required for analysis. Edit mode will help create DDL in a format that can be more easily applied to a service environment.). UK96219 HOLD DATA END UK96222 HOLD DATA START UK96222 HOLD DATA END UK96226 HOLD DATA START ++ HOLD(UK93437) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM81848 corrects a problem of possible incorrect output for a query containing ORDER BY, GROUP BY, or set function DISTINCT when hybrid join is chosen with SORTN_JOIN=N, an index matches the ORDER BY, GROUP BY, or set function DISTINCT columns, and no extra sort is added to handle this sorting. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK96226 HOLD DATA END UK96227 HOLD DATA START UK96227 HOLD DATA END UK96234 HOLD DATA START UK96234 HOLD DATA END UK96235 HOLD DATA START UK96235 HOLD DATA END UK96237 HOLD DATA START ++ HOLD(UK95544) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13210) COMMENT (***Action for PM89078: See PM89078 APAR/PTF text for additional information about why a REBIND is necessary. PM89078 corrects incorrect output for an SQL statement with inlist table access and field proc 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.). UK96237 HOLD DATA END UK96265 HOLD DATA START ++ HOLD(UK70649) SYS FMID(HDBAA10) REASON(ACTION) DATE(13211) COMMENT (***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.). UK96265 HOLD DATA END UK96272 HOLD DATA START UK96272 HOLD DATA END UK96302 HOLD DATA START ++ HOLD(UK96302) SYS FMID(HDBAA10) REASON(ACTION) DATE(13214) COMMENT (See PM88321 APAR/PTF text for additional information about why it is necessary to take an image copy of DSNDB01.SYSUTILX. The PTF for APAR PM88321 changes the logging done for SYSIBM.SYSUTILX. Specifically, it disables Change Data Capture for DSNDB01.SYSUTILX and re-enables full logging. Note that for full logging of SYSUTILX to become effective, you must take an image copy of DSNDB01.SYSUTILX. This only needs to be done once, whether you are running in a data sharing group or in a non-data sharing environment.). UK96302 HOLD DATA END UK96310 HOLD DATA START UK96310 HOLD DATA END UK96313 HOLD DATA START UK96313 HOLD DATA END UK96317 HOLD DATA START UK96317 HOLD DATA END 1 UK96319 HOLD DATA START UK96319 HOLD DATA END UK96323 HOLD DATA START ++ HOLD(UK96323) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13213) COMMENT (***Action for PM90157: See PM90157 APAR/PTF text for additional information about why a REBIND is necessary. PM90157 corrects a problem that incorrect output, SQLCODE -404, or other unexpected behavior due to a storage overlay could happen for an SQL statement that satisfies all of the following conditions: 1. It contains a table expression or view with SET operator. 2. The CCSIDs of the tables in the SET operation branches are different. 3. A null padding-side column of an outer join exists in the SELECT list of one of the SET operation branches. 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.). UK96323 HOLD DATA END UK96335 HOLD DATA START ++ HOLD(UK96335) SYS FMID(HDBAA10) REASON(ACTION) DATE(13213) COMMENT (PM85432 does not fix existing data which has been affected by this problem, it does prevent future data from becoming corrupted by this issue. The user must identify the objects which have been affected and bring the data back to a consistent state. Objects that are affected must have the following conditions met: - The table must have an EDITPROC. - The table space or partition must have COMPRESS YES. - REORG with KEEPDICTIONARY must have been run with a dictionary present after PM44787/UK73145/UK73146 had been applied. The following SELECT statement can be used to determine if the first two conditions were met: SELECT TB.CREATOR, TB.NAME, TB.DBNAME, TB.TSNAME, TP.PARTITION FROM SYSIBM.SYSTABLES TB, SYSIBM.SYSTABLEPART TP WHERE TB.EDPROC <> ' ' AND TB.DBNAME = TP.DBNAME AND TB.TSNAME = TP.TSNAME AND TP.COMPRESS = 'Y'; 1 A REPORT RECOVERY can identify the names of the REORG job(s) that were run after the PTF was applied, however it cannot indicate if the KEEPDICTIONARY keyword was used during the REORG at the time. Because EDITPROCs can manipulate the data in many different ways, below are just a few methods for possibly identifying which tables may have corrupted data if it is not possible to determine whether or not the above conditions were all met: - A table space scan (SELECT * FROM XYZ) can be used to check if every record in the table can be EDITPROC decoded and displayed in the output, however even if the display is successful it is possible the actual output of the data is not correct and therefore corrupted. An ABEND can also occur if the data after the EDITPROC decoding cannot be properly formatted. - If an index is present on the data/column that has been EDITPROC encoded then a CHECK INDEX could detect the data corruption with an index/data mismatch if it has not been rebuilt after the data was corrupted. An ABEND can also occur if the data after the EDITPROC decoding cannot be properly formatted.). UK96335 HOLD DATA END UK96350 HOLD DATA START UK96350 HOLD DATA END UK96357 HOLD DATA START ++ HOLD(UK96357) SYS FMID(HDBAA10) REASON(ACTION) DATE(13213) COMMENT (After applying this PTF, you need to re-assemble and linkedit DSNHDECP to pick up the changes in DSNARIB. Under DB2 data sharing, if each member of the group has its own DSNHDECP module then you need to repeat the steps below for each member. These are the steps to update DSNHDECP: (1) Create a separate job containing only the DSNTIZP and DSNTIZQ steps from the job DSNTIJUZ previously edited by the install CLIST. (2) Re-assemble and linkedit the DSNHDECP load module by running your newly created job to produce a new DSNHDECP. (3) Stop and start your DB2. See INFO APAR II14660 for more information.). UK96357 HOLD DATA END UK96368 HOLD DATA START ++ HOLD(UK96368) SYS FMID(HDBAA10) REASON(DOC) DATE(13225) COMMENT ( The DB2 10 Installation Guide is updated to account for increasing the maximum value of DSMAX to 200000. This change 1 is now available in the DB2 10 Installation Guide on the IBM Information Management website: * DSMAX field (DSMAX subsystem parameter) (db2z_ipf_dsmax): Change the maximum value to 200000. * CLIST calculations panel 1: DSNTIPC (db2z_dsntipc): Change the maximum value to 200000 here: 1 DSMAX - MAXIMUM OPEN DATA SETS = 20000 (1-100000)). ++ HOLD(UK96368) SYS FMID(HDBAA10) REASON(ACTION) DATE(13225) COMMENT (***Action for PM88166 (DB2 10) This PTF increases the maximum number of data sets that DB2 is capable of having open at one time from 100000 to 200000. The allowed maximum is specified by DB2 parameter DSMAX in DSN6SPRM, which can now range from 1 to 200000 data sets. The DSMAX default setting remains 20000. Recommendations and considerations: * In order to apply this PTF, you must first apply the PTFs for APARs PM88165 and PM87969. These PTFs provide additional internal DB2 changes needed to support more than 100000 concurrently open data sets. * Use z/OS Version 1 Release 13 or higher for any DB2 subsystem that will have a DSMAX setting greater than 100000. * Complete one of the following actions to improve the performance of opening and closing data sets: - Update the ALLOCxx parmlib member to set the SYSTEM MEMDSENQMGMT value to ENABLE. - Issue system command SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE Updating the ALLOCxx parmlib is strongly recommended because the change remains effective across IPLs. If the SETALLOC command is used to enable SYSTEM MEMDSENQMGMT, a DB2 restart is required to make the change effective. * ATTENTION: A DSMAX setting larger than 100000 will cause a noticeable increase in consumption of below-the-bar (BTB) storage by z/OS. Testing by IBM indicates that when the number of concurrent data sets opened by DB2 reaches the new limit of 200000, z/OS could consume about 700 megabytes of storage BTB, consistent with the expected consumption of about 4 kilobytes per open data set. In addition, the DB2 DBM1 address space can use significant amounts of BTB storage when there are many page set objects in DBET exception state. Testing by IBM indicates that when there are over 100000 objects with exception states, mostly ICOPY (33,756) and AREO* (67,690), DBET consumes about 400 MB below the bar storage. When below the bar storage constraint occurs, the abends RC00E20003, RC00E20013, RC00E20016, or RC00E70005 may occur at the next storage request. If you have already installed or migrated to DB2 10 then after applying this PTF, you need to take the following actions: 1 (1) Update customized copies of DB2 installation CLIST members (2) Copy updated DB2 installation panels to alternate libraries (3) Optionally modify the DSMAX parameter setting Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required for all DB2 10 customers This PTF modifies CLIST members 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 if you maintain copies of the DB2 installation panels outside of SMP/E: This PTF modifies DB2 installation panel DSNTIPC 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 DSNTIPC panel to that library. ---------------------------------------------------------------- (3) Optionally modify the DSMAX parameter setting ---------------------------------------------------------------- ==> This action is required only if you want to change the DSMAX setting used by DB2: After applying this PTF, edit your customized copy of job DSNTIJUZ as follows: * Follow the recommendations noted earlier * Add or update the DSMAX keyword parameter with an integer setting of 1 to 200000 to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If the DSMAX parameter is not specified, it will be set to the default value of 20000 when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. * If you change the DSMAX setting, you should also update the OVDSMAX entry in the DB2 10 CLIST (DSNTIDxx) file for this DB2. Edit the DSNTIDxx file, locate the OVDSMAX entry, and set the last field (indicated by below) to your DSMAX value from DSNTIJUZ: OVDSMAX CHAR M NONE NONE ). UK96368 HOLD DATA END 1 UK96377 HOLD DATA START UK96377 HOLD DATA END UK96399 HOLD DATA START UK96399 HOLD DATA END UK96420 HOLD DATA START UK96420 HOLD DATA END UK96423 HOLD DATA START UK96423 HOLD DATA END UK96439 HOLD DATA START UK96439 HOLD DATA END UK96441 HOLD DATA START UK96441 HOLD DATA END UK96443 HOLD DATA START UK96443 HOLD DATA END UK96451 HOLD DATA START UK96451 HOLD DATA END UK96463 HOLD DATA START UK96463 HOLD DATA END UK96469 HOLD DATA START ++ HOLD(UK96469) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13218) COMMENT (***Action for PM90188: See PM90188 APAR/PTF text for additional information about why a REBIND is necessary. PM90188 corrects a problem of non-optimal access path may be selected when an SQL statement satisfies all of the following conditions: 1. EXISTS predicate is used in WHEN clause of CASE expression; 2. multiple tables are referenced in FROM clause; 3. predicate transitive closure happens. 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.). UK96469 HOLD DATA END UK96475 HOLD DATA START UK96475 HOLD DATA END UK96523 HOLD DATA START UK96523 HOLD DATA END UK96548 HOLD DATA START ++ HOLD(UK96548) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13220) COMMENT (***Action for PM91243: See PM91243 APAR/PTF text for additional information about why a REBIND is necessary. PM91243 corrects a problem of ABEND0C4 RC00000010 at DSNSLD1.DSNSVBK when running a query referencing a partition-by-growth 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.). ++ HOLD(UK90468) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13220) COMMENT (***Action for PM75044: See PM75044 APAR/PTF text for additional information about why a REBIND is necessary. PM75044 corrects the conditions that can lead to the occurrence of an ABEND04E RC00E72018 at DSNXSZK OFFSET 2DBE when executing a query with group by, running with parallelism. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83742) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13220) COMMENT (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 1 letter to determine which, if any, applications could be affected by this change.). UK96548 HOLD DATA END UK96551 HOLD DATA START ++ HOLD(UK94230) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13227) COMMENT (See PM83404 APAR/PTF text for additional information about why a REBIND is necessary. PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC P016 when the GETHINT built-in function is used to retrieve the hint for the password with which the data of a NOT NULL column were encrypted but there was no hint specified during data encryption. 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.). ++ HOLD(UK94230) SYS FMID(HDBAA10) REASON(ACTION) DATE(13227) COMMENT (PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC P016 when the GETHINT built-in function is used to retrieve the hint for the password with which the data of a NOT NULL column were encrypted but there was no hint specified during data encryption. To make this fix effective for any view, column mask, or row permission defined on expressions that contain the GETHINT function, the object must be regenerated using the ALTER VIEW REGENERATE, ALTER MASK REGENERATE, or ALTER PERMISSION REGENERATE statement, respectively, or dropped and recreated after application of this PTF. To make this fix effective for any MQT, SQL scalar UDF, or index defined on expressions that contain the GETHINT function, the object must be dropped and recreated after application of this PTF. After application of the PTF, the nullability of the GETHINT scalar function may be different. Applications using DESCRIBE may be impacted. Proper actions should be taken if such impact is observed. If the DSNTIAUL sample program is used correctly to generate a LOAD utility control statement, then after application of this PTF, the new control statement generated may not match the nullability of the GETHINT scalar functions from the previous control statement. Proper action should be taken if such mismatch is observed. This PTF affects the nullability of the GETHINT built-in scalar function returned by dynamic SQL processing programs, such as SPUFI, DSNTEP2, and DSNTEP4. Proper actions should be taken 1 if such change is observed.). UK96551 HOLD DATA END UK96595 HOLD DATA START ++ HOLD(UK90830) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(13222) COMMENT (***Action for PM74803: PM74803 is an APAR that includes changes to support a functional code change that will be enabled once this APAR is applied. Earlier, a pre-conditioning APAR PM69760 was delivered. In a data sharing group, this pre-conditioning APAR should be applied to all members before applying this enabling APAR to any member. The code change is enabled once this enabling APAR is applied. The following APAR enables the fix for the problem of timeout by SCA REBUILD when a concurrent mainline DBET updater happens to be in the notify exit path.). UK96595 HOLD DATA END UK96619 HOLD DATA START UK96619 HOLD DATA END UK96625 HOLD DATA START UK96625 HOLD DATA END UK96630 HOLD DATA START ++ HOLD(UK96630) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13224) COMMENT (See PM87230 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Starting in DB2 10 New Function Mode (NFM), this APAR changed the encoding scheme for the graphic host variable (GRAPHIC, VARGRAPHIC, or DBCLOB) when the value of the field MIXED DATA on installation panel DSNTIPF is NO and: 1. the statement is a EBCDIC or ASCII encoding scheme statement, or 2. the statement is a multiple encoding scheme statement and the application encoding scheme is EBCDIC or ASCII. In the above statement the graphic host variable is processed in EBCDIC or ASCII, but there is no double byte CCSID assigned for the graphic host variable because of MIXED DATA = NO. This causes SQLCODE -332 to be issued when conversion for the graphic host variable is needed. To avoid SQLCODE -332, starting in DB2 10 NFM, this APAR sets the encoding scheme for the graphic host variable to Unicode encoding scheme when the field MIXED DATA on installation panel DSNTIPF is NO and: 1 1. the statement is a EBCDIC or ASCII encoding scheme statement, or 2. the statement is a multiple encoding scheme statement and the application encoding scheme is EBCDIC or ASCII. Also starting in DB2 10 NFM, if such a Unicode graphic host variable is referenced in the context with a column that follows the comparison rule or the result data type rule, the target CCSID of the comparison or the result data type operation will use the column's CCSID (or the derived value based on a column's CCSID). In the SQL Reference, the new Note 2 has been added to the Table 36. "Operand that supplies the CCSID for character conversion" for the Host Variable operand as below. Note: 2. If a graphic host variable is referenced in the statment, and the value of the field MIXED DATA on installation panel DSNTIPF is NO, the column or the derived value based on a column supplies the target CCSID set. To make this change effective for a static application in V10 NFM, it must be rebound on V10 after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK96630 HOLD DATA END UK96647 HOLD DATA START UK96647 HOLD DATA END UK96651 HOLD DATA START UK96651 HOLD DATA END UK96652 HOLD DATA START UK96652 HOLD DATA END UK96657 HOLD DATA START UK96657 HOLD DATA END UK96662 HOLD DATA START UK96662 HOLD DATA END UK96670 HOLD DATA START UK96670 HOLD DATA END UK96681 HOLD DATA START UK96681 HOLD DATA END 1 UK96687 HOLD DATA START UK96687 HOLD DATA END UK96691 HOLD DATA START UK96691 HOLD DATA END UK96695 HOLD DATA START UK96695 HOLD DATA END UK96725 HOLD DATA START UK96725 HOLD DATA END UK96734 HOLD DATA START ++ HOLD(UK96734) SYS FMID(HIZAA10) REASON(ACTION) DATE(13227) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY IBM recommends that you install DB2 APAR PM59756 PTFs UK77559, UK77560 or UK77561 on all DB2 for z/OS DB2 subsystems to fix HIPER APAR PM59756 before installing this RRSAF ERLY code PTF or other DB2 PTFs for RRSAF. PM59756 fixes a base DB2 V10 problem.). ++ HOLD(UK91836) SYS FMID(HIZAA10) REASON(ACTION) DATE(13227) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY IBM recommends that you install DB2 PTF UK77559 to fix HIPER APAR PM59756 before installing this PTF or other DB2 PTFs for RRSAF. PM59756 fixes a base DB2 V10 problem.). ++ HOLD(UK78783) SYS FMID(HIZAA10) REASON(ACTION) DATE(13227) COMMENT (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.). ++ HOLD(UK77171) SYS FMID(HIZAA10) REASON(ACTION) DATE(13227) COMMENT (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. 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.). ++ HOLD(UK75933) SYS FMID(HIZAA10) REASON(ACTION) DATE(13227) COMMENT (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.). UK96734 HOLD DATA END UK96744 HOLD DATA START ++ HOLD(UK96744) SYS FMID(HDBAA10) REASON(ACTION) DATE(13227) COMMENT (<++HOLD text for pm87044> BEFORE APPLYING THIS PTF, SETTING THE CURRENT OPTIMIZATION HINT SPECIAL REGISTER FROM A JCC APPLICATION USING THE PROPERTIES API WITH AN INVALID STRING LENGTH > 128 BYTES RETURNED SQLCODE 0. AFTER APPLYING THIS PTF, DB2 WILL NOW CORRECTLY INDICATE THIS 1 IS AN INVALID STRING BECAUSE IT IS LONGER THAN THE ALLOWED LENGTH. DB2 WILL NOW ISSUE SQLCODE -725 FOR THIS SITUATION.). UK96744 HOLD DATA END UK96752 HOLD DATA START ++ HOLD(UK96752) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13228) COMMENT (***Action for PM92790: See PM92790 APAR/PTF text for additional information about why a REBIND is necessary. PM92790 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS DSNXGSFN M628 could happen or SQLCODE -180 could be incorrectly issued for an SQL statement that satisfies all of the following conditions: 1. It contains a table expression or view with SET operator. 2. The CCSIDs of the tables in the SET operation branches are different. 3. A Date or Timestamp item is in the SELECT list of one of the SET operation branches. 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.). UK96752 HOLD DATA END UK96787 HOLD DATA START UK96787 HOLD DATA END UK96800 HOLD DATA START ++ HOLD(UK96800) SYS FMID(HDBAA10) REASON(ACTION) DATE(13232) COMMENT (The PTF for APAR PM92742 has modified the SYSTABLES.AVGROWLEN statistic collected by the RUNSTATS utility. The AVGROWLEN will no longer include the length of the ID map entry and therefore may no longer be equal to the RECLENGTH statistic in the same catalog table, SYSTABLES. This change will make the AVGROWLEN consistent with the AVGROWLEN catalog statistics in SYSTABLESPACE and SYSTABLEPART gathered by RUNSTATS. A similar problem can occur on SYSTABLES.AVGROWLEN value gathered inline by the LOAD and REORG utilities.). UK96800 HOLD DATA END UK96807 HOLD DATA START UK96807 HOLD DATA END UK96810 HOLD DATA START ++ HOLD(UK96810) SYS FMID(HIZAA10) REASON(ACTION) DATE(13228) 1 COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). ++ HOLD(UK93654) SYS FMID(HIZAA10) REASON(ACTION) DATE(13228) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). UK96810 HOLD DATA END UK96816 HOLD DATA START UK96816 HOLD DATA END UK96817 HOLD DATA START UK96817 HOLD DATA END UK96824 HOLD DATA START ++ HOLD(UK96824) SYS FMID(HDBAA10) REASON(DOC) DATE(13232) COMMENT (***Documentation for PM90182: See PM90182 APAR/PTF text for additional information. The following text describes the function that is provided by this APAR. This information will be available in the Information Management Software for z/OS Solutions Information Center at a later date. When receiving RACF PassTickets over TCP/IP communications from a DB2 for z/OS requester, the following RACF actions must be taken for global authentication cache not to be used for 1 PassTickets when "NO REPLAY PROTECTION" is not specified in the PassTicket profile. - A RACF PTKTDATA resource profile must be created at the server system or sysplex using the following naming rules: RDEFINE PTKTDATA IRRPTAUTH.applname.userid or RDEFINE PTKTDATA IRRPTAUTH.applname.* Where applname is either the generic LU name or IPNAME assigned to each member of a serving data sharing group or is the LUNAME or IPNAME assigned to the serving non-data sharing subsystem. Where userid is either an asterisk ("*") or a RACF userid that one wants to allow into the serving subsystem or member of a data sharing group. - Once the RACF profile has been defined, the PTKTDATA resource must be refreshed as follows: SETROPTS RACLIST(PTKTDATA) REFRESH - Once the PTKTDATA resource profiles have been refreshed and loaded, the userid assigned in the STDATA of the STARTED profile of the ssidDIST address space must be permitted to read this new profile as follows: PERMIT IRRPTAUTH.applanme.userid CLASS(PTKTDATA) - ID(dist_userid) ACCESS(READ) or PERMIT IRRPTAUTH.applname.* CLASS(PTKTDATA) - ID(dist_userid) ACCESS(READ) Where userid and dist_userid are not the same. The above actions do not need to be taken if one wants to take advantage of global authentication cache for PassTickets.). UK96824 HOLD DATA END UK96839 HOLD DATA START ++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(13231) COMMENT (***Action for PM58951 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58951 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry 1 with (wsdbu01043533) identifier.). UK96839 HOLD DATA END UK96845 HOLD DATA START UK96845 HOLD DATA END UK96847 HOLD DATA START ++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(13231) COMMENT (***Action for PM58952 ____________________________________________________________ This PTF contains a fix for a defect in the SQLJ translator. Incorrect code was generated for an SQL SELECT INTO statement using a common table expression specified with the "WITH" keyword. To make this fix effective for any impacted SQLJ program, after applying the APAR, you must re-translate the SQLJ program, then you must run the SQLJ Binder (db2sqljbind) again on the affected profiles and rebind the profiles. See PM58952 APAR/PTF text in the PTF cover letter for further information about this problem. Reference entry with (wsdbu01043533) identifier.). UK96847 HOLD DATA END UK96850 HOLD DATA START UK96850 HOLD DATA END UK96852 HOLD DATA START UK96852 HOLD DATA END UK96857 HOLD DATA START UK96857 HOLD DATA END UK96871 HOLD DATA START ++ HOLD(UK96871) SYS FMID(HDBAA10) REASON(ACTION) DATE(13232) COMMENT (The PTF of APAR PM87844 has extended the PREFORMAT function of the LOAD SHRLEVEL NONE and REORG AUX YES utility to support preformatting of LOB table spaces and auxiliary index being processed. The auxiliary pagesets would be preformatted up to its HARP value automatically when PREFORMAT is specified, and no other user action is required. APAR PM87844 introduces the following changes to externals: Utility Guide and Reference is updated as follows: Under the REORG TABLESPACE keyword section: 1 PREFORMAT Specifies that the remaining pages are to be preformatted up | to the high-allocated RBA in the table space and index spaces | that are associated with the table space or partitions that are being reorganized. The preformatting occurs after the data is loaded and the indexes are built. PREFORMAT can operate on an entire table space and its index spaces, or on a partition of a partitioned table space and | its corresponding partitioning index space. When AUX YES | is specified or accepted as the default, the LOB table spaces | and auxiliary indexes that are associated with the base | partitions that are being reorganized are also preformatted at | the end of RELOAD phase. ... Under the LOAD keyword section: PREFORMAT Specifies that the remaining pages are preformatted up to the high-allocated RBA in the table space and index space that are associated with the table that is specified in table.name. The preformatting occurs after the data has been loaded and the indexes are built. PREFORMAT can operate on an entire table space and its index spaces, or on a partition of a partitioned table space and on the corresponding partitions of partitioned indexes, if any exist. Specifying LOAD PREFORMAT (rather than PART integer PREFORMAT) tells LOAD to serialize at the table space level, which can inhibit concurrent processing of separate partitions. If you want to serialize at the partition level, specify PART integer PREFORMAT. See "Option descriptions for INTO TABLE" for information about specifying PREFORMAT at the partition level. | The PREFORMAT keyword also applies to LOB table spaces and | auxiliary indexes that are associated with the base table or | partitions that LOAD serialized. XML objects are not | preformatted.). UK96871 HOLD DATA END UK96875 HOLD DATA START UK96875 HOLD DATA END UK96879 HOLD DATA START UK96879 HOLD DATA END UK96886 HOLD DATA START ++ HOLD(UK96886) SYS FMID(HDBAA10) REASON(ACTION) DATE(13234) 1 COMMENT (DFSMS APAR OA41617 is required and must be installed in order to alleviate the problem reported for PM87248.). UK96886 HOLD DATA END UK96896 HOLD DATA START ++ HOLD(UK96896) SYS FMID(JDBAA17) REASON(ACTION) DATE(13232) COMMENT (*** Action for PM94538 (Version 10) This APAR PM94538, together with DB2 APAR PM94536, provides a mechanism to prevent load module DSNARRS from being prematurely deleted when MULTICONTEXT=2. To fully implement this APAR fix, it must be installed together with PM94536. If PM94536 is not installed, then the fix delivered by this APAR will not be enabled. Specification of MULTICONTEXT=2 enables a multithreaded ODBC application to always maintain an active environment handle under a designated LE thread in a multiple-context environment. MULTICONTEXT=2 is to be used only under the direction of IBM Software Support. Complete documentation for MULTICONTEXT=2 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 at a later date.). UK96896 HOLD DATA END UK96919 HOLD DATA START UK96919 HOLD DATA END UK96925 HOLD DATA START UK96925 HOLD DATA END UK96933 HOLD DATA START UK96933 HOLD DATA END UK96935 HOLD DATA START UK96935 HOLD DATA END UK96950 HOLD DATA START ++ HOLD(UK96950) SYS FMID(HDBAA10) REASON(ACTION) DATE(13234) COMMENT (The query provided in the ++HOLD of PM78210/UK90728 has been updated to exclude views. PM78210 fixes CREATE TABLE to define implicit table spaces in reordered row format(RRF) when all of the following conditions are true: 1 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 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). The sample query may not take into account all customer environments and scenarios. The query output should be analyzed to verify the table spaces returned are in BRF and contain tables with inline LOB columns If so, the table spaces must be dropped and recreated after PM78210 has been 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 = ' ' AND TAB.TYPE <> 'V' );). ++ HOLD(UK90728) SYS FMID(HDBAA10) REASON(ACTION) DATE(13234) COMMENT (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 1 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 = ' ' );). UK96950 HOLD DATA END UK96951 HOLD DATA START UK96951 HOLD DATA END UK96954 HOLD DATA START UK96954 HOLD DATA END UK96958 HOLD DATA START UK96958 HOLD DATA END UK96959 HOLD DATA START UK96959 HOLD DATA END UK96982 HOLD DATA START UK96982 HOLD DATA END UK96987 HOLD DATA START ++ HOLD(UK96987) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13239) COMMENT (***Action for PM93043: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM93043 corrects a problem in which an inefficient access path may be selected for a query specifying OPTIMIZE FOR 1 ROW or FETCH FIRST 1 ROW and an ORDER BY if an index is available to support the ORDER BY in reverse order. 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.). ++ HOLD(UK96956) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13239) COMMENT (***Action for PM90987: See PM90987 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM90987 corrects a problem of a bad access path for a partitioned table when the table is limited to only 1 partition for page range access, and there is at least one DPSI on the 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.). ++ HOLD(UK92981) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13239) COMMENT (***Action for PM83144: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83144 corrects a problem in which DB2 could incorrectly discard an multi-index access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92968) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13239) COMMENT (***Action for PM81295: See PM81295 APAR/PTF text for additional information about why a REBIND is necessary. PM81295 corrects a problem of poor query performance for a query containing OR predicates that map to a single index. The poor performance can occur when a range-list index access plan may not be assigned the lowest cost of any plan it beats. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK96987 HOLD DATA END UK96992 HOLD DATA START ++ HOLD(UK94249) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13235) COMMENT (**Action for PM83911: See PM83911 APAR/PTF text for additional information about why a REBIND is necessary. PM83911 corrects a problem that incorrect output or ABEND04E RC00E72018 at the location DSNXGRDS DSNXSBUC OFFSET08EE for V9 (OFFSET3EA4 for V10) could happen for an SQL statement that contains an aggregation function in the ORDER BY clause and the aggregation function has an argument referencing a SELECT list item that is not a simple column nor a literal constant. 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.). UK96992 HOLD DATA END UK97000 HOLD DATA START UK97000 HOLD DATA END UK97002 HOLD DATA START UK97002 HOLD DATA END UK97009 HOLD DATA START ++ HOLD(UK97009) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13240) COMMENT (***Action for PM92837: See PM92837 APAR/PTF text for additional information about why a REBIND is necessary. PM92837 corrects a problem of ABEND04E at DSNXGRDS.DSNXGINB:M103 when a query contains join predicates with VARBINARY data type. 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.). UK97009 HOLD DATA END UK97013 HOLD DATA START ++ HOLD(UK97013) SYS FMID(HDBAA10) REASON(DOC) DATE(13238) COMMENT (PM90568 adds DBID/PSID or DBIB/OBID selection filtering to IFI 306 log read via the DSNWLI READS call. A pointer is added to the WQAL interface control block and when non-zero points to a new WQLS control block for specification of the list of table space DBID and PSID or the table diagnostic log record DBID and OBID. The details are shown in the DSNDWQAL macro.). UK97013 HOLD DATA END UK97014 HOLD DATA START UK97014 HOLD DATA END UK97017 HOLD DATA START UK97017 HOLD DATA END 1 UK97020 HOLD DATA START UK97020 HOLD DATA END UK97022 HOLD DATA START UK97022 HOLD DATA END UK97025 HOLD DATA START UK97025 HOLD DATA END UK97033 HOLD DATA START UK97033 HOLD DATA END UK97085 HOLD DATA START UK97085 HOLD DATA END UK97087 HOLD DATA START UK97087 HOLD DATA END UK97099 HOLD DATA START UK97099 HOLD DATA END UK97104 HOLD DATA START ++ HOLD(UK70914) SYS FMID(HDBAA10) REASON(ACTION) DATE(13240) COMMENT (***Action for PM41805: See PM41805 APAR/PTF text for additional information about why further ACTION might be necessary. PM41805 corrects a problem that can occur when DATETIME arithmetic returns a NULL value. However, DB2 does not zero out the data part of the result and can leave it containing "bad" data. Eventually, this can cause an incorrect result to be returned. For the recreate example described in the apar PM41805 text, if the incorrect data already exists in the database, the following simple example (steps) might be helpful in correcting it. 1. Drop the index which has the LAST_DATE column as one of the index keys. DROP INDEX I1; COMMIT; 2. Apply the PTF for apar PM41805 and recycle DB2. 3. Rerun the UPDATE statement which causes the incorrect result. 1 UPDATE T1 SET LAST_DATE = LAST_DATE - ((DAYS('07/20/2010') - DAYS('05/28/2009'))DAYS); 4. Recreate the dropped index. CREATE INDEX I1 ON T1 (IDN ASC, LAST_DATE ASC); COMMIT; 5. Execute the SELECT statement (again) which uses index access and references the LAST_DATE column as a stage 1 predicate. SELECT * FROM T1 WHERE IDN = 2 AND LAST_DATE IS NULL; After the application of apar PM41805 and re-running the UPDATE statement in Step 3., a correct NULL value will correct/replace the "bad" null value in the table. Once the same index is recreated, and the LAST_DATE column is referenced as a stage 1 predicate in the SELECT query, a correct result will be returned.). UK97104 HOLD DATA END UK97105 HOLD DATA START UK97105 HOLD DATA END UK97113 HOLD DATA START UK97113 HOLD DATA END UK97115 HOLD DATA START UK97115 HOLD DATA END UK97120 HOLD DATA START ++ HOLD(UK97120) SYS FMID(HDBAA10) REASON(ACTION) DATE(13240) COMMENT (***Action for PM80405 (V10) This PTF modifies the source code for DSNTSMFD (DB2 sample application for decompressing compressed DB2 SMF records). Applying the PTF updates only the DSNTSMFD source code. The updates do not affect your current DSNTSMFD load module until you rebuild it as follows: (1) If you use DSNTSMFD as supplied by DB2, run job steps ASM and LKED of your customized copy of job DSNTEJDS to assemble and link-edit the load module for DSNTSMFD. (2) If you use a modified version of DSNTSMFD, redo your modifications and then run JOB steps ASM and LKED from your customized copy of job DSNTEJDS to assemble 1 and link-edit the load module for DSNTSMFD.). UK97120 HOLD DATA END UK97140 HOLD DATA START UK97140 HOLD DATA END UK97146 HOLD DATA START ++ HOLD(UK97146) SYS FMID(HDBAA10) REASON(DOC) DATE(13241) COMMENT (PM73388 introduces the following changes to externals: DB2 10 for z/OS SQL Reference: ALTER TABLESPACE, Notes Section: Invalidation of packages: All of the packages that refer to that table space are invalidated when any of the following conditions are true: ... - When increasing the MAXPARTITIONS attribute of a . DB2 10 for z/OS Application programming and SQL: New row added to Table 1. Changes that require packages to be rebound. Change made: ALTER TABLESPACE with MAXPARTITIONS to increase the maximum number of partitions Required Action: No action is required. DB2 automatically rebinds invalidated plans or packages. This is not the final version of changes. Information about these changes 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.). UK97146 HOLD DATA END UK97149 HOLD DATA START UK97149 HOLD DATA END UK97156 HOLD DATA START UK97156 HOLD DATA END UK97158 HOLD DATA START UK97158 HOLD DATA END UK97160 HOLD DATA START UK97160 HOLD DATA END 1 UK97162 HOLD DATA START ++ HOLD(UK97162) SYS FMID(HDBAA10) REASON(ACTION) DATE(13241) COMMENT (The PTF for APAR PM83839 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.). UK97162 HOLD DATA END UK97180 HOLD DATA START UK97180 HOLD DATA END UK97181 HOLD DATA START ++ HOLD(UK95459) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM88354 corrects a problem where a query meeting all of the following conditions could return incorrect output: 1. Has top-level UNION ALL; 2. Each leg of the UNION ALL selects from the same single table; 3. Each leg has the same columns in the SELECT list; 4. There is no ORDER BY, GROUP BY, set function, or DISTINCT in any leg; 5. Parallelism is not used; AND 6. An index-on-expression is chosen for access to a table in one or more legs of the 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.). ++ HOLD(UK94426) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (See PM85237 APAR/PTF text for additional information about why a REBIND is necessary. PM85237 corrects an incorrect output problem that may occur when (1) sparse index access is used on a table, and (2) not all the eligible join predicates are used for the sparse index key. 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.). ++ HOLD(UK94510) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (***Action for PM84970: See PM84970 APAR/PTF text for additional information about why a REBIND is necessary. PM84970 corrects a problem of ABND04E RC00C90101 at DSNIWNRF ERQUAL 502C when a query contains a CREATE GLOBAL TEMPORARY TABLE in a correlated sub-select and the parent query block of the correlated sub-select runs in parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK95022) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (***Action for PM84151: See PM84151 APAR/PTF text for additional information about why a REBIND is necessary. PM84151 corrects a problem of an ABEND when an index on expression (IOE) is used against a range predicate in which the left-hand-side and right-hand-side have different string lengths and CCSIDs. 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.). ++ HOLD(UK91647) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. APAR PM75619 corrects two problems. The first problem occurs on both V9 and V10. A query may produce incorrect output when a UNICODE table joins to an EBCDIC view which is a UNION ALL, and at the same time, when index-on-expression (IOE) is used for that query. The second problem occurs on V10 only. DB2 may not issue a REORG suggestion as it should. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92086) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13242) COMMENT (A rebind is necessary for static applications to rebuild 1 access paths based on changes in this APAR. PM63095 corrects a problem of ABEND04E RC00C90101 in DSNIPSFI :5007 when executing an SQL statement containing a User Defined Function (UDF) with the DISALLOW PARALLEL parameter while parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK97181 HOLD DATA END UK97183 HOLD DATA START ++ HOLD(UK97183) SYS FMID(HDBAA10) REASON(ACTION) DATE(13242) COMMENT (This PTF adds a DB2 parameter, XML_RESTRICT_EMPTY_TAG, that can be specify whether DB2 will serialize an XML empty element using an empty element tag. XML provides two forms for denoting an empty element: - a short form of "" which is referred to as the empty element tag - a long form of "" which is a start-element tag followed by an end-element tag. Across DB2 versions and depending on the context in which the empty XML element appears, DB2 sometimes generates "" and sometimes generates "". The XML_RESTRICT_EMPTY_TAG subsystem parameter determines whether DB2 will force the long form of the XML empty element. Valid settings are: * NO : Specifies that DB2 may serialize an empty XML element as an empty-element tag or as a start-element followed by an end-element. ===> This is the default setting. * YES: Specifies that DB2 will not serialize an XML empty element using an empty-element tag. DB2 will serialize an XML empty element using a start-element tag followed by an end-element tag (i.e. ). If you have already installed or migrated to DB2 10, 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 the package for DSNTXAZP Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all customers 1 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 XML_RESTRICT_EMPTY_TAG=, where is NO or YES, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding XML_RESTRICT_EMPTY_TAG 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 ==> This action is required for all customers This PTF adds an entry for XML_RESTRICT_EMPTY_TAG 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. In each such copy, add the following line: XML_RESTRICT_EMPTY_TAG CHAR M NO YES Change to the value you specified for XML_RESTRICT_EMPTY_TAG in step (2), above. ---------------------------------------------------------------- (4) Update the package for DSNTXAZP ==> This action is required for all customers who use DSNTXAZP to update DB2 CLIST input (DSNTIDXX) members: Submit a job that contains the following BIND statement: BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) - ACTION(ADD) ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where is the high-level qualifier for the DB2 subsystem target libraries.). 1UK97183 HOLD DATA END UK97198 HOLD DATA START UK97198 HOLD DATA END UK97204 HOLD DATA START UK97204 HOLD DATA END UK97227 HOLD DATA START ++ HOLD(UK97227) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13245) COMMENT (***Action for PM91172: A rebind is necessary for static applications to rebuild the access paths based on the changes in this APAR. PM91172 corrects a problem that ABEND0C4 RC04 at DSNXRFN +268A may occur when executing a query which uses an OMNIFIND function and for which a hybrid join plan is chosen. 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.). ++ HOLD(UK93125) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13245) COMMENT (***Action for PM81000: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM81000 corrects a problem of inaccurately estimated I/O and CPU of a parent query block table in hybrid join when parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK97227 HOLD DATA END UK97229 HOLD DATA START UK97229 HOLD DATA END UK97231 HOLD DATA START UK97231 HOLD DATA END UK97236 HOLD DATA START UK97236 HOLD DATA END 1 UK97238 HOLD DATA START UK97238 HOLD DATA END UK97243 HOLD DATA START UK97243 HOLD DATA END UK97245 HOLD DATA START UK97245 HOLD DATA END UK97263 HOLD DATA START ++ HOLD(UK97263) SYS FMID(HDBAA10) REASON(ACTION) DATE(13246) COMMENT (The PTF for APAR PM90310 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.). UK97263 HOLD DATA END UK97269 HOLD DATA START UK97269 HOLD DATA END UK97275 HOLD DATA START UK97275 HOLD DATA END UK97283 HOLD DATA START UK97283 HOLD DATA END UK97294 HOLD DATA START UK97294 HOLD DATA END UK97296 HOLD DATA START UK97296 HOLD DATA END UK97305 HOLD DATA START UK97305 HOLD DATA END 1UK97309 HOLD DATA START UK97309 HOLD DATA END UK97332 HOLD DATA START UK97332 HOLD DATA END UK97360 HOLD DATA START ++ HOLD(UK97360) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13256) COMMENT (***Action for PM92272: See PM92272 APAR/PTF text for additional information about why a REBIND is necessary. PM92272 corrects a problem that performance regression could happen for a static SQL statement that has a non-boolean term BETWEEN predicate with a Timestamp column and host variables. 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.). UK97360 HOLD DATA END UK97362 HOLD DATA START UK97362 HOLD DATA END UK97369 HOLD DATA START UK97369 HOLD DATA END UK97375 HOLD DATA START UK97375 HOLD DATA END UK97384 HOLD DATA START UK97384 HOLD DATA END UK97386 HOLD DATA START UK97386 HOLD DATA END UK97390 HOLD DATA START ++ HOLD(UK80840) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13252) COMMENT (***Action for PM67966: See PM67966 APAR/PTF text for additional information about why a REBIND is necessary. PM67966 corrects a problem that can result in an incorrect 1 result set, more rows than expected, being returned for a query that contains a correlated subquery for an EXISTS predicate, and there is a unique index on expression defined on the table that is referenced in the correlated 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.). UK97390 HOLD DATA END UK97396 HOLD DATA START UK97396 HOLD DATA END UK97423 HOLD DATA START UK97423 HOLD DATA END UK97427 HOLD DATA START UK97427 HOLD DATA END UK97465 HOLD DATA START ++ HOLD(UK97465) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13254) COMMENT (***Action for PM95277 See PM95277 APAR/PTF text for additional information about why a REBIND is necessary. PM95277 corrects an incorrect output problem that can occur for an SQL statement that references an SQL table function. The incorrect output can occur for the following cases: 1. The SQL statement references an SQL table function and a view. 2. The SQL statement references a multi-level nested SQL table function and the argument of the SQL table function contains a column expression. 3. The SQL statement references an SQL table function in the subquery predicate and the SQL table function is materialized. 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.). ++ HOLD(UK96508) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13254) COMMENT (***Action for PM89329 See PM89329APAR/PTF text for additional information about why a REBIND is necessary. 1 PM89329 corrects a problem of incorrect out put may occur for an SQL statement that references an SQL table function. Incorrect out put may occur for the following cases: 1. The SQL statement references an SQL table function and a view . 2. The SQL statement references a multi-level nested SQL table function and the argument of the SQL table function contains a column expression. 3. The SQL statement references an SQL table function in the subquery predicate and the SQL table function is materialized. 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.). UK97465 HOLD DATA END UK97468 HOLD DATA START UK97468 HOLD DATA END UK97483 HOLD DATA START UK97483 HOLD DATA END UK97488 HOLD DATA START UK97488 HOLD DATA END UK97517 HOLD DATA START UK97517 HOLD DATA END UK97524 HOLD DATA START UK97524 HOLD DATA END UK97538 HOLD DATA START UK97538 HOLD DATA END UK97542 HOLD DATA START ++ HOLD(UK97542) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13256) COMMENT (***Action for PM92588: See PM92588 APAR/PTF text for additional information about why a REBIND is necessary. PM92588 corrects a problem of ABEND0C7 at DSNXRINT OFFSET 3EF2 for an SQL statement that satisfies all of the following conditions: 1. The statement contains an DB2 generated equal, IN or BETWEEN transitive closure predicate. 2. The generated transitive closure predicate references a 1 column and a host variable. 3. The column was a not null decimal and a NULL value was sent in during execution time for the host variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK93059) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13256) COMMENT (***Action for PM83563: See PM83563 APAR/PTF text for additional information about why a REBIND is necessary. PM83563 corrects a problem that matching index access is incorrectly used for an SQL statement that contains a predicate with a 'Non-column expression CONCAT empty string' when the column comparing to this expression is Timestamp data type. 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.). ++ HOLD(UK91605) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13256) COMMENT (***Action for PM79953: See PM79953 APAR/PTF text for additional information about why a REBIND is necessary. PM79953 corrects a problem of an inefficient access path being chosen by DB2 for a SQL statement which satisfies the following conditions: 1.it contains a VALUE COMPARE predicate or a BETWEEN predicate with an arithmetic expression, 2.the arithmetic expression has a host variable or parameter marker and integer constant as its operators, 3.matching index access is possible for the query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90447) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13256) COMMENT (***Action for PM76452: See PM76452 APAR/PTF text for additional information about why a REBIND is necessary. PM76452 corrects a problem of ABEND0C7 RC0 at DSNXRDEC +59BC when a transitive closure predicate takes the form of column = host variable where the column is a not null decimal and a NULL value was sent in during execution time for the host variable. 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.). UK97542 HOLD DATA END UK97556 HOLD DATA START UK97556 HOLD DATA END UK97573 HOLD DATA START UK97573 HOLD DATA END UK97593 HOLD DATA START UK97593 HOLD DATA END UK97603 HOLD DATA START ++ HOLD(UK97603) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(13259) COMMENT (***Action for PM91547: PM91547 is an APAR that includes changes to support a functional code change that will be enabled once this APAR is applied. Earlier, a pre-conditioning APAR PM69760 was delivered. In a data sharing group, this pre-conditioning APAR should be applied to all members before applying this enabling APAR to any member. The code change is enabled once this enabling APAR is applied. The following APAR enables the fix for the problem of timeout by SCA REBUILD when a concurrent mainline DBET updater happens to be in the notify exit path.). UK97603 HOLD DATA END UK97630 HOLD DATA START UK97630 HOLD DATA END UK97669 HOLD DATA START UK97669 HOLD DATA END UK97673 HOLD DATA START UK97673 HOLD DATA END UK97675 HOLD DATA START ++ HOLD(UK96015) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13261) COMMENT (***Action for PM90116: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. 1 PM90116 corrects a problem in which an inefficient access path may be selected when statistics in SYSCOLDIST and SYSINDEXES are in conflict. 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.). ++ HOLD(UK96020) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13261) COMMENT (See PM88835 APAR/PTF text for additional information about why a REBIND is necessary. PM88835 corrects a problem that the index probing feature may incorrectly set the frequency of the histogram quantiles where the histogram statistics are generated for IN-list predicates and there is more than 1 quantile generated. 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.). UK97675 HOLD DATA END UK97692 HOLD DATA START UK97692 HOLD DATA END UK97707 HOLD DATA START ++ HOLD(UK97707) SYS FMID(HDBAA10) REASON(DOC) DATE(13267) COMMENT (++HOLD DOC changes for APAR PM91639 The Messages manual has been modified to add reason code 34 for message DSNU334I to indicate an invalid FORMAT INTERNAL record header length. Example message text for DSNU334I with reason code 34: INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL' INVALID FOR 'SYSADM.TBB' ERROR CODE '34' DSNU334I csect-name INPUT FIELD field-name INVALID FOR table-name, ERROR CODE error-code Explanation: The LOAD utility found incorrect input data. csect-name: The name of the control section that issued the message. field-name: The name of the field for which incorrect data was provided. table-name: The name of the table. 1 error-code: Description of the problem. Possible error codes are: 01 Input numeric value is out of the range for the table column. 02 Input numeric field contains invalid numeric data. 03 An error occurred when converting input numeric data to floating-point data. 04 Input packed decimal data is in error. 05 Input is too long for a date column. 06 Input is too short for a date column. 07 Input is too long for a time column. 08 Input is too short for a time column. 09 Input is too long for a timestamp column. 10 Input is too short for a timestamp column. 11 Input character field is too long for the table column. 12 Input variable character field is too long for the table column. 13 Input is out of range for the date/time column. 14 Input is invalid for the date/time column. 15 Input length is incorrect for numeric column. 16 Input contains a blank character. 17 Input is too long for a graphic column. 18 Input is invalid for a graphic column. 19 Input is too long for the table column after a required CCSID conversion. 20 Input contained an invalid code point for a required CCSID conversion. 21 Input does not conform to the rules for valid data for a required CCSID conversion. 22 Input causes an error during CCSID conversion. An example of this type of error would be an error in a user exit routine. 23 Input is invalid for a ROWID column. 24 Input contained a code point that when translated from the source resulted in a substitution character being placed in the target string. This condition can occur when the NOSUBS keyword was specified and no discard data set was specified. 25 The range of values for an identity column is exhausted. 26 A null value has been supplied for a not null column. 27 Input is invalid for a security label column. 28 Input is a valid security label, but the SECLABEL and the user's does not have the authority to load this SECLABEL. 29 Decimal floating point conversion error. 31 XML is not well formed. >>34 The FORMAT INTERNAL record header length is invalid. << System action: Further utility processing is terminated. User response: Correct the input data and resubmit the job. Make sure that the field specification on the LOAD statement is consistent with the table definition and the input data. Correcting this error might mean changing: v The table definition v The LOAD statement v The input data 1 Severity: 8 (error) Related reference:). ++ HOLD(UK97707) SYS FMID(HDBAA10) REASON(ACTION) DATE(13267) COMMENT (++HOLD ACT for PM91639: This APAR adds a new validity check to check to see if the data is in FORMAT INTERNAL prior to load by checking the actual record length against the length described in the internal format record header and issuing message DSNU334I with reason code 34 and ABEND04E RC00E40323 if the values do not match. No other data validity checks are being done as part of this APAR. Example message text for DSNU334I with reason code 34: INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL' INVALID FOR 'SYSADM.TBB' ERROR CODE '34' Please note that certain editors such as ISPF may strip trailing blanks with variable blocked (VB) records if the EDITSET 'Preserve length' option is not set. Any editor like ISPF that may not honor the existing record length generated by the UNLOAD FORMAT INTERNAL may now cause LOAD FORMAT INTERNAL to fail this new record length validity check. Users of FORMAT INTERNAL are recommended to not modify the internal format records and if editing is necessary it is required that the editor used will preserve the VB record length as it is unloaded by the UNLOAD FORMAT INTERNAL utility. Existing records unloaded with FORMAT INTERNAL that have been edited with an editor that does not honor the VB record length will need to be unloaded again with UNLOAD FORMAT INTERNAL to generate a new SYSREC data set prior to running LOAD FORMAT INTERNAL.). UK97707 HOLD DATA END UK97760 HOLD DATA START UK97760 HOLD DATA END UK97770 HOLD DATA START UK97770 HOLD DATA END UK97828 HOLD DATA START UK97828 HOLD DATA END UK97861 HOLD DATA START UK97861 HOLD DATA END UK97873 HOLD DATA START 1UK97873 HOLD DATA END UK97902 HOLD DATA START UK97902 HOLD DATA END UK97939 HOLD DATA START ++ HOLD(UK97939) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13269) COMMENT (PM94158 corrects a problem of incorrect output returned when query contains LIKE predicate with RTRIM/STRIP FUNCTION and literal pattern with blank pattern and index created on column in RTRIM/STRIP.). UK97939 HOLD DATA END UK97981 HOLD DATA START UK97981 HOLD DATA END UK98030 HOLD DATA START ++ HOLD(UK98030) SYS FMID(HDBAA10) REASON(DOC) DATE(13270) COMMENT (This is the enabling apar for PM90970. PM90970 must be applied to all members of a data sharing group before applying PM94353. The -START DATABASE command is enhanced to allow a new ACCESS keyword of RREPL to permit read only access to the data except by applications designated as a replication product. RRS attach is enhanced with a new function of 'SET_REPLICATION' to identify to DB2 that the application is a replication product. This function is restricted to only supervisor state and APF authorized programs - that is, an application link edited as AC(1) and residing in an APF authorized library or that is running supervisor state as indicated by the PSW. An attempt to invoke the 'SET_REPLICATION' function will result in a abend with reason code 00C12035 if not properly authorized. Applications not designated as a replication product which attempt to perform an insert, update, or delete will receive a resource unavailable error with a reason code of 00C90224. Utilities will behave as with status RO but with the new reason code for the resource unavailable. SET REPLICATION function for RRSAF The RRSAF SET_REPLICATION function enables an APF authorized program to identify to DB2 as a replication program. Calling the SET_REPLICATION function is optional. If you do not call it, DB2 treats the application normally. The SET_REPLICATION function allows the application to perform insert, update, and delete operations when the tablespace or database is started access RREPL. The following diagram shows the syntax of the SET REPLICATION 1 function. DSNRLI SET_REPLICATION function >>--CALL DSNRLI-------------------------------------------> >-(--function--+------------------------------------+--)-->< '--,--retcode--+----------------+--' '--,--reascode--' Parameters point to the following areas: function An 18 byte area that contains SET_REPLICATION retcode A 4-byte area in which RRSAF places the return code. This parameter is optional. If you do not specify retcode, RRSAF places the return code in register 15 and the reason code in register 0. reascode A 4-byte area in which RRSAF places the reason code. This parameter is optional. If you do not specify reascode, RRSAF places the reason code in register 0. If you specify reascode, you must also specify retcode. -DISPLAY DATABASE Syntax +--,------------+ v | >--RESTRICT--(-----+---------+--+--)-->< |--ACHKP--| |--CHKP---| |--COPY---| |--GRECP--| |--LPL----| |--RBDP---| |--RECP---| |--REORP--| |--RO-----| |--RREPL--| |--STOP---| |--UT-----| |--UTRO---| |--UTRW---| |--UTUT---| |--UT*----| '--WEPR---' RESTRICT Limits the display to databases, table spaces, or indexes in a restricted status. This includes those page sets that have logical page list entries. Specifying one or more keywords further limits the display to the named objects only. 1 Abbreviation: RES Use of a database is restricted if the database is in any of the following situations: It is started for read-only processing. It is started for read or replication only processing. It is started for utility-only processing. It is stopped. Use of a table space or index space is restricted if the table space or index space is in any of the following situations: It is in one of the three situations listed previously. It is being processed by a utility. It is in COPY-pending, CHECK-pending, RECOVER-pending, group buffer pool RECOVER-pending, auxiliary CHECK-pending, or REORG-pending status. It contains a page error range. It contains pages in the logical page list (LPL). Specify one or more of the following keywords to limit objects that are to belisted. ACHKP Displays objects in the auxiliary warning advisory state. CHKP Display objects that are in CHECK-pending status. COPY Display objects that are in COPY-pending status. GRECP Displays objects that are in group buffer pool RECOVER-pending status. LPL Displays logical page list entries. RBDP Displays index objects that are in REBUILD- or RECOVER-pending status. This includes the restricted states RBDP, RBDP*, PSRBDP, LPL, and WEPR. RECP Displays objects that are in RECOVER-pending status, including the restricted states RECP, RECP*, LPL, and WEPR (write error page range). REORP Displays objects that are in REORG-pending status. RO Displays objects that are in read-only mode. RREPL Displays objects that are in read and replication only mode. STOP Displays objects that are stopped, including the restricted states STOP, STOPE, STOPP, and LSTOP. UT Displays objects that are in utility access mode. UTRO Display objects that are serialized for utility access and available for read-only access. UTRW Display objects that are serialized for utility access and 1 available for read-write access. UTUT Displays objects that are serialized for utility access and unavailable. UT* Displays objects that are in any utility access mode: UT, UTRW, UTRO, or UTUT. WEPR Displays write error page range information. -START DATABASE Syntax .--RW-----. >--ACCESS--(--+--RO-----+--)-->< |--UT-----| |--RREPL--| '--FORCE--' Option descriptions ACCESS Specifies whether the objects that are started are in read/write read only, or utility only status. Also forces access to objects that are in unavailable status. Abbreviation: ACC (RW) Allows programs to read from and write to the specified databases, table spaces, indexes, or partitions. (RO) Allows programs to only read from the specified databases, table spaces, indexes, or partitions. Any programs attempting to write to the specified objects will not succeed. Do not use this option for a database for declared temporary tables (databases created with the AS TEMP option). (UT) Allows only DB2 online utilities and the SQL DROP statement to access the specified databases, table spaces, indexes, or partitions. (RREPL) Allows programs to only read from the specified databases, table spaces, indexes, or partitions unless they have identified as a replication program. Any other programs attempting to write to the specified objects will not succeed. Do not use this option for a database for declared temporary tables (databases created with the AS TEMP option). Note: If RREPL is specified in V10 CM or V10 ENFM it will be converted to RO and no message will be issued. (FORCE) Resets any indications that a table space, index, or partition is unavailable because of pages in the logical page list, pending-deferred restarts, write-error ranges, read-only accesses, or utility controls. FORCE also resets the 1 CHECK-pending, COPY-pending, and RECOVER-pending states. Full access to the data is forced. FORCE cannot be used to reset the restart-pending (RESTP) state. When using ACCESS(FORCE), you must use a single database name, the SPACENAM option, and an explicit list of table space and index names. You cannot use any range or combination of pattern- matching characters (*), including DATABASE (*) or SPACENAM (*). A utility-restrictive state is reset (and the utility is terminated) only if all of the target objects are reset with this command. To identify which objects are target objects of the utility, use the DISPLAY DATABASE command, or run the DIAGNOSE utility with the DISPLAY SYSUTIL option. The DIAGNOSE utility should be used only under the direction of IBM Software Support. Note: ACCESS(FORCE) will not successfully complete if the object you are trying to force was placed in a utility-read-only (UTRO) utility-read-write (UTRW), or utility-utility (UTUT) state by a utility running in a previous release of DB2. If this situation is encountered, DB2 issues message DSNI041I. To reset the restrictive state, you must terminate the utility using the release of DB2 in which it was started. A table space or index space that is started with ACCESS(FORCE) might be in an inconsistent state. New Codes: 00C12035 Explanation: The DB2 RRSAF attachment facility function SET_REPLICATION was invoked by a program that was not APF authorized or was not running in supervisor state. This condition can indicate a security violation. System action: The application is abended. User response: The SET_REPLICATION function can only be invoked from an APF authorized or supervisor state program. Contact your security administrator to make the changes required to make your program an APF authorized program or to have your program run in supervisor state. Problem determination: 00C90224 Explanation: An attempt was made to allocate a resource for update operations. However, the resource was already started for read and replication only access. System action: The allocation process is not allowed. Operator response: If this reason code appears in message 1 DSNT501I, determine whether the named resource should be started for read and replication only access. User response: Determine when the resource is started for read/write access, and rerun the job. Problem determination: The requested operation is not performed. An SQLCODE -904 is issued, and/or message DSNT501I is issued. For more information, refer to the SQL return code in Codes, or to the description of the DSNT501I message in Messages.). ++ HOLD(UK98030) SYS FMID(HDBAA10) REASON(ACTION) DATE(13270) COMMENT (DSNTIJUZ must be run to reassemble the system parameters module (DSNZPARM by default) to pick up changes to DSN3DIR1. This is the enabling APAR for PM90970. The PTF for APAR PM90970 must be applied to all members of a DB2 V10 data sharing group before applying the PTF for this APAR PM94353 and exploiting RREPL.). UK98030 HOLD DATA END UK98047 HOLD DATA START UK98047 HOLD DATA END UK98065 HOLD DATA START UK98065 HOLD DATA END UK98072 HOLD DATA START UK98072 HOLD DATA END UK98085 HOLD DATA START UK98085 HOLD DATA END UK98116 HOLD DATA START UK98116 HOLD DATA END UK98135 HOLD DATA START ++ HOLD(UK69865) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13275) COMMENT (After appying the apar, rebind all the packages found by the following query. SELECT NAME, RELEASE FROM SYSIBM.SYSPACKAGE WHERE RELEASE = 'I';). UK98135 HOLD DATA END UK98147 HOLD DATA START UK98147 HOLD DATA END 1UK98150 HOLD DATA START UK98150 HOLD DATA END UK98223 HOLD DATA START UK98223 HOLD DATA END UK98262 HOLD DATA START UK98262 HOLD DATA END UK98271 HOLD DATA START UK98271 HOLD DATA END UK98290 HOLD DATA START UK98290 HOLD DATA END UK98291 HOLD DATA START UK98291 HOLD DATA END UK98355 HOLD DATA START UK98355 HOLD DATA END UK98357 HOLD DATA START UK98357 HOLD DATA END UK98463 HOLD DATA START UK98463 HOLD DATA END UK98497 HOLD DATA START ++ HOLD(UK77628) SYS FMID(HDBAA10) REASON(DOC) DATE(13288) COMMENT (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 1 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.). ++ HOLD(UK98497) SYS FMID(HDBAA10) REASON(ACTION) DATE(13288) COMMENT (***Action for PM97729: See PM97729 APAR/PTF text for additional information. PM97729 corrects the following problem: SYSOUT should not be specified on the SYSREC DD for UNLOAD SPANNED YES. In some cases, no error occured. With PM97729, DSNU034I with reason code X'00E40070' will be issued.). ++ HOLD(UK97410) SYS FMID(HDBAA10) REASON(ACTION) DATE(13288) COMMENT (***Action for PM91942: See PM91942 APAR/PTF text for additional information. PM91942 corrects the following problem: UNLOAD SPANNED YES allocated a VBS data set with LRECL=32756 even though logical records in the data set were greater than 32K (32K = 32768). IDCAMS PRINT of the data set ended with S002-0004 because a logical record length was greater than LRECL for the data set. UNLOAD SPANNED YES will be corrected to use LRECL 32768 for VBS data sets to allow for logical records greater than 32K. Existing IDCAMS does not support VBS data sets with logical records greater than 32760 so this fix could cause IDCAMS to issue IDC0005I in this case. Prior to PM91942, if UNLOAD SPANNED YES generated a SYSREC with all logical records less than 32760, IDCAMS against that SYSREC would not issue IDC0005I; however, this SYSREC would not be correct for appending logical records greater than 32K on a subsequent UNLOAD. If it is known that all logical records generated by UNLOAD are less than 32K, specifying SPANNED NO or omitting SPANNED may be used to generate a format VB data set; otherwise, UNLOAD SPANNED YES (causing a VBS data set with LRECL=32768) is appropriate.). ++ HOLD(UK97425) SYS FMID(HDBAA10) REASON(ACTION) DATE(13288) 1 COMMENT (The PTF for APAR PM88695 has modified CSECTs in both the DSNUT101 and DSNUTILA unload 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.). ++ HOLD(UK77628) SYS FMID(HDBAA10) REASON(ACTION) DATE(13288) COMMENT (*** 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.). UK98497 HOLD DATA END UK98505 HOLD DATA START UK98505 HOLD DATA END UK98533 HOLD DATA START UK98533 HOLD DATA END UK98543 HOLD DATA START ++ HOLD(UK98543) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13290) COMMENT (PM94543 corrects a problem of incorrect output returned when a range list access path is chosen for the table and the boolean term predicate not applied as matching predicate in all OR legs.). ++ HOLD(UK93759) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13290) COMMENT (***Action for PM85238: See PM85238 APAR/PTF text for additional information about why a REBIND is necessary. PM85238 corrects a problem of incorrect output may be returned when a range list access path is chosen for the table and one of non-boolean term predicates under OR is not the matching predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK78270) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13290) COMMENT (***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.). UK98543 HOLD DATA END UK98545 HOLD DATA START ++ HOLD(UK98545) SYS FMID(HDBAA10) REASON(DOC) DATE(13291) COMMENT (00E70031 Explanation The maximum number of audit policies exceeded in the subsystem. No more than 32 audit policies can be started in a subsystem. System action The audit policy is not started. This reason code is in the IFCID 0362 trace record. System programmer response Issue the following command to identify the audit policies that are started: DISPLAY TRACE(AUDIT) DETAIL(2) Then, issue a STOP TRACE command to stop an audit policy before starting one.). UK98545 HOLD DATA END UK98551 HOLD DATA START UK98551 HOLD DATA END UK98569 HOLD DATA START ++ HOLD(UK98569) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13293) COMMENT (***Action for PM94086: See PM94086 APAR/PTF text for additional information about why a REBIND is necessary. PM94086 corrects a problem that incorrect output or ABEND0C7 RC00000000 at the location DSNXGRDS DSNXROHB OFFSET273C for V9(OFFSET27B8 for V10, OFFSET2550 for V11) could be caused by an 1 UPDATE statement that contains a row expression assignment and a scalar full select returning empty is assigning to a NOT NULL column in the the row expression assignment. 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.). ++ HOLD(UK90803) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(13293) COMMENT (***Action for PM74746: See PM74746 APAR/PTF text for additional information about why a REBIND is necessary. PM74746 corrects a bind time problem that can result in an ABEND0C6-6 at location DSNXVCDF+27B or +27D for a query referencing a large complex view that has a UNION ALL and decimal arithmetic. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90803) SYS FMID(HDBAA10) REASON(ACTION) DATE(13293) COMMENT (Please note that the following action will need to be performed along with applying the ptf for this apar. Any nested views that are created with the symptoms mentioned in the apar description will need to be dropped and recreated.). UK98569 HOLD DATA END UK98586 HOLD DATA START UK98586 HOLD DATA END UK98589 HOLD DATA START UK98589 HOLD DATA END UK98618 HOLD DATA START UK98618 HOLD DATA END UK98635 HOLD DATA START UK98635 HOLD DATA END UK98675 HOLD DATA START UK98675 HOLD DATA END READY END