HOLDDATA FOR DB2 9.1 PUT Level ** Please read through all the holddata before acting on any of it. ** GENERAL

Transcription

1 HOLDDATA FOR DB2 9.1 PUT Level 0806 ** Please read through all the holddata before acting on any of it. ** GENERAL 1. Rebind all static DB2 application which match criteria. Member REBIND DSN910.SVSC.HOLDCNTL can be used to do that 2. The following PTFs require additional action: UK Run DSN910.SVSC.HOLDCNTL(D06TEJ1L) UK Stop schedular - from SDSF command line issue the UK37311 following command: /F DB9GADMT,APPL=SHUTDOWN - If you have never run DSNTIJSG, you can run job DSN910.SVSC.HOLDCNTL(D#6TIJSG) - Otherwise run DSN910.SVSC.HOLDCNTL(D06TIJSG) to rebind - Restart schedular - from SDSF issue /S DB9GADMT - Refresh WLM environments: DB9GENV6 from SDSF command line issue the following command: /V WLM,APPLENV=DB9GENV6,REFRESH UK Run DSN910.SVSC.HOLDCNTL(D06BJAR) ********************* HOLDDATA **************************************** SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 21, 2008 System: S0W1 Time: 09:35:09 ***************************************************************** * The following PTFs have HOLD Reason: ACTION * ***************************************************************** UK37370 Jul 17, :55 Jul 21, :23 UK37370 HDB HOLD(UK37370) SYS FMID(HDB9910) REASON(ACTION) DATE(08168) (**Action for PK63580 (V9) Process the following commands to bind the packages that updated as a result of installing this PTF: BIND PACKAGE(DSNJAR) MEMBER(DSNX9LDJ) - ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) - LIBRARY('<prefix>.SDSNDBRM') Note: <prefix> is the data set prefix of your DB2 V9). UK37311 Jul 17, :55 Jul 21, :23 UK37311 HDB HOLD(UK37311) SYS FMID(HDB9910) REASON(ACTION) DATE(08164) (This PTF modifies the DB2-supplied stored procedure SYSPROC.GET_SYSTEM_INFO to allow it to return only specific sets of information as requested. *************************************************************** Actions for customers who are already using DB2 V9: ***************************************************************

2 If you have already installed or migrated to DB2 V9 then after applying this PTF, you need to refresh the WLM environments used by the following modified stored procedures: SYSPROC.GET_CONFIG SYSPROC.GET_MESSAGE SYSPROC.GET_SYSTEM_INFO It is not necessary to refresh the packages for these stored procedures ). UK37286 Jul 17, :55 Jul 21, :23 UK37286 HDB HOLD(UK37286) SYS FMID(HDB9910) REASON(ACTION) DATE(08164) (To activate the changes in this PTF you need to take following actions: (1) Stop the scheduler for administrative tasks. (2) Bind the packages of the scheduler. (3) Start the scheduler again. Each of these actions is detailed below. Note that DB2 must be running. (1) If the scheduler is running, stop it first by executing following console command: modify dsnadmt,appl=shutdown where dsnadmt is the name of the scheduler. (2) Bind the scheduler packages as follows: (a) Make a work copy of your customized copy of DSNTIJSG. (b) Remove all job steps except DSNTIAS. (c) In job step DSNTIAS, remove all CREATE statements and remove the BIND PACKAGE commands for members DSNADMTU, DSNA6THP and DSNADMCD. (d) Run the modified job to bind the scheduler packages. (e) When finished, you can erase the work copy of the job. For data sharing, this action needs to be performed only once for the group. (3) Start the scheduler again by executing following console command: start dsnadmt where dsnadmt is the name of the scheduler.). UK37399 Jul 17, :55 Jul 21, :23 UK37399 JDB9914 PK HOLD(UK37399) SYS FMID(JDB9914) REASON(ACTION) DATE(08169) (***Action for PK This PTF adds DSNEDP02, a new DCLGEN ISPF panel to the SDSNPFPE target library. This PTF also updates DSNEDP01, the main DCLGEN ISPF panel, in the SDSNPFPE target library as follows: - It adds a new field, ADDITIONAL OPTIONS, for choosing whether to display or suppress the new DCLGEN options panel. - It moves an existing field, RIGHT MARGIN, to the new panel See the cover letter for information about the changes to DCLGEN.. If you keep the DCLGEN panels in a library other than SDSNPFPE then after applying this PTF, you need to copy the updated DSNEDP01 member and the new DSNEDP02 member to that library.).

