1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES READY %HOLDDATA WDB2I.R.DB2101S.SMPPTS IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED UK71333 HOLD DATA START UK71333 HOLD DATA END UK72025 HOLD DATA START UK72025 HOLD DATA END UK72077 HOLD DATA START UK72077 HOLD DATA END UK72081 HOLD DATA START UK72081 HOLD DATA END UK72088 HOLD DATA START UK72088 HOLD DATA END UK72091 HOLD DATA START UK72091 HOLD DATA END UK72268 HOLD DATA START UK72268 HOLD DATA END UK72303 HOLD DATA START UK72303 HOLD DATA END UK72345 HOLD DATA START ++ HOLD(UK72345) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271) COMMENT (***Action for PM43934: See PM43934 APAR/PTF text for additional information about why a REBIND is necessary. PM43934 corrects a problem that can lead to an ABEND04E RC00E70005 at location DSNXESX2:P404. To make this fix effective for a static application, it must 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(UK66763) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271) COMMENT (***Action for PM28718: 1 See PM28718 APAR/PTF text for additional information about why a REBIND is necessary. PM28718 corrects a problem of incorrect output when running a query which SELECT from MERGE when the UPDATE clause is in row expression format and the MERGE contains an INCLUDE 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.). UK72345 HOLD DATA END UK72373 HOLD DATA START ++ HOLD(UK72373) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271) COMMENT (***Action for PM39078: See PM39078 APAR/PTF text for additional information about why a REBIND is necessary. PM39078 corrects a problem of missing warning message when a query which references an XML column that does not support multiple XML versions and it is bound with the USE CURRENTLY COMMITTED option. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK72373) SYS FMID(HDBAA10) REASON(DOC) DATE(11271) COMMENT (Existing warning SQLCODE +20002 is changed by this APAR/PTF. The change will be documented in the DB2 Codes, SQL Reference, Command Reference manuals respectively. The texts for SQLCODE +20002 are: +20002 THE clause SPECIFICATION IS IGNORED FOR OBJECT object-name Explanation This message is issued in response to a clause specification that was ignored on a query statement. System action The statement is processed. User response To stop receiving this message, avoid ACCESSCONCURRENTRESOLUTION(UseCurrentlyCommitted) bind option for a plan or package accessing non-versioned XML, or avoid a statement (accessing non-versioned XML) prepared with "Use Currently Committed" attribute. User response needs real action: 1 If an XML column does not support multiple XML versions, you can convert to an XML column that supports multiple XML versions by following these steps: 1. Unload the data from the table that contains the XML columns. 2. Drop the table. 3. Create the table in a universal table space. The new table supports multiple XML versions. 4. Load the data into the table. SQLSTATE 01624). UK72373 HOLD DATA END UK72444 HOLD DATA START UK72444 HOLD DATA END UK72447 HOLD DATA START UK72447 HOLD DATA END UK72517 HOLD DATA START UK72517 HOLD DATA END UK72540 HOLD DATA START UK72540 HOLD DATA END UK72550 HOLD DATA START UK72550 HOLD DATA END UK72558 HOLD DATA START UK72558 HOLD DATA END UK72603 HOLD DATA START UK72603 HOLD DATA END UK72625 HOLD DATA START UK72625 HOLD DATA END UK72687 HOLD DATA START UK72687 HOLD DATA END UK72741 HOLD DATA START UK72741 HOLD DATA END 1UK72775 HOLD DATA START UK72775 HOLD DATA END UK72786 HOLD DATA START UK72786 HOLD DATA END UK72803 HOLD DATA START ++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(DOC) DATE(11284) COMMENT (This PTF introduces the following changes to DB2 ODBC externals: New DB2 ODBC for z/OS initialization keywords described as follows. LIMITEDBLOCKFETCH = 0 | 1 This keyword is a performance optimization keyword that specifies whether DB2 ODBC is to attempt limited block fetch when fetching result sets from the connected data source. 0 = Limited block fetch is not used. 0 is the default. 1 = DB2 ODBC attempts to use limited block fetch. If blocking is supported at the server for the result set that is being fetched, DB2 ODBC retrieves as many rows as it can fit in a query data block in a single fetch request. QUERYDATASIZE = integer This keyword specifies the amount of query data, in bytes, that DB2 returns on each FETCH operation when limited block fetch is enabled. The default value is 32767. Possible values are: 32767 294911 557055 819199 65535 327679 589823 851967 98303 360447 622591 884735 131071 393215 655359 917503 163839 425983 688127 950271 196607 458751 720895 983039 229375 491519 753663 1015807 262143 524287 786431 1048575 If you specify a value that is not a valid value, DB2 ODBC sets QUERYDATASIZE to the nearest valid value. Information about the new DB2 ODBC initialization keywords and DB2 ODBC limited block fetch will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). ++ HOLD(UK67822) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284) COMMENT (*** Action for PM32032 (Version 10) The following database request module (DBRM) is updated by this PTF: DSNCLIQR Application of this PTF requires a BIND PACKAGE for the above package. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. 1 Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site.). ++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284) COMMENT (The following database request modules (DBRMs) are updated by this PTF: DSNCLINF DSNCLIC1 DSNCLIMS DSNCLIQR DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only) Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site. This PTF introduces two new DB2 ODBC initialization keywords LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block fetch. Limited block fetch is a performance optimization that enables applications to improve the performance of FETCH operations when connected to a local DB2 for z/OS server. If limited block fetch is not desired, no further action is necessary other than rebinding the DBRMs listed above; otherwise please note the following. When you enable limited block fetch, the data that is returned to your application might not reflect the data that has been committed to the source table. If your application fetches data from tables that are updated by other users, or if your application uses savepoints and issues ROLLBACK TO SAVEPOINT to manage transactions, you should disable limited block fetch.). ++ HOLD(UK60517) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284) COMMENT ( This PTF updates DB2 ODBC for z/OS database request module (DBRM) DSNCLIC1. After you apply this PTF, you need to run the BIND PACKAGE command to recreate the package for DSNCLIC1. Failure to bind the required package could result in SQLCODE -805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the prefix.SDSNSAMP data set for an example of how to perform the BIND command.). ++ HOLD(UK56516) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284) COMMENT 1 (The following database request modules (DBRMs) for ODBC DB2 for z/OS are updated by this PTF: DSNCLIMS DSNCLIC1 Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the SDSNSAMP dataset for an example of how to perform the BIND command.). UK72803 HOLD DATA END UK72809 HOLD DATA START UK72809 HOLD DATA END UK72834 HOLD DATA START UK72834 HOLD DATA END UK72870 HOLD DATA START UK72870 HOLD DATA END UK72880 HOLD DATA START UK72880 HOLD DATA END UK72946 HOLD DATA START ++ HOLD(UK72946) SYS FMID(J2AG210) REASON(ACTION) DATE(11287) COMMENT (This apar provides the functions to retrieve the current and surrounding grid cells from a starting point. For the existing users, if they like to use this function then submit 2 last steps: CREATE01 and BINDSK19 of DSN5SENB job. For the new users should follow the instructions contained in the book IBM Spatial Support for DB2 z/OS to enable Spatial functionality.). UK72946 HOLD DATA END UK72958 HOLD DATA START UK72958 HOLD DATA END UK72974 HOLD DATA START ++ HOLD(UK72974) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11287) COMMENT (***Action for PM48011: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM48011 corrects a problem of inaccurate cost estimation for a query with subqueries that is correlated to multiple tables or with a correlated subquery predicate under a non-boolean term 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.). UK72974 HOLD DATA END UK72985 HOLD DATA START UK72985 HOLD DATA END UK73058 HOLD DATA START UK73058 HOLD DATA END UK73079 HOLD DATA START UK73079 HOLD DATA END UK73137 HOLD DATA START ++ HOLD(UK73137) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(11294) COMMENT (PM44216 is an enabling APAR that includes additional support for the subsystem parameter XML_RANDOMIZE_DOCID (added by APAR PM31487). The additional support is enabled when XML_RANDOMIZE_DOCID is set to YES. Users who are not creating tables with XML columns on data-sharing systems will not be affected by PM44210/PM44216. For users who will create new tables with XML columns in a data-sharing group and intend to enable the parameter XML_RANDOMIZE_DOCID, the pre-conditioning APAR PM44210 for DB2 9 for z/OS and the pre-conditioning APAR PM31486 for DB2 10 for z/OS must be applied to all data-sharing members before enabling APAR PM44216 is applied to any member.). UK73137 HOLD DATA END UK73147 HOLD DATA START UK73147 HOLD DATA END UK73165 HOLD DATA START ++ HOLD(UK73165) SYS FMID(HDBAA10) REASON(ACTION) DATE(11297) COMMENT (The PTF for APAR PM47687 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch 1 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.). UK73165 HOLD DATA END UK73178 HOLD DATA START UK73178 HOLD DATA END UK73180 HOLD DATA START ++ HOLD(UK73180) SYS FMID(HDBAA10) REASON(ACTION) DATE(11297) COMMENT (***Action for PM37057 (V10): This APAR/PTF provides additional enhancements to the DB2 10 for z/OS support for client access using a digital certificate. DB2 10 for z/OS remote connection authentication processing has been enhanced to ensure remote client's that accesses DB2 using a digital certificate are properly authenticated when the remote client user ID is different from the certificate user ID. To implement client access to DB2 using a digital certificate, users need to define a trusted context at the DB2 server where the system authorization ID is set to the value of the user ID associated with the client certificate. The trusted context would need to include all the user IDs that are allowed to use it (such as, remote client user IDs or the mapped user IDs if z/OS identity name filtering is configured). Example: A client certificate is registered to RACF and it is associated with user ID, CERTID01. A remote client application is configured to access DB2 using a digital certificate and its user ID provided to DB2 is USER01. To define the trusted context at the DB2 server, users might consider the following sample DDL: CREATE TRUSTED CONTEXT CTXT1 BASED UPON CONNECTION USING CERTID01 NO DEFAULT ROLE ENABLE ATTRIBUTES(ADDRESS '1.2.3.4') WITH USE FOR USER01; See PM37057 APAR/PTF text for additional information.). UK73180 HOLD DATA END UK73264 HOLD DATA START UK73264 HOLD DATA END 1 UK73432 HOLD DATA START UK73432 HOLD DATA END UK73436 HOLD DATA START UK73436 HOLD DATA END UK73478 HOLD DATA START ++ HOLD(UK73478) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(11306) COMMENT (***Action for PM35190: See PM35190 APAR/PTF text for additional information. PM35190 is the enabling APAR that introduces the new function support to allow selects from some Directory objects. Earlier, a pre-conditioning APAR PM42331 was delivered and will be needed. In a data sharing group, this pre-conditioning APAR should be applied to all members before applying this ENABLING APAR to any member. The new function will be enabled once this ENABLING APAR is applied and DB2 enters NFM or once this ENABLING APAR is applied and a special CATMAINT is run with the input: CATMAINT UPDATE UNLDDN PM35190). ++ HOLD(UK73478) SYS FMID(HDBAA10) REASON(DOC) DATE(11306) COMMENT (***Action for PM35190: See PM35190 APAR/PTF text for additional information. This APAR/PTF changes the text of SQL code -607. The change will be documented in the DB2 Codes manual and in the Information Management Software for z/OS Solutions Information Center. A new bullet under the example for SQL code -607: - The operation is on a directory object and the unit of work could not be converted to UR. For example: UPDATE T1 SET C1 = (SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX); in this case, the SELECT against a directory object can not be converted to UR.). ++ HOLD(UK72772) SYS FMID(HDBAA10) REASON(ACTION) DATE(11306) COMMENT (See PM47932 APAR/PTF text for additional information. This PTF fixes the default maximum number of databases that can be created implicitly. Applying this PTF will not remove existing implicit databases 1 or update the current maximum number of implicit databases allowed. You can use the following query to find out the current maximum number of implicit databases allowed: SELECT MAXVALUE FROM SYSIBM.SYSSEQUENCES WHERE SCHEMA = 'SYSIBM' AND NAME = 'DSNSEQ_IMPLICITDB'; You can use the following statement to alter it: ALTER SEQUENCE SYSIBM.DSNSEQ_IMPLICITDB MAXVALUE This can be DB2's new default value of 10000 or any valid value as allowed by the ALTER SEQUENCE statement.). UK73478 HOLD DATA END UK73534 HOLD DATA START UK73534 HOLD DATA END UK73587 HOLD DATA START UK73587 HOLD DATA END UK73600 HOLD DATA START UK73600 HOLD DATA END UK73617 HOLD DATA START UK73617 HOLD DATA END UK73625 HOLD DATA START UK73625 HOLD DATA END UK73649 HOLD DATA START UK73649 HOLD DATA END UK73663 HOLD DATA START ++ HOLD(UK73663) SYS FMID(HDBAA10) REASON(ACTION) DATE(11312) COMMENT (This PTF corrects a problem where rows containing incorrectly truncated data are inserted into explain tables DSN_FUNCTION_TABLE and DSN_PREDICAT_TABLE. As a result, subsequent SELECTs on these tables received SQLCODE -331. After applying this PTF, you must delete the rows that are currently in the tables causing -331 to stop receiving the SQL code.). UK73663 HOLD DATA END 1UK73677 HOLD DATA START UK73677 HOLD DATA END UK73691 HOLD DATA START UK73691 HOLD DATA END UK73695 HOLD DATA START UK73695 HOLD DATA END UK73750 HOLD DATA START UK73750 HOLD DATA END UK73797 HOLD DATA START ++ HOLD(UK73797) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11315) COMMENT (***Action for PM50507: See PM50507 APAR/PTF text for additional information about why a REBIND is necessary. PM50507 corrects a problem of the DB2 optimizer in calculating the cost of hash access for a hash-organized table. The fix will get a more accurate estimation of hash access, and enable the DB2 optimizer to choose hash access methods over other suboptimal method(s). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK72787) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11315) COMMENT (A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM45292 corrects a problem in which a DB2 intentional abend may occur when a query contains the RID function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK73797 HOLD DATA END UK73808 HOLD DATA START UK73808 HOLD DATA END UK73842 HOLD DATA START UK73842 HOLD DATA END 1 UK73863 HOLD DATA START ++ HOLD(UK70468) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11319) COMMENT (***Action for PM38744: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM38744 corrects a problem of inaccurate cost estimation for an index on the inner table in a join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK73863 HOLD DATA END UK73908 HOLD DATA START ++ HOLD(UK73908) SYS FMID(HDBAA10) REASON(ACTION) DATE(11320) COMMENT (The PTF for APAR PM50893 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.). UK73908 HOLD DATA END UK73938 HOLD DATA START UK73938 HOLD DATA END UK73941 HOLD DATA START UK73941 HOLD DATA END UK73956 HOLD DATA START UK73956 HOLD DATA END UK74004 HOLD DATA START UK74004 HOLD DATA END UK74043 HOLD DATA START UK74043 HOLD DATA END 1 UK74044 HOLD DATA START UK74044 HOLD DATA END UK74063 HOLD DATA START UK74063 HOLD DATA END UK74123 HOLD DATA START UK74123 HOLD DATA END UK74131 HOLD DATA START UK74131 HOLD DATA END UK74181 HOLD DATA START UK74181 HOLD DATA END UK74244 HOLD DATA START UK74244 HOLD DATA END UK74247 HOLD DATA START UK74247 HOLD DATA END UK74314 HOLD DATA START UK74314 HOLD DATA END UK74373 HOLD DATA START ++ HOLD(UK66610) SYS FMID(HDBAA10) REASON(DOC) DATE(11334) 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 1 greater than RRTHashOvrFlwRatio. RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The default value is ' 15'. A plus sign (+) preceding or following the value, or a plus sign by itself indicates that the DSNACCOX stored procedure returns the calculated ratio value in the result set. A negative value indicates that the criterion is not used. The ratio of hash access overflow index entries to the total number of rows is returned in column RRTHashOvrFlwRatPCT of the result set. Figure 4. DSNACCOX formula for recommending a REORG on a table space has an additional criteria: (((QueryType='REORG' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL')) AND (REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR (NACTIVE IS NULL OR NACTIVE > 5) AND ((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND REORGINSERTS > RRTInsertsAbs) OR (((REORGDELETE x 100) / TOTALROWS > RRTDeletesPct) AND REORGDELETE > RRTDeleteAbs) OR (REORGCLUSTERSENS > 0 AND (REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR ((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR | (Object is not using hash organization and ((SPACE x 1024) / RRTDataSpaceRat)) OR ((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS > RRTIndRefLimit) OR REORGMASSDELETE > RRTMassDelLimit OR EXTENTS > ExtentLimit) OR | ((QueryType='REORG' OR QueryType='ALL') AND | ObjectType='ALL' * AND | Overflow index hash access is used**, AND | ((overflow index TOTALENTRY x 100) / TOTALROWS > RRTHashOvrFlwRatio)) OR ((QueryType='RESTRICT' OR QueryType='ALL') AND (ObjectType='TS' OR ObjectType='ALL') AND The table space is in advisory or informational reorg pending status) |Note: | * ObjectType='ALL' must be specified to use this criteria. | for this criterion to be used. If ObjectType='TS' or | ObjectType='IX' is specified, and '+' is specified for | RRTHashOvrFlwRatio, an error message is issued. If | ObjectType='TS' or ObjectType='IX' is specified, and | '+' is not specified for RRTHashOvrFlwRatio, this | 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 1 "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(UK66610) SYS FMID(HDBAA10) REASON(ACTION) DATE(11334) 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). UK74373 HOLD DATA END UK74375 HOLD DATA START UK74375 HOLD DATA END UK74383 HOLD DATA START UK74383 HOLD DATA END UK74390 HOLD DATA START UK74390 HOLD DATA END UK74399 HOLD DATA START ++ HOLD(UK74399) SYS FMID(HDBAA10) REASON(DELETE) DATE(11335) COMMENT (This PTF deletes the module DSNADMJ5. This PTF deletes the module DSNXEAS. 1 This PTF deletes the module DSNXEAS1. This PTF deletes the module DSNXESID. This PTF deletes the module DSN7GBRS.). UK74399 HOLD DATA END UK74453 HOLD DATA START UK74453 HOLD DATA END UK74462 HOLD DATA START UK74462 HOLD DATA END UK74477 HOLD DATA START UK74477 HOLD DATA END UK74482 HOLD DATA START ++ HOLD(UK74482) SYS FMID(HDBAA10) REASON(ACTION) DATE(11338) 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. It also modifies DSNADMSB, a program that can be used to call SYSPROC.ADMIN_INFO_SQL. Finally, it modifies the DB2 V10 installation process, relocating responsibility for binding the DSNADMSB package and plan from job DSNTIJSG to job DSNTIJRT. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRMs DSNADMSS and DSNADMSB --------------------------------------------------------------- ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2 supplied stored procedures. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- 1 ==> 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 DSNTIJSG --------------------------------------------------------------- ==> All DB2 V10 customers who maintain a customized copy of DB2 installation job DSNTIJSG need to take this action after applying the PTF (a) Edit your customized copy of DSNTIJSG. (b) In job step DSNTIRU, locate and remove the bind package and bind plan statements for DSNADMSB. DSNADMSB is now bound as necessary when you run job DSNTIJRT. (c) In job step DSNTIJG, locate and remove the grant statement for PLAN DSNADMSB. Authority to execute DSNADMSB is now granted when you run job DSNTIJRT according to the authorization IDs in the GRANTTO list of the configuration statement for stored procedure SYSPROC.ADMIN_INFO_SQL. (d) Save your changes.). ++ HOLD(UK70375) SYS FMID(HDBAA10) REASON(ACTION) DATE(11338) 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. It also modifies DSNADMSB, a program that can be used to call SYSPROC.ADMIN_INFO_SQL. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2 supplied stored procedures. 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 1 changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. --------------------------------------------------------------- (2) Refresh the WLM environment --------------------------------------------------------------- ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Issue the following VARY MVS command from the console to refresh the WLM application environment: VARY WLM,APPLENV=!wlmenv!,REFRESH where !wlmenv! is the name of the WLM application environment for running the SYSPROC.ADMIN_INFO_SQL stored procedure. --------------------------------------------------------------- (3) Rebind the package for DSNADMSB --------------------------------------------------------------- ==> All DB2 V10 customers who use the DSNADMSB program to call the SYSPROC.ADMIN_INFO_SQL stored procedure need to take this action after applying the PTF Submit a job that contains the following BIND statements: BIND PACKAGE(DSNADMSB) MEM(DSNADMSB) - ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) - LIBRARY('.SDSNDBRM') where is the high-level qualifier for the target DB2 subsystem.). UK74482 HOLD DATA END UK74491 HOLD DATA START ++ HOLD(UK74491) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046) COMMENT (***Action for PM53780: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM53780 corrects a problem in which incorrect statistics are used for a DGTT or CGTT when the table is empty. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). 1++ HOLD(UK73797) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046) COMMENT (***Action for PM50507: See PM50507 APAR/PTF text for additional information about why a REBIND is necessary. PM50507 corrects a problem of the DB2 optimizer in calculating the cost of hash access for a hash-organized table. The fix will get a more accurate estimation of hash access, and enable the DB2 optimizer to choose hash access methods over other suboptimal method(s). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK72787) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046) COMMENT (A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM45292 corrects a problem in which a DB2 intentional abend may occur when a query contains the RID function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK74491 HOLD DATA END UK74503 HOLD DATA START UK74503 HOLD DATA END UK74527 HOLD DATA START UK74527 HOLD DATA END UK74534 HOLD DATA START UK74534 HOLD DATA END UK74535 HOLD DATA START ++ HOLD(UK74535) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340) 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(UK68665) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340) 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(UK66483) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340) 1 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.). UK74535 HOLD DATA END UK74537 HOLD DATA START UK74537 HOLD DATA END UK74555 HOLD DATA START UK74555 HOLD DATA END UK74560 HOLD DATA START ++ HOLD(UK74560) SYS FMID(HDBAA10) REASON(ACTION) DATE(11341) COMMENT (This PTF fixes an 0C4 abend in the user-defined function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) when it is processing a DB2 scheduler task that has multiple execution statuses. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** *********************************************************** * This action is required for all V10 customers *********************************************************** Run your customized copy of job DSNTIJRT with MODE(INSTALL) to alter the scratchpad length of the modified user-defined function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) from 16 to 8208 and to bind this function's DBRM. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job.). UK74560 HOLD DATA END UK74587 HOLD DATA START UK74587 HOLD DATA END UK74596 HOLD DATA START UK74596 HOLD DATA END UK74623 HOLD DATA START 1UK74623 HOLD DATA END UK74648 HOLD DATA START UK74648 HOLD DATA END UK74649 HOLD DATA START UK74649 HOLD DATA END UK74659 HOLD DATA START UK74659 HOLD DATA END UK74716 HOLD DATA START ++ HOLD(UK74716) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11346) COMMENT (***Action for PM52371: See PM52371 APAR/PTF text for additional information about why a REBIND is necessary. PM52371 corrects a problem of unexpected SQLCODE -161 issued for an INSERT into SYMMETRIC view statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK74716 HOLD DATA END UK74718 HOLD DATA START UK74718 HOLD DATA END UK74721 HOLD DATA START UK74721 HOLD DATA END UK74725 HOLD DATA START UK74725 HOLD DATA END UK74731 HOLD DATA START UK74731 HOLD DATA END UK74737 HOLD DATA START UK74737 HOLD DATA END UK74745 HOLD DATA START UK74745 HOLD DATA END 1 UK74747 HOLD DATA START UK74747 HOLD DATA END UK74778 HOLD DATA START UK74778 HOLD DATA END UK74779 HOLD DATA START ++ HOLD(UK74779) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11347) 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(11347) 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(11347) 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.). UK74779 HOLD DATA END 1 UK74807 HOLD DATA START UK74807 HOLD DATA END UK74815 HOLD DATA START UK74815 HOLD DATA END UK74866 HOLD DATA START ++ HOLD(UK74866) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11349) COMMENT (***Action for PM50516: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM50516 corrects a problem in which an incorrect compound filter factor is computed when there is data skew and that data skew is represented by frequency statistics. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK74866 HOLD DATA END UK74868 HOLD DATA START UK74868 HOLD DATA END UK74881 HOLD DATA START UK74881 HOLD DATA END UK74884 HOLD DATA START UK74884 HOLD DATA END UK74911 HOLD DATA START UK74911 HOLD DATA END UK74922 HOLD DATA START UK74922 HOLD DATA END UK74940 HOLD DATA START UK74940 HOLD DATA END UK74968 HOLD DATA START UK74968 HOLD DATA END 1UK74981 HOLD DATA START UK74981 HOLD DATA END UK74989 HOLD DATA START UK74989 HOLD DATA END UK75093 HOLD DATA START UK75093 HOLD DATA END UK75105 HOLD DATA START UK75105 HOLD DATA END UK75106 HOLD DATA START UK75106 HOLD DATA END UK75161 HOLD DATA START ++ HOLD(UK75161) SYS FMID(HDBAA10) REASON(ACTION) DATE(11365) COMMENT (The PTF for APAR PM47255 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.). UK75161 HOLD DATA END UK75202 HOLD DATA START UK75202 HOLD DATA END UK75208 HOLD DATA START UK75208 HOLD DATA END UK75229 HOLD DATA START UK75229 HOLD DATA END UK75234 HOLD DATA START UK75234 HOLD DATA END UK75262 HOLD DATA START 1UK75262 HOLD DATA END UK75286 HOLD DATA START UK75286 HOLD DATA END UK75291 HOLD DATA START ++ HOLD(UK75291) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12009) COMMENT (***Action for PM49645: See PM49645 APAR/PTF text for additional information about why a REBIND is necessary. PM49645 corrects a problem of abend0E4 at DSNXESX2:M999 for a SELECT from INSERT/UPDATE/MERGE/DELETE statement that contain an include column and an EXISTS 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(UK71122) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12009) COMMENT (See PM43916 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM43916 corrects a problem where a query with INSERT/UPDATE/DELETE within a SELECT statement hits SQLCODE -20478 error since the estimated query cost has a mismatch between the SQLCA and GET DIAGNOSTICS area. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK75291 HOLD DATA END UK75294 HOLD DATA START UK75294 HOLD DATA END UK75317 HOLD DATA START UK75317 HOLD DATA END UK75322 HOLD DATA START UK75322 HOLD DATA END UK75335 HOLD DATA START UK75335 HOLD DATA END 1 UK75385 HOLD DATA START UK75385 HOLD DATA END UK75395 HOLD DATA START UK75395 HOLD DATA END UK75452 HOLD DATA START UK75452 HOLD DATA END UK75551 HOLD DATA START UK75551 HOLD DATA END UK75581 HOLD DATA START ++ HOLD(UK75581) SYS FMID(HDBAA10) REASON(ACTION) DATE(12019) COMMENT (The PTF for PM54759 fixes the stored procedure SYSPROC.ADMIN_UTL_MONITOR so that the task it adds to the DB2 scheduler task list to execute the stored procedure SYSPROC.ADMIN_UTL_EXECUTE can be executed by the DB2 scheduler when DECIMAL=COMMA is enabled in DSNHDECP. See the PTF cover letter for more information. *************************************************************** Actions for DB2 10 for z/OS customers who are using the DB2-supplied stored procedures SYSPROC.ADMIN_UTL_MONITOR and SYSPROC.ADMIN_UTL_EXECUTE in conjunction with the DB2 administrative task scheduler *************************************************************** After applying this PTF, you need to remove the task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list. This action is detailed below: (1) Ensure that the DB2 scheduler is up and running. If scheduler is not running, execute the following console command: START DSNADMT where DSNADMT is the name of the scheduler. (2) Invoke the user-defined function ADMIN_TASK_LIST to determine if the task 'DB2 AUTO PROCEDURE EXECUTE' is in the DB2 scheduler task list, by issuing the following SQL statement: SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE'; A JOB example for this action is given below in the JOB 1 EXAMPLES section. When no such task exists proceed to step (4). Otherwise, proceed to step (3), below. (3) Remove task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list by invoking the DB2-supplied stored procedure SYSPROC.ADMIN_TASK_REMOVE: CALL SYSPROC.ADMIN_TASK_REMOVE (task-name, return-code, message) with the input parameter 'task-name' set to 'DB2 AUTO PROCEDURE EXECUTE'. 'return-code' and 'message' are output parameters. A JOB example of using DB2 REXX Language Support for this action is given below in the JOB EXAMPLES section. (4) If the DB2 scheduler was started in step (1), stop the scheduler by executing the following console command: MODIFY DSNADMT,APPL=SHUTDOWN where DSNADMT is the name of the scheduler. *************************************************************** JOB EXAMPLES *************************************************************** Prior to running any example, customize it for your system by adding a valid job card and modifying the examples as indicated below. *************************************************************** STEP (2) EXAMPLE QUERY DSNADM.ADMIN_TASK_LIST Required actions: 1. In lines 1-3,14 replace 'DSN!!0' with the prefix of the target library for DB2 V10 2. In line 12 replace '!DSN!' with your DB2 subsystem name 3. In line 13 replace 'DSNTEP!!' with the plan name for DSNTEP2 on your DB2 *************************************************************** //JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR // DD DSN=DSN!!0.SDSNLOAD,DISP=SHR // DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR //DSNTEP2 EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20 //SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //CEEDUMP DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSTSIN DD * 1 DSN SYSTEM(!DSN!) RUN PROGRAM(DSNTEP2) PLAN(DSNTEP!!) - LIB('DSN!!0.RUNLIB.LOAD') PARMS('/ALIGN(MID)') END //SYSIN DD * SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE' *************************************************************** STEP (3) EXAMPLE CALL SYSPROC.ADMIN_TASK_REMOVE Required actions: 1. In lines 1-3 replace 'DSN!!0' with the prefix of the target library for DB2 V10 2. In line 10 replace '#' with a forward slash '/'. Closing comment sequence is not allowed within ++HOLD text. 3. In line 11 replace '!DSN!' with your DB2 subsystem name *************************************************************** //JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR // DD DSN=DSN!!0.SDSNLOAD,DISP=SHR // DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR //REXX EXEC PGM=IEBUPDTE,PARM='NEW' //SYSPRINT DD SYSOUT=* //SYSUT2 DD DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(2,1,1)), // DSORG=PO,BLKSIZE=0,RECFM=FB,LRECL=80 //SYSIN DD * ./ ADD NAME=CALLSP /* REXX *# SSID = !DSN! TASKNAME = 'DB2 AUTO PROCEDURE EXECUTE' RETCODE = 12 MESSAGE = COPIES(' ',1332) "SUBCOM DSNREXX" IF RC <> 0 THEN S_RC = RXSUBCOM('ADD','DSNREXX','DSNREXX') ADDRESS DSNREXX "CONNECT" SSID IF SQLCODE = 0 THEN DO SAY 'CONNECTED TO ' SSID ADDRESS DSNREXX "EXECSQL CALL ", "SYSPROC.ADMIN_TASK_REMOVE(", ":TASKNAME, :RETCODE, :MESSAGE)" IF SQLCODE <> 0 THEN SAY 'FAILURE DURING SP CALL SQLCODE =' SQLCODE SQLERRMC ELSE DO IF RETCODE <> 0 THEN SAY 'FAILURE RETURNED FROM SP.' RETCODE ' ' MESSAGE ELSE SAY 'TASK WAS REMOVED' END 1 ADDRESS DSNREXX "DISCONNECT" END ELSE SAY 'CONNECTION FAILED' S_RC = RXSUBCOM('DELETE','DSNREXX','DSNREXX') EXIT RETCODE /* //CALL EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20, // PARM='%CALLSP' //SYSPROC DD DSN=*.REXX.SYSUT2,DISP=(OLD,DELETE) //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DUMMY *************************************************************** END OF JOB EXAMPLES ***************************************************************). UK75581 HOLD DATA END UK75583 HOLD DATA START UK75583 HOLD DATA END UK75587 HOLD DATA START ++ HOLD(UK75587) SYS FMID(J2AG210) REASON(ACTION) DATE(12024) COMMENT (This APAR is a replacement for apar PM47333, ptf UK72946. This apar provides the function to retrieve the current and surrounding grid cells from a starting point. For existing users, if they would like to use this function, please submit the last two steps (CREATE01 and BINDSK19) of the DSN5SENB job. For new users, please follow the instructions contained in the publication "IBM Spatial Support for DB2 z/OS" to enable Spatial functionality.). ++ HOLD(UK72946) SYS FMID(J2AG210) REASON(ACTION) DATE(12024) COMMENT (This apar provides the functions to retrieve the current and surrounding grid cells from a starting point. For the existing users, if they like to use this function then submit 2 last steps: CREATE01 and BINDSK19 of DSN5SENB job. For the new users should follow the instructions contained in the book IBM Spatial Support for DB2 z/OS to enable Spatial functionality.). UK75587 HOLD DATA END UK75634 HOLD DATA START UK75634 HOLD DATA END 1 UK75674 HOLD DATA START UK75674 HOLD DATA END UK75687 HOLD DATA START UK75687 HOLD DATA END UK75766 HOLD DATA START ++ HOLD(UK71709) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12027) 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(12027) COMMENT (***Action for PM32384: See PM32384 APAR/PTF text for additional information about why a REBIND is necessary. PM32384 corrects a problem of inaccurate index filter factor estimate when multi-column cardinality exists in some cases which may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK75766 HOLD DATA END UK75779 HOLD DATA START UK75779 HOLD DATA END UK75785 HOLD DATA START UK75785 HOLD DATA END UK75836 HOLD DATA START UK75836 HOLD DATA END 1UK75883 HOLD DATA START UK75883 HOLD DATA END UK75906 HOLD DATA START ++ HOLD(UK75906) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12034) 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.). UK75906 HOLD DATA END UK75933 HOLD DATA START ++ HOLD(UK75933) SYS FMID(HIZAA10) REASON(ACTION) DATE(12034) 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.). UK75933 HOLD DATA END UK75943 HOLD DATA START UK75943 HOLD DATA END UK75946 HOLD DATA START UK75946 HOLD DATA END UK75949 HOLD DATA START ++ HOLD(UK75949) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036) COMMENT (***Action for PM50451: See PM50451 APAR/PTF text for additional information about why a REBIND is necessary. PM50451 corrects a problem of ABEND04E RC00E72018 at CSECT DSNXSBUC offset 3E7A may happen when running query with groupby clause and parallelism enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK72877) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036) COMMENT (***Action for PM45209: 1 See PM45209 APAR/PTF text for additional information about why a REBIND is necessary. PM45209 corrects a problem of incorrect output on query containing aggregate function distinct w/o group by and running with dpsi index and parallelism. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK71915) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036) COMMENT (***Action for PM43740: See PM43740 APAR/PTF text for additional information about why a REBIND is necessary. PM43740 corrects a problem of ABEND04E RC00E70005 in DSNXGDT2 M201 may occur when one of the following condition met: 1. a UNION/INTERSECT/EXCEPT query with COUNT COLUMN function, MIN/MAX aggregate function in the selection list and the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 2. Or a UNION ALL/INTERSECT ALL/EXCEPT ALL query with ORDER BY clause and COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also,the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 3. Or a query with ORDER BY clause and a COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also, the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. 4. Or a SELECT DISTINCT statement with COUNT COLUMN function, MIN/MAX aggregate function in the selection list. Also, the input of the COUNT COLUMN function, MIN/MAX aggregate function has FIELD PROC defined on it running in parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK71922) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036) COMMENT (***Action for PM39444: See PM39444 APAR/PTF text for additional information about why a REBIND is necessary. PM39444 corrects a problem of ABEND04E RC00E72018 at DSNXSTSE offset 0A9C may occur when a query contains a column function in the selection list and its result data type is a LOB running in parallel. To make this fix effective for a static application, it must be 1 rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK68830) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036) COMMENT (***Action for PM36118: See PM36118 APAR/PTF text for additional information about why a REBIND is necessary. PM36118 corrects a problem of ABEND0C4 RC00000011 DSNXRSGB offset 5E5C may occur when view has duplicate group by columns To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK75949 HOLD DATA END UK75956 HOLD DATA START UK75956 HOLD DATA END UK75960 HOLD DATA START UK75960 HOLD DATA END UK75989 HOLD DATA START UK75989 HOLD DATA END UK76053 HOLD DATA START ++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(DOC) DATE(12040) COMMENT (See PM47356 APAR/PTF text for additional information. This APAR/PTF modifies the DB2 Utility Guide and Reference and the Messages manual. The change will be documented in the DB2 Utility Guide and Reference and Messages, and in the Information Management Software for z/OS Solutions Information Center. The change is as follows. In the Utility Guide and Reference, under REORG TABLESPACE, Option descriptions, SORTDATA option: SORTDATA NO Specifies that the data is to be unloaded in the order of the clustering index. SORTDATA NO cannot be specified | with SHRLEVEL CHANGE or if the table space is in REORG- | PENDING. Specify SORTDATA NO if one of the following conditions is true: 1 * The data is in or near perfect clustering order, the | table space is not in REORP, and the REORG utility is used to reclaim space from dropped tables. * The data is very large, an insufficient amount of disk | space is available for sorting, and the table space is not in REORP. In the Messages manual, under DSNU messages: DSNU070I csect-name KEYWORD OR OPERAND x INVALID WITH y Explanation: The use of a keyword or operand is | inconsistent with another keyword, operand or condition. | x and y The keywords, operands or conditions that cannot be used together. System action: The control statement in error is rejected and processing is halted. User response: Correct the control statement in error and resubmit the job. | Problem determination: The REORG TABLESPACE | utility issues this message when the keywords, operands or | conditions are not allowed to be used in combination.). ++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(ACTION) DATE(12040) COMMENT (The PTF for APAR PM47356 has modified the REORG TABLESPACE utility to issue the following message and end with RC8 when REORG TABLESPACE SORTDATA NO is run against a non-Partition- By-Growth (non-PBG) partitioned table space in REORG-PENDING (REORP). A REORG TABLESPACE SORTDATA YES is required to remove the REORP state. MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH 'TABLE SPACE IN REORG PENDING'). UK76053 HOLD DATA END UK76071 HOLD DATA START UK76071 HOLD DATA END UK76083 HOLD DATA START UK76083 HOLD DATA END UK76086 HOLD DATA START UK76086 HOLD DATA END UK76093 HOLD DATA START UK76093 HOLD DATA END 1 UK76109 HOLD DATA START UK76109 HOLD DATA END UK76110 HOLD DATA START UK76110 HOLD DATA END UK76112 HOLD DATA START UK76112 HOLD DATA END UK76113 HOLD DATA START UK76113 HOLD DATA END UK76147 HOLD DATA START UK76147 HOLD DATA END UK76148 HOLD DATA START UK76148 HOLD DATA END UK76153 HOLD DATA START UK76153 HOLD DATA END UK76155 HOLD DATA START UK76155 HOLD DATA END UK76162 HOLD DATA START ++ HOLD(UK76162) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12044) COMMENT (***Action for PM49443: See PM49443 APAR/PTF text for additional information about why a REBIND is necessary. PM49443 allows LIKE predicates with the UPPER scalar function to become indexable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK73601) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12044) COMMENT (***Action for PM48939: See PM48939 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM48939 corrects a problem of incorrect output may occur when a pair-wise join query uses a multi-column index between dimension table and Fact table and there is a Fact table local predicate covered by the same multi-column index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK76162 HOLD DATA END UK76164 HOLD DATA START UK76164 HOLD DATA END UK76178 HOLD DATA START UK76178 HOLD DATA END UK76206 HOLD DATA START UK76206 HOLD DATA END UK76209 HOLD DATA START UK76209 HOLD DATA END UK76211 HOLD DATA START ++ HOLD(UK76211) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12045) COMMENT (A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM50592 corrects a performance problem when a pair-wise join plan is used for a short-running query with estimated elapsed time less than 0.5 second. In that case, the actual elapsed time may be over 0.5 sec. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK76211 HOLD DATA END UK76231 HOLD DATA START UK76231 HOLD DATA END UK76247 HOLD DATA START UK76247 HOLD DATA END UK76249 HOLD DATA START UK76249 HOLD DATA END 1 UK76251 HOLD DATA START UK76251 HOLD DATA END UK76309 HOLD DATA START ++ HOLD(UK76309) SYS FMID(HDBAA10) REASON(ACTION) DATE(12047) COMMENT (The PTF for APAR PM38329 has modified CSECTs in both the DSNUT101 and DSNLDTML load modules, affecting the utility batch and DB2 DDF address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DDF address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DDF address spaces, the problem the PTF addresses will not be resolved.). UK76309 HOLD DATA END UK76352 HOLD DATA START UK76352 HOLD DATA END UK76370 HOLD DATA START UK76370 HOLD DATA END UK76379 HOLD DATA START UK76379 HOLD DATA END UK76387 HOLD DATA START UK76387 HOLD DATA END UK76404 HOLD DATA START UK76404 HOLD DATA END UK76407 HOLD DATA START UK76407 HOLD DATA END UK76421 HOLD DATA START UK76421 HOLD DATA END UK76431 HOLD DATA START UK76431 HOLD DATA END 1 UK76439 HOLD DATA START ++ HOLD(UK73300) SYS FMID(HDBAA10) REASON(ACTION) DATE(12053) COMMENT (The ++HOLD and action is for DB2 users running in z/OS 1.12 or higher only. See PM46045 APAR/PTF text for additional information. The following summarizes the interactions of DB2 APARs PM17542, PM46045, and z/OS APARs OA36101, OA37361, and OA37362. It is intended to help you determine when to apply DB2 and z/OS APARs, and in what order. 1. PM17542 only - exposed to overlay and missing SMF I/O counting at address space level. MEMDSENQMGMT irrelevent. 2. PM17542 with OA36101 - exposed to missing SMF I/O counting at address space level only. MEMDSENQMGMT irrelevent. 3. PM17542 with OA36101, OA37361 & OA37362 - no longer exposed to either problem. 4. PM17542 with PM46045 - S99DASUP setting now only turned on when MEMDSENQMGMT is enabled. Exposed to overlay and missing SMF I/O counting at address space level ONLY when MEMDSENQMGMT is ENABLED. 5. PM17542 with PM46045 & OA36101 - S99DASUP setting now only turned on when MEMDSENQMGMT is enabled. Exposed to missing SMF I/O counting at address space level ONLY when MEMDSENQMGMT is ENABLED. 6. PM17542 with PM46045, OA36101, OA37361 & OA37362 - no longer exposed to either problem. Performance benefits for both features introduced with PM17542 only available when MEMDSENQMGMT is ENABLED. Instructions on setting MEMDSENQMGMT to DISABLE or ENABLE: ---------------------------------------------------------- Work with your system programmer to complete one of the following actions: - Update the ALLOCxx parmlib member to set the SYSTEM MEMDSENQMGMT value. SYSTEM MEMDSENQMGMT(DISABLE) or SYSTEM MEMDSENQMGMT(ENABLE) - Issue system command SETALLOC SETALLOC SYSTEM,MEMDSENQMGMT=DISABLE or SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE Note: 1. Updating the ALLOCxx parmlib is strongly recommended as it 1 remains effective across IPLs. You may apply the PTF and update the ALLOCxx parmlib member at different times. However the benefit of the APAR will only be available after re-IPL with ALLOCxx changes or after issuing the SETALLOC command as described above. 2. If SETALLOC SYSTEM,MEMDSENQMGMT command is used, a DB2 restart is required to make the change effective. 3. System command D ALLOC,OPTIONS can be used to display the status of MEMDSENQMGMT in z/OS. Sample DISPLAY output: IEFA003I 15.35.15 ALLOC OPTIONS SPACE PRIMARY: 4 SECONDARY: 24 : SYSTEM IEFBR14_DELMIGDS: LEGACY TAPELIB_PREF: EQUAL REMIND_INTV: 90 VERIFY_UNCAT: FAIL TEMPDSFORMAT: INCLUDELABEL MEMDSENQMGMT: ENABLE). UK76439 HOLD DATA END UK76444 HOLD DATA START UK76444 HOLD DATA END UK76445 HOLD DATA START UK76445 HOLD DATA END UK76455 HOLD DATA START ++ HOLD(UK76455) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM51073: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM51073 corrects a problem that incorrect output may be returned by a query if a NOT PADDED DPSI is used to return rows in order and a matching predicate of the index is a LIKE predicate matching on a column 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(UK71025) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM40235: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM40235 corrects a problem in which an unpredictable access path may be chosen when index-only access is possible. To make this fix effective for a static application, it must 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(UK71000) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM39849: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM39849 corrects a problem that DB2 may choose an inefficient access path while there exists an efficient index access path with screening 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.). UK76455 HOLD DATA END UK76457 HOLD DATA START ++ HOLD(UK76457) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM55976: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM55976 corrects a problem in which the most appropriate index only access may not be selected. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK75265) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM52549: See PM52549 APAR/PTF text for additional information about why a REBIND is necessary. PM52549 corrects a problem of SQLCODE=-510 when doing a BIND/REBIND on a FOR UPDATE cursor and IN-list direct table access is attempted. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change.). UK76457 HOLD DATA END UK76480 HOLD DATA START ++ HOLD(UK75592) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM53062: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM53062 corrects a problem that incorrect output may be returned by a query with GROUP BY clause and a set function with DISTINCT. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK70468) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059) COMMENT (***Action for PM38744: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM38744 corrects a problem of inaccurate cost estimation for an index on the inner table in a join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK76480 HOLD DATA END UK76482 HOLD DATA START ++ HOLD(UK63012) SYS FMID(HDBAA10) REASON(ACTION) DATE(12059) COMMENT (---------------------------------------------------------------- THE PM25093 CORRECTION APPLIED ON ONE DB2 DATA SHARING MEMBER IS NOT DEPENDENT ON ITS BEING APPLIED ON ALL OTHER DB2 DATA SHARING MEMBERS. HOWEVER, IF A SEQUENCE OBJECT IS SHARED BY APPLICATIONS ON MULTIPLE DB2 MEMBERS IN A DATA SHARING ENVIRONMENT, IT IS ADVISED THAT THE PTF OF APAR PM25093 SHOULD BE APPLIED ON ALL THE DB2 DATA SHARING MEMBERS WHERE THOSE APPLICATIONS WILL BE RUN. ----------------------------------------------------------------). UK76482 HOLD DATA END UK76516 HOLD DATA START UK76516 HOLD DATA END 1 UK76522 HOLD DATA START UK76522 HOLD DATA END UK76527 HOLD DATA START UK76527 HOLD DATA END UK76530 HOLD DATA START UK76530 HOLD DATA END UK76577 HOLD DATA START ++ HOLD(UK76577) SYS FMID(HDBAA10) REASON(ACTION) DATE(12058) COMMENT (Please note. If you are using DATE exits, this concerns you. If you are using a DATE exit, specifically an EBCDIC, ASCII, or UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make sure it is functioning properly. If it is, a query referencing the TIMESTAMP built-in function should work correctly and no action is necessary. If however the exit is not working properly and the query referencing the TIMESTAMP built-in function worked in DB2 9 but is now not working in DB2 10 (i.e. it does not return the expected result), then please ensure that the exit is coded and working properly.). UK76577 HOLD DATA END UK76578 HOLD DATA START ++ HOLD(UK76578) SYS FMID(HDBAA10) REASON(ACTION) DATE(12059) COMMENT (***Action for PM53818: This PTF corrects the problem where SQL scalar functions became unusable after running the DSNTIJEN job. If the DSNTIJEN job has not completed successfully, you should apply this PTF first before starting or continuing the DSNTIJEN job. If the DSNTIJEN job has already completed without this PTF, you can identify any affected SQL scalar functions by running the following query: SELECT R.SCHEMA ,R.NAME ,R.SPECIFICNAME FROM SYSIBM.SYSROUTINES AS R WHERE R.INLINE = 'Y' AND R.ORIGIN = 'Q' AND LENGTH(R.PARSETREE) = 0; Any rows returned from the above query identify the affected SQL scalar functions. You will need to drop and re-create them 1 to correct the problem. You do not need to run the query if the DSNTIJEN job has not been run or DB2 is running in CONVERSION mode, otherwise this query may return no rows or a negative SQLCODE.). UK76578 HOLD DATA END UK76589 HOLD DATA START ++ HOLD(UK76589) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12058) 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.). UK76589 HOLD DATA END UK76596 HOLD DATA START UK76596 HOLD DATA END UK76609 HOLD DATA START UK76609 HOLD DATA END UK76610 HOLD DATA START ++ HOLD(UK76610) SYS FMID(HDBAA10) REASON(ACTION) DATE(12062) COMMENT (***Action for PM54699 (V10) This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it for your DB2 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration.). UK76610 HOLD DATA END UK76631 HOLD DATA START 1UK76631 HOLD DATA END UK76636 HOLD DATA START UK76636 HOLD DATA END UK76642 HOLD DATA START UK76642 HOLD DATA END UK76643 HOLD DATA START UK76643 HOLD DATA END UK76645 HOLD DATA START UK76645 HOLD DATA END UK76650 HOLD DATA START ++ HOLD(UK76650) SYS FMID(HDBAA10) REASON(ACTION) DATE(12066) COMMENT (***Actions for PM52012 This PTF adds a new DB2 subsystem parameter in DSN6SPRM named REORG_LIST_PROCESSING that allows you to specify the default setting for the PARALLEL option of the DB2 REORG TABLESPACE utility. The PARALLEL option indicates whether REORG TABLESPACE will process all partitions specified in the input LISTDEF statement in a single utility execution (PARALLEL YES) or process each in a separate utility execution (PARALLEL NO). Valid options for DSN6SPRM.REORG_LIST_PROCESSING are: * PARALLEL: REORG TABLESPACE will assume PARALLEL YES when the PARALLEL keyword is not specified in the utility control statement. ==> This is the default setting * SERIAL : REORG TABLESPACE will assume PARALLEL NO when the PARALLEL keyword is not specified in the utility control 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 1 target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter REORG_LIST_PROCESSING=, where is PARALLEL or SERIAL, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding REORG_LIST_PROCESSING here, the value will be set to the default of PARALLEL 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 REORG_LIST_PROCESSING to the CLIST default input member, DSNTIDXA, 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: REORG_LIST_PROCESSING CHAR M NONE NONE Change to the value you specified for REORG_LIST_PROCESSING in step (2), above. If you do not add REORG_LIST_PROCESSING to a DSNTIDxx member, the DB2 installation CLIST will assume REORG_LIST_PROCESSING=PARALLEL when run with that member as input.). UK76650 HOLD DATA END UK76651 HOLD DATA START UK76651 HOLD DATA END 1UK76653 HOLD DATA START UK76653 HOLD DATA END UK76689 HOLD DATA START UK76689 HOLD DATA END UK76698 HOLD DATA START UK76698 HOLD DATA END UK76699 HOLD DATA START UK76699 HOLD DATA END UK76766 HOLD DATA START UK76766 HOLD DATA END UK76774 HOLD DATA START UK76774 HOLD DATA END UK76782 HOLD DATA START ++ HOLD(UK76782) SYS FMID(HDBAA10) REASON(DOC) DATE(12062) COMMENT (The "RACF Access Control Module Guide" (SC19-2982-01) is updated with the changes below. Chapter 14: RACF authorization checking reference - In "System privileges" section, a note is added for SYSDBADM. SYSDBADM XAPLPRIV value: DB2AAUTHU Privcode 287 (x'11F') The user must have sufficient authority to: One of these resources: In class: ------------------------------------------------------------ DB2-subsystem.SYSDBADM MDSNSM or GDSNSM DB2-subsystem.SYSCTRL DSNADM DB2-subsystem.SYSADM DSNADM Note: DB2® turns on bit 7 of the XAPLFLG1 field for a user table that includes user defined data type or user defined function. If this bit is on, the RACF® access control module bypasses checking for the SYSCTRL authority.). UK76782 HOLD DATA END UK76785 HOLD DATA START 1UK76785 HOLD DATA END UK76802 HOLD DATA START ++ HOLD(UK76802) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12069) COMMENT (***Action for PM57388: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM57388 corrects a problem in which DB2 does not properly determine the sorted order of the data for a query. This can result in incorrect output and/or 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.). UK76802 HOLD DATA END UK76803 HOLD DATA START UK76803 HOLD DATA END UK76806 HOLD DATA START ++ HOLD(UK76806) SYS FMID(HDBAA10) REASON(ACTION) DATE(12065) COMMENT (***Action for PM54662 (V10): This PTF adds an online-changeable subsystem parameter in DSN6FAC called DDF_COMPATIBILITY that can be used to specify whether DDF returns stored procedure parameters according to their declared types (V10 behavior) or according to the types of the arguments specified in the CALL statement (pre-V10 behavior). Valid settings for DDF_COMPATIBILITY are: * null : V10 behavior is maintained. DDF returns stored procedure parameters according their declared types. ==> This is the default setting * SP_PARMS_NJV: Pre-V10 behavior is used for stored procedure CALLs from IBM Data Server for non-Java clients, Version 9.* and below. DDF converts the data from a stored procedure's declared SQL type to the argument type specified in the CALL statement. 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 ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add either the keyword parameter 'DDF_COMPATIBILITY=,' or 'DDF_COMPATIBILITY=SP_PARMS_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 adds an entry for DDF_COMPATIBILITY to the CLIST default input members in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: DDF_COMPATIBILITY CHARR M NONE NONE Change to SP_PARMS_NJV if you specified 'DDF_COMPATIBILITY=SP_PARMS_NJV,' in step (2), above. Otherwise, change to NULL 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.). UK76806 HOLD DATA END UK76808 HOLD DATA START UK76808 HOLD DATA END 1UK76814 HOLD DATA START UK76814 HOLD DATA END UK76819 HOLD DATA START ++ HOLD(UK76819) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12065) COMMENT (***Action for PM55938: See PM55938 APAR/PTF text for additional information about why a REBIND is necessary. PM55938 corrects a problem of choosing an inefficient access path instead of a DPSI index access path for a query with an EXISTS subquery. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK76819 HOLD DATA END UK76827 HOLD DATA START UK76827 HOLD DATA END UK76834 HOLD DATA START UK76834 HOLD DATA END UK76844 HOLD DATA START UK76844 HOLD DATA END UK76845 HOLD DATA START UK76845 HOLD DATA END UK76846 HOLD DATA START UK76846 HOLD DATA END UK76847 HOLD DATA START UK76847 HOLD DATA END UK76862 HOLD DATA START UK76862 HOLD DATA END UK76865 HOLD DATA START UK76865 HOLD DATA END UK76867 HOLD DATA START 1UK76867 HOLD DATA END UK76870 HOLD DATA START UK76870 HOLD DATA END UK76912 HOLD DATA START ++ HOLD(UK75700) SYS FMID(HDBAA10) REASON(DOC) DATE(12068) COMMENT (***Documentation for PM52087: Please see the PTF cover letter for more information. This APAR/PTF changes the description for DB2 reason code 00D31030. The change will be documented in the DB2 for z/OS Codes manual and in the Information Management Software for z/OS Solutions Information Center. The explanation for DB2 reason code '00D31030'X is updated to include the following new bullet item: . The SYSMODENAME column in the SYSIBM.LUNAMES table in the communications database (CDB) is greater than 8 bytes.). UK76912 HOLD DATA END UK76936 HOLD DATA START ++ HOLD(UK76936) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12073) COMMENT (***Action for PM57492: See PM57492 APAR/PTF text for additional information about why a REBIND is necessary. PM57492 corrects an incorrect output problem where the join predicate involves graphic data and there is a derived predicate for inner table of a sort merge join. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK76936 HOLD DATA END UK76938 HOLD DATA START UK76938 HOLD DATA END UK76959 HOLD DATA START UK76959 HOLD DATA END UK76961 HOLD DATA START UK76961 HOLD DATA END 1UK76994 HOLD DATA START UK76994 HOLD DATA END UK76996 HOLD DATA START UK76996 HOLD DATA END UK76997 HOLD DATA START UK76997 HOLD DATA END UK76999 HOLD DATA START UK76999 HOLD DATA END UK77001 HOLD DATA START UK77001 HOLD DATA END UK77003 HOLD DATA START ++ HOLD(UK77003) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12072) COMMENT (***Action for PM55479: See PM55479 APAR/PTF text for additional information about why a REBIND is necessary. PM55479 corrects a problem that DB2 incorrectly handles the length of histogram statistics of a DECIMAL column. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK74866) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12072) COMMENT (***Action for PM50516: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM50516 corrects a problem in which an incorrect compound filter factor is computed when there is data skew and that data skew is represented by frequency statistics. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK77003 HOLD DATA END UK77005 HOLD DATA START UK77005 HOLD DATA END 1 UK77007 HOLD DATA START UK77007 HOLD DATA END UK77031 HOLD DATA START UK77031 HOLD DATA END UK77038 HOLD DATA START ++ HOLD(UK76315) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076) COMMENT (***Action for PM54955: See PM54955 APAR/PTF text for additional information about why a REBIND is necessary. PM54955 corrects a problem of incorrect output for a query that references a scalar fullselect in its predicate 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.). ++ HOLD(UK77038) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076) COMMENT (***Action for PM54034: See PM54034 APAR/PTF text for additional information about why a REBIND is necessary. PM54034 corrects a problem of incorrect output for an SQL statement that references to an SQL inline table user defined function multiple times with different arguments and the SQL inline table user defined function contains a common table expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK65976) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076) COMMENT (***Action for PM30064: See PM30064 APAR/PTF text for additional information about why a REBIND is necessary. PM30064 made an performance enhancement for a query satisfying all of the following conditions: 1. The query contains host variables or parameter markers. 2. The query references a view or table expression which contains UNION ALL and returns a LOB column. 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(UK76977) SYS FMID(HDBAA10) REASON(ACTION) DATE(12076) COMMENT (After application of the PTF, the data length calculated of CONCAT() function may be less than its previous DESCRIBE when all of the following conditions are satisfied: 1. the type of one parameter of CONCAT() is GRAPHIC; 2. the other parameter of CONCAT() is scalar full-select, whose type is also GRAPHIC. Since there is no data in the extra length of CONCAT() prior to applying this APAR, no problem would be caused after this APAR is applied. If applications using DESCRIBE is impacted, proper actions should be taken. 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 data length of the CONCAT() function with scalar full-select from the previous control statement. Proper action should be taken if such mismatch is observed.). UK77038 HOLD DATA END UK77041 HOLD DATA START UK77041 HOLD DATA END UK77085 HOLD DATA START UK77085 HOLD DATA END UK77096 HOLD DATA START UK77096 HOLD DATA END UK77101 HOLD DATA START UK77101 HOLD DATA END UK77102 HOLD DATA START UK77102 HOLD DATA END UK77107 HOLD DATA START UK77107 HOLD DATA END UK77111 HOLD DATA START UK77111 HOLD DATA END 1UK77113 HOLD DATA START UK77113 HOLD DATA END UK77157 HOLD DATA START UK77157 HOLD DATA END UK77170 HOLD DATA START ++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12079) COMMENT (See PM40724 APAR/PTF text for additional information about why a REBIND is necessary. APAR PM38326 is the necessary pre-conditioning apar for this APAR. PM40724 corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(12079) COMMENT (PM40724 is an APAR that includes changes to support functional extensions to the existing built-in functions and to introduce a new built-in function that will be enabled once this APAR is applied in DB2 NFM (New Function Mode). Earlier, pre-conditioning APAR PM38326 was delivered. In a data sharing group, the pre-conditioning APAR should be applied to all members before applying this enabling APAR to any member. The code change is enabled once this enabling APAR is applied. The functional extensions to the following existing built-in functions are enabled by APAR PM40724. 1. LTRIM 2. RTRIM 3. REPLACE 4. ROUND 5. STRIP 6. TRUNCATE The new built-in function called, TRIM, is introduced by APAR PM40724. This APAR also corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character.). ++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(DOC) DATE(12079) COMMENT (See PM40724 APAR/PTF text for additional information. PM40724 introduces the following changes to externals: 1 LTRIM The LTRIM function removes bytes from the beginning of a string expression based on the content of a trim expression. >>--LTRIM--(--string-expression---+--------------------+-)->< '-,--trim-expression-' The LTRIM function removes all of the characters that are contained in trim-expression from the beginning of string-expression. The search is done by comparing the binary representation of each character (which consists of one or more bytes) in trim-expression to the bytes at the beginning of string-expression. If the string-expression is defined as FOR BIT DATA, the search is done by comparing each byte in trim-expression to the byte at the beginning of string-expression. string-expression An expression that specifies the source string. The argument must be an expression that returns a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. If string-expression is not FOR BIT DATA, trim-expression must not be FOR BIT DATA. trim-expression An expression that specifies the characters to remove from the beginning of string-expression. The expression must return a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. The default for trim-expression depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. Otherwise, a single byte blank. For EBCDIC, X'40' represents 1 a blank. If not EBCDIC, X'20' represents a blank. string-expression and trim-expression must have compatible data types. If string-expression and trim-expression have different CCSID sets, trim-expression is converted to the CCSID of string-expression. The result of the function depends on the data type of string-expression. VARCHAR if string-expression is a character string. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. VARGRAPHIC if string-expression is a graphic string. VARBINARY if string-expression is a binary string. The length attribute of the result is the same as the length attribute of string-expression. The actual length of the result for a character or binary string is the length of string-expression minus the number of bytes that are removed. The actual length of the result for a graphic string is the length (in the number of double byte characters) of string-expression minus the number of double byte characters removed. If all of the characters are removed, the result is an empty string (the length is zero). If any argument can be null, the result can be null; if any argument is null, the result is the null value. The CCSID of the result is the same as that of string-expression Refer to LTRIM section in the DB2 10 for z/OS SQL Reference for more information. RTRIM The RTRIM function removes bytes from the end of a string expression based on the content of a trim expression. >>--RTRIM--(--string-expression---+--------------------+-)->< '-,--trim-expression-' The RTRIM function removes all of the characters contained in trim-expression from the end of string-expression. The search is done by comparing the binary representation of each character (which consists of one or more bytes) in trim-expression to the bytes at the end of string-expression. If the string-expression is defined as FOR BIT DATA, the search is done by comparing each byte in trim-expression to the byte at the end of string-expression. 1 string-expression An expression that specifies the source string. The argument must be an expression that returns a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. If string-expression is not FOR BIT DATA, trim-expression must not be FOR BIT DATA. trim-expression An expression that specifies the characters to remove from the end of string-expression. The expression must return a value that is a built-in string data type that is not a LOB, or a numeric data type. If the value is not a string data type, it is implicitly cast to VARCHAR before the function is evaluated. The default for trim-expression depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. Otherwise, a single byte blank. For EBCDIC, X'40' represents a blank. When not EBCDIC, X'20' represents a blank. string-expression and trim-expression must have compatible data types. If string-expression and trim-expression have different CCSID sets, trim-expression is converted to the CCSID of string-expression. The result of the function depends on the data type of string-expression. VARCHAR if string-expression is a character string. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. VARGRAPHIC if string-expression is a graphic string. VARBINARY if string-expression is a binary string. The length attribute of the result is the same as the length attribute of string-expression. 1 The actual length of the result for a character or binary string is the length of string-expression minus the number of bytes removed. The actual length of the result for a graphic string is the length (in number of double byte characters) of string-expression minus the number of double byte characters removed. If all of the characters are removed, the result is an empty string (the length is zero). If any argument can be null, the result can be null; if any argument is null, the result is the null value. The CCSID of the result is the same as that of string-expression Refer to RTRIM section in the DB2 10 for z/OS SQL Reference for more information. REPLACE >>-REPLACE-(-source-string-,-search-string-+-----------------+-> ',-replace-string-' >-)->< replace-string An expression that specifies the replacement string. The expression must return a value that is a built-in character string, graphic string, or binary string data type that is not a LOB. The argument can also be a numeric data type. The numeric argument is implicitly cast to a VARCHAR data type. If replace-string is not specified or is an empty string, nothing replaces the string that is removed from the source string. Refer to REPLACE section in the DB2 10 for z/OS SQL Reference for more information. ROUND .-,--0-------------------. >>-ROUND-(--numeric-expression-1-+------------------------+-)->< '-,-numeric-expression-2-' Refer to ROUND section in the DB2 10 for z/OS SQL Reference for more information. TRUNCATE or TRUNC .-,--0------------------. >>-+TRUNCATE-+-(-numeric-expression1-+-----------------------+-> '-TRUNC---' '-,-numeric-expression2-' 1 >-)->< Refer to TRUNCATE section in the DB2 10 for z/OS SQL Reference for more information. STRIP The STRIP function is similar to the TRIM scalar function. Refer to TRIM section in the DB2 10 for z/OS SQL Reference for more information. TRIM The TRIM function removes bytes from the beginning, from the end, or from both the beginning and end of a string expression. >>--TRIM--(--+----------------------------------------+--> | .-BOTH-----. | '-+----------+--+----------------+--FROM-' |-B--------| '-trim-constant--' |-LEADING--| |-L--------| |-TRAILING-| '-T--------' >--string-expression---)-------------------------------->< The schema is SYSIBM. The first argument, if specified, indicates whether characters are removed from the end or the beginning of the string. If the first argument is not specified, the characters are removed from both the end and the beginning of the string. trim-constant Specifies a constant that indicates the binary, SBCS, or DBCS character that is to be removed. If string-expression is a character string, trim-constant must be an SBCS or DBCS single-character (2 bytes) constant. If string-expression is a binary string, trim-constant must be a single-byte binary string constant. If string-expression is a DBCS graphic or DBCS-only string, trim-constant must be a graphic constant that consists of a single DBCS character. The default for trim-constant depends on the data type of string-expression: A DBCS blank if string-expression is a DBCS graphic string. For ASCII, the CCSID determines the hex value that represents a DBCS blank. For example, for Japanese (CCSID 301), X'8140' represents a DBCS while for 1 Simplified Chinese, X'A1A1' represents a DBCS blank. For EBCDIC, X'4040' represents a DBCS blank. A UTF-16 or UCS-2 blank (X'0020') if string-expression is a Unicode graphic string. A value of X'00' if string-expression is a binary string. Otherwise, a single byte blank. For EBCDIC, X'40' represents a blank. When not EBCDIC, X'20' represents a blank. string-expression An expression that returns a value that is a built-in character string data type, graphic data type, binary string data type, or numeric data type. string-expression must not be a LOB. If string-expression is numeric, it is cast to a character string before the function is evaluated. For more information about converting numeric to a character string, see VARCHAR. string-expression and trim-expression must have compatible data types. The data type of the result depends on the data type of string-expression: If string-expression is a character string data type, the result is VARCHAR. If string-expression is defined as FOR BIT DATA the result is FOR BIT DATA. If string-expression is a graphic string data type, the result is VARGRAPHIC. If string-expression is a binary string data type, the result is VARBINARY. The length attribute of the result is the same as the length attribute string-expression. The actual length of the result is the length of string-expression minus the number of characters removed. If all of the characters are removed, the result is an empty string. If string-expression can be null, the result can be null; if string-expression is null, the result is the null value. The CCSID of the result is the same as that of string-expression Example: Assume the host variable HELLO of type CHAR(9) has a value of 'Hello '. SELECT TRIM(:HELLO), TRIM(TRAILING FROM :HELLO) FROM SYSIBM.SYSDUMMY1 Results in 'Hello' and ' Hello' respectively. 1 Example: Assume the host variable BALANCE of type CHAR(9) has a value of '000345.50'. SELECT TRIM(L '0' FROM :BALANCE) FROM SYSIBM.SYSDUMMY1 Results in '345.50' Refer to TRIM section in the DB2 10 for z/OS SQL Reference.). ++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(ACTION) DATE(12079) COMMENT (This PTF corrects the problem of an SQLCODE -171 issued for a query that references the STRIP built-in function containing a single multi-byte mixed data strip-character. If after applying both apars PM38326 and PM40724, the failing query still returns an SQLCODE -171 or for a static query a rebind does not resolve the problem, one or more of the following actions may need to be performed depending on the makeup of the query. 1. Views. Regenerate views using the ALTER VIEW REGENERATE statement. 2. Materialized query tables (MQT). Drop and recreate the MQTs. 3. SQL table UDFs. Drop and recreate the UDFs. 4. SQL scalar UDFs. Regenerate functions using the ALTER FUNCTION REGENERATE. statement. 5. SQL native procedures. Regenerate procedures using the ALTER PROCEDURE REGENERATE statement. 6. Row permissions and column masks. Regenerate using the ALTER PERMISSION REGENERATE or ALTER MASK REGENERATE statement. 7. Indexes with key expressions. Regenerate indexes using the ALTER INDEX REGENERATE statement.). UK77170 HOLD DATA END UK77195 HOLD DATA START 1UK77195 HOLD DATA END UK77197 HOLD DATA START UK77197 HOLD DATA END UK77206 HOLD DATA START UK77206 HOLD DATA END UK77229 HOLD DATA START UK77229 HOLD DATA END UK77248 HOLD DATA START ++ HOLD(UK77248) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12085) COMMENT (***Action for PM56084: See PM56084 APAR/PTF text for additional information about why a REBIND is necessary. Please note that the second problem addressed by PM56084 is required to have the static application rebound. Incorrect output can occur when a not NULL XML column is fetched. DB2 does not set the nullability information properly at bind time which leads to an incorrect value written for the NULL byte when retrieving a not NULL XML column for the JCC Type 2 Driver with Limited Block Fetch. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK69995) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12085) COMMENT (***Action for PM38688: See PM38688 APAR/PTF text for additional information about why a REBIND is necessary. PM38688 corrects a problem of incorrect out when query contains EXCEPT and UNION To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK77248 HOLD DATA END UK77249 HOLD DATA START 1UK77249 HOLD DATA END UK77338 HOLD DATA START UK77338 HOLD DATA END UK77339 HOLD DATA START UK77339 HOLD DATA END UK77366 HOLD DATA START UK77366 HOLD DATA END UK77367 HOLD DATA START UK77367 HOLD DATA END UK77376 HOLD DATA START UK77376 HOLD DATA END UK77380 HOLD DATA START UK77380 HOLD DATA END UK77407 HOLD DATA START UK77407 HOLD DATA END UK77410 HOLD DATA START UK77410 HOLD DATA END UK77426 HOLD DATA START ++ HOLD(UK77426) SYS FMID(HDBAA10) REASON(ACTION) DATE(12087) COMMENT (***Action for PM57630: PM57630 corrects a problem where SQLCODE -331 is issued incorrectly when translating characters from CCSID 367 to CCSID 937. DB2 code has been changed to invoke Unicode services instead of the conversion procedure DSNXVTWC when translating characters from CCSID 367 to CCSID 937. DB2 code will ignore the row for this translation in SYSIBM.SYSSTRINGS. After applying this PTF the following three characters will be translated differently. SM060000 Ý '5B'x SM080000 ¨ '5D'x SD150000 ¬ '5E'x 1 Prior to applying this PTF, the DSNXVWTC proc is called and the characters '5B'x, '5D'x, and '5E'x are translated to '4A'x, '6A'x, and '5F'x respectively. After applying this PTF, Unicode services is called and the characters '5B'x, '5D'x, and '5E'x are translated to 'BA'x, 'BB'x, and 'B0'x respectively. All other characters are translated the same by DSNXVTWC and Unicode services. The following is a table to help illustrate the changes: ----------------------------------------------------------- |GCGID |character| CCSID | CCSID 937 | CCSID 937 | | | | 367 | (by DSNXVWTC) | by UCS | ----------------------------------------------------------- |SM060000 | Ý | '5B'x | '4A'x |'BA'x | ----------------------------------------------------------- |SM080000 | ¨ | '5D'x | '6A'x |'BB'x | ----------------------------------------------------------- |SD150000 | ¬ | '5E'x | '5F'x |'B0'x | ----------------------------------------------------------- If you have any applications that depend on these translated values they may need to be modified to handle the correct values. See PM57630 APAR/PTF text for additional information.). UK77426 HOLD DATA END UK77430 HOLD DATA START UK77430 HOLD DATA END UK77451 HOLD DATA START UK77451 HOLD DATA END UK77481 HOLD DATA START ++ HOLD(UK77481) SYS FMID(HIZAA10) REASON(ACTION) DATE(12090) 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.). UK77481 HOLD DATA END UK77500 HOLD DATA START 1++ HOLD(UK77500) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12090) COMMENT (***Action for PM56845: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM56845 allows you to specify whether, for queries that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access paths that require sort when there exists at least one access path that avoids sort. To make this fix effective for a static application, it must 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(UK77500) SYS FMID(HDBAA10) REASON(ACTION) DATE(12090) COMMENT (***Action for PM56845: This PTF adds a new DB2 subsystem parameter in DSN6SPRM named OPT1ROWBLOCKSORT that allows you to specify whether, for queries that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access paths that require sort when there exists at least one access path that avoids sort. Valid options are: * ENABLE : When OPTIMIZE FOR 1 ROW is used with a query, DB2 will disable sort access paths when a no-sort choice is available. * DISABLE: DB2 will strongly discourage sort access paths and is unlikely to choose sort access paths, but there will be a chance a sort access path can win. This is the behavior which was present in DB2 9 and prior releases. ==> This is the default setting If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is 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. 1 ---------------------------------------------------------------- (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 OPT1ROWBLOCKSORT=, where is DISABLE or ENABLE, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding OPT1ROWBLOCKSORT here, the value will be set to the default of DISABLE when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF adds an entry for OPT1ROWBLOCKSORT to the CLIST default input member, DSNTIDXA, 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: OPT1ROWBLOCKSORT CHAR G DISABLE ENABLE Change to the value you specified for OPT1ROWBLOCKSORT in step (2), above. If you do not add OPT1ROWBLOCKSORT to a DSNTIDxx member, the DB2 installation CLIST will assume OPT1ROWBLOCKSORT=DISABLE when run with that member as input.). UK77500 HOLD DATA END UK77506 HOLD DATA START UK77506 HOLD DATA END UK77518 HOLD DATA START UK77518 HOLD DATA END UK77548 HOLD DATA START UK77548 HOLD DATA END 1 UK77556 HOLD DATA START UK77556 HOLD DATA END UK77572 HOLD DATA START UK77572 HOLD DATA END UK77584 HOLD DATA START UK77584 HOLD DATA END UK77633 HOLD DATA START UK77633 HOLD DATA END UK77636 HOLD DATA START UK77636 HOLD DATA END UK77652 HOLD DATA START UK77652 HOLD DATA END UK77666 HOLD DATA START UK77666 HOLD DATA END UK77693 HOLD DATA START ++ HOLD(UK74927) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12095) COMMENT (See PM52694 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM52694 fixes a query costing problem when the query has outer join and FETCH FIRST n ROWS ONLY or OPTIMIZE FOR n ROWS. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK77693 HOLD DATA END UK77699 HOLD DATA START UK77699 HOLD DATA END UK77733 HOLD DATA START UK77733 HOLD DATA END UK77737 HOLD DATA START UK77737 HOLD DATA END 1 UK77739 HOLD DATA START UK77739 HOLD DATA END UK77743 HOLD DATA START ++ HOLD(UK77743) SYS FMID(HDBAA10) REASON(ACTION) DATE(12100) COMMENT (The PTF for APAR PM59401 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.). UK77743 HOLD DATA END UK77745 HOLD DATA START ++ HOLD(UK77745) SYS FMID(HDBAA10) REASON(ACTION) DATE(12102) COMMENT (*** Action for PM59280 *** This fix corrects a SQLCODE104 symptom observed at the server site (site2), but to correct the problem this fix must be applied to the DB2 for z/OS requester site (site1) where alias resolution is enabled. Review the PTF cover letter for further explanation of the requester (site1) applications that are affected.). UK77745 HOLD DATA END UK77769 HOLD DATA START UK77769 HOLD DATA END UK77778 HOLD DATA START UK77778 HOLD DATA END UK77822 HOLD DATA START UK77822 HOLD DATA END UK77835 HOLD DATA START UK77835 HOLD DATA END UK77843 HOLD DATA START 1++ HOLD(UK77843) SYS FMID(HDBAA10) REASON(ACTION) DATE(12101) COMMENT (***Action for PM56690: See PM56690 APAR/PTF text for additional information. PM56690 changes the output in SYSREC for UNLOAD DATE column to TIMESTAMP EXTERNAL with no length specified from 19 byte timestamp to 26 byte timestamp; with length specified equal to 26, the output is changed from 19 byte timestamp plus 7 padding blanks to 26 byte timestamp. New applications or procedures developed on DB2 10 for z/OS using the UNLOAD output may be affected by this modification and may need to be changed accordingly.). UK77843 HOLD DATA END UK77844 HOLD DATA START UK77844 HOLD DATA END UK77857 HOLD DATA START UK77857 HOLD DATA END UK77877 HOLD DATA START UK77877 HOLD DATA END UK77885 HOLD DATA START UK77885 HOLD DATA END UK77887 HOLD DATA START UK77887 HOLD DATA END UK77907 HOLD DATA START UK77907 HOLD DATA END UK77919 HOLD DATA START ++ HOLD(UK76492) SYS FMID(HDBAA10) REASON(ACTION) DATE(12103) COMMENT (APAR PM54727 has corrected an issue where REORG REBALANCE on a partitioned table space with an editproc defined can result in corrupted limit key values in the DB2 catalog and directory. In the event that the above limit key corruption has occurred, user can repair the catalog/directory by manually altering the limit keys to the correct value on the affected table space / partitions, and then run a REORG TABLESPACE utility to remove the restrictive REORP status.). UK77919 HOLD DATA END 1 UK77920 HOLD DATA START ++ HOLD(UK77920) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12104) COMMENT (***Action for PM52237 See PM52237 APAR/PTF text for additional information about why a REBIND is necessary. Apar PM52237 reduces the XML storage usage so as not to exceed the specified zparm limit. As a result, this will reduce the chance of receiving an SQLCODE904 (or SQLCODE -904), a Resource Unavailable condition with reason code rc00D50001 or rc00D50002, which means excessive storage used for XMLTABLE. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK77920 HOLD DATA END UK77942 HOLD DATA START UK77942 HOLD DATA END UK77953 HOLD DATA START UK77953 HOLD DATA END UK77956 HOLD DATA START UK77956 HOLD DATA END UK77963 HOLD DATA START UK77963 HOLD DATA END UK77992 HOLD DATA START UK77992 HOLD DATA END UK77996 HOLD DATA START UK77996 HOLD DATA END UK77997 HOLD DATA START ++ HOLD(UK77997) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12111) COMMENT (***Action for PM57745: See PM57745 APAR/PTF text for additional information about why a REBIND is necessary. PM57745 corrects a problem that storage overlay could happen for an SQL statement that returns data in the type of DBCLOB. 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.). UK77997 HOLD DATA END UK78003 HOLD DATA START UK78003 HOLD DATA END UK78004 HOLD DATA START ++ HOLD(UK78004) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107) 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(12107) 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(12107) 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 1 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.). ++ HOLD(UK65223) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107) 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.). UK78004 HOLD DATA END UK78007 HOLD DATA START UK78007 HOLD DATA END UK78030 HOLD DATA START UK78030 HOLD DATA END UK78100 HOLD DATA START UK78100 HOLD DATA END UK78109 HOLD DATA START UK78109 HOLD DATA END UK78112 HOLD DATA START UK78112 HOLD DATA END UK78130 HOLD DATA START UK78130 HOLD DATA END UK78134 HOLD DATA START UK78134 HOLD DATA END UK78166 HOLD DATA START UK78166 HOLD DATA END UK78170 HOLD DATA START 1++ HOLD(UK76577) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111) COMMENT (Please note. If you are using DATE exits, this concerns you. If you are using a DATE exit, specifically an EBCDIC, ASCII, or UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make sure it is functioning properly. If it is, a query referencing the TIMESTAMP built-in function should work correctly and no action is necessary. If however the exit is not working properly and the query referencing the TIMESTAMP built-in function worked in DB2 9 but is now not working in DB2 10 (i.e. it does not return the expected result), then please ensure that the exit is coded and working properly.). ++ HOLD(UK74371) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111) COMMENT (The following behavior difference may be noticed with the application of this apar. Please note that this apar corrects an instance where an incorrect SQLCODE180 could be issued. Instead, an SQLCODE181 should be issued. So, any static applications that check for an SQLCODE180 (or -180) should also be checking for an SQLCODE181 (or -181).). UK78170 HOLD DATA END UK78176 HOLD DATA START ++ HOLD(UK78176) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111) COMMENT (Applying this apar will not fix the package which is already broken. The customer can run the following query to find all native stored procedures and ALTER REGENERATE these procedures can correct the broken package. SELECT * FROM SYSIBM.SYSPACKAGE WHERE PLANMGMT NOT IN ('E','B') AND APREUSE NOT IN ('N',' ') AND (TYPE='N' OR TYPE='F')). UK78176 HOLD DATA END UK78180 HOLD DATA START ++ HOLD(UK78180) SYS FMID(HDBAA10) REASON(DOC) DATE(12117) COMMENT (PM58294 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference: Changed option for utility REORG: DISCARD Specifies that records that meet the specified WHEN conditions are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD statement in the JCL, discarded records are saved in the | associated data set. Otherwise, the utility discards records | without saving them in a data set. You can specify any SHRLEVEL option with DISCARD; however, if you specify SHRLEVEL CHANGE, modifications that are made 1 during the reorganization to data rows that match the discard criteria are not permitted. In this case, REORG TABLESPACE terminates with an error. If you specify DISCARD, rows are decompressed and edit routines are decoded. If you also specify DISCARD to a file, rows are decoded by field procedure, and the following columns are converted to DB2 external format: (1)SMALLINT (2)INTEGER (3)FLOAT (4)DECIMAL (5)TIME (6)TIMESTAMP Otherwise, edit routines or field procedures are bypassed on both the UNLOAD and RELOAD phases for table spaces. Validation procedures are not invoked during either phase. Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY option. | You cannot specify DISCARD for a base table with LOB columns | unless the discard records are less than 32k or you want to | discard records without saving them in a data set. You cannot specify DISCARD for a base table with XML columns or for an XML table space. REORG TABLESPACE DISCARD cannot be specified on a system-maintained temporal table space when versioning is active. When versioning is active and DISCARD is specified, REORG TABLESPACE fails with message DSNU076I and return code 8.). ++ HOLD(UK78180) SYS FMID(HDBAA10) REASON(ACTION) DATE(12117) COMMENT (The PTF for APAR PM58294 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved.). UK78180 HOLD DATA END UK78202 HOLD DATA START UK78202 HOLD DATA END UK78206 HOLD DATA START 1UK78206 HOLD DATA END UK78211 HOLD DATA START UK78211 HOLD DATA END UK78230 HOLD DATA START ++ HOLD(UK78230) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12115) COMMENT (The PTF for PM60499 is a companion fix and requires the fix for APAR PM55051 for FMID HDBAA10 to be applied.). UK78230 HOLD DATA END UK78235 HOLD DATA START UK78235 HOLD DATA END UK78247 HOLD DATA START UK78247 HOLD DATA END UK78277 HOLD DATA START UK78277 HOLD DATA END UK78286 HOLD DATA START UK78286 HOLD DATA END UK78307 HOLD DATA START UK78307 HOLD DATA END UK78358 HOLD DATA START UK78358 HOLD DATA END UK78390 HOLD DATA START UK78390 HOLD DATA END UK78404 HOLD DATA START UK78404 HOLD DATA END UK78406 HOLD DATA START UK78406 HOLD DATA END UK78414 HOLD DATA START UK78414 HOLD DATA END UK78418 HOLD DATA START 1++ HOLD(UK78418) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12122) COMMENT (***Action for PM58322: See PM58322 APAR/PTF text for additional information about why a REBIND is necessary. PM58322 corrects a problem of missing a negative SQLCODE on the insert or delete operation in the statements such as INSERT, DELETE, MERGE, or SELECT FROM those where the object table references a view and the view definition references a DB2 directory table such as SYSLGRNX. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK78418 HOLD DATA END UK78426 HOLD DATA START UK78426 HOLD DATA END UK78449 HOLD DATA START UK78449 HOLD DATA END UK78472 HOLD DATA START UK78472 HOLD DATA END UK78476 HOLD DATA START UK78476 HOLD DATA END UK78514 HOLD DATA START ++ HOLD(UK78514) SYS FMID(HDBAA10) REASON(ACTION) DATE(12125) COMMENT (***Action for PM53243 (V10): For users who are interested in exploiting the functions provided via this PTF, the following actions need to be considered: * For a CALL statement to a DB2 for z/OS Stored Procedure, the Stored Procedure name can be identified via a literal or by using a host variable or parameter marker. When using a literal for the stored procedure name, and in order to benefit from the enhancement that provides a valid routine ID in various IFCID records, the packages that contain the CALL statement must be rebound after this PTF is applied. * For an SQL statement that invokes a DB2 for z/OS User-Defined Function, and in order to benefit from the enhancement to provide a valid routine ID in various IFCID records, the packages that contain the SQL statement must be rebound after this PTF is applied. 1 * The mapping of IFCID233 remains compatible with prior versions and no immediate change is required. However, applications that parse this record will need to be changed in order to exploit the new fields.). UK78514 HOLD DATA END UK78526 HOLD DATA START ++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(12125) 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.). UK78526 HOLD DATA END UK78529 HOLD DATA START ++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(12126) 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.). UK78529 HOLD DATA END UK78575 HOLD DATA START UK78575 HOLD DATA END UK78581 HOLD DATA START ++ HOLD(UK75209) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129) COMMENT (***Action for PM51654: 1 See PM51654 APAR/PTF text for additional information about why a REBIND is necessary. PM51654 corrects a problem when incorrect output could happen for a complex SQL statement or view with an outer join and a correlated sub-query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK73620) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129) COMMENT (***Action for PM47058: See PM47058 APAR/PTF text for additional information about why a REBIND is necessary. PM47058 corrects a problem of incorrect output when an SQL statement satisfies all of the following conditions: 1. table expression with sideway reference is defined in this SQL statement; 2. LEFT OUTER JOIN is involved in this SQL statement; 3. CPU parallelism setting is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK71528) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129) COMMENT (***Action for PM41296: See PM41296 APAR/PTF text for additional information about why a REBIND is necessary. PM41296 corrects a problem of an SQL statement which defines a table expression one the preserved side of LEFT OUTER JOIN, and a CASE statement or non-column expression is defined in the SELECT list of the table expression and is referenced in the SQL statement. Performance may regress when a SQL statement satisfies all of the following conditions: 1. OUTER JOIN is contained, and the preserved side is defined with table expression; 2. a CASE statement or non-column expression is defined in the SELECT list of the above table expression; 3. a table expression column which corresponds to the CASE statement or non-column expression from condition #2 is referenced in predicate of the SQL statement. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK78581) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(12129) COMMENT (***Action for PM55928: PM55928 is a pre-conditioning APAR that includes changes to support a new function that will be enabled via another APAR PM56631. At this time, all of the changes are transparent to the user. In a data sharing group, this pre-conditioning APAR should be applied to all members before the later enabling APAR PM56631 is applied to any member. The new function is not enabled until the enabling APAR PM56631 is applied. If the new function will not be used, then there is no need to take precautions for rolling through the pre-conditioning PTF ahead of the enabling PTF. Instead, both pre-conditioning PTF and enabling PTF can be rolled through together. In addition, because the new function can only be used in DB2 10 New Function Mode (NFM), both pre-conditioning PTF and enabling PTF can be rolled through together on DB2 10 CM subsystems.). UK78581 HOLD DATA END UK78606 HOLD DATA START UK78606 HOLD DATA END UK78609 HOLD DATA START UK78609 HOLD DATA END UK78632 HOLD DATA START ++ HOLD(UK78632) SYS FMID(HDBAA10) REASON(ACTION) DATE(12130) COMMENT (The PTF for APAR PM57632 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the function the PTF addresses will not be enabled. The fix for APAR PM57632 is a companion fix. It requires the fix for APAR PM60438, for FMID JDBAA1K to be applied.). UK78632 HOLD DATA END UK78633 HOLD DATA START ++ HOLD(UK78633) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12130) 1 COMMENT (The fix for APAR PM60438 is a companion fix. It requires the fix for APAR PM57632, for FMID HDBAA10 to be applied.). ++ HOLD(UK71420) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12130) COMMENT (The fix for APAR PM42560 is a companion fix. It requires the fix for APAR PM27962, for FMID HDBAA10 to be applied.). UK78633 HOLD DATA END UK78678 HOLD DATA START UK78678 HOLD DATA END UK78700 HOLD DATA START ++ HOLD(UK78700) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12132) COMMENT (***Action for PM60533: See PM60533 APAR/PTF text for additional information about why a REBIND is recommended. After you apply this PTF, some applications might experience performance degradation. To improve the performance of those applications, rebind their plans and packages. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK78700 HOLD DATA END UK78722 HOLD DATA START UK78722 HOLD DATA END UK78723 HOLD DATA START UK78723 HOLD DATA END UK78782 HOLD DATA START UK78782 HOLD DATA END UK78785 HOLD DATA START ++ HOLD(UK78522) SYS FMID(HDBAA10) REASON(DOC) DATE(12137) COMMENT (PM57001 introduces the following changes to externals and the approximate text will be added to the V10 DB2 SQL Reference. This text is subject to change. Changed option for ALTER TABLESPACE MAXPARTITIONS: Specifies that the table space is partition-by-growth. integer specifies the maximum number of partitions to which the table | space can grow or shrink. integer must be in the range of 1 to 4096, depending on the value that is in effect for DSSIZE and the page size of the table space, and must not be less than 1 | the number of physical partitions already allocated for the table space. See CREATE TABLESPACE for more information about how DSSIZE and the page size are related. Information about this changed option will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). UK78785 HOLD DATA END UK78787 HOLD DATA START UK78787 HOLD DATA END UK78788 HOLD DATA START ++ HOLD(UK78788) SYS FMID(HDBAA10) REASON(DOC) DATE(12137) COMMENT (PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE is specified with OBID 1. The approximate text will be updated in the DB2 SQL Reference and Codes manual. This text is subject to change. ============= SQL Reference ============= CREATE TABLE->OBID integer Identifies the OBID to be used for this table. An OBID is the identifier for an object's internal descriptor. The | integer must be greater than 1 and not identify an existing or previously used OBID of the database. If you omit OBID, DB2 generates a value. ===== Codes ===== -736 The specified OBID does not fall within the acceptable range | for OBIDs, which is 2 to 32767.). ++ HOLD(UK78788) SYS FMID(HDBAA10) REASON(ACTION) DATE(12137) COMMENT (PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE is specified with OBID 1. Existing tables with OBID 1 should be dropped and recreated with a different OBID. A query, such as the sample query below may be used to identify tables with OBID 1. SELECT * FROM SYSIBM.SYSTABLES WHERE OBID = 1 AND ( TYPE = 'T' OR TYPE = 'M' OR TYPE = 'H' ) ;). UK78788 HOLD DATA END 1UK78834 HOLD DATA START UK78834 HOLD DATA END UK78883 HOLD DATA START UK78883 HOLD DATA END UK78929 HOLD DATA START UK78929 HOLD DATA END UK79001 HOLD DATA START ++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(DOC) DATE(12144) COMMENT (This PTF introduces the following changes to DB2 ODBC externals: New DB2 ODBC for z/OS initialization keywords described as follows. LIMITEDBLOCKFETCH = 0 | 1 This keyword is a performance optimization keyword that specifies whether DB2 ODBC is to attempt limited block fetch when fetching result sets from the connected data source. 0 = Limited block fetch is not used. 0 is the default. 1 = DB2 ODBC attempts to use limited block fetch. If blocking is supported at the server for the result set that is being fetched, DB2 ODBC retrieves as many rows as it can fit in a query data block in a single fetch request. QUERYDATASIZE = integer This keyword specifies the amount of query data, in bytes, that DB2 returns on each FETCH operation when limited block fetch is enabled. The default value is 32767. Possible values are: 32767 294911 557055 819199 65535 327679 589823 851967 98303 360447 622591 884735 131071 393215 655359 917503 163839 425983 688127 950271 196607 458751 720895 983039 229375 491519 753663 1015807 262143 524287 786431 1048575 If you specify a value that is not a valid value, DB2 ODBC sets QUERYDATASIZE to the nearest valid value. Information about the new DB2 ODBC initialization keywords and DB2 ODBC limited block fetch will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). ++ HOLD(UK71561) SYS FMID(JDBAA17) REASON(DOC) DATE(12144) COMMENT (*** Documentation for PM25678 (Version 10) A new initialization keyword, INTERRUPT, has been added to allow you to specify the interrupt processing mode when SQLCancel() is called to cancel the processing on a statement. 1 Complete documentation for the SQLCancel() API will be provided in the DB2 10 for z/OS ODBC Guide and Reference and in the Information Management Software for z/OS Solutions Information Center.). ++ HOLD(UK67822) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144) COMMENT (*** Action for PM32032 (Version 10) The following database request module (DBRM) is updated by this PTF: DSNCLIQR Application of this PTF requires a BIND PACKAGE for the above package. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site.). ++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144) COMMENT (The following database request modules (DBRMs) are updated by this PTF: DSNCLINF DSNCLIC1 DSNCLIMS DSNCLIQR DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only) Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 CLI bind job DSNTIJCL in the SDSNSAMP data set for an example of how to perform the BIND command. Also, refer to the prolog of DSNTIJCL for specific instructions on how to bind each DBRM and on how to customize the DSNTIJCL job for use at your site. This PTF introduces two new DB2 ODBC initialization keywords LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block fetch. Limited block fetch is a performance optimization that enables applications to improve the performance of FETCH operations when connected to a local DB2 for z/OS server. If limited block fetch is not desired, no further action is necessary other than rebinding the DBRMs listed above; otherwise please note the following. When you enable limited block fetch, the data that is returned to your application might not reflect the data that has been committed to the source table. If your application fetches data from tables that are updated by other users, or if your application uses savepoints and issues ROLLBACK TO SAVEPOINT to manage transactions, you should disable limited block fetch.). 1++ HOLD(UK60517) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144) COMMENT ( This PTF updates DB2 ODBC for z/OS database request module (DBRM) DSNCLIC1. After you apply this PTF, you need to run the BIND PACKAGE command to recreate the package for DSNCLIC1. Failure to bind the required package could result in SQLCODE -805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the prefix.SDSNSAMP data set for an example of how to perform the BIND command.). ++ HOLD(UK56516) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144) COMMENT (The following database request modules (DBRMs) for ODBC DB2 for z/OS are updated by this PTF: DSNCLIMS DSNCLIC1 Application of this PTF requires a BIND PACKAGE for the above packages. Failure to rebind the required packages could result in SQLCODE=-805 at application run time. Refer to the sample DB2 ODBC bind job DSNTIJCL in the SDSNSAMP dataset for an example of how to perform the BIND command.). UK79001 HOLD DATA END UK79004 HOLD DATA START UK79004 HOLD DATA END UK79008 HOLD DATA START UK79008 HOLD DATA END UK79011 HOLD DATA START UK79011 HOLD DATA END UK79013 HOLD DATA START ++ HOLD(UK79013) SYS FMID(HDBAA10) REASON(ACTION) DATE(12144) COMMENT (The PTF for APAR PM64065 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data 1 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(UK69216) SYS FMID(HDBAA10) REASON(ACTION) DATE(12144) COMMENT ( After applying the fix for PM31180 in DB2 10 for z/OS, FLASHCOPY IMAGE COPIES of partitioned objects with more than one partition or of linear objects containing more than one piece will insert a string of the form database-name.space-name into the DSNAME (data set name) column of the SYSCOPY record it writes for the FLASHCOPY record with DSNUM 0, similar to SYSCOPY records that are currently written for various types of non-backup activity. This is done to prevent invalid data set names from being written in these records. Users or automated programs sensitive to the contents of SYSIBM.SYSCOPY are advised.). UK79013 HOLD DATA END UK79014 HOLD DATA START UK79014 HOLD DATA END UK79015 HOLD DATA START UK79015 HOLD DATA END UK79017 HOLD DATA START UK79017 HOLD DATA END UK79062 HOLD DATA START ++ HOLD(UK79062) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12145) COMMENT (***Action for PM62259: See PM62259 APAR/PTF text for additional information about why a REBIND is necessary. PM62259 corrects a problem of incorrect output when a query contains OLAP specifications and a subquery predicate. This APAR also corrects ABENDOC4 RC00000038 DSNXOWIN+104A when a query contains multiple OLAP specifications other than RANK, DENSE_RANK, and ROW_NUMBER. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK79062 HOLD DATA END UK79065 HOLD DATA START UK79065 HOLD DATA END 1 UK79067 HOLD DATA START ++ HOLD(UK79067) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12145) COMMENT (***Action for PM62038: See PM62038 APAR/PTF text for additional information about why a REBIND is necessary. PM62038 corrects a problem of incorrect output that may occur when a query runs in parallel in-list (PLAN_TABLE's ACCESSTYPE = 'N' and ACCESS_PGROUP_ID > 0); and after the index column which is covered by the in-list predicate, there are also other predicates applied on at least one more index 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.). UK79067 HOLD DATA END UK79117 HOLD DATA START UK79117 HOLD DATA END UK79163 HOLD DATA START UK79163 HOLD DATA END UK79178 HOLD DATA START UK79178 HOLD DATA END UK79180 HOLD DATA START UK79180 HOLD DATA END UK79230 HOLD DATA START ++ HOLD(UK79230) SYS FMID(HDBAA10) REASON(ACTION) DATE(12152) COMMENT (See PM48742 APAR/PTF text in the PTF cover letter for additional information about this APAR. This APAR fixes two problems - one is incorrect index entries created for an XML value index with key type SQL DECFLOAT; another is incorrectly issuing SQLCODE -16061 when performing general comparison of invalid format of special values to numeric type in XPath predicates when no matching index exists. To make this fix effective for an application, users need to check if there is any XML value index with key type SQL DECFLOAT in use. If so, users need to run CHECK INDEX on such index after the application of this PTF to see it reports any data/index mismatch. REBUILD INDEX needs to be done for index with mismatch 1 issue. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK79230 HOLD DATA END UK79240 HOLD DATA START UK79240 HOLD DATA END UK79241 HOLD DATA START ++ HOLD(UK79241) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12152) COMMENT (***Action for PM61565: See PM61565 APAR/PTF text for additional information about why a REBIND is necessary. PM61565 corrects a problem of incorrect output when an SQL statement satisfies all of the following conditions: 1. SQL contains 'simple-when' CASE expression; 2. the column which is under CASE clause is defined with field procedure; 3. constants are under WHEN clause. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UK79241 HOLD DATA END UK79281 HOLD DATA START UK79281 HOLD DATA END UK79290 HOLD DATA START UK79290 HOLD DATA END UK79316 HOLD DATA START ++ HOLD(UK74411) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156) COMMENT (***Action for PM56722 (V10) This PTF modifies program DSNTRIN to install and configure the SYSPROC.ADMIN_INFO_SQL stored procedure in all modes of DB2 10 for z/OS. Previously, ADMIN_INFO_SQL (which is useful for gathering DB2 diagnostic and tuning data) was not installed in conversion mode after migration from DB2 UDB for z/OS Version 8. If you migrated to DB2 V10 from DB2 V8 and DB2 is not yet in new-function mode then after applying this PTF you need to take the following action: Run your copy of job DSNTIJRT with MODE(INSTALL) to install and configure SYSPROC.ADMIN_INFO_SQL. 1 If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job.). ++ HOLD(UK79316) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156) COMMENT (This PTF provides two new features: -- The Omnifind Text Search is moving to a new release, IBM Text Search for DB2 z/OS (IBMTS). -- A new stored procedure, SYSPROC.SYSTS_ALTER, can be used to modify the options of an existing IBM Text Search index. If you have already installed or migrated to DB2 10 for z/OS, you need to perform the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Copy updated DB2 installation panels to alternate libraries (3) Update your customized copy of job DSNTIJRT (4) Update private copies of the DSNTIDxx CLIST input member (5) Run installation job DSNTIJRT to install new objects (6) Run installation job DSNTIJRV to validate new objects Detailed guidance for these actions is given further below. If you currently use or want to use IBM Text Search for DB2 for z/OS, you need to perform these additional actions: (I) Download the most current version of IBMTS (II) New IBMTS users: Install the IBMTS server (III) Existing users: Migrate to IBMTS from OmniFind server (IV) Add the new stored procedure SYSPROC.SYSTS_ALTER. (V) Where to find more information Detailed guidance for these actions is given further below. ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Actions for all customers ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies CLIST members DSNTINST, DSNTINSV, and DSNTINS1 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any 1 tailoring you have done to your private copies of these CLISTs. You may also want to move them to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Copy updated DB2 installation panels to alternate libraries *********************************************************** * This action is required for all V10 customers who maintain * copies of the DB2 installation panels outside of SMP/E: *********************************************************** This PTF modifies the DB2 installation panels DSNTIPRA and DSNTIPRJ in the prefix.SDSNSPFP target library. If you keep the DB2 installation panels in a different library then after applying this PTF, you need to copy the updated panels to that library. ---------------------------------------------------------------- (3) Update customized copies of installation job DSNTIJRT *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF modifies installation job DSNTIJRT in the prefix.SDSNSAMP target library. After you apply this PTF, you need to add the following to the list of configuration control statements under the CFIGIN DD in your customized copy of DSNTIJRT: SYSPROC.SYSTS_ALTER WLMENV(DSNWLM_GENERAL) GRANTTO(PUBLIC) Notes: (a) Always leave a blank line between each configuration control statement (b) Inspect each of the new configuration control statement and if required: - Change the WLMENV parameter settings to the names of the WLM environment you use to run these routines at your site - Change the GRANTTO parameter setting to the authorization IDs that need access to the routines - Optionally add the PKGOWNER option ---------------------------------------------------------------- (4) Update private copies of the DSNTIDxx CLIST input member *********************************************************** * This action is required for all V10 customers *********************************************************** This PTF adds entries to store values entered into new fields on installation panel DSNTIPRL: - RTJ09ACL: GRANT EXECUTE setting for SYSPROC.SYSTS_ALTER - RTJ09PKO: PACKAGE OWNER setting for SYSPROC.SYSTS_ALTER - RTJ09WLM: WLM ENV NAME setting for SYSPROC.SYSTS_ALTER 1 You need to make the same changes to all private copies of your CLIST output (DSNTIDxx) member. In each such copy, add the following lines: RTJ09ACL CHAR M NONE NONE PUBLIC RTJ09PKO CHAR M NONE NONE NULL RTJ09WLM CHAR M NONE NONE DSNWLM_GENERAL The values shown in the 6th column are the DB2-supplied default settings. If you specified different settings in action (3) above, change the settings in column 6 accordingly. ---------------------------------------------------------------- (5) Run installation job DSNTIJRT to install new objects *********************************************************** * This action is optional for V10 customers *********************************************************** After you have completed the above actions, run your updated copy of job DSNTIJRT to install and grant access to the new routine, SYSPROC.SYSTS_ALTER, and to rebind the packages for the IBM Text Search routines. ---------------------------------------------------------------- (6) Run installation job DSNTIJRV to validate new objects *********************************************************** * This action is optional for V10 customers *********************************************************** After you have completed the above actions, run your customized copy of job DSNTIJRV to validate installation and configuration of SYSPROC.SYSTS_ALTER. ---------------------------------------------------------------- ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Additional actions for Text Search customers ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| The users need to follow the instructions in the "IBM Text Search for DB2 for z/OS" book to define the Text Search stored procedures and enable Text Search. The following information will refer to the "IBM Text Search for DB2 for z/OS" book. ---------------------------------------------------------------- (I) Download the most current version of IBMTS *********************************************************** * This action is required for Text Search customers *********************************************************** Download the most current version which is FIX R1L5 from the following Web site: http://www.ibm.com/software/data/db2/zos/downloads/oftss.html On this Web site, download the zip file and the readme file for IBMTS Text Search for DB2 for z/OS. 1 The following shows the names of the zip files of IBMTS Text Search Servers: Linux32 - TextSearchServer_setuplinux32.zip Linux64 - TextSearchServer_setuplinux64.zip Window32 - TextSearchServer_setupwin32.zip Window64 - TextSearchServer_setupwin64.zip zLinux - TextSearchServer_setupzlinux.zip For Window32/64: right click the zip then choose extract option For Linux32/Linux64/zlinux: chmod 755 TextSearchServer_setupxxxx.zip unzip TextSearchServer_setupxxxx.zip To install or update the IBMTS server, please refer to the following publications: --readme.html: document that accompanies the installation file. --"Installation, Administration, and Reference": the product documentation for the IBM Text Search for DB2 z/OS. ---------------------------------------------------------------- (II) New IBMTS users: Install the IBMTS server *********************************************************** * This action is required for Text Search customers *********************************************************** To install the IBMTS server, the user needs to follow: Chapter 4. Installing and configuring text search functions --Installing IBM Text Search for DB2 z/OS. (for the new installation). or --Installing fixes on top of the current server. (install IBMTS server on the existing server). ---------------------------------------------------------------- (III) Existing users: Migrate to IBMTS from OmniFind server *********************************************************** * This action is required for Text Search customers *********************************************************** For existing users to migrate IBMTS from OmniFind server they need to follow: Chapter 4. Installing and configuring text search functions --Migrating to IBM Text Search for DB2 for z/OS from OmniFind Text Search. ---------------------------------------------------------------- (IV) Add the new stored procedure SYSPROC.SYSTS_ALTER. *********************************************************** * This action is required for Text Search customers *********************************************************** Refer to steps (5) and (6) of the section above titled 1 "Actions for all customers" ---------------------------------------------------------------- (V) Where to find more information ---------------------------------------------------------------- The user can look for more information for the new SYSTS_ALTER stored procedure at: Chapter 5. Administration stored procedures for text search SYSPROC.SYSTS_ALTER.). ++ HOLD(UK67507) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156) 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. 4. This apar introduces the text search server level R2L11. To update the text search server, download the most current version which is FIX R2L11, from the following Web site: http://www.ibm.com/software/data/db2/zos/downloads/oftss.html From this Web site, click Download OmniFind Text Search Server for DB2 for z/OS. The following shows the names of the files that start the silent installation or update of a Text Search server. 1. Linux - TS_fixR2L11linux_i586.bin 2. zLinux - TS_fixR2L11zlinux.bin 3. Windows - TS_fixR2L11win32.exe To install or update the server, please reference the following publications: "Instructions for installing": readme.html document that accompanies the installation file. "Installation, Administration, and Reference": The product documentation for the IBM Text Search for DB2 z/OS and the IBM OmniFind Text Search Server. 5. This apar provides the fix related to the backup index table. After applying this APAR the users should run 1 SYSTS_UPDATE with ALLROWS options for all the indexes aready created with option UPDATEWITHBACKUP = 1 to make sure the backup index table refreshed with the full collection. Note that UPDATEWITHBACKUP = 1 is default option for SYSTS_CREATE, there for all most the indexes are created with this option. The users can use the following SQL statement to look for the indexes created before applying this APAR with UPDATEWITHBACKUP = 1 select a.indexid, indexschema, indexname, parameter, value from sysibmts.systextindexes a, sysibmts.systextconfiguration where a.indexid = b.indexid and parameter = 'UPDATEWITHBACKUP' and value = '1' Assume that the index SCHEMA1.IVC2 has UPDATEWITHBACKUP = 1 then the users need to run SYSTS_UPDATE with option ALLROWS for this index: CALL SYSPROC.SYSTS_UPDATE('SCHEMA1','IVC2','ALLROWS')). UK79316 HOLD DATA END UK79319 HOLD DATA START UK79319 HOLD DATA END UK79333 HOLD DATA START UK79333 HOLD DATA END UK79373 HOLD DATA START ++ HOLD(UK79373) SYS FMID(HDBAA10) REASON(ACTION) DATE(12158) COMMENT (See PM63986 APAR/PTF text in the PTF cover letter for additional information about this APAR. PM63986 fixes the problem that the XML index key entry might not be inserted for some XML document. This may cause incorrect output when the index is used. To make this fix effective for the existing XML index, please run CHECK INDEX on the XML index after application of this PTF and rebuild the XML index if there is any data/index mismatch.). UK79373 HOLD DATA END UK79393 HOLD DATA START UK79393 HOLD DATA END UK79400 HOLD DATA START UK79400 HOLD DATA END 1UK79404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79406 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79421 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79441 HOLD DATA START UK79441 HOLD DATA END UK79447 HOLD DATA START ++ HOLD(UK78241) SYS FMID(HDBAA10) REASON(DOC) DATE(12160) COMMENT (APAR PM58177 has enabled REORG TABLESPACE SHRLEVEL CHANGE to accept a user defined mapping table created in a partition-by-growth ( PBG ) table space. The Utility Guide and Reference has been updated with the following information, under the REORG TABLESPACE utility in section titled 'Mapping table and SHRLEVEL CHANGE' : Before running REORG TABLESPACE with SHRLEVEL CHANGE on a table space with non-LOB data, you must create a mapping table and index for the table space. The table space that | contains the mapping table must be either classic segmented | or a partition-by-growth table space, and cannot be the table space to be reorganized.). ++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(DOC) DATE(12160) COMMENT (See PM47356 APAR/PTF text for additional information. This APAR/PTF modifies the DB2 Utility Guide and Reference and the Messages manual. The change will be documented in the DB2 Utility Guide and Reference and Messages, and in the Information Management Software for z/OS Solutions Information Center. The change is as follows. In the Utility Guide and Reference, under REORG TABLESPACE, Option descriptions, SORTDATA option: SORTDATA NO Specifies that the data is to be unloaded in the order of the clustering index. SORTDATA NO cannot be specified | with SHRLEVEL CHANGE or if the table space is in REORG- | PENDING. Specify SORTDATA NO if one of the following conditions is true: * The data is in or near perfect clustering order, the | table space is not in REORP, and the REORG utility is used to reclaim space from dropped tables. * The data is very large, an insufficient amount of disk | space is available for sorting, and the table space is not in REORP. In the Messages manual, under DSNU messages: 1 DSNU070I csect-name KEYWORD OR OPERAND x INVALID WITH y Explanation: The use of a keyword or operand is | inconsistent with another keyword, operand or condition. | x and y The keywords, operands or conditions that cannot be used together. System action: The control statement in error is rejected and processing is halted. User response: Correct the control statement in error and resubmit the job. | Problem determination: The REORG TABLESPACE | utility issues this message when the keywords, operands or | conditions are not allowed to be used in combination.). ++ HOLD(UK77573) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (***Action for PM59605 This PTF modifies the DB2 installation CLIST member DSNTINST to fix a bug that causes it to ignore the NEWFUN setting specified in the DSNTIDxx input member when the CLIST is run in UPDATE mode. This PTF modifies DSNTINST in the SDSNCLST target library only. If you have already installed or migrated to this version of DB2 then after applying this PTF, you need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside.). ++ HOLD(UK78229) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (The PTF for APAR PM55051 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the function the PTF provides will not be available. PM55051 provides support for REORG TABLESPACE PART SORT NPSIs (Non-partitioned Secondary Indexes). This is a performance enhancement to part-level REORG involving 1 NPSIs intended to improve elapsed time. Since the removal of the BUILD2 phase for partition-level REORG in DB2 9, the performance of REORG was degraded in some cases due to the cost of building shadow NPSIs. Shadow NPSIs are populated initially with keys of parts which are not in the scope of the REORG during the UNLOAD phase. Then keys from parts within the scope of the REORG are sorted and inserted into the shadow NPSI during the SORT and REBUILD phases, respectively. Significant performance improvement can be achieved by sorting all keys of the NPSI in the same sort operation and rebuilding the index from the entire set of sorted keys. This APAR will add functionality to improve performance while leaving the old behavior intact and allow the customer to control the behavior through the installation panel and a keyword. This APAR modifies the processing of non-partitioned secondary indexes for REORG TABLESPACE PART SHRLEVEL CHANGE/REFERENCE when NPSIs are defined on the table space. Processing of NPSIs in this case will now be done in one of two ways as documented in the UNLOAD phase section of Execution Phase of REORG TABLESPACE in the Utility Guide and Reference. 1. During UNLOAD, one or more subtasks unload NPSI keys from parts not within the scope of the REORG and build the shadow NPSI. Keys from parts within the scope of the REORG are generated from the reorganized data rows, sorted, and inserted in the shadow index. 2. During UNLOAD, one or more subtasks processes NPSI keys from parts not within the scope of the REORG. These keys are routed to a sort process to be sorted with the keys from parts within the scope of the REORG. The shadow NPSI is built from this sorted set of keys. A new message is issued when all keys of an NPSI are sorted during a part-level REORG TABLESPACE. A new keyword is added on REORG to control the sorting of all NPSI keys during a part-level REORG TABLESPACE. The zparm controlling the sorting of all NPSI keys during a part-level REORG is extended to allow more options. ---------------------------------------------------------------- Changes to Messages and Codes DSNU1242I csect-name ALL KEYS OF A NON-PARTITIONED SECONDARY INDEX WILL BE SORTED Explanation During a part-level REORG all keys of a non-partitioned secondary index will be sorted before rebuilding the index. This is controlled by the keyword SORTNPSI and the zparm REORG_PART_SORT_NPSI. When SORTNPSI is specified as YES or AUTO all keys may be sorted. When SORTNPSI is not specified, and REORG_PART_SORT_NPSI is set to YES or AUTO, all keys may be sorted. 1 System action Processing is continues. Severity 0 (informational) ---------------------------------------------------------------- Changes to Utility Guide and Reference A new keyword SORTNPSI is added to control the method of building an NPSI during REORG TABLESPACE PART. Options of AUTO, YES, and NO are available on the keyword. A default is not applicable in this case because the value will be determined by zparm REORG_PART_SORT_NPSI if the keyword is not specified. .-FORCE--NONE----. (3) >--+----------------+--------+-----------------+---------------> +-FORCE--READERS-+ +-SORTNPSI AUTO---+ '-FORCE--ALL-----' '-SORTNPSI YES----' '-SORTNPSI NO-----' 3. The default for SORTNPSI is the value of the REORG_PART_SORT_NPSI subsystem parameter. SORTNPSI Specifies when REORG TABLESPACE PART should sort all keys of a non-partitioned secondary index. This keyword is ignored for a REORG that is not partition-level or a REORG with no non-partitioned secondary indexes. If SORTNPSI is not specified the value will be determined by zparm REORG_PART_SORT_NPSI. The benefit of sorting all keys of a non-partitioned secondary index increases as the ratio of data reorganized to total data in the table space increases. AUTO Specifies that if sorting all keys of the non-partitioned secondary indexes improves the elapsed time and CPU performance, all keys are sorted. YES Specifies that if sorting all keys of the non-partitioned secondary indexes improves the elapsed time, all keys are sorted. NO Specifies that only keys of the non-partitioned secondary indexes that are in the scope of the REORG are sorted. The default value is the value of subsystem parameter REORG_PART_SORT_NPSI. ---------------------------------------------------------------- Changes to DB2 Installation This APAR modifies the DSN6SPRM.REORG_PART_SORT_NPSI subsystem parameter. 1 REORG_PART_SORT_NPSI specifies the default method of building an NPSI during REORG TABLESPACE PART when the SORTNPSI keyword is not provided in the utility control statement. Valid settings for REORG_PART_SORT_NPSI are AUTO, NO, and YES. The default setting is NO. REORG_PART_SORT_NPSI is online changeable and has member scope in data sharing. DSN6SPRM: The REORG_PART_SORT_NPSI parameter is added with a range of AUTO, NO, and YES. The default setting is NO. DSNTIJUZ: The REORG_PART_SORT_NPSI parameter is added under the DSN6SPRM invocation with a default setting of NO. ---------------------------------------------------------------- Changes to DB2 instrumentation DSNDQWPZ: Field QWP4RPSNE is modified to trace the REORG_PART_SORT_NPSI internal setting: . . . QWP4RPSN DS CL1 REORG_PART_SORT_NPSI * * A=AUTO, N=NO, Y=YES . . . The IFCID 106 formatter stored procedures, SYSPROC.DSNWZP and SYSPROC.ADMIN_INFO_SYSPARM are updated to report the REORG_PART_SORT_NPSI setting. ---------------------------------------------------------------- This PTF adds an online-changeable subsystem parameter in DSN6SPRM called REORG_PART_SORT_NPSI that can be used to specify the default method of building a non-partitioned secondary index (NPSI) during REORG TABLESPACE PART. This setting will be used when the SORTNPSI keyword is not provided in the utility control statement. The SORTNPSI keyword specifies whether REORG TABLESPACE PART should decide to sort all keys of a NPSI and how to make that decision. The setting is ignored for a REORG which is not part-level or a REORG with no NPSIs. Valid settings for this parameter are: * AUTO: Specifies that if sorting all keys of the NPSI(s) improves the elapsed time and CPU performance, all keys are sorted. * YES : Specifies that if sorting all keys of the NPSI(s) improves the elapsed time, all keys are sorted. * NO : Specifies that only keys of the NPSI(s) that are in the scope of the REORG are sorted. => This is the default setting If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members 1 (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter REORG_PART_SORT_NPSI=, where is AUTO, NO, or YES, to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding REORG_PART_SORT_NPSI here, the value will be set to the default of NO when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF adds an entry for REORG_PART_SORT_NPSI to the CLIST default input members in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: REORG_PART_SORT_NPSI CHARR M AUTO YES$ Change to the value you specified for REORG_PART_SORT_NPSI in step (2), above. If you do not add REORG_PART_SORT_NPSI to a DSNTIDxx member, the DB2 installation CLIST will assume REORG_PART_SORT_NPSI=NO when run with that member as input.). ++ HOLD(UK76492) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (APAR PM54727 has corrected an issue where REORG REBALANCE on a 1 partitioned table space with an editproc defined can result in corrupted limit key values in the DB2 catalog and directory. In the event that the above limit key corruption has occurred, user can repair the catalog/directory by manually altering the limit keys to the correct value on the affected table space / partitions, and then run a REORG TABLESPACE utility to remove the restrictive REORP status.). ++ HOLD(UK78208) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (Action for PM53254: The PTF of PM53254 adds a new system parameter called REORG_IGNORE_FREESPACE, which specifies whether the REORG TABLESPACE utility should ignore the PCTFREE and FREEPAGE values when reloading data rows into a Partition By Growth (PBG) table space in the following circumstances: - When reorganizing a subset of the PBG partition(s) - When the table in the PBG table space has LOB column(s) Valid settings for REORG_IGNORE_FREESPACE are NO and YES. The default is NO, meaning that the PCTFREE and FREEPAGE values will be honored by the REORG TABLESPACE utility. To incorporate this fix the DB2 initialization parameter module, DSNZPARM, will need to be reassembled and re-linked by running the DB2 install clist DSNTINST using UPDATE mode. Insure that the output sample library name specified in panel DSNTIPT is not the same as an existing library name from a previous execution of the DSNTINST clist as the clist processing will delete all members delete all members of the data set name specified. Note: Customers who receive return code 8 and message "ASMA939U Unable to load external function module - DSNTIXL" when applying this PTF need to refer to Info APAR II13979. If you have already installed or migrated to this release of DB2, you need to take the following actions after applying this PTF: (1) Optional: Update your DB2 subsystem parameter (DSNZPxxx) modules: * Add the keyword parameter REORG_IGNORE_FREESPACE=, where is either NO or YES (NO is recommended) to the invocation of the DSN6SPRM macro in your customized version of the installation job DSNTIJUZ. Make sure to add a continuation character in column 72 if needed. If you omit adding REORG_IGNORE_FREESPACE here, the value will be set to the default of NO when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified, to assemble and link the load module. * After the job completes, you must either use the SET SYSPARM command or stop and start DB2 for the change to take effect. 1 (2) Required: Update your private copies of the CLIST defaults (DSNTIDxx) member: This PTF adds an entry for REORG_IGNORE_FREESPACE to the CLIST default input member, DSNTIDXA, in the SDSNSAMP target library. You need to add this entry to all private copies of your CLIST output (DSNTIDxx) member for DB2. In each such copy, add the following line: REORG_IGNORE_FREESPACE CHAR M NO YES where is the value you specified for REORG_IGNORE_FREESPACE when you modified DSNTIJUZ in step (1), above. Specify NO for if you bypassed step (1). (3) Required: Update customized copies of installation CLIST member DSNTINST: This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside.). ++ HOLD(UK74936) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (*** Action for PM47659 *** This APAR has changed the UNLOAD utility to utilize the RUNSTATS NPAGES statistic from SYSIBM.SYSTABLES to estimate the space needed for the SYSREC data set. A RUNSTATS against the target table space is recommended prior to the UNLOAD to ensure the accurate estimation for space requirement.). ++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160) COMMENT (The PTF for APAR PM47356 has modified the REORG TABLESPACE utility to issue the following message and end with RC8 when REORG TABLESPACE SORTDATA NO is run against a non-Partition- By-Growth (non-PBG) partitioned table space in REORG-PENDING (REORP). A REORG TABLESPACE SORTDATA YES is required to remove the REORP state. MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH 'TABLE SPACE IN REORG PENDING'). UK79447 HOLD DATA END UK79505 HOLD DATA START UK79505 HOLD DATA END UK79544 HOLD DATA START UK79544 HOLD DATA END UK79553 HOLD DATA START UK79553 HOLD DATA END 1 UK79562 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79589 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79602 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79619 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79630 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79665 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79683 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79701 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79710 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79762 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79770 HOLD DATA START ++ HOLD(UK79770) SYS FMID(HDBAA10) REASON(DOC) DATE(12176) COMMENT (PM63979 introduces the following changes to the Messages publication: Description change for message DSNU1140I: DSNU1140I csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY Explanation The number of instances of the indicated message issued during a utility operation has exceeded the maximum number permitted. csect-name The name of the control section that issued the message. max-messages The maximum number of messages that are issued before this message is issued. This value is controlled by the utility that issues message DSNU1140I. message-number The message number that has reached the limit and is now suppressed. | Example 1: The LOAD utility issues message DSNU1140I after 2000 instances of any of the following messages: DSNU313I, DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have triggered the suppressed message are still discarded. | Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message | DSNU1140I after 2000 instances of message DSNU1239I, when | MAXERR is specified to greater than 2000 or 0. Any rows that | would have triggered the suppressed message are still not | unloaded. System action Processing continues. No additional instances of message-number messages are issued. Only the issuance of the message is suppressed. Any action that is associated with the suppressed message number still occurs. 1 User response No action is required. Severity 0). ++ HOLD(UK79770) SYS FMID(HDBAA10) REASON(ACTION) DATE(12176) COMMENT (The PTF for APAR PM63979 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. To make this fix effective for a static application, it must be The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved.). ++ HOLD(UK75124) SYS FMID(HDBAA10) REASON(ACTION) DATE(12176) COMMENT (The PTF for APAR PM50005 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved. ***Action for PM50006: It should be noted that the removal of these UNLOAD restrictions will now allow clone and/or base table data to be UNLOADed using image copy data sets from the other table in the clone relationship as follows: 1 - UNLOAD from base table using a clone table image copy. 2 - UNLOAD from clone table using a base table image copy. And in these cases the MSGDSNU1227I and MSGDSNU1408I messages will no longer be issued and the return codes will be zero with this APAR fix.). UK79770 HOLD DATA END UK79774 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79820 HOLD DATA START UK79820 HOLD DATA END 1 UK79823 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79832 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79871 HOLD DATA START ++ HOLD(UK79871) SYS FMID(HDBAA10) REASON(ACTION) DATE(12179) COMMENT (The PTF for APAR PM62786 has modified CSECTs in both the DSNUT101 and DSN3AMGP load modules, affecting the utility batch and DB2 MSTR address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 MSTR address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 MSTR address spaces, the problem the PTF addresses will not be resolved.). ++ HOLD(UK62466) SYS FMID(HDBAA10) REASON(ACTION) DATE(12179) COMMENT (The PTF for APAR PM25135 has modified CSECTs in both the DSNUT101 and DSN3AMGP load modules, affecting the utility batch and DB2 MSTR address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 MSTR address space until DB2 is stopped and started. The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 MSTR address spaces, the problem the PTF addresses will not be resolved.). UK79871 HOLD DATA END UK79876 HOLD DATA START UK79876 HOLD DATA END UK79881 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK79911 HOLD DATA START UK79911 HOLD DATA END UK79995 HOLD DATA START UK79995 HOLD DATA END UK80106 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80113 HOLD DATA START ++ HOLD(UK80113) SYS FMID(HDBAA10) REASON(DOC) DATE(12188) COMMENT (With the PTF for PM52724, a new DB2 message, DSNU1544I, will be issued during the RECOVER utility with the BACKOUT YES option if the recovery cannot proceed: 1 .. DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER TABLE ACTIVITY .. Explanation: BACKOUT YES was specified for the RECOVER utility, but it cannot proceed because a prior SQL mass DELETE, TRUNCATE TABLE, or DROP TABLE occurred on the object. The deleted data for these activities are not logged, hence cannot be backed out. The recovery is prohibited when this kind of activity has occurred between the recovery point (specified by TOLOGPOINT or TORBA) and the current time. .. System action: The utility terminates processing. .. User response: Remove the BACKOUT YES option from the RECOVER utility statement and resubmit the job. This will recover the list of objects by restoring a backup then applying the logs forward to the recovery point. .. Severity: 8 (error) .. See the closing text of PM52724 for details.). ++ HOLD(UK80113) SYS FMID(HDBAA10) REASON(ACTION) DATE(12188) COMMENT (After the application of the PTF for APAR PM52724, the SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will no longer be inserted for SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION on segmented or universal table spaces (UTS). .. A new DB2 message, DSNU1544I, will now be issued during the RECOVER utility with the BACKOUT YES option if the recovery cannot proceed: .. DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER TABLE ACTIVITY .. Explanation: BACKOUT YES was specified for the RECOVER utility, but it cannot proceed because a prior SQL mass DELETE, TRUNCATE TABLE, or DROP TABLE occurred on the object. The deleted data for these activities are not logged, hence cannot be backed out. The recovery is prohibited when this kind of activity has occurred between the recovery point (specified by TOLOGPOINT or TORBA) and the current time. .. System action: The utility terminates processing. .. User response: Remove the BACKOUT YES option from the RECOVER utility statement and resubmit the job. This 1 will recover the list of objects by restoring a backup then applying the logs forward to the recovery point. .. Severity: 8 (error) .. See the closing text of PM52724 for details.). UK80113 HOLD DATA END UK80120 HOLD DATA START UK80120 HOLD DATA END UK80191 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80199 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80206 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80231 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80240 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80243 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80259 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80291 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80299 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80327 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80337 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80357 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80359 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80363 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80372 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80407 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80414 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80439 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80447 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80449 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80459 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80493 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80522 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80523 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80525 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80552 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80559 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80662 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80672 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80785 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80830 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80840 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80868 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80897 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80910 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80929 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80931 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK80981 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81001 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81020 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81022 ACCEPTED - (NOT IN PTS) - NO COVER LETTER 1UK81023 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81045 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81046 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81064 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81147 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81174 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81177 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81178 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81181 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81223 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81241 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81263 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81271 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81304 ACCEPTED - (NOT IN PTS) - NO COVER LETTER UK81306 ACCEPTED - (NOT IN PTS) - NO COVER LETTER READY END