UI14824 HOLD DATA START UI14824 HOLD DATA END UI14871 HOLD DATA START UI14871 HOLD DATA END UI15538 HOLD DATA START UI15538 HOLD DATA END UI15543 HOLD DATA START UI15543 HOLD DATA END UI15845 HOLD DATA START ++ HOLD(UI15178) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14069) COMMENT (See PI06999 APAR/PTF text for additional information about why a REBIND is necessary. PI06999 implements the code to check the target XML column in the SET assignment clause of an UPDATE statement with the XMLMODIFY function on a VIEW and issue SQLCODE4730 if the target XML column is not in the XML versioning format. To make this fix effective for a static application, it must 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(UI15398) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14069) COMMENT (***Action for PI06237: See PI06237 APAR/PTF text for additional information about why a REBIND is necessary. PI06237 corrects a problem that index-only access could be incorrectly chosen for an SQL statement that contains a ROW CHANGE expression or RID function on a view, which may cause a performance issue. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI15845 HOLD DATA END UI16018 HOLD DATA START 1UI16018 HOLD DATA END UI16189 HOLD DATA START UI16189 HOLD DATA END UI16194 HOLD DATA START UI16194 HOLD DATA END UI16242 HOLD DATA START UI16242 HOLD DATA END UI16266 HOLD DATA START UI16266 HOLD DATA END UI16315 HOLD DATA START ++ HOLD(UI16315) SYS FMID(HDBAA10) REASON(ACTION) DATE(14080) COMMENT (*************************************************************** Actions for customers who are using DB2 V10: *************************************************************** Run installation job DSNTIJRT to bind modified stored procedures packages *********************************************************** *********************************************************** * This action is required for all V10 customers *********************************************************** Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the stored procedures SYSPROC.ADMIN_UTL_MONITOR and SYSPROC.ADMIN_UTL_EXECUTE packages. 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(UK78763) SYS FMID(HDBAA10) REASON(ACTION) DATE(14080) COMMENT (*************************************************************** Actions for customers who are already using DB2 10: *************************************************************** Run installation job DSNTIJRT to bind modified stored procedures packages *********************************************************** * This action is required for all V10 customers *********************************************************** 1 Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the stored procedure SYSPROC.ADMIN_UTL_MONITOR. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job.). ++ HOLD(UK75581) SYS FMID(HDBAA10) REASON(ACTION) DATE(14080) 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 EXAMPLES section. When no such task exists proceed to step (4). Otherwise, proceed to step (3), below. 1 (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 * DSN SYSTEM(!DSN!) RUN PROGRAM(DSNTEP2) PLAN(DSNTEP!!) - LIB('DSN!!0.RUNLIB.LOAD') PARMS('/ALIGN(MID)') END 1 //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 ADDRESS DSNREXX "DISCONNECT" END ELSE SAY 'CONNECTION FAILED' 1 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 ***************************************************************). UI16315 HOLD DATA END UI16325 HOLD DATA START UI16325 HOLD DATA END UI16330 HOLD DATA START UI16330 HOLD DATA END UI16335 HOLD DATA START ++ HOLD(UI16335) SYS FMID(HDBAA10) REASON(ACTION) DATE(14080) COMMENT (This PTF corrects a problem where rows containing incorrectly truncated data may be inserted into explain table DSN_SORTKEY_TABLE. As a result, subsequent SELECTs on this table receive SQLCODE -331. After applying this PTF, you must delete the rows that are currently in the table causing -331 to stop receiving the SQL code.). UI16335 HOLD DATA END UI16342 HOLD DATA START UI16342 HOLD DATA END UI16394 HOLD DATA START UI16394 HOLD DATA END UI16395 HOLD DATA START UI16395 HOLD DATA END UI16433 HOLD DATA START ++ HOLD(UI13821) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14085) COMMENT (***Action for PM99602: See PM99602 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM99602 corrects a problem of an ABEND04E RC00E70005 and incorrect output: An ABEND04E RC00E70005 at location DSNNXML DSNNOCCN M450 may occur when a SQL statement satisfies following conditions: 1. a VIEW or table expression defined with UNION ALL is referenced in a full-select. 2. a where clause in above full-select contains XMLTABLE. 3. row-xquery-argument in above XMLTABLE is a host variable. Incorrect output can occur when a SQL statement satisfies following conditions: 1. a VIEW or table expression defined with UNION ALL is referenced in a full-select. 2. a where clause in the above full-select contains an external TABLE UDF defined with DETERMINISTIC and NO EXTERNAL ACTION. 3. a parameter of the above external TABLE UDF is a host variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI16433) SYS FMID(HDBAA10) REASON(ACTION) DATE(14085) COMMENT (***Action for PI10749: PI10749 corrects a problem of ABEND0C4 RC00000004 in DSNXEBR 0AA4 when a cursor with rowset positioning is used in a native SQL procedure or compiled SQL scalar function. After the application of this PTF, ALTER PROCEDURE REGENERATE is required for each native SQL procedure that is affected, or ALTER FUNCTION REGENERATE is required for each compiled SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure or compiled SQL scalar function could be affected by this change.). UI16433 HOLD DATA END UI16449 HOLD DATA START UI16449 HOLD DATA END UI16451 HOLD DATA START ++ HOLD(UI16451) SYS FMID(HDBAA10) REASON(ACTION) DATE(14101) COMMENT (***Action for PM81679 (DB2 10) This PTF modifies DSNTWR, the external module for the SYSPROC.WLM_REFRESH stored procedure so that, when WLM_REFRESH is called with a NULL or blank SSID parameter setting on a DB2 data sharing group that has a group attach name defined, it uses that group attach name, rather than the ID of the DB2 subsystem 1 on which it runs, to construct the name of its SAF resource profile, ssid.WLM_REFRESH.wlm-environment-name. This change makes WLM_REFRESH conform to documented behavior. This PTF also adds a new sample program called DSNTWRE that returns a copy of the DB2 Environmental Information Block (EIB). DSNTWRE is used by DSNTWR as follows: When WLM_REFRESH is called with a null or blank SSID parameter, DSNTWR runs DSNTWRE as a subtask and obtains the data sharing group name and group attach name from the returned EIB. If both are non-blank, DSNTWR uses the group attach name to construct the SAF resource profile; Otherwise it uses the ID of the DB2 subsystem on which WLM_REFRESH runs. DSNTWRE, like DSNTWR, is provided in both load module form and source code form. The load module resides in member DSNTWRE of the SDSNLOAD library. The source code resides in member DSNTWRE of the SDSNSAMP library. IVP job DSNTEJ6W is modified with an optional job step that can be used to prepare a local DSNTWRE module from the DSNTWRE source code. This PTF also modifies the link-edit parameters in two existing job steps of DSNTEJ6W. Pre-apply actions for this PTF: ------------------------------ Actions are required -before- applying this PTF if all of the following conditions are true: * You have already installed or migrated to DB2 10 * You run the WLM_REFRESH stored procedure on a data sharing group that has a group attach name defined * You call WLM_REFRESH with the second parameter, SSID, set to null or blank If all of the above are true then, after you apply this PTF, WLM_REFRESH will use the group attach name rather than the ID of the DB2 subsystem on which it runs as the first qualifier of the SAF resource profile. Therefore, before applying this PTF, verify or define, for each WLM environment that can be refreshed by WLM_REFRESH, a SAF profile in resource class DSNR having the format: group-attach-name.WLM_REFRESH.wlm-environment-name where: * group-attach-name is the group attach name for the data sharing group where WLM_REFRESH runs * wlm-environment-name is the name of a WLM environment that can be refreshed by WLM_REFRESH As with any SAF profile, wildcard characters may be used to extend the scope. For example 'DSN*.WLM_REFRESH.DSNWLM*' would include all WLM environments that begin with DSNWLM and run on any data sharing group with an attach name that begins with DSN. Also verify that each authorization ID allowed to use WLM_REFRESH to refresh a specified WLM environment is permitted READ or higher access on the WLM_REFRESH SAF profile for that WLM environment. 1 Alternatively, you can modify calls to WLM_REFRESH to pass the subsystem ID explicitly in the second parameter. Customers who meet all three of the qualifications noted above need to follow these pre-apply actions before applying this PTF because after the PTF is applied: * In the absence of a matching SAF profile, the WLM_REFRESH call will return code 4 and this message DSNT541I WLM REFRESH REQUEST FAILED. RESOURCE PROFILE group-attach-name.WLM_REFRESH.wlm-environment-name IS UNDEFINED and the refresh request will not be performed. In response, define the missing profile and permit READ or higher access on it to authorization IDs that need to refresh the specified WLM environment. * When a matching SAF profile exists but the calling authorization ID lacks READ or higher access the WLM_REFRESH call will return code 8 and this message DSNT542I SQL ID sql-id IS NOT AUTHORIZED TO REFRESH WLM ENVIRONMENT wlm-environment-name and the refresh request will not be performed. In response, permit READ or higher access on the profile to authorization IDs that need to refresh the specified WLM environment. Post-apply actions for this PTF: ------------------------------- If you have already installed or migrated to DB2 10, you need to take the following actions -after- applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update customized copies of sample job DSNTEJ6W (3) Rebuild or delete any private copies of module DSNTWR (4) Bind the package for DSNTWR These actions are detailed below: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members *********************************************************** * This action is required for all DB2 10 customers *********************************************************** This PTF modifies CLIST member DSNTINS3 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your private copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update customized copies of sample job DSNTEJ6W *********************************************************** * This action is optional for all DB2 10 customers who * maintain a customized copy of DSNTEJ6W *********************************************************** This PTF modifies job DSNTEJ6W in the prefix.SDSNSAMP target library as follows: 1 * It changes the link edit parameters in optional job step PH06WS01 from: PARM.LKED='LIST,LET,XREF,REUS,AMODE=31,RMODE=ANY,RENT' to: PARM.LKED='LIST,XREF,AMODE=31,RMODE=ANY,RENT' After applying this PTF, make the same change in your customized copy of DSNTEJ6W. * It also changes the link edit parameters in job step PH06WS03 from: PARM.LKED='AMODE=31,RMODE=ANY,MAP,RENT,REUS' to: PARM.LKED='AMODE=31,RMODE=ANY,MAP,RENT' After applying this PTF, make the same change in your customized copy of DSNTEJ6W. * It adds an optional (commented-out) job step called PH06WS00. PH06WS00 can be uncommented and run to prepare a DSNTWRE load module from the source code in member DSNTWRE of the prefix.SDSNSAMP library. However, it is recommended that you use the DSNTWRE load module provided by DB2 in the prefix.SDSNLOAD library. After applying this PTF, add job step PH06WS00: (1) Edit your customized copy of DSNTEJ6W (2) Make a copy of job step PH06WS01 and insert it as the first job step, that is just ahead of step PH06WS01. (3) Rename the new (first) job step PH06WS01 to PH06WS00 (4) Edit job step PH06WS00: - Change all occurrences of 'DSNTWRS' to 'DSNTWRE' - Change all occurrences of 'DSNTWR' to 'DSNTWRE' - Remove SETCODE AC(1) from the link-edit SYSIN DD statement (5) Save your changes ---------------------------------------------------------------- (3) Rebuild or delete any private copies of module DSNTWR *********************************************************** * This action is required for all DB2 10 customers who * maintain a private copy of DSNTWR, the external module * for WLM_REFRESH *********************************************************** This PTF updates DSNTWR, the DB2-supplied load module for WLM_REFRESH, in the prefix.SDSNLOAD library. It also updates DSNTWRS, the sample source code for DSNTWR, in the prefix.SDSNSAMP library. If you maintain a private copy of module DSNTWR, you either need to delete it in order to use the DB2-supplied DSNTWR module instead or you need to update it to include the changes introduced by this PTF. To continue maintaining your own DSNTWR module, proceed as follows: 1 (a) Compare your source code to that in member DSNTWRS of the prefix.SDSNSAMP library to identify necessary code changes. (b) After completing your code changes, use job steps PH06WS01 and PH06WS02 of your customized copy of job DSNTEJ6W to prepare an updated DSNTWR module and to bind a package from the updated DBRM. ---------------------------------------------------------------- (4) Bind the package for DSNTWR *********************************************************** * This action is required for all DB2 10 customers who use * the DB2-supplied DSNTWR module *********************************************************** This PTF updates DSNTWR, the external module for WLM_REFRESH plus the DBRM for DSNTWR. After applying this PTF, proceed as follows to bind a package from the updated DSNTWR DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2-supplied stored procedures. If you have previously run DSNTIJRT, re-running 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 re-run DSNTIJRT without the PREVIEW option or customize and run the generated job.). UI16451 HOLD DATA END UI16477 HOLD DATA START UI16477 HOLD DATA END UI16498 HOLD DATA START UI16498 HOLD DATA END UI16501 HOLD DATA START UI16501 HOLD DATA END UI16507 HOLD DATA START UI16507 HOLD DATA END UI16521 HOLD DATA START UI16521 HOLD DATA END UI16524 HOLD DATA START 1UI16524 HOLD DATA END UI16534 HOLD DATA START UI16534 HOLD DATA END UI16536 HOLD DATA START UI16536 HOLD DATA END UI16538 HOLD DATA START UI16538 HOLD DATA END UI16545 HOLD DATA START UI16545 HOLD DATA END UI16602 HOLD DATA START UI16602 HOLD DATA END UI16606 HOLD DATA START UI16606 HOLD DATA END UI16612 HOLD DATA START UI16612 HOLD DATA END UI16614 HOLD DATA START UI16614 HOLD DATA END UI16667 HOLD DATA START UI16667 HOLD DATA END UI16670 HOLD DATA START UI16670 HOLD DATA END UI16672 HOLD DATA START UI16672 HOLD DATA END UI16688 HOLD DATA START UI16688 HOLD DATA END UI16695 HOLD DATA START UI16695 HOLD DATA END UI16700 HOLD DATA START 1UI16700 HOLD DATA END UI16701 HOLD DATA START UI16701 HOLD DATA END UI16707 HOLD DATA START UI16707 HOLD DATA END UI16754 HOLD DATA START UI16754 HOLD DATA END UI16798 HOLD DATA START UI16798 HOLD DATA END UI16810 HOLD DATA START UI16810 HOLD DATA END UI16826 HOLD DATA START UI16826 HOLD DATA END UI16852 HOLD DATA START UI16852 HOLD DATA END UI16862 HOLD DATA START UI16862 HOLD DATA END UI16906 HOLD DATA START ++ HOLD(UI16906) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14099) COMMENT (See PI11720 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PI11720 corrects a problem that can cause data to incorrectly be inserted into a table when processing the INSERT portion of a MERGE statement when the UPDATE operation should be processed instead. This results in an SQLCODE -803. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI16906 HOLD DATA END UI16911 HOLD DATA START ++ HOLD(UI16911) SYS FMID(HDBAA10) REASON(DOC) DATE(14099) COMMENT 1 (APAR PI11730 changes the SQLCODE -20129 and the error message DSNH20129I as following: -20129 LOCAL SPECIAL REGISTER IS NOT VALID AS USED Explanation: An attempt was made to reference a special register, but the syntax was invalid for the specified special register. The CURRENT PACKAGE PATH special register, or a local special register such as CURRENT SERVER or CURRENT PACKAGESET cannot be referenced in an assignment statement (SET or VALUES INTO) where the special register is part of an expression in the source value, or where multiple source values are being assigned to multiple targets. The only valid uses of these special registers in a SET host-variable statement or VALUES INTO statement are: SET :hv= CURRENT SERVER; SET :hv= CURRENT PACKAGESET; SET :hv= CURRENT PACKAGE PATH; VALUES CURRENT SERVER INTO :hv; VALUES CURRENT PACKAGESET INTO :hv; VALUES CURRENT PACKAGE PATH INTO :hv; These restrictions apply only when the reference to the special register appears outside of the body of a native SQL procedure or an SQL scalar function. System action: The statement cannot be processed. Programmer response: Correct the statement in one of the following ways: Do not use the special register in an expression as the source of a SET or VALUES INTO statement. Do not assign multiple values to multiple special registers in a SET or VALUES INTO statement. SQLSTATE: 560B5 Severity: 8 (error) Information about this changed SQLCODE and error message will be included in the Information Management Software for z/OS Solutions Information Center at a later date.). UI16911 HOLD DATA END UI16941 HOLD DATA START UI16941 HOLD DATA END 1UI16958 HOLD DATA START ++ HOLD(UI16958) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14100) COMMENT (***Action for PI12418: See PI12418 APAR/PTF text for additional information about why a REBIND is necessary. PI12418 prevents an abend which might occur when a query uses the SOUNDEX built-in function in a predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI16958 HOLD DATA END UI16988 HOLD DATA START UI16988 HOLD DATA END UI17039 HOLD DATA START ++ HOLD(UI17039) SYS FMID(HDBAA10) REASON(DOC) DATE(14104) COMMENT (***Description for PI12047: See PI12047 APAR/PTF text for additional information about this enhancement. PI12047 removes the following restriction: Currently a correlation clause must be specified after a user-defined table function reference (SQLCODE -104). But some users want to omit the correlation clause and instead reference the name of the table function (and names of the result columns) directly in the query. For example: CREATE TABLE T1(C1 DEC); INSERT INTO T1 VALUES(1); COMMIT; CREATE FUNCTION TUDF1 (X INT) RETURNS TABLE (TCOL1 INT) LANGUAGE SQL SPECIFIC DEPTINFO2 DETERMINISTIC READS SQL DATA RETURN SELECT C1 + X FROM T1; COMMIT; SELECT X.C1 FROM TABLE(TUDF1(1)) X(C1); Currently the following receives SQLCODE -104: 1 SELECT TCOL1 FROM TABLE(TUDF1(1)); This PTF removes the requirement that a correlation clause must be specified after a table function reference. After application of the PTF, the above SELECT statement will work without SQLCODE -104. This PTF does not remove the requirement that a typed correlation clause must be specified after a generic table function. If the typed correlation clause is not specified, after the application of the PTF, the query may receive SQLCODE -390. If the correlation clause is not specified, and the table function has a syntax error, after application of the PTF, the query may receive SQLCODE -199. The above is an approximate description, and the SQL Reference will be updated to show the removal of the restriction.). UI17039 HOLD DATA END UI17042 HOLD DATA START ++ HOLD(UI12986) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14105) COMMENT (This PTF adds a new option, DISABLE_IMPCAST_JV, to the DB2 subsystem parameter DSN6FAC.DDF_COMPATIBILITY. You can use the DDF_COMPATIBILITY parameter to enable DB2 pre-V10 DDF compatibility with a Java IBM Data Server driver. The new DDF_COMPATIBILITY option is: - DISABLE_IMPCAST_JV: Use the pre-V10 server compatibility behavior which is not to implicitly cast input host variables during server host variable bind-in processing. This option provides such compatibility for all Java IBM Data Server driver level. This option is deprecated in DB2 10. If the DISABLE_IMPCAST_NJV option is specified on any member of a data sharing environment, it is recommended to specify it on all members. DDF_COMPATIBILITY options can be specified individually or together. Examples: DDF_COMPATIBILITY= DDF_COMPATIBILITY=DISABLE_IMPCAST_JV DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_JV) DDF_COMPATIBILITY=(DISABLE_IMPCAST_NJV,DISABLE_IMPCAST_JV) The default for DDF_COMPATIBILITY remains null (as shown in the first example above) meaning that DB2 10 or DB2 11 DDF behavior 1 is maintained with all clients. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers. This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers who want to use the DISABLE_IMPCAST_JV option of the DDF_COMPATIBILITY parameter, with or without the SP_PARMS_NJV and DISABLE_IMPCAST_NJV options. After applying this PTF, edit your customized copy of job DSNTIJUZ as follows: * Add or update the DDF_COMPATIBILITY keyword parameter in the invocation of the DSN6FAC macro and specify a setting of DISABLE_IMPCAST_JV, for example: DDF_COMPATIBILITY=DISABLE_IMPCAST_JV, If additional options are needed, use the list format, for example: DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_JV), Make sure to add a continuation character in column 72 if needed. If you omit adding DDF_COMPATIBILITY here, the value will be set to the default of null when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies the entry for DDF_COMPATIBILITY in the CLIST default input members in the SDSNSAMP target library. You need to add or update this entry in all private copies of your CLIST output DSNTIDxx member. In each such copy, convert any existing DDF_COMPATIBILITY entry in this format 1 DDF_COMPATIBILITY CHARR M NONE NONE to the format below. If no entry for DDF_COMPATIBILITY is present, add one that is in the format below. DDF_COMPATIBILITY STR M Change to NULL if you skipped step (2), above. Otherwise, change to one of the following: SP_PARMS_NJV, DISABLE_IMPCAST_NJV DISABLE_IMPCAST_JV SP_PARMS_NJV,DISABLE_IMPCAST_NJV SP_PARMS_NJV,DISABLE_IMPCAST_JV SP_PARMS_NJV,DISABLE_IMPCAST_NJV,DISABLE_IMPCAST_JV DISABLE_IMPCAST_NJV, DISABLE_IMPCAST_JV 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.). ++ HOLD(UI17042) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14105) COMMENT (This PTF adds a new option called IGNORE_TZ to the DSN6FAC.DDF_COMPATIBILITY subsystem parameter. It can be specified by users using a supported Java IBM Data Server driver to request the pre-V10 behavior for binding TIMESTAMP input host variable into TIMESTAMP target. - IGNORE_TZ: Use the pre-V10 server compatibility behavior which is to ignore TIME ZONE information in the boundary error checking for TIMESTAMP WITH TIME ZONE input TIMESTAMP WITH TIME ZONE input variables during server host variable bind-in processing when target data type is TIMESTAMP. This option provides such compatibility only for all Java IBM Data Server drivers level. This option is deprecated in DB2 10. If the IGNORE_TZ option is specified on any member of a data sharing environment, it is recommended to specify it on all members. IGNORE_TZ options can be specified individually or together. Examples: DDF_COMPATIBILITY= DDF_COMPATIBILITY=DISABLE_IMPCAST_JV DDF_COMPATIBILITY=IGNORE_TZ DDF_COMPATIBILITY=(SP_PARMS_NJV,IGNORE_TZ) DDF_COMPATIBILITY=(DISABLE_IMPCAST_NJV,SP_PARMS_JV,IGNORE_TZ) 1 The default for DDF_COMPATIBILITY remains null (as shown in the first example above) meaning that DB2 10 DDF behavior is maintained with all clients. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Update the package for DSNTXAZP Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers. This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers who want to use the IGNORE_TZ option of the DDF_COMPATIBILITY parameter, with or without the SP_PARMS_NJV, DISABLE_IMPCAST_NJV, and DISABLE_IMPCAST_JV options. After applying this PTF, edit your customized copy of job DSNTIJUZ as follows: * Add or update the DDF_COMPATIBILITY keyword parameter in the invocation of the DSN6FAC macro and specify a setting of IGNORE_TZ, for example: DDF_COMPATIBILITY=IGNORE_TZ, If additional options are needed, use the list format, for example: DDF_COMPATIBILITY=(SP_PARMS_NJV,IGNORE_TZ), Make sure to add a continuation character in column 72 if needed. If you omit adding DDF_COMPATIBILITY here, the value will be set to the default of null when you assemble the DSNZPxxx module. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must either use the -SET SYSPARM command or stop and restart DB2 for the change to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies the entry for DDF_COMPATIBILITY in the CLIST default input members in the SDSNSAMP target library. 1 You need to add or update this entry in all private copies of your CLIST output DSNTIDxx member. In each such copy, convert any existing DDF_COMPATIBILITY entry that has this format: DDF_COMPATIBILITY CHARR M NONE NONE or this format: DDF_COMPATIBILITY STR M to this format: DDF_COMPATIBILITY LSTR M DDF_COMPATIBILITY1 LSTR M NULL Change the setting you specified in step (2), above. If necessary, you can continue the setting onto the DDF_COMPATIBILITY1 entry by splitting it after a comma. For example: DDF_COMPATIBILITY LSTR M SP_PARMS_NJV,DISABLE_IMPCAST_NJV, DDF_COMPATIBILITY1 LSTR M DISABLE_IMPCAST_JV,IGNORE_TZ If you do not add entries for DDF_COMPATIBILITY to a DSNTIDxx member, the DB2 installation CLIST will assume 'DDF_COMPATIBILITY=,' when run with that member as input. --------------------------------------------------------------- (4) Update the package for DSNTXAZP --------------------------------------------------------------- ==> This action is required for all customers who use DSNTXAZP to update DB2 CLIST input (DSNTIDXX) members Submit a job that contains the following BIND statement: BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) - ACTION(ADD) ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where is the high-level qualifier for the DB2 subsystem target libraries. ---------------------------------------------------------------). UI17042 HOLD DATA END UI17082 HOLD DATA START UI17082 HOLD DATA END UI17098 HOLD DATA START UI17098 HOLD DATA END UI17121 HOLD DATA START ++ HOLD(UI17121) SYS FMID(HDBAA10) REASON(ACTION) DATE(14106) COMMENT (This PTF modifies Database Metadata stored procedure SYSIBM.SQLCOLUMNS. *************************************************************** Actions for customers who are already using DB2 V10: 1 *************************************************************** If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU (2) Refresh the WLM environment Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRM DSNACOLU 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 MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. (2) Refresh the WLM environment Issue the following VARY MVS command to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment in which the Database Metadata stored procedure SYSIBM.SQLCOLUMNS is running.). ++ HOLD(UI15737) SYS FMID(HDBAA10) REASON(ACTION) DATE(14106) COMMENT (This PTF modifies Database Metadata stored procedure SYSIBM.SQLCOLUMNS. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU (2) Refresh the WLM environment 1 Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to rebind DBRM DSNACOLU ==> This action is required for all V10 customers Run your customized copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRM DSNACOLU 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 MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. (2) Refresh the WLM environment Issue the following VARY MVS command to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment in which the Database Metadata stored procedure SYSIBM.SQLCOLUMNS is running.). UI17121 HOLD DATA END UI17126 HOLD DATA START UI17126 HOLD DATA END UI17149 HOLD DATA START UI17149 HOLD DATA END UI17167 HOLD DATA START UI17167 HOLD DATA END UI17182 HOLD DATA START ++ HOLD(UI17182) SYS FMID(HDBAA10) REASON(ACTION) DATE(14107) COMMENT (PI11454 corrects a problem that incorrect statement number and section number could be generated when a native SQL procedure 1 or non-inline SQL scalar function satisfies following conditions: 1. CREATE PROCEDURE/FUNCTION statement contains at least 2 assignment-statements that references user-defined function (UDF) or built-in function(BIF). 2. One of the assignment-statement references a UDF which does not exist during bind time. 3. One of the assignment-statement references a BIF. After the application of this PTF, ALTER PROCEDURE/FUNCTION REGENERATE is required for each native SQL procedure/SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure and SQL scalar function could be affected by this change.). UI17182 HOLD DATA END UI17200 HOLD DATA START UI17200 HOLD DATA END UI17201 HOLD DATA START UI17201 HOLD DATA END UI17203 HOLD DATA START UI17203 HOLD DATA END UI17226 HOLD DATA START UI17226 HOLD DATA END UI17240 HOLD DATA START ++ HOLD(UI17240) SYS FMID(HDBAA10) REASON(ACTION) DATE(14111) COMMENT (***Action for PI09198: See PI09198 APAR/PTF text for additional information about why a REBIND is necessary. PI09198 enables the following new functions for execution on an IBM DB2 Analytics Accelerator: (1) Execution of queries with time and timestamp constants containing "24:00" (2) FOR BIT DATA datatype (3) Refinement of query eligibility To make this new function effective for a static application containing accelerated static SQL queries, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). 1UI17240 HOLD DATA END UI17244 HOLD DATA START UI17244 HOLD DATA END UI17277 HOLD DATA START ++ HOLD(UI17277) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14112) COMMENT (PI13088 corrects a problem that can cause an abend at DSNISFW : 500B for a query of view defined with set functions.). ++ HOLD(UI16250) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14112) COMMENT (See PI10748 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PI10748 corrects problems that can cause abend for a query with sideway reference predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI15881) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14112) COMMENT (PI08794 corrects a problem of incorrect output returned when query contains GROUP BY,ORDER BY and FETCH FIRST N ROW with outer join. To make this fix effective for static applications, you need to rebind the affected applications after you apply this PTF.). UI17277 HOLD DATA END UI17279 HOLD DATA START UI17279 HOLD DATA END UI17291 HOLD DATA START UI17291 HOLD DATA END UI17305 HOLD DATA START UI17305 HOLD DATA END UI17310 HOLD DATA START UI17310 HOLD DATA END UI17315 HOLD DATA START UI17315 HOLD DATA END UI17349 HOLD DATA START 1++ HOLD(UI17349) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14114) COMMENT (***Action for PI10708: See PI10708 APAR/PTF text for additional information about why a REBIND is necessary. PI10708 corrects a problem of ABEND04E RC00C90101 DSNOTFLA ERQUAL5004. This abend may occur for an SQL statement that contains a CONCAT built-in function or a CONCAT operator and the argument of the CONCAT operation is a LOB 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.). UI17349 HOLD DATA END UI17351 HOLD DATA START UI17351 HOLD DATA END UI17359 HOLD DATA START UI17359 HOLD DATA END UI17369 HOLD DATA START ++ HOLD(UI17369) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14114) COMMENT (See PI12825 APAR/PTF text for additional information about why a REBIND is necessary. APAR PI12825 fixes the abend problem when passing the output of a CASE expression into XMLTABLE 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.). UI17369 HOLD DATA END UI17371 HOLD DATA START UI17371 HOLD DATA END UI17411 HOLD DATA START UI17411 HOLD DATA END UI17421 HOLD DATA START UI17421 HOLD DATA END UI17483 HOLD DATA START 1UI17483 HOLD DATA END UI17485 HOLD DATA START UI17485 HOLD DATA END UI17488 HOLD DATA START UI17488 HOLD DATA END UI17496 HOLD DATA START UI17496 HOLD DATA END UI17533 HOLD DATA START UI17533 HOLD DATA END UI17564 HOLD DATA START UI17564 HOLD DATA END UI17579 HOLD DATA START UI17579 HOLD DATA END UI17597 HOLD DATA START UI17597 HOLD DATA END UI17610 HOLD DATA START ++ HOLD(UI17610) SYS FMID(HDBAA10) REASON(ACTION) DATE(14122) COMMENT (***Action for PI14040 (DB2 10 for z/OS) This PTF modifies the DB2 scheduler for administrative tasks so that when the z/OS Language Environment variable TZ is set to a time zone with Daylight Savings Time alternative, it correctly schedules a task for execution during Daylight Savings Time. Post-apply actions for this PTF: -------------------------------- If you have already installed or migrated to DB2 10 for z/OS then after applying this PTF you need to take the following actions after applying this PTF: (1) Stop the DB2 scheduler for administrative tasks. (2) Start the DB2 scheduler for administrative tasks. These actions are detailed below. ---------------------------------------------------------------- (1) Stop the DB2 scheduler for administrative tasks. *********************************************************** * This action is required for all DB2 10 customers who use 1 * the DB2 scheduler for administrative tasks, i.e., the * DSN6SPRM.ADMTPROC subsystem parameter setting is not * null. *********************************************************** If the DB2 scheduler is running, stop it first by executing the following console command: MODIFY DSNADMT,APPL=SHUTDOWN where DSNADMT is the name of the scheduler. ---------------------------------------------------------------- (2) Start the DB2 scheduler for administrative tasks. *********************************************************** * This action is required for all DB2 10 customers who use * the DB2 scheduler for administrative tasks, i.e., the * DSN6SPRM.ADMTPROC subsystem parameter setting is not * null. *********************************************************** To start the DB2 scheduler again, execute the following console command: START DSNADMT where DSNADMT is the name of the scheduler.). UI17610 HOLD DATA END UI17622 HOLD DATA START ++ HOLD(UI17622) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14122) COMMENT (***Action for PI15176: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI15176 corrects a problem in which DB2 may not read in multi-column frequency and/or histogram statistics for a table referenced more than once in a query. This could lead to an inefficient access path and poor query performance. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI17622 HOLD DATA END UI17630 HOLD DATA START UI17630 HOLD DATA END UI17632 HOLD DATA START UI17632 HOLD DATA END UI17638 HOLD DATA START UI17638 HOLD DATA END UI17640 HOLD DATA START 1UI17640 HOLD DATA END UI17678 HOLD DATA START ++ HOLD(UI13489) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14125) COMMENT (***Action for PM98161 See PM98161APAR/PTF text for additional information about why a REBIND is necessary. PM98161 corrects a problem that incorrect SQLCODE -333 may be issued when rebind, incremental rebind or deploy a native SQL procedure or a compiled SQL scalar function that contains FOR BIT DATA SQL variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI14400) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14125) COMMENT (***Action for PI07053: See PI07053 APAR/PTF text for additional information about why a REBIND is necessary. PI07053 corrects a problem for which an SQLCODE -332 (SQLCODE332) can be issued incorrectly for an SQL statement that references an SQL Table UDF whose output requires a CCSID conversion. To make this fix effective for a static application, it must 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(UI14265) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14125) COMMENT (***Action for PI05107: See PI05107 APAR/PTF text for additional information about why a REBIND is necessary. PI05107 corrects the following problems: An ABEND04E RC00E70005 at the location DSNXGRDS DSNXOBFC P140 can occur when an SQL statement satisfies following conditions: 1. The SQL statement contains a DECODE function. 2. An argument of the DECODE function is untyped parameter marker. SQLCODE -401 may not be issued correctly when an SQL statement satisfies following conditions: 1. The SQL statement contains a DECODE function. 2. 'else-expression' is not compatible with any of 'result-expression' in the DECODE function. 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(UI17678) SYS FMID(HDBAA10) REASON(DOC) DATE(14125) COMMENT (The DB2 for z/OS SQL Reference will be updated with the following desciption of the MEDIAN function. The final wording is subject to change without notice. The MEDIAN function returns the median of a set of numbers. >>--MEDIAN--(-numeric-expression-)----------->< The schema is SYSIBM. numeric-expression An expression that returns a built-in numeric, character or graphic string data type (SQLSTATE 42815, SQLCODE -171). A string value is implicitly cast to a numeric value. numeric-expression must not include a scalar fullselect (SQLSTATE 42607, SQLCODE -112), or invoke a function that is non-deterministic or has an external action (SQLSTATE 42845, SQLCODE -583). If the argument is DECFLOAT(n), the result of the function is DECFLOAT(34). Otherwise, the result of the function is double precision floating-point. The function is applied to the set of values derived from the argument values by the elimination of null values. The result can be null. If numeric-expression is null or if the function is applied to the empty set, the result is the null value. Example 1: Calculate the median salary of the employees in department D11 from the EMPLOYEE table. SELECT MEDIAN(SALARY) FROM EMPLOYEE WHERE WORKDEPT = 'D11'; The result is 24680.00. There are 11 employees in department D11. The middle row of a group of 11 values is the sixth row. The result of MEDIAN over that group is the value of the sixth row, which is 24680.00. Example 2: Calculate the median salary of the employees in department E21 from the EMPLOYEE table. SELECT MEDIAN(SALARY) FROM EMPLOYEE WHERE WORKDEPT = 'E21'; 1 The result is 24605.00. There are six employees in department E21. Since there are an even number of rows, the MEDIAN is computed by interpolating a value between the middle two rows. The middle two rows are row three with value 23840.00 and row four with value 25370.00. MEDIAN is computed by averaging those two values, which results in 24605.00. Additional Notes: When EXPLAIN is issued against an SQL statement that references MEDIAN, but the statement could not be run on the accelerator server for any reason, the following values would be populated in the PLAN_TABLE. For a SELECT statement, column QBLOCK_TYPE would have the value 'PRUNED', and column ACCESSTYPE would have the value ' ' (blank). When a view is referenced in an SQL statement that uses the MEDIAN function, the tables referred to in the view must be enabled for acceleration (SQLCODE -4742, SQLSTATE 560D5). Those tables referred to in the view do not need to be enabled for acceleration when the view is created. For a static SQL statement that references MEDIAN, BIND or REBIND of the package must specify the QUERYACCELERATION bind option with ENABLE, ENABLEWITHFAILBACK, ELIGIBLE, or ALL (SQLCODE -4742, SQLSTATE 560D5).). ++ HOLD(UI17678) SYS FMID(HDBAA10) REASON(ACTION) DATE(14125) COMMENT (***Action for PI10167: See PI10167 APAR/PTF text for additional information about why a BIND is necessary. PI10167 enables the new function MEDIAN queries to be run only on an accelerartor. To make this fix effective for a static application containing static SQL queries with the new MEDIAN function to be accelerated, the application must be bound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI14400) SYS FMID(HDBAA10) REASON(ACTION) DATE(14125) COMMENT (***Action for PI07053: The following ACTION needs to be performed on behalf of this apar. Please note that along with the application of this fix, if the Table UDF (user-defined function) is nested, it will need to be dropped and recreated.). UI17678 HOLD DATA END UI17692 HOLD DATA START UI17692 HOLD DATA END 1 UI17694 HOLD DATA START UI17694 HOLD DATA END UI17698 HOLD DATA START UI17698 HOLD DATA END UI17701 HOLD DATA START UI17701 HOLD DATA END UI17716 HOLD DATA START ++ HOLD(UI17716) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14126) COMMENT (===>Action for PI12607 (DB2 10) This PTF adds a new option called SP_PARMS_JV to the DSN6FAC.DDF_COMPATIBILITY subsystem parameter. It can be specified by customers using a supported Java IBM Data Server driver to request the pre-V10 behavior for returning parameters from stored procedures: - SP_PARMS_JV: Use the pre-V10 server compatibility behavior which is to return stored procedure parameters according to the SQL type of each argument, as specified by the application in the stored procedure call, in the following cases: * if the calling application is using an IBM Data Server Java driver which does not have the fix of APAR IC80974 * and, the stored procedure has no parameter of the following types: XML, TIMESTAMP with TIME ZONE, TIMESTAMP with extended precision (>6). If the client driver does not have the fix of IC80974 or if the stored procedure has one of the above V10 parameter types or if the SP_PARMS_JV option is not specified then DB2 will use the default server behavior which is to return stored procedure parameters according to the SQL type specified for each parameter in the stored procedure declaration. If the SP_PARMS_JV option is specified on any member of a data sharing environment, it is recommended to specify it on all members. SP_PARMS_JV options can be specified individually or together. 1 Examples: DDF_COMPATIBILITY= DDF_COMPATIBILITY=DISABLE_IMPCAST_JV DDF_COMPATIBILITY=SP_PARMS_JV DDF_COMPATIBILITY=(SP_PARMS_NJV,SP_PARMS_JV) DDF_COMPATIBILITY=(DISABLE_IMPCAST_NJV,SP_PARMS_JV) The default for DDF_COMPATIBILITY remains null (as shown in the first example above) meaning that DB2 10 DDF behavior is maintained with all clients. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Update the package for DSNTXAZP Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is recommended for all customers. This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required for all customers who want to use the SP_PARMS_JV option of the DDF_COMPATIBILITY parameter, with or without other options. After applying this PTF, edit your customized copy of job DSNTIJUZ as follows: * Add or update the DDF_COMPATIBILITY keyword parameter in the invocation of the DSN6FAC macro and specify a setting of SP_PARMS_JV, for example: DDF_COMPATIBILITY=SP_PARMS_JV, If additional options are needed, use the list format, for example: DDF_COMPATIBILITY=(SP_PARMS_NJV,SP_PARMS_JV), 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 1 ---------------------------------------------------------------- ==> This action is required for all customers This PTF modifies the entry for DDF_COMPATIBILITY in the CLIST default input members in the SDSNSAMP target library. You need to add or update this entry in all private copies of your CLIST output DSNTIDxx member. In each such copy, convert any existing DDF_COMPATIBILITY entry that has this format: DDF_COMPATIBILITY CHARR M NONE NONE or this format: DDF_COMPATIBILITY STR M to the format below. If no entry for DDF_COMPATIBILITY is present, add one that is in the format below: DDF_COMPATIBILITY LSTR M DDF_COMPATIBILITY1 LSTR M NULL Change to the setting you specified in step (2), above. If necessary, you can continue the setting onto the DDF_COMPATIBILITY1 entry by splitting it after a comma. For example: DDF_COMPATIBILITY LSTR M SP_PARMS_NJV,DISABLE_IMPCAST_NJV, DDF_COMPATIBILITY1 LSTR M DISABLE_IMPCAST_JV,SP_PARMS_JV Change to NULL if your customized copy of DSNTIJUZ does not specify the DDF_COMPATIBILITY parameter or if it specifies either 'DDF_COMPATIBILITY=,' or 'DDF_COMPATIBILITY=()'. If you do not add entries for DDF_COMPATIBILITY to a DSNTIDxx member, the DB2 installation CLIST will assume 'DDF_COMPATIBILITY=,' when run with that member as input. --------------------------------------------------------------- (4) Update the package for DSNTXAZP --------------------------------------------------------------- ==> This action is required for all customers who use DSNTXAZP to update DB2 CLIST input (DSNTIDXX) members Submit a job that contains the following BIND statement: BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) - ACTION(ADD) ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') where is the high-level qualifier for the DB2 subsystem target libraries. ---------------------------------------------------------------). UI17716 HOLD DATA END UI17762 HOLD DATA START UI17762 HOLD DATA END 1UI17834 HOLD DATA START UI17834 HOLD DATA END UI17851 HOLD DATA START ++ HOLD(UK70914) SYS FMID(HDBAA10) REASON(ACTION) DATE(14129) COMMENT (***Action for PM41805: See PM41805 APAR/PTF text for additional information about why further ACTION might be necessary. PM41805 corrects a problem that can occur when DATETIME arithmetic returns a NULL value. However, DB2 does not zero out the data part of the result and can leave it containing "bad" data. Eventually, this can cause an incorrect result to be returned. For the recreate example described in the apar PM41805 text, if the incorrect data already exists in the database, the following simple example (steps) might be helpful in correcting it. 1. Drop the index which has the LAST_DATE column as one of the index keys. DROP INDEX I1; COMMIT; 2. Apply the PTF for apar PM41805 and recycle DB2. 3. Rerun the UPDATE statement which causes the incorrect result. UPDATE T1 SET LAST_DATE = LAST_DATE - ((DAYS('07/20/2010') - DAYS('05/28/2009'))DAYS); 4. Recreate the dropped index. CREATE INDEX I1 ON T1 (IDN ASC, LAST_DATE ASC); COMMIT; 5. Execute the SELECT statement (again) which uses index access and references the LAST_DATE column as a stage 1 predicate. SELECT * FROM T1 WHERE IDN = 2 AND LAST_DATE IS NULL; After the application of apar PM41805 and re-running the UPDATE statement in Step 3., a correct NULL value will correct/replace the "bad" null value in the table. Once the same index is recreated, and the LAST_DATE column is referenced as a stage 1 predicate in the SELECT query, a correct result will be returned.). UI17851 HOLD DATA END 1 UI17859 HOLD DATA START UI17859 HOLD DATA END UI17861 HOLD DATA START UI17861 HOLD DATA END UI17875 HOLD DATA START UI17875 HOLD DATA END UI17902 HOLD DATA START ++ HOLD(UI17902) SYS FMID(HDBAA10) REASON(ACTION) DATE(14132) COMMENT (This APAR adds a new feature for the DB2XML.SOAPHTTPNV and DB2XML.SOAPHTTPNC UDFs to return SOAP message when the HTTP status code is not 200. The ENVAR option "RETURN_ERROR=YES" is implemented. When this ENVAR option is specified, the UDFs will enclose the SOAP message in an error element as below and return it when the HTTP status code is not 200. {SOAP message} This gives the application the opportunity to handle the error programmatically. To enable this new ENVAR option, run following ALTER statements for the corresponding UDFs and rebind the application. ALTER SPECIFIC FUNCTION DB2XML.SOAPHTTPNVIVO RUN OPTIONS 'POSIX(ON),XPLINK(ON),ENVAR("RETURN_ERROR=YES")' ALTER SPECIFIC FUNCTION DB2XML.SOAPHTTPNVICO RUN OPTIONS 'POSIX(ON),XPLINK(ON),ENVAR("RETURN_ERROR=YES")' ALTER SPECIFIC FUNCTION DB2XML.SOAPHTTPNCICO RUN OPTIONS 'POSIX(ON),XPLINK(ON),ENVAR("RETURN_ERROR=YES")' ALTER SPECIFIC FUNCTION DB2XML.SOAPHTTPNCIVO RUN OPTIONS 'POSIX(ON),XPLINK(ON),ENVAR("RETURN_ERROR=YES")'). UI17902 HOLD DATA END UI17904 HOLD DATA START ++ HOLD(UI17904) SYS FMID(HDBAA10) REASON(ACTION) DATE(14132) COMMENT (The PTF for APAR PM74574 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 1 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.). UI17904 HOLD DATA END UI17906 HOLD DATA START UI17906 HOLD DATA END UI17926 HOLD DATA START UI17926 HOLD DATA END UI17940 HOLD DATA START ++ HOLD(UK83798) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14133) COMMENT (***Action for PM71904: See PM71904 APAR/PTF text for additional information about why a REBIND is necessary. PM71904 corrects a problem of poor query performance for a query with a predicate or predicates on a timestamp column inside an OR predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83458) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14133) COMMENT (***Action for PM71471: See PM71471 APAR/PTF text for additional information about why a REBIND is necessary. PM71471 corrects a predicate localization problem when there is an EXISTS subquery in the CASE expression of the select list. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90663) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14133) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM69713 corrects a problem where incorrect output can occur 1 on a query if there are: 1. two or more predicates with IN-lists on the same column; 2. the predicates are involved in compound OR predicates; and 3. the OR predicates involve columns from more than one table. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17940) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14133) COMMENT (***Action for PI14090: See PI14090 APAR/PTF text for additional information about why a REBIND is necessary. PI14090 corrects a problem of SQL performance on a query which contains a predicate or predicates with implicit CAST inside an OR predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI17940 HOLD DATA END UI17992 HOLD DATA START UI17992 HOLD DATA END UI18020 HOLD DATA START ++ HOLD(UI13948) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM98839: See PM98839 APAR/PTF text for additional information about why a REBIND is necessary. PM98839 corrects a problem of ABEND0C4 RC00000038 in DSNXRSGB when a query contains a subquery that undergoes a subquery-to- join transformation when the access type for the table from this subquery is 'N', and the matching columns have an IN-subquery predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI12324) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM97589: See PM97589 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM97589 corrects a problem between index-only access versus non-index-only access. Under some special circumstances, DB2 may not recognize a desirable index-only access. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK98528) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM94815: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM94815 corrects a problem that an unnecessary sort may be performed for a query even if the index selected could avoid the sort for the GROUP BY/ORDER BY specified in the query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK97992) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM94767: See PM94767 APAR/PTF text for additional information about why a REBIND is necessary. PM94767 corrects a problem where an inefficient access path can be chosen when there is an index without matching columns to support GROUP BY or ORDER BY order, and that query or query block also has OPTIMIZE FOR n ROWS or FETCH FIRST n ROWS ONLY. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK96987) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM93043: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM93043 corrects a problem in which an inefficient access path may be selected for a query specifying OPTIMIZE FOR 1 ROW or FETCH FIRST 1 ROW and an ORDER BY if an index is available to support the ORDER BY in reverse order. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK96956) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 1 COMMENT (***Action for PM90987: See PM90987 APAR/PTF text for additional information about why a REBIND is necessary. PM90987 corrects a problem of a bad access path for a partitioned table when the table is limited to only 1 partition for page range access, and there is at least one DPSI on the table. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK95412) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM90480: See PM90480 APAR/PTF text for additional information about why a REBIND is necessary. PM90480 corrects a problem of inaccurate compound filter factor of two RANGE predicates on the same column which may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK96217) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM89605 corrects a problem where ABEND0CC RC0C in DSNXOCCX+0F74 or poor query performance could occur for a query with an IS NULL on a column with histogram statistics collected on it and there is only a single quantile. Also, the single quantile represents the NULL frequency. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK95956) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM89036: See PM89036 APAR/PTF text for additional information about why a REBIND is necessary. PM89036 corrects a problem of SQL performance for a user whose queries contain join predicates with histogram statistics on both of the join columns. 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(UK94952) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM87836: See PM87836 APAR/PTF text for additional information about why a REBIND is necessary. PM87836 corrects problems of incorrect UNCERTAINTY values in DSN_PREDICAT_TABLE and incorrect cost fields in DSN_DETCOST_TABLE. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK94034) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM85671: See PM85671 APAR/PTF text for additional information about why a REBIND is necessary. PM85671 corrects a problem of a poorly performing access path for a partitioned table when: 1. DB2 uses an EQUAL predicate with host variables or parameter markers to limit the partitions for page range access, 2. The PLAN_TABLE shows PAGE_RANGE='Y', 3. There is at least one DPSI on the table, and 4. There is a GROUP BY or ORDER BY in the query. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92981) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM83144: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83144 corrects a problem in which DB2 could incorrectly discard an multi-index access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92968) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM81295: 1 See PM81295 APAR/PTF text for additional information about why a REBIND is necessary. PM81295 corrects a problem of poor query performance for a query containing OR predicates that map to a single index. The poor performance can occur when a range-list index access plan may not be assigned the lowest cost of any plan it beats. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92539) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM80699: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM80699 corrects a problem that incorrect output may be returned for a query with a GROUP BY list which has a SUBSTR or YEAR function as well as the column referenced by the function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92197) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM80413: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM80413 corrects a problem in which page range screening (PAGE_RANGE='Y') is not chosen when a DPSI is used with one-fetch index access (ACCESSTYPE='I1'). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK92081) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM80173: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM80173 corrects a problem that DB2 may select a nested loop join and a table space scan without sparse index used on the inner table for a join in a recursive common table expression. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be 1 affected by this change.). ++ HOLD(UK92252) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM79973: See PM79973 APAR/PTF text for additional information about why a REBIND is necessary. PM79973 corrects a possible query performance problem for a query that contains FETCH FIRST 1 ROW ONLY, OPTIMIZE FOR 1 ROW, or an EXISTS subquery, and there exists an index where all the predicates can be matching predicates. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK91069) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM78070: See PM78070 APAR/PTF text for additional information about why a REBIND is necessary. PM78070 corrects a problem of incorrect output that can happen for a query which contains UNION, EXCEPT, EXCEPT ALL or ORDER BY and whose top query block has exactly one table. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK91588) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM76495: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM76495 corrects a problem that an inefficient index may be selected when multiple indexes are estimated to be highly selective and the matching column coverage of one index is the superset of the matching column and the screening column coverage of the inefficient index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90090) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM75364: See PM75364 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM75364 corrects a problem of inaccurate filter factor estimate of an IS NOT DISTINCT FROM predicate that may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90518) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM74991: See PM74991 APAR/PTF text for additional information about why a REBIND is necessary. PM74991 corrects a problem of choosing a poorly performing access path for queries containing predicates on columns where frequency or histogram statistics have been collected. The predicate is a range predicate with parameter marker (or parameter markers) or host variable (or host variables), or the predicate refers to a subquery (except an EQUAL or NOT EQUAL subquery). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83996) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM74543: See PM74543 APAR/PTF text for additional information about why a REBIND is necessary. PM74543 corrects a problem of choosing a poorly performing access path for a partitioned table when queries involve partitioned tables, and EQUAL with host variables or parameter markers, and a DPSI (Data Partitioned Secondary Index). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83426) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM74152: A rebind is necessary for static applications to rebuild internal structures used at runtime based on the changes in this APAR. PM74152 corrects a problem in which DB2 may incorrectly return no rows for a query using page range access where a range predicate exists on a partitioning column defined as CHAR(1). 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(UK83646) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM73328: See PM73328 APAR/PTF text for additional information about why a REBIND is necessary. PM73328 corrects a problem of selecting Index Scan access using a less filtering index over INLIST access using a more filtering index, which may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83909) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM72374: A rebind is necessary for static applications to rebuild access paths based on the changes in this PTF. PM72374 corrects a problem in which DB2 chooses an index matching on only a few (or one) column(s) when an alternate index exists with matching that is estimated to be very selective and matching columns that are a superset of the chosen index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK81821) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM70949: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM70949 corrects a problem in which a tablespace scan access path may be incorrectly chosen when using an internal serviceability feature to influence access path selection with ACCESS_TYPE='INLIST'. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK81527) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM69949: 1 A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM69949 corrects a problem in which DB2 may choose a highly selective or index-only DPSI without page range when a more efficient non-DPSI index exists. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK81765) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM69139: See PM69139 APAR/PTF text for additional information about why a REBIND is necessary. PM69139 corrects a problem of inaccurate compound filter factor of two range predicates on the same column that may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK81450) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM68086: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM68086 corrects a problem in which compound filter factor may be overestimated, potentially resulting in a suboptimal access path and poor performance. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK80905) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM67292: A rebind is necessary to rebuild package and/or plan structures based on the changes in this APAR. PM67292 corrects a problem that DB2 may improperly favor range list index scan over multiple index access. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). 1++ HOLD(UK80701) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM66948: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM66948 corrects a problem of inaccurate filter factor estimation for a predicate if the predicate references a nullable column on which histogram statistics exist. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK80906) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM66098: See PM66098 APAR/PTF text for additional information about why a REBIND is necessary. PM66098 corrects a problem where DB2 does not select an equal unique index even though it may be the best choice, resulting in a query performance problem. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK80118) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM64871: See PM64871 APAR/PTF text for additional information about why a REBIND is necessary. PM64871 corrects a problem of inaccurate filter factor estimation of an IN-subquery predicate that may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK79977) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM64315: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM64315 corrects a problem in which the filter factor for a compound predicate containing an OR predicate could be overestimated. The incorrect compound filter factor could result in an inefficient access path and resulting poor query 1 performance. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK80750) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM62712: See PM62712 APAR/PTF text for additional information about why a REBIND is necessary. PM62712 corrects a problem of choosing an inefficient range-list access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK79324) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM61658: See PM61658 APAR/PTF text for additional information about why a REBIND is necessary. PM61658 corrects a problem of over-estimated correlated subquery cardinality when global query optimization is enabled (OPTXQB=ON) and there are materialized views involved in the join between the parent query block and the correlated subquery. This may result in an inefficient access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK78278) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM61011: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM61011 corrects a problem in which DB2 incorrectly chooses to sort instead of using reverse index scan to avoid the sort when OPTIMIZE FOR 1 ROW is specified. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77766) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM59585: 1 A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM59585 corrects a problem in which an inefficient access path is selected when multiple highly selective indexes exist that can provide the same matching coverage. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK79618) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM56435: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PM56435 corrects a problem in which DB2 could compute an incorrect compound filter factor. This could lead to an inefficient access path and poor query performance. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77343) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM56355: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM56355 corrects a problem that DB2 may favor regular index scan over range list index scan while range list index scan is a more efficient access method for a query with data-dependent pagination. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK76457) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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 1 affected by this change.). ++ HOLD(UK76819) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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.). ++ HOLD(UK77003) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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(UK75450) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM54681: See PM54681 APAR/PTF text for additional information about why a REBIND is necessary. PM54681 corrects a problem of possibly getting an inefficient access path for a query with predicates referencing a column or columns where frequency or histogram statistics have been collected. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK75265) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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. 1 To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK74779) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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(UK76455) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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(UK74866) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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.). ++ HOLD(UK77642) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. 1 PM49539 corrects an ABEND 0CF when incorrect internal values may be used to recalculate the filter factor of the related RANGE or BETWEEN predicates at execution time. The incorrect internal values may be saved by DB2 at BIND/PREPARE time if the package is bound with REOPT(AUTO), and one or more queries in the package contain RANGE or BETWEEN predicate(s). To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK72974) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM48011: 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.). ++ HOLD(UK71709) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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(UK71025) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM40235: 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 1 affected by this change.). ++ HOLD(UK71000) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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.). ++ HOLD(UK71244) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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(UK69338) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM37547: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM37547 corrects a problem in which DB2 may calculate an incorrect filter factor for an after join predicate on a column defined as NOT NULL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK69335) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM37038: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM37038 corrects a problem in which DB2 may choose a poor access path for a query with a row expression predicate. 1 To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK67935) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM36392: See PM36392 APAR/PTF text for additional information about why a REBIND is necessary. PM36392 corrects a problem that the filter factor of an equal predicate may be inaccurate if histogram statistics exist on a column of that predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK67933) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM35585: See PM35585 APAR/PTF text for additional information about why a REBIND is necessary. PM35585 corrects a problem that a compound filter factor may be underestimated if multi-column histogram statistics exist. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK67416) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM34936: See PM34936 APAR/PTF text for additional information about why a REBIND is necessary. PM34936 corrects a problem where the DB2 optimizer may overestimate the composite size of a join when the query contains an OR predicate that can be applied to the newly resulting composite. To make this fix effective for a static application, it must 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(UK67932) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM32401: See PM32401 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM32401 corrects a problem of inaccurate filter factor estimation of a compound predicate containing an IN list predicate and an equal join predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK69998) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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.). ++ HOLD(UK66006) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (See PM30595 APAR/PTF text for additional information about why a REBIND is necessary. PM30595 corrects a problem in access method comparison when there is an index to support GROUP BY or ORDER BY order and the query block has OPTIMIZE FOR n ROWS or FETCH FIRST n ROWS ONLY, or it appears in an EXISTS-subquery predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK64628) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (See PM27699 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM27699 corrects a problem where an inefficient access path can be chosen when a compound predicate filter factor is underestimated. It usually happens when column group frequency statistics can be used to estimate compound predicate filter factor. To make this fix effective for a static application, it must 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(UK64003) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM26521: 1 See PM26521 APAR/PTF text for additional information about why a REBIND is necessary. PM26521 corrects a problem where the filter factor of an IS NULL predicate is underestimated as 1E-9 if there is a NULL value in the column, histogram statistics exist, but frequency statistics do not exist. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK66563) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (See PM26471 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM26471 fixes a problem where there is an efficient index access available but DB2 did not choose it. Instead, DB2 chose a multiple index access plan. It also fixes a problem where DB2 did not choose an efficent index list prefetch plan. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK65017) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM25934: See PM25934 APAR/PTF text for additional information about why a REBIND is necessary. PM25934 corrects a problem where the cost of a DPSI could be underestimated when multiple partitions are qualified. To make this fix effective for a static application, it must 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(UK65681) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM25554: See PM25554 APAR/PTF text for additional information about why a REBIND is necessary. PM25554 corrects a problem that DB2 may overestimate cost of an index access on a partition table if the index is a partitioning index and its first column matches an IN-list 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.). 1++ HOLD(UK64444) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 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.). ++ HOLD(UK65366) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PM24833: See PM24833 APAR/PTF text for additional information about why a REBIND is necessary. PM24833 corrects a problem that DB2 may choose a poorly performing index with list prefetch when other highly selective indexes exist. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK64520) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (See PM23073 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM23073 fixes a filter factor estimation problem for a LIKE predicate with MIXED data. The filter factor estimation problem could lead to a poor access path. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK63680) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (See PM22534 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. PM22534 corrects a storage overlay problem when star join is enabled and the number of internal tables created by star join processing exceeds the max number of tables supported by DB2. After the overlay occurs, various abends can happen. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK63049) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) 1 COMMENT (***Action for PM21335: See PM21335 APAR/PTF text for additional information about why a REBIND is necessary. PM21335 corrects a problem of in which an inefficient index may be selected for the leading table in a query block. This problem can occur if multiple highly selective candidate indexes exist. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17138) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI11937: See PI11937 APAR/PTF text for additional information about why a REBIND is necessary. PI11937 corrects a problem of SQL performance. DB2 may choose a range list index with less matching or 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.). ++ HOLD(UI17983) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI10812: A rebind is necessary to rebuild package structures based on the changes in this APAR. PI10812 corrects a problem that DB2 may not match as many columns as possible for a row-expression-IN-subquery predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17135) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI10323: See PI10323 APAR/PTF text for additional information about why a REBIND is necessary. PI10323 corrects a problem of ABEND04E RC00E70005 in DSNISRID when the query contains an equal predicate or IN-list predicate on a ROWID type column, and multiple indexes exist that provide high filtering. 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(UI15909) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI09579: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI09579 corrects a problem in which a multi-column frequency statistic containing an unqualified value may not be used to improve the compound filter factor. To make this fix effective for a static application, it must 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(UI17140) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI08856: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI08856 corrects a problem that a less efficient index may be selected while another index can match a superset of the of the matching and screening predicates of this index. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI15061) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (***Action for PI07262: See PI07262 APAR/PTF text for additional information about why a REBIND is necessary. PI07262 corrects a problem of SQL performance where the DB2 optimizer may favor range list index scan with data page access over index-only access. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK94952) SYS FMID(HDBAA10) REASON(ACTION) DATE(14135) COMMENT (PM87836 does not correct the incorrect values that are already in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE. The incorrect values may or may not be readily identifiable as incorrect by simple visual inspection. To get the correct values, apply this fix. Then, delete the old rows in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE. 1 EXPLAIN the statements again to re-populate the DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE with the correct values.). ++ HOLD(UK80414) SYS FMID(HDBAA10) REASON(ACTION) DATE(14135) COMMENT (***Action for PM65872: See PM65872 APAR/PTF text for additional information about why a REBIND is necessary. PM65872 corrects a problem of infinite loop that can occur when there are a very large number of predicates, and items in the SELECT list, and at least one predicate is an equal-, ANY-, or IN-subquery. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18020 HOLD DATA END UI18032 HOLD DATA START ++ HOLD(UI17092) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14135) COMMENT (A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PI10961 corrects a performance problem where a suboptimal access plan may be chosen when pair-wise join and parallelism is enabled. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18032 HOLD DATA END UI18057 HOLD DATA START ++ HOLD(UI18057) SYS FMID(HDBAA10) REASON(DOC) DATE(14136) COMMENT (PI14970 introduces the following documentation changes : A footnote will be added to the description of the TIMESTAMP scalar function for "expression-1" after the following sentence : "A character string or graphic string with an actual length of 14 that represents a valid date and time in the form  yyyyxxddhhmmss, where yyyy is the year, xx is the month, dd is the day, hh is the hour, mm is the minute, and ss is the seconds." Footnote = "A character or graphic string with an actual length of 14 that represents a valid date and time (as allowed for the 1 TIMESTAMP function) is also allowed as input to other scalar functions that accept a timestamp as an input argument." Information about this new/changed function/option/ZPARM/ variable/message/code 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.). UI18057 HOLD DATA END UI18073 HOLD DATA START UI18073 HOLD DATA END UI18116 HOLD DATA START UI18116 HOLD DATA END UI18121 HOLD DATA START UI18121 HOLD DATA END UI18127 HOLD DATA START UI18127 HOLD DATA END UI18145 HOLD DATA START UI18145 HOLD DATA END UI18155 HOLD DATA START UI18155 HOLD DATA END UI18163 HOLD DATA START ++ HOLD(UI18163) SYS FMID(HDBAA10) REASON(DOC) DATE(14140) COMMENT (PI13725 introduces the following changes to externals: The DB2 for z/OS SQL Reference will be updated to include a VALUES clause as a form of a fullselect. This form of VALUES clause is allowed outside a trigger only with the following rules: 1. V10 New Function Mode (NFM) must be in effect. 2. A VALUES clause must be dynamically prepared via a cursor. 3. The VALUES clause must contain simple references of sequences only. 4. The VALUES clause must be a stand-alone query without other clauses. 5. The result of the VALUES clause must be fetched via the cursor to invoke the sequence references. Refer to the DB2 for z/OS SQL Reference for the details. 1 Here is an example in a PLI application: DCL HV1 FIXED BIN(31); DCL HV2 FIXED BIN(31); EXEC SQL DECLARE C1 CURSOR FOR VALUES_STMT; EXEC SQL PREPARE VALUES_STMT FROM 'VALUES (NEXTVAL FOR SQM38201, NEXTVAL FOR SQM38202)' ; EXEC SQL OPEN C1; EXEC SQL FETCH C1 INTO :HV1, :HV2; EXEC CLOSE C1; For the DESCRIBE OUTPUT statement, if the statement-name (in the syntax) refers to a fullselect (by way of a prepared select-statement) that is actually a VALUES clause, the DESCRIBE statement will return information about the result of the VALUES clause. Because the VALUES clause, as a form of fullselect, must be dynamically prepared, it is a candidate to cache if the dynamic statement cache is enabled, hence, it is visible when EXPLAIN STMTCACHE is specified or the special register CURRENT EXPLAIN MODE is set to YES or EXPLAIN. However, the new VALUES clause is NOT considered an explainable statement. If you specify the VALUES clause for explainable-SQL-statement in EXPLAIN PLAN | ALL statement, you will receive SQLCODE -104. The select-statement in a FOR statement (SQL control statement) must not be a fullselect that is a VALUES clause. Information about this change in the DB2 for z/OS SQL Reference will be included in the Information Management Software for z/OS Solutions Information Center at a later date.). UI18163 HOLD DATA END UI18183 HOLD DATA START ++ HOLD(UI18183) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14141) COMMENT (PI16179 is a pre-conditioning APAR that includes changes to support a functional code change that will be enabled via APAR PI08409 at a later date. At this time, all of the changes are transparent to the user. In a data sharing group, this pre- conditioning APAR(PI16179) should be applied to all members before the later enabling APAR PI08409 is applied to any member. 1 The code change is not enabled until the enabling APAR PI08409 is applied. PI08409 corrects a problem of performance regression for static SQL queries when an inefficient access path is selected but instead a more efficient range list access path exists. The problem can occur when a predicate eligible for index matching in a range list leg references a timestamp column. Please note, an incorrect result could occur if the pre- conditioning APAR(PI16179) is not applied to all members prior to applying the enabling APAR(PI08409) to any member in a data sharing group.). UI18183 HOLD DATA END UI18186 HOLD DATA START UI18186 HOLD DATA END UI18219 HOLD DATA START UI18219 HOLD DATA END UI18239 HOLD DATA START UI18239 HOLD DATA END UI18276 HOLD DATA START ++ HOLD(UI18276) SYS FMID(HDBAA10) REASON(ACTION) DATE(14143) COMMENT (The APAR PI13518 fixes the problem that SQLCODE -433 will be issued when the encoding field in the XML prolog is not UTF-8. To make this change effective, the WLM environment must be refreshed after the application of the PTF. Issue the following VARY MVS command from the console to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment for running the SYSFUN.XSLTRANSFORM UDF.). UI18276 HOLD DATA END UI18285 HOLD DATA START UI18285 HOLD DATA END UI18288 HOLD DATA START UI18288 HOLD DATA END UI18294 HOLD DATA START UI18294 HOLD DATA END 1 UI18332 HOLD DATA START UI18332 HOLD DATA END UI18334 HOLD DATA START UI18334 HOLD DATA END UI18336 HOLD DATA START UI18336 HOLD DATA END UI18350 HOLD DATA START UI18350 HOLD DATA END UI18360 HOLD DATA START UI18360 HOLD DATA END UI18374 HOLD DATA START UI18374 HOLD DATA END UI18378 HOLD DATA START ++ HOLD(UI18378) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14148) COMMENT (***Action for PI13532: See PI13532 APAR/PTF text for additional information about why a REBIND is necessary. PI13532 corrects a problem that the abend 04E-00C90101 at DSNIOST2:5001 may occur when parallelism incorrectly builds the index key length for child task. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18378 HOLD DATA END UI18391 HOLD DATA START UI18391 HOLD DATA END UI18394 HOLD DATA START UI18394 HOLD DATA END UI18421 HOLD DATA START UI18421 HOLD DATA END UI18433 HOLD DATA START 1++ HOLD(UI18433) SYS FMID(J2AG210) REASON(ACTION) DATE(14149) COMMENT (After the application of this apar/ptf, the DB2 subsystem needs to be refreshed so it can pickup the changes for the DSN5SFNC module.). UI18433 HOLD DATA END UI18446 HOLD DATA START UI18446 HOLD DATA END UI18472 HOLD DATA START UI18472 HOLD DATA END UI18486 HOLD DATA START UI18486 HOLD DATA END UI18488 HOLD DATA START UI18488 HOLD DATA END UI18492 HOLD DATA START UI18492 HOLD DATA END UI18497 HOLD DATA START ++ HOLD(UK93041) SYS FMID(HDBAA10) REASON(DOC) DATE(14153) COMMENT (The fix for APAR PM77340 has an associated change to the DB2 documentation, similar to the following: Under Section "Defining the SQL communications area, SQLSTATE, and SQLCODE in REXX", the following text: If you use the ADDRESS DSNREXX "CONNECT" ssid syntax to connect to DB2, the SQLCA variables are a set of simple variables. If you use the CALL SQLDBS "ATTACH TO" syntax to connect to DB2, the SQLCA variables are compound variables that begin with the stem SQLCA. is changed to the following: The SQLCA has the following forms: A set of simple variables A set of compound variables that begin with the stem SQLCA The simple variables is the default form of the SQLCA. Using CALL SQLEXEC results in the compound stem variables. Otherwise, the attachment command used determines the form of the SQLCA. If you use the ADDRESS DSNREXX 'CONNECT' ssid syntax to connect to DB2, the SQLCA variables are a set of simple variables. If you use the CALL SQLDBS 'ATTACH TO' 1 syntax to connect to DB2, the SQLCA variables are compound variables that begin with the stem SQLCA. Switching forms of the SQLCA within an application is not recommended. Under section "Accessing the DB2 REXX language support application programming interfaces" The SQLDBS and SQLEXEC forms of the DSNREXX commands were described as: CALL SQLDBS 'ATTACH TO' ssid is equivalent to ADDRESS DSNREXX 'CONNECT' ssid. CALL 'SQLEXEC' "SQL-statement" is equivalent to ADDRESS DSNREXX 'EXECSQL' "SQL-statement". CALL SQLDBS 'DETACH' is equivalent to ADDRESS DSNREXX 'DISCONNECT'. These are changed to the following: CALL SQLDBS 'ATTACH TO' ssid is an alternative to ADDRESS DSNREXX 'CONNECT' ssid. CALL 'SQLEXEC' "SQL-statement" is an alternative to ADDRESS DSNREXX 'EXECSQL' "SQL-statement". CALL SQLDBS 'DETACH' is an alternative to ADDRESS DSNREXX 'DISCONNECT'.). UI18497 HOLD DATA END UI18526 HOLD DATA START UI18526 HOLD DATA END UI18528 HOLD DATA START UI18528 HOLD DATA END UI18537 HOLD DATA START ++ HOLD(UI18537) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (***Action for PI16826: See PI16826 APAR/PTF text for additional information about why a REBIND is necessary. PI16826 corrects a problem of SQLCODE -404 issued incorrectly when an SQL statement contains set operations, multiple common table expressions which include OUTER JOIN where column defined with NOT NULL are referenced. 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.). UI18537 HOLD DATA END UI18548 HOLD DATA START ++ HOLD(UI18548) SYS FMID(HIZAA10) REASON(ACTION) DATE(14155) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). UI18548 HOLD DATA END UI18553 HOLD DATA START ++ HOLD(UI14198) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (See PM99167 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PM99167 corrects problems that can cause abend for a query running with GROUP BY and OLAP function and there is no column in the select list. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK96107) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (See PM92612 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM92612 corrects a problem that can cause an ABEND04E at DSNIDM.DSNIWKFL:5009 when running a query that contains an OLAP function and select list that involves VARCHAR and TIMESTAMP WITH TIME ZONE columns. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83553) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (See PM72976 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. Apar PM72976 corrects a problem that can cause an ABEND04E RC00C90101 at DSNIDM.DSNONLLE:5003 when running a query that 1 contains an OLAP function and a group by clause that references a LOB column. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI18553) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (See PI11594 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PI11594 corrects problems that can cause abend for a query containing a SET function and an OLAP function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI14121) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (See PI05269 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PI05269 corrects a problem that can cause an abend when executing a query that contains an OLAP function, an order by, and an IN-subquery 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.). UI18553 HOLD DATA END UI18558 HOLD DATA START ++ HOLD(UK70809) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (***Action for PM38025: See PM38025 APAR/PTF text for additional information about why a REBIND is necessary. PM38025 corrects a problem of incorrect output when like predicate is used as matching predicate and column is created with mixed data. To make this fix effective for a static application, it must 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(UI18558) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14155) COMMENT (PI16101 corrects a problem where parallelism may incorrectly build the index key range for the child tasks when the query involves sort merge join and there is an IN predicate. As a 1 result, an abend may occur during execution if the data in the rows falls outside the incorrectly built index key range. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18558 HOLD DATA END UI18568 HOLD DATA START UI18568 HOLD DATA END UI18570 HOLD DATA START UI18570 HOLD DATA END UI18574 HOLD DATA START ++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(14155) 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.). UI18574 HOLD DATA END UI18579 HOLD DATA START ++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(14156) 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.). UI18579 HOLD DATA END 1 UI18608 HOLD DATA START UI18608 HOLD DATA END UI18639 HOLD DATA START UI18639 HOLD DATA END UI18668 HOLD DATA START UI18668 HOLD DATA END UI18674 HOLD DATA START ++ HOLD(UK97146) SYS FMID(HDBAA10) REASON(DOC) DATE(14157) COMMENT (PM73388 introduces the following changes to externals: DB2 10 for z/OS SQL Reference: ALTER TABLESPACE, Notes Section: Invalidation of packages: All of the packages that refer to that table space are invalidated when any of the following conditions are true: ... - When increasing the MAXPARTITIONS attribute of a . DB2 10 for z/OS Application programming and SQL: New row added to Table 1. Changes that require packages to be rebound. Change made: ALTER TABLESPACE with MAXPARTITIONS to increase the maximum number of partitions Required Action: No action is required. DB2 automatically rebinds invalidated plans or packages. This is not the final version of changes. Information about these changes will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). UI18674 HOLD DATA END UI18701 HOLD DATA START UI18701 HOLD DATA END UI18705 HOLD DATA START ++ HOLD(UI12310) SYS FMID(H2AF210) REASON(ACTION) DATE(14160) COMMENT (This PTF should be applied only by customers that ordered 1 and installed DB2 Accessories Suite Version 3 Release 1, as it adds member DSN5NOT3 in the SDSNNOTC target library, and this notices file reflects the components and functions delivered with your order of DB2 Accessoires Suite V3. You should not apply this PTF unless you are a licensed customer DB2 Accessories Suite Version 3 Release 1.). ++ HOLD(UI18705) SYS FMID(H2AF210) REASON(ACTION) DATE(14160) COMMENT (This PTF should be applied only by customers that ordered and installed DB2 Accessories Suite Version 3 Release 2 as it updates member DSN5NOT3 in the SDSNNOTC target library and this notices file reflects the components and functions delivered with your order of DB2 Accessories Suite Version 3 Release 2. You should not apply this PTF unless you are a licensed customer of DB2 Accessories Suite Version 3 Release 2.). UI18705 HOLD DATA END UI18723 HOLD DATA START UI18723 HOLD DATA END UI18727 HOLD DATA START ++ HOLD(UI12294) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14161) COMMENT (***Action for PM90617: See PM90617 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PM90617: (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(ADD) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSNA10.SDSNDBRM') (c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). ++ HOLD(UK97958) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14161) COMMENT ( ***Action for PM88775: See PM88775 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PM88775: (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(ADD) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSNA10.SDSNDBRM') (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). ++ HOLD(UI15181) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14161) COMMENT (***Action for PI06664: See PI06664 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PI06664: (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) - 1 ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSNA10.SDSNDBRM') (c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). ++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(DOC) DATE(14161) COMMENT (PM74794 introduces the following changes to the DB2 10 for z/OS Utility Guide and Reference - Appendix B. DB2-supplied stored procedures for utility operations Section - DSNACCOX stored procedure Chapter - DSNACCOX output Table 145 - Result set row for second DSNACCOX result set | NAME VARCHAR(128) Table space name, index name, or | index space name. Index space | name is used if the row is added | as a result of checking a | restricted state and the index | name is not available at the time. Information about this changed information will be included in the Information Management Software for z/OS Solutions Information Center (http://publib.boulder.ibm.com/infocenter/imzic) at a later date.). ++ HOLD(UI12294) SYS FMID(HDBAA10) REASON(ACTION) DATE(14161) COMMENT (***Action for PM90617: See PM90617 APAR/PTF text for additional information. After applying the fix for PM90617, DSNACCOX will reverse the recommendation based on percentage criterion on an object with TOTALROWS or TOTALENTRIES of zero. If TOTALROWS or TOTALENTRIES is zero, we now rely on the related absolute criteria.). ++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(ACTION) DATE(14161) COMMENT ( ***Action for PM74794: See PM74794 APAR/PTF text for additional information. Post-apply actions after applying the fix for APAR PM74794: (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity (b) Rebind package for DSNACCOX. An example on how to do this is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name. (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity). ++ HOLD(UK79842) SYS FMID(HDBAA10) REASON(ACTION) DATE(14161) COMMENT (After you apply the PTF for APAR PM61574, Non Partitioned Index 1 is no longer recommended for reorg or runstats when chklevel 32 is specified and any of the ts partitioned is recommended for reorg or runstats.). ++ HOLD(UI18727) SYS FMID(HDBAA10) REASON(ACTION) DATE(14161) COMMENT (The package for DSNACCOX needs to be bound after applying the fix for APAR PI15366. An example of how to do this is: BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) - ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) - LIBRARY('DSN!!0.SDSNDBRM') Change 'DSN!!0' to the prefix of your target library name.). ++ HOLD(UI15181) SYS FMID(HDBAA10) REASON(ACTION) DATE(14161) COMMENT (PLEASE NOTE: After applying the fix for APAR PI06664, DSNACCOX will reverse the recommendation based on percentage criterion on the object with TOTALROWS or TOTALENTRIES of zero. If the TOTALROWS or TOTALENTRIES is zero, we now rely on the related absolute criteria.). UI18727 HOLD DATA END UI18730 HOLD DATA START UI18730 HOLD DATA END UI18732 HOLD DATA START UI18732 HOLD DATA END UI18756 HOLD DATA START UI18756 HOLD DATA END UI18766 HOLD DATA START ++ HOLD(UI18766) SYS FMID(HDBAA10) REASON(ACTION) DATE(14162) COMMENT (***Action for PI13612 (DB2 V10) This PTF modifies the DB2 installation process as follows to support IBM Enterprise COBOL for z/OS Version 5.1 (COBOL V5.1): * DB2 installation job DSNTIJIN now creates prefix.RUNLIB.LOAD, the sample application load module library, as a PDSE rather than a PDS because programs compiled by COBOL V5.1 can be bound only as program objects and program objects are not supported by PDSs. * DB2 installation panel DSNTIPU now has a new field, COBOL LE PRELINKER PHASE, for indicating whether preparation of COBOL programs should include a prelink phase. Choices are YES (the default) and NO. For COBOL V5.1, specify NO because programs compiled by COBOL V5.1 must be bound directly as program objects. * When you specify NO in the new COBOL LE PRELINKER PHASE field on panel DSNTIPU, during editing of the DSNHICOB language JCL 1 proc in DB2 installation job DSNTIJMV, the installation CLIST: - inserts DD statements for additional work files used by COBOL V5.1 in the compiler proc step and - removes the prelinker proc step Also, during editing of the DB2 IVP job DSNTEJ5C, the installation CLIST sets the DSNH PRELINK option to NO. This PTF modifies the DSNHC CLIST (compiler invocation for the DSNH program preparation CLIST) to allocate additional work files needed by COBOL V5.1, and to use a work file data set defined as RECFM=FB,LRECL=80 to pass object code from the COBOL compiler to the prelinker or link-editor. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Copy updated DB2 installation panels to alternate libraries (3) Update private copies of the DSNTIDxx CLIST input member (4) Update your customized copy of job DSNTIJIN (5) Update your customized copy of job DSNTIJMV (6) Update your customized copy of job DSNTEJ5C Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all DB2 V10 customers. This PTF modifies CLIST members DSNHC, DSNTINST, DSNTINS1, DSNTINS2, and DSNTINS3 in the prefix.SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your 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 DB2 V10 customers who maintain copies of the DB2 installation panels outside of SMP/E. This PTF modifies DB2 installation panel DSNTIPU 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 DSNTIPU panel to that library. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ==> This action is required for all DB2 V10 customers. This PTF adds an entry for the new COBOL LE PRELINKER PHASE field on installation panel DSNTIPU to the CLIST 1 default input member, DSNTIDXA, in the prefix.SDSNSAMP target library. You need to add this entry to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: ICOBPRLK CHAR M NO YES Change to NO if you want the DB2 installation CLIST to configure installation jobs for COBOL V5.1. Otherwise, change to YES. ---------------------------------------------------------------- (4) Update your customized copy of job DSNTIJIN ==> This action is required for all DB2 V10 customers who maintain a private copy of job DSNTIJIN. This PTF changes the allocation of prefix.RUNLIB.LOAD, the DB2 sample application library, from a PDS to a PDSE. After applying this PTF, edit your customized copy of DSNTIJIN and locate job step DSNTNOV. If this job step is not present, disregard the remainder of this action item. Otherwise, locate the RUNLIB DD statement and add this parameter: DSNTYPE=LIBRARY Also change the DCB statement from DCB=BLKSIZE=6233 to DCB=(RECFM=U,LRECL=0,BLKSIZE=32760) ---------------------------------------------------------------- (5) Update your customized copy of job DSNTIJMV ==> This action is required for all DB2 V10 customers who maintain a private copy of job DSNTIJMV and use COBOL V5.1 to prepare DB2 COBOL programs. Edit your customized copy of DSNTIJMV and locate the embedded DSNHICOB JCL proc. If this proc is not present disregard the remainder of this action item. Otherwise: (a) In proc step COB of the DSNHICOB proc, add the following DD statements: //SYSUT8 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT9 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT10 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT11 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT12 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT13 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT14 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSUT15 DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), // UNIT=SYSDA //SYSMDECK DD SPACE=(800,(&WSPC,&WSPC),,,ROUND), 1 // UNIT=SYSDA (b) Delete proc step PLKED of the DSNHICOB proc (c) In proc step LKED of the DSNHICOB proc, change this: //SYSLIN DD DSN=&&PLKSET,DISP=(OLD,DELETE) to this: //SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE) If you have not already done so, you can use steps (a), (b), and (c) to convert the DSNHICOB proc in your system proclib to support COBOL V5.1. Note that for COBOL V5.1 all data sets allocated by the SYSLMOD DD of proc step LKED, either directly or by JCL override, must be a PDSE not a PDS. ---------------------------------------------------------------- (6) Update your customized copy of job DSNTEJ5C ==> This action is required for all DB2 V10 customers who maintain a private copy of job DSNTEJ5C and use COBOL V5.1 to prepare DB2 COBOL programs. Edit your customized copy of DSNTEJ5C and change all three occurrences of: PRELINK(YES) to: PRELINK(NO)). UI18766 HOLD DATA END UI18772 HOLD DATA START UI18772 HOLD DATA END UI18782 HOLD DATA START UI18782 HOLD DATA END UI18806 HOLD DATA START UI18806 HOLD DATA END UI18820 HOLD DATA START UI18820 HOLD DATA END UI18850 HOLD DATA START ++ HOLD(UI17622) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14167) COMMENT (***Action for PI15176: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI15176 corrects a problem in which DB2 may not read in multi-column frequency and/or histogram statistics for a table referenced more than once in a query. This could lead to an inefficient access path and poor query performance. 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(UI18378) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14167) COMMENT (***Action for PI13532: See PI13532 APAR/PTF text for additional information about why a REBIND is necessary. PI13532 corrects a problem that the abend 04E-00C90101 at DSNIOST2:5001 may occur when parallelism incorrectly builds the index key length for child task. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18850 HOLD DATA END UI18907 HOLD DATA START UI18907 HOLD DATA END UI18914 HOLD DATA START UI18914 HOLD DATA END UI18957 HOLD DATA START ++ HOLD(UI18957) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14169) COMMENT (***Action for PI16442: See PI16442 APAR/PTF text for additional information about why a REBIND is necessary. PI16442 corrects a problem with the WHEN clause in a BEFORE or AFTER trigger if the WHEN clause references the name of a column of the triggering table and one of the following conditions is true: 1. The referenced name is qualified by the triggering table name where the name is different from the OLD or NEW correlation name. 2. The referenced name is not qualified by the OLD or NEW correlation name and the OLD or NEW correlation name is defined. Examples: (corresponding to the cases just mentioned) 1. CREATE TRIGGER TRIG1 NO CASCADE BEFORE UPDATE OF C1 ON T1 REFERENCING OLD AS OLD_ROW NEW AS NEW_ROW 1 FOR EACH ROW MODE DB2SQL WHEN(NEW_ROW.C1 = (SELECT T1.C2 FROM SYSIBM.SYSDUMMY1)) ... Currently T1.C2 should have received SQLCODE -206, but it is left unresolved. The result of the trigger is unpredictable. After application of the PTF, the above trigger must be rebound to receive SQLCODE -206. 2. CREATE TRIGGER TRIG2 NO CASCADE BEFORE UPDATE OF C1 ON T1 REFERENCING OLD AS OLD_ROW NEW AS NEW_ROW FOR EACH ROW MODE DB2SQL WHEN(NEW_ROW.C1 = (SELECT C2 FROM SYSIBM.SYSDUMMY1)) ... Currently C2 should have received SQLCODE -203, but it is left unresolved. The result of the trigger is unpredictable. After application of the PTF, the above trigger must be rebound to receive SQLCODE -203. To make this fix effective for a trigger, the trigger package must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, trigger packages could be affected by this change.). ++ HOLD(UI18957) SYS FMID(HDBAA10) REASON(ACTION) DATE(14169) COMMENT (This PTF corrects a problem with the WHEN clause in a BEFORE or AFTER trigger if the following conditions are true: 1. The WHEN clause references the name of a column from the triggering table. 2. The referenced name is qualified by the OLD or NEW correlation name and the OLD or NEW correlation name is the same as the triggering table name. Here are examples: CREATE TABLE T1(C1 INT, C2 INT); CREATE TRIGGER TRIG1 NO CASCADE BEFORE UPDATE OF C1 ON T1 REFERENCING OLD AS OLD_ROW NEW AS T1 FOR EACH ROW MODE DB2SQL WHEN(OLD_ROW.C1 = T1.C2) ... 1 CREATE TRIGGER TRIG2 NO CASCADE BEFORE UPDATE OF C1 ON T1 REFERENCING OLD AS OLD_ROW NEW AS T1 FOR EACH ROW MODE DB2SQL WHEN(OLD_ROW.C1 = (SELECT T1.C2 FROM SYSIBM.SYSDUMMY1)) ... Currently T1.C2 should have been resolved to a new transition variable but it's left unresolved. The result of the triggers is unpredictable. After application of the PTF, the above triggers must be dropped and recreated immediately. In the above examples, after recreate T1.C2 will be resolved to the new transition variable.). UI18957 HOLD DATA END UI18960 HOLD DATA START UI18960 HOLD DATA END UI18990 HOLD DATA START UI18990 HOLD DATA END UI18992 HOLD DATA START UI18992 HOLD DATA END UI18994 HOLD DATA START ++ HOLD(UI18994) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14170) COMMENT (***Action for PI13727: See PI13727 APAR/PTF text for additional information about why a REBIND is necessary. PI13727 corrects a problem of DSNT501I message (RUA REASON 0000006C) or an ABEND ABENDS0C4 00000004 RC04 in DSNISRID. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI18994 HOLD DATA END UI19024 HOLD DATA START UI19024 HOLD DATA END UI19027 HOLD DATA START UI19027 HOLD DATA END 1 UI19029 HOLD DATA START UI19029 HOLD DATA END UI19037 HOLD DATA START UI19037 HOLD DATA END UI19043 HOLD DATA START UI19043 HOLD DATA END UI19070 HOLD DATA START UI19070 HOLD DATA END UI19075 HOLD DATA START UI19075 HOLD DATA END UI19080 HOLD DATA START ++ HOLD(UI19080) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14175) COMMENT (***Action for PI13724 (DB2 10) This PTF adds a new DB2 subsystem parameter called SUPPRESS_HINT_SQLCODE_DYN that can be used to specify how DB2 should handle the SQLCODE when optimization hints are applied for a dynamic SQL execution. Static queries and dynamic EXPLAIN statements are not affected. Valid settings are: - NO : Means that DB2 will return SQLCODE +394 (if all hints are used) or SQLCODE +395 (if any hint was invalid). ==> This is the default setting - STMT: Means that DB2 will suppress SQLCODEs +394 and +395 for statement level optimization hints if a statement level hint is applied successfully or unsuccessfully for a dynamic SQL execution. - ALL : Means that DB2 will suppress SQLCODEs +394 and +395 for all optimization hints, including statement level optimization hints and classic PLAN_TABLE optimization hints, even if the hint is applied successfully or unsuccessfully for a dynamic SQL execution. If you have already installed or migrated to DB2 10, you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Update the package for DSNTXAZP 1 Detailed guidance for these actions follows: --------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ==> This action is required for all customers This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. --------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ==> This action is required for all customers This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter SUPPRESS_HINT_SQLCODE_DYN= (where is NO, STMT, or ALL) to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. If you omit adding SUPPRESS_HINT_SQLCODE_DYN 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 SUPPRESS_HINT_SQLCODE_DYN to the CLIST default input member, DSNTIDXA, in the SDSNSAMP target library. You need to add this entry to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following line: SUPPRESS_HINT_SQLCODE_DYN CHAR M NONE NONE Change to the value you specified for SUPPRESS_HINT_SQLCODE_DYN in step (2), above. --------------------------------------------------------------- (4) Update the package for DSNTXAZP ==> This action is required for all customers who use DSNTXAZP to update DB2 CLIST input (DSNTIDXX) members Submit a job that contains the following BIND statement: BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) - ACTION(ADD) ENCODING(EBCDIC) - LIBRARY('prefix.SDSNDBRM') 1 where is the high-level qualifier for the DB2 subsystem target libraries. ---------------------------------------------------------------). UI19080 HOLD DATA END UI19105 HOLD DATA START ++ HOLD(UI19105) SYS FMID(HDBAA10) REASON(DOC) DATE(14175) COMMENT (*** Documentation for PI17163 *** The following new reason code is added to the DB2 Codes manual. 00D34451 Explanation: A remote application connected to a DB2 server and issued an SQL statement that contains a three-part name or alias that refers to a table or view at a remote location. However, the remote reference actually resolves to the local DB2 server location. This situation can occur when the SQL statement refers to a location alias but the package for the application was bound before the location alias was defined. System action: The SQL statement is rejected. User response: Bind the application package at the server after the location alias has been defined. For a data sharing group, ensure that the location alias is defined on all members. Problem determination: Use the -DISPLAY DDF command to determine the location aliases for the server. Ensure that any location alias references in the application exist at the server when the package is bound.). UI19105 HOLD DATA END UI19116 HOLD DATA START UI19116 HOLD DATA END UI19119 HOLD DATA START ++ HOLD(UI19119) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14175) COMMENT (***Action for PI18121: See PI18121 APAR/PTF text for additional information about why a REBIND is necessary. PI18121 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS DSNXRNUM M115 or incorrect SQLCODE -420 could happen for an SQL statement containing a subquery predicate with a DECFLOAT column or a column implicitly cast to DECFLOAT, when the subquery contains ORDER BY on a column that is not in the select list. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17349) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14175) COMMENT (***Action for PI10708: See PI10708 APAR/PTF text for additional information about why a REBIND is necessary. PI10708 corrects a problem of ABEND04E RC00C90101 DSNOTFLA ERQUAL5004. This abend may occur for an SQL statement that contains a CONCAT built-in function or a CONCAT operator and the argument of the CONCAT operation is a LOB 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.). UI19119 HOLD DATA END UI19125 HOLD DATA START UI19125 HOLD DATA END UI19129 HOLD DATA START ++ HOLD(UI19129) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14176) COMMENT (***Action for PI19010: See PI19010 APAR/PTF text for additional information about why a REBIND is necessary. PI19010 corrects a problem of ABEND0C4 RC00E70005 at location DSNXRRP OFFSETM110 can occur for an SQL statement that contains an after join or during join predicate which contains a timestamp column and a string host variable. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI19129 HOLD DATA END UI19136 HOLD DATA START UI19136 HOLD DATA END UI19138 HOLD DATA START UI19138 HOLD DATA END UI19141 HOLD DATA START UI19141 HOLD DATA END 1UI19147 HOLD DATA START UI19147 HOLD DATA END UI19153 HOLD DATA START UI19153 HOLD DATA END UI19159 HOLD DATA START ++ HOLD(UI19159) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14177) COMMENT (***Action for PI17479: See PI17479 APAR/PTF text for additional information about why a REBIND is necessary. PI17479 corrects a problem that incorrect output could happen for an SQL statement with a scalar-fullselect containing a table expression or view with UNION ALL, when the SELECT item of the scalar-fullselect is NOT NULL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17994) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14177) COMMENT (***Action for PI13861: See PI13861 APAR/PTF text for additional information about why a REBIND is necessary. PI13861 corrects a problem of ABEND04E RC00E70005 at location DSNXGRDS DSNXSINE M103 or DSNXSZK M103 when a SELECT statement references SYSIBM.SYSDUMMY1, SYSIBM.SYSDUMMYE, SYSIBM.SYSDUMMYA, or SYSIBM.SYSDUMMU tables and contains OLAP specification. To make this fix effective for a static application, it must 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(UI17944) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14177) COMMENT (***Action for PI09729: See PI09729 APAR/PTF text for additional information about why a REBIND is necessary. PI09729 corrects a problem that ABEND04E RC00E70005 at the location DSNXGRDS DSNXRDEC P005, DSNXRSBC P041, DSNXRINT P026, DSNXRTIM P016 or DSNXRDOU P011 could happen for an SQL statement satisfying all of the following conditions: 1. It contains a table expression or view with UNION ALL. 2. It contains a predicate with a host variable or parameter marker. 1 3. The predicate is on a column from the table expression or view. 4. The columns of the predicate in the UNION branches have different nullabilties. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI19159 HOLD DATA END UI19196 HOLD DATA START UI19196 HOLD DATA END UI19207 HOLD DATA START ++ HOLD(UI17624) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14177) COMMENT (See PI14495 APAR/PTF text for additional information about why a REBIND is necessary. PI14495 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 routes to an IBM DB2 Analytics Accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must 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(UI19207) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14177) COMMENT (***Action for PI14368: See PI14368 APAR/PTF text for additional information about why a REBIND is necessary. PI14368 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 routes to an accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must 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(UI17690) SYS FMID(HDBAA10) REASON(ACTION) DATE(14177) COMMENT (***Action for PI16184: See PI16184 APAR/PTF text for additional information about why a REBIND is necessary. PI16184 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 1 routes to an IBM DB2 Analytics Accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI19207 HOLD DATA END UI19223 HOLD DATA START ++ HOLD(UI19223) SYS FMID(HDBAA10) REASON(ACTION) DATE(14178) COMMENT (This APAR requires that z/OS APAR OA44779 is installed for the DB2 changes to be fully effective. When z/OS APAR OA44779 and this DB2 APAR PI10964 are both installed DB2 should be stopped and started so DB2 RRSAF will obtain the new RRS installed function flags.). UI19223 HOLD DATA END UI19226 HOLD DATA START UI19226 HOLD DATA END UI19251 HOLD DATA START UI19251 HOLD DATA END UI19257 HOLD DATA START UI19257 HOLD DATA END UI19260 HOLD DATA START UI19260 HOLD DATA END UI19265 HOLD DATA START ++ HOLD(UI19265) SYS FMID(HDBAA10) REASON(ACTION) DATE(14181) COMMENT (The PTF for APAR PI11839 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.). UI19265 HOLD DATA END UI19269 HOLD DATA START 1UI19269 HOLD DATA END UI19271 HOLD DATA START UI19271 HOLD DATA END UI19299 HOLD DATA START ++ HOLD(UI13850) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14182) COMMENT (PM99313 corrects a problem of incorrect output returned when query contains a UNION ALL clause in its subquery predicate.). ++ HOLD(UI19299) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14182) COMMENT (See PI18013 APAR/PTF text in the PTF cover letter for additional information about why a REBIND is necessary. APAR PI18013 corrects problems that can cause abend for a query containing a XML column inside a MQB or an uncorrelated scalar full select. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI17278) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14182) COMMENT (PI14858 corrects an incorrect output problem that may occur when a query containing EXISTS or IN and set function in subquery without the GROUP BY or HAVING clause.). UI19299 HOLD DATA END UI19307 HOLD DATA START UI19307 HOLD DATA END UI19317 HOLD DATA START UI19317 HOLD DATA END UI19320 HOLD DATA START UI19320 HOLD DATA END UI19326 HOLD DATA START UI19326 HOLD DATA END UI19328 HOLD DATA START UI19328 HOLD DATA END UI19330 HOLD DATA START ++ HOLD(UI19330) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14183) COMMENT 1 (***Action for PI19360: See PI19360 APAR/PTF text for additional information about why a REBIND is necessary. PI19360 corrects the following 2 problems: An ABND0C7 RC00000000 at location DSNXGRDS.DSNXRSGB OFFSET768E may occur when an SELECT statement satisfies the following conditions: 1. query contains SUM or AVG function with an argument of DEC function. 2. there is only one argument whose data type is DECFLOAT in the DEC function. 3. query contains GROUP BY clause. Incorrect output may occur when an SQL statement satisfies the following conditions: 1. statement contains SUM or AVG function with an argument of DEC function. 2. there is only one argument whose data type is DECFLOAT in the DEC function. 3. the precision of DECFLOAT value is greater than 15. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI19330) SYS FMID(HDBAA10) REASON(ACTION) DATE(14183) COMMENT (PI19360 corrects the following 2 problems: An ABND0C7 RC00000000 at location DSNXGRDS.DSNXRSGB OFFSET768E may occur when an SELECT statement satisfies the following conditions: 1. query contains SUM or AVG function with an argument of DEC function. 2. there is only one argument whose data type is DECFLOAT in the DEC function. 3. query contains GROUP BY clause. Incorrect output may occur when an SQL statement satisfies the following conditions: 1. statement contains SUM or AVG function with an argument of DEC function. 2. there is only one argument whose data type is DECFLOAT in the DEC function. 3. the precision of DECFLOAT value is greater than 15. To make this fix effective for any MQT(materialized query table) that contain the pattern described above and are created in V9 later, the objects must be dropped and recreated after application of this PTF. 1 To make this fix effective for any index defined on expressions, column mask, or row permission defined on expressions that contain the above function, the object must be regenerated using the ALTER INDEX REGENERATE, ALTER MASK REGENERATE, or ALTER PERMISSION REGENERATE statement, respectively, or dropped and recreated after application of this PTF. To make the fix effective for a native SQL PL, ALTER PROCEDURE/ FUNCTION REGENERATE statement can be used to regenerate the SQL PL. After application of the PTF, the data length of above function may be different. Applications using DESCRIBE may be impacted. Proper actions should be taken if such impact is observed. If the DSNTIAUL sample program is used correctly to generate a LOAD utility control statement, then after application of this PTF, the new control statement generated may not match the data length of above function from the previous control statement. Proper action should be taken if such mismatch is observed. If the DSNTIAUL sample program is used correctly to generate a LOAD utility control statement, then after application of this PTF, the new control statement generated may not match the data format of the data from the previous control statement. Proper actions should be taken if such mismatch is observed. This PTF may also affect the output of a DESCRIBE. Please check any applications that use the generated SQLDA result from a DESCRIBE that could be affected.). UI19330 HOLD DATA END UI19341 HOLD DATA START ++ HOLD(UI19341) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14184) COMMENT (***Action for PI20156: See PI20156 APAR/PTF text for additional information about why a REBIND is necessary. PI20156 corrects an incorrout problem with the ROW_NUMBER, RANK or DENSE_RANK OLAP specification. To make this fix effective for a static application, it must 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(UI15267) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14184) COMMENT (***Action for PI0766I: See PI07661 APAR/PTF text for additional information about why a REBIND is necessary. PI07661 corrects an ABEND0C4 at DSNIDM DSNIRNXT problem for an 1 SQL statement that uses a moving aggregate OLAP specification. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI19341 HOLD DATA END UI19347 HOLD DATA START UI19347 HOLD DATA END UI19363 HOLD DATA START UI19363 HOLD DATA END UI19374 HOLD DATA START UI19374 HOLD DATA END UI19376 HOLD DATA START UI19376 HOLD DATA END UI19383 HOLD DATA START ++ HOLD(UI19383) SYS FMID(HDBAA10) REASON(ACTION) DATE(14188) COMMENT (If you have already installed or migrated to DB2 10 then, you need to take the following actions after applying this PTF: Procedures for these actions are given below. ---------------------------------------------------------------- (1) Run installation job DSNTIJRT to bind DBRM DSNAPRKU ==> This action is required for all V10 customers Run your copy of job DSNTIJRT with MODE(INSTALL) to bind the DBRM DSNAPRKU and refresh the package for DBMD stored procedure SYSIBM.SQLPRIMARYKEYS. If you have previously run DSNTIJRT, rerunning with MODE(INSTALL) will cause it to detect and correct only missing and downlevel SQL objects and packages for DB2-supplied routines. Note:Use MODE(INSTALL-PREVIEW) to obtain a report of any changes without processing them. The PREVIEW option will also generate and output a JCL job to the JCLOUT DD that contains any SQL and bind statements to be processed. 1 After reviewing the changes, either rerun DSNTIJRT without the PREVIEW option or customize and run the generated job. (2) Refresh the WLM environment Issue the following VARY MVS command to refresh the WLM application environment VARY WLM,APPLENV=,REFRESH where is the name of the WLM application environment in which the Database Metadata stored procedure SYSIBM.SQLPRIMARYKEYS running.). UI19383 HOLD DATA END UI19385 HOLD DATA START UI19385 HOLD DATA END UI19420 HOLD DATA START UI19420 HOLD DATA END UI19422 HOLD DATA START UI19422 HOLD DATA END UI19428 HOLD DATA START ++ HOLD(UI19428) SYS FMID(JDBAA17) REASON(DOC) DATE(14189) COMMENT (*** Documentation for PI19449 (Version 10) A new initialization keyword, EXTENDEDTABLEINFO, has been added to allow users to specify whether extended table information is returned in the SQLTables() result set. Complete documentation will be provided in the DB2 for z/OS collection in the IBM Knowledge Center, at this URL: http://www-01.ibm.com/support/knowledgecenter/SSEPEK/ db2z_prodhome.html). ++ HOLD(UI19428) SYS FMID(JDBAA17) REASON(ACTION) DATE(14189) COMMENT (*** Action for PI19449 (Version 10) This APAR PI19449, together with DB2 APAR PI18897, provides an enhancement to allow users to specify whether extended table information is returned in the SQLTables() result set. To fully implement this enhancement, PI19449 must be installed together with PI18897. If PI18897 is not installed, then the enhancement delivered by this APAR will not be enabled.). UI19428 HOLD DATA END UI19432 HOLD DATA START UI19432 HOLD DATA END 1 UI19465 HOLD DATA START UI19465 HOLD DATA END UI19506 HOLD DATA START UI19506 HOLD DATA END UI19508 HOLD DATA START UI19508 HOLD DATA END UI19519 HOLD DATA START ++ HOLD(UI19519) SYS FMID(HDBAA10) REASON(ACTION) DATE(14191) COMMENT (For IBM Text Search with DB2 10 for z/OS, after applying this PTF, the user needs to take the following actions: (A) Run the DSNTIJRT job with MODE(INSTALL) to rebind the Text Search packages. 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 the DSNTIJRT job without the PREVIEW option or customize it and run the generated job. (B) Download and install the most current version of IBMTS, the IBM Text Search server. (1) Download the most current version which is FIX R1L5.1 from the following Web site: http://www.ibm.com/software/data/db2/zos/downloads/oftss.html From this Web site, download the zip file and the readme file for IBMTS Text Search for DB2 for z/OS. The following shows the names of the zip files for the IBMTS Text Search Servers: Linux32 - TS_fixR1L5.1_linux32.zip Linux64 - TS_fixR1L5.1_linux64.zip Window32 - TS_fixR1L5.1_win32.zip Window64 - TS_fixR1L5.1_win64.zip zLinux - TS_fixR1L5.1_zlinux.zip For Window32/64: right click the zip button then choose the extract option. For Linux32/Linux64/zlinux, change mode and unzip the files. Example: chmod 755 TS_fixR1L5.1_linux32.zip 1 unzip TS_fixR1L5.1_linux32.zip To install or update the IBMTS server, please refer to the following publications: --readme.html: document that accompanies the installation file. --"Installation, Administration, and Reference": the product documentation for the IBM Text Search for DB2 z/OS. (2) New IBMTS users: Install the IBMTS server. To install the IBMTS server, the user needs to follow these instructions. Chapter 4. Installing and configuring text search functions --Installing IBM Text Search for DB2 z/OS. (3) Existing users: Migrate to IBMTS from OmniFind server. For existing users to migrate IBMTS from OmniFind server, please follow these instructions: Chapter 4. Installing and configuring text search functions --Migrating to IBM Text Search for DB2 for z/OS from OmniFind Text Search. or --Installing fixes on top of the current server. (install IBMTS server on the existing server). (4) Where to find more information ---------------------------------------------------------------- The user can look for more information at: Installation, Administration, and Reference IBM Text Search for DB2 for z/OS: http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/ com.ibm.db2z10.doc.srchz/src/srchz/dasz_srchz.htm Administration stored procedures for text search: http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/ com.ibm.db2z10.doc.srchz/src/tpc/tsrch_storedpro.htm). UI19519 HOLD DATA END UI19540 HOLD DATA START UI19540 HOLD DATA END UI19543 HOLD DATA START ++ HOLD(UI19543) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14192) COMMENT (This PTF provides new function to accelerate static SELECT INTO statement. To enable a static SELECT INTO for acceleration, the application must be rebound after application of this PTF. 1 See PI18965 APAR/PTF cover letter text for more details and additional information.). ++ HOLD(UI19543) SYS FMID(HDBAA10) REASON(DOC) DATE(14192) COMMENT (This PTF adds new reason code 23 for existing SQLCODE -4742 as follows: 23 The SELECT INTO is bound for acceleration but is run as a remote SELECT INTO, which is not supported for acceleration. . Programmer Response: 23 Remove the SELECT INTO statement, or REBIND the package with bind option QUERYACCELERATION(NONE). If the program is an SQL PL procedure or function, use one of the following alternatives instead of using BIND or REBIND PACKAGE: - Alter the procedure or function by using ALTER PROCEDURE or ALTER FUNCTION - Drop and then re-create the procedure or function by using CREATE PROCEDURE or CREATE FUNCTION). UI19543 HOLD DATA END UI19571 HOLD DATA START UI19571 HOLD DATA END UI19578 HOLD DATA START UI19578 HOLD DATA END UI19587 HOLD DATA START UI19587 HOLD DATA END UI19598 HOLD DATA START UI19598 HOLD DATA END UI19624 HOLD DATA START UI19624 HOLD DATA END UI19629 HOLD DATA START UI19629 HOLD DATA END UI19644 HOLD DATA START ++ HOLD(UI19644) SYS FMID(HDBAA10) REASON(DOC) DATE(14197) COMMENT (PI11167 introduces a new informational message DSNT299I. DSNT299I csect-name NO INACTIVE COPIES EXIST FOR PACKAGE  = package-name 1 Explanation This message is issued when the FREE PACKAGE command is issued with the PLANMGMTSCOPE(INACTIVE) option, and the specified package has no inactive copies. package-name Name of the specified package. System action No action. User Response This is an informational message. No action is needed.). UI19644 HOLD DATA END UI19653 HOLD DATA START UI19653 HOLD DATA END UI19690 HOLD DATA START ++ HOLD(UI19690) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14198) COMMENT (***Action for PI19676: See PI19676 APAR/PTF text for additional information about why a REBIND is necessary. PI19676 corrects a problem of an index defined on a key-expression may not be used by DB2, when an SQL statement satisfies all of following conditions: 1. the key-expression is used within a scalar fullselect; 2. the above scalar fullselect is referenced in another 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.). UI19690 HOLD DATA END UI19693 HOLD DATA START ++ HOLD(UI19693) SYS FMID(HDBAA10) REASON(ACTION) DATE(14198) COMMENT (***Action for PI17079 (DB2 10) This PTF modifies installation panel DSNTIP6 to correct the DEFAULT TEMPLATE field so that it will accept a DB2 utilities template name that contains substring notation. The DEFAULT TEMPLATE setting is assigned to the DB2 subsystem parameter DSN6SPRM.FCCOPYDDN. If you have already installed or migrated to this version of DB2 and you maintain copies of the DB2 installation panels outside of SMP/E then after applying this PTF, you need to refresh them 1 from the updated DSNTIP6 panel in your prefix.SDSNSPFP library.). UI19693 HOLD DATA END UI19696 HOLD DATA START ++ HOLD(UI19696) SYS FMID(JDBAA14) REASON(ACTION) DATE(14198) COMMENT (***Action for PI17700 (SDSNPFPE) This PTF modifies an ISPF panel for the DB2 Interactive (DB2I) facility, in the SDSNPFPE target library. The panel is DSNEOP02: DB2I Defaults Panel 2. If you keep the DB2I panels in a different library then after applying this PTF, you need to copy over the updated panel from the SDSNPFPE target library.). UI19696 HOLD DATA END UI19720 HOLD DATA START UI19720 HOLD DATA END UI19722 HOLD DATA START UI19722 HOLD DATA END UI19725 HOLD DATA START UI19725 HOLD DATA END UI19744 HOLD DATA START ++ HOLD(UI19744) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14199) COMMENT (***Action for PI17868: A rebind is necessary to rebuild package structures based on the changes in this APAR. PI17868 corrects a problem that DB2 may produce incorrect output for a query with a row expression predicate if the row expression predicate is selected as the matching predicate in an "N" or "IN" access type and the row expression predicate is partially matched. To make this fix effective for a static application, it must 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(UI18551) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14199) COMMENT (***Action for PI16217: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI16217 corrects a problem in which a list prefetch access path 1 may be selected for a table defined as VOLATILE or qualifying for NPGTHRSH when there is an alternate index that provides more matching 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.). UI19744 HOLD DATA END UI19760 HOLD DATA START UI19760 HOLD DATA END UI19764 HOLD DATA START UI19764 HOLD DATA END UI19796 HOLD DATA START UI19796 HOLD DATA END UI19800 HOLD DATA START UI19800 HOLD DATA END UI19815 HOLD DATA START ++ HOLD(UK98040) SYS FMID(HDBAA10) REASON(ACTION) DATE(14202) COMMENT (This PTF modifies V10 premigration checkout job DSNTIJPM. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: - Edit your customized copy of DSNTIJPM - Delete all lines and copy in the DSNTIJPM member from the prefix.SDSNSAMP library - Follow the directions in the job prolog to customize it your DB2 - If you are preparing to migrate to DB2 V10, run the updated customized job to check for conditions that may affect your migration.). ++ HOLD(UI18611) SYS FMID(HDBAA10) REASON(ACTION) DATE(14202) COMMENT (This PTF modifies the DB2 10 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 10, run the updated customized job to check for conditions that may affect your migration. This PTF also modifies the DB2 11 premigration checkout job, 1 DSNTIJPB. 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 DSNTIJPB - Delete all lines and copy in the DSNTIJPB 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 11, run the updated customized job to check for conditions that may affect your migration.). ++ HOLD(UI19815) SYS FMID(HDBAA10) REASON(ACTION) DATE(14202) COMMENT (***Action for PI11316 (DB2 10) This PTF modifies the DB2 10 premigration check-out 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 10, run the updated customized job to check for conditions that might affect your migration. This PTF also modifies the DB2 11 premigration check-out job, DSNTIJPB. 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 DSNTIJPB - Delete all lines and copy in the DSNTIJPB 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 11, run the updated customized job to check for conditions that might affect your migration.). ++ HOLD(UI17155) SYS FMID(HDBAA10) REASON(ACTION) DATE(14202) COMMENT (***Action for PI11236 (DB2 10 for z/OS) This PTF modifies the DB2 10 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 10, run the updated customized job to check for conditions that may affect your migration. This PTF also modifies the DB2 11 premigration checkout job, DSNTIJPB. If you maintain a customized copy of this job then after applying this PTF, you need to refresh it as follows: 1 - Edit your customized copy of DSNTIJPB - Delete all lines and copy in the DSNTIJPB 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 11, run the updated customized job to check for conditions that may affect your migration.). ++ HOLD(UI16235) SYS FMID(HDBAA10) REASON(ACTION) DATE(14202) COMMENT (***Action for PI09041 (DB2 10) This PTF modifies the DB2 10 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 10, run the updated customized job to check for conditions that may affect your migration. This PTF also modifies the DB2 11 premigration checkout job, DSNTIJPB. 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 DSNTIJPB - Delete all lines and copy in the DSNTIJPB 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 11, run the updated customized job to check for conditions that may affect your migration.). UI19815 HOLD DATA END UI19886 HOLD DATA START UI19886 HOLD DATA END UI19891 HOLD DATA START UI19891 HOLD DATA END UI19895 HOLD DATA START ++ HOLD(UI19895) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14204) COMMENT (***Action for PI17470: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI17470 corrects a problem in which various statistics may not be used for optimization of a query against a clone table. This may lead to an inefficient access path and poor query 1 performance. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI14000) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14204) COMMENT (***Action for PI04769: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI04769 corrects a problem that DB2 may select a different access path on the test subsystem from the production subsystem even if the test subsystem is modeling the production subsystem by simulating CPU speed, number of processors, RID pool, sort pool and buffer pool settings. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI19895 HOLD DATA END UI19897 HOLD DATA START UI19897 HOLD DATA END UI19900 HOLD DATA START UI19900 HOLD DATA END UI19902 HOLD DATA START ++ HOLD(UI13639) SYS FMID(HIZAA10) REASON(ACTION) DATE(14204) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). ++ HOLD(UK96810) SYS FMID(HIZAA10) REASON(ACTION) DATE(14204) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 1 3. Issue -REFRESH DB2,EARLY). ++ HOLD(UK93654) SYS FMID(HIZAA10) REASON(ACTION) DATE(14204) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). ++ HOLD(UI19902) SYS FMID(HIZAA10) REASON(ACTION) DATE(14204) COMMENT (***Action for PI21701: 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.). UI19902 HOLD DATA END UI19954 HOLD DATA START UI19954 HOLD DATA END UI19960 HOLD DATA START UI19960 HOLD DATA END UI19996 HOLD DATA START UI19996 HOLD DATA END UI20000 HOLD DATA START ++ HOLD(UI20000) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14206) COMMENT 1 (***Action for PI20247: See PI20247 APAR/PTF text for additional information about why a REBIND is necessary. PI20247 corrects a problem for static SQL query acceleration where doing a BIND or REBIND PACKAGE that specifies bind option QUERYACCELERATION while DB2 subsystem parameter ACCELMODEL=YES. To make this fix effective for a static application that contains static SQL queries intended for acceleration, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20000 HOLD DATA END UI20035 HOLD DATA START UI20035 HOLD DATA END UI20041 HOLD DATA START UI20041 HOLD DATA END UI20058 HOLD DATA START UI20058 HOLD DATA END UI20069 HOLD DATA START UI20069 HOLD DATA END UI20099 HOLD DATA START UI20099 HOLD DATA END UI20103 HOLD DATA START UI20103 HOLD DATA END UI20106 HOLD DATA START UI20106 HOLD DATA END UI20108 HOLD DATA START UI20108 HOLD DATA END UI20110 HOLD DATA START UI20110 HOLD DATA END UI20112 HOLD DATA START UI20112 HOLD DATA END 1 UI20115 HOLD DATA START UI20115 HOLD DATA END UI20117 HOLD DATA START UI20117 HOLD DATA END UI20143 HOLD DATA START ++ HOLD(UI20143) SYS FMID(HDBAA10) REASON(ACTION) DATE(14212) COMMENT (The PTF for APAR PI05161 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.). UI20143 HOLD DATA END UI20151 HOLD DATA START ++ HOLD(UI20151) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14212) COMMENT (***Action for PI20688: See PI20688 APAR/PTF text for additional information about why a REBIND is necessary. PI20688 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 routes to an accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20151 HOLD DATA END UI20153 HOLD DATA START UI20153 HOLD DATA END UI20160 HOLD DATA START UI20160 HOLD DATA END 1 UI20162 HOLD DATA START UI20162 HOLD DATA END UI20164 HOLD DATA START UI20164 HOLD DATA END UI20172 HOLD DATA START UI20172 HOLD DATA END UI20190 HOLD DATA START UI20190 HOLD DATA END UI20243 HOLD DATA START ++ HOLD(UK63012) SYS FMID(HDBAA10) REASON(ACTION) DATE(14216) 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. ----------------------------------------------------------------). UI20243 HOLD DATA END UI20301 HOLD DATA START UI20301 HOLD DATA END UI20314 HOLD DATA START ++ HOLD(UI19545) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14218) COMMENT (***Action for PM94681 (DB2 10) This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. These instructions supersede the instructions for any previous PTF on 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 bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers. This PTF updates programs module DSNADMSS plus the DBRM for DSNADMSS.After applying this PTF, proceed as follows to bind a package from the updated DSNADMSS DBRM. 1 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.). ++ HOLD(UI20314) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14218) COMMENT (***Action for PI21058 (DB2 10 for z/OS) This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. If you have already installed or migrated to DB2 V10, you need to take the following actions after applying this PTF: --------------------------------------------------------------- (1) Run installation job DSNTIJRT to bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers. This PTF updates program module DSNADMSS and the DBRM for DSNADMSS. After applying this PTF, proceed as follows to bind the updated DSNADMSS DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to bind the DSNADMSS 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.). ++ HOLD(UI15281) SYS FMID(HDBAA10) REASON(ACTION) DATE(14218) COMMENT (***Action for PI07646 (DB2 10) This PTF modifies DSNADMSS, the external module for SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used to collect DB2 environmental service data. These instructions supersede any previous PTF instructions. 1 If you have already installed or migrated to DB2 V10, you need to take the following action after applying this PTF: --------------------------------------------------------------- Run installation job DSNTIJRT to bind DBRM DSNADMSS --------------------------------------------------------------- ==> This action is required for all V10 customers. This PTF updates programs module DSNADMSS plus the DBRM for DSNADMSS. After applying this PTF, proceed as follows to bind a package from the updated DSNADMSS DBRM. Run your copy of job DSNTIJRT with MODE(INSTALL) to install, bind, and grant access to the DB2-supplied stored procedures. If you have previously run DSNTIJRT, re-running 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 re-run DSNTIJRT without the PREVIEW option or customize and run the generated job.). UI20314 HOLD DATA END UI20329 HOLD DATA START ++ HOLD(UI20329) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14219) COMMENT (***Action for PI17335: See PI17335 APAR/PTF text for additional information about why a REBIND is necessary. PI17335 corrects an abend ABEND0C4 occur at DSNISELL OFFSET079C or OFFSET076C for queries that reference inline LOB columns and satisfy the star join transformation. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20329 HOLD DATA END UI20338 HOLD DATA START UI20338 HOLD DATA END UI20346 HOLD DATA START UI20346 HOLD DATA END 1UI20363 HOLD DATA START UI20363 HOLD DATA END UI20365 HOLD DATA START UI20365 HOLD DATA END UI20367 HOLD DATA START UI20367 HOLD DATA END UI20375 HOLD DATA START UI20375 HOLD DATA END UI20387 HOLD DATA START UI20387 HOLD DATA END UI20414 HOLD DATA START UI20414 HOLD DATA END UI20439 HOLD DATA START ++ HOLD(UI20439) SYS FMID(HDBAA10) REASON(ACTION) DATE(14224) COMMENT (***Action for PI20069 (DB2 10) This PTF modifies the DB2 installation CLIST default input members, DSNTIDXA and DSNTIDXB. It corrects an error in the CLIST range checking of the settings for SIMULATED_CPU_COUNT and SIMULATED_CPU_SPEED. If you have already installed or migrated to DB2 10, you need to make the correction in your private DSNTIDxx members. Edit each such member, locate the entries for SIMULATED_CPU_COUNT and SIMULATED_CPU_SPEED, and change the fifth field to NONE. In other words, change this format: SIMULATED_CPU_COUNT CHARR G OFF 255 SIMULATED_CPU_SPEED CHARR G OFF 2147483647 to this: SIMULATED_CPU_COUNT CHARR G OFF NONE SIMULATED_CPU_SPEED CHARR G OFF NONE where is the current setting of SIMULATED_CPU_COUNT and is the current setting of SIMULATED_CPU_SPEED. Save your changes.). UI20439 HOLD DATA END UI20441 HOLD DATA START UI20441 HOLD DATA END 1UI20452 HOLD DATA START ++ HOLD(UI20452) SYS FMID(HDBAA10) REASON(ACTION) DATE(14224) COMMENT (After the PTF for apar PI20643 is installed, users will need to rerun DSNTIJML for the 'BINDBRM' step to rebind MQListener. Also, users will need to rebind the MQListener's applications.). UI20452 HOLD DATA END UI20454 HOLD DATA START UI20454 HOLD DATA END UI20558 HOLD DATA START ++ HOLD(UI20558) SYS FMID(HDBAA10) REASON(DOC) DATE(14226) COMMENT (PI13918 introduces the following changes to externals: Changed messages or codes: For reason code 00E70022, the following is added to the System programmer response: If DBNAME is specified to be greater than 8, correct the value to a length that is 8 characters or less.). UI20558 HOLD DATA END UI20561 HOLD DATA START UI20561 HOLD DATA END UI20585 HOLD DATA START ++ HOLD(UK98123) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM94160: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM94160 corrects a problem that DB2 may select an inefficient join sequence for a query which has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK94462) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM87084: See PM87084 APAR/PTF text for additional information about why a REBIND is necessary. PM87084 corrects a problem of incorrect output for a query with an ORDER BY clause that refers to a table with an OMNIFIND function. 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(UK94519) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM85160: See PM85160 APAR/PTF text for additional information about why a REBIND is necessary. PM85160 corrects a problem of SQL performance when queries contain join predicates involving column expressions or queries joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK93392) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM83457: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM83457 corrects a problem that the DB2 optimizer may select an inefficient join sequence for a query if the query has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK83543) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM75197: See PM75197 APAR/PTF text for additional information about why a REBIND is necessary. PM75197 corrects a problem of inefficient access path for read only queries with FOR UPDATE. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90219) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM73214: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. 1 PM73214 corrects a problem of inaccurate cost estimation for a query when the query contains a view or table expression with UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK90222) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM72676: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM72676 corrects a problem of inaccurate cost estimation for a query when the query contains nested non-correlated subqueries. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK77770) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM58932: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PM58932 corrects a problem that DB2 may choose an inefficient join sequence for a query joining 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK68201) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM34814: See PM34814 APAR/PTF text for additional information about why a REBIND is necessary. PM34814 corrects a problem that DB2 may select an inefficient join sequence for a query if a declared global temporary table is involved or statistics on join columns are not collected. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK68203) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM32404: 1 See PM32404 APAR/PTF text for additional information about why a REBIND is necessary. PM32404 corrects a problem of inaccurate filter factor estimation for a predicate that is generated by global optimization for an IN subquery or EXISTS subquery if there are multiple IN or EXISTS subqueries in the same query block. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK66477) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM29262: See PM29262 APAR/PTF text for additional information about why a REBIND is necessary. PM29262 corrects a problem of inaccurate output in DSN_DETCOST_TABLE when a materialized query block occurs. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK66093) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM25629: See PM25629 APAR/PTF text for additional information about why a REBIND is necessary. PM25629 resolves a case in which an inefficient join sequence could be chosen for a query block with four or fewer tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK67419) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PM17234: See PM17234 APAR/PTF text for additional information about why a REBIND is necessary. PM17234 will allow more join permutations to be considered when there are a high number of query blocks, but each query block contains less than or equal to four tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI20219) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) 1 COMMENT (***Action for PI21209: See PI21209 APAR/PTF text for additional information about why a REBIND is necessary. PI21209 corrects a problem that DB2 may select an inefficient join sequence for a query if the query contains a join predicate involving column expressions with columns from 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI20585) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14226) COMMENT (***Action for PI18833: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI18833 corrects a problem that DB2 may select an inefficient join sequence for a query which has a query block with a join of 3 or more tables. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20585 HOLD DATA END UI20600 HOLD DATA START UI20600 HOLD DATA END UI20615 HOLD DATA START UI20615 HOLD DATA END UI20617 HOLD DATA START UI20617 HOLD DATA END UI20621 HOLD DATA START ++ HOLD(UI20621) SYS FMID(HDBAA10) REASON(ACTION) DATE(14229) COMMENT (PI19842 corrects a problem of ABEND04E RC00E70005 at location DSNXGRDS DSNXSTRC M777 or other unexpected ABEND0C4 or ABEND04E or unexpected SQLCODE -104 during rebind when a compiled SQL scalar function contains a RETURN statement which returns an expression with special register CURRENT SERVER, CURRENT PACKAGESET or CURRENT PACKAGE PATH. After the application of this PTF, ALTER FUNCTION REGENERATE is required for each SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, compiled 1 SQL scalar function could be affected by this change.). UI20621 HOLD DATA END UI20670 HOLD DATA START ++ HOLD(UI20670) SYS FMID(HDBAA10) REASON(ACTION) DATE(14231) COMMENT (***Action for PI21713 (DB2 10 for z/OS) This PTF modifies the DB2-supplied stored procedure SYSPROC.ADMIN_DS_LIST to list migrated data sets and generation data sets correctly. *************************************************************** Actions for customers who are already using DB2 V10: *************************************************************** If you have already installed or migrated to V10, run your copy of the installation job DSNTIJRT with MODE(INSTALL) to bind the ADMIN_DS_LIST 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.). UI20670 HOLD DATA END UI20685 HOLD DATA START ++ HOLD(UI20685) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14231) COMMENT (***Action for PI21188: PI21188 is a pre-conditioning APAR that includes changes to support a functional code change that will be enabled via APAR PI22531 at a later date. At this time, all of the changes are transparent to the user. In a data sharing group, this pre-conditioning APAR (PI21188) should be applied to all members before the later enabling APAR PI22531 is applied to any member. The code change is not enabled until the enabling APAR PI22531 is applied.). UI20685 HOLD DATA END UI20733 HOLD DATA START UI20733 HOLD DATA END UI20776 HOLD DATA START UI20776 HOLD DATA END 1 UI20778 HOLD DATA START UI20778 HOLD DATA END UI20786 HOLD DATA START UI20786 HOLD DATA END UI20788 HOLD DATA START UI20788 HOLD DATA END UI20792 HOLD DATA START ++ HOLD(UI20792) SYS FMID(HIZAA10) REASON(ACTION) DATE(14233) 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.). UI20792 HOLD DATA END UI20794 HOLD DATA START UI20794 HOLD DATA END UI20796 HOLD DATA START ++ HOLD(UK97939) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14233) COMMENT (PM94158 corrects a problem of incorrect output returned when query contains LIKE predicate with RTRIM/STRIP FUNCTION and literal pattern with blank pattern and index created on column in RTRIM/STRIP.). ++ HOLD(UI20796) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14233) COMMENT (***Action for PI20948: See PI20948 APAR/PTF text for additional information about why a REBIND is necessary. PI20948 corrects a problem of incorrect output which may occur when a table is accessed via an index and the index column has an expression predicate on it running in parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover 1 letter to determine which, if any, applications could be affected by this change.). UI20796 HOLD DATA END UI20823 HOLD DATA START UI20823 HOLD DATA END UI20825 HOLD DATA START UI20825 HOLD DATA END UI20828 HOLD DATA START UI20828 HOLD DATA END UI20834 HOLD DATA START UI20834 HOLD DATA END UI20836 HOLD DATA START UI20836 HOLD DATA END UI20843 HOLD DATA START UI20843 HOLD DATA END UI20846 HOLD DATA START UI20846 HOLD DATA END UI20848 HOLD DATA START ++ HOLD(UI20848) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14237) COMMENT (PI18866 corrects a problem for a DB2 for z/OS accelerated static SQL query in either of the following usage scenarios: - returned as a result set from a DB2 remote stored procedure or remote native SQL procedure, - as a static query in an SQLJ application that is run using the IBM® Data Server Driver for JDBC and SQLJ, when using the db2sqljcustomize command parameter ' -onlinecheck NO '. . To make this fix effective for the accelerated static SQL query usage described above, after application of this PTF, - the stored procedure package must be rebound or for a native SQL procedure an ALTER PROCEDURE must be done. - for the SQLJ application, the associated DB2 package must be bound or rebound via the method you normally use for your SQLJ applications for DB2 for z/OS. See PI18866 APAR/PTF cover letter text for more details and additional information.). UI20848 HOLD DATA END 1 UI20852 HOLD DATA START ++ HOLD(UI16023) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14237) COMMENT (***Action for PI08057: See PI08057 APAR/PTF text for additional information about why a REBIND is necessary. PI08057 corrects a problem of ABEND0E0 RC00000028 at location DSNIDM DSNOGETD OFFSET3754 when a MERGE statement satisfies following conditions: 1. Binding a MERGE statement with bind option EXTENDEDINDICATOR YES. 2. Target of the UPDATE or INSERT clause is the column that is LOBs. 3. Source of the UPDATE or INSERT clause is the column from source table which is not LOBs. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20852 HOLD DATA END UI20910 HOLD DATA START UI20910 HOLD DATA END UI20930 HOLD DATA START UI20930 HOLD DATA END UI20956 HOLD DATA START UI20956 HOLD DATA END UI20965 HOLD DATA START ++ HOLD(UI20965) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14241) COMMENT (***Action for PI18243: See PI18243 APAR/PTF text for additional information about why a REBIND is necessary. PI18243 corrects a problem of inefficient access path selection of an ambiguous scroll cursor with an ORDER BY clause. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI20965 HOLD DATA END 1 UI20980 HOLD DATA START UI20980 HOLD DATA END UI20985 HOLD DATA START UI20985 HOLD DATA END UI21017 HOLD DATA START ++ HOLD(UK93957) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14245) COMMENT (See PM82533 APAR/PTF text for additional information about why a REBIND is necessary. PM82533 corrects a problem of an SQL statement which contains a table expression, CTE or view that is used on the preserved side of OUTER JOIN, and this table expression, CTE or view contains a correlated IN subquery. DB2 may not choose to correlate/de- correlate the IN subquery due to aggressive table expression/ view merge, which may cause performance regression. After application of the PTF, when an internal serviceability feature is disabled on your system under the suggestion of DB2 service, the aggressive table expression/view merge will not happen for a table expression, CTE or view on the preserved side of OUTER JOIN that contains a correlated IN subquery. To make this fix effective for a static application, it must be rebound after application of this PTF and the internal serviceability feature is disabled on your system. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI21017 HOLD DATA END UI21019 HOLD DATA START UI21019 HOLD DATA END UI21027 HOLD DATA START UI21027 HOLD DATA END UI21039 HOLD DATA START UI21039 HOLD DATA END UI21041 HOLD DATA START ++ HOLD(UI21041) SYS FMID(HDBAA10) REASON(ACTION) DATE(14245) COMMENT (The PTF for APAR PI19784 has modified CSECTs in both the DSNUT101 and DSNUTILA load modules, affecting the utility batch and DB2 DBM1 address spaces. After the PTF has been applied, it will become active in the utility batch address space immediately upon job submission, while it will not take effect in the DB2 DBM1 address space until DB2 is stopped and started. 1 The PTF does not have to be applied to all members in a data sharing environment simultaneously, and may be staged across each member. However, until the fix is active in both the utility batch and DB2 DBM1 address spaces, the problem the PTF addresses will not be resolved.). UI21041 HOLD DATA END UI21047 HOLD DATA START UI21047 HOLD DATA END UI21049 HOLD DATA START UI21049 HOLD DATA END UI21051 HOLD DATA START UI21051 HOLD DATA END UI21084 HOLD DATA START UI21084 HOLD DATA END UI21104 HOLD DATA START ++ HOLD(UI21104) SYS FMID(HDBAA10) REASON(ACTION) DATE(14247) COMMENT (***Action for PI19131 (DB2 10) This APAR modifies DSNTRIN, the installation and configuration tool for DB2-supplied stored procedures and user-defined functions (UDFs), to correct invalid syntax in the generated create statement for the SYSTOOLS.REGSP stored procedure. It also modifies DSNTRIN to detect and alter existing instances of SYSTOOLS.REGSP that are defined with the error. If you have already installed or migrated to DB2 10, you need to run your copy of job DSNTIJRT with MODE(INSTALL) to check for and correct problems with the SYSTOOLS.REGSP stored procedure. 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.). UI21104 HOLD DATA END 1UI21107 HOLD DATA START UI21107 HOLD DATA END UI21112 HOLD DATA START ++ HOLD(UI21112) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14247) COMMENT (PI19349 is a pre-conditioning APAR that includes changes to correct a problem where XML storage is not released when the query contains an XMLPARSE function and its output is passed into XMLTABLE function for further processing. The fix will be enabled via APAR PI20544 at a later date. At this time, all of the changes are transparent to the user. In a data sharing group, this pre-conditioning APAR should be applied to all members before the later enabling APAR is applied to any member. The fix is not enabled until the enabling APAR is applied.). UI21112 HOLD DATA END UI21118 HOLD DATA START ++ HOLD(UI21118) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14247) COMMENT (***Action for PI21874: See PI21874 APAR/PTF text for additional information about why a REBIND is necessary. PI21874 corrects the problem of incorrect output when a SQL scalar function, native SQL procedure, index on expression or multiple-row-insert with NOT ATOMIC CONTINUE ON SQLEXCEPTION satisfies the following list of conditions: 1. The statement contains a POSSTR function. 2. The data type of the second argument of above POSSTR function is BLOB, CLOB or DBCLOB. To make this fix effective for a static application, it must 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(UI17369) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14247) COMMENT (See PI12825 APAR/PTF text for additional information about why a REBIND is necessary. APAR PI12825 fixes the abend problem when passing the output of a CASE expression into XMLTABLE function. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI21118) SYS FMID(HDBAA10) REASON(ACTION) DATE(14247) COMMENT (PI21874 corrects the problem of incorrect output when a SQL scalar function, native SQL procedure, index on expression or multiple-row-insert with NOT ATOMIC CONTINUE ON SQLEXCEPTION 1 satisfies the following list of conditions: 1. The statement contains a POSSTR function. 2. The data type of the second argument of above POSSTR function is BLOB, CLOB or DBCLOB. To make this fix effective for any index defined on expressions that contain the above function, the object must be regenerated using the ALTER INDEX REGENERATE statement or dropped and recreated after application of this PTF. After the application of this PTF, ALTER PROCEDURE/FUNCTION REGENERATE is required for each native SQL procedure/compiled SQL scalar function that is affected. Review the PTF cover letter to determine which, if any, native SQL procedure and SQL scalar function could be affected by this change.). UI21118 HOLD DATA END UI21122 HOLD DATA START ++ HOLD(UI21122) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14248) COMMENT (***Action for PI22793: See PI22793 APAR/PTF text for additional information about why a REBIND is necessary. PI22793 corrects a problem that incorrect output could happen for an SQL statement containing a function VARCHAR_FORMAT on a FOR BIT DATA 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.). UI21122 HOLD DATA END UI21152 HOLD DATA START UI21152 HOLD DATA END UI21163 HOLD DATA START ++ HOLD(UI20074) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14251) COMMENT (***Action for PI17107: A rebind is necessary for static applications to rebuild access paths based on changes in this APAR. PI17107 corrects a problem where ABEND04E RC00E70005 in DSNXESX4:P403 can occur on an UPDATE WHERE CURRENT OF statement if the target of the update is a view which contains a subquery. 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.). UI21163 HOLD DATA END UI21172 HOLD DATA START UI21172 HOLD DATA END UI21176 HOLD DATA START UI21176 HOLD DATA END UI21178 HOLD DATA START ++ HOLD(UI21178) SYS FMID(HIZAA10) REASON(ACTION) DATE(14251) COMMENT ( This PTF requires either an ERLY code refresh or a re-IPL of zOS. To refresh, enter the following commands after applying the PTF: MODIFY LLA,REFRESH -STOP DB2 ... (only if the DB2 subsystem is started) -REFRESH DB2,EARLY -START DB2,PARM=... These commands are not necessary if you re-IPL after applying the PTF.). ++ HOLD(UI18945) SYS FMID(HIZAA10) REASON(ACTION) DATE(14251) COMMENT (***Action for PI18566: This PTF requires either an ERLY code refresh or a re-IPL of zOS. To refresh, enter the following commands after applying the PTF: MODIFY LLA,REFRESH -STOP DB2 ... (only if the DB2 subsystem is started) -REFRESH DB2,EARLY -START DB2,PARM=... These commands are not necessary if you re-IPL after applying the PTF.). ++ HOLD(UI18548) SYS FMID(HIZAA10) REASON(ACTION) DATE(14251) COMMENT (This PTF updates the ERLY code. After you apply this fix, you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2 command. The procedure for issuing the REFRESH command is: 1 1. Issue -STOP DB2 2. Issue MODIFY LLA,REFRESH 3. Issue -REFRESH DB2,EARLY). UI21178 HOLD DATA END UI21192 HOLD DATA START ++ HOLD(UI21192) SYS FMID(HIZAA10) REASON(ACTION) DATE(14252) COMMENT (***Action for PI24305: 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.). UI21192 HOLD DATA END UI21202 HOLD DATA START UI21202 HOLD DATA END UI21235 HOLD DATA START UI21235 HOLD DATA END UI21247 HOLD DATA START ++ HOLD(UK62817) SYS FMID(HDBAA10) REASON(ACTION) DATE(14253) COMMENT (In version 10 coexistence mode, all active version 8 and version 9 members MUST apply this APAR before any version 10 member with this APAR applied is restarted. If not applied properly, -DISPLAY THREAD SCOPE(GROUP) commands will not return valid data from remote version 8 and version 9 members which may result in a large amount of invalid output on the version 10 member. In addition, an ABEND0C4 in CSECT DSNVDTT may be encountered on the version 10 member.). UI21247 HOLD DATA END UI21280 HOLD DATA START UI21280 HOLD DATA END UI21287 HOLD DATA START UI21287 HOLD DATA END 1 UI21288 HOLD DATA START ++ HOLD(UI21288) SYS FMID(HDBAA10) REASON(ACTION) DATE(14254) COMMENT (APAR PI23703 fixes a problem where a sequence may incorrectly generate duplicate or unexpected values if the sequence is concurrently ALTERed and accessed by the NEXTVAL statement. DB2 has been modified to correctly serialize concurrent ALTER SEQUENCE and sequence reference processing. With this APAR applied, concurrently altering and referencing a sequence will no longer result in incorrect, duplicate values from that sequence. However, applying this APAR does not fix sequence objects that are already affected by this problem. If any such objects are identified by your users, they must restart the sequence with either the ALTER SEQUENCE RESTART or ALTER SEQUENCE RESTART WITH statements or drop and recreate the sequence after applying this APAR.). UI21288 HOLD DATA END UI21304 HOLD DATA START ++ HOLD(UI21304) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14254) COMMENT (See PI23868 APAR/PTF text for additional information about why a REBIND is necessary. PI23868 corrects a problem of incorrect output returned for a outer join with UNION or UNION ALL and FETCH FIRST N ROW or ORDER BY in its 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.). UI21304 HOLD DATA END UI21331 HOLD DATA START UI21331 HOLD DATA END UI21335 HOLD DATA START UI21335 HOLD DATA END UI21385 HOLD DATA START UI21385 HOLD DATA END UI21419 HOLD DATA START UI21419 HOLD DATA END 1UI21550 HOLD DATA START ++ HOLD(UI21550) SYS FMID(HDBAA10) REASON(ACTION) DATE(14265) COMMENT (This APAR/PTF provides a job to update some entries in SYSCHECKS.CHECKCONDITION in the catalog for catalog table check constraints. Please run the following query to determine whether there are entries that need to be updated: SELECT * FROM SYSIBM.SYSCHECKS WHERE DBID=6 AND CHECKCONDITION LIKE '% IN (-1,-2) %' If any rows are returned, please run the CATMAINT utility as follows: CATMAINT UPDATE UNLDDN PI18738). ++ HOLD(UI16445) SYS FMID(HDBAA10) REASON(ACTION) DATE(14265) COMMENT (This apar corrects rows that were inserted into the catalog for the directory objects. To see if you have rows that need to be updated run the query: SELECT NAME,TBNAME,LENGTH(LABEL) FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'SYSIBM' AND TBNAME IN ('SYSUTIL','DBDR','SCTR','SPTR','SYSLGRNX','SYSUTILX') AND LENGTH(LABEL) ¬= 0; If this query returns rows you have rows that need to be corrected by running the utility job CATMAINT UPDATE UNLDDN PI08928 This job will invalidate packages that are dependent on the directory tables, delete the catalog rows and then insert the correct rows. If the following query returns 0 rows SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1; The rows have not been added and they can be added using the same job.). UI21550 HOLD DATA END UI21620 HOLD DATA START UI21620 HOLD DATA END UI21640 HOLD DATA START ++ HOLD(UI21640) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14267) COMMENT (***Action for PI22098: 1 See PI22098 APAR/PTF text for additional information about why a REBIND is necessary. PI22098 corrects an ABEND0C7 at DSNXRSGB OFFSET7720 or an incorrect result problem that can occur for an SQL statement that references a VIEW. The VIEW contains a UNION clause and a subquery that references an aggregate function OR a UNION ALL clause and a subquery that references an aggregate function and the query does not satisfy the union distribution criteria. The input of the aggregate function contains a decimal expression. The problem can occur when the precision specified for the creation of the view and the execution of the query differs. To make this fix effective for a static application, it must 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(UI21640) SYS FMID(HDBAA10) REASON(ACTION) DATE(14267) COMMENT (The following ACTION needs to be performed on behalf of this apar. Please note that along with the application of this fix, if the VIEW is a nested view, it will need to be dropped and recreated.). UI21640 HOLD DATA END UI21659 HOLD DATA START UI21659 HOLD DATA END UI21710 HOLD DATA START ++ HOLD(UI21710) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14268) COMMENT (***Action for PI22946: See PI22946 APAR/PTF text for additional information about why a REBIND is necessary. PI22946 corrects a problem of incorrect output may occur when a query contains a subquery predicate which referencing a global temporary table and its parent query block of the subquery predicate runs on parallel. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). 1UI21710 HOLD DATA END UI21748 HOLD DATA START UI21748 HOLD DATA END UI21768 HOLD DATA START UI21768 HOLD DATA END UI21881 HOLD DATA START UI21881 HOLD DATA END UI21946 HOLD DATA START ++ HOLD(UI21946) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14275) COMMENT (***Action for PI22945: See PI22945 APAR/PTF text for additional information about why a REBIND is necessary. PI22945 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 routes to an accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI21946 HOLD DATA END UI21990 HOLD DATA START UI21990 HOLD DATA END UI22071 HOLD DATA START UI22071 HOLD DATA END UI22111 HOLD DATA START UI22111 HOLD DATA END UI22175 HOLD DATA START ++ HOLD(UK95379) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287) COMMENT (***Action for PM88698: See PM88698 APAR/PTF text for additional information about why a REBIND is necessary. PM88698 corrects a problem that incorrect output could happen 1 for an SQL statement that contains special registers in GRPOUP BY and a view or table expression with UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI15888) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287) COMMENT (***Action for PI08763: See PI08763 APAR/PTF text for additional information about why a REBIND is necessary. PI08763 corrects a problem of incorrect output for an SQL statement that contains OUTER JOIN and subquery predicate, where the subquery predicate contains a table expression or view with UNION ALL. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI15912) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287) COMMENT (***Action for PI08206: See PI08206 APAR/PTF text for additional information about why a REBIND is necessary. PI08206 corrects the following problems: An ABEND0C4 RC00000038 at location DSNXGRDS DSNXOCT OFFSET0540 or ABEND0C4 RC00000004 at location DSNXGRDS DSNXRBND OFFSET0814 may occur when an SQL statement satisfies following conditions: 1. a statement contains nested UNION/UNION ALL with ORDER BY clause. 2. some sort-keys in the ORDER BY clause is not referenced in the select list. Incorrect output may occur when a SQL statement contains nested UNION/UNION ALL with FETCH FIRST 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.). UI22175 HOLD DATA END UI22212 HOLD DATA START UI22212 HOLD DATA END 1UI22227 HOLD DATA START UI22227 HOLD DATA END UI22407 HOLD DATA START ++ HOLD(UI22407) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14295) COMMENT (***Action for PI24616: See PI24616 APAR/PTF text for additional information about why a REBIND is necessary. PI24616 corrects a problem incorrect output for an SQL statement referencing an SQL inline table user defined function that contains multiple outer joins. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI22407 HOLD DATA END UI22568 HOLD DATA START UI22568 HOLD DATA END UI22611 HOLD DATA START UI22611 HOLD DATA END UI22642 HOLD DATA START UI22642 HOLD DATA END UI22644 HOLD DATA START UI22644 HOLD DATA END UI22646 HOLD DATA START UI22646 HOLD DATA END UI22682 HOLD DATA START ++ HOLD(UK98543) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (PM94543 corrects a problem of incorrect output returned when a range list access path is chosen for the table and the boolean term predicate not applied as matching predicate in all OR legs.). ++ HOLD(UK97939) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (PM94158 corrects a problem of incorrect output returned when query contains LIKE predicate with RTRIM/STRIP FUNCTION and literal pattern with blank pattern and index created on column in RTRIM/STRIP.). ++ HOLD(UK93759) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) 1 COMMENT (***Action for PM85238: See PM85238 APAR/PTF text for additional information about why a REBIND is necessary. PM85238 corrects a problem of incorrect output may be returned when a range list access path is chosen for the table and one of non-boolean term predicates under OR is not the matching predicate. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UK78270) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PM57955: See PM57955 APAR/PTF text for additional information about why a REBIND is necessary. PM57955 corrects a problem of ABEND04E RC00E70005 in DSNXORGL P130 when query with range list access (ACCESSTYPE = 'NR' in PLAN_TABLE) participated in parallel sort-merge join group. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). ++ HOLD(UI20796) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PI20948: See PI20948 APAR/PTF text for additional information about why a REBIND is necessary. PI20948 corrects a problem of incorrect output which may occur when a table is accessed via an index and the index column has an expression predicate 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(UI22682) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PI20473: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI20473 corrects a problem in which DB2 may improperly set the search range for a LIKE predicate when it is matching on an index. This may result in poor query performance. 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(UI21022) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PI18374: See PI18374 APAR/PTF text for additional information about why a REBIND is necessary. PI18374 corrects a problem that an inefficient access path may be chosen when there are two EQUAL predicates on the same partitioning key column, and the partitioning key consists of only a single 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(UI15802) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (PI08414 corrects a problem of incorrect output returned when SQL statements with range list access and fieldproc defined on index key.). UI22682 HOLD DATA END UI22684 HOLD DATA START ++ HOLD(UI22684) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PI26227: A rebind is necessary for static applications to rebuild access paths based on the changes in this APAR. PI26227 corrects a problem in which incorrect output may be generated for a query with an IS NULL predicate on a partitioning 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.). UI22684 HOLD DATA END UI22687 HOLD DATA START ++ HOLD(UK70809) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PM38025: See PM38025 APAR/PTF text for additional information about why a REBIND is necessary. PM38025 corrects a problem of incorrect output when like predicate is used as matching predicate and column is created with mixed data. 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(UI22687) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (PI17033 corrects an incorrect output problem that may occur when parallelism incorrectly builds the index key range for the child tasks. To make this fix effective for a static application, it must 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(UI18558) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (PI16101 corrects a problem where parallelism may incorrectly build the index key range for the child tasks when the query involves sort merge join and there is an IN predicate. As a result, an abend may occur during execution if the data in the rows falls outside the incorrectly built index key range. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI22687 HOLD DATA END UI22695 HOLD DATA START UI22695 HOLD DATA END UI22699 HOLD DATA START ++ HOLD(UI22699) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14304) COMMENT (***Action for PI22916: See PI22916 APAR/PTF text for additional information about why a REBIND is necessary. PI22916 corrects a problem of INCORROUT on a SELECT with CURRENT DEGREE = ANY and using the UNPACK 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.). UI22699 HOLD DATA END UI22717 HOLD DATA START ++ HOLD(UI22717) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14307) COMMENT (***Action for PI15740: A rebind is necessary for static applications to rebuild 1 access paths based on changes in this APAR. PI15740 corrects a problem where incorrect output can occur for a query which uses a range list access path and contains multiple range predicates on the same column in the same direction. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI22717 HOLD DATA END UI22737 HOLD DATA START UI22737 HOLD DATA END UI22764 HOLD DATA START UI22764 HOLD DATA END UI22773 HOLD DATA START ++ HOLD(UI22773) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14308) COMMENT (***Action for PI22465: See PI22465 APAR/PTF text for additional information about why a REBIND is necessary. PI22465 corrects a problem for a query with a LIKE predicate containing mixed data 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.). UI22773 HOLD DATA END UI22950 HOLD DATA START ++ HOLD(UI22950) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14316) COMMENT (***Action for PI26285: See PI26285 APAR/PTF text for additional information about why a REBIND is necessary. This apar corrects a problem that can cause DB2 to return an incorrect result, more rows than expected. The problem can occur for a query that includes a large indexable IN-List with many NULL elements that DB2 does not process properly. To make this fix effective for a static application, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI22950 HOLD DATA END 1 UI23100 HOLD DATA START UI23100 HOLD DATA END UI23122 HOLD DATA START ++ HOLD(UI18603) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14321) COMMENT (***Action for PI15409: See PI15409 APAR/PTF text for additional information about why a REBIND is necessary. PI15409 corrects a problem of incorrect output or ABEND04E RC00E70005 at DSNXOEXC M200 may occur for an SQL statement that satisfies the following conditions: 1. The SQL statement references an SQL in line table user defined function. 2. The SQL inline table user defined function references another SQL inline table user defined function inside a common table expression. 3. The second SQL inline table user user defined function references the function's argument inside a common 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(UI16457) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14321) COMMENT (***Action for PI12501: See PI12501 APAR/PTF text for additional information about why a REBIND is necessary. PI12501 corrects a problem of ABEND04E RC00E70005 at location DSNXGRDS DSNXGDT2 M201 when an SQL statement satisfies following conditions: 1. REFRESH TABLE with an MQT. 2. the MQT is defined with an IN predicate or quantified predicate containing row-value-expression and fullselect. 3. the data type against one of result columns from fullselect is character or graphic strings. To make this fix effective for a static application, it must 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(UI14016) SYS FMID(HDBAA10) REASON(ACTION) DATE(14321) COMMENT (***Action for PM98848: See PM98848 APAR/PTF text for additional information about why a REBIND is necessary. 1 PM98848 corrects a problem of SQLCODE -204 being issued when dropping a view or a Materialized Query Table that satisfies the following conditions: 1. The Materialized Query Table references a view. 2. The view contains an XMLTABLE. Run the following query to identity the problem views or Materialized Query Table on DB2 10 for z/OS: SELECT * FROM SYSIBM.SYSVIEWDEP WHERE BNAME = 'XMLTABLE' AND BTYPE = 'F' AND DTYPE = 'M'; Run the following query to identity the problem views or Materialized Query Table on DB2 11 for z/OS: SELECT * FROM SYSIBM.SYSDEPENDENCIES WHERE BNAME = 'XMLTABLE' AND BTYPE = 'F' AND DTYPE = 'M'; If there are rows returned please contact IBM support and we can provide a CATMAINT job that will clean up your catalog. Please supply the result of the query above and refer to APAR PM98848 when you open your SR with IBM support.). ++ HOLD(UI18603) SYS FMID(HDBAA10) REASON(ACTION) DATE(14321) COMMENT (***Action for PI15409: The following ACTION needs to be performed on behalf of this apar. Please note that along with the application of this fix, if the Table UDF (user-defined function) is nested, it will need to be dropped and recreated.). UI23122 HOLD DATA END UI23127 HOLD DATA START ++ HOLD(UI13035) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14321) COMMENT (See PM97952 APAR/PTF text for additional information. PM97952 is a pre-conditioning APAR that includes changes to enhance XMLTABLE performance which will be enabled via APAR PM98160 later. At this time, all changes are transparent to the user. In a data sharing group, this pre-conditioning APAR should be applied to all members before the enabling APAR is applied to any member. The performance enhancement is not enabled until the enabling APAR PM98160 is applied.). UI23127 HOLD DATA END UI23147 HOLD DATA START 1++ HOLD(UI18014) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14321) COMMENT (This PTF modifies the source code for DSNTIAUL (DB2 sample unload program). Applying the PTF updates only the DSNTIAUL source code. The updates do not affect your current DSNTIAUL load module until you reprepare and rebind it. * On DB2 10 systems running in conversion mode (CM) or enabling-new-function mode (ENFM), no action is required after applying this PTF. The updates will be used when you run the DB2 10 IVP jobs after DB2 enters new-function mode (NFM). * On DB2 10 systems in new-function mode, you need to take the following actions: (1) If you use a modified version of DSNTIAUL, redo your modifications (2) Run your customized copy of IVP job DSNTEJ2A to assemble and link-edit the load module and bind the plan for DSNTIAUL. Running this job will also verify that the DSNTIAUL was prepared and bound correctly.). ++ HOLD(UI23147) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14321) COMMENT (This PTF modifies the source code for DSNTIAUL (DB2 sample unload program). Applying the PTF updates only the DSNTIAUL source code. The updates do not affect your current DSNTIAUL load module until you reprepare and rebind it. * On DB2 10 systems running in conversion mode (CM) or enabling-new-function mode (ENFM), no action is required after applying this PTF. The updates will be used when you run the DB2 10 IVP jobs after DB2 enters new-function mode (NFM). * On DB2 10 systems in new-function mode, you need to take the following actions: (1) If you use a modified version of DSNTIAUL, redo your modifications (2) Run your customized copy of IVP job DSNTEJ2A to assemble and link-edit the load module and bind the plan for DSNTIAUL. Running this job will also verify that the DSNTIAUL was prepared and bound correctly.). UI23147 HOLD DATA END UI23171 HOLD DATA START ++ HOLD(UI23171) SYS FMID(HDBAA10) REASON(ACTION) DATE(14322) COMMENT (This apar corrects the problems fixed by apars PM88612 and PI08928. If the following query returns 0 rows SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1; No rows have been added and no further action is required. The job listed below can be used to add the correct rows if needed. Problem 1: 1 This apar corrects rows for the SYSIBM.SYSLGRNX table in SYSIBM.SYSCOLUMNS table. To see if you have rows that need to be updated run the query: SELECT NAME,FOREIGNKEY FROM SYSIBM.SYSCOLUMNS WHERE NAME='LGRPSID' AND TBNAME = 'SYSLGRNX' AND TBCREATOR = 'SYSIBM' AND FOREIGNKEY = 'S'; If this query returns rows you have rows that need to be updated. To update the rows run the job below. Problem 2: This apar corrects rows that were inserted into the catalog for the directory objects. To see if you have rows that need to be updated run the query: SELECT NAME,TBNAME,LENGTH(LABEL) FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'SYSIBM' AND TBNAME IN ('SYSUTIL','DBDR','SCTR','SPTR','SYSLGRNX','SYSUTILX') AND LENGTH(LABEL) <> 0; If this query returns rows you have rows that need to be updated. If there are rows that need to be updated for either problem, they can be corrected by running the job: CATMAINT UPDATE UNLDDN PI26218 This job will invalidate packages that are dependent on the directory tables, delete the catalog rows and then insert the correct rows. This job only needs to be run once and it corrects both problems if needed. It is only needed in V10 NFM.). UI23171 HOLD DATA END UI23321 HOLD DATA START UI23321 HOLD DATA END UI23340 HOLD DATA START UI23340 HOLD DATA END UI23388 HOLD DATA START UI23388 HOLD DATA END UI23410 HOLD DATA START 1++ HOLD(UI23410) SYS FMID(HDBAA10) REASON(ACTION) DATE(14329) COMMENT (Applying this APAR PI25748 will not fix existing column that have already been added. In order to fix the problem, after applies APAR PI25748, the user needs to 1. if no new data is inserted to the ALTERed table, execute REPAIR DBD REBUILD DATABASE database-name on the affected database 2. or if new data is inserted to the ALTERed table, then the table must be dropped then recreated. Please note, after new data is inserted into the ALTERed table, if without drop/recreate the table, the new column data is missing even after REPAIR REBUILD is performed and the subsequent queries could return incorrect output.). UI23410 HOLD DATA END UI23435 HOLD DATA START UI23435 HOLD DATA END UI23461 HOLD DATA START UI23461 HOLD DATA END UI23669 HOLD DATA START ++ HOLD(UI23669) SYS FMID(HDBAA10) REASON(ACTION) DATE(14339) COMMENT (This fix corrects a problem that the node id in the XML document is not assigned correctly during the partial update of an XML document. The fix does not fix the invalid node id in the existing XML document. If you suspect an XML document has invalid node id, you can use the following example UPDATE statement to do a whole document update which will reassign a new node id to every node in the document. Example: UPDATE ADMF001.TB_CUSTOMER_ACCOUNT_PBG SET CUSTOMER_CREATE_XML1 = XMLSERIALIZE(CUSTOMER_CREATE_XML1 AS CLOB) WHERE CUSTOMER_ID = 1;). UI23669 HOLD DATA END UI23679 HOLD DATA START ++ HOLD(UI22009) SYS FMID(HDBAA10) REASON(ACTION) DATE(14341) COMMENT (The PTF for APAR PI21602 has modified LOAD SHRLEVEL NONE and REORG SHRLEVEL NONE (NOSYSREC not specified) to abend with ABEND04E RC00E40800 after issuing message 1 DSNU3341I - CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT. The utilities will now abend so that a RESTART is possible.). UI23679 HOLD DATA END UI23690 HOLD DATA START ++ HOLD(UI23690) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14342) COMMENT (***Action for PI29176: See PI29176 APAR/PTF text for additional information about why a REBIND is necessary. PI29176 corrects a problem for SQL query acceleration when there are errors in the DB2 modified query text that DB2 routes to an accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must 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(UI22157) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14342) COMMENT (***Action for PI26089: See PI26089 APAR/PTF text for additional information about why a REBIND is necessary. PI26089 corrects a problem for SQL query acceleration where there are errors in the DB2 modified query text that DB2 routes to an accelerator. To make this fix effective for a static application containing accelerated static SQL queries, the application must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications could be affected by this change.). UI23690 HOLD DATA END UI23711 HOLD DATA START UI23711 HOLD DATA END UI23713 HOLD DATA START UI23713 HOLD DATA END UI23741 HOLD DATA START UI23741 HOLD DATA END UI23743 HOLD DATA START UI23743 HOLD DATA END 1 UI23745 HOLD DATA START UI23745 HOLD DATA END UI24088 HOLD DATA START UI24088 HOLD DATA END UI24103 HOLD DATA START UI24103 HOLD DATA END UI24475 HOLD DATA START UI24475 HOLD DATA END UI24481 HOLD DATA START UI24481 HOLD DATA END UI24794 HOLD DATA START UI24794 HOLD DATA END UI24847 HOLD DATA START UI24847 HOLD DATA END READY END