3 UK37292 Jul 17, :55 Jul 21, :23 UK26565 HDB HOLD(UK26565) SYS FMID(HDB9910) REASON(ACTION) DATE(08164) (IMPACT on INSTALLED BASE Existing external Stored Procedures and external User Defined Functions are not affected by this change. They can continue to return shorter diagnostic strings when signalling errors, even though DB2 will allocate more storage backing them. Stored procedure and User Defined Function providers can modify their programs to take advantage of the new limit. However, please note that a REBIND is necessary after providers modified their programs.). UK37243 Jul 17, :55 Jul 21, :23 UK37243 HDB9910 PK HOLD(UK37243) SYS FMID(HDB9910) REASON(ACTION) DATE(08162) (***Action for PK63665 (V9) This PTF updates the source code for DSNTEP2 and DSNTEP4 plus the shipped object decks (DSNTEP2L and DSNTEP4L) and shipped DBRMs (DSN@EP2L and DSN@EP4L). These changes do not become effective until you rebuild the load modules and rebind the plans. * On DB2 V9 systems running in compatibility mode (CM) or enabling-new-function mode (ENFM), no further action is required after applying this PTF. The updates will be used when you run the V9 IVP jobs after DB2 V9 enters new-function mode. * On DB2 V9 systems in new-function mode, proceed as follows: (a) If you use DSNTEP2 or DSNTEP4 (or both) as supplied by DB2, run IVP job DSNTEJ1L to relink the load modules from the shipped object modules and bind the plans from the shipped DBRMs. (b) If you use a modified version of DSNTEP2 or DSNTEP4 (or both) redo your modifications and then run IVP job DSNTEJ1P to recompile and link-edit the load modules and bind the plans for DSNTEP2 and DSNTEP4.). UK37222 Jul 17, :55 Jul 21, :23 UK36117 HDB9910 PK HOLD(UK36117) SYS FMID(HDB9910) REASON(ACTION) DATE(08162) (***Action for PK64555: PK64555 corrects a problem of ABEND0C4 RC38 DSNXOP0 +8A3A +82B2 for the query satisfying the following conditions: 1. The query references a view or table expression which contains UNION ALL. 2. The query select list contains AS name. 3. The query select list contains aggregate

4 function. To make this fix effective, if the symptom occurs due to reference a view satisfying the described conditions, then the problem view must be dropped and recreated after the application of this PTF.). UK37145 Jul 17, :55 Jul 21, :23 UK28260 HDB HOLD(UK28260) SYS FMID(HDB9910) REASON(ACTION) DATE(08158) (IFCID 022 data sections 2 and 3 mapped by QW0022P and QW0022X, respectively, are now varying length repeating groups. Prior to this APAR (PK42318), these sections could be improperly formatted if long names were present in the data. While the change to a varying length repeating group corrects the formatting issue, the parsing algorithm for IFCID 022 has been changed; please refer to macro DSNDQWT0 for a full description of the varying length repeating group parsing algorithm. Any applications or monitors parsing IFCID 022 may need to be changed to support the corrected format.). UK36866 Jul 17, :54 Jul 21, :23 UK36866 HIZ HOLD(UK36866) SYS FMID(HIZ9910) REASON(ACTION) DATE(08149) (In order for this PTF to be fully effective, an IPL or REFRESH DB2,EARLY is required. The DB2 member should be stopped before issuing the REFRESH DB2, EARLY command.). UK31692 Jul 17, :54 Jul 21, :23 UK36224 HDB9910 PK HOLD(UK36224) SYS FMID(HDB9910) REASON(ACTION) DATE(08163) (***Action for PK56021 (V9) (1) This PTF modifies the installation sample job DSNTEJ1 in the prefix.sdsnsamp target library. If you keep customized copies of this sample job in a different library, then after applying this PTF, you need to update them to add the following step: //* //* STEP 33: REORGANIZE TABLESPACE DSN8D91A.DSN8S91R //* AND DSN8D91A.DSN8S91S TO RESET //* REORG-PENDING STATUS //* //PH01S33 EXEC DSNUPROC,PARM='DSN,DSNTEX',COND=(4,LT) //SORTLIB DD DSN=SYS1.SORTLIB,DISP=SHR //SORTOUT DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND) //DSNTRACE DD SYSOUT=* //SYSUT1 DD UNIT=SYSDA,SPACE=(4000,(50,50),,,ROUND) //SYSREC DD UNIT=SYSDA,SPACE=(4000,(200,200),,,ROUND) //SYSIN DD * REORG TABLESPACE DSN8D91A.DSN8S91R SORTDEVT(SYSDA) SORTNUM 4

5 REORG TABLESPACE DSN8D91A.DSN8S91S SORTDEVT(SYSDA) SORTNUM 4 - If necessary, change the first option in the DSNUPROC parm list from DSN to your subsystem name (as specified in field 1 SUBSYSTEM NAME of installation panel DSNTIPM). - If necessary, change DSN=SYS1.SORTLIB to the name of your system sort library (as specified in field 3 SORT LIBRARY of installation panel DSNTIPW). (2) If you have already run installation sample job DSNTEJ1, then issue the -DISPLAY DB(DSN8D91A) command to check if the table space DSN8S91R and DSN8S91S are in advisory REORG-pending (AREO) status. If the table spaces are in advisory REORG-pending status, then customize and resubmit job DSNTEJ1 to run the REORG utility in STEP 33.). UK31692 Jul 17, :54 Jul 21, :23 UK31692 HDB HOLD(UK31692) SYS FMID(HDB9910) REASON(ACTION) DATE(08163) (PK52905 introduces the following incompatible change for DB2 9: A version generating ALTER TABLE ADD COLUMN and DML in the same commit scope will be blocked. If a version generating ALTER TABLE ADD COLUMN follows DML in the same commit scope, an SQLCODE -910 will be issued. The same will result if DML follows a version generating ALTER TABLE ADD COLUMN in the same commit scope. As a result, all applications where a version generating ALTER TABLE ADD COLUMN and DML are in the same commit scope will require modification so that they are in different units of work. DB2 will generate a new table space version when adding a column to a table, except for the following cases: 1.When the table resides in a non-partitioned table space and the table is already versioned and there is no data in the current committed version format. 2.When the containing table space has the DEFINE NO attribute. This PTF also modifies the DB2 for z/os V9 sample job DSNTEJ1. If you have created a customized copy of this job, then after applying this PTF, you need to modify the PH01S02 step by adding a COMMIT statement to the following: - After the CREATE VIEW DSN8910.VDSPTXT statement and before ALTER TABLE DSN8910.DEPT statement - After the ALTER TABLE DSN8910.PROJ statement and before CREATE TABLE DSN8910.EDEPT statement - After the CREATE TABLE DSN8910.EEPA statement and before the ALTER TABLE DSN8910.EDEPT statement - After the ALTER TABLE DSN8910.EEPA statement and before the CREATE SEQUENCE DSN8910.POID statement If you have already run DSNTEJ1 on DB2 for z/os V9, it is not necessary to rerun it. If you have not yet created a customized copy of DSNTEJ1, no further action is needed - the changes will be picked up when you run the DB2 installation CLIST.). UK37084 Jul 17, :55 Jul 21, :23 UK37084 HDB HOLD(UK37084) SYS FMID(HDB9910) REASON(ACTION) DATE(08157)

