Scope: All DB2 Users
Effective Date: 4/1/2015
Group Name: Z_SW_TDS_DB2_SYSTEMS
Affected Locations: All sites
Summary: Provide DB2 Hold data and cover letters for DB2 V10 Maintenance, HP release level AH00 (IBM RSU1501+)
Justification: IBM DB2 software frequently requires actions to be taken to fully implement the fixes being applied. Often these actions are the type of work done by DBA's (Database Administrators) and/or application support staff. As an example, many fixes require DB2 binds to implement the maintenance. If these actions aren't taken, the fixes generally will not take effect, though most often will not cause any adverse effect otherwise.
Benefits to Users: Alert non-systems support staff of actions they may need to take to fully implement maintenance fixes supplied by the vendor.
Details: Please see the attachments for the details on the fixes being applied with this current level of maintenance and any hold actions that may be required. Please note, that the actions required for subsystem level items are handled by Z_SW_TDS_DB2_SYSTEM team, and need not be addressed by application developers or DBA's.
Primary Contact: Cathy Puzzuoli (cathy.puzzuoli@hpe.com)
Secondary Contact: TDSDB2@HP.COM
UI14824 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI05930 -
****************************************************************
* USERS AFFECTED: Users of clone table. *
****************************************************************
* PROBLEM DESCRIPTION: EXCHANGE DATA statement takes too long. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
EXCHANGE DATA between a base table and its clone table does
a DRAIN(ALL) on both the base and clone objects. This is not
necessary after PM33354 applied.
DB2 is changed to not lock or drain the table space on
EXCHANGE DATA statement.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI05930
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDACL PI05930
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI05930 DSNGDACL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDACL
LISTEND
UI14824 COVER LETTER END
UI14871 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI05582 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND878 RC10 occurred in module *
* DSN9SCN9 because of a shortage of DB2 *
* LSQA storage. *
* The problem occurred when DB2 was *
* started and an active log data set *
* was full, so a log offload was started *
* and received this ABEND878. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An ABEND878 RC10 occurred in module DSN9SCN9 because of a
shortage of DB2 LSQA storage.
Module DSN3RRSC has been to avoid this DB2 LSQA storage
shortage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI05582
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3RRSC PI05582
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI05582 DSN3RRSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3RRSC
LISTEND
UI14871 COVER LETTER END
UI15538 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM94646 -
****************************************************************
* USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) *
* users in DATASHARING SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 users may encounter abend: *
* ABND=04E-00D30014 because deadlock exit *
* is driven with invalid userdata. *
* *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
Whenever a deadlock cycle is detected, IRLM will:
. Drive the first exit to DBMS to collect information about the
resource, owner and user data.
. Drive the second exit to inform the DBMS about the victim to
break the deadlock ccycle.
The logic is applied to both local and global deadlock cycle.
Under certain conditions, the first exit of a local deadlock
cycle is skipped, but its second deadlock exit is scheduled
and driven to the DBMS. Without the user data obtaining from
the return of the first deadlock exit, the second deadlock exit
includes invalid user data in its deadlock parameter list.
This invalid userdata in the second deadlock exit causes the
abend in DB2.
1 GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code is added to drive the first exit for a local deadlock
cycle.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM94646
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL242 PM94646
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM94646 DXRRL242
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL242
LISTEND
UI15538 COVER LETTER END
UI15543 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM92230 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM230) users. *
****************************************************************
* PROBLEM DESCRIPTION: AbendS0C4 occurred in DXRRL24H because *
* the address of the first RHWA element *
* in the segment had dirty high-half. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM accessed the RHWA segments to perform the storage
compression for the RHWA pool. In one of the segment,
the address of the first element contained dirty high-half
causing the S0C4 abend.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Since RHWA pool resides below the BAR, a 31-bit pointer is
used to access the first RHWA element in the segment.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM92230
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL24H PM92230
DXRRL272 PM92230
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM92230 DXRRL24H DXRRL272
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL24H
DXRRL272
LISTEND
UI15543 COVER LETTER END
UI15845 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06781 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of an SQL *
* statement that contains a table expression *
* or view with a COUNT(*) or COUNT_BIG(*) in *
* the SELECT list, and the COUNT(*) or *
* COUNT_BIG(*) is referenced in a sub-query *
* predicate. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE120 could be incorrectly issued *
* for an SQL statement that contains a *
* table expression or view with a *
* COUNT(*) or COUNT_BIG(*) in the SELECT *
* list, and the COUNT(*) or COUNT_BIG(*) *
* is referenced in a sub-query predicate. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
WITH TX1 AS
(SELECT CREATOR
,COUNT(*) AS NUM_ROWS
FROM SYSIBM.SYSTABLES TB1
WHERE CREATOR = 'SYSIBM'
GROUP BY CREATOR
)
SELECT CREATOR
,NUM_ROWS
FROM TX1
WHERE EXISTS
(SELECT *
FROM SYSIBM.SYSTABLES TB2
WHERE TB2.CREATOR = TX1.CREATOR
AND TB2.COLCOUNT = TX1.NUM_ROWS)
1 ;
DB2 did not correctly process the aforementioned SQL statement,
which caused the incorrect SQLCODE120.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no SQLCODE120.
Additional keywords: SQLTABLEEXPR SQLCTE SQLSUBQUERY SQLVIEW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06781
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEXE PI06781
DSNXOEX1 PI06781
DSNXOOS1 PI06781
DSNXOVC PI06781
DSNXOW1 PI06781
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06781 DSNXOEXE DSNXOEX1 DSNXOOS1 DSNXOVC DSNXOW1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEXE
1 DSNXOEX1
DSNXOOS1
DSNXOVC
DSNXOW1
LISTEND
UI15845 COVER LETTER END
UI16018 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM93687 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM230) users in DATASHARING *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM abended U2023 in DXRRL731 because *
* a GETMAIN request for below-the-BAR *
* private storage failed. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
A GDM - Global Deadlock Manager - received a large number of
deadlock information message segments from its peers. The GDM
tried to merge all message segments into a single big one.
Although there were lots of smaller freed segments in the Local
Variable Storage pool, not a single segment was big enough for
the GDM to merge all the messages. Also, the compression logic
did not compress the freed variable segments very efficiently.
This forced the IRLM storage manager to make a new GETMAIN
request with large size. The request failed causing the 2031
abend in DXRRL731.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
As in the case of the NOTIFY request with large message (greater
than 4 megabytes), the storage for the deadlock external cycle
information will be obtained from the hybrid pool. This storage
will be released back to the system right after the deadlock
external cycle information is processed.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM93687
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL24I PM93687
DXRRL731 PM93687
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM93687 DXRRL24I DXRRL731
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DXRRL24I
DXRRL731
LISTEND
UI16018 COVER LETTER END
UI16189 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI08758 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of IN subquery *
* predicates and parallelism. *
* *
* All DB2 10 for z/OS users of views with *
* UNION ALL and a specific timestamp *
* precision. *
* *
* All DB2 10 and DB2 11 for z/OS users of *
* SQL user defined table function with *
* any Common Table Expression. *
****************************************************************
* PROBLEM DESCRIPTION: 1.An ABEND04E RC00E70005 at location *
* DSNXGDT2 M201 may occur for an SQL *
* statement that satisfies all of the *
* following conditions: *
* 1. The SQL statement contains an IN *
* subquery predicate. *
* 2. The subquery contains UNION/UNION *
* ALL. *
* 3. The left hand side data type of *
* the IN subquery predicate is DATE *
* or TIME and the data type returned *
* from the subquery is CHAR or VARCHAR. *
* 4. Parallelism is used *
* *
* 2.An ABEND04E RC00E70005 at location *
* DSNXGDT2 M206 may occur for an SQL *
* statement that satisfies all the *
* following conditions: *
* 1. The SQL statement references a view *
* with UNION ALL. *
* 2. The view column data type is *
* TIMESTAMP. *
* *
* 3. An ABEND04E RC00E70005 at location *
* DSNXOOS2 M265 may occur for an SQL *
* statement that references an SQL *
* user defined table function and *
* a Common Table Expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. ABEND04E RC00E70005 at location DSNXGDT2 M201
1 CREATE TABLE T1 (C11 INT, C12 DATE);
CREATE TABLE T2 (c21 INT, C22 DATE);
CREATE TABLE T3 (c31 INT, C32 DATE);
SELECT C12 FROM T1
WHERE (C12) IN (SELECT CHAR(C22,ISO) FROM T2
UNION
SELECT CHAR(C32,ISO) FROM T3);
An abend may occur for the SQL statement above because DB2
did not set the CCSID of the subquery correctly.
2. ABEND04E RC00E70005 at location DSNXGDT2 M206
For Example,
CREATE TABLE T1 (C1 TIMESTAMP(12));
CREATE TABLE T2 (C2 VARCHAR(26));
INSERT INTO T1 VALUES ('2008-01-01-12.12.20.123');
INSERT INTO T2 VALUES ('2009-01-01-12.12.20.123');
CREATE VIEW V1 (VC1) AS
SELECT C1 FROM T1 WHERE C1 = '2008-01-01-12.12.20.123'
UNION ALL
SELECT C2 FROM T2 WHERE C2 = '2009-01-01-12.12.20.123';
SELECT * FROM V1 WHERE V1.VC1 = '2009-01-01-12.12.20.123';
An abend may occur for the SQL statement above because DB2
did not set the timestamp precision correctly for the second
branch of the UNION ALL inside the view V1 when the first branch
is pruned.
3. ABEND04E RC00E70005 at location DSNXOOS2 M265
For Example,
WITH RES1 AS (
SELECT * FROM TABLE(TUDF_ALL(
INTEGER(430618) , '2013-01-31' , 'EUR')) AS X
)
SELECT * FROM RES1
WHERE RES1.BM = (SELECT MAX(RES1.BM) FROM RES1)
where TUDF_ALL is an SQL user defined table function.
An abend may occur for the SQL statement above because DB2 did
not handle the reference to the SQL user defined table
function inside the Common Table Expression correctly.
DB2 was updated to fix the above abends.
Additional Keywords: SQLPRUNE SQLVIEW SQLCCSID
SQLUNION SQLUNIONALL SQLTIMESTAMP
SQLDATE SQLIN
SQLCTE SQLINLINE SQLTABLEUDF
PARALLELISM SQLPARALLELISM DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI08758
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEXC PI08758
DSNXOOS2 PI08758
DSNXOPRE PI08758
DSNXOW2F PI08758
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI08758 DSNXOEXC DSNXOOS2 DSNXOPRE DSNXOW2F
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEXC
DSNXOOS2
DSNXOPRE
DSNXOW2F
LISTEND
UI16189 COVER LETTER END
UI16194 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12469 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2 for zOS *
* that have multi-volume tape archive log *
* data sets. *
****************************************************************
* PROBLEM DESCRIPTION: Repeated Mount and Keep messages can *
* be seen when DB2 is processing a log *
* read request for an LRSN range that *
* resides in a multi-volume tape archive *
* log data set, and the archive tape *
* delayed deallocation time is in *
* effect. SYSPLEXDS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When processing a log read request for an LRSN range that
exists in a multi-volume tape archive data set, the ENDRBA in
a log data set block may not be correct for the archive
log data set. When DB2 advances into the second volume of
the data set, this could result in a repeated sequence of
IEC501A MOUNT and IEC502E KEEP messages for the archive log
data set volumes when archive log tape delayed deallocation
time is active. To stop the repeated messages, turn off
archive log tape delayed deallocate time with the
DB2 -SET ARCHIVE TIME(0) command. It is not recommended to
use this option in data sharing mode as it can result in
extended archive volume allocation delays and possible archive
1 log volume deadlocks. You can disable this option across
DB2 restarts with the DSNZPARM DSN6LOGP DEALLCT=(0000)
setting.
DSNJR106 has been changed so that the ENDRBA for a multi-volume
tape archive log data set will be correct in the archive log
data set block.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12469
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJR106 PI12469
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12469 DSNJR106
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJR106
LISTEND
UI16194 COVER LETTER END
UI16242 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12504 -
****************************************************************
* USERS AFFECTED: DB2 users issuing REBIND PACKAGE with a *
* package name containing "TRIGGER"
*
****************************************************************
* PROBLEM DESCRIPTION: When REBIND PACKAGE is issued with a *
* package name containing the string *
* TRIGGER, DB2 may incorrectly process *
* the command as a REBIND TRIGGER PACKAGE *
* command *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a REBIND command is issued, DB2 differentiates REBIND
PACKAGE from REBIND TRIGGER PACKAGE based on the presence of
the TRIGGER keyword in the REBIND command. When the TRIGGER
keyword is present in the package specification after a
closing parentheses, DB2 will incorrectly determine that the
REBIND PACKAGE command is a REBIND TRIGGER PACKAGE command.
For example...
REBIND PACKAGE( -
COLL1.PACKAGE1.(VERSION1) -
,COLL1.TRIGGERB -
) EXPLAIN (YES) CURRENTDATA(NO) DBPROTOCOL(DRDA)
Since the package named TRIGGERB is after a package
1 specification that includes a closing parentheses, DB2 will
incorrectly determine that this is a REBIND TRIGGER PACKAGE
command. Since DBPROTOCOL(DRDA) is not a valid option for
REBIND TRIGGER PACKAGE, DB2 issues an error.
Depending on the REBIND PACKAGE command, the error message
could differ but will be a result of the command being
processed as a REBIND TRIGGER PACKAGE instead of a
REBIND PACKAGE. A DSNTRACE will show CSECT DSNECP47 is
called for REBIND TRIGGER PACKAGE instead of CSECT DSNECP45
for REBIND PACKAGE.
Additional keywords:
SQLTRIGGER
DB2 code has been changed to only recognize the TRIGGER keyword
when it is not a part of the package specification.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12504
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNECP19 PI12504
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12504 DSNECP19
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNECP19
LISTEND
UI16242 COVER LETTER END
UI16266 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11130 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the REBUILD INDEX utility on a *
* partition level. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C202B1 DSNB1PER OFFSET038E *
* and RC00C202B2 DSNB1PPP OFFSET2642 *
* during concurrent REBUILD INDEX *
* SHRLEVEL CHANGE utilities against *
* different partitions of the same index *
* running on different members of a data *
* sharing group. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A REBUILD INDEX SHRLEVEL CHANGE on one partition of an index
1 was running concurrently with a REBUILD INDEX SHRLEVEL CHANGE
of a different partition of the same index on a different
data sharing member. That utility abended with an ABEND04E
RC00C202B1 DSNB1PER +x'038E' and RC00C202B2 DSNB1PPP +x'2642'.
The same problem occurred when an SQL update was running. The
problem is caused because REBUILD INDEX SHRLEVEL CHANGE is
opening all partitions of the index during the LOG phase even
though the utility is operating at a partition level.
REBUILD INDEX SHRLEVEL CHANGE LOG phase code has been modified
to only open the index partition it is operating on.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11130
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCLAX PI11130
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11130 DSNUCLAX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCLAX
LISTEND
UI16266 COVER LETTER END
UI16315 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM95437 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of the following *
* DB2 supplied stored procedures: *
* - SYSPROC.ADMIN_UTL_MONITOR *
* - SYSPROC.ADMIN_UTL_EXECUTE *
****************************************************************
* PROBLEM DESCRIPTION: 1. Table spaces / partitions with a *
* real-time statistics DATASIZE of 0 *
* are not checked by *
* SYSPROC.ADMIN_UTL_MONITOR. *
* *
* 2. SYSPROC.ADMIN_UTL_EXECUTE fails *
* with DSNA601I and REASON CODE 2. *
* *
* 3. In DB2 11 for z/OS *
* SYSPROC.ADMIN_UTL_MONITOR returns *
* with DSNA653I DSNX7UTL CANNOT FIND *
* ZPARM STATCLUS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. The stored procedure SYSPROC.ADMIN_UTL_MONITOR might not
1 write alerts for table spaces or partitions with a DATASIZE
of zero in SYSIBM.SYSTABLESPACESTATS.
2. The stored procedure SYSPROC.ADMIN_UTL_EXECUTE might fail
with DSNA601I and REASON 2 if there is a utility running
with the same name stem as SYSPROC.ADMIN_UTL_EXECUTE is
using.
1. Table spaces / partitions with a real-time statistics
DATASIZE of zero are now being checked by
SYSPROC.ADMIN_UTL_MONITOR.
2. SYSPROC.ADMIN_UTL_EXECUTE utility name stem algorithm
was changed to reduce the likelihood of naming
conflicts.
3. Problem is fixed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM95437
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***************************************************************
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.
ACTION:
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
Run installation job DSNTIJRT to bind modified stored
procedures packages
***********************************************************
* This action is required for all V10 customers
***********************************************************
Run your customized copy of job DSNTIJRT with MODE(INSTALL)
1 to bind the stored procedure SYSPROC.ADMIN_UTL_MONITOR.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
ACTION:
The PTF for PM54759 fixes the stored procedure
SYSPROC.ADMIN_UTL_MONITOR so that the task it adds to the DB2
scheduler task list to execute the stored procedure
SYSPROC.ADMIN_UTL_EXECUTE can be executed by the DB2 scheduler
when DECIMAL=COMMA is enabled in DSNHDECP.
See the PTF cover letter for more information.
***************************************************************
Actions for DB2 10 for z/OS customers who are using
the DB2-supplied stored procedures
SYSPROC.ADMIN_UTL_MONITOR and
SYSPROC.ADMIN_UTL_EXECUTE in conjunction
with the DB2 administrative task scheduler
***************************************************************
After applying this PTF, you need to remove the task
'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list.
This action is detailed below:
(1) Ensure that the DB2 scheduler is up and running. If
scheduler is not running, execute the following console
command:
START DSNADMT
where DSNADMT is the name of the scheduler.
(2) Invoke the user-defined function ADMIN_TASK_LIST to
determine if the task 'DB2 AUTO PROCEDURE EXECUTE' is in the
DB2 scheduler task list, by issuing the following SQL
statement:
SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T
WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE';
A JOB example for this action is given below in the JOB
EXAMPLES section.
When no such task exists proceed to step (4). Otherwise,
proceed to step (3), below.
(3) Remove task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2
1 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
//SYSIN DD *
SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T
1 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'
S_RC = RXSUBCOM('DELETE','DSNREXX','DSNREXX')
1 EXIT RETCODE
/*
//CALL EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20,
// PARM='%CALLSP'
//SYSPROC DD DSN=*.REXX.SYSUT2,DISP=(OLD,DELETE)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
***************************************************************
END OF JOB EXAMPLES
***************************************************************
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@7EXE PM95437
DSN@7MON PM95437
DSNX7EXE PM95437
DSNX7MON PM95437
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM95437 DSN@7EXE DSN@7MON DSNX7EXE DSNX7MON
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX7EXE
DSNX7MON
MACROS
DSN@7EXE
DSN@7MON
LISTEND
UI16315 COVER LETTER END
UI16325 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM93459 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND702 RC14 may occur in module *
* DSN3EOTS during DB2 shutdown. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND702 RC14 may occur in module DSN3EOTS during DB2
shutdown if the POST is issued very late during DB2 shutdown.
Module DSN3EOTS has been updated to avoid the ABEND702.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM93459
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSN3EOTS PM93459
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM93459 DSN3EOTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3EOTS
LISTEND
UI16325 COVER LETTER END
UI16330 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06903 -
****************************************************************
* USERS AFFECTED: All CATMAINT UPDATE SCHEMA/OWNER/VCAT SWITCH *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: CATMAINT UPDATE SCHEMA/OWNER/VCAT *
* SWITCH incorrectly issues the DSNU767I *
* error message when it is executed *
* after a previous failed attempt. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
CATMAINT UPDATE SCHEMA/OWNER/VCAT SWITCH incorrectly issues
error message DSNU767I when it is executed after a previous
failed attempt.
The error message was a result of executing error checking
code unexpectedly due to a logic error.
DB2 code has been updated to avoid the aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06903
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEDLC PI06903
DSNUECM0 PI06903
DSNUECM4 PI06903
DSNUESCM PI06903
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06903 DSNGEDLC DSNUECM0 DSNUECM4 DSNUESCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEDLC
DSNUECM0
DSNUECM4
1 DSNUESCM
LISTEND
UI16330 COVER LETTER END
UI16335 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10829 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of EXPLAIN table DSN_SORTKEY_TABLE *
* that use mixed data *
****************************************************************
* PROBLEM DESCRIPTION: When issuing a SELECT on EXPLAIN table *
* DSN_SORTKEY_TABLE SQLCODE -331 with *
* reason 16 may be issued. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When issuing a SELECT on EXPLAIN table DSN_SORTKEY_TABLE SQLCODE
-331 with reason 16 may be issued.
The affected column includes TEXT from DSN_SORTKEY_TABLE. The
above problem was caused by improperly truncating mixed data.
Additional keywords:
SQLEXPLAIN SQLCODE331
DB2 code has been changed to properly truncate mixed data in the
TEXT column of DSN_SORTKEY_TABLE when the string is too long
so that the SQLCODE is no longer issued.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10829
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOD8 PI10829
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10829 DSNXOD8
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOD8
1 LISTEND
UI16335 COVER LETTER END
UI16342 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09003 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of an SQL *
* statement that contains a user-defined *
* function with a LOB parameter marker and *
* at least one other argument following it. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS DSNXOOS1 M310, DSNXGRDS *
* DSNXGDT2 M100 or other locations *
* could happen for an SQL statement *
* satisfying all of the following *
* conditions: *
* *
* 1. It contains a user-defined function. *
* 2. The user-defined function contains *
* more than one parameter. *
* 3. One of the parameters, except the *
* last one, is LOB related data type. *
* 4. The argument for the LOB parameter *
* is a parameter marker. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE FUNCTION UDF_1 (P1 CLOB(2M), P2 VARCHAR(10))
RETURNS VARCHAR(15)
RETURN 'TEST UDF:' || P2
;
SELECT UDF_1(?, 'ABC')
FROM SYSIBM.SYSDUMMY1
;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLUDF PARAMETERMARKER SQLPMARKER SQLPMK
SQLLOB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09003
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOFN3 PI09003
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09003 DSNXOFN3
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOFN3
LISTEND
UI16342 COVER LETTER END
UI16394 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM91723 -
****************************************************************
* USERS AFFECTED: All IRLM230(HIR2230) users data sharing *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability to diagnose hung Notify *
* requests in IRLM. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
Additional serviceability is needed to diagnose problems in DB2
and IMS environments where a Notify request gets suspended and
delayed. Its hard to figure out which member of the data
sharing group has not returned the response for the Notify.
Notify requester could be holding other locks or latches which
causes other transactions to time out. Without MVS dumps from
all data sharing members, its hard to figure out on which member
that Notify processing is stuck.
This APAR adds more serviceability code in IRLM to diagnose
problems related to Notify request processing. IRLM will include
initial part of the actual Notify message when CTRACE is written
for Notify request processing. For additional diagnostic
procedures please contact IBM support for help.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM91723
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL020 PM91723
DXRRL109 PM91723
DXRRL141 PM91723
DXRRL150 PM91723
DXRRL187 PM91723
DXRRL230 PM91723
DXRRL272 PM91723
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM91723 DXRRL020 DXRRL109 DXRRL141 DXRRL150 DXRRL187 DXRRL230
1 DXRRL272
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL020
DXRRL109
DXRRL141
DXRRL150
DXRRL187
DXRRL230
DXRRL272
LISTEND
UI16394 COVER LETTER END
UI16395 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM91843 -
****************************************************************
* USERS AFFECTED: All IRLM2.3 (HIR2230) users. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM storage sub-pools can grow large *
* and if they are not compressed sooner, *
* it causes storage spike that could *
* impact an LPAR and could potentially *
* cause group-wide outage. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM storage management needs some enhancements to handle a
spike in workload activities more efficeiently.
1. This APAR is an enhancement of IRLM storage management.
IRLM will detect high storage usage in IRLM storage sub-pools
and trigger storage compression every deadlock interval.
IRLM sub-pools that gets ECSA storage will be subjected to an
additional compression cycle if there were more free segments
to be compressed.
2. When additional diagnostics are turned on, IRLM may issue
abendu2025 in DXRRL750 for delays in getting mainlatch over 5
minutes. These diagnostic flags are off by default and can be
turned on via an IRLM Modify commands only.
Please contact IBM service for details on how to turn on
additional diagnostics to capture dumps for analysis of
delays/hang associated with issuance of DXR167E messages on
the console.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM91843
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL020 PM91843
1 DXRRL187 PM91843
DXRRL24B PM91843
DXRRL272 PM91843
DXRRL401 PM91843
DXRRL410 PM91843
DXRRL750 PM91843
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM91843 DXRRL020 DXRRL187 DXRRL24B DXRRL272 DXRRL401 DXRRL410
DXRRL750
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL020
DXRRL187
DXRRL24B
DXRRL272
DXRRL401
DXRRL410
DXRRL750
LISTEND
UI16395 COVER LETTER END
UI16433 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10749 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users who use *
* non-boolean IS NULL predicate for a NOT NULL *
* column, or cursor with rowset positioning in *
* a native SQL procedure or compiled SQL *
* scalar function *
****************************************************************
* PROBLEM DESCRIPTION: There are two problems addressed: *
* (1) ABEND04E RC00E70005 in DSNXOB2 M100 *
* may occur for an SQL statement that *
* contains a non-boolean IS NULL *
* predicate for a NOT NULL column. *
* (2) ABEND0C4 RC00000004 in DSNXEBR 0AA4 *
* may occur when a cursor with rowset *
* positioning is used in a native SQL *
* procedure or compiled SQL scalar *
* function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below to illustrate problem (1):
CREATE TABLE MYTABLE(C1 INT NOT NULL, C2 INT);
SELECT 1 FROM MYTABLE
WHERE C1 IS NULL
OR (C2 = 1 AND 1 = 1);
1
The pruning of the IS NULL predicate is not processed correctly,
which results in the abend.
An example is shown below to illustrate problem (2):
CREATE TABLE MYTABLE(C1 CHAR(2));
CREATE PROCEDURE MYPROC
BEGIN
DECLARE X CHAR(1);
DECLARE MYCURSOR CURSOR WITH ROWSET POSITIONING FOR
SELECT IBMREQD FROM SYSIBM.SYSDUMMY1;
OPEN MYCURSOR;
FETCH NEXT FROM MYCURSOR INTO X;
CLOSE MYCURSOR;
INSERT INTO MYTABLE VALUES(X);
END!
SOLUTION:
DB2 has been modified to correctly process the aforementioned
SQL statements.
Additional Keywords: SQLSP SQLNATIVESQLPL SQLNULL SQLNOTNULL
SQLOR SQLISNULL SQLPRUNING OFFSET0AA4
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10749
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM99602:
See PM99602 APAR/PTF text for additional information about
why a REBIND is necessary.
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
1 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.
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOB2 PI10749
DSNXOYFR PI10749
DSNXOYP0 PI10749
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10749 DSNXOB2 DSNXOYFR DSNXOYP0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOB2
DSNXOYFR
DSNXOYP0
LISTEND
UI16433 COVER LETTER END
UI16449 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10509 -
****************************************************************
* USERS AFFECTED: All users of DSNTWLMB and *
* SYSPROC.DSN_WLM_APPLENV in DB2 10 for z/OS *
* and DB2 11 for z/OS are affected by this *
* change. *
****************************************************************
* PROBLEM DESCRIPTION: One or both of the following problems *
* occurs: *
* (1) Execution of DSNTWLMB with *
* PARM='ACTION(WLMINFO)' terminates *
* with abend 0C4-4 when the user ID *
* of the job or task does not have *
1 * READ access or higher to resource *
* profile MVSADMIN.WLM.POLICY in *
* CLASS(FACILITY) *
* (2) Calls to DSN_WLM_APPLENV with *
* parameter 1 (action) set to *
* 'WLMINFO' fail with SQLCODE -430 *
* due to abend 0C4-4 in external *
* module DSNTWLMS when the *
* authorization ID of the process *
* does not have READ access or higher *
* to resource profile *
* MVSADMIN.WLM.POLICY in *
* CLASS(FACILITY). *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
The DSNTWLMB program provides a batch interface for installing,
activating, and obtaining basic information about WLM
environments. It is used by DB2 installation job DSNTIJRW to
create the core DB2 WLM environments.
Likewise, the DSN_WLM_APPLENV stored procedure provides an SQL
interface for defining, installing, activating, and obtaining
basic information about WLM environments.
When z/OS resource profile MVSADMIN.WLM.POLICY is defined in
resource class FACILITY, the user ID executing DSNTWLMB or the
authorization ID calling DSN_WLM_APPLENV must have at least READ
access on the profile in order to obtain information about a WLM
environment; it must have at least UPDATE access in order to
install or activate a WLM environment. Otherwise, the request
fails with the following diagnostic messages:
DSNT024I DSNTWLMx action FAILED
DSNT037I DSNTWLMx action WLM SERVICE DEFINITION REQUEST
FAILED, MACRO = macro-name, RETURN CODE =
return-code, REASON CODE = reason-code
Currently, however, DSNTWLMB abends as noted in the Problem
Description if run with 'PARM='ACTION(WLMINFO)' when the user ID
lacks READ access to MVSADMIN.WLM.POLICY. Likewise,
DSN_WLM_APPLENV fails as noted in the Problem Description if
called with parameter 1 (action) set to 'WLMINFO' when the
authorization ID of the process lacks READ access to
MVSADMIN.WLM.POLICY.
In response, this APAR fixes a code bug in DSNTWLMB so that it
will no longer abend if run with 'PARM='ACTION(WLMINFO)' when
the user ID lacks READ access to resource profile
MVSADMIN.WLM.POLICY in CLASS(FACILITY). Instead, it will
output messages DSNT024I and DSNT037I and then terminate with
return code 8.
Likewise, this APAR fixes a code bug in DSNTWLMS so that it
will no longer abend if DSN_WLM_APPLENV is called with the
action parameter set to 'WLMINFO' and the authorization ID of
the process lacks READ access MVSADMIN.WLM.POLICY. Instead,
1 the call will end with SQLCODE 0, parameter 4 (return code) will
contain 8, and parameter 5 (message) will contain the DSNT024I
and DSNT037I messages.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10509
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTWLMB PI10509
DSNTWLMS PI10509
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10509 DSNTWLMB DSNTWLMS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTWLMB
DSNTWLMS
LISTEND
UI16449 COVER LETTER END
UI16451 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM81679 -
****************************************************************
* USERS AFFECTED: All users of the SYSPROC.WLM_REFRESH stored *
* procedure in DB2 10 for z/OS and DB2 11 for *
* z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: WLM_REFRESH has two input parameters, *
* one for the name of the WLM environment *
* to be refreshed and the other for the *
* subsystem ID (SSID). It uses these *
* parameters to generate the name of an *
* authorization resource profile that *
* determines whether to honor the refresh *
* request. *
* *
* In a data sharing environment, when *
* WLM_REFRESH is called with its SSID *
* parameter set to null or blank, it is *
* supposed to use the group attach name, *
* if one is defined, to build the *
* resource profile name. Currently, *
* however, it always uses the DB2 *
* subsystem name. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
WLM_REFRESH is a DB2-supplied stored procedure that can be
called by an authorized user to request refresh of a specified
1 WLM environment on a remote or local system.
In order to execute the CALL statement successfully, the SQL
authorization ID of the process must have READ access or higher
to the z/OS Security Server System Authorization Facility (SAF)
resource profile ssid.WLM_REFRESH.wlm-environment-name in
resource class DSNR. Both wlm-environment-name and ssid can be
passed as input parameters to WLM_REFRESH:
* wlm-environment-name specifies the name of the WLM
environment that you want to refresh.
* ssid specifies the subsystem ID of the DB2 subsystem with
which the WLM environment is associated. If this parameter
is NULL or blank, WLM_REFRESH uses one of the following
values for this parameter:
- In a non-data sharing environment, WLM_REFRESH uses the
ID of the DB2 subsystem on which it runs.
- In a data sharing environment, WLM_REFRESH uses the group
attach name, if defined, of the data sharing group on which
it runs. If a group attach name is not defined then
WLM_REFRESH uses the ID of the DB2 subsystem on which
it runs.
Currently, in DB2 10 and 11, when the ssid parameter is NULL or
blank, WLM_REFRESH always uses the ID of the DB2 subsystem on
which it runs to construct the name of the SAF resource profile,
even if the environment is a data sharing environment that has a
group attach name defined.
This APAR modifies WLM_REFRESH so that, when called with a NULL
or blank SSID parameter setting on a DB2 data sharing group that
has a group attach name defined, it uses the group attach name
rather than the ID of the DB2 subsystem on which it's running
to construct the name of the SAF resource profile,
ssid.WLM_REFRESH.wlm-environment-name.
In order to discover the group attach name, DSNTWR, the external
module for WLM_REFRESH, now runs a subtask called DSNTWRE that
returns a copy of the DB2 Environmental Information Block (EIB).
DSNTWR then obtains from the EIB the data sharing group name
and group attach name. 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 is running.
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.
Introducing DSNTWRE: Program to obtain the DB2 EIB
--------------------------------------------------
Like DSNTWR, DSNTWRE is provided in both object and source
format. DSNTWRE is attached by DSNTWR as a subtask but it could
1 also be linked and run inline by any program that wants to
obtain the EIB. DSNTWRE uses the DB2 RRSAF IDENTIFY function
to locate the EIB.
DSNTWRE expects 4 parameters:
1. The address of a 4-byte character field that contains:
- on input : The DB2 subsystem name
- on output: (unchanged)
2. The address of a fullword field that contains:
- on input : (unused)
- on output: The return code of this program.
3. The address of a character field, whose size is equivalent
to the size of the DSNDEIB macro. This field contains:
- on input : (unused)
- on output: Unchanged if parameter 2 is not 0, otherwise the
EIB (as defined by DSNDEIB macro)
4. The address of a 120-byte varying-length character field that
contains:
- on input : (unused)
- on output: Unchanged if parameter 2 is 0, otherwise a DB2
error message.
If DSNTWRE runs successfully, it returns 0 at the address
specified by parameter 2 and the EIB content at the address
specified by parameter 3.
If DSNTWRE runs unsuccessfully, it leaves parameter 3 unchanged
and returns one of the following diagnostic messages via
parameter 4:
* DSNA614I DSNTWRE UNABLE TO OBTAIN WORK AREA STORAGE,
SIZE = n BYTES
In this case, it returns 8 at the address specified by
parameter 2.
* DSNT012I DSNTWRE rrsaf-function REQUEST FAILED. DSNRLI RETURN
CODE = dsnrli-return, RRSAF RETURN CODE =
rrsaf-return, RRSAF REASON CODE = rrsaf-reason
In this case, it returns the RRSAF return code at the address
specified by parameter 2.
Changes to DSNTWR: External module for WLM_REFRESH
--------------------------------------------------
As noted earlier, DSNTWR runs DSNTWRE as a subtask. Before
attempting the attach, DSNTWR uses BLDL to ensure that DSNTWRE
is available. If it is not, DSNTWR ends with return code -991
and this (new) message:
DSNT548I DSNTWR LOAD MODULE NAME DSNTWRE NOT FOUND, BLDL
R15=return-code, R0=reason-code
If DSNTWRE is available, DSNTWR will attach it as a subtask,
passing in the addresses of the subsystem ID and areas for a
1 return code, the EIB, and an output message.
If DSNTWRE sets a non-zero return code, DSNTWR ends with the
return code and message passed back from DSNTWRE.
If DSNTWRE sets a zero return code then, if the data sharing
group name and the group attach name field in the returned EIB
are both non-blank, DSNTWR will use the group attach name to
build the SAF resource profile. Otherwise, DSNTWR will use
the ID of the DB2 subsystem on which WLM_REFRESH runs.
Changes to sample job DSNTEJ6W
------------------------------
Sample job DSNTEJ6W prepares, binds, and executes a sample
caller of WLM_REFRESH. It also contains optional (commented-
out) job steps for preparing and binding DSNTWR from its
source module, prefix.SDSNSAMP(DSNTWRS).
A new, optional (commented-out) job step, PH06WS00, is added
to DSNTEJ6W that can be used to prepare DSNTWRE from its
source module, prefix.SDSNSAMP(DSNTWRE).
In addition, minor changes are made to PH06WS01, an optional
job step that can be used to prepare module DSNTWR from its
source module, prefix.SDSNSAMP(DSNTWRS). In particular, the
link edit parameter list is changed from
PARM.LKED='LIST,LET,XREF,REUS,AMODE=31,RMODE=ANY,RENT'
to:
PARM.LKED='LIST,XREF,AMODE=31,RMODE=ANY,RENT'
Finally, minor changes are also made to PH06WS03, the job step
that prepares DSN8ED6, a sample caller of WLM_REFRESH. In
particular, the link edit parameter list is changed from
PARM.LKED='AMODE=31,RMODE=ANY,MAP,RENT,REUS'
to:
PARM.LKED='AMODE=31,RMODE=ANY,MAP,RENT'
New DB2 message
---------------
DSNT548I program-name LOAD MODULE NAME module-name NOT FOUND,
BLDL R15=return-code, R0=reason-code
Explanation: Prior to an attempted load or attach, program
program-name could not be located during MVS BLDL processing.
The BLDL issued a return code of return-code and a reason code
of reason-code.
program-name
The name of the program that issued this message
module-name
The name of the module that could not be found.
return-code
The return code issued by the BLDL request.
reason-code
The BLDL reason code.
1 System action: Module program-name terminates.
System programmer response: Verify that the named load module
exists, and that DB2 can access it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM81679
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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
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
1 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.
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
1 ***********************************************************
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:
* 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
1 ***********************************************************
* 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:
(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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@WR PM81679
DSNTEJ6W PM81679
DSNTINS3 PM81679
DSNTWR PM81679
DSNTWRE PM81679
1 HDBAA10J PM81679
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM81679 DSN@WR DSNTEJ6W DSNTINS3 DSNTWR DSNTWRE HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTWR
DSNTWRE
MACROS
DSN@WR
DSNTEJ6W
DSNTINS3
LISTEND
UI16451 COVER LETTER END
UI16477 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09632 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of -ACCESS *
* MODE(STATS) command. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E30086 DSNTDMI or *
* RC00C90101 DSNGEDFR ERQUAL50FF when *
* running -ACCESS DB(*) SP(*) MODE(STATS) *
* command concurrently with a DROP *
* database. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A timing window may exist after -ACCESS MODE(STATS) command
processor accessing a DBD and a DROP database occurs. As the
processor does not acquire any DBD lock, the abend may occur
when freeing the non-existent DBD.
Since the RTS externalization routine which flushes the
in-memory stats does not require DBD access other than itself,
the ACCESS MODE(STATS) command processor code is changed to free
the DBD as soon as possible and ignore DBD not found error.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09632
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDMI PI09632
DSNTDMST PI09632
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09632 DSNTDMI DSNTDMST
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDMI
DSNTDMST
LISTEND
UI16477 COVER LETTER END
UI16498 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12061 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: After ALTERing a table space's DSSIZE *
* from 4G to a higher value, the 4G limit *
* may still be enforced, resulting in *
* LOAD failing with RC00C90099 or INSERT *
* failing with RC00C9009C. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After ALTERing the DSSIZE for a table space from 4G to a higher
value, and materializing the ALTER by doing a REORG, there may
be a residual 4G limit value stored in a page set control block
which will block LOAD or INSERT from using the additional space.
The code which handles updating attributes in the page set
control block has been modified to ensure that the 4G limit
value is zeroed out when the DSSIZE is no longer 4G.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12061
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1OPS PI12061
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12061 DSNB1OPS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1OPS
LISTEND
UI16498 COVER LETTER END
UI16501 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10162 -
****************************************************************
1 * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the LOAD utility. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability APAR *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
Serviceability APAR for the LOAD utility.
Serviceablity APAR for the LOAD utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10162
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUDIAG PI10162
DSNUFCMD PI10162
DSNUGDDD PI10162
DSNUGPRT PI10162
DSNURILD PI10162
DSNURPIB PI10162
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10162 DSNUDIAG DSNUFCMD DSNUGDDD DSNUGPRT DSNURILD DSNURPIB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUDIAG
DSNUFCMD
DSNUGDDD
DSNUGPRT
DSNURILD
DSNURPIB
LISTEND
UI16501 COVER LETTER END
UI16507 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09564 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of CREATE FUNCTION (SQL table). *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE590 is incorrectly issued for a *
* CREATE FUNCTION (SQL table) statement *
* when the same name appears in both the *
* input parameter list and the RETURNS *
* TABLE column name. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQLCODE590 is incorrectly issued for a CREATE FUNCTION (SQL
1 table) statement when the same name appears in both the input
parameter list and the RETURNS TABLE column name.
DB2 should process the unique name checking separately for the
CREATE FUNCTION (SQL table) input parameter list and the
RETURNS TABLE column name.
Following is an example of such failing scenario:
CREATE TABLE TB1 (
FC1 CHAR(8) NOT NULL,
FC2 CHAR(3) NOT NULL,
FC3 CHAR(3) NOT NULL )
CCSID UNICODE ;
CREATE FUNCTION MYFUN1 (
FC1 CHAR(8),
FC2 CHAR(3))
RETURNS TABLE (
FC2 CHAR(3),
FC3 CHAR(3))
LANGUAGE SQL READS SQL DATA NO EXTERNAL ACTION DETERMINISTIC
PARAMETER CCSID UNICODE
RETURN
SELECT MYFUN1.FC2, FC3
FROM TB1
WHERE FC2 = '001'
AND FC1 = MYFUN1.FC1
;
DB2 is modified to process the unique name checking separately
for the CREATE FUNCTION (SQL table) input parameter list and
the RETURNS TABLE column name.
Additional Keywords: SQLCODE590 SQLUDF SQLTUDF SQLTABLEUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09564
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISB2 PI09564
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09564 DSNXISB2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISB2
LISTEND
UI16507 COVER LETTER END
UI16521 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI06381 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and *
* DB2 11 for z/OS users of REORG INDEX. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40322 RC00C90101 at *
* DSNKINSL ERQUAL5033 during a RESTART *
* CURRENT of a REORG INDEX in the UNLOAD *
* phase. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REORG INDEX on a non-unique index was cancelled by the user
in the UNLOAD phase, and then restarted from current. This
REORG INDEX abended with ABEND04E RC00E40322 RC00C90101 at
DSNKINSL:5033 because a duplicate key was detected during the
BUILD phase.
During RESTART in the UNLOAD phase, REORG INDEX did not
reposition correctly on the index and unloaded a duplicate key,
causing the utility to fail during the BUILD phase.
REORG code has been modified to correct the aforementioned
problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06381
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFBI PI06381
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06381 DSNURFBI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFBI
LISTEND
UI16521 COVER LETTER END
UI16524 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11739 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS, DB2 11 for z/OS users *
* of REBUILD INDEX. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 RC38 at DSNB1REL OFFSET02AC *
* during a CHECK INDEX after a REBUILD *
* INDEX on a varying length key index. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
1 ****************************************************************
A REBUILD INDEX ran on an index with varying length key after a
DSN1COPY copied the data to the table space. A subsequent CHECK
INDEX abended with ABEND0C4 RC38 at DSNB1REL + '02AC'x. A query
on the table also hit the same abend.
This problem occurred because REBUILD INDEX inserted some
keys with incorrect key lengths, which came from some dirty data
from the DSN1COPY, and caused the storage overlay.
Additional Keywords: RC00E40311 RC00E30104 RC00E40347
A sanity check has been added for REBUILD INDEX. If the index
key length is greater than the maximum value, an ABEND04E
RC00E4D5D2 will be issued.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11739
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURBXC PI11739
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11739 DSNURBXC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURBXC
LISTEND
UI16524 COVER LETTER END
UI16534 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10112 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Storage leak in the BB1RMID pool. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For castout requests initiated due to an out-of-storage
condition in the Group Buffer Pool, there is a timing window
in which the castout may end up being skipped because the
page set is being closed. When this happens, the Castout
Request Block (CRB) does not get freed.
The castout scheduling code has been modified to free the CRB
storage when the castout request is being skipped.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10112
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PCO PI10112
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10112 DSNB1PCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PCO
LISTEND
UI16534 COVER LETTER END
UI16536 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12511 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: DSNJU004 Print Log Map Utility prints *
* -ARCHIVE LOG command history prints *
* the highest number of members seen in *
* a data sharing group including the *
* number of DB2 members successfully *
* destroyed by the DSNJU003 utility. It *
* should print the current number of *
* members in the group. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSNJU004 -ARCHIVE LOG command history displays the highest
number of members seen in the data sharing group, which will
include members destroyed by the DSNJU003 utility that have not
had their member IDs reused.
DSNJU004 -ARCHIVE LOG command history has been modified to
print the number of members not destroyed by the DSNJU003
utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12511
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJU004 PI12511
DSNJU104 PI12511
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12511 DSNJU004 DSNJU104
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNJU004
DSNJU104
LISTEND
UI16536 COVER LETTER END
UI16538 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13097 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of XML *
* and LOBs. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E rc00D31010 occurs at *
* DSNLILLM DSNLCMSL ABNDID0008 in the *
* distributed environment when a remote *
* application references a migrated *
* package with a LOB locator containing *
* XML values. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E rc00D31010 occurs at DSNLILLM DSNLCMSL ABNDID0008 in
the distributed environment when a remote application uses a
pre-v10 bound package with a LOB locator that contains XML
values.
For a down level request, DB2 allows an XML column to be
selected into a LOB locator. Because DB2 does not materialize
the XML column at fetch time, this results in a length-checking
inconsistency during subsequent host variable bind-out process,
resulting in the abend mentioned above.
The following example helps to illustrate the problem.
1. Create a Table with one XML column.
Insert into the Table.
! Connect application to a database server
EXEC SQL CONNECT TO STLEC2;
CREATE TABLE T1 (C1 XML);
INSERT INTO T1 VALUES (XMLPARSE (DOCUMENT
'<A><B><C>ABC</C></B></A>'));
2. From an application, define two host variables, one for
a LOB column, one for a LOB locator.
DCL HVBLOBL SQL TYPE IS BLOB_LOCATOR;
DCL HVBLOB1 SQL TYPE IS BLOB(1M);
3. From the application to be run in a distributed environment,
execute the following SELECT and VALUES INTO statements
1 and bind the package.
EXEC SQL CONNECT TO STLEC2;
EXEC SQL SELECT C1 INTO :HVBLOBL FROM T1;
EXEC SQL VALUES(:HVBLOBL) INTO :HVBLOB1;
Note: All of the above steps are to be completed in DB2 v9.
4. Now, migrate DB2 v9 to v10 or v11 and execute the
application using the v9 bound package.
DB2 does not materialize the XML column when fetching it into
the host variable HVBLOBL. This causes the length-checking
inconsistency error when later, the HVBLOBL is bound out to
HVBLOB1. The aforementioned abend can occur.
The code in DB2 is modified to materialize the XML data when it
is fetched. This will avoid the abend.
Additional Keywords: SQLXML SQLLOB SQLHOSTVAR SQLMIGRATION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13097
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNAOUT PI13097
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13097 DSNNAOUT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNAOUT
LISTEND
UI16538 COVER LETTER END
UI16545 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM97594 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE DISCARD FROM TABLE *
* with a very large IN LIST predicate. *
****************************************************************
* PROBLEM DESCRIPTION: Longer than expected elapsed times when *
* a REORG TABLESPACE DISCARD FROM TABLE *
* runs with a WHEN clause with an IN list *
* containing a very large number of *
* values. *
1 ****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
REORG utility was run on a table with a WHEN clause which had an
IN predicate containing a list specifying more than 500000
values. The REORG ran for longer than expected and in some
cases timed out or received an ABENDS322. This was due to the
way the utility parser obtains and maintains storage for IN list
predicates, which is relatively inefficient when the number of
values is very large.
This problem can also occur for UNLOAD WHEN with a large IN
list.
Code in the DB2 utility parser has been modified to improve its
storage handling when processing IN predicate values for REORG
WHEN clauses.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM97594
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGPRS PM97594
DSNUGPRV PM97594
DSNUGPRW PM97594
DSNUGPRZ PM97594
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM97594 DSNUGPRS DSNUGPRV DSNUGPRW DSNUGPRZ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGPRS
DSNUGPRV
DSNUGPRW
DSNUGPRZ
LISTEND
UI16545 COVER LETTER END
UI16602 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09808 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS Users of IFCID 199, *
* specifically QW0199GP get pages *
****************************************************************
* PROBLEM DESCRIPTION: QW0199GP value does not represent the *
* correct interval for dataset statistics *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the retrieval of the dataset statistics for QW0199GP,
DB2 was not recording the time interval when DSSTIME fired
1 while the READS trace was being cut.
DB2 has been modified to record the additional get page
values.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09808
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1TSD PI09808
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09808 DSNB1TSD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1TSD
LISTEND
UI16602 COVER LETTER END
UI16606 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM98530 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of SYSPLEX *
* PARALLELISM. *
****************************************************************
* PROBLEM DESCRIPTION: High ECSA storage usage in SYSPLEX *
* PARALLELISM case due to storage leak *
* when parallel threads are cancelled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
High ECSA storage usage in case where parallel threads are
cancelled. The problem is when the parallel threads are
cancelled, in certain cases ECSA storage is not freed during
cancelling process. So ECSA storage will be accumulated without
being freed after a long duration of time.
The problem is not query specific, so we will not have a
sample query here. Any query running in SYSPLEX parallelism
could potentially hit this problem.
DB2 has been fixed to free the ECSA storage during
CANCEL process for SYSPLEX parallelism query. The
problem no longer occurs after the fix.
Additional keywords: PARALLELISM SYSPLEX
DB2PARALL/K SQLSYSPLEXP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM98530
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTTRUN PM98530
DSNXPSEN PM98530
DSNXRTSC PM98530
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM98530 DSNTTRUN DSNXPSEN DSNXRTSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTTRUN
DSNXPSEN
DSNXRTSC
LISTEND
UI16606 COVER LETTER END
UI16612 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13248 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically where: *
* - DB2 for z/OS data sharing group is *
* accessed as a server *
* - Connect requests to the group are using *
* SNA from another DB2 for z/OS subsystem *
* or data sharing group *
* - RACF passtickets are included with the *
* connection security credentials *
* - Subsystem parameter DDF THREADS *
* (DSN6FAC CMTSTAT) is set to INACTIVE *
****************************************************************
* PROBLEM DESCRIPTION: Passticket based authentication *
* intermittently fails with message *
* DSNL030I DSNLAGNX REASON=00F30085. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the process of accepting a connection at a member of
a data sharing group, DDF issues a z/OS SAF RACHECK request
to authenticate the userid and password presented to DB2. If
the requestor is another DB2 for z/OS subsystem or member of
a data sharing group, the password in the connection request
could be a RACF passticket. To ensure that a RACF passticket
can be validated correctly, DDF will include an application
name value in the RACHECK request.
If the new connection request is serviced by a newly created
DataBase Access Thread (DBAT), the RACHECK request is
successful and the connection is accepted.
However, if the new connection request happens to be serviced
by a pooled DBAT (thread type name of DISCONN), the RACHECK
1 request fails because an incorrect application name value is
provided on the RACHECK request. Message DSNL030I with CSECT
DSNLAGNX and REASON=00F30085 will be issued to reflect the
failure and the rejection of the connection.
DB2 has been changed to consistently provide an appropriate
application name value in the RACHECK request regardless of the
type of DBAT used to service the new connection request.
Note: For a DB2 data sharing group, the value used for the
application name is its SNA Generic LU name, if configured.
The generic LU name is specified via the GENERIC keyword of
the DDF BSDS statement processed by the DB2 Change Log
Inventory utility (DSNJU003).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13248
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLAGNX PI13248
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13248 DSNLAGNX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLAGNX
LISTEND
UI16612 COVER LETTER END
UI16614 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06809 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users that take locks in the *
* index access path against segmented table *
* spaces. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNITCUS ERQUAL5049 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An abend ERQUAL5049 occurred in DSNITCUS during cursor block
cleanup activity due to a mismatch in the number of locks in the
statistics counters. During index access on a segmented table
space, a lock request triggered lock escalation. Then the key
obtained was subsequently disqualified and another iteration of
the key search loop found the next qualifying key value. A lock
request for the new value was again issued to the lock manager
even though the table space had already lock escalated to a
gross level lock. This then led to mismatches in the lock
statistics counters.
1 DB2 code has been corrected in the lock escalation path to set
an index gross lock held flag. The logic in the index manager
code will now detect that there has been lock escalation and
will then avoid taking another lock on the qualifying row for
a segmented table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06809
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKFLST PI06809
DSNKFPRV PI06809
DSNKFTCH PI06809
DSNKNXT2 PI06809
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06809 DSNKFLST DSNKFPRV DSNKFTCH DSNKNXT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKFLST
DSNKFPRV
DSNKFTCH
DSNKNXT2
LISTEND
UI16614 COVER LETTER END
UI16667 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12687 -
****************************************************************
* USERS AFFECTED: All DB2 11, DB2 10 and DB2 9 for z/OS *
* users with defer defined data sets. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E with RC00C90101 *
* at DSNILKDR:1001 when *
* roll back a data set defer *
* define process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a data set defer define process, before the CLR log
record is written the process can still be rolled back.
In this case, the roll back happened before a drain lock was
taken, DB2 tried to free a drain lock without checking if
it was held caused this 04E abend at DSNILKDR:1001.
Fixes made in DB2's data set defer define process to make sure
it holds the drain lock before issuing the free drain lock call.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12687
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICINV PI12687
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12687 DSNICINV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICINV
LISTEND
UI16667 COVER LETTER END
UI16670 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI08508 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Repeated START/STOP of DDF causes a *
* slow storage leak and may cause an *
* ECSA storage shortage. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Starting and stopping DDF causes a slow leak of DB2 control
blocks and can eventually lead to an ECSA storage shortage.
DB2 has been modified to reuse the control blocks used during
DDF startup and shutdown.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI08508
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3SSCN PI08508
DSN3SSES PI08508
DSN3SSI1 PI08508
DSN3SSRQ PI08508
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI08508 DSN3SSCN DSN3SSES DSN3SSI1 DSN3SSRQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3SSCN
DSN3SSES
DSN3SSI1
DSN3SSRQ
1
LISTEND
UI16670 COVER LETTER END
UI16672 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09978 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 version 11 writes the begin UR *
* log record for a global transaction *
* with an invalid offset when the *
* BSDS has not been converted by the *
* DSNJCNVT utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 Version 11 changed the size of the log record header (LRH)
when the system has been converted by the DSNJCNVT utility. The
begin UR log record for a global transaction specifies the
offset to the XID for the larger log record when written by a
Version 11 subsystem in all modes.
This is a problem in CM mode when a DB2 Version 10 member is
attempting to read a log written by a Version 11 member or
vice-versa when a DB2 Version 11 member is attempting to read
a Version 10 log record.
DB2 Version 10 has been modified to tolerate and fix up a
begin UR log record for global transactions written by a
Version 11 member.
DB2 Version 11 has been modified to tolerate and fix up a
begin UR log record for global transactions written by a
Version 10 member.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09978
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJR103 PI09978
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09978 DSNJR103
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJR103
LISTEND
UI16672 COVER LETTER END
1
UI16688 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12045 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000004 or RC0000003B in *
* DSNNOGET +099C or DSNNOGET +448A may *
* occur when using XPath to query an XML *
* document who's *
* DB2_GENERATED_DOCID_FOR_XML is greater *
* than 2147483647 and the query includes *
* SELECT DISTINCT, GROUP BY or ORDER BY *
* clause. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For example:
The CREATE TABLE statement below will create a table with
XML column X1. Assuming there are rows with the
DB2_GENERATED_DOCID_FOR_XML greater then 2147483647.
CREATE TABLE T1
(
I1 INTEGER
,X1 XML
);
The following query has SELECT DISTINCT clause and the XPath
accesses some XML document who's DB2_GENERATED_DOCID_FOR_XML
is greater than 2147483647. In such a case, the ABEND0C4
RC00000004 or RC0000003B in DSNNOGET +099C or DSNNOGET +448A
may occur.
SELECT DISTINCT XMLCAST(XMLQUERY('$x/a[b = 22]/c'
PASSING T1.X1 AS "x") AS VARCHAR(10))
FROM T1
WHERE XMLEXISTS('$x/a[b = 22]/c'
PASSING T1.X1 AS "x");
DB2 is modified so the ABEND0C4 RC00000004 or RC0000003B in
DSNNOGET +099C or DSNNOGET +448A will not occur.
Additional Keyword: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12045
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOAPU PI12045
DSNNOCCN PI12045
DSNNOGET PI12045
DSNNOINS PI12045
DSNNOXMV PI12045
1 DSNNOXVC PI12045
DSNNQIV PI12045
DSNNQMD PI12045
DSNXMLSM PI12045
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12045 DSNNOAPU DSNNOCCN DSNNOGET DSNNOINS DSNNOXMV DSNNOXVC
DSNNQIV DSNNQMD DSNXMLSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOAPU
DSNNOCCN
DSNNOGET
DSNNOINS
DSNNOXMV
DSNNOXVC
DSNNQIV
DSNNQMD
DSNXMLSM
LISTEND
UI16688 COVER LETTER END
UI16695 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06614 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS non-data sharing users *
****************************************************************
* PROBLEM DESCRIPTION: DB2 failed to open a data set. Resource *
* unavailable with reason RC00C2010D is *
* returned to user and MSGDSNB232I is *
* issued to the console. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
DB2 failed to open a data set and issued MSGDSNB232I -
'UNEXPECTED DATA SET LEVEL ID ENCOUNTERED - LEVEL ID =lvlid
EXPECTED LEVEL ID=xlvlid DSN=dsn'. The message was issued in
error. The data set was not down level.
This can happen only when all of the following are true:
- the environment is non-Data Sharing.
- prior to first migration to V10, the system RBA was
numerically higher than the system timestamp.
- for a given object, the syslgrnx record with the highest
startlrsn has a startrba which falls numerically between the
system timestamp value at the time the record was created and
the system timestamp value at the time the open is attempted.
Code was changed in utility general services to prevent false
downlevel detection errors when a data set is opened.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06614
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUAHR2 PI06614
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06614 DSNUAHR2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUAHR2
LISTEND
UI16695 COVER LETTER END
UI16700 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14134 -
****************************************************************
* USERS AFFECTED: All users of DSNTRVFY, the validation tool *
* for DB2-supplied stored procedures and *
* user-defined functions (UDFs), in DB2 10 *
* for z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: When DB2 has no default WLM environment *
* DSNTIJRV, job step DSNTRVFY (program *
* DSNTRVFY), terminates with return code *
* 8 and these messages: *
* DSNT031I DSNTRVFY VALIDATION FOR *
* schema.name FAILED. *
* DSNT038I DSNTRVFY - THE WLM *
* ENVIRONMENT IS NOT *
* AVAILABLE. *
* where schema.name is one or more of *
* the following routines: *
* SYSTOOLS.REGSP *
* SYSTOOLS.REG_MATCHES *
* SYSTOOLS.REG_MATCHES_NOFLAGS *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
Job DSNTIJRV executes program DSNTRVFY which can be used to
validate installation and configuration of DB2-supplied stored
procedures and UDFs. Validation includes checking the WLM
environment for running each routine.
DB2 support for JSON (enabled by APAR PM98357) added a number
of DB2-supplied routines, including a native SQL procedure
(SYSTOOLS.REGSP) and two SQL UDFs (SYSTOOLS.REG_MATCHES and
SYSTOOLS.REG_MATCHES_NOFLAGS). A subsequent APAR, PI11403,
modified the CREATE statements for these three particular
routines to specify the DISABLE DEBUG MODE option.
1 When a native SQL proc or SQL function is created with DISABLE
DEBUG MODE, the WLM_ENVIRONMENT column of the SYSIBM.SYSROUTINES
row for that routine is assigned DB2's default WLM environment,
that is the setting of the DSN6SYSP.WLMENV parameter.
If DSN6SYSP.WLMENV is set to blank or null, meaning that DB2 has
no default WLM environment, the WLM_ENVIRONMENT column of rows
in SYSIBM.SYSROUTINES for native SQL procs and SQL functions
that were created with DISABLE DEBUG MODE is also blank.
When DSNTRVFY attempts to validate the WLM environment for these
routines, it reports an error that the WLM environment is not
available, as noted in the problem description.
In response, this APAR modifies DSNTRVFY to bypass the WLM
environment validation for DB2-supplied native SQL procedures
and DB2-supplied SQL UDFs, even when the WLM_ENVIRONMENT column
of the SYSIBM.SYSROUTINES row for such a routine is not blank.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14134
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@RVFY PI14134
DSNTRVFY PI14134
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14134 DSN@RVFY DSNTRVFY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTRVFY
MACROS
DSN@RVFY
LISTEND
UI16700 COVER LETTER END
UI16701 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12250 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS with tracing *
* enabled and an error scenario occurred *
* during the firing of a ifi timer. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 IN DSNWVZXT *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The IFI timer module sets a recovery FRR if there is an error
1 in the recovery handling. The label used by the compiler was
incorrect by 4 bytes and the branch missed an instruction
resulting in the reported abend.
DB2 has been modified to branch to the correct location.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12250
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWVZXT PI12250
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12250 DSNWVZXT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVZXT
LISTEND
UI16701 COVER LETTER END
UI16707 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12428 -
****************************************************************
* USERS AFFECTED: All users of DB2/ODBC sample job DSNTEJ80 *
* and DB2 ODBC sample application DSN8OD1 in *
* DB2 10 for z/OS and DB2 11 for z/OS are *
* affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 ODBC sample job DSNTEJ80 job step *
* PH080S04 (program DSN8OD1) ends with *
* return code 0 and the following *
* messages: *
* *
* DSNU054I -DSN1 hh:mm:ss.nn DSNUGMAP *
* - TABLESPACE 'DSN8D91A.DSN8S91E' *
* NOT FOUND *
* DSNU605I -DSN1 hh:mm:ss.nn DSNUSVAL *
* - ERROR OCCURRED IN ACCESSING *
* TABLESPACE DSN8D91A.DSN8S91E *
* DSNU012I hh:mm:ss.nn DSNUGBAC - UTILITY *
* EXECUTION TERMINATED, HIGHEST *
* RETURN CODE=8 *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
DSN8OD1 is a sample C program that demonstrates using ODBC to
call SYSPROC.DSNUTILS, the DB2 Utilities Stored Procedure, and
process the result set from DSNUTILS.
When calling DSNUTILS, DSN8OD1 passes a DB2 RUNSTSATS utility
1 statement that specifies partition 3 of the table space that
contains the DB2 sample employee table, EMP.
Currently, the RUNSTATS statement specifies DSN8D91A.DSN8S91E,
which is the database and table space for the DB2 9 sample EMP
table. If these objects do not exist on a DB2 subsystem that
is running DB2 10 or DB2 11, the RUNSTATS request fails and
DSN8OD1 outputs the error messages noted in the Problem
Description.
In response, this APAR modifies DSN8OD1 as follows:
* In DB2 10, it changes the database and table space specified
for RUNSTATS to DSN8D10A.DSN8S10E, which contains the DB2 10
sample EMP table.
* In DB2 11, it changes the database and table space specified
for RUNSTATS to DSN8D11A.DSN8S11E, which contains the DB2 11
sample EMP table.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI12428
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN8OD1 PI12428
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12428 DSN8OD1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSN8OD1
LISTEND
UI16707 COVER LETTER END
UI16754 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09427 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of SELECT query *
* involving ORDER BY with a spanned record *
* whose length is larger than 32K. *
****************************************************************
* PROBLEM DESCRIPTION: An ABND04E RC00C200C6 at DSNB1REL *
* offset 0ECE occurs when running a *
* SELECT query with ORDER BY with a *
* sorted record whose length larger than *
* 32K. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a workfile insert of a spanned record, it may run into a
Bufferpool critical condition, DB2 logic can release the holding
1 page without resetting its internal control flags, such residual
flags can cause an abend later.
DB2 code is modified to skip the checking of bufferpool critical
condition while inserting a spanned record into a workfile.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09427
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISRTW PI09427
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09427 DSNISRTW
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISRTW
LISTEND
UI16754 COVER LETTER END
UI16798 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13130 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of Spatial support. *
****************************************************************
* PROBLEM DESCRIPTION: An SQLCODE443 is issued when selecting *
* or referencing the *
* DB2GSE.ST_INTERSECTION Spatial *
* function from DSNXRUFS location -101. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An SQLCODE443 is issued when selecting or referencing the
DB2GSE.ST_INTERSECTION Spatial function when a polygon overlays
another polygon.
The following query provides a failing example using
ST_INTERSECTION.
SELECT DB2GSE.ST_INTERSECTION(A.M_POLYGON, B.M_POLYGON)
FROM SYSADM.MULPOLYGONS1 A ,SYSADM.MULPOLYGONS2 B;
The unexpected result returned is,
SQL0965W SQLSTATE=01568
SQL0443N Routine "GSEOVERLAY" (specific name
STGN00070OVBB") has returned an
error SQLSTATE with diagnostic text
"GSE3400C Unknown error -2000.".
1 SQLSTATE=38SS0
The code in the DB2 Spatial component has been modified to
correct the ST_INTERSECTION problem when using the maximum
resolution to prevent the SQLCODE443 or Spatial "GSE3400C
Unknown error -2000" error when one polygon overlays
another polygon.
Additional Keywords: SQLSPATIAL SQLCODE443
COMPONENT: 5655-R1402-J2AG210
APARS FIXED: PI13130
SPECIAL CONDITIONS:
COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN5SG25 PI13130
DSN5SS2E PI13130
DSN5SS36 PI13130
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13130 DSN5SG25 DSN5SS2E DSN5SS36
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN5SG25
DSN5SS2E
DSN5SS36
LISTEND
UI16798 COVER LETTER END
UI16810 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14294 -
****************************************************************
* USERS AFFECTED: All DB2 9,10,11 for z/OS users who executes *
* SQL INSERT and UPDATE statements with *
* isolation level repeatable read. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101, *
* LOC=DSNIDM.DSNIMSAR ERQUAL5003 occurred *
* when running SQL INSERT or UPDATE *
* statements with isolation level *
* repeatable read. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend occurs during the execution of SQL INSERT or
SQL UPDATE statements. There is an index created on the table
that the INSERT or UPDATE statements run against, and
isolation level repeatable read is used.
1 Index manager requests RR lock on the next rid which is located
on the same index page as the rid that is being inserted or
updated.
The application then encounters a resource unavailable
condition. During the cleanup processing, the internal flag
indicating the lock state on the next rid remains set after the
index manager cleanup routine. The residual flag causes ABEND04E
RC00C90101 LOC=DSNIDM.DSNIMSAR ERQUAL5003 in data manager
cleanup routine.
Index manager cleanup routine is changed to reset the internal
flag representing the lock state when the lock requested by
index manager during insert is released.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14294
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKMSAX PI14294
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14294 DSNKMSAX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKMSAX
LISTEND
UI16810 COVER LETTER END
UI16826 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06677 -
****************************************************************
* USERS AFFECTED: Users of scrollable cursors and Load Resume *
* utility on a universal table space (UTS). *
****************************************************************
* PROBLEM DESCRIPTION: Abend04E RC00C90105 DSNIWLPG ERQUAL0C27 *
* during LOAD RESUME YES on a universal *
* table space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Load Resume Yes SHRLEVEL NONE could fail when 255 rows exist in
the current last page and the highest rids have been deleted
under a scrollable cursor. Load incorrectly loaded rows into
the page, wrapping the max row count and overlaying the
beginning IDMAP entries.
DSNIDLDU is changed to correctly handle non-reusable IDMAP
entries during Load Resume processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06677
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDLDU PI06677
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06677 DSNIDLDU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDLDU
LISTEND
UI16826 COVER LETTER END
UI16852 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM96961 -
****************************************************************
* USERS AFFECTED: Users of DB2 10 for z/OS and higher in data *
* sharing mode, who perform online zparm *
* changes to SIMULATED_CPU_SPEED and *
* SIMULATED_CPU_COUNT. *
****************************************************************
* PROBLEM DESCRIPTION: Users who perform online zparm changes *
* to SIMULATED_CPU_SPEED and/or to *
* SIMULATED_CPU_COUNT in one DB2 member *
* will not see these new value(s) for *
* this DB2 member reflected in the local *
* Task Manager block of the other DB2 *
* members in the data sharing group or in *
* the SCA, unless the user recycles the *
* DB2 subsystem. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Online zparm changes to SIMULATED_CPU_SPEED and/or
SIMULATED_CPU_COUNT in one DB2 member will now be updated in the
local Task Manager block of every member in the data sharing
group and the SCA.
Online zparm changes to SIMULATED_CPU_SPEED and/or
SIMULATED_CPU_COUNT will now be updated in the local Task
Manager block of every member in the data sharing group and in
SCA without requiring the user to recycle the DB2 subsystem.
Keywords: DB2DSHR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM96961
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSNTTCHZ PM96961
DSNTTEPL PM96961
HDBAA10J PM96961
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM96961 DSNTTCHZ DSNTTEPL HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTTCHZ
DSNTTEPL
LISTEND
UI16852 COVER LETTER END
UI16862 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09303 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG SHRLEVEL *
* CHANGE utility. *
****************************************************************
* PROBLEM DESCRIPTION: Reducing outage window duration for *
* REORG SHRLEVEL CHANGE execution. *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
Internal changes to reduce duration of SWITCH phase and
application outage window during REORG SHRLEVEL CHANGE
execution.
Code has been modified to reduce the SWITCH phase and outage
window duration during REORG SHRLEVEL CHANGE execution.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09303
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CPP PI09303
DSNURCCP PI09303
DSNURDRN PI09303
DSNURFIJ PI09303
DSNURLOG PI09303
DSNURSWD PI09303
DSNURWT PI09303
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09303 DSNB1CPP DSNURCCP DSNURDRN DSNURFIJ DSNURLOG DSNURSWD
DSNURWT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNB1CPP
DSNURCCP
DSNURDRN
DSNURFIJ
DSNURLOG
DSNURSWD
DSNURWT
LISTEND
UI16862 COVER LETTER END
UI16906 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11720 -
****************************************************************
* USERS AFFECTED: All DB2 9, DB2 10, and DB2 11 for z/OS users *
* of the MERGE statement. *
****************************************************************
* PROBLEM DESCRIPTION: Data may be inserted incorrectly into a *
* table which leads to an SQLCODE803 when *
* DB2 processes the an SQL MERGE *
* statement when the target table's RID *
* is larger than 'FF00000000'X. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the processing of an SQL MERGE statement, DB2 incorrectly
process the INSERT operation instead of the UPDATE operation.
This may results in an SQLCODE803 when data is incorrectly
inserted into a target table with a RID larger than
'FF00000000'X.
The bindtime code in DB2 has been modified to correct the
conditions leading to the incorrect behavior.
Additional Keywords: SQLMERGE SQLINSERT SQLUPDATE
SQLCODE803
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11720
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGMRG PI11720
DSNXODM PI11720
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11720 DSNXGMRG DSNXODM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGMRG
DSNXODM
LISTEND
UI16906 COVER LETTER END
UI16911 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11730 -
****************************************************************
* USERS AFFECTED: Users of native SQL procedures or SQL scalar *
* functions which reference special registers *
* CURRENT SERVER, CURRENT PACKAGE PATH or *
* CURRENT PACKAGESET in DB2 9, DB2 10 and DB2 *
* 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may incorrectly issue the SQLCODE *
* -20129 when rebinding a native SQL *
* procedure or an SQL scalar function *
* that contains the special register *
* CURRENT SERVER, CURRENT PACKAGE PATH *
* or CURRENT PACKAGESET in the CASE *
* expression of a CASE statement. *
* If one of these three *
* special registers is part of an *
* expression in the source value of a *
* SET assignment-statement or a VALUES *
* INTO statement inside a native SQL *
* procedure or an SQL scalar function, *
* DB2 will issue the SQLCODE -20129. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following examples will expose the problem (SQLCODE -20129):
CREATE PROCEDURE SP1(OUT P1 INT)
LANGUAGE SQL
BEGIN
CASE CURRENT SERVER
WHEN 'DBT1' THEN
SET P1 = 1;
WHEN 'DBT2' THEN
SET P1 = 2;
ELSE
SET P1 = 3;
END CASE;
1 RETURN;
END!
CREATE PROCEDURE SP2(OUT P1 CHAR(20))
LANGUAGE SQL
BEGIN
SET P1 = CURRENT SERVER || '1234' ;
END!
CREATE PROCEDURE SP3(OUT P1 CHAR(20))
LANGUAGE SQL
BEGIN
VALUES CURRENT SERVER || '1234' INTO P1 ;
END!
After applying this APAR,
the special registers CURRENT SERVER, CURRENT
PACKAGE PATH and CURRENT PACKAGESET can be combined with other
expressions in a SET assignment statement or VALUES INTO
statement in a native SQL procedure or an SQL scalar function.
They can also be used in the CASE expression of a CASE
statement.
Additional keywords: SQLCODE20129 SQLNATIVESQLPL SQLSCALARUDF
SQLSPECIALREG
DB2 code is modified so that the three special registers:
CURRENT SERVER, CURRENT PACKAGE PATH and CURRENT PACKAGESET
can be used in the CASE expression of a CASE statement and
in an expression of the
SET assignment or VALUES INTO statement inside a native SQL
procedure or an SQL scalar function.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11730
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
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:
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHSMS1 PI11730
DSNHSM5R PI11730
DSNXOYDA PI11730
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11730 DSNHSMS1 DSNHSM5R DSNXOYDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHSMS1
DSNHSM5R
DSNXOYDA
LISTEND
UI16911 COVER LETTER END
UI16941 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10842 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 & 11 for z/OS. *
****************************************************************
1 * PROBLEM DESCRIPTION: ABEND0C4 in csect DSNTLDEA or DSNTLTIM *
* may occur during a deadlock or timeout *
* processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 Timeout and Deadlock processing involves extracting the
DB2 thread information for the lock waiter and/or holder. This
information may be wrong for CUBs and RURE type of work units
due to incorrect validation check of DB2 control blocks. As a
result, referencing a null pointer causes ABEND0C4 leading to
system termination.
This APAR corrects the validation checks for finding DB2 agent
information of waiting request in the Timeout and Deadlock Exits
to prevent ABEND0C4.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10842
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTLDEA PI10842
DSNTLTIM PI10842
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10842 DSNTLDEA DSNTLTIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTLDEA
DSNTLTIM
LISTEND
UI16941 COVER LETTER END
UI16958 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12418 -
****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of the *
* SOUNDEX or DIFFERENCE built-in function *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at location *
* DSNKMVKY 5001 (ERQUAL5001) or at *
* location 5004 (ERQUAL5004) can occur *
* for a query that contains a predicate *
* with the SOUNDEX or DIFFERENCE *
* built-in function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The above abends can occur if the following conditions are
true :
1
- the SQL contains a predicate that is pushed down to the
Index Manager or Data Manager subcomponent for evaluation.
- the predicate contains the SOUNDEX or DIFFERENCE built-in
function
- the CCSID translation for the built-in function needs to
read a row from the SYSIBM.SYSSTRINGS catalog table and
that has not been previously cached.
Please note that the PUSHDOWN column of the DSN_FILTER_TABLE
shows whether the predicate is pushed down to Index Manager
or Data Manager for evaluation.
The following SQL is an example that may encounter the abend:
SELECT NAME
FROM T1
WHERE SOUNDEX(NAME) = SOUNDEX('Andrew');
It is possible for the query to abend at other locations
not mentioned above.
The code in DB2 was modified to not push down predicates
for queries with a SOUNDEX or DIFFERENCE built-in function
in the predicate. This may affect performance of the query.
Additional Keywords: SQLPREDPUSHDOWN SQLSOUNDEX SQLCCSID
SQLDIFFERENCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12418
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPB PI12418
DSNXORES PI12418
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12418 DSNXOPB DSNXORES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXOPB
DSNXORES
LISTEND
UI16958 COVER LETTER END
UI16988 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11245 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of queries with *
* UNION and column masks *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at location *
* DSNXGRDS DSNXOACM P030 or P080 can *
* occur for a query referencing a view *
* or table expression that contains *
* UNIONs and columns defined with a *
* column mask. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The above abends can occur if the query references a view or
table expression and the view or table expression meets the
following criteria:
1. There are more than 64 set operators such as UNION
2. Every subselect references at least one column that has a
column mask defined on it.
An example follows :
CREATE TABLE TMASK ( C1 INT WITH DEFAULT NULL );
CREATE MASK MASK1 ON TMASK AS A FOR COLUMN C1
RETURN CASE WHEN (C1 > 1) THEN NULL ELSE C1 END
ENABLE;
ALTER TABLE TMASK ACTIVATE COLUMN ACCESS CONTROL;
* more than 64 subselects UNIONed
CREATE VIEW VMASK AS (
SELECT C1 FROM TMASK
UNION
SELECT C1 FROM TMASK
UNION
SELECT C1 FROM TMASK
UNION
...
UNION
SELECT C1 FROM TMASK);
1 SELECT * FROM VMASK; - abend occurs on the SELECT
DB2 10 for z/OS does not support column masks in a UNION
subselect and will issue SQLCODE -20478 after this apar is
applied.
DB2 has been modified to handle more than 64 unioned subselects
with column masks. DB2 10 for z/OS will issue SQLCODE -20478
after this PTF is applied.
Additional keywords : SQLUNION SQLTABLEEXPR SQLVIEW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11245
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOACM PI11245
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11245 DSNXOACM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOACM
LISTEND
UI16988 COVER LETTER END
UI17039 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12047 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 users who use *
* user-defined table functions and will *
* like to omit the correlation name *
****************************************************************
* PROBLEM DESCRIPTION: 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 its result columns) *
* directly in the query. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
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
1 reference the name of the table function (and its 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:
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 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.
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 its 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;
1
SELECT X.C1 FROM TABLE(TUDF1(1)) X(C1);
Currently the following receives SQLCODE -104:
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.
Additional keywords: SQLTABLEUDF, SQLTUDF, SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12047
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
***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
1 RETURN SELECT C1 + X FROM T1;
COMMIT;
SELECT X.C1 FROM TABLE(TUDF1(1)) X(C1);
Currently the following receives SQLCODE -104:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHSM10 PI12047
DSNXOP0 PI12047
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12047 DSNHSM10 DSNXOP0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHSM10
DSNXOP0
LISTEND
UI17039 COVER LETTER END
UI17042 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI04839 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* accessing DB2 10 for z/OS in new function *
* mode from a Java IBM Data Server Client *
* Driver where the client application uses *
* TIMESTAMP WITH TIMEZONE data type as input *
* and TIMESTAMP data type as target. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 V10 issues an SQLCODE181 when a *
1 * client application passing in a *
* boundary TIMESTAMP WITH TIMEZONE input *
* value (e.g. 9999-12-31-23.59.59.000000 *
* -8:00) to a TIMESTAMP target data type. *
* DB2 does an intermediate conversion of *
* the TIMESTAMP WITH TIMEZONE value into *
* the TIMESTAMP value in UTC format (i.e. *
* 10000-01-01-07.59.59.000000) when *
* processing. This causes the value to *
* go beyond the maximum TIMESTAMP value *
* that DB2 supports. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the client application uses PreparedStatement.setTimestamp
method to pass in a boundary TIMESTAMP input value to a
TIMESTAMP target against DB2 10 NFM server, Java IBM Data Server
Client driver appends the time zone information from the local
time zone. During server processing, the value gets converted
in UTC format which may cause it to go beyond the maximum or
minimum TIMESTAMP value DB2 supports.
.
One solution is provided by the Java IBM Data Server Driver.
See APARs PM96293, PM96295 and IC99579. Refer to those APARs
for details.
To prevent applications from getting SQLCODE181, DB2 server
provides a new option, IGNORE_TZ, for the DDF_COMPATIBILITY
ZPARM. The new ZPARM option allows DB2 server to ignore
TIMEZONE portion of the value in the TIMESTAMP WTIH TIMEZONE
input to a TIMESTAMP target during the intermediate conversion
processing. When IGNORE_TZ option is turned on for the
DDF_COMPATIBILITY ZPARM, then SQLCODE181 will be prevented.
The ZPARM and trace details:
1. 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
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.
1
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)
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.
2. This PTF also introduced a new value for field QW0366FN in
IFCID 0366 to help detect whether an application may encounter
SQLCODE181 due to a boundary value of the TIMESTAMP WITH
TIMEZONE input value when it is passed into DB2 10 Server.
DB2 10 Server will produce the IFCID 0366 trace records with
the new value when all of the following conditions are met:
(1). IFCID 0366 is enabled on DB2 10 for z/OS server
(2). IGNORE_TZ is set for DDF_COMPATIBILITY zparm
(3). The application is using a supported Java IBM Data Server
Driver
This is the new value introduced for QW0366FN field:
QW0366FN = 9
A QW0366FN 9 record indicates a data type conversion from
a TIMESTAMP WITH TIME ZONE input to a TIMESTAMP data
during input host variable bind-in process on server when
DDF_COMPATIBILITY zparm is set to IGNORE_TZ to ignore the
time zone information sent by Java IBM Data Server Driver.
When examining collected IFCID 0366 trace records, if any record
with a QW0366FN value of 9 then take a closer look at the input
TIMESTAMP string and act accordingly if a boundary TIMESTAMP
value (e.g. 0001-01-01-00.00.00.000000 or
9999-12-31-23.59.59.000000) is used. The TIMEZONE information
appended by the driver may cause the converted intermediate
TIMESTAMP value to underflow or overflow respectively.
3. This PTF modifies the installation CLIST in both DB2 10 and
DB2 11 so that it can manage additional settings for the
DSN6FAC.DDF_COMPATIBILITY parameter. In particular, the CLIST
input (DSNTIDxx) member now stores DDF_COMPATIBILITY parameter
in two consecutive entries, DDF_COMPATIBILITY and
DDF_COMPATIBILITY1. For example:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M <y>
1
See the ++HOLD actions for guidance on adapting your private
copies of the DSNTIDxx member.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI04839
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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
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
1 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
DDF_COMPATIBILITY CHARR M NONE NONE <x>
to the format below. If no entry for DDF_COMPATIBILITY is
present, add one that is in the format below.
DDF_COMPATIBILITY STR M <x>
Change <x> to NULL if you skipped step (2), above.
Otherwise, change <x> 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
1
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.
DB2BIND:
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)
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.
1
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers 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.
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 <x>
or this format:
DDF_COMPATIBILITY STR M <x>
to this format:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M NULL
Change <x> 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:
1 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 <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI04839
DSNDQWPZ PI04839
DSNDQW05 PI04839
DSNLXRSS PI04839
DSNTIDXA PI04839
DSNTIDXB PI04839
DSNTINST PI04839
DSNTXAZP PI04839
DSNWZIFA PI04839
DSNXRIHD PI04839
DSNXRIHS PI04839
DSN6FAC PI04839
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI04839 DSN@XAZP DSNDQWPZ DSNDQW05 DSNLXRSS DSNTIDXA DSNTIDXB
DSNTINST DSNTXAZP DSNWZIFA DSNXRIHD DSNXRIHS DSN6FAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXRSS
DSNTXAZP
DSNWZIFA
DSNXRIHD
DSNXRIHS
MACROS
DSN@XAZP
DSNDQWPZ
DSNDQW05
DSNTIDXA
DSNTIDXB
DSNTINST
1 DSN6FAC
LISTEND
UI17042 COVER LETTER END
UI17082 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07794 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/0S *
* utility users of RUNSTATS TABLESPACE *
* TABLE COLGROUP *
****************************************************************
* PROBLEM DESCRIPTION: INCORROUT MSGDSNU616I and incorrect *
* aggregate cardinality statistics in *
* SYSIBM.SYSCOLDIST catalog table *
* when RUNSTATS TABLESPACE TABLE *
* COLGROUP is executed. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When RUNSTATS TABLESPACE TABLE with multiple COLGROUP keywords
(with same leading columns) are specified, incorrect
intermediate cardinalities were reported. The incorrect
aggregated statistics were stored in the SYSCOLDIST catalog
table.
The incorrect intermediate cardinality statistics were
collected due to the usage of only one estimation data
structure.
When RUNSTATS TABLESPACE TABLE COLGROUP TABLESAMPLE SYSTEM
was executed on a segmented tablespace, incorrect intermediate
cardinalities were reported in MSGDSNU616I and those values
were inserted into the SYSCOLDIST catalog table.
This was caused by an incorrect number of total rows
that was being passed to the estimation routine.
Code was modified to aggregate the intermediate
cardinalities for the COLGROUP by a better estimation
algorithm.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI07794
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSDST PI07794
DSNUSEF2 PI07794
DSNUSITS PI07794
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07794 DSNUSDST DSNUSEF2 DSNUSITS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNUSDST
DSNUSEF2
DSNUSITS
LISTEND
UI17082 COVER LETTER END
UI17098 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06426 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of CREATE ALIAS *
* who also have system parameter DBACRVW=YES. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -551 incorrectly received on a *
* CREATE ALIAS for a history table when *
* executed by an authorization ID that *
* does not have CREATEALIAS privilege *
* or SYSADM/SYSCTRL authority but does *
* have DBADM authority when DBACRVW is *
* set to YES. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQLCODE -551 was incorrectly received when executing
CREATE ALIAS for a history table using an authorization ID
having DBADM authority, and when system parameter DBACRVW=YES.
The error can also occur when attempting to create an alias
for a materialized query table (MQT) or a clone table.
DB2 has been changed such that CREATE ALIAS on history tables,
MQTs and clone tables does not incorrectly receive SQLCODE -551
when executed by an authorization ID having DBADM authority
when DBACRVW=YES.
ADDITIONAL KEYWORDS:
SQLCODE551
SQLCREATE
SQLALIAS
SQLBITEMPORAL
SQLMQT
SQLCLONE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06426
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODD2 PI06426
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06426 DSNXODD2
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODD2
LISTEND
UI17098 COVER LETTER END
UI17121 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12215 -
****************************************************************
* USERS AFFECTED: All Users of the DB2 Universal JDBC Driver, *
* DB2 OLE DB Driver, DB2 z/OS ODBC driver *
* or the CLI Driver provided with DB2 for *
* Linux, Unix and Windows Version 8 and above *
* that connect to DB2 10 z/OS and DB2 11 z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Database Metadata stored procedure *
* SYSIBM.SQLCOLUMNS may return *
* SQL0443N/SQLSTATE38113 with DIAGNOSTIC *
* TEXT "-104 AR ) CCSID FOR" when
*
* SYSSCHEMA keyword is in use. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After migrating DB2 for z/OS from V9 to V10, applications using
Database Metadata procedure, SYSIBM.SQLCOLUMNS, with SYSSCHEMA
keyword in use may encounter SQL0443N/SQLSTATE38113 with
DIAGNOSTIC TEXT "-104 AR ) CCSID FOR".
The following error message may be seen from WLM output:
DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL "AR".
SOME SYMBOLS THAT MIGHT BE LEGAL ARE: ) CCSID FOR"
Database Metadata procedure SYSIBM.SQLCOLUMNS is fixed to
return correct result set when SYSCHEMA is in use.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12215
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
Procedures for these actions are given below.
----------------------------------------------------------------
1
(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=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application
environment in which the Database Metadata stored procedure
SYSIBM.SQLCOLUMNS is running.
ACTION:
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
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
1 If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
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=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application
environment in which the Database Metadata stored procedure
SYSIBM.SQLCOLUMNS is running.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@COLU PI12215
DSNACOLU PI12215
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12215 DSN@COLU DSNACOLU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNACOLU
MACROS
DSN@COLU
LISTEND
UI17121 COVER LETTER END
UI17126 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06924 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E50106 may occur *
* during End of Task processing for a *
* nested UDF. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An ABEND04E RC00E50106 can occur when a nested UDF in abort
processing goes through end of task processing. DB2 processing
looks on the wrong agent chain for the target thread and abends
when it cannot find it.
DB2 processing has been modified to find the agent on the
correct chain during EOT processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06924
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVRDAG PI06924
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06924 DSNVRDAG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVRDAG
LISTEND
UI17126 COVER LETTER END
UI17149 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14190 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* CATMAINT utility users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 AT DSNXGRDS *
* and error MSGDSNU087 (INVALID *
* OPERAND TYPE FOR KEYWORD SWITCH) *
* were issued for the CATMAINT UPDATE *
* SCHEMA SWITCH utility when the SWITCH *
* operands were enclosed in single *
* quotes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Customer ran a CATMAINT UPDATE SCHEMA SWITCH utility
with invalid operands. Error message DSNU087 was issued
but the utility did not halt processing. This allowed a
subsequent abend.
The code to set return code RC8 and exit after the DSNU087
message was missing.
This error can occur if either of the SWITCH schema-name
operands is in single quotes, or if any of the UPDATE OWNER FROM
owner-name operands is in single quotes.
1 The missing code has been added. The CATMAINT utility will
terminate with RC8 following the DSNU087 message.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14190
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGPPA PI14190
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14190 DSNUGPPA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGPPA
LISTEND
UI17149 COVER LETTER END
UI17167 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM86380 -
****************************************************************
* USERS AFFECTED: All DB2 V10 users and higher. *
* **NOTE** *
* The function in PM86380 is only made *
* available if z/OS OA42345 is also applied. *
* Either may be applied without the other. *
****************************************************************
* PROBLEM DESCRIPTION: High Virtual Common (HVCOMMON) storage *
* may be read even though frames are all *
* in first reference state, causing *
* them all to be backed which increases *
* the amount of REAL used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 uses Page Protect function to protect the majority of unused
HVCOMMON storage object but it only prevents writing to that
storage, not reading it. If monitor or error causes all of the
protected pages which are in FREF ( first reference ) state to
be read, the entire object range may be BACKED in REAL for the
duration of this DB2 instance.
DB2 is changed to enable GUARDPAGE function for the HVCOMMON
object which was delivered by z/OS OA42345. IF this apar is
applied to the z/OS, then PM86380 will result in the majority
of the HVCOMMON object being Guarded. This means that those
pages beyond the guardpage are not eligible for Read or Write.
If DB2 needs to use a portion of the object which has been
guarded, the guardpage will be moved. If z/OS OA42345 is NOT
APPLIED, there will be no guarded storage and the entire object
would be open for read and write. Unused storage would not
1 be protected.
The z/OS function is provided by:
R770 PSY UA71398 UP13/11/20
R78H PSY UA71401 UP13/11/20
R780 PSY UA71399 UP13/11/20
R790 PSY UA71400 UP13/11/20
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM86380
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNSVSGM PM86380
DSNSVSPC PM86380
DSNSVSVP PM86380
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM86380 DSNSVSGM DSNSVSPC DSNSVSVP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNSVSGM
DSNSVSPC
DSNSVSVP
LISTEND
UI17167 COVER LETTER END
UI17182 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11454 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of a native SQL *
* procedure or non-inline SQL scalar function *
* containing assignment-statement. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect statement number and section *
* number could be generated when a native *
* SQL procedure 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. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
CREATE PROCEDURE TEST.P1()
LANGUAGE SQL
DISABLE DEBUG MODE
L1: BEGIN
DECLARE VAR2 CHAR(10);
DECLARE VAR3 CHAR(10);
DECLARE VAR4 CHAR(10);
SET VAR3 = SUBSTR1('ABC',1,2,3);
SET VAR4 = SUBSTR('ABCD',1, 2);
END L1!
DB2 does not process the assignment-statement properly which
can result in incorrect statement and section numbers being
generated, and can result in the execution of additional SQL
statements at run time.
After applying this APAR, STMTNO, SECTNO, STMTNOI and SECTNOI
column information can be changed in SYSIBM.SYSPACKSTMT and
SYSIBM.SYSQUERY table.
QUERYNO and SECTNOI column information can be changed in
EXPLAIN tables.
DB2 is modified correctly to process assignment-statement
to avoid the problem.
Additional Keywords: SQLSP SQLSTOREDPROC SQLNATIVESQLPL
SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11454
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
PI11454 corrects a problem that incorrect statement number and
section number could be generated when a native SQL procedure
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.
1
Review the PTF cover letter to determine which, if any, native
SQL procedure and SQL scalar function could be affected by
this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOYPL PI11454
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11454 DSNXOYPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOYPL
LISTEND
UI17182 COVER LETTER END
UI17200 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12132 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG SHRLEVEL *
* CHANGE. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C7 at DSNURLAP OFFSET326E during *
* the LOG phase of a REORG TABLESPACE *
* SHRLEVEL CHANGE with KEEPDICTIONARY *
* option on a partition-by-growth (PBG) *
* table space with COMPRESS YES *
* attribute. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REORG SHRLEVEL CHANGE with KEEPDICTIONARY option ran on a
compressed PBG table space which had partitions with different
dictionaries. The table in this table space was defined with
Change Data Capture (CDC) attribute. This REORG abended with
ABEND0C7 at DSNURLAP + '326E'x when applying a log record of a
cross-partition update during the LOG phase.
This problem occurred because REORG was not applying the log
record correctly.
The same problem could also occur for a non-CDC table.
REORG code has been modified to handle the cross-partition
update logs correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12132
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGLGR PI12132
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12132 DSNUGLGR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGLGR
LISTEND
UI17200 COVER LETTER END
UI17201 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12563 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of part level REORG TABLESPACE *
* SHRLEVEL CHANGE or REFERENCE. *
****************************************************************
* PROBLEM DESCRIPTION: Deadlock on catalog table space *
* DSNDB06.SYSTSTPT occurred during the *
* SWITCH phase of two concurrent part *
* level online REORGs. One of them *
* failed with ABEND04E RC00E4070D *
* RC00C90088 and MSGDSNT500I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
Two REORG SHRLEVEL CHANGE utilities concurrently ran on some
disjoint parts of a partitioned table space. One of the REORGs
failed with ABEND04E RC00E4070D RC00C90088 along with the
message DSNT500I because a deadlock occurred on the catalog
table space DSNDB06.SYSTSTPT when updating the EPOCH column
in SYSIBM.SYSTABLEPART table during the SWITCH phase.
This problem occurred because of a logic error when updating
the EPOCH column in SYSIBM.SYSTABLEPART table during a
disjoint part REORG.
REORG code has been modified to correct the logic error when
updating the EPOCH column in SYSIBM.SYSTABLEPART table during
the SWITCH phase.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12563
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURSWD PI12563
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12563 DSNURSWD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNURSWD
LISTEND
UI17201 COVER LETTER END
UI17203 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13342 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RUNSTATS REPORT NO UPDATE NONE or *
* ACCESSPATH with HISTORY SPACE or ALL option. *
****************************************************************
* PROBLEM DESCRIPTION: RUNSTATS REPORT NO UPDATE NONE HISTORY *
* ALL updated a zero value to the SPACEF *
* column in SYSIBM.SYSTABLES_HIST table *
* for a partitioned table space. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A RUNSTATS REPORT NO UPDATE NONE HISTORY ALL on a partitioned
table space incorrectly set the SPACEF column in SYSIBM.
SYSTABLES_HIST table to zero.
The same problem also occurred on the AVGROWLEN column in
SYSIBM.SYSTABLES_HIST table.
This problem occurred because some space-related statistics
were not collected for a partitioned table space when REPORT
NO and UPDATE NONE or ACCESSPATH were specified, even with
the option HISTORY SPACE or ALL.
The problem could also occur for LOAD or REORG with inline
statistics.
RUNSTATS code has been modified to collect space-related
statistics if REPORT NO UPDATE NONE/ACCESSPATH with HISTORY
SPACE/ALL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13342
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSATS PI13342
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13342 DSNUSATS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSATS
LISTEND
UI17203 COVER LETTER END
1UI17226 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13232 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users in *
* migration processing. Specifically those *
* with remote applications, connecting to the *
* DB2 10 for z/OS server which has fallen back *
* to DB2 10 for z/OS in Conversion Mode (CM*) *
* or Enabling New Function Mode* (ENFM*) from *
* previous New Function Mode (NFM). *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -4700 and SQLCODE -104 may be *
* returned when a client application *
* using IBM Java Data Server Driver *
* accesses a DB2 10 for z/OS server in *
* Conversion Mode (CM*), or Enabling New *
* Function Mode (ENFM*) which has fallen *
* back from New Function Mode (NFM). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an IBM Java Data Server Driver based application accesses
a DB2 10 for z/OS CM* or ENFM* subsystem, which has fallen back
from NFM, the driver still recognizes the remote server as DB2
10 for z/OS server in NFM and may therefore associate SQL with
an "WITH EXTENDED INDICATOR" attribute string. However, this
attribute string is not supported at a DB2 10 for z/OS server
in non NFM, thus SQLCODE -4700 or SQLCODE -104 is returned.
Relative to IBM Java Data Server Driver based applications, DB2
10/11 for z/OS server processing has been changed to tolerate
and remove the "WITH EXTENDED INDICATOR" attribute string
when
in CM* and ENFM*.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13232
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLZSMT PI13232
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13232 DSNLZSMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLZSMT
LISTEND
UI17226 COVER LETTER END
UI17240 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI09198 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and 11 for z/OS *
* who use IBM DB2 Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR provides the following new *
* functions for IBM DB2 Analytics *
* Accelerator: *
* *
* (1) Enable execution of time and *
* timestamp constants containing *
* a time 24:00 constant in a query. *
* (2) support query offloading for the *
* FOR BIT DATA data type if the *
* statement only references EBCDIC *
* SBCS expressions. *
* (3) Refinement of eligibility for *
* queries with FETCH FIRST N ROWS *
* ONLY. *
* *
* This APAR provides the following fix: *
* (1) Execution of a query on an *
* accelerator with multiple ORDER BY *
* clauses can abend: *
* ABEND0C4 RC00000038 at DSNXONZC +324C *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the following new functions for IBM DB2
Analytics Accelerator:
(1) Enable execution of time and timestamp constants containing
a time 24:00 constant in a query.
(2) support query offloading for the FOR BIT DATA data type if
the statement only references EBCDIC SBCS expressions.
(3) Refinement of eligibility for queries with FETCH FIRST N
ROWS ONLY.
This APAR provides the following fix:
(1) Execution of a query on an accelerator with multiple
ORDER BY clauses can abend:
ABEND 0C4 RC00000038 at DSNXONZC+324C
For static SQL queries that have been bound for acceleration
and will use any of the new functions above, REBIND the
package(s) for the failing queries after applying this PTF.
Additional Keywords:
IDAAV4R1/K ABEND0C4 RC00000038 OFFSET324C SQLFFNR SQLORDERBY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09198
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXRSQ PI09198
DSNXODML PI09198
DSNXOD5 PI09198
DSNXOEX1 PI09198
DSNXONZA PI09198
DSNXONZB PI09198
DSNXONZC PI09198
DSNXONZH PI09198
DSNXONZQ PI09198
DSNXONZS PI09198
DSNXOOS1 PI09198
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09198 DSNLXRSQ DSNXODML DSNXOD5 DSNXOEX1 DSNXONZA DSNXONZB
DSNXONZC DSNXONZH DSNXONZQ DSNXONZS DSNXOOS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXRSQ
DSNXODML
DSNXOD5
DSNXOEX1
DSNXONZA
DSNXONZB
DSNXONZC
DSNXONZH
DSNXONZQ
DSNXONZS
DSNXOOS1
LISTEND
UI17240 COVER LETTER END
UI17244 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI14750 -
****************************************************************
* USERS AFFECTED: All DB2 data sharing users of IFCID 306. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 IN CSECT DSNIDLGR *
* ERQUAL503B WHEN ADDING A NEW MEMBER TO *
* THE DATA SHARING GROUP. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a new member is added to (or Joined) data sharing group and
IFCID 306 application is reading all the log records (i.e.
WQALLCRI=WQALLCRA), it is possible that DB2 will return a log
record with zero RBA to the caller. However, Data Manager (DM)
log read routine does not tolerate reading zero RBA log record
and issues the RC00C90101 abend, indicating that IFCID 306
requesting too old log data set. This is not correct, when a new
member just join the data sharing group and we are reading its
log records. The very first log record written by any new member
will be assign RBA of zero. Therefore, in this case reading and
returning log record with zero RBA is ok. DM logic will tolerate
zero RBA in this special case and will not abend.
DB2 IFCID 306 log read logic is modified to tolerate zero RBA
log record when reading log records from the DB2 member that has
just joined the data sharing group.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14750
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDLGR PI14750
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14750 DSNIDLGR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDLGR
LISTEND
UI17244 COVER LETTER END
UI17277 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13088 -
****************************************************************
* USERS AFFECTED: ALL DB2 for z/OS v10 users of a query *
* containing view defined with set functions. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNISFW : 500B *
* may occur for a query containing view *
1 * defined with set functions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C90101 at DSNISFW : 500B may occur for a query
containing view defined with set functions.
The following query is an example of this case:
CREATE VIEW VIEWT(COL1,COL2)
AS
WITH n (COL1,COL2)
AS (SELECT TAB1.COL1,CAST(TAB1.COL2 AS INTEGER) AS COL2
FROM TAB1)
SELECT COL1,COL2
FROM n;
SELECT COUNT(*) FROM VIEWT;
The bindtime code in DB2 is modified to correct the conditions
leading to the incorrect result.
Additional keywords:SQLSETFUNCTION SQLVIEW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13088
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
PI13088 corrects a problem that can cause an abend at
DSNISFW : 500B for a query of view defined with set functions.
DB2BIND:
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.
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOMS PI13088
DSNXOSR PI13088
DSNXOSSF PI13088
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13088 DSNXOMS DSNXOSR DSNXOSSF
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOMS
DSNXOSR
DSNXOSSF
LISTEND
UI17277 COVER LETTER END
UI17279 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11673 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD SHRLEVEL NONE with FLASHCOPY *
* YES *
****************************************************************
* PROBLEM DESCRIPTION: RC4 during a LOAD SHRLEVEL NONE with *
* FLASHCOPY YES only *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a LOAD SHRLEVEL NONE with FLASHCOPY YES and no COPYDDN
specified. The LOAD ended with RC00000004 in spite of the fact
that the FLASHCOPY return code was zero and the LOAD did not
have any warning message in the job output.
LOAD was incorrectly setting a RC4 when no sequential copy
(COPYDDN) was made even though a FLASHCOPY copy was.
The LOAD utility code has been modified to not set RC4 when no
COPYDDN is specified with FLASHCOPY YES.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11673
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURILD PI11673
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11673 DSNURILD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURILD
LISTEND
UI17279 COVER LETTER END
UI17291 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15146 -
1 ****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries that use the FETCH FIRST n ROWS ONLY *
* clause. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E rc00E20009 can occur at *
* DSNSVSFB OFFSET0898 when an invalid *
* number of blocks is requested by SORT *
* for fetch first processing when using *
* the FETCH FIRST n ROWS ONLY clause. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E rc00E20009 can occur at DSNSVSFB +0898 when an
invalid number of blocks is requested by SORT for fetch first
processing (on behalf of the FETCH FIRST n ROWS ONLY clause).
The error occurs because the fetch first processing module
should not have been invoked, it was invoked in error. This
occurs because a calculation (which uses the size of the row and
the number of fetch first rows) result was not compared with a
correct 'constant value' which is used to determine which mode
of processing SORT should use for fetch first processing.
This 'constant value' is not defined properly so the result of
the compare is not correct which dictates the improper code
path.
The code in DB2 has been modified to correct the condition
leading to the failure by redefining the 'constant value'. This
will allow the compare to work properly which will prevent the
errant code path.
Additional Keywords: SQLFFNR SQLSORT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15146
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSORI PI15146
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15146 DSNXSORI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSORI
LISTEND
UI17291 COVER LETTER END
1UI17305 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12606 -
****************************************************************
* USERS AFFECTED: All DB2 data sharing users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNKPGCM *
* ERQUAL5001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an index page set is getting physically opened by the
Pseudo Close Processor, a concurrent group buffer pool
checkpoint operation is also running, trying to cast out pages
for the same page set which is not fully opened. Castout may
fail and place the index page set in LPL. Automatic LPL recovery
may also fail due to the same reason.
DB2 castout logic has been fixed to check the proper indicator
and make sure that the page set open process is complete before
using the page set for castout.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12606
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5PCO PI12606
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12606 DSNB5PCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5PCO
LISTEND
UI17305 COVER LETTER END
UI17310 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11035 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNB5SC2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend occurs when DSNB5SC2 searches for an entry in a pageset
write log record, following a failure writing a page to the GBP.
Abend happens only if the write was not being logged (normal for
a force-at-commit write), and only when using a zero log pointer
results in seeing a non-zero entry count in low core.
1 DSNB5SC2 has been modified to avoid the log record search when
the write is not being logged.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11035
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5SC2 PI11035
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11035 DSNB5SC2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5SC2
LISTEND
UI17310 COVER LETTER END
UI17315 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06045 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Abend 0C4-00000038 DSNLCMSL+2A5E. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After a DB2 for z/OS server returned LOB data to a remote
requester, DB2 freed an internal LOB related structure but
neglected to clear the pointer to that structure. During a
subsequent request, this reference to the residual LOB
structure can cause the reported abend.
DB2 for z/OS server processing has been changed to clear its
pointer to the LOB structure after returning LOB data to the
remote requester.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06045
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCRTD PI06045
DSNLCSRR PI06045
DSNLIRTR PI06045
DSNLXRSS PI06045
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06045 DSNLCRTD DSNLCSRR DSNLIRTR DSNLXRSS
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCRTD
DSNLCSRR
DSNLIRTR
DSNLXRSS
LISTEND
UI17315 COVER LETTER END
UI17349 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10708 -
****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of *
* LOB and CONCAT built-in function *
* or CONCAT operator. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNOTFLA *
* ERQUAL5004 could occur *
* for an SQL statement that *
* contains a CONCAT built-in *
* function or a CONCAT operator *
* in the select list and the *
* argument of the CONCAT operator *
* is a LOB expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(C1 VARCHAR(32600), C2 INT);
SELECT CLOB(C1) || CLOB(C1) FROM T1 ORDER BY C2;
DB2 did not correctly process the aforementioned SQL statements,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statements, so there will be no ABEND.
Additional keywords: SQLLOB SQLCONCAT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10708
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSL PI10708
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10708 DSNXOSL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSL
LISTEND
UI17349 COVER LETTER END
UI17351 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13431 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of a view *
* created from V5 or prior releases with a *
* COUNT(*) or COUNT_BIG(*), or DB2 10 and 11 *
* for z/OS users of UNICODE, GRAPHIC, *
* VARGRAPHIC or DBCLOB built in functions. *
* *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000004 at the location *
* DSNXGRDS DSNXOOS1 OFFSET42A4 could *
* happen for an SQL statement containing *
* a view created and migrated from V5 or *
* prior releases, and the view contains a *
* COUNT(*) or COUNT_BIG(*). *
* *
* SQLCODE -20289 may be issued *
* incorrectly for SQL statement that *
* references UNICODE, VARGRAPHIC, *
* GRAPHIC or DBCLOB built in *
* functions. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. ABEND0C4 RC00000004 at the location DSNXGRDS DSNXOOS1
OFFSET42A4
An example of the view is shown below:
1 CREATE TABLE T1 (
C1 INT,
C2 INT
);
CREATE VIEW V1 AS(
SELECT C1, COUNT(*) AS CNT
FROM T1
GROUP BY C1
HAVING COUNT(*) > 1
);
DB2 did not correctly process the aforementioned view created
and migrated from V5 or prior releases, which caused the ABEND.
2. SQLCODE -20289 may be issued incorrectly for statementthat
references UNICODE, VARGRAPHIC, GRAPHIC, or DBCLOB built in
functions.
SQLCODE -20280 may be issued incorrectly due to an unitialized
variable.
DB2 has been modified to correctly process the aforementioned
view, so there will be no ABEND.
Db2 has been modified to correctly process statements reference
UNICODE, VARGRAPHIC, GRAPHIC, or DBCLOB built in functions
correctly.
Additional keywords: SQLVIEW SQLCOUNT SQLCOUNTBIG
SQLUNICODE, SQLGRAPHIC, SQLVARGRAPHIC,
SQLDBCLOB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13431
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFA PI13431
DSNXOBFF PI13431
DSNXOEX1 PI13431
DSNXOOS1 PI13431
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13431 DSNXOBFA DSNXOBFF DSNXOEX1 DSNXOOS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBFA
DSNXOBFF
DSNXOEX1
DSNXOOS1
LISTEND
1UI17351 COVER LETTER END
UI17359 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM99259 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* REORG TABLESPACE ROWFORMAT RRF utility *
* users on DEFINE NO objects. *
****************************************************************
* PROBLEM DESCRIPTION: Allow row format conversion from basic *
* row format (BRF) to reordered row *
* format (RRF) during a REORG TABLESPACE *
* utility on a DEFINE NO undefined object *
* when ROWFORMAT RRF is specified. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When a REORG TABLESPACE ROWFORMAT RRF utility is run on an
object that is not yet defined, the utility will issue
MSGDSNU185I - THE VSAM DATA SET DOES NOT EXIST and will end
with RC0 without doing any row format conversion.
This APAR will enable row format conversion from BRF format
to RRF format during a REORG TABLESPACE ROWFORMAT RRF utility
on an undefined table space. MSGDSNU1173I will be issued, the
object will be updated to indicate it is in RRF format, and
SYSIBM.SYSTABLEPART FORMAT column will be updated with an
"R" for RRF format.
The conversion from BRF to RRF on DEFINE NO undefined table
spaces will only be done during a REORG of the entire table
space.
Row format conversion from basic row format (BRF) to reordered
row format (RRF) will be done during a REORG TABLESPACE
ROWFORMAT RRF utility run on an undefined object. The utility
will issue DSNU1173I - TABLE SPACE tsname WILL BE CONVERTING
FROM BASIC ROW FORMAT TO REORDERED ROW FORMAT and will end
with RC0. The FORMAT column of SYSTABLEPART will be updated
with the character "R" to indicate the object is in RRF
format
and the object identifier will be updated to RRF format.
If the object is in RRF format prior to the REORG, no
conversion is needed and the utility will issue DSNU185I and
end with RC0. Conversion for undefined objects during a REORG
TABLESPACE utility will only be done on objects in BRF format,
with the ROWFORMAT RRF keyword, and only when the REORG is of
the entire table space. As with REORG for defined objects,
the ROWFORMAT RRF keyword overrides the existing SPRMRRF
setting.
The utility Guide and Reference manual will be updated to
reflect this change.
Effect of utilities on objects that have the DEFINE NO attribute
1 ----------------------------------------------------------------
Note added to REORG TABLESPACE:
REORG TABLESPACE processes the object if ROWFORMAT RRF is
explicitly specified and the specified target is an entire
undefined table space in basic row format. In this case,
DB2 updates the row format definition in the catalog and
directory. No data sets are defined for the table space.
Effects of running REORG TABLESPACE
-----------------------------------
REORG TABLESPACE converts an undefined table space to reordered
row format if both of the following conditions are true:
* ROWFORMAT RRF is explicitly specified
* The specified target is an entire undefined table space in
basic row format.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM99259
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURBUS PM99259
DSNURFIT PM99259
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM99259 DSNURBUS DSNURFIT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURBUS
DSNURFIT
LISTEND
UI17359 COVER LETTER END
UI17369 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12825 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of CASE *
* expression and XMLTABLE function. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC0000003B DSNNQIV +9E02 or *
* ABEND0C4 RC00000010 DSNNQIV +9F40 may *
* occur when passing the output of a *
* CASE expression into the XMLTABLE *
* function. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC3B DSNNQIV OFFSET9E02 or ABEND0C4 RC10 DSNNQIV
OFFSET9F40 may occur when passing the output of a CASE
expression into the XMLTABLE function.
For example,
In the following query, the output of the CASE expression
is passed into the XMLTABLE function.
SELECT T2.C FROM T1,
XMLTABLE('/a/b'
PASSING CASE WHEN V1 > ' '
THEN XMLPARSE(V1)
ELSE XMLPARSE(V2)
END
COLUMNS
C VARCHAR(5) PATH 'c') T2;
When running this query, one of the aforementioned abends may
occur.
DB2 is modified, so the abends will not occur.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12825
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOOS2 PI12825
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12825 DSNXOOS2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOOS2
LISTEND
UI17369 COVER LETTER END
1
UI17371 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07616 -
****************************************************************
* USERS AFFECTED: All DB2 for z/os V11 users *
****************************************************************
* PROBLEM DESCRIPTION: Redo phase of the log apply *
* encountered ABEND04E 00C200AD in *
* DSNICLAP OFFSET2BB0 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend with reason code C200AD occurred during the
REDO log phase when unlatching an index page.
The REDO process is trying to apply a format log record
to an index page. But there is a page size error
between the buffer manager control block and the physical page,
so the format log record was not applied. However, during the
clean up process at exit, a page type was referenced on the
physical page itself. Since the page format log record was not
applied, the wrong information on the physical page was
used. As a result, the C200AD abend was triggered.
DB2 code has been modified to use the buffer manager control
block instead of looking at the page itself.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI07616
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICLAP PI07616
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07616 DSNICLAP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICLAP
LISTEND
UI17371 COVER LETTER END
UI17411 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14870 -
****************************************************************
* USERS AFFECTED: All DB2 V10 and higher *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNY011I message issued followed by *
* ABEND04E RSN00E8005A when attempting to *
* start a V11 DB2 member on LPAR *
* configured with 510T of HVSHARE. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
The message DSNY011I is issued when either there is no HVSHARE
or HVCOMMON defined at IPL or the amount remaining of either of
these is less than needed for the DB2. Researching the dump
found that the field used for testing, RCELVSHRGBYTES, is
actually the HWM for the LPAR and was very close to 510T but the
in-use amount was only a few gigabytes. The field that should
be tested is for current allocation.
The initialization module has been changed to check the amount
of HVSHARE and HVCOMMON which are currently in-use rather than
the high water mark. The only circumvention should you hit this
problem is to apply this apar or IPL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14870
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNYASCP PI14870
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14870 DSNYASCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNYASCP
LISTEND
UI17411 COVER LETTER END
UI17421 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12497 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNB1PPG. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A timing window exists in which DSNB1PPG is negotiating a page
P-lock while another agent is stealing the buffer used by that
page. This results in DSNB1PPG trying to put information into
the P-lock trace table using a zero PB0 pointer, which may
cause an ABEND0C4.
DSNB1PPG has been modified to avoid accessing the PB0 when the
page it is processing has been stolen.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12497
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PPG PI12497
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12497 DSNB1PPG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PPG
LISTEND
UI17421 COVER LETTER END
UI17483 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13733 -
****************************************************************
* USERS AFFECTED: All users who migrate to DB2 10 NFM or *
* to DB2 11 and there is user defined index *
* on the catalog table. *
****************************************************************
* PROBLEM DESCRIPTION: Migration to DB2 10 NFM or DB2 11 *
* could hit ABEND04E RC00E40601 in *
* DSNUTILA DSNUEXDL +14EE *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When there is a user defined index on the catalog table, during
migration, we could have the above abend.
DB2 code has been changed to not block alter index and SQL
insert/update/delete on a catalog table in the same commit
scope if the attribute of the key column is not changed
for the migration.
Additional keyword: DB2MIGV10/K DB2MIGV11/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13733
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDART PI13733
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13733 DSNGDART
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDART
1 LISTEND
UI17483 COVER LETTER END
UI17485 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14298 -
****************************************************************
* USERS AFFECTED: All DB2 users who drop or alter an object *
* which is referenced by a package bound in *
* V10 or above. *
****************************************************************
* PROBLEM DESCRIPTION: When dropping or altering an object *
* which is referenced by a package bound *
* in V10 and above, ABEND04E with *
* RC00C90101 in DSNGEPDL (500F) may *
* occur. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When executing a V10/V11 bound package, an internal counter
is set incorrectly. Dropping or altering an object invalidates
the package which references the object. It is not expected
for the package counter value to be greater than 1, which
results in the above abend.
DB2 code has been changed to tolerate an incorrect count
so that dropping or altering an object can successfully
invalidate the package. A diagnostic dump will be taken
if the counter goes wrong.
Additional keywords: SQLDROP SQLALTER
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14298
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFSP PI14298
DSNGEPDL PI14298
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14298 DSNGEFSP DSNGEPDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFSP
DSNGEPDL
LISTEND
UI17485 COVER LETTER END
UI17488 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI10369 -
****************************************************************
* USERS AFFECTED: All IFCID002 users *
****************************************************************
* PROBLEM DESCRIPTION: The value for stealable pages QISEKLRU *
* can be incorrect. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A monitor display for the EDM SKEL pool entries shows
incorrect values for STEALABLE PAGES (QISEKLRU) field.
For example:
STEALABLE PAGES could be greater than PAGES IN SKEL POOL.
There is a timing window where two concurrent threads could
modify the counter of STEALABLE PAGES at the same time, which
causes the incorrect values for QISEKLRU.
The code has been updated to fix the timing issue which
could cause the incorrect STEALABLE PAGES (QISEKLRU) field.
Additional keywords: IFCID002
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10369
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFBL PI10369
DSNGEFSP PI10369
DSNGERBK PI10369
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10369 DSNGEFBL DSNGEFSP DSNGERBK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFBL
DSNGEFSP
DSNGERBK
LISTEND
UI17488 COVER LETTER END
UI17496 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12332 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS *
* who have very large queries *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at DSNXOPG1 *
* OFFSET1B62 may occur for a query *
1 * on a table in a partitioned table *
* space where a column in the *
* partitioning key is referenced in: *
* 1. Around 32K or more OR predicates; *
* OR *
* 2. An IN-list predicate containing *
* around 32K or more elements *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC00000038 at DSNXOPG1 OFFSET1B62 may occur for a query
on a table in a partitioned table space where a column in the
partitioning key is referenced in:
1. Around 32K or more OR predicates; OR
2. An IN-list predicate containing around 32K or more elements.
The OR predicates can be converted to an IN-list, and a counter
for the number of IN-list items overflowed. Such a query
should receive SQL code -101, but received an abend instead.
For example, take the following query which has over 32K
predicates of the form 'A.C1 = n', for different values of n.
A is in a partitioned table space, and A.C1 is the partitioning
key:
SELECT A.C1, B.C1, B.C2
FROM A, B
WHERE
A.C2 = B.C2 AND
(A.C1 = '00000010' OR
A.C1 = '00000014' OR
A.C1 = '00000016' OR
A.C1 = '00000022' OR
. . .
A.C1 = '09999977');
This query can encounter the abend.
Additional Keywords:
SQLIN SQLOR
Code is updated to avoid the abend described above. Such a
query will now get SQL code -101.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12332
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODML PI12332
DSNXOPCO PI12332
DSNXOPG PI12332
DSNXOPG1 PI12332
DSNXOPRS PI12332
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI12332 DSNXODML DSNXOPCO DSNXOPG DSNXOPG1 DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODML
DSNXOPCO
DSNXOPG
DSNXOPG1
DSNXOPRS
LISTEND
UI17496 COVER LETTER END
UI17533 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10033 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of TEMPLATE specifying *
* NULLFILE for the data set name *
****************************************************************
* PROBLEM DESCRIPTION: A LOAD utility with the input data set *
* defined with a TEMPLATE statement that *
* specified 'NULLFILE' for the data set *
* name abended with an ABEND04E *
* RC00E40070 *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD REPLACE INDDN utility with the input data set defined
with a TEMPLATE statement and specifying 'NULLFILE' as the data
set name, abended with ABEND04E RC00E40070.
The system parameter variable NON_VSAM_XTIOT was set to YES
which allows certain z/OS control blocks to be allocated in
above the line storage. The error occurred while attempting to
check if the input data set had been opened. Because it was a
NULLFILE, certain control blocks did not exist but a code error
attempted to reference them
Code has been modified to handle a TEMPLATE with 'NULLFILE' as
the data set name.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10033
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGSDA PI10033
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10033 DSNUGSDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNUGSDA
LISTEND
UI17533 COVER LETTER END
UI17564 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13794 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: During space reuse processing on a *
* pseudo deleted record (PD-Rec), the *
* page became broken with 0C32 error *
* code. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Improper marking of the PGBROKEN flag on the page during
a PD-Rec space reuse processing, opened up a timing window
that could cause DB2 mark its ID-Map entry as a hole to
be reused but not properly chaining it to the rest of
the holes on the page. This caused the page check to fail
with an error code of 0C32.
Changes made in DB2 to mark the PGBROKEN flag properly, to
close that timing window, so that when turning a PD-Rec into
a hole to be reused it'll be properly chained with other
available spaces on the page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13794
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIREPR PI13794
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13794 DSNIREPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIREPR
LISTEND
UI17564 COVER LETTER END
UI17579 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13427 -
****************************************************************
1 * USERS AFFECTED: All DB2 users of Data Sharing. *
****************************************************************
* PROBLEM DESCRIPTION: LOB TABLE SPACE DEFINED AS NOT LOGGED *
* IS LEFT IN GRECP,LPL STATE AFTER DB2 *
* GROUP RESTART *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DB2 Group restart, all Group Buffer Pool Dependent (GBPD)
objects are added to Group Recover Pending (GRECP) state. This
includes NOT LOGGED LOB space. Since LOB space are NOT LOGGED,
it remained in GRECP,LPL state. Auto-GRECP can make an
enhancement to treat NOT LOGGED LOB table space slightly
different since DB2 always logs changes to system pages and to
auxiliary indexes. Therefore, at the end of auto-GRECP recovery
at the end of restart, these LOB table space will be in AUXW
state instead of GRECP,LPL state. This should allow update or
delete of the LOB objects.
DB2 auto-GRECP recovery logic is modified to mark LOB tablespace
in AUXW state instead of leaving it in GRECP,LPL state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13427
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIAGBR PI13427
DSNIERST PI13427
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13427 DSNIAGBR DSNIERST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIAGBR
DSNIERST
LISTEND
UI17579 COVER LETTER END
UI17597 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16165 -
****************************************************************
* USERS AFFECTED: All DB2 users of RESTORE SYSTEM Utility. *
****************************************************************
* PROBLEM DESCRIPTION: RESTORE SYSTEM Utility ending with RC08 *
* when Fast Log Apply (FLA) is disabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When RESTORE SYSTEM is run with the Fast Log Apply (FLA)
disabled, accessing FLA field may result in a program exception
1 error. This program exception error will invoke Program Recovery
Routine (PRR) which will process this error condition and
terminate the RESTORE SYSTEM utility with RC08. This APAR will
make sure that if FLA is disabled, it will not reference or
access any FLA code logic. This will avoid program exception
errors during log apply phase of RESTORE SYSTEM and premature
termination of RESTORE SYSTEM Utility.
DB2 RESTORE SYSTEM log apply logic is modified to avoid program
exception error when FLA is not used for data recovery.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16165
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRSTR PI16165
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16165 DSNIRSTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRSTR
LISTEND
UI17597 COVER LETTER END
UI17610 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14040 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the DB2 scheduler for *
* administrative tasks. *
****************************************************************
* PROBLEM DESCRIPTION: During Daylight Savings Time, when *
* the z/OS Language Environment variable *
* TZ is set to a time zone with Daylight *
* Savings Time alternative, the DB2 *
* scheduler schedules a task for *
* execution one hour after the time *
* specified in the BEGIN_TIMESTAMP *
* of the task. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
When the DB2 scheduler is started and there is a time zone
defined in the environment variable TZ of the z/OS
Language Environment, the scheduler calculates the current
local time and UTC based on the difference between UTC and
standard time. However, it does not adjust this difference
accordingly if the Daylight Savings Time alternative is also
defined in the environment variable TZ. Therefore, during
1 daylight savings time, the calculated difference between
UTC and local time is off by x seconds, where x is the
difference in seconds between daylight savings time and
standard time.
In response, the scheduler is modified to take daylight
savings time into account when calculating the current
local time or UTC and the Daylight Savings Time
alternative is defined in the environment variable TZ.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14040
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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
* 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.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNA6UTL PI14040
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14040 DSNA6UTL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNA6UTL
LISTEND
UI17610 COVER LETTER END
UI17622 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15176 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of multi-column frequency *
* or multi-column histogram statistics. *
****************************************************************
* PROBLEM DESCRIPTION: When multi-column frequency or *
* histogram statistics exist for a table *
* referenced more than once in a query, *
* DB2 may neglect to read in these *
* multi-column frequency or histogram *
* statistics at bind/prepare. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may neglect to use multi-column frequency or histogram
statistics if both of the following conditions are satisfied.
* Single column frequencies do not exist on the leading column
of the multi-column frequency column group
OR
Single column histograms do not exist on the leading column
of the multi-column histogram column group.
* The table with these statistics is referenced more than once
in the query.
When this problem occurs, DB2 may select an inefficient access
path which could lead to poor query performance.
Additional Keywords:
SQLPERFORMANCE SQLACCESSPATH SQLSTATS
DB2 has been modified to avoid ignoring the multi-column
statistics in the described scenario.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15176
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCN PI15176
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15176 DSNXOCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCN
LISTEND
UI17622 COVER LETTER END
UI17630 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14181 -
****************************************************************
* USERS AFFECTED: Users of PBG (Partitioned By Growth) table *
* spaces in the WORKFILE data base. *
****************************************************************
* PROBLEM DESCRIPTION: Wrong partition number was specified in *
* RESOURCE UNAVAILABLE REASON=00C9009C *
* message from module DSNITLPE when it *
* could not allocate a segment. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. DSNITLPE could not allocate a segment in existing partitions
and it found that a new partition could not be added because
the MaxPartitions limit was already reached. When it issued
the error message, it incorrectly specified the number of the
partition that it tried to add, instead of the number of the
last existing partition where it could not allocate a
segment.
2. When a segment could not be allocated in a particular
partition of a PBG table space for some reason, the space
management code marked the whole table space as unavailable,
without knowing the status of other possible partitions in
1 the same table space.
DSNITLPE has been corrected to use the correct partition
number when it issues the resource-unavailable message.
The space-management code has been corrected to not mark the
whole table space as unavailable when space cannot be
allocated in a single partition of a PBG table space in the
WORKFILE data base.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14181
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISEGF PI14181
DSNITLPE PI14181
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14181 DSNISEGF DSNITLPE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISEGF
DSNITLPE
LISTEND
UI17630 COVER LETTER END
UI17632 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14208 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of compressed *
* Partition by Growth table space. *
****************************************************************
* PROBLEM DESCRIPTION: ABND=04E-00E3000D, DSNPXTN0+35AC, LOAD *
* fails with error message DSNU017I, *
* REASON=X'00E7000A'. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A LOAD into a compressed PBG tablespace caused a new partition
to be created. The primary allocation was small, causing
secondary allocation, while the dictionary was being copied
from the previous partition to the current partition.
The 00E3000D abend happened due to the DSM (Data Space manager)
module's attempt to set up an ESTAE with an FRR (Functional
Recovery Routine) already active on the stack.
In this case the FRR was already set up by a module
in DSM's calling chain.
Code has been corrected to avoid the situation when an FRR would
already be active when DSM tries to establish an ESTAE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14208
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIZLDL PI14208
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14208 DSNIZLDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIZLDL
LISTEND
UI17632 COVER LETTER END
UI17638 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM96957 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users desiring a different *
* global default filter factor. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 determines a default filter factor *
* based on the cardinality of the column. *
* In many cases (especially for range *
* predicates), this default filter factor *
* is not an adequate representation of *
* the filtering that occurs at runtime. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 determines a default filter factor based on the cardinality
of the column. In many cases (especially for range predicates),
this default filter factor is not an adequate representation of
the filtering that occurs at runtime.
This APAR provides an interface for users to supply more
accurate default filter factor estimates. Contact IBM support
for guidance on using this interface.
Additional Keywords:
DFLTFFOVERRIDE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM96957
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIEPL PM96957
DSNXODF PM96957
1 DSNXODFB PM96957
DSNXODFE PM96957
DSNXODFT PM96957
DSNXOD0P PM96957
DSNXOD3 PM96957
DSNXOOVR PM96957
HDBAA10J PM96957
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM96957 DSNXIEPL DSNXODF DSNXODFB DSNXODFE DSNXODFT DSNXOD0P
DSNXOD3 DSNXOOVR HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIEPL
DSNXODF
DSNXODFB
DSNXODFE
DSNXODFT
DSNXOD0P
DSNXOD3
DSNXOOVR
LISTEND
UI17638 COVER LETTER END
UI17640 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14188 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 and 11 for z/OS users of XML. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 does not respond to user's request *
* for canceling a long running XML query *
* that contains XPath with wild-card and *
* function call. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The XPath in the following query contains //* and local-name
function call.
SELECT XMLQUERY('//*[local-name(.)="xyz"]' PASSING X1) FROM
T1;
This query might run for a long time when the XML document is
very big. When a user tries to cancel it, DB2 has no response
because the XML query processing module does not check for a
user's cancel request.
DB2 is modified to check for the user's cancel request in the
XML query processing, so the user can cancel the long running
XML query.
Additional Keyword: XMLALL
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI14188
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNQSCN PI14188
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14188 DSNNQSCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNQSCN
LISTEND
UI17640 COVER LETTER END
UI17678 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10167 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who use *
* IBM DB2 Analytics Accelerator that will *
* use the new MEDIAN function. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR provides the new function *
* MEDIAN for execution only on an *
* accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the new function MEDIAN for execution only on
an accelerator.
For a static SQL query that will use the new function above,
BIND the package for the query after applying the PTF.
Keywords
IDAAV3R1/K IDAAV4R1/K SQLMEDIAN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10167
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 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.
DB2BIND:
***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.
DB2BIND:
***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.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DOCUMENTATION:
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.
1
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';
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).
1 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).
ACTION:
***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.
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFA PI10167
DSNXOBF3 PI10167
DSNXODML PI10167
DSNXODTR PI10167
DSNXOD1 PI10167
DSNXOEX1 PI10167
DSNXOFN2 PI10167
DSNXOIN PI10167
DSNXOLTD PI10167
DSNXONZA PI10167
DSNXONZO PI10167
DSNXONZQ PI10167
DSNXOOS1 PI10167
DSNXORFN PI10167
DSNXOVD PI10167
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10167 DSNXOBFA DSNXOBF3 DSNXODML DSNXODTR DSNXOD1 DSNXOEX1
DSNXOFN2 DSNXOIN DSNXOLTD DSNXONZA DSNXONZO DSNXONZQ
DSNXOOS1 DSNXORFN DSNXOVD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXOBFA
DSNXOBF3
DSNXODML
DSNXODTR
DSNXOD1
DSNXOEX1
DSNXOFN2
DSNXOIN
DSNXOLTD
DSNXONZA
DSNXONZO
DSNXONZQ
DSNXOOS1
DSNXORFN
DSNXOVD
LISTEND
UI17678 COVER LETTER END
UI17692 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11170 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the LOAD utility *
****************************************************************
* PROBLEM DESCRIPTION: Restart of a LOAD RESUME YES LOG NO *
* utility with partition parallelism *
* after ABEND04E RC00E40323 due to *
* DISCARD limit reached, resulted in no *
* COPY PENDING set on the loaded *
* partition(s) *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a LOAD RESUME YES LOG NO DISCARDS 1 INTO TABLE PART
INDDN with partition parallelism. The LOAD job abended with
ABEND04E RC00E40323 due to DISCARD limit being reached. When the
LOAD was restarted with DISCARD 0, it completed with RC4 but
did not set COPYP against the loaded partition(s).
The problem occurred because a local flag was not set properly.
A similar problem exists for a restart of a LOAD LOG NO
COPYDICTIONARY with at least two INTO TABLE PART INDDN REPLACE
statements and one INDDN is a DUMMY data set.
The problem can also occur with LOAD PARALLEL in DB2 11.
The LOAD utility code was modified to correct the
aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11170
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURBDN PI11170
DSNURPDC PI11170
DSNURSLD PI11170
DSNURWBF PI11170
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11170 DSNURBDN DSNURPDC DSNURSLD DSNURWBF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURBDN
DSNURPDC
DSNURSLD
DSNURWBF
LISTEND
UI17692 COVER LETTER END
UI17694 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09650 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY, REORG, LOAD, REBUILD INDEX *
* utility with FCCOPYDDN specified or RECOVER *
* from a FlashCopy image copy. *
****************************************************************
* PROBLEM DESCRIPTION: FlashCopy failed with DFSMSdss message *
* ADR707E when user did not have the *
* correct RACF authority, but the utility *
* job ended with RC0 instead of RC8 and a *
* record was inserted into SYSIBM.SYSCOPY *
* indicating a successful FlashCopy had *
* been made when it had not. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a COPY, REORG, LOAD, REBUILD INDEX utility with
FCCOPYDDN specified or RECOVER from a FlashCopy image copy when
user did not have the correct RACF authority. The utility job
ended with RC0 instead of RC8 and a record was inserted into
SYSIBM.SYSCOPY indicating a successful FlashCopy had been made,
however the FlashCopy data set was not created.
In the case of COPY utility with COPYDDN and FCCOPYDDN
specified, ABEND04E RC00E40347 was received because no
FlashCopy data set was available from which to make a
sequential copy.
The problem occurred because the utility failed to handle the
1 error message MSGADR707E from DFSMSdss when the user did not
have the correct RACF authority.
DB2 code has been modified to handle message ADR707E and RC8
from DFDSS when FlashCopy is requested for COPY, REORG, LOAD
, REBUILD INDEX or RECOVER utilities.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09650
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGFUM PI09650
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09650 DSNUGFUM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGFUM
LISTEND
UI17694 COVER LETTER END
UI17698 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI08413 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS utility users of REORG *
* TABLESPACE to materialize an ALTER INLINE *
* LOB LENGTH Schema change *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE to materialize an *
* ALTER INLINE LOB LENGTH results in *
* parallel subtasks abending with either *
* RC00C200A2 at DSNB1GET +'45F2' or *
* RC00C90101 at DSNONLLE:5063 *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REORG of a Partition By Range ( PBR ) table space was run to
materialize an ALTER INLINE LOB LENGTH. During parallel reload,
the subtasks abended with either ABEND04E RC00C200A2 at DSNB1GET
OFFSET45F2 or ABEND04E RC00C90101 at DSNONLLE ERQUAL5063 and the
utility abends with an ABEND04E RC00E40347.
The problem occurred because each of the subtasks were using
the same internal control block to process the LOB column for
its partition. Each subtask needs to have their own internal
control block for LOB processing.
An ABENDS0C4 RC11 from DSNB1RTR +x'039C' has also been seen for
this problem.
1 Additional Keywords: ABEND0C4 OFFSET039C
Code has been changed to allocate a separate control block for
each subtask to process the inline LOB column(s) for its
partition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI08413
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUECMI PI08413
DSNUGUCA PI08413
DSNURLAP PI08413
DSNURLBI PI08413
DSNURPUI PI08413
DSNURWBF PI08413
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI08413 DSNUECMI DSNUGUCA DSNURLAP DSNURLBI DSNURPUI DSNURWBF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECMI
DSNUGUCA
DSNURLAP
DSNURLBI
DSNURPUI
DSNURWBF
LISTEND
UI17698 COVER LETTER END
UI17701 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14883 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RUNSTATS INDEX SHRLEVEL REFERENCE *
* utility *
****************************************************************
* PROBLEM DESCRIPTION: RUNSTATS INDEX SHRLEVEL REFERENCE *
* UPDATE ALL on SYSIBM.DSNTNX01 results *
* in DSNT501I - RESOURCE UNAVAILABLE and *
* DSNT500I - RESOURCE UNAVAILABLE REASON *
* '00C90083' and abends with ABEND04E *
* RC00E40213 *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
Customer ran a RUNSTATS INDEX SHRLEVEL REFERENCE UPDATE ALL
against index SYSIBM.DSNTNX01 which is defined on table
SYSIBM.SYSCOLDIST. RUNSTATS failed with ABEND04E RC00E40213
CAUSE 00C90083 and issued messages MSGDSNT501I - RESOURCE
1 UNAVAILABLE and message MSGDSNT501I - RESOURCE UNAVAILABLE on
DSNDB06.DSNTNX01 when trying to insert a row into
SYSIBM.SYSCOLDIST.
This problem happened because the RUNSTATS incorrectly
flagged SYSIBM.DSNTNX01 as non-target object.
Additional Keywords: RC00C90083
RUNSTATS utility code has been modified to correct the
aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14883
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSSRI PI14883
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14883 DSNUSSRI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSSRI
LISTEND
UI17701 COVER LETTER END
UI17716 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12607 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* using a Java IBM Data Server Client Driver *
* application to call a stored procedure on *
* DB2 10 and 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: After a DB2 for z/OS database server is *
* migrated to Version 10, an application *
* using the Java IBM Data Server Client *
* Driver calls a stored procedure on the *
* migrated server. The CALL fails with *
* the java.lang.ClassCastException error, *
* indicating the conversion between the *
* parameter type in the stored procedure *
* declaration and the argument type *
* specified in the application's CALL *
* statement is not supported by the *
* driver. The Java application did not *
* encounter this error before the DB2 *
* server was migrated to V10. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
DB2 10 for z/OS implemented enhancements to the way in which
stored procedure parameters are returned to the calling
application at the remote requester.
- Before Version 10, DB2 returned stored procedure parameters
according to the type of the corresponding arguments in
the stored procedure CALL.
- Beginning in Version 10, DB2 returns stored procedure
parameters according to the SQL type of the parameter as
defined in the stored procedure declaration.
This change improves performance for the call by eliminating
server conversions of the parameter data; implements the same
behavior as used by DB2 for returning other outputs, such as
cursor or singleton select data; and is the same behavior as is
implemented on other servers in the DB2 Family.
.
However, this change in DB2 server behavior may cause some
applications using Java IBM Data Server Client Driver to fail
with the java.lang.ClassCastException error, if they do not
specify argument types that are compatible with the declared
type of the corresponding parameter in the stored procedure.
The required corrective action is to change the Java
application to use the compatible argument types.
To fix the ClassCastException error, problematic application
CALL statements should be changed to specify argument types that
are compatible with the declared type of the corresponding
parameter in the stored procedure (as described above).
However, until all necessary application changes can be
deployed, new support is added to allow problematic application
to function relative to prior DB2 behavior.
.
This PTF provides a new option, SP_PARMS_JV, for the
DDF_COMPATIBILITY ZPARM. The new ZPARM option allows the DB2
server to return stored procedure parameters according to the
types of the arguments specified in the CALL statement (pre-V10
behavior) when an application is using a Java IBM Data Server
Client Driver.
.
For DB2 11 for z/OS, this PTF does not recognize SP_PARMS_JV for
DDF_COMPATIBILITY ZPARM when the CURRENT APPLICATION
COMPATIBILITY level is equal or greater than V11R1. The
SP_PARMS_JV value is recognized when the CURRENT APPLICATION
COMPATIBILITY level is equal to V10R1 at DB2 11 for z/OS.
.
The existing value 8 for QW0366FN field of IFCID 366 trace can
be used to indicate that DB2 server returns data matching the
data types of the corresponding CALL statement when
DDF_COMPATIBILITY ZPARM is set to SP_PARMS_JV.
.
Please refer to ++HOLD document for more information.
.
Please note, this problem can be addressed by applying the fix
from Java IBM Data Server Client Driver in DB2 Version 9.7 Fix
Pack 6 for Linux, UNIX, and Windows. Please refer to APAR
IC80974 for details.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12607
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
===>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.
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.
1
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
----------------------------------------------------------------
==> 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 <x>
1
or this format:
DDF_COMPATIBILITY STR M <x>
to the format below. If no entry for DDF_COMPATIBILITY is
present, add one that is in the format below:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M NULL
Change <x> 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 <x> 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 <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWPZ PI12607
DSNDQW05 PI12607
DSNLZD00 PI12607
DSNWZIFA PI12607
DSN6FAC PI12607
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12607 DSNDQWPZ DSNDQW05 DSNLZD00 DSNWZIFA DSN6FAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLZD00
DSNWZIFA
1 MACROS
DSNDQWPZ
DSNDQW05
DSN6FAC
LISTEND
UI17716 COVER LETTER END
UI17762 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13361 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2 *
* 11 for z/OS users of DSN1COPY utility *
****************************************************************
* PROBLEM DESCRIPTION: (1) In DB2 9, after using DSN1COPY to *
* restore a full image copy to a *
* multi-piece non-partitioned index *
* (NPI), which is defined as COMPRESS *
* YES, RUNSTATS utility against the index *
* space failed with ABEND04E RC00C90101 *
* at DSNKBULD EQUAL2003 *
* *
* (2) In DB2 10 and DB2 11, MSGDSN1992I *
* or MSGDSN1961I is issued during *
* DSN1COPY utility restoring a COMPRESS *
* YES index space from a full image copy *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
In DB2 9, user used DSN1COPY with PIECESIZ(4G) to copy a full
image copy to a multi-piece NPI, which is defined as COMPRESS
YES. The DSN1COPY ended with RC0, but when the index space was
accessed later by a RUNSTATS utility, ABEND04E RC00C90101 at
DSNKBULD:2003 was issued.
The reason for this error was that DSN1COPY set the maximum
page number of the output data set incorrectly. It caused some
pages, which should have been inserted into piece 1, to be
copied into piece 2.
In DB2 10 and DB2 11,
(1)When using DSN1COPY with PIECESIZ(4G) to restore a
multi-piece COMPRESS YES NPI from a full image copy, the
DSN1COPY job terminated RC08 with message DSN1992I - VSAM PUT
ERROR, RPLERREG=008, RPLERRCD=028.
(2)When using DSN1COPY with DSSIZE(4G) or LARGE parameter to
restore a full image copy of a partitioned index, which was
defined as COMPRESS YES, message DSN1961I - PIECE NUMBER xxxx
IS INVALID was issued.
DSN1COPY is modified to correct the aforementioned problems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13361
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN1COPY PI13361
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13361 DSN1COPY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN1COPY
LISTEND
UI17762 COVER LETTER END
UI17834 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14111 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REBUILD INDEX and RECOVER *
* of objects in Read or Replication Only *
* (RREPL) status *
****************************************************************
* PROBLEM DESCRIPTION: REBUILD INDEX and RECOVER utilities on *
* objects in RREPL ( Read or Replication *
* Only ) status issues DSNU590I and ends *
* with RC8. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REBUILD INDEX and RECOVER utilities run on objects that are in
RREPL status result in MSGDSNU590I - RESOURCE NOT AVAILABLE,
REASON=X'00C90224', ON database.object PROHIBITS PROCESSING and
the utility ends with RC8.
Both utilities should be allowed to operate on objects that are
in RREPL status.
Additional Keyword: RC00C90224
Code has been changed to allow REBUILD INDEX and RECOVER to
operate on objects in RREPL status.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14111
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBCTD PI14111
DSNIDBET PI14111
DSNUGDTC PI14111
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14111 DSNIBCTD DSNIDBET DSNUGDTC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBCTD
DSNIDBET
DSNUGDTC
LISTEND
UI17834 COVER LETTER END
UI17851 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16686 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* datetime arithmetic. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -183 may be incorrectly *
* returned when adding seconds or *
* minutes duration to a timestamp. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When adding seconds or minutes duration to a timestamp,
SQLCODE -183 may be incorrectly returned instead of a valid
timestamp.
The following queries are examples that can cause SQLCODE -183
to be incorrectly returned:
SELECT TIMESTAMP('0001-01-01-00.00.00') + 5258964900 MINUTES
FROM SYSIBM.SYSDUMMY1;
SELECT TIMESTAMP('0001-01-01-00.00.00') + 315537894000 SECONDS
FROM SYSIBM.SYSDUMMY1;
The correct result is: 9999-12-31-23.00.00.000000
The DB2 code was modified so the correct result is returned
when adding seconds or minutes duration to a timestamp.
Additional Keywords: SQLTIMESTAMP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16686
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM41805:
See PM41805 APAR/PTF text for additional information about
why further ACTION might be necessary.
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDTF PI16686
DSNXRDT9 PI16686
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16686 DSNXRDTF DSNXRDT9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDTF
DSNXRDT9
1 LISTEND
UI17851 COVER LETTER END
UI17859 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12599 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 Z/OS users of *
* IFC 306 with compressed data. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C20305 can occur at *
* location DSNIOPNP OFFSET3BF0 when *
* Altering the table to add partitions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 didn't properly serialize the operation between a IFC306
thread and a thread that was Altering the table to add
additional partitions. This caused inconsistency between some
internal DB2 control blocks on the object. As a result,
when DB2 tried to open a new partition of the object, some
control blocks indicated the partition didn't exist and
DB2 abend with RC00C20305.
Fixes made in DB2 to properly serialize the operation between
a IFC306 thread and the thread Altering the table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12599
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBCTD PI12599
DSNIFPSC PI12599
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12599 DSNIBCTD DSNIFPSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBCTD
DSNIFPSC
LISTEND
UI17859 COVER LETTER END
UI17861 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10550 -
****************************************************************
* USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users *
* of SLIP zero address detection (ZAD). *
****************************************************************
1 * PROBLEM DESCRIPTION: ZAD report may detect an uninitialized *
* base register value in DBET module *
* DSNIBCTD. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ZAD report may detect an uninitialized base register value in
the DBET module DSNIBCTD, which may lead to unexpected results.
DBET paths which determine whether a resource
can be allocated have been modified to initialize
internal base registers which were uninitialized.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10550
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CLM PI10550
DSNB1DRA PI10550
DSNB1LCM PI10550
DSNB1POC PI10550
DSNIBCTD PI10550
DSNICLDR PI10550
DSNICUBC PI10550
DSNIDBCB PI10550
DSNISDLE PI10550
DSNIXMDE PI10550
DSNOLMDE PI10550
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10550 DSNB1CLM DSNB1DRA DSNB1LCM DSNB1POC DSNIBCTD DSNICLDR
DSNICUBC DSNIDBCB DSNISDLE DSNIXMDE DSNOLMDE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CLM
DSNB1DRA
DSNB1LCM
DSNB1POC
DSNIBCTD
DSNICLDR
DSNICUBC
DSNIDBCB
DSNISDLE
DSNIXMDE
DSNOLMDE
LISTEND
UI17861 COVER LETTER END
UI17875 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM96493 -
1 ****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2 *
* 11 for z/OS utility users of LOAD INTO TABLE *
* PART INDDN DISCARDDN *
****************************************************************
* PROBLEM DESCRIPTION: LOAD INTO TABLE PART INDDN DISCARDDDN *
* utilizing a different discard data set *
* for each partition places a wrong *
* row in the wrong discard data set *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD INTO TABLE INDDN DISCARDDN, utilizing partition parallel
LOAD, and specifying a different discard data set for each
partition, uses only a single discard data set and some of the
rows placed in that data set are incorrect.
This error occurs with a unique non-partitioned index ( NPI )
and only when the duplicate keys are in different partition(s).
The error occurs because discard processing presumes the
duplicate keys are all in the same partition and uses that
discard data set to report the rows in error. For example, if
there were 3 duplicate keys,
row 1 from partition 1
row 20 from partition 3
row 30 from partition 4
all 3 would be placed in the discard data set for partition 1.
However, the rows placed in that data set would not be correct
for partitions 3 and 4. They would actually be rows 20 and 30
from the input data set for partition 1. This is because
processing would only be looking at the input data set for
partition 1 to find the row to place in the discard data set.
It should be noted that although the discard data set contains
some wrong rows, the correct duplicate rows were deleted from
the table so there is no data integrity problem.
LOAD code has been changed to place the correct row into the
discard data set for the partition in which the LOAD was
attempted.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM96493
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURDNP PM96493
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM96493 DSNURDNP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNURDNP
LISTEND
UI17875 COVER LETTER END
UI17902 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12714 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of DB2 Web *
* Services Consumer functions. *
****************************************************************
* PROBLEM DESCRIPTION: The SOAP message is not returned when *
* the DB2 SOAPHTTP UDF receives a non-200 *
* HTTP status code. The application can *
* not handle the SOAP error *
* programmatically. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently, when the DB2 SOAPHTTP UDF received a non-200 HTTP
status code, the DB2 SOAPHTTP UDF returns SQLCODE -443 with a
generic error message. The SOAP error message from the server
is lost.
A new ENVAR option "RETURN_ERROR=YES" is added to the DB2
SOAPHTTP UDF. When the option is specified, the DB2 SOAPHTTP
UDF will package the SOAP message in an error element and return
it. The SQLCODE -443 will not be issued. The application can
look at the SOAP message and handle the error.
Additional Keywords: SQLCODE443 SQLXML SQLUDF SOAPHTTPNC
SOAPHTTPNV
The ENVAR option "RETURN_ERROR=YES" is implemented.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12714
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
<error httprc="{HTTP status code}">
{SOAP message}
</error>
1 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")'
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWSCCC PI12714
DSNWSCCV PI12714
DSNWSCVC PI12714
DSNWSCVV PI12714
DSNWSHLP PI12714
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12714 DSNWSCCC DSNWSCCV DSNWSCVC DSNWSCVV DSNWSHLP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWSCCC
DSNWSCCV
DSNWSCVC
DSNWSCVV
DSNWSHLP
LISTEND
UI17902 COVER LETTER END
UI17904 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM74574 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE utility *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability. *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
Serviceability.
Serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM74574
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
immediately upon job submission, while it will not take effect
in the DB2 DBM1 address space until DB2 is stopped and started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURBXA PM74574
DSNURBXD PM74574
DSNURBXE PM74574
DSNURFIT PM74574
DSNURKAC PM74574
DSNURORG PM74574
DSNURPCT PM74574
DSNURPRD PM74574
DSNURPTB PM74574
DSNURPUI PM74574
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM74574 DSNURBXA DSNURBXD DSNURBXE DSNURFIT DSNURKAC DSNURORG
DSNURPCT DSNURPRD DSNURPTB DSNURPUI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURBXA
DSNURBXD
DSNURBXE
DSNURFIT
DSNURKAC
DSNURORG
DSNURPCT
DSNURPRD
DSNURPTB
DSNURPUI
LISTEND
UI17904 COVER LETTER END
UI17906 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16022 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
1 * who use the JDBC Type 2 driver *
* implementation on z/OS and have nested *
* non-Java stored procedures or UDFs. *
****************************************************************
* PROBLEM DESCRIPTION: Users encounter sqlcode -804 on *
* DESCRIBE PROCEDURE issued within a *
* stored procedure or UDF. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The SQLCODE -804 is issued incorrectly when the routine which
executes DESCRIBE PROCEDURE is non-java and the calling
application or routine uses the JDBC Type 2 driver
implementation on z/OS (T2/z). A control block field which
indicates that the caller uses T2/z was inadvertently
inherited by the called routine. This caused DB2 to take an
incorrect code path resulting in the -804.
DB2 code is modified to re-initialize the T2/z indicator for
nested routines.
Additional Keywords: SQLCODE804 JCCT2ZOS
SQLTRIGGER SQLSP SQLSTOREDPROC SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16022
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXESTS PI16022
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16022 DSNXESTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXESTS
LISTEND
UI17906 COVER LETTER END
UI17926 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13075 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the UNLOAD TABLESPACE FROMCOPY *
* utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C7 DSNUULVA OFFSET5E64 during an *
* UNLOAD TABLESPACE FROMCOPY utility *
* specifying a copy made prior to an *
* ALTER TABLESPACE DSSIZE for a *
* partitioned table space. *
1 ****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A full image copy was taken of a partitioned table space
followed by an ALTER TABLESPACE DSSIZE 64G. A subsequent UNLOAD
TABLESPACE FROMCOPY was run, specifying the copy taken prior
to the ALTER. The UNLOAD utility abended with an ABEND0C7
DSNUULVA + x'5E64'. The abend occurred because UNLOAD
calculated an incorrect partition number based on the current
DSSIZE instead of the characteristics of the object at the
time the copy was taken.
This problem can occur for any change in DSSIZE that affects
the internal calculation of the partition number.
UNLOAD code has been modified to check for a change in the
DSSIZE when unloading FROMCOPY.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13075
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULCB PI13075
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13075 DSNUULCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULCB
LISTEND
UI17926 COVER LETTER END
UI17940 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14090 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users whose query *
* contains a predicate or predicates with *
* implicit CAST inside an OR predicate. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may add CAST to a predicate or *
* predicates inside an OR predicate, *
* which might block the range list *
* access path. *
* This may result in poor query *
* performance. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may miss using a range list access path when DB2 adds
an implicit CAST to a predicate or predicates inside an OR
1 predicate when the column data type is not compatible with
the literal data type.
This may result in poor query performance.
ADDITIONAL KEYWORDS:
SQLACCESSPATH SQLPERFORMANCE SQLOR
RANGELIST SQLRANGELIST
The problems mentioned above are fixed so that DB2 will consider
range list access when DB2 adds an implicit CAST to a predicate
or predicates inside an OR predicate.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14090
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM71904:
See PM71904 APAR/PTF text for additional information about
why a REBIND is necessary.
PM71904 corrects a problem of poor query performance for a
query with a predicate or predicates on a timestamp column
inside an OR predicate.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM71471:
See PM71471 APAR/PTF text for additional information about
why a REBIND is necessary.
PM71471 corrects a predicate localization problem when there
is an EXISTS subquery in the CASE expression of the select
list.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM69713 corrects a problem where incorrect output can occur
on a query if there are:
1. two or more predicates with IN-lists on the same column;
2. the predicates are involved in compound OR predicates; and
3. the OR predicates involve columns from more than one table.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
1 affected by this change.
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPPD PI14090
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14090 DSNXOPPD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPPD
LISTEND
UI17940 COVER LETTER END
UI17992 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16300 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users who run a *
* REBIND PLAN(*) command *
****************************************************************
* PROBLEM DESCRIPTION: REBIND PLAN(*) terminated prematurely *
* with MSGDSNT238I or MSGDSNX200I when *
* it should continue rebinding the rest *
* of the plans. Other error messages are *
* possible. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
REBIND PLAN(*) terminated prematurely with MSGDSNT238I or
MSGDSNX200I when it should continue rebinding the rest of the
plans. Other error messages are possible. This happens when some
qualified plans were bound before DB2 V10 directly from DBRMs.
The root cause for the unexpected termination of REBIND PLAN is
one internal function code is set incorrectly.
Additional keywords:
MSGDSNT238I MSGDSNX200I
1 DB2 code has been changed so that the internal function code is
set correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16300
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBRB PI16300
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16300 DSNTBRB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBRB
LISTEND
UI17992 COVER LETTER END
UI18020 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14460 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS who *
* have very large queries *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 in DSNXOPG2 M111 *
* can occur for a query on a table in a *
* partitioned tablespace where a column *
* in the partitioning key is referenced *
* in approximately 32K or more OR *
* predicates or IN-list items *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 in DSNXOPG2 M111 can occur for a query
on a table in a partitioned tablespace where a column in
the partitioning key is referenced in approximately 32K or
more OR predicates or IN-list items.
A counter in DSNXOPG2 for the number of IN-list items
overflowed, and caused a storage overlay. The storage
overlay could cause DB2 to come down, depending on what
storage gets overlaid. Other unpredictable abends
could also occur depending on the type of storage that
gets overlaid.
Such a query should receive SQL code -101 instead of abending.
Additional Keywords:
SQLIN SQLOR SQLSTORAGE DB2OVRLAY/K
Code is modified to avoid the described abend. SQL code -101
1 is issued instead of the abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14460
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***Action for PM97589:
See PM97589 APAR/PTF text for additional information about
why a REBIND is necessary.
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.
DB2BIND:
***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.
DB2BIND:
***Action for PM94767:
See PM94767 APAR/PTF text for additional information about
why a REBIND is necessary.
1 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.
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
1
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.
DB2BIND:
***Action for PM89036:
See PM89036 APAR/PTF text for additional information about
why a REBIND is necessary.
PM89036 corrects a problem of SQL performance for a user
whose queries contain join predicates with histogram
statistics on both of the join columns.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***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
1 affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PM81295:
See PM81295 APAR/PTF text for additional information about
why a REBIND is necessary.
PM81295 corrects a problem of poor query performance for a
query containing OR predicates that map to a single index.
The poor performance can occur when a range-list index access
plan may not be assigned the lowest cost of any plan it beats.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***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
1 affected by this change.
DB2BIND:
***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
affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PM78070:
See PM78070 APAR/PTF text for additional information about
why a REBIND is necessary.
PM78070 corrects a problem of incorrect output that can happen
for a query which contains UNION, EXCEPT, EXCEPT ALL or
ORDER BY and whose top query block has exactly one table.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM75364:
See PM75364 APAR/PTF text for additional information about
why a REBIND is necessary.
PM75364 corrects a problem of inaccurate filter factor estimate
of an IS NOT DISTINCT FROM predicate that may result in an
inefficient access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
***Action for PM74152:
A rebind is necessary for static applications to rebuild
1 internal structures used at runtime based on the changes in
this APAR.
PM74152 corrects a problem in which DB2 may incorrectly return
no rows for a query using page range access where a range
predicate exists on a partitioning column defined as CHAR(1).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***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.
DB2BIND:
***Action for PM70949:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM70949 corrects a problem in which a tablespace scan access
path may be incorrectly chosen when using an internal
serviceability feature to influence access path selection
with ACCESS_TYPE='INLIST'.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
1 affected by this change.
DB2BIND:
***Action for PM69949:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM69949 corrects a problem in which DB2 may choose a highly
selective or index-only DPSI without page range when a more
efficient non-DPSI index exists.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM69139:
See PM69139 APAR/PTF text for additional information about
why a REBIND is necessary.
PM69139 corrects a problem of inaccurate compound filter
factor of two range predicates on the same column that may
result in an inefficient access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***Action for PM67292:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM67292 corrects a problem that DB2 may improperly favor range
list index scan over multiple index access.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
1 DB2BIND:
***Action for PM66948:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM66948 corrects a problem of inaccurate filter factor
estimation for a predicate if the predicate references a
nullable column on which histogram statistics exist.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PM64871:
See PM64871 APAR/PTF text for additional information about
why a REBIND is necessary.
PM64871 corrects a problem of inaccurate filter factor
estimation of an IN-subquery predicate that may result in
an inefficient access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM64315:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM64315 corrects a problem in which the filter factor for a
compound predicate containing an OR predicate could be
overestimated. The incorrect compound filter factor could
result in an inefficient access path and resulting poor query
performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
1 letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM62712:
See PM62712 APAR/PTF text for additional information about
why a REBIND is necessary.
PM62712 corrects a problem of choosing an inefficient range-list
access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM61658:
See PM61658 APAR/PTF text for additional information about
why a REBIND is necessary.
PM61658 corrects a problem of over-estimated correlated
subquery cardinality when global query optimization
is enabled (OPTXQB=ON) and there are materialized views
involved in the join between the parent query block and the
correlated subquery. This may result in an inefficient access
path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM61011:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM61011 corrects a problem in which DB2 incorrectly chooses
to sort instead of using reverse index scan to avoid the sort
when OPTIMIZE FOR 1 ROW is specified.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM59585:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM59585 corrects a problem in which an inefficient access path
is selected when multiple highly selective indexes exist that
can provide the same matching coverage.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM56435:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM56435 corrects a problem in which DB2 could compute an
incorrect compound filter factor. This could lead to an
inefficient access path and poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***Action for PM55976:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM55976 corrects a problem in which the most appropriate index
only access may not be selected.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM55479:
See PM55479 APAR/PTF text for additional information about
why a REBIND is necessary.
PM55479 corrects a problem that DB2 incorrectly handles the
length of histogram statistics of a DECIMAL column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***Action for PM52549:
See PM52549 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52549 corrects a problem of SQLCODE=-510 when doing a
BIND/REBIND on a FOR UPDATE cursor and IN-list direct table
access is attempted.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM52548:
See PM52548 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52548 fixes an abend 0C4 RC00000038 DSNISPBM + 1A64 that can
occur during query execution for queries containing IS NULL
or LIKE predicates.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***Action for PM50516:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM50516 corrects a problem in which an incorrect compound
filter factor is computed when there is data skew and that
data skew is represented by frequency statistics.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM49539 corrects an ABEND 0CF when incorrect internal values may
be used to recalculate the filter factor of the related RANGE or
BETWEEN predicates at execution time. The incorrect internal
values may be saved by DB2 at BIND/PREPARE time if the
package is bound with REOPT(AUTO), and one or more queries
in the package contain RANGE or BETWEEN predicate(s).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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
1 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.
DB2BIND:
***Action for PM44942:
See PM44942 APAR/PTF text for additional information about
why a REBIND is necessary.
PM44942 corrects a problem of a poorly performing access path
caused by incorrect filter factor estimation for a compound
predicate when frequency or histogram statistics exist, or
column cardinality is 1 or 2.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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
affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PM38082:
See PM38082 APAR/PTF text for additional information about
why a REBIND is necessary.
PM38082 corrects a query performance problem involving
1 significant loss of page range screening for queries with
multi-column partitioning keys and predicates with host
variables or parameter markers on those columns.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM37547:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM37547 corrects a problem in which DB2 may calculate an
incorrect filter factor for an after join predicate on a
column defined as NOT NULL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM36392:
See PM36392 APAR/PTF text for additional information about
why a REBIND is necessary.
PM36392 corrects a problem that the filter factor of an equal
predicate may be inaccurate if histogram statistics exist on
a column of that predicate.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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
1 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.
DB2BIND:
***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.
DB2BIND:
***Action for PM32401:
See PM32401 APAR/PTF text for additional information about
why a REBIND is necessary.
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.
DB2BIND:
***Action for PM32384:
See PM32384 APAR/PTF text for additional information about
why a REBIND is necessary.
PM32384 corrects a problem of inaccurate index filter factor
estimate when multi-column cardinality exists in some cases
which may result in an inefficient access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
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,
1 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.
DB2BIND:
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.
DB2BIND:
***Action for PM26521:
See PM26521 APAR/PTF text for additional information about
why a REBIND is necessary.
PM26521 corrects a problem where the filter factor of an IS NULL
predicate is underestimated as 1E-9 if there is a NULL value
in the column, histogram statistics exist, but
frequency statistics do not exist.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
See 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.
DB2BIND:
***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.
1
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
See PM25059 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM25059 corrects a problem where the page range reduction
is done incorrectly. It may cause DB2 to choose a plan with
an extra GROUP BY / ORDER BY sort where it is not needed.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
See PM23073 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM23073 fixes a filter factor estimation problem for a LIKE
predicate with MIXED data. The filter factor estimation
problem could lead to a poor access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
1 affected by this change.
DB2BIND:
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.
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
1 ***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
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
***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.
DB2BIND:
***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.
1 ACTION:
PM87836 does not correct the incorrect values that are already
in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE. The incorrect
values may or may not be readily identifiable as incorrect
by simple visual inspection.
To get the correct values, apply this fix. Then, delete the
old rows in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE.
EXPLAIN the statements again to re-populate the
DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE with the correct
values.
ACTION:
***Action for PM65872:
See PM65872 APAR/PTF text for additional information about
why a REBIND is necessary.
PM65872 corrects a problem of infinite loop that can occur when
there are a very large number of predicates, and items in the
SELECT list, and at least one predicate is an equal-, ANY-, or
IN-subquery.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDACC PI14460
DSNIRCCA PI14460
DSNIRCCD PI14460
DSNIRCCS PI14460
DSNXGTBC PI14460
DSNXOAND PI14460
DSNXOCCF PI14460
DSNXOCCX PI14460
DSNXOCSC PI14460
DSNXOCSH PI14460
DSNXOCSM PI14460
DSNXOCSN PI14460
DSNXOCSP PI14460
DSNXODF PI14460
DSNXODFB PI14460
DSNXODFE PI14460
DSNXODFR PI14460
DSNXODFT PI14460
DSNXODFX PI14460
DSNXOGBM PI14460
DSNXOGCM PI14460
DSNXOGCT PI14460
DSNXOGCX PI14460
DSNXOGC3 PI14460
DSNXOGNC PI14460
DSNXOGOR PI14460
DSNXOGP PI14460
DSNXOINQ PI14460
DSNXOIXP PI14460
1 DSNXOLPR PI14460
DSNXOPB PI14460
DSNXOPCO PI14460
DSNXOPG PI14460
DSNXOPGG PI14460
DSNXOPG1 PI14460
DSNXOPG2 PI14460
DSNXOPRP PI14460
DSNXOPRS PI14460
DSNXOPTC PI14460
DSNXOQSJ PI14460
DSNXOSPJ PI14460
DSNXOSS PI14460
DSNXOTCC PI14460
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14460 DSNGDACC DSNIRCCA DSNIRCCD DSNIRCCS DSNXGTBC DSNXOAND
DSNXOCCF DSNXOCCX DSNXOCSC DSNXOCSH DSNXOCSM DSNXOCSN
DSNXOCSP DSNXODF DSNXODFB DSNXODFE DSNXODFR DSNXODFT
DSNXODFX DSNXOGBM DSNXOGCM DSNXOGCT DSNXOGCX DSNXOGC3
DSNXOGNC DSNXOGOR DSNXOGP DSNXOINQ DSNXOIXP DSNXOLPR
DSNXOPB DSNXOPCO DSNXOPG DSNXOPGG DSNXOPG1 DSNXOPG2
DSNXOPRP DSNXOPRS DSNXOPTC DSNXOQSJ DSNXOSPJ DSNXOSS
DSNXOTCC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDACC
DSNIRCCA
DSNIRCCD
DSNIRCCS
DSNXGTBC
DSNXOAND
DSNXOCCF
DSNXOCCX
DSNXOCSC
DSNXOCSH
DSNXOCSM
DSNXOCSN
DSNXOCSP
DSNXODF
DSNXODFB
DSNXODFE
DSNXODFR
DSNXODFT
DSNXODFX
DSNXOGBM
DSNXOGCM
DSNXOGCT
DSNXOGCX
DSNXOGC3
DSNXOGNC
DSNXOGOR
DSNXOGP
DSNXOINQ
1 DSNXOIXP
DSNXOLPR
DSNXOPB
DSNXOPCO
DSNXOPG
DSNXOPGG
DSNXOPG1
DSNXOPG2
DSNXOPRP
DSNXOPRS
DSNXOPTC
DSNXOQSJ
DSNXOSPJ
DSNXOSS
DSNXOTCC
LISTEND
UI18020 COVER LETTER END
UI18032 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09337 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4-04 DSNXOSPJ +0DE8 *
* may occur due to an incorrect internal *
* pointer setting during the BIND or *
* PREPARE process when the DB2 optimizer *
* estimates the costs of pair-wise join *
* choices. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the DB2 optimizer estimates the costs of pair-wise join
choices during the process of BIND or PREPARE, an 0C4 ABEND may
occur which is caused by an incorrect internal pointer setting
due to internal processing errors. An intentional ABEND
04E-00E70005 in DSNXOSJO may be raised to catch such a case.
Additional Keywords:
ABEND0C4 RC00000004 in DSNXOSPJ OFFSET0DE8 SQLPAIRWISEJOIN
SQLACCESSPATH ABEND04E RC00E70005
Code is changed to fix the problem that caused an 0C4 ABEND
for the situation described above. As with any change to DB2
query optimization that can drive a different access path,
there is some risk of query performance regression.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09337
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
1
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSJO PI09337
DSNXOSPJ PI09337
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09337 DSNXOSJO DSNXOSPJ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSJO
DSNXOSPJ
LISTEND
UI18032 COVER LETTER END
UI18057 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14970 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of built-in *
* functions with timestamp strings. *
****************************************************************
* PROBLEM DESCRIPTION: An SQLCODE -180 can occur after *
* migration to DB2 10 or DB2 11 for a *
* timestamp string with a length of 14 as *
* input to the DATE scalar function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DATE scalar function documentation allows a character string
as its input argument. The string must be a valid string
representation of a date or timestamp as documented in the SQL
Reference section "String representations of datetime
values".
It can also be a string with an actual length of 7 that
represents a valid date in the form yyyynnn. Releases of DB2
prior to Version 10 also allowed a 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. The character string with length 14 is not documented
as a valid input to the DATE function. DB2 Version 10 and 11
will issue an SQLCODE -180 for a character string with a
length of 14 as input to a scalar function such as DATE in the
following example:
1
SELECT DATE ('20140327000000')
FROM SYSIBM.SYSDUMMY1 ;
Other scalar functions that allowed an input character string
with a length of 14 in DB2 releases prior to Version 10 may also
issue an SQLCODE -180 in DB2 Version 10 and 11.
To help with migration to DB2 10 and DB2 11, the code in DB2 has
been modified to allow the following input expression :
"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."
for the following scalar functions :
ADD_MONTHS
DATE
DAY
DAYOFMONTH
DAYOFWEEK
DAYOFWEEK_ISO
DAYOFYEAR
DAYS
EXTRACT
HOUR
JULIAN_DAY
LAST_DAY
MIDNIGHT_SECONDS
MINUTE
MONTH
MONTHS_BETWEEN
NEXT_DAY
QUARTER
ROUND_TIMESTAMP
SECOND
TIME
TIMESTAMP_ISO
TRUNC_TIMESTAMP
WEEK
WEEK_ISO
YEAR
The following will be added to the DB2 10 and DB2 11 for z/OS
publications to clarify the input argument on the above scalar
functions.
"A character or graphic string with an actual length of 14
that represents a valid date and time (as allowed for the
TIMESTAMP function) is also allowed as input to other scalar
functions that accept a timestamp as an input argument."
Additional keywords: SQLMIGRATION SQLCODE180 SQLTIMESTAMP
1 SQLDATE SQLTIME
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14970
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
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
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDEC PI14970
DSNXRINT PI14970
DSNXRLET PI14970
DSNXRTIM PI14970
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14970 DSNXRDEC DSNXRINT DSNXRLET DSNXRTIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDEC
DSNXRINT
DSNXRLET
DSNXRTIM
LISTEND
UI18057 COVER LETTER END
UI18073 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM96007 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the *
1 * VARCHAR function. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 returns incorrect output when *
* integer 32767 is used as the second *
* parameter in the VARCHAR scalar *
* function and the first parameter *
* contains at least 32767 characters. *
* The typical incorrect output is an *
* empty string returned. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 returns incorrect output when integer 32767 is used as the
second parameter in the VARCHAR scalar function and the first
parameter contains at least 32767 characters.
The following example illustrates the problem.
1. Create a table with an XML column.
CREATE TABLE T1 (X1 XML);
Populate the table with an XML size larger than 32767
bytes.
2. Fetch X1 and convert it to VARCHAR with a length of 32767
bytes.
SELECT VARCHAR(XML2CLOB(X1),32767) FROM T1;
DB2 code does not handle the maximum VARCHAR function length
correctly, and eventually it leads to an 'empty string'
incorrect result.
Please note, the memory overlay happens when the maximum length
is used for VARCHAR and the real data character length is at
least 32767. The memory overlay might also lead to the
incorrect result, and it might also lead to other unexpected DB2
behavior, like a DB2 crash.
DB2 code has been modified to address the above problem caused
by a memory overlay.
Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT DB2OVRLAY/K SMCOVERLAY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM96007
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXROB9 PM96007
DSNXROE9 PM96007
DSNXROHB PM96007
DSNXROHE PM96007
DSNXROHR PM96007
1 DSNXROHS PM96007
DSNXROH2 PM96007
DSNXROS9 PM96007
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM96007 DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS
DSNXROH2 DSNXROS9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXROB9
DSNXROE9
DSNXROHB
DSNXROHE
DSNXROHR
DSNXROHS
DSNXROH2
DSNXROS9
LISTEND
UI18073 COVER LETTER END
UI18116 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09643 -
****************************************************************
* USERS AFFECTED: All DB2 users of index defined with COPY NO *
****************************************************************
* PROBLEM DESCRIPTION: When processing an ALTER INDEX *
* BUFFERPOOL for a COPY NO index, *
* a row with ICTYPE='A' and STYPE='F' *
* is incorrectly inserted into SYSCOPY. *
* Later on the MODIFY RECOVERY utility *
* could not delete the rows with *
* ICTYPE='A' and STYPE='F' in SYSCOPY *
* for those indexes defined with COPY NO. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The ICTYPE='A" and STYPE='F' row is incorrectly inserted by
an ALTER INDEX BUFFERPOOL, when the REORG TABLESPACE or REORG
INDEX utility materializes the pending definition change for a
COPY NO index.
DB2 has been changed to not insert rows with ICTYPE='A'
and STYPE='F in SYSCOPY for those indexes defined with COPY NO.
Applying this APAR does not remove the rows with ICTYPE='A' in
SYSCOPY. However these residual rows do not cause any problem.
User can alter the index from COPY NO to YES and then alter it
back to COPY NO which will delete all of the SYSCOPY rows for
the index.
Additional keywords: SQLALTER
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI09643
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDAIP PI09643
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09643 DSNGDAIP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDAIP
LISTEND
UI18116 COVER LETTER END
UI18121 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12713 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of CREATE or *
* ALTER TABLE with LOB columns. *
****************************************************************
* PROBLEM DESCRIPTION: User receives ABND=04E-00E70005, *
* LOC=DSNXIDDL.DSNXICDR:P213 when *
* creating a table with one or more LOB *
* columns. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABND=04E-00E70005,LOC=DSNXIDDL.DSNXICDR:P213 may occur during
CREATE TABLE processing if:
- one of the columns is defined as a LOB data type
- the base database is explicitly defined
- an implicit LOB table space will be created
Given these conditions, the ABEND may also occur in the
following situations:
- The user executes a ALTER TABLE ADD COLUMN statement with a
LOB data type.
- The user executes a ALTER TABLE ADD PARTITION statement.
- The base table space is partition-by-growth and a new
partition is added.
This problem occurs because DB2 incorrectly handles certain
characters in the database name when creating an implicit LOB
table space.
DB2 has been modified to correctly handle the database name when
creating an implicit LOB table space. With this APAR applied,
DB2 will properly create implicit LOB table spaces during CREATE
TABLE processing when given explicitly defined databases.
1 Additional Keywords:
SQLCREATE
SQLALTER
SQLLOB
ABEND04E
RC00E70005
DSNXICDR
P213
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12713
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICDR PI12713
DSNXISB7 PI12713
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12713 DSNXICDR DSNXISB7
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICDR
DSNXISB7
LISTEND
UI18121 COVER LETTER END
UI18127 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15801 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS with IFCID 306 *
* and accounting class 5. *
****************************************************************
* PROBLEM DESCRIPTION: IFCID 306 processing may generate *
* arch.log(quiesce) time when accounting *
* class(5) is on, even though the *
* -ARCHIVE LOG MODE(QUIESCE) command has *
* not been issued. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During collection of statistics on an end IFCID 306 call,
DB2 was accumulating wait time into the QPACALOG field
incorrectly.
.
The incorrect arch.log(quiesce) values can be seen when
accounting class 5 (IFCID187) is turned on.
DB2 has been modified to not accumulate time in the QPACALOG
field during the IFICID 306 call.
.
KEYWORDS: IFCID306 IFCID 187
1
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15801
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWVSR1 PI15801
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15801 DSNWVSR1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVSR1
LISTEND
UI18127 COVER LETTER END
UI18145 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11062 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of -ACCESS DATABASE *
* MODE(NGBPDEP) and -START DATABASE commands *
****************************************************************
* PROBLEM DESCRIPTION: The APAR fixes the following problems *
* in -ACCESS DATABASE MODE(NGBPDEP) *
* command processing: *
* *
* 1. When the command is unable to remove *
* the group buffer pool (GBP) *
* dependency, message DSNI048I is *
* displayed as expected. But a *
* non-zero return code is not returned *
* to the user. Neither should the *
* message DSN9022I indicating normal *
* completion be displayed. *
* *
* DSNI048I @ DSNILSTS CLAIMERS EXIST *
* FOR DATA BASE.... *
* SPACE NAME.... *
* PART.... *
* GROUP BUFFERPOOL *
* DEPENDENCY CANNOT BE *
* REMOVED *
* DSN9022I @ DSNTDDIS 'ACCESS *
* DATABASE' NORMAL NORMAL *
* COMPLETION *
* *
* 2. For a non-partitioning index (NPI), *
* the same DSNI048 message may be *
1 * repeatedly displayed n times where n *
* is the number of partitions of the *
* base partitioned tablespace. Once *
* is sufficient. *
* *
* 3. DSNI048I may be displayed for an *
* invalid part number specified in the *
* part list or range of the PART *
* parameter. *
* *
* 4. msgDSNI045I may be displayed with a *
* blank REASON. *
* *
* DSNI045I -DB2B OPEN FAILED FOR *
* BP1DB, SPACE NAME BP1TS, PART N/A, *
* REASON *
* DSNT305I -DB2B SUBSYSTEM FAILURE *
* DURING ACCESS DATABASE COMMAND *
* PROCESSING. RC=00000008, *
* REASON=00000000 *
* DSN9023I -DB2B DSNTDDIS 'ACCESS *
* DATABASE' ABNORMAL COMPLETION *
* *
* 5. For V10 only, unexpected DSNI048I *
* may appear even there is no claimer *
* on the object. *
* *
* 6. For V10 only, ABEND04E RC00E501A1 in *
* DSNVSRX may occur when running other *
* DATABASE command such as -START DB. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. When RC4 is returned from buffer manager GBP conversion
service indicating that GBP dependency cannot be removed, the
command processor module does not save the error code after
issuing DSNI048I. Hence it is not passed back to the caller
and DSN9022I is displayed.
2. The NPI is processed based on the number of parts of the base
tablespace. However the GBP dependency for NPI is by the
pageset. The repeated calls to GBP conversion service are
unnecessary so are the multiple DSNI048I displays.
3. The part number specified in the part list or range is not
checked against the maximum part number. Hence DSNI048I may
be displayed for an invalid part number
4. When composing the parameters for issuing message DSNI045I,
the reason code field may be missing. Hence the message is
displayed with a blank REASON.
5. In V10, the input parameter to GBP conversion service may
not be set correctly. Hence unexpected DSNI048I may occur.
6. In V10, the cleanup logic in -ACCESS command processor isn't
1 restricted to -ACCESS. Hence abend RC00E501A1 may occur when
-START DB command trying to suspend on an active -ACCESS
command.
The code is changed to pass back the error code to the caller
with proper messages DSNT305I and DSN9023I.
DSNI048I @ DSNILSTS CLAIMERS EXIST FOR
DATA BASE ....
SPACE NAME ....
PART ....
GROUP BUFFERPOOL DEPENDENCY CANNOT BE REMOVED.
DSNT305I @ SUBSYSTEM FAILURE DURING ACCESS DATABASE COMMAND
PROCESSING. RC=00000004, REASON=00000000
DSN9023I @ DSNTDDIS 'ACCESS DATABASE' ABNORMAL COMPLETION
The code is also fixed to call GBP conversion service once only
for the NPI. The invalid part number will be detected early.
DSNI045I message will be always issued with a REASON parameter.
In V10, the input parameter to GBP conversion service will be
set correctly, and the cleanup logic will be restricted for
-ACCESS properly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11062
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILSTS PI11062
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11062 DSNILSTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILSTS
LISTEND
UI18145 COVER LETTER END
UI18155 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16851 -
****************************************************************
* USERS AFFECTED: Users who drop and then create a database in *
* datasharing environment *
****************************************************************
* PROBLEM DESCRIPTION: When creating a database, customer *
* could receive ABEND04E DSNGDCID *
* ERQUAL5002. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a datasharing environment, after drop database A and
1 committing the drop on sub-system 1, the internal database id
is marked as re-useable. When create database B on another
sub-system 2, the internal database id is picked up and
sub-system 2 has reference to database A, the above abend
could be hit.
DB2 has been changed to not reuse the internal database id
if there is still a reference to the DBD associated with this
internal database id to avoid the abend.
If the abend is hit, try to create the database later on
should be successful.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16851
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCID PI16851
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16851 DSNGDCID
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCID
LISTEND
UI18155 COVER LETTER END
UI18163 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13725 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users who want *
* to use VALUES outside a trigger *
* to reference a sequence. *
****************************************************************
* PROBLEM DESCRIPTION: Currently VALUES is only *
* available inside a trigger body and *
* if referenced outside a trigger *
* body, users will receive SQLCODE -142 *
* or DSNH142I. However, *
* some users want to use VALUES *
* outside a trigger to *
* reference a sequence object. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently VALUES is only available inside a
trigger body. However, some users want to use VALUES
outside a trigger body to reference a sequence object.
The following example will receive the SQLCODE -142 if the
1 VALUES is outside a trigger:
VALUES NEXT VALUE FOR MYSEQ1;
After applying this APAR, DB2 for z/OS will support a simple
VALUES clause as a form of a fullselect outside a trigger with
the following rules:
1. V10 New Function Mode (NFM) or above 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.
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;
Additional keywords: SQLCODE142 MSGDSNH142I SQLVALUES
SQLSEQUENCE
DB2 code and SQL reference are modified to support a simple
VALUES clause as a form of a fullselect outside a trigger.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13725
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
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
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.
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.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEPLC PI13725
DSNHSM5R PI13725
DSNXEDP PI13725
DSNXEDSC PI13725
DSNXEDS1 PI13725
DSNXESX PI13725
DSNXOD1 PI13725
DSNXOGP2 PI13725
DSNXOOP PI13725
DSNXOPB PI13725
DSNXOVLS PI13725
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13725 DSNGEPLC DSNHSM5R DSNXEDP DSNXEDSC DSNXEDS1 DSNXESX
DSNXOD1 DSNXOGP2 DSNXOOP DSNXOPB DSNXOVLS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPLC
DSNHSM5R
DSNXEDP
DSNXEDSC
DSNXEDS1
DSNXESX
DSNXOD1
DSNXOGP2
DSNXOOP
DSNXOPB
DSNXOVLS
LISTEND
UI18163 COVER LETTER END
UI18183 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16179 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of range list access. *
****************************************************************
* PROBLEM DESCRIPTION: APAR PI16179 is a pre-conditioning APAR *
* for PI08409, the enabling APAR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the necessary pre-conditioning code for a
later APAR, PI08409.
APAR PI08409 will provide a solution for the following problem
related to range list access (ACCESSTYPE='NR').
DB2 may incorrectly select an inefficient access path for a
1 static query when a more efficient range list access path
exists. This problem can occur when a predicate eligible for
index matching in a range list leg references a timestamp
column. If the query were prepared dynamically, the efficient
range list access path would be chosen.
This APAR adds the pre-conditioning code needed for a later
enabling APAR PI08409.
Additional Keywords: RANGELIST SQLRANGELIST SQLTIMESTAMP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16179
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEBR PI16179
DSNXRBND PI16179
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16179 DSNXEBR DSNXRBND
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXRBND
LISTEND
UI18183 COVER LETTER END
UI18186 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15118 -
****************************************************************
1 * USERS AFFECTED: All V10,V11 DB2 for z/OS users using *
* indexes. *
****************************************************************
* PROBLEM DESCRIPTION: THIS APAR SERVES AS THE MAINTENANCE OF *
* INTERNAL SERVICEABILITY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
THIS APAR SERVES AS THE MAINTENANCE OF INTERNAL SERVICEABILITY.
THIS APAR SERVES AS THE MAINTENANCE OF INTERNAL SERVICEABILITY.
PMB page read activity added to index log records.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15118
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKBIDP PI15118
DSNKDLE PI15118
DSNKDPG PI15118
DSNKINSL PI15118
DSNKINSN PI15118
DSNKISPL PI15118
DSNKISPN PI15118
DSNKREST PI15118
DSNKSALO PI15118
DSNKSDEA PI15118
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15118 DSNKBIDP DSNKDLE DSNKDPG DSNKINSL DSNKINSN DSNKISPL
DSNKISPN DSNKREST DSNKSALO DSNKSDEA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKBIDP
DSNKDLE
DSNKDPG
DSNKINSL
DSNKINSN
DSNKISPL
DSNKISPN
DSNKREST
DSNKSALO
DSNKSDEA
LISTEND
UI18186 COVER LETTER END
UI18219 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15569 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
1 * timestamp strings *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE180 may occur for unsupported *
* timestamp strings after applying *
* UI13818 in DB2 10 or UI13819 in DB2 11. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 10, when the DB2 subsystem parameter BIF_COMPATIBILITY
is set to V9 or V9_DECIMAL_VARCHAR, DB2 tolerates some
invalid string representations of timestamp values. However,
after applying UI13818 and setting the DB2 subsystem parameter
PGRNGSCR to YES, SQLCODE180 may occur for these timestamp
strings.
In DB2 11, when the DB2 subsystem parameter BIF_COMPATIBILITY
is set to V9 or V9_DECIMAL_VARCHAR, and the application
compatibility level is equal to V10R1, DB2 tolerates some
invalid string representations of timestamp values. However,
after applying UI13819, SQLCODE180 may occur for these timestamp
strings.
DB2 has been modified to tolerate the unsupported timestamp
strings when
(1) in DB2 10, the DB2 subsystem parameter BIF_COMPATIBILITY is
set to V9 or V9_DECIMAL_VARCHAR, and the DB2 subsystem parameter
PGRNGSCR is set to YES;
(2) in DB2 11, the DB2 subsystem parameter BIF_COMPATIBILITY is
set to V9 or V9_DECIMAL_VARCHAR, and the application
compatibility level is equal to V10R1.
DB2 has been modified not to issue SQLCODE180 for the
unsupported timestamp strings when
(1) in DB2 10, the DB2 subsystem parameter BIF_COMPATIBILITY is
set to V9 or V9_DECIMAL_VARCHAR, and the DB2 subsystem parameter
PGRNGSCR is set to YES;
(2) in DB2 11, the DB2 subsystem parameter BIF_COMPATIBILITY is
set to V9 or V9_DECIMAL_VARCHAR, and the application
compatibility level is equal to V10R1.
Additional Keywords: SQLTIMESTAMP SQLCODE180
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15569
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLTD PI15569
DSNXOW2C PI15569
DSNXOW2D PI15569
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15569 DSNXOLTD DSNXOW2C DSNXOW2D
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLTD
DSNXOW2C
DSNXOW2D
LISTEND
UI18219 COVER LETTER END
UI18239 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10639 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of the following *
* dynamic query acceleration features: *
* (1) A DB2 'virtual' accelerator for queries *
* (2) Either the dynamic SQL statement EXPLAIN *
* or the special register CURRENT EXPLAIN *
* MODE = EXPLAIN to evaluate a dynamic SQL *
* query's eligibility for acceleration *
****************************************************************
* PROBLEM DESCRIPTION: This APAR provides new function that *
* allows either the dynamic EXPLAIN *
* statement or the special register *
* CURRENT EXPLAIN MODE = EXPLAIN to be *
* used with DB2 Profile Monitor to *
* evaluate a dynamic SQL query's *
* eligibility for acceleration against *
* a specific accelerator named in the DB2 *
* Profile table DSN_PROFILE_ATTRIBUTES . *
* This is most useful when you want to *
* use a 'virtual' accelerator for query *
* evaluation instead of a 'real' *
* accelerator. *
* *
* This APAR also addresses the following *
* abends when DB2 unexpectedly executes *
* an accelerated dynamic SQL query that *
* was prepared using CURRENT EXPLAIN *
* MODE = EXPLAIN : *
* (1) ABEND04E RC00C90101 DSNIBCTD :5007 *
* (2) ABEND04E RC00E20009 *
* DSNXEDC3 . DSNSVSFB +0898 *
* Other abend symptoms may be possible. *
* The abends can occur with or without *
* using a virtual accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently, the DB2 dynamic SQL statement EXPLAIN or the DB2
special register CURRENT EXPLAIN MODE = EXPLAIN can be used to
evaluate a dynamic SQL query's eligibility for acceleration.
However, DB2, not the user, chooses the target accelerator used
for this acceleration evaluation. If the user wants a 'virtual'
1 accelerator to be used for the query's acceleration evaluation
instead of a 'real' accelerator when both are 'active' for the
DB2 subsystem, DB2 will not choose the 'virtual' accelerator.
.
This APAR provides new function that allows either the dynamic
EXPLAIN statement or the special register CURRENT EXPLAIN
MODE = EXPLAIN to be used with DB2 Profile Monitor to evaluate
a dynamic SQL query's eligibility for acceleration against
a specific accelerator named in the DB2 Profile table
SYSIBM.DSN_PROFILE_ATTRIBUTES . In this way, the user can
direct DB2 to use instead a virtual accelerator for evaluating
a query for acceleration.
.
A new function keyword, ACCEL_NAME_EXPLAIN, for
SYSIBM.DSN_PROFILE_ATTRIBUTES has been added. The column
ATTRIBUTE1 contains the real or virtual accelerator
name. This profile monitoring attribute is supported
for the following profile scopes:
Global
AUTHID+LOCATION
PLANNAME+COLLID+PKGNAME
.
This new attribute directs a dynamic EXPLAIN statement
to evaluate an SQL query for acceleration to the accelerator
defined in ACCEL_NAME_EXPLAIN. When using the special register
CURRENT EXPLAIN MODE = EXPLAIN, during the PREPARE of
a dynamic SQL query the query is evaluated for acceleration
to the accelerator defined in ACCEL_NAME_EXPLAIN.
.
The new function ACCEL_NAME_EXPLAIN will not be used for the
following scenarios:
(1) static SQL queries during BIND/REBIND PACKAGE EXPLAIN(YES)
or EXPLAIN(ONLY)
(2) dynamic SQL queries PREPAREd when using CURRENT EXPLAIN
MODE=YES
.
ACCEL_NAME_EXPLAIN will not cause an SQL query to be actually
accelerated to a specific accelerator at execution time.
.
Example
-------
The following example assumes there is an existing
virtual accelerator with the name VACCEL. The INSERT
statements below create a global profile such that all dynamic
EXPLAIN statements with CURRENT QUERY ACCELERATION=ENABLE,
ENABLE WITH FAILBACK, ELIGIBLE or ALL will use the
accelerator VACCEL.
.
INSERT INTO SYSIBM.DSN_PROFILE_TABLE (PROFILEID)
VALUES (1);
.
INSERT INTO SYSIBM.DSN_PROFILE_ATTRIBUTES
(PROFILEID,KEYWORDS,ATTRIBUTE1,ATTRIBUTE2,ATTRIBUTE3)
VALUES
(1, 'ACCEL_NAME_EXPLAIN', 'VACCEL',NULL,NULL);
.
1 After executing the INSERT statements above, the
-START PROFILE command must be issued so that the profile
is activated. At this time all dynamic EXPLAIN statements
will use the virtual accelerator 'VACCEL'.
.
SET CURRENT QUERY ACCELERATION=ENABLE;
SET CURRENT EXPLAIN MODE=EXPLAIN;
SELECT * FROM T1 WHERE C1>2 FOR FETCH ONLY;
.
The SELECT statement above will populate the EXPLAIN tables
since CURRENT EXPLAIN MODE=EXPLAIN and will use the
virtual accelerator 'VACCEL' as defined in the profile tables.
---------------------------------------------------------
This APAR also addresses the following abends when DB2
unexpectedly executes an accelerated dynamic SQL query that
was prepared using CURRENT EXPLAIN MODE = EXPLAIN :
(1) AB04E RC00C90101 DSNIBCTD :5007
(2) AB04E RC00E20009 DSNXEDC3 . DSNSVSFB +0898
Other abend symptoms may be possible. The abends can occur
with or without uing a virtual accelerator.
Keywords:
IDAAV4R1/K IDAAV3R1/K ABEND04E SQLEXPLAIN ERQUAL5007
OFFSET0898 00C90101 00E20009
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10639
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNT1RSP PI10639
DSNXODML PI10639
DSNXOMPS PI10639
DSNXONZA PI10639
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10639 DSNT1RSP DSNXODML DSNXOMPS DSNXONZA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNT1RSP
DSNXODML
DSNXOMPS
DSNXONZA
LISTEND
UI18239 COVER LETTER END
UI18276 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13518 -
****************************************************************
1 * USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* SYSFUN.XSLTRANSFORM function. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -433 is issued when calling *
* the SYSFUN.XSLTRANSFORM with the XML *
* document in which the encoding field of *
* the prolog is not UTF-8. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the SYSFUN.XSLTRANSFORM is called, the XML documents are
converted into UNICODE. If the encoding field in the XML prolog
does not specify UTF-8, the XML parser will issue the "Content
is not allowed in prolog" exception. This causes the SQLCODE
-433 to be issued.
The XSLTRANSFORM UDF is modified, so the error will not occur.
Additional keywords: SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13518
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application environment
for running the SYSFUN.XSLTRANSFORM UDF.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9SPJ PI13518
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13518 DSNX9SPJ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNX9SPJ
LISTEND
UI18276 COVER LETTER END
UI18285 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI08944 -
****************************************************************
1 * USERS AFFECTED: All DB2 for z/OS IMS users of transactions *
* defined with MODE=MULT *
****************************************************************
* PROBLEM DESCRIPTION: When IMS calls the DB2 Commit Verify *
* exit, DB2 signals that a commit or *
* rollback is required in the case where *
* the application has not done an insert *
* or update. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When IMS calls the DB2 Commit Verify exit, DB2 signals that a
commit or rollback is required in the case where the application
has not done an insert or update. Insert, update, or other DB2
functions, for example, held cursors or global temporary tables,
may place the DB2 UR in an inconsistent state.
DB2 should be changed to check a different control block
location which may be a less restrictive, but still accurate,
indication whether the DB2 UR is in a reset or inflight state.
This would allow the DB2 Commit Verify exit to return a
a signal to IMS that a commit or rollback is not required.
DB2 has been updated to modify its checking for the DB2 Commit
Verify exit.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI08944
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEEZ PI08944
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI08944 DSNXEEZ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEEZ
LISTEND
UI18285 COVER LETTER END
UI18288 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13237 -
****************************************************************
* USERS AFFECTED: DB2 9 for z/OS, DB2 10 for z/OS and DB2 11 *
* for z/OS users of the START DATABASE *
* command with ACCESS(FORCE) option and the *
* database or index space specified contains *
* an index on a table residing in a *
* partition-by-growth (PBG) Universal Table *
* Space (UTS). *
****************************************************************
1 * PROBLEM DESCRIPTION: START DATABASE command with *
* ACCESS(FORCE) option failed to *
* clean up REFP status for an index *
* space containing an index on a *
* table contained in a PBG UTS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
START DATABASE with ACCESS(FORCE) specified may fail to
clean up the index space status for an index space containing
an index on a table residing in a PBG UTS.
The START DATABASE with ACCESS(FORCE) option has been modified
to clean up the status of an index space containing an index
on a table residing in a PBG UTS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13237
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISTFO PI13237
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13237 DSNISTFO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISTFO
LISTEND
UI18288 COVER LETTER END
UI18294 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10962 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of MODIFY RECOVERY utility and *
* cloned objects *
****************************************************************
* PROBLEM DESCRIPTION: MODIFY RECOVERY utility does not *
* clean up OBD information as expected *
* for cloned objects *
****************************************************************
* RECOMMENDATION: *
****************************************************************
MODIFY RECOVERY utility deletes information about
versioning of objects which has been made obsolete as
a result of the removal of backup information from
the time when the versioning info was created. This
1 allows for more flexibility in the use of versioning going
forward.
A problem with this function has been reported involving the
use of cloned tables.
Consider this scenario:
1. create a clone of an existing table:
ALTER TABLE ... ADD CLONE ...
2. perform an exchange using the clone:
EXCHANGE DATA BETWEEN TABLE ...
3. make a copy of the table space:
COPY TABLESPACE ... FULL YES ...
4. drop the clone:
ALTER TABLE ... DROP CLONE ...
5. add versioning to the table by adding a column:
ALTER TABLE ... ADD COLUMN ...
6. materialize the ALTER from the previous step and reconcile
the versioning.
REORG ...
7. clean up SYSCOPY, SYSLGRNX, and OBDREC information.
MODIFY RECOVERY ... DELETE AGE(*)
MODIFY RECOVERY utility should have deleted the OBDREC
information for the table but it did not, because it could
not locate the records to be deleted for this object in
catalog table SYSIBM.SYSOBDS.
Note: in cases where REPAIR VERSIONS utility determines
it must delete versioning information from SYSIBM.SYSOBDS
for an object with similar cloning activity, this problem
can also be seen.
Code was changed so that versioning information for cloned
objects can be found in the DB2 catalog and deleted by MODIFY
RECOVERY and REPAIR VERSIONS utilities when necessary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10962
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGUVR PI10962
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10962 DSNUGUVR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGUVR
LISTEND
UI18294 COVER LETTER END
UI18332 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI14891 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY FULL NO utility. *
****************************************************************
* PROBLEM DESCRIPTION: An incremental copy was allowed to be *
* taken by COPY FULL NO immediately after *
* a LOAD RESUME YES LOG YES SHRLEVEL NONE *
* on a PBG table space. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a COPY FULL NO on a partition-by-growth (PBG) table
space right after a LOAD RESUME YES LOG YES SHRLEVEL NONE.
After LOAD utility is run, but no subsequent full image copy is
taken, an incremental image copy should not be allowed, a full
image copy should be taken with message DSNU402I issued.
But in this case, a full image copy was not enforced because
LOAD RESUME YES inserted SYSCOPY records by partition and COPY
FULL NO did not check for part level SYSCOPY records for PBG
table space when the COPY utility was run against the entire
table space with DSNUM ALL.
COPY utility has been modified to disallow an incremental copy
for a PBG table space after a LOAD SHRLEVEL NONE utility is run
on the table space and no subsequent full image copy is taken.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14891
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBAIC PI14891
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14891 DSNUBAIC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBAIC
LISTEND
UI18332 COVER LETTER END
UI18334 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15149 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of DSN1PRNT against a page range of a *
* FlashCopy image copy. *
****************************************************************
* PROBLEM DESCRIPTION: DSN1PRNT on a page range of a FlashCopy *
1 * image copy issued MSGDSN1953I and *
* failed with MSGDSN1993I and RC8. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A DSN1PRNT with PRINT page range parameter against a FlashCopy
image copy issued an error message DSN1953I - STARTING PAGE
NUMBER REQUIRES AN INPUT DATA SET NAME OF data-set-name, and
failed with the message DSN1993I - DSN1PRNT TERMINATED,
page-count PAGES PROCESSED and RC8.
This problem occurred because DSN1PRNT checked the input VSAM
data set name using the DB2 naming conventions, based on the
specified page range. However a FlashCopy image copy data set
would not follow these naming conventions.
DSN1PRNT code has been modified to not check the input VSAM data
set name for FlashCopy image copies. As a result, DSN1PRNT will
not issue any error messages nor print any pages if the PRINT
page range does not exist in the input data set, if that data
set is a FlashCopy image copy.
This is a fix completion for PM94266.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15149
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN1PRNT PI15149
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15149 DSN1PRNT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN1PRNT
LISTEND
UI18334 COVER LETTER END
UI18336 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17697 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS *
* who run queries on tables with indexes *
* defined on them *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC04 in DSNXOGCX +14DA can *
* occur for a query on a table with *
* an index defined on it *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC04 in DSNXOGCX +14DA can occur on bind/prepare of a
1 query on a table with an index defined on it. A zero pointer
is referenced, which is testing a value in low core memory.
That storage location is usually non-zero; however, if it
is zero, this abend can occur. The problem may appear more
often when running on z/OS 2.1 .
Additional Keywords:
DSNXOGCX OFFSET14DA
Code is changed to check for a zero pointer before using it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17697
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGCX PI17697
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17697 DSNXOGCX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGCX
LISTEND
UI18336 COVER LETTER END
UI18350 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16183 -
****************************************************************
* USERS AFFECTED: All DB2 IFI READS users. *
****************************************************************
* PROBLEM DESCRIPTION: IFCID 401 may not be returned on an IFI *
* READS call. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The IFCID 401 record contains information about static
applications in the EDM pool. Sometimes the READS of
IFCID 401 does not return information about all
static applications in the EDM pool.
An error in internal logic can cause DB2 to not return
information about all static applications that are in the EDM
pool. The logic has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16183
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEPLC PI16183
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16183 DSNGEPLC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPLC
LISTEND
UI18350 COVER LETTER END
UI18360 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17492 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of UNLOAD FROMCOPY PART n utility *
* for partition-by-growth table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: AE PI13789 FIX COMPLETION *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
AE PI13789 FIX COMPLETION
AE PI13789 FIX COMPLETION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17492
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULGL PI17492
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17492 DSNUULGL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULGL
LISTEND
UI18360 COVER LETTER END
UI18374 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM99570 -
****************************************************************
* USERS AFFECTED: All DB2 11, DB2 10 and DB2 9 for z/OS users *
* of field procedure. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000004 while running a *
1 * fieldproc with an entry point offset *
* other than zero. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DB2 calls a field procedure that does not have an entry
point address at offset 0 into the module, the wrong address is
used to execute this procedure, causing a DB2 abend.
In the reported case, the customer received ABEND0C4-04.
Different abends are possible depending upon the field
procedure.
DB2 code has been modified to use the correct address to execute
field procedures regardless of entry point offset.
Additional Keyword: SQLFIELDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM99570
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDCML PM99570
DSNIENSR PM99570
DSNILDBP PM99570
DSNIREDR PM99570
DSNITEDI PM99570
DSNXIFLM PM99570
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM99570 DSNIDCML DSNIENSR DSNILDBP DSNIREDR DSNITEDI DSNXIFLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDCML
DSNIENSR
DSNILDBP
DSNIREDR
DSNITEDI
DSNXIFLM
LISTEND
UI18374 COVER LETTER END
UI18378 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13532 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS parallelism *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND 04E-00C90101 at DSNIOST2:5001 may *
* occur when a query meets all of the *
* following criteria: *
1 * *
* 1.Parallelism is chosen in the *
* access path. *
* *
* 2.DPSI index is chosen in the access *
* path and this DPSI is defined with *
* INCLUDE columns. *
* *
* 3.The query returns rows in the DPSI *
* key sequence. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND 04E-00C90101 at DSNIOST2:5001 may occur when a query
meets all of the following criteria:
1.Parallelism is chosen in the access path.
2.DPSI index is chosen in the access path and this DPSI is
defined with INCLUDE columns.
3.The query returns rows in the DPSI key sequence.
In this scenario, DB2 may incorrectly build the index key
length and the child tasks may abend.
Additional keywords:
PARALLELISM SQLPARALLELISM DB2PARALL/K SQLINCLUDE SQLDPSI
Parallelism is disabled for the situations described above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13532
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLCM PI13532
DSNXOLM1 PI13532
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13532 DSNXOLCM DSNXOLM1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXOLCM
DSNXOLM1
LISTEND
UI18378 COVER LETTER END
UI18391 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16448 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS new function. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR provides support for DB2 new *
* function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides support for DB2 new function.
DB2 module DSNYSTRT has been updated to provide support for DB2
new function.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16448
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNYSTRT PI16448
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16448 DSNYSTRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNYSTRT
LISTEND
UI18391 COVER LETTER END
UI18394 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09088 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users are affected. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability enhancements. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides serviceability enhancements which will
not affect DB2 functionality.
1 This APAR provides serviceability enhancements which will not
affect DB2 functionality.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI09088
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWPZ PI09088
DSNDSPRM PI09088
DSNLXGVR PI09088
DSNLXRDT PI09088
DSNLXROP PI09088
DSNLXRQX PI09088
DSNLXRSL PI09088
DSNLXRSQ PI09088
DSNLZD00 PI09088
DSNLZRCI PI09088
DSNLZRDA PI09088
DSNLZSR4 PI09088
DSNLZS00 PI09088
DSNXEDC3 PI09088
DSNXEDC4 PI09088
DSNXEDT3 PI09088
DSNXEFDA PI09088
DSNXELX PI09088
DSNXIAB3 PI09088
DSNXICB1 PI09088
DSNXICB3 PI09088
DSNXICVT PI09088
DSNXIRCO PI09088
DSNXISB4 PI09088
DSNXOMD PI09088
DSNXOQ2 PI09088
DSNZOVTB PI09088
DSN6SPRC PI09088
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09088 DSNDQWPZ DSNDSPRM DSNLXGVR DSNLXRDT DSNLXROP DSNLXRQX
DSNLXRSL DSNLXRSQ DSNLZD00 DSNLZRCI DSNLZRDA DSNLZSR4
DSNLZS00 DSNXEDC3 DSNXEDC4 DSNXEDT3 DSNXEFDA DSNXELX
DSNXIAB3 DSNXICB1 DSNXICB3 DSNXICVT DSNXIRCO DSNXISB4
DSNXOMD DSNXOQ2 DSNZOVTB DSN6SPRC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXGVR
DSNLXRDT
DSNLXROP
DSNLXRQX
DSNLXRSL
DSNLXRSQ
DSNLZD00
DSNLZRCI
1 DSNLZRDA
DSNLZSR4
DSNLZS00
DSNXEDC3
DSNXEDC4
DSNXEDT3
DSNXEFDA
DSNXELX
DSNXIAB3
DSNXICB1
DSNXICB3
DSNXICVT
DSNXIRCO
DSNXISB4
DSNXOMD
DSNXOQ2
DSNZOVTB
MACROS
DSNDQWPZ
DSNDSPRM
DSN6SPRC
LISTEND
UI18394 COVER LETTER END
UI18421 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16505 -
****************************************************************
* USERS AFFECTED: All IRLM230(HIR2230) users. *
****************************************************************
* PROBLEM DESCRIPTION: 1. Change-ID in few IRLM modules is not *
* updated to the apar maintenance level. *
* 2. Need more serviceability to diagnose *
* IRLM delays/hangs in doing a large *
* number of child lock propagation. *
* 3. Need ability to collect timely dumps *
* for lock resource timeouts. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
1. IRLM maintenance level in some modules was not changed to
to the correct APAR level. This leads to looking at incorrect
level of code for IRLM service and problem diagnosis.
This issue exists in few modules which did not change after
IRLM 2.3 was GA'ed.
2. Need more serviceability to diagnose delays in propagating
large number of child locks to the coupling facility lock
structure. Captured dumps don't have enough details about
time it took for completion of each processing, involving
tens of thousands of child locks.
3. Need an ability to collect diagnostic dumps of all members
in a data sharing group, when desired for diagnosing a
timeout on a lock request.
1 GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
1. This APAR updates IRLM apar maintenance level in those
modules which were missing it.
2. This APAR also adds serviceability code for child lock
propagation. Child lock propagation processing will timestamp
beginning and end time in the SCA control block. IRLM will
also write ctrace if 10000 or more child locks are sent in a
single processing to the CF lock structure.
3. Another serviceability is added to collect diagnostic dumps
of all data sharing members when a lock request is timed out.
DB2/IMS caller could turn on RLPDMPDS flag on a lock/change
request if they desire dumps to be collected on timeout.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI16505
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL0C0 PI16505
DXRRL0E0 PI16505
DXRRL0F0 PI16505
DXRRL0F1 PI16505
DXRRL030 PI16505
DXRRL050 PI16505
DXRRL080 PI16505
DXRRL1A0 PI16505
DXRRL1E0 PI16505
DXRRL1E1 PI16505
DXRRL1H0 PI16505
DXRRL1N0 PI16505
DXRRL1P0 PI16505
DXRRL1Q0 PI16505
DXRRL111 PI16505
DXRRL120 PI16505
DXRRL140 PI16505
DXRRL150 PI16505
DXRRL181 PI16505
DXRRL183 PI16505
DXRRL186 PI16505
DXRRL2A0 PI16505
DXRRL2A1 PI16505
DXRRL2A2 PI16505
DXRRL2A3 PI16505
DXRRL2E2 PI16505
DXRRL2F1 PI16505
DXRRL2H0 PI16505
DXRRL2N0 PI16505
DXRRL2P0 PI16505
DXRRL2P1 PI16505
DXRRL2P2 PI16505
DXRRL2R0 PI16505
DXRRL2T1 PI16505
1 DXRRL201 PI16505
DXRRL220 PI16505
DXRRL222 PI16505
DXRRL24D PI16505
DXRRL24E PI16505
DXRRL24G PI16505
DXRRL243 PI16505
DXRRL244 PI16505
DXRRL245 PI16505
DXRRL248 PI16505
DXRRL271 PI16505
DXRRL280 PI16505
DXRRL290 PI16505
DXRRL291 PI16505
DXRRL292 PI16505
DXRRL600 PI16505
DXRRL7C1 PI16505
DXRRL700 PI16505
DXRRL740 PI16505
DXRRL780 PI16505
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16505 DXRRL0C0 DXRRL0E0 DXRRL0F0 DXRRL0F1 DXRRL030 DXRRL050
DXRRL080 DXRRL1A0 DXRRL1E0 DXRRL1E1 DXRRL1H0 DXRRL1N0
DXRRL1P0 DXRRL1Q0 DXRRL111 DXRRL120 DXRRL140 DXRRL150
DXRRL181 DXRRL183 DXRRL186 DXRRL2A0 DXRRL2A1 DXRRL2A2
DXRRL2A3 DXRRL2E2 DXRRL2F1 DXRRL2H0 DXRRL2N0 DXRRL2P0
DXRRL2P1 DXRRL2P2 DXRRL2R0 DXRRL2T1 DXRRL201 DXRRL220
DXRRL222 DXRRL24D DXRRL24E DXRRL24G DXRRL243 DXRRL244
DXRRL245 DXRRL248 DXRRL271 DXRRL280 DXRRL290 DXRRL291
DXRRL292 DXRRL600 DXRRL7C1 DXRRL700 DXRRL740 DXRRL780
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL0C0
DXRRL0E0
DXRRL0F0
DXRRL0F1
DXRRL030
DXRRL050
DXRRL080
DXRRL1A0
DXRRL1E0
DXRRL1E1
DXRRL1H0
DXRRL1N0
DXRRL1P0
DXRRL1Q0
DXRRL111
DXRRL120
DXRRL140
DXRRL150
DXRRL181
DXRRL183
DXRRL186
1 DXRRL2A0
DXRRL2A1
DXRRL2A2
DXRRL2A3
DXRRL2E2
DXRRL2F1
DXRRL2H0
DXRRL2N0
DXRRL2P0
DXRRL2P1
DXRRL2P2
DXRRL2R0
DXRRL2T1
DXRRL201
DXRRL220
DXRRL222
DXRRL24D
DXRRL24E
DXRRL24G
DXRRL243
DXRRL244
DXRRL245
DXRRL248
DXRRL271
DXRRL280
DXRRL290
DXRRL291
DXRRL292
DXRRL600
DXRRL7C1
DXRRL700
DXRRL740
DXRRL780
LISTEND
UI18421 COVER LETTER END
UI18433 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15212 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* Spatial support. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR is removing the use of the *
* DSN5SMSG library from Spatial functions *
* which will make the Spatial component *
* independent of using ICU (International *
* Component for Unicode). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The purpose of this apar is to remove using the DSN5SMSG DLL to
make Spatial functions independent of ICU (International
Component for Unicode).
1
The Spatial function dependency on ICU is being removed by this
Spatial function enhancement. Instead of using the ICU
functionality for creating Spatial messages, internal functions
will replace the ICU functions. Therefore, the DSN5SMSG message
library will be no longer be loaded by the Spatial functions.
The DSN5SMSG DLL module will no longer be loaded during
execution of Spatial functions. With this enhancement, there is
no requirement for the ICU component when executing Spatial
functions.
Additional Keywords: SQLSPATIAL
COMPONENT: 5655-R1402-J2AG210
APARS FIXED: PI15212
SPECIAL CONDITIONS:
COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
After the application of this apar/ptf, the DB2 subsystem needs
to be refreshed so it can pickup the changes for the DSN5SFNC
module.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN5SG0E PI15212
DSN5SG25 PI15212
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15212 DSN5SG0E DSN5SG25
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN5SG0E
DSN5SG25
LISTEND
UI18433 COVER LETTER END
UI18446 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07936 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: In DB2 V9, -ACCESS, -DISPLAY, -START, *
* or -STOP command with DATABASE *
* parameter may receive RC 0 when the *
* user is not authorized to access the *
* database. A non-zero return code is *
* expected. *
* *
* In DB2 V9, V10, and V11, ABEND0C4 *
* DSNTDMST+16E6 may occur when using *
* aforementioned commands. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
When the command processor detects that the user is not
authorized to access the database, the error may not be handled
properly. As a result, the command may receive RC 0.
ABEND0C4 DSNTDMST may happen when accessing the multiline
message block without checking its existence first.
The code is fixed to return non-zero return code with message
DSN9023I for unauthorized users, and to ensure that the
multiline message block exists before accessing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI07936
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDMST PI07936
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07936 DSNTDMST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDMST
LISTEND
UI18446 COVER LETTER END
UI18472 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15104 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of an SQL *
* statement that contains a 'SELECT *' in a *
* CASE WHEN condition, and the case expression *
* is in the SELECT list of a table expression. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS DSNXODTR P333 could happen for *
* an SQL statement that contains a *
* 'SELECT *' in a CASE WHEN condition, *
* and the case expression is in the *
* SELECT list of a table expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(C1 CHAR(10));
COMMIT;
1 SELECT 1 FROM (
SELECT
CASE
WHEN 'ABC' IN (SELECT * FROM T1)
THEN 'XYZ'
ELSE 'AAA'
END AS C1
FROM SYSIBM.SYSDUMMY1) AS X
;
SQLCODE -582 should be issued for the SQL statement above, while
DB2 did not correctly process it, which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND, and SQLCODE -582 will
be correctly issued.
Additional keywords: SQLTABLEEXPR SQLCASE SQLWHEN SQLCTE
SQLCODE582
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15104
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODTR PI15104
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15104 DSNXODTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODTR
LISTEND
UI18472 COVER LETTER END
UI18486 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15681 -
****************************************************************
* USERS AFFECTED: All IRLM230 (HIR2230) users. *
****************************************************************
* PROBLEM DESCRIPTION: Storage compression does not occur as *
* frequently as intended for the *
* CSA/ECSA pools. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
When the total CSA/ECSA storage usage reaches the pre-
defined threshold value, the compression logic is supposed
to run more frequently. Because an incorrect field is used
in making the decision, compression is not invoked as often
as intended.
1 GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
The correct field is used to trigger the compression logic.
Note: customer who uses Extended Deadlock should apply fix code
of this APAR because some modules are shipped with down
level DXRRLMCB macro.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI15681
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2U0 PI15681
DXRRL2V0 PI15681
DXRRL24B PI15681
DXRRL240 PI15681
DXRRL249 PI15681
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15681 DXRRL2U0 DXRRL2V0 DXRRL24B DXRRL240 DXRRL249
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2U0
DXRRL2V0
DXRRL24B
DXRRL240
DXRRL249
LISTEND
UI18486 COVER LETTER END
UI18488 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09107 -
****************************************************************
* USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) *
* data sharing users sysplexds smduplex. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM makes un-necessary disconnect with *
* the lock structure if the structure is *
* in duplexing mode. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
During start-up, IRLM connects to the lock structure. If the
structure is in (regular) rebuild process then IRLM disconnects
itself from the structure. IRLM re-connects to the lock
structure once the rebuild process is completed.
1
For lock structure defined as DUPLEX(ENABLED), the structure
is constantly in duplexing rebuild process as soon as there is
a connector connected to it. There is no need to disconnect
from the lock structure if it's in duplexing rebuild process.
In an XES group with large number of members, if all members
try to connect to a DUPLEX(ENABLED) lock structure concurrently,
then it's very likely that some members will disconnect itself
from the structure.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Before connecting to the structure, IRLM queries the lock
structure status. If the structure is in duplexing rebuild
process, then a corresponding flag is turn ON. This flag
prevents the health check logic to issue the disconnect.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI09107
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL710 PI09107
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09107 DXRRL710
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL710
LISTEND
UI18488 COVER LETTER END
UI18492 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13181 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI *
* and DB2 11 for z/OS ODBC/CLI running *
* with LIMITEDBLOCKFETCH=1. *
****************************************************************
* PROBLEM DESCRIPTION: Fetching NULL data from an unbound *
* column with LIMITEDBLOCKFETCH=1 *
* causes NULL data to return for the *
* column for all subsequent rows. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When SQLGetData() is called to fetch an unbound column with
1 NULL data, the column is flagged as NULL by a NULL indicator
for the current row. This NULL indicator, however, does not
get reset each time a new row is retrieved. This causes
SQLGetData() to always return NULL data for the column.
Code has been updated to reset the NULL indicator for each row.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI13181
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC27 PI13181
DSNAOG27 PI13181
DSNAOCLI PI13181
DSNAOSDK PI13181
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13181 DSNAOC27 DSNAOG27 DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC27
DSNAOG27
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI18492 COVER LETTER END
UI18497 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM95925 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of DSNREXX who issue invalid commands *
* or run with customized REXX environments. *
****************************************************************
* PROBLEM DESCRIPTION: DSNREXX applications may receive *
* erroneous return codes when passing *
* invalid DSNREXX commands to DB2. *
* Also, after a DISCONNECT call, DSNREXX *
* may abend with an ABEND0C1 at +0002 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When passing an invalid command to DSNREXX, the return code
from DSNREXX should be minus 3 (-3), however, the 31-bit address
of DSNTZAAA is returned (a very high value). An example of an
invalid command being sent to DSNREXX might be:
Address DSNREXX "SELECT * FROM Q.STAFF" ;
1
Additionally, on a DISCONNECT call, in some environments,
DSNREXX can receive an ABENDS0C1 at location +0002 OFFSET0002.
DSNREXX code has been changed to return a -3 for an invalid
command. Also, DSNREXX will check for a valid pointer prior
to calling IRXEXCOM on a DISCONNECT call.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM95925
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
The fix for APAR PM77340 has an associated change to the
DB2 documentation, similar to the following:
Under Section "Defining the SQL communications area,
SQLSTATE, and SQLCODE in REXX",
the following text:
If you use the ADDRESS DSNREXX "CONNECT" ssid syntax
to connect to DB2, the SQLCA variables are a set of
simple variables. If you use the CALL SQLDBS "ATTACH TO"
syntax to connect to DB2, the SQLCA variables are
compound variables that begin with the stem SQLCA.
is changed to the following:
The SQLCA has the following forms:
A set of simple variables
A set of compound variables that begin with the stem SQLCA
The simple variables is the default form of the SQLCA. Using
CALL SQLEXEC results in the compound stem variables.
Otherwise, the attachment command used determines the form of
the SQLCA. If you use the ADDRESS DSNREXX 'CONNECT' ssid
syntax to connect to DB2, the SQLCA variables are a set of
simple variables. If you use the CALL SQLDBS 'ATTACH TO'
syntax to connect to DB2, the SQLCA variables are compound
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".
1
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'.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTZAAA PM95925
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM95925 DSNTZAAA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTZAAA
LISTEND
UI18497 COVER LETTER END
UI18526 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17841 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility executing via DB2 Stored Procedure *
* (DSNUTILU/DSNUTILS) and utilizing Trusted *
* Context authorization *
****************************************************************
* PROBLEM DESCRIPTION: UNLOAD TABLESPACE being executed from *
* the Utilities Stored Procedure *
* (DSNUTILU) and utilizing Trusted *
* Context authorization, issues *
* MSGDSNU1253I and ends with RC8. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
UNLOAD TABLESPACE was run from a DB2 Stored Procedure utilizing
Trusted Context authorization and issued message DSNU1253I USER
user-id DOES NOT HAVE THE SELECT PRIVILEGE ON TABLE table-name
in TABLESPACE table-space-name and ends with RC8.
The error is due to the Trusted Context authorization
information from the submitting batch job not being propagated
to the utility being run via a DB2 Stored Procedure.
1 While this problem occurred during the UNLOAD utility, any
utility being executed via a DB2 Stored Procedure with Trusted
Context can be affected. Another message that can be produced
for this is DSNU060I USER userid NOT AUTHORIZED FOR utility-name
UTILITY ON DATABASE dbase-name.
Additional keyword: MSGDSNU060I
Utility code has been changed to propagate any Trusted Context
authorization information from the submitting batch job to the
DB2 Stored Procedure executing that utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17841
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGBAC PI17841
DSNUGSIT PI17841
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17841 DSNUGBAC DSNUGSIT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGBAC
DSNUGSIT
LISTEND
UI18526 COVER LETTER END
UI18528 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11547 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00F30905 is taken by DB2 *
* after a CALLRTM TYPE=MEMTERM is issued *
* for the same address space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00F30905 is taken by DB2 after a CALLRTM
TYPE=MEMTERM is issued for the same address space. This
additional abend should not be necessary.
Module DSN3SSES has been updated to avoid the additional
ABEND04E RC00F30905.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11547
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3SSES PI11547
DSN3SSI1 PI11547
DSN3SSI2 PI11547
DSN3SSRQ PI11547
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11547 DSN3SSES DSN3SSI1 DSN3SSI2 DSN3SSRQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3SSES
DSN3SSI1
DSN3SSI2
DSN3SSRQ
LISTEND
UI18528 COVER LETTER END
UI18537 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16826 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement containing OUTER JOIN, multiple *
* common table expressions (CTE) and set *
* operations. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -404 may be issued incorrectly *
* for an SQL statement containing set *
* operations, and multiple common table *
* expressions which include OUTER JOIN *
* where column defined with NOT NULL are *
* referenced. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
DDL:
CREATE TABLE TEST.T1
(C1 CHAR(2) NOT NULL,
C2 CHAR(5) NOT NULL);
CREATE TABLE TEST.T2
(C1 CHAR(2) NOT NULL,
C2 CHAR(5) NOT NULL);
INSERT INTO TEST.T1 VALUES('1A', '11ABC');
INSERT INTO TEST.T2 VALUES('1A', '22EDF');
SQL:
WITH CTE1 (COL11, COL12) AS
(SELECT B.C1, B.C2
1 FROM TEST.T1 AS A
LEFT OUTER JOIN TEST.T2 AS B
ON A.C1 = B.C1),
CTE2 (COL21, COL22) AS
(SELECT COL11, COL12
FROM CTE1),
CTE3 (COL31, COL32) AS
(SELECT COL21, COL22
FROM CTE2
UNION ALL
SELECT C1, C2
FROM TEST.T1),
CTE4 (COL41, COL42) AS
(SELECT COL21, COL22
FROM CTE2
UNION ALL
SELECT C1, C2
FROM TEST.T1)
SELECT COL51, COL52 FROM
(SELECT COL31, COL32
FROM CTE3
UNION ALL
SELECT COL41, COL42
FROM CTE4;
) CT5(COL51, COL52);
DB2 did not handle the null ability correctly in the above
SQL statement and caused the SQLCODE.
Code in DB2 has been modified correctly to process an SQL
statement containing OUTER JOIN, multiple common table
expressions (CTE) and set operations.
Additional keywords: SQLCTE SQLUNIONALL SQLLEFTJOIN
SQLLEFT SQLCODE404 SQLUNION
SQLINTERSECT SQLINTERSECTALL
SQLEXCEPT SQLEXCEPTALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16826
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
1 affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCNR PI16826
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16826 DSNXOCNR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCNR
LISTEND
UI18537 COVER LETTER END
UI18548 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14346 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: If the user issues a CANCEL IRLM *
* command to terminate DB2, and there are *
* DB2 applications that do not monitor *
* the RRSAF Terminate ECB, the *
* applications may issue SQL late in DB2 *
* shutdown. DB2 will stop the SQL *
* requests with RC100 RC00F30805. DB2 *
* module DSNAPRHX recovery in the allied *
* address space may get an ABEND0C4 while *
* cleaning up those SQL requests if DB2 *
* blocks have already been freed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 module DSNAPRHX may get an ABEND0C4 while cleaning
up DB2 control blocks very late during DB2 shutdown.
DB2 has already blocked the application SQL request with
RC100 and RC00F30805, however it may get an ABEND0C4
when cleaning up control blocks before it returns to the
calling application.
Module DSNAPRHX has been updated to avoid an ABEND0C4 when
referencing DB2 control blocks.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI14346
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAPRHX PI14346
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14346 DSNAPRHX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRHX
LISTEND
UI18548 COVER LETTER END
UI18553 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11594 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users and DB2 11 for *
* z/OS users of queries with an OLAP function *
* and a set function. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E72018 DSNXGRDS.DSNXSINE *
* +331A may occur for a query containing *
* an OLAP function and a set function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E72018 DSNXGRDS.DSNXSINE+331A may occur for a query
containing an OLAP function and a set function.
An example for error case is shown below:
SELECT DENSERANK() OVER (ORDER BY C1), NEED.C1
FROM ( SELECT C1,
MAX(CASE WHEN C2 = 'P' THEN '1' ELSE '0' END) AS P
FROM T1
WHERE C3 = 'TX'
GROUP BY C1 ) NEED
HAVING P ='0'
ORDER BY 1;
The bindtime code in DB2 is modified to correct the conditions
leading to the ABEND.
Additional Keywords: ABEND0C4 SQLSQLRANK SQLDENSERANK SQLOLAP
SQLROWNUMBER SQLGROUPBY SQLSETFUNCTION
SQLHAVING
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11594
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
DB2BIND:
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.
DB2BIND:
See PM72976 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
Apar PM72976 corrects a problem that can cause an ABEND04E
RC00C90101 at DSNIDM.DSNONLLE:5003 when running a query that
contains an OLAP function and a group by clause that references
a LOB column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
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.
DB2BIND:
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
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOWIN PI11594
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11594 DSNXOWIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOWIN
LISTEND
UI18553 COVER LETTER END
UI18558 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16101 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of parallelism *
****************************************************************
* PROBLEM DESCRIPTION: During execution of a query in *
* parallel, the following abend may *
* occur: *
* *
* ABEND04E RC00E72100 in DSNXSPKY +065E *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During execution of a query in parallel, the following abend may
occur:
ABEND04E RC00E72100 in DSNXSPKY +065E
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.
Additional keywords:
PARALLELISM SQLPARALLELISM DB2PARALL/K ABEND04E RC00E72100
OFFSET065E SQLIN SQLSMJ SQLMSJ SMJ MSJ
DB2 code has been changed to properly build the index key ranges
for this scenario.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16101
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLDE PI16101
DSNXOLFQ PI16101
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16101 DSNXOLDE DSNXOLFQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLDE
DSNXOLFQ
LISTEND
UI18558 COVER LETTER END
UI18568 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14913 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of *
* Resource Limit Facility (RLF) in *
* Data Sharing environment *
****************************************************************
1 * PROBLEM DESCRIPTION: ABEND04E RC00E30001 at *
* DSNTGSCC DSNTCDSH OFFSET126E *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Under data sharing environment RLF holds p-locks on the RLF
objects while RLF is active. These p-locks are released during
STOP RLIMIT process. In the reported case, STOP RLIMIT process
attempted to release a p-lock which was not held for RLF,
resulting in the reported abend.
.
Related Keyword: DB2RLF
DB2 has been modified to avoid releasing a p-lock that is not
held for RLF during STOP RLIMIT process.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14913
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTCDSH PI14913
DSNTCSRS PI14913
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14913 DSNTCDSH DSNTCSRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTCDSH
DSNTCSRS
LISTEND
UI18568 COVER LETTER END
UI18570 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12625 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* SQL scalar functions that use the z/OS *
* Language Environment. *
****************************************************************
* PROBLEM DESCRIPTION: Performance of certain scalar SQL *
* functions may degrade because of *
* unnecessary synchronization calls. *
* Only scalar functions that use the *
* Language Environment are affected. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Certain SQL scalar functions utilize the z/OS Language
Environment (LE) as an execution environment.
1 Unnecessary synchronization was being performed for these
functions as part of some serviceability logic. This resulted
in a performance overhead.
The affected functions include:
COS, COSH, ACOS, SIN, SINH, ASIN, TAN, TANH, ATAN, ATAN2, COT,
EXP, LN, LOG10, POWER, LAST_DAY, NEXT_DAY, ROUND_TIMESTAMP,
ADD_MONTH, TRUNC_TIMESTAMP.
The unnecessary synchronization has been removed to improve the
performance of the mentioned scalar functions when used in the
Language Environment (LE).
Additional Keywords: SQLPERFORMANCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12625
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXINIT PI12625
DSNXLEII PI12625
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12625 DSNXINIT DSNXLEII
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXINIT
DSNXLEII
LISTEND
UI18570 COVER LETTER END
UI18574 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07861 -
****************************************************************
* USERS AFFECTED: All Users of the IBM Data *
* Server Driver for JDBC and SQLJ *
****************************************************************
* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and *
* SQLJ version 3.65.117 is provided by *
* this APAR ( JCCV365117 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V11, DB2 z/OS V10, *
* DB2 z/OS V9 and alternate supplemental *
* driver for DB2 z/OS V8 ( JCCZOSDB2V11, *
* JCCZOSDB2V10, JCCZOSDB2V9, JCCZOSDB2V8) *
* *
1 * This APAR delivers a new release (3.65) *
* of the IBM Data Server Driver for JDBC *
* and SQLJ providing an accumulation of *
* defect fixes and enhancements. *
* *
* Individual items are documented in the *
* APAR summary section that follows. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
JCC sub-category keywords:
JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ
The following changes are delivered in this APAR:
_______________________________________________________________
All zos Connectivity: When application calls setBytes() method,
this may fail with SQLCODE4474(-4474) if the target column type
is CHAR on ZOS Databases. This issue is fixed.(RTC 36106)
_______________________________________________________________
All zos Connectivity: An application may receive
SQLCODE181(-181) when it sends a timestamp with date
component as 9999-12-31 or 0001-01-01
(for example 9999-12-31 23:59:59.0) for a timestamp
parameter of a stored procedure using the setObject() api.
This occurs when timezone adjustment on the DB2 server
causes the value to overflow or underflow. This has
been fixed in the JCC driver by omitting TIME ZONE
information in the value sent to the server in case the
date in the timestamp matches 9999-12-31 or 0001-01-01.
(RTC 42217)
_______________________________________________________________
All zos Connectivity: Due to a conversion logic error, the
client application may receive ????? from the JCC driver
instead of the actual SQLSTATE string. . This issue is fixed.
(RTC 42728)
_______________________________________________________________
Type-2 zos Connectivity: When there are multiple prepared
statements opened simultaneously on a connection, and one
of those statements is closed, an
ArrayIndexOutOfBoundsException may occur on a subsequent
operation on any of the remaining open prepared statements.
This issue is fixed.(RTC 46966)
_______________________________________________________________
Type-2 zos Connectivity: When the streamChunkSize property is
not correctly sent by the JCC driver, this can result in a
application hang when reading blob data from the DB2 z/OS
server. This issue is fixed.(RTC 40269)
_______________________________________________________________
Type-4 connectivity: The JCC driver frees a transport on
receiving a RLSCONV REUSE reply for a COMMIT request even when
there is a new UOW chained to the COMMIT. The symptoms in an
application would indicate loss of session data or other
failures that can be associated with the transport having been
switched in the middle of a UOW.
This issue is fixed.(RTC 45936)
_______________________________________________________________
1 Type-4 connectivity: Client affinities failback does not
complete after the primary has been up. The JCC driver traces
indicate that the failback timer either does not show up as
running or repeatedly ends abruptly without indication of
whether it detected the primary to be up or not.
This issue is fixed. (RTC 45939).
_______________________________________________________________
Type-4 connectivity: Connection to DB2 fails when running the
JCC driver in a SP800-131 STRICT mode JVM. A communication
error containing the text "Message: Received fatal alert:
handshake_failure. ERRORCODE=-4499, SQLSTATE=08001" is received
by the application. This issue is fixed.(RTC 45793).
_______________________________________________________________
Type-4 connectivity: SQLException with SQLCODE4228(-4228) may
be received by an application when using a connection with
enableSysplexWLB=true and executing a preparedStatement
containing parameters of the type BLOB, CLOB, LONGVARCHAR,
LONGVARBINARY, BINARY, VARGRAPHIC or LONGVARGRAPHIC.
This issue is fixed. (RTC 39666).
_______________________________________________________________
Type-4 connectivity: When the JCC keepAliveTimeout property is
set to a value of zero, OS-level TCP/IP keep-alive settings do
not take effect on JCC connections. This behavior is not in
sync with the CLI driver where OS-level keep-alive settings get
applied to driver connections when the keepAliveTimeout is set
to zero. This issue is fixed. (RTC 32207).
_______________________________________________________________
Type-4 connectivity: A special register configured on a
connection URL or a datasource may fail to take effect when
1. JCC triggers a license check immediately after acquiring a
connection and 2. application invokes a commit() or rollback()
as the first thing on the connection before any other SQL
operations. Incorrect special register values can cause
applications to receive SQL errors such as
SQLCODE204(-204) in this scenario. This issue is fixed.
(RTC 41202).
_______________________________________________________________
Type-4 connectivity: The isValid(int timeout) API may throw
NullPointerException when client reroute is enabled. Also, the
isValid (int timeout) API may not honor the specified timeout
in certain scenarios. This issue is fixed.(RTC 35828).
_______________________________________________________________
Type-4 connectivity: On an XA connection, if the first SQL
submitted suffers an SQLException, the subsequent SQL may
receive an XAER_PROTO along with the message "Error executing
XAResource.start(). This issue is fixed.(RTC 39374).
_______________________________________________________________
Type-4 connectivity: The getCatalog() API always returns
CURRENT SERVER value by default which is incorrect. JCC driver
also introduced a new global boolean property
retCatalogAsServer, to control the RETCAT option for
getCatalog() API usage when invoking the SYSIBM.SQLTABLES
stored procedure.
( RTC 44231)
The items described in the APAR Problem
Summary have been resolved as noted in
1 the summary and included in this APAR.
COMPONENT: 5740-XYR02-JDBAA12
APARS FIXED: PI07861
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAQJBA PI07861
DSNAQJBB PI07861
DSNAQJB1 PI07861
DSNAQJB2 PI07861
DSNAQJB3 PI07861
DSNAQJB4 PI07861
DSNAQJB5 PI07861
DSNAQJB6 PI07861
DSNAQJB7 PI07861
DSNAQJB8 PI07861
DSNAQJC1 PI07861
DSNAQJC2 PI07861
DSNAQJC3 PI07861
DSNAQJC4 PI07861
DSNAQJRM PI07861
DSNAQJS1 PI07861
DSNAQJS2 PI07861
DSNAQ3CA PI07861
DSNAQ3CC PI07861
DSNAQ3CE PI07861
DSNAQ3CF PI07861
DSNAQ3CM PI07861
DSNAQ3C0 PI07861
DSNAQ3C1 PI07861
DSNAQ3C2 PI07861
DSNAQ3C3 PI07861
DSNAQ3C4 PI07861
DSNAQ3C5 PI07861
DSNAQ3C6 PI07861
DSNAQ3C7 PI07861
DSNAQ3C8 PI07861
DSNAQ3C9 PI07861
DSNAQ3E1 PI07861
1 DSNAQ6CC PI07861
DSNAQ6CE PI07861
DSNAQ6CF PI07861
DSNAQ6CM PI07861
DSNAQ6C0 PI07861
DSNAQ6C1 PI07861
DSNAQ6C2 PI07861
DSNAQ6C3 PI07861
DSNAQ6C4 PI07861
DSNAQ6C5 PI07861
DSNAQ6C6 PI07861
DSNAQ6C7 PI07861
DSNAQ6C9 PI07861
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07861 DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4
DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2
DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3CA
DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1
DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7
DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ6CC DSNAQ6CE DSNAQ6CF
DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4
DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAQ3CA
DSNAQ3CC
DSNAQ3CE
DSNAQ3CF
DSNAQ3CM
DSNAQ3C0
DSNAQ3C1
DSNAQ3C2
DSNAQ3C3
DSNAQ3C4
DSNAQ3C5
DSNAQ3C6
DSNAQ3C7
DSNAQ3C8
DSNAQ3C9
DSNAQ6CC
DSNAQ6CE
DSNAQ6CF
DSNAQ6CM
DSNAQ6C0
DSNAQ6C1
DSNAQ6C2
DSNAQ6C3
DSNAQ6C4
DSNAQ6C5
DSNAQ6C6
DSNAQ6C7
DSNAQ6C9
1 MACROS
DSNAQJBA
DSNAQJBB
DSNAQJB1
DSNAQJB2
DSNAQJB3
DSNAQJB4
DSNAQJB5
DSNAQJB6
DSNAQJB7
DSNAQJB8
DSNAQJC1
DSNAQJC2
DSNAQJC3
DSNAQJC4
DSNAQJRM
DSNAQJS1
DSNAQJS2
DSNAQ3E1
LISTEND
UI18574 COVER LETTER END
UI18579 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07860 -
****************************************************************
* USERS AFFECTED: All Users of the IBM Data *
* Server Driver for JDBC and SQLJ *
****************************************************************
* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and *
* SQLJ version 4.15.120 is provided by *
* this APAR ( JCCV415120 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V11, DB2 z/OS V10 and *
* DB2 z/OS V9( JCCZOSDB2V11, *
* JCCZOSDB2V10, JCCZOSDB2V9 ) *
* *
* This APAR delivers a new release (4.15) *
* of the IBM Data Server Driver for JDBC *
* and SQLJ providing an accumulation of *
* defect fixes and enhancements. *
* *
* Individual items are documented in the *
* APAR summary section that follows. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
JCC sub-category keywords:
JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ
The following changes are delivered in this APAR:
_______________________________________________________________
1 All zos Connectivity: When application calls setBytes() method,
this may fail with SQLCODE4474(-4474) if the target column type
is CHAR on ZOS Databases. This issue is fixed.(RTC 36106)
_______________________________________________________________
All zos Connectivity: An application may receive
SQLCODE181(-181) when it sends a timestamp with date
component as 9999-12-31 or 0001-01-01
(for example 9999-12-31 23:59:59.0) for a timestamp
parameter of a stored procedure using the setObject() api.
This occurs when timezone adjustment on the DB2 server
causes the value to overflow or underflow. This has
been fixed in the JCC driver by omitting TIME ZONE
information in the value sent to the server in case the
date in the timestamp matches 9999-12-31 or 0001-01-01.
(RTC 42217)
_______________________________________________________________
All zos Connectivity: Due to a conversion logic error, the
client application may receive ????? from the JCC driver
instead of the actual SQLSTATE string. . This issue is fixed.
(RTC 42728)
_______________________________________________________________
Type-2 zos Connectivity: When there are multiple prepared
statements opened simultaneously on a connection, and one
of those statements is closed, an
ArrayIndexOutOfBoundsException may occur on a subsequent
operation on any of the remaining open prepared statements.
This issue is fixed.(RTC 46966)
_______________________________________________________________
Type-2 zos Connectivity: When the streamChunkSize property is
not correctly sent by the JCC driver, this can result in a
application hang when reading blob data from the DB2 z/OS
server. This issue is fixed.(RTC 40269)
_______________________________________________________________
Type-4 connectivity: The JCC driver frees a transport on
receiving a RLSCONV REUSE reply for a COMMIT request even when
there is a new UOW chained to the COMMIT. The symptoms in an
application would indicate loss of session data or other
failures that can be associated with the transport having been
switched in the middle of a UOW.
This issue is fixed.(RTC 45936)
_______________________________________________________________
Type-4 connectivity: Client affinities failback does not
complete after the primary has been up. The JCC driver traces
indicate that the failback timer either does not show up as
running or repeatedly ends abruptly without indication of
whether it detected the primary to be up or not.
This issue is fixed. (RTC 45939).
_______________________________________________________________
Type-4 connectivity: Connection to DB2 fails when running the
JCC driver in a SP800-131 STRICT mode JVM. A communication
error containing the text "Message: Received fatal alert:
handshake_failure. ERRORCODE=-4499, SQLSTATE=08001" is received
by the application. This issue is fixed.(RTC 45793).
_______________________________________________________________
Type-4 connectivity: SQLException with SQLCODE4228(-4228) may
be received by an application when using a connection with
1 enableSysplexWLB=true and executing a preparedStatement
containing parameters of the type BLOB, CLOB, LONGVARCHAR,
LONGVARBINARY, BINARY, VARGRAPHIC or LONGVARGRAPHIC.
This issue is fixed. (RTC 39666).
_______________________________________________________________
Type-4 connectivity: When the JCC keepAliveTimeout property is
set to a value of zero, OS-level TCP/IP keep-alive settings do
not take effect on JCC connections. This behavior is not in
sync with the CLI driver where OS-level keep-alive settings get
applied to driver connections when the keepAliveTimeout is set
to zero. This issue is fixed. (RTC 32207).
_______________________________________________________________
Type-4 connectivity: A special register configured on a
connection URL or a datasource may fail to take effect when
1. JCC triggers a license check immediately after acquiring a
connection and 2. application invokes a commit() or rollback()
as the first thing on the connection before any other SQL
operations. Incorrect special register values can cause
applications to receive SQL errors such as
SQLCODE204(-204) in this scenario. This issue is fixed.
(RTC 41202).
_______________________________________________________________
Type-4 connectivity: The isValid(int timeout) API may throw
NullPointerException when client reroute is enabled. Also, the
isValid (int timeout) API may not honor the specified timeout
in certain scenarios. This issue is fixed.(RTC 35828).
_______________________________________________________________
Type-4 connectivity: On an XA connection, if the first SQL
submitted suffers an SQLException, the subsequent SQL may
receive an XAER_PROTO along with the message "Error executing
XAResource.start(). This issue is fixed.(RTC 39374).
_______________________________________________________________
Type-4 connectivity: The getCatalog() API always returns
CURRENT SERVER value by default which is incorrect. JCC driver
also introduced a new global boolean property
retCatalogAsServer, to control the RETCAT option for
getCatalog() API usage when invoking the SYSIBM.SQLTABLES
stored procedure.
( RTC 44231)
The items described in the APAR Problem
Summary have been resolved as noted in
the summary and included in this APAR.
COMPONENT: 5740-XYR02-JDBAA12
APARS FIXED: PI07860
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM58952
____________________________________________________________
This PTF contains a fix for a defect in the SQLJ translator.
Incorrect code was generated for an SQL SELECT INTO statement
using a common table expression specified with the "WITH"
keyword. To make this fix effective for any impacted SQLJ
program, after applying the APAR, you must re-translate the
1 SQLJ program, then you must run the SQLJ Binder (db2sqljbind)
again on the affected profiles and rebind the profiles.
See PM58952 APAR/PTF text in the PTF cover letter for
further information about this problem. Reference entry
with (wsdbu01043533) identifier.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAJJC1 PI07860
DSNAJJC2 PI07860
DSNAJ3CC PI07860
DSNAJ3CE PI07860
DSNAJ3CF PI07860
DSNAJ3CM PI07860
DSNAJ3C0 PI07860
DSNAJ3C1 PI07860
DSNAJ3C2 PI07860
DSNAJ3C3 PI07860
DSNAJ3C4 PI07860
DSNAJ3C5 PI07860
DSNAJ3C6 PI07860
DSNAJ3C7 PI07860
DSNAJ3C9 PI07860
DSNAJ6CC PI07860
DSNAJ6CE PI07860
DSNAJ6CF PI07860
DSNAJ6CM PI07860
DSNAJ6C0 PI07860
DSNAJ6C1 PI07860
DSNAJ6C2 PI07860
DSNAJ6C3 PI07860
DSNAJ6C4 PI07860
DSNAJ6C5 PI07860
DSNAJ6C6 PI07860
DSNAJ6C7 PI07860
DSNAJ6C9 PI07860
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07860 DSNAJJC1 DSNAJJC2 DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM
DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5
DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF
DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4
DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAJ3CC
DSNAJ3CE
DSNAJ3CF
DSNAJ3CM
DSNAJ3C0
DSNAJ3C1
DSNAJ3C2
DSNAJ3C3
DSNAJ3C4
1 DSNAJ3C5
DSNAJ3C6
DSNAJ3C7
DSNAJ3C9
DSNAJ6CC
DSNAJ6CE
DSNAJ6CF
DSNAJ6CM
DSNAJ6C0
DSNAJ6C1
DSNAJ6C2
DSNAJ6C3
DSNAJ6C4
DSNAJ6C5
DSNAJ6C6
DSNAJ6C7
DSNAJ6C9
MACROS
DSNAJJC1
DSNAJJC2
LISTEND
UI18579 COVER LETTER END
UI18608 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12954 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Page latch timeout, with resource *
* unavailable reason code RC00C20031. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A page latch deadlock may occur if one agent holds an S latch on
one page, then requests an S latch on a second page, but the
latch on the second page needs to be upgraded to X either to
acquire a page P-lock or to refresh the page - and meanwhile
another agent is doing the same thing but accessing the pages
in the reverse order. One example of this is when one agent is
doing a forward index scan while another is doing a backward
index scan. Although the S latch request for the second page
is requested conditionally, this is not carried over to the
internal upgrade to X.
The code to implicitly upgrade a page latch from S to X, in
order to refresh the page or get the page P-lock, has been
modified to request the X latch conditionally if the original
S latch was requested conditionally.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12954
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1LTS PI12954
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12954 DSNB1LTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1LTS
LISTEND
UI18608 COVER LETTER END
UI18639 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16424 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Abend 04E-00D31109 DSNLCCNR:000C. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a DB2 for z/OS application executes a read-only query
against a remote DB2 for z/OS location, a performance
improvement capability called "extra query block" processing
can be triggered. To trigger this capability, applications
typically must utilize the OPTIMIZE FOR N ROWS clause on a
read-only SELECT statement where N is large (which exceeds the
number of rows that can fit within one 32KB query reply block).
However, DB2 for z/OS ODBC applications, which run with the
LIMITEDBLOCKFETCH ODBC initialization keyword set to 1, may
also trigger this extra query block processing when the query
is sent to a remote DB2 for z/OS location.
If the requesting DB2 for z/OS application either fetches
all rows of the query result, or closes the cursor before
retrieving all rows, an abend will not occur.
However, if the application executes a different SQL statement
while the extra query blocks have yet to be retrieved, DB2 DDF
requester processing must then drain these pending query blocks
into memory (since only one operation can be ongoing on a
connection to a server at a time). As the application switches
between different SQL, DB2 DDF requester processing may
internally leave the connection with the remote location in an
invalid state. Once this invalid state has been set, any new
SQL from the application which then needs to be sent to the
remote location may lead to abend 04E-00D31109 DSNLCCNR:000C.
DB2 for z/OS DDF requester processing has been changed to
check and adjust, if necessary, the internal state of a
connection with a remote location.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16424
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCCNR PI16424
DSNLCSRR PI16424
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16424 DSNLCCNR DSNLCSRR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCCNR
DSNLCSRR
LISTEND
UI18639 COVER LETTER END
UI18668 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16067 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of Declare *
* Global Temporary Tables (DGTT). *
****************************************************************
* PROBLEM DESCRIPTION: IFCID 21 trace records showed that high *
* global contention on DGTT URID locks *
* (lock type '3E'x). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When requesting a DGTT URID lock, DB2 didn't properly specify
its scope. This gave the acquired lock a non-local attribute
and resulted in increased global lock contention events as
well as longer global lock contention class 3 elapsed time.
When requesting a DGTT URID lock, DB2 will now make sure
its scope is non-global.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16067
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISEGD PI16067
DSNISEGF PI16067
DSNISGNS PI16067
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16067 DSNISEGD DSNISEGF DSNISGNS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNISEGD
DSNISEGF
DSNISGNS
LISTEND
UI18668 COVER LETTER END
UI18674 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15079 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* use audit policies. *
* *
****************************************************************
* PROBLEM DESCRIPTION: 1.ABEND0C4 at DSNXAMAP OFFSET 069A *
* occurred when IFCID 361 trace is on *
* and SET SYSPARM command is issued to *
* change a security related parameter *
* online. *
* *
* 2.Incorrect IFCID 361 trace record *
* when SET SYSPARM command is used to *
* change a security related parameter. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1.ABEND0C4 at DSNXAMAP OFFSET 069A occurred when IFCID 361
trace is turned on by an audit policy and SET SYSPARM
command is issued to change a security related zparm online.
This is because incorrect address was used to access the
trace parameter list.
2.Incorrect IFCID 361 records may be written if the trace is
turned on by an audit policy and SET SYSPARM command is
issued to change a security related zparm online.
This is because DB2 did not process the trace return
code correctly.
DB2 code has been changed to use correct address to access
the parameter list and process the return code correctly
in the above scenarios.
Additional Keyword: IFCID361
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15079
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
1 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 <table
space>.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDMI PI15079
DSNXAMAP PI15079
DSNXIASQ PI15079
DSNXIATS PI15079
DSNZCMD1 PI15079
DSN9SCNP PI15079
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15079 DSNTDMI DSNXAMAP DSNXIASQ DSNXIATS DSNZCMD1 DSN9SCNP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDMI
DSNXAMAP
DSNXIASQ
DSNXIATS
DSNZCMD1
DSN9SCNP
LISTEND
UI18674 COVER LETTER END
UI18701 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI11064 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and DB2 11 *
* for z/OS in a data sharing coexistence *
* configuration. *
****************************************************************
* PROBLEM DESCRIPTION: CHECK INDEX on an object on DB2 10 *
* for z/OS is allowed when CHECK INDEX *
* on the same object is already running *
* on DB2 11 for z/OS in the same data *
* sharing group. This resulted in *
* ABEND04E RC00D70017 AT DSNPSCTC+X'09A0' *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a data-sharing configuration with one member running DB2 10
for z/OS and another member running DB2 11 for z/OS, CHECK INDEX
run on the DB2 10 member on a set of objects should be
incompatible with CHECK INDEX on the same objects running on
the DB2 11 member. DSNU180I should be issued in the job output
of the CHECK INDEX run on the DB2 10 member if the CHECK INDEX
on the DB2 11 member started first. DSNU180I was not issued and
the CHECK INDEX on the DB2 10 member was allowed to proceed.
ADDITIONAL KEYWORDS: MSGDSNU180I OFFSET09A0 DB2COEXIST
Modified compatibility checking to issue DSNU180I for a CHECK
INDEX on a DB2 10 for z/OS if CHECK INDEX on the same objects
is already running on another member at DB2 11 for z/OS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11064
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGUCC PI11064
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11064 DSNUGUCC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGUCC
LISTEND
UI18701 COVER LETTER END
UI18705 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17004 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users that *
* ordered and installed DB2 Accessories *
* Suite for z/OS Version 3 Release 2. *
1 ****************************************************************
* PROBLEM DESCRIPTION: This PTF will update member DSN5NOT3 *
* in the SDSNNOTC target library. *
* DSN5NOT3 is the notices file for *
* bundled components delivered in the *
* 5697-Q04, DB2 Accessories Suite for *
* z/OS Version 3 Release 2 product. For *
* a list of components in this release *
* see U.S. Software Announcement *
* letter 214-148 announced May 6, 2014. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After you apply this PTF the DSN5NOT3 notices file in target
library SDSNNOTC will be updated to reflect components
delivered in this 3.2 release of DB2 Accessories Suite.
COMPONENT: 5655-R1403-H2AF210
APARS FIXED: PI17004
SPECIAL CONDITIONS:
COPYRIGHT: 5655-R1403 COPYRIGHT IBM CORP. 2006 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF should be applied only by customers that ordered
and installed DB2 Accessories Suite Version 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.
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN5NOT3 PI17004
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17004 DSN5NOT3
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSN5NOT3
LISTEND
UI18705 COVER LETTER END
1
UI18723 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15304 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNV086E DB2 ABNORMAL TERMINATION *
* REASON=00F30420 running REORG utility *
* with FORCE option *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When REORG FORCE cancels a thread, the cancel operation picks up
the EB control block address without holding a system latch.
When the EB address is used for thread cancellation, the EB
address may have been reused by a different thread. As a result,
a wrong thread may get cancelled, and depending on the
activities of the cancelled thread, DB2 may be brought down.
DB2 has been fixed to acquire a system latch before picking up
the EB address for thread cancellation. The latch protects the
EB address from getting freed and reused until the cancel
operation is complete.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15304
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1DRA PI15304
DSNB1LDA PI15304
DSNB1LDN PI15304
DSNB1LRR PI15304
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15304 DSNB1DRA DSNB1LDA DSNB1LDN DSNB1LRR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DRA
DSNB1LDA
DSNB1LDN
DSNB1LRR
LISTEND
UI18723 COVER LETTER END
UI18727 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15366 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the DSNACCOX stored procedure with *
1 * objects in Persistent Read Only - PRO *
* restricted state. *
****************************************************************
* PROBLEM DESCRIPTION: DSNACCOX recommends COPY on an object *
* with Persistent Read Only, PRO *
* restricted state. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
DSNACCOX gives COPY, REORG, or RUNSTATS recommendation
regardless of the restricted state of the object, since the
restricted state can change between the time the recommendation
was given and the time the utility is executed.
However, a PRO restricted state is a persistent state and
therefore DSNACCOX should not give any COPY or REORG
recommendations.
DSNACCOX code is changed to avoid returning COPY and REORG
recommendation when the object is in PRO restricted state.
The following formulas in the Managing Performance manual
had been updated:
DSNACCOX formula for recommending a full image copy on a
table space
(((QueryType='COPY' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL') AND
| (Object is not in Persistent Read Only (PRO) status) AND
(ICType='F' OR ICType='B')) AND
(COPYLASTTIME IS NULL OR
REORGLASTTIME>COPYLASTTIME OR
LOADRLASTTIME>COPYLASTTIME OR
(CURRENT DATE-COPYLASTTIME)>CRDaySncLastCopy OR
((COPYUPDATEDPAGES×100)/NACTIVE>CRUpdatedPagesPct AND
(COPYUPDATEDPAGES>CRupdatedPagesAbs)) OR
((COPYCHANGES×100)/TOTALROWS>ICRChangesPct) OR
((QueryType='RESTRICT' OR QueryType='ALL' OR
QueryType='COPY' ) AND
(ObjectType='TS' OR ObjectType='ALL') AND
The table space is in COPY-pending status or informational
COPY-pending status))
DSNACCOX formula for recommending an incremental image copy on
a table space
((QueryType='COPY' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL') AND
|(Object is not in Persistent Read Only (PRO) status) AND
(ICType='I') AND
COPYLASTTIME IS NOT NULL) AND
(LOADRLASTTIME>COPYLASTTIME OR
REORGLASTTIME>COPYLASTTIME OR
((COPYUPDATEDPAGES×100)/NACTIVE>ICRUpdatedPagesPct) AND
(COPYUPDATEDPAGES>ICRUpdatedPagesAbs)) OR
((COPYCHANGES×100)/TOTALROWS>ICRChangesPct)
DSNACCOX formula for recommending a REORG on a table space
(((QueryType='REORG' OR QueryType='ALL') AND
1 (ObjectType='TS' OR ObjectType='ALL') AND
| (Object is not in Persistent Read Only (PRO) status)) AND
(REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR
(NACTIVE IS NULL OR NACTIVE > 5) AND
((((REORGINSERTS×100)/TOTALROWS>RRTInsertsPct) AND
REORGINSERTS>RRTInsertsAbs) OR
(((REORGDELETE×100)/TOTALROWS>RRTDeletesPct) AND
REORGDELETE>RRTDeletesAbs) OR
(REORGCLUSTERSENS > 0 AND (REORGUNCLUSTINS×100)/
TOTALROWS>RRTUnclustInsPct) OR
(REORGDISORGLOB×100)/TOTALROWS>RRTDisorgLOBPct OR
(SPACE×1024)/DATASIZE>RRTDataSpaceRat OR
((REORGNEARINDREF+REORGFARINDREF)×100)/TOTALROWS>
RRTIndRefLimit OR
REORGMASSDELETE>RRTMassDelLimit OR
EXTENTS>ExtentLimit)) OR
((QueryType='REORG' OR QueryType='ALL') AND
ObjectType='ALL' AND
overflow index for hash access is used, and
(overflow index TOTALENTRY x 100) / TOTALROWS >
RRTHashOvrFlwRatio)) OR
((QueryType='RESTRICT' OR QueryType='ALL' OR
QueryType='REORG' ) AND
(ObjectType='TS' OR ObjectType='ALL') AND
The table space is in advisory or informational reorg
pending status)
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15366
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
DB2BIND:
***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
DB2BIND:
***Action for PI06664:
See PI06664 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PI06664:
1 (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
DOCUMENTATION:
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.
ACTION:
***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.
ACTION:
***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
ACTION:
After you apply the PTF for APAR PM61574, Non Partitioned Index
is no longer recommended for reorg or runstats when chklevel
1 32 is specified and any of the ts partitioned is recommended for
reorg or runstats.
ACTION:
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.
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@CCOX PI15366
DSNACCOX PI15366
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15366 DSN@CCOX DSNACCOX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNACCOX
MACROS
DSN@CCOX
LISTEND
UI18727 COVER LETTER END
UI18730 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14427 -
****************************************************************
* USERS AFFECTED: DB2 10 for zOS and DB2 11 for zOS users *
* who run stored procedures in debug mode *
* with XML parameters or variables *
****************************************************************
* PROBLEM DESCRIPTION: ABEND 0C4-00000038 at DSNNORSQ +1004 *
* when using a stored procedure in debug *
* mode with XML parameters or variables. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend occurs because the internal XML descriptor is
overwritten.
DB2 is modified to prevent the XML descriptor overlay.
1 Addtional keywords: SQLSP SQLSTOREDPROC ABEND0C4
DEBUGMODE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14427
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDBG PI14427
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14427 DSNXEDBG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDBG
LISTEND
UI18730 COVER LETTER END
UI18732 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18129 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of UNLOAD FROMCOPYDDN *
****************************************************************
* PROBLEM DESCRIPTION: UNLOAD FROMCOPYDDN with the image copy *
* data set on tape abends with ABENDS0C4 *
* RC38 at DSNUULJA +x'0A12' *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
UNLOAD FROMCOPYDDN with the image copy data set on tape abended
with an ABEND0C4 at DSNUULJA OFFSET0A12. The error was due to
specifying a non-existent DD card name for the image copy data
set. Because the DD card did not exist, UNLOAD processing did
not create an internal control block, but set some internal
pointers as if it did and abended when invalid storage was
referenced.
Additional keywords: MSGDSNU035I
UNLOAD FROMCOPYDDN has been changed to not set certain internal
pointers when a DD card name is specified but does not exist.
UNLOAD will now issue message DSNU035I - UNABLE TO FIND DD CARD
FOR DDNAME n and end with RC8.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18129
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUUNLD PI18129
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18129 DSNUUNLD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUUNLD
LISTEND
UI18732 COVER LETTER END
UI18756 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13863 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* of SELECT statements that include the *
* EBCDIC_STR built-in function with a *
* LOB argument. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E20009 at DSNXRSB2 *
* DSNSVSFB OFFSET0898 can occur for a *
* query that includes the EBCDIC_STR *
* built-in function with a LOB column *
* argument. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E20009 at DSNXRSB2 DSNSVSFB OFFSET0898 can occur
for a query that contains the EBCDIC_STR built-in function of a
LOB column.
The following example illustrates a failing case where TEXT is
a LOB column.
SELECT EBCDIC_STR(TEXT)
FROM T1;
If the input to the EBCDIC_STR built-in function is large
enough, the above query can result in the above failure.
The code in DB2 was modified to correct the problem which can
lead to the failure.
Additional Keywords: SQLLOB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13863
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSNXRSB2 PI13863
DSNXRS39 PI13863
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13863 DSNXRSB2 DSNXRS39
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRSB2
DSNXRS39
LISTEND
UI18756 COVER LETTER END
UI18766 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13612 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* customers who use IBM Enterprise COBOL *
* for z/OS Version 5.1 are affected by this *
* change. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 for z/OS installation support for *
* IBM Enterprise COBOL for z/OS Version *
* 5.1 (COBOL V5.1). *
* *
* One or more of the following errors *
* occurs when using COBOL V5.1 to prepare *
* DB2 COBOL programs: *
* * Preparation of DB2 COBOL programs *
* using the DSNHICOB JCL proc fails in *
* proc step COB (program IGYCRCTL) *
* with return code 106 due to abend *
* 0106 with reason code 0B and these *
* error messages: *
* IEC130I SYSMDECK DD STATEMENT *
* MISSING *
* IGYSI5013-U An error occurred *
* while attempting to open *
* file "SYSMDECK".
*
* *
* * Preparation of DB2 COBOL programs *
* using the DSNHICOB JCL proc fails in *
* proc step COB (program IGYCRCTL) *
* with return code 16 and these error *
* messages: *
* IGYOS5000-U The compilation was *
* terminated due to an *
* uncorrectable error *
* condition. *
* IGYOS5124-U A required compiler *
* work file, "SYSUT8 ",
*
* was not allocated. *
1 * *
* * Preparation of DB2 COBOL programs *
* using the DSNHICOB JCL proc fails in *
* proc step LKED (program IEWL) with *
* return code 12 and this error *
* message: *
* IEW2606S 4B39 MODULE INCORPORATES *
* VERSION 3 PROGRAM OBJECT *
* FEATURES AND CANNOT BE *
* SAVED IN LOAD MODULE *
* FORMAT. *
* *
* * Preparation of DB2 COBOL programs *
* using the DSNH program preparation *
* CLIST fails with return code 12 due *
* to abend 0C03 with reason code 4 and *
* these error messages: *
* IKJ56641I IGYCRCTL ENDED DUE TO *
* ERROR+ *
* IKJ56641I SYSTEM ABEND CODE C03 *
* REASON CODE 00000004 *
* IEC130I SYSMDECK DD STATEMENT *
* MISSING *
* IGYSI5013-U An error occurred *
* while attempting to open *
* file "SYSMDECK".
*
* *
* * Preparation of DB2 COBOL programs *
* using the DSNH program preparation *
* CLIST fails with return code 16 and *
* these error messages: *
* DSNH740I ======= IBMCOB FINISHED, *
* RC = 16 ======= *
* DSNH759I DSNH TERMINATING, IBMCOB *
* RC = 16 *
* IGYOS5000-U The compilation was *
* terminated due to an *
* uncorrectable error *
* condition. *
* IGYOS5124-U A required compiler *
* work file, "SYSUT8 ",
*
* was not allocated. *
* *
* * Preparation of DB2 COBOL programs *
* using the DSNH program preparation *
* CLIST with option PRELINK(YES) *
* fails with return code 12 and *
* these error messages: *
* DSNH740I ======= PRELINK FINISHED, *
* RC = 12 ======= *
* DSNH759I DSNH TERMINATING, PRELINK *
* RC = 12 *
* SEVERE ERROR EDC4000: Unable to *
* open DD:SYSIN. *
* *
* * Preparation of DB2 COBOL programs *
1 * using the DSNH program preparation *
* CLIST with option PRELINK(NO) *
* fails with return code 16 and *
* these error messages: *
* DSNH740I ======= LINK FINISHED, *
* RC = 16 ======= *
* DSNH759I DSNH TERMINATING, LINK *
* RC = 16 *
* due to system abend 0C4, reason code *
* 10 in z/OS binder module IEWBIND. *
* *
* * Preparation of DB2 COBOL programs *
* using the DSNH program preparation *
* CLIST fails with return code 12 and *
* these error messages: *
* DSNH740I ======= LINK FINISHED, *
* RC = 12 ======= *
* DSNH759I DSNH TERMINATING, LINK *
* RC = 12 *
* IEW2606S 4B39 MODULE INCORPORATES *
* VERSION 3 PROGRAM OBJECT *
* FEATURES AND CANNOT BE *
* SAVED IN LOAD MODULE *
* FORMAT. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
DB2 for z/OS installation provides a number of JCL procs for
preparing DB2 application programs with a variety of programming
languages. In particular, the DSNHICOB proc contains steps for
precompiling and compiling DB2 COBOL programs using IBM
Enterprise COBOL and further steps for prelinking the object
module and link-editing the load module.
DB2 for z/OS also provides the DSNH CLIST for preparing
application programs. DSNH calls another CLIST, DSNHC, to
perform the compilation phase of the preparation.
The arrival of IBM Enterprise COBOL for z/OS Version 5.1
(COBOL V5.1) impacts DSNHICOB, DSNH,and DSNHC as follows:
* A library-processing output file (SYSMDECK) DD must now be
allocated. The SYSMDECK file receives the output from library
processing, that is, the expansion of COPY, BASIS, REPLACE,
and EXEC SQL INCLUDE statements. Without this DD statement,
the COBOL V5.1 compiler terminates with either
- abend code 0106 and reason code 0B
- abend code 0C03 and reason code 4
and these messages:
IEC130I SYSMDECK DD STATEMENT MISSING
IGYSI5013-U An error occurred while attempting to open
file "SYSMDECK".
* Additional system utility DDs, SYSUT8 - SYSUT15, must now be
allocated. Otherwise, the COBOL V5.1 compiler terminates
with return code 16 and these messages:
IGYOS5000-U The compilation was terminated due to an
1 uncorrectable error condition.
IGYOS5124-U A required compiler work file, "SYSUTx ",
was not allocated.
where 'x' is 8, 9, 10, 11, 12, 13, 14, or 15.
* The DSNHC CLIST must now pass object code from the COBOL
compiler to the prelinker or link-editor in a work file data
set that is defined with a fixed block record format and a
logical record length of 80. Otherwise:
- if the PRELINK(YES) option was specified, the DSNH CLIST
will terminate with return code 12 and severe error
EDC4000 (Unable to open DD:SYSIN)
- if the PRELINK(NO) option was specified, the DSNH CLIST
will terminate with return code 16 due to system abend 0C4
reason 10 by the z/OS binder.
* Executables must be program objects. Prelinking and link-
editing of load modules are no longer supported. Program
objects must reside in a PDSE. Otherwise, the z/OS binder
terminates with return code 12 and this error message
message:
IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT
FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT.
This APAR provides the following DB2 10 and DB2 11 installation
changes in support of COBOL V5.1:
* The DSNHC CLIST now allocates the additional DD statements
needed by COBOL V5.1. It is also corrected 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.
* Panel DSNTIPU (DATA SET NAMES PANEL 2) now provides a field,
COBOL LE PRELINKER PHASE, for indicating whether COBOL
program preparation should include prelinking. Valid settings
are:
- YES: This setting is acceptable for supported versions of
IBM COBOL prior to COBOL V5.1. It causes the DB2
installation CLIST to continue to customize jobs as
it did prior to this APAR.
==> This is the default setting
- NO : This setting is required for COBOL V5.1 and acceptable
for prior, supported versions. It causes the DB2
installation CLIST, during editing of the DSNHICOB JCL
proc in job DSNTIJMV, to insert the additional DD
statements needed by COBOL V5.1 to the compiler proc
step and to remove the prelinker proc step entirely.
The SYSLMOD DD of the LKED proc step must allocate a
PDSE. Also, during editing of IVP job DSNTEJ5C, the
installation CLIST will change the DSNH (program
preparation) CLIST PRELINK option setting from YES to
NO.
* Job DSNTIJIN now defines the DB2 sample application load
library, prefix.RUNLIB.LOAD, as a PDSE rather than a PDS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13612
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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
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
1 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
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 <x>
Change <x> to NO if you want the DB2 installation CLIST
to configure installation jobs for COBOL V5.1. Otherwise,
change <x> 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
1 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),
// 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)
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI13612
DSNHC PI13612
DSNTIDXA PI13612
DSNTIDXB PI13612
DSNTIJIN PI13612
DSNTINST PI13612
DSNTINS1 PI13612
DSNTINS2 PI13612
DSNTINS3 PI13612
1 DSNTIPU PI13612
DSNTXAZP PI13612
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13612 DSN@XAZP DSNHC DSNTIDXA DSNTIDXB DSNTIJIN DSNTINST
DSNTINS1 DSNTINS2 DSNTINS3 DSNTIPU DSNTXAZP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
MACROS
DSN@XAZP
DSNHC
DSNTIDXA
DSNTIDXB
DSNTIJIN
DSNTINST
DSNTINS1
DSNTINS2
DSNTINS3
DSNTIPU
LISTEND
UI18766 COVER LETTER END
UI18772 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15560 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of compressed *
* table spaces *
****************************************************************
* PROBLEM DESCRIPTION: DB2 abnormally terminated with *
* ABEND04F RC00F30420, following *
* ABEND04E RC00E50013, RC00E20028, *
* RC00E20005, RC00E30001, and RC00C9021C *
* during INSERT activity on a table *
* space defined as COMPRESS YES. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User created a table space with COMPRESS YES and began
running INSERTs into it. Prior to the INSERTs, the existing
data in the table space had been corrupted accidentally by the
user through the invalid use of DSN1COPY.
The INSERT job eventually issued an ABEND04E 00C9021C, which
was expected due to the data inconsistencies.
This immediately led to a series of ABEND04E ABENDs:
00E20028 (unexpected data in stack storage)
00E50013 (DB2 execution unit abended)
00E20005 (invalid block for free request)
00E30001 (inconsistency detected by service controller)
Finally, DB2 terminated with ABEND04F 00F30420 (failure during
1 deferred end-of-task processing).
This problem was caused by incorrect error handling of the
original abend.
Error handling logic was corrected in the routine that manages
dictionary building during INSERT for objects defined with
COMPRESS YES.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15560
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUZLCR PI15560
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15560 DSNUZLCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUZLCR
LISTEND
UI18772 COVER LETTER END
UI18782 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15861 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS or DB2 11 for *
* z/OS who use IBM DB2 Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE=-4742, SQLERRP=DSNXONZB might *
* occur when a statement contains tables *
* that are of different support levels. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a statement contains tables that are on different
support levels, SQLCODE=-4742, SQLERRP=DSNXONZB might occur.
For example, if a query to be accelerated is
SELECT * FROM T1, T2 FETCH FIRST 5 ROWS;
and the accelerated table T1 on the accelerator is on support
level 3, while T2 on the same accelerator is on support level
2, then SQLCODE=-4742, SQLERRP=DSNXONZB might occur.
Additional Keywords:
IDAAV4R1/K
This APAR fix will prepare/bind the query correctly with
consideration of possible different table support levels
on the same accelerator, which eliminates the issuing of
SQLCODE=-4742 from SQLERRP=DSNXONZB.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15861
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXONZA PI15861
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15861 DSNXONZA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXONZA
LISTEND
UI18782 COVER LETTER END
UI18806 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12594 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users of *
* *
* -DISPLAY GROUP *
* *
* command when the DB2 system is in *
* Point In Time Recovery (PITR) state. *
****************************************************************
* PROBLEM DESCRIPTION: When the DB2 is in PITR, *
* *
* -DISPLAY GROUP *
* *
* shows SPT01 INLINE LENGTH 0 even *
* though the inline length has not *
* been changed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DB2 Directory and Catalog is not accessible when the DB2
system is in PITR state. The information of SPT01 INLINE
LENGTH therefore is not available.
The message from DISPLAY GROUP should state that the resource
is unavailable and should include the reason code, resource
type and resource name that is not available instead of
displaying the inline length 0.
DB2 has been modified so that the message DSN7100I indicates
the SPT01 INLINE LENGTH is not available and including
the reason code, type of object and the object name when DB2
is in PITR state.
Additionally, when DB2 is in ENFM mode, DSN7100I also
displays the mew function mode enablement information of
each catalog and directory table space when DETAIL(*)
1 option is specified in the DISPLAY GROUP command.
This information is also unavailable when DB2 is in PITR
state.
DSN7100I message is modified as follows:
1. When the DB2 is in PITR state, the SPT01 INLINE LENGTH
information is replaced with :
SPT01 INLINE LENGTH INFORMATION NOT AVAILABLE
REASON 00C9000A
TYPE 00000200
NAME DSNDB01.DBD01
2. When the DB2 is in ENFM mode and PITR state, the table
space information is replaced with :
TABLE SPACE NEW FUNCTION ENABLEMENT INFORMATION NOT AVAILABLE
REASON 00C9000A
TYPE 00000200
NAME DSNDB01.DBD01
Additional Keywords: MSGDSN7100I RC00C9000A
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12594
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNFMDIR PI12594
DSNF7DIR PI12594
DSNUECMJ PI12594
DSN7GCMD PI12594
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12594 DSNFMDIR DSNF7DIR DSNUECMJ DSN7GCMD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFMDIR
DSNF7DIR
DSNUECMJ
DSN7GCMD
LISTEND
UI18806 COVER LETTER END
UI18820 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15309 -
****************************************************************
* USERS AFFECTED: DB2 users of stored procedures and *
* User Defined Functions (UDFs). *
1 ****************************************************************
* PROBLEM DESCRIPTION: When a stored procedure goes into *
* recovery, the following problems *
* may occur: *
* - Stored procedure thread hang *
* - s30d-0 psw=070c0000813c5432 dsnvsrrx *
* - DB2 crash *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a stored procedure goes into recovery, there is a
chance that the recovery process is attempting to get an
invalid latch due to a bad DB2 control block. So the
stored procedure thread suspends with no chance of waking
up. Later, when the thread is going through EOM for the
ASID, it is still hung on this invalid latch and then DB2
tries to terminate it with no success. After trying for
several times, DB2 crashes.
DB2 stored procedure recovery process has been fixed so that
the stored procedure thread won't suspend on an invalid latch
in case the DB2 control block is bad.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15309
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9CAC PI15309
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15309 DSNX9CAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9CAC
LISTEND
UI18820 COVER LETTER END
UI18850 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18062 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS or DB2 11 for z/OS users *
* with queries containing range predicates *
* or queries running with parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: During query optimization failed *
* access to SYSIBM.SYSCOLSTATS may result *
* in one of the following abends. *
* ABEND04E RC00C90101 *
* AT DSNIDM.DSNITCUS ERQUAL5002 *
* ABEND0C4 AT DSNIDM.DSNITCUS+0162 *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
During query optimization DB2 might access SYSIBM.SYSCOLSTATS
for queries with range predicates or queries eligible for
query parallelism. If the access to SYSIBM.SYSCOLSTATS fails
(e.g. due to a timeout) one of the following abends may occur.
ABEND04E RC00C90101 AT DSNIDM.DSNITCUS ERQUAL5002
ABEND0C4 AT DSNIDM.DSNITCUS+0162
The abends are a result of an uninitialized variable and as
such may be intermittent.
The caller to DSNITCUS when this problem occurs will be DSNXOCN,
DSNXOLCM, or DSNXOLM1.
Additional Keywords:
SQLSTATS
DB2 code was corrected to initialize the problem variable.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18062
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCN PI18062
DSNXOLCM PI18062
1 DSNXOLM1 PI18062
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18062 DSNXOCN DSNXOLCM DSNXOLM1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCN
DSNXOLCM
DSNXOLM1
LISTEND
UI18850 COVER LETTER END
UI18907 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17460 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those utilizing trusted *
* contexts for inbound TCP/IP connections. *
****************************************************************
* PROBLEM DESCRIPTION: Periodic DSNL513I messages issued *
* from DSNXATIM with an invalid ERRNO *
* value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A trusted context can be defined at a DB2 for z/OS server where
its usage is to be verified against specific inbound client
network addresses. The network addresses to be trusted are
attributes of the trusted context.
To validate the trusted context usage, DB2 utilizes the UNIX
System Services (USS) getaddrinfo callable service to determine
the IP addresses associated with the domain name specified in
the trusted context definition. The client IP address is
validated against the IP addresses that have been determined.
If the getaddrinfo is not successful, a DSNL513I message
should be issued to indicate that the domain name is not
valid. Depending on the residual contents of storage, the
message will either not be issued at all, or it will contain
an incorrect ERRNO value (although the invalid domain name
value is correctly reported).
DB2 is changed to initialize storage such that the DSNL513I
message will be issued, if necessary, and will reflect the
correct ERRNO value.
Note: The DSNL513I message will continue to be reported until
either the trusted context is altered to remove the invalid
domain name or the domain name and IP address(es) association
is corrected. The message, however, will be reported at most
once every five minutes.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17460
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLIDNS PI17460
DSNLILE PI17460
DSNLILNR PI17460
DSNXATIM PI17460
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17460 DSNLIDNS DSNLILE DSNLILNR DSNXATIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLIDNS
DSNLILE
DSNLILNR
DSNXATIM
LISTEND
UI18907 COVER LETTER END
UI18914 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19102 -
****************************************************************
* USERS AFFECTED: All users of the help panel for DB2 for z/OS *
* installation or DB2I. *
****************************************************************
* PROBLEM DESCRIPTION: The help panel for installation or *
* DB2I, DSN4HELP, contains pointers to *
* the Information Management for z/OS *
* Solutions Information Center. The *
* panel should point to the IBM *
* Knowledge Center. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Help panel DSN4HELP has references to the Information Management
Software for z/OS Solutions Information Center and the URL for
that information center. The help panel needs to point to the
DB2 for z/OS collection in the IBM Knowledge Center instead.
In help panel DSN4HELP, references to the Information Management
for z/OS Software for z/OS Solutions Information Center were
changed to the DB2 for z/OS collection in the IBM Knowledge
Center.
COMPONENT: 5740-XYR00-JDBAA14
APARS FIXED: PI19102
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSN4HELP PI19102
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19102 DSN4HELP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSN4HELP
LISTEND
UI18914 COVER LETTER END
UI18957 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16442 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users who use *
* the WHEN clause in a BEFORE or AFTER *
* trigger where the WHEN clause references *
* the name of a column of the triggering *
* table *
****************************************************************
* PROBLEM DESCRIPTION: The result of the trigger can be *
* unpredictable if the WHEN clause in *
* a BEFORE or AFTER trigger 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 OLD or NEW correlation *
* name and the OLD or NEW *
* correlation name is the same as *
* the triggering table name. *
* *
* 2. The referenced name is qualified *
* by the triggering table name *
* where the name is different from *
* the OLD or NEW correlation name. *
* *
* 3. The referenced name is not *
* qualified by the OLD or NEW *
* correlation name and the OLD or *
* NEW correlation name is defined. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The result of the trigger can be unpredictable if the WHEN
clause in a BEFORE or AFTER trigger 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 OLD or NEW
1 correlation name and the OLD or NEW correlation name is
the same as the triggering table name.
2. The referenced name is qualified by the triggering table
name where the name is different from the OLD or NEW
correlation name.
3. 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 three cases just mentioned)
CREATE TABLE T1(C1 INT, C2 INT);
1. 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)
...
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 resolved to a new
transition variable but it's left unresolved.
The result of each trigger is unpredictable.
2. CREATE TRIGGER TRIG3
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 T1.C2 FROM SYSIBM.SYSDUMMY1))
...
Currently T1.C2 should have received SQLCODE -206, or
T1.C2 could have resolved to a global variable if
APPLCOMPAT in effect is 'V11R1', but it is left
unresolved. The result of the trigger is unpredictable.
3. CREATE TRIGGER TRIG4
NO CASCADE BEFORE UPDATE OF C1 ON T1
REFERENCING OLD AS OLD_ROW
NEW AS NEW_ROW
FOR EACH ROW
1 MODE DB2SQL
WHEN(NEW_ROW.C1 = (SELECT C2 FROM SYSIBM.SYSDUMMY1))
...
Currently C2 should have received SQLCODE -203, or
C2 could have resolved to a global variable if
APPLCOMPAT in effect is 'V11R1', but it is left
unresolved. The result of the trigger is unpredictable.
DB2 has been modified to ensure the above examples are
processed correctly.
Additional keywords: SQLTRIGGER SQLWHEN SQLBEFORE SQLAFTER
SQLUNPREDICTABLE SQLTRANSITION
SQLVARIABLE SQLCODE206 SQLGLOBALVAR
SQLGLOBAL SQLQUALIFIER
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16442
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
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.
1
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.
ACTION:
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)
...
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
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXORSO PI16442
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16442 DSNXORSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORSO
LISTEND
UI18957 COVER LETTER END
UI18960 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12398 -
****************************************************************
* USERS AFFECTED: All DB2 V10 and V11 for z/OS NFM users who *
* perform insert operations on Universal *
* Table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: Insert performance degradation with *
* high get page count when using *
* Multi-row insert operation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the exhaustive search prior to the physical extend of
the data set, the Multi-Row insert operation encounters a high
get page count. In this case, insert operation fails to find
available space to insert and will search the same set of
space map pages or data pages for each insert operation within
the same Muli-Row insert statement.
As a result, a high get page count occurs for each Multi-Row
Insert statement.
During the exhaustive search step within each Multi-Row insert
statement, the insert operation will remember the last
inserted position. So the subsequent insert operation within
the same statement will use the prior position as the starting
point for exhaustive search.
******** Note ********
This is a forward fit of V9 apar PI06926.
******** Note ********
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12398
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICUBC PI12398
DSNISGSC PI12398
DSNISRTI PI12398
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12398 DSNICUBC DSNISGSC DSNISRTI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICUBC
DSNISGSC
DSNISRTI
LISTEND
UI18960 COVER LETTER END
UI18990 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15994 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of SPANNED data with LOAD and UNLOAD. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND878 DSNUGBAC during LOAD DATA *
* INCURSOR FORMAT SPANNED YES. *
* LOAD INCURSOR is not valid with *
* FORMAT SPANNED YES. *
* *
* SPANNED YES is not included in the *
* SYSPUNCH data set generated for an *
* UNLOAD SPANNED YES FROMCOPY utility. *
* UNLOAD FROMCOPY or FROMCOPYDDN is *
* not valid with SPANNED YES. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
ABENDS878 DSNUGBAC when a LOAD DATA INCURSOR FORMAT SPANNED YES
is run. SPANNED records are not valid with the LOAD INCURSOR /
Crossloader (xloader) utility.
UNLOAD FROMCOPY or FROMCOPYDDN with SPANNED YES was run
successfully. However, the LOAD utility statement in the
SYSPUNCH data set did not include FORMAT SPANNED YES.
SPANNED YES is not valid with UNLOAD FROMCOPY or FROMCOPYDDN.
LOAD DATA INCURSOR FORMAT SPANNED YES will now issue MSGDSNU070I
DSNU070I -
KEYWORD OR OPERAND 'SPANNED YES' INVALID WITH 'INCURSOR'
LOAD DATA FORMAT SPANNED YES INTO TABLE PART n INCURSOR will
1 now issue MSGDSNU070I
DSNU070I -
KEYWORD OR OPERAND 'SPANNED YES' INVALID WITH 'PART INCURSOR'
UNLOAD FROMCOPY SPANNED YES or UNLOAD FROMCOPYDDN SPANNED YES
will now issue MSGDSNU070I.
DSNU070I -
KEYWORD OR OPERAND 'FROMCOPY' INVALID WITH 'SPANNED YES'
DSNU070I -
KEYWORD OR OPERAND 'FROMCOPYDDN' INVALID WITH 'SPANNED YES'
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15994
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDDF PI15994
DSNUGDDS PI15994
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15994 DSNUGDDF DSNUGDDS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDDF
DSNUGDDS
LISTEND
UI18990 COVER LETTER END
UI18992 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17974 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the CHECK DATA utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40012 DSNUGCKP OFFSET1706 *
* with RC00C90004 during CHECK DATA *
* TABLESPACE AUXERROR REPORT SCOPE ALL. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A CHECK DATA TABLESPACE AUXERROR REPORT SCOPE ALL abended with
an ABEND04E RC00E40012 DSNUGCKP +x'1706' with RC00C90004. The
table with the failure had a LOB column but did not have any XML
columns. The abend occurred when CHECK DATA was executing a
code path specific to XML column processing and used residual
storage for an object identifier.
CHECK DATA has been modified to qualify the code path for XML
1 specific code.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17974
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUKSCT PI17974
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17974 DSNUKSCT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUKSCT
LISTEND
UI18992 COVER LETTER END
UI18994 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13727 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: When query is using RID list access, *
* and work file is used to store the RIDs *
* after a RID list overflow has occurred, *
* the RID work file may not be freed *
* until COMMIT/ROLLBACK time, causing the *
* unnecessary accumulation of work file *
* resources. In addition, an ABEND 0C4 in *
* in DSNIDM.DSNISRID may be seen when *
* DB2 reaches internal work file OBID *
* limit. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When list prefetch or multiple index access are used in the
access path, and when RID overflow has occurred, DB2 could use
a temporary work file to store the RIDs (instead of a RID Pool)
in order to continue the RID list access.
In some situations, this temporary work file may not be freed
until the COMMIT/ROLLBACK time (for example when application
CLOSEs the cursor before consuming all of the rows in the result
set).
Thus, in certain situations, especially when COMMITs are rare,
accumulation of work file resources is possible which could
lead to "resource unavailable" error (for instance when
internal work file OBID limit is reached).
As a result, DSNT501I message (RUA REASON 0000006C) could be
issued. Also, an ABEND ABENDS0C4 00000004 RC04 in DSNISRID
OFFSET0290 could be seen.
1 Hybrid join and Pairwise join (dynamic index anding)
are not affected by this issue.
DB2 has been fixed to clean up temporary work file on CLOSE.
Additional Keywords:
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13727
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIWKFD PI13727
DSNXGRTS PI13727
DSNXRRID PI13727
DSNXSFIN PI13727
DSNXSFUN PI13727
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13727 DSNIWKFD DSNXGRTS DSNXRRID DSNXSFIN DSNXSFUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWKFD
DSNXGRTS
DSNXRRID
DSNXSFIN
DSNXSFUN
LISTEND
UI18994 COVER LETTER END
UI19024 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15739 -
****************************************************************
* USERS AFFECTED: All DB2 9, DB2 10, and DB2 11 for z/OS users *
* of multi-row insert (MRI) in the distributed *
* environment. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect values can be inserted into *
* a table, located in another remote DB2 *
1 * for z/OS, via a 3-part name when a JDBC *
* application uses the z/OS Type 2 IBM *
* Data Server Driver for JDBC and SQLJ *
* to connect (to DB2) to perform a batch *
* insert of DOUBLE values. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect DOUBLE values can be inserted into a DOUBLE column
(defined for a table located in a remote DB2 for z/OS) via a
3-part name when a JDBC application uses the z/OS Type 2 IBM
Data Server Driver for JDBC and SQLJ to connect to DB2 to
perform a 'batch' insert.
The following example helps to illustrate the problem.
1. Assume the existence of a Table TAB1 at location STLEC2 that
is defined with a DOUBLE column COL1.
2. A JDBC application contains the following insert statement
with the addBatch and executeBatch methods to insert Double
values into table STLEC2.TAB1 from location STLEC1.
//connect the STLEC1 with JDBC type 2 driver.
url = "jdbc:db2:STLEC1";
conn = DriverManager.getConnection ( url, user, password );
Statement stmt = conn.createStatement();
String sql="insert into STLEC2.SYSADM.TAB1 values(?)";
PreparedStatement ps = conn.prepareStatement(sql);
for(int i=0;i<5;i++)
{
ps.setDouble(1,12.44);
ps.addBatch();
}
ps.executeBatch();
3. Perform the insert.
The result of the above insert is that the incorrect value
1.596875000000000E-1 is inserted (5 times) into COL1 for TAB1 at
STLEC2.
The incorrect inserted value(s) occur because the code logic
needed to convert the binary float to hexadecimal float is
missing.
Please note:
1. This problem can occur with any numeric target data type,
not just DOUBLE.
2. This problem can occur with any type of application that uses
DB2 for z/OS as the requester, not just the JDBC application.
1 The code in DB2 is modified to add the needed conversion logic
to prevent the incorrect insert.
Additional Keywords: SQLINSERT JCCT2ZOS SQLMULTIROW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15739
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRIHR PI15739
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15739 DSNXRIHR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRIHR
LISTEND
UI19024 COVER LETTER END
UI19027 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16895 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for zOS users of *
* IFCID 66 trace and UPDATE / DELETE *
* statement in a distributed environment. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 incorrectly records IFCID 66 *
* trace for a remotely executed UPDATE or *
* DELETE statement when no row is *
* qualified. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 traces an IFCID 66 record on the start of execution of a
close cursor, for both explicit and implicit close, of a
statement.
For UPDATE / DELETE statements, DB2 issues SQLCODE 100 if no row
is qualified.
In the reported case, when UPDATE / DELETE statements was
remotely executed and no row was qualified, DB2 incorrectly
drove the implicit close process due to SQLCODE 100,
resulting in IFCID 66 tracing indicating implicit close
in QW0066IM field.
DB2 has been modified to avoid the implicit close process as
well as IFCID 66 tracing for UPDATE / DELETE statements.
1 Keywords: IFCID066 SQLUPDATE SQLDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16895
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEBR PI16895
DSNXEBR9 PI16895
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16895 DSNXEBR DSNXEBR9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXEBR9
LISTEND
UI19027 COVER LETTER END
UI19029 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15197 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V10 and V11 users of sort *
* work files, and work files created for *
* created global temporary tables (CGTT) *
* and trigger transition tables. *
****************************************************************
* PROBLEM DESCRIPTION: 1. ABEND04E RC00C90101, DSNGDVRT:500D *
* in DB2 for z/OS V10 and V11. *
* *
* 2. SQL ERROR CODE -404 for queries *
* utilizing work files for selecting LOB *
* columns, in DB2 for z/OS V10 and V11. *
* *
* 3. The following abends can occur in *
* DB2 for z/OS V11 during workfile *
* processing when the row size is close *
* to the 32K page size limit and the *
* table has variable length columns: *
* *
* 3.1. ABEND04E DSNIWKFL ERQUAL500F (for *
* CGTTs or trigger transition tables). *
* *
* 3.2. ABEND04E DSNISFW ERQUAL500B or *
* ABEND04E DSNISFW ERQUAL500C (for *
* aggregate function evaluations against *
* a sort workfile or CGTT). *
* *
* 3.3. ABEND04E DSNIWNRF ERQUAL505B (for *
* various sort workfiles). *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
1. The DSNGDVRT:500D abend happened due to an error in the
code's handling of adding the length of a length indicator
field to the total record length of a spanned workfile record,
resulting in an overflow of the length variable and
corruption of the length value. This error was detected
further down in the process and the abend was issued.
2. The -404 SQL error code happens due to a component
interface error which leads to the length of a varchar
column being interpreted as too long when the varchar
column represents a LOB column.
3. The other aforementioned abends can occur during workfile
processing when the row size is close to the 32K page size
limit and the table has long varchar columns.
This is due to DB2 mistakenly adding 4 bytes as length holder
for each variable length column, when it should be only 2
bytes. The resulting calculation mistakenly can indicate that
the workfile row is larger than 32K, and can lead to one of
the abends.
Code has been corrected to handle the length field
of varchar columns in a workfile record correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15197
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIWKFL PI15197
DSNXRIB9 PI15197
DSNXRID9 PI15197
DSNXRIHB PI15197
DSNXRIHD PI15197
DSNXRIHR PI15197
DSNXRIHS PI15197
DSNXRIS9 PI15197
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15197 DSNIWKFL DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR
DSNXRIHS DSNXRIS9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWKFL
DSNXRIB9
DSNXRID9
DSNXRIHB
DSNXRIHD
DSNXRIHR
DSNXRIHS
DSNXRIS9
1
LISTEND
UI19029 COVER LETTER END
UI19037 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM88171 -
****************************************************************
* USERS AFFECTED: All DB2 10 & 11 z/OS users of hash tables *
* (ORGANIZE BY HASH) *
****************************************************************
* PROBLEM DESCRIPTION: For DB2 10 NFM: *
* ABEND04E RC00C90101 DSNICUMW ERQUAL5003 *
* for a table with hash organization. *
* *
* For DB2 10 and V11 NFM: *
* Orphan child rows possible when parent *
* in a referential integrity relationship *
* is in a hash table space. *
* *
* For DB2 11 (CM/NFM): *
* ABEND04E RC00C90101 DSNIACCH ERQUAL5020 *
* in a table with hash organization. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a referential integrity relationship, orphan rows can occur
in a child table when inserting into the child table and the
parent table is a organized by hash.
When the parent table is organized by hash, DB2 will choose
hash access to locate the parent row during SQL INSERT or LOAD
utility. However, DB2 may use the wrong key to check for the
parent and possibly allow the insert/load to complete even
though the actual parent key does not exist, thus creating an
orphan row.
Subsequent access of the orphan row in the child table may
result in one or more of the report abends.
This APAR corrects DB2 RI constraint parent key check for an
SQL INSERT statement or LOAD utility, when using hash access.
statement and LOAD Utility.
Additional keywords: SQLINSERT SQLUPDATE SQLDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM88171
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIACCH PM88171
DSNICREL PM88171
DSNIRELI PM88171
DSNIRFNX PM88171
1 DSNIRIDR PM88171
DSNISDLE PM88171
DSNUKNFK PM88171
DSNURCRI PM88171
DSNXREOJ PM88171
DSNXRFF PM88171
DSNXRFN PM88171
DSNXROJ1 PM88171
DSNXRSFN PM88171
DSNXRSGB PM88171
DSNXRSJ PM88171
DSNXRSVW PM88171
DSNXRT1J PM88171
DSNXSBUC PM88171
DSNXSIND PM88171
DSNXSING PM88171
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM88171 DSNIACCH DSNICREL DSNIRELI DSNIRFNX DSNIRIDR DSNISDLE
DSNUKNFK DSNURCRI DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1
DSNXRSFN DSNXRSGB DSNXRSJ DSNXRSVW DSNXRT1J DSNXSBUC
DSNXSIND DSNXSING
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNICREL
DSNIRELI
DSNIRFNX
DSNIRIDR
DSNISDLE
DSNUKNFK
DSNURCRI
DSNXREOJ
DSNXRFF
DSNXRFN
DSNXROJ1
DSNXRSFN
DSNXRSGB
DSNXRSJ
DSNXRSVW
DSNXRT1J
DSNXSBUC
DSNXSIND
DSNXSING
LISTEND
UI19037 COVER LETTER END
UI19043 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM94699 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
1 * Specifically where DB2 10 for z/OS has *
* migrated to NFM, and/or reverted back to *
* CM* or ENFM*. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 10 for z/OS, operating as a *
* server, may provide (to remote client *
* environments) an inconsistent *
* representation of its DRDA Unicode *
* Manager support once DB2 has migrated *
* to NFM, and perhaps then fallen back *
* to CM* or ENFM*. *
* This may lead to the following DB2 *
* server symptoms: *
* . Message DSNL032I REASON=00D35000 *
* ERROR ID=DSNLZSEA0091 *
* . Message DSNL030I DSNLTSEC.30 *
* As a result of these server symptoms, *
* remote requester environments may also *
* report symptoms. Known symptoms *
* include: *
* . DB2 z/OS, 10 NFM or higher, *
* specific requesters: *
* - Message DSNL031I REASON=00D351FF *
* ERROR ID=DSNLZRPA0001 *
* . All requesters: *
* - SQLCODE -30073 or -30082. *
* The symptoms occur once DB2, or DDF, *
* has been recycled after a change in *
* the DB2 server migration mode. *
* The condition only seems to occur *
* relative to TCP/IP communications to *
* the DB2 server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Once a migration has occurred to V10 NFM, and DB2 or DDF has
been recycled, DB2/DDF, operating as a server, will now honor
"DRDA Unicode Manager" based network traffic from remote
requester environments.
A failing situation may then occur depending on whether the DB2
server operates as a stand alone subsystem or as a member of a
data sharing group.
. Stand alone subsystem.
Remote requester environments will then become aware that
the DB2 server can now support DRDA Unicode Manager based
traffic.
If DB2 falls back to CM* or ENFM*, and DB2 or DDF is
recycled, the DB2/DDF server will no longer honor DRDA
Unicode Manager based network traffic.
However, remote requester environments may still operate on
its prior knowledge that the DB2 server (still) does support
DRDA Unicode Manager based traffic and may therefore format
DRDA messages with this understanding.
The DB2/DDF server now considers this traffic as invalid and
issues a DSNL032I REASON=00D35000 ERROR ID=DSNLZSEA0091
message.
1 Note: The remote requester application will likely see this
error in the form of SQLCODE -30073.
A DB2 for z/OS requester will also likely issue a
DSNL031I REASON=00D351FF ERROR ID=DSNLZRPA0001 message.
Subsequent connections to the DB2 server may result in
message DSNL030I DSNLTSEC.30 due to authentication tokens
being encoded in an unexpected form.
Note: The remote requester application will likely see this
error in the form of SQLCODE -30082.
To resolve the inconsistency, the requester environment
typically must be recycled, or success has been also observed
by stopping the server environment (DB2 or DDF) and waiting
for an extended period (at least 5 minutes) before restarting
(the extended server outage may cause the remote requester to
reevaluate its knowledge of the DB2 server capabilities).
. Data sharing group.
Other members of the group that have not yet been recycled
will continue to report the absence of DRDA Unicode Manager
based network traffic support. As a result, remote requester
environments will be presented with an inconsistent
representation of the group support depending on which member
is accessed. The requester environment may therefore format
DRDA messages with an incorrect understanding relative to the
actual member that is accessed.
The DB2/DDF server member may detect this traffic as invalid
and issue a DSNL032I REASON=00D35000 ERROR ID=DSNLZSEA0091
message.
Note: The remote requester application will likely see this
error in the form of SQLCODE -30073.
A DB2 for z/OS requester will also likely issue a
DSNL031I REASON=00D351FF ERROR ID=DSNLZRPA0001 message.
Subsequent connections to the DB2 server may result in
message DSNL030I DSNLTSEC.30 due to authentication tokens
being encoded in an unexpected form.
Note: The remote requester application will likely see this
error in the form of SQLCODE -30082.
To resolve the inconsistency, all group members (that have
not yet been recycled) must be recycled (DB2 or DDF) in order
to allow all members to honor DRDA Unicode Manager based
network traffic, hence providing a consistent representation
of the DB2 group's server support.
A similar condition exists when DB2 has fallen back to CM* or
ENFM* and at least one member has been recycled (DB2 or DDF).
The recycled member(s) will no longer honor DRDA Unicode
Manager based network traffic which is inconsistent with
other members that have not yet been recycled.
In this case too, all group members (that have not yet been
recycled) must be recycled (DB2 or DDF) in order to allow all
members to no longer honor DRDA Unicode Manager based network
traffic, hence providing a consistent representation of the
DB2 group's server support.
It may be necessary for requester environments to be recycled
as well once a consistent DB2 group representation of support
has been established.
DB2 10 for z/OS has been changed to dynamically (with out
1 requiring a DB2/DDF restart) recognize a transition to NFM and
to immediately honor DRDA Unicode Manager based network traffic
support. Once in NFM, this support will remain, even if DB2
falls back to CM* or ENFM*.
This behavior applies to stand alone subsystems or all members
of a data sharing group since a DB2 V10 code base is known to
be present (even among all members) and hence DRDA Unicode
Manager based network traffic can be tolerated regardless of
migration mode (NFM, CM*, ENFM*).
Data Sharing users should be aware that this change can be
deployed to members as opportunity permits, but errors may
continue until this change can be deployed to all members of
the group.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM94699
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTEXC PM94699
DSNLTMIN PM94699
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM94699 DSNLTEXC DSNLTMIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTEXC
DSNLTMIN
LISTEND
UI19043 COVER LETTER END
UI19070 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12431 -
****************************************************************
* USERS AFFECTED: DB2 users of workfile database and *
* DECLARE GLOBAL TEMPORARY TABLE (DGTT) who *
* cancel a rollback *
****************************************************************
* PROBLEM DESCRIPTION: After cancelling a rollback of creating *
* a workfile/DGTT, the customer may see *
* an ABEND0C4 at DSNICMT2+25CA *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An internal control block is freed by rollback which could still
be referenced by workfile table OBDREC if the rollback was
cancelled. Referencing this control block could cause the above
abend.
DB2 code has been changed to free the control block when
workfile table OBDREC is freed to avoid accessing the freed
1 control block.
Additional keywords: SQLDGTT DGTT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12431
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCMT PI12431
DSNGDDRT PI12431
DSNGDLOG PI12431
DSNTADL PI12431
DSNTAEA PI12431
DSNXECW PI12431
DSNXECWA PI12431
DSNXECWU PI12431
DSNXEPLG PI12431
DSNXEUF0 PI12431
DSNXEWST PI12431
DSNXIDCL PI12431
DSNXMIT2 PI12431
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12431 DSNGDCMT DSNGDDRT DSNGDLOG DSNTADL DSNTAEA DSNXECW
DSNXECWA DSNXECWU DSNXEPLG DSNXEUF0 DSNXEWST DSNXIDCL
DSNXMIT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCMT
DSNGDDRT
DSNGDLOG
DSNTADL
DSNTAEA
DSNXECW
DSNXECWA
DSNXECWU
DSNXEPLG
DSNXEUF0
DSNXEWST
DSNXIDCL
DSNXMIT2
LISTEND
UI19070 COVER LETTER END
UI19075 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16783 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER utility on a list *
1 * containing index spaces. *
****************************************************************
* PROBLEM DESCRIPTION: Restart of a failed RECOVER utility *
* left all index spaces in CHECK PENDING *
* (CHKP) status and issued MSGDSNU563I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A successful restart of a RECOVER utility job after an abend
left all index spaces in CHECK PENDING (CHKP) status and issued
MSGDSNU563I (object is in check pending) even though all the
table spaces and index spaces are in the RECOVER list.
The issue occurs because RECOVER utility does not save the
relationship between table spaces and index spaces correctly
upon restart.
RECOVER utility was modified to correct the restart logic.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16783
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCAIN PI16783
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16783 DSNUCAIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCAIN
LISTEND
UI19075 COVER LETTER END
UI19080 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13724 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of optimization *
* hints. *
****************************************************************
* PROBLEM DESCRIPTION: Many 3rd party produced dynamic SQL *
* applications do not check or tolerate *
* +394/+395 SQLCODE when a query is *
* executing. This prevents the *
* successful use of statement hints, *
* since introducing a hint can result in *
* an application failure. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides 2 usability enhancements for optimization
hints.
1
1. Many applications do not handle SQLCODEs +394/+395 when the
optimization hint is applied to a dynamic SQL execution.
Therefore, these customers cannot use optimization hints to
influence access path selection for a dynamic query.
This APAR introduces subsystem parameter
SUPPRESS_HINT_SQLCODE_DYN to control whether SQLCODE +394/+395
is returned for a dynamic query with optimization hint applied.
Valid settings for SUPPRESS_HINT_SQLCODE_DYN 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.
Static queries and dynamic EXPLAIN statements are not affected
by this subsystem parameter. DB2 will continue to return
SQLCODEs +394/+395 when binding static queries or EXPLAINing
dynamic queries.
2. The cost estimation for a query with an optimization hint
applied may not be accurate but it is not indicated in EXPLAIN
output.
To improve the usability of cost estimation with optimization
hints, the cost estimation of a query with an optimization hint
applied will be marked as COST_CATEGORY "B" in
DSN_STATEMNT_TABLE. A new reason for putting the cost estimation
into cost category B is "OPTIMIZATION HINTS" - "The
optimization
hint is applied to the statement or APREUSE(ERROR/WARN) is
applied to the package".
Additional Keywords:
OPTHINT OPTHINTS SQLCODE394 SQLCODE395 SQLEXPLAIN
DB2 has been enhanced to improve the usability of optimization
hints as described above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13724
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 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
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=<x>
(where <x> 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.
1 * 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 <x>
Change <x> 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')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI13724
DSNDQWPZ PI13724
DSNDQW00 PI13724
DSNDSPRM PI13724
DSNTIDXA PI13724
DSNTIDXB PI13724
DSNTIJUZ PI13724
DSNTINST PI13724
DSNTXAZP PI13724
DSNWZIFA PI13724
DSNXOD3 PI13724
DSNXOES5 PI13724
DSNXOMPS PI13724
DSNXOOP PI13724
DSNXOPCO PI13724
DSNXOTR1 PI13724
DSNXOTR2 PI13724
DSN6SPRM PI13724
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13724 DSN@XAZP DSNDQWPZ DSNDQW00 DSNDSPRM DSNTIDXA DSNTIDXB
DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSNXOD3 DSNXOES5
DSNXOMPS DSNXOOP DSNXOPCO DSNXOTR1 DSNXOTR2 DSN6SPRM
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
DSNWZIFA
DSNXOD3
DSNXOES5
DSNXOMPS
DSNXOOP
DSNXOPCO
DSNXOTR1
DSNXOTR2
MACROS
DSN@XAZP
DSNDQWPZ
DSNDQW00
DSNDSPRM
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6SPRM
LISTEND
UI19080 COVER LETTER END
UI19105 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17163 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: The following symptom may appear when *
* an application connects to a remote DB2 *
* for z/OS server and executes an SQL *
* statement containing a system-directed *
* (three-part name) remote reference: *
* - ABEND 04E-00D3440B *
* LOC=DSNLXLLM.DSNLXHCN:0019 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application connects to a DB2 for z/OS server. The
application executes an SQL statement containing a (three-part
name) system-directed remote reference. The remote reference
is actually intended to be associated to a location alias for
the same DB2 server but the location alias was not (yet)
defined when the application package was bound.
The application package is then executed once the location
alias is defined but results in a DB2 abend:
ABEND04E-00D3440B LOC=DSNLXLLM.DSNLXHCN:0019.
To correct the condition, the application package must be
bound (re-bound) once the location alias is defined.
1
DB2 has been changed to issue SQLCODE -904, with a new reason
code 00D34451, in order to describe the failing condition.
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.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17163
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
*** 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.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXHCN PI17163
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17163 DSNLXHCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXHCN
LISTEND
UI19105 COVER LETTER END
UI19116 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16746 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a query *
* with a correlated subquery containing FETCH *
* FIRST N ROWS clause. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output can be returned for a *
* query with an outer join with a *
* correlated subquery containing FETCH *
* FIRST N ROWS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect record values can be returned for a query with an
outer join with a correlated subquery containing FETCH FIRST
N ROWS. The reason for incorrect output is because DB2 doesn't
reset an internal variable for FETCH FIRST N ROWS retrieving
counter to zero after each execution of the correlated subquery.
The following example illustrates how this incorrect output can
occur.
1. Define 2 tables and insert data into the tables.
CREATE TABLE T1 (C1 INT, C2 INT);
CREATE TABLE T2 (C3 INT, C4 INT);
INSERT INTO T1 VALUES (1,2);
INSERT INTO T1 VALUES (3,4);
INSERT INTO T2 VALUES (7,8);
2. Run below query.
SELECT C1 AS T1C1, C2 AS T1C2 ,
TX.TXC3 AS TXC3 , TX.SUMC4 AS TXSUMC4
FROM T1
LEFT JOIN TABLE
(SELECT C3 AS TXC3 , SUM(C4) AS SUMC4
FROM T2 AS T2
WHERE C3 > T1.C1
GROUP BY C3
FETCH FIRST ROW ONLY )
1 AS TX ON 1=1;
This query should return 2 rows as below.
+-----------------------------------------------------------+
| C1 | C2 | C5 | C6 |
+-----------------------------------------------------------+
1_| 1 | 2 | 7 | 8 |
2_| 3 | 4 | 7 | 8 |
+-----------------------------------------------------------+
However, DB2 will return below records.
+-----------------------------------------------------------+
| C1 | C2 | C5 | C6 |
+-----------------------------------------------------------+
1_| 1 | 2 | 7 | 8 |
2_| 3 | 4 | ? | ? |
+-----------------------------------------------------------+
DB2 returns above incorrect output because it doesn't reset an
internal variable storing for rows retrieved after each
execution of the correlated subquery.
DB2 has been modified to return the column values correctly.
Additional keywords : SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K SQLOUTERJOIN SQLOUTER SQLLEFT
SQLLEFTJOIN SQLSUBQUERY SQLCORRSUBQ
SQLFFNR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16746
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRCLS PI16746
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16746 DSNXRCLS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRCLS
LISTEND
UI19116 COVER LETTER END
UI19119 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18121 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of an SQL *
* statement containing a subquery predicate *
* with a DECFLOAT column or a column *
1 * implicitly cast to DECFLOAT, when the *
* subquery contains ORDER BY on a column that *
* is not in the select list. *
****************************************************************
* PROBLEM DESCRIPTION: 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
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.
Some examples are shown below:
CREATE TABLE T1(C1 DECFLOAT(16));
CREATE TABLE T2(C1 DECIMAL(10, 1),
C2 DATE);
CREATE TABLE T3(C1 DECIMAL(10, 1),
C2 CHAR(10));
INSERT INTO T1 VALUES( 1 );
INSERT INTO T2 VALUES(1.0, '2014-01-01');
INSERT INTO T2 VALUES(1.1, '2014-01-02');
INSERT INTO T3 VALUES(1.0, 'ABC');
INSERT INTO T3 VALUES(1.1, 'XYZ');
-- Example for the ABEND
SELECT *
FROM T1
WHERE C1 IN (SELECT C1
FROM T2
ORDER BY C2
)
;
-- Example for the SQLCODE -420
SELECT *
FROM T1
WHERE C1 IN (SELECT C1
FROM T3
ORDER BY C2
)
;
-- Example for implicit added cast to DECFLOAT
1 CREATE TABLE T1(C1 CHAR(10));
CREATE TABLE T2(C1 DECIMAL(10, 1),
C2 DATE);
INSERT INTO T1 VALUES('1');
INSERT INTO T2 VALUES(1.0, '2014-01-01');
INSERT INTO T2 VALUES(1.1, '2014-01-02');
SELECT *
FROM T1
WHERE C1 IN (SELECT C1
FROM T2
ORDER BY C2
)
;
DB2 did not correctly process the aforementioned SQL statements,
which caused the ABEND or incorrect SQLCODE.
DB2 has been modified to correctly process the aforementioned
SQL statements, so there will be no ABEND or incorrect SQLCODE.
Additional keywords: SQLSUBQUERY SQLORDERBY SQLDECFLOAT
SQLCODE420
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18121
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSL PI18121
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18121 DSNXOSL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSL
LISTEND
UI19119 COVER LETTER END
UI19125 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14384 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of ROW TRANSACTION TIMESTAMP. *
****************************************************************
* PROBLEM DESCRIPTION: ABND04E RC00C90101 DSNIKESR ERQUAL5008 *
* occurred when deleting a record with *
* row transaction timestamp columns. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The reported abend occurred when deleting a record with columns
which are defined as not null row transaction timestamp columns
(row begin, row end, transaction start id) and there is an
index created on the row transaction timestamp columns.
In addition, the row transaction timestamp columns were alter
added to a populated table. The abend was triggered when
trying to get the default value of a row transaction timestamp
column while processing the index key during the delete of
records that were inserted before the alter add of the row
transaction timestamp column.
This abend is not limited to SQL DELETE and could occur
during an SQL SELECT or FETCH operation and during a utility
such as REORG, RUNSTATS, CHECK DATA, CHECK INDEX and UNLOAD.
DB2 code has been modified to get the correct default value
for row transaction timestamp columns.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14384
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIKESR PI14384
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14384 DSNIKESR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIKESR
LISTEND
UI19125 COVER LETTER END
UI19129 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19010 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries with equal predicates that include a *
* timestamp column and a string host variable. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 rc00E70005 at location *
* DSNXRRP OFFSETM110 for DB2 10 or *
* OFFSETM840 for DB2 11 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 rc00E70005 can occur at location DSNXRRP (OFFSETM110
for DB2 10 or OFFSETM840 for DB2 11) for an SQL query that
contains an after join or during join predicate that contains a
timestamp column and a string host variable.
The following example illustrates such a failing query.
Step 1. Create three tables, each with a TIMESTAMP column.
CREATE TABLE T1 (C1 TIMESTAMP);
CREATE TABLE T2 (C2 TIMESTAMP);
CREATE TABLE T3 (C3 TIMESTAMP);
Step 2. Perform the following query which contains joins on the
timestamp columns and a predicate with a timestamp
column and a string host variable.
SELECT *
FROM T1 LEFT OUTER JOIN T2
ON T1.C1 = T2.C2
LEFT OUTER JOIN T3
1 ON T1.C1 = T3.C3
WHERE T1.C1 = :HOSTVCHAR1 OR T2.C2 > :HOSTVARCHAR2;
The abend can occur because DB2 does not correctly process the
above SQL statement.
DB2 was updated to process the join predicate which contains
a timestamp column and a string host variable correctly.
Additional Keywords: SQLTIMESTAMP SQLHOSTVAR SQLJOIN PAGERANGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19010
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOW2C PI19010
DSNXOW2D PI19010
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19010 DSNXOW2C DSNXOW2D
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOW2C
DSNXOW2D
LISTEND
UI19129 COVER LETTER END
UI19136 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI05920 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* DB2 10 and DB2 11 for z/OS only. *
****************************************************************
1 * PROBLEM DESCRIPTION: DB2 for z/OS, as a requester, abend *
* 0C4-0000003B DSNSLD4 .DSNSVSFB+0696 *
* during abort processing which results *
* in DB2 abnormal termination with *
* reason 00D94001. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a DB2 for z/OS (as a requester) application package opens
a query to a remote server and the server incorrectly returns a
reply message which violates DRDA protocol, DB2 for z/OS
(requester processing) may detect the server error in the form
of an abend.
Example: 04E-00D34412 DSNLXGLM.DSNLXRBT:000A.
As a result of this primary abend, the DB2 thread will abort
and terminate. However, the following secondary abend may
occur during abort processing:
ABND=0C4-0000003B at LOC=DSNSLD4 .DSNSVSFB+0696
This secondary abend during abort processing leads to a DB2
abnormal termination with reason 00D94001.
The secondary abend occurs due to incorrect (stack) storage
usage that is not expected to be managed during abort
processing.
DB2 for z/OS requester processing is changed to utilize
storage that can successfully be managed by abort processing
in the event of an (primary) abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI05920
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXROP PI05920
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI05920 DSNLXROP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXROP
LISTEND
UI19136 COVER LETTER END
UI19138 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17873 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS *
* users of an unfenced routine which *
* references a view. *
****************************************************************
1 * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur during *
* bind time at location DSNXGUDF M113 *
* when referencing a VIEW in an unfenced *
* routine. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E rc00E70005 at location DSNXGUDF M113 can occur
when referencing a VIEW in an unfenced routine.
During bind time, DB2 can incorrectly reference a zero storage
address when generating execution time structures. If any of
the first two bytes at this location (address) are set, DB2 can
then abend when creating an execution structure.
The code in DB2 has been modified to correct the problem of
referencing an incorrect address during bind time.
Additional Keywords: SQLUDF SQLVIEW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17873
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGUDF PI17873
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17873 DSNXGUDF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGUDF
LISTEND
UI19138 COVER LETTER END
UI19141 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14521 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of ALTER TABLE ADD COLUMN. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70006 at DSNXISB5 *
* ERQUAL P026 may occur when executing an *
* ALTER TABLE ADD COLUMN statement and *
* the referenced table space is *
* unavailable. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70006 at DSNXISB5 ERQUAL P026 may occur when
1 executing an ALTER TABLE ADD COLUMN statement and the referenced
table space is unavailable. The unavailable reason code is
00C90094.
In this case, DB2 should issue a SQLCODE -904 with proper
unavailable resource type 00000200, reason code 00C90094, and
resource name.
After applying this APAR, user needs to resolve the system
environment issue to make the resource available, then rerun the
ALTER TABLE ADD COLUMN statement.
DB2 is modified to detect the resource unavailable signal and
issue the SQLCODE -904 instead.
Additional Keywords: SQLALTER ABEND04E RC00E70006 ERQUALP026
SQLCODE904 RC00C90094
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14521
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIDMN PI14521
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14521 DSNXIDMN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIDMN
LISTEND
UI19141 COVER LETTER END
UI19147 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15854 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users run UPDATE statements *
****************************************************************
* PROBLEM DESCRIPTION: DB2 run into a storage shortage issue *
* when multiple UPDATE statements are *
* executed concurretly under dynamic *
* cache environment. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Under dynamic cache environment, after UPDATE statements are
run, DB2 may not free its associated UPROC storage due to
performance reason. The storage for UPROCs may therefore be
accumulated and cause a storage shortage in DB2.
DB2 code is modified to provide a relief of storage leak due to
the accumulated UPROCs. DB2 will use a UPROC built at dynamic
1 cache prepare time and avoid to create another UPROC at runtime.
DB2 will invalidate dynamic cache packages and quiesce the use
count at CREATE and ALTER INDEX time to ensure the UPROC's
consistent state. The logic change may cause potential SQLCODE
-904 for CREATE and ALTER INDEX.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15854
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILREP PI15854
DSNXICIX PI15854
DSNXICX2 PI15854
DSNXODML PI15854
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15854 DSNILREP DSNXICIX DSNXICX2 DSNXODML
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
DSNXICIX
DSNXICX2
DSNXODML
LISTEND
UI19147 COVER LETTER END
UI19153 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16838 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of CREATE *
* INDEX on a table residing in a database *
* with a blank SYSDATABASE.STGROUP value. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE -204 might be *
* received when CREATE INDEX is issued *
* on a table residing in a database with *
* a blank SYSDATABASE.STGROUP value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Unexpected SQLCODE -204 may result from CREATE INDEX on a table
residing in a database with a blank SYSDATABASE.STGROUP value.
System default databases or databases created prior to DB2 V7
may contain a blank SYSDATABASE.STGROUP value. Unexpected
SQLCODE -551 or -552 may also be received due to the same
reason.
DB2 has been modified to properly handle index creation
on tables residing in a database with a blank
SYSDATABASE.STGROUP value.
1
ADDITIONAL KEYWORDS:
SQLCODE204
SQLCODE551
SQLCODE552
SQLCREATE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16838
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODDL PI16838
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16838 DSNXODDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODDL
LISTEND
UI19153 COVER LETTER END
UI19159 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17479 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 or 11 for z/OS users of an SQL *
* statement with a scalar-fullselect *
* containing a table expression or view with *
* UNION ALL. *
****************************************************************
* PROBLEM DESCRIPTION: 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(C1 INT NOT NULL);
CREATE TABLE T2(C1 INT NOT NULL);
INSERT INTO T1 VALUES(1);
SELECT
(SELECT DISTINCT 1
FROM
(SELECT C1
1 FROM T1
UNION ALL
SELECT C1
FROM T2
)TX
WHERE TX.C1 > 0
) AS C1
FROM T1
;
The query above should return an integer value 1, while it
incorrectly returned a NULL. DB2 did not correctly process the
aforementioned SQL statement, which caused the incorrect output.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no incorrect output.
Additional keywords: SQLTABLEEXPR SQLVIEW SQLSCALAR
SQLFULLSELECT SQLSCALARFULSEL SQLUNIONALL
SQLNOTNULL SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17479
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***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.
DB2BIND:
1 ***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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOB2 PI17479
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17479 DSNXOB2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOB2
LISTEND
UI19159 COVER LETTER END
UI19196 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19137 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIIMSI:5020 or *
* other abends may occur during a *
* migration. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
ABEND04E RC00C90101 DSNIIMSI:5020 or other abends may occur
during a CATMAINT UPDATE. The number of columns in
SYSIBM.SYSTABLESPACESTATS and/or SYSIBM.SYSINDEXSPACESTATS may
change between the releases of DB2. During a migration to or
falling back from a newer release, DB2 may process using the
1 RTS catalog table defined for the older release even though
the catalog is for the newer release. Real-time Statistics
was not handling this change in the number of columns between
releases.
Additional keywords: ERQUAL5020 ERQUAL5006 DSNIMOFR:5006
Code has been modified to correct the aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19137
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRTSU PI19137
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19137 DSNIRTSU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRTSU
LISTEND
UI19196 COVER LETTER END
UI19207 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14368 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* IBM DB2 Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes the following issues *
* for IBM DB2 Analytics Accelerator. *
* *
* (1) For an EXPLAIN of an INSERT with *
* subSELECT statement, *
* DSN_QUERYINFO_TABLE may not *
* populate with any rows. *
* (2) A query with the function TRUNC *
* may return incorrect output when *
* executed on an accelerator. *
* (3) A query that contains an ORDER BY *
* in a set operation may fail on *
* an accelerator. *
* (4) A query with the function CHAR *
* with a FOR BIT DATA column and *
* OCTETS may return incorrect *
* output. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes the following issues for IBM DB2 Analytics
1 Accelerator.
(1) For an EXPLAIN of an INSERT with subSELECT statement,
DSN_QUERYINFO_TABLE may not populate with any rows when
zparm QUERY_ACCEL_OPTIONS does not include the value 2.
(2) A query with the function TRUNC may return incorrect
output when executed on an accelerator if the value of the
1st argument is very large. For example TRUNC(C1,-1) where
C1 is a BIGINT column with a value of 14683479057743532.
(3) A query that contains an ORDER BY within a set operation
UNION, UNION ALL, INTERSECT, INTERSECT ALL, EXCEPT, or
EXCEPT ALL may fail with SQLCODE -901 Reason "42000: ERROR:
found "NULLS" on an accelerator.
(4) A query with the function CHAR with a FOR BIT DATA
column and OCTETS may return incorrect output.
For static SQL queries that have been bound for acceleration
and will use any of the new functions above, after applying
this PTF, REBIND the package for the failing query.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K SQLTRUNC SQLEXPLAIN SQLSETOP
SQLCHAR FORBITDATA
DB2 code is fixed for expected results and behavior.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14368
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
DB2BIND:
***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.
1 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.
ACTION:
***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
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODML PI14368
DSNXONZC PI14368
DSNXONZS PI14368
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14368 DSNXODML DSNXONZC DSNXONZS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODML
DSNXONZC
DSNXONZS
LISTEND
UI19207 COVER LETTER END
UI19223 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10964 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of RRSAF. *
****************************************************************
* PROBLEM DESCRIPTION: RRSAF threads may hang if an *
* application address space is cancelled *
* with an MVS CANCEL. The hang occurs *
* because a thread is holding page *
* latches when it is cancelled. *
* In reviewing the dumps for this *
* problem, there may be threads in *
* abort waiting in DSNB5RDP. *
* Message DSNR048I may also be *
* issued for threads. *
1 * Other symptoms may include a suspend *
* in DSNB1LTS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
RRSAF threads may hang if an application address space is
cancelled with an MVS CANCEL.
Symptoms may include threads in abort waiting in DSNB5RDP,
a suspend in DSNB1LTS, or message DSNR048I.
MSGDSNR048I
DB2 modules DSN3RRSI and DSN3RRSM have been updated to defer DB2
abort processing for a cancelled thread until DB2 deferred EOT
processing for the application task. DSN3RRSM will rely on a
new flag which is set for an RRS Backout exit call to determine
whether to immediately process or defer abort for the DB2 UR.
This change to DSN3RRSM is specifically for the terminating
syncpoint case, in which the RRSAF application is cancelled
and MVS context services EOT processing calls RRS which
drives Backout exits for the Resource Managers which have
expressed interest in the RRS UR.
This APAR requires that z/OS APAR OA44779 is installed for the
change to be effective.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10964
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3RRSI PI10964
DSN3RRSM PI10964
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10964 DSN3RRSI DSN3RRSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3RRSI
DSN3RRSM
LISTEND
UI19223 COVER LETTER END
UI19226 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14777 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users that *
1 * use CPU parallelism query. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNICMT2 *
* ERQUAL5368 during commit process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 keeps track of the RID blocks it allocates so that they can
be freed at commit. When there are multiple parallel tasks
involved, due to improper serialization, DB2 mis-counted the
total RID blocks it allocated and caused a 04E abend at
DSNICMT2:5368 during commit process.
Fixes made in DB2 so that proper serialization is acquired when
transferring RID blocks between tasks.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14777
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXPRE2 PI14777
DSNXRRID PI14777
DSNXRRI9 PI14777
DSNXRTSC PI14777
DSNXRTSS PI14777
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14777 DSNXPRE2 DSNXRRID DSNXRRI9 DSNXRTSC DSNXRTSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXPRE2
DSNXRRID
DSNXRRI9
DSNXRTSC
DSNXRTSS
LISTEND
UI19226 COVER LETTER END
UI19251 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13155 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the COPY2COPY, MERGECOPY, *
* and MODIFY RECOVERY utilities. *
****************************************************************
* PROBLEM DESCRIPTION: Adding serviceability for the *
* COPY2COPY, MERGECOPY, and MODIFY *
* RECOVERY utilities. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
Adding serviceability for the COPY2COPY, MERGECOPY, and
and MODIFY RECOVERY utilities.
Adding serviceability for the COPY2COPY, MERGECOPY, and
and MODIFY RECOVERY utilities.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13155
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUMDEL PI13155
DSNUYAS1 PI13155
DSNUYAS2 PI13155
DSNU2AII PI13155
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13155 DSNUMDEL DSNUYAS1 DSNUYAS2 DSNU2AII
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUMDEL
DSNUYAS1
DSNUYAS2
DSNU2AII
LISTEND
UI19251 COVER LETTER END
UI19257 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18837 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the *
* ROUND function (for integers and big *
* integers) and the TRUNCATION function (for *
* big integers). *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result or an unexpected *
* SQLCODE +802 can be returned from the *
* ROUND function for integer or big *
* integer input. An incorrect result *
* can be returned from the TRUNCATION *
* function for big integer input. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result that can include an SQLCODE +802 warning
(SQLCODE802) can be returned from the ROUND function. More
specifically, the ROUND function, with integer or big integer
input, and the TRUNCATION function, with big integer input, can
return an unexpected or incorrect result.
1 The following examples help to illustrate the problem.
Example 1. ROUND function with integer input.
SELECT ROUND(1648000000, -9) FROM SYSIBM.SYSDUMMYU;
The unexpected result is an SQLCODE +802. However, the expected
result is 2000000000, the same as that which is returned for
SELECT ROUND(1647000000, -9) FROM SYSIBM.SYSDUMMYU;
Example 2. ROUND function with big integer input.
CREATE TABLE T1 ( ROUNDP1 INTEGER NOT NULL DEFAULT 0,
ROUNDP2 SMALLINT NOT NULL DEFAULT 0 ) ;
INSERT INTO T1 VALUES ( 5, -1 );
SELECT ROUND ( CAST( 5 AS BIGINT ), ROUNDP2 ) FROM T1;
The result returned is 0 when 10 is expected as is the case
for this query
SELECT ROUND ( CAST(ROUNDP1 AS BIGINT), -1) FROM T1;
Example 3. TRUNCATION function with big integer input.
Using the same table T1 above,
SELECT TRUNC (CAST(1647786000 AS BIGINT), ROUNDP2) FROM T1;
The result returned is 0 when 1647786000 is expected as is the
case for this query
SELECT TRUNC (CAST(1647786000 AS BIGINT), -1) FROM T1;
The code in the ROUND and TRUNCATION routines in DB2 is modified
to correct the problem which can lead to an incorrect or
unexpected result.
Additional Keywords: SQLCODE802 SQLROUND SQLTRUNCATE
SQLBIF BIGINT BIGINTEGER SQLBIGINT
SQLINCORROUT INCORROUT SQLINCORR
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18837
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRINT PI18837
DSNXRLNG PI18837
1 DSNXRLN9 PI18837
DSNXRNT9 PI18837
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18837 DSNXRINT DSNXRLNG DSNXRLN9 DSNXRNT9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRINT
DSNXRLNG
DSNXRLN9
DSNXRNT9
LISTEND
UI19257 COVER LETTER END
UI19260 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI09491 -
****************************************************************
* USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) *
* users and data sharing users sysplexds. *
****************************************************************
* PROBLEM DESCRIPTION: Abend2025 occurs in DXRRL2R0 after IRLM *
* is brought down by the modify command: *
* F ProcIrlm,ABEND,NODUMP *
* *
* Error message DXR139E appears before *
* the 2025 dump. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
An asynchronous CHANGE request was issued to change a global
modifiable P-lock with state X to a non-modified state S.
Before the CHANGE request was completed, a MODIFY command was
entered to bring down IRLM with NODUMP option:
F IrlmProc,ABEND,NODUMP
IRLM built a QUIT QE and queued it to the request handler.
Meanwhile the CHANGE request returned from XES and it's queued
to one of the hash table ordered queues.
The QUIT processor tried to retain the global modifiable
P-lock. It's unaware that the P-lock had changed to non-
modified on the lock structure. Thus, the IXLRT REQUEST
(UPDATENTRY) for the P-lock failed with RC=08 and RSN=081A
(IXLRSNCODENORTENTRY) which caused the 2025 abend.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code is updated to skip the abend2025 if IRLM detects that
1 it's brought down with a NODUMP option.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI09491
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2R0 PI09491
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI09491 DXRRL2R0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2R0
LISTEND
UI19260 COVER LETTER END
UI19265 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11839 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG REBALANCE utility *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE REBALANCE SHRLEVEL *
* CHANGE enablement *
****************************************************************
* RECOMMENDATION: Apply PTF when available *
****************************************************************
This APAR enables REORG TABLESPACE REBALANCE to execute with
the SHRLEVEL CHANGE option in DB2 10 for z/OS, as well as in
DB2 11 for z/OS Conversion Mode ( CM ).
The Utility Guide and Reference manual will be updated with the
above new function enablement. In particular, the SHRLEVEL
CHANGE restriction under the REBALANCE keyword in the REORG
TABLESPACE section will be removed.
Code has been modified to introduce the REORG TABLESPACE
REBALANCE SHRLEVEL CHANGE support.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11839
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIIDIS PI11839
DSNISRTI PI11839
DSNUGDDM PI11839
DSNUGUCA PI11839
DSNURLAP PI11839
DSNURLOG PI11839
DSNURLXL PI11839
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11839 DSNIIDIS DSNISRTI DSNUGDDM DSNUGUCA DSNURLAP DSNURLOG
DSNURLXL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIIDIS
DSNISRTI
DSNUGDDM
DSNUGUCA
DSNURLAP
DSNURLOG
DSNURLXL
LISTEND
UI19265 COVER LETTER END
UI19269 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15301 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the LOAD utility. *
****************************************************************
* PROBLEM DESCRIPTION: A LOAD RESUME YES LOG NO into a table *
* space with a LOB column set the LOB *
* table space to be COPY PENDING, *
* although it did not load any data into *
* the LOB table space. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a LOAD RESUME YES LOG NO to load data into a table
space with a LOB column. All LOB data was loaded inline, thus
the LOB table space was not updated, but COPYP was set on the
LOB table space.
The problem happened because LOAD did not check whether the LOB
1 table space had been loaded before setting COPYP. The problem
can also happen if all the loaded LOBs are zero length LOBs or
null LOBs.
LOAD utility has been modified to check whether the LOB table
space is loaded before setting COPYP.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15301
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURICP PI15301
DSNURWI PI15301
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15301 DSNURICP DSNURWI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURICP
DSNURWI
LISTEND
UI19269 COVER LETTER END
UI19271 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15860 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG utility with SORTDATA NO. *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL REFERENCE *
* SORTDATA NO on disjoint part ranges *
* abended with ABEND04E RC00C9007E at *
* DSNIRLPG OFFSETCC0C during the RELOAD *
* phase. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REORG TABLESPACE SHRLEVEL REFERENCE with SORTDATA NO ran on
a list which included disjoint partition ranges of a range-
partitioned universal table space (PBR) with a clustering
partitioning index abended with ABEND04E RC00C9007E at DSNIRLPG
+ x'CC0C' during the RELOAD phase.
Data corruption could also happen when the REORG is restarting
from the UNLOAD phase.
This problem occurred because an internal control block was not
set up correctly to handle unloading data from disjoint
partition ranges.
The same problem could occur for:
- Classical partitioned table space
- REORG TABLESPACE SHRLEVEL NONE
1 - REORG PART(m,n:l)
- Part level REORG after partition rotation
REORG code has been changed to correctly set up the control
block required for SORTDATA NO processing for disjoint
partition ranges, as well as the other problems.
RESTART(PHASE) will be used if REORG is restarted in the UNLOAD
phase in the aforementioned senarios.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15860
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFBR PI15860
DSNURFIT PI15860
DSNURRNG PI15860
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15860 DSNURFBR DSNURFIT DSNURRNG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFBR
DSNURFIT
DSNURRNG
LISTEND
UI19271 COVER LETTER END
UI19299 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18013 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* with a XML column inside a MQB or an *
* uncorrelated scalar full select. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNNOLCK M220 *
* ERQUAL220 may occur for queries with *
* XML columns inside a MQB or an *
* uncorrelated scalar full select. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 at DSNNOLCK M220 ERQUAL220 may occur for
queries with XML columns inside a MQB or an uncorrelated scalar
full select.
Examples for error case is shown below:
(1) MQB
1 SELECT T1.C1, TX.C3
FROM T1 LEFT OUTER JOIN (SELECT T2.C1, T3.C1 ,T2.C_XML
FROM T2 LEFT OUTER JOIN T3 ON T2.C1
WHERE T3.C2 IS NULL AND T2.C3>0 AND
) TX(C1, C2, C3)
ON T1.C1 = TX.C1;
(2) scalar full select
SELECT I1, (SELECT X1 FROM T1 WHERE T1.I1 = T2.I1) FROM T2;
The bindtime code in DB2 is modified to correct the conditions
leading to the ABEND.
Additional Keywords: ABEND04E SQLXML SQLMQB SQLSCALARFULLSELECT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18013
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
PM99313 corrects a problem of incorrect output returned when
query contains a UNION ALL clause in its subquery predicate.
DB2BIND:
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.
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGA1 PI18013
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18013 DSNXOGA1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGA1
LISTEND
UI19299 COVER LETTER END
UI19307 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI16423 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOB columns in a table with *
* AUDIT CHANGES/ALL option. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 AT DSNXVTRS: *
* P000 may occur when running a *
* utility job or a DML operation when *
* adding partition on partition by *
* growth table space is needed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXVTRS: P000 may occur when running
a UTILITY job (such as REORG) or a DML operation (such as
INSERT) on a table object which meets the following conditions:
1. the table space is partition by growth (PBG), and
2. the base table contains LOB column(s), and
3. the base table is defined with AUDIT CHANGES/ALL, and
4. a new partition is grown during the execution of Utility job
or DML operation
When all the above conditions are met, DB2 incorrectly writes
out an audit trace record for the newly created auxiliary table
when it should not. There may be other unexpected symptoms
depending on the audit trace information availability when
writing it.
DB2 has been modified so that audit trace records are not
incorrectly written out.
Additional Keywords: SQLLOB IFCID142 SQLPBG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16423
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICB7 PI16423
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16423 DSNXICB7
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICB7
LISTEND
UI19307 COVER LETTER END
UI19317 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI16238 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users using index compression *
****************************************************************
* PROBLEM DESCRIPTION: LOAD RESUME or INSERT may fail with *
* ABEND04E RC00C90101 DSNKISPL ERQUAL5014 *
* after ALTER COLUMN that affects both *
* table and COMPRESS YES index. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ALTER COLUMN placed table and index space in REORG-pending
(AREO*) advisory status. Although, this is not a restrictive
state, table and index space should be reorganized for optimal
performance.
While COMPRESS YES index was in AREO*, splitting position on
splitting leaf page was not accurately processed causing
ABEND04E RC00C90101 DSNKISPL ERQUAL5014.
Additional Keywords: SQLALTER SQLINSERT
Additional Symptoms: DSNKPGCM ERQUAL5006 ERQUAL5007
MSGDSNU086
Index leaf split code has been modified to handle uncommon
splitting position.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16238
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKISPL PI16238
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16238 DSNKISPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKISPL
LISTEND
UI19317 COVER LETTER END
UI19320 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18989 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of the *
* DECIMAL, FLOAT, and BIGINT data types. *
****************************************************************
* PROBLEM DESCRIPTION: After an application detects an *
* overflow condition that results from a *
1 * DECIMAL to BIGINT or a FLOAT to BIGINT *
* conversion, an ABEND04E RC00E70005 *
* occurs at DSNXGRDS DSNXEBR M662. In a *
* distributed environment, an ABEND04E *
* RC00D3440B can occur at DSNLXGLM *
* DSNLXRBF OFFSET0130. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 can occur at location DSNXGRDS DSNXEBR
M662 (or in the distributed environment an ABEND04E RC00D3440B
can occur at location DSNLXGLM DSNLXRBF OFFSET0130) when
fetching DECIMAL or FLOAT data into a BIGINT host variable when
the data exceeds the maximum size for the DB2 BIGINT datatype.
The failure occurs because DB2 is missing code to issue SQLCODE
-304 when the above overflow occurs.
The following example helps to illustrate the problem.
1. Create a Table T1 with a DECIMAL column and insert a row
into the table.
CREATE TABLE T1 (C1 DECIMAL(31, 0));
INSERT INTO T1 VALUES (9234567890123456789);
2. In a C application, define one host variable with a data type
of long long int, and declare a cursor to use for FETCH.
long long var1;
EXEC SQL DECLARE CUR1 CURSOR FOR
SELECT C1 FROM T1;
EXEC SQL OPEN CUR1;
EXEC SQL FETCH CUR1 INTO :var1;
3. Bind the package and then execute it.
Since the value of C1 exceeds the maximum of a DB2 BIGINT data
type, an overflow will occur during the 'DECIMAL to BIGINT'
conversion. However, since DB2 did not format an SQLCODE for
this condition, it results in an abend.
The code in DB2 is modified to issue an SQLCODE -304 for the
overflow condition that can result from the 'DECIMAL to BIGINT'
or the 'FLOAT to BIGINT' data type conversion. This will avoid
the abend.
Additional Keywords: SQLCODE304 SQLHOSTVAR SQLDECIMAL SQLFLOAT
SQLBIGINT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18989
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXROB9 PI18989
DSNXROE9 PI18989
DSNXROHB PI18989
DSNXROHE PI18989
DSNXROHR PI18989
DSNXROHS PI18989
DSNXROH2 PI18989
DSNXROS9 PI18989
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18989 DSNXROB9 DSNXROE9 DSNXROHB DSNXROHE DSNXROHR DSNXROHS
DSNXROH2 DSNXROS9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXROB9
DSNXROE9
DSNXROHB
DSNXROHE
DSNXROHR
DSNXROHS
DSNXROH2
DSNXROS9
LISTEND
UI19320 COVER LETTER END
UI19326 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18831 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS RRSAF users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 occurred in module DSN3CMT1 *
* during recovery processing for an RRS *
* application failure. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 occurred in module DSN3CMT1 during recovery
processing for an RRS application failure. The application is
using DB2 WLM Managed Stored Procedures.
This ABEND0C4 in DSN3CMT1 only occurs in DB2 V10 and V11 for
z/OS.
KEYWORDS: DB2SP SQLSP SQLSTOREDPROC
Module DSN3CMT1 has been updated to avoid the ABEND0C4.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18831
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3CMT1 PI18831
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18831 DSN3CMT1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3CMT1
LISTEND
UI19326 COVER LETTER END
UI19328 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM82830 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Remote Java client application *
* receives -4499 exception. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an IBM Data Server Driver/Client for Java is used by a
remote client application to access a DB2 for z/OS subsystem,
client application connections are directed by the driver to
a physical connection which the client application utilizes
for its access to the DB2 for z/OS subsystem. The physical
connection to the DB2 for z/OS server is called a transport.
Sometimes the transport chosen by the driver could have
already been established and used for previous Java client
connections in which case the connection is considered to
be reused. During connection reuse processing, the driver
replays the exchanges that were previously used to establish
the connection with DB2 for the current Java client
connection.
In this case, the transport was originally established to
support "DRDA Unicode Manager" network traffic. As long as
other Java client applications, which reuse this transport
connection, also request support of "DRDA Unicode Manager"
network traffic, no error would be detected. If, however,
during connection reuse processing, "DRDA Unicode Manager"
network traffic support is not requested, the DB2 server
incorrectly interprets the connection reuse sequence as
supporting "DRDA Unicode Manager". DB2 then incorrectly
detects that a parameter on one of the DRDA exchanges is
invalid and subsequently terminates the connection. This
causes the Java client application to receive a -4499
exception.
1 DB2 has been changed to correctly determine whether or not
"DRDA Unicode Manager" network traffic support is being
requested by a remote client during a connection reuse
sequence.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM82830
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLZSEA PM82830
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM82830 DSNLZSEA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLZSEA
LISTEND
UI19328 COVER LETTER END
UI19330 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19360 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an *
* SQL statement containing SUM or AVG function *
* with an argument of DEC function and there *
* is only one argument whose data type is *
* DECFLOAT in the DEC function. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C7 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 *
1 * function. *
* 3. the precision of DECFLOAT value is *
* greater than 15. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create a Table T1.
CREATE TABLE T1(
C1 CHAR(1),
C2 DECFLOAT(16)
);
Step 2. Populate the Table.
INSERT INTO T1 VALUES(
'A', 5000000000000000
);
Step 3. SELECT statement which can cause the ABEND0C7.
SELECT C1, SUM(DEC(C2))
FROM T1
GROUP BY C1;
Step 4. SELECT statement which can cause the incorrect output.
SELECT SUM(DEC(C2)) AS C1
FROM T1;
The expected result:
+------------------------------------+
| C1 |
+------------------------------------+
1_| 5000000000000000 |
+------------------------------------+
The real result:
+------------------------------------+
| C1 |
+------------------------------------+
1_| 0 |
+------------------------------------+
DB2 does not process the result data length and precision
of DEC function and SUM function properly which can result
in the ABEND0C7 and incorrect output.
If SUM(DEC(C2)) is defined as a column of VIEW, the column
information is saved incorrectly in the catalog before applying
the APAR.
The DECIMAL function can work properly without the APAR fix.
DB2 is modified correctly to process the result length and
precision of DEC function and SUM function to avoid the
problem.
1 Additional Keywords: SQLAVG SQLSUM SQLDECFLOAT SQLGROUPBY
SQLVIEW SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19360
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
ACTION:
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.
1 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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFA PI19360
DSNXOBFF PI19360
DSNXOBF3 PI19360
DSNXOBF4 PI19360
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19360 DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBFA
DSNXOBFF
DSNXOBF3
DSNXOBF4
1
LISTEND
UI19330 COVER LETTER END
UI19341 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20156 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of OLAP *
* specifications, RANK, DENSE_RANK and *
* ROW_NUMBER. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect value may be returned for *
* the OLAP specifications RANK, *
* DENSE_RANK or ROW_NUMBER. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect value may be returned for a query referencing an
OLAP specification. The following must be true for the
incorrect output to occur :
- the OLAP specification is a RANK, DENSE_RANK or ROW_NUMBER
- the SQL is static ( or dynamic where the internal structures
are reused)
- The SQL is executed multiple times in an application program
The following is one example of when the problem may occur :
EXEC SQL DECLARE C1 CURSOR FOR
SELECT ROW_NUMBER ()
OVER (PARTITION BY C1 ORDER BY C2)
FROM T1;
for (i=1; i<=2; i++){
EXEC SQL OPEN C1;
EXEC SQL FETCH C1 INTO :rownum;
EXEC SQL CLOSE C1;
}
The value fetched into host variable 'rownum' should be 1 but
DB2 is incorrectly returning the value 2 for the second
iteration of the loop.
DB2 has been changed to clean up all of the internal structures
for the OLAP specification during CLOSE CURSOR processing. A
rebind is necessary to make this change effective for static
applications.
Additional keywords : SQLOLAP SQLINCORR INCORROUT
SQLINCORROUT DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20156
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***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
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGSAF PI20156
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20156 DSNXGSAF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGSAF
LISTEND
UI19341 COVER LETTER END
UI19347 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10015 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REORG TABLESPACE *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE abended with ABENDS0C4 *
* at DSNUFOBD +x'035E' *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REORG TABLESPACE was run and abended with ABEND0C4 RC4 at
DSNUFOBD OFFSET035E. This abend occurred because REORG
1 processed the table space as if there were pending ALTERs that
needed to be materialized, but because there were none, certain
control blocks were not built. When a pointer from one was
used, low core was accessed for that data which in turn,
attempted to access storage that was not allocated.
REORG code has been changed to alleviate the aforementioned
problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10015
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFIT PI10015
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10015 DSNURFIT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFIT
LISTEND
UI19347 COVER LETTER END
UI19363 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15439 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and *
* DB2 11 for z/OS users of RECOVER utility. *
****************************************************************
* PROBLEM DESCRIPTION: RECOVER utility does not restore the *
* image copy that is expected when in *
* fallback processing and there is a *
* point in time recovery record in *
* SYSCOPY. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User made an image copy (COPY1), then ran RECOVER TOCOPY to
COPY1, and then made another copy, COPY2.
They then ran RECOVER TOCOPY to COPY2, which went into RECOVER
fallback processing when COPY2 was not available. The RECOVER
job should have chosen COPY1 as the recovery base but instead
fell back further looking for an earlier recovery base even
when COPY1 was available for use. The problem occurred because
RECOVER fallback processing does not handle point in time
recovery SYSCOPY records correctly.
The RECOVER utility code has been modified to correctly select
the best available recovery base if a point in time recovery
record is encountered while in fallback processing.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15439
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCASA PI15439
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15439 DSNUCASA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCASA
LISTEND
UI19363 COVER LETTER END
UI19374 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19969 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS who *
* bind/prepare queries *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNXOES5 +022E can occur *
* on bind/prepare of a query if the *
* Resource Limit Facility (RLF) is not *
* started *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 in DSNXOES5 +022E can occur on the bind/prepare of a
query if the Resource Limit Facility (RLF) is not started.
Additional Keywords:
DSNXOES5 OFFSET022E
Code is updated to avoid referencing from a zero pointer when
RLF is not started.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19969
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOES5 PI19969
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19969 DSNXOES5
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNXOES5
LISTEND
UI19374 COVER LETTER END
UI19376 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18041 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users *
* of -STOP DATABASE command on *
* a workfile database. *
****************************************************************
* PROBLEM DESCRIPTION: Concurrent workfile allocation and *
* -STOP DATABASE command on the workfile *
* database could cause following abend : *
* 1.ABND=04E-00C200B0 at DSNB1SWS+216C *
* 2.ABND=04E-00C90101 at DSNIPSFI:5001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Improper serialization in -STOP DATABASE command opened up
a timing window that can let workfile allocation to continue
to allocate a workfile from a workfile data base that's being
stopped. This could cause following abend :
1. ABEND04E RC00C200B0 at DSNB1SWS+216C
2. ABEND04E RC00C90101 ERQUAL5001 in DSNIPSFI
Fixes made in -STOP DATABASE command to properly serialize
itself with workfile allocation. So that workfile allocation
will not be allowed to allocate a workfile from a workfile
data base that's being stopped.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18041
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDSTP PI18041
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18041 DSNTDSTP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDSTP
LISTEND
UI19376 COVER LETTER END
UI19383 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI17179 -
****************************************************************
* USERS AFFECTED: All users of the CLI Driver provided with *
* DB2 for Linux, Unix, and windows version 8 *
* and above that connect to DB2 10 for z/OS *
* or DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Stored procedure SYSIBM.SQLPRIMARYKEYS *
* returns an SQLCODE203 when called from *
* OLE DB applications with keyword DBNAME *
* through the CLI driver. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR *
****************************************************************
Database Metadata store procedure, SYSIBM.SQLPRIMARYKEYS, is
used when a CLI application calls SQLPrimarykeys(). When INI
configuration keyword DBNAME is in use and DATATYPE='OLEDB' is
set, CLI driver receives SQLCODE -203 on the call to procedure
SYSIBM.SQLPRIMARYKEYS.
The reported problem is fixed. The correct result set is
returned and no SQLCODE203 is issued.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17179
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
After reviewing the changes, either rerun DSNTIJRT without
1 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=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application
environment in which the Database Metadata stored procedure
SYSIBM.SQLPRIMARYKEYS running.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@PRKU PI17179
DSNAPRKU PI17179
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17179 DSN@PRKU DSNAPRKU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRKU
MACROS
DSN@PRKU
LISTEND
UI19383 COVER LETTER END
UI19385 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16683 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* customers who use the RECOVER utility *
* with system-level backup. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIBMOC + *
* '5005'x occurred during RECOVER *
* using a system-level backup (SLB) as *
* the recovery base. The RECOVER *
* job abended with RC00E40106. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
During RECOVER using a system-level backup as the recovery base,
the RECOVER job abended with ABEND04E RC00E40106 and RC00C90101
at DSNIBMOC OFFSET5005;
The target object was in LPL status before the RECOVER job and
caused the job to fail during the LOGAPPLY phase. A similar
problem could also occur if the target object was in GRECP
status before recovering with a system-level backup. It could
1 also occur if the target object was in either LPL or GRECP
status when the user uses a FLASHCOPY to recover.
ADDITIONAL KEYWORDS: RC00C20206, RC00C20210
Code was changed in the RECOVER utility to reset both LPL and
GRECP status when using a system-level backup as the recovery
base or when using a FLASHCOPY to recover.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16683
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCARS PI16683
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16683 DSNUCARS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCARS
LISTEND
UI19385 COVER LETTER END
UI19420 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18762 -
****************************************************************
* USERS AFFECTED: All DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: User may receive ABEND04E RC00E2000C, *
* pool full, condition even if pool has *
* free storage. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If an above-the-bar (ATB) pool has free storage in various
xslots such that the amount of storage in the pool ( phbgstor )
has reached the maximum allowed (phbgmstor), this failure will
occur. Contraction does not empty all storage from a size slot
even though it is all free. So even after contraction occurs,
a pool may contain too much storage to allow an expansion of
another size when needed. This occurs in pools with small
defined maximum allowed storage, such as LOB and XML.
Contraction has been changed to free all eligible storage
segments from a size slot.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18762
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNSCON2 PI18762
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18762 DSNSCON2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNSCON2
LISTEND
UI19420 COVER LETTER END
UI19422 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13132 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* inline LOBs (Large Objects). *
****************************************************************
* PROBLEM DESCRIPTION: DB2 can experience a storage shortage *
* when inserting or updating a table *
* with an inline LOB column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 can run into a possible storage shortage problem when
inserting into or updating a table with an inline LOB column.
The storage shortage can occur because DB2 does not release the
storage acquired for processing inline LOBs when errors (such as
a duplicate key) are encountered and the statement is in
'rollback'. This accumulation can result in a short-on-storage
condition for DB2.
The following example can help illustrate the problem using an
INSERT.
Step 1. Create Table T1 with an inline LOB column.
CREATE TABLE T1 ( C1 INT, C2 CLOB(100) INLINE LENGTH 4 )
IN MYDB.MYTS CCSID UNICODE;
CREATE UNIQUE INDEX MYINDEX ON T1(C1);
Step 2. Insert a row into Table T1.
INSERT INTO T1(C1, C2) VALUES(1, 'ROW11111111111111111');
Step 3. From an application, insert into Table T1 multiple
times.
1 APP:
DO HIND2 = 1 TO 10;
EXEC SQL INSERT INTO T1(C1,C2)
VALUES(1,'ROW22222222222222222');
END;
The code in DB2 is modified to properly release the obtained
(accumulated) storage to avoid a short-on-storage condition.
Additional Keywords: SQLLOB SQLINSERT SQLUPDATE DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13132
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILREP PI13132
DSNISRTI PI13132
DSNOLINS PI13132
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13132 DSNILREP DSNISRTI DSNOLINS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
DSNISRTI
DSNOLINS
LISTEND
UI19422 COVER LETTER END
UI19428 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19449 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC/CLI and DB2 Version 11 for z/OS *
* ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR (PI19449) implements DCR *
* DM1806 to support the new ODBC *
* initialization (INI) keyword *
* EXTENDEDTABLEINFO. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The information currently returned by ODBC API SQLTables() is
insufficient for vendors to exploit extended table information
such as accelerated tables and other related information.
A new initialization keyword, EXTENDEDTABLEINFO, has been added
to allow users to specify whether extended table information
1 is returned in the SQLTables() result set. When SQLTables() is
called, users can utilize the EXTENDEDTABLEINFO keyword, in
conjuction with a new table type 'ACCEL-ONLY TABLE', to specify
whether accelerator-only tables should be included in the
result set, and if the tables are included, how they are
reported in the TABLE_TYPE column.
Setting the EXTENDEDTABLEINFO keyword also allows users to
obtain additional information about tables in the SQLTables()
result set through a set of new columns.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI19449
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
*** 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
ACTION:
*** 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC03 PI19449
DSNAOC14 PI19449
DSNAOC15 PI19449
DSNAOG02 PI19449
DSNAOG03 PI19449
DSNAOG08 PI19449
DSNAOG13 PI19449
DSNAOG14 PI19449
DSNAOG15 PI19449
DSNAOCLI PI19449
DSNAOSDK PI19449
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19449 DSNAOC03 DSNAOC14 DSNAOC15 DSNAOG02 DSNAOG03 DSNAOG08
DSNAOG13 DSNAOG14 DSNAOG15 DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNAOC03
DSNAOC14
DSNAOC15
DSNAOG02
DSNAOG03
DSNAOG08
DSNAOG13
DSNAOG14
DSNAOG15
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI19428 COVER LETTER END
UI19432 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19023 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of XML. *
****************************************************************
* PROBLEM DESCRIPTION: AE PI16473 FIX COMPLETION *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI16473 fix completion.
AE PI16473 FIX COMPLETION
Additional keywords: XMLALL SQLCODE904 SQLXML SQLSTORAGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19023
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOCCN PI19023
DSNNORCN PI19023
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19023 DSNNOCCN DSNNORCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOBXI
DSNNOCCN
DSNNOINS
DSNNORCN
DSNNORES
LISTEND
UI19432 COVER LETTER END
1
UI19465 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15633 -
****************************************************************
* USERS AFFECTED: DB2 users with AUTOSIZE(YES) buffer pools. *
****************************************************************
* PROBLEM DESCRIPTION: Buffer pool size adjustment message *
* MSGDSNB555I may appear too frequently. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When WLM drives DB2's data collection exit for an AUTOSIZE(YES)
buffer pool, DB2 incorrectly returns the number of allocated
buffers for two distinct buffer counts. One of these counts
should be the defined buffer pool size, independent from the
number of buffers allocated. This incorrect information can
cause WLM to drive frequent and redundant size adjustments.
The data collection routine for AUTOSIZE(YES) buffer pools has
been modified to correctly return both the defined and allocated
buffer counts.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15633
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5WDC PI15633
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15633 DSNB5WDC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5WDC
LISTEND
UI19465 COVER LETTER END
UI19506 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20175 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of -DISPLAY *
* DATABASE command *
****************************************************************
* PROBLEM DESCRIPTION: ABEND RC00F9000C DSN9SCNP may happen on *
* DISPLAY DATABASE COMMAND -DIS DB(*) *
* SPACE(*) LOCKS LIMIT(*) ONLY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When attempting to issue the message DSNT390I DISPLAY OF
1 DATABASE CONTINUED, the -DISPLAY DB command processor happened
to hit a PHB message buffer limit. In response, the processor
was expected to issue DSNT390I DISPLAY OF DATABASE TERMINATED
followed by the message DSNT306I RESPONSE MESSAGE LIMIT HAS BEEN
REACHED. However a continuation flag was not reset and
prevented DSNT390I TERMINATED message from issuing. As a result
DSN9SCNP abended 00F9000C.
The database command processor code is fixed to issue DSNT390I
TERMINATED message properly when encountering PHB message buffer
limit.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20175
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDMUL PI20175
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20175 DSNTDMUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDMUL
LISTEND
UI19506 COVER LETTER END
UI19508 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17503 -
****************************************************************
* USERS AFFECTED: All DB2 users of IFCID199 *
****************************************************************
* PROBLEM DESCRIPTION: QW0199SC is not being populated *
* correctly *
****************************************************************
* RECOMMENDATION: *
****************************************************************
QW0199SC introduced by apar pm90422 is used to externalize the
last timestamp of when the dataset statistics has been reported.
.
Within DB2, the dataset statistics timestamp was being
tracked, but did not get externalized in the IFCID 199 trace
record.
DB2 has been modified to externalize the value into the QW0199SC
field in the QW0199 record.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17503
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1DBP PI17503
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17503 DSNB1DBP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DBP
LISTEND
UI19508 COVER LETTER END
UI19519 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17265 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10, and 11 for z/OS users of *
* the IBM Text Search for DB2 z/OS (Omnifind). *
****************************************************************
* PROBLEM DESCRIPTION: This apar will improve query wildcard *
* search functionality for the text *
* search server and enhance the *
* SYSTS_UPDATE stored procedure to *
* significantly improve the performance *
* for updating a small number of rows. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar will deliver the following two improvements.
(1) Improve wildcard searching functionality for the text search
server.
Some wildcard searching will return the expected results while
others may not.
For example, given the appropriate data, if a wildcard search is
performed to search for 'disapprove*', rows will be returned
that contain 'disapproving'. This result is incorrect. If
however we search for 'disapprov*', we will get 'disapproving'.
This is correct.
(2) Enhance the SYSTS_UPDATE stored procedure to enhance
performance for updating a small number of rows.
The user will need to download and install the most current
version of the IBMTS server from this link.
http://www.ibm.com/software/data/db2/zos/downloads/oftss.html
Along with the application of this apar, the included ++HOLD
1 information and instructions should be referenced for improved
wildcard searching using the IBM Text Search and for the
performance improvements offered for the SYSTS_UPDATE stored
procedure.
Additional Keywords: SQLOMNIFIND OMNIFIND TEXTSEARCH INCORROUT
SQLINCORROUT SQLINCORR DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17265
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
unzip TS_fixR1L5.1_linux32.zip
To install or update the IBMTS server, please refer to
1 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
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@O001 PI17265
DSN@O002 PI17265
DSN@O004 PI17265
DSN@O005 PI17265
DSN@O007 PI17265
DSN@O008 PI17265
DSN@O009 PI17265
DSN@O011 PI17265
DSN@O012 PI17265
DSN@O013 PI17265
DSN@O014 PI17265
DSN@O015 PI17265
DSN@O016 PI17265
DSN@O017 PI17265
1 DSN@O019 PI17265
DSN@O021 PI17265
DSN5OCA3 PI17265
DSN5OCA6 PI17265
DSN5OCO3 PI17265
DSN5OCO6 PI17265
DSN5OCU3 PI17265
DSN5OCU6 PI17265
DSN5OPAL PI17265
DSN5OPCR PI17265
DSN5OPDR PI17265
DSN5OPMS PI17265
DSN5OPRE PI17265
DSN5OPSD PI17265
DSN5OPSP PI17265
DSN5OPST PI17265
DSN5OPTO PI17265
DSN5OPUP PI17265
DSN5OTMS PI17265
DSN5OTS PI17265
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17265 DSN@O001 DSN@O002 DSN@O004 DSN@O005 DSN@O007 DSN@O008
DSN@O009 DSN@O011 DSN@O012 DSN@O013 DSN@O014 DSN@O015
DSN@O016 DSN@O017 DSN@O019 DSN@O021 DSN5OCA3 DSN5OCA6
DSN5OCO3 DSN5OCO6 DSN5OCU3 DSN5OCU6 DSN5OPAL DSN5OPCR
DSN5OPDR DSN5OPMS DSN5OPRE DSN5OPSD DSN5OPSP DSN5OPST
DSN5OPTO DSN5OPUP DSN5OTMS DSN5OTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSN@O001
DSN@O002
DSN@O004
DSN@O005
DSN@O007
DSN@O008
DSN@O009
DSN@O011
DSN@O012
DSN@O013
DSN@O014
DSN@O015
DSN@O016
DSN@O017
DSN@O019
DSN@O021
DSN5OCA3
DSN5OCA6
DSN5OCO3
DSN5OCO6
DSN5OCU3
DSN5OCU6
DSN5OPAL
DSN5OPCR
1 DSN5OPDR
DSN5OPMS
DSN5OPRE
DSN5OPSD
DSN5OPSP
DSN5OPST
DSN5OPTO
DSN5OPUP
DSN5OTMS
DSN5OTS
LISTEND
UI19519 COVER LETTER END
UI19540 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18620 -
****************************************************************
* USERS AFFECTED: All DB2 users running CPU parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Various abend codes of RC00E20003 or *
* RC00E20016 or RC00D3001A can occur *
* while running with a CPU parallelism *
* query which may cause DB2 subsystem to *
* crash. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While running with a CPU parallelism query, DB2 may crash with
various abend codes of RC00E20003 or RC00E20016 or RC00D3001A.
The abend primarily is caused by a tremendous amount of storage
(such as 673956K) is allocated in the RID BLOCK POOL. When a
CPU parallelism query is running, the same thread may also run
other applications to allocate RID BLOCK storage, under today
logic, those RID BLOCKs storage will not be freed when an active
parallelism query is still running.
DB2 logic is modified to distinguish which RID BLOCKs are used
by an active parallelism query, for those RID BLOCKs are not
involved in the parallelism query, DB2 can free them even the
active parallelism query is still running.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18620
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNITCUS PI18620
DSNXRTSC PI18620
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18620 DSNITCUS DSNXRTSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNITCUS
DSNXRTSC
LISTEND
UI19540 COVER LETTER END
UI19543 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18965 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of query acceleration *
****************************************************************
* PROBLEM DESCRIPTION: This APAR addresses the following query *
* acceleration items: *
* *
* (1) This APAR provides new function to *
* accelerate a static SELECT INTO *
* statement that is run locally. *
* *
* (2) After a REBIND PACKAGE specifying *
* QUERYACCELERATION for a native *
* SQL (or SQLPL ) procedure package, *
* SQLCODE -313 occurs when a static *
* query bound for acceleration is run *
* from that SQLPL procedure. *
* *
* (3) This APAR provides support to honor *
* the FETCH FIRST n ROWS ONLY clause *
* specified in the PREPARE ATTRIBUTES *
* clause for an accelerated dynamic *
* cursor query. This could improve *
* the overall performance of this *
* accelerated dynamic query by *
* reducing the query's result size. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
(1) Acceleration of a static SQL SELECT INTO statement:
----------------------------------------------------------------
With this APAR/PTF you can now bind a static SQL SELECT INTO
for acceleration to an accelerator. The SELECT INTO must be
run locally in order to be accelerated -- a SELECT INTO that is
to be run remotely at a DB2z server will not be accelerated when
it is run.
.
As with the existing support for static cursor query
acceleration, the existing bind options QUERYACCELERATION and
GETACCELARCHIVE are used to bind the static SELECT INTO for
acceleration. Please see the existing DB2 documentation for more
details describing the usage of these bind options for query
acceleration. To bind a SELECT INTO for acceleration,
a package must be bound or rebound 'after' application of this
PTF. For an SQL PL routine containing the SELECT INTO, instead
of REBIND PACKAGE you must use ALTER PROCEDURE or ALTER FUNCTION
1 specifying option QUERY ACCELERATION.
Packages or SELECT INTO statements previously bound before
this PTF is applied are not affected and those SELECT INTO
statements are not accelerated.
.
After application of this PTF, if a BIND or REBIND PACKAGE with
QUERYACCELERATION (or an ALTER PROCEDURE/FUNCTION with
QUERY ACCELERATION for SQL PL routine) is done for application
containing a SELECT INTO that is to be run remotely at a DB2z
server, the SELECT INTO is bound for acceleration during BIND or
REBIND PACKAGE time (or ALTER PROCEDURE/FUNCTION time).
However, when that SELECT INTO is run remotely, DB2 will fail it
with SQLCODE -4742 and reason code 23.
.
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
.
.
This PTF also provides support for 'accelerator modeling' for
SELECT INTO. Prior to this PTF, accelerator modeling shows
zeroes for "accelerator eligible execution-time elapsed and
CPU times" in the accounting trace IFCID 3 for a SELECT INTO
that is run, which is correct because SELECT INTO could not be
accelerated.
Now, after application of this PTF, if the existing DB2
subsystem parameter ACCELMODEL=YES then a new BIND or REBIND
PACKAGE (or new ALTER PROCEDURE/FUNCTION for SQL PL) will enable
an eligible SELECT INTO for 'accelerator modeling' as it is run
in DB2. If that SELECT INTO is run locally and is eligible for
acceleration, then IFCID 3 will show non-zero values for
"accelerator eligible elapsed and CPU times".
However, if the SELECT INTO is run remotely, then IFCID 3 will
continue to show zeroes for those fields because a SELECT INTO
that is run remotely cannot be accelerated.
.
Note that 'accelerator modeling' does not accelerate a query to
an accelerator -- the query runs only in DB2.
================================================================
.
.
(2) After REBIND PACKAGE with bind option QUERYACCELERATION for
1 a native SQL procedure (SQL PL procedure) package, a static
query bound for acceleration gets SQLCODE -313 when
the procedure is invoked:
----------------------------------------------------------------
For a native SQL procedure (or SQL PL procedure), REBIND PACKAGE
with QUERYACCELERATION for the procedure's package does not
perform all the necessary steps to bind a static query for
acceleration -- this is by design and expected. Instead,
an ALTER PROCEDURE specifying QUERY ACCELERATION is required.
As with attempts to use many other bind options on a REBIND
PACKAGE for an SQL PL procedure package, an attempt to specify
bind option QUERYACCELERATION on the REBIND should fail with
existing message DSNT215. Instead, in this case DB2 accepted
the REBIND PACKAGE with QUERYACCELERATION specified and rebound
the SQL PL package, but, as expected, without completing all the
steps necessary for binding a static query for acceleration in
an SQL PL procedure. As a result, when the procedure was invoked
and DB2 accelerated the query, SQLCODE -313 occurred.
.
With this PTF, DB2 now correctly fails the REBIND PACKAGE with
QUERYACCELERATION for an SQL PL package and issues message
DSNT215 as expected. Note that this problem and fix also apply
to a compiled SQL scalar function (or SQL PL function or UDF ).
An ALTER PROCEDURE or ALTER FUNCTION should be used instead.
.
This problem and restriction is specific to REBIND PACKAGE for
SQL PL routine packages, and does not occur for REBIND PACKAGE
of a regular DB2 package where QUERYACCELERATION bind option is
supported.
================================================================
.
.
(3) Honor FETCH FIRST n ROWS ONLY clause in PREPARE ATTRIBUTES
for an accelerated dynamic query:
----------------------------------------------------------------
This PTF also provides the support to honor the FETCH FIRST n
ROWS ONLY clause specified in the PREPARE ATTRIBUTES for
an accelerated dynamic cursor query. Prior to this PTF, for
an accelerated dynamic query only the FETCH FIRST clause
specified in the query text itself was honored, and a FETCH
FETCH FIRST clause specified in the PREPARE ATTRIBUTES clause
was ignored. So in the PREPARE ATTRIBUTES case all rows
satisfying the accelerated query predicate were returned from
the accelerator, instead of the number of rows specified in
the FETCH FIRST clause of the ATTRIBUTES. Now, by honoring
the ATTRIBUTES FETCH FIRST clause, as we honor FETCH FIRST
specified in the query text, the result size returned from this
case of accelerated query is reduced according to the number
of rows specified in the FETCH FIRST. This can improve
the overall performance of the accelerated dynamic query that
uses PREPARE ATTRIBUTES to specify FETCH FIRST n ROWS ONLY.
.
If you are using a tool to submit your dynamic query to DB2 for
acceleration and that tool specifies FETCH FIRST n ROWS ONLY in
the PREPARE ATTRIBUTES clause, then after application of this
PTF fewer rows may now be returned by the query and available to
1 your application when compared to behavior 'before' this PTF.
.
Note again that prior to this PTF, a FETCH FIRST n ROWS ONLY
clause specified in the query text itself is already honored for
an accelerated query.
Additional search keywords: IDAAV3R1/K IDAAV4R1/K SQLQUERY
SQLFFNR SQLNATIVESQLPL
SQLPROCEDURE SQLSCALARUDF SQLUDF
SQLCODE313 SQLCODE4742 MSGDSNT215I
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18965
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
See PI18965 APAR/PTF cover letter text for more details and
additional information.
DOCUMENTATION:
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
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAB2 PI18965
DSNTBBP2 PI18965
DSNTBRB2 PI18965
DSNXEAAL PI18965
DSNXEPP PI18965
DSNXERT PI18965
DSNXERT2 PI18965
DSNXODML PI18965
DSNXONZC PI18965
DSNXONZO PI18965
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18965 DSNTBAB2 DSNTBBP2 DSNTBRB2 DSNXEAAL DSNXEPP DSNXERT
DSNXERT2 DSNXODML DSNXONZC DSNXONZO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNTBAB2
DSNTBBP2
DSNTBRB2
DSNXEAAL
DSNXEPP
DSNXERT
DSNXERT2
DSNXODML
DSNXONZC
DSNXONZO
LISTEND
UI19543 COVER LETTER END
UI19571 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13190 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* list prefetch and concurrent REORG. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E in DSNIDM.DSNISRID at *
* ERQUAL5013 or an incorrout may occur *
* for a query using a list prefetch *
* access path after a REORG. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend or incorrout may occur if DB2 attempts to retrieve a
row for a record id (RID) that does not exist. For list prefetch
(PLAN_TABLE.PREFETCH = L) access paths, DB2 retrieves the list
of RIDs through an index. If the list overflows the RID pool,
DB2 may write the RIDs to a workfile. Because a lock is not held
in some scenarios, a concurrent REORG may execute and change the
RID values. The problem can occur for cursors defined with hold
against a partitioned table space.
The DB2 code was modified to prevent REORG on a table space or
a partition while using list prefetch to retrieve RIDs from a
workfile.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13190
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICMT2 PI13190
DSNIDALC PI13190
DSNIRSVP PI13190
DSNITCUS PI13190
1 DSNXREOJ PI13190
DSNXRFF PI13190
DSNXRFN PI13190
DSNXRFRL PI13190
DSNXROJ1 PI13190
DSNXRRID PI13190
DSNXRSFN PI13190
DSNXRSGB PI13190
DSNXRT1J PI13190
DSNXSBUC PI13190
DSNXSIND PI13190
DSNXSING PI13190
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13190 DSNICMT2 DSNIDALC DSNIRSVP DSNITCUS DSNXREOJ DSNXRFF
DSNXRFN DSNXRFRL DSNXROJ1 DSNXRRID DSNXRSFN DSNXRSGB
DSNXRT1J DSNXSBUC DSNXSIND DSNXSING
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICMT2
DSNIDALC
DSNIRSVP
DSNITCUS
DSNXREOJ
DSNXRFF
DSNXRFN
DSNXRFRL
DSNXROJ1
DSNXRRID
DSNXRSFN
DSNXRSGB
DSNXRT1J
DSNXSBUC
DSNXSIND
DSNXSING
LISTEND
UI19571 COVER LETTER END
UI19578 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17360 -
****************************************************************
* USERS AFFECTED: All DB2 user who is running migration job *
* DSNTIJEN and have real time statistics RTS *
* for last used information in SYSPACKAGE *
* enabled. *
****************************************************************
* PROBLEM DESCRIPTION: When RTS is enabled and DSNTIJEN is *
* running, customer may hit ABEND04E *
* RC00C90111 at DSNIFPSC ERQUAL5011. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
DSNTIJEN alters SYSPACKAGE during migration, RTS could update
SYSPACKAGE for lastused column at the same time. There is a
small window, the incorrect internal id for SYSPACKAGE could be
used by RTS, which results in the above abend.
DB2 has been changed to close the window to avoid the abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17360
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGERTS PI17360
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17360 DSNGERTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGERTS
LISTEND
UI19578 COVER LETTER END
UI19587 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17945 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS or DB2 11 for z/OS users of *
* REORG TABLESPACE of a LOB table space *
****************************************************************
* PROBLEM DESCRIPTION: Performance improvement for REORG *
* TABLESPACE of a LOB table space *
****************************************************************
* RECOMMENDATION: Apply PTF when available *
****************************************************************
REORG TABLESPACE for LOB table space performance enhancement.
Modified logic for a REORG TABLESPACE of a LOB table space to
improve performance. This performance modification does not
apply when the LOB table space is processed using AUX YES on
a REORG of a base table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17945
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURLOB PI17945
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17945 DSNURLOB
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURLOB
LISTEND
UI19587 COVER LETTER END
UI19598 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18033 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNB260I is not issued for a long *
* running reader if this agent had made *
* some updates followed by a COMMIT *
* before becoming an un-committed long *
* running reader. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an agent performs some kind of update followed by a
COMMIT, then continues as an un-committed long running reader,
DB2 incorrectly skips issuing MSGDSNB260I message for this
reader.
DB2 has been fixed to issue MSGDSNB260I message for all
un-committed long running readers.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18033
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PCK PI18033
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18033 DSNB1PCK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PCK
LISTEND
UI19598 COVER LETTER END
UI19624 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18534 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, *
* and DB2 11 for z/OS users. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Recompile for module declaration *
* changes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Recompile for module declaration changes.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18534
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXVCTS PI18534
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18534 DSNXVCTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXVCTS
LISTEND
UI19624 COVER LETTER END
UI19629 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17867 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users *
* of compressed table spaces *
* and replication. *
****************************************************************
* PROBLEM DESCRIPTION: When DataBase is in RREPL (Read and *
* Replication restrictive access state), *
* DB2 failed to build the compression *
* dictionary when replicating data. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A properly authorized data replication program should be
allowed to build the compression dictionary. However without
proper checking, DB2 denied its request to build the compression
dictionary with a DSNT501I message and reason code of 00C90224.
Fixes made in DB2, a properly authorized replication program
will now be allowed to build the compression dictionary when
the DataBase is in RREPL state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17867
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBET PI17867
DSNISRTI PI17867
DSNUZLCR PI17867
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17867 DSNIDBET DSNISRTI DSNUZLCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBET
DSNISRTI
DSNUZLCR
LISTEND
UI19629 COVER LETTER END
UI19644 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11167 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* run a FREE PACKAGE(*) command with the *
* option PLANMGMTSCOPE(INACTIVE). *
****************************************************************
* PROBLEM DESCRIPTION: FREE PACKAGE(*) PLANMGMTSCOPE(INACTIVE) *
* fails with message DSNT234I indicating *
* the message space limit exceeded. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
FREE PACKAGE(*) PLANMGMTSCOPE(INACTIVE) fails with message
DSNT234I indicating the message limit exceeded.
There were too many unnecessary and misleading messages produced
during the FREE process. Specifically DSNT232I was issued for
each package no matter whether inactive copies of the package
exist or not.
Additional Keywords:
MSGDSNT234I MSGDSNT232I MSGDSNT299I
Code has been changed so DSNT232I is issued only when inactive
copies of a package exist and are freed successfully. When none
of the packages specified in the command has any inactive copy,
an informational message DSNT299I is issued to indicate no
inactive copies exist.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11167
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
1 PI11167 introduces a new informational message DSNT299I.
DSNT299I
csect-name NO INACTIVE COPIES EXIST FOR PACKAGE = package-name
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNFMDIR PI11167
DSNFTDIR PI11167
DSNTBAP PI11167
DSNTBFR2 PI11167
DSNTBMSG PI11167
DSNTBSPM PI11167
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11167 DSNFMDIR DSNFTDIR DSNTBAP DSNTBFR2 DSNTBMSG DSNTBSPM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFMDIR
DSNFTDIR
DSNTBAP
DSNTBFR2
DSNTBMSG
DSNTBSPM
LISTEND
UI19644 COVER LETTER END
UI19653 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19974 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: The following symptom may occur during *
* COMMIT processing for remote *
* applications connected to a DB2 for *
* z/OS server. *
* - ABEND 04E-00D31010 *
* LOC=DSNLILLM.DSNLQINA:0015 *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application uses the IBM Data Server Driver to connect
to a DB2 for z/OS server, and executes one or more SQL
statements. The application then sets the CURRENT PACKAGE PATH
special register, and executes additional SQL statements,
followed by a COMMIT. During COMMIT processing, DDF did not
clean up all its internal controls blocks. This led to the
ABEND 04E-00D31010 LOC=DSNLILLM.DSNLQINA:0015 when DDF attempted
to inactivate the connection. The following conditions are
required for the reported error to occur:
. DB2 is configured with DDF THREADS=INACTIVE (DSN6FAC CMTSTAT
INACTIVE)
. IBM Data Server Driver packages are bound KEEPDYNAMIC(YES)
. Application sets the CURRENT PACKAGE PATH special register
DB2 has been corrected to free all required internal control
blocks during COMMIT, thus allowing the connection to be
inactivated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19974
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXPCA PI19974
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19974 DSNLXPCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXPCA
LISTEND
UI19653 COVER LETTER END
UI19690 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19676 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of SQL *
* statement containing scalar fullselect and *
* expressions which are defined as index keys. *
****************************************************************
* PROBLEM DESCRIPTION: 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 *
1 * referenced in another expression. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
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.
The following example helps to illustrate above problem:
DDL:
CREATE TABLE TEST.T1 (C1 INT, C2 VARCHAR(10));
CREATE INDEX TEST.IOE ON TEST.T1 (UPPER(C2));
SQL:
SELECT (SELECT A.C1
FROM TEST.T1 AS A
WHERE UPPER(A.C2) = 'ABC') + 99 AS COL#1
FROM SYSIBM.SYSDUMMY1;
DB2 didn't handle the key-expression UPPER(C2) within scalar
fullselect correctly, which reduced that the index TEST.IOE
was not used.
DB2 code has been modified correctly to process aforementioned
problem.
Additional keywords: SQLINDEXONEXP SQLSCALAR SQLFULLSELECT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19676
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOKEX PI19676
DSNXOWPT PI19676
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19676 DSNXOKEX DSNXOWPT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOKEX
DSNXOWPT
LISTEND
UI19690 COVER LETTER END
UI19693 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17079 -
****************************************************************
* USERS AFFECTED: All users of subsystem parameter *
* DSN6SPRM.FCCOPYDDN in DB2 10 for z/OS and *
* DB2 11 for z/OS are affected by this APAR. *
****************************************************************
* PROBLEM DESCRIPTION: When the DSN6SPRM.FCCOPYDDN parameter *
* is specified with a DB2 Utilities *
* template name that contains substring *
* notation, that is one which contains *
* parentheses and which may also contain *
* a comma, assembly of the subystem *
* parameter (DSNZPxxx) module fails with *
* code 12 and one or more occurrences of *
* the following message: *
* ASMA254I *** MNOTE *** ... **INVALID *
* CHARACTER n IN DEFAULT *
* TEMPLATE *
* *
* Likewise, when the DEFAULT TEMPLATE *
* NAME field on installation panel *
* DSNTIP6 (DB2 10) or DSNTIP61 (DB2 11) *
* specifies a DB2 Utilities template name *
* that contains substring notation, it *
* fails field validation with this *
* message: *
* DSNT560I Entry is not a valid DB2 *
* Utilities TEMPLATE data set *
* name expression *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
DB2 subsystem parameter DSN6SPRM.FCCOPYDDN specifies the default
setting of the FCCOPYDDN parameter for the following DB2
utilities:
* COPY (when DSN6SPRM.FLASHCOPY_COPY=YES)
* LOAD (when DSN6SPRM.FLASHCOPY_LOAD=YES)
* REORG TABLESPACE (when DSN6SPRM.FLASHCOPY_REORG_TS=YES)
* REBUILD INDEX (when DSN6SPRM.FLASHCOPY_REBUILD_INDEX=YES)
* REORG INDEX (when DSN6SPRM.FLASHCOPY_REORG_INDEX=YES)
FCCOPYDDN specifies a DB2 Utilities template data set name
1 expression to be used to derive the copy data set name to be
allocated by the utility during operation.
DSN6SPRM.FCCOPYDDN is externalized as DEFAULT TEMPLATE. In DB2
10, this field appears on installation panel DSNTIP6; in DB2 11,
it appears on installation panel DSNTIP61.
Currently, both DSN6SPRM.FCCOPYDDN and DEFAULT TEMPLATE do not
accept template names that contain variables with substring
notation. For example:
&VAR(1).
&VAR(2,1).
Template names that contain substring notation are rejected with
the symptoms noted in the problem description section of this
APAR.
In response, this APAR modifies DSN6SPRM.FCOPYDDN and DEFAULT
TEMPLATE NAME to accept template names that contain substring
notation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17079
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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
from the updated DSNTIP6 panel in your prefix.SDSNSPFP library.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIP6 PI17079
DSN6SPCK PI17079
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17079 DSNTIP6 DSN6SPCK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIP6
DSN6SPCK
LISTEND
UI19693 COVER LETTER END
UI19696 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI17700 -
****************************************************************
* USERS AFFECTED: All users of the DB2 Interactive (DB2I) *
* facility in DB2 10 for z/OS and DB2 11 for *
* z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: Batch JCL jobs generated by DB2I fail *
* with a JCL error and one or more of *
* the following messages: *
* IEFC452I INVALID - JOB NOT RUN - *
* JCL ERROR *
* IEFC662I INVALID LABEL *
* because the job name in the job card *
* included by DB2I exceeds 8 characters. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
The DB2I facility provides a convenient DB2 interface for
running ad-hoc SQL queries (SPUFI), generating host language
data structures for tables and views (DCLGEN), preparing and
executing host applications (PROGRAM PREPARATION and RUN),
managing packages and plans (BIND/REBIND/FREE), processing
commands (DB2 COMMANDS), and running utilities (UTILITIES).
Some DB2I functions such as PROGRAM PREPARATION and UTILITIES
have an option to generate and run batch JCL. Generated jobs
include the job card specified on DB2I defaults panel 2
(DSNEOP02). By default, DB2I initializes the job name as the
TSO user ID followed by the letter 'A'.
Currently, if the user ID exceeds 7 characters when the job
card is initialized, jobs generated by DB2I can fail with the
symptoms noted in the Problem Description section of this APAR.
In response, this APAR modifies DB2I to check the length of the
TSO user ID when initializing the job card fields on panel
DSNEOP02. When a user ID consists of more than 7 characters,
DB2I will form the job name from the first 7 characters and add
the letter 'A'. This change will prevent JCL errors caused by
DB2I generating an invalid job name when the user ID is longer
than 7 characters.
COMPONENT: 5740-XYR00-JDBAA14
APARS FIXED: PI17700
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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
1 from the SDSNPFPE target library.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNEOP02 PI17700
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17700 DSNEOP02
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNEOP02
LISTEND
UI19696 COVER LETTER END
UI19720 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20280 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users that rebind packages. *
****************************************************************
* PROBLEM DESCRIPTION: Space used for the DSNDB01.SPT01 *
* table space can grow when packages *
* are rebound. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When rebinding a package, free space might not be used
efficiently causing the table space to grow. This was caused by
an incorrect value in a control block describing the table
space and can start once the table space is changed to a 32k
page in V10 ENFM.
The internal control block that describes DSNDB01.SPT01 table
space has been corrected to efficiently use the free space.
This does not reclaim free space if REBIND PACKAGE was done
before the APAR was applied. REORG TABLESPACE can be used to
reclaim unused free space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20280
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEDB1 PI20280
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20280 DSNGEDB1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEDB1
1
LISTEND
UI19720 COVER LETTER END
UI19722 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18184 -
****************************************************************
* USERS AFFECTED: All DB2 for z/Os users running accounting *
* class 3 reports for P-locks, and all users *
* IFCID 21 trace records. *
****************************************************************
* PROBLEM DESCRIPTION: 1. High "other P-lock" suspension times
*
* reported in DB2 accounting class 3. *
* 2. IFCID 21 trace records don't show *
* lock resource name for a Change lock *
* requests (upgrade case only). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. DB2 Pageset P-lock suspension time during the Pageset P-lock
negotiations, is incorrectly reported and shows up in the
OTHER bucket(QWACAWTQ) instead of the PARENT P-LOCK bucket.
This error in accounting is caused by use of lock token
instead of the lock resource name when a request is sent
to IRLM.
2. IFCID 21 traces for lock change requests don't show the lock
resource name even when lock token and resource name both
were set in the request to IRLM. IFCID 21 detail report
shows "N/P" for the resource name(QW0021RN) and
type(QW0021KT) in the output, which makes it difficult to
correlate that record with a lock resource.
This APAR corrects an accounting error in class 3 reporting.
Pageset P-lock suspension times will be accounted in PARENT
P-LOCK bucket instead of OTHER.
Code has been changed to show the lock resource name and type
in IFCID 21 trace record for lock change requests.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18184
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PLK PI18184
DSNTLLDS PI18184
DSNTLLOC PI18184
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18184 DSNB1PLK DSNTLLDS DSNTLLOC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PLK
1 DSNTLLDS
DSNTLLOC
LISTEND
UI19722 COVER LETTER END
UI19725 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17840 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of UNLOAD XML with file reference *
* variables (FRV) *
****************************************************************
* PROBLEM DESCRIPTION: UNLOAD XML FRV did not honor &PA and *
* &PART for the XML FRV even though *
* partition parallelism is used. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
UNLOAD XML FRV substituted 00000 for &PART or &PA on the XML
FRV
TEMPLATE even though partition parallelism was active. The &PA
and &PART substitution variables should be used when partition
parallelism is active.
UNLOAD has been changed to correct the aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17840
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULDB PI17840
DSNUULPB PI17840
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17840 DSNUULDB DSNUULPB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULDB
DSNUULPB
LISTEND
UI19725 COVER LETTER END
UI19744 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17868 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of queries with *
* row expression predicates *
****************************************************************
1 * PROBLEM DESCRIPTION: 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may produce incorrect output for a query with a row
expression predicate if all the following conditions are
satisfied:
1. Access type "N" or "IN" is selected to access the
table with
the row expression predicate;
2. Not all the columns in the row expression predicate are
selected as the matching columns;
3. The query avoids sort for operations which require order,
such as ORDER BY, GROUP BY, sort merge join, etc. The required
order is the index key order.
For example,
SELECT
FROM T1
WHERE (C1,C2,C4) IN
(SELECT C1,C2,C4
FROM T2
GROUP BY C1,C2,C4)
ORDER BY C1,C2,C3;
If there is an index defined on T1(C1,C2,C3) and the index is
selected to access T1 with access type "N", DB2 may not
perform
sort for the ORDER BY. However, the result may not be returned
in the index key order. A sort operation is needed to ensure
the result is in the correct order.
Additional Keywords:
SQLINCORROUT DB2INCORR/K SQLINCORR INCORROUT SQLINSUBQ
SQLORDERBY SQLGROUPBY ROWEXPRESSION
DB2 has been modified to perform a sort for the case described
above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17868
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 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.
DB2BIND:
***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
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCSC PI17868
DSNXOGBM PI17868
DSNXOPRP PI17868
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17868 DSNXOCSC DSNXOGBM DSNXOPRP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSC
DSNXOGBM
DSNXOPRP
LISTEND
UI19744 COVER LETTER END
UI19760 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17747 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of ALTER TABLE *
* SET DATA TYPE or ALTER VIEW *
****************************************************************
* PROBLEM DESCRIPTION: User receives ABND=0C4-00000004, *
* LOC=DSNXIDDL.DSNXIRTR+2EB2 when *
* executing ALTER TABLE SET DATA TYPE *
* or ALTER VIEW *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An ABND=0C4-00000004,LOC=DSNXIDDL.DSNXIRTR+2EB2 may occur during
ALTER TABLE SET DATA TYPE or ALTER VIEW processing. This occurs
because DB2 incorrectly utilizes memory while executing the
affected statements.
Note that other unexpected behavior or symptoms may occur from
executing the affected statements.
DB2 has been updated to utilize memory appropriately while
processing the ALTER TABLE SET DATA TYPE and ALTER VIEW
statements.
Additional Keywords:
SQLALTER
ABEND0C4
RC00000004
DSNXIRTR
2EB2
OFFSET2EB2
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17747
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIRTR PI17747
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17747 DSNXIRTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIRTR
LISTEND
UI19760 COVER LETTER END
UI19764 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12905 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE utility with *
* LOG YES, SHRLEVEL NONE, using partition *
* parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: -TERM UTIL command does not delete *
* SYSLGRNX rows written by REORG utility *
* prior to a failure. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A REORG TABLESPACE utility with LOG YES SHRLEVEL NONE and
1 partition parallelism abended in the RELOAD phase. A
subsequent -TERM UTIL command failed to delete the associated
rows written by the REORG to DSNDB01.SYSLGRNX for the target
table space, potentially leading to unpredictable results.
In order for -TERM UTILITY to properly clean up SYSLGRNX
after a failed REORG, the REORG utility must set values in
DSNDB01.SYSUTILX which are valid in the event a -TERM UTILITY
command is later used. This problem occurred because one of
the fields was not set correctly.
Note that after a similar failed REORG, the -START DATABASE...
SPACE...ACCESS(FORCE) command could also fail to clean up
SYSLGRNX records due to this problem.
The required SYSUTILX field is now set properly by REORG
utility.
Additional keywords: SQLCODE904 RC00C2010D MSGDSNB232I DSNB232I
downlevel detection
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12905
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURPRD PI12905
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12905 DSNURPRD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURPRD
LISTEND
UI19764 COVER LETTER END
UI19796 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19987 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS, and DB2 11 for z/OS *
* customers running REORG TABLESPACE utility *
* using DB2 Sort for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: The REORG TABLESPACE utility was using *
* DFSORT for index sorting even though *
* DB2 Sort for z/OS was enabled and used *
* for the single data sort. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When the REORG TABLESPACE utility is running with a single data
sort process which requires a large portion of the available
memory it is possible that the utility will fall back to DFSORT
1 when sorting of the index keys begins due to an incorrect
memory assignment between data and index sorts.
Code has been changed to reserve sufficient memory resources
for index sorting with DB2 Sort for z/OS during REORG.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19987
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGSRT PI19987
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19987 DSNUGSRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGSRT
LISTEND
UI19796 COVER LETTER END
UI19800 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17573 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* use IBM DB2 Analytics Accelerator (IDAA). *
****************************************************************
* PROBLEM DESCRIPTION: The following problems are reported: *
* *
* 1. -STOP/-START ACCEL command hang. *
* *
* 2. DB2 abend with ABEND=04E-00D31010, *
* LOC=DSNLIGLM.DSNLCCNR+1378, +1326, *
* +1564, +150A, etc. *
* This abend may lead to symptom 1. *
* *
* 3. DB2 abend with ABEND=0C4-00000038, *
* LOC=DSNX8LLM.DSNX8EKG+26D2, +26B4, *
* +2644, +26B8, etc. *
* This abend may lead to symptom 1. *
* *
* 4. After TCP/IP or communication *
* failure, Accelerator Services will *
* be terminated without user issuing *
* the -STOP ACCEL command. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Accelerator services must handle many errors and abend
conditions. It must allow the service to complete as a result
1 of normal and abnormal termination events. In addition,
Accelerator services should allow an automatic reconnect to the
IDAA server after a communication failure.
The following problems are reported:
1. -STOP/-START ACCEL command hang. Any abends in DSNX8EKG
may put the DSNX8EKG process in an inconsistent state which
prevents the shutdown of Accelerator and DDF services. The
Accelerator Status will remain in STOPPEND forever until
DB2 is recycled. A -STOP ACCEL MODE (FORCE) has no effect.
2. Due to a TCPIP or communication failure, DB2 may abend with
ABEND=04E-00D31010, LOC=DSNLIGLM.DSNLCCNR+1378, +1326,
+1564, +150A, etc. This abend may lead to symptom 1.
3. Due to a DSNX8EKG logic error, ABEND=0C4-00000038, LOC=
DSNX8LLM.DSNX8EKG+26B4, +2644, +26D2, +26B8, etc may occur.
This abend may lead to symptom 1.
4. After a communication failure, Accelerator services will be
terminated without the user issuing a -STOP ACCEL command.
Accelerator services have been enhanced to provide more
meaningful messages and better stability. It now allows
the heartbeat connection to be re-established after a
communication failure. Accelerator services is also enhanced
to tolerate abend conditions. Any fatal error will cause the
Accelerator services to stop and a -STOP ACCEL MODE(FORCE)
command will stop the Accelerator service immediately.
DSNX870I and DSNX871I message reporting have been enhanced.
IDAA for z/OS considers an Accelerator to be Online when
communication with the Accelerator is successful and the
Accelerator has reported its status to be ONLINE. When
Accelerator is not reachable or Accelerator has reported its
condition has changed, IDAA for z/OS considers the Accelerator
to be NOT ONLINE and no queries will be offloaded.
Message DSNX871I will be issued when Accelerator comes Online.
DSNX871I
csect-name ACCELERATOR accelerator-name IS ONLINE
Message DSNX870I will be issued when Accelerator comes Offline.
DSNX870I
csect-name ACCELERATOR accelerator-name IS NOT ONLINE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17573
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX8API PI17573
DSNX8EKG PI17573
DSNX8STA PI17573
DSNX8WAC PI17573
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17573 DSNX8API DSNX8EKG DSNX8STA DSNX8WAC
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX8API
DSNX8EKG
DSNX8STA
DSNX8WAC
LISTEND
UI19800 COVER LETTER END
UI19815 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11316 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of user-created *
* catalog indexes *
****************************************************************
* PROBLEM DESCRIPTION: User receives resource unavailable *
* errors related to user-created catalog *
* indexes during migration *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Users may receive object or resource unavailable errors related
to user-created catalog indexes during migration.
These errors include, but are not limited to the following:
- Errors with reason code 00D70014
- Errors with reason code 00E50013
This problem occurs because DB2 encounters unexpected
user-created catalog index definitions that interfere with the
migration process.
DB2 is modified to make all new catalog indexes DB2-managed and
be created in the DB2 catalog data space. This behavior will be
in effect in DB2 10 enabling new-function mode and on.
When creating an index on the catalog, the STOGROUP and VCAT
clauses are ignored. An SQL warning is not returned when the
clauses are ignored. The following catalog table values are set
instead:
- SYSIBM.SYSINDEXES.ERASERULE = 'N'
- SYSIBM.SYSINDEXPART.STORTYPE = 'E'
- SYSIBM.SYSINDEXPART.STORNAME = '00000001'
- SYSIBM.SYSINDEXPART.VCATNAME = '00000001'
- SYSIBM.SYSINDEXPART.PQTY = -1
- SYSIBM.SYSINDEXPART.SQTY = -1
When altering a catalog index, the STOGROUP and VCAT clauses are
ignored. An SQL warning is not returned when the clauses are
ignored.
Applying this APAR does not change existing user-created catalog
1 indexes. These indexes must be dropped and recreated for them to
function correctly.
This APAR also modifies the following premigration check jobs
for DB2 10 and 11 as indicated:
* DB2 10 premigration check jobs: DSNTIJPM (in DB2 10) and
DSNTIJPA (in DB2 9)
- Report 2 is modified to identify all user-defined indexes on
the DB2 catalog. After you have completed migration to
DB2 10 new-function mode, you need to drop and recreate
these indexes to make them reside in the DB2 catalog space.
- Report 3 is discontinued.
* DB2 11 premigration check jobs: DSNTIJPM (in DB2 11) and
DSNTIJPB (in DB2 10)
- Report 2 is modified to identify all user-defined indexes on
the DB2 catalog that do not reside in the DB2 catalog space.
You need to drop and recreate these indexes before you
migrate to the next release of DB2.
- Report 3 is discontinued.
The DB2 for z/OS SQL Reference for Version 10 and Version 11 has
been updated to indicate that all indexes on the catalog are now
DB2-managed and the USING clause of CREATE and ALTER INDEX is
ignored for these indexes.
Specifically, the following changes are made:
- In the CREATE INDEX topic, under "Using clause for
non-partitioned indexes," any references to specifying USING
for catalog tables have been removed.
- The CREATE INDEX topic has the following new section:
"User-defined indexes on catalog tables", and it summarizes
the new behavior associated with this APAR.
- The CREATE INDEX topic no longer has the recommendation to
create any user-created indexes on any DB2 catalog tables in
user-managed data sets.
- In the "SQL statements allowed on the catalog" topic, under
CREATE INDEX, the USING clause is added to the list of clauses
that are ignored.
Additionally, the following publications for Version 10 and
Version 11 has been updated as follows:
- The Installation Guide adds a release incompatibility to
indicate that all indexes on the catalog are DB2-managed. It
also instructs the user to see the report and recommendations
from job DSNTIJPM if there are existing user-defined indexes
on the catalog.
- The Administration Guide information on defining index space
storage has been modified to distinguish between catalog and
non-catalog indexes. It also notes that references to the
USING clause of CREATE and ALTER INDEX only apply to
non-catalog indexes.
- The Utility Guide instructions for recovering the catalog and
directory now states that the procedure assumes users have
applied this APAR. It also no longer recommends that catalog
indexes be user-managed.
1 Additional Keywords:
SQLCREATE
SQLALTER
SQLMIGRATION
DB2MIGV10/K
DB2MIGV11/K
RC00D70014
RC00E50013
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11316
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
ACTION:
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.
ACTION:
***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
1 - 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.
ACTION:
***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:
- 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.
ACTION:
***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
1 - 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIJPB PI11316
DSNTIJPM PI11316
DSNXIAIX PI11316
DSNXICX2 PI11316
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11316 DSNTIJPB DSNTIJPM DSNXIAIX DSNXICX2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIAIX
DSNXICX2
MACROS
DSNTIJPB
DSNTIJPM
LISTEND
UI19815 COVER LETTER END
UI19886 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20543 -
****************************************************************
* USERS AFFECTED: DB2 V10 data sharing users, running in *
* compatibility mode. *
****************************************************************
* PROBLEM DESCRIPTION: Performance degradation when running *
* utilities or DDL against partition by *
* growth (PBG) table spaces, due to *
* excessive locking. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a drain is requested by a utility or DDL job on a PBG
table space, and the drain includes all defined partitions, it
is converted to a space-level drain. In V10 compatibility mode,
1 the space-level drain has to acquire drain locks for every part
up to MAXPARTITIONS. For a table space with a high value for
MAXPARTITIONS, this can drive thousands of additional lock
requests, resulting in poor performance. The worst case is
for a PBG table space with MAXPARTITIONS 4096 and only one
active part.
The logic which determines whether to promote a single-part or
part-range drain request to a space-level drain has been changed
to consider the MAXPARTITIONS value for a PBG table space in V10
compatibility mode.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20543
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICLDR PI20543
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20543 DSNICLDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICLDR
LISTEND
UI19886 COVER LETTER END
UI19891 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19307 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of the BIND command *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNTBAP.DSNTBAP2 during *
* BIND. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 in DSNTBAP.DSNTBAP2 during BIND. This problem is
most likely to occur on z/OS V2R2.
Additional Keywords:
OFFSET4734 OFFSET4B98
DB2 code has been corrected to avoid the abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19307
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAP2 PI19307
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19307 DSNTBAP2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBAP2
LISTEND
UI19891 COVER LETTER END
UI19895 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17470 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of clone tables. *
****************************************************************
* PROBLEM DESCRIPTION: Various statistics are not used for *
* optimization of a query against a *
* clone table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Optimization of a query referencing a clone table should use
the statistics from the base table. The following statistics
are incorrectly read from the clone table.
* SYSTABLES.PCTROWCOMP
* All SYSTABSTATS statistics
Since RUNSTATS cannot be run against the clone table, reading
these statistics for the clone table instead of the base table
object is guaranteed to result in default statistics.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE SQLSTATS
DB2 has been modified to use statistics from the base table
when optimizing a clone table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17470
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
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.
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTL PI17470
DSNXOTPL PI17470
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17470 DSNXOTL DSNXOTPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTL
DSNXOTPL
LISTEND
UI19895 COVER LETTER END
UI19897 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21017 -
****************************************************************
* USERS AFFECTED: DB2 users of stored procedures and *
* User Defined Functions (UDFs). *
****************************************************************
* PROBLEM DESCRIPTION: During stored procedure or UDF *
* execution, user abend0C4 may occur *
* at DSNX9GPL +0E7C *
* or incorrect code path may be taken *
* which can lead to unpredictable *
* result. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 code is missing a test for a zero pointer before the
code references the offset from that pointer. This may
result in abends, overlays, or incorrect code paths since
1 the storage content of the offset can be unpredictable.
DB2 code has been fixed to add the test of zero pointer
before accessing the storage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21017
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9GPL PI21017
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21017 DSNX9GPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9GPL
LISTEND
UI19897 COVER LETTER END
UI19900 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20352 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* who are using, or plan to use, *
* High Performance DBAT support. That is, *
* users which operate DDF with option *
* PKGREL(BNDOPT). *
****************************************************************
* PROBLEM DESCRIPTION: New function is being provided to *
* reduce the CPU required to manage *
* High Performance DBATs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 10 for z/OS introduced a new DDF server thread processing
mode called High Performance DBATs. If DDF has been modified
to operate in this mode (-MODIFY DDF PKGREL(BNDOPT)), DDF keeps
a client connection attached to its DBAT for up to 200 units-
of-work. The DBAT must have allocated a package which was
bound with the RELEASE DEALLOCATE bind option to activate high
performance DBAT processing. Also, the 200 units-of-work must
not hold resources, such as open WITH HOLD cursors, declared
global temporary tables, and/or LOB locators, past any
transaction end of unit-of-work.
Currently, as soon as the client connection terminates, DDF
also terminates the associated DBAT if the DBAT has operated
in high performance DBAT mode. That is, DDF will not attempt
to pool the high performance DBAT regardless of how many
units-of-work the connection/DBAT has processed. If a client
connection terminates before using a high performance DBAT for
1 more than 200 units-of-work, DDF could potentially use more CPU
to create new DBATs for the benefit of subsequent connections.
DB2 has been changed to pool a high performance DBAT when the
associated connection terminates. DDF will still only allow
the DBAT to be pooled for up to 200 units-of-work. The
improved availability of pooled DBATs will help reduce the CPU
cost that would otherwise be required to create a new DBAT when
needed.
Also, in order to prevent a high performance DBAT from being
pooled indefinitely, or until DDF has been recycled, when the
POOL THREAD TIMEOUT (DSN6FAC POOLINAC) subsystem parameter is
set to 0, DB2 will internally apply a default value of 120
seconds.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20352
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLEDDA PI20352
DSNLQCTL PI20352
DSNLQDIS PI20352
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20352 DSNLEDDA DSNLQCTL DSNLQDIS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLEDDA
DSNLQCTL
DSNLQDIS
LISTEND
UI19900 COVER LETTER END
UI19902 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21701 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4-04 attempting to store into *
* storage allocated from a key 7 SP241 *
* page that has been invalidly page *
* protected. Most likely the abends *
* will occur in DB2 or IRLM modules. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If the DSN6SPRM PROTOFF=NO DSNZPARM option is set (or is
set to NO by default), DB2 will page protect the complete
4K pages of the DB2 Early code to prevent code overlays.
1 The end of the DSN3EPX load module was not being calculated
correctly by DSN3UR00. This did not cause a problem until
all the DB2 Version 11 Early Code PTFs up to and including
UI18946 were applied. This caused the size of the DSN3EPX
load module to become x'AF18' bytes in length. Since the
module is loaded into storage allocated on a page boundary,
the module then extended into the last x'100' bytes of the
last 4K page. This exposed a base code problem calculating
the ending address of the load module. DB2 then incorrectly
page protected the last page which contained 232 bytes of
available space in the key 7, SP241 page. If another
storage request allocated storage in this page, any update
to the storage would abend with S0C4-04 as the page is
page protected.
There is no problem with the code change in PTF UI18946, but
it was decided to flag the PTF as PE so users would not be
exposed to this base code problem.
The incorrect ending address of the DSN3EPX load module stored
in the EEPL control block has been corrected in DSN3UR00.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI21701
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
ACTION:
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
ACTION:
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
ACTION:
This PTF updates the ERLY code. After you apply this fix,
1 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
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3UR00 PI21701
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21701 DSN3UR00
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3UR00
LISTEND
UI19902 COVER LETTER END
UI19954 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19263 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNOBSE M401 or *
* ABEND04E RC00E70005 DSNNOBSE M406 may *
* occur when processing the binary XML *
* document and the SYSIBM.SYSXMLSTRINGS *
* table is not available. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The SYSIBM.SYSXMLSTRINGS table is required when processing the
binary XML document. When the SYSIBM.SYSXMLSTRINGS table is not
1 available, the resource not available return code is not handled
properly. This causes the ABEND to occur.
DB2 is modified, so SQLCODE -904 will be issued instead of the
ABEND.
Additional keywords: SQLXML XMLALL SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19263
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOBSC PI19263
DSNNOBSE PI19263
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19263 DSNNOBSC DSNNOBSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOBSC
DSNNOBSE
LISTEND
UI19954 COVER LETTER END
UI19960 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18117 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of hybrid join parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXRTSS *
* :M113 may occur when a complex query *
* contains high level of nested hybrid *
* join running in parallel. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXRTSS :M113 may occur when a
complex query contains high level of nested hybrid join running
in parallel straw model. It is because the reserved storage for
saving the original table objects information and hybrid join
operation setting is not big enough, hence triggers the sanity
check.
It is not query dependent. Any complex query contains high
level of nested hybrid join running in parallel straw model
could hit this intentional abend.
DB2 is modified to dynamic allocate enough storage to save all
the necessary table objects information and hybrid join
operation setting for parallel straw model.
1
Additional Keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K
SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18117
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRTSS PI18117
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18117 DSNXRTSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRTSS
LISTEND
UI19960 COVER LETTER END
UI19996 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18258 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of EXPLAIN STMTCACHE STMTID. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at *
* DSNXGRDS DSNXEXPL M030 when running *
* EXPLAIN STMTCACHE STMTID with a STMTID *
* greater than 8 digits. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When EXPLAIN STMTCACHE STMTID is run with a STMTID that is
longer than 8 digits and an error is encountered, DB2 doesn't
properly format the STMTID into the error message. This
leads to an ABEND04E RC00E70005 at DSNXGRDS.DSNXEXPL:M030.
For example, this abend could occur when executing
EXPLAIN STMTCACHE STMTID 123456789
if STMTID 123456789 doesn't exist in the cache.
Additional Keywords:
SQLCODE20248 SQLEXPLAIN
DB2 code has been fixed to properly format the STMTID. With
the APAR applied, SQLCODE20248 will be issued instead of
the abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18258
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXVCCS PI18258
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18258 DSNXVCCS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXVCCS
LISTEND
UI19996 COVER LETTER END
UI20000 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20247 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of static SQL query *
* acceleration and DB2 subsystem parameter *
* ACCELMODEL = YES *
****************************************************************
* PROBLEM DESCRIPTION: When DB2 subsystem parameter / zparm *
* ACCELMODEL=YES, a BIND or REBIND *
* PACKAGE specifying bind option *
* QUERYACCELERATION does not bind *
* a qualified static SQL query for *
* acceleration. DB2 instead binds *
* the static query to be run only in DB2 *
* without acceleration, allowing *
* DB2 'accelerator modeling' behavior to *
* take precedence over the requested *
* QUERYACCELERATION behavior. *
* *
* This is incorrect DB2 acceleration *
* behavior and DB2 should bind *
* the qualified static SQL query for *
* acceleration as the user requested, *
* even when zparm ACCELMODEL=YES. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR corrects a problem for static SQL query acceleration,
where if DB2 subsystem parameter / zparm ACCELMODEL = YES
(requesting DB2 to bind or prepare queries to run only in DB2
as normal but do 'accelerator modeling' for those queries),
a BIND or REBIND PACKAGE specifying bind option
QUERYACCELERATION does not bind a qualified static SQL query for
acceleration. DB2 incorrectly ignores the QUERYACCELERATION
behavior that the user specified in the bind option and binds
the static query to be run only in DB2 without acceleration.
As a result, DB2 'accelerator modeling' behavior incorrectly
took precedence over the user-requested QUERYACCELERATION
1 behavior. When a BIND or REBIND PACKAGE specifies bind option
QUERYACCELERATION, DB2 should honor the requested
QUERYACCELERATION behavior over 'accelerator modeling' (i.e.,
zparm ACCELMODEL=YES) and bind the qualified static query for
acceleration.
.
One quick way to confirm whether the static query was bound for
acceleration during the BIND or REBIND PACKAGE, is to examine
the catalog table SYSIBM.SYSPACKSTMT column STATUS value for
the particular static query in the package. If that query's
STATUS column does not contain the letter value 'O', then
that static query was not bound for acceleration.
.
Another way to confirm the invalid precedence order of
'accelerator modeling' (ACCELMODEL=YES) is to REBIND the
package with bind option EXPLAIN(ONLY) (this does not produce
a new package or replace or change the previous package) and
examine the bind-generated output in the DB2 table
DSN_QUERYINFO_TABLE. If any rows have the value 'ACCELMDL' in
column QINAME1, then the query was bound to run only in DB2 and
with 'accelerator modeling'.
.
If you have confirmed, by using either of the above methods,
that your static queries were not bound for acceleration due to
the invalid precedence of zparm ACCELMODEL, you can do one of
the following:
- To circumvent the problem without applying this PTF,
temporarily reset the zparm ACCELMODEL to NO (ACCELMODEL is
online changeable), then REBIND the affected packages.
After the REBINDs have completed and the packages'
SYSIBM.SYSPACKSTMT column STATUS = 'O' for those static
queries you intended to accelerate, restore zparm
ACCELMODEL to YES if you want to continue with 'accelerator
modeling' for other applications.
- Or, after applying this PTF, REBIND the affected packages.
No reset of zparm ACCELMODEL is needed.
After the REBINDs have completed, confirm that the packages'
SYSIBM.SYSPACKSTMT column STATUS = 'O' for those static
queries you intended to accelerate.
.
Additional search keywords:
IDAAV4R1/K SQLACCELMODEL
DB2 bind code is corrected so that when a BIND or REBIND
PACKAGE specifying bind option QUERYACCELERATION is issued,
DB2 honors the requested QUERYACCELERATION behavior as
precedent over 'accelerator modeling' when DB2 subsystem
parameter ACCELMODEL=YES, and DB2 binds the qualified static
query for acceleration.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20247
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI20247:
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODML PI20247
DSNXOMPS PI20247
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20247 DSNXODML DSNXOMPS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODML
DSNXOMPS
LISTEND
UI20000 COVER LETTER END
UI20035 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20397 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS *
* utility and inline statistics *
* collecting statistics on index on *
* expression type indexes *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E2000F in DSNSVSFB+X'08EA' *
* during RUNSTATS INDEX utility *
* execution. *
* *
* Zero cardinality statistics reported in *
* DSNU1350I and DSNU1351I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When the user executed RUNSTATS INDEX on a partitioned
index on expression, the utility terminated with ABEND04E
RC00E2000F in DSNSVSFB+ x'08EA'. Incorrect cardinality
statistics were reported in MSGDSNU1350I for
SYSKEYTARGETSTATS catalog table and in MSGDSNU1351I for
SYSKEYTARGETS. The incorrect statistics were inserted into
SYSIBM.SYSKEYTARGETSTATS and SYSIBM.SYSKEYTARGETS catalog
1 tables.
When the aggregation of the statistics for the key targets
were done, an incorrect pointer was passed to the aggregation
routine. This resulted in a storage overlay and incorrect
statistics being gathered.
The data structure for aggregation was not built which
resulted in incorrect zero cardinality statistics reported
in DSNU1350I and DSNU1351I.
Both of the aforementioned problems can also occur during
the collection of statistics on index on expression via
inline statistics.
ADDITIONAL KEYWORDS:
DB2OVRLAY/K
OFFSET08EA
Code was modified to pass the correct pointer to aggregate
the partition level key target statistics and to build
the data structure to facilitate aggregation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20397
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSEOF PI20397
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20397 DSNUSEOF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSEOF
LISTEND
UI20035 COVER LETTER END
UI20041 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16980 -
****************************************************************
* USERS AFFECTED: All V10 and V11 DB2 for z/os users of *
* LOB table space when its corresponding *
* base table is Universal Table Space *
****************************************************************
* PROBLEM DESCRIPTION: It is possible ISO(UR) query that *
* qualify pseudo delete base row but *
* result in -904 SQL error due to *
* deleted LOB data space has been *
* reused. *
1 * *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. The insert process of LOB data can reuse the committed
delete space by examining the buffer pool read LRSN of
its associated base table if the base table is in UTS.
However, an invalid pointer was used to reference
agent page set claim and drain information control block (PBA)
of the base table. As a result, the delete LOB space may be
reused sooner if the LOB data is in the different buffer pool
from its base table. This can lead to ISO(UR) query may
be able to read pseudo delete base row but can not
find its associated LOB data and result in -904 SQL error.
This is a very narror timing window and can only happen if
the base table space is a Universal Table Space.
2. Invalid partition number was set in the page set
control block (OBDPSET) for directory and catalog object.
As a result, DSNOALLO:5009 sanity check can be triggered.
1. DB2 code is changed to use correct pointer when referencing
the base table agent page set claim and drain information
control block (PBA).
2. Added logic to correct the partition number on the page set
descriptor control block (OBDPSET) of the directory or catalog
object when these control block was set up in the EDM pool.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16980
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDALS PI16980
DSNGEPUF PI16980
DSNOALLO PI16980
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16980 DSNGDALS DSNGEPUF DSNOALLO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDALS
DSNGEPUF
DSNOALLO
LISTEND
UI20041 COVER LETTER END
UI20058 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16982 -
****************************************************************
* USERS AFFECTED: Users who use a DEFINE NO index. *
1 ****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E4D5D2, LOC=DSNUTILA. *
* DSNURBXA+463C *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When data is first inserted into a DEFINE NO index, index
dataset will be defined. If the dataset already exists, DB2
could incorrectly use the existing dataset. This can cause the
above abend or other unexpected problems later.
DB2 is fixed to return an error if dataset already exist for
a DEFINE NO index on the first insert into the index.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16982
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDAIP PI16982
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16982 DSNGDAIP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDAIP
LISTEND
UI20058 COVER LETTER END
UI20069 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19154 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* DB2 10 and DB2 11 for z/OS only. *
****************************************************************
* PROBLEM DESCRIPTION: ABND 04E-00D3440B *
* LOC=DSNLXLLM.DSNLXHSE:0028 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application (site1) connects to a DB2 for z/OS server
(site2) and executes SQL that causes a "hop" to yet another
remote DB2 for z/OS server (site3). The SQL returns LOB/XML
output that is retrieved by the remote application using
progressive streaming.
The DB2 for z/OS (site2) server may abend as reported when
processing the reply message/data in response to the DRDA
(DDM) GETNXTCHK command.
DB2 for z/OS (hopping site2) is changed to correctly handle
the reply from the DRDA GETNXTCHK command.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19154
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXHSE PI19154
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19154 DSNLXHSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXHSE
LISTEND
UI20069 COVER LETTER END
UI20099 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18199 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of -ACCESS DATABASE *
* MODE(OPEN) command *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNI045I may contain REASON 00000000 *
* when -ACCESS DATABASE MODE(OPEN) failed *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When -ACCESS command encounters a claim failure, the reason code
may not be set. As a result, DSNI045I may contain REASON
00000000.
-ACCESS command code is changed to set a proper reason code in
response to a claim failure.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18199
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILSTS PI18199
DSNTDMST PI18199
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18199 DSNILSTS DSNTDMST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILSTS
DSNTDMST
1
LISTEND
UI20099 COVER LETTER END
UI20103 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21025 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: In DB2 10, the same message DSNI044I *
* may be repeated many times during LPL *
* recovery such as performed by -START *
* DATABASE command. This only happens *
* when the object is an NPI. *
* *
* In DB2 11, DSNI044I may be missing *
* during LPL recovery such as performed *
* by -START DATABASE command. This can *
* happen to any object but only in *
* non-data sharing system. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 10, the same page range block for LPL recovery was built
a number of times for NPI by referencing the associated
partitioned tablespace, causing extraneous messages DSNI044I.
In DB2 11, the return code checking on the DB2 member id call is
not handled correctly. As a result, DSNI044I message is skipped
in non-data sharing system.
The code is fixed to issue DSNI044I message properly during LPL
recovery.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21025
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISREC PI21025
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21025 DSNISREC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISREC
LISTEND
UI20103 COVER LETTER END
UI20106 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI16229 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users *
* with Partition By Growth (PBG) *
* tablespace. *
****************************************************************
* PROBLEM DESCRIPTION: A partial rollback of a failed PBG *
* add-partition process caused the just *
* added partition remain visible after *
* the rollback. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When Create PBG is in the same commit scope as its growing
partition process, if roll back this Unit of Recovery (UR)
becomes necessary, DB2 didn't completely roll back the growing
partition process. This caused the added partition remain
visible in DB2 catalog.
Fixes made in DB2 to properly rollback a PBG's add-partition
process if the PBG is also created in the same commit scope.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16229
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCOB PI16229
DSNIFPSC PI16229
DSNIOPNP PI16229
DSNIPSFI PI16229
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16229 DSNGDCOB DSNIFPSC DSNIOPNP DSNIPSFI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCOB
DSNIFPSC
DSNIOPNP
DSNIPSFI
LISTEND
UI20106 COVER LETTER END
UI20108 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21696 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: Previous DSN3EPX load module storage *
* is not freed following the refresh of *
1 * the Early Code with the -REFRESH *
* command. Each -REFRESH command and *
* subsequent restart of DB2 will *
* orphan approximately 40K of SP241 *
* E/CSA storage. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 specifies the wrong subpool when issuing the conditional
FREEMAIN for the previous DSN3EPX load module storage, after a
new version of the Early Code has been loaded with the -REFRESH
DB2,EARLY command.
DSNYASCP has been changed to specify the correct storage
subpool (SP241) when issuing the FREEMAIN for DSN3EPX load
module storage following the -REFRESH DB2,EARLY command.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21696
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNYASCP PI21696
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21696 DSNYASCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNYASCP
LISTEND
UI20108 COVER LETTER END
UI20110 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17355 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries containing LIKE predicates using *
* CLOBs encoded as UTF8. *
****************************************************************
* PROBLEM DESCRIPTION: An infinite loop can occur in DB2 when *
* executing a query that uses UTF8 CLOB *
* data with a large data length in a LIKE *
* predicate. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An infinite loop can occur in DB2 when executing a query that
uses UTF8 CLOB data with a relatively large data length in a
LIKE predicate.
The following query provides a possible failing example.
1
SELECT *
FROM SYSIBM.SYSPACKSTMT
WHERE LOCATION = ' '
AND COLLID = 'ABC'
AND SUBSTR(NAME,1,7) = 'DEF'
AND STATEMENT LIKE '% ADD_MONTHS %';
The column STATEMENT is defined as a CLOB UNICODE in Table
SYSIBM.SYSPACKSTMT. When the CLOB contains mixed data and is
being used in a LIKE predicate, if the length of the CLOB is
larger than the buffer internally used by DB2 LOB LIKE predicate
processing, and the mixed data happens to fall on the buffer
boundary, DB2 handles the data incorrectly which can eventually
result in an infinite loop during this processing.
The code in DB2 has been modified to correct the problem leading
to a possible infinite loop.
Additional Keywords: SQLLOB SQLLIKE LOOPDSNOUL8
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17355
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOUL8 PI17355
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17355 DSNOUL8
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOUL8
LISTEND
UI20110 COVER LETTER END
UI20112 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17569 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and DB2 *
* 11 for z/OS users of RENAME TABLE RLST-name *
* (Resource Limit Specification Table) and *
* RENAME INDEX RLST-index-name. *
****************************************************************
* PROBLEM DESCRIPTION: A SQLCODE148 (DB2 9) or SQLCODE750 ( *
* DB2 10 and DB2 11) may be issued *
* incorrectly when executing a RENAME *
* TABLE RLST-name (Resource Limit *
* Specification Table) statement. And *
* a SQLCODE148 (DB2 9 and DB2 10) or *
* SQLCODE750 (DB2 11) may be issued *
1 * incorrectly when executing a RENAME *
* INDEX RLST-index-name statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A SQLCODE148 (DB2 9) or SQLCODE750 (DB2 10 and DB2 11) may be
issued incorrectly when executing a RENAME TABLE RLST-name
statement. Or a SQLCODE148 (DB2 9 and DB2 10) or SQLCODE750
(DB2 11) may be issued incorrectly when executing a RENAME
INDEX RLST-index-name statement.
When comparing the RLST name, DB2 only examines the first 7 or 6
characters instead of the full table or index name. Hence, it
could potentially block the legitimate RENAME statement.
DB2 could also incorrectly allowing RENAME TABLE RLST-table-name
or RENAME INDEX RLST-index-name runs successfully when DB2
should block it and issue a SQLCODE in data sharing environment.
This could lead to unexpected failing symptoms if an active RLST
object is incorrectly allowed to be renamed.
Following is an example of the failing scenario:
1. Create RLST tables:
CREATE DATABASE DSNRLST;
CREATE TABLESPACE DSNRLS01 IN DSNRLST CLOSE NO;
COMMIT;
CREATE TABLE DSNRLST01
(AUTHID VARCHAR(128) NOT NULL WITH DEFAULT,
PLANNAME CHAR( 8) NOT NULL WITH DEFAULT,
ASUTIME INTEGER,
LUNAME CHAR( 8) NOT NULL WITH DEFAULT,
RLFFUNC CHAR( 1) NOT NULL WITH DEFAULT,
RLFBIND CHAR( 1) NOT NULL WITH DEFAULT,
RLFCOLLN VARCHAR(128) NOT NULL WITH DEFAULT,
RLFPKG VARCHAR(128) NOT NULL WITH DEFAULT,
RLFASUERR INTEGER,
RLFASUWARN INTEGER,
RLF_CATEGORY_B CHAR( 1) NOT NULL WITH DEFAULT)
IN DSNRLST.DSNRLS01;
CREATE TYPE 2 UNIQUE INDEX DSNARL01
ON DSNRLST01
(RLFFUNC, AUTHID DESC, PLANNAME DESC,
RLFCOLLN DESC, RLFPKG DESC, LUNAME DESC)
CLUSTER CLOSE NO;
CREATE TABLE DSNRLMT01
(RLFFUNC CHAR(1)NOT NULL WITH DEFAULT,
RLFEUAN CHAR(32) NOT NULL WITH DEFAULT,
RLFEUID CHAR(16) NOT NULL WITH DEFAULT,
RLFEUWN CHAR(18) NOT NULL WITH DEFAULT,
RLFIP CHAR(254) NOT NULL WITH DEFAULT,
ASUTIME INTEGER,
RLFASUERR INTEGER,
1 RLFASUWARN INTEGER,
RLF_CATEGORY_B CHAR(1) NOT NULL WITH DEFAULT)
IN DSNRLST.DSNRLS01;
CREATE UNIQUE INDEX DSNMRL01
ON DSNRLMT01
(RLFFUNC, RLFEUAN DESC, RLFEUID DESC,
RLFEUWN DESC, RLFIP DESC)
CLUSTER CLOSE NO;
CREATE TABLE DSNRLST02
(AUTHID VARCHAR(128) NOT NULL WITH DEFAULT,
PLANNAME CHAR( 8) NOT NULL WITH DEFAULT,
ASUTIME INTEGER,
LUNAME CHAR( 8) NOT NULL WITH DEFAULT,
RLFFUNC CHAR( 1) NOT NULL WITH DEFAULT,
RLFBIND CHAR( 1) NOT NULL WITH DEFAULT,
RLFCOLLN VARCHAR(128) NOT NULL WITH DEFAULT,
RLFPKG VARCHAR(128) NOT NULL WITH DEFAULT,
RLFASUERR INTEGER,
RLFASUWARN INTEGER,
RLF_CATEGORY_B CHAR( 1) NOT NULL WITH DEFAULT)
IN DSNRLST.DSNRLS01;
CREATE TYPE 2 UNIQUE INDEX DSNARL02
ON DSNRLST02
(RLFFUNC, AUTHID DESC, PLANNAME DESC,
RLFCOLLN DESC, RLFPKG DESC, LUNAME DESC)
CLUSTER CLOSE NO;
CREATE TABLE DSNRLMT02
(RLFFUNC CHAR(1)NOT NULL WITH DEFAULT,
RLFEUAN CHAR(32) NOT NULL WITH DEFAULT,
RLFEUID CHAR(16) NOT NULL WITH DEFAULT,
RLFEUWN CHAR(18) NOT NULL WITH DEFAULT,
RLFIP CHAR(254) NOT NULL WITH DEFAULT,
ASUTIME INTEGER,
RLFASUERR INTEGER,
RLFASUWARN INTEGER,
RLF_CATEGORY_B CHAR(1) NOT NULL WITH DEFAULT)
IN DSNRLST.DSNRLS01;
CREATE UNIQUE INDEX DSNMRL02
ON DSNRLMT02
(RLFFUNC, RLFEUAN DESC, RLFEUID DESC,
RLFEUWN DESC, RLFIP DESC)
CLUSTER CLOSE NO;
2. Start resource limit facility and specify a resource limit
table for the facility to use:
-START RLIMIT ID=01
3. Rename the RLST table name, then SQLCODE148 (DB2 9) or
SQLCODE750 (DB2 10 and DB2 11) will be issued incorrectly:
1 RENAME TABLE DSNRLST02 TO DSNRLST99;
RENAME TABLE DSNRLMT02 TO DSNRLMT99;
4. Rename the RLST index name, then SQLCODE148 (DB2 9 and DB2
10) or SQLCODE750 (DB2 11) will be issued incorrectly:
RENAME INDEX DSNARL02 TO DSNARL99;
RENAME INDEX DSNMRL02 TO DSNMRL99;
DB2 is modified to examine the full RLST table and index name
for the RENAME TABLE/INDEX RLST-name statement.
Additional Keywords: SQLCODE148 SQLCODE750 SQLRENAME
DB2RLF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17569
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIRIX PI17569
DSNXIRTB PI17569
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17569 DSNXIRIX DSNXIRTB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIRIX
DSNXIRTB
LISTEND
UI20112 COVER LETTER END
UI20115 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19017 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries that can use a sparse index. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC11 at DSNXRFF OFFSET21FC *
* can occur when a query that uses a *
* sparse index is executed again after *
* DB2 issues an SQLCODE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 RC11 at DSNXRFF OFFSET21FC (v11) can occur for a
query that uses a sparse index when it is executed again after
it receives an SQLCODE from DB2.
When a query which uses a sparse index (PRIMARY_ACCESSTYPE=T)
receives an SQLCODE, for example an SQLCODE904 due to a resource
1 not available condition, if the same query is executed again
without being prepared, DB2 could generate the above ABEND
because some internal structures were not cleaned up properly.
DB2 expects the failing query to be prepared again.
Please note, other SQLCODEs (i.e. SQLCODE905) could also cause
the above ABEND.
The code in DB2 has been modified to correct the condition
leading to the abend when the query was executed again without
being re-prepared.
Additional Keywords: SQLSPARSEINDEX SPARSEINDEX
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19017
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXREOJ PI19017
DSNXREO9 PI19017
DSNXRFF PI19017
DSNXRFF9 PI19017
DSNXROJ1 PI19017
DSNXROJ9 PI19017
DSNXRSFN PI19017
DSNXRSGB PI19017
DSNXRSG9 PI19017
DSNXRSN9 PI19017
DSNXRT1J PI19017
DSNXRT19 PI19017
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19017 DSNXREOJ DSNXREO9 DSNXRFF DSNXRFF9 DSNXROJ1 DSNXROJ9
DSNXRSFN DSNXRSGB DSNXRSG9 DSNXRSN9 DSNXRT1J DSNXRT19
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXREOJ
DSNXREO9
DSNXRFF
DSNXRFF9
DSNXROJ1
DSNXROJ9
DSNXRSFN
DSNXRSGB
DSNXRSG9
DSNXRSN9
DSNXRT1J
DSNXRT19
LISTEND
UI20115 COVER LETTER END
1UI20117 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16422 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REORG *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000010 DSNXRBN9 +x'007A' *
* when extracting keys for spatial *
* index during REORG TABLESPACE *
* KEEPDICTIONARY RELOAD phase. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A REORG TABLESPACE KEEPDICTIONARY was run on a compressed
table space when there was a spatial index defined.
The REORG caused an overlay when extracting keys for the
spatial index, DB2 incorrectly attempted to extract the keys
from the compressed record, which lead to the storage overlay.
REORG utility code has been modified to used the expanded
record when extracting keys for the spatial index.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16422
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRLPG PI16422
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16422 DSNIRLPG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRLPG
LISTEND
UI20117 COVER LETTER END
UI20143 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI05161 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of UNLOAD DELIMITED UNICODE *
* and LOAD DELIMITED UNICODE *
****************************************************************
* PROBLEM DESCRIPTION: UNLOAD DELIMITED UNICODE of a UNICODE *
* table with DBCS columns issues *
* MSGDSNU1250 and ends with RC8 *
* *
* LOAD INTO TABLE UNICODE FORMAT *
* DELIMITED of a UNICODE table with a *
1 * GRAPHIC column with STRIP completes *
* with RC0 but issues message DSNU1230I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
1. UNLOAD DELIMITED UNICODE from a UNICODE table with DBCS
columns (GRAPHIC and/or VARGRAPHIC) issues message DSNU1250I -
ERROR IN CCSID TRANSLATION FOR "DBCS PAD CHAR", FROM CCSID
1200
TO 1208 and ends with RC8.
This was the result of the DBCS padding character in UTF-16
format being translated to an SBCS character in UTF-8 format
which was considered invalid.
2. LOAD INTO TABLE UNICODE FORMAT DELIMITED of a UNICODE table
with a GRAPHIC column specified with STRIP TRAILING in the
field-spec completes successfully but invalidly issues message
MSGDSNU1230I - INCONSISTENT STRIP CHAR LENGTH FOR FIELD column
name, TABLE table name.
This was the result of LOAD expecting the padding character to
be 2 bytes when in fact it was 1 byte. Because the input data
was in UTF-8, the single byte padding character was correct.
Also, while testing this fix, it was discovered that when
loading a VARGRAPHIC column (a unicode table with unicode input)
from either variable-length column data input or with FORMAT
DELIMITED, after ccsid conversion, the first byte of the
VARGRAPHIC data can be invalid.
UNLOAD DELIMITED UNICODE code has been changed to allow the
conversion of the padding character from double-byte to
single-byte for DBCS column data.
Code for LOAD FORMAT DELIMITED UNICODE into a UNICODE table has
been changed to not put out the DSNU1230I message. Also, code
LOAD code has been changed to not skip conversion of the first
byte of a VARGRAPHIC column.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI05161
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURUFL PI05161
DSNURWBG PI05161
DSNUULGL PI05161
DSNUULIA PI05161
DSNUULVA PI05161
DSNUUNLD PI05161
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI05161 DSNURUFL DSNURWBG DSNUULGL DSNUULIA DSNUULVA DSNUUNLD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURUFL
DSNURWBG
DSNUULGL
DSNUULIA
DSNUULVA
DSNUUNLD
LISTEND
UI20143 COVER LETTER END
UI20151 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20688 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes the following issues *
* for query acceleration. *
* *
* (1) (DB2 10 and DB2 11) A query with *
* the function VARCHAR with a FOR BIT *
* DATA column and OCTETS may return *
* incorrect output. *
* (2) (DB2 10 and DB2 11) An OLAP *
* specification using the aggregate *
* function AVG on a DECIMAL datatype *
* may return incorrect output. *
* (3) (DB2 10) An INSERT with subselect *
* statement may be incorrectly *
* evaluted when subsystem parameter *
* ACCELMODEL has a value of YES. *
* (4) (DB2 10 and DB2 11) A complex *
* query with an ORDER BY clause may *
* return output in the incorrect *
* order. *
* (5) (DB2 10 and DB2 11) A query with *
* '-' or '+' on a constant or *
* a view reference resolves to a *
* constant may issue SQLCODE -904. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes the following issues for query acceleration:
(1) (DB2 10 and DB2 11) A query with the function VARCHAR with
a FOR BIT DATA column and OCTETS may return incorrect
output.
(2) (DB2 10 and DB2 11) An OLAP specification using the
aggregate function AVG on a DECIMAL datatype may return
incorrect output.
(3) (DB2 10) An INSERT with subselect statement may be
incorrectly evaluted when subsystem parameter ACCELMODEL
has a value of YES. EXPLAIN will show that
DSN_STATEMNT_TABLE.TOTAL_COST will have a value that is less
than 5000 and DSN_STATEMNT_TABLE.REASON will incorrectly
contain 'ACCELMODEL ELIGIBLE'. Both QWAC_ACCEL_ELIG_CP
and QWAC_ACCEL_ELIG_CP will be incorrectly incremented.
(4) (DB2 10 and DB2 11) A complex query with an ORDER BY clause
may return results in the incorrect order.
(5) (DB2 10 and DB2 11) A query with '-' or '+' on a constant or
a view reference resolves to a constant may issue SQLCODE
-904 "Invalid SQL statement".
For static SQL queries that have been bound for acceleration
and will use any of the new functions above, REBIND the
package for the failing query after applying this PTF.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K SQLVARCHAR SQLOLAP SQLAVG ACCELMODEL INSERT
ORDERBY SQLCODE904
DB2 code is fixed for expected results and behavior.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20688
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOIN PI20688
DSNXONZC PI20688
1 DSNXONZS PI20688
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20688 DSNXOIN DSNXONZC DSNXONZS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOIN
DSNXONZC
DSNXONZS
LISTEND
UI20151 COVER LETTER END
UI20153 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18630 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS users, DB2 10 for z/OS *
* users and DB2 11 for z/OS users with SQL *
* statements that generates SQL warning or *
* error during processing. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00D34429 at *
* DSNLXGLM.DSNLXRSQ 0032 and other *
* various abend(s) may occur when there *
* are multiple message tokens, and the *
* total length of leading message *
* token(s) plus the delimiter(s) is *
* exactly 70 bytes *
* *
* In V9, the abend may even occur if *
* there are more than two message tokens *
* and the first message token is exactly *
* 34 bytes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00D34429 at DSNLXGLM.DSNLXRSQ 0032 and other various
abend may occur when there are multiple error message tokens,
and the total length of leading message token(s) plus
delimiter(s) is exactly 70 bytes. In V9, the abend may even
occur if there are more than two message tokens and the first
message token is exactly 34 bytes.
DB2 has been modified to correctly handle the
error message text in Diagnostic area and SQLCA.
SOLUTION:
Additional keywords: ABEND04E SQLGETDIAG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18630
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDWA PI18630
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18630 DSNXEDWA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDWA
LISTEND
UI20153 COVER LETTER END
UI20160 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19867 -
****************************************************************
* USERS AFFECTED: DB2 users with PM94263 applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40347 running the RECOVER *
* utility with the PARALLEL option. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
PM94263 modified the way in which the necessity of a claim is
checked for with a partitioned table space. The change did not
work correctly for a utility subtask holding an "inherited"
drain. The result is that a utility subtask may request a
claim which can fail due either to a timeout on a drain lock
(held by the utility main task), or to some exceptional state.
Although various utilities utilize subtasks which could in
theory hit this kind of failure, the only known failure is that
of a RECOVER utility with the PARALLEL option running on DB2
V10 in compatibility mode. A restore subtask of the RECOVER
can time out on a drain lock, causing the RECOVER to fail with
ABEND04E RC00E40347 CAUSE=X'00C20042'.
The processing for an "inherited" drain has been modified to
set
the drain duration, so that the claim logic can distinguish the
inherited drain from the case where the drain lock is held for
other reasons.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19867
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CLM PI19867
DSNB1DRA PI19867
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19867 DSNB1CLM DSNB1DRA
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CLM
DSNB1DRA
LISTEND
UI20160 COVER LETTER END
UI20162 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21486 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who use *
* IBM DB2 Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 Abend=04E-00F30801, *
* LOC=DSN3EPX.DSNAPRHX+2296 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Utilizing Accelerator Services with Workload Balancing (WLB)
may lead to a condition where a DB2 latch is not released. The
failure to release the latch only occurs under rare (internal)
conditions and will lead to abend 04E-00F30801 DSNAPRHX+2296
and a DB2 termination.
Accelerator Services Workload Balancing processing has been
changed to make sure all latches are released.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21486
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX8WAC PI21486
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21486 DSNX8WAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX8WAC
LISTEND
UI20162 COVER LETTER END
UI20164 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16898 -
****************************************************************
1 * USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNB5COM, DSNURWBF, or *
* other DSNB* or DSNU* CSECTs. *
* ABEND04E RC00C200A4 in DSNB5COM, *
* DSNB5RAP, or DSNB5RAP. *
* ABEND04E RC00C200B0 in various CSECTs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abends are the result of a partition being physically
closed out from under a utility which is holding a space-level
drain. The close is driven by an ACCESS DATABASE MODE=NGBPDEP
command issued on another member.
The ACCESS DATABASE MODE=NGBPDEP logic has been modified to
properly serialize with another process which is holding a
space-level drain.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16898
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CLM PI16898
DSNB1DRA PI16898
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16898 DSNB1CLM DSNB1DRA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CLM
DSNB1DRA
LISTEND
UI20164 COVER LETTER END
UI20172 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15667 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10 and 11 for z/OS users of *
* index-controlled partitioning table. *
****************************************************************
* PROBLEM DESCRIPTION: User received the following abend: *
* ABEND04E RC00C90110 *
* DSNIDM.DSNIPTYM:5005 during an ALTER *
* INDEX statement that converts the *
* table from index-controlled to table- *
* controlled partitioning. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 During the conversion processing from index-controlled
partitioning to table-controlled partitioning, if user has
the zparm IX_TB_PART_CONV_EXCLUDE set and the object being
converted was created prior to V6 with a 40 bytes limit key
limit, DB2 did not handle the conversion properly. This
resulted in user receiving the reported abend during the
conversion.
Please note that this problem can result in other unexpected
DB2 errors, abends, and behaviors. Some of the known ones are:
- REPAIR DBD reporting error after conversion:
For example:
OBDS DIFFER AT OFFSET X'000002FE' OBDPSNXT(7) -
INFORMATION NOT IN D
EXISTING VALUE X'0000'
REBUILT VALUE X'0358'
OBDS DIFFER AT OFFSET X'00000300' OBDPSPRV(7) -
INFORMATION NOT IN D
EXISTING VALUE X'0000'
REBUILT VALUE X'0288'
OBDS DIFFER AT OFFSET X'00000666' OBDLMKY(1:XMINLN)
- data being placed in wrong partition after conversion
- SYSTABLEPART.LIMITKEY_INTERNAL might contain incorrect
value
Since the problem occurs during the conversion processing
from index-controlled to table-controlled partitioning, other
paths might be affected also. The following are potential
paths that might be affected:
- ALTER TABLE ADD PARTITION
- ALTER TABLE ALTER PARTITION
- ALTER TABLE ROTATE PARTITION
- ALTER TABLE ADD CLONE
- ALTER INDEX
- DROP INDEX
This APAR also addresses the issue where the 'MAXVALUE'
external limit key value for the last partition was
populated incorrectly during the conversion from
index-controlled partitioning to table-controlled.
For example:
SYSTABLEPART.LIMITKEY contains 'MAXVALUE, MAXVALUE, MAXVAL'
This particular 'MAXVALUE' issue is not related to the 40
bytes limit. Please note that this external limit key value
is for reference purpose only and does not affect DB2
functionality.
DB2 has been fixed to handle pre-V6 objects with 40 bytes
limit properly during the index-controlled to table-
controlled partitioning conversion when user has the zparm
IX_TB_PART_CONV_EXCLUDE set to YES to exclude insignificant
key columns.
1
DB2 has been fixed to populate 'MAXVALUE' properly for the
last partition during the index-controlled to table-
controlled partitioning conversion.
Please note that applying this apar will not fix any existing
objects. Customer will need to drop and recreate the table
to correct the problem.
Additional Keywords:
SQLCODE663
SQLALTER
SQLCREATE
SQLDROP
SQLTABLE
SQLINDEX
SQLINCORR
SQLINCORROUT
INCORROUT
DB2INCORR/K
DB2OVRLAY/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15667
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIAB6 PI15667
DSNXIAB7 PI15667
DSNXISB6 PI15667
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15667 DSNXIAB6 DSNXIAB7 DSNXISB6
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIAB6
DSNXIAB7
DSNXISB6
LISTEND
UI20172 COVER LETTER END
UI20190 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11814 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V9, V10, and V11 users. *
****************************************************************
* PROBLEM DESCRIPTION: All DB2 for z/OS V9, DB2 for z/OS V10, *
* and DB2 for z/OS V11 users of the *
* IFCID flat file (DSNWMSGS). *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
Updates to the IFCID flat file (DSNWMSGS) for the first
half of 2014 are needed for all supported DB2 for z/OS
versions.
This APAR delivers updates to the IFCID flat file (DSNWMSGS)
for the following DB2 for z/OS versions:
- DB2 9 for z/OS
- DB2 10 for z/OS
- DB2 11 for z/OS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11814
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWMSGS PI11814
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11814 DSNWMSGS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNWMSGS
LISTEND
UI20190 COVER LETTER END
UI20243 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22142 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: Zero address detection report found *
* potential abend in DSNISEGF and other *
* modules. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A log info processing macro may reference a field based on a
zero pointer, and potentially causes abend in DSNISEGF and other
modules.
The code has been fixed to check the pointer before referencing
the field.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22142
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
----------------------------------------------------------------
THE PM25093 CORRECTION APPLIED ON ONE DB2 DATA SHARING MEMBER IS
1 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.
----------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDLGC PI22142
DSNICLAP PI22142
DSNICNOT PI22142
DSNICUR PI22142
DSNIDILS PI22142
DSNIDLDS PI22142
DSNIDLDU PI22142
DSNIDLEO PI22142
DSNIDLOD PI22142
DSNIFNP PI22142
DSNIFOI PI22142
DSNIHPGM PI22142
DSNILGBW PI22142
DSNILGCL PI22142
DSNILSMG PI22142
DSNILSMU PI22142
DSNIPOCI PI22142
DSNIQGSE PI22142
DSNIREPR PI22142
DSNISDLE PI22142
DSNISEGF PI22142
DSNISGNS PI22142
DSNISGRT PI22142
DSNISGSU PI22142
DSNISMCP PI22142
DSNISMEX PI22142
DSNISMFO PI22142
DSNISMRS PI22142
DSNISMRT PI22142
DSNISMSU PI22142
DSNIUMAV PI22142
DSNIVOBD PI22142
DSNIWLPG PI22142
DSNIXMLC PI22142
DSNIXTND PI22142
DSNIZLDL PI22142
DSNI1OP PI22142
DSNKBIDP PI22142
DSNKDPG PI22142
DSNKFRMT PI22142
DSNKINSN PI22142
DSNKISPL PI22142
DSNKISPN PI22142
DSNKLNPG PI22142
DSNKPDGB PI22142
DSNODALN PI22142
DSNODEAL PI22142
1 DSNOFHDR PI22142
DSNOFHLS PI22142
DSNOFLLS PI22142
DSNOFLMP PI22142
DSNOLADS PI22142
DSNOLINS PI22142
DSNOLSCN PI22142
DSNORCHU PI22142
DSNPRST1 PI22142
DSNXOD1 PI22142
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22142 DSNGDLGC DSNICLAP DSNICNOT DSNICUR DSNIDILS DSNIDLDS
DSNIDLDU DSNIDLEO DSNIDLOD DSNIFNP DSNIFOI DSNIHPGM
DSNILGBW DSNILGCL DSNILSMG DSNILSMU DSNIPOCI DSNIQGSE
DSNIREPR DSNISDLE DSNISEGF DSNISGNS DSNISGRT DSNISGSU
DSNISMCP DSNISMEX DSNISMFO DSNISMRS DSNISMRT DSNISMSU
DSNIUMAV DSNIVOBD DSNIWLPG DSNIXMLC DSNIXTND DSNIZLDL
DSNI1OP DSNKBIDP DSNKDPG DSNKFRMT DSNKINSN DSNKISPL
DSNKISPN DSNKLNPG DSNKPDGB DSNODALN DSNODEAL DSNOFHDR
DSNOFHLS DSNOFLLS DSNOFLMP DSNOLADS DSNOLINS DSNOLSCN
DSNORCHU DSNPRST1 DSNXOD1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDLGC
DSNICLAP
DSNICNOT
DSNICUR
DSNIDILS
DSNIDLDS
DSNIDLDU
DSNIDLEO
DSNIDLOD
DSNIFNP
DSNIFOI
DSNIHPGM
DSNILGBW
DSNILGCL
DSNILSMG
DSNILSMU
DSNIPOCI
DSNIQGSE
DSNIREPR
DSNISDLE
DSNISEGF
DSNISGNS
DSNISGRT
DSNISGSU
DSNISMCP
DSNISMEX
DSNISMFO
DSNISMRS
DSNISMRT
DSNISMSU
1 DSNIUMAV
DSNIVOBD
DSNIWLPG
DSNIXMLC
DSNIXTND
DSNIZLDL
DSNI1OP
DSNKBIDP
DSNKDPG
DSNKFRMT
DSNKINSN
DSNKISPL
DSNKISPN
DSNKLNPG
DSNKPDGB
DSNODALN
DSNODEAL
DSNOFHDR
DSNOFHLS
DSNOFLLS
DSNOFLMP
DSNOLADS
DSNOLINS
DSNOLSCN
DSNORCHU
DSNPRST1
DSNXOD1
LISTEND
UI20243 COVER LETTER END
UI20301 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22302 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: The new MAXRTU (maximum tape units) *
* and DEALLCT (delayed deallocation *
* time) DSNZPARM values are not *
* activated following the -SET SYSPARM *
* command. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A pointer to the current DSNZPARM DSN6LOGP parameter values
is not updated correctly while processing a -SET SYSPARM
command to activate a new DSNZPARM. The -DISPLAY ARCHIVE
command output will show the initial ZPARM values in the
COUNT and TIME fields. The -SET ARCHIVE command can be
used to update these values when this happens.
DSNJCHGZ has been changed to update the pointer to the
current DSNZPARM DSN6LOGP values when processing a -SET
SYSPARM command to activate a new or updated DSNZPARM module.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI22302
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJCHGZ PI22302
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22302 DSNJCHGZ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJCHGZ
LISTEND
UI20301 COVER LETTER END
UI20314 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21058 -
****************************************************************
* USERS AFFECTED: Users of DB2 9 for z/OS and DB2 10 for z/OS *
* and DB2 11 for z/OS who use the stored *
* procedure SYSPROC.ADMIN_INFO_SQL. *
****************************************************************
* PROBLEM DESCRIPTION: ADMIN_INFO_SQL is not generating the *
* DDL for the index on MQT table. *
****************************************************************
* RECOMMENDATION: Apply PTF *
****************************************************************
ADMIN_INFO_SQL does not have the logic to generate the DDL for
the index on MQT table.
The reported ADMIN_INFO_SQL problems are now corrected.
ADDITIONAL KEYWORDS:
SQLSP SQLSTOREDPROC ADMININFOSQL SQLMQT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21058
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 ---------------------------------------------------------------
==> 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, 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.
DB2BIND:
***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.
ACTION:
***Action for PI07646 (DB2 10)
1 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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMSS PI21058
DSNADMSS PI21058
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21058 DSN@DMSS DSNADMSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMSS
MACROS
DSN@DMSS
LISTEND
UI20314 COVER LETTER END
UI20329 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17335 -
****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of an SQL *
1 * statement that uses inline LOB columns *
* and star joins. *
****************************************************************
* PROBLEM DESCRIPTION: Star join queries that reference *
* an inline LOB column may receive *
* an abend ABEND0C4 at DSNISELL *
* OFFSET079 or OFFSET076C. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend ABEND0C4 at DSNISELL OFFSET079C or OFFSET076C may occur
for queries that reference inline LOB columns and satisfy
the star join transformation because DB2 did not process
the inline LOB columns during star join transformation
correctly.
DB2 was updated to process the inline LOB columns correctly
during star join transformation.
Additional Keywords: SQLLOB SQLSTARJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17335
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSJT PI17335
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17335 DSNXOSJT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSJT
LISTEND
UI20329 COVER LETTER END
UI20338 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI16986 -
****************************************************************
* USERS AFFECTED: Users of DB2 10 for z/OS and DB2 11 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBGN:5006 and *
* ABEND04E RC00C9008E in module DSNIDBLK *
* may occur on all members when DBET *
* encounters a timeout attempting to *
* acquire a hash lock. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a timeout is encountered when the DBET component attempts
to acquire a hash lock, each DB2 member will issue a
diagnostic ABEND.
The diagnostic ABENDs were initially added to help diagnose
timeout problems in earlier releases, which were difficult
to diagnose without information from all members.
For later releases, these diagnostic ABENDs are no longer
needed due to improved code quality.
ABEND04E RC00C90101 DSNIDBGN:5006 and ABEND04E RC00C9008E
in module DSNIDBLKs have been removed when DBET encounters
a timeout during an attempt to acquire a hash lock. The
said ABENDs may still be issued for other timeouts and
deadlock scenarios
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16986
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBLK PI16986
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16986 DSNIDBLK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBLK
LISTEND
UI20338 COVER LETTER END
UI20346 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20390 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of CREATE INDEX on DECLARE GLOBAL *
* TEMPORARY TABLE (DGTT). *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect output may be returned *
1 * when selecting the result from a *
* DECLARE GLOBAL TEMPORARY TABLE via *
* index accessing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect output may be returned when accessing a DECLARE
GLOBAL TEMPORARY TABLE (DGTT) via its index. When CREATE INDEX
on a DGTT, DB2 may register the index's attributes incorrectly.
This causes the incorrect output and the failing symptoms may
not limit to incorrect output, it could also include abend in
different modules and offset.
Following is an example of such failing scenario:
DECLARE GLOBAL TEMPORARY TABLE
SESSION.MYDGTT
LIKE SYSIBM.SYSTABLES
;
CREATE INDEX TMPIDX01 ON SESSION.MYDGTT
(NAME, CREATOR);
CREATE UNIQUE INDEX TMPIDX02 ON SESSION.MYDGTT
(NAME, DBID, OBID)
;
DB2 is modified to register the DGTT index attribute correctly.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLDGTT DGTT SQLCREATE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20390
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDBIX PI20390
DSNXICX2 PI20390
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20390 DSNGDBIX DSNXICX2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDBIX
DSNXICX2
LISTEND
UI20346 COVER LETTER END
UI20363 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20372 -
1 ****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of LOAD FORMAT INTERNAL *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20992 DSNSVSVB +x'0E46' *
* and ABENDS0C4 RC38 DSNSVSVB +x'0B68' *
* after a LOAD FORMAT INTERNAL is run *
* converting data in Basic Row Format *
* (BRF) to the Reordered Row Format *
* (RRF) of the table space. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD FORMAT INTERNAL utility was run which loaded data in BRF
format into a table which had been converted to RRF. The LOAD
caused an overlay by using an inefficient work area during the
BRF to RRF conversion of the rows. Multiple abends occurred
including ABEND04E RC00E20992 DSNSVSVB OFFSET0E46 and ABEND0C4
RC38 DSNSVSVB OFFSET0B68, as well as ABEND04E RC00E2000F
DSNSVSFB OFFSET0858. The work area for the conversion of rows
was not initialized correctly.
Additional Keywords: +x'0858' DB2OVRLAY/K
LOAD utility code has been modified to fix the aforementioned
problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20372
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURPLI PI20372
DSNURWI PI20372
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20372 DSNURPLI DSNURWI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURPLI
DSNURWI
LISTEND
UI20363 COVER LETTER END
UI20365 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19044 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD utility with multiple *
* LOB columns. *
* *
1 * All DB2 11 for z/OS users of LOAD utility *
* with STATISTICS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90D01 DSNOTCSO *
* OFFSET70BE during a LOAD utility *
* with multiple LOB columns and *
* not all are loaded inline. *
* *
* ABENDS0C4 DSNUGSRP OFFSET1B9C *
* and ABEND04E RC00E40347 during *
* a LOAD utility with STATISTICS *
* COLGROUP FREQVAL. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
DB2 10 for z/OS and DB2 11 for z/OS:
A LOAD utility with multiple LOB columns where some but not all
LOB columns were loaded inline abended with ABEND04E RC00C90D01
DSNOTCSO +x'70BE'. The problem occurred when a LOB column was
erroneously processed as an inline LOB because of an internal
flag that was not reset.
DB2 11 for z/OS:
A LOAD utility with STATISTICS TABLE COLGROUP FREQVAL specified
to collect distribution statistics abended with an ABEND0C4
DSNUGSRP +x'1B9C' and ended with RC00E40347. The problem
occurred when distribution statistics were processed incorrectly
during the inline statistics sort.
The LOAD utility on DB2 10 for z/OS and DB2 11 for z/OS has
been modified to process inline LOB columns correctly.
The LOAD utility on DB2 11 for z/OS has been modified to
sort the inline statistic records correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19044
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURWBF PI19044
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19044 DSNURWBF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURWBF
LISTEND
UI20365 COVER LETTER END
UI20367 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI19040 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REPAIR utility *
****************************************************************
* PROBLEM DESCRIPTION: DB2 10 for z/OS and DB2 11 for z/OS: *
* ABEND04E RC00C90101 DSNICUBC:500B *
* during REPAIR LOCATE DELETE SHRLEVEL *
* CHANGE. *
* *
* DB2 11 for z/OS: *
* DSNU675I indicates incorrect version *
* number for pageset during a *
* REPAIR CATALOG utility. *
* *
* Data rows were not deleted during a *
* REPAIR DELETE DATAONLY utility. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REPAIR LOCATE DELETE SHRLEVEL CHANGE utility on DB2 10 for
z/OS or DB2 11 for z/OS abends with ABEND04E RC00C90101
DSNICUBC:500B when the table has HASH organization. REPAIR
was testing a variable incorrectly for HASH.
DB2 11 for z/OS only:
REPAIR CATALOG utility has the incorrect version number
as seen in MSGDSNU675I.
DSNU675I - LOW VERSION FOR DBID=X'nnnn' PSID=X'nnnn'
OBID=X'nnnn' DB2 CATALOG IS 0, BUT IN THE PAGE SET IS 1.
REPAIR was using an incorrect variable for REPAIR CATALOG.
A REPAIR LOCATE TABLESPACE dbname.tsname RID X'0205' DELETE
DATAONLY utility was run to delete a data record. The REPAIR
ended successfully but the data record was not deleted.
REPAIR utility code has been modified to fix the aforementioned
problems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19040
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCDEL PI19040
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19040 DSNUCDEL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCDEL
LISTEND
UI20367 COVER LETTER END
1
UI20375 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20956 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of XML *
* publishing functions. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000038 DSNSVSFB+0696 or *
* ABEND0C4 RC00000004 DSNXXGEN+218C may *
* occur when XML storage allocation *
* failed when processing the XML *
* publishing functions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the XML storage is not available, SQLCODE -904 should be
issued. But in some case while processing the XML publishing
function, like XMLATTRIBUTES, XMLCOMMENT, XMLCONCAT, XMLELEMENT,
XMLFOREST, XMLNAMESPACES, XMLPI and XMLTEXT, the returned
pointer is not handled properly. This may cause the ABEND0C4
RC00000038 DSNSVSFB+0696 or ABEND0C4 RC00000004 DSNXXGEN+218C
to occur.
DB2 is modified so the SQLCODE -904 will be issued, instead of
ABEND.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20956
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXMLSM PI20956
DSNXXGEN PI20956
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20956 DSNXMLSM DSNXXGEN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXMLSM
DSNXXGEN
LISTEND
UI20375 COVER LETTER END
UI20387 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20169 -
****************************************************************
* USERS AFFECTED: All Users of DB2. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Abend04E RC00C90101 in DSNIUNCA *
* ERQUAL5006 DURING BACKOUT LOG APPLY *
* PHASE OF ONLINE REORG. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During Log apply phase of online reorg Data Manager (DM)
may require to performs page compaction before it can insert a
new record successfully in the candidate page. When page
compaction is perform, DM writes a diagnostic log record subtype
= '0068'X. If for some reason that atomic insert operation
fails, DM triggers backout which backs out just that insert
operation. During back out operation, DM does not process this
diagnostic log record correctly which results in backout
operation incorrectly detecting end of the log. i.e. reaching
begin Unit of Recovery (UR) log record instead of stopping at
the above diagnostic log record.
DM log apply logic will make sure that it will process the
above page compaction diagnostic log record, if written
during the online reorg log apply phase.
DB2 REORG log apply error handler logic is modified to process
all log record in a correct sequence to avoid unwarranted log
apply failure.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20169
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIUNCA PI20169
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20169 DSNIUNCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIUNCA
LISTEND
UI20387 COVER LETTER END
UI20414 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18100 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those using TCP/IP with APAR *
* PM98265 applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABND=04E-00D3440D *
* LOC=DSNLILLM.DSNLISDA+0D46 *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
When a DB2 requester fails to establish a connection to a
remote location, in some cases DB2 might incorrectly use a
different location, not specified by the application, to
establish the connection. This can happen if APAR PM98265 is
applied.
After a successful data send, DB2 attempts to update accounting
information relative to the (incorrect) location but an abend
may occur because the associated accounting block does not
exist.
DB2 connection "fail over" logic has been changed to ensure
that the location being targeted is consistent with the
application request.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18100
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCCDR PI18100
DSNLCITR PI18100
DSNLTCCN PI18100
DSNLTINT PI18100
DSNLTRDL PI18100
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18100 DSNLCCDR DSNLCITR DSNLTCCN DSNLTINT DSNLTRDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCCDR
DSNLCITR
DSNLTCCN
DSNLTINT
DSNLTRDL
LISTEND
UI20414 COVER LETTER END
UI20439 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20069 -
****************************************************************
* USERS AFFECTED: All users of the installation CLIST for DB2 *
* 10 for z/OS and DB2 11 for z/OS are affected *
* by this change. *
****************************************************************
* PROBLEM DESCRIPTION: The DB2 installation CLIST terminates *
* after outputting the following error *
* messages: *
* *
1 * DSNT456I ERROR IN VARIABLE *
* SIMULATED_CPU_COUNT, VALUE *
* IS n *
* DSNT460I VALUE IS TOO HIGH, MAXIMUM *
* IS 255 *
* DSNT465I VARIABLE SIMULATED_CPU_COUNT *
* SET TO n *
* DSNT468I ERROR(S) ENCOUNTERED, OUTPUT *
* IS BYPASSED. *
* *
* where 'n' is the SIMULATED_CPU_COUNT *
* setting specified in the DSNTIDxx *
* input member. *
* *
* The CLIST may also terminate after *
* outputting the following error *
* messages: *
* *
* DSNT456I ERROR IN VARIABLE *
* SIMULATED_CPU_SPEED, VALUE *
* IS n *
* DSNT460I VALUE IS TOO HIGH, MAXIMUM *
* IS 2147483647 *
* DSNT465I VARIABLE SIMULATED_CPU_SPEED *
* SET TO n *
* DSNT468I ERROR(S) ENCOUNTERED, OUTPUT *
* IS BYPASSED. *
* *
* where 'n' is the SIMULATED_CPU_SPEED *
* setting specified in the DSNTIDxx *
* input member. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
Configuration settings managed by the DB2 installation CLIST
are typically validated by the DB2 installation panels. However,
the CLIST itself performs independent range validation on many
settings, using minimum and maximum bounds that reside in the
fourth and fifth fields of the settings' entries in the CLIST
input (DSNTIDxx) member. For example, in the following entry,
character (as opposed to numeric) range checking is specified
to indicate that a valid setting for AUTHID ranges from a single
byte of not less than '$' to 8 bytes of not greater than
'Z9999999':
AUTHID CHARR G $ Z9999999 <x>
If this is not the case, the CLIST writes diagnostic messages
and terminates.
CHARR comparisons are strictly character-oriented, thus '2' is
considered larger than '10'.
The unexpected validation errors for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED, noted in the problem description section
of this APAR, occur because the DSNTIDxx range check settings
1 for those parameters specify a numeric upper bound
SIMULATED_CPU_COUNT CHARR G OFF 255 <y>
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <z>
The intent was to validate that SIMULATED_CPU_COUNT is set
to OFF or to a value of up to 255; and to validate that
SIMULATED_CPU_SPEED is set to OFF or to a value of up to
2147483647. However, because CHARR range checking is
character-oriented, any setting that begins with '3' - '9'
is reported as out of bounds.
Note: The actual upper bound of SIMULATED_CPU_COUNT, enforced by
DSN6SPRM at assembly time, is 127 not 255 as currently
indicated in DSNTIDxx.
In response, DSNTIDXA and DSNTIDXB are modified to discontinue
range checking the upper bound of SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED:
SIMULATED_CPU_COUNT CHARR G OFF NONE <y>
SIMULATED_CPU_SPEED CHARR G OFF NONE <z>
Since the settings of these parameters can be either alphabetic
or numeric, only the lower (alphebetic) bound can be checked.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20069
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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 <y>
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <z>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <y>
SIMULATED_CPU_SPEED CHARR G OFF NONE <z>
where <y> is the current setting of SIMULATED_CPU_COUNT
and <z> is the current setting of SIMULATED_CPU_SPEED. Save
your changes.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIDXA PI20069
DSNTIDXB PI20069
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20069 DSNTIDXA DSNTIDXB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIDXA
DSNTIDXB
LISTEND
UI20439 COVER LETTER END
UI20441 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22438 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) Users. *
* Specifically those operating with DSNHDECP *
* SCCSID 290 environments. *
****************************************************************
* PROBLEM DESCRIPTION: QMDA information in IFCID 3 Accounting *
* records may contain invalid data *
* relative to DB2 10 for z/OS (New *
* Function Mode), or higher, *
* environments with DSNHDECP SCCSID=290. *
* An invalid user ID value may also be *
* observed in various messages. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Once DB2 10 for z/OS is migrated to New Function Mode, which
also applies to DB2 11 for z/OS (any mode), DB2 for z/OS will
support Unicode based DRDA traffic from remote client
application environments. As a result, the DB2 must convert
this Unicode data to EBCDIC.
QMDA information in the IFCID 3 accounting record originates
from remote clients via the PRDDTA contents of the DRDA ACCRDB
command. This data is converted to EBCDIC using the DSNHDECP
SCCSID value but lower case values are converted incorrectly
in SCCSID 290 environments because this character range is
reserved for Katakana characters.
Users typically notice this conversion error relative to the
QMDAAPPL and QMDAATID fields since they often contain lower
case characters. These fields may be reported as PLANNAME and
ENDUSER values in OMPE accounting trace reports.
Users may also notice an invalid user ID value in various
messages. These include the USERID value in the DSNV437I
(V437) message of the Display Thread command report, or in the
user ID (third) component of THREAD-INFO information provided
in some messages.
Relative to DSNHDECP SCCSID 290 environments, DB2 has been
changed to convert DRDA ACCRDB PRDDTA contents to EBCDIC using
CCSID 37 instead of the DSNHDECP SCCSID (290) value.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22438
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTACC PI22438
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22438 DSNLTACC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTACC
LISTEND
UI20441 COVER LETTER END
UI20452 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20643 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* of the MQListener application. *
****************************************************************
* PROBLEM DESCRIPTION: This apar provides an enhancement for *
* the MQListener application to support *
* multiple versions of native stored *
* procedures. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Prior to this apar, if multiple versions of native stored
procedures were defined via the MQListener application,
MQListener could terminate with an SQLCODE811 (SQL code -811)
during its startup.
This apar provides an enhancement for MQListener to support
multiple versions of native stored procedures. MQListener will
now setup the active version of a native stored procedure during
startup and will invoke that version for its life time.
After applying the ptf for this apar PI20643, the following
actions will need to be performed. Rerun DSNTIJML for the
'BINDBRM' step to rebind MQListener and rebind the MQListener's
applications.
Additional Keywords: SQLCODE811
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20643
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@MQCF PI20643
DSN@MQRN PI20643
DSNAMQLN PI20643
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20643 DSN@MQCF DSN@MQRN DSNAMQLN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSN@MQCF
DSN@MQRN
DSNAMQLN
LISTEND
UI20452 COVER LETTER END
UI20454 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18923 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of FIELDPROC. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC00000004 at DSNXISB6 *
* OFFSET 81CE may occur when creating *
* a partitioned index where at least *
* one column is encoded by FIELDPROC. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 RC00000004 at DSNXISB6 OFFSET 81CE may occur when
creating a partitioned index where at least one column is
encoded by a FIELDPROC and this FIELDPROC is encoded as a
DECIMAL data type.
When DB2 processes each column in a partitioned index and it
reaches a FIELDPROC column of DECIMAL data type, the limit key
value is not processed correctly. Hence causes the abend.
The incorrect handling of FIELDPROC DECIMAL column could also
occur at ALTER TABLE ADD PARTITION, ALTER TABLE ALTER / ROTATE
PARTITION, ALTER INDEX ALTER PARTITION, and ALTER TABLE ADD
PARTITION BY statements and the symptom may vary.
Following is an example of such failing scenario:
CREATE DATABASE MYDB01;
1
CREATE TABLESPACE MYTS01
IN MYDB01
USING STOGROUP SYSDEFLT
PRIQTY 4 SECQTY 4
NUMPARTS 3
SEGSIZE 0
BUFFERPOOL BP2
MAXROWS 255;
CREATE TABLE T1
(I1 INT NOT NULL,
I2 INT NOT NULL,
I3 INT NOT NULL,
C4 VARCHAR(2) FIELDPROC FPALL5 NOT NULL,
PRIMARY KEY (I1, C4, I2))
IN MYDB01.MYTS01 ;
COMMIT ;
CREATE UNIQUE INDEX IDX01
ON T1
(I1 ASC,
C4 ASC,
I2 ASC)
USING STOGROUP SYSDEFLT
PRIQTY 4 SECQTY 4
(PARTITION 1 ENDING AT (1.),
PARTITION 2 ENDING AT (500.),
PARTITION 3 ENDING AT (1000.))
BUFFERPOOL BP1
;
COMMIT ;
DB2 is modified to process the limit key value correctly if it
is encoded by a FIELDPROC DECIMAL data type.
Additional Keywords: SQLCREATE SQLDECFLOAT SQLALTER
SQLFIELDPROC ABEND0C4 RC00000004
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18923
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISB6 PI18923
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18923 DSNXISB6
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISB6
LISTEND
UI20454 COVER LETTER END
1
UI20558 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI13918 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* who use audit policies. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 CSECT DSNXAMAP *
* occurred when an audit policy *
* was started. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 CSECT DSNXAMAP occurred when an audit
policy was started, where the DBNAME field specified for the
policy in SYSIBM.SYSAUDITPOLICIES was longer than supported.
However, this did not set the error return code, and
DB2 consequently reported incorrectly that the trace
was started.
Code has been changed to issue an error instead of an abend,
if the DBNAME specified is greater than 8 characters.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI13918
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXAMAP PI13918
DSNXKDC2 PI13918
DSNXKDR2 PI13918
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI13918 DSNXAMAP DSNXKDC2 DSNXKDR2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXAMAP
DSNXKDC2
DSNXKDR2
LISTEND
UI20558 COVER LETTER END
1UI20561 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06690 -
****************************************************************
* USERS AFFECTED: All DB2 V10 and V11 for z/OS users. *
* *
****************************************************************
* PROBLEM DESCRIPTION: When the LOB table space SYSSPUDXA *
* and SYSSPUDXB associated with the *
* DBD01 table space have grown beyond *
* 1 low level spacemap, then a high *
* concurrent DDL or BIND operation *
* can experience space map page *
* latch contention. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When inserting LOB data into the space beyond the first low
level space map page of the SYSSPUDXA and SYSSPUDXB table
spaces, an exclusive latch is acquired for space search.
Its purpose is to optimize performance by avoiding the need
need to toggle between s-latch and x-latch on the space map
page just in case an extend is necessary.
However, this results in the space map page latch contention
when there is a high volume of concurrent threads running
parallel and accessing these table spaces.
DB2 code is modified to only acquire exclusive x-lath on
space map page when possible free space is found for
insert.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06690
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOALLO PI06690
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06690 DSNOALLO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOALLO
LISTEND
UI20561 COVER LETTER END
UI20585 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18833 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* multi-table joins. *
1 ****************************************************************
* PROBLEM DESCRIPTION: DB2 may select an inefficient join *
* sequence for a query which has a query *
* block with a join of 3 or more tables. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may select an inefficient join sequence for a query which
has a query block with a join of 3 or more tables. In
particular, when there are multiple tables which are joined
via unique indexes, one of them may be joined at a later
position while joining it earlier may provide better
performance.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE
Code is changed to resolve the access path selection issue
for the situation described above. DB2 will have a better
chance to choose more efficient access paths for these
types of queries. As with any change to DB2 query
optimization that can drive a different access path,
there is some risk of query performance regression.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18833
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***Action for PM87084:
See PM87084 APAR/PTF text for additional information about
why a REBIND is necessary.
PM87084 corrects a problem of incorrect output for a query
with an ORDER BY clause that refers to a table with an
OMNIFIND function.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
1 ***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.
DB2BIND:
***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.
DB2BIND:
***Action for PM75197:
See PM75197 APAR/PTF text for additional information about
why a REBIND is necessary.
PM75197 corrects a problem of inefficient access path for
read only queries with FOR UPDATE.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM73214:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM73214 corrects a problem of inaccurate cost estimation for
a query when the query contains a view or table expression with
UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM72676:
1
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.
DB2BIND:
***Action for PM58932:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM58932 corrects a problem that DB2 may choose an inefficient
join sequence for a query joining 3 or more tables.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM34814:
See PM34814 APAR/PTF text for additional information about
why a REBIND is necessary.
PM34814 corrects a problem that DB2 may select an inefficient
join sequence for a query if a declared global temporary table
is involved or statistics on join columns are not collected.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM32404:
See PM32404 APAR/PTF text for additional information about
why a REBIND is necessary.
PM32404 corrects a problem of inaccurate filter factor
estimation for a predicate that is generated by global
optimization for an IN subquery or EXISTS subquery if there are
multiple IN or EXISTS subqueries in the same query block.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM29262:
1
See PM29262 APAR/PTF text for additional information about
why a REBIND is necessary.
PM29262 corrects a problem of inaccurate output in
DSN_DETCOST_TABLE when a materialized query block occurs.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM25629:
See PM25629 APAR/PTF text for additional information about
why a REBIND is necessary.
PM25629 resolves a case in which an inefficient join sequence
could be chosen for a query block with four or fewer tables.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM17234:
See PM17234 APAR/PTF text for additional information about
why a REBIND is necessary.
PM17234 will allow more join permutations to be considered when
there are a high number of query blocks, but each query block
contains less than or equal to four tables.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PI18833:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
1
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPKN PI18833
DSNXOSJO PI18833
DSNXOTS PI18833
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18833 DSNXOPKN DSNXOSJO DSNXOTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPKN
DSNXOSJO
DSNXOTS
LISTEND
UI20585 COVER LETTER END
UI20600 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22185 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE utility on a *
* table space with hash organization *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE AUTOESTSPACE YES on a *
* table space with hash organization got *
* ABEND04E RC00C90101 DSNICDPH ERQUAL500B *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a REORG TABLESPACE AUTOESTSPACE YES on a table space
with hash organization. During initialization, the utility
failed with an ABEND04E RC00C90101 DSNICDPH:500B due to an
incorrect data size used. The incorrect value is caused by
usage of a negative DATASIZE value from Real Time Statistics
( RTS ).
Although uncommon, there are valid situations which can result
in RTS having a negative DATASIZE value. In such situations,
REORG should treat the negative RTS values as not available.
Code has been modified for REORG to avoid using negative RTS
DATASIZE value during AUTOESTSPACE execution on a table space
with hash organization.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22185
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGHSH PI22185
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22185 DSNUGHSH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGHSH
LISTEND
UI20600 COVER LETTER END
UI20615 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20992 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users who use FlashCopy image *
* copies (FCIC). *
****************************************************************
* PROBLEM DESCRIPTION: Utilities using FlashCopy did not *
* update the COPYLASTTIME value in *
* SYSIBM.SYSTABLESPACESTATS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran a COPY utility with FLASHCOPY YES FCCOPYDDN but without
the COPYDDN keyword. The utility ended with RC0 but the column
COPYLASTTIME in SYSIBM.SYSTABLESPACESTATS was not updated with
the copy timestamp. The Real-Time statistic (RTS) for the FCIC
timestamp was not updated. This problem can also occur for the
REORG TABLESPACE, REORG INDEX, LOAD, and REBUILD INDEX utilities
SYSIBM.SYSINDEXSPACESTATS was not updated as well.
These other RTS columns were not zeroed or set to null when the
FCIC was created: COPYUPDATEDPAGES, COPYCHANGES, COPYUPDATELRSN,
COPYUPDATETIME.
This problem only occurs if FlashCopy image copies were the only
type of copy being taken.
This problem also exists for FLASHCOPY CONSISTENT with FCCOPYDDN
specified.
DB2 code was changed to update the RTS COPY column values when
FlashCopy is requested for COPY, REORG, LOAD or REBUILD INDEX
utilities.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20992
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBAFI PI20992
DSNUGFCR PI20992
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20992 DSNUBAFI DSNUGFCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBAFI
DSNUGFCR
LISTEND
UI20615 COVER LETTER END
UI20617 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17855 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of MODIFY RECOVERY utility and *
* BACKUP SYSTEM utility *
****************************************************************
* PROBLEM DESCRIPTION: MODIFY RECOVERY placed some table *
* spaces in COPY-pending status when *
* BACKUP SYSTEM was running, even *
* though there were plenty of previous *
* System Level Backups (SLBs) available *
* for these table spaces and MODIFY *
* RECOVERY did not remove any image *
* copy entries from SYSIBM.SYSCOPY *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran a MODIFY RECOVERY utility while BACKUP SYSTEM utility
was running. When both of these utilities successfully
finished, some table spaces were placed in COPY-pending status
by MODIFY even though there were some SLBs that satisfied the
requirement to be backups for those table spaces. MODIFY issued
message DSNU573I - NO BACKUP COPIES FOUND and message DSNU381I -
TABLESPACE name IS IN COPY PENDING.
The problem occurred because the MODIFY RECOVERY utility
incorrectly used information for the SLB in progress to
check if it was valid for whole table space.
Additional keywords: SQLCODE -904 SQLCODE904 RC00C90097
MSGDSNU573I MSGDSNU381I
The MODIFY RECOVERY utility has been changed to check whether
the current SLB is in progress and if so will check the
previous SLB.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17855
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUMDEL PI17855
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17855 DSNUMDEL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUMDEL
LISTEND
UI20617 COVER LETTER END
UI20621 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19842 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of a compiled SQL *
* scalar function with a RETURN statement that *
* returns an expression which contains special *
* register CURRENT SERVER, CURRENT PACKAGESET *
* or CURRENT PACKAGE PATH. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at location *
* DSNXGRDS DSNXSTRC M777 or other *
* unexpected ABEND0C4 or ABEND04E *
* or unexpected SQLCODE -104 during *
* rebind may occur 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
CREATE FUNCTION SFUN1(P_NAME VARCHAR(4))
RETURNS VARCHAR(64)
LANGUAGE SQL
DETERMINISTIC
NO EXTERNAL ACTION
READS SQL DATA
INHERIT SPECIAL REGISTERS
DISABLE DEBUG MODE
CURRENT DATA NO
RETURN CASE
1 WHEN SUBSTR(P_NAME, 1, 3) = 'TS4'
THEN P_NAME
WHEN CURRENT SERVER = 'DR_D2T0'
THEN '..' !! P_NAME
ELSE P_NAME
END?
DB2 does not process the expression of RETURN statement properly
which can result in storage overlay and parser error during
rebind.
DB2 is modified correctly to process the expression of RETURN
statement to avoid the problem.
Additional Keywords: DB2OVRLAY/K SQLUDF SQLSPECIALREG
SQLCODE104 SQLSTORAGE SQLREBIND
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19842
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
SQL scalar function could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOYIF PI19842
DSNXOYTR PI19842
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19842 DSNXOYIF DSNXOYTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOYIF
DSNXOYTR
LISTEND
UI20621 COVER LETTER END
UI20670 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21713 -
****************************************************************
* USERS AFFECTED: All users of the DB2-supplied stored *
1 * procedure SYSPROC.ADMIN_DS_LIST, in *
* DB2 10 for z/OS and DB2 11 for z/OS, *
* are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: One or more of the following errors *
* occurs when the DB2 stored procedure *
* SYSPROC.ADMIN_DS_LIST is run *
* (1) DB2 V10: A migrated data set is *
* listed repeatedly until the *
* maximum number of result set rows *
* (as specified by the input *
* parameter MAX_RESULTS) is reached. *
* (2) DB2 V10 and DB2 V11: The name of *
* the oldest generation of a GDG is *
* correctly listed with the high *
* level part of the name (i.e., *
* name of the GDG) stripped off. *
* However, the names of subsequent *
* generations are listed without *
* the GDG name stripped off. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
DB2 V10: While going through a list of data sets to be
returned to the procedure caller, when ADMIN_DS_LIST
encounters a migrated data set, it inserts the migrated
data set information in the result set. However, after the
insert, it does not skip to the next data set in the list.
This causes the stored procedure to keep inserting the
same migrated data set in the result set until it reaches the
specified maximum number of result set rows.
DB2 V10 and DB2 V11: An incorrect variable is checked to
identify a generation data set, causing the second symptom
described in the above PROBLEM DESCRIPTION section.
In response:
- In DB2 V10, ADMIN_DS_LIST is modified to list a migrated
data set only once.
- In DB2 V11, ADMIN_DS_LIST is modified to always strip the
GDG name from the data set name when listing generation data
sets.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21713
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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:
***************************************************************
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMDL PI21713
DSNADMDL PI21713
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21713 DSN@DMDL DSNADMDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMDL
MACROS
DSN@DMDL
LISTEND
UI20670 COVER LETTER END
UI20685 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21188 -
****************************************************************
* USERS AFFECTED: Preconditioning APAR for enabling APAR *
* PI22531. *
****************************************************************
* PROBLEM DESCRIPTION: 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. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
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.
1
Keywords:
EXPLAIN IDAAV4R1/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21188
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOD0 PI21188
DSNXOD0Z PI21188
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21188 DSNXOD0 DSNXOD0Z
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOD0
DSNXOD0Z
LISTEND
UI20685 COVER LETTER END
UI20733 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19850 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* LOBs (Large Objects). *
****************************************************************
* PROBLEM DESCRIPTION: The following two failures (or failure *
* symptoms) could be encountered when *
* using LOBs with the XMLPARSE function. *
* *
* 1. ABEND04E RC00C90101 at DSNOGETD 5008 *
* 2. SQL CODE -20398 RC=000C,RSN=3019 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following two failures (or failure symptoms) could be
encountered when using LOBs with the XMLPARSE function.
1 1. An ABEND04E RC00C90101 at location DSNOGETD ERQUAL5008.
2. An SQLCODE20398 RC=000C,RSN=3019.
When DB2 attempts to convert non-unicode, non-XML data
to a unicode mixed CCSID(1208) via XMLPARSE function, DB2
failed to propagate the resultant length following the
conversion if the conversion causes the original non-unicode
mixed data to expand.
The following two query examples are provided to help
illustrate both failure symptoms.
In the following two examples, CONTENT (in example 1) and
MY_CLOB(in example 2) are in EBCDIC encoding. However,
the result of XMLPARSE will be XML data type with unicode
mixed encoding (1208).
Please note that this error is data dependent, only when the
result of conversion has expanded.
Example 1.
CREATE TABLE MYTAB
( COL1 TIMESTAMP NOT NULL
, COL2 DECIMAL ( 5 , 0 ) NOT NULL
, COL3 VARCHAR ( 28000 )
, CONSTRAINT MYCONS
PRIMARY KEY
(COL1
,COL2
)
)
IN MYDB.MYTS
WITH LLL( COL1, COL2, CONTENT ) AS (
SELECT
COL1, COL2,
CAST(TRIM(COL3) AS CLOB(2M))
FROM MYTAB P
WHERE COL2 = 1
UNION ALL
SELECT
BASE.COL1
, KID.COL2
, BASE.CONTENT CONCAT TRIM(KID.COL3)
FROM LLL BASE, MYTAB KID
WHERE BASE.COL1 = KID.COL1
AND KID.COL2 = BASE.COL2+1
)
SELECT
COL1, COL2,
XMLPARSE( DOCUMENT CONTENT PRESERVE WHITESPACE )
FROM LLL
WHERE (COL1, COL2)
IN (
SELECT COL1, MAX(COL2)
FROM LLL GROUP BY COL1
)
1 ;
Example 2.
SELECT X.*
INTO VAR5
FROM XMLTABLE('/a/b' passing
XMLPARSE(MY_CLOB)
Columns C1 CHAR(5) Path '.') X ;
The code in DB2 is modified to avoid the abend and the
SQLCODE failures.
Additional Keywords: SQLLOB SQLXML
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19850
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOTCSO PI19850
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19850 DSNOTCSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOTCSO
LISTEND
UI20733 COVER LETTER END
UI20776 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17620 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of IFCID0021. *
****************************************************************
* PROBLEM DESCRIPTION: In IFCID 21, the Lock Type '3E'x is *
* the DGTT URID lock, but this lock type *
* was not identified in DSNDQW00. Other *
* lock types had the same issue. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
QW0021KT is used to identify the lock resource type.
DB2 was issuing locked resource types which were not
documented.
DB2 has been modified to add the additional lock resource
types.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17620
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQW00 PI17620
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17620 DSNDQW00
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNDQW00
LISTEND
UI20776 COVER LETTER END
UI20778 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20321 -
****************************************************************
* USERS AFFECTED: All Users of DB2 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: During an authorization check for a *
* plan on an RRS reSIGNON the following *
* abend can occur on an abend scenario. *
* . *
* ABEND04E RC00C90101 AT DSNGEFBL +0EB0 *
* OFFSET0EB0 *
* . *
* Note, other offsets may be possible. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During an RRS resignon, recovery services did not setup a
thread level recovery FRR to handle error scenarios.
.
When authorization for a plan is needed as a new user
broadcast is being issued and there is an abend during
this process, the thread's recovery routines does not get
control to release the necessary latches.
.
This resulted in the reported ABEND04E RC00C90101.
DB2 has been modified to setup a thread level FRR for the
authorization process to handle error scenarios and clean up
the proper structures.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20321
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTAXAC PI20321
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20321 DSNTAXAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTAXAC
LISTEND
UI20778 COVER LETTER END
UI20786 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11924 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users with UK95633 *
* applied, and all DB2 11 for z/OS users *
* with UK98462 applied, who run RESTORE *
* SYSTEM utility with FROMDUMP specified. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNUVBRD during RESTORE *
* SYSTEM utility with FROMDUMP, after *
* applying PM80707 / UK95633 (DB2 10) *
* or PM93233 / UK98462 (DB2 11). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After applying PM80707 / UK95633 in DB2 10, or
PM93233 / UK98462 in DB2 11, two problems can be seen
while running RESTORE SYSTEM utility with FROMDUMP.
1. If HSM fails to return to DB2 normally when invoked by
RESTORE SYSTEM with FROMDUMP, the RESTORE SYSTEM job
fails with ABEND0C4 RC11 in DSNUVBRD near OFFSET1E7C
(DB2 10) or near OFFSET11E4 (DB2 11).
This was due to incomplete checking upon return from
HSM to make sure all necessary fields were set correctly.
2. RESTORE SYSTEM FROMDUMP can sometimes receive ABEND0C4
RC4 in DSNUVBRD near OFFSET1E76 (DB2 10) or near OFFSET1242
(DB2 11) shortly after HSM is successfully invoked.
This occurred when DB2 accessed unallocated storage while
copying a block of storage to a new location. This problem
is intermittent.
additional keywords: ABENDS0C4 0C4 S0C4 PIC4 PIC11
00000004 00000011 +X'1E7C' +X'11E4' +X'1E76' +X'1242'
MSGDSNU1631I
The problems introduced by PM80707 and PM93233 have been fixed.
1. an HSM failure received by DB2 during RESTORE SYSTEM FROMDUMP
will now cause the job to receive
DSNU1631I DSNUVBRD - RESTORE SYSTEM UTILITY FAILED BECAUSE
THE CALL TO DFSMSHSM FAILED WITH RC = rc REASON = rsn
and fail with RC8.
2. RESTORE SYSTEM will no longer access storage which may not
1 have been allocated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11924
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUVBRD PI11924
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11924 DSNUVBRD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUVBRD
LISTEND
UI20786 COVER LETTER END
UI20788 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20134 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD Utility with XML column. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXVTRS:M420 *
* occurs when running DB2 LOAD Utility *
* to load XML data into a table with *
* an XML column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 DSNXVTRS:M420 occurs when running DB2
LOAD Utility to load XML data from HFS and the size of the XML
data file is the multiple of the file i/o buffer size.
For example:
Assume the UNLOADed XML data that contains the path of the
XML data in the HFS, /tmp/PM42304/UNLOADdata/EUGMOFXH, and the
size of the /tmp/PM42304/UNLOADdata/EUGMOFXH file is the
multiple of the file i/o buffer size.
When using LOAD Utility to load this XML data, the ABEND04E
RC00E70005 DSNXVTRS:M420 will occur.
DB2 is modified so the abend will not occur.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20134
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNAINP PI20134
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20134 DSNNAINP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNAINP
LISTEND
UI20788 COVER LETTER END
UI20792 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22105 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: Multiple ABEND0C4s occur in module *
* DSN3RRSX recovery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 occurs in module DSN3RRSX retry. The first abend
occurs during the RRSAF Prepare exit for a Stored Procedure.
The subsequent ABEND0C4s occur because DSN3RRSX recovery has
not restored the STATREG data register when it gets control
from RTM. This recovery problem could also occur for abends
that occur when processing other RRSAF exits.
This fix will also add a check to verify that the ace pointer
is not zero before using it.
DB2 module DSN3RRSX has been updated to avoid the problem with
restoring the STATREG data reg.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI22105
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF requires either an ERLY code refresh or a re-IPL of
zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
1 the PTF.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3RRSX PI22105
DSN3RRXF PI22105
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22105 DSN3RRSX DSN3RRXF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3RRSX
DSN3RRXF
LISTEND
UI20792 COVER LETTER END
UI20794 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21662 -
****************************************************************
* USERS AFFECTED: DB2 10 and DB2 11 for z/OS users who *
* include triggers in their operation. *
****************************************************************
* PROBLEM DESCRIPTION: ABND0C4-00000004 at *
* DSNXGRDS.DSNXEXAT+5952 *
* or other similar abends may occur *
* when a trigger is activated. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a trigger is activated, an abend
ABND0C4-04 at DSNXGRDS.DSNXEXAT+5952 may occur.
The abend is caused by an uninitialized variable.
DB2 has been modified to properly initialize the variable
before the variable is referenced.
Other Keywords:
ABEND0C4 OFFSET5952
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21662
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEXAT PI21662
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21662 DSNXEXAT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNXEXAT
LISTEND
UI20794 COVER LETTER END
UI20796 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20948 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may occur when *
* accessing a table via an index and the *
* index column has an expression range *
* predicate on it running in parallel. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output may occur when accessing a table via an
index and the index column has an expression range predicate
on it running in parallel. When seting up the high/low key range
for each parallel child task, DB2 unintentionally overwrites
the expression predicate buffer. Hence, it could lead to the
incorrect output.
The following is an example of such failing scenario:
CREATE TABLE T1
(C1 SMALLINT,
C2 INT,
C3 CHAR(5));
CREATE INDEX IDX01 ON T1 (C1, C2);
SELECT C1
FROM T1
WHERE C1 > YEAR(CURRENT DATE) - 2;
DB2 is modified to set up the high/low key range for each child
task correctly without overwriting the expression predicate
result buffer.
Additional Keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K
SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20948
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
1 DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBM PI20948
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20948 DSNXOBM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBM
LISTEND
UI20796 COVER LETTER END
UI20823 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22010 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a *
* complex materialized query table. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E2000D at location *
* DSNXOXED DSNSVSFB OFFSET08DA (for V10) *
* or OFFSET08B6 (for V11) could happen *
* when a complex materialized query table *
* is used by a query. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E2000D at location DSNXOXED DSNSVSFB OFFSET08DA
(for V10) or OFFSET08B6 (for V11) could happen when a complex
materialized query table is used by a query.
DB2 did not correctly process the complex materialized query
table which caused the ABEND.
DB2 has been modified to correctly process a complex
materialized query table, so there will be no ABEND.
Additional keywords: SQLMQT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22010
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOXED PI22010
DSNXOXM PI22010
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22010 DSNXOXED DSNXOXM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOXED
DSNXOXM
LISTEND
UI20823 COVER LETTER END
UI20825 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22262 -
****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of an SQL *
* statement that contains a common table *
* expression with a variable, when the common *
* table expression is not referenced. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS.DSNXORHV M101 could happen for *
* an SQL statement that contains a common *
* table expression with a variable, when *
* the common table expression is not *
* referenced and the BIND option REOPT is *
* ALWAYS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1 (
C1 INT,
C2 INT
)
;
WITH CTE1(C1, C2) AS(
SELECT C1, C2
FROM T1
WHERE C1 = ?
)
SELECT COUNT(*)
FROM T1
WHERE C1 = ?
1 ;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLHOSTVAR PARAMETERMARKER SQLPMARKER
SQLPMK SQLCTE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22262
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXORHV PI22262
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22262 DSNXORHV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORHV
LISTEND
UI20825 COVER LETTER END
UI20828 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18723 -
****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of an SQL *
* statement containing a view whose select *
* list item, all but the last, is a scalar *
* function with string unit specification and *
* retuning a character string. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS DSNXGDT2 M111 could happen for *
* an SQL statement containing a view *
* whose select list item, all but the *
* last, is a scalar function with string *
* unit specification and retuning a *
* character string. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE VIEW V1 AS
SELECT
SUBSTRING( 'ABCDEF' , 1, 1, CODEUNITS16 ) AS C1
, 'ABCDEF' AS C2
1 FROM SYSIBM.SYSDUMMY1
;
SELECT * FROM V1
;
DB2 did not correctly process the aforementioned SQL statements,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statements, so there will be no ABEND.
Additional keywords: SQLVIEW SQLFUNCTION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18723
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODTR PI18723
DSNXOFN2 PI18723
DSNXOP1 PI18723
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18723 DSNXODTR DSNXOFN2 DSNXOP1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODTR
DSNXOFN2
DSNXOP1
LISTEND
UI20828 COVER LETTER END
UI20834 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20990 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: The Resource Lock manager request *
* Parameter List (RLPL), allocated *
* for a partition lock or during lock *
* escalation were not properly freed *
* during thread cancelation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The RLPL that was not properly freed during thread cancelation
will remain in ECSA even after the thread is gone. To reclaim
the storage occupied by those RLPL, users need to recycle their
DB2.
Fixes made in DB2 to properly freed the RLPL during thread
1 cancelation, so it won't remain in ECSA after the thread
is gone.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20990
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDALC PI20990
DSNILKDY PI20990
DSNILKES PI20990
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20990 DSNIDALC DSNILKDY DSNILKES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDALC
DSNILKDY
DSNILKES
LISTEND
UI20834 COVER LETTER END
UI20836 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22269 -
****************************************************************
* USERS AFFECTED: DB2 10 and DB2 11 for z/OS users with Data *
* Base in RREPL (Read-or-Replication-only) *
* access mode. *
****************************************************************
* PROBLEM DESCRIPTION: A query on a table may be timed out *
* if its database is in RREPL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When data base is in RREPL, DB2 mistakenly acquired a S gross
lock on the tablespace for any read access. This caused other
agent that needs to access the same tablespace to be timed out.
Fixes made in DB2, so it no longer acquires the S gross lock
on the tablespace if its database is in RREPL. This will allow
more concurrent access to the tablespace.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22269
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBCA PI22269
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI22269 DSNIDBCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBCA
LISTEND
UI20836 COVER LETTER END
UI20843 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21828 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 terminated with ABEND04F *
* RC00E50731 after multiple ABEND0C4 *
* failures in DSNVDTA. MSGDSNV509I *
* is issued prior to DB2 termination. *
* The message is typically issued from *
* the xxxxMSTR address space, but may *
* be issued by xxxxDBM1 or xxxxDIST. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2's monitor task will look for latch holders that are
blocking other threads waiting on the held latch and
internally issue -DISPLAY THREAD SERVICE(WAIT) to attempt
to give higher priority to the latch holder.
In the reported failure, there was an inconsistency in the
agent chain due to a previous problem. This caused the command
to ABEND0C4. The monitor recovery successfully retried. The
subsequent invocation of -DISPLAY THREAD SERVICE(WAIT) suffered
the same abend. After 6 failures, the monitor decided to
terminate the DB2 subsystem.
The monitor task should not terminate DB2 if there is a problem
that causes -DISPLAY THREAD SERVICE(WAIT) to abend. The abend
will be retired, but if it occurs repeatedly the monitor
task will no longer issue the internal call to -DISPLAY THREAD.
The monitor limit for abends remains in place. If serious
problems are detected, the DB2 subsystem will still terminate.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21828
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVMON PI21828
DSNVSDC0 PI21828
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI21828 DSNVMON DSNVSDC0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVMON
DSNVSDC0
LISTEND
UI20843 COVER LETTER END
UI20846 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19782 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC/CLI and DB2 Version 11 for z/OS *
* ODBC/CLI running with LIMITEDBLOCKFETCH=0. *
****************************************************************
* PROBLEM DESCRIPTION: SQLExtendedFetch() returns row status *
* SQL_ROW_SUCCESS_WITH_INFO for rows *
* containing truncated data, when it *
* should return row status *
* SQL_ROW_SUCCESS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When data that is returned for one or more columns in a
row is truncated, SQLExtendedFetch() sets the corresponding
entry in the row status array to SQL_ROW_SUCCESS_WITH_INFO,
instead of SQL_ROW_SUCCESS.
Code has been changed to return the correct row status.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI19782
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC27 PI19782
DSNAOG27 PI19782
DSNAOG0W PI19782
DSNAOCLI PI19782
DSNAOSDK PI19782
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19782 DSNAOC27 DSNAOG27 DSNAOG0W DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC27
DSNAOG27
DSNAOG0W
DSNAOCLI
1
MACROS
DSNAOSDK
LISTEND
UI20846 COVER LETTER END
UI20848 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18866 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of an accelerated *
* static SQL query in one of the following *
* scenarios: *
* - as a result set returned from a DB2 *
* remote stored procedure or remote native *
* SQL procedure (or SQL PL procedure) *
* - as a static query in an SQLJ application *
* that is run using the IBM® Data Server *
* Driver for JDBC and SQLJ, where *
* the user's SQLJ application DB2 package *
* was bound using db2sqljcustomize command *
* parameter ' -onlinecheck NO '. *
* Parameter ' -onlinecheck YES ' is *
* the default. *
****************************************************************
* PROBLEM DESCRIPTION: In the reported problem, a DB2 remote *
* stored procedure or remote native SQL *
* procedure (or SQL PL procedure) *
* returned a result set that is also *
* an accelerated static SQL query. *
* When that procedure terminated *
* the following abend occurred: *
* *
* ABEND04E RC00E70005 at DSNXERT2 :P110 *
* *
* The abend can also occur when using *
* an accelerated static query in an SQLJ *
* application bound as a DB2 package *
* using db2sqljcustomize command *
* parameter ' -onlinecheck NO ', where *
* there is no DB2 routine procedure used *
* in the scenario. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The user invoked a remote DB2 stored procedure that returns
a result set that is also an accelerated static SQL query, and
when the remote procedure terminated, the following
DB2 application abend occurred:
.
ABEND04E RC00E70005 at DSNXERT2 :P110
.
The abend can also occur if the remote procedure is a DB2
native SQL procedure (or SQL PL procedure). The abend does
1 *not* occur for the local DB2 procedure scenario, nor when
an accelerated dynamic query is returned as the result set from
the remote procedure.
.
The abend can also occur without using DB2 routine procedures
for an accelerated static SQL query in an SQLJ application that
is run using the IBM® Data Server Driver for JDBC and SQLJ,
where the user's SQLJ application was bound as a DB2 package
using db2sqljcustomize command parameter ' -onlinecheck NO '.
Parameter '-onlinecheck YES ' is the default, and the abend does
not occur for an SQLJ application when using this default.
.
The abend occurred when DB2 attempted to return SQL descriptor
information about the accelerated static SQL query, but DB2 had
not correctly saved the SQL descriptor information for
the accelerated static query, resulting in the abend.
This occurrence of the DSNXERT2 :P110 abend is limited to
the specific accelerated static query scenarios described above,
where SQL descriptor information about the static query
is needed. It is not applicable to other typical usages of
accelerated static SQL queries.
.
To avoid this reported abend for an SQLJ application, bind the
DB2 SQLJ application package again but using
the db2sqljcustomize command parameter '-onlinecheck YES'
instead of 'onlinecheck NO'.
.
To make this fix effective for the accelerated static SQL query,
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.
DB2 was changed to correctly return SQL descriptor information
about the accelerated static SQL query used in the scenarios
described above.
.
Search keywords: IDAAV4R1/K SQLPROCEDURE SQLSP SQLSTOREDPROC
OFFSETP110 JCCSQLJ JCCT2ZOS JCCT4
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18866
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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,
1 - 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXELX PI18866
DSNXEPP PI18866
DSNXERT2 PI18866
DSNXODML PI18866
DSNXOQ2 PI18866
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18866 DSNXELX DSNXEPP DSNXERT2 DSNXODML DSNXOQ2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXELX
DSNXEPP
DSNXERT2
DSNXODML
DSNXOQ2
LISTEND
UI20848 COVER LETTER END
UI20852 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22542 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of SQL *
* containing UPDATE, INSERT or MERGE statement *
* with bind option EXTENDEDINDICATOR(YES). *
****************************************************************
* PROBLEM DESCRIPTION: This APAR addresses TWO problems. *
* *
* Problem 1. *
* *
* An ABEND0C4 RC0000003B at location *
* DSNXGRDS DSNXOST OFFSET2048, DSNXGRDS *
* DSNXOMRG OFFSET4EB8, or DSNXGRDS *
* DSNXOCAS OFFSET82A6 may occur when a *
* MERGE statement satisfies all of the *
* following list of conditions: *
* *
* 1. a target column of *
* modification-operation is defined in *
* a VIEW which isn't allowed to be *
* updated or defined in base table *
* with generated always in *
1 * generated-column-definition. *
* 2. the right hand side of *
* modification-operation is a column *
* of the source-table. *
* 3. The EXTENDEDINDICATOR(YES) bind *
* option or the specification of WITH *
* EXTENDED INDICATORS prepare *
* attribute is used. *
* *
* Problem 2. *
* *
* SQLCODE -798 or -151 may issue at a *
* different location when an INSERT or *
* UPDATE statement satisfies all of the *
* following list of conditions: *
* *
* 1. a target column of insert or update *
* operation is defined with generated *
* always in *
* generated-column-definition. *
* 2. the right hand side of insert or *
* update operation is a host variable *
* or CAST specification with host *
* variable. *
* 3. The EXTENDEDINDICATOR(YES) bind *
* option or the specification of WITH *
* EXTENDED INDICATORS prepare *
* attribute is used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following examples help to illustrate the problems.
Step 1. Create a Table T1.
CREATE TABLE T1(
POLICY_ID CHAR(5),
SYS_UPDATE NOT NULL GENERATED ALWAYS FOR EACH ROW
ON UPDATE AS ROW CHANGE TIMESTAMP,
SYS_START TIMESTAMP(12) NOT NULL
GENERATED ALWAYS AS ROW BEGIN,
SYS_END TIMESTAMP(12) NOT NULL
GENERATED ALWAYS AS ROW END,
CREATE_ID TIMESTAMP(12) NOT NULL
GENERATED ALWAYS AS TRANSACTION START ID,
PERIOD SYSTEM_TIME(SYS_START, SYS_END)
);
Step 2. The application uses the EXTENDEDINDICATOR bind option.
BIND PACKAGE(...) MEMBER(...)-
EXTENDEDINDICATOR(YES) ....
Step 3. MERGE statement which can cause ABEND0C4.
DCL IND1 BIN FIXED(15);
1 DCL CHARHV1 CHAR(5);
DCL ROWCHHV CHAR(32);
IND1 = 0;
CHARHV1 = 'AAAAA';
ROWCHHV = '2013-12-30-00.00.00.000000000000';
EXEC SQL
MERGE INTO T1 AS V
USING (VALUES(:ROWCHHV :IND1, :CHARHV1 :IND1) FOR 1 ROWS)
AS T(C1, ID)
ON(V.POLICY_ID = T.ID)
WHEN MATCHED THEN
UPDATE
SET (V.SYS_UPDATE, V.POLICY_ID) = (T.C1, T.ID)
WHEN NOT MATCHED THEN
INSERT (V.SYS_UPDATE, V.POLICY_ID)
VALUES(T.C1, T.ID)
NOT ATOMIC CONTINUE ON SQLEXCEPTION;
Step 4. An INSERT or UPDATE SQL statement can cause a SQLCODE
-798 or -151 to be issued at a different location.
DCL IND1 BIN FIXED(15);
DCL ROWCHHV CHAR(32);
IND1 = 0;
ROWCHHV = '2013-12-30-00.00.00.000000000000';
EXEC SQL
INSERT INTO T1(SYS_UPDATE)
VALUES(CAST(:ROWCHHV :IND1 AS TIMESTAMP(12)));
EXEC SQL
UPDATE T1
SET (SYS_UPDATE) = (CAST(:ROWCHHV :IND2 AS TIMESTAMP(12)));
SQLCODE -798 or -151 is issued at DSNXOCAS.
After applying APAR fix, SQLCODE will be issued at DSNXOFF.
DB2 does not process the extended indicator variable properly
which can result in the abend and incorrect SQLCODE.
The bind time code in DB2 is modified to process extended
indicator variables properly to avoid the unexpected problems.
Additional Keywords: SQLUPDATE SQLMERGE SQLINSERT SQLHOSTVAR
SQLCODE798 SQLCODE151 SQLCAST
EXTENDED INDICATORS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22542
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI08057:
See PI08057 APAR/PTF text for additional information about
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCAS PI22542
DSNXOFF PI22542
DSNXOIN PI22542
DSNXOMRG PI22542
DSNXOST PI22542
DSNXOVC PI22542
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22542 DSNXOCAS DSNXOFF DSNXOIN DSNXOMRG DSNXOST DSNXOVC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCAS
DSNXOFF
DSNXOIN
DSNXOMRG
DSNXOST
DSNXOVC
LISTEND
UI20852 COVER LETTER END
UI20910 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22485 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of MODIFY RECOVERY utility in a data *
* sharing environment. *
****************************************************************
* PROBLEM DESCRIPTION: MODIFY RECOVERY incorrectly issued *
* MSGDSNU572I and MSGDSNU381I and put *
* a table space in COPY PENDING when *
* useable copies were available in a *
* data sharing environment. *
1 ****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
If a MODIFY RECOVERY is run in a data sharing environment where
there are residual, open-ended SYSLGRNX entries with MEMBER ID
0000 for the table space written prior to the DB2 system
becoming a member of a data sharing group, MSGDSNU572I -
'ALL site SYSCOPY RECORDS FOR TABLESPACE HAVE BEEN DELETED'
and MSGDSNU381I - 'TABLESPACE IS IN COPY PENDING' are
incorrectly issued and the table space can be left in COPY
PENDING despite useable copies being available.
This problem occurred due to incorrect logic of handling the
open-ended SYSLGRNX entries with MEMBER ID 0000 in a data
sharing environment.
MODIFY RECOVERY utility code was changed to correctly handle
the SYSLGRNX entries with MEMBER ID 0000 to avoid putting
the table space in COPY PENDING when useable copies are
available.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22485
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBCOP PI22485
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22485 DSNUBCOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBCOP
LISTEND
UI20910 COVER LETTER END
UI20930 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19655 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of the UNLOAD, RUNSTATS, *
* REORG, REBUILD and CHECK INDEX utilities. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC4 at DSNUULXA OFFSET0DF2 *
* during UNLOAD utility. *
* *
* ABEND0C4 RC4 at DSNUSTBL OFFSET48EC *
* during RUNSTATS utility. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
UNLOAD encountered an ABENDS0C4 RC00000004 at DSNUULXA +x'0DF2'
1 when trying to unlatch a page not held in the buffer. This
problem occurs when unloading pointer overflow records where
the page being held is not the same as that saved in an internal
control block.
The same problem can also occur for REORG TABLESPACE, CHECK
INDEX, REBUILD INDEX, and RUNSTATS.
Additional symptoms: ABEND0C4 RC00000004 DSNUSTBL OFFSET48EC
+x'48EC'
Utility code has been modified to only unlatch pages currently
being held in the buffer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19655
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCRUL PI19655
DSNUKIUL PI19655
DSNURFBR PI19655
DSNURSCN PI19655
DSNUSTBL PI19655
DSNUULXA PI19655
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19655 DSNUCRUL DSNUKIUL DSNURFBR DSNURSCN DSNUSTBL DSNUULXA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCRUL
DSNUKIUL
DSNURFBR
DSNURSCN
DSNUSTBL
DSNUULXA
LISTEND
UI20930 COVER LETTER END
UI20956 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22915 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Lost updates in data sharing. *
* *
* Corrupted data can result in any of *
* the following symptoms: *
* - Incorrect output, INCORROUT. *
* - ABEND04E RC00C90101, RC00C90102, *
* RC00C90105, or RC00C902xx in *
1 * various CSECTs. *
* - Data/index inconsistencies reported *
* by the CHECK INDEX utility. *
* - Page regression reported by the *
* DSN1LOGP utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A small timing window exits in the process of converting a table
space or index to GBP-dependent, where the P-lock is being
negotiated from state S to state IS. If a page is prefetched
into the buffer pool after the P-lock sequence number is
incremented but before the pageset is marked GBP-dependent, and
if the page has a residual "registered" flag set from an
earlier
period of GBP-dependency, then the page will appear to be both
current and registered, when in fact it has not been registered.
This can cause DB2 to not receive a cross-invalidation when
another member updates that page, resulting in page regression
symptoms.
The P-lock negotiation logic has been modified to close the
timing window, by deferring the increment of the P-lock sequence
number until after the setting of the GBP-dependent status.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22915
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PPP PI22915
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22915 DSNB1PPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PPP
LISTEND
UI20956 COVER LETTER END
UI20965 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18243 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users who use *
* ambiguous scroll cursors. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may choose an inefficient access *
* path for an ambiguous scroll cursor *
* with an ORDER BY clause, where an index *
* matching on an IN-list predicate can be *
* the optimal access method but IN-list *
* is chosen for index screening. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
If a cursor is an ambiguous scroll cursor and the SELECT
statement contains an ORDER BY clause, an INLIST predicate
might not be chosen as index matching but as index screening,
which can result in sub-optimal performance.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE SQLIN SQLORDERBY
SQLASENSITIVE SQLSCROLL
Code is changed to correct the access path selection
for the situation described above. DB2 will have a better
chance to choose more efficient access paths for these
types of queries. As with any change to DB2 query
optimization that can drive a different access path,
there is some risk of query performance regression.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18243
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGCX PI18243
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18243 DSNXOGCX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGCX
LISTEND
UI20965 COVER LETTER END
UI20980 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21658 -
****************************************************************
1 * USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Code analysis found that a zero pointer *
* could be used. No problem has been *
* reported. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Code analysis has found that there are some cases where a zero
pointer could be used to reference storage. No problem has been
reported but this could cause an abend or other unpredictable
results.
The code has been updated to check the pointer before it is used
to reference storage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21658
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEDLC PI21658
DSNGEGFB PI21658
DSNGEPLC PI21658
DSNGESFR PI21658
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21658 DSNGEDLC DSNGEGFB DSNGEPLC DSNGESFR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEDLC
DSNGEGFB
DSNGEPLC
DSNGESFR
LISTEND
UI20980 COVER LETTER END
UI20985 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23112 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement containing an COUNT(*) or *
* COUNT_BIG(*) and a view. *
****************************************************************
* PROBLEM DESCRIPTION: After applying the APAR PI06781 ( *
* UI15845 for V10, UI15846 for V11), *
* ABEND0C4 RC00000004 at the location *
* DSNXGRDS DSNXOOS1 OFFSET5E98 / *
* OFFSET5E46 (for V10) or OFFSET686C (for *
* V11) could happen for an SQL statement *
* satisfying all of the following *
1 * conditions: *
* *
* 1, It contains a view which can be *
* merged. *
* 2. It contains a subquery predicate *
* which satisfies all of the following *
* conditions: *
* A. The subquery contains a table *
* expression with UNION ALL. *
* B. The subquery contains a COUNT(*) *
* or COUNT_BIG(*) in the HAVING *
* clause. *
* C. The subquery contains a *
* correlated column. *
* *
* ABEND0C4 RC00000004 at the location *
* DSNXGRDS DSNXOOS1 OFFSET42A4 could *
* happen for an SQL statement containing *
* a view created and migrated from V6 or *
* prior releases, and the view contains a *
* COUNT(*) or COUNT_BIG(*). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 CHAR(10) NOT NULL,
C2 CHAR(10) NOT NULL
);
CREATE VIEW V1(C1, C2) AS (
SELECT C1, C2
FROM T1
);
SELECT *
FROM V1
WHERE
EXISTS
(SELECT C1, COUNT(*)
FROM
(SELECT * FROM T1
WHERE T1.C1 = V1.C1
UNION ALL
SELECT * FROM T1
) TX(C1, C2)
GROUP BY C1
HAVING COUNT(*) > 1
)
;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
1
Additional keywords: SQLTABLEEXPR SQLCTE SQLSUBQUERY SQLVIEW
SQLCORRSUBQ SQLUNIONALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23112
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEX1 PI23112
DSNXOOS1 PI23112
DSNXOPDS PI23112
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23112 DSNXOEX1 DSNXOOS1 DSNXOPDS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEX1
DSNXOOS1
DSNXOPDS
LISTEND
UI20985 COVER LETTER END
UI21017 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16260 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* table expressions or views. *
****************************************************************
* PROBLEM DESCRIPTION: An abend ABEND04E RC00E2000C at *
* DSNXOMTX DSNSVSVB OFFSET +0AC2 *
* may occur for a complex SQL *
* statements that contains multiple *
* table expressions or views. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An abend ABEND04E RC00E2000C at DSNXOMTX DSNSVSVB OFFSET +0AC2
may occur for a complex SQL statements that contains multiple
table expressions or views because the storage is not managed
efficiently when the table expressions or views are merged.
DB2 was updated to manage the storage efficiently when the
table expressions or views are merged.
Additional Keywords: SQLVIEW SQLSTOR SQLTABLEEXPR SQLSTORAGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16260
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOAF PI16260
DSNXOCU PI16260
DSNXODTX PI16260
DSNXOMTX PI16260
DSNXORMQ PI16260
DSNXOTDA PI16260
DSNXOXCP PI16260
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16260 DSNXOAF DSNXOCU DSNXODTX DSNXOMTX DSNXORMQ DSNXOTDA
DSNXOXCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOAF
DSNXOCU
DSNXODTX
DSNXOMTX
DSNXORMQ
DSNXOTDA
DSNXOXCP
LISTEND
UI21017 COVER LETTER END
UI21019 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21107 -
****************************************************************
* USERS AFFECTED: All DB2 9, 10, and 11 for z/OS users of *
1 * functions that use the z/OS Language *
* Environment. *
****************************************************************
* PROBLEM DESCRIPTION: A DB2 thread may get suspended *
* indefinitely after a thread *
* cancelation request from the user. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a scenario where a user is submitting and canceling SQL
queries that need to use LE environment within DB2 subsystem,
there is a small window where a thread holding an LE token is
canceled before it can return the token to the available queue.
If at that time the limit of LE tokens (controlled by LEMAX
subsystem parameter) is reached, another thread that requires
LE processing may suspend indefinitely.
This situation is rare, since it requires the thread to be
cancelled on a very specific and small code flow window.
Setting LEMAX to its default value (20) or higher will also
work around the issue.
DB2 code was changed to return SQLCODE -20101 with reason code
00E73004 if wait for an available token exceeds 10 seconds.
ADDITIONAL KEYWORDS: SQLLE DSNZPARM SQLCANCEL DB2HANG
SQLCODE20101
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21107
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXCEES PI21107
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21107 DSNXCEES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXCEES
LISTEND
UI21019 COVER LETTER END
UI21027 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23264 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users who need *
* an updated copy of the Diagnosis Guide *
* and Reference (V9, V10, V11). *
1 ****************************************************************
* PROBLEM DESCRIPTION: This APAR provides updated PDF files *
* of the DB2 for z/OS Diagnosis Guide *
* and Reference for V9, V10, and V11. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the following versions of the DB2
Diagnosis Guide and Reference in PDF format:
V9: LY37-3218-10
V10: LY37-3220-07
V11: LY37-3222-01
These are the same versions of this document that are
available on the latest DB2 for z/OS licensed library
collections.
This APAR provides the following versions of the DB2
Diagnosis Guide and Reference in PDF format:
V9: LY37-3218-10
V10: LY37-3220-07
V11: LY37-3222-01
To read these documents, download them as binary to your PC
or other system that supports a PDF reader, such as the Adobe
Acrobat Reader.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23264
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDR PI23264
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23264 DSNDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNDR
LISTEND
UI21027 COVER LETTER END
UI21039 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22837 -
****************************************************************
* USERS AFFECTED: All DB2 users of IFCID134 *
****************************************************************
* PROBLEM DESCRIPTION: When IFCID134 trace is turned on, *
* customer may hit ABEND0C4 *
* RC00000011 at DSNGEDM.DSNGERBK +1EEA *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 DB2 caches internal data structures in internal pool.
When the pool is full, LRU could occur. If LRU could
not get enough space and IFCID134 trace is on, the
above abend could be received due to accessing an
incorrect pointer.
DB2 code has been changed to setup correct pointer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22837
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGERBK PI22837
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22837 DSNGERBK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGERBK
LISTEND
UI21039 COVER LETTER END
UI21041 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19784 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS, and DB2 11 for z/OS *
* utility users with DB2 Sort for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Serviceability.
Serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19784
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
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
1 utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCRIB PI19784
DSNUCRUL PI19784
DSNUCSIN PI19784
DSNUGALC PI19784
DSNUGLSR PI19784
DSNUGRAR PI19784
DSNUGSOR PI19784
DSNUGSRP PI19784
DSNUGSTA PI19784
DSNUGUCA PI19784
DSNUKDXC PI19784
DSNUKIUL PI19784
DSNUKLBD PI19784
DSNUKLOB PI19784
DSNUKPIK PI19784
DSNUREKY PI19784
DSNURPCT PI19784
DSNURPIB PI19784
DSNURPTB PI19784
DSNURSIN PI19784
DSNURULN PI19784
DSNURWBF PI19784
DSNUSAFK PI19784
DSNUSAFQ PI19784
DSNUSAFV PI19784
DSNUSDRB PI19784
DSNUSSIN PI19784
DSNUSSIT PI19784
DSNUSTBL PI19784
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19784 DSNUCRIB DSNUCRUL DSNUCSIN DSNUGALC DSNUGLSR DSNUGRAR
DSNUGSOR DSNUGSRP DSNUGSTA DSNUGUCA DSNUKDXC DSNUKIUL
DSNUKLBD DSNUKLOB DSNUKPIK DSNUREKY DSNURPCT DSNURPIB
DSNURPTB DSNURSIN DSNURULN DSNURWBF DSNUSAFK DSNUSAFQ
DSNUSAFV DSNUSDRB DSNUSSIN DSNUSSIT DSNUSTBL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCRIB
DSNUCRUL
DSNUCSIN
DSNUGALC
DSNUGLSR
DSNUGRAR
DSNUGSOR
DSNUGSRP
DSNUGSTA
DSNUGUCA
DSNUKDXC
DSNUKIUL
1 DSNUKLBD
DSNUKLOB
DSNUKPIK
DSNUREKY
DSNURPCT
DSNURPIB
DSNURPTB
DSNURSIN
DSNURULN
DSNURWBF
DSNUSAFK
DSNUSAFQ
DSNUSAFV
DSNUSDRB
DSNUSSIN
DSNUSSIT
DSNUSTBL
LISTEND
UI21041 COVER LETTER END
UI21047 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18921 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of MERGECOPY utility *
****************************************************************
* PROBLEM DESCRIPTION: MERGECOPY didn't merge multiple *
* incremental copies with out of *
* sequence system pages properly. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran a MERGECOPY utility to create a new full image copy
from another full image copy and multiple incremental copies.
The job ended with RC=0 and new a full copy was created. But
when the newly created full image copy was used as a source
for UNLOAD and then LOAD, reloaded data in the table was
inconsistent.
The reported problem was caused by the MERGECOPY utility not
properly copying the pages when the source incremental copies
contain out of sequence system pages and also duplicated
system pages.
The MERGECOPY utility has been changed to correctly copy the out
of sequence system pages.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18921
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUYBR3 PI18921
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18921 DSNUYBR3
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUYBR3
LISTEND
UI21047 COVER LETTER END
UI21049 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19290 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the RECOVER and COPY utility. *
****************************************************************
* PROBLEM DESCRIPTION: RECOVER table space with XML column to *
* TOLOGPOINT incorrectly set or reset *
* the base table in Auxiliary *
* CHECK-pending (ACHKP). *
* *
* RECOVER or COPY with PARALLEL on a *
* list containing a very large number *
* of objects results in *
* ABEND065-0000000C. *
* *
* Restart RECOVER failed with ABEND04E *
* RC00C90101 DSNKPGCM:5008 when writing *
* the compressed index page into dasd. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR addresses three problems in DB2 11. Problems 1 and 2
apply to DB2 11 only. The third problem (ABEND04E during
restart of RECOVER utility) applies to both DB2 10 and DB2 11.
1. RECOVER sets or resets the base table space in ACHKP
incorrectly, due to the way it processes XML segmented or
partitioned table space.
2. In the case of RECOVER or COPY utility with PARALLEL
specified and a large list, ABENDS065 RC0C was received
because too many subtasks were attached at the same time.
The degree of parallelism was not capped by a subsystem
parameter, but was only based on a virtual memory
calculation.
3. A restart of a RECOVER utility failed with ABEND04E
RC00C90101 because a compressed index page was incorrectly
compressed again when it was written to dasd.
RECOVER utility code has been modified to set or reset the
base table space in ACHKP correctly.
1 RECOVER and COPY utility code has been modified to cap the
parallelism by the subsystem parameter.
RECOVER utility code has been modified to avoid compressing
index pages which are already compressed as they are written
to dasd.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19290
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCAWT PI19290
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19290 DSNUCAWT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCAWT
LISTEND
UI21049 COVER LETTER END
UI21051 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19506 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users who use FlashCopy image *
* copies (FCIC). *
****************************************************************
* PROBLEM DESCRIPTION: COPY utility with FLASHCOPY option *
* generated non-unique sequence numbers *
* when a TEMPLATE is used with the &SQ. *
* substitution variable. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran a COPY utility with FLASHCOPY option on a list of
objects using a TEMPLATE for FCCOPYDDN. The TEMPLATE was
defined with the &SQ. (sequence number) substitution variable
in the data set name. The &SQ. value was not incremented
according to the object sequence. This resulted in more than
one object in the list having the identical data set name,
causing the job to fail with DFSMSdss message ADR709E.
This problem can also occur for the REORG, LOAD, or REBUILD
INDEX utilities with FLASHCOPY option on a list of objects
using a TEMPLATE for FCCOPYDDN.
The code has been modified to correctly generate the sequence
number for a TEMPLATE with &SQ. variable when used for
FCCOPYDDN on a utility with FLASHCOPY YES.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19506
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBBFC PI19506
DSNUGFCB PI19506
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19506 DSNUBBFC DSNUGFCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBBFC
DSNUGFCB
LISTEND
UI21051 COVER LETTER END
UI21084 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20603 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG utility *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability changes for REORG data *
* validations in the LOG apply phase *
****************************************************************
* RECOMMENDATION: Apply PTF when available *
****************************************************************
Serviceability changes to introduce additional data validations
in the LOG phase of REORG TABLESPACE executions.
Serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20603
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURLAP PI20603
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20603 DSNURLAP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURLAP
LISTEND
UI21084 COVER LETTER END
1UI21104 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19131 -
****************************************************************
* USERS AFFECTED: All users of DSNTRIN, the installation and *
* configuration tool for DB2-supplied stored *
* procedures and user-defined functions (UDFs) *
* in DB2 10 for z/OS and DB2 11 for z/OS, are *
* affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: Users of JSON support in DB2 10 and 11 *
* can experience failures that include *
* these diagnostics: *
* ILLEGAL SYMBOL ".". SOME SYMBOLS
*
* THAT MIGHT BE LEGAL ARE: , FROM INTO. *
* SQLCODE=-104, SQLSTATE=42601 *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
DSNTRIN is a program called by job DSNTIJRT to install and
configure DB2-supplied routines, including those provided for
JSON (JavaScript Object Notation) support in DB2 for z/OS.
Currently, users of this support may encounter the SQLCODE -104
error noted in the problem description section of this APAR.
The error occurs because of a syntax error in the SQL statement
generated by DSNTRIN to create the SYSTOOLS.REGSP stored
procedure.
In response, this APAR fixes DSNTRIN to generate the create
statement for SYSTOOLS.REGSP correctly. It also modifies
DSNTRIN to detect and correct the error in existing instances
of SYSTOOLS.REGSP.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19131
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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.
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@RIN PI19131
DSNTRIN PI19131
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19131 DSN@RIN DSNTRIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTRIN
MACROS
DSN@RIN
LISTEND
UI21104 COVER LETTER END
UI21107 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22579 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* customers running the DSNTIJEN job. *
****************************************************************
* PROBLEM DESCRIPTION: The DSNTIJEN job failed in the ENFM0010 *
* job step but ENFM processing continued *
* with a return code of zero. DSNTIJEN *
* processing continued to step ENFM0020 *
* where the ENFM process stopped with a *
* RC=8 and the following message being *
* issued: *
* *
* DSNU777I DSNUECM0 - CATENFM CONVERT *
* STATUS - TABLE SPACE *
* CONVERSION ORDER ERROR. *
* *
* Additional keywords: MSGDSNU777I *
* DB2MIGV10/K DB2MIGV11/K *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A resource unavailable condition during the ENFM processing of
the SYSUTILX directory table space (ENFM0010) was not
correctly handled and it resulted in the ENFM0010 step having
a zero return code. This allowed the DSNTIJEN job ENFM
processing to continue when it should have terminated.
1
When the DSNTIJEN ENFM0020 step was executed it failed and the
following message was displayed in the job output:
DSNU777I DSNUECM0 - CATENFM CONVERT STATUS - TABLE
SPACE CONVERSION ORDER ERROR.
The ENFM process properly detected that the previous DSNTIJEN
job step hadn't yet completed successfully and the ENFM
process was stopped with a RC=8.
DB2 code has been updated so that the ENFM process will properly
handle a resource unavailable condition (00C9000A) during
SYSUTILX ENFM processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22579
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUECM2 PI22579
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22579 DSNUECM2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECM2
LISTEND
UI21107 COVER LETTER END
UI21112 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19349 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of XMLPARSE *
* and XMLTABLE functions. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -904 with REASON 00D50001 or *
* 00D50002 and RESOURCE 0000090A is *
* issued or ABEND04E RC00E70005 *
* DSNNQXCA:M111 occurs when the query *
* contains XMLPARSE function and its *
* output is passed to XMLTABLE function *
* for further processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This is the pre-conditioning APAR for the fix that corrects the
problem of XML storage which is not released when the query
contains XMLPARSE function and its output is passed to XMLTABLE
function for further processing.
1 The enabling APAR is PI20544 which will be shipped at a later
date.
This is the pre-conditioning APAR which prepares the data
sharing group for the enabling APAR.
Additional keywords: SQLXML XMLALL SQLCODE904 RC00D50001
RC00D50002
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19349
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNQXCA PI19349
DSNXEBR PI19349
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19349 DSNNQXCA DSNXEBR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNQXCA
DSNXEBR
LISTEND
UI21112 COVER LETTER END
UI21118 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21874 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a SQL *
* statement containing POSSTR function and *
* the data type of the second argument of *
* POSSTR is BLOB, CLOB or DBCLOB. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may occur 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 * 1. The statement contains a POSSTR *
* function. *
* 2. The data type of the second argument *
* of above POSSTR function is BLOB, *
* CLOB or DBCLOB. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following examples help to illustrate the problem.
Step 1. Create objects.
CREATE TABLE T1 (
"C1" INT,
"C2" BLOB(10)
);
CREATE VIEW V1(D1) AS
SELECT C1 FROM T1
WHERE POSSTR(BLOB(X'33302E31302E3939393A'||
YEAR(CURRENT DATE)),
BLOB(X'31302E3939393A'||YEAR(CURRENT DATE))
)>0
WITH CHECK OPTION;
CREATE INDEX INDEX1 ON T1(
POSSTR(SUBSTR(C2, 1, 10),
BLOB(X'31302E3939393A'))
);
CREATE FUNCTION IUDF1 ()
RETURNS INTEGER
LANGUAGE SQL
DETERMINISTIC
NO EXTERNAL ACTION
READS SQL DATA
RETURN POSSTR(BLOB(X'33302E31302E3939393A'),
BLOB(X'31302E3939393A')) ;
CREATE FUNCTION GENBLOB ()
RETURNS BLOB(10)
LANGUAGE SQL
READS SQL DATA
NO EXTERNAL ACTION
DETERMINISTIC
BEGIN
DECLARE LLEN BLOB(10);
SET LLEN = BLOB(X'33302E31302E3939393A');
RETURN LLEN;
END!
CREATE FUNCTION SFUN1 ()
RETURNS INTEGER
LANGUAGE SQL
READS SQL DATA
1 NO EXTERNAL ACTION
DETERMINISTIC
BEGIN
DECLARE LLEN INTEGER;
SET LLEN=POSSTR(BLOB(X'33302E31302E3939393A'),
BLOB(X'31302E3939393A'));
RETURN LLEN;
END!
CREATE PROCEDURE MYTEST(IN INBLOB BLOB, OUT LLEN INTEGER)
LANGUAGE SQL
COMMIT ON
RETURN NO
L0: BEGIN
SET LLEN = POSSTR(INBLOB, BLOB(X'31302E3939393A'));
END L0!
Step 2. Populate Table T1.
INSERT INTO T1 VALUES(1, BLOB(X'33302E31302E3939393A'));
Step 3. statements which can cause incorrect output.
Example#1: SELECT statement which references index on expression
INDEX1.
SELECT 1 FROM T1
WHERE POSSTR(SUBSTR(C2, 1, 10),
BLOB(X'31302E3939393A')) = 4;
The expected result:
+----------------+
| |
+----------------+
1_| 1 |
+----------------+
But before applying APAR fix, it retrieves 0 row.
Example#2: call native SQL procedure MYTEST.
DCL HV1 SQL TYPE IS BLOB(100);
DCL HV2 BIN FIXED(31);
EXEC SQL SET :HV1 = BLOB(X'33302E31302E3939393A');
EXEC SQL CALL MYTEST(:HV1, :HV2);
The expected result of :HV2 is 4.
But before applying APAR fix, the result of :HV2 is 0.
Example#3: call compiled SQL scalar function SFUN1 or inlined
SQL scalar function IUDF1.
SELECT SFUN1() FROM SYSIBM.SYSDUMMY1;
1 SELECT IUDF1() FROM SYSIBM.SYSDUMMY1;
The expected result:
+----------------+
| |
+----------------+
1_| 4 |
+----------------+
Result before applying APAR fix:
+----------------+
| |
+----------------+
1_| 0 |
+----------------+
Example#4: multiple-row-insert statement with user-defined
function or special register in POSSTR function.
EXEC SQL
INSERT INTO T1(C1) VALUES(
POSSTR(GENBLOB(),
BLOB(X'31302E3939393A'))
)
FOR 2 ROWS
NOT ATOMIC CONTINUE ON SQLEXCEPTION;
EXEC SQL
INSERT INTO T1(C1) VALUES(
POSSTR(BLOB(X'33302E31302E3939393A'||YEAR(CURRENT DATE)),
BLOB(X'31302E3939393A'||YEAR(CURRENT DATE))))
FOR 2 ROWS
NOT ATOMIC CONTINUE ON SQLEXCEPTION;
The expected inserted value is 4.
But before applying APAR fix, the inserted value is 0.
Example#5: multiple-row-insert statement with a VIEW which
contains POSSTR in a predicate and the second
argument of POSSTR contains special register.
EXEC SQL
INSERT INTO V1(D1) VALUES(4)
FOR 2 ROWS
NOT ATOMIC CONTINUE ON SQLEXCEPTION;
The expected inserted value is 4.
But before applying APAR fix, unexpected SQLCODE -254 will be
issued.
DB2 does not process the data type of the second argument of
POSSTR function properly which can result in the incorrect
output.
DB2 has been modified correctly to process the data type of the
second argument of POSSTR function to avoid the incorrect
output.
1
Additional keywords: SQLCREATE SQLSP SQLSTOREDPROC
SQLNATIVESQLPL SQLUDF
SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLVIEW SQLSPECIALREG
SQLINSERT SQLINDEXONEXP SQLCODE254
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21874
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
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.
ACTION:
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 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
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEXF PI21874
DSNXOOS2 PI21874
DSNXRINT PI21874
DSNXRNT9 PI21874
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21874 DSNXOEXF DSNXOOS2 DSNXRINT DSNXRNT9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEXF
DSNXOOS2
DSNXRINT
DSNXRNT9
LISTEND
UI21118 COVER LETTER END
UI21122 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22793 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement containing a function *
* VARCHAR_FORMAT on a FOR BIT DATA column. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output could happen for an *
* SQL statement containing a function *
* VARCHAR_FORMAT on a FOR BIT DATA *
* column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 VARCHAR (80) FOR BIT DATA
);
INSERT INTO T1 VALUES
(X'0E4650458646F245EB438F43BD439143580F')
;
SELECT VARCHAR_FORMAT(C1) FROM T1;
The result of the VARCHAR_FORMAT(C1) should be a FOR BIT DATA
1 type, while DB2 set it with a incorrect CCSID, which could cause
incorrect output when the incorrect CCSID was used to interpret
the data returned.
DB2 has been modified to correctly set the result data CCSID for
VARCHAR_FORMAT on a FOR BIT DATA column, so there will be no
incorrect output.
Additional keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLCCSID
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22793
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFA PI22793
DSNXOBFF PI22793
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22793 DSNXOBFA DSNXOBFF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBFA
DSNXOBFF
LISTEND
UI21122 COVER LETTER END
UI21152 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22762 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: Zero address detection report found *
* potential abend in DSNILRBK and other *
* modules. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
A database table block macro may not process the optional input
parameter properly, and potentially causes abend in DSNILRBK due
to zero pointer. Potential abends are also found in DSNIPSFI
and DSNIPSI due to zero pointer addressing.
The code has been fixed to process the optional input parameter
properly, and check the pointer before referencing the control
block.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22762
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDLGC PI22762
DSNICINV PI22762
DSNICMT1 PI22762
DSNICMT2 PI22762
DSNILRBK PI22762
DSNILREP PI22762
DSNIPSFI PI22762
DSNIPTYM PI22762
DSNIWKFD PI22762
DSNIWTTA PI22762
DSNKRMPD PI22762
DSNKSDEA PI22762
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22762 DSNGDLGC DSNICINV DSNICMT1 DSNICMT2 DSNILRBK DSNILREP
DSNIPSFI DSNIPTYM DSNIWKFD DSNIWTTA DSNKRMPD DSNKSDEA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDLGC
DSNICINV
DSNICMT1
DSNICMT2
DSNILRBK
DSNILREP
DSNIPSFI
DSNIPTYM
DSNIWKFD
DSNIWTTA
DSNKRMPD
DSNKSDEA
LISTEND
UI21152 COVER LETTER END
UI21163 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23016 -
1 ****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS with *
* UPDATE WHERE CURRENT OF statements where the *
* target table is a view containing a subquery *
****************************************************************
* PROBLEM DESCRIPTION: AE PI17107 fix completion *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI17107 fix completion
AE PI17107 fix completion
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23016
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPCO PI23016
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23016 DSNXOPCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPB
DSNXOPCO
LISTEND
UI21163 COVER LETTER END
UI21172 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22206 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ABND04E RC00E30001 at DSNTLCAU+0AEA *
* during phase 2 commit. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
When index access was used with a held cursor, and the page
accessed by the held cursor was updated, the lock on the
page/row was not released at commit. On the commit following
the close cursor, DB2 attempted to release the lock on the
table space to which the still locked page/row belonged. IRLM
detected that all page/row locks associated with the table
space had not been released, resulting in an abend.
Fixes made in DB2 to release all page/row locks at commit for
held cursors using index access.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22206
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICMTC PI22206
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22206 DSNICMTC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICMTC
LISTEND
UI21172 COVER LETTER END
UI21176 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23263 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An RRSAF thead is hung after it is MVS *
* cancelled. Message DSNR048I is issued *
* for the hang backout. The RRSAF *
* threads are suspended in either *
* DSNB5RDP or DSNB1TIMR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An RRSAF thead is hung after it is MVS cancelled. Message
Messgae DSNR048I is issued for the hang backout.
The RRSAF threads are suspended in either DSNB5RDP or
DSNB1TMR.
In this case RRS implicit Backout is called with the
ATRXFlagApplicationAsyncAbend flag set.
DB2 has been updated to defer the DB2 UR Abort if the RRSAF
Backout exit has been called for an implicit Backout with
the ATRXFlagApplication SysncAbend flag set, if DB2 can
determine that EOT will be called for the RRSAF tasks.
1 This fix requires that PI23266 also be installed for the
fix to be fully effective.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23263
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3ID30 PI23263
DSN3RRSM PI23263
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23263 DSN3ID30 DSN3RRSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3ID30
DSN3RRSM
LISTEND
UI21176 COVER LETTER END
UI21178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23266 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An RRSAF thead is hung after it is MVS *
* cancelled. Message DSNR048I is issued *
* for the hang backout. The RRSAF *
* threads are suspended in either *
* DSNB5RDP or DSNB1TIMR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An RRSAF thead is hung after it is MVS cancelled. Message
Messgae DSNR048I is issued for the hang backout.
The RRSAF threads are suspended in either DSNB5RDP or
DSNB1TMR.
In this case RRS implicit Backout is called with the
ATRXFlagApplicationAsyncAbend flag set.
DB2 has been updated to defer the DB2 UR Abort if the RRSAF
Backout exit has been called for an implicit Backout with
the ATRXFlagApplication SysncAbend flag set, if DB2 can
determine that EOT will be called for the RRSAF tasks.
This fix requires that PI23263 also be installed for the
fix to be fully effective.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI23266
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 ACTION:
This PTF requires either an ERLY code refresh or a re-IPL
of zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
the PTF.
ACTION:
***Action for 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.
ACTION:
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
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAPRHX PI23266
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23266 DSNAPRHX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRHX
LISTEND
UI21178 COVER LETTER END
1
UI21192 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24305 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: Environmental issues were causing *
* CPF requests to fail with an ABEND806 *
* RC2C attempting to LINK to IEAVG710. *
* The CPF requests are issued to DEFINE *
* or DELETE the DB2 Command Prefix. *
* The CPF DEFINE issued by DSN3EC0X *
* attempting to register the command *
* prefix during DB2 startup abended, *
* followed by a second abend on the *
* conditional CPF DELETE issued by the *
* DSN3EC0X Estae. This left the ERLY *
* block in the 'STARTING' state, *
* which caused subsequent DB2 commands *
* to be queued. An IPL was needed to *
* reset the ERLY block so that DB2 *
* could be restarted. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following messages were seen after attempting to restart
DB2:
-DSN4 STA DB2
IOS000I 8610,**,SIM,**,**06,,,G49DN1,GXIB034
IEW4009I FETCH FAILED FOR MODULE IEAVG710 FROM DDNAME ISPLLIB
BECAUSE OF AN I/O ERROR.
CSV031I LIBRARY SEARCH FAILED FOR MODULE IEAVG710, RETURN CODE
24, REASON CODE 2706043E, DDNAME ISPLLIB
CSV028I ABEND806-2C JOBNAME=GXIB034 STEPNAME=LGINFIBM
IEA989I SLIP TRAP ID=X806 MATCHED. JOBNAME=GXIB034, ASID=0273.
IOS000I 8610,**,SIM,**,**06,,,G49DN1,GXIB034
IEW4009I FETCH FAILED FOR MODULE IEAVG710 FROM DDNAME ISPLLIB
BECAUSE OF AN I/O ERROR.
CSV031I LIBRARY SEARCH FAILED FOR MODULE IEAVG710, RETURN CODE
24, REASON CODE 2706043E, DDNAME ISPLLIB
CSV028I ABEND806-2C JOBNAME=GXIB034 STEPNAME=LGINFIBM
IEA989I SLIP TRAP ID=X806 MATCHED. JOBNAME=GXIB034, ASID=0273.
The second abend on the CPF issued by the Estae in DSN3EC0X
prevented the ERLY block from being reset. DB2 could not be
restarted until an IPL was done.
Additional tracking has been added to DSN3EC0X to avoid
issuing the CPF DELETE in the Estae if the CPF DEFINE has
abended.
The PTF for this APAR requires either an ERLY code refresh or
a re-IPL of zOS.
To refresh, enter the following commands after applying
1 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.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI24305
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3EC0X PI24305
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24305 DSN3EC0X
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3EC0X
LISTEND
UI21192 COVER LETTER END
UI21202 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19976 -
****************************************************************
* USERS AFFECTED: DB2 10 and DB2 11 for z/OS users who have *
* static, ambiguous, non-held updateable *
* cursors with RELEASE DEALLOCATE enabled *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 issued by DSNITDLE *
* ERQUAL5005 on a positioned DELETE. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
A rollback issued after an OPEN / FETCH but before the
DELETE WHERE CURRENT OF cursor can
cause the two sections to get out of sync.
DB2 will traverse all sections related to the cursor to
do processing required to maintain consistency with the
cursor.
Additional keywords: SQLDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19976
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXECWA PI19976
DSNXEDP PI19976
DSNXEDSC PI19976
DSNXERT PI19976
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19976 DSNXECWA DSNXEDP DSNXEDSC DSNXERT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXECWA
DSNXEDP
DSNXEDSC
DSNXERT
LISTEND
UI21202 COVER LETTER END
UI21235 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22380 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* that can use a sparse index. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E2000F at DSNXECL *
* DSNSVSFB +08EA (OFFSET08EA) can occur *
* when a sparse index calculates the *
* number of in-memory workfile entries *
* incorrectly when BOTH an in-memory hash *
* and workfile are used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E2000F can occur at location DSNXECL DSNSVSFB
OFFSET08EA (because of a storage overlay) when a sparse index
1 miscalculates the number of in-memory workfile entries (for the
sparse index) when BOTH an in-memory hash and workfile are used.
This combination of both an in-memory hash and workfile can
occur when there is a large number of records in the sparse
index. The miscalculation for the in-memory portion was
originally based on the amount of storage used along with an
assumption (i.e. estimate) of the amount of hash space used. If
this hash space used is more than the estimate, then the sparse
index adjusts the amount of in-memory records that it can hold.
However, it never took into account that the very last record
could overlay the trailer at the end of the storage.
DB2 has been modified to correct the number of in-memory
workfile entries (calculation) for a sparse index if BOTH an in-
memory hash and workfile are used and readjusts the number after
it (finally) determines the hash space to use. This will prevent
the possible storage overlay.
Additional Keywords: SPARSEINDEX SQLSPARSEINDEX
DB2OVRLAY/K SMCOVERLAY SQLSTORAGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22380
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSMRE PI22380
DSNXSMRG PI22380
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22380 DSNXSMRE DSNXSMRG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSMRE
DSNXSMRG
LISTEND
UI21235 COVER LETTER END
UI21247 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21272 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS with datasharing *
* who issue the -DIS THREAD SCOPE(GROUP) *
* command *
****************************************************************
* PROBLEM DESCRIPTION: Storage leak in above the bar shared *
* memory *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 With DB2 10, several blocks were moved above the bar to store
message output for DISPLAY THREAD commands with the option
SCOPE(GROUP).
.
When there are messages sent back from other
datasharing members in the group, DB2 was not freeing these
above the bar blocks at the end of the command, resulting in
the reported storage leak.
DB2 has been modified to free the storage once the
output message is no longer needed.
.
KEYWORDS: DB2STGLK/K DB2DSHR SYSPLEXDS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21272
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
In version 10 coexistence mode, all active version 8 and
version 9 members MUST apply this APAR before any version 10
member with this APAR applied is restarted. If not applied
properly, -DISPLAY THREAD SCOPE(GROUP) commands will not return
valid data from remote version 8 and version 9 members which may
result in a large amount of invalid output on the version
10 member. In addition, an ABEND0C4 in CSECT DSNVDTT may
be encountered on the version 10 member.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVDTT PI21272
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21272 DSNVDTT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVDTT
LISTEND
UI21247 COVER LETTER END
UI21280 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24194 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 does not terminate immediately *
* when a log read error is received *
* due to an incorrect RBA or LRSN *
* specified on a conditional restart *
* of DB2. DB2 restart may eventually *
* abend, or could complete restart *
* without truncating the logs. This can *
* happen during a conditional restart in *
1 * single logging mode, when there are *
* COPY2 active log data sets registered *
* in the BSDS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A non-zero return code could be lost in DSNJW306 when a log
read error is received during a conditional restart of DB2
in single logging mode, and when there are still COPY2 active
log data sets in the BSDS. DB2 should terminate immediately
with:
DSNJ232I OUTPUT DATA SET CONTROL INITIALIZATION PROCESSING
FAILED and
DSNV086E DB2 ABNORMAL TERMINATION REASON=00E80084
Return code checking has been corrected in DSNJW306.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24194
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJW306 PI24194
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24194 DSNJW306
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW306
LISTEND
UI21280 COVER LETTER END
UI21287 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22615 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of accounting records *
* and/or correlating token is not correct *
* QWACPACE *
****************************************************************
* PROBLEM DESCRIPTION: 1. Rollup accounting records not always *
* written when the trace is qualified due *
* to reason QWACRSTL/QWACRSTG *
* *
* 2. Token used to correlate a task is *
* not correct in the accounting trace *
* record QWACPACE *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. During retrieval of accounting records (IFCID0003), some
records were not being produced and instead were being filtered
1 out during the qualification process.
.
DB2 v10 has internal blocks for accounting trace records that
were moved above the bar while the code was still looking into
the previous storage area. When looking into the incorrect
area, some SMF records may look to be QWACRSTG or QWACRSTL and
caused DB2 to skip these records.
.
2. QWACPACE is used as the token to correlate a parallel,
utility subtask or autonomous transaction rollup record. When
DB2 v10 code looked at the previous storage area as detailed
in section 1, QWHCAACE can report the token of the current
running task, instead of the correct QWACPACE expected.
SOLUTION: DB2 has been modified to address the correct block
for properly qualified records and report the correct
token to correlate.
KEYWORDS: IFCID 0003
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22615
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CMU PI22615
DSNB1DGB PI22615
DSNB1DRA PI22615
DSNB1DUP PI22615
DSNB1FLW PI22615
DSNB1GBR PI22615
DSNB1GET PI22615
DSNB1GRC PI22615
DSNB1LDN PI22615
DSNB1LTS PI22615
DSNB1LTX PI22615
DSNB1PPG PI22615
DSNB1SSR PI22615
DSNB1TGB PI22615
DSNB1TSD PI22615
DSNB5BPL PI22615
DSNB5CMX PI22615
DSNB5COM PI22615
DSNB5DEL PI22615
DSNB5GBG PI22615
DSNB5GGP PI22615
DSNB5PCO PI22615
DSNB5PGB PI22615
DSNB5RAP PI22615
DSNB5RDP PI22615
DSNB5SCM PI22615
DSNB5SCO PI22615
DSNB5SC1 PI22615
DSNB5SC2 PI22615
DSNB5STS PI22615
DSNB5ULK PI22615
1 DSNB5WCS PI22615
DSNJC005 PI22615
DSNJC007 PI22615
DSNJR006 PI22615
DSNJR007 PI22615
DSNJW001 PI22615
DSNJW101 PI22615
DSNKLTCH PI22615
DSNLCITR PI22615
DSNLCMBE PI22615
DSNLCSRR PI22615
DSNLCVTR PI22615
DSNRUB01 PI22615
DSNTLSUS PI22615
DSNVEUS1 PI22615
DSNVSLT0 PI22615
DSNVXLT0 PI22615
DSNWVAPR PI22615
DSNWVCOL PI22615
DSNWVZD1 PI22615
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22615 DSNB1CMU DSNB1DGB DSNB1DRA DSNB1DUP DSNB1FLW DSNB1GBR
DSNB1GET DSNB1GRC DSNB1LDN DSNB1LTS DSNB1LTX DSNB1PPG
DSNB1SSR DSNB1TGB DSNB1TSD DSNB5BPL DSNB5CMX DSNB5COM
DSNB5DEL DSNB5GBG DSNB5GGP DSNB5PCO DSNB5PGB DSNB5RAP
DSNB5RDP DSNB5SCM DSNB5SCO DSNB5SC1 DSNB5SC2 DSNB5STS
DSNB5ULK DSNB5WCS DSNJC005 DSNJC007 DSNJR006 DSNJR007
DSNJW001 DSNJW101 DSNKLTCH DSNLCITR DSNLCMBE DSNLCSRR
DSNLCVTR DSNRUB01 DSNTLSUS DSNVEUS1 DSNVSLT0 DSNVXLT0
DSNWVAPR DSNWVCOL DSNWVZD1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CMU
DSNB1DGB
DSNB1DRA
DSNB1DUP
DSNB1FLW
DSNB1GBR
DSNB1GET
DSNB1GRC
DSNB1LDN
DSNB1LTS
DSNB1LTX
DSNB1PPG
DSNB1SSR
DSNB1TGB
DSNB1TSD
DSNB5BPL
DSNB5CMX
DSNB5COM
DSNB5DEL
DSNB5GBG
DSNB5GGP
1 DSNB5PCO
DSNB5PGB
DSNB5RAP
DSNB5RDP
DSNB5SCM
DSNB5SCO
DSNB5SC1
DSNB5SC2
DSNB5STS
DSNB5ULK
DSNB5WCS
DSNJC005
DSNJC007
DSNJR006
DSNJR007
DSNJW001
DSNJW101
DSNKLTCH
DSNLCITR
DSNLCMBE
DSNLCSRR
DSNLCVTR
DSNRUB01
DSNTLSUS
DSNVEUS1
DSNVSLT0
DSNVXLT0
DSNWVAPR
DSNWVCOL
DSNWVZD1
LISTEND
UI21287 COVER LETTER END
UI21288 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23703 -
****************************************************************
* USERS AFFECTED: DB2 9, 10, and 11 for z/OS *
* users of sequences *
****************************************************************
* PROBLEM DESCRIPTION: User receives duplicate sequence values *
* after executing ALTER SEQUENCE *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. In the *
* meantime, users can avoid the problem by *
* refraining from executing ALTER SEQUENCE *
* statements and NEXTVAL invocations *
* concurrently. *
****************************************************************
A sequence may incorrectly generate duplicate or unexpected
values if the sequence is concurrently ALTERed and accessed by
the NEXTVAL statement. This occurs because DB2 incorrectly
serializes concurrent ALTER SEQUENCE and NEXTVAL statement
processing.
1 DB2 has been modified to correctly serialize concurrent
ALTER SEQUENCE and sequence reference processing. 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. For such objects, users
must restart the sequence with either ALTER SEQUENCE RESTART or
ALTER SEQUENCE RESTART WITH statements or drop and recreate the
sequence after applying this APAR.
Additional Keywords
SQLALTER
SQLSEQUENCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23703
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIAQ1 PI23703
DSNXIASQ PI23703
DSNXISB2 PI23703
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23703 DSNXIAQ1 DSNXIASQ DSNXISB2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIAQ1
DSNXIASQ
DSNXISB2
LISTEND
UI21288 COVER LETTER END
UI21304 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI23868 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS version 10 and DB2 for z/OS *
* version 11 users of queries that contain a *
* OUTRE JOIN with UNION or UNION ALL and *
* FETCH FIRST N ROW or ORDER BY in its *
* subquery. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may be returned for a *
* OUTER JOIN with UNION or UNION ALL *
* and FETCH FIRST N ROW or ORDER BY in *
* its subquery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output may be returned for a OUTER JOIN with
UNION or UNION ALL and FETCH FIRST N ROW or ORDER BY in its
subquery.
An example for incorrect output is shown below:
WITH
TAB1 (AB) AS
(SELECT 'ALFA'
FROM SYSIBM.SYSDUMMY1
UNION
SELECT 'BETA'
FROM SYSIBM.SYSDUMMY1
UNION
SELECT 'XXXX'
FROM SYSIBM.SYSDUMMY1 FETCH FIRST 2 ROW ONLY )
SELECT *
FROM SYSIBM.SYSDUMMY1 LEFT OUTER JOIN TAB1 AS T ON 1 = 1
WITH UR;
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no incorrect output.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLUNION SQLJOIN SQLOUTERJOIN
SQLFULLJOIN SQLLEFTJOIN SQLRIGHTJOIN
SQLORDERBY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23868
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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
1 rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOMS PI23868
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23868 DSNXOMS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOMS
LISTEND
UI21304 COVER LETTER END
UI21331 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23098 -
****************************************************************
* USERS AFFECTED: All DB2 users using IRLM220 (HIR2220) and *
* IRLM230 (HIR2230) in SYSPLEXDS data-sharing. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 ABEND04E-00C90101 may be issued in *
* DSNKINSL ERQUAL5033 after MSGDSNI031I *
* for lock escalation. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
DB2 may issue ABEND04E-00C90101 in DSNKINSL for broken page(s).
and MSGDSNU086I may be seen in the syslog. This could occur
following a lock escalation. This problem could occur due to
incorrect grant of the parent table/partition lock in IRLM in
DB2 environment using CPU parallelism (DEGREE=ANY), or using
global transactions. A child task using the same compatibility
class token as the parent task, is considered compatible and
gets the lock in any requested state. If the resultant state of
the two locks ( held by the parent task and requested by the
child task) is exclusive but SLM lock state inversion was set
for the lock, IRLM would incorrectly revert the SLM held state
to 'shared' from 'exclusive' state. This results in another
transaction to obtain the parent table/partition lock
invalidly and be able to update the data.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
This APAR fixes IRLM error to calculate the SLM lock state
correctly when issuing IXLLOCK ALTER for a lock. With this
change, IRLM will not change the SLM state of a lock when it is
already held in exclusive state but locking protocol 2 logic
in DB2 is requesting lock state inversion. This will provide
1 proper protection of the parent table/partition lock to avoid
data corruption ABEND04E 00C90101 in DSNKINSL.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI23098
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL1E0 PI23098
DXRRL120 PI23098
DXRRL770 PI23098
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23098 DXRRL1E0 DXRRL120 DXRRL770
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL1E0
DXRRL120
DXRRL770
LISTEND
UI21331 COVER LETTER END
UI21335 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21119 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of an *
* implicit or explicit cast of a LOB data type *
* to a CHAR, VARCHAR, GRAPHIC, VARGRAPHIC, *
* BINARY, or VARBINARY data type. *
****************************************************************
* PROBLEM DESCRIPTION: An unexpected ABEND04E RC00E70005 at *
* location DSNXRRP M700 can occur when *
* performing a data type conversion (a *
* LOB is being converted to a different *
* data type) when an error condition is *
* reached prior to processing a predicate *
* referencing the data. Instead, DB2 *
* should return a correct SQL error code. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An unexpected ABEND04E RC00E70005 can occur at location DSNXRRP
M700 when casting a LOB data type to a CHAR, VARCHAR, GRAPHIC,
VARGRAPHIC, BINARY, or VARBINARY data type when an error
condition is reached prior to processing the predicate
referencing the converted data. DB2 should return a correct
SQLCODE instead.
The following example can illustrate the problem.
1 1. Create a Table with a LOB column and populate the table.
CREATE TABLE T1 (I1 INT, C1 CLOB(1K));
INSERT INTO T1 VALUES(1, CLOB('TEST'));
2. Execute a query which casts a LOB to a VARCHAR data type.
SELECT CAST(C1 AS VARCHAR(3200)) FROM T1
WHERE I1 + 2 < 10;
During the conversion from CLOB to VARCHAR, if there is an error
condition reached (e.g. a resource not available condition), DB2
does not handle the error properly (accidentally letting the
error condition continue) which eventually leads to the above
abend during predicate processing. Instead, DB2 should issue an
SQLCODE -904 and stop before predicate processing in this case.
Please note, some other unexpected DB2 abends could also occur.
The code in DB2 has been modified to prevent the unexpected
abend by issuing the correct SQLCODE for the detected error.
Additional Keywords: SQLLOB SQLCODE904 SQLCAST
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21119
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRBIN PI21119
DSNXRBI9 PI21119
DSNXRDBC PI21119
DSNXRDB9 PI21119
DSNXRSBC PI21119
DSNXRSB9 PI21119
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21119 DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRBIN
DSNXRBI9
DSNXRDBC
DSNXRDB9
DSNXRSBC
DSNXRSB9
LISTEND
UI21335 COVER LETTER END
UI21385 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI20434 -
****************************************************************
* USERS AFFECTED: All DB2 10 & 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: #1. ABEND04E RC00C90102 DSNIBHUN:0C2C *
* or ABEND04E RC00C90101 DSNIBHUN:501B. *
* during RESTART inabort process on a *
* DSNDB01 object. *
* *
* #2. ABEND0C4 DSNISRTI +176a accessing *
* zero address. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
#1. For DSNDB01 object, when backing out an INSERT
log record during RESTART (in-abort), the page needed
to go through compaction process in order to insert back
the data record. Since all pseudo deleted space was
reserved and owned by the same URID, this space should be
compacted and reused by this undo process. Due to missing
communication, the compaction routine was not able to make
those pseudo deleted space available for reuse, and the
log record was not applied to re-insert back the data,
causing DSNIBHUN abends.
#2. During insert process, an internal zero address was
referenced causing 0C4 abend in DSNISRTI.
#1. DB2 code in DSNIBHUN is modified for DSNDB01 object
to consider reuse for the available space when the page
is committed or the space is reserved and owned by the
same URID.
#2. DB2 code in INSERT flow is modified to make sure no
zero address can be accessed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20434
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBHUN PI20434
DSNIRLPG PI20434
DSNISRTI PI20434
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20434 DSNIBHUN DSNIRLPG DSNISRTI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBHUN
DSNIRLPG
DSNISRTI
1
LISTEND
UI21385 COVER LETTER END
UI21419 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23711 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of LOBs *
* with hybrid join. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90101 occurs at DSNIDM *
* DSNOPUFF ERQUAL5037 for a hybrid join *
* when the outer table contains a LOB *
* column that needs to be sorted. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00C90101 can occur at DSNIDM DSNOPUFF ERQUAL5037
for a query that uses a hybrid join access path, references a
LOB column selected from the outer table, and the outer table
needs to be sorted.
The following example helps to illustrate the problem.
Step 1. Create two tables, each with an index.
CREATE TABLE T1 (C1 INT NOT NULL WITH DEFAULT 0);
CREATE TABLE T2 (C1 INT NOT NULL WITH DEFAULT 0,
C2 BLOB(1M) WITH DEFAULT NULL
INLINE LENGTH 4000);
CREATE UNIQUE INDEX IX1 ON T1(C1) CLUSTER;
CREATE INDEX IX2 ON T2(C1) NOT CLUSTER;
Step 2. Insert rows of data into each table.
Step 3. Perform the following select statement using a hybrid
join access path.
SELECT T1.C1, T2.C2
FROM T1 INNER JOIN T2 ON T1.C1 = T2.C1;
The inner table T1 has an index which is clustered and no sort
is needed (hybrid join case 2). The outer table T2 needs to be
sorted and copied to an intermediate table in memory. However,
the LOB column C2 (from Table T2) is not moved correctly by DB2
and this leads to the above mentioned abend.
The code in DB2 has been modified to correctly move the LOB
data using the actual length instead of the declared length.
This will prevent the reported abend.
1 Additional Keywords: SQLLOB SQLHYBRIDJOIN SQLHYBRID HYBRIDJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23711
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRFHJ PI23711
DSNXRGBJ PI23711
DSNXRSFJ PI23711
DSNXRSFN PI23711
DSNXRSGB PI23711
DSNXRT3J PI23711
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23711 DSNXRFHJ DSNXRGBJ DSNXRSFJ DSNXRSFN DSNXRSGB DSNXRT3J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRFHJ
DSNXRGBJ
DSNXRSFJ
DSNXRSFN
DSNXRSGB
DSNXRT3J
LISTEND
UI21419 COVER LETTER END
UI21550 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18738 -
****************************************************************
* USERS AFFECTED: All DB2 users of SYSCHECKS.CHECKCONDITION *
* catalog column to replicate check *
* constraints. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE -104 when *
* replicating check constraints using *
* SYSCHECKS.CHECKCONDITION. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User unexpectedly receive SQLCODE -104 when replicating catalog
table check constraints using SYSCHECKS.CHECKCONDITION.
There are some entries in SYSCHECKS for catalog table check
constraints that contain expressions similar to
'COL1 IN (-1,-2)'. This expression is not valid when
DECIMAL DECP is a COMMA.
This problem does not affect the normal operation of DB2.
1 Catalog initialization files have been updated to fix the
problem for new DB2 installations.
For existing DB2 subsystems, users need to follow the ++HOLD
actions to update the catalog. Here is the text of the
++HOLD actions:
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
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18738
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
ACTION:
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
1
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIS50 PI18738
DSNT0850 PI18738
DSNUECM0 PI18738
DSNUECSE PI18738
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18738 DSNTIS50 DSNT0850 DSNUECM0 DSNUECSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECM0
DSNUECSE
MACROS
DSNTIS50
DSNT0850
LISTEND
UI21550 COVER LETTER END
UI21620 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19132 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM and DB2 abend U2027 DXRRL150+0B8C *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After a RC00E50013 soft cancel failure, IRLM abended on a U2027
causing subsequent DB2 failure. As a result of recovery cleanup
processes for the RC00E50013 failure, an unlatch operation
allowed an IRLM parameter list (RLPL) to be reused prematurely.
IRLM detected this condition and failed on the ABENDU2027.
DB2 program recovery code has been corrected to remove the
unlatch operation in the log record undo / redo code path.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19132
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIB PI19132
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19132 DSNIB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIB
LISTEND
UI21620 COVER LETTER END
UI21640 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22098 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* views that contain aggregate functions *
* with decimal data types. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C7 at DSNXRSGB OFFSET *
* +7720 or an incorrect result can be *
* returned from an SQL statement that *
* references a view that contains *
* a subquery with a UNION or UNION ALL *
* clause and an aggregate function *
* having a decimal expression as input. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C7 at DSNXRSGB OFFSET7720 or an incorrect result can be
returned from an SQL statement that satisfies all of the
following conditions:
1. The statement references a view.
2. The view contains a subquery
with a UNION clause and each leg
includes an aggregate function or
the view contains a subquery
with a UNION ALL clause, each leg
includes an aggregate function and
the query does not satisfy the
union distribution criteria.
3. The input of the aggregate function
contains a decimal expression.
4. The DECIMAL precision option that
is specified at execution differs
from that used during view creation.
1
The following example helps to illustrate a failing case.
Step 1. Create a Table T1.
CREATE TABLE T1 (C1 DECIMAL(14, 5));
INSERT INTO T1 (C1) VALUES (123456789.54321);
Step 2. Create a VIEW V1, on Table T1, using DEC(15) precision.
CREATE VIEW V1 (VC1) AS
SELECT SUM(C1 * 1) FROM T1
UNION
SELECT SUM(C1 * 1) FROM T1 ;
Step 3. Select from the view using DEC(31) precision.
SELECT * FROM V1;
Without the apar fix, incorrect output is returned.
+------------------------------------+
| VC1 |
+------------------------------------+
1_| .01234 |
+------------------------------------+
With the apar fix, correct output is returned.
+------------------------------------+
| VC1 |
+------------------------------------+
1_| 123456789.54321 |
+------------------------------------+
Incorrect output is returned in this case because DB2 did not
hande the different DECIMAL precision options correctly.
The code in DB2 is modified to process a UNION/UNION ALL
in VIEW that contains aggregate functions on decimal
expressions properly when a precision, different from that
used for view creation, is specified.
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.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLUNION SQLUNIONALL
SQLSUM SQLAVG SQLVIEW SQLDECIMAL
SQLARITH SQLDECIMAL31 SQLDEC31
SQLDECIMAL15 SQLDEC15
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22098
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI22098:
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.
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOADT PI22098
DSNXOARI PI22098
DSNXOTDA PI22098
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22098 DSNXOADT DSNXOARI DSNXOTDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOADT
DSNXOARI
DSNXOTDA
LISTEND
UI21640 COVER LETTER END
1UI21659 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18583 -
****************************************************************
* USERS AFFECTED: Users with tables defined with a foreign *
* key and an index with an INCLUDE column, *
* where both conditions are true: *
* 1. the index key columns are an exact *
* match or a superset (i.e. contains *
* same columns in the same order) of *
* the foreign key *
* 2. the index contains an INCLUDE column *
* which is part of the foreign key. *
****************************************************************
* PROBLEM DESCRIPTION: LOAD utility may incorrectly result in *
* MSGDSNU361I if the table is part of a *
* referential integrity relationship *
****************************************************************
* RECOMMENDATION: *
****************************************************************
LOAD utility may incorrectly result in DSNU361I -FOREIGN KEY
HAS NO PRIMARY KEY FOR RELATIONSHIP, if a table is a child
table of a referential integrity relationship because DB2 may
have chosen an incorrect foreign key index. Specifically, one
or more columns used in the foreign key are defined as INCLUDE
column in the index.
This error may occur when an index with an INCLUDE column is
defined on the table and both conditions are true:
1. the index key columns are an exact match
(i.e. contains same columns in the same order) of
the foreign key
2. the index contains an INCLUDE column which is used as part
of the foreign key.
The wrong index may be chosen during CREATE INDEX, ALTER INDEX,
DROP INDEX, or when FOREIGN KEY is specified on CREATE TABLE
or ALTER TABLE.
Other unexpected errors may occur when running utilities.
DB2 will no longer select an index as a foreign key index if a
foreign key column is defined as an INCLUDE column. The follow-
ing paths, where the foreign key index is chosen, have been
updated:
CREATE INDEX
DROP INDEX
ALTER INDEX ADD COLUMN
ALTER TABLE ADD FOREIGN KEY
This APAR does not fix existing problems. If the reported
problem is encountered, users should alter the table to
drop and re-create the foreign key once the APAR is applied.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18583
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDAIX PI18583
DSNGDBDC PI18583
DSNGDBIX PI18583
DSNGDDIX PI18583
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18583 DSNGDAIX DSNGDBDC DSNGDBIX DSNGDDIX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDAIX
DSNGDBDC
DSNGDBIX
DSNGDDIX
LISTEND
UI21659 COVER LETTER END
UI21710 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22946 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of global temporary table and *
* parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect output may occur when the *
* following condition are all met: *
* 1. The query has a group by clause and *
* and aggregate function in the *
* selection list, and *
* 2. The query contains a subquery *
* predicate which referencing a global *
* temporary table,, and *
* 3. The parent query block of this *
* subquery predicate has a parallel *
* sort group in it, and *
* 4. This parallel sort is sort for group *
* by. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect output may occur when the following condition
are all met:
1. The query has a group by clause and an aggregate function in
the selection list, and
2. The query contains a subquery predicate which referencing a
global temporary table, and
3. The parent query block of this subquery predicate has a
parallel sort group in it, and
4. This parallel sort group is sort for group by.
1
When all the above condition are met, DB2 does not adjust the
buffer correctly for the parallel sort group of the global
temporary table's column.
Following is an example of such failing query:
SELECT CAST(TTNAME AS CHAR(18) CCSID EBCDIC) AS TABNAME,
CAST(TCREATOR AS CHAR(8) CCSID EBCDIC) AS CREATOR,
MAX(UPDATEAUTH) AS EDIT,
CAST(T.DBNAME AS CHAR(8) CCSID EBCDIC) AS DBNAMEL,
TTNAME AS TABELLE_L,
TCREATOR AS CREATOR_L,
LABEL AS LABEL_L,
T.DBNAME AS DBNAME_L
FROM SYSIBM.SYSTABAUTH
INNER JOIN SYSIBM.SYSTABLES T
ON TTNAME = NAME AND TCREATOR = CREATOR
WHERE TTNAME LIKE 'D%'
AND ( TCREATOR LIKE '%'
OR ( T.DBNAME LIKE '%' AND T.TYPE='T'))
AND GRANTEE IN
( SELECT CAST(STG_GROUP AS VARCHAR(128) CCSID UNICODE)
FROM MYTEMPTAB
)
GROUP BY TTNAME,TCREATOR,LABEL,T.DBNAME
;
NOTE: MYTEMPTABL is a global temporary table
DB2 is modified to adjust column buffer of the global temporary
table correctly.
Additional Keywords: SQLGROUPBY SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLGTT GTT SQLDGTT DGTT
PARALLELISM SQLPARALLELISM DB2PARALL/K
SQLSUBQUERY SQLINSUBQ SQLSETFUNCTION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22946
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLCM PI22946
DSNXOLL PI22946
DSNXOLM1 PI22946
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22946 DSNXOLCM DSNXOLL DSNXOLM1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLCM
DSNXOLL
DSNXOLM1
LISTEND
UI21710 COVER LETTER END
UI21748 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM89966 -
****************************************************************
* USERS AFFECTED: All V10, V11 DB2 for z/OS users using *
* UNIQUE WHERE NOT NULL indexes when *
* INCLUDE columns are present. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output was returned by *
* DB2 when access of an index with *
* an INCLUDE column was performed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The incorrect output was returned by DB2 when access of a
UNIQUE WHERE NOT NULL index (that contained at least 1
INCLUDE column) was performed.
Additional Keywords: DB2INCORR/K, INCORROUT, SQLINCORROUT
DB2 was incorrectly scanning UNIQUE WHERE NOT NULL indexes
when at least 1 INCLUDE column was present. Code within
DB2 has been corrected to account for all columns of a
UNIQUE WHERE NOT NULL index when an INCLUDE column is present.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM89966
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIKESE PM89966
DSNIOST2 PM89966
DSNIRIDR PM89966
DSNKBULD PM89966
DSNKCEST PM89966
DSNKDLE PM89966
DSNKFLRR PM89966
1 DSNKFLST PM89966
DSNKFPRV PM89966
DSNKFTCH PM89966
DSNKFTRR PM89966
DSNKINSL PM89966
DSNKLOD2 PM89966
DSNKMDEL PM89966
DSNKNXT2 PM89966
DSNKPOSI PM89966
DSNKREST PM89966
DSNXOTL PM89966
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM89966 DSNIKESE DSNIOST2 DSNIRIDR DSNKBULD DSNKCEST DSNKDLE
DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKINSL
DSNKLOD2 DSNKMDEL DSNKNXT2 DSNKPOSI DSNKREST DSNXOTL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIKESE
DSNIOST2
DSNIRIDR
DSNKBULD
DSNKCEST
DSNKDLE
DSNKFLRR
DSNKFLST
DSNKFPRV
DSNKFTCH
DSNKFTRR
DSNKINSL
DSNKLOD2
DSNKMDEL
DSNKNXT2
DSNKPOSI
DSNKREST
DSNXOTL
LISTEND
UI21748 COVER LETTER END
UI21768 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19439 -
****************************************************************
* USERS AFFECTED: All DB2 customers requesting IFCID 375 *
* trace. *
****************************************************************
* PROBLEM DESCRIPTION: When writing trace for IFCID 375, the *
* following abends may be seen: *
* DSNIRIDR:5003, and *
* DSNXEFDA+035DE. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
The reason code is destroyed when writing trace IFCID 375.
Changed code to save and restore the reason code around the
trace.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI19439
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIKDEF PI19439
DSNIREFS PI19439
DSNIREPR PI19439
DSNIRIDL PI19439
DSNIRIDR PI19439
DSNIRLPG PI19439
DSNISRTI PI19439
DSNIXLDR PI19439
DSNURBXA PI19439
DSNXRRID PI19439
DSNXRRI9 PI19439
DSNXSFIN PI19439
DSNXSFML PI19439
DSNXSFPR PI19439
DSNXSFUN PI19439
DSNXSMIN PI19439
DSNXSMRL PI19439
DSNXSMUN PI19439
DSNXSPRM PI19439
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19439 DSNIKDEF DSNIREFS DSNIREPR DSNIRIDL DSNIRIDR DSNIRLPG
DSNISRTI DSNIXLDR DSNURBXA DSNXRRID DSNXRRI9 DSNXSFIN
DSNXSFML DSNXSFPR DSNXSFUN DSNXSMIN DSNXSMRL DSNXSMUN
DSNXSPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIKDEF
DSNIREFS
DSNIREPR
DSNIRIDL
DSNIRIDR
DSNIRLPG
DSNISRTI
DSNIXLDR
DSNURBXA
DSNXRRID
DSNXRRI9
DSNXSFIN
DSNXSFML
DSNXSFPR
DSNXSFUN
DSNXSMIN
1 DSNXSMRL
DSNXSMUN
DSNXSPRM
LISTEND
UI21768 COVER LETTER END
UI21881 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23280 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* use IBM DB2 Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: -STOP ACCEL command hangs when there *
* is no thread off-loaded to the remote *
* Accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 registered a thread that was intended to off-load to the
remote Accelerator. However, in certain cases, this thread may
not off-load after all and deregistration may be delayed if the
thread continues servicing other work. This will result in a
hang of -STOP ACCEL command processing.
DB2 has been changed to register accelerator interest only
when actually necessary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23280
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXHCS PI23280
DSNLXNEW PI23280
DSNLXRCN PI23280
DSNLXRWA PI23280
DSNXONZA PI23280
DSNXONZB PI23280
DSNX8WAC PI23280
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23280 DSNLXHCS DSNLXNEW DSNLXRCN DSNLXRWA DSNXONZA DSNXONZB
DSNX8WAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXHCS
DSNLXNEW
DSNLXRCN
DSNLXRWA
DSNXONZA
1 DSNXONZB
DSNX8WAC
LISTEND
UI21881 COVER LETTER END
UI21946 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22945 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes possible incorrect *
* output when a query with the TIME() *
* scalar function is executed on an *
* accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes possible incorrect output when a query with the
TIME() scalar function is executed on an accelerator when the
expression is a timestamp data type. The hour, minute, second
and fractional seconds are included in the result of TIME()
when executed on an accelerator. The correct behavior for
TIME() is to return the hour, minute, and second.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K SQLTIME
DB2 code is fixed to return the correct result.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22945
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXONZA PI22945
DSNXONZS PI22945
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22945 DSNXONZA DSNXONZS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXONZA
DSNXONZS
LISTEND
UI21946 COVER LETTER END
UI21990 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22630 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG *
* TABLESPACE SHRLEVEL CHANGE utility on a *
* partition by growth table space *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E4030F DSNURLAP OFFSET4600 *
* or ABEND04E RC00C90D01 DSNOTCSO *
* OFFSET6FB4 encountered during REORG *
* TABLESPACE SHRLEVEL CHANGE execution *
* on a PBG table space *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There are two problems addressed in this apar :
1> User ran a REORG TABLESPACE SHRLEVEL CHANGE utility
against a compressed PBG table space.
During REORG log apply phase, in order to apply an
UPDATE log record, the data row needed to be inserted into a
different partition. An invalid pointer was used to point to the
row to be inserted. That caused bad data to be inserted into
the table space during REORG utility. When there was a unique
index created on the table space being reorged, the invalid data
row could cause the uniqueness violation error and cause the
REORG to fail with ABEND04E RC00E4030F DSNURLAP OFFSET4600.
It is also possible that REORG can finish successfully,
but data is left broken after REORG utility.
2> User ran a REORG TABLESPACE SHRLEVEL CHANGE utility
against a PBG table space and there was a LOB column defined on
the table being reorged.
During REORG log apply phase, when applying an UPDATE
log record, the base row needed to be moved to a different
partition. The log apply code tried to move the LOB data
to the new partition as well, causing ABEND04E RC00C90D01,
M=DSNTFRCV,LOC=DSNIDM .DSNOTCSO OFFSET6FB4.
Code has been modified to correct the PBG cross partition update
logic in REORG log apply phase to resolve the aforementioned
issues.
1
1> The correct pointer is used to point to the row when REORG
applies an UPDATE log record on a table in compressed PBG
table space and needs to insert the correct row to a different
partition.
2> When REORG applies an UPDATE log record and causes the base
row to change partition, data manager log apply routine will
not try to move the LOB data to the new partition. REORG utility
will handle the LOB movement/deletion/insertion after the
base row update is done.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22630
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILREP PI22630
DSNIREPR PI22630
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22630 DSNILREP DSNIREPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
DSNIREPR
LISTEND
UI21990 COVER LETTER END
UI22071 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22446 -
****************************************************************
* USERS AFFECTED: All LOB streaming user of DB2 10 for *
* z/OS *
****************************************************************
* PROBLEM DESCRIPTION: 00C90101 ABEND in DSNOGLOB:5008 *
* during REORG of LOB table space *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Depending on the LOB data distribution in the LOB table space,
broken linkage for multiple LOB map pages can occur when
inserting LOB data via the streaming method.
As a result, partial LOB data can be retrieved and result
in an abend, when the total length of the LOB data does not
match the actual retrieved LOB size.
DB2 code is changed to ensure that LOB map page linkage is
properly processed when inserting a piece of LOB data and the
current LOB map page is fully populated with prior LOB data.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI22446
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOFLMP PI22446
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22446 DSNOFLMP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOFLMP
LISTEND
UI22071 COVER LETTER END
UI22111 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22551 -
****************************************************************
* USERS AFFECTED: All DB2 V11 and DB2 V10 for z/OS users of *
* SQL DELETE with a self-referencing subquery *
* with PI10321/UI16426/UI16427 applied. *
****************************************************************
* PROBLEM DESCRIPTION: An infinite loop occurred at DSNIRSET *
* with PI10321/UI16426/UI16427 applied. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
With PI10321/UI16426/UI16427 applied, during an SQL DELETE with
a self-referencing subquery, when DB2 repositioned on a row in
the table, it reached the maximum number of low level locks
allowed and lock escalation occurred. Because an internal bit
was not set to indicate that locks had escalated, DB2 went into
an infinite loop in an attempt to obtain a lower level lock.
SQL example:
DELETE FROM D X
WHERE I1 = (SELECT I2 FROM D Y WHERE X.I1 = Y.I1)
DB2 code has been modified to set an internal flag when lock
escalation occurs.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22551
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRSET PI22551
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI22551 DSNIRSET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRSET
LISTEND
UI22111 COVER LETTER END
UI22175 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22417 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* complex SQL statements that contain *
* UNION ALL. *
* *
* All DB2 11 for z/OS users of global *
* variables. *
****************************************************************
* PROBLEM DESCRIPTION: This apar addresses two problems: *
* *
* 1. An infinite loop in DSNXODSO can *
* occur for a complex SQL statement *
* that contains UNION ALL. *
* *
* 2. An SQLCODE -433 may be issued *
* incorrectly when a value is *
* assigned to a global variable *
* because the length of the value *
* exceeds the defined length of the *
* global variable. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar addresses two problems:
1. An infinite loop in DSNXODSO can
occur for a complex SQL statement
that contains UNION ALL.
2. An SQLCODE -433 may be issued
incorrectly when a value is
assigned to a global variable
because the length of the value
exceeds the defined length of the
global variable.
The following is an example for problem (2).
CREATE VARIABLE GV VARCHAR(1);
SET GV = 'ABC';
1
In this case, the length of the global variable is 1 and the
length of the value being assigned to it is 3.
Instead of receiving an SQLCODE -433 (SQLCODE433), an
SQLCODE +445 (warning) should be issued.
DB2 was modified to remove the infinite loop conditions in
DSNXODSO when processing a complex SQL statement that contains a
UNION ALL clause.
Also, DB2 will now issue an SQLCODE +445 when a value (whose
length exceeds the defined length of the global variable) is
assigned to a global variable.
Additional Keywords: SQLUNIONALL SQLGLOBALVAR SQLCODE433
SQLCODE445 SQLINCORROUT INCORROUT SQLINCORR
DB2INCORR/K LOOP INFINITE ENDLESS SQLLOOP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22417
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM88698:
See PM88698 APAR/PTF text for additional information about
why a REBIND is necessary.
PM88698 corrects a problem that incorrect output could happen
for an SQL statement that contains special registers in GRPOUP
BY and a view or table expression with UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***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.
DB2BIND:
***Action for PI08206:
See PI08206 APAR/PTF text for additional information about
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODSO PI22417
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22417 DSNXODSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODSO
LISTEND
UI22175 COVER LETTER END
UI22212 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26334 -
****************************************************************
* USERS AFFECTED: All DB2 for zOS users with distributed *
* global transactions. *
****************************************************************
* PROBLEM DESCRIPTION: Threads can hang due to resources *
* held by a DDF server thread in a *
* global transaction, that is deadlocked *
* with another thread in the same global *
* transaction. A dump will show the *
* thread suspended in DSNRQXID when *
* called for ABORT processing during *
* DDF ABEND recovery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A thread in a global transaction can deadlock with another
1 thread in the global transaction when one of the threads
abends while processing an SQL request. Other threads in DB2
can then queue for resources held by threads in the global
transaction, which can result in extended latch waits, P-Lock
errors, and other errors associated with hung threads.
Following is a scenario that can result in the global
transaction deadlock situation.
T1 is a DDF server thread that owns the global transaction and
is in DB2 processing an SQL request.
T2 is a second DDF server thread in the global transaction,
and is waiting for T1 to release ownership of the GXID (global
transaction control block).
T1 receives an ABEND04E RC00E50013 due to a cancel resulting
from a connection error (or timeout) from the client.
T1 ABEND recovery releases GXID ownership before an ABORT is
issued that will release resources like page latches.
T2 obtains GXID ownership and begins processing an SQL request.
T2 then queues up for a DB2 latch, which is held by a thread
waiting for a resource (ie. page latch) owned by T1.
T1 ABEND recovery then percolates back to DDF recovery, which
will issue an ABORT.
T1 ABORT processing then suspends in DSNRQXID, waiting for T2
to release GXID ownership.
T1 is now waiting for T2, and T2 is waiting for T1, which
results in a deadlock.
ABEND recovery in DSNXERD (and DSNXERD2 in Version 11) has
been changed so that GXID ownership will not be released
when a DDF server thread in a global transaction abends until
after the ABORT is done, and resources are released.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26334
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXERD PI26334
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26334 DSNXERD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXERD
LISTEND
UI22212 COVER LETTER END
UI22227 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22930 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
1 * BIND/REBIND PACKAGE or REBIND TRIGGER *
* command. *
****************************************************************
* PROBLEM DESCRIPTION: A BIND or REBIND command can cause *
* ABEND0C4 RC00000004 in DSNGEPIS at any *
* of the following offsets: *
* *
* OFFSET25E8 *
* OFFSET2A2A *
* OFFSET2658 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A BIND or REBIND command can cause ABEND0C4 RC00000004 in
DSNGEPIS at the following offsets:
OFFSET25E8
OFFSET2A2A
OFFSET2658
The root cause is a storage overlay. DB2 tries to reference
freed storage.
Additional Keywords:
DB2OVRLAY/K SQLSTORAGE ABEND0C4 RC00000004 OFFSET25E8
OFFSET2A2A OFFSET2658
DB2 code has been changed to fix the storage overlay problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22930
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBCM PI22930
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22930 DSNTBCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBCM
LISTEND
UI22227 COVER LETTER END
UI22407 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24616 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* of SQL inline table user defined *
* function and outer joins. *
****************************************************************
1 * PROBLEM DESCRIPTION: Incorrect out may occur for an *
* SQL statement that satisfies all of *
* the following conditions: *
* 1. The SQL statement references to *
* an SQL inline table user defined *
* function. *
* 2. The SQL inline table user defined *
* function contains multiple outer *
* joins. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For Example,
CREATE TABLE A (C1 CHAR(20), C2 CHAR(20));
CREATE TABLE B (C1 CHAR(20), C2 CHAR(20));
CREATE TABLE C (C1 CHAR(20), C2 CHAR(20));
INSERT INTO A VALUES ('2','2');
INSERT INTO B VALUES ('2','2');
INSERT INTO C VALUES ('2','2');
CREATE FUNCTION UDF1 (SESSION_DK_ID CHAR(20))
RETURNS TABLE (DK_ID CHAR(20))
SPECIFIC UDF1
LANGUAGE SQL
READS SQL DATA
NO EXTERNAL ACTION
DETERMINISTIC
CARDINALITY 1000
RETURN
SELECT
A1.C1
FROM A AS A1 LEFT OUTER JOIN B ON A1.C1=B.C1
INNER JOIN A AS A2 ON A1.C1=A2.C1
WHERE A1.C2=SESSION_DK_ID;
SELECT * FROM TABLE (UDF1 ('2'))X;
The SQL statement above returns 0 row because DB2 did not handle
the SQL inline table user defined function and outer joins
correctly.
DB2 was fixed to handle the SQL inline table user defined
function and outer joins correctly.
Additional Key words: SQLINCORR SQLINCORROUT
INCORROUT DB2INCORR/K
SQLINLINE SQLTABLEUDF
SQLOUTERJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24616
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI24616:
See PI24616 APAR/PTF text for additional information about
why a REBIND is necessary.
1
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXORMQ PI24616
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24616 DSNXORMQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORMQ
LISTEND
UI22407 COVER LETTER END
UI22568 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24141 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C200A4 in DSNB5RDP or *
* DSNB5RAP. *
* *
* Various symptoms of broken data, *
* including: *
* - Incorrect output, INCORROUT. *
* - ABEND04E RC00C90101, RC00C90102, *
* RC00C90105, or RC00C902xx in *
* various CSECTs. *
* - Data/index inconsistencies reported *
* by the CHECK INDEX utility. *
* - Page regression reported by the *
* DSN1LOGP utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If an agent physically closing a page set or partition
encounters a Media Manager disconnect failure, and is canceled
while performing the close, the recovery routine may drive the
physical close code a second time, which will result in another
Media Manager disconnect request. Assuming that the original
failed disconnect freed the MMIB block, and further assuming
that a subsequent open was assigned the same MMIB address, this
second disconnect could result in a situation where a pageset
or partition has lost its MMIB but may still use it to issue
1 I/Os. Most likely these will fail. However, if the same MMIB
was reassigned yet again to a third pageset/partition, there
can now be two objects using the same MMIB. This can result
in I/O errors, or in misdirected I/Os leading to broken data.
The physical close logic handling a Media Manager disconnect
failue has been modified to ensure that the MMIB address is
cleared, to guarantee that it cannot be used for any further
disconnect request.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24141
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CST PI24141
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24141 DSNB1CST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CST
LISTEND
UI22568 COVER LETTER END
UI22611 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22460 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of MASS DELETE *
* against a table with self reference and *
* delete rule is CASCADE. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIMS1W *
* ERQUAL5002 during MASS DELETE execution *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During MASS DELETE execution against a table with self
reference, if there is page set level exclusive lock held and
the pageset lock is not selective one, DB2 will decide to use
row by row delete, but the foreign key for the self reference
will not be disconnected along with data record. If the table
delete rule is cascade, child records via the foreign key index
access failed to find record and the ABEND at DSNIMS1W happened.
Here are 2 possible scenario making non selective exclusive
pageset lock
1. LOCK TABLE IN EXCLUSIVE MODE
2. LOCKSIZE IS TABLESPACE OR TABLE
DB2 code has been modified to force disconnection from the
self reference foreign key during the slow mass delete against
1 table with self reference and delete rule is CASCADE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22460
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDIFS PI22460
DSNISDLE PI22460
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22460 DSNIDIFS DSNISDLE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDIFS
DSNISDLE
LISTEND
UI22611 COVER LETTER END
UI22642 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM95754 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Various short on storage related *
* abends may occur. *
* Symptoms may include: *
* o 04E-00E2000C,DSNLILNR.DSNSVSVB+0AC2 *
* o 04E-00E2000C,DSNLTACC.DSNSVSVB+0AC2 *
* o 04E-00E2000C,DSNLIRTR.DSNSVSVB+0AC2 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When remote client applications connect to a DB2 for z/OS (V10
or higher) server via TCP/IP, System Profile Monitoring (SPM)
support monitors events related to the different remote client
applications that access DB2, even if SPM is not enabled. The
storage acquired on behalf of monitoring these events (SPME
control blocks) can be reused when the storage no longer
reflects any active usage. However, the active usage is not
properly maintained in the following cases:
o The thread is a High Performance DBAT.
o The thread is associated with Keep Dynamic packages.
o The thread has serviced accelerated queries.
The erroneous active usage information prevents the storage
from being reused to monitor other events. This leads to an
accumulation of storage in the 'SPM SHARED ATB POOL' storage
pool. Over time, this accumulation can eventually lead to
various short on storage related abend symptoms such as
04E-00E2000C.
1
DB2 for z/OS server processing has been changed to correctly
reflect its SPM related storage usage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM95754
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLIRTR PM95754
DSNLQCTL PM95754
DSNLQDIS PM95754
DSNLTACT PM95754
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM95754 DSNLIRTR DSNLQCTL DSNLQDIS DSNLTACT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLIRTR
DSNLQCTL
DSNLQDIS
DSNLTACT
LISTEND
UI22642 COVER LETTER END
UI22644 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18834 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of queries with *
* a predicate resulting in no qualifying rows. *
****************************************************************
* PROBLEM DESCRIPTION: During prepare of an SQL statement, DB2 *
* probed the index to estimate the number *
* of qualifying keys. DB2 may produce a *
* higher filter factor when there are no *
* qualifying rows. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During prepare of an SQL statement, DB2 probed the index
to estimate the number of qualifying keys. DB2 may produce a
higher filter factor when there are no qualifying rows.
For example:
SELECT * FROM T1
WHERE C1 > 'A';
- T1.C1 has COLCARDF=1
- LOW2KEY and HIGH2KEY both have value 'A'.
- Table has only one row with value C1 = 'A'
1 DB2 may incorrectly overestimate the filter factor, which may
cause an inefficient access path or poor query performance.
Additional Keywords: SQLPERFORMANCE SQLACCESSPATH
INDEXPROBING SQLLT SQLGT
DB2 has been enhanced to provide more accurate filter factor
estimates when predicates involve less than (<) and/or
greater than (>) operators.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18834
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKCEST PI18834
DSNXOGBM PI18834
DSNXOPRP PI18834
DSNXOPRS PI18834
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18834 DSNKCEST DSNXOGBM DSNXOPRP DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKCEST
DSNXOGBM
DSNXOPRP
DSNXOPRS
LISTEND
UI22644 COVER LETTER END
UI22646 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25818 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) Users. *
* DB2 10 and DB2 11 for z/OS only. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 for z/OS, as a requester, abend *
* 04E-00E2000F DSNLXREL.DSNSVSFB+8EA *
* during abort processing which results *
* in DB2 abnormal termination with reason *
* 00D94001. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a DB2 for z/OS (as a requester) application package closed
a remote cursor, DB2 freed an internal control block without
clearing its associated anchor pointer.
A subsequent abend during close cursor processing caused the
DB2 thread to abort and terminate. However, the following
1 secondary abend may also occur during abort processing:
ABND=04E-00E2000F DSNLXREL.DSNSVSFB+8EA
This secondary abend during abort processing leads to a DB2
abnormal termination with reason 00D94001.
The secondary abend occurs when DB2 attempts to free
storage that has been previously freed.
DB2 for z/OS requester processing is changed to clear the
anchor pointer to its freed internal control block
to avoid DB2 abnormal termination.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25818
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXRCL PI25818
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25818 DSNLXRCL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXRCL
LISTEND
UI22646 COVER LETTER END
UI22682 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20473 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of LIKE predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may fail to properly set the search *
* range for a LIKE predicate when it is *
* matching on an index. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may fail to properly set the search range for a LIKE
predicate when it is matching on an index. This may result in
one or both of the following problems:
* DB2 may compute an inaccurate filter factor based on
the results of index probing at bind/prepare time for
a LIKE predicate under REOPT. This may lead to an
inefficient access path and poor performance.
* Explain may report matching index access for a LIKE
1 predicate with an ESCAPE clause even though no filtering
is applied at the index. The filtering is instead applied
as stage 2 potentially resulting in poor performance.
Additional Keywords:
SQLPERFORMANCE SQLACCESSPATH SQLLIKE
DB2 code has been corrected to properly handle LIKE predicates
for the problems described.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20473
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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.
DB2BIND:
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.
DB2BIND:
***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.
DB2BIND:
***Action for PM57955:
See PM57955 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57955 corrects a problem of ABEND04E RC00E70005 in DSNXORGL
P130 when query with range list access (ACCESSTYPE = 'NR' in
PLAN_TABLE) participated in parallel sort-merge join group.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI20948:
See PI20948 APAR/PTF text for additional information about
1 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.
DB2BIND:
***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
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for 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.
DB2BIND:
PI08414 corrects a problem of incorrect output returned when
SQL statements with range list access and fieldproc defined
on index key.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBM PI20473
DSNXOIXP PI20473
DSNXOLFQ PI20473
DSNXOPG1 PI20473
DSNXOPG2 PI20473
DSNXORGL PI20473
DSNXRTYP PI20473
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20473 DSNXOBM DSNXOIXP DSNXOLFQ DSNXOPG1 DSNXOPG2 DSNXORGL
DSNXRTYP
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBM
DSNXOIXP
DSNXOLFQ
DSNXOPG1
DSNXOPG2
DSNXORGL
DSNXRTYP
LISTEND
UI22682 COVER LETTER END
UI22684 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26227 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of partitioned tables *
* with a NULLable partitioning column. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may produce incorrect output for a *
* query with an IS NULL predicate on a *
* partitioning column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When evaluating page range screening, DB2 can incorrectly
eliminate a partition that can have qualifying rows. This
can lead to missing or no rows in the result. For this
problem to occur all of the following conditions must apply.
* The table is partitioned
* A partitioning column of the table is NULLable
* There exists an IS NULL predicate on the NULLable
column.
The problem is more likely to occur when the NULLable column
is first in the limit key and also when that column is a
DECIMAL, TIME, DATE, or TIMESTAMP datatype.
Additional Keywords:
SQLINCORROUT INCORROUT SQLINCORR DB2INCORR/K
SQLDATE SQLTIME SQLTIMESTAMP SQLNULL SQLISNULL
PAGERANGE
DB2 code has been modified to produce the correct output for
the described scenario. This problem is already fixed in
DB2 11.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26227
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPG2 PI26227
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26227 DSNXOPG2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPG2
LISTEND
UI22684 COVER LETTER END
UI22687 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17033 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2 *
* 11 for z/OS users of parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may occur when a query *
* meets all of the following criteria: *
* *
* 1. Parallelism is chosen in the *
* access path *
* *
* 2. The query contains a predicate *
* with an unknown literal value *
* during prepare time. Examples *
* include host variables, parameter *
* markers, special registers and UDF *
* parameters. *
* *
* 3. Matching index access is chosen in *
* the access path and the matching *
* column is referenced in the *
* predicate with the unknown literal *
* *
* 4. The matching column is defined as *
* NOT NULL *
1 * *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output may occur when a query meets all of the
following criteria:
1. Parallelism is chosen in the access path
2. The query contains a predicate with an unknown literal
value during prepare time. Examples include host variables,
parameter markers, special registers and UDF parameters.
3. Matching index access is chosen in the access path and the
matching column is referenced in the predicate with the
unknown literal.
4. The matching column is defined as NOT NULL
In this scenario, DB2 may incorrectly build the index key range
for the child tasks which may cause incorrect output.
Additional keywords:
PARALLELISM SQLPARALLELISM DB2PARALL/K SQLINCORR INCORROUT
SQLINCORROUT DB2INCORR/K SQLHOSTVAR PARAMETERMARKER SQLPMARKER
SQLPMK SQLSPECIALREG SQLUDF SQLNULL
DB2 code has been changed to properly build the index key ranges
for this scenario.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17033
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
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
1 letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEMG1 PI17033
DSNXOLDE PI17033
DSNXOLFQ PI17033
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17033 DSNXEMG1 DSNXOLDE DSNXOLFQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEMG1
DSNXOLDE
DSNXOLFQ
LISTEND
UI22687 COVER LETTER END
UI22695 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24668 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of UNLOAD DELIMITED of CHAR *
* column(s) to VARCHAR with STRIP *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 RC11 at DSNUULVA +x'4642' *
* during UNLOAD DELIMITED of a CHAR *
* column as a VARCHAR specifying STRIP *
* TRAILING *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
UNLOAD DELIMITED was run to unload CHAR columns as VARCHAR and
specifying STRIP TRAILING. One of the columns contained all
blanks. When UNLOAD stripped the trailing blanks, a length of 0
for the variable length data was left. UNLOAD then attempted to
move 255 bytes into the output buffer for that column data which
overflowed into unallocated storage. This resulted in the
ABEND0C4 RC4 at DSNUULVA OFFSET4642.
1 This error could also occur when specifying STRIP LEADING or
STRIP BOTH.
Additional Keyword: DB2OVRLAY/K
UNLOAD DELIMITED code has been changed to alleviate the
aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24668
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULVA PI24668
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24668 DSNUULVA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULVA
LISTEND
UI22695 COVER LETTER END
UI22699 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22916 -
****************************************************************
* USERS AFFECTED: Users of DB2 V10 and V11 for z/OS using *
* CURRENT DEGREE = ANY and the UNPACK *
* function. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output occurs on a SELECT *
* when using CURRENT DEGREE = ANY *
* and the UNPACK function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output occurs on a SELECT when using CURRENT DEGREE
= ANY and the UNPACK function.
DB2 has been fixed to handle the case where the UNPACK function
and parallelism are used.
Additional Keywords: SQLSELECT SQLPARALLELISM SQLINCORR
SQLINCORROUT SQLUNPACK CURRENTDEGREE
UNPACK
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22916
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
1 ***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSCF PI22916
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22916 DSNXOSCF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSCF
LISTEND
UI22699 COVER LETTER END
UI22717 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15740 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS *
* who have queries eligible for range list *
* access *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output (duplicate rows *
* returned) can occur for a query *
* using range list access when the *
* query contains multiple range *
* predicates on the same column *
* in the same direction. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output can occur for a query using range list access
when there are multiple range predicates on the same
column in the same direction. For example:
SELECT C9
FROM T1
WHERE
C1 = 12345 AND
C3 >= ' ' AND
(
(C2 = 20952 AND
C3 = ' ' AND
1 C4 >= '0001-01-01')
OR
(C2 = 20952 AND
C3 > ' ')
OR
(C2 >= 20952 AND <=== multiple range predicates on C2
C2 <= 20999 AND
C2 > 20952 ) <=== in the same direction
);
An index exists on (C1, C2, C3, C4) which can provide
range list access.
Additional Keywords:
SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K RANGELIST
SQLLT SQLGT SQLLE SQLGE
Code is changed to ensure that ranges are built correctly for
the situation described above so that the correct output is
returned.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15740
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI15740:
A rebind is necessary for static applications to rebuild
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGBM PI15740
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15740 DSNXOGBM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBM
LISTEND
UI22717 COVER LETTER END
UI22737 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI26964 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Delays in page P-lock negotiation, of *
* up to 4 minutes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For the case where a page P-lock negotiation downgrades the lock
to S mode, there are situations where the subsequent release of
the page by the P-lock exit will drive an unlock. This can
happen if the buffer pool is being contracted, or if there is a
"must complete" process waiting for a buffer, or if DB2 was
started with the "LIGHT" option. An unlock cannot proceed if
the P-lock exit is active, so when the unlock is requested by
the P-lock exit itself, it will hang until IRLM marks the exit
"canceled" after 4 minutes.
The page P-lock exit logic has been modified to always negotiate
by releasing the lock, rather than downgrading from X to S when
the other member requested the lock in S.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26964
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PPG PI26964
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26964 DSNB1PPG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PPG
LISTEND
UI22737 COVER LETTER END
UI22764 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21897 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* using aggregate functions and a HAVING *
* clause *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may be returned for a *
* query containing a HAVING clause and *
* no GROUP BY clause with an aggregate *
* function such as COUNT evaluated *
* against the empty set. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
DB2 incorrectly returns no rows for a query with the following
criteria. It should return one row.
1. The query contains an aggregate function such as COUNT
2. There is no GROUP BY clause
3. There is a HAVING clause or a WHERE clause transformed
to a HAVING
4. The intermediate result table of the HAVING is the
empty set.
The following query returns incorrect output. The query
returns no rows. The expected output is one row with the
value 0.
SELECT COUNT(*)
FROM T2
WHERE 1=0
HAVING COUNT(*)>=0;
DB2 has been modified to process the aggregate functions
against the empty set.
Additional keywords : SQLHAVING SQLCOUNT SQLMAX SQLMIN
SQLSUM SQLAVG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21897
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRGBJ PI21897
DSNXRGB9 PI21897
DSNXRSGB PI21897
DSNXRSG9 PI21897
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21897 DSNXRGBJ DSNXRGB9 DSNXRSGB DSNXRSG9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRGBJ
DSNXRGB9
DSNXRSGB
DSNXRSG9
LISTEND
UI22764 COVER LETTER END
UI22773 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI22465 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a query *
* with a LIKE predicate containing mixed data *
* columns. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result can be returned *
* from a query which includes a LIKE *
* predicate for a character column that *
* contains mixed data. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result (more rows than expected) can be returned
from a query that contains a LIKE predicate for a character
column that references mixed data. The problem occurs because
DB2 doesn't reset an internal variable for mixed data properly
for residual like predicate evaluation.
The following example illustrates how this problem can occur.
1. DECP should have MIXED set to YES.
2. Create Table and insert mixed data.
CREATE TABLE USER1.TB1
(
COL1 VARCHAR(200) NOT NULL
,COL2 CHAR(4) NOT NULL
,PRIMARY KEY (COL1, COL2)
) ;
INSERT INTO USER1.TB1 ( COL1, COL2 )
VALUES .......
3. Run the following query.
SELECT DISTINCT HEX(A.COL1) AS HEX
FROM USER1.TB1 AS A
INNER JOIN USER1.TB2 AS B ON
A.COL2 = B.COL2
WHERE A.COL1 LIKE '%a%'
OR B.COL2 = 'W'
This query returns 1 row when it should not.
However, DB2 should not return any records. The reason why DB2
returns 1 record is because the residual like predicate
evaluation for mixed data is not processed properly, so between
the shift in '0E'X and shift out '0F'X bytes, a single HEX byte
can be regarded as a single byte for the current CCSID. This
can cause a mis-matched comparison, which can produce an
unexpected result.
DB2 has been modified to handle the like predicate for mixed
1 data correctly.
Additional keywords : SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K SQLLIKE MIXED
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22465
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGVCM PI22465
DSNXRRP PI22465
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22465 DSNXGVCM DSNXRRP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGVCM
DSNXRRP
LISTEND
UI22773 COVER LETTER END
UI22950 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26285 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS user's of *
* queries that include a where predicate *
* with an indexable IN-List (containing *
* many NULL entries/elements). *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result of more rows than *
* expected can be returned from a query *
* that includes a where predicate with an *
* indexable IN-List (containing many null *
* entries/elements) if it is transformed *
* to use IN-List table access. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An incorrect result (more rows than expected) can be returned
from a query that includes a where predicate with an indexable
IN-List (containing many NULL elements) if it is transformed to
an "IN-List table". The PLAN_TABLE shows ACCESSTYPE = 'IN'.
PLEASE NOTE: The TOP_ID column used to reference the IN-List in
the following example is not NULL and is necessary for this
problem.
The following dynamic SQL, fashioned from the reported case,
presents such a failing case.
Given the following TABLE and chosen INDEX definition.
STEP 1. Create a table T1 and index IDX1.
CREATE TABLE ABC.T1
(PEZ_ID TIMESTAMP (6) WITHOUT TIME ZONE NOT NULL,
PFD_ZP TIMESTAMP (6) WITHOUT TIME ZONE NOT NULL
WITH DEFAULT '9999-12-31-00.00.00.000000',
BEG_DAT DATE NOT NULL,
END_DAT DATE NOT NULL WITH DEFAULT '9999-12-31',
ERS_ZP TIMESTAMP (6) WITHOUT TIME ZONE NOT NULL
WITH DEFAULT,
DAT_ID CHAR(1) FOR SBCS DATA NOT NULL
WITH DEFAULT 'J',
PRODUCT_ID TIMESTAMP (6) WITHOUT TIME ZONE NOT NULL,
TOP_ID CHAR(10) NOT NULL,
CONSTRAINT PEZ_ID
PRIMARY KEY (PEZ_ID,
PFD_ZP,
BEG_DAT))
....
CREATE INDEX IDX1
ON ABC.T1
(TOP_ID ASC,
PFD_ZP DESC,
BEG_DAT DESC)
....
STEP 2. Insert a row of data into the table.
INSERT INTO ABC.T1 VALUES
('1999-10-31-00.00.00.000000','1991-10-31-00.00.00.000000',
'2014-10-01','2014-10-31','2014-12-31-00.00.00.000000','J',
'2000-12-31-00.00.00.000000',x'00000000000000000000');
STEP 3. Execute the following dynamic SQL.
Execute the following dynamic SQL with 24 parameter markers,
4 which are outside the IN-List, and 20 inside the IN-List.
1
Assign and set values for the parameter markers, i.e. host
variable and indicator variable assignments.
HV1: '1990-10-31-00.00.00.000000', I1=0
HV2: '2014-12-31-00.00.00.000000', I2=0
HV3: '2014-12-31', I3=0
HV4: '2012-12-31', I4=0
IN-List HV's.
HV5: '', I5=-1 ... HV24: '', I24=-1
SELECT DISTINCT T1.PEZ_ID,
HEX(T1.TOP_ID),
T1.BEG_DAT, T1.END_DAT,
T1.ERS_ZP, T1.PFD_ZP,
T1.DAT_ID, T1.PRODUCT_ID
FROM ABC.T1 AS T1
WHERE ((T1.PFD_ZP > ?
AND T1.ERS_ZP <= ? )
AND (T1.BEG_DAT <= ?
AND T1.END_DAT >= ? )
AND T1.DAT_ID = 'J')
AND T1.TOP_ID IN (?,?,?,?,?,?,?,?,?,?,
?,?,?,?,?,?,?,?,?,?) ORDER BY 1;
STEP 4. Check the results.
A single row is returned but no rows are expected to be
returned. So, "more rows than expected" are returned.
Please Note:
In some applications, if the query/cursor is executed multiple
times but with different host variable assignments, the first
iteration can accidentally work whereas the second iteration may
produce an unexpected result as in the reported case. So, the
problem is dependent on the access path chosen and also could
depend on residual values in memory from the first execution.
The code in DB2 (bindtime) has been modified to correct the
logic for processing parameter markers with negative indicators
for IN-List table access to prevent incorrect results from being
returned during execution.
Additional Keywords: SQLINCORROUT INCORROUT SQLINCORR
DB2INCORR/K SQLINLIST
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26285
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI26285:
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRM1 PI26285
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26285 DSNXGRM1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGRM1
LISTEND
UI22950 COVER LETTER END
UI23100 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20371 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of XML *
****************************************************************
* PROBLEM DESCRIPTION: This APAR addresses the following *
* problems that may occur when accessing *
* XML data *
* 1. Concurrency issue because base page *
* latch was held while acquiring *
* unconditional IS lock against XML table *
* , XML table space or partition of XML *
* table space *
* 2. Reader with isolation level UR might *
* skip committed record *
* *
* Additional keyword: DB2INCORR/K, XML *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When issuing an IS lock on an XML table, XML table space or
partition of XML table space, DB2 didn't release the latch on
the base data page. Since the locking request was unconditional,
the latch could be held for as long as the locking request was
suspended waiting for a lock. Other concurrent agents requesting
access to the base page might be blocked.
1 ISO(UR) reader accessing XML data might erroneously skip
committed rows if the base data page was changed after XML
locking was done.
DB2 code has been modified as follows:
1. DB2 no longer holds a latch while requesting an
unconditional lock on an XML table, XML table space or
partition of an XML table space.
2. For an ISO(UR) reader, if the base page changes when locking
the XML table space, DB2 will recheck the base record to
determine if it still qualifies rather than skipping the
record.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20371
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIACCH PI20371
DSNIADR PI20371
DSNILRBK PI20371
DSNIONXP PI20371
DSNIONX2 PI20371
DSNIOST2 PI20371
DSNIRNXT PI20371
DSNIRPRE PI20371
DSNIRPRV PI20371
DSNIRSET PI20371
DSNISRID PI20371
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20371 DSNIACCH DSNIADR DSNILRBK DSNIONXP DSNIONX2 DSNIOST2
DSNIRNXT DSNIRPRE DSNIRPRV DSNIRSET DSNISRID
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNIADR
DSNILRBK
DSNIONXP
DSNIONX2
DSNIOST2
DSNIRNXT
DSNIRPRE
DSNIRPRV
DSNIRSET
DSNISRID
LISTEND
UI23100 COVER LETTER END
UI23122 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23445 -
1 ****************************************************************
* USERS AFFECTED: All DB2 10 or 11 for z/OS users of *
* view with multiple UNION/UNION ALL *
* with PI15409 applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC0000003B may occur for *
* query references a view that *
* contains multiple UNION/UNION ALL *
* with PI15409 / UI18603 (DB2 10) / *
* UI18604 (DB2 11). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For example,
1. Create a view
CREATE VIEW V1 AS
SELECT * FROM T1
UNION
SELECT * FROM T2
....
SELECT * FROM T129;
2. Reference a view
SELECT * FROM V1;
The abend occurs because the DB2 internal data structure that
is used to hold the query blocks exceeds the maximum limit.
This problem is exposed with PI15409.
DB2 was updated to increase the size of the DB2 internal data
structure which is used to hold the query blocks.
Additional KeyWords: SQLUNION SQLUNIONALL SQLVIEW
DB2OVRLAY/K SMCOVERLAY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23445
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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
1 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.
DB2BIND:
***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.
ACTION:
***Action for PM98848:
See PM98848 APAR/PTF text for additional information about
why a REBIND is necessary.
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
1 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.
ACTION:
***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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOACA PI23445
DSNXOB1 PI23445
DSNXOFN3 PI23445
DSNXOLV PI23445
DSNXOMTX PI23445
DSNXOONY PI23445
DSNXOTL PI23445
DSNXOVC PI23445
DSNXOVM PI23445
DSNXOV0 PI23445
DSNXOV1 PI23445
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23445 DSNXOACA DSNXOB1 DSNXOFN3 DSNXOLV DSNXOMTX DSNXOONY
DSNXOTL DSNXOVC DSNXOVM DSNXOV0 DSNXOV1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOACA
DSNXOB1
DSNXOFN3
DSNXOLV
DSNXOMTX
DSNXOONY
DSNXOTL
DSNXOVC
DSNXOVM
DSNXOV0
DSNXOV1
LISTEND
UI23122 COVER LETTER END
UI23127 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22948 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS user of *
* pureXML *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 DSNNQOPM OFFSET248F6 , *
1 * OFFSET24902 , OFFSET2490E , OFFSET24914 *
* or DSNNQOPS OFFSETFC40 , OFFSETFC4C , *
* OFFSETFC58 , OFFSETFC5E , OFFSETFC68 or *
* DSNNOSER OFFSETF9DE , OFFSETF9EA , *
* OFFSETF9F6 , OFFSETF9FC , OFFSETFA06 or *
* DSNNQOPN OFFSET11F20 , OFFSET11F2C , *
* OFFSET11F38 , OFFSET11F3E , OFFSET11F48 *
* or DSNNORCN OFFSET1E908 , OFFSET1E914 , *
* OFFSET1E920 , OFFSET1E926 , OFFSET1E930 *
* or DSNXQXQ2 OFFSET462C , OFFSETEB2C or *
* DSNXQXQ2 M909 or DSNNQSCN OFFSET6DDC or *
* DSNNQMD OFFSET4C34 can occur during the *
* bind or processing of the XMLQUERY, *
* XMLEXISTS, XMLTABLE or XMLMODIFY *
* functions. *
* *
* Also xmlns="" might not (while it
*
* should) be added when using XMLMODIFY *
* to update an XML document in the case *
* when the target node has default *
* namespace declared and the source node *
* doesn't. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An invalid use of zero pointers to reference storage can result
in the ABEND0C4.
When using insert expression or replace expression of the
XMLMODIFY function to insert a new node or replace a node in an
XML document with a new node, if the target node has the default
namespace declared and the source node (i.e., new node) doesn't,
xmlns="" should be added to the source node during insert or
replace. But in some error case, xmlns="" is not added while
it
should be.
DB2 is modified to correct the usage of the pointers to
eliminate the occurrence of ABEND0C4 and xmlns="" will be
added
for the above mentioned XMLMODIFY cases.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22948
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
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.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOAPU PI22948
DSNNOBSC PI22948
DSNNOBSE PI22948
DSNNOCCN PI22948
DSNNOGIK PI22948
DSNNORCN PI22948
DSNNOSCO PI22948
DSNNOSER PI22948
DSNNOUPD PI22948
DSNNQDTM PI22948
DSNNQFLR PI22948
DSNNQFL2 PI22948
DSNNQIV PI22948
DSNNQMD PI22948
DSNNQOB PI22948
DSNNQOPM PI22948
DSNNQOPN PI22948
DSNNQOPR PI22948
DSNNQOPS PI22948
DSNNQRES PI22948
DSNNQSCN PI22948
DSNNQTOP PI22948
DSNNQXCA PI22948
DSNXQXQ2 PI22948
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22948 DSNNOAPU DSNNOBSC DSNNOBSE DSNNOCCN DSNNOGIK DSNNORCN
DSNNOSCO DSNNOSER DSNNOUPD DSNNQDTM DSNNQFLR DSNNQFL2
DSNNQIV DSNNQMD DSNNQOB DSNNQOPM DSNNQOPN DSNNQOPR
DSNNQOPS DSNNQRES DSNNQSCN DSNNQTOP DSNNQXCA DSNXQXQ2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOAPU
DSNNOBSC
DSNNOBSE
DSNNOCCN
DSNNOGIK
DSNNORCN
DSNNOSCO
DSNNOSER
DSNNOUPD
DSNNQDTM
DSNNQFLR
DSNNQFL2
DSNNQIV
DSNNQMD
DSNNQOB
DSNNQOPM
DSNNQOPN
DSNNQOPR
DSNNQOPS
DSNNQRES
DSNNQSCN
1 DSNNQTOP
DSNNQXCA
DSNXQXQ2
LISTEND
UI23127 COVER LETTER END
UI23147 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22421 -
****************************************************************
* USERS AFFECTED: All users of DSNTIAUL in DB2 Version 9 and *
* DB2 Version 10 for z/OS who have PM86927 *
* applied (UI18016 for V9,UI18014 for V10) *
* are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: After applying UI18016 and UI18014, *
* DB2 9 and 10 customers who run on *
* z/OS 1.12 or older cannot assemble *
* DSNTIAUL. It is terminated with *
* return code 8 and the message: *
* ASMA034E *** ERROR *** *
* Addressability error *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSNTIAUL is a sample dynamic SQL processing application that is
used primarily to unload data from DB2 tables to an externalized
format. DSNTIAUL also generates a LOAD control statement that
can be used in conjunction with the DB2 LOAD utility to load the
externalized data back into DB2.
A recent APAR, PM86927, modified DSNTIAUL to specify 'XML'
rather than 'CLOB' in the field specification for each XML
column in the generated LOAD control statement when the
DSNTIAUL LOBFILE option is not specified. In z/OS 1.12 and
previous releases, certain system macros can cause assembly
to fail with msgASMA034E.
In response, this APAR removes the PM86927 modications to
DSNTIAUL in DB2 9 and 10 to avoid disrupting customers who
use z/OS 1.12 and older releases.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22421
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
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
1 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.
DB2BIND:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIAUL PI22421
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22421 DSNTIAUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIAUL
LISTEND
UI23147 COVER LETTER END
UI23171 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26218 -
****************************************************************
* USERS AFFECTED: All users that need to fix or add the *
* catalog rows updated by APARs PM88612 *
* or PI08928 and have views on tables in *
* the Directory database DSNDB01. *
* *
* or *
1 * *
* All users that have views on tables in *
* the Directory database DSNDB01 and are *
* going to go through ENFM for DB2 for *
* z/OS V11. *
****************************************************************
* PROBLEM DESCRIPTION: A view was created on SYSIBM.SYSUTIL. *
* The job *
* CATMAINT UPDATE UNLDDN PI08928 *
* was run to correct rows in the catalog. *
* After the job was run a SQLCODE204 was *
* received when an attempt was made to *
* drop the view. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
APARS PM88612 and PI08928 fixed and added rows in the catalog
to represent tables in the DIRECTORY database DSNDB01. The
changes where made by running the jobs
CATMAINT UPDATE UNLDDN PM88612
or
CATMAINT UPDATE UNLDDN PI08928
If a view was created on a table in DSNDB01 before one of
these jobs was run, the job would remove the row for the
view from SYSIBM.SYSTABLES but it would not remove the row
for the view from SYSIBM.SYSVIEWS or SYSIBM.SYSVIEWDEP.
This would cause an SQLCODE204 if you try to drop the view
or an SQLCODE601 when you tried to create the view. This
problem can also occur when you go through ENFM for DB2
for z/OS V11.
This APAR corrects the problem where views exist on tables
in DSNDB01 when a CATMAINT job is run to correct catalog
rows. It also makes the corrections fixed by APARS
PM88612 and PI08928. A new job is provided to make the
corrections and preserve the views:
CATMAINT UPDATE UNLDDN PI26218
This CATMAINT supersedes the previous CATMAINT update
jobs from APARS PM88612 and PI08928.
The code has also been updated to leave the views on tables in
DSNDB01 intact when DSNTIJEN is run on DB2 V11.
This job can only be run on DB2 V10 NFM or DB2 V11 CM.
Applying this APAR does not correct views on tables in DSNDB01
that were broken before the APAR was applied. The orphaned
views can exist in any mode. The following query can be used to
identify views that are broken.
SELECT
1 V.CREATOR AS VCREATOR,
V.NAME AS VNAME,
V.SEQNO AS VSEQNO,
V.TYPE AS VTYPE
FROM SYSIBM.SYSVIEWS V
WHERE V.TYPE = 'V'
AND NOT EXISTS
( SELECT * FROM SYSIBM.SYSTABLES T
WHERE T.CREATOR = V.CREATOR
AND T.NAME = V.NAME);
If this query returns rows, you have one or more broken views.
Please contact IBM support for help.
++HOLD for V10
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:
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,
1 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.
++HOLD for V11
This APAR corrects the problem fixed by APAR
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.
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 and 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 is only needed in V11 CM
because the rows are automatically corrected when the
system goes through ENFM.
KEYWORDS: DB2MIGV11/K DB2MIGV10/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26218
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
1 job listed below can be used to add the correct rows if needed.
Problem 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUECM0 PI26218
DSNUECSE PI26218
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26218 DSNUECM0 DSNUECSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECM0
DSNUECSE
1
LISTEND
UI23171 COVER LETTER END
UI23321 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21358 -
****************************************************************
* USERS AFFECTED: Data Capture applications using IFCID 306 *
* to read compressed log data in DB2 for *
* z/OS V10 and V11. *
****************************************************************
* PROBLEM DESCRIPTION: IFI 306 log read failed with *
* reason code 00C90064. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In data sharing environment, insert from one DB2 member,
say DB2A, into a compressed table space can trigger dictionary-
building for the pageset or partition during the insert, and
then subsequent rows inserted into the same pageset or partition
and the associated log records will get compressed. If an
IFI 306 reader runs from another DB2 member, say DB2B, using
the same pageset or partition at the same time, there is a
timing window during which the IFI 306 reader on DB2B may see
the newly compressed log records before the dictionary is
loaded in DB2B's buffer. In this case the IFI 306 will fail
with reason = 00C90064.
DB2 code has been modified to load the dictionary from DASD if
the IFI 306 log reader encounters compressed log records
when the dictionary has not been loaded yet.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21358
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDCML PI21358
DSNIZLDR PI21358
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21358 DSNIDCML DSNIZLDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDCML
DSNIZLDR
LISTEND
UI23321 COVER LETTER END
UI23340 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI26457 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE. *
****************************************************************
* PROBLEM DESCRIPTION: Storage overlays can occur during or *
* after a REORG TABLESPACE that converts *
* records from basic row format (BRF) to *
* reordered row format (RRF) *
* The storage overlays can cause DB2 to *
* crash. *
* The following dumps may be issued *
* before DB2 crashes: *
* - ABEND0C4 RC00000038, RC00000010, *
* RC00000004, RC00000011 in various *
* CSECTS. *
* - ABEND04E RC00E4D5D2 DSNUULVA *
* OFFSET406C *
* - ABEND04E RC00E2000E DSNSVSFB *
* OFFSET08C6 *
* - ABEND04E RC00E20992 DSNSVSFB *
* OFFSET0EA8 *
* - ABEND04E RC00E2000D DSNSVSFB *
* OFFSET08DA *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Given the following conditions:
- table space contains BRF records
- an ALTER TABLE ADD COLUMN was done before DB2 V6
- the table space was never reorged after the ALTER TABLE
ADD COLUMN
REORG on that table space didn't reset the record length
after converting BRF records to RRF, which resulted in a large
storage overlay and caused DB2 to crash.
DB2 code has been modified to reset record length after
converting BRF records to RRF.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26457
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIMOFR PI26457
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26457 DSNIMOFR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIMOFR
LISTEND
1UI23340 COVER LETTER END
UI23388 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24399 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER utility which uses a *
* system level backup (SLB) as a recovery *
* base. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 DSNUGSTA, ABEND04E RC00C90101 *
* DSNIDBSE, other unpredictable symptoms *
* resulting from storage overlay during *
* RECOVER utility from an SLB. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In the following specific scenario, a storage overlay can
occur, which can lead to a variety of abends and other
unpredictable symptoms, including in some cases an abend
of the DB2 subsystem.
Scenario:
1. BACKUP SYSTEM utility to make a system level backup (SLB)
to be used as a base for recovery of individual objects.
2. LOAD REPLACE LOG YES or REORG LOG YES utility at the
partition level of every part of a partitioned object.
3. RECOVER DSNUM ALL utility on the partitioned object.
Although such an overlay can result in various symptoms,
some of the ones observed include:
ABEND04E RC00C90101 DSNIDBSE:5006 ERQUAL5006
ABEND04E RC00E20005 DSNSVBK +1AB6 OFFSET1AB6
ABENDS0C4 RC38 DSNUGSTA +1FF8 OFFSET1FF8
.
Additional keywords: DB2OVRLAY/K
Code was changed in RECOVER utility to avoid storage overlays
in the aforementioned scenario.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24399
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCBMT PI24399
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24399 DSNUCBMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBMT
LISTEND
1UI23388 COVER LETTER END
UI23410 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25748 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of DROP *
* PRIMARY KEY and ADD COLUMN clauses in the *
* same ALTER TABLE statement. *
****************************************************************
* PROBLEM DESCRIPTION: After a DROP PRIMARY KEY and ADD *
* COLUMN clauses in the same ALTER *
* TABLE statement is executed, *
* 1. an ABEND04E RC00C90101 at DSNGDVIX *
* :5006 may occur when a subsequent *
* CREATE INDEX references the newly *
* added column, *
* 2. or an ABEND04E RC00C90101 at *
* DSNIZMOV :500C may occur when a *
* subsequent SELECT statement *
* references the newly added column. *
* 3. or errors may occur when executing *
* a REPAIR DBD DIAGNOSE DATABASE *
* against the database name of the *
* ALTERed table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After an DROP PRIMARY KEY and ADD COLUMN clauses in the same
ALTER TABLE statement is executed,
1. an ABEND04E RC00C90101 at DSNGDVIX :5006 may occur when
subsequent CREATE INDEX references the newly added column,
2. or an ABEND04E RC00C90101 at DSNIZMOV :500C may occur when
subsquent a SELECT statement references the newly added
column.
3. or errors may occur when executing a REPAIR DBD DIAGNOSE
DATABASE against the database name of the ALTERed table.
Following are the sample error messages:
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000072'
OBDRCCSID_OFFSET
DSNU904I DSNUEDRT - EXISTING VALUE X'00EC'
DSNU905I DSNUEDRT - REBUILT VALUE X'00FC'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000004'
OBDRELTH
DSNU904I DSNUEDRT - EXISTING VALUE X'00000338'
DSNU905I DSNUEDRT - REBUILT VALUE X'00000348'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'0000000C'
OBDREXTO - INFORMATION NOT IN DB2
CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'000000FC'
DSNU905I DSNUEDRT - REBUILT VALUE X'0000010C'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000018'
obdrFixedLen
DSNU904I DSNUEDRT - EXISTING VALUE X'0027'
DSNU905I DSNUEDRT - REBUILT VALUE X'0029'
1 DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'0000001A'
obdrFixedLenAndO
DSNU904I DSNUEDRT - EXISTING VALUE X'0027'
DSNU905I DSNUEDRT - REBUILT VALUE X'0029'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000040'
OBDREMAL
DSNU904I DSNUEDRT - EXISTING VALUE X'0027'
DSNU905I DSNUEDRT - REBUILT VALUE X'0029'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'0000006F'
OBDREMRK - INFORMATION NOT IN DB2
CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'D3'
DSNU905I DSNUEDRT - REBUILT VALUE X'00'
DSNU906I DSNUEDRT - EXISTING VALUE 'L'
DSNU907I DSNUEDRT - REBUILT VALUE '.'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000074'
OBDRENFD
DSNU904I DSNUEDRT - EXISTING VALUE X'0006'
DSNU905I DSNUEDRT - REBUILT VALUE X'0007'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000D8'
OBDRELST(6)
DSNU904I DSNUEDRT - EXISTING VALUE X'02'
DSNU905I DSNUEDRT - REBUILT VALUE X'00'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000EA'
OBDRELST(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'00'
DSNU905I DSNUEDRT - REBUILT VALUE X'02'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000EB'
OBDRFTYP(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'00010000'
DSNU905I DSNUEDRT - REBUILT VALUE X'02404000'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000EC'
OBDRSYSD(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'01'
DSNU905I DSNUEDRT - REBUILT VALUE X'40'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000EC'
OBDRUDefault(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'01000000'
DSNU905I DSNUEDRT - REBUILT VALUE X'40400000'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000ED'
OBDRDBCS(7) - INFORMATION NOT IN
DB2 CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'0000'
DSNU905I DSNUEDRT - REBUILT VALUE X'4000'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F1'
OBDREXNID(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'25'
DSNU905I DSNUEDRT - REBUILT VALUE X'00'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F0'
OBDRCCSIDI(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'00'
DSNU905I DSNUEDRT - REBUILT VALUE X'01'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F2'
OBDREFLL(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'0000'
DSNU905I DSNUEDRT - REBUILT VALUE X'0002'
1 DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F4'
OBDREFOF(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'0000'
DSNU905I DSNUEDRT - REBUILT VALUE X'0027'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F6'
OBDREUFN(7) - INFORMATION NOT IN
DB2 CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'4040'
DSNU905I DSNUEDRT - REBUILT VALUE X'0000'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000F8'
OBDREFOF2(7) - INFORMATION NOT IN
DB2 CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'4000'
DSNU905I DSNUEDRT - REBUILT VALUE X'0027'
DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'000000FA'
OBDREFLL2(7)
DSNU904I DSNUEDRT - EXISTING VALUE X'0000'
DSNU905I DSNUEDRT - REBUILT VALUE X'0002'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000114'
OBDRXMAX - INFORMATION NOT IN DB2
CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'7E23'
DSNU905I DSNUEDRT - REBUILT VALUE X'0031'
DSNU916I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000118'
OBDRXMIN - INFORMATION NOT IN DB2
CATALOG
DSNU904I DSNUEDRT - EXISTING VALUE X'0000'
DSNU905I DSNUEDRT - REBUILT VALUE X'0031'
DSNU938I DSNUEDDR - OBD X'0003' HAD DIFFERENCES WHICH
WERE NOT IN A NAMED FIELD
00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000
*................................*
******** LINES FROM 00000020 TO 00000120 ARE THE SAME AS
THE ABOVE LINE
00000120 00000000 7E230000 00000090 00000000 00000000
00000000 00000000 00000000
*....=...........................*
00000140 00000000 00000000 00500001 00000000 00000000
00000000 00000000 22AB0040
*.........&..................... *
00000160 D6C2E7F2 00000000 00000000 00000000 00000000
00500000 00000000 00000000
*OBX2.................&..........*
00000180 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000
*................................*
******** LINES FROM 000001A0 TO 00000320 ARE THE SAME AS
THE ABOVE LINE
00000320 00000000 00000000 00000000 00000000 00000000
00000000
*........................ *
DSNU913I DSNUEDDR - OBD X'0003' COMPARISON COMPLETE --
17 ERRORS WERE FOUND
1
There may be other unexpected symptoms.
When DB2 processes the DROP PRIMARY KEY clause, DB2 processes
the ADD COLUMN clause incompletely.
Following is an example of such failing scenario:
1. Create the testing table:
CREATE TABLE MYT1
(C1 CHAR(5) NOT NULL,
C2 CHAR(10) NOT NULL,
C3 INT NOT NULL,
C4 INT NOT NULL,
C5 CHAR(8) NOT NULL,
C6 CHAR(8) NOT NULL,
PRIMARY KEY (C1, C3)
) ;
2. Create index for the primary key:
CREATE UNIQUE INDEX MYIDX01 ON MYT1
(C1, C3);
3. ALTER TABLE DROP PRIMARY KEY and ADD COLUMN:
ALTER TABLE MYT1
DROP PRIMARY KEY
ADD C101 CHAR(2) NOT NULL WITH DEFAULT ;
4, Create index refers to the new column, an ABEND04E RC00C90101
at DSNGDVIX :5006 may occur:
CREATE INDEX MYIDX03 ON MYT1
(C1, C3, C101) ;
5. or SELECT the just added column, an abend ABEND04E RC00C90101
at DSNIZMOV :500C may occur
SELECT C101
FROM MYT1 ;
6. or executing a REPAIR DBD DIAGNOSE DATABASE job on the
database name of the ALTERed table, errors may be reported.
Applying this APAR PI25748 will not fix tables for which added
column were not correctly processed.
In order to fix the problem, after applies APAR PI25748,
customer needs to
1. execute REPAIR DBD REBUILD DATABASE on the affected database
if no new data is inserted to the ALTERed table
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 subsequent
queries could return incorrect output.
DB2 has been modified to process ADD COLUMN correctly when
specified in the same ALTER TABLE statement as DROP PRIMARY
KEY.
1 Additional Keywords: ABEND04E RC00C90101
SQLALTER SQLCREATE
SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25748
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIAB1 PI25748
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25748 DSNXIAB1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIAB1
LISTEND
UI23410 COVER LETTER END
UI23435 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27527 -
****************************************************************
* USERS AFFECTED: DB2 9, 10 and 11 for z/OS users of ALTER *
* TABLE ROTATE PARTITION statement. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output via index scan against *
* the table in a partitioned table space *
* after ALTER TABLE ROTATE PARTITION *
* statement execution. *
* *
* *
* Additional keywords: *
* *
1 * DB2INCORR/K, SQLINCORR, SQLINCORROUT, *
* INCORROUT, NO ROWS FOUND (NRF) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ALTER TABLE ROTATE PARTITION statement might only pseudo delete
index entries on coresponding partition of a Partitioning Index
(PI).
If a query came in, for which DB2 chose index access via the PI,
pseudo deleted index entries in the partition might cause
incorrect output of no qualified records though there are.
For an ALTER TABLE ROTATE PARTITION statement, DB2 code has been
modified to physically delete index entries in the paritioning
index.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27527
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISDLE PI27527
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27527 DSNISDLE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISDLE
LISTEND
UI23435 COVER LETTER END
UI23461 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23366 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS users with *
* PM74477 / UK91616, and DB2 10 and DB2 11 for *
* z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20015 DSNSLD1.DSNSVSTK *
* OFFSET0124 during incremental REBIND *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E20015 DSNSLD1.DSNSVSTK OFFSET0124 was encountered
during incremental rebind of statements bound prior to DB2 V8
that reference the following special registers: CURRENT
PACKAGESET, CURRENT PATH, CURRENT SQLID, CURRENT USER or CURRENT
OPTIMIZATION HINT.
Further investigation shows that after processing an excessive
number of incremental rebinds, there was a shortage of storage.
1 The storage shortage was due to statement-level control blocks
that were allocated during incremental rebind that were not
freed.
DB2 was modified to free the statement-level control blocks that
were allocated during incremental rebind.
Additional Keyword: SQLSPECIALREG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23366
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEBR PI23366
DSNXEBR9 PI23366
DSNXECL PI23366
DSNXECLF PI23366
DSNXECW PI23366
DSNXECWA PI23366
DSNXECWU PI23366
DSNXERB PI23366
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23366 DSNXEBR DSNXEBR9 DSNXECL DSNXECLF DSNXECW DSNXECWA
DSNXECWU DSNXERB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXEBR9
DSNXECL
DSNXECLF
DSNXECW
DSNXECWA
DSNXECWU
DSNXERB
LISTEND
UI23461 COVER LETTER END
UI23669 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27231 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of XMLMODIFY *
* function. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNOUPD M173 or *
* ABEND04E RC00E70005 DSNNOUPD M370 may *
* occur when processing the XMLMODIFY *
* function to do partial update of an XML *
* document. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
When using XMLMODIFY to do a partial update of an XML document,
the node id used to keep track of the document order may be
assigned an invalid id. This causes the ABEND to occur when the
invalid node id is referenced later.
After applying the fix, the correct node ids will be assigned to
the node during the execution of the XMLMODIFY function. But it
does not fix the invalid node ids in the existing documents. To
fix the invalid node id problem, a whole document update is
needed to reassign the node ids to all nodes in the document.
Below is an example UPDATE statement to do the whole document
update.
UPDATE ADMF001.TB_CUSTOMER_ACCOUNT_PBG
SET CUSTOMER_CREATE_XML1 =
XMLSERIALIZE(CUSTOMER_CREATE_XML1 AS CLOB)
WHERE CUSTOMER_ID = 1;
DB2 is modified to correct the node id assignment. Once the
correct node id is assigned, the ABEND will not occur.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27231
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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;
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOUPD PI27231
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27231 DSNNOUPD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNNOUPD
LISTEND
UI23669 COVER LETTER END
UI23679 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25372 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNINUKY ERQUAL5002 *
* during a LOAD DATA INTO TABLE PART *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
ABEND04E RC00C90101 at DSNINUKY:5002 happened during a LOAD DATA
INTO TABLE PART n with the default option ENFORCE CONSTRAINTS on
a table with referential integrity (RI) relationships defined.
The problem occurred because LOAD utility was running
parallelism but the number of indexes was not calculated
correctly, which caused a storage overlay when building internal
structures.
Additional symptoms and keywords:
RC00E4002E at DSNUGSUU + x'5418' OFFSET5418
ABEND0C4 RC00000038 RC38 DSNURWBF + x'08F6' OFFSET08F6
ABENDS0C4 DB2OVRLAY/K
LOAD utility has been modified to calculate index number
correctly when loading into the table with RI relationships
defined.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25372
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
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
DSNU3341I - CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT.
The utilities will now abend so that a RESTART is possible.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURPIB PI25372
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25372 DSNURPIB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURPIB
1 LISTEND
UI23679 COVER LETTER END
UI23690 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29176 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use query *
* acceleration and have PI22945 applied, *
* V10 PTF UI21946 or V11 PTF UI21947. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes SQLCODE -904 when *
* the TIME() scalar function is executed *
* on an accelerator when the expression *
* is a timestamp data type. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes SQLCODE -904 when the TIME() scalar function
is executed on an accelerator when the expression is a
timestamp data type.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLTIME SQLCODE904
DB2 code is fixed to return the correct result.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29176
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***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.
DB2BIND:
***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.
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXONZS PI29176
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29176 DSNXONZS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXONZS
LISTEND
UI23690 COVER LETTER END
UI23711 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29728 -
****************************************************************
* USERS AFFECTED: All IRLM 2.3 (HIR2230) users data sharing *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: High IRLM CPU time may be observed in *
* IRLM and XCF address spaces when an *
* application is doing multiple INSERTS *
* and DELETES under page-level locking. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
A DB2 thread may do multiple inserts and deletes under the same
commit scope. When Page-level locking is used, IRLM may issue
IXLLOCK ALTER requests to XES to change the locking attributes
of the page lock as the thread changes from being inserter to
deleter and vice-versa. IRLM forces this change to XES but it
may issue another IXLLOCK ALTER request when the change is done
and the waiter RLB for the change is released. In case of very
conditional locking for the page lock, the page lock request
may be successful or get rejected by XES. The erroneous second
IXLLOCK ALTER request could go asynchronous in XES which may
result in additional signalling required for contention
management. Since IRLM/XES is returning these very conditional
requests very fast back to DB2, the caller can come back very
fast trying for next page lock. In the event that a large number
of such page lock requests are unsuccessful, it may stack up
a big number of async IXLLOCK requests in XES. Such spike in
processing these async requests in XES would result in high
CPU time that can lead to group wide slowdown.
GEN:
KEYWORDS:
SYSPLEXDS
1
*** END IMS KEYWORDS ***
This APAR would remove the erroneous extra IXLLOCK ALTER request
that was being sent to XES when a request is being force sent
for altering the locking attributes of a lock. Removing the
unnecessary requests to XES which happens during insert/delete
row operations, would help in reducing the CPU time to process
these requests in XES.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI29728
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL120 PI29728
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29728 DXRRL120
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL120
LISTEND
UI23711 COVER LETTER END
UI23713 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26596 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users recovering *
* indoubt transactions after affected *
* objects have been placed into group buffer *
* pool recovery pending (GRECP), which also *
* results in adding index pages to the *
* logical page list (LPL). *
****************************************************************
* PROBLEM DESCRIPTION: Index UPDATE from an indoubt thread is *
* not backed out when the index was put *
* into logical page list (LPL) status *
* during DB2 restart and the thread *
* was aborted after restarting DB2. *
* Although LPL recovery has completed, *
* CHECK INDEX utility reports an *
* inconsistency like this: *
* DSNU711I DSNUKIKI - NO ROW FOR INDEX *
* ENTRY. RID=X'000003A603' *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Index UPDATE from an indoubt thread is not backed out when the
index was put into LPL during DB2 restart and the thread was
aborted after restarting DB2. Although LPL recovery has
1 completed running the CHECK INDEX utility reports an
inconsistency like this:
DSNU711I DSNUKIKI - NO ROW FOR INDEX ENTRY. RID=X'000003A603'
During the recovery of the indoubt transaction (while in GRECP),
DB2 was not correctly increasing the LPL range to allow for the
full backout of the indoubt transaction.
Additional keywords: MSGDSNU711I
Code in DB2 has been modified to extend the LPL processing
range when recovering an indoubt transaction while the object
was in GRECP status.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26596
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKUNR2 PI26596
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26596 DSNKUNR2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKUNR2
LISTEND
UI23713 COVER LETTER END
UI23741 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27493 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of the *
* LPAD or RPAD built-in functions. *
****************************************************************
* PROBLEM DESCRIPTION: When using the LPAD built-in function *
* with a vargraphic (DBCS) string *
* expression and the PAD character(s) *
* being the empty string, an unexpected *
* SQLCODE -331 (SQLCODE331) from DSNXROHB *
* location -117 can occur. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using the LPAD built-in function with vargraphic (DBCS)
data being referenced as the string expression, and the PAD
character(s) being the empty string, an unexpected SQLCODE -331
(SQLCODE331) from DSNXROHB location -117 can occur. The string
expression has to consist of multi-byte (DBCS or MBCS) character
data. An incorrect result is also possible.
1 The problem was reported using a static application. The
following example presents a simple failing case.
Step 1. Create a simple table with a vargraphic column.
CREATE TABLE TEST1 ( F_CHAR VARGRAPHIC(10)
DEFAULT NOT NULL ) CCSID UNICODE ;
Step 2. Insert a row of data into Table TEST1.
INSERT INTO TEST1( F_CHAR ) VALUES ('0123456789');
Step 3. In a static application, execute the following select
statement.
Define a host variable HV2 to contain a 10 character result.
EXEC SQL
SELECT LPAD(F_CHAR,3,'') INTO :HV2
FROM TEST1
END-EXEC.
Step 4. Bind and run the application package.
Step 5. Check the results.
An SQLCODE -331 from DSNXROHB, location -117, occurs because
the result length is not setup properly by DB2 for a DBCS
character string.
The expected result is the string '012'.
The following example returns the expected result.
EXEC SQL
SELECT LPAD('0123456789',3,'') INTO :HV2
FROM TEST1
END-EXEC.
Please note: The same failure can occur whether using the LPAD
or the RPAD built-in function.
Another example of a simple failing case is
SELECT LPAD(VARGRAPHIC('0123456789'),3,'') INTO :HV2
FROM TEST1
Additionally, an incorrect result can be returned instead of the
SQLCODE -331. For example,
1
SELECT RPAD(VARGRAPHIC('0123456789'),4,'') INTO :HV2
FROM TEST1
This case returns '01', the expected result is '0123'.
The code in DB2 is modified to set up the correct result length
if using an empty string as the PAD character(s) for the LPAD
or RPAD built-in functions when the input is vargraphic or
DBCS data.
Additional Keywords: SQLCODE331 SQLLPAR SQLRPAD
SQLINCORROUT INCORROUT SQLINCORR
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27493
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRSB2 PI27493
DSNXRS39 PI27493
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27493 DSNXRSB2 DSNXRS39
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRSB2
DSNXRS39
LISTEND
UI23741 COVER LETTER END
UI23743 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30138 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS who *
* have queries eligible for range list *
* access *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output (duplicate or missing *
* rows) can occur for a query with OR *
* predicates that can be mapped to a *
* single index when range-list index *
* scan is used (ACCESSTYPE='NR' in *
* the PLAN_TABLE) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output (duplicate or missing rows) can occur for a
query with OR predicates that can be mapped to a single index
1 when range-list index scan is used. Each leg of the OR
is referred to below as a 'range'. Specifially, this
problem can occur when all of the following conditions
are met:
- Two ranges overlap;
- When comparing 2 of the overlapping ranges (say ranges 2
and 3 from the example below), one range matches on
more index keys than the other range; and
- Given that there are n matching predicates for range 3,
the predicate matching on the nth index key has the
same literal value but different operator than the
operator of the predicate on the same column from range 2.
For example:
SELECT C1, C2, C3, C4, C5
FROM T1
WHERE
C1 = '10' AND
((C2 = '10' AND C3 = '10' AND C4 > '10') OR <= range 1
(C2 = '10' AND C3 > '20') OR <= range 2
(C2 >='10')) ; <= range 3
IX1(C1, C2, C3, C4)
Ranges 2 and 3 overlap. Range 2 matches on more index keys
(C1, C2, C3) than range 3 does (C1, C2). There are 2 matching
predicates for range 3. The predicate matching on the
2nd index key, C2, of range 3 is: C2 >= '10' .
The predicate on the same column from range 2 is: C2 = '10' .
The operator from these 2 predicates is different: >= vs. =
This case can get incorrect output when range list access
is chosen.
Additional Keywords:
SQLINCORROUT SQLINCORR INCORROUT DB2INCORR/K RANGELIST SQLOR
Code is updated to handle the query described above properly
so that the correct result can be returned when using range
list access.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30138
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSRL PI30138
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30138 DSNXOSRL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSRL
LISTEND
1UI23743 COVER LETTER END
UI23745 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26459 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of ALTER TABLE *
* ALTER COLUMN SET DATA TYPE *
****************************************************************
* PROBLEM DESCRIPTION: ALTER TABLE ALTER COLUMN SET DATA TYPE *
* on tables whose columns have *
* SYSCOLUMNS.DATATYPEID = 0 may not *
* generate a new version for non-padded *
* indexes whose key contains the altered *
* column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If columns of a table have SYSCOLUMNS.DATATYPEID = 0, during
the first column alteration, DB2 may incorrectly neglect to
generate a new version for indexes on the table when the
following conditions are met:
1. The index is a non-padded index
2. The altered column type is character, graphic, binary, or
timestamp
3. The index key contains the altered column and other
columns whose SYSCOLUMNS.DATATYPEID is 0
The problem of unversioned indexes may cause:
1. incorrect versions on the subsequent column alterations
2. storage overlay and DB2 termination. Here are possible
abends that may occur
ABEND0C4 RC0000003B DSNSVBK OFFSET1302
ABEND04E RC00E2000F DSNIDALC DSNSVSFB OFFSET0858
ABEND0C4 RC00000038 DSNITCUS OFFSET3C48
ABEND0C4 RC00000038 DSNICMT2 OFFSET8160
ABEND0C4 RC00000038 DSNIONX2 OFFSET0B44
3. uniqueness issue as the unique index may no longer enforce
uniqueness and allow duplicates
4. other unexpected symptoms.
In addition, taken image copies of the index might be bad if
they contain data in the format that is missing the version
number.
DB2 has been modified to correctly generate a new version for
indexes on tables whose columns have SYSCOLUMNS.DATATYPEID = 0
Applying this APAR does not help to fix any index that was
unversioned or incorrectly versioned. The bad index needs to
be dropped and re-created.
Additional Keywords
SQLALTER
1 SMCOVERLAY
DB2OVRLAY/K
SQLINCORR
SQLINCORROUT
DB2INCORR/K
DB2ABTERM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26459
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIALC PI26459
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26459 DSNXIALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIALC
LISTEND
UI23745 COVER LETTER END
UI24088 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28594 -
****************************************************************
* USERS AFFECTED: All DB2 FOR Z/OS V10 AND V11 customers who *
* have applied apar PI19976. *
****************************************************************
* PROBLEM DESCRIPTION: During rollback processing, DB2 follows *
* a corrupt section pointer which causes *
* a circular chain (infinite loop). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 keeps a linked list of related cursor sections (i.e declare
cursor, update where current of cursor, etc). In this case the
pointer to the next related section is self-referencing.
This caused DB2 to go into an infinite loop.
DB2 will now inspect the linked list to ensure the pointers are
not self-referencing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28594
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXECWA PI28594
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28594 DSNXECWA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXECWA
LISTEND
UI24088 COVER LETTER END
UI24103 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31921 -
****************************************************************
* USERS AFFECTED: All DB2 Data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: (1) ABEND04E RC00C90101 DSNISREC *
* ERQUAL5001 (2) ABEND04E RC00E20013 *
* during auto-GRECP recovery *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During Atuo-GRECP recovery, all the GRECP objects were included
in GRECP recovery list which resulted in large number of
GRECP objects failure during GRECP recovery. The reason for
these GRECP objects failure because those GRECP objects
were not opened by that member. This results in users to issue
several -START DB command. When too many -START DB command is
issued it is possible that DB2 may encountered 00E20013
(out of local master address space storage condition),
especially, data sharing group is large. By limiting number of
GRECP objects in each member's GRECP recovery list, it will also
avoid abend04E in DSNISREC ERQUAL5001.
DB2 auto-GRECP logic is modified to limit recovery of auto-GRECP
objects for each members to avoid these abends.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31921
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIERST PI31921
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31921 DSNIERST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIERST
LISTEND
UI24103 COVER LETTER END
1
UI24475 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26033 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an *
* ALTER TABLE ALTER COLUMN or ALTER VIEW *
* statement referencing a TABLE or VIEW *
* which has a TRIGGER defined on it. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E2000C at location *
* DSNHXLTR DSNSVSVB OFFSET0AB6 may occur *
* when a statement satisfies all of the *
* following list of conditions: *
* *
* 1. ALTER TABLE ALTER COLUMN or *
* ALTER VIEW statement that references *
* a TABLE or VIEW. *
* 2. A TRIGGER is defined on above TABLE *
* or VIEW. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create objects.
CREATE TABLE T1(
C1 VARCHAR(8),
C2 VARCHAR(2)
)!
CREATE VIEW V1(D1, D2) AS
SELECT C1, C2 FROM T1!
CREATE TRIGGER TRI1
AFTER INSERT ON T1
REFERENCING NEW AS RNEW FOR EACH ROW MODE DB2SQL
BEGIN ATOMIC
INSERT INTO T1 VALUES(RNEW.C1, RNEW.C2);
END!
CREATE TRIGGER TRI2
INSTEAD OF INSERT ON V1
REFERENCING NEW AS RNEW FOR EACH ROW MODE DB2SQL
BEGIN ATOMIC
INSERT INTO V1 VALUES('AAA', 'BB');
END!
Step 2. Statements which can cause ABEND.
1
Example#1:
ALTER TABLE T1
ALTER COLUMN C1 SET DATA TYPE VARCHAR(10)
ALTER COLUMN C2 SET DATA TYPE VARCHAR(10)!
Example#2:
ALTER VIEW V1 REGENERATE!
DB2 does not free storage properly when process the above ALTER
statement which may result in the ABEND.
The ABEND occurs because DB2 run out of storage since the
storage that are allocated when processing the statement
ALTER TABLE... ALTER COLUMN... SET DATA TYPE... isn't freed.
DB2 has been modified correctly to free storage when
processing ALTER statement.
Additional keywords: SQLALTER SQLVIEW SQLTRIGGER SQLSTORAGE
DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26033
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISUB PI26033
DSNXOOP PI26033
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26033 DSNXISUB DSNXOOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISUB
DSNXOOP
LISTEND
UI24475 COVER LETTER END
UI24481 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31261 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM 2.3) users data sharing *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM may issue MSGDXR175E - out of IRLM *
* private storage after PM89139/UK96959, *
1 * incorrectly. DB2/IMS subsystem may be *
* hung or abend due to reported storage *
* shortage by IRLM. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM accounting of its currently allocated private storage below
the 2G bar, may result in its counter showing a very high value.
This may be inaccurate in a data sharing environment. IRLM may
have a situation where IRLM workarea storage pool (that handles
XES SRBs for Complete and Notify Exits) expands for a spike of
activities and later, the storage is contracted. Storage
contraction does not adjust the accounting counter correctly
for this pool, leading to MSGDXR175I being issued inaccurately.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
This APAR fixes the storage accounting error in contraction of
private storage workarea subpool (RHWKL). IRLM accounting will
reduce the amount of private storage released from RLMACPVT
counter to prevent DXR175E being issued incorrectly.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI31261
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL24H PI31261
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31261 DXRRL24H
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL24H
LISTEND
UI24481 COVER LETTER END
UI24794 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28695 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users who perform a *
* SELECT query which uses the sort operations *
* after applying ptf UI17653 or UI17654. *
****************************************************************
* PROBLEM DESCRIPTION: Abnormal high CPU usage after canceling *
* the running SQL SELECT statement where *
* a CGTT workfile is deleted. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
After cancelling a running SELECT statement where a CGTT
workfile is deleted, an abormal high CPU usage is observed which
caused by a loop at agent deallocation process after the cancel.
DB2 code is fixed to properly dequeue the partial
workfile at agent deallocation time.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28695
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDALC PI28695
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28695 DSNIDALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDALC
LISTEND
UI24794 COVER LETTER END
UI24847 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28150 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of compiled *
* SQL scalar function created or generated *
* in V11 *
****************************************************************
* PROBLEM DESCRIPTION: In co-existence environment, the *
* implicit regeneration of a compiled *
* SQL scalar function that was created *
* or generated in V11 may encounter an *
* ABEND04E RC00E70100 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In co-existence environment, DB2 10 issues an ABEND04E
RC00E70100 when implicitly regenerating a complied SQL scalar
function that was created or generated in V11 and whose name
is different than the specific name. An SQLCODE904 is issued
for the unavailable routine.
If there is another compiled SQL scalar function that happens
to have the same name as the specific name of the function
being regenerated, DB2 10 will incorrectly regenerate this
function. As the function that is supposed to be regenerated
is not regenerated, the autobind process may hang. The user
may have to use a DB2 CANCEL THREAD command to terminate the
1 thread.
DB2 10 has been modified to correctly look up SYSROUTINES when
implicitly regenerating a complied SQL scalar function.
Additional Keywords
DB2COEXIST/K
DB2MIGV11/K
SQLUDF
RC00E70100
SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28150
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISUB PI28150
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28150 DSNXISUB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISUB
LISTEND
UI24847 COVER LETTER END
READY
END
|
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 <x>
to the format below. If no entry for DDF_COMPATIBILITY is
present, add one that is in the format below.
DDF_COMPATIBILITY STR M <x>
Change <x> to NULL if you skipped step (2), above.
Otherwise, change <x> 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 <x>
or this format:
DDF_COMPATIBILITY STR M <x>
to this format:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M NULL
Change <x> 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 <prefix> 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=<wlmenv>,REFRESH
where <wlmenv> 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=<wlmenv>,REFRESH
where <wlmenv> 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 <x>
or this format:
DDF_COMPATIBILITY STR M <x>
to the format below. If no entry for DDF_COMPATIBILITY is
present, add one that is in the format below:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M NULL
Change <x> 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 <x> 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 <prefix> 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.
<error httprc="{HTTP status code}">
{SOAP message}
</error>
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=<wlmenv>,REFRESH
where <wlmenv> 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 <table
space>.
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 <x>
Change <x> to NO if you want the DB2 installation CLIST
to configure installation jobs for COBOL V5.1. Otherwise,
change <x> 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=<x>
(where <x> 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 <x>
Change <x> 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 <prefix> 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=<wlmenv>,REFRESH
where <wlmenv> 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 <y>
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <z>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <y>
SIMULATED_CPU_SPEED CHARR G OFF NONE <z>
where <y> is the current setting of SIMULATED_CPU_COUNT
and <z> 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
| |
Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release level AH00 
AH00 Covers