6 (This PTF modifies the installation job DSNTIJIN in the prefix.sdsnsamp target library. If you keep copies of this sample job in a different library, then after applying this PTF, you need to update your copy of DSNTIJIN by increasing the BSDS from RECORDS (860 20) to RECORDS ( ) and the BSDS index from RECORDS (5 5) to RECORDS (66 33). If you have not yet converted your BSDS to the new format, then before running the DSNJCNVB utility you need to increase the minimum space allocation of the BSDS to the new sizes noted above. Otherwise, the conversion may fail with space allocation errors.). SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 21, 2008 System: S0W1 Time: 09:35:09 ***************************************************************** * The following PTFs have HOLD Reason: DB2BIND * ***************************************************************** UK37384 Jul 17, :55 Jul 21, :23 UK37384 HDB9910 PK HOLD(UK37384) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08168) (***Action for PK65062: See PK65062 APAR/PTF text in the PTF cover letter for PK65062 corrects a problem of ABEND04E RC00E70005 at DSNXORLI:P001 when a UNION/UNION ALL query contains a lit constant on some of the UNION/UNION ALL subselect selection list running in parallel. UK37292 Jul 17, :55 Jul 21, :23 UK37292 HDB9910 PK HOLD(UK37292) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08164) (***Action for PK59752: PK59752 provides new function support for the PACKAGE PATH option used on the SQL statements CREATE PROCEDURE and CREATE FUNCTION. See PK59752 APAR/PTF text in the PTF cover letter for additional information about why a REBIND may be necessary for some applications that will use this function.). UK37292 Jul 17, :55 Jul 21, :23 UK26565 HDB9910 PK HOLD(UK26565) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08164) (***Action for PK42911:

7 See PK42911 APAR/PTF text in the PTF cover letter for The current limit for a diagnostic message for an external Stored Procedure or an external User Defined Function with the PARAMETER STYLE SQL option is 70 bytes. PK42911 extends the size of this diagnostic message from 70 bytes to 1000 bytes for DB2 R910. To utilize this feature for a static SQL application which invokes a Stored Procedure or a User Defined Function which has been modified to take advantage of this new function, a rebind will be needed after application of this PTF. Please review the PTF cover letter to determine which, if any, applications could be UK37267 Jul 17, :55 Jul 21, :23 UK37267 HDB HOLD(UK37267) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08163) (See PK07362 APAR/PTF text in the PTF cover letter for APAR PK07362 corrects a problem that can cause an locking problem. UK37244 Jul 17, :55 Jul 21, :23 UK37244 HDB9910 PK HOLD(UK37244) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08162) (***Action for PK64709: See PK64709 APAR/PTF text in the PTF cover letter for PK64709 corrects a problem of incorrect output that may occur on a query containing both an OR predicate and host variables (or parameter markers), if both page range screening and multi-index access are chosen by DB2. UK37242 Jul 17, :55 Jul 21, :23 UK37242 HDB9910 PK HOLD(UK37242) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08162) (***Action for PK65589: See PK65589 APAR/PTF text in the PTF cover letter for

8 Apar PK65589 corrects a problem that can result in an ABEND04E RC00E70005 at location DSNNOGET:M720. UK37240 Jul 17, :55 Jul 21, :23 UK37226 HDB9910 PK HOLD(UK37226) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08162) (***Action for PK65257: See PK65257 APAR/PTF text in the PTF cover letter for PK65257 corrects a problem with choosing an index path over R-scan when the index column cannot be used for the range predicate because the column is randomized in the index. UK37240 Jul 17, :55 Jul 21, :23 UK37206 HDB HOLD(UK37206) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08162) (See PK63622 APAR/PTF text in the PTF cover letter for PK63622 corrects a problem where a less efficient access path may be chosen when the inner table of a nested loop join (NLJ) has an IN-list or IN-subquery predicate as an index matching predicate. UK37222 Jul 17, :55 Jul 21, :23 UK35613 HDB9910 PK HOLD(UK35613) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08162) (***Action for PK63582: See PK63582 APAR/PTF text in the PTF cover letter for PK63582 corrects a problem of incorrect output when a query references a table expression or view containing UNION ALL and the query also references a predicate containing a host variable or parameter marker.

9 UK37145 Jul 17, :55 Jul 21, :23 UK28260 HDB9910 PK HOLD(UK28260) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08158) (***Action for PK42318: See PK42318 APAR/PTF text in the PTF cover letter for PK42318 corrects a problem of possible incorrect trace data for IFCID 022, which records miniplans that are generated for an SQL statement. UK37123 Jul 17, :55 Jul 21, :23 UK37123 HDB9910 PK HOLD(UK37123) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK65889: See PK65889 APAR/PTF text in the PTF cover letter for PK65889 corrects a problem of incorrect output for queries that contain a DISTINCT set function in the select list and a GROUP BY clause. UK37123 Jul 17, :55 Jul 21, :23 UK36788 HDB9910 PK HOLD(UK36788) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK64209: See PK64209 APAR/PTF text in the PTF cover letter for PK64209 corrects a problem of an incorrect order for the result of a query containing an ORDER BY that may occur when the ORDER BY refers to expressions.

10 UK37110 Jul 17, :55 Jul 21, :23 UK34230 HDB9910 PK HOLD(UK34230) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK60603: See PK60603 APAR/PTF text in the PTF cover letter for PK60603 corrects a problem of abend in DSNXGRDS.DSNXRDEC+2B92 when a query selection list contains a decimal constant number and running in parallel. UK37110 Jul 17, :55 Jul 21, :23 UK33578 HDB9910 PK HOLD(UK33578) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK58483: See PK58483 APAR/PTF text in the PTF cover letter for PK58483 corrects a problem of ABEND04E RC00C90101 at DSNIDM. DSNIZMOS:5016 when a query contains union/union all and different subselect returns different data type like date column and literal constant string and runs in parallel. UK37110 Jul 17, :55 Jul 21, :23 UK32637 HDB9910 PK HOLD(UK32637) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK55236: See PK55236 APAR/PTF text in the PTF cover letter for PK55236 corrects a problem of abend in DSNXESX2:P403 when a parallel-sort group is disabled at bindtime due to the record length of the parallel group exceeds the 32K limit. UK37110 Jul 17, :55 Jul 21, :23 UK37110 HDB9910 PK53221

11 ++ HOLD(UK37110) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK53221: See PK53221 APAR/PTF text in the PTF cover letter for PK53221 corrects a problem of ABEND04E RC00E70005 DSNXESX2:P404 when a query contains RANK functions and runs in parallel. UK37110 Jul 17, :55 Jul 21, :23 UK27173 HDB9910 PK HOLD(UK27173) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (***Action for PK46464: See PK46464 APAR/PTF text in the PTF cover letter for PK46464 corrects a problem of 04E ABEND RC00E70005 in DSNOGLOB ERQUAL5001 when query contains insert with subselect on a LOB column, and subselect is running in parallel. UK37098 Jul 17, :55 Jul 21, :23 UK37098 HDB HOLD(UK37098) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (See PK65030 APAR/PTF text in the PTF cover letter for PK65030 corrects a filter factor estimation problem for correlated subquery predicates that could result in slow query performance. UK37098 Jul 17, :55 Jul 21, :23 UK32099 HDB HOLD(UK32099) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08157) (See PK56230 APAR/PTF text in the PTF cover letter for PK56230 corrects a problem of possible poor query performance due to an incorrect filter factor calculation for an IN

12 predicate. This can occur when the IN predicate contains a non-correlated subquery that contains a declared global temporary table (DGTT), and the number of rows in the DGTT is small. UK37068 Jul 17, :55 Jul 21, :23 UK37068 HDB HOLD(UK37068) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08156) (See PK65293 APAR/PTF text in the PTF cover letter for APAR PK65293 corrects a problem that can cause an abend when a COMMON TABLE EXPRESSION (CTE) is involved in starjoin and the query referencing the CTE contains UNION/UNION ALL in a table expression. UK37025 Jul 17, :55 Jul 21, :23 UK37025 HDB9910 PK HOLD(UK37025) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08155) (***Action for PK62882: See PK62882 APAR/PTF text in the PTF cover letter for PK62882 corrects a problem of ABEND04E RC00E70005 DSNXGPGR:M160 when a query contains nested IN/EXISTS subquerys and hybrid join running in parallel. UK37001 Jul 17, :55 Jul 21, :23 UK37001 HDB9910 PK HOLD(UK37001) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08154) (***Action for PK63191: See PK63191 APAR/PTF text in the PTF cover letter for PK63191 corrects a problem of less rows being returned from a query whose predicate is pushed into a materialized view and the predicate triggers a transitive closure predicate to be generated inside the view definition where the transitive closure predicate references multiple encoding scheme operands.

13 To make this fix effective for a static application or a package, it must be rebound after application of this PTF. Review the PTF cover letter to determine which, if any, applications or packages could be UK36978 Jul 17, :54 Jul 21, :23 UK36978 HDB HOLD(UK36978) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08154) (See PK64293 APAR/PTF text in the PTF cover letter for APAR PK64293 corrects a problem that can cause an abend for a query running with I/O parallelism and the table is accessed via DPSI index. UK36978 Jul 17, :54 Jul 21, :23 UK35539 HDB HOLD(UK35539) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08154) (See PK62064 APAR/PTF text in the PTF cover letter for PK62064 disables parallelism when a query is run in parallelism and a materialized outer join result exists in the parallel group. UK36978 Jul 17, :54 Jul 21, :23 UK35969 HDB HOLD(UK35969) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08154) (See PK60079 APAR/PTF text in the PTF cover letter for PK60079 fixes an incorrect output problem when a query is run in parallelism with sort merge join, where a sort on the composite table is processed 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 UK36791 Jul 17, :54 Jul 21, :23 UK36791 HDB9910 PK64965

14 ++ HOLD(UK36791) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08148) (***Action for PK64965: See PK64965 APAR/PTF text in the PTF cover letter for PK64965 corrects a problem of incorrect out when query contains nested IN/EXISTS and indexable IN subquery predicate. UK36791 Jul 17, :54 Jul 21, :23 UK36412 HDB HOLD(UK36412) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08148) (See PK63350 APAR/PTF text in the PTF cover letter for APAR PK63350 corrects a problem that can cause incorrect output for a query that has an IN-subquery in the subselect under an update statement. UK36790 Jul 17, :54 Jul 21, :23 UK36790 HDB9910 PK HOLD(UK36790) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08148) (***Action for PK64395: See PK64395 APAR/PTF text in the PTF cover letter for PK64395 corrects a problem ABEND0C4 DSNXOGA1 +051A when query contains non-boolean term subquery predicate with select DISTINCT and an indexable IN subquery predicate. UK36790 Jul 17, :54 Jul 21, :23 UK26002 HDB HOLD(UK26002) SYS FMID(HDB9910) REASON(DB2BIND) DATE(08148) (See PK45658 APAR/PTF text in the PTF cover letter for APAR PK45658 corrects a problem that can cause an incorrect out for a query containing order by and fetch fist N row only

15 SMP/E HOLDDATA Report JES Node: SVSCJES2 PTF Detail Report Date: Jul 21, 2008 System: S0W1 Time: 09:35:09 ***************************************************************** * The following PTFs have HOLD Reason: DOC * ***************************************************************** UK37292 Jul 17, :55 Jul 21, :23 UK26565 HDB HOLD(UK26565) SYS FMID(HDB9910) REASON(DOC) DATE(08164) (Along with the supporting code change, this apar will also make the following publication changes to the Application Programming and SQL Guide. Publication changes for DB2 R For DB2 R910, a 1000 byte diagnostic message is supported. In Chapter 26. "Stored Procedures for client/server processing", Section 'Example of stored procedure linkage conversion SQL', CHANGE the following assembler code in Figure 234, LOCDIAG DS H,CL70 LOCAL COPY OF DIAGNOSTIC DATA TO, LOCDIAG DS H,CL1000 LOCAL COPY OF DIAGNOSTIC DATA CHANGE the following C code in Figure 236, p_diag charr71ù, TO, p_diag charr1001ù, Note: Code comments remain unchanged. CHANGE the following COBOL code in Figure 237, 49 P-DIAG-TEXT PIC X(70). TO, 49 P-DIAG-TEXT PIC X(1000). CHANGE the following PL/I code in Figure 238, DCL 01 P-DIAG CHAR(70) VARYING;

16 TO, DCL 01 P-DIAG CHAR(1000) VARYING; Note: Code comments remain unchanged.). UK37255 Jul 17, :55 Jul 21, :23 UK37255 HDB HOLD(UK37255) SYS FMID(HDB9910) REASON(DOC) DATE(08163) (The PTF for APAR PK62998 has added the following documentation changes to the Messages manual. MSGDSNU1350I lists an incorrect statistic name KEYCARDF instead of CARDF as follows: DSNU1350I csect-name SYSKEYTARGETSTATS CATALOG STATISTICS FOR index-name KEYSEQ keyseq-num PARTITION part-num KEYCARDF = cardinality HIGHKEY = highkey HIGH2KEY = high2key LOWKEY= lowkey LOW2KEY= low2key The message description for MSGDSNU1350I was corrected in Messages manual as follows: DSNU1350I csect-name SYSKEYTARGETSTATS CATALOG STATISTICS FOR index-name KEYSEQ keyseq-num PARTITION part-num CARDF = cardinality HIGHKEY = highkey HIGH2KEY = high2key LOWKEY= lowkey LOW2KEY= low2key MSGDSNU1351I lists an incorrect statistic name KEYCARDF instead of CARDF as follows: DSNU1351I csect-name SYSKEYTARGETS CATALOG STATISTICS FOR index-name KEYSEQ keyseq-num KEYCARDF = cardinality HIGH2KEY = high2key LOW2KEY= low2key The message description for MSGDSNU1351I was corrected in the Messages manual as follows: DSNU1351I csect-name SYSKEYTARGETS CATALOG STATISTICS FOR index-name KEYSEQ keyseq-num CARDF = cardinality HIGH2KEY = high2key LOW2KEY= low2key). UK36744 Jul 17, :54 Jul 21, :23 UK28730 HDB HOLD(UK28730) SYS FMID(HDB9910) REASON(DOC) DATE(08144)

17 (See PK48032 APAR/PTF text for additional information. The following subsection under REPAIR in the Utility Guide and Reference will be updated to remove references to XML: SET statement option descriptions NOAUXWARN Specifies that the auxiliary warning (AUXW) status of the specified table space is to be reset. The specified table space must be a base table space or LOB table space.). UK31692 Jul 17, :54 Jul 21, :23 UK31692 HDB HOLD(UK31692) SYS FMID(HDB9910) REASON(DOC) DATE(08163) (SQL REFERENCE Under ALTER TABLE Notes section: Notes Restrictions on data change statements in the same unit of work as ALTER TABLE with certain clauses: Data change statements cannot follow, in the same unit of work, ALTER TABLE statements that specify any of the following clauses: -ADD PARTITION -ADD PARTITIONING KEY -ALTER COLUMN SET DATA TYPE -ROTATE FIRST TO LAST -ADD COLUMN that results in a new version ADMINISTRATION GUIDE section 'Table space versions' will be updated as follows: Table space versions DB2 creates a table space version each time you commit one or more of the following schema changes by using the ALTER TABLE statement: - Extend the length of a character (char data type) or graphic (graphic data type) column - Change the type of a column within character data types (char, varchar) - Change the type of a column within graphic data types (graphic, vargraphic) - Change the type of a column within numeric data types (small integer, integer, float, real, float8, double, decimal) - Add a column to a table - Extend the length of a varying character (varchar data type) or varying graphic (vargraphic data type) column, if the table is already versioned. Exceptions: DB2 does not create a table space version under the following circumstances: - When the data sets of the table space is not defined - When you extend the length of a varying character. (varchar data type) or varying graphic (vargraphic data type) column, and the table is not already versioned. - When you specify the same data type and length that a column currently has, such that its definition does not actually change. - When you add a column to a table in a non-partitioned table space, and the table is already versioned with no data in the current committed version format.).