Scope: All DB2 Users
Effective Date: 09/01/2013
Group Name: Z_SW_TDS_DB2_SYSTEM
Affected Locations: All Sites
Summary: Provide DB2 Hold Data and Cover letters for DB2 V10 Maintenance, HP release level AC00 (IBM RSU 1207+)
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 requires DB2 binds to implement that 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 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 needn't be addressed by application developers or DBA's.
Primary Contact: Rebecca Keller (719-592-4258)
Secondary Contact: TDSDB2@HP.COM
1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES
READY
%COVRLETR WDB2I.R.DB2101S.SMPPTS
IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED
UK71333 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM38164 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: 1. Repeated access to *
* SYSINDEXSPACESTATS when *
* SYSINDEXSPACESTATS.NLEAF is NULL *
* or unavailable during index *
* probing. *
* *
* 2. ABEND0C9 RC00000009 DSNKCEST *
* OFFSET061C during index probing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. If the in-memory value of SYSINDEXSPACESTATS.NLEAF is
unknown, an access to SYSINDEXSPACESTATS is made to retrieve
NLEAF. If NLEAF is NULL, or SYSINDEXSPACESTATS is unavailable,
the in-memory value is never initialized and repeated access
to SYSINDEXSPACESTATS occurs.
The repeated access shows up as excessive I/O and overhead
during bind.
2. When SYSINDEXSPACESTATS.NLEAF is NULL or unavailable,
a divide by 0 can occur resulting in S0C9 abend.
1. DB2 is changed to be fault tolerant when the number of
leaf pages is unknown. When NLEAF is unavailable, an
alternate method is used to estimate the number of leaf
pages in an index.
2. DB2 is changed to inspect the value of NLEAF before using
it as a divisor.
PM47781 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V10 users *
****************************************************************
* PROBLEM DESCRIPTION: fix completion for apar PM38164 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
fix completion for apar PM38164
fix completion for apar PM38164
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM38164,PM47781
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
DSNKCEST PM38164 PM47781
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM38164 DSNKCEST
PM47781 DSNKCEST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKCEST
LISTEND
UK71333 COVER LETTER END
UK72025 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM44938 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of inline LOBs *
* with parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at *
* location DSNXORLI P008 when running a *
* query with parallelism that contains an *
* inline LOB and outer join. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 can occur at location DSNXORLI:P008 when
running a query with parallelism that contains an inline LOB and
outer join. Parallelism is not supported for inline LOBs, but
DB2 failed to disable parallelism for inline LOBs due to outer
join optimization.
The following example illustrates a failing case. Please note
however that this example is not guaranteed to reproduce the
problem because it also depends on the access path chosen during
the bind process.
Step 1. Create a Table with an inline LOB.
CREATE TABLE MYTABLE (C1 INT,
C2 INT,
C3 CLOB(1M) INLINE LENGTH 100,
C4 VARCHAR(2),
C5 VARCHAR(2));
Step 2. Using special register, enable parallelism.
SET CURRENT DEGREE='ANY';
1
Step 3. Execute the following query that contains outer join.
SELECT T1.C1
FROM MYTABLE AS T1 JOIN MYTABLE AS T2
ON CAST(T1.C3 AS VARCHAR(2)) = T2.C4
LEFT JOIN MYTABLE AS T3 ON T2.C4 = T3.C5
LEFT JOIN MYTABLE AS T4 ON T3.C1 = T4.C2;
The abend mentioned above should occur.
DB2 is modified to disable parallelism when inline LOBs are
detected with outer joins.
Additional Keywords: SQLPARALLEL PARALLELISM DB2PARALL/K
SQLLOB SQLOUTERJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM44938
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOB2 PM44938
DSNXORMQ PM44938
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM44938 DSNXOB2 DSNXORMQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOB2
DSNXORMQ
LISTEND
UK72025 COVER LETTER END
UK72077 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM39800 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of RID access *
* path. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXGRDS *
* DSNXRRP location M700 may occur when *
* fetching rids into a workfile and an *
* error such as resource unavailable *
* occurs on the workfile. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend may occur if the following conditions are true :
- the SQL query is using rid access
1 - RID list overflow has occurred
- an error such as resource unavailable occurred while
writing the RIDS to a workfile
- there is a stage 2 predicate on the query
The following is an example of a query using multiple index
access that may encounter the abend.
CREATE TABLE T1 (C1 INT, C2 INT);
CREATE INDEX IX1 ON T1(C1);
CREATE INDEX IX2 ON T1(C2);
SELECT C1 FROM T1
WHERE C1 = 1 AND
C2 = 2 AND
INT(C1) = 1;
SQLCODE -913 from location -120 in DSNXRPJW is an alternate
symptom of this problem.
DB2 has been fixed so the SQLCODE -913 is no longer issued
for this case since the access path reverted to table space
scan.
Additional keywords : SQLCODE913
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM39800
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRRID PM39800
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM39800 DSNXRRID
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRRID
LISTEND
UK72077 COVER LETTER END
UK72081 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47629 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users who need *
* an updated copy of the Diagnosis Guide *
* and Reference. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR provides an updated PDF *
1 * copy of the DB2 10 for z/OS *
* Diagnosis Guide and Reference. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the following version of the DB2
Diagnosis Guide and Reference in PDF format:
V10: LY37-3220-03
This is the same version of this document that is
available on the latest DB2 for z/OS licensed library
collection.
This APAR provides the following version of the DB2 for z/OS
Diagnosis Guide and Reference in PDF format:
V10: LY37-3220-03
To read this document, download it as binary to your PC
or other system that has a PDF reader, such as the Adobe
Acrobat Reader.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47629
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 PM47629
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47629 DSNDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNDR
LISTEND
UK72081 COVER LETTER END
UK72088 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM42312 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of DML DELETE *
* operations. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 *
* DSNIDM.DSNIDLDS ERQUAL5013 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For a UTS table, the inconsistent information in its spacemap
page caused DB2 logic to read an empty page.
DB2 logic is modified to correctly reflect the data page
status in its spacemap page.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM42312
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISGSU PM42312
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM42312 DSNISGSU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGSU
LISTEND
UK72088 COVER LETTER END
UK72091 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45300 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those users who are utilizing *
* the Private Protocol to DRDA Protocol REXX *
* catalog analysis tool, DSNTP2DP, to *
* generate the commands needed to convert *
* plans and/or packages to use DRDA protocol. *
****************************************************************
* PROBLEM DESCRIPTION: Possible TSO/E NOT VALID COMMAND error *
* when processing the generated command *
* output from DSNTP2DP. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When install job, DSNTIJPD, which executes the private protocol
to DRDA protocol catalog analysis program, DSNTP2DP, is run
to examine a DB2 catalog for plans or packages which need to
be converted, it generates output which, when used as input
to the TSO Batch command parser, IKJEFT01, needs to be edited
before the generated commands can be run. The problem occurs
when DSNTP2DP generates a commented version of a command by
using TSO command line continuation techniques. Comments in a
TSO command input stream cannot use line continuation. The
problem generally occurs when the length of a fully qualified
package name, i.e. collection-id.package-id.(version-id), is
long enough to cause the command being commented to exceed
72 characters in length.
DB2 has been changed so that when DSNTP2DP has to generate
a commented version of a command, DSNTP2DP will correctly
generate a separate comment line for each line of a command
which would itself have to be generated as multiple lines
having a trailing TSO line continuation character and not
1 exceeding 72 characters in length.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM45300
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTP2DP PM45300
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45300 DSNTP2DP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTP2DP
LISTEND
UK72091 COVER LETTER END
UK72268 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46870 -
****************************************************************
* USERS AFFECTED: Users of the COBOL DB2 coprocessor for DB2 *
* V9.1 for z/OS or DB2 V10.1 for z/OS using *
* FETCH WITH CONTINUE followed by FETCH or *
* FETCH CURRENT CONTINUE followed by FETCH *
****************************************************************
* PROBLEM DESCRIPTION: When using FETCH WITH CONTINUE followed *
* by FETCH, or FETCH CURRENT CONTINUE *
* followed by FETCH in a COBOL *
* application and using the DB2 *
* coprocessor to prepare the program, *
* SQLCODE -20411 is issued erroneously. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example illustrates the reported problem:
EXEC SQL
FETCH CURRENT CONTINUE FROM C1 INTO :MY-CLOB
END-EXEC.
...
EXEC SQL
FETCH C2 INTO :MY-BIG-CLOB
END-EXEC.
At execution time, SQLCODE -20411 is issued erroneously.
SQLCODE = -20411, ERROR: A FETCH CURRENT CONTINUE OPERATION
WAS REQUESTED FOR C2 BUT THERE IS NO PRESERVED, TRUNCATED
DATA TO RETURN.
1 SQLSTATE = 24524 SQLSTATE RETURN CODE
SQLERRP = DSNXEFCC SQL PROCEDURE DETECTING ERROR
With the fix, the FETCH following the FETCH CURRENT CONTINUE
should be executed correctly if there are no other SQL errors.
Additional keywords: SQLCODE20411 db2coprocessor
The DB2 coprocessor is changed so that the SQLCODE -20411 will
not be issued erroneously.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46870
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHTARY PM46870
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46870 DSNHTARY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHTARY
LISTEND
UK72268 COVER LETTER END
UK72303 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46833 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD ENFORCE CONSTRAINTS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNICLOS:5007 *
* during a LOAD utility with ENFORCE *
* CONSTRAINTS. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD UTILITY with ENFORCE CONSTRAINTS abended with an ABEND04E
RC00C90101 in DSNICLOS ERQUAL5007 at the end of the ENFORCE
phase. An incorrect data base identifier was used during a
close of one of the foreign keys.
Code has been modified to use the correct data base identifier.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46833
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURCRI PM46833
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46833 DSNURCRI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURCRI
LISTEND
UK72303 COVER LETTER END
UK72345 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM43934 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of DB2 sort. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXESX2 P404 *
* may occur *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An internal DB2 sort buffer can contain several fields.
In the error case, one of these fields is set incorrectly
which could lead to an abend
This problem is more likely to occur with parallelism but
can occur without
The code in DB2 has been modified to setup the sort buffer field
correctly so that relocation failures do not occur during
execution.
Additional keywords: SQLPARALLELISM SQLSORT DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM43934
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM43934:
See PM43934 APAR/PTF text for additional information about
why a REBIND is necessary.
PM43934 corrects a problem that can lead to an ABEND04E
RC00E70005 at location DSNXESX2:P404.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM28718:
1
See PM28718 APAR/PTF text for additional information about
why a REBIND is necessary.
PM28718 corrects a problem of incorrect output when running
a query which SELECT from MERGE when the UPDATE clause is in
row expression format and the MERGE contains an INCLUDE column
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGMVE PM43934
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM43934 DSNXGMVE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGMVE
LISTEND
UK72345 COVER LETTER END
UK72373 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM39078 -
****************************************************************
* USERS AFFECTED: ALL DB2 10 for z/OS users of XML columns *
* and the USE CURRENTLY COMMITTED option. *
****************************************************************
* PROBLEM DESCRIPTION: Missing warning message +20002 *
* when user uses the USE CURRENTLY *
* COMMITTED option or attribute to bind *
* or prepare a query which references an *
* XML column that does not support *
* multiple XML versions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Missing warning message +20002 when user uses the USE
CURRENTLY COMMITTED option or attribute to bind or
prepare a query which references an XML column that does not
support multiple XML versions.
The following example will issue a warning message after
applying this apar.
DECLARE C11 CURSOR FOR
SELECT INT1, XML1 FROM TB843T1 FOR FETCH ONLY;
XML1 is an XML column that does not support multiple XML
versions.
The above query is bound using
1 ACCESSCONCURRENTRESOLUTION(UseCurrentlyCommitted) bind option.
DB2 is updated to issue warning message for a query as above.
Addtional Keywords: SQLXML SQLCODE20002
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM39078
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM39078:
See PM39078 APAR/PTF text for additional information about
why a REBIND is necessary.
PM39078 corrects a problem of missing warning message when a
query which references an XML column that does not support
multiple XML versions and it is bound with the USE CURRENTLY
COMMITTED option.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DOCUMENTATION:
Existing warning SQLCODE +20002 is changed by this APAR/PTF.
The change will be documented in the DB2 Codes, SQL Reference,
Command Reference manuals respectively.
The texts for SQLCODE +20002 are:
+20002
THE clause SPECIFICATION IS IGNORED FOR OBJECT object-name
Explanation
This message is issued in response to a clause specification
that was ignored on a query statement.
System action
The statement is processed.
User response
To stop receiving this message, avoid
ACCESSCONCURRENTRESOLUTION(UseCurrentlyCommitted) bind option
for a plan or package accessing non-versioned XML, or
avoid a statement (accessing non-versioned XML) prepared with
"Use Currently Committed" attribute.
User response needs real action:
If an XML column does not support multiple XML versions,
you can convert to an XML column that supports multiple XML
versions by following these steps:
1. Unload the data from the table that contains the XML
columns.
2. Drop the table.
1 3. Create the table in a universal table space. The new
table supports multiple XML versions.
4. Load the data into the table.
SQLSTATE
01624
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOZAT PM39078
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM39078 DSNXOZAT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOZAT
LISTEND
UK72373 COVER LETTER END
UK72444 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM38593 -
****************************************************************
* USERS AFFECTED: ALL DB2 FOR z/OS V8, DB2 9 FOR z/OS, AND *
* DB2 10 FOR z/OS USERS OF COPY UTILITY WITH *
* SHRLEVEL CHANGE ON OBJECTS DEFINED AS *
* TRACKMOD NO AND WHO UTILIZE REAL TIME *
* STATISTICS (RTS). *
****************************************************************
* PROBLEM DESCRIPTION: REAL TIME STATISTICS NOT UPDATED *
* AS EXPECTED AFTER COPY SHRLEVEL *
* CHANGE ON TRACKMOD NO OBJECTS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Users who run COPY utility with SHRLEVEL CHANGE on objects
created with, or altered to, TRACKMOD NO may observe that
Real Time Statistics (RTS) field COPYUPDATEDPAGES is not
updated as expected.
COPYUPDATEDPAGES may perpetually contain a zero value even
though pages have been changed as evidenced by nonzero values
in the COPYCHANGES column for the same objects.
Applications using these RTS values may treat TRACKMOD NO
objects incorrectly as having less update activity than they
have, or none at all.
COPY utility with SHRLEVEL CHANGE was changed so that
Real Time Statistics are kept for TRACKMOD NO objects as
they are for other objects.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM38593
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
DSNUBAFI PM38593
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM38593 DSNUBAFI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBAFI
LISTEND
UK72444 COVER LETTER END
UK72447 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45651 -
****************************************************************
* USERS AFFECTED: ALL DB2 10 FOR z/OS USERS WHO INSERT DATA *
* WITH SQL INSERT STATEMENTS ON OBJECTS *
* DEFINED WITH COMPRESS YES *
****************************************************************
* PROBLEM DESCRIPTION: ELONGATED ELAPSED TIME DURING *
* INSERTS OF UNCOMPRESSED ROWS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran many INSERT statements on an object defined with
COMPRESS YES.
When enough data was inserted to start building the
compression dictionary, the dictionary was not built due to
the nature of the data.
In this event, DB2 will not continue to retry building the
dictionary, as there can be a CPU cost in doing so, which is
undesirable if it is not likely to be successful.
However, in this case the user data was such that as more
rows were inserted a dictionary would have been built after the
point this determination was made. Thus, the expected
performance benefit of compression on the remainder of the
INSERTs was not realized.
The Build Dictionary routine for compression during INSERT,
and the code which invokes it, were changed to periodically
redrive attempts to build a compression dictionary in such
a way to maximize the benefits of compression while minimizing
the cost of unsuccessful attempts to build a dictionary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM45651
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISRTI PM45651
DSNUZLCR PM45651
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45651 DSNISRTI DSNUZLCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISRTI
DSNUZLCR
LISTEND
UK72447 COVER LETTER END
UK72517 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46041 -
****************************************************************
* USERS AFFECTED: All DB2 zOS users. *
****************************************************************
* PROBLEM DESCRIPTION: DSNIHSET ERQUAL1005 ABEND04E with *
* RC00C90101 during postponed abort *
* process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When process an add-volume log record during postponed abort,
DB2 mistakenly went to the Page Set Control Block (PSCB) chain
to search for this Agent's Page Block (PBA). A left-over PSCB
in the chain misled DB2 to think it held the page set lock,
so DB2 requested a page lock without holding its page set lock.
Then this page lock request failed at DSNIHSET:1005.
During postponed abort, DB2 should go to the Data Base Recovery
control Table (DBRT) for the PBA, not the PSCB chain under the
Cursor Table (CT). Fixes made in DB2, so it'll find the correct
PBA and avoid the lock failure.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46041
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIOPNP PM46041
DSNIOPPS PM46041
DSNIOPPZ PM46041
DSNPAVLR PM46041
DSNUKIFK PM46041
DSNUKNFK PM46041
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46041 DSNIOPNP DSNIOPPS DSNIOPPZ DSNPAVLR DSNUKIFK DSNUKNFK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNIOPNP
DSNIOPPS
DSNIOPPZ
DSNPAVLR
DSNUKIFK
DSNUKNFK
LISTEND
UK72517 COVER LETTER END
UK72540 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM40417 -
****************************************************************
* USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS *
* USERS *
****************************************************************
* PROBLEM DESCRIPTION: INCREASED RECOVERY TIMES DUE TO *
* INVALID OPEN ENDED SYSLGRNX RANGES *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User observed longer than expected elapsed times for
RECOVER utility for some objects. Further investigation
revealed that the extra time was spent in LOGAPPLY phase,
which in turn was shown to be due to open ended records
in DSNDB01.SYSLGRNX for those objects (i.e., the STOPRBA
and STOPLRSN fields were zero) even though those objects
were not open for update and had no logged activity
against them that RECOVER would need.
Close processes (for example, -STOP DB command, DB2
pseudo-close, etc.) which should have closed out these
open ended records did not, but instead were observed
to have inappropriately updated older records and not
the most recent open ended one.
This was because DB2 close processing calls a DB2 service
to retrieve the most recent SYSLGRNX record for an object,
and in some cases the service incorrectly retrieved a
record which was not the most recent one.
For this to be possible, all of the following must be true:
- the environment is non-Data Sharing.
- DB2 is running in V9 New Function Mode (NFM) or above,
or has returned from V9 NFM or above.
- prior to first migration to V9 NFM or above, the system RBA
was numerically higher than the system timestamp.
The DB2 service used to retrieve the most recent SYSLGRNX
record for pseudo-close processing was changed to fix this
problem so that the record retrieved will really be the most
recent.
Note that the fix to this problem is to correctly close
SYSLGRNX records which exist for objects that are open for
update. In some situations this didn't work correctly, and
the impact to RECOVER was due to the presence of these records.
Since the problem (and the fix) do not affect RECOVER utility
directly, applying this fix might not yield an immediate benefit
1 to RECOVER. Over time, as new SYSLGRNX records are created
and subsequently closed with the fix applied, the benefit to
RECOVER will be seen.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM40417
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUAHR2 PM40417
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM40417 DSNUAHR2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUAHR2
LISTEND
UK72540 COVER LETTER END
UK72550 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48643 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS Version 10. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNJ106I LOG READ ERROR with *
* ERROR STATUS=00201110 reading an *
* active log data set that was not *
* completely formatted (HURBA < HARBA). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An active log data set was redefined with a larger size, and
the original active log was REPRO'ed into this new, larger log
data set. This results in the high-used RBA (HURBA) being
less than the high-allocated RBA (HARBA). An IFI IFCID 306
application began reading this active log data set, and
pre-fetch operations were receiving an out-of-extent error
attempting to read beyond the HURBA. This error did not
cause the IFI application to fail. DB2 will shut down the
log read pre-fetch operation following this error message.
The code to limit the pre-fetch log reads to the formatted area
(HURBA) of the active log data set has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48643
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJR006 PM48643
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48643 DSNJR006
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJR006
LISTEND
UK72550 COVER LETTER END
UK72558 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46400 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 users of CP query *
* parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Thread loops in DSNTTSPD, DSNTTSAT, *
* and DSNXPRE3 after an SQL error *
* condition raised by a parallel task. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An SQL error for a parallel task was not properly propagated
to the originating task before the parallel task exited. Since
the originating task had no knowledge of the error, it continued
to wait for the parallel task to finish, causing the symptom
thread loop.
This only occurs for SQL errors that generate extended
diagnostic blocks greater than 32k bytes in size.
DB2 code has been modified to propagate SQL error conditions
noted above to the originating task. This allows the
originating task to terminate correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46400
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEMSG PM46400
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46400 DSNXEMSG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEMSG
LISTEND
UK72558 COVER LETTER END
1
UK72603 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM42165 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* LOAD REPLACE utility users of PBG table *
* spaces. *
****************************************************************
* PROBLEM DESCRIPTION: A LOAD REPLACE utility leaves *
* unallocated partitions of a partition *
* by growth table space in a RECOVER *
* PENDING state resulting in message *
* DSNU202I and RC8 by a subsequent *
* utility. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD REPLACE utility was run on a PBG table space. The
LOAD was successful but subsequent utility access to the table
space resulted in MSGDSNU202I - RECOVER PENDING ON TABLE SPACE
name PROHIBITS PROCESSING.
During the LOAD REPLACE, the utility was unable to determine the
actual number of partitions for the PBG table space and instead,
used the maximum number of partitions. This resulted in
unallocated partitions being placed in RECP at the start of the
utility, without being reset at the end of the utility
execution.
Code has been modified to place only the actual number of
partitions of the table space in the pending state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM42165
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFRP PM42165
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM42165 DSNURFRP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFRP
LISTEND
UK72603 COVER LETTER END
UK72625 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47784 -
1 ****************************************************************
* USERS AFFECTED: All users of DB2. *
****************************************************************
* PROBLEM DESCRIPTION: Physical open of indoubt object *
* during DB2 end restart even when *
* DEFER ALL is specified. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During end of restart, DB2 physically opens all the objects
associated with indoubt Unit of Recovery (UR). This may cause
DB2 to issue message DSNB207I - DYNAMIC ALLOCATION OF DATA SET
FAILED, if the data set does not exist. Today, DB2 always
tries to open data sets for indoubt UR, although page set is
zparm deferred. To avoid DB2 issuing DSNB207I message, Data
Manager (DM), at the end of restart, will not try to physically
open the page set if the page set is zparm deferred.
DB2 end restart logic is changed so that if page set is zparm
deferred, it will not be physically opened for indoubt or
postponed abort URs.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47784
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 PM47784
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47784 DSNIERST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIERST
LISTEND
UK72625 COVER LETTER END
UK72687 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48185 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those using the member *
* specific DVIPA specified in the DB2 BSDS. *
****************************************************************
* PROBLEM DESCRIPTION: When a client tries to connect to a *
* stopped DB2 using the member specific *
* DVIPA, notification of the outage can *
* get delayed which, in turn, delays the *
* rerouting of the connection to an *
* available member. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
When DDF stops, it disables the member specific DVIPA that is
specified in the DB2 BSDS (Boot Strap Data Set) and used for
remote connectivity. When a remote client tries to connect to
DB2 using the disabled DVIPA, it can take several minutes for
it to get notified of the outage, thus delaying the reroute of
the connection request to an available member.
DDF has been changed to no longer delete the member specific
DVIPA, defined in the DB2 BSDS, when DDF is stopped. This is
required for the benefit of providing instantaneous connection
request failures if remote client systems attempt to access the
DB2 member where DDF is now stopped. The will allow the remote
client system to more quickly and efficiently reroute the
request to available members of the data sharing group.
Users should be aware that they may now see the presence of
the DVIPA even though DDF, or even DB2, is stopped. This will
now be the normal behavior. The presence of the DVIPA is not
an issue because the DVIPA will be inherited by the DB2 (DDF)
member regardless of wherever it is restarted in the sysplex.
This new behavior is only relevant for member specific DVIPA
addresses that are specified in the DB2 BSDS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48185
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLITR0 PM48185
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48185 DSNLITR0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLITR0
LISTEND
UK72687 COVER LETTER END
UK72741 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45679 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users issuing STOP DATABASE *
* command for a list of objects. *
****************************************************************
* PROBLEM DESCRIPTION: ABND04E RC00C90101 DSNISTDB ERQUAL1001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00C90101 was encountered when trying to STOP a
1 list of databases. The command format may be as follows
-STOP DATABASE(DB00*A)
with the use of a wildcard asterisk. At the point of failure
DB2 was expecting that appropriate locks had been obtained for
all objects in the list. During the unlock attempt an unexpected
return code indicated that locks had not been obtained for some
of the objects in the list. There were potential timing holes
when DB2 may encounter a problem in reading the DB2 catalog or
during locking attempts for some of the objects. In those cases
DB2 was still trying to process the entire list of objects.
This then led to the RC00C90101 failure in DSNISTDB.
DB2 code has been corrected to disallow any processing of a
partially built list of objects for the STOP DATABASE command.
MSGDSNT305 will be issued for the Batch (synchronous) and online
(asynchronous) environment and a non-zero return code will
be issued. A sample message may be as follows :
DSNT305I @ SUBSYSTEM FAILURE DURING STOP DATABASE COMMAND
PROCESSING. RC=00000074, REASON=00E30064
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM45679
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISTDB PM45679
DSNTDSTP PM45679
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45679 DSNISTDB DSNTDSTP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISTDB
DSNTDSTP
LISTEND
UK72741 COVER LETTER END
UK72775 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46432 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000004 at DSNXACKP+0710 *
* occurred during command processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During authorization check for a command, an abend
ABEND0C4 RC00000004 DSNXACKP+0710
occurred.
1 This was caused because of an incorrect length being specified
for a storage move instruction to move the command string
to the primary address space.
Similar abends may occur due to an incorrect length being
specified for a storage move instruction to move various
authorization check parameters to the primary address space.
DB2 code is changed to correct the length
of storage move in the above scenarios.
Additional keywords: OFFSET0710 DSNXACKP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46432
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXACKP PM46432
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46432 DSNXACKP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXACKP
LISTEND
UK72775 COVER LETTER END
UK72786 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45387 -
****************************************************************
* USERS AFFECTED: All DB2 users who use BIND PLAN with MEMBER *
* option and ENABLE option. *
****************************************************************
* PROBLEM DESCRIPTION: When using BIND PLAN with both MEMBER *
* and ENABLE options, the following abend *
* may happen: *
* ABND=04E-00C90101 at DSNIBNRF:501E *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using bind plan with the MEMBER option, DB2 implicitly
converts DBRM members into packages, and then binds the plan
with a package list. If the ENABLE option is also specified,
and one or more of the DBRMs are in an inconsistent state or
completely missing, DB2 may incorrectly use an internal pointer
when processing the ENBALE option for the plan, and may
generate the following abend:
ABND=04E-00C90101 at DSNIBNRF:501E
DB2 has been fixed to handle BIND PLAN with the MEMBER option
and ENABLE option correctly.
1
ADDITIONAL KEYWORDS: ABEND04E RC00C90101 DSNIBNRF ERQUAL501E
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM45387
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAP1 PM45387
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45387 DSNTBAP1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBAP1
LISTEND
UK72786 COVER LETTER END
UK72803 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM26789 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC. *
****************************************************************
* PROBLEM DESCRIPTION: Performance enhancement in DB2 ODBC *
* for z/OS fetch processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 ODBC introduces two new initialization keywords,
LIMITEDBLOCKFETCH and QUERYDATASIZE, to be specified in the
data source stanza of the initialization file. These two
keywords allow applications to enable limited block fetch
to improve the performance of FETCH operations when connected
to a local DB2 for z/OS server.
LIMITEDBLOCKFETCH = 0 | 1
This keyword is a performance optimization keyword that
specifies whether DB2 ODBC is to attempt limited block fetch
when fetching result sets from the connected data source.
0 = Limited block fetch is not used. 0 is the default.
1 = DB2 ODBC attempts to use limited block fetch. If
blocking is supported at the server for the result set
that is being fetched, DB2 ODBC retrieves as many rows
as it can fit in a query data block in a single fetch
request.
QUERYDATASIZE = integer
This keyword specifies the amount of query data, in bytes, that
DB2 returns on each FETCH operation when limited block fetch is
1 enabled. The default value is 32767. Possible values are:
32767 294911 557055 819199
65535 327679 589823 851967
98303 360447 622591 884735
131071 393215 655359 917503
163839 425983 688127 950271
196607 458751 720895 983039
229375 491519 753663 1015807
262143 524287 786431 1048575
If you specify a value that is not a valid value, DB2 ODBC sets
QUERYDATASIZE to the nearest valid value.
This APAR introduces two new DB2 ODBC initialization keywords,
LIMITEDBLOCKFETCH and QUERYDATASIZE, to support limited block
fetch. Limited block fetch can improve data retrievel for
local DB2 for z/OS queries.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PM26789
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
This PTF introduces the following changes to DB2 ODBC externals:
New DB2 ODBC for z/OS initialization keywords described as
follows.
LIMITEDBLOCKFETCH = 0 | 1
This keyword is a performance optimization keyword that
specifies whether DB2 ODBC is to attempt limited block fetch
when fetching result sets from the connected data source.
0 = Limited block fetch is not used. 0 is the default.
1 = DB2 ODBC attempts to use limited block fetch. If blocking
is supported at the server for the result set that is
being fetched, DB2 ODBC retrieves as many rows as it can
fit in a query data block in a single fetch request.
QUERYDATASIZE = integer
This keyword specifies the amount of query data, in bytes, that
DB2 returns on each FETCH operation when limited block fetch is
enabled. The default value is 32767. Possible values are:
32767 294911 557055 819199
65535 327679 589823 851967
98303 360447 622591 884735
131071 393215 655359 917503
163839 425983 688127 950271
196607 458751 720895 983039
229375 491519 753663 1015807
262143 524287 786431 1048575
If you specify a value that is not a valid value, DB2 ODBC sets
QUERYDATASIZE to the nearest valid value.
Information about the new DB2 ODBC initialization keywords
and DB2 ODBC limited block fetch will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.
ACTION:
1 *** Action for PM32032 (Version 10)
The following database request module (DBRM) is updated by
this PTF:
DSNCLIQR
Application of this PTF requires a BIND PACKAGE for the above
package. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
ACTION:
The following database request modules (DBRMs) are updated by
this PTF:
DSNCLINF
DSNCLIC1
DSNCLIMS
DSNCLIQR
DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only)
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
This PTF introduces two new DB2 ODBC initialization keywords
LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block
fetch. Limited block fetch is a performance optimization that
enables applications to improve the performance of FETCH
operations when connected to a local DB2 for z/OS server.
If limited block fetch is not desired, no further action is
necessary other than rebinding the DBRMs listed above;
otherwise please note the following.
When you enable limited block fetch, the data that is returned
to your application might not reflect the data that has been
committed to the source table. If your application fetches
data from tables that are updated by other users, or if your
application uses savepoints and issues ROLLBACK TO SAVEPOINT
to manage transactions, you should disable limited block fetch.
ACTION:
This PTF updates DB2 ODBC for z/OS database request module
(DBRM) DSNCLIC1.
After you apply this PTF, you need to run the BIND PACKAGE
command to recreate the package for DSNCLIC1. Failure to bind
the required package could result in SQLCODE -805 at application
1 run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
prefix.SDSNSAMP data set for an example of how to perform the
BIND command.
ACTION:
The following database request modules (DBRMs) for ODBC
DB2 for z/OS are updated by this PTF:
DSNCLIMS
DSNCLIC1
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
SDSNSAMP dataset for an example of how to perform the
BIND command.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC24 PM26789
DSNAOC03 PM26789
DSNAOC06 PM26789
DSNAOC28 PM26789
DSNAOC27 PM26789
DSNAOC22 PM26789
DSNAOC14 PM26789
DSNAOC15 PM26789
DSNAOC1U PM26789
DSNAOG02 PM26789
DSNAOG24 PM26789
DSNAOG03 PM26789
DSNAOG04 PM26789
DSNAOG1R PM26789
DSNAOG05 PM26789
DSNAOG06 PM26789
DSNAOG28 PM26789
DSNAOG08 PM26789
DSNAOG0A PM26789
DSNAOG1S PM26789
DSNAOG0C PM26789
DSNAOG0E PM26789
DSNAOG0I PM26789
DSNAOG0J PM26789
DSNAOG0O PM26789
DSNAOG1W PM26789
DSNAOG25 PM26789
DSNAOG0Q PM26789
DSNAOG0R PM26789
DSNAOG27 PM26789
DSNAOG0S PM26789
DSNAOG26 PM26789
DSNAOG0U PM26789
DSNAOG22 PM26789
DSNAOG0W PM26789
1 DSNAOG13 PM26789
DSNAOG14 PM26789
DSNAOG15 PM26789
DSNAOG16 PM26789
DSNAOG1V PM26789
DSNAOG17 PM26789
DSNAOG1U PM26789
DSN@LIC1 PM26789
DSN@LIMS PM26789
DSN@LINF PM26789
DSN@LIQR PM26789
DSN@LIV1 PM26789
DSNAOCLI PM26789
DSNAOSDK PM26789
DSNAOTRC PM26789
DSNAOC0G PM26789
DSNAOC0F PM26789
DSNAOC21 PM26789
DSNAOC0P PM26789
DSNAOC07 PM26789
DSNAOG0G PM26789
DSNAOG0F PM26789
DSNAOG21 PM26789
DSNAOG0P PM26789
DSNAOG07 PM26789
DSNAOC1L PM26789
DSNAOG1L PM26789
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM26789 DSNAOC24 DSNAOC03 DSNAOC06 DSNAOC28 DSNAOC27 DSNAOC22
DSNAOC14 DSNAOC15 DSNAOC1U DSNAOG02 DSNAOG24 DSNAOG03
DSNAOG04 DSNAOG1R DSNAOG05 DSNAOG06 DSNAOG28 DSNAOG08
DSNAOG0A DSNAOG1S DSNAOG0C DSNAOG0E DSNAOG0I DSNAOG0J
DSNAOG0O DSNAOG1W DSNAOG25 DSNAOG0Q DSNAOG0R DSNAOG27
DSNAOG0S DSNAOG26 DSNAOG0U DSNAOG22 DSNAOG0W DSNAOG13
DSNAOG14 DSNAOG15 DSNAOG16 DSNAOG1V DSNAOG17 DSNAOG1U
DSN@LIC1 DSN@LIMS DSN@LINF DSN@LIQR DSN@LIV1 DSNAOCLI
DSNAOSDK DSNAOTRC DSNAOC0G DSNAOC0F DSNAOC21 DSNAOC0P
DSNAOC07 DSNAOG0G DSNAOG0F DSNAOG21 DSNAOG0P DSNAOG07
DSNAOC1L DSNAOG1L
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC24
DSNAOC03
DSNAOC06
DSNAOC28
DSNAOC27
DSNAOC22
DSNAOC14
DSNAOC15
DSNAOC1U
DSNAOG02
DSNAOG24
DSNAOG03
1 DSNAOG04
DSNAOG1R
DSNAOG05
DSNAOG06
DSNAOG28
DSNAOG08
DSNAOG0A
DSNAOG1S
DSNAOG0C
DSNAOG0E
DSNAOG0I
DSNAOG0J
DSNAOG0O
DSNAOG1W
DSNAOG25
DSNAOG0Q
DSNAOG0R
DSNAOG27
DSNAOG0S
DSNAOG26
DSNAOG0U
DSNAOG22
DSNAOG0W
DSNAOG13
DSNAOG14
DSNAOG15
DSNAOG16
DSNAOG1V
DSNAOG17
DSNAOG1U
DSNAOCLI
DSNAOTRC
DSNAOC0G
DSNAOC0F
DSNAOC21
DSNAOC0P
DSNAOC07
DSNAOG0G
DSNAOG0F
DSNAOG21
DSNAOG0P
DSNAOG07
DSNAOC1L
DSNAOG1L
MACROS
DSN@LIC1
DSN@LIMS
DSN@LINF
DSN@LIQR
DSN@LIV1
DSNAOSDK
LISTEND
UK72803 COVER LETTER END
1
UK72809 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46208 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of trusted context *
* *
****************************************************************
* PROBLEM DESCRIPTION: DSNE137I message received *
* intermittently when the user should *
* be allowed to switch in the trusted *
* connection *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSNE137I message was received intermittently when the
TSO command DSN ASUSER keyword was specified to switch
user in the trusted connection.
The message like the following was received, when the switch
user should be allowed:
DSNE137I YOU ARE NOT AUTHORIZED TO CONNECT TO DB2 ASUSER USER1
SQLCODE -20371 may also be received in a trusted connection,
when the user should be allowed to switch.
The trusted context switch user algorithm did not consider all
the users allowed to switch in a trusted connection, which
resulted in the error.
The trusted context switch user algorithm has been changed to
consider all the users defined for the trusted context.
Additional keywords: SQLCODE20371 MSGDSNE137I SQLTRUSTED
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46208
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXATUM PM46208
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46208 DSNXATUM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXATUM
LISTEND
UK72809 COVER LETTER END
1
UK72834 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46777 -
****************************************************************
* USERS AFFECTED: None. This is a fix for an internal *
* undocumented serviceability item. *
****************************************************************
* PROBLEM DESCRIPTION: Fix for an undocumented service feature *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Fix for an undocumented service feature.
Fix for an undocumented service feature.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46777
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBMF PM46777
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46777 DSNIDBMF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBMF
LISTEND
UK72834 COVER LETTER END
UK72870 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49212 -
****************************************************************
* USERS AFFECTED: All users of the DSNJU004 Print Log Map *
* utility in data sharing mode. *
****************************************************************
* PROBLEM DESCRIPTION: The DSNJU004 utility may issue *
* MSGDSNJ434I when the SYSIN input *
* specifies MEMBER *, and the utility *
* output will only contain information *
* from the BSDS specified on the *
* GROUP DD statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using the TRAPS NAME(IGVINITGETMAIN) parm in the system
DIAGxx PARMLIB member, the DSNJU004 Print Log Map utility may
issue DSNJ434I DSNJU004 SYSIN MUST CONTAIN AT LEAST ONE RECORD
when SYSIN specifies MEMBER *. The DSNJU004 output will only
contain information from the BSDS specified on the GROUP DD
1 statement. This is due to an uninitialized variable.
When running the DB2 Version 9.1 DSNJU004 utility, the
MEMBER * output may not include the archive log data set
entries and may fail with RC16 and:
DSNJ201I DSNJU004 PRINT LOG UTILITY PROCESSING WAS UNSUCCESSFUL
DSNJU004 has been changed to initialize the variables.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49212
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 PM49212
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49212 DSNJU004
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJU004
LISTEND
UK72870 COVER LETTER END
UK72880 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46337 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Page parity error - MSGDSNT500I with *
* reason code RC00C200FD - on a page in *
* a table space or index with a 32K page *
* size. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In data sharing, it is possible for one member to be reading a
32K page from DASD concurrently with another member writing the
page. This can result in a page parity error if the read comes
back with one half of the page newer than the other. DB2 has
logic to detect this and reissue the read, but it doesn't
handle the case where the page originally had a zero LRSN (i.e.
the page was formatted by a LOG NO utility).
The page read logic has been modified to correctly redrive the
read of a 32K page when a parity error is encountered.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46337
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 DSNB5RDP PM46337
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46337 DSNB5RDP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5RDP
LISTEND
UK72880 COVER LETTER END
UK72946 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47333 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of Spatial support. *
****************************************************************
* PROBLEM DESCRIPTION: This apar provides several new *
* functions to retrieve the current *
* and surrounding grid cell from a *
* starting point. After applying *
* this apar, there is one new load *
* module named DSN5SBIG. Two last steps *
* of DSN5SENB are used for creating *
* and binding for the new functions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar provides the function DB2GSE.IDXKEY2D to retrieve
the current and surrounding grid cells from a starting point.
Examples about using the function:
1-
The following statement invokes the function to retrieve the
grid cells of the POINTS object, 'SYSADM' is the schema name
and 'PTIDX2' is the index name of the Spatial index of the
POINTS column.
SELECT DB2GSE.IDXKEY2D(POINTS,'SYSADM','PTIDX2')
FROM SYSADM.POINTS;
2-
The following statement invokes the function to retrieve
8 surrouding grid cells:
WITH DTOTAL (GRIDNO1, GRIDNO2, GRIDNO3, GRIDNO4, GRIDNO5,
GRIDNO6, GRIDNO7, GRIDNO8) AS
(SELECT T.GRID1, T.GRID2, T.GRID3, T.GRID4,
T.GRID5, T.GRID6, T.GRID7, T.GRID8
FROM TABLE (DB2GSE.IDXKEY2D( 4294967297) ) T
)
SELECT GRIDNO1, GRIDNO2, GRIDNO3, GRIDNO4, GRIDNO5, GRIDNO6,
GRIDNO7, GRIDNO8 FROM DTOTAL;
1
3-
The following statement invoke the function to return
9 surrounding grids:
SELECT T.GRIDCENTRAL ,
T.GRID1, T.GRID2, T.GRID3, T.GRID4,
T.GRID5, T.GRID6, T.GRID7, T.GRID8
FROM TABLE
(DB2GSE.IDXKEY2D( DB2GSE.ST_POINT( 10,21, 1) , 1) ) T ;
4-
The following statement invoke the function to retrieve
3 layers of the surrounding grids:
SELECT T.* FROM TABLE (DB2GSE.IDXKEY2D( 4294967297 ,3) ) T;
COMPONENT: 5655-R1402-J2AG210
APARS FIXED: PM47333
SPECIAL CONDITIONS:
COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This apar provides the functions to retrieve the current
and surrounding grid cells from a starting point.
For the existing users, if they like to use this function
then submit 2 last steps: CREATE01 and BINDSK19 of
DSN5SENB job.
For the new users should follow the instructions contained
in the book
IBM Spatial Support for DB2 z/OS to enable Spatial
functionality.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@SK19 PM47333
DSN5SDEN PM47333
DSN5SENB PM47333
DSN5SK20 PM47333
DSN5SK21 PM47333
DSN5SK28 PM47333
DSN5SK29 PM47333
DSN5SK30 PM47333
J2AG210J PM47333
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47333 DSN@SK19 DSN5SDEN DSN5SENB DSN5SK20 DSN5SK21 DSN5SK28
DSN5SK29 DSN5SK30 J2AG210J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN5SDEN
DSN5SK20
DSN5SK21
DSN5SK28
DSN5SK29
1 DSN5SK30
MACROS
DSN@SK19
DSN5SENB
LISTEND
UK72946 COVER LETTER END
UK72958 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47264 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of the DB2 stored procedure *
* SYSPROC.ADMIN_INFO_SYSLOG *
****************************************************************
* PROBLEM DESCRIPTION: When SYSPROC.ADMIN_INFO_SYSLOG *
* is called, it returns the following *
* error message: *
* DSNA635I DSNADMIL AN INTERNAL ERROR *
* OCCURRED. Wrong number of *
* parameters 8. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
Afer APAR PM39997 is applied, the REXX ARG() function now
returns a value that is one less than before.
Without APAR PM39997 applied, ADMIN_INFO_SYSLOG receives
the value 9 from the REXX ARG() function. After APAR PM39997
is applied, ADMIN_INFO_SYSLOG receives the value 8 from the
REXX ARG() function.
ADMIN_INFO_SYSLOG is modified to check for 8 parameters,
instead of 9, and to use the REXX ARG() function to get
the argument index of the NULL indicator passed to it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47264
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNADMIL PM47264
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47264 DSNADMIL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNADMIL
LISTEND
UK72958 COVER LETTER END
1
UK72974 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48011 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of subqueries. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may select an inefficient access *
* path for a query with subqueries that *
* is correlated to multiple tables, or *
* with a correlated subquery predicate *
* under a non-boolean term predicate. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may produce an inaccurate cost estimation for a query with
subquery that is correlated to multiple tables or with a
subquery predicate under a non-boolean term predicate.
As a result, DB2 may select an inefficient access path for
the query. In particular, DB2 may select an access path
with Sort Merge Join.
For example,
SELECT *
FROM T1, T2
WHERE T1.C1 = T2.C1
AND EXISTS(
SELECT 1
FROM T3
WHERE T3.C2 = T1.C2
AND T3.C3 = T2.C3);
The above query contains a subquery that is correlated both T1
and T2 in its parent query block. DB2 may select an inefficient
access path for the above query due to the inaccurate cost
estimation problem.
Additional Keywords:
SQLACCESSPATH SQLSUBQUERY SQLPERFORMANCE SQLSMJ SMJ SQLMSJ MSJ
Code has been modified to provide a more accurate cost
estimation for queries described as above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48011
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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
or with a correlated subquery predicate under a non-boolean
1 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCSM PM48011
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48011 DSNXOCSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSM
LISTEND
UK72974 COVER LETTER END
UK72985 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46175 -
****************************************************************
* USERS AFFECTED: DB2 users using commands while the command *
* process abends. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 occured in the recovery retry *
* of DSN9SCN7, DSN9SCN8, DSN9SCN0, or *
* DSN9SCNF. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Most of DB2 command process logic is running in a 32bits
addressing space. When the command processor invokes other
DB2 logic running in a 64bits address space, high words
of special registers, such as stack register, code
register and stat register, may contain residual values.
If DB2 abends outside of the command processor, it will
retry with incorrect special registers and cause 0C4 abends.
DB2 command process logic has been modified to restore
special registers before recovery retry.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46175
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN9SCNF PM46175
DSN9SCN0 PM46175
DSN9SCN7 PM46175
DSN9SCN8 PM46175
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46175 DSN9SCNF DSN9SCN0 DSN9SCN7 DSN9SCN8
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN9SCNF
DSN9SCN0
DSN9SCN7
DSN9SCN8
LISTEND
UK72985 COVER LETTER END
UK73058 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47094 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* RUNSTATS utility users with index on *
* expression. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect authorization checking causes *
* DSNU619I to be issued. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When the user executed RUNSTATS REPORT YES utility on an index
on expression, the utility incorrectly issued MSGDSNU619I -
'USER auth_id DOES NOT HAVE PRIVILEGE ON TABLE table_name'.
The message was issued due to an incorrect authorization
check.
This problem can occur during inline STATISTICS execution
as well.
Code was changed to correctly perform the authorization
check for the object.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47094
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSPKD PM47094
DSNUSUKD PM47094
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47094 DSNUSPKD DSNUSUKD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSPKD
1 DSNUSUKD
LISTEND
UK73058 COVER LETTER END
UK73079 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46555 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: SYSIBM.SYSTABLESPACESTATS.TOTALROWS *
* shows a higher value than the actual *
* number of rows in the table space. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
The problem can occur due to an update of an overflow record.
If the update increases the size of the overflow record, so that
the record needs to be moved to another data page, the
compensation operations in case of an abort can lead to an
increase of the TOTALROWS counter.
The real-time statistics rollback logic was changed.
This APAR does not modify any existing TOTALROWS values.
In oder to correct TOTALROWS for table spaces that are affected
by this problem, REORG needs to be run after applying fix.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46555
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 PM46555
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46555 DSNIBHUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBHUN
LISTEND
UK73079 COVER LETTER END
UK73137 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM44216 -
****************************************************************
* USERS AFFECTED: All DB2 users who create tables with XML *
* columns. *
****************************************************************
1 * PROBLEM DESCRIPTION: PM44216 adds new subsystem parameter *
* XML_RANDOMIZE_DOCID which specifies *
* that the DOCIDs for tables that *
* are created with XML columns can *
* be generated in random order *
* instead of sequentially. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 9 for z/OS, PM44216 adds new subsystem parameter
XML_RANDOMIZE_DOCID which indicates whether the DOCIDs for
tables that are created with XML columns are to be generated in
random order instead of sequentially.
Tables with XML columns and DOCIDs generated in random order
may have a performance benefit when concurrent users are
inserting XML simultaneously.
The new function takes effect when the DSNZPARM module is
reassembled with XML_RANDOMIZE_DOCID=YES and put into effect.
Tables created after XML_RANDOMIZE_DOCID is set to YES will
get DOCIDs generated in random order. Tables created prior
to applying this PTF, and tables created with
XML_RANDOMIZE_DOCID set to NO will continue to have DOCIDs
generated in sequential order.
The default value of XML_RANDOMIZE_DOCID is NO, which
provides the same behavior for generating DOCIDs that DB2
has without applying this PTF. In other words, applying
this PTF will have no effect unless XML_RANDOMIZE_DOCID
is set to YES.
In DB2 10 for z/OS, APAR PM31487 adds the XML_RANDOMIZE_DOCID
subsystem parameter but requires DB2 10 for z/OS new-function
mode in order to create table with DOCIDs that are generated in
random order. APAR PM44216 allows tables with DOCIDs that are
generated in random order to be created in DB2 10 for z/OS
conversion mode after migration from DB2 9 for z/OS.
PRECONDITIONING APAR CONSIDERATIONS:
This APAR requires support from one or more preconditioning
APARs according to the DB2 version and whether the environment
is data sharing.
* DB2 9 for z/OS: A prerequisite for this APAR is UK72542,
the PTF for preconditioning APAR PM44210. On DB2 for z/OS
data sharing systems, apply PTF UK72542 to -all- V9 members
of the group before applying the fix for this APAR to -any-
member if all of the following are true:
- DB2 is running in V9 new-function mode
- You will set the XML_RANDOMIZE_DOCID parameter to YES
- You will be creating tables with XML columns
* DB2 10 for z/OS: A prerequisite for this APAR is UK68722,
the PTF for preconditioning APAR PM31486. On DB2 for z/OS
1 data sharing systems, apply PTF UK68722 to -all- V10 members
of the group before applying the fix for this APAR to -any-
member if all of the following are true:
- DB2 is not running in V10 new-function mode
- You have set or will set the XML_RANDOMIZE_DOCID parameter
to YES
- You will be creating tables with XML columns
* DB2 data sharing systems that are in coexistence mode during
migration from DB2 9 for z/OS to DB2 10 for z/OS: Apply PTF
UK72542 to -all- V9 members of the group and apply PTF UK68722
to -all- V10 members of the group before applying the fix for
this APAR to -any- member if all of the following are true:
- You have set or will set the XML_RANDOMIZE_DOCID parameter
to YES
- You will be creating tables with XML columns
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM44216
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
PM44216 is an enabling APAR that includes additional support
for the subsystem parameter XML_RANDOMIZE_DOCID (added by
APAR PM31487). The additional support is enabled when
XML_RANDOMIZE_DOCID is set to YES.
Users who are not creating tables with XML columns on
data-sharing systems will not be affected by PM44210/PM44216.
For users who will create new tables with XML columns in
a data-sharing group and intend to enable the parameter
XML_RANDOMIZE_DOCID, the pre-conditioning APAR PM44210
for DB2 9 for z/OS and the pre-conditioning APAR PM31486
for DB2 10 for z/OS must be applied to all data-sharing
members before enabling APAR PM44216 is applied to any member.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICQ1 PM44216
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM44216 DSNXICQ1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICQ1
LISTEND
UK73137 COVER LETTER END
UK73147 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PM47899 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of CHECK DATA *
* utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNUKIFK:53C6 *
* during CHECK DATA utility against a *
* table with a varying length foreign *
* key. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
The CHECK DATA utility was run on a table with a varying length
foreign key. During the referential constraint checking, a
local pointer was used to address the varying length column of
the key. After processing a full buffer and returning to the RI
checking, the pointer was no longer valid, causing the utility
to abend with ABEND04E RC00C90101 in DSNUKIFK ERQUAL:53C6.
CHECK DATA utility is changed to maintain addressability to the
varying length column of the foreign key.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47899
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUKGET PM47899
DSNUKIFK PM47899
DSNUKREL PM47899
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47899 DSNUKGET DSNUKIFK DSNUKREL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUKGET
DSNUKIFK
DSNUKREL
LISTEND
UK73147 COVER LETTER END
UK73165 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47687 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the LOAD *
* ENFORCE CONSTRAINTS utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 DSNUGSDA +x'5298' RC11 or *
* ABENDS0C4 DSNURRRI +x'1658' RC11 during *
* a restart of a LOAD ENFORCE CONSTRAINTS *
* DISCARDS n in the ENFORCE phase. *
1 ****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD ENFORCE CONSTRAINTS DISCARDS n with parallel index
build abended with an ABEND04E RC00E40323 and MSGDSNU317I -
DISCARD LIMIT HAS BEEN REACHED. The DISCARD value was changed
to DISCARDS 0 to allow unlimited discards, and the LOAD was
restarted. The LOAD restarted in the ENFORCE phase but abended
with an ABEND0C4 in either DSNUGSDA + x'5298' or
DSNURRRI + x'1658'.
The DSNUGSDA abend occurred because the SORTOUT data set
checkpoint control block was not built correctly during the
initial LOAD resulting in problems during the restart. This
problem is specific to parallel index build processing.
The DSNURRRI abend occurred due to incorrect addressability to
a checkpoint control block used in record positioning when
rectifying referential integrity errors for a table in a
segmented table space (non-UTS, non-partitioning).
Additional symptoms: DSNU317I REASON=00000011
Code has been modified to correct the problems with the
checkpoint control blocks used during LOAD restart processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47687
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM47687 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
DSNURPIB PM47687
DSNURRRI PM47687
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47687 DSNURPIB DSNURRRI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURPIB
DSNURRRI
1
LISTEND
UK73165 COVER LETTER END
UK73178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48862 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG TABLESPACE utility. *
****************************************************************
* PROBLEM DESCRIPTION: Inaccurate estimated log count during *
* REORG LOG apply processing resulted in *
* DEADLINE termination with MSGDSNU374I *
* on a PBG table space *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a REORG TABLESPACE SHRLEVEL CHANGE against a
partitioned by growth ( PBG ) table space. At the start of the
LOG phase, REORG came up with an inaccurate estimate of the
number of log records to be applied, which led to a DEADLINE
termination with DSNU374I - REORG WITH SHRLEVEL REFERENCE OR
CHANGE HAS BEEN TERMINATED, REASON=2.
Incorrect program logic resulted in an over-estimate of the
number of log records to be applied for a PBG table space.
This problem does not occur when REORG is operating on a subset
of the PBG partitions.
Code has been modified to better estimate the number of log
records to be applied on a REORG of a PBG table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48862
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGEST PM48862
DSNURLOG PM48862
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48862 DSNUGEST DSNURLOG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGEST
DSNURLOG
LISTEND
UK73178 COVER LETTER END
UK73180 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM37057 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically where a DB2 10 for z/OS server *
* is accessed by remote clients using SSL *
* client (mutual) authentication. *
****************************************************************
* PROBLEM DESCRIPTION: Additional enhancements to *
* DB2 10 for z/OS digital certificate *
* authentication support. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 10 for z/OS implemented the preliminary support to enable
remote clients to access DB2 using digital certificates. In the
z/OS digital certificate environment, the Secure Socket Layer
(SSL) client (mutual) authentication security protocol
identifies and authenticates the remote client when it presents
its certificate as identification and its proof-of-possession
(of the certificate) as authentication.
Note: Traditional remote client applications authenticate
themselves to DB2 by presenting their user ID and password.
Thus, the client's user ID and password provide
identification and authentication.
The client certificate is registered and stored in certificate
profiles in RACF. Each certificate is associated with a RACF
user ID. When a secure connection is established between the
client and DB2, the RACF user ID associated with the client
certificate is known to DB2. During DB2 remote connection
authentication processing, if the remote client's user ID is
not the same as the user ID associated with the certificate,
DB2 needs to give special considerations when authenticating
the remote client that is attempting to access DB2 using a
digital certificate.
DB2 10 for z/OS remote connection authentication processing has
been enhanced to ensure remote client's that accesses DB2 using
a digital certificate are properly authenticated when the
remote client user ID is different from the certificate user ID.
To implement client access to DB2 using a digital certificate,
users need to define a trusted context at the DB2 server where
the system authorization ID is set to the value of the user ID
associated with the client certificate. The trusted context
would need to include all the user IDs that are allowed to use
it (such as, remote client user IDs or the mapped user IDs if
z/OS identity name filtering is configured).
Example: A client certificate is registered to RACF and it is
associated with user ID, CERTID01. A remote client application
is configured to access DB2 using a digital certificate and
its user ID provided to DB2 is USER01. To define the trusted
context at the DB2 server, users might consider the following
sample DDL:
CREATE TRUSTED CONTEXT CTXT1
BASED UPON CONNECTION USING CERTID01
NO DEFAULT ROLE ENABLE
1 ATTRIBUTES(ADDRESS '1.2.3.4')
WITH USE FOR USER01;
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM37057
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM37057 (V10):
This APAR/PTF provides additional enhancements to the
DB2 10 for z/OS support for client access using a digital
certificate.
DB2 10 for z/OS remote connection authentication processing has
been enhanced to ensure remote client's that accesses DB2 using
a digital certificate are properly authenticated when the
remote client user ID is different from the certificate user ID.
To implement client access to DB2 using a digital certificate,
users need to define a trusted context at the DB2 server where
the system authorization ID is set to the value of the user ID
associated with the client certificate. The trusted context
would need to include all the user IDs that are allowed to use
it (such as, remote client user IDs or the mapped user IDs if
z/OS identity name filtering is configured).
Example: A client certificate is registered to RACF and it is
associated with user ID, CERTID01. A remote client application
is configured to access DB2 using a digital certificate and
its user ID provided to DB2 is USER01. To define the trusted
context at the DB2 server, users might consider the following
sample DDL:
CREATE TRUSTED CONTEXT CTXT1
BASED UPON CONNECTION USING CERTID01
NO DEFAULT ROLE ENABLE
ATTRIBUTES(ADDRESS '1.2.3.4')
WITH USE FOR USER01;
See PM37057 APAR/PTF text for additional information.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTSEC PM37057
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM37057 DSNLTSEC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTSEC
LISTEND
UK73180 COVER LETTER END
UK73264 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PM46255 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, DB2 9 and DB2 10 *
* DRDA / DDF users who use remote binds *
* with zparm DRDA_RESOLVE_ALIAS = YES. *
****************************************************************
* PROBLEM DESCRIPTION: Abend ABEND0C4 DSNXOFCR+04D2 *
* may occur for an SQL statement *
* during a remote bind with zparm *
* DRDA_RESOLVE_ALIAS=YES *
* that references to a qualified *
* column name with an undefined *
* table qualifier. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend ABEND0C4 DSNXOFCR+04D2 may occur for an SQL statement
during a remote bind with zparm DRDA_RESOLVE_ALIAS=YES
that references to a qualified column name with an undefined
table qualifier.
For Example,
CREATE TABLE TB1 (C1 CHAR(20));
SELECT T1.C1 FROM TB1 T2;
The above statement may cause an abend during the remote bind
because the column T1.C1 is undefined.
DB2 was fixed to remove the abend during the remote bind for
SQL statement that references to a qualified column name with
an undefined table qualifier.
Additional Keywords: SQLDRDA DB2DRDA
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46255
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOFCR PM46255
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46255 DSNXOFCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOFCR
LISTEND
UK73264 COVER LETTER END
UK73432 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM49779 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of REBUILD INDEX *
****************************************************************
* PROBLEM DESCRIPTION: REBUILD INDEX SHRLEVEL CHANGE results *
* in ABEND0C4 RC11 from DSNUCLAX *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REBUILD INDEX SHRLEVEL CHANGE was run. While processing the
current log record, an invalid pointer was referenced and
resulted in the ABENDS0C4.
REBUILD INDEX has been changed to use the appropriate index key
pointer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49779
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 PM49779
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49779 DSNUCLAX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCLAX
LISTEND
UK73432 COVER LETTER END
UK73436 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM37646 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 9.1 for z/OS *
* ODBC/CLI and DB2 10 for z/OS ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: Calling SQLGetData() to fetch UNICODE *
* CLOB column data in pieces into a *
* buffer of C type SQL_C_CHAR or *
* SQL_C_WCHAR fails with SQLSTATE=01004 *
* SQLCODE=-99999 ERRLOC=1:77:1 or *
* SQLCODE=-189 when the application is *
* connected to a DB2 for z/OS server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQLGetData() can be called repeatedly to fetch long data in
pieces. When fetching from a UNICODE CLOB column and the C
1 data type specified on the SQLGetData() call is SQL_C_CHAR or
SQL_C_WCHAR, the function fails with SQLSTATE=01004
SQLCODE=-99999 ERRLOC=1:77:1 or SQLCODE=-189, along with
a CUNLCNV error message in the output indicating that the
target buffer was exhausted before all characters in the source
buffer were converted. An example of the CUNLCNV error message
is shown below:
CUNLCNV character conversion routine failed.
Source CCSID = 1208
Target CCSID = 1200
Warning -
The target buffer was exhausted before all
characters in the source buffer were converted.
Bytes not yet converted: 31.
SQLGetData() has been changed so that UNICODE CLOB data
can be fetched in pieces into UNICODE buffers of C type
SQL_C_CHAR or SQL_C_WCHAR when the application is
connected to a DB2 for z/OS server.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PM37646
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 PM37646
DSNAOG27 PM37646
DSNAOCLI PM37646
DSNAOSDK PM37646
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM37646 DSNAOC27 DSNAOG27 DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC27
DSNAOG27
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UK73436 COVER LETTER END
UK73478 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM35190 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Provide the ability to SELECT from *
* directory tables SYSIBM.SYSLGRNX, *
1 * SYSIBM.SYSUTILX and SYSIBM.SYSUTIL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides support for SQL SELECT from directory tables
SYSIBM.SYSLGRNX, SYSIBM.SYSUTIL and SYSIBM.SYSUTILX.
This capability and the resulting output is primarily
intended for use by IBM support.
The following restrictions apply:
- The authorization rules that apply for selects against
the catalog also apply for selects against Directory
objects. The authority must include one of the following:
- Install SYSADM
- SYSADM
- SYSCTRL
- ACCESSCTRL
- DATAACCESS
- SECADM
- SQLADM
- System DBADM
- DBADM on DSNDB01
- select on a specific table
- Only SELECT and FETCH are permitted.
- No transaction L-locks will be acquired regardless of
application isolation level.
The example for the SQLCODE -607 has been enhanced with the
following:
- The operation is on a directory object and the unit of work
could not be converted to UR. For example: UPDATE T1 SET C1 =
(SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX); In
this case, the SELECT against a directory object can not be
converted to UR.
The ability to SELECT from Directory objects is enabled when NFM
(New Function Mode) is entered. The ability to SELECT from the
Directory objects is not enabled in a new install. For a new
install or if DB2 is already in NFM when apar is applied it can
be enabled by running a utility job:
CATMAINT UPDATE UNLDDN PM35190
To verify if the ability to SELECT from Directory objects has
been enabled, a row will be returned from the following SELECT:
SELECT * FROM SYSIBM.SYSDATABASE WHERE DBID=1;
DSNTESQ has been updated to support this change. Without this
APAR query7 may return rows for DBNAME DSNDB01.
***Action for PM35190:
See PM35190 APAR/PTF text for additional information.
This APAR/PTF changes the text of SQL code -607. The change
1 will be documented in the DB2 Codes manual and in the
Information Management Software for z/OS Solutions Information
Center.
A new bullet under the example for SQL code -607:
- The operation is on a directory object and the unit of work
could not be converted to UR. For example:
UPDATE T1 SET C1 =
(SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX);
in this case, the SELECT against a directory object can not
be converted to UR.
***Action for PM35190:
See PM35190 APAR/PTF text for additional information.
PM35190 is the enabling APAR that introduces the new function
support to allow selects from some Directory objects. Earlier,
a pre-conditioning APAR PM42331 was delivered and will be
needed. In a data sharing group, this pre-conditioning APAR
should be applied to all members before applying this ENABLING
APAR to any member. The new function will be enabled once this
ENABLING APAR is applied and DB2 enters NFM or once this
ENABLING APAR is applied and a special CATMAINT is run with the
input:
CATMAINT UPDATE UNLDDN PM35190
See above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM35190
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
***Action for PM35190:
See PM35190 APAR/PTF text for additional information.
PM35190 is the enabling APAR that introduces the new function
support to allow selects from some Directory objects. Earlier,
a pre-conditioning APAR PM42331 was delivered and will be
needed. In a data sharing group, this pre-conditioning APAR
should be applied to all members before applying this ENABLING
APAR to any member. The new function will be enabled once this
ENABLING APAR is applied and DB2 enters NFM or once this
ENABLING APAR is applied and a special CATMAINT is run with the
input:
CATMAINT UPDATE UNLDDN PM35190
DOCUMENTATION:
***Action for PM35190:
1 See PM35190 APAR/PTF text for additional information.
This APAR/PTF changes the text of SQL code -607. The change
will be documented in the DB2 Codes manual and in the
Information Management Software for z/OS Solutions Information
Center.
A new bullet under the example for SQL code -607:
- The operation is on a directory object and the unit of work
could not be converted to UR. For example:
UPDATE T1 SET C1 =
(SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX);
in this case, the SELECT against a directory object can not
be converted to UR.
ACTION:
See PM47932 APAR/PTF text for additional information.
This PTF fixes the default maximum number of databases that can
be created implicitly.
Applying this PTF will not remove existing implicit databases
or update the current maximum number of implicit databases
allowed.
You can use the following query to find out the current maximum
number of implicit databases allowed:
SELECT MAXVALUE FROM SYSIBM.SYSSEQUENCES
WHERE SCHEMA = 'SYSIBM'
AND NAME = 'DSNSEQ_IMPLICITDB';
You can use the following statement to alter it:
ALTER SEQUENCE SYSIBM.DSNSEQ_IMPLICITDB MAXVALUE <number>
This <number> can be DB2's new default value of 10000 or any
valid value as allowed by the ALTER SEQUENCE statement.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTESQ PM35190
DSNUECM0 PM35190
DSNUECSE PM35190
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM35190 DSNTESQ DSNUECM0 DSNUECSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECM0
DSNUECSE
MACROS
1 DSNTESQ
LISTEND
UK73478 COVER LETTER END
UK73534 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49742 -
****************************************************************
* USERS AFFECTED: Any DB2 for z/OS log record-processing tools *
* that rely on the log records to determine *
* the row format of a row *
****************************************************************
* PROBLEM DESCRIPTION: DB2 log records written during repeated *
* cross-partition update in a commit *
* scope can show an incorrect value for *
* the row format, whether (RRF) Reordered *
* Row Format or (BRF) Basic Row Format *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For SQL UPDATE operation that caused a row to switch to
another partition, followed by another SQL UPDATE of that same
row that forced a second partition switch (double overflow
condition) within the same commit scope, log records written
for any base sub-record (a.k.a. pointer record) changes were
not capturing the correct row format.
These log records that were incorrect include 'delete base
sub-record' log records as well as 'update base sub-record'
log records.
While the incorrect row format setting in a log record is not
a problem for any kind of log apply / recovery process, it can
be a problem for any tools that rely on the log record for
information on which row format the log record corresponds to.
DB2 code has been changed to determine the correct row format
when writing log records supporting double overflow condition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49742
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDLEO PM49742
DSNIREPR PM49742
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49742 DSNIDLEO DSNIREPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDLEO
1 DSNIREPR
LISTEND
UK73534 COVER LETTER END
UK73587 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46544 -
****************************************************************
* USERS AFFECTED: DB2 SYSPLEX query parallelism users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC0000003B IN DSNSVSVB *
* OFFSET +0DA2 can occur when DB2 *
* serializes storage requests of *
* multiple SYSPLEX parallel *
* tasks. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 allocates storage for the workfile OBD in the accumlating
agent's pool. If the accumulating agent is another parallel
task, not the parent task, DB2 hit the above abend, because the
accumlating agent storage pool can not be shared with other
parallel tasks.
DB2 has been changed to allocate storage for the workfile OBD
from the correct agent pool for a parallel task on the
assistant DB2 member.
additional keyword: SYSPLEX PARALLEL
SQLPARALLELISM DB2PARALL/K
PM51843 -
****************************************************************
* USERS AFFECTED: AE PM46544 fix completion *
****************************************************************
* PROBLEM DESCRIPTION: AE PM46544 fix completion *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PM46544 fix completion
AE PM46544 fix completion
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46544,PM51843
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCDB PM46544 PM51843
DSNGDCII PM51843
DSNGDCOB PM46544
DSNGDCOI PM46544
DSNGDDRT PM46544
DSNGDLOG PM46544
DSNTTRUN PM51843
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46544 DSNGDCDB DSNGDCOB DSNGDCOI DSNGDDRT DSNGDLOG
PM51843 DSNGDCDB DSNGDCII DSNTTRUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCDB
DSNGDCII
DSNGDCOB
DSNGDCOI
DSNGDDRT
DSNGDLOG
DSNTTRUN
LISTEND
UK73587 COVER LETTER END
UK73600 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48142 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 at DSNIZREP+'05DE'x during *
* BIND of an UPDATE on an old table *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While processing the BIND on an UPDATE statement on an old
table (created prior DB2 V3), addressability of a pointer was
not set properly before use of this pointer. As a result, an
an ABEND0C4 was encountered.
DB2 was modified to properly set a pointer before use.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48142
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIIMSI PM48142
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48142 DSNIIMSI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIIMSI
LISTEND
UK73600 COVER LETTER END
1UK73617 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46976 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS user who uses *
* LOB table space with GBPCACHE SYSTEM *
****************************************************************
* PROBLEM DESCRIPTION: Down level header page with message *
* DSNB232I was encountered when using *
* a LOB table space with GBPCACHE *
* SYSTEM. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For a LOB table space defined as GBPCACHE SYSTEM, DB2 does not
handle the header page consistently. Sometimes it is treated
as a "system" page, and sometimes not. This can result in
the
header page being written to both the GBP and to DASD, at
different levels. A subsequent open of the LOB space can read
an old version of the header page and fail with a down-level
detection error.
DB2 has been modified to treat the header page of a LOB with
GBPCACHE SYSTEM consistently as a "non-system" page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46976
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 PM46976
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46976 DSNOALLO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOALLO
LISTEND
UK73617 COVER LETTER END
UK73625 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM44892 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS user who uses Partition *
* by Growth table space and data versioning *
****************************************************************
* PROBLEM DESCRIPTION: The header hash bucket lock for *
* inserting system page information *
* into a partition which does not have *
* a free segment can possibly cause *
* performance degradation on a *
1 * Partition by Growth table space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The insert after ALTER Table which creates a new data version
requires the new version of the OBDREC to be inserted into the
system page. The target partition of the inserting data row
must have a free segment/page for the new system page.
The header page hash bucket lock is used to serialize
concurrent transactions inserting the same OBDREC into
a system page. However, when the target partition does
not have a free page/segment for the new OBDREC, the duration
of holding header page hash bucket lock while looking for
space in the other partition could possibly result in
performance degradation. This situation only occurs if
there are a high volume of concurrent transactions after
ALTER TABLE before REORG of the PBG table space.
DB2 code is changed to cache the information when a partition
does not have a free segment for a system page.
This information is saved after the first encounter of
"partition does not have free segment for system page"
during insert of system page process. Thereafter, any new
record that requires a new version number to be inserted
will be redirected to search space in another partition.
This is to reduce the use of header page hash bucket lock
on the partition that does not have the free segment for
the system page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM44892
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISRTI PM44892
DSNIVOBD PM44892
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM44892 DSNISRTI DSNIVOBD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISRTI
DSNIVOBD
LISTEND
UK73625 COVER LETTER END
UK73649 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48724 -
****************************************************************
* USERS AFFECTED: DB2 users turning off DASD IO logging *
* or using striped data sets *
1 ****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E2002F on DSNSVSFM *
* or ABEND04C ON DSNB5UTX *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar fixed two problems:
(1) DB2 DASD write logic may free the storage of
log buffers twice and cause abend. This only happens
when a page set status log record is needed and DASD IO
logging is turned off due to system environment setting.
(2) DB2 IO exit logic may get 0C4 abend when recovering from
previous abends. The recovery logic accesses a control block
when its basing pointer is not set. This IO exit logic is
seldom invoked. Striped data sets are exceptions.
DB2 DASD write logic has been modified to free the logging
storage correctly. DB2 IO exit logic was changed to set the
basing pointer before accessing the control block.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48724
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5COM PM48724
DSNB5UEX PM48724
DSNB5UTX PM48724
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48724 DSNB5COM DSNB5UEX DSNB5UTX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5COM
DSNB5UEX
DSNB5UTX
LISTEND
UK73649 COVER LETTER END
UK73663 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48865 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of virtual indexes. *
* *
* DB2 9 for z/OS and DB2 10 for z/OS users of *
* any of these EXPLAIN tables: *
* - DSN_FUNCTION_TABLE *
* - DSN_PREDICAT_TABLE *
* - DSN_QUERY_TABLE *
1 ****************************************************************
* PROBLEM DESCRIPTION: (1) While using virtual indexes on DB2 *
* 10 for z/OS, the following abend may *
* occur: *
* *
* - ABEND04E RC00C90101 in DSNIBCTD :5007 *
* *
* (2) When issuing a SELECT on *
* DSN_FUNCTION_TABLE or *
* DSN_PREDICAT_TABLE *
* SQLCODE -331 with reason 16 may be *
* issued. *
* *
* (3) While using EXPLAIN on a query *
* that has a GROUP BY with all literals, *
* the NODE_DATA column may show a GROUP *
* BY node with no GROUP BY items. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
(1) While using virtual indexes on DB2 10 for z/OS the following
abend may occur:
- ABEND04E RC00C90101 in DSNIBCTD :5007
(2) When issuing a SELECT on DSN_FUNCTION_TABLE or
DSN_PREDICAT_TABLE SQLCODE -331 with reason 16 may be issued.
The affected columns include FUNCTION_TEXT from
DSN_FUNCTION_TABLE, and TEXT and LITERALS from
DSN_PREDICAT_TABLE.
(3) While using EXPLAIN on a query that has a GROUP BY with all
literals, the NODE_DATA column may show a GROUP BY node with no
GROUP BY items.
An example that demonstrates this problem:
Query:
SELECT 'string' AS TEXT
FROM T1
GROUP BY 'string'
Output before fix:
...
<FROM-CLAUSE>
FROM
<TAB-REF TNO="1"
TYPE="T">SYSADM.T1</TAB-REF>
</FROM-CLAUSE>
<GROUP-BY>
GROUP BY
</GROUP-BY>
...
Output after fix:
1 ...
<FROM-CLAUSE>
FROM
<TAB-REF TNO="1"
TYPE="T">SYSADM.T1</TAB-REF>
</FROM-CLAUSE>
...
The above problems were caused by:
- incorrect handling of virtual indexes
- improper truncation of mixed data
- not checking for GROUP BY items
Additional keywords:
ABEND04E RC00C90101 DSNIBCTD ERQUAL5007 SQLCODE331 SQLEXPLAIN
DB2 code has been changed to:
(1) Fix the problem and not issue the abend
(2) Fix the problem for the FUNCTION_TEXT column of
DSN_FUNCTION_TABLE and the TEXT and LITERALS columns of
DSN_PREDICAT_TABLE so that the SQLCODE is not issued
(3) Fix the problem and not print out the GROUP BY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48865
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 are inserted into explain tables
DSN_FUNCTION_TABLE and DSN_PREDICAT_TABLE. As a result,
subsequent SELECTs on these tables received SQLCODE -331.
After applying this PTF, you must delete the rows that
are currently in the tables causing -331 to stop receiving
the SQL code.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODTX PM48865
DSNXOD2 PM48865
DSNXOD4 PM48865
DSNXORTS PM48865
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48865 DSNXODTX DSNXOD2 DSNXOD4 DSNXORTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODTX
DSNXOD2
DSNXOD4
DSNXORTS
LISTEND
1UK73663 COVER LETTER END
UK73677 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48219 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users *
* who use INSERT/UPDATE/DELETE/MERGE *
* statements within a SELECT statement *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E in DSNXOAF.DSNSVSVB+06CC *
* may occur for an INSERT/UPDATE/ *
* DELETE/MERGE statement that *
* references to a view and an OLAP *
* function within a SELECT *
* statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E in DSNXOAF.DSNSVSVB+06CC may occur for an
INSERT/UPDATE/DELETE/MERGE statement that references to
a view and an OLAP function within a SELECT statement.
For Example,
CREATE VIEW V1 AS SELECT * FROM T1;
SELECT * FROM FINAL TABLE (
UPDATE V1
SET C1 = 1
WHERE C2 =
(SELECT RANK() OVER (ORDER BY T2.C3)
FROM T2))
The abend may occur for the statement above because the storage
which is allocated to process the OLAP function is not freed
correctly.
DB2 was fixed to remove the abend when process the
UPDATE/INSERT/MERGE/DELETE statements that references to
a view and an OLAP function within a SELECT statement.
Additional Keywords: SQLRANK SQLDENSERANK SQLROWNUMBER OLAP
SQLVIEW SQLSELWINSERT SQLSELWUPDATE
SQLSELWMERGE SQLSELWDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48219
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOADT PM48219
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48219 DSNXOADT
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOADT
LISTEND
UK73677 COVER LETTER END
UK73691 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49541 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 users of CREATE or ALTER *
* PROCEDURE of a native SQL procedure. *
****************************************************************
* PROBLEM DESCRIPTION: The following error may occur during a *
* CREATE or ALTER PROCEDURE for a native *
* SQLPL procedure when the bind of an *
* SQL statement returns an SQLCODE +585 *
* (see details below). *
* . *
* ABEND0C4 RC00000038 at *
* DSNXGRDS . DSNXGTRE +0362 *
* . *
* or other offsets may occur *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For native SQL stored procedures, the CREATE or ALTER PROCEDURE
process automatically returns to the caller any SQL conditions
that should be externalized.
.
In the reported abend case, during the CREATE/ALTER PROCEDURE
the bind of an SQL statement within the SQLPL procedure issued
a negative SQLCODE and DB2 stored this condition to be returned
to the caller. However, on the bind of a subsequent SQL stmt
that required processing of an SQL PATH schema list, DB2 issued
SQLCDOE +585. For this internal SQL PATH processing, DB2 must
suppress the +585 but the suppression caused DB2 to incorrectly
restore the previous -SQLCODE, resulting in
AB0C4 RC00000038 at DSNXGTRE OFFSET362
during the bind of the SQL statement.
.
DB2 has been modified so that the accidental restore of a
previous condition is not done.
Additional keywords: SQLPROCEDURE SQLCODE585 SQLNATIVESQLPL
SQLSP SQLSTOREDPROC S0C4
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49541
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
DSNXEDWA PM49541
DSNXEPAR PM49541
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49541 DSNXEDWA DSNXEPAR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDWA
DSNXEPAR
LISTEND
UK73691 COVER LETTER END
UK73695 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50059 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: This is a service enhancement APAR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar provides service enhancement fixes.
DB2 code has been modified to enhance serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50059
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGCAL PM50059
DSNXGUDF PM50059
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50059 DSNXGCAL DSNXGUDF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGCAL
DSNXGUDF
LISTEND
UK73695 COVER LETTER END
UK73750 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49059 -
****************************************************************
1 * USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: After an MVS cancel, the following *
* abends may occur: *
* 1. ABEND0D5 in CSECT DSNVSRRX *
* 2. ABEND in CSECT DSNVEUS2 or DSNVSRX *
* during resume processing *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. DSNVSRRX pause release recovery does not properly account
for the absence of an EB. It may use a non-existent EB to
issue a SSAR in the non-DB2 suspend recovery path.
2. DSNVSRRX does not properly serialize a ROB swap after a
cancel. This may leave EBROB pointing to an incorrect ROB which
may lead to an ABEND for the resumer.
DSNVSRRX recovery has been corrected to
1. account for the absence of an EB and
2. serialize ROB swap processing to prevent
an incorrect ROB reference
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49059
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVSRRX PM49059
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49059 DSNVSRRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVSRRX
LISTEND
UK73750 COVER LETTER END
UK73797 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50507 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users who use *
* hash-organized tables. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may choose other suboptimal access *
* method for a hash-organized table, even *
* when hash access is the best access *
* method. *
* *
* For example, table T1 is hash-organized *
* on column (C1, C2). T1 has another *
1 * unique index UIX on column (C1, C2). *
* When T1's hash space does not overflow, *
* the hash access should provide better *
* query performance than UIX for the *
* folowing query: *
* *
* SELECT ... *
* FROM T1 *
* WHERE C1 = ? and C2 = ? *
* *
* However, DB2 may choose UIX over the *
* hash access method, leading to *
* suboptimal query performance. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Hash access is efficient for queries that use equal predicates
to access a single row on a table, especially when there is no
overflow in the hash space. However, DB2 may choose other access
method(s) instead of the hash access method, even when the
hash-organized table does not have an overflow in the hash
space. This problem is due to an incorrect calculation in the
DB2 optimizer to determine the cost of hash access.
The DB2 optimizer is modified to correct the calculation, to get
a more accurate cost estimation for hash access. As a result,
when there is no overflow in the hash space, hash access is
determined to have a lower cost than other access method(s), and
DB2 optimizer will prefer using hash access on the
hash-organized table for queries using equal predicates to
locate a single row.
Additional Keywords:
SQLACCESSPATH
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50507
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM50507:
See PM50507 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50507 corrects a problem of the DB2 optimizer in calculating
the cost of hash access for a hash-organized table. The
fix will get a more accurate estimation of hash access,
and enable the DB2 optimizer to choose hash access methods over
other suboptimal method(s).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
1 DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM45292 corrects a problem in which a DB2 intentional abend may
occur when a query contains the RID function.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPRS PM50507
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50507 DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPRS
LISTEND
UK73797 COVER LETTER END
UK73808 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47986 -
****************************************************************
* USERS AFFECTED: All users of DB2 9 OR DB2 10 (for z/OS). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND 04E RC00E20004 at *
* DSNIPSI . DSNSVBK +05FC *
* . *
* Other storage shortage abends possible. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In the reported case, an application that contained repeated
invocations of multi-row INSERT and MERGE SQLs encountered
DB2 storage related abends due to shortage of virtual storage
in DBM1 address space.
Visual examination of the dump storage mapping of the AGL
( Agent Local ) pool showed excessive number of blocks with
eyecatcher ' TLST '. DB2 allocates this internal control block
to keep track of nesting SQL restrictions. During processing
of multi-row INSERT and MERGE, this internal TLST control block
was allocated for every row processed and not freed later. This
led to proliferation of the internal TLST control blocks in DBM1
AGL pool storage leading up to the DB2 storage shortage.
DB2 code has been modified to correctly free the internal
TLST control block.
.
1 RELATED KEYWORDS: SQLSTORAGE ABEND04E AB04E 00E20004
GROWTH LEAK EXCESSIVE OFFSET05FC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47986
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXETCH PM47986
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47986 DSNXETCH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXETCH
LISTEND
UK73808 COVER LETTER END
UK73842 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50221 -
****************************************************************
* USERS AFFECTED: ALL DB2 USERS *
****************************************************************
* PROBLEM DESCRIPTION: ABEND MODULE DXRRL2R2:03 PM00614 *
* RETLOCK DETECTED INCOMPATIBLE *
* LOCK *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During group restart, DB2 was trying to request a
RETLOCK for SYSSEQUENCES table for multiple members,
and IRLM later detected incompatible lock.
Since DB2's mainline process does not acquire logical
locks when updating SYSSEQUENCES table, DB2 should
not reacquire logical locks for the same object
during group restart.
DB2's log apply routine is modified to avoid the
lock request for SYSSEQUENCES table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50221
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 PM50221
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50221 DSNIB
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIB
LISTEND
UK73842 COVER LETTER END
UK73863 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50361 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS executing a *
* statement which has range predicate(s) *
* that have values which are internally *
* cast and are indexable. *
****************************************************************
* PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE *
* FOLLOWING REPORTED SYMPTOMS: *
* *
* ABEND04E RC00E70005 *
* CSECT DSNXOIXP:P130 *
* *
* *
* PROBLEM SCENARIO: *
* *
* The reported abend occurs when *
* executing a statement which contain *
* range predicates that have to be cast *
* internally in DB2 for comparison and *
* are indexable. *
* *
* Here's an example: *
* *
* CREATE TABLE T1 ( *
* "C1" DECIMAL(10, 0) NOT NULL
*
* ,"C2" CHAR(1) FOR SBCS DATA NOT NULL
*
* ,"C3" DECIMAL(4, 0) NOT NULL
*
* , PRIMARY KEY ("C1",
*
* "C2"))
*
* *
* CREATE UNIQUE INDEX "IDX1"
*
* ON "T1" (
*
* "C1" ASC,
*
* "C2" ASC)
*
* *
* SELECT *
* C1, C2 *
* FROM T1 *
* WHERE C3 = 1000 *
* AND C1 > 9000000000 *
* AND C1 < 10000000000 *
* WITH UR FOR FETCH ONLY *
* *
1 * Note that C1 will be cast internally *
* by DB2 in order to compare an integer *
* to a decimal. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SUMMARY OF DB2 EVENTS:
Internally, DB2 did not correctly check all the predicate types
in the statement and as a result called a procedure that was
not able to handle the casting of the predicate.
PROBLEM CONCLUSION:
DB2 now checks all predicate types before calling the procedure.
ADDITIONAL KEYWORDS:
SQLLT SQLGT INDEXONLY INDEXPROBING
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50361
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM38744:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM38744 corrects a problem of inaccurate cost estimation for an
index on the inner table in a join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGBM PM50361
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50361 DSNXOGBM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBM
LISTEND
UK73863 COVER LETTER END
UK73908 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50893 -
1 ****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* REBUILD INDEX utility users. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 accessing an index after *
* REBUILD INDEX failed. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REBUILD INDEX failed during initialization without
resetting the index, and completed with RC=8. However,
the version number in OLDEST_VERSION was updated to
be the same as the current version for the index in
SYSIBM.SYSINDEXES and SYSIBM.SYSINDEXPART. This updating
of the version resulted in improper conversion to the
current version for existing keys in the index, and this
resulted in the ABEND0C4.
Another problem fixed with this apar is an ABEND0C4 in
DSNUSIDX offset '69d4'x when collecting inline statistics,
and message DSNU706I was received indicating that a row
was in the wrong table space partition.
If REBUILD INDEX doesn't complete successfully with RC=0
or RC=4, then avoid updating the catalog tables containing
the lowest version for the index.
If message MSGDSNU706I for a data row in the wrong partition
or message MSGDSNU340I for a duplicate key is issued, then
any keys associated with these errors will be bypassed
during statistics processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50893
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM50893 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCRIX PM50893
DSNUCTER PM50893
DSNURBXC PM50893
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PM50893 DSNUCRIX DSNUCTER DSNURBXC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCRIX
DSNUCTER
DSNURBXC
LISTEND
UK73908 COVER LETTER END
UK73938 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54089 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of the LOAD utility with *
* INDEXDEFER option *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40083 DSNUGASO + x'082A' *
* occurs when running LOAD utility with *
* INDEXDEFER ALL/NPI option into a table *
* in a non-partitioned table space *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When running LOAD utility with option INDEXDEFER ALL/NPI,
ABEND04E RC00E40083 at DSNUGASO OFFSET082A may occur on a
non-partitioned table space with indexes defined.
The abend happens because we check an internal structure
incorrectly. The internal structure is not set for LOAD with
option INDEXDEFER ALL/NPI into non-partitioned table space and
thus should not be checked.
DB2 utility code has been modified to check the internal
structure for LOAD with option INDEXDEFER ALL/NPI correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54089
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGASO PM54089
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54089 DSNUGASO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGASO
LISTEND
1UK73938 COVER LETTER END
UK73941 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50014 -
****************************************************************
* USERS AFFECTED: All IMS users of IRLM230 (HIR2230) SYSPLEXDS *
* DATASHARING. *
****************************************************************
* PROBLEM DESCRIPTION: IMS ABEND0C1 due to invalid branch from *
* IRLM Resume Exit in DXRRL110. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
An IMS lock request with the FORCE attribute may result in all
child locks belonging to a work unit, to be propagated to SLM.
The child prop request may get suspended in IRLM. Under certain
conditions if IRLM is not able to get the required internal
latches, it may not turn on the suspend indicators in the IMS
RLPL on return. IMS could re-use the RLPL if the suspend flags
are not set in the RLPL. Later, when IRLM tries to resume the
requester, it could cause ABEND0C1 because of an invalid
Resume Exit address in the RLPL.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
This APAR fixes the problem with copying back RLPL feedback
to IMS on a lock request that also results in child lock
propagation. IMS will suspend the caller correctly and this
will avoid getting an ABEND0C1 due to RLPL re-use.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM50014
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL121 PM50014
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50014 DXRRL121
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL121
LISTEND
UK73941 COVER LETTER END
UK73956 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47353 -
1 ****************************************************************
* USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) *
* users in DATASHARING SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS878 with reason code 08 occurred *
* because IRLM failed to release storage *
* for QE28s which it acquired from ECSA. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM received lots of messages from a terminating peer member.
For each receiving message, it sent back an acknowledgment by
obtaining storage from ECSA to build the responding QE. Since
the sending peer member had disconnected with the structure,
the acknowledgment QE could not be delivered to the sender.
Under such circumstance, IRLM failed to release the storage of
those acknowledgment QEs.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
If either the sending member or the receiving member is invalid,
the sending of the acknowledgment message will fail. In such
case, code is added to release the storage of the QE.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM47353
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL730 PM47353
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47353 DXRRL730
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL730
LISTEND
UK73956 COVER LETTER END
UK74004 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50727 -
****************************************************************
* USERS AFFECTED: All users of IFI monitor applications. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 may occur in CSECT DSNWVOPX *
* when a monitor application issues *
* a -STOP TRACE command on a trace with *
* an OP buffer destination. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
A timing window exists such that the OP buffer MBUF may be
cleared while another thread tracing data to that same OP buffer
is using the MBUF data for a cross-memory post. The zeroing of
MBUFACE may result in an ABEND0C4.
ABEND0C4's in CSECT DSNWVOPX in cross-memory post logic will
not result in a dump and will be retried.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50727
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWVFRR PM50727
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50727 DSNWVFRR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVFRR
LISTEND
UK74004 COVER LETTER END
UK74043 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50589 -
****************************************************************
* USERS AFFECTED: All DB2 z/OS v10 users of workfile. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS04E DSNISGSC ERQUAL500D occurred *
* during space search for an insert into *
* a workfile PBG table space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 performs a sanity check to ensure that the same segment
number is not used more than once. This check does not
include the partition number, which may cause a false
DSNISGSC ERQUAL500D when a WF PBG spans partitions.
DB2 code is modified to consider the Workfile condition
for the sanity check.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50589
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISGSC PM50589
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50589 DSNISGSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGSC
LISTEND
UK74043 COVER LETTER END
UK74044 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM43441 -
****************************************************************
* USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS *
* USERS OF LISTDEF UTILITY WITH THE LOB *
* KEYWORD SPECIFIED *
****************************************************************
* PROBLEM DESCRIPTION: OBJECTS ARE INCLUDED IN A LISTDEF *
* LIST THAT SHOULD BE EXCLUDED *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User used LISTDEF to define a list of LOB objects similar
to the following:
LISTDEF mylist
INCLUDE TABLESPACES X*.* LOB -- include all LOBs in all
-- DATABASES STARTING WITH X...
EXCLUDE TABLESPACES X5*.* LOB -- but exclude those which are
in db's starting with X5...
INCLUDE TABLESPACES A*.* LOB -- also include LOBs in all
DATABASES STARTING WITH A...
The resulting list included objects like X5AA.MYLOB even
though they were specifically excluded in the LISTDEF
definition.
This happened due to an error in the way LISTDEF handles
filtering of objects when LOB is specified.
This problem might potentially be seen when other LISTDEF
keywords are used, such as BASE, ALL, or XML.
Code in list manager was changed to improve the handling
of filtering keywords for LISTDEF.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM43441
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUILSA PM43441
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM43441 DSNUILSA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNUILSA
LISTEND
UK74044 COVER LETTER END
UK74063 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50674 -
****************************************************************
* USERS AFFECTED: All DB2 v10 package users. *
****************************************************************
* PROBLEM DESCRIPTION: Customer could receive the abend *
* ABEND0C4 RC00000011 at DSNGEFSP +0E12 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There is a small window when error or cancel could cause a freed
DB2 internal control block be accessed, which results in the
above abend.
DB2 has been changed to prevent the freed control blocked from
being accessed.
Additional keywords:
0C4 ABEND0C4 S0C4 ABENDS0C4 11 PIC11 OFFSET0E12 +0E12 0E12
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50674
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 PM50674
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50674 DSNGEFSP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFSP
LISTEND
UK74063 COVER LETTER END
UK74123 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49264 -
****************************************************************
* USERS AFFECTED: All db2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Customer could receive the abend *
1 * RC00C90101 DSNGEFLC ERQUAL5006 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When attempting to execute a package an ABEND04E RC00C90101
in DSNGEFLC erqual 5006 was recieved.
When a package is being executed locks are acquired. Some times
locks that are held on other members of a data sharing group
cause a lock request to fail and produced the abend. DB2 code
has been updated to detect that the lock request failed and
return a resource unavailable instead of the abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49264
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEPDL PM49264
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49264 DSNGEPDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPDL
LISTEND
UK74123 COVER LETTER END
UK74131 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48264 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of LOAD utility with SYSREC DD DUMMY. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU1036I and RC8 during a LOAD *
* utility with SYSREC DD DUMMY. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A LOAD REPLACE with SYSREC DD DUMMY failed with DSNU1036I
- UNABLE TO ESTIMATE SPACE REQUIREMENTS FOR ddname. The error
message was issued during TEMPLATE processing for the following
waork data set, such as SYSUT1, ERRDDN... LOAD was erroneously
issuing DSNU1036I for the work data set because of a residual
flag left from the DD DUMMY SYSREC processing.
Code has been modified to tolerate a SYSREC DD DUMMY for
LOAD utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48264
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
DSNURELD PM48264
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48264 DSNURELD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURELD
LISTEND
UK74131 COVER LETTER END
UK74181 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM39210 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V9 and V10 users. *
****************************************************************
* PROBLEM DESCRIPTION: During RESTART of DB2, ABEND0C4 *
* occurred at DSNKIXDB OFFSET338C. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During RESTART of DB2, ABEND0C4 occurred in
DSNKIXDB OFFSET338C. The abend happened during the open of
an index that was versioned. The type of versioning for the
failing index was where 1 or more columns were added to a table
space and an associated index space within the same commit
scope. So, during the open of the failing index space at
RESTART, information vital to versioning was not available,
which eventually lead to the abend.
Additional abends are possible when default values are missing
during RESTART such as:
ABND04E DSNIIDIS ERQUAL5002
ABND04E DSNIDIFS ERQUAL5007
The module DSNKIXDB has been modified to detect during DB2
RESTART, when column DEFAULT information for ALTER ADDed
columns is not available and at that time, mark the index as
LPL. When module DSNKIXDB places an index into LPL, on the
console, the MSGDSNI001I will display with RC00C90095 and
the NAME of the index object that was placed into LPL. After
the RESTART of DB2 completes, those index objects marked as
LPL will need to be restarted using the DB2 START command to
remove them from LPL.
Also added in this APAR (within module DSNKIXDB), is one
additional sanity check during the open of any index
to validate that the internal structures of the index matches
that of the catalog. If the check fails then, ABND04E
DSNKIXDB ERQUAL5042 (invalid column defaults).
1 If this abend occurs, then the failing index object
needs to be corrected by doing either a REORG TABLESPACE or
REBUILD INDEX.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM39210
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKIXDB PM39210
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM39210 DSNKIXDB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKIXDB
LISTEND
UK74181 COVER LETTER END
UK74244 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM31312 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, DB2 for z/OS V9.1, *
* and DB2 for z/OS V10 users of the *
* IFCID flat file (DSNWMSGS), and *
* DB2 for z/OS V10 users of the *
* CSECT flat file (DSNWMODS). *
****************************************************************
* PROBLEM DESCRIPTION: DSNWMSGS and DSNWMODS need to be *
* updated to reflect changes since the *
* first quarter of 2011. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Updates to the IFCID flat file (DSNWMSGS) and CSECT flat file
(DSNWMODS) since the first quarter of 2011 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 UDB for z/OS V8
- DB2 for z/OS V9.1
- DB2 for z/OS V10
This APAR delivers updates to the CSECT flat file (DSNWMODS)
for the following DB2 for z/OS version:
- DB2 for z/OS V10
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM31312
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
DSNWMODS PM31312
DSNWMSGS PM31312
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM31312 DSNWMODS DSNWMSGS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNWMODS
DSNWMSGS
LISTEND
UK74244 COVER LETTER END
UK74247 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51320 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS executing a *
* CREATE INDEX statement which has *
* a key expression or index on *
* expression. *
****************************************************************
* PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE *
* FOLLOWING REPORTED SYMPTOMS: *
* *
* SQLCODE = 0 *
* SQLSTATE = 01517 *
* *
* *
* PROBLEM SCENARIO: *
* *
* The reported problem occurs when *
* executing a CREATE INDEX statement *
* which contains a key expression and *
* TRACE IFCID 22 is turned on. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SUMMARY OF DB2 EVENTS:
Internally, DB2 should not have attempted to trace IFCID 22
information related to the creation on the key expression
in the CREATE INDEX statement.
PROBLEM CONCLUSION:
DB2 is now fixed so that it will not trace IFCID 22 information
when invoking a CREATE INDEX statement with a key expression.
ADDITIONAL KEYWORDS:
SQLCREATE SQLINDEXONEXP IFCID22 SQLSTATE01517
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51320
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPB PM51320
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51320 DSNXOPB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPB
LISTEND
UK74247 COVER LETTER END
UK74314 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52531 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0D7 RC25 on a SSAR issued by *
* DSNYALLI as an address was attempting *
* to connect to DB2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An allied address space was terminating the connection with
DB2 when a cancel abend occurred while DSNYAUTH was waiting
on the ASCEIECB ECB for the DB2 address spaces to destroy
the cross-memory authorization. The estae in DSNYEATE waited
for the ASCE use count to go to zero before resetting and
releasing the ASCE for reuse. The POST to the ASCEIECB ECB
from the DB2 MSTR address space was asynchronous, and actually
occurred after the ASCE was reset. The next user of the
ASCE will POST the DB2 MSTR address space to establish cross-
memory authorization and WAIT on the ASCEIECB. Since the ECB
was already POSTed, DSNYAUTH did not WAIT for the cross-memory
authorization which resulted in an ABEND0D7-25 on the
subsequent SSAR to the DB2 MSTR address space.
The ASCEIECB ECB will be initialized before the POST/WAIT
sequence in DSNYAUTH.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52531
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNYAUTH PM52531
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52531 DSNYAUTH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNYAUTH
LISTEND
UK74314 COVER LETTER END
UK74373 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51730 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* DSNACCOX stored procedure users who *
* specify a QUERYTYPE of REORG only. *
****************************************************************
* PROBLEM DESCRIPTION: 1. DSNACCOX returns rows with a REORG *
* recommendation value of NO when *
* only REORG is specified in the *
* QUERYTYPE parameter. INCORROUT *
* *
* 2. DSNACCOX fails intermittently when *
* it encounters an SQL warning. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
1. DSNACCOX incorrectly generates an SQL statement with a
clause of EXTENT=YES OR REORG=YES when a QUERYTYPE of
REORG only is specified, causing rows with EXTENT=YES
and REORG=NO to be returned as well.
2. DSNACCOX check for a non-zero SQLCODE to detect an SQL
failure. However, depending on the environment, an SQL
operation can be performed with a warning (positive
SQLCODE), causing DSNACCOX to incorrectly terminate.
1. DSNACCOX code is fixed to only return rows with REORG=YES
when QUERYTYPE contains only REORG.
2. DSNACCOX code is changed to check for a negative SQLCODE to
detect an SQL failure.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51730
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
The fix for APAR PM25652, introduces a new special option,
RRTHashOvrFlwRatio. The Utility Guide and Reference and
The Application Programming Guide documentation on DSNACCOX
will have a new description of RRTHashOvrFlwRatio as follows:
1 Syntax:
-|---+---' '--------------+---|-
+-RRTHashOvrFlwRatio-+
'- -1 ---------------'
Description:
RRTHashOvrFlwRatio
Specifies a criterion for recommending that the REORG utility
is run on a table space. If the following conditions are true,
DSNACCOX recommends running REORG:
- The hash access overflow index is being used for access.
- The number of hash access overflow index entries divided by
the total number of rows (expressed as a percentage) is
greater than RRTHashOvrFlwRatio.
RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The
default value is ' 15'. A plus sign (+) preceding or following
the value, or a plus sign by itself indicates that the DSNACCOX
stored procedure returns the calculated ratio value in the
result set. A negative value indicates that the criterion is
not used.
The ratio of hash access overflow index entries to the total
number of rows is returned in column RRTHashOvrFlwRatPCT of the
result set.
Figure 4. DSNACCOX formula for recommending a REORG on a table
space has an additional criteria:
(((QueryType='REORG' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL')) AND
(REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR
(NACTIVE IS NULL OR NACTIVE > 5) AND
((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND
REORGINSERTS > RRTInsertsAbs) OR
(((REORGDELETE x 100) / TOTALROWS > RRTDeletesPct) AND
REORGDELETE > RRTDeleteAbs) OR
(REORGCLUSTERSENS > 0 AND
(REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR
((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR
| (Object is not using hash organization and ((SPACE x 1024) /
RRTDataSpaceRat)) OR
((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS >
RRTIndRefLimit) OR
REORGMASSDELETE > RRTMassDelLimit OR
EXTENTS > ExtentLimit) OR
| ((QueryType='REORG' OR QueryType='ALL') AND
| ObjectType='ALL' * AND
| Overflow index hash access is used**, AND
| ((overflow index TOTALENTRY x 100) / TOTALROWS >
RRTHashOvrFlwRatio)) OR
((QueryType='RESTRICT' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL') AND
The table space is in advisory or informational reorg
pending status)
1
|Note:
| * ObjectType='ALL' must be specified to use this criteria.
| for this criterion to be used. If ObjectType='TS' or
| ObjectType='IX' is specified, and '+' is specified for
| RRTHashOvrFlwRatio, an error message is issued. If
| ObjectType='TS' or ObjectType='IX' is specified, and
| '+' is not specified for RRTHashOvrFlwRatio, this
| criterion is not used.
| ** The overflow index is used when SYSINDEXES.HASH ='Y' AND
| SYSINDEXSPACESTATS.REORGINDEXACCESS > 0.
Add the following table entry to table for the
"DSNACCOX OUTPUT" section.
Result set row for second DSNACCOX result set
----------------------------------------------------------------
|Column name | Data type |Description |
----------------------------------------------------------------
|RRTHashOvrFlwRatPCT| Double |This is an optional column, |
| | |and it is being returned when |
| | |there is a plus (+) sign in |
| | |the RRTHashOverFlwRatio. |
| | | |
| | |If OBJECTTYPE is ALL and REORG|
| | |is YES, the ratio of Hash |
| | |Access overflow index entries |
| | |to the total number of rows, |
| | |expressed as a percentage. |
| | |Otherwise null. |
| | | |
| | |If the ratio of Hash Access |
| | |overflow index entries to the |
| | |total number of rows does not |
| | |exceed the value specified for|
| | |RRTHashOvrFlwRatio or meet the|
| | |criteria requirement, this |
| | |value is null. |
----------------------------------------------------------------
ACTION:
Post-apply actions after applying the fix for APAR PM25652:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this is
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@CCOX PM51730
DSNACCOX PM51730
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51730 DSN@CCOX DSNACCOX
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNACCOX
MACROS
DSN@CCOX
LISTEND
UK74373 COVER LETTER END
UK74375 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52521 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REPAIR SET *
* utility. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability APAR for REPAIR SET. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
Serviceability APAR for REPAIR SET.
Serviceability APAR for REPAIR SET.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52521
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCBRS PM52521
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52521 DSNUCBRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBRS
LISTEND
UK74375 COVER LETTER END
UK74383 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50469 -
****************************************************************
* USERS AFFECTED: All users of SPUFI in DB2 9 for z/OS and *
* DB2 10 for z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: SPUFI may report more records were *
* read than exist in the input data set. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
SPUFI is an option of the DB2 for z/OS Interactive (DB2I)
facility that can be used to process dynamic SQL statements
via ISPF.
After SPUFI has completed processing of the input SQL
statements, it prints the following message to indicate
the number of input records read:
DSNE621I NUMBER OF INPUT RECORDS READ IS x
Currently, SPUFI may not report the correct number of
records read:
(1) When the input data set is empty, SPUFI reports
2 records as read.
(2) When no errors were encountered and SPUFI processed
the full input data set, SPUFI reports one more record
than exists as read.
In response, SPUFI was updated to provide the correct number
of records read.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50469
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNESM21 PM50469
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50469 DSNESM21
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNESM21
LISTEND
UK74383 COVER LETTER END
UK74390 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48406 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of RECOVER *
* utility using concurrent copy. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C2 RC00000002 at IFG019RA:2DE6 *
* during RECOVER utility using *
* concurrent copy. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
1 ****************************************************************
User ran RECOVER utility which restored a concurrent copy. The
utility abended with ABENDS0C2 because some DB2 code later ran
in Problem State when it should have run in Supervisor State.
Although this problem happened only for RECOVER utility when
it restored a concurrent copy, it is possible that a similar
problem could occur in other circumstances or for other
utilities.
DB2 utility code was changed not to alter the execution state
in cases when it is not necessary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48406
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGTRA PM48406
DSNUGTRB PM48406
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48406 DSNUGTRA DSNUGTRB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGTRA
DSNUGTRB
LISTEND
UK74390 COVER LETTER END
UK74399 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53276 -
****************************************************************
* USERS AFFECTED: All DB2 V10 users. *
****************************************************************
* PROBLEM DESCRIPTION: DELETION OF OBSOLETE MODULES *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DELETION OF OBSOLETE MODULES
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53276
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DELETE:
This PTF deletes the module DSNADMJ5.
DELETE:
This PTF deletes the module DSNXEAS.
DELETE:
1 This PTF deletes the module DSNXEAS1.
DELETE:
This PTF deletes the module DSNXESID.
DELETE:
This PTF deletes the module DSN7GBRS.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNADMJ5 PM53276
DSNTEJSQ PM53276
DSNXEAS PM53276
DSNXEAS1 PM53276
DSNXESID PM53276
DSN7GBRS PM53276
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53276 DSNADMJ5 DSNTEJSQ DSNXEAS DSNXEAS1 DSNXESID DSN7GBRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMJ5
DSNXEAS
DSNXEAS1
DSNXESID
DSN7GBRS
MACROS
DSNTEJSQ
LISTEND
UK74399 COVER LETTER END
UK74453 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49932 -
****************************************************************
* USERS AFFECTED: All DB2 10 for DB2 DRDA / DDF *
* users who use remote binds. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE -512 *
* may be issued during a remote *
* bind for an SQL statement *
* that is longer than 32K. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Unexpected SQLCODE -512 may be issued during a remote
bind for an SQL statement that is longer than 32K.
DB2 was fixed to handle the SQL statement
which is longer than 32K during a remote bind.
Additional Keywords: SQLDRDA DB2DRDA
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49932
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
DSNXOALS PM49932
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49932 DSNXOALS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOALS
LISTEND
UK74453 COVER LETTER END
UK74462 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49617 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of LOB columns *
* having default values with the LOB INLINE *
* LENGTH subsystem parameter. *
* *
****************************************************************
* PROBLEM DESCRIPTION: The following statements result in an *
* ABEND04E RC00C90101 abend. *
* *
* CREATE TABLE *
* ALTER TABLE ADD COLUMN *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For the LOB column where the inline length is not explicitly
specified and the LOB INLINE LENGTH subsystem parameter is not
applicable and a default value is specified, DB2 should issue
SQLCODE -574. However DB2 does not correctly handle the check
and results in an ABEND04E RC00C90101 abend.
Affected statements and result would be:
o Statements:
CREATE TABLE
ALTER TABLE ADD COLUMN
o Result:
ABEND04E RC00C90101 DSNGD001.DSNGDVRT:501D
DB2 has been fixed to properly issue SQLCODE -574 when a LOB
column has a default value specified, but the inline length
is not explicitly specified and the INLINE LOB LENGTH subsystem
parameter is not applicable.
1
Additional keywords
SQLCREATE
SQLALTER
DB2LOB
SQLCODE574
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49617
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISB5 PM49617
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49617 DSNXISB5
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISB5
LISTEND
UK74462 COVER LETTER END
UK74477 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM44912 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* defer key processing on segmented table *
* space or universal table space (UTS) *
****************************************************************
* PROBLEM DESCRIPTION: When executing multiple row update or *
* online REORG against segmented table *
* space or UTS, defer key processing may *
* be triggered. If there were one or more *
* pointer records need to be removed on a *
* data page such as cross partition *
* update for UTS, which may cause that *
* data page empty, but the empty status *
* of that data page was not updated in *
* the space map page. *
* ABEND04E RC00C90101 at DSNIDLDU *
* ERQUAL5013 or other abend symptoms may *
* occur. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
Defer key processing may be triggered when executing multiple
row update or online REORG. In the path of segmented table space
or UTS, if there were one or more pointer records need to be
removed on a data page such as cross partition update for UTS,
1 which may cause that data page empty, but the empty status of
the data page was not updated in the space map page.
ABEND04E RC00C90101 at DSNIDLDU ERQUAL5013 or other abend
symptoms may occur.
DB2 has been fixed to update the data page empty status in space
map page for segmented table space or UTS correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM44912
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 PM44912
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM44912 DSNIKDEF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIKDEF
LISTEND
UK74477 COVER LETTER END
UK74482 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49717 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS who need to send *
* environment re-creation information to the *
* DB2 service team when requested for a *
* problem related to DB2 query processing. *
****************************************************************
* PROBLEM DESCRIPTION: THIS FIX ADDRESSES SEVERAL ISSUES *
* RELATED TO OUTPUT RE-CREATION FOR *
* DDL AND STATS. THE SYMPTOMS USUALLY *
* ARE INCORRECT OUTPUT WHEN BUILDING THE *
* DDL AND STATS OUTPUT FILES. *
* *
* In DB2 V10 only this fix also addresses *
* the following warning that can occur *
* when job DSNTIJSG binds the package for *
* program DSNADMSB (a program that can be *
* used to drive the ADMIN_INFO_SQL stored *
* procedure): *
* *
* DSNX100I - BIND SQL WARNING *
* USING SYSADM AUTHORITY *
* PLAN=(NOT APPLICABLE) *
* DBRM=DSNADMSB *
* STATEMENT=nnn *
* PROCEDURE *
* SYSPROC.ADMIN_INFO_SQL *
1 * IS NOT DEFINED *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SUMMARY OF ADMIN_INFO_SQL EVENTS:
ADMIN_INFO_SQL was sometimes not producing the
correct output when creating DDL and STATS output files. Here
are a list of reported issues:
- Added quotes to drop and create Alias
- Added SET CURRENT SQLID = 'xx' before creating view/MQT to
handle embedded tables that are not qualified
- Fixed select of VCAT or STOGROUP when creating indexes
- Removed 'IN' when creating global temp tables
- Removed 'APPEND NO' Only use 'APPEND YES'
- Fixed NULL pointer problem which could cause abend
- Fixed create table DECIMAL(x,y) requires a space for
HDECP DECIMAL=COMMA now DECIMAL(x, y)
- Fixed PLAN_TABLE insert statements to handle lower requested
versions. Example V10->V9
In addition, the DB2 installation process for binding DSNADMSB
(a program that can be used to drive the ADMIN_INFO_SQL stored
procedure) can result in the bind warning noted in the Problem
Description section of this APAR because job DSNTIJSG binds
DSNADMSB before ADMIN_INFO_SQL is created.
ADMIN_INFO_SQL had several new features added:
- Added support for View/View dependencies
- Added additional support in PLAN_TABLE service data
- Added ADMIN_INFO_SQL information to EXPL file
PROBLEM CONCLUSION:
The reported ADMIN_INFO_SQL DDL and STATS problems
are now corrected.
The DB2 V10 installation process is modified as follows to
prevent warnings during binding of DSNADMSB:
- Statements for binding the DSNADMSB package and plan are
removed from job DSNTIJSG
- Binding of the DSNADMSB package and plan is now performed by
job DSNTIJRT, program DSNTRIN, as part of installation and
1 customization of DB2-supplied routines - including the
ADMIN_INFO_SQL stored procedure.
Running job DSNTIJRT will now bind the DSNADMSB package if one
or more of the following conditions is true:
- No package exists for DSNADMSB
- No existing package for DSNADMSB matches the consistency
token of the DSNADMSB DBRM in prefix.SDSNDBRM
- The package for DSNADMSB is marked invalid or inoperative
Running job DSNTIJRT will bind a plan for DSNADMSB if one or
more of the following conditions is true:
- No plan exists for DSNADMSB
- The plan for DSNADMSB is marked invalid or inoperative
In addition, DSNTIJRT will grant execute access on the
DSNADMSB package and plan to each authorization ID in the
GRANTTO list of the configuration control statement for
ADMIN_INFO_SQL that does not already have that access.
DB2 V9 users who receive the warning message when binding
DSNADMSB should ignore the warning.
ADDITIONAL KEYWORDS:
SQLSP SQLSTOREDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49717
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. It also modifies
DSNADMSB, a program that can be used to call
SYSPROC.ADMIN_INFO_SQL. Finally, it modifies the DB2 V10
installation process, relocating responsibility for binding the
DSNADMSB package and plan from job DSNTIJSG to job DSNTIJRT.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRMs DSNADMSS
and DSNADMSB
---------------------------------------------------------------
==> This action is required for all V10 customers
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2 supplied stored
procedures.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
1 DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
---------------------------------------------------------------
(2) Refresh the WLM environment
---------------------------------------------------------------
==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL
stored procedure need to take this action after applying
the PTF
Issue the following VARY MVS command from the console to
refresh the WLM application environment:
VARY WLM,APPLENV=!wlmenv!,REFRESH
where !wlmenv! is the name of the WLM application
environment for running the SYSPROC.ADMIN_INFO_SQL stored
procedure.
---------------------------------------------------------------
(3) Update your customized copy of job DSNTIJSG
---------------------------------------------------------------
==> All DB2 V10 customers who maintain a customized copy of DB2
installation job DSNTIJSG need to take this action after
applying the PTF
(a) Edit your customized copy of DSNTIJSG.
(b) In job step DSNTIRU, locate and remove the bind package
and bind plan statements for DSNADMSB. DSNADMSB is now
bound as necessary when you run job DSNTIJRT.
(c) In job step DSNTIJG, locate and remove the grant
statement for PLAN DSNADMSB. Authority to execute
DSNADMSB is now granted when you run job DSNTIJRT
according to the authorization IDs in the GRANTTO list
of the configuration statement for stored procedure
SYSPROC.ADMIN_INFO_SQL.
(d) Save your changes.
ACTION:
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. It also modifies
DSNADMSB, a program that can be used to call
SYSPROC.ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers
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.
---------------------------------------------------------------
(2) Refresh the WLM environment
---------------------------------------------------------------
==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL
stored procedure need to take this action after applying
the PTF
Issue the following VARY MVS command from the console to
refresh the WLM application environment:
VARY WLM,APPLENV=!wlmenv!,REFRESH
where !wlmenv! is the name of the WLM application
environment for running the SYSPROC.ADMIN_INFO_SQL stored
procedure.
---------------------------------------------------------------
(3) Rebind the package for DSNADMSB
---------------------------------------------------------------
==> All DB2 V10 customers who use the DSNADMSB program to call
the SYSPROC.ADMIN_INFO_SQL stored procedure need to take
this action after applying the PTF
Submit a job that contains the following BIND statements:
BIND PACKAGE(DSNADMSB) MEM(DSNADMSB) -
ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) -
LIBRARY('<prefix>.SDSNDBRM')
where <prefix> is the high-level qualifier for the
target DB2 subsystem.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMSB PM49717
DSN@DMSS PM49717
DSN@RIN PM49717
DSNADMSB PM49717
DSNADMSS PM49717
1 DSNTESR PM49717
DSNTIJSG PM49717
DSNTINS1 PM49717
DSNTRIN PM49717
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49717 DSN@DMSB DSN@DMSS DSN@RIN DSNADMSB DSNADMSS DSNTESR
DSNTIJSG DSNTINS1 DSNTRIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMSB
DSNADMSS
DSNTRIN
MACROS
DSN@DMSB
DSN@DMSS
DSN@RIN
DSNTESR
DSNTIJSG
DSNTINS1
LISTEND
UK74482 COVER LETTER END
UK74491 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53780 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of declared global *
* temporary tables(DGTTs) or created global *
* temporary tables(CGTTs) *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may use incorrect table statistics *
* for access path selection when a DGTT *
* or CGTT is empty. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If statistics show that a table has zero rows, DB2 will use
CARDF and NPAGES statistics from real time statistics (RTS) to
validate the number of rows in the table. Access path selection
will then be based on the statistics reported by RTS.
In the case of a DGTT or CGTT, the statistics tracked by
RTS do not accurately represent a single instance of the
temporary table and should not be used for access path
selection.
This problem may result in poor performance due to a poor
access path choice.
Additional keywords:
1 SQLACCESSPATH SQLPERFORMANCE SQLSTATS SQLDGTT SQLGTT
Query optimization does not use statistics from RTS for DGTTs
and CGTTs.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53780
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM53780:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM53780 corrects a problem in which incorrect statistics are
used for a DGTT or CGTT when the table is empty.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM50507:
See PM50507 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50507 corrects a problem of the DB2 optimizer in calculating
the cost of hash access for a hash-organized table. The
fix will get a more accurate estimation of hash access,
and enable the DB2 optimizer to choose hash access methods over
other suboptimal method(s).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM45292 corrects a problem in which a DB2 intentional abend may
occur when a query contains the RID function.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPRS PM53780
DSNXORTS PM53780
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53780 DSNXOPRS DSNXORTS
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPRS
DSNXORTS
LISTEND
UK74491 COVER LETTER END
UK74503 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM46632 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG SHRLEVEL CHANGE utility *
****************************************************************
* PROBLEM DESCRIPTION: Reducing LOG phase outage window for *
* REORG SHRLEVEL CHANGE processing. *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
The following enhancements are introduced to the LOG phase of
REORG SHRLEVEL CHANGE utility to reduce the application outage
window during the last read-only log iteration:
- avoid scanning the spacemap for dirty pages in the final
incremental inline copy if no log records are applied in
the final log iteration
- enable short deferred write on the shadow datasets
- when reporting utility subphase statistics, avoid collecting
statistics for non read-only log iteration to reduce the
total virtual storage consumption
Code has been modified to implement the aforementioned
enhancements to the LOG phase of REORG SHRLEVEL CHANGE utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM46632
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBASP PM46632
DSNURCCP PM46632
DSNURLOG PM46632
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM46632 DSNUBASP DSNURCCP DSNURLOG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBASP
1 DSNURCCP
DSNURLOG
LISTEND
UK74503 COVER LETTER END
UK74527 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51552 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS Command Line *
* Processor (CLP) are affected. *
****************************************************************
* PROBLEM DESCRIPTION: Command Line Processor (CLP) may fail *
* to initialize with Java 1.5 and 1.4 *
* and return the following error: *
* *
* java.lang.UnsupportedClassVersionError: *
* (com/ibm/db2/clp/db2) bad major version *
* at offset=6 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The Command Line Processor failed to initialize under Java
Runtime Environment 1.5 or 1.4. The following error is
observed:
java.lang.UnsupportedClassVersionError: (com/ibm/db2/clp/db2)
bad major version at offset=6
Command Line Processor has been recompiled using Java 1.4.2.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51552
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNCLP PM51552
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51552 DSNCLP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNCLP
LISTEND
UK74527 COVER LETTER END
UK74534 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48856 -
****************************************************************
1 * USERS AFFECTED: All users of DB2 10 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Changes to the early code and *
* associated macros are being made to *
* provide compatibility with future *
* releases of DB2 for z/OS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Changes are required to DB2 10 to make it compatible with a
future release of DB2 for z/OS.
This APAR updates code in DB2 10 for z/OS so it will
be compatible with future releases of DB2 for Z/OS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48856
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3AMI1 PM48856
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48856 DSN3AMI1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3AMI1
LISTEND
UK74534 COVER LETTER END
UK74535 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45652 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Changes to the early code and *
* associated macros are being made to *
* provide compatibility with future *
* releases of DB2 for z/OS. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Changes are required to DB2 10 to make it compatible with a
future release of DB2 for z/OS.
This APAR updates code in DB2 10 for z/OS so it will be
compatible with future releases of DB2 for Z/OS.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PM45652
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 ACTION:
In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.
ACTION:
In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2,EARLY command.
ACTION:
In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAPRHX PM45652
DSN3RRSX PM45652
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45652 DSNAPRHX DSN3RRSX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRHX
DSN3RRSX
LISTEND
UK74535 COVER LETTER END
UK74537 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50473 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V10 users *
****************************************************************
* PROBLEM DESCRIPTION: The Mass delete lock is held *
* incorrectly in V10 new function mode. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect way to determine V10 new function mode during the
process of performing Mass Delete or Alter Rotate partition on
the Universal Table Space. As the result, a Mass Delete lock
can be held incorrectly.
DB2 code is changed to determine DB2 V10 function mode
correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50473
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 PM50473
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50473 DSNISEGD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISEGD
LISTEND
UK74537 COVER LETTER END
UK74555 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50857 -
****************************************************************
* USERS AFFECTED: DB2 V10 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Performance degradation when running *
* workloads with a high degree of page *
* P-lock contention. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a page P-lock negotiation, the P-lock exit routine goes
through a validation scan to ensure that the P-lock is still
associated with a page in the buffer pool. Depending upon how
large the buffer pool is, this scan can use up a lot of CPU in
csect DSNB1PPG, and cause class 14 latch contention.
The page P-lock exit logic has been modified to eliminate the
validation scan for the case where the P-lock is held in X mode.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50857
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1LTS PM50857
DSNB1LTX PM50857
DSNB1PPG PM50857
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50857 DSNB1LTS DSNB1LTX DSNB1PPG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1LTS
DSNB1LTX
DSNB1PPG
LISTEND
UK74555 COVER LETTER END
1UK74560 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51625 -
****************************************************************
* USERS AFFECTED: All users of DB2 9 for z/OS and DB2 *
* 10 for z/OS who are using the DB2- *
* supplied user-defined function *
* DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY). *
****************************************************************
* PROBLEM DESCRIPTION: DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) *
* abends with 0C4 while processing a *
* DB2 scheduler task that has multiple *
* execution statuses. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) saves a task's information
it read from SYSIBM.ADMIN_TASKS in a local variable. Since a
local variable is used, the task information is not preserved
between the function's FETCH operations when more than one
execution status has to be returned for this task. Therefore,
subsequent FETCH operations can result in an 0C4 abend.
DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) is modified to save a
task's information which it read from SYSIBM.ADMIN_TASKS in the
scratchpad, thereby increasing the scratchpad length of this
function from 16 to 8208.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51625
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF fixes an 0C4 abend in the user-defined function
DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) when it is processing
a DB2 scheduler task that has multiple execution statuses.
***************************************************************
Actions for customers who are already using DB2 V10:
***************************************************************
***********************************************************
* This action is required for all V10 customers
***********************************************************
Run your customized copy of job DSNTIJRT with MODE(INSTALL)
to alter the scratchpad length of the modified user-defined
function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) from 16 to
8208 and to bind this function's DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
1 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@DMTH PM51625
DSN@RIN PM51625
DSNADMTH PM51625
DSNTESR PM51625
DSNTRIN PM51625
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51625 DSN@DMTH DSN@RIN DSNADMTH DSNTESR DSNTRIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMTH
DSNTRIN
MACROS
DSN@DMTH
DSN@RIN
DSNTESR
LISTEND
UK74560 COVER LETTER END
UK74587 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52915 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0D6 RC27 during a LIGHT(YES) *
* restart when there was one INDOUBT UR *
* that was resolved during restart. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a LIGHT(YES) restart, there was one RRSAF INDOUBT UR
that was resolved during restart. MSGDSNR053I was issued
after this last INDOUBT UR was resolved, and DB2 began to
shutdown while DDF was still in the process of starting.
DSNRUC02 issued a PC during DDF processing but the PC number
in the RMFT was already reset, leading to the ABEND0D6.
DSNYSTPW has been changed to wait until restart has completed
before allowing DB2 shutdown to continue when DB2 shutdown has
been initiated in this scenario.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52915
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 DSNYSTPW PM52915
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52915 DSNYSTPW
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNYSTPW
LISTEND
UK74587 COVER LETTER END
UK74596 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51561 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of LOBs. *
****************************************************************
* PROBLEM DESCRIPTION: When running a Spatial query or some *
* other kind of query which references *
* LOBs, an ABEND0C9 rc9 can occur at *
* location DSNOLLM .DSNOGETD OFFSET07CE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running a Spatial query or some other kind of query which
references LOBs, an ABEND0C9 can occur at location
DSNOLLM DSNOGETD OFFSET07CE.
An example of a failing Spatial query is as follows
SELECT SID
FROM CUSTOMERS AS CT, STORES AS ST
WHERE DB2GSE.ST_WITHIN(CT.COVER,
DB2GSE.ST_POLYGON('POLYGON ((' || RTRIM(CHAR(ST.X - 0.3)) ||
' ' || RTRIM(CHAR(ST.Y - 0.3)) ||
',' || RTRIM(CHAR(ST.X - 0.3)) ||
' ' || RTRIM(CHAR(ST.Y + 1.5)) ||
',' || RTRIM(CHAR(ST.X + 1.5)) ||
' ' || RTRIM(CHAR(ST.Y)) ||
',' || RTRIM(CHAR(ST.X - 0.3)) ||
' ' || RTRIM(CHAR(ST.Y - 0.3)) || '))', 1)) = 1
AND DB2GSE.ST_WITHIN(S_COVER,
DB2GSE.ST_POLYGON('POLYGON ((2.5 3.5, 2.5 9.1, 12.5 6.0,' ||
' 2.5 3.5))', 1)) = 1
AND SID BETWEEN ? AND ?
ORDER BY SID ;
Please note that this failure can also occur for other
(non-Spatial) queries that reference a zero-length LOB while
executing an error path.
Additionally, the likelihood of this failure occurring is very
1 small.
The code is modified in DB2 so that an SQLCODE -904 is issued
appropriately when an error path is taken for a zero-length LOB.
Additional Keywords: SQLSPATIAL SQLLOB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51561
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNONLLE PM51561
DSNOTCSO PM51561
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51561 DSNONLLE DSNOTCSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNONLLE
DSNOTCSO
LISTEND
UK74596 COVER LETTER END
UK74623 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48518 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* XMLAGG function with GROUP BY. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 AT DSNXGRDS DSNXXAGG +19C0 *
* occurred when the first XML value in a *
* group is NULL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 AT DSNXGRDS DSNXXAGG +19C0 occurred when the first XML
value in a group is NULL.
Please look at following example. The value for the XML column
C2 for the first row is NULL.
CREATE TABLE T1 (C1 INTEGER, C2 XML);
INSERT INTO T1 (C1) VALUES(10);
INSERT INTO T1 (C1, C2) VALUES(10, '<a>111</a>');
The following query will aggregate the XML value in C2. Because
the first C2 value in the group is NULL, the abend occurs when
executing the query.
1
SELECT XMLAGG(C2) FROM T1
GROUP BY C1;
DB2 is modified to ensure that the ABEND will not occur.
Additional keywords: SQLXML SQLGROUPBY OFFSET19C0
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48518
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXXAGG PM48518
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48518 DSNXXAGG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXXAGG
LISTEND
UK74623 COVER LETTER END
UK74648 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52053 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of migrated pre- *
* v10 packages containing queries which have a *
* SORT whose input is coming from a UNION. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at *
* location DSNXPUF0 M106 when SORT puffs *
* an MSIB to a v10 format. This can occur *
* for a pre-v10 migrated package that *
* contains a query with a SORT whose *
* input comes from a UNION. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 can occur at location DSNXPUF0 M106 when
SORT puffs an MSIB to a v10 format. This can occur for a pre-
v10 migrated package that contains a query with a SORT whose
input comes from a UNION.
The puffing of the MSIB is only needed by SORT when it utilizes
the 'one move block fetch' where the input to SORT is a single
Runtime fetch block. If the sort is complex, the input (to
sort) may not be a single Runtime fetch block but may be a UNION
which then includes other Runtime fetch blocks. In this case,
this block will not have an MSIB and its location in storage may
1 point to other storage which should not be puffed.
The code in DB2 is modified to check if SORT is using a 'one
move block fetch' for a "migrated SORT" prior to puffing the
MSIB block information.
Additional Keywords: SQLMIGRATION SQLUNION SQLSORT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52053
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 PM52053
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52053 DSNXSORI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSORI
LISTEND
UK74648 COVER LETTER END
UK74649 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52214 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V10 users using indexes, *
* REORG INDEX, CHECK INDEX, or RUNSTATS *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKTRAV ERQUAL501B *
* occurred after resource not available *
* condition was raised. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C90101 DSNKTRAV ERQUAL501B occurred after resource
not available (RNA) condition was raised.
Index leaf prefetch was used to read multiple leaf pages.
A non-zero return code was return with reason code
RC00D3003C - stating that a client program issued a cancel
request. The return code was not handled and caused abend.
Other abends may occur during index access range scan,
REORG INDEX, CHECK INDEX, or RUNSTATS. For example:
DSNICUBC ERQUAL5001
DSNISFX2 ERQUAL501E
Code has been modified to handle the resource not available
(RNA) conditions.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52214
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
DSNKLFPR PM52214
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52214 DSNKLFPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKLFPR
LISTEND
UK74649 COVER LETTER END
UK74659 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51338 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 9.1 for z/OS *
* ODBC/CLI and DB2 10 for z/OS ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: Using an empty string as input for *
* a SQL_CHAR parameter and calling *
* SQLExecute() repeatedly results in *
* SQLCODE -804 and reason code 9. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Calling SQLExecute() repeatedly fails with SQLCODE -804
and reason code 9 when an empty string is bound to a
parameter of SQL type SQL_CHAR and the parameter type
is SQL_PARAM_INPUT.
In the case of parameters that are not parameters of a
stored procedure CALL statement, SQLCODE -804 only occurs
if AUTOCOMMIT is off and there are no commits issued
between the SQLExecute() calls.
Code has been changed to correctly process input empty
strings bound to SQL_CHAR parameter markers when the SQL
is executed repeatedly.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PM51338
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG0U PM51338
DSNAOCLI PM51338
DSNAOSDK PM51338
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51338 DSNAOG0U DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOG0U
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UK74659 COVER LETTER END
UK74716 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52371 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* INSERT into SYMMETRIC view statement. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE -161 could be *
* issued for an INSERT statement *
* satisfies the following conditions: *
* 1. The target of the INSERT is a *
* SYMMETRIC view, *
* 2. The inserted data conforms to *
* the view definition. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Unexpected SQLCODE -161 could be issued for an INSERT statement
satisfies the following conditions:
1. The target of the INSERT is a SYMMETRIC view,
2. The inserted data conforms to the view definition.
The following example could recreate the problem:
CREATE TABLE MYTEST1
(C1 VARCHAR(24), C2 VARCHAR(24));
CREATE VIEW MYVIEW AS
SELECT * FROM MYTEST1
WHERE C1 IN ('TEST1', 'TEST23') WITH CHECK OPTION;
INSERT INTO MYVIEW VALUES('TEST1', 'MYTEST');
SQLCODE -161 issued for INSERT statement even though the data
in the values clause conforms to the symmetric view definition.
DB2 is updated to handle the INSERT statement above
correctly.
Additional keywords: SQLVIEW SQLINSERT SQLCODE161
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52371
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM52371:
See PM52371 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52371 corrects a problem of unexpected SQLCODE -161 issued
for an INSERT into SYMMETRIC view statement.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOW2F PM52371
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52371 DSNXOW2F
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOW2F
LISTEND
UK74716 COVER LETTER END
UK74718 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47802 -
****************************************************************
* 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.62.95 is provided by *
* this APAR ( JCCV36295 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V10, DB2 z/OS V9 and *
* the alternate supplemental driver *
* for DB2 z/OS V8. ( JCCZOSDB2V10, *
* JCCZOSDB2V9, JCCZOSDB2V8) *
* *
* This APAR delivers a service bundling *
* to release 3.62 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. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
JCC sub-category keywords:
JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ
The following changes are delivered in this APAR:
____________________________________________________________
All Connectivities: Even with atomic multirow insert disabled,
the driver still throws a warning with the message "Atomic
batch is not supported by server. The batch was submitted,
but not in atomic mode." for a merge sql statement. This has
been fixed (wsdbu01004701)
____________________________________________________________
All Connectivities: If the license stored procedure is not
installed and sysplex is enabled, StackOverflowError might
occur. This problem has been fixed. (wsdbu00999416 )
____________________________________________________________
All Connectivities: A java.lang.IndexOutOfBoundsException
occurred when trying to retrieve an XML value which DB2
server has failed to return due to an SQL error. This has
been fixed to return the SQL error. (wsdbu00976992)
____________________________________________________________
All Connectivities: Driver sends incorrect time value to DB2
server using PreparedStatement.setObject() call.
setObject(x, "12:00 PM", java.sql.Types.TIME) method call
caused the driver to send "00:00" instead of "12:00"
to the
DB2 server. setObject(x, "12:00 AM", java.sql.Types.TIME)
method call caused the driver to send "12:00" instead of
"00:00" to the DB2 Server. This has been resolved.
(wsdbu00988877)
____________________________________________________________
All connectivities: When ":" exists in an sql statement and
the property "enableNamedParameterMarkers" is set to 1(YES),
the driver may mistaken the ":" as a Named Parameter Marker
even thought it is not one. And if there is standard parameter
markers in the same sql, the driver will throw a SQLCODE4463
(-4463) error with the message "Invalid parameter marker usage.
Named parameter markers and standard parameter markers may not
be used in the same statement." This problem has been fixed.
(wsdbu00731226)
____________________________________________________________
All connectivities: A new global override property
"db2.jcc.override.enableMultirowInsertSupport" is provided.
The default value is DB2BaseDataSource.NOT_SET(0). When it is
set to the default value or DB2BaseDataSource.YES(1), driver
will use multirow insert under executeBatch call targeting a
DB2 z/OS server V8 NFM or above. When it is set to
DB2BaseDataSource.NO(2), driver disables multirow insert
under executeBatch call. (wsdbu01004996)
____________________________________________________________
Type-2 z/OS Connectivity: DB2 ABEND may occur during an open
cursor call when targeting DB2 z/OS V10. This has been fixed
(wsdbu00997886)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, the driver
1 fails to do auto seamless failover when packages are bound
using keepDynamic on the DB2 server. Instead, the driver
throws a SQLCODE30108 (-30108) error. This has been fixed.
(wsdbu00991244)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, the driver
fails to balance the workload properly if an unexpected
disconnect exception occurs while trying to open a new
transport (physical connection) to DB2 when requested by an
application connection. This has been fixed. (wsdbu00982417)
(wsdbu00982417).
____________________________________________________________
Type-4 Connectivity: When an application invokes a Stored
Procedure against DB2 z/OS as a local transaction on an XA
connection, it fails with the error SQLCODE751 (-751).
This problem has been fixed. (wsdbu00992988)
____________________________________________________________
Type-4 Connectivity: With client affinities, HADR, or DB2
with data sharing (LUW only) environment, the driver can
wait for a long period of time (10 minutes or more) to close a
connection if all DB2 instances go down before the close. This
problem has been fixed. (wsdbu00723426)
____________________________________________________________
Type-4 Connectivity: The driver reports an unexpected
NullPointerException during the failover processing for
applications connecting to a data sharing or a HADR system.
This has been fixed. (wsdbu00738031)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, if system
is heavy loaded with multiple threads competing with small
amount of the transport pool objects, the driver might get
distribution protocol error with SQLCODE4499 (-4499). This
problem has been fixed.(wsdbu00977620)
____________________________________________________________
Type-4 connectivity: If the target is v97FP4+ database
cataloged on LUW V95, the application may get various
Exceptions, one of the Exception is "Mutually exclusive fields
cannot both contain non-null values." The problem is fixed.
(wsdbu01005308)
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: PM47802
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAQJBA PM47802
DSNAQJBB PM47802
DSNAQJB1 PM47802
DSNAQJB2 PM47802
DSNAQJB3 PM47802
DSNAQJB4 PM47802
DSNAQJB5 PM47802
1 DSNAQJB6 PM47802
DSNAQJB7 PM47802
DSNAQJB8 PM47802
DSNAQJC1 PM47802
DSNAQJC2 PM47802
DSNAQJC3 PM47802
DSNAQJC4 PM47802
DSNAQJRM PM47802
DSNAQJS1 PM47802
DSNAQJS2 PM47802
DSNAQ3CA PM47802
DSNAQ3CC PM47802
DSNAQ3CE PM47802
DSNAQ3CF PM47802
DSNAQ3CM PM47802
DSNAQ3C0 PM47802
DSNAQ3C1 PM47802
DSNAQ3C2 PM47802
DSNAQ3C3 PM47802
DSNAQ3C4 PM47802
DSNAQ3C5 PM47802
DSNAQ3C6 PM47802
DSNAQ3C7 PM47802
DSNAQ3C8 PM47802
DSNAQ3C9 PM47802
DSNAQ3E1 PM47802
DSNAQ6CC PM47802
DSNAQ6CE PM47802
DSNAQ6CF PM47802
DSNAQ6CM PM47802
DSNAQ6C0 PM47802
DSNAQ6C1 PM47802
DSNAQ6C2 PM47802
DSNAQ6C3 PM47802
DSNAQ6C4 PM47802
DSNAQ6C5 PM47802
DSNAQ6C6 PM47802
DSNAQ6C7 PM47802
DSNAQ6C9 PM47802
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47802 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
1 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
MACROS
DSNAQJBA
DSNAQJBB
DSNAQJB1
DSNAQJB2
DSNAQJB3
DSNAQJB4
DSNAQJB5
DSNAQJB6
DSNAQJB7
DSNAQJB8
DSNAQJC1
DSNAQJC2
DSNAQJC3
DSNAQJC4
DSNAQJRM
DSNAQJS1
DSNAQJS2
DSNAQ3E1
LISTEND
UK74718 COVER LETTER END
UK74721 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47800 -
****************************************************************
* USERS AFFECTED: All Users of the IBM Data *
* Server Driver for JDBC and SQLJ *
1 ****************************************************************
* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and *
* SQLJ version 4.12.93 is provided by *
* this APAR ( JCCV41293 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for both DB2 z/OS V10 and DB2 z/OS V9 *
* ( JCCZOSDB2V10, JCCZOSDB2V9 ) *
* *
* This APAR delivers a service bundling *
* to release 4.12 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 Connectivities: Even with atomic multirow insert disabled,
the driver still throws a warning with the message "Atomic
batch is not supported by server. The batch was submitted,
but not in atomic mode." for a merge sql statement. This has
been fixed (wsdbu01004701)
____________________________________________________________
All Connectivities: If the license stored procedure is not
installed and sysplex is enabled, StackOverflowError might
occur. This problem has been fixed. (wsdbu00999416 )
____________________________________________________________
All Connectivities: A java.lang.IndexOutOfBoundsException
occurred when trying to retrieve an XML value which DB2
server has failed to return due to an SQL error. This has
been fixed to return the SQL error. (wsdbu00976992)
____________________________________________________________
All Connectivities: Driver sends incorrect time value to DB2
server using PreparedStatement.setObject() call.
setObject(x, "12:00 PM", java.sql.Types.TIME) method call
caused the driver to send "00:00" instead of "12:00"
to the
DB2 server. setObject(x, "12:00 AM", java.sql.Types.TIME)
method call caused the driver to send "12:00" instead of
"00:00" to the DB2 Server. This has been resolved.
(wsdbu00988877)
____________________________________________________________
All connectivities: When ":" exists in an sql statement and
the property "enableNamedParameterMarkers" is set to 1(YES),
the driver may mistaken the ":" as a Named Parameter Marker
even thought it is not one. And if there is standard parameter
markers in the same sql, the driver will throw a SQLCODE4463
(-4463) error with the message "Invalid parameter marker usage.
1 Named parameter markers and standard parameter markers may not
be used in the same statement." This problem has been fixed.
(wsdbu00731226)
____________________________________________________________
All connectivities: A new global override property
"db2.jcc.override.enableMultirowInsertSupport" is provided.
The default value is DB2BaseDataSource.NOT_SET(0). When it is
set to the default value or DB2BaseDataSource.YES(1), driver
will use multirow insert under executeBatch call targeting a
DB2 z/OS server V8 NFM or above. When it is set to
DB2BaseDataSource.NO(2), driver disables multirow insert
under executeBatch call. (wsdbu01004996)
____________________________________________________________
Type-2 z/OS Connectivity: DB2 ABEND may occur during an open
cursor call when targeting DB2 z/OS V10. This has been fixed
(wsdbu00997886)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, the driver
fails to do auto seamless failover when packages are bound
using keepDynamic on the DB2 server. Instead, the driver
throws a SQLCODE30108 (-30108) error. This has been fixed.
(wsdbu00991244)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, the driver
fails to balance the workload properly if an unexpected
disconnect exception occurs while trying to open a new
transport (physical connection) to DB2 when requested by an
application connection. This has been fixed. (wsdbu00982417)
(wsdbu00982417).
____________________________________________________________
Type-4 Connectivity: When an application invokes a Stored
Procedure against DB2 z/OS as a local transaction on an XA
connection, it fails with the error SQLCODE751 (-751).
This problem has been fixed. (wsdbu00992988)
____________________________________________________________
Type-4 Connectivity: With client affinities, HADR, or DB2
with data sharing (LUW only) environment, the driver can
wait for a long period of time (10 minutes or more) to close a
connection if all DB2 instances go down before the close. This
problem has been fixed. (wsdbu00723426)
____________________________________________________________
Type-4 Connectivity: The driver reports an unexpected
NullPointerException during the failover processing for
applications connecting to a data sharing or a HADR system.
This has been fixed. (wsdbu00738031)
____________________________________________________________
Type-4 Connectivity: Under sysplexWLB environment, if system
is heavy loaded with multiple threads competing with small
amount of the transport pool objects, the driver might get
distribution protocol error with SQLCODE4499 (-4499). This
problem has been fixed.(wsdbu00977620)
____________________________________________________________
Type-4 connectivity: If the target is v97FP4+ database
cataloged on LUW V95, the application may get various
Exceptions, one of the Exception is "Mutually exclusive fields
cannot both contain non-null values." The problem is fixed.
1 (wsdbu01005308)
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: PM47800
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAJJC1 PM47800
DSNAJJC2 PM47800
DSNAJ3CC PM47800
DSNAJ3CE PM47800
DSNAJ3CF PM47800
DSNAJ3CM PM47800
DSNAJ3C0 PM47800
DSNAJ3C1 PM47800
DSNAJ3C2 PM47800
DSNAJ3C3 PM47800
DSNAJ3C4 PM47800
DSNAJ3C5 PM47800
DSNAJ3C6 PM47800
DSNAJ3C7 PM47800
DSNAJ3C9 PM47800
DSNAJ6CC PM47800
DSNAJ6CE PM47800
DSNAJ6CF PM47800
DSNAJ6CM PM47800
DSNAJ6C0 PM47800
DSNAJ6C1 PM47800
DSNAJ6C2 PM47800
DSNAJ6C3 PM47800
DSNAJ6C4 PM47800
DSNAJ6C5 PM47800
DSNAJ6C6 PM47800
DSNAJ6C7 PM47800
DSNAJ6C9 PM47800
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47800 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
1 DSNAJ3C2
DSNAJ3C3
DSNAJ3C4
DSNAJ3C5
DSNAJ3C6
DSNAJ3C7
DSNAJ3C9
DSNAJ6CC
DSNAJ6CE
DSNAJ6CF
DSNAJ6CM
DSNAJ6C0
DSNAJ6C1
DSNAJ6C2
DSNAJ6C3
DSNAJ6C4
DSNAJ6C5
DSNAJ6C6
DSNAJ6C7
DSNAJ6C9
MACROS
DSNAJJC1
DSNAJJC2
LISTEND
UK74721 COVER LETTER END
UK74725 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM31940 -
****************************************************************
* USERS AFFECTED: None. This is a fix for a group restart- *
* related undocumented serviceability item. *
****************************************************************
* PROBLEM DESCRIPTION: Fix for a group restart-related *
* undocumented service feature. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Fix for a group restart-related undocumented service feature.
Fix for a group restart-related undocumented service feature.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM31940
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBNI PM31940
DSN1LDET PM31940
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM31940 DSNIDBNI DSN1LDET
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBNI
DSN1LDET
LISTEND
UK74725 COVER LETTER END
UK74731 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52239 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 users of data sharing. *
****************************************************************
* PROBLEM DESCRIPTION: AB04E RC00C90101 DSNIDM . *
* DSNIDBNG : 5009 when using DB2 *
* data sharing *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a thread processing a delete for an SCA entry is suspended
and subsequently canceled via a CANCEL THREAD command, the
thread does not exit properly, resulting in the symptom ABEND.
DB2 code has been changed to process the soft cancel correctly
in the scenario.
Additional Keyword: ABEND04E
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52239
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN7LRC1 PM52239
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52239 DSN7LRC1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN7LRC1
LISTEND
UK74731 COVER LETTER END
UK74737 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51155 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8 and DB2 9 for z/OS and *
* DB2 10 for z/OS users of LOAD utility in a *
1 * data sharing environment. *
****************************************************************
* PROBLEM DESCRIPTION: In data sharing environment, an endless *
* loop occurred during a LOAD ENFORCE *
* CONSTRAINTS INTO a table, created in *
* a segmented table space and has an *
* informational referential relationship *
* defined on it. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
In a data sharing environment, a LOAD ENFORCE CONSTRAINTS ran
on a table of a segmented table space, and it has an
informational RI defined on it.
LOAD fell into an endless loop when trying to sync the object
information between the DB2 members for RI processing. The
problem occurred because a variable was not reset properly.
The code has been modified to correct the reported problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51155
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGAFS PM51155
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51155 DSNUGAFS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGAFS
LISTEND
UK74737 COVER LETTER END
UK74745 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49235 -
****************************************************************
* USERS AFFECTED: All users of CATMAINT UPDATE SCHEMA SWITCH *
****************************************************************
* PROBLEM DESCRIPTION: CATMAINT UDPATE SCHEMA SWITCH MAY FAIL *
* UNEXPECTEDLY WITH ONE OF THE FOLLOWING *
* ERRORS: *
* 1. ABEND04E RC00E40601 in DSNUESCM *
* 2. Message DSNU767I with reason code 8 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. ABEND04E RC00E40601 in DSNUESCM:
The CATMAINT UPDATE SCHEMA SWITCH code commits changes when a
certain number of catalog records are updated. In cases where
1 the records have a parent/child relation and there is a commit
when processing child records, the internal cursor for the
parent record needs to be re-positioned before it can be
updated. However, the code did not take that into consideration
and therefore it failed with ABEND04E RC00E40601 in DSNUESCM
when updating the parent record.
2. Message DSNU767I with reason code 8:
CATMAINT UPDATE SCHEMA SWITCH prevents switching schema names
that are referenced in the check condition in the table
check constraints. This restriction was enforced by scanning
the content in SYSCHECKS.CHECKCONDITION. However, this scanning
produced false errors with DSNU767I messages.
DB2 code has been updated to prevent the errors.
Additional Keywords:
MSGDSNU767I
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49235
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUESCM PM49235
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49235 DSNUESCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUESCM
LISTEND
UK74745 COVER LETTER END
UK74747 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49788 -
****************************************************************
* USERS AFFECTED: All DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: RC00C200E2 from utility RECOVER *
* TABLESPACE DSNUM where DSNUM is greater *
* than one. It may happen when the *
* underlying data set of the DB2 managed *
* linear page set does not exist. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When encountering missing data set during page set reset, the
missing one will not be re-defined if the piece number (DSNUM)
is 2 or higher for a DB2 managed multi-piece linear page set.
As a result, RECOVER may fail with RC00C200E2.
1 The reset module is fixed to re-define the missing data set of
the DB2 managed linear page set.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49788
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNPRST1 PM49788
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49788 DSNPRST1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNPRST1
LISTEND
UK74747 COVER LETTER END
UK74778 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49120 -
****************************************************************
* USERS AFFECTED: REPAIR DBD TEST/DIAGNOSE users who fall back *
* from V10 CM or is in V10/V9 or V10/V8 *
* coexistence *
****************************************************************
* PROBLEM DESCRIPTION: REPAIR DBD TEST/DIAGNOSE reports errors *
* in unnamed fields for a table *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a DBD is changed in V10 CM mode, after fall back to V9 or V8,
REPAIR DBD TEST/DIAGNOSE may report errors on unnamed fields for
a table. This error can also occur in a V9 or V8 member in a
coexistence environment.
DB2 code is fix to reset the new OBDREFLL2 field in the prime
OBD when writing a DBD to DASD in V10 CM, so that REPAIR DBD
TEST/DIAGNOSE run in V8 or V9 will not incorrectly report
errors.
Applying this APAR will not fix DBDs has been changed in V10 CM
unless the DBD is changed again in V10 after APAR is applied.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49120
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCPD PM49120
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49120 DSNGDCPD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCPD
LISTEND
UK74778 COVER LETTER END
UK74779 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52548 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users who have queries *
* with IS NULL or LIKE predicates. *
****************************************************************
* PROBLEM DESCRIPTION: Abend 0C4 RC00000038 at DSNISPBM *
* offset 1A64 may occur during query *
* execution for queries containing *
* IS NULL or LIKE predicates, *
* and Explain shows that page range *
* screening is used. *
* (PLAN_TABLE. PAGE_RANGE = 'Y') *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend 0C4 RC00000038 at DSNISPBM offset 1A64 may occur during
query execution for queries containing IS NULL or LIKE
predicates, and Explain shows that page range screening is used.
(PLAN_TABLE. PAGE_RANGE = 'Y')
Additional keywords:
ABEND0C4 RC00000038 SQLLIKE SQLISNULL PAGERANGE
The problem is fixed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52548
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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.
To make this fix effective for a 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 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.
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPG2 PM52548
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52548 DSNXOPG2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPG2
LISTEND
UK74779 COVER LETTER END
UK74807 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53734 -
****************************************************************
* USERS AFFECTED: All users of DB2. *
****************************************************************
* PROBLEM DESCRIPTION: Improve BSDS latch monitoring for the *
* offload service task. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Improve BSDS latch monitoring for the offload service task.
1 BSDS latch monitoring has been improved to avoid abending
the offload service task with ABEND04F RC00D1F001 on low
priority or slow running systems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53734
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJOFF3 PM53734
DSN3EOTM PM53734
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53734 DSNJOFF3 DSN3EOTM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJOFF3
DSN3EOTM
LISTEND
UK74807 COVER LETTER END
UK74815 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50742 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40204 in DSNUGSPC, while *
* running a RUNSTATS SHRLEVEL CHANGE *
* utility against a partitioned table *
* space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend may occur if RUNSTATS releases its claim on a data or
index partition, and that partition gets physically closed.
Although RUNSTATS SHRLEVEL CHANGE acquires an allocation-
duration read claim, it may at some point also request a
commit-duration write claim which overrides the original claim
duration. So the claim will be released when the utility
issues a commit.
The claim logic has been modified to no longer allow a shorter-
duration claim request to downgrade the duration of an already-
held claim.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50742
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 DSNB1CLM PM50742
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50742 DSNB1CLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CLM
LISTEND
UK74815 COVER LETTER END
UK74866 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50516 -
****************************************************************
* USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users *
* with queries referencing columns with *
* significant data skew. *
****************************************************************
* PROBLEM DESCRIPTION: The compound filter factor calculated *
* by DB2 can be underestimated when the *
* product of the atomic filter factors *
* is greater than 1 divided by the *
* multi-column cardinality statistic. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The compound filter factor calculated by DB2 can be
underestimated when the product of the atomic filter factors
is greater than 1 divided by the multi-column cardinality
statistic.
This problem will only occur when there are multi-column
frequency statistics on the same column set as the multi-column
cardinality statistic. Further, it is unlikely that the
product of the atomic filter factors is high enough for
this problem to occur unless there is significant data
skew on one or more columns in the set.
For example, consider the following query where 90% of the
rows have C2=1 and COLCARDF(C1)=10.
SELECT ...
FROM T1
WHERE C1 = ?
AND C2 = 1
With a multi-column cardinality for (C1,C2) of 100, DB2
will incorrectly compute the compound filter factor of
the predicates on C1 and C2 as 1/100 = 1% if there are
multi-column frequency statistics on (C1,C2). The more
accurate compound filter factor is 90% * 1/10 = 9%.
1 Additional Keywords:
SQLPERFORMANCE SQLACCESSPATH SQLSTATS
DB2 has been modified to more accurately compute the compound
filter factor in this case.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50516
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGNC PM50516
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50516 DSNXOGNC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGNC
LISTEND
UK74866 COVER LETTER END
UK74868 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48066 -
****************************************************************
* USERS AFFECTED: All DB2 users processing tables with *
* referential integrity defined. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E 00E20004 LOC=DSNIPSI.DSNSVBK *
* +05FC. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While running MERGE statement on tables with RI relationships, a
false indication of the existence of Trigger can cause a TLST
block to be allocated unnecessarily. If users run those MERGE
statements in a long duration job, it eventually caused a
storage shortage in DB2.
1 DB2 has been fixed to correctly report the state about whether a
trigger exists in the involving table with RI defined.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48066
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRMRG PM48066
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48066 DSNXRMRG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRMRG
LISTEND
UK74868 COVER LETTER END
UK74881 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52336 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E50012 after MSGDSNL044I *
* indicating a WLM IWMECREA macro error *
* due to RC0C and RSN0C0C. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DDF attempts to create an enclave to process a client's
new unit-of-work, the request to create the enclave can fail
due to a temporary condition. DDF reports this error via the
DSNL044I message. However, DDF did not bypass the attempt to
schedule its current execution to run under an enclave. Since
an enclave token does not exist, the attempt fails and DB2
task abended with reason code 00E50012.
DB2 has been changed to continue running the unit-of-work as
a normal SRB when a temporary error is detected during the
attempt to create an enclave.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52336
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVSDC0 PM52336
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PM52336 DSNVSDC0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVSDC0
LISTEND
UK74881 COVER LETTER END
UK74884 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52474 -
****************************************************************
* USERS AFFECTED: All DB2 users who execute pre-V10 plans *
* with DBRMs directly bound. *
****************************************************************
* PROBLEM DESCRIPTION: Executing a pre-V10 plan with DBRMs *
* directly bound, users may experience *
* the following two problems: *
* 1. If there are rows associated with *
* this plan in SYSIBM.SYSPLSYSTEM *
* table, then executing this plan *
* may result the following abend: *
* ABEND04E RC00C90101 at DSNIBNRF+5002 *
* *
* 2. If the plan has been successfully *
* executed, then the following values *
* are populated into PATHSCHEMAS *
* column of SYSIBM.SYSPACKAGE table, *
* even though the plan uses default *
* path schemas: *
* "SYSIBM, SYSFUN, SYSPROC and *
* <plan qualifier>".
*
****************************************************************
* RECOMMENDATION: *
****************************************************************
There are two problems identified, and both are related to
DBRM-to-PACKAGE conversion during automatic rebind.
The first problem is that when executing a pre-V10 plan with
DBRMs directly bound, DB2 automatically rebinds the plan, and
converts the DBRMs into packages. If the plan has associated
rows in SYSIBM.SYSPLSYSTEM table, DB2 fails to restore an
internal pointer, and causes an abend during such a process.
The second problem is that according to the DB2 SQL Reference,
the PATHSCHEMAS column of SYSIBM.SYSPACKAGE should not contain
any value if the default path value is in effect. However,
during DBRM to package conversion triggered by automatic rebind,
DB2 populates the PATHSCEHMAS column with SYSIBM, SYSFUN,
SYSPROC and plan qualifier, even though the parent plan uses
the default path value. This behavior does not cause any problem
with the plan or package, but is inconsistent with the SQL
Reference.
DB2 has been fixed to restore the pointer during automatic
1 rebind, and not populate the default path values into
PATHSCHEMAS column of SYSIBM.SYSPACKAGE if the plan uses the
default path.
Note that the packages which already have the default path value
in the PATHSCHEMAS column do not cause any problems during
execution because those are the actual paths DB2 internally
uses to resolve unqualified data.
Additional Keywords:
ABEND04E RC00C90101 ERQUAL5002 PATHSCHEMAS PATH
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52474
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAB PM52474
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52474 DSNTBAB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBAB
LISTEND
UK74884 COVER LETTER END
UK74911 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51089 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* RUNSTATS utility users with multi-column *
* key partitioned indexes. *
****************************************************************
* PROBLEM DESCRIPTION: INCORROUT FIRSTKEYCARD in MSGDSNU617I *
* and in SYSIBM.SYSINDEXES catalog *
* table. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
The user collected statistics using a mix of RUNSTATS
TABLESPACE PART and RUNSTATS INDEX PART utility jobs
on a multi-column key partititoned index with non-unique
values spanning across parts, which resulted in incorrect
FIRSTKEYCARDF statistics being gathered for the index in
SYSIBM.SYSINDEXES catalog table. The FIRSTKEYCARDF value
in MSGDSNU617I was incorrect for the partitioned index.
The FIRSTKEYCARDF value was incorrect because of the mix of
statistics collected via the tablespace and index scans.
Another cause for incorrect FIRSTKEYCARDF statistics was
1 an incorrect variable being used in the algorithm.
The code was changed to better estimate the FIRSTKEYCARDF
statistic, when RUNSTATS INDEX PART is specified on the
multi-column key partitioned index having a low cardinality
and high number of index partitions.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51089
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSACO PM51089
DSNUSAIX PM51089
DSNUSEOF PM51089
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51089 DSNUSACO DSNUSAIX DSNUSEOF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSACO
DSNUSAIX
DSNUSEOF
LISTEND
UK74911 COVER LETTER END
UK74922 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51556 -
****************************************************************
* USERS AFFECTED: All DB2 10 users that have stored procedures *
* bound when the DB2 install parameter *
* DESCSTAT = NO *
****************************************************************
* PROBLEM DESCRIPTION: AB04E RC00E70005 DSNXEBR : M303 on *
* DB2 10 while running a stored procedure *
* bound when the DB2 install parameter *
* DESCSTAT = NO. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While processing a stored procedure bound with DESCSTAT = NO,
DB2 took an incorrect code path and accessed invalid internal
control blocks, leading to the symptom ABEND.
DB2 code has been corrected to take the correct code path in
the scenario listed above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51556
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
DSNXEBR PM51556
DSNXEBR9 PM51556
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51556 DSNXEBR DSNXEBR9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXEBR9
LISTEND
UK74922 COVER LETTER END
UK74940 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50552 -
****************************************************************
* USERS AFFECTED: All DB2 10 users of special register EXPLAIN *
* MODE or of SQL statement EXPLAIN PACKAGE *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -552 received when running *
* a dynamic SQL statement that was *
* successfully prepared when special *
* register CURRENT EXPLAIN MODE = YES . *
* . *
* SQLCODE -552 received when running *
* SQL statement EXPLAIN PACKAGE and *
* the current authID has SQLADM privilege *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After a dynamic SQL statement is successfully prepared when
special register CURRENT EXPLAIN MODE = YES , no other authority
or privilege, not even SQLADM, should be required to execute
that prepared statement when EXPLAIN MODE = YES and populate
the DSN_STATEMENT_CACHE_TABLE for that single dynamic statement.
For this scenario DB2 invalidly failed the execution of the
successfully prepared statement with authority failure
SQLCODE552 .
.
For the SQL statement EXPLAIN PACKAGE that explains static SQL
statements in a DB2 package, the user's attempt to issue
EXPLAIN PACKAGE using SQLADM authority failed with SQLCODE552.
However, an authID having the SQLADM privilege should have been
allowed to successfully issue EXPLAIN PACKAGE, but DB2 invalidly
failed the attempt.
.
For executing successfully prepared dynamic SQL under EXPLAIN
MODE = YES , DB2 code was modified to not require additional
privileges and SQLCODE -552 is no longer issued.
.
For executing EXPLAIN PACKAGE, DB2 code was modified to accept
1 SQLADM authority and SQLCODE -552 is no longer issued.
.
Additional search keywords: SQLEXPLAIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50552
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEXPL PM50552
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50552 DSNXEXPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEXPL
LISTEND
UK74940 COVER LETTER END
UK74968 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51765 -
****************************************************************
* USERS AFFECTED: DB2 users of stored procedures and *
* User Defined Functions (UDFs). *
****************************************************************
* PROBLEM DESCRIPTION: The following abend occurs when *
* forcing the address space down: *
* 0C4-00000011, *
* LOC=DSNTGSCC.DSNTBAB +157A *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The task is in the middle of an autobind processing.
Since the address space is forced down, the recovery process
keeps trying to terminate the task while the autobind is still
going on. This finally results in the abend since recovery have
cleaned up the DB2 control block which is still needed by the
autobind.
Stored procedure end of memory processing has been enhanced
so that in some situations, the recovery won't aggressively
terminate the tasks.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51765
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9MON PM51765
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51765 DSNX9MON
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9MON
LISTEND
UK74968 COVER LETTER END
UK74981 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52327 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Long request elapsed times with high *
* CPU consumption is observed when *
* connecting to remote locations. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 10 for z/OS Distributed Data Facility (DDF) processing
was enhanced to recognize any update to the Communications
DataBase (CDB), specifically any update that altered the
configuration for communications to any remote location via
TCP/IP, without the need to first stop and then start DDF once
the update was made.
However, the support only checked that an object with a PSID of
X'00D6' (214) was being processed by an insert, update, or
delete operation. The SYSDDF tablespace of the catalog
database (DSNDB06) does have a PSID of 214, but since the PSID
of an object is unique only within a given database (DBID),
other objects which have a PSID of 214 in other databases will
incorrectly trigger the online notification of a CDB update.
As a result of incorrectly detecting a CDB change, and as a
result of an additional logic error that fails to detect the
existence of associated cached information that already exists,
DB2 generates duplicate cached information. Over time, with
many falsely detected updates to the CDB, cache related control
block chains become excessively long. This causes an
unnecessary over utilization of storage and causes excessive
consumption of CPU to search the entire chain.
DB2 has been changed to check for both the DBID and PSID of
the object being updated to ensure that the updated object
reflects the CDB tablespace, DSNDB06.SYSDDF, before triggering
an event that an update has occurred to the CDB. Also, if a
valid update has been made to the CDB, DDF has been changed to
correctly match an existing cached location entry if there was
no change in the CDB to a location's specification. Finally,
if an application decides to rollback any change being made to
the CDB, DB2 has been changed to ensure that the notification
1 of an update to the CDB is terminated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52327
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 PM52327
DSNISRTI PM52327
DSNITDLE PM52327
DSNLVCIP PM52327
DSNTABA PM52327
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52327 DSNILREP DSNISRTI DSNITDLE DSNLVCIP DSNTABA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
DSNISRTI
DSNITDLE
DSNLVCIP
DSNTABA
LISTEND
UK74981 COVER LETTER END
UK74989 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48397 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD *
****************************************************************
* PROBLEM DESCRIPTION: Restart of a LOAD INCURSOR utility *
* that abended in the SORT phase resulted *
* in ABEND04E RC00E40005 from DSNUGSOR *
* and messages MSGICE017A - INVALID *
* POSITION OR LENGTH IN CONTROL FIELD - *
* REASON CODE IS 06 and MSGICE012A - *
* MISSING FIELDS OPERAND DEFINER are *
* issued. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
Restart of a LOAD INCURSOR utility that had originally abended
in the SORT phase, ended with an ABEND04E RC00E40005 from
DSNUGSOR. Also, messages MSGICE017A - INVALID POSITION OR
LENGTH IN CONTROL FIELD - REASON CODE IS 06 and MSGICE012A -
MISSING FIELDS OPERAND DEFINER are issued.
An example of the invalid parameter is (from the joblog - the
underlined portion is the value in error):
1
SORT FIELDS=
(00006.0,00000.4,A,00012.0,00002.0,A,00001.0,00001.5,A,0001*
4.0,00000.0,A,00001.0,00005.0,A)
_______
A valid parameter would be:
SORT FIELDS=
(00006.0,00000.4,A,00012.0,00002.0,A,00001.0,00001.5,A,0001*
4.0,00219.0,A,00001.0,00005.0,A)
_______
The abend occurred because the parameter list passed to DFSORT
did not have the correct offset for the index(es) that were
defined on the table. DFSORT abended it's process when it
discovered the invalid parameter.
This abend could also occur on a LOAD utility that does not
specify INCURSOR.
LOAD restart code has been changed to correctly set up the
offset(s) for the SORT FIELDS parameter(s).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48397
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURSIX PM48397
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48397 DSNURSIX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURSIX
LISTEND
UK74989 COVER LETTER END
UK75093 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52747 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V9 and V10 users of ACCESS *
* DATABASE COMMAND. *
****************************************************************
* PROBLEM DESCRIPTION: Not all pagesets of the databases are *
* opened or becoming non-group buffer *
* pool dependent when issuing the ACCESS *
* ACCESS DATABASE SPACENAM MODE(OPEN) or *
* MODE(NGBPDEP) with specifying the *
1 * database-name and space-name with *
* wildcard. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While processing the ACCESS DATABASE command for multiple spaces
in the databases , the command code doesn't initialize a loop
variable correctly which cause the reported problem.
The command code has been fixed to correctly initialize the
loop variable.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52747
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 PM52747
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52747 DSNILSTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILSTS
LISTEND
UK75093 COVER LETTER END
UK75105 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50598 -
****************************************************************
* USERS AFFECTED: Users who alter a table with decimal column *
* created prior to V8 *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C7 in load module DSNIDM csect *
* DSNIMOFR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A table with decimal column was created prior to V8. After a
series of ALTERs to the table, MODIFY RECOVERY, and REPAIR DBD
REBUILD is done, an abend in DSNIMOFR may occur when DB2 tries
to convert the decimal column value when it does not need to.
Other unexpected abends or incorrout can occur when the decimal
column is referenced.
This APAR also fixes a problem where OBD prime is not inserted
into SYSIBM.SYSOBDS when it is created to store the old
precision/scale values on altering a decimal column. This will
result in REPAIR DBD TEST/DIAGNOSE falsely reporting an error on
field OBDRX2OBD_PRIME_OFFSET like the following:
1 DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'xxxxxxxx'
OBDRX2OBD_PRIME_OFFSET
DSNU904I DSNUEDRT - EXISTING VALUE X'xxxx'
DSNU905I DSNUEDRT - REBUILT VALUE X'0000'
DB2 is fixed to not convert the decimal column when it is not
needed, the abend problem is fixed after applying this APAR.
Code is fixed to correctly insert a SYSIBM.SYSOBDS record when
an OBD prime is created to store the old precision/scale on
altering a decimal column.
This APAR will not fix the existing missing SYSIBM.SYSOBDS
record problem. When REPAIR DBD TEST/DIAGNOSE reports an error
on field OBDRX2OBD_PRIME_OFFSET, REPAIR DBD REBUILD is NOT
recommended until MODIFY RECOVERY is run to purge all old
versions of the table.
Additional Keyword: SQLALTER INCORROUT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50598
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 PM50598
DSNIADR PM50598
DSNIBNRF PM50598
DSNICRFT PM50598
DSNICUMW PM50598
DSNIDIFS PM50598
DSNIDLER PM50598
DSNIESEN PM50598
DSNIETRV PM50598
DSNIHSET PM50598
DSNIIDIS PM50598
DSNIKDEF PM50598
DSNIKESR PM50598
DSNILREP PM50598
DSNIMNEX PM50598
DSNIMOFK PM50598
DSNIMOFR PM50598
DSNINUKY PM50598
DSNIONX2 PM50598
DSNIOST2 PM50598
DSNIRELK PM50598
DSNIRFNX PM50598
DSNIRIDL PM50598
DSNIRLPG PM50598
DSNIRNXT PM50598
DSNIRPRE PM50598
DSNIRSET PM50598
DSNISFRL PM50598
DSNISFS PM50598
DSNISFWL PM50598
DSNISFX2 PM50598
1 DSNISPBM PM50598
DSNISRID PM50598
DSNITDLE PM50598
DSNIWNRF PM50598
DSNIXLDI PM50598
DSNIZMOS PM50598
DSNKFLRR PM50598
DSNKFLST PM50598
DSNKFPRV PM50598
DSNKFTCH PM50598
DSNKFTRR PM50598
DSNKMVKY PM50598
DSNKNXT2 PM50598
DSNOLDEL PM50598
DSNUULCA PM50598
DSNUUSEL PM50598
DSNXIATB PM50598
DSNXOPBM PM50598
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50598 DSNIACCH DSNIADR DSNIBNRF DSNICRFT DSNICUMW DSNIDIFS
DSNIDLER DSNIESEN DSNIETRV DSNIHSET DSNIIDIS DSNIKDEF
DSNIKESR DSNILREP DSNIMNEX DSNIMOFK DSNIMOFR DSNINUKY
DSNIONX2 DSNIOST2 DSNIRELK DSNIRFNX DSNIRIDL DSNIRLPG
DSNIRNXT DSNIRPRE DSNIRSET DSNISFRL DSNISFS DSNISFWL
DSNISFX2 DSNISPBM DSNISRID DSNITDLE DSNIWNRF DSNIXLDI
DSNIZMOS DSNKFLRR DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR
DSNKMVKY DSNKNXT2 DSNOLDEL DSNUULCA DSNUUSEL DSNXIATB
DSNXOPBM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNIADR
DSNIBNRF
DSNICRFT
DSNICUMW
DSNIDIFS
DSNIDLER
DSNIESEN
DSNIETRV
DSNIHSET
DSNIIDIS
DSNIKDEF
DSNIKESR
DSNILREP
DSNIMNEX
DSNIMOFK
DSNIMOFR
DSNINUKY
DSNIONX2
DSNIOST2
DSNIRELK
DSNIRFNX
DSNIRIDL
1 DSNIRLPG
DSNIRNXT
DSNIRPRE
DSNIRSET
DSNISFRL
DSNISFS
DSNISFWL
DSNISFX2
DSNISPBM
DSNISRID
DSNITDLE
DSNIWNRF
DSNIXLDI
DSNIZMOS
DSNKFLRR
DSNKFLST
DSNKFPRV
DSNKFTCH
DSNKFTRR
DSNKMVKY
DSNKNXT2
DSNOLDEL
DSNUULCA
DSNUUSEL
DSNXIATB
DSNXOPBM
LISTEND
UK75105 COVER LETTER END
UK75106 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47601 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of COPY utility *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C20305 DSNB1PCP:22DA *
* during COPY utility with SCOPE PENDING *
* on a list of partitions of a table *
* space and its index(es). *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran COPY utility with SCOPE PENDING to copy the partitions
of a table space and its index space using SCOPE PENDING when
the index was in informational copy pending (ICOPY) state.
The COPY utility abended with ABEND04E RC00C20305 because in
some instances the code needed to properly establish partition
numbers for each object being copied was mistakenly skipped.
The same problem occurs for CONCURRENT COPY.
COPY utility is modified not to bypass initialization code when
it is needed for table spaces whose indexes are in COPY or ICOPY
state.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM47601
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBACI PM47601
DSNUBAII PM47601
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47601 DSNUBACI DSNUBAII
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBACI
DSNUBAII
LISTEND
UK75106 COVER LETTER END
UK75161 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47255 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of LOAD utility with XML columns. *
****************************************************************
* PROBLEM DESCRIPTION: Data row and XML column data loaded *
* erroneously after MSGDSNU283I and *
* SQLCODE -20345 occur during a LOAD *
* utility with DISCARDS processing. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD SHRLEVEL CHANGE DISCARDS utility on a table with an XML
column issued DSNU283I - XML error SQLCODE = -20345 and ended
with RC4. The XML error was valid, however, DISCARDS processing
was not complete and the row and XML data remained in the
tables. LOAD SHRLEVEL CHANGE insert processing was not driving
a delete of the data row or the XML column data.
In DB2 10 for z/OS, the LOAD SHRLEVEL CHANGE utility abends
with an ABEND04E RC00E41002 after the XML error SQLCODE20345
is encountered.
LOAD SHRLEVEL CHANGE utility code has been modified to drive
through the INDEXVAL phase to delete the row and XML column
data when an XML error occurs. The utility output will now
include MSGDSNU355I and MSGDSNU356I messages. DB2 10 will
no longer abend in this circumstance.
DSNU355I - DSNURVIX - INDEXVAL PHASE STATISTICS - n DUPLICATE
KEY ERRORS, KEY EVALUATION ERRORS, XML ERRORS, OR LOB ERRORS
WERE CORRECTED BY DELETING n DATA ROWS
1 DSNU356I DSNURVIX - INDEXVAL PHASE COMPLETE, ELAPSED TIME=
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47255
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM47255 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDILS PM47255
DSNURELD PM47255
DSNURVAL PM47255
DSNURWBF PM47255
DSNURWI PM47255
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47255 DSNIDILS DSNURELD DSNURVAL DSNURWBF DSNURWI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDILS
DSNURELD
DSNURVAL
DSNURWBF
DSNURWI
LISTEND
UK75161 COVER LETTER END
UK75202 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM37423 -
****************************************************************
* USERS AFFECTED: All users of index on expression and *
* spatial index. *
****************************************************************
* PROBLEM DESCRIPTION: REPAIR DBD reported error at *
* offset X'00000122' for *
* OBDKT_PRECISION. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
There are two problems that can cause the reported mismatch in
the OBD during REPAIR DBD processing.
First problem:
During CREATE/ALTER processing, DB2 did not handle the precision
of certain data types correctly for index on expression and
spatial index. This may result in an incorrect value being
recorded in SYSKEYTARGETS.SCALE or the index OBD.
Second problem:
REPAIR DBD did not handle the precision of certain data types
correctly in SYSKEYTARGETS for index on expression and spatial
index. This may result in REPAIR DBD incorrectly reporting an
error for the index.
The following is a sample of the reported error:
DSNU920I DSNUEDFT - OBDS DIFFER AT OFFSET X'00000122'
OBDKT_PRECISION(3)
DSNU904I DSNUEDFT - EXISTING VALUE X'00'
DSNU905I DSNUEDFT - REBUILT VALUE X'0C'
DSNU913I DSNUEDDR - OBD X'00A0' COMPARISON COMPLETE --
1 ERRORS WERE FOUND
Please note that these errors may cause other unpredictable
behaviors.
DB2 has been fixed to handle the precision of data types
correctly for index on expression and spatial index.
Affected indexes can be dropped and recreated to correct the
error.
Additional Keywords:
SQLCREATE
SQLALTER
SQLINDEX
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM37423
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDAIX PM37423
DSNGDBIX PM37423
DSNUEXDB PM37423
DSNXIIKY PM37423
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM37423 DSNGDAIX DSNGDBIX DSNUEXDB DSNXIIKY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDAIX
DSNGDBIX
1 DSNUEXDB
DSNXIIKY
LISTEND
UK75202 COVER LETTER END
UK75208 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51950 -
****************************************************************
* USERS AFFECTED: DB2 customers using hash organization. *
****************************************************************
* PROBLEM DESCRIPTION: Storage overlay resulting in various *
* 0C4 abends during REORG of a *
* hash table space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Serviceability is needed to trap storage overlay closer to the
time of its occurrence so that the cause of the overlay can be
determined.
Additional sanity checks are introduced. If a storage overlay
occurs, these checks will catch the problem sooner.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51950
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 PM51950
DSNIRFNX PM51950
DSNIRIDR PM51950
DSNIRLPG PM51950
DSNISRTI PM51950
DSNUCRUL PM51950
DSNUKIUL PM51950
DSNURFBR PM51950
DSNURSCN PM51950
DSNUSTBL PM51950
DSNUULXA PM51950
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51950 DSNIACCH DSNIRFNX DSNIRIDR DSNIRLPG DSNISRTI DSNUCRUL
DSNUKIUL DSNURFBR DSNURSCN DSNUSTBL DSNUULXA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNIRFNX
DSNIRIDR
DSNIRLPG
DSNISRTI
DSNUCRUL
1 DSNUKIUL
DSNURFBR
DSNURSCN
DSNUSTBL
DSNUULXA
LISTEND
UK75208 COVER LETTER END
UK75229 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48763 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS version 9 and version 10 *
* users of REPAIR VERSIONS Utility who have *
* applied APAR PM27940/PTF UK69816 *
* /PTF UK69817. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90110 DSNIROBD:5383 *
* might occur when running Utility Repair *
* Versions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
PM27940 enhanced the check of version information by retrieving
the OBDREC information from the system page. If user copies data
from one system to the other without ensuring the objects match
between two systems, the inconsistency of the objects can cause
abend from retrieval of the OBDREC. The possible error could be
mismatch of the OBID, table was dropped from target system, etc.
DB2 code has been fixed to ignore that OBDREC or OBDREC ID
exists in the system page but not in the catalog of the target
system for Repair Versions Utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48763
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIVGET PM48763
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48763 DSNIVGET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIVGET
LISTEND
UK75229 COVER LETTER END
UK75234 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM42532 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS that use plans *
* or packages bound with USECURRENTLYCOMMITTED *
* or statements prepared with USE CURRENTLY *
* COMMITTED *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C200A2 at DSNIRNXT+A86A *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This problem occurs when the all of the following conditions
are met:
1. table space scan
2. a plan or package bound with USECURRENTLYCOMMITTED
or
a statement prepared with USE CURRENTLY COMMITTED
3. row level locking
During the scan, DB2 failed to reinitialize a bit when
looping through the records on a page to find a qualifying
record. As a result it locked a pointer subrecord twice
and acquired a latch on the pointer subrecord. DB2 then
tried to get the latch again and this caused the abend
because it already held the latch.
The bit used during table space scan to indicate whether the
record is uncommitted is re-initialized for each iteration of
the loop that loops through the records on a page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM42532
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRNXT PM42532
DSNIRPRE PM42532
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM42532 DSNIRNXT DSNIRPRE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRNXT
DSNIRPRE
LISTEND
UK75234 COVER LETTER END
UK75262 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52543 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Following a GBP structure failure, *
* attempts to rebuild that structure may *
* repeatedly fail with MSGDSNB335I and *
* RSN00C20205. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A couple of timing windows exist between the damage assessment
process for a failed GBP structure, and the deallocation of that
GBP and its associated buffer pool. These windows can leave the
GBP marked as "GBP recover pending" in the DB2 control
blocks,
which can in turn lead to subsequent rebuild failures with
RSN00C20205.
DB2 code has been modified to ensure that the "GBP recovery
pending" status for a group buffer pool is cleared either when
the buffer pool is being deallocated during damage assessment,
or at the next GBP allocation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52543
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1GC1 PM52543
DSNB1TXP PM52543
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52543 DSNB1GC1 DSNB1TXP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1GC1
DSNB1TXP
LISTEND
UK75262 COVER LETTER END
UK75286 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53010 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS Version 10. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00D10269 in DSNJW107. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A DB2 thread was preempted while holding the log-write
latch, and after the buffer use count was incremented. This
was preventing the log write engine from externalizing the log
records. The log writer detected that the process had stalled
and abended in DSNJW107 with an ABEND04E RC00D10269 instead of
1 waiting indefinitely. The system only had 1 online, non-zIIP
or non-zAAP CPU and the preempted thread had not been
dispatched for over 3 minutes.
The stalled log record build detection in DSNJW107 has been
improved for systems with limited CPUs available.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53010
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJW107 PM53010
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53010 DSNJW107
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW107
LISTEND
UK75286 COVER LETTER END
UK75291 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49645 -
****************************************************************
* USERS AFFECTED: All DB2 9, DB2 10 for z/OS users of *
* SELECT from INSERT/UPDATE/DELETE/MERGE *
* statement. *
****************************************************************
* PROBLEM DESCRIPTION: Abend04E at DSNXESX2:M999 *
* for a SELECT from INSERT/DELETE *
* UPDATE/MERGE statement that *
* contains an include column and *
* an EXISTS correlated subquery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend04E at DSNXESX2:M999 for a SELECT from INSERT/DELETE
UPDATE/MERGE statement that contains an include column and
an EXISTS correlated subquery.
For Example,
SELECT *
FROM FINAL TABLE(
UPDATE TB INCLUDE (CIN5 CHAR(5))
SET C1 = 'A1', CIN5 = C1
WHERE EXISTS (SELECT 1 FROM T2
WHERE T2.C1 = TB.C1 AND T2.C1 = 'A'));
The abend occurs for the above statement because DB2 does not
handle the correlated subquery and the include column correctly.
1 DB2 was fixed to handle the subquery and the include column
in the SELECT from INSERT/UPDATE/MERGE/DELETE statement
correctly.
Additional Keywords: SQLSELWINSERT SQLSELWUPDATE
SQLSELWMERGE SQLCORRSUBQ SQLSELWDELETE
SQLCORRSUBQ SQLEXISTS SQLSUBQUERY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49645
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM49645:
See PM49645 APAR/PTF text for additional information about
why a REBIND is necessary.
PM49645 corrects a problem of abend0E4 at DSNXESX2:M999
for a SELECT from INSERT/UPDATE/MERGE/DELETE statement
that contain an include column and an EXISTS correlated
subquery.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
See PM43916 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM43916 corrects a problem where a query with
INSERT/UPDATE/DELETE within a SELECT statement hits SQLCODE
-20478 error since the estimated query cost has a mismatch
between the SQLCA and GET DIAGNOSTICS area.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOIN PM49645
DSNXOIWS PM49645
DSNXOST PM49645
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49645 DSNXOIN DSNXOIWS DSNXOST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOIN
DSNXOIWS
DSNXOST
1 LISTEND
UK75291 COVER LETTER END
UK75294 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53029 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR is to provide a DB2 *
* serviceability enhancement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides serviceability functions
for IBM Service and has no external symptoms
or changes.
This APAR provides serviceability functions for IBM Service.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53029
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOST PM53029
DSNXOTL PM53029
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53029 DSNXOST DSNXOTL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOST
DSNXOTL
LISTEND
UK75294 COVER LETTER END
UK75317 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51845 -
****************************************************************
* USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: 1. ABEND0C6 may occur in DXRRL2P1 *
* during recovery in IRLM for ABEND015F, *
* causing IRLM to terminate. *
* 2. IRLM may not come down after issuing *
* F irlmproc,abend,nodump command. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
1 ****************************************************************
When a workunit executing in IRLM gets starved for cpu cycles
IRLM may issue SYSEVENT ENQHOLD to boost the dispatch priority
of the caller. In a certain timing window, the caller may
already have gone and IRLM could end up issuing ENQRLSE with
invalid parms. This may cause ABENDS15F to be issued by SRM.
IRLM recovery handles this error and during the cleanup process
IRLM may free the workarea storage (RHWKA) for the interrupted
request. This causes problems as that RHWKA could be in use
at that time.
In another situation where a user is attempting to bring down
IRLM by issuing F irlmproc,abend,nodump command
IRLM may stay up resulting in DB2 restart failure later on.
When IRLM processes a QUIT request while there were pending SRBs
scheduled for Deadlock or Timeout drive in DBMS Exits, IRLM
will keep its internal usecount up which will prevent the
QUIT from being processed. If DBMS address space goes away
without resuming those SRBs back to IRLM, IRLM will remain up.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
IRLM recovery code for ABEND015F is updated to handle the
recovery correctly and not cause IRLM to terminate.
IRLM health checking is updated to clear the IRLM usecount that
could remain up as a result of DBMS address space terminating
when a F irlmproc,abend,nodump command was processed.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM51845
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL272 PM51845
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51845 DXRRL272
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL272
LISTEND
UK75317 COVER LETTER END
UK75322 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM40627 -
****************************************************************
* USERS AFFECTED: All DB2 zOS V10 customers using table space *
* scan. *
****************************************************************
1 * PROBLEM DESCRIPTION: More detailed information is needed in *
* some data manager internal traces for *
* debugging and serviceability. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSNIRNXT:5001 abend is seen when Data Manager services are
requested with residual values in the interface block.
Serviceability is improved to detect where the residual values
are coming from. More details are added in some DM internal
trace entries. Error handling is cleaned up in one place.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM40627
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBMIR PM40627
DSNILKDY PM40627
DSNIRNXT PM40627
DSNISUPI PM40627
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM40627 DSNIBMIR DSNILKDY DSNIRNXT DSNISUPI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBMIR
DSNILKDY
DSNIRNXT
DSNISUPI
LISTEND
UK75322 COVER LETTER END
UK75335 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53165 -
****************************************************************
* USERS AFFECTED: All users of DSNTWLMB (batch program for *
* adding a WLM application environment) in *
* DB2 10 for z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: When reading input from the SYSIN DD, *
* the DSNTWLMB program injects a blank *
* character if a token splits or wraps *
* onto the next physical input record. *
* The error occurs only if columns 72 *
* to 80 of the wrapped input record *
* contains non-blanks. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 The DSNTWLMB program provides a batch interface for defining,
installing, and activating WLM environments. It is invoked by
DB2 installation job DSNTIJRW to create the core DB2 WLM
environments.
DSNTWLMB reads from the SYSIN DD to obtain the configuration
parameters for creating a WLM environment. The parameters can
be entered on one line (up to 72 characters per line) or
multiple lines. Currently, when a parameter token is split or
wrapped onto more than one physical input record, DSNTWLMB
injects a blank character at the point where the token is split.
The error occurs only if the wrapped record contains non-blanks,
such as sequence numbers, in columns 73 to 80.
In response, DSNTWLMB is corrected so that a blank character is
not injected when a configuration parameter token splits or
wraps onto the next line. The behavior is the same regardless
of whether the wrapped record contains non-blanks in columns 73
to 80.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53165
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 PM53165
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53165 DSNTWLMB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTWLMB
LISTEND
UK75335 COVER LETTER END
UK75385 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53740 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS executing a *
* remote BIND PACKAGE command. *
****************************************************************
* PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE *
* FOLLOWING REPORTED SYMPTOMS: *
* *
* ABEND0C4 RC0000003B *
* CSECT DSNSVBK OFFSET1302 *
* *
* PROBLEM SCENARIO: *
* *
* The reported error occurred when *
1 * attempting a BIND PACKAGE DEPLOY of *
* a native stored procedure from a DB2 *
* V10(CM9) subsystem to another V10(CM9) *
* subsystem. The problem may occur on *
* any remote BIND PACKAGE operation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SUMMARY OF DB2 EVENTS:
DB2 was attempting to acquire more storage to accommodate the
size of a large statement. This resulted in an error as the
storage release mechanism was pointing to an incorrect
address.
PROBLEM CONCLUSION:
DB2 has been fixed to point to the correct address when
releasing storage acquired for statement usage.
ADDITIONAL KEYWORDS:
BIND DEPLOY SQLSTORAGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53740
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAS2 PM53740
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53740 DSNTBAS2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBAS2
LISTEND
UK75385 COVER LETTER END
UK75395 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52720 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of the IPCS *
* DSNWDMP VERBX. *
****************************************************************
* PROBLEM DESCRIPTION: Stack detail information in the DS=#, *
* ST=# report was not complete for most *
* agents. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DS=#,ST=# would not display stack detail information unless
all agent stack storage was available for processing.
The DS=#,ST=# report has been enhanced to display as much
1 stack detail as possible for a given agent.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52720
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWDFSK PM52720
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52720 DSNWDFSK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWDFSK
LISTEND
UK75395 COVER LETTER END
UK75452 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53990 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, and DB2 10 for z/OS *
* utility users with ZPARM UTSORTAL=YES *
****************************************************************
* PROBLEM DESCRIPTION: Utility fails with ABEND04E RC00E40005 *
* and ABEND04E RC00E40347 after DFSORT *
* failed with MSGICE046A SORT CAPACITY *
* EXCEEDED after sort work data sets *
* failed to be extended with ABENDSB37. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
DFSORT fails with ICE046A SORT CAPACITY EXCEEDED even though
the record number passed in FILSZ is correct. The sort work
data sets are allocated by the utility as indicated by message
DSNU3340I UTILITY PERFORMS DYNAMIC ALLOCATION OF SORT DISK
SPACE. These data sets are not allocated in sufficient size
and failed to extend when receiving an ABENDB37 in the
following situations:
1. Short fixed records sorted in DFSORT.
2. Very disordered data sorted in DFSORT under DB2 10.
Enhance the allocation of sort work data sets to better handle
short fixed records and very disorganized data in DB2 10.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53990
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
DSNUGALC PM53990
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53990 DSNUGALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGALC
LISTEND
UK75452 COVER LETTER END
UK75551 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52154 -
****************************************************************
* USERS AFFECTED: DB2 9 and 10 for z/OS users of *
* materialized query tables (MQT) *
* referencing a user-defined function *
* or cast function. *
****************************************************************
* PROBLEM DESCRIPTION: DROP TABLESPACE results in *
* ABEND04E RC00E70006 at DSNXIDST:P120 *
* when the table space specified contains *
* an MQT which references a user- *
* defined function or cast function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Dropping an MQT which references a user-defined function
or cast function may result in ABEND04E RC00E70006 at
DSNXIDST:P120.
Dropping an MQT which references a user-defined function
or cast function has been fixed to prevent the reported
abend. This includes an explicit DROP TABLE referencing the
MQT or any DROP which causes the MQT to be dropped implicitly
such as dropping the database or table space which contains
the MQT.
ADDITIONAL KEYWORDS:
SQLDROP
SQLMQT
SQLUDF
SQLFUNCTION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52154
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIDST PM52154
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52154 DSNXIDST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIDST
LISTEND
UK75551 COVER LETTER END
UK75581 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54759 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the *
* DB2-supplied stored procedures *
* SYSPROC.ADMIN_UTL_MONITOR and *
* SYSPROC.ADMIN_UTL_EXECUTE. *
****************************************************************
* PROBLEM DESCRIPTION: When DECIMAL=COMMA is enabled in *
* DSNHDECP, the DB2 scheduler *
* encountered SQLCODE -104 when it tried *
* to execute the task which was added *
* by the stored procedure *
* ADMIN_UTL_MONITOR to execute the *
* stored procedure ADMIN_UTL_EXECUTE. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
When ADMIN_UTL_MONITOR adds a task to the DB2 scheduler task
list to execute the stored procedure ADMIN_UTL_EXECUTE, it
specified a procedure input containing a comma character
followed immediately by a numeric character. When DECIMAL=COMMA
is enabled in DSNHDECP, the DB2 scheduler encountered
SQLCODE -104 as it attempts to execute this task.
ADMIN_UTL_MONITOR is modified to insert a whitespace character
between a comma character and a numeric character in the
procedure input of the task executing the stored procedure
ADMIN_UTL_EXECUTE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54759
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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.
***************************************************************
1 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
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
1 ***************************************************************
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
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 *#
1 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')
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@7MON PM54759
DSNX7MON PM54759
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54759 DSN@7MON DSNX7MON
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX7MON
1
MACROS
DSN@7MON
LISTEND
UK75581 COVER LETTER END
UK75583 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51182 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically where a remote application *
* from a down-level client system accesses *
* TIMESTAMP data from a DB2 10 for z/OS *
* server. *
****************************************************************
* PROBLEM DESCRIPTION: A remote application from a down-level *
* client receives an error (such as *
* SQLCODE -30000) when accessing *
* TIMESTAMP data at a DB2 10 for z/OS *
* server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application from a down-level client performs a SELECT
SQL statement against DB2 10 for z/OS server. The query data
returned by the DB2 server includes TIMESTAMP data for the
query. The DB2 server replies with descriptor and the query
data but the query descriptor contains an incorrect DRDA FD:OCA
length for the TIMESTAMP data type when a down-level client is
used.
In this reported case, a down-level DB2 for iSeries client was
in use. When the incorrect DRDA FD:OCA length for TIMESTAMP
data type was returned from DB2 for z/OS server, the iSeries
client issued SQLCODE -30000.
DB2 10 for z/OS server processing has been changed to return
the correct DRDA FD:OCA length for the TIMESTAMP data type for
down-level clients.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51182
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLFDO5 PM51182
DSNLFDO6 PM51182
DSNLFDO7 PM51182
DSNLFDO8 PM51182
DSNLFDO9 PM51182
DSNLFD10 PM51182
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PM51182 DSNLFDO5 DSNLFDO6 DSNLFDO7 DSNLFDO8 DSNLFDO9 DSNLFD10
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLFDO5
DSNLFDO6
DSNLFDO7
DSNLFDO8
DSNLFDO9
DSNLFD10
LISTEND
UK75583 COVER LETTER END
UK75587 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53477 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of Spatial support. *
****************************************************************
* PROBLEM DESCRIPTION: This apar provides a new function *
* DB2GSE.IDXKEY2D to retrieve the current *
* and surrounding grid cells from a *
* starting point. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar provides the new function DB2GSE.IDXKEY2D to retrieve
the current and surrounding grid cells from a starting point.
The following examples are provided to show how this function
can be used.
1-
The following statement invokes the function to retrieve the
grid cells of the POINTS object where 'SYSADM' is the schema
name and 'PTIDX2' is the index name of the Spatial index of the
POINTS column.
SELECT DB2GSE.IDXKEY2D(POINTS,'SYSADM','PTIDX2')
FROM SYSADM.POINTS;
2-
The following statement invokes the function to retrieve
8 surrounding grid cells.
WITH DTOTAL (GRIDNO1, GRIDNO2, GRIDNO3, GRIDNO4, GRIDNO5,
GRIDNO6, GRIDNO7, GRIDNO8) AS
(SELECT T.GRID1, T.GRID2, T.GRID3, T.GRID4,
T.GRID5, T.GRID6, T.GRID7, T.GRID8
FROM TABLE (DB2GSE.IDXKEY2D( 4294967297) ) T
)
SELECT GRIDNO1, GRIDNO2, GRIDNO3, GRIDNO4, GRIDNO5, GRIDNO6,
1 GRIDNO7, GRIDNO8 FROM DTOTAL;
3-
The following statement invokes the function to return
9 surrounding grids.
SELECT T.GRIDCENTRAL ,
T.GRID1, T.GRID2, T.GRID3, T.GRID4,
T.GRID5, T.GRID6, T.GRID7, T.GRID8
FROM TABLE
(DB2GSE.IDXKEY2D( DB2GSE.ST_POINT( 10,21, 1) , 1) ) T;
4-
The following statement invokes the function to retrieve
3 layers of the surrounding grids.
SELECT T.* FROM TABLE (DB2GSE.IDXKEY2D( 4294967297 ,3) ) T;
This apar provides a new function DB2GSE.IDXKEY2D to retrieve
the current and surrounding grid cells from a starting point.
After applying this apar, there is one new load module named
DSN5SBIG. The last two steps of DSN5SENB are used for creating,
granting, and binding for the new function.
Additional Keywords: SQLSPATIAL
COMPONENT: 5655-R1402-J2AG210
APARS FIXED: PM53477
SPECIAL CONDITIONS:
COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This APAR is a replacement for apar PM47333, ptf UK72946.
This apar provides the function to retrieve the current
and surrounding grid cells from a starting point.
For existing users, if they would like to use this function,
please submit the last two steps (CREATE01 and BINDSK19) of the
DSN5SENB job.
For new users, please follow the instructions contained in the
publication "IBM Spatial Support for DB2 z/OS" to enable
Spatial
functionality.
ACTION:
This apar provides the functions to retrieve the current
and surrounding grid cells from a starting point.
For the existing users, if they like to use this function
then submit 2 last steps: CREATE01 and BINDSK19 of
DSN5SENB job.
For the new users should follow the instructions contained
in the book
IBM Spatial Support for DB2 z/OS to enable Spatial
1 functionality.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@SK19 PM53477
DSN5SDEN PM53477
DSN5SENB PM53477
DSN5SK20 PM53477
DSN5SK21 PM53477
DSN5SK28 PM53477
DSN5SK29 PM53477
DSN5SK30 PM53477
J2AG210J PM53477
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53477 DSN@SK19 DSN5SDEN DSN5SENB DSN5SK20 DSN5SK21 DSN5SK28
DSN5SK29 DSN5SK30 J2AG210J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN5SDEN
DSN5SK20
DSN5SK21
DSN5SK28
DSN5SK29
DSN5SK30
MACROS
DSN@SK19
DSN5SENB
LISTEND
UK75587 COVER LETTER END
UK75634 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51809 -
****************************************************************
* USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS *
* USERS OF RESTORE SYSTEM UTILITY *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 IN DSNUVBRD NEAR OFFSET0BCA *
* DURING RESTORE SYSTEM UTILITY WHEN *
* FROMDUMP IS SPECIFIED BUT NO SYSTEM *
* LEVEL BACKUP ON TAPE IS FOUND *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran RESTORE SYSTEM utility with FROMDUMP specified,
and due to an anomaly in their procedures, the system level
backup identified as the one to be used was not available.
Under these circumstances the job should issue an appropriate
message and end with RC8, or continue to look for a backup
on DASD, but instead the job abended with ABEND0C4 in DSNUVBRD.
RESTORE SYSTEM code was changed to not abend when the target
1 system level backup is not available.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51809
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 PM51809
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51809 DSNUVBRD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUVBRD
LISTEND
UK75634 COVER LETTER END
UK75674 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53020 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: NPAGES in SYSIBM.SYSTABLESPACESTATS *
* could grow larger than NACTIVE on some *
* table space types. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
NPAGES is not being decremented when a page gets emptied for
table spaces that are neither defined as segmented nor as
strictly clustered (e.g. classic partitioned table spaces).
The real-time statistics logic was changed to decrement NPAGES
for all table space types when a page gets emptied.
This APAR does not modify any existing values. In order to
correct existing values run REORG on the affected table spaces.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53020
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDILS PM53020
DSNIDLEO PM53020
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53020 DSNIDILS DSNIDLEO
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDILS
DSNIDLEO
LISTEND
UK75674 COVER LETTER END
UK75687 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54608 -
****************************************************************
* USERS AFFECTED: All DB2 v10 users. *
****************************************************************
* PROBLEM DESCRIPTION: WLM invocation to boost the priority *
* of the lock holder upon resource *
* contention, may not work in DB2 *
* non-datasharing environment. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a non datasharing environment, DB2 did not pass the lock
holder information in a call to WLM using ?IWMCNTN macro. WLM
will not be able to perform a boost action as a result.
DB2 will now pass the lock holder details in IWMCNTN call to WLM
for lock resource contention in a non-datasharing environment.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54608
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTLTIM PM54608
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54608 DSNTLTIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTLTIM
LISTEND
UK75687 COVER LETTER END
UK75766 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52006 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS using the *
* REOPT(AUTO) bind option *
****************************************************************
1 * PROBLEM DESCRIPTION: ABEND0C4 RC38 in DSNSLD4.DSNSVSFB+065C *
* may occur when binding with the *
* REOPT(AUTO) bind option *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC38 in DSNSLD4.DSNSVSFB+065C may occur during bind
when using the REOPT(AUTO) bind option, or poor query
performance is possible when using REOPT(AUTO). An incorrect
variable was being used to reference storage in an array,
leaving gaps in the array. Upon freeing the storage,
the gap was detected, leading to the abend. If the abend
does not occur, it is still possible to have degraded query
performance as a result of the incorrect array.
Additional Keywords:
REOPT AUTO SQLPERFORMANCE
Code was changed to correct the variable being used to
reference the storage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52006
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCCF PM52006
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52006 DSNXOCCF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCCF
LISTEND
UK75766 COVER LETTER END
UK75779 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54941 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* RUNSTATS utility users using ZPARM *
* setting of STATCLUS=STANDARD *
****************************************************************
* PROBLEM DESCRIPTION: Incorrout CLUSTERRATIOF in MSGDSNU617I *
* and in SYSIBM.SYSINDEXES catalog table *
* when RUNSTATS utility is executed on *
* partitioned index with ZPARM STATCLUS *
* set to STANDARD *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When the user executed RUNSTATS INDEX PART on a partitioned
index with the ZPARM STATCLUS set to STANDARD, the utility
reported incorrect CLUSTERRATIOF value in MSGDSNU617I and
stored the incorrect value in SYSIBM.SYSINDEXES catalog table.
The incorrect value was computed due to an incorrect assembler
instruction. Since a 31 bit instruction was used in the
computation instead of the 64 bit instruction, the value
was truncated causing unexpected results.
Code was changed to generate the correct 64 bit assembler
instruction, so that the aggregated value is not truncated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54941
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSAIX PM54941
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54941 DSNUSAIX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSAIX
1
LISTEND
UK75779 COVER LETTER END
UK75785 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51566 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and *
* DB2 9 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: Thread hung in CSECT DSNTABA after an *
* MVS cancel. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A thread that is cancelled while executing a call to IRLM will
resynchronize with IRLM call during the thread termination
logic in CSECT DSNTABA. DSNTABA will determine if it should
wait for the request to return to DB2 or if the outstanding
request has been cancelled by IRLM. There is a window where
thread termination logic incorrectly determines that it
needs to wait for IRLM request to complete causing a hang in
CSECT DSNTABA.
Correct the code to close the cancel window.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51566
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTLLOC PM51566
DSNTLQRY PM51566
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51566 DSNTLLOC DSNTLQRY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTLLOC
DSNTLQRY
LISTEND
UK75785 COVER LETTER END
UK75836 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51453 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG TABLESPACE SHRLEVEL CHANGE utility *
1 * in data-sharing *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE *
* failed with ABEND04E RC00E4030E in *
* the LOG phase *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a REORG TABLESPACE SHRLEVEL CHANGE in a data-sharing
group, where concurrent DML applications were modifying the
table space being reorganized at the same time. The REORG
failed with ABEND04E RC00E4030E in DSNURLXL + x'144E'
during the LOG apply phase.
The reported problem is caused by a boundary condition in
which the REORG utility misapplied a log record twice.
Additional keywords:
OFFSET144E
Code has been modified to correct the aforementioned boundary
condition resulting in the REORG log apply issue.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51453
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 PM51453
DSNURLOG PM51453
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51453 DSNUGLGR DSNURLOG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGLGR
DSNURLOG
LISTEND
UK75836 COVER LETTER END
UK75883 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56005 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: The start LRSN of a log data set may *
* be slightly lower than the end LRSN *
* value for the previous log data set *
* when the active log data sets are *
* truncated and switched during DB2 *
* restart. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
The active logs of a running DB2 member were copied for
remote site recovery. One copy of the active log pair
contained more log data than the other copy, so the active
logs were truncated and switched during log initialization
with different end RBA and LRSN values. If the last CI
(control interval) of the 'longer' active log ends with
the first or middle segment of a spanned log record, the
start LRSN of the next active log pair could be slightly
lower than the end LRSN of the truncated log data set.
The log truncation and switch code has been changed so that
the start LRSN of the log pair that is switched to will be set
correctly in this scenario.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56005
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJW009 PM56005
DSNJW307 PM56005
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56005 DSNJW009 DSNJW307
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW009
DSNJW307
LISTEND
UK75883 COVER LETTER END
UK75906 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53285 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS parallelism *
* users who use a user-defined function *
* (UDF). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIPSFI *
* ERQUAL5007 SQLCODE904 RC00E30100 *
* when a query has a UDF and is run *
* in parallelism. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This problem could happen under the following conditions:
1 1. The query has a GROUP BY sort and the sort is done in
parallel (SORTC_GROUPBY=Y and SORTC_PGROUP_ID > 0
in PLAN_TABLE), and
2. There is a UDF in the select list or GROUP BY list, and
3. The UDF is defined as DISALLOW PARALLEL or
UNDETERMINISTIC or CONTAIN SQL or READS SQL
Additional Keywords:
SQLCPUP SQLPARALLELISM SET CURRENT DEGREE ANY
DB2PARALL/K SQLUDF SQLGROUPBY
Parallel sort is disabled for the situations described above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53285
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PM53285 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM53285 fixes an execution time abend when a query contains a
user-defined function and is run in parallelism.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLL PM53285
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53285 DSNXOLL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLL
LISTEND
UK75906 COVER LETTER END
UK75933 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54840 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: The user ended a DB2 application with *
* an MVS STOP command and received an *
* ABEND0C4 in DSN3RRSX. *
1 * ABEND0C4 RSN11 *
* ABEND0C4-11 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 module DSN3RRSX received an ABEND0C4 while processing a
Context_Switch for a private context owned by a non-IBM resource
manager. A customer application obtained the private context
from the resource manager and then connected to DB2. The
Context_Switch with the CTX_SWITCH_DISASSOC_END_NORM flag was
driven in the resource manager address space, however module
DSN3RRSX was trying to access a control block in the application
address space.
Module DSN3RRSX will be updated to avoid the ABEND0C4 while
processing a Context_Switch when the private context is not
owned by the address space that connected to DB2.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PM54840
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3RRSX PM54840
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54840 DSN3RRSX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3RRSX
LISTEND
UK75933 COVER LETTER END
UK75943 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51826 -
****************************************************************
* USERS AFFECTED: DB2 for z/os V10 with Hash Table Space *
****************************************************************
* PROBLEM DESCRIPTION: The Hash Chain on the hash home pgae *
* is broken after SQL INSERT, *
* therefore ABEND04E RC00C90105 *
* DSNISGRT ERQUAL0C44 is triggered *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a record can not be inserted into the hash home page, this
record must be inserted into the hash overflow area.
1 During space search of the hash overflow pages,
another hash home page was found and processed as a
hash overflow page incorrectly, which result in a
broken hash chain on the page. Therefore, the sanity check
of the page was triggered and the transaction abended
with 04E-00C90105 & erqual code 0C44.
DB2 code was modified to ensure only non-hash home page is
used for hash over flow area.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51826
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISGNS PM51826
DSNISGSU PM51826
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51826 DSNISGNS DSNISGSU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGNS
DSNISGSU
LISTEND
UK75943 COVER LETTER END
UK75946 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52157 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC11 at DSNUGSTA +x'1A00' *
* during TERM phase of REORG *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
While processing through the deallocation code in the TERM phase
of REORG, a control block was referenced after the pointer to it
had been cleared. This resulted in referencing low core storage
and led to the ABENDS0C4 RC11 at DSNUGSTA+x'1A00'.
Additional keyword: OFFSET1A00
Code has been changed to verify a valid pointer to the control
block in question before referencing it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52157
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
DSNUGSTA PM52157
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52157 DSNUGSTA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGSTA
LISTEND
UK75946 COVER LETTER END
UK75949 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50451 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users who run query with groupby clause *
* and parallelism enabled. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E72018 at CSECT DSNXSBUC *
* offset 3E7A may happen when running *
* query with groupby clause and *
* parallelism enabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND at location DSNXGRDS.DSNXSBUC may occur when running
query with groupby clause and parallelism enabled.
The following query is an example of this case.
SET CURRENT DEGREE='ANY';
SELECT V1.C1
FROM (SELECT 'A' FROM T1
UNION ALL
SELECT DISTINCT TX.C1
FROM (SELECT C1 FROM T2
UNION ALL
SELECT C1 FROM T3) TX(C1)
) AS V1(C1)
WHERE V1.C1 LIKE 'A%'
UNION ALL
SELECT V1.C1
FROM (SELECT 'A' FROM T1
UNION ALL
SELECT DISTINCT TX.C1
FROM (SELECT C1 FROM T2
UNION ALL
SELECT C1 FROM T3) TX(C1)
) AS V1(C1)
WHERE V1.C1 > 'A'
1 GROUP BY V1.C1
;
An ABEND04E may occur with the SELECT statement.
The code in DB2 is modified to correct the failing condition.
Additional keyword: SQLPARALLELISM SQLGROUPBY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50451
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM50451:
See PM50451 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50451 corrects a problem of ABEND04E RC00E72018 at CSECT
DSNXSBUC offset 3E7A may happen when running query with
groupby clause and parallelism enabled.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM45209:
See PM45209 APAR/PTF text for additional information about
why a REBIND is necessary.
PM45209 corrects a problem of incorrect output on query
containing aggregate function distinct w/o group by and running
with dpsi index and parallelism.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM43740:
See PM43740 APAR/PTF text for additional information about
why a REBIND is necessary.
PM43740 corrects a problem of ABEND04E RC00E70005 in DSNXGDT2
M201 may occur when one of the following condition met:
1. a UNION/INTERSECT/EXCEPT query with COUNT COLUMN function,
MIN/MAX aggregate function in the selection list and the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
2. Or a UNION ALL/INTERSECT ALL/EXCEPT ALL query with ORDER BY
clause and COUNT COLUMN function, MIN/MAX aggregate function
in the selection list. Also,the input of the COUNT COLUMN
1 function, MIN/MAX aggregate function has FIELD PROC defined
on it running in parallel.
3. Or a query with ORDER BY clause and a COUNT COLUMN function,
MIN/MAX aggregate function in the selection list. Also, the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
4. Or a SELECT DISTINCT statement with COUNT COLUMN function,
MIN/MAX aggregate function in the selection list. Also, the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM39444:
See PM39444 APAR/PTF text for additional information about
why a REBIND is necessary.
PM39444 corrects a problem of ABEND04E RC00E72018 at DSNXSTSE
offset 0A9C may occur when a query contains a column function
in the selection list and its result data type is a LOB running
in parallel.
To make this fix effective for a static application, it must be
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 PM36118:
See PM36118 APAR/PTF text for additional information about
why a REBIND is necessary.
PM36118 corrects a problem of ABEND0C4 RC00000011 DSNXRSGB
offset 5E5C may occur when view has duplicate group by
columns
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGSGP PM50451
DSNXOCON PM50451
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50451 DSNXGSGP DSNXOCON
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGSGP
1 DSNXOCON
LISTEND
UK75949 COVER LETTER END
UK75956 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51512 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* SQL DELETE with referential integrity (RI) *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIRELS ERQUAL5012 *
* may occur during the process of DELETE *
* when the following conditions exist: *
* *
* 1. the table has one or more child *
* tables *
* 2. the parent key index is defined as *
* NOT PADDED *
* 3. the parent key index is in a rebuild *
* pending status *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An SQL DELETE against a parent table that had a NOT PADDED
primary key index in a rebuild pending status (e.g. RBDP)
abended with DSNIRELS:5012 while performing a table space scan
for dependent rows.
The reason for the abend was that during the scan for dependent
rows, the parent's primary key index still had to be accessed
for key comparison, however the code did not take into account
the possibility that the primary key index might be physically
closed due to it being in a rebuild pending status.
DB2 code has been modified to avoid the ABEND04E and issue
SQLCODE904 -904 with RC00C900AE on the primary key index when
the index is unavailable during the scan for dependent rows.
Additional keywords: SQLDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51512
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRELS PM51512
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51512 DSNIRELS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNIRELS
LISTEND
UK75956 COVER LETTER END
UK75960 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49154 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of queries that *
* employ sparse index access (in the plan *
* table, column PRIMARY_ACCESSTYPE is 'T') *
****************************************************************
* PROBLEM DESCRIPTION: In DB2 10 for z/OS, incorrout or *
* performance degradation is possible in *
* queries that use sparse index (in plan *
* table, PRIMARY_ACCESSTYPE is 'T') *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a sorted workfile scan, the new predicate evaluation
mechanism took over even though it was not set up for such a
scan. This resulted in millions of extra getpages for sparse
index access.
Code has been changed so that the new predicate evaluation
does not kick in for sorted workfile scan.
Additional keywords: SQLINCORR SQLINCORROUT DB2INCORR/K
PERFM SQLPERFORMANCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49154
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIWNRF PM49154
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49154 DSNIWNRF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWNRF
LISTEND
UK75960 COVER LETTER END
UK75989 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56361 -
****************************************************************
* USERS AFFECTED: All DB2 V10 HDBAA10 users. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Allied address spaces which are reused *
* repeatedly, such as WLM Stored *
* Procedures, WAS, or JES Initiators may *
* experience an out-of-storage abend such *
* as RC00E20003, RC00E20015, or other *
* RC00E2nnnn storage bend. Analysis *
* shows that there are many pages which *
* contain an 8 byte allocation, usually *
* at the very end of the page. Page may *
* contain residual field names such as *
* FTBL, ASST, and PHBG. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The control block getmained at ALLIED start-up for the PHB to
house the pool of PHBs, was changed from being double-word
bounded to quad-word bounding on the getmain. The ALLIED
termination failed to round up the actual length of the control
block, causing 8 bytes to be orphaned each time the address
space was reused. If this ASID remains active and reused for an
extended period of time, this causes severe fragmentation of the
private storage in the address space.
The FREEMAIN during ALLIED termination has been changed so that
the correct size of the control block is used.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56361
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNSFPL PM56361
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56361 DSNSFPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNSFPL
LISTEND
UK75989 COVER LETTER END
UK76053 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47356 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG TABLESPACE. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNILPG:5007 during *
* a REORG TABLESPACE SORTDATA NO on a *
* partitioned table space in reorg *
1 * pending (REORP). *
* *
* ABENDS0C4 DSNURFIT OFFSET6084 during *
* REORG TABLESPACE. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
1. A REORG TABLESPACE SORTDATA NO on a partitioned table space
abended with an ABEND04E RC00C90101 DSNILPG ERQUAL5007 when an
invalid partition number was detected. Prior to the REORG,
the partition's limit keys had been altered, and the table
space was in REORP. The alter of the limit keys caused REORG
to unload and reload the data rows from the partitions out of
partition order, causing the abend.
REORG does not expect records to be out of partitioning order
and therefore needs to restrict the use of SORTDATA NO when the
table space is in reorg pending. Message DSNU070I will now be
be issued for this scenario. This does not apply to Partition-
By-Growth (PBG) table spaces.
2. ABEND0C4 DSNURFIT +x'6084' during REORG TABLESPACE occurred
when an invalid index was used to reference into an element of
an array structure.
MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH
'TABLE SPACE IN REORG PENDING' will now be issued when REORG
TABLESPACE SORTDATA NO is run against a non-PBG partitioned
table space in reorg pending, and the utility will end with RC8.
REORG code was also modified to use the correct array index.
This APAR/PTF modifies the DB2 Utility Guide and Reference
and the Messages manual. The change will be documented in
the DB2 Utility Guide and Reference and Messages, and in the
Information Management Software for z/OS Solutions Information
Center.
The change is as follows.
In the Utility Guide and Reference, under REORG TABLESPACE,
Option descriptions, SORTDATA option:
SORTDATA
NO
Specifies that the data is to be unloaded in the order
of the clustering index. SORTDATA NO cannot be specified
| with SHRLEVEL CHANGE or if the table space is in REORG-
| PENDING. Specify SORTDATA NO if one of the following
conditions is true:
* The data is in or near perfect clustering order, the
| table space is not in REORP, and the REORG utility is
used to reclaim space from dropped tables.
* The data is very large, an insufficient amount of disk
| space is available for sorting, and the table space is
not in REORP.
1
In the Messages manual, under DSNU messages:
DSNU070I csect-name KEYWORD OR OPERAND x
INVALID WITH y
| Explanation: The use of a keyword or operand is
| inconsistent with another keyword, operand or condition.
| x and y The keywords, operands or conditions that
cannot be used together.
System action: The control statement in error is
rejected and processing is halted.
User response: Correct the control statement in error
and resubmit the job.
Problem determination: The REORG TABLESPACE
| utility issues this message when the keywords, operands or
| conditions are not allowed to be used in combination.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47356
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
See PM47356 APAR/PTF text for additional information.
This APAR/PTF modifies the DB2 Utility Guide and Reference
and the Messages manual. The change will be documented in
the DB2 Utility Guide and Reference and Messages, and in the
Information Management Software for z/OS Solutions Information
Center.
The change is as follows.
In the Utility Guide and Reference, under REORG TABLESPACE,
Option descriptions, SORTDATA option:
SORTDATA
NO
Specifies that the data is to be unloaded in the order
of the clustering index. SORTDATA NO cannot be specified
| with SHRLEVEL CHANGE or if the table space is in REORG-
| PENDING. Specify SORTDATA NO if one of the following
conditions is true:
* The data is in or near perfect clustering order, the
| table space is not in REORP, and the REORG utility is
used to reclaim space from dropped tables.
* The data is very large, an insufficient amount of disk
| space is available for sorting, and the table space is
not in REORP.
In the Messages manual, under DSNU messages:
1
DSNU070I csect-name KEYWORD OR OPERAND x
INVALID WITH y
Explanation: The use of a keyword or operand is
| inconsistent with another keyword, operand or condition.
| x and y The keywords, operands or conditions that
cannot be used together.
System action: The control statement in error is
rejected and processing is halted.
User response: Correct the control statement in error
and resubmit the job.
| Problem determination: The REORG TABLESPACE
| utility issues this message when the keywords, operands or
| conditions are not allowed to be used in combination.
ACTION:
The PTF for APAR PM47356 has modified the REORG TABLESPACE
utility to issue the following message and end with RC8 when
REORG TABLESPACE SORTDATA NO is run against a non-Partition-
By-Growth (non-PBG) partitioned table space in REORG-PENDING
(REORP). A REORG TABLESPACE SORTDATA YES is required to remove
the REORP state.
MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH
'TABLE SPACE IN REORG PENDING'
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGRST PM47356
DSNURFIT PM47356
DSNURSWD PM47356
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47356 DSNUGRST DSNURFIT DSNURSWD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGRST
DSNURFIT
DSNURSWD
LISTEND
UK76053 COVER LETTER END
UK76071 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57298 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNVEOT1 during service *
1 * task EOT (end of task) processing *
* due to incorrect addressability to *
* the LCOM block. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A DB2 service task TCB abended in the DBM1 address space.
DB2 was processing the EOT notification for the service
task TCB and attempted to RESUME the synchronous requestor
of the service task. The requestor had been canceled,
so the RESUME cancel exit in DSNVEOT1 was driven and
received an ABEND0C4 as control block addressability is
not correct.
LCOM addressability in DSNVEOT1 has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57298
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVEOT1 PM57298
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57298 DSNVEOT1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVEOT1
LISTEND
UK76071 COVER LETTER END
UK76083 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54056 -
****************************************************************
* USERS AFFECTED: All DB2 9, DB2 10 for z/OS users of INDEX ON *
* EXPRESSION. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE -270 or ABEND0C4 *
* RC00000011 at DSNXORFN + 1496 *
* could occur when a user defined *
* function is referenced in a CREATE *
* INDEX statement, SQLCODE -356 shall *
* be issued in this case. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Unexpected SQLCODE -270 or ABEND0C4 RC00000011 at
DSNXORFN + 1496 could occur when a user defined
function is referenced in a CREATE INDEX statement,
SQLCODE -356 shall be issued in this case.
1 The following example could recreate the problem.
CREATE TABLE T1(C1 INTEGER, C2 VARCHAR(5));
CREATE FUNCTION MYUDF1 (CH1 VARCHAR(5))
RETURNS VARCHAR(8)
NOT VARIANT
NO EXTERNAL ACTION
CONTAINS SQL
RETURN CH1||'ABC';
CREATE UNIQUE INDEX IX1 ON T1(MYUDF1(C2));
DB2 is updated to issue sqlcode -356 correctly when USER
DEFINED FUNCTION is referenced in CREATE INDEX statement.
Additional Keywords: SQLINDEXONEXP SQLCODE356 SQLCODE270
SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54056
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEBIS PM54056
DSNXOADT PM54056
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54056 DSNXEBIS DSNXOADT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBIS
DSNXOADT
LISTEND
UK76083 COVER LETTER END
UK76086 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55824 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically where DB2 for z/OS is a member *
* of a data sharing group that is accessed as *
* a server via TCP/IP. *
****************************************************************
* PROBLEM DESCRIPTION: When a DB2 for z/OS system is a member *
* of a data sharing group, a -STOP DDF *
* MODE(QUIESCE) command may incorrectly *
* cause DDF to stop completely even when *
* active DBATs are present. The following *
* messages may occur: *
* . EZD1298I DYNAMIC VIPA dvipa DELETED *
* FROM tcpstackname *
* . EZD1207I DYNAMIC VIPA dvipa WAS *
* DELETED USING CLOSE API BY jobname *
* ON tcpstackname *
1 * . DSNL511I DSNLIENO TCP/IP *
* CONVERSATION FAILED TO LOCATION *
* location-name IPADDR=ip-address *
* PORT=port SOCKET=RECV *
* RETURN CODE=3448 *
* REASON CODE=00000000 *
* . DSNL006I -DDF STOP COMPLETE *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a -STOP DDF MODE(QUIESCE) command is issued at a DB2
system, which is also a member of a data sharing group, stop
DDF processing may complete normally even when active DBATs are
present. This incorrect behavior may occur when there are
connections that are accessing the DB2 member via the
member specific DVIPA (Dynamic Virtual IP Address), which is
specified using the BIND keyword on the PORT statement in the
TCP/IP profile (TCPIP.PROFILE). During stop DDF mode quiesce
processing, DB2/DDF incorrectly closes the TCP/IP socket that
was used to bind the member specific DVIPA and this closing of
the TCP/IP socket implicitly drives TCP/IP to delete any
outstanding DVIPA connections associated with this socket as
well. Hence, when these DVIPA sockets are closed the related
active DBAT is terminated and when the last active DBAT is
terminated, stop DDF processing will complete normally.
Note: IBM Data Server Driver for JDBC and SQLJ clients may
unexpectedly receive ERROR CODE=-30108 when this problem
occurs.
DB2 for z/OS Stop DDF Mode Quiesce processing has been changed
to defer the closing of the TCP/IP socket that is used to bind
the member specific DVIPA until all active DBATs have
terminated normally.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55824
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLITRM PM55824
DSNLITR0 PM55824
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55824 DSNLITRM DSNLITR0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLITRM
DSNLITR0
LISTEND
UK76086 COVER LETTER END
1UK76093 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55811 -
****************************************************************
* USERS AFFECTED: All DB2 9 or DB2 10 for z/OS users who *
* deploy query parallelism *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXECT :M600 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While DB2 was executing a query in parallel mode, the following
abend occurred:
ABEND04E RC00E70005 DSNXGRDS.DSNXECT :M600
DB2 has been modified such that the abend will no longer occur.
.
Additional search keywords: SQLPARALLELISM DB2PARALL/K AB04E
M600 OFFSETM600
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55811
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXECT PM55811
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55811 DSNXECT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXECT
LISTEND
UK76093 COVER LETTER END
UK76109 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53985 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of a native SQL *
* procedure containing an SQL statement that *
* could run into SQLCODE -408. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS.DSNXGMVE:M100 could happen *
* when a native SQL procedure is created *
* with the option WITH EXPLAIN and an SQL *
* statement that could run into SQLCODE *
* -408. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 ABEND04E RC00E70005 at the location DSNXGRDS.DSNXGMVE:M100 could
happen when a native SQL procedure is created with the option
WITH EXPLAIN and an SQL statement that could run into SQLCODE
-408.
An example is shown below:
Step 1. Create EXPLAIN tables in V9 format.
Step 2. Run the following CREATE PROCEDURE statement.
CREATE PROCEDURE MYSP1 ()
WITH EXPLAIN
BEGIN
DECLARE P_INT INTEGER;
DECLARE P_SCHEMA CHAR(8);
SELECT CREATEDTS INTO P_INT
FROM SYSIBM.SYSTABLES
WHERE CREATOR = P_SCHEMA;
END#
DB2 did not correctly process the aforementioned CREATE
PROCEDURE statement, which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
CREATE PROCEDURE statement, so there will be no ABEND.
Additional keywords: SQLCODE408 SQLNATIVESQLPL SQLSP
SQLSTOREDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53985
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOOP PM53985
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53985 DSNXOOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOOP
LISTEND
UK76109 COVER LETTER END
UK76110 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55210 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of the REORG TABLESPACE utility. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Multiple DSNU393I or DSNU394I messages *
* were issued for one index during a *
* REORG TABLESPACE SHRLEVEL CHANGE *
* utility with parallel index build when *
* the mapping index had the same object *
* id as one of the tables being reorged. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A REORG SHRLEVEL CHANGE was run on a table with parallel index
build, and the mapping index had the same object id as one
of the table indexes. Multiple MSGDSNU393I or MSGDSNU394I
messages were issued for the mapping index and the table index.
REORG sorts the index keys by the object identifer (OBID) and
therefore, problems can occur when table index has the same OBID
as the mapping table index.
The REORG utility code has been modified to add additional
fields to use to sort the index keys.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55210
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURPSS PM55210
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55210 DSNURPSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURPSS
LISTEND
UK76110 COVER LETTER END
UK76112 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51825 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of COPY utility *
* with the FLASHCOPY option. *
****************************************************************
* PROBLEM DESCRIPTION: COPY with FLASHCOPY option does not *
* properly detect a duplicate output *
* data set and creates a new one *
* with the same name instead. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a COPY utility with FLASHCOPY option on a tablespace
1 using a TEMPLATE for FCCOPYDDN, then ran the COPY utility again
using the same TEMPLATE for FCCOPYDDN. The second COPY utility
deleted the existing data sets generated from TEMPLATE and
created new ones successfully instead of reporting an error.
COPY utility is missing check for duplicate data sets for
COPY with FLASHCOPY. This problem can also occur for FLASHCOPY
when the output data set is not a TEMPLATE.
COPY utility is modified to issue
MSGDSNU407I - 'DATA SET ALREADY USED FOR PREVIOUS IMAGE COPY'
and
MSGDSNU408I - 'dsn EXISTS WITH....'
and return RC8 when duplicate data sets are found for FLASHCOPY.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51825
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBCKD PM51825
DSNUGFCB PM51825
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51825 DSNUBCKD DSNUGFCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBCKD
DSNUGFCB
LISTEND
UK76112 COVER LETTER END
UK76113 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55036 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of CHECK DATA utility. *
****************************************************************
* PROBLEM DESCRIPTION: CHECK DATA SHRLEVEL CHANGE reset CHKP *
* status, but it should not. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a CHECK DATA SHRLEVEL CHANGE utility against a table
space which was in CHECK PENDING(CHKP) state. CHECK DATA utility
reset CHKP status for the table space, but since it was SHRLEVEL
CHANGE and operates only on shadow data sets it should not have
reset this state.
CHECK DATA is modified not to reset CHKP status for SHRLEVEL
CHANGE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55036
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
DSNUKNFK PM55036
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55036 DSNUKNFK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUKNFK
LISTEND
UK76113 COVER LETTER END
UK76147 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52870 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS (V10 CM and higher) *
* users of deletes or updates on universal *
* table space with page-level locking *
* who use cursors defined as WITH ROWSET *
* POSITIONING when deleting/updating the *
* table *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNICUMW ERQUAL1001 *
* during SQL DELETE WHERE CURRENT OF from *
* a universal table space with page-level *
* locking, when the cursor is defined as *
* WITH ROWSET POSITIONING *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The aforementioned abend happened during DELETE WHERE CURRENT OF
(could also happen in UPDATE WHERE CURRENT OF), due to an
incorrectly invoked CHANGE call to IRLM.
In the call, the CUB owning work unit was used when the IRLM
structures expected (correctly) the CT's owning work unit.
The calling module did not take into account that in multi-row
fetch applications DB2 may have changed OWU ownership of
existing locks in that CUB to the CT, in preparation for the
new row set coming in.
Here is a sample sequence that can expose this issue:
DECLARE CUR1 CURSOR WITH HOLD WITH ROWSET POSITIONING FOR
SELECT EMPID
FROM EMPTBL FOR UPDATE OF EMPID
1
OPEN CUR1
FETCH NEXT ROWSET FROM CUR1 FOR 2 ROWS INTO :EMPID
DELETE FROM EMPTBL WHERE CURRENT OF CUR1
FETCH NEXT ROWSET FROM CUR1 FOR 2 ROWS INTO :EMPID
DELETE FROM EMPTBL WHERE CURRENT OF CUR1
Code has been modified for DB2 to correctly invoke IRLM.
Additional keywords: SQLROWSET SQLDELETE SQLUPDATE SQLPBG PBG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52870
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICUMW PM52870
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52870 DSNICUMW
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICUMW
LISTEND
UK76147 COVER LETTER END
UK76148 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55782 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of *
* SQLPL char/varchar variable *
* compare with timestamp data type. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at DSNXGDT2:M206 *
* may occur for an SQL statement that *
* contains a predicate involving an SQL *
* char/varchar variable and a timestamp *
* data type. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 at DSNXGDT2:M206 may occur for an SQL
statement that contains a predicate involving an SQL
char/varchar variable and a timestamp data type.
1
For Example,
CREATE TABLE T1 (C1 TIMESTAMP, C2 TIMESTAMP);
CREATE PROCEDURE TEST
DECLARE INSRT_TSTMP CHAR(26) DEFAULT '';
DECLARE TEST_CURSOR CURSOR FOR
SELECT C1
FROM T1 WHERE C1 = C2 AND C1 = INSRT_TSTMP;
OPEN TEST_CURSOR;
The statement above causes an abend because the transitive
closure predicate between column C2 and the SQL variable
INSRT_TSTMP is not generated correctly.
DB2 was fixed to generate the transitive closure predicate
between an SQL char/varchar variable and a timestamp
data type correctly.
Additional Key Words: SQLPL SQLNATIVESQLPL SQLTIMESTAMP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55782
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFB PM55782
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55782 DSNXOBFB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBFB
LISTEND
UK76148 COVER LETTER END
UK76153 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49543 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: Performance degradation and virtual *
* storage shortage when processing *
* a large number of XML documents *
* *
* SQLCODE904 was issued with RC00D50001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes the non-linear performance degradation and
poor virtual storage usage as the number of XML documents
processed grows.
1
For example, in the following query with XMLAGG:
SELECT XMLAGG( XMLQUERY('//Id' PASSING
XMLELEMENT(NAME "A", XMLCOL ))) FROM T1;
In the above example, when the XMLAGG function is used in a SQL
statement that aggregates many XML documents in memory, the
time for running the query and the XML virtual storage usage
both grow non-linearly.
DB2 is updated to improve XML performance and virtual storage
usage.
Additional Keywords: SQLXML SQLSTORAGE SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49543
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 PM49543
DSNNOCCN PM49543
DSNNOGET PM49543
DSNNOINS PM49543
DSNNORSQ PM49543
DSNNOSCO PM49543
DSNNOXMV PM49543
DSNNOXVC PM49543
DSNNQFLR PM49543
DSNNQIV PM49543
DSNNQMD PM49543
DSNNQOB PM49543
DSNNQOPM PM49543
DSNNQXCA PM49543
DSNXDMPS PM49543
DSNXMLSM PM49543
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49543 DSNNOBSC DSNNOCCN DSNNOGET DSNNOINS DSNNORSQ DSNNOSCO
DSNNOXMV DSNNOXVC DSNNQFLR DSNNQIV DSNNQMD DSNNQOB
DSNNQOPM DSNNQXCA DSNXDMPS DSNXMLSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOBSC
DSNNOCCN
DSNNOGET
DSNNOINS
DSNNORSQ
DSNNOSCO
DSNNOXMV
DSNNOXVC
DSNNQFLR
DSNNQIV
1 DSNNQMD
DSNNQOB
DSNNQOPM
DSNNQXCA
DSNXDMPS
DSNXMLSM
LISTEND
UK76153 COVER LETTER END
UK76155 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56182 -
****************************************************************
* USERS AFFECTED: All DB2 users of IRLM230 (HIR2230) in *
* DATASHARING SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 abended RC00D900F7. *
* IRLM abended S0C4 in DXRRL7C1 or *
* DXRRL760 or DXRRL120 with MSGDXR122E. *
* ABENDU2027 may also be seen in DXRRL7C1 *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
A CHANGE STATE down request may result in the RHBMODST
being set to FF during the XES NOTIFY exit processing
for the requester. This can result in the ABEND0C4 if
the cached state matrix is used to look up the resultant
state, or if the error is caught by DXRRL7C1, the
the ABENDU2027 will occur. DB2 could be in CM, ENFM
and NFM mode. This cached state matrix check only
occurs while DB2 is using Locking protocol 1.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
This apar fixes the NOTIFY process to prevent the incorrect
RHBMODST from being set.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM56182
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2T1 PM56182
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56182 DXRRL2T1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2T1
1 LISTEND
UK76155 COVER LETTER END
UK76162 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49443 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of LIKE predicates that contain the UPPER *
* scalar function. *
****************************************************************
* PROBLEM DESCRIPTION: This apar addresses the problem of *
* LIKE predicates containing the UPPER *
* scalar function that are non-indexable. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a query contains a LIKE predicate with the UPPER scalar
function, the predicate cannot become indexable. With this
apar, this predicate can now become indexable.
The following example shows an EXPLAIN for a query containing a
LIKE predicate with the UPPER scalar function.
EXPLAIN ALL SET QUERYNO = 1 FOR
SELECT FIRSTNME FROM EMP
WHERE LASTNAME LIKE UPPER(CAST(? AS VARCHAR(200)));
On running the above EXPLAIN statement, the result would show
the KEYFIELD column of the DSN_PREDICAT_TABLE to contain a 'Y'
if there is a suitable INDEX available for the LASTNAME column.
Please note that the LIKE predicate must be a boolean term
predicate to become indexable. Also, the argument to the UPPER
scalar function must be simple, i.e. a literal, a host variable,
or a parameter marker with an allowable string data type.
DB2 has been modified to allow LIKE predicates that contain the
UPPER scalar function to become indexable.
Please note that this apar is the forward fit of apar PM45033
for DB2 for z/OS V8.
Additional Keywords: SQLINDEX SQLLIKE SQLUPPER
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49443
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM49443:
See PM49443 APAR/PTF text for additional information about
why a REBIND is necessary.
1
PM49443 allows LIKE predicates with the UPPER scalar function
to become indexable.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM48939:
See PM48939 APAR/PTF text for additional information about
why a REBIND is necessary.
PM48939 corrects a problem of incorrect output may occur when a
pair-wise join query uses a multi-column index between dimension
table and Fact table and there is a Fact table local predicate
covered by the same multi-column index.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRM1 PM49443
DSNXGSFN PM49443
DSNXOAF PM49443
DSNXOBM PM49443
DSNXOMEX PM49443
DSNXORHV PM49443
DSNXOW2D PM49443
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49443 DSNXGRM1 DSNXGSFN DSNXOAF DSNXOBM DSNXOMEX DSNXORHV
DSNXOW2D
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGRM1
DSNXGSFN
DSNXOAF
DSNXOBM
DSNXOMEX
DSNXORHV
DSNXOW2D
LISTEND
UK76162 COVER LETTER END
UK76164 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52445 -
****************************************************************
1 * USERS AFFECTED: All DB2 parallelism users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC3B in DSNXECL +11DE can *
* occur when running in parallelism. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC3B in DSNXECL +11DE can occur when running in
parallelism. During DB2 clean up process, some temporary
files have been cleaned up, but their file tokens are not
reset, so DB2 tries to clean up these files that have already
been freed. This causes the abend.
This error is not query specific.
DB2 has been fixed to clear the temporary file's token
once they are freed, so that they will not be freed again
later, which may cause unexpected abends.
Additional Keywords: SQLPARALLEL DB2PARALL/K
PARALLELISM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52445
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXPDST PM52445
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52445 DSNXPDST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXPDST
LISTEND
UK76164 COVER LETTER END
UK76178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54138 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD SHRLEVEL CHANGE with *
* partition parallelism into a table which has *
* a trigger invoking a stored procedure. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 at DSNXA02 + x'847A' occurs *
* when running LOAD with option SHRLEVEL *
* CHANGE into a TABLE with a TRIGGER that *
* calls a STORED PROCEDURE *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
1 ABENDS0C4 at DSNXA02 OFFSET847A happens when LOAD SHRLEVEL
CHANGE with partition parallelism is executed for a table with
an AFTER INSERT TRIGGER which calls a STORED PROCEDURE and the
stored procedure creator does not have execute privilege.
In this case, DB2 needs to check if the application PLAN owner
that calls the STORED PROCEDURE is authorized to execute the
STORED PROCEDURE. But the PLAN owner of the utility parallel
subtask is not set up correctly, which causes the abend.
DB2 utility code has been modified to set up the utility PLAN
owner for LOAD SHRLEVEL CHANGE parallel subtask properly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54138
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGUCA PM54138
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54138 DSNUGUCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGUCA
LISTEND
UK76178 COVER LETTER END
UK76206 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52079 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those with remote applications *
* that utilize progressive streaming function *
* and connect to a DB2 for z/OS server. *
****************************************************************
* PROBLEM DESCRIPTION: A remote application, such as a CLI *
* application, can receive SQLCODE *
* -30071 with SQLERRP DSNLXGCS when *
* accessing LOB or XML data on a DB2 *
* for z/OS server via a progressive *
* reference. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application is connected to a DB2 for z/OS server
and performs a SELECT statement with the progressive streaming
function enabled to request progressive streaming behavior.
This function optimizes the return of LOB and XML data
depending on the actual length of the data. The LOB and XML
data can be returned in its entirety or as a progressive
1 reference when the size of the LOB and XML data is large (for
example, as defined by the CLI LOBCacheSize keyword). Then the
remote client system can manage to retrieve the LOB and XML
data by using the progressive reference.
When the remote application tries to access such large LOB
and XML data via the progressive reference, the DB2 server
incorrectly rejects the request with SQLCODE -30073 indicating
that the received progressive reference is invalid.
This occurs because internal processing at the DB2 for z/OS
server does not correctly maintain the progressive reference
for the subsequent retrieval of the LOB and XML data when there
is more than one query data block returned to the client
in response to a single request.
DB2 for z/OS server processing has been changed to maintain the
progressive reference correctly for large LOB and XML data for
the subsequent retrieval of such data.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52079
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXCQ6 PM52079
DSNLXCQ7 PM52079
DSNLXXSS PM52079
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52079 DSNLXCQ6 DSNLXCQ7 DSNLXXSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXCQ6
DSNLXCQ7
DSNLXXSS
LISTEND
UK76206 COVER LETTER END
UK76209 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54705 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of Access Control *
* Authorization exit (DSNX@XAC) *
* *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect reason code issued in *
* ABEND04E RC00E70009 at DSNXACAE:P300 *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 When Access Control Authorization Exit is active, an abend
ABEND04E RC00E70009 at DSNXACAE:P300
occurred due to an error during authorization ID conversion.
The reason code '00E70009'X issued is misleading for an abend
due to an internal conversion error.
This reason code can also be issued for similar abends due to
conversion error in DSNXACAE.
DB2 code has been changed to issue reason code '00E70005'X
for abends due to conversion error in DSNXACAE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54705
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXACAE PM54705
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54705 DSNXACAE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXACAE
LISTEND
UK76209 COVER LETTER END
UK76211 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM50592 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users utilizing starjoin *
* pair-wise join technology and *
* parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Sometimes a query which should run *
* in a short amount of time may run *
* longer when the following conditions *
* are met. *
* *
* 1. Pairwise join plan is used *
* 2. There is only one pairjoin leg *
* 3. The query is estimated to run in *
* less than 0.5 sec. *
* *
* When the conditions above are met, *
* the query can actually have a longer *
* elapsed time. *
* *
* SQLPAIRWISEJOIN SQLSTARJOIN *
1 * SQLPERFORMANCE SQLPARALLELISM *
* PARALLELISM DB2PARALL/K *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Sometimes a query that should run in a short amount of time
may run longer when the following conditions are met.
1. Pairwise join plan is used
2. There is only one pairjoin leg
3. The query is estimated to run in less than 0.5 sec.
When a pairjoin plan is being processed, regardless
of whether the user enables parallelism or not,
DB2 will always try to activate parallelism to process
the pairjoin legs.
The problem occurs because of a bug in the time interval
used for the parent task to wake up and check the child
task status.
The problem described above is fixed in some cases
by using a short initial time interval for the
parent task to wake up and check the status of the
child task.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM50592
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM50592 corrects a performance problem when a pair-wise join
plan is used for a short-running query with estimated elapsed
time less than 0.5 second. In that case, the actual elapsed
time may be over 0.5 sec.
To make this fix effective for a static application, it must
be rebound after application of this PTF. Review the PTF
cover letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRTS PM50592
DSNXOGP PM50592
DSNXOPJD PM50592
DSNXROPT PM50592
DSNXRPJP PM50592
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM50592 DSNXGRTS DSNXOGP DSNXOPJD DSNXROPT DSNXRPJP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNXGRTS
DSNXOGP
DSNXOPJD
DSNXROPT
DSNXRPJP
LISTEND
UK76211 COVER LETTER END
UK76231 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53520 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of the LOAD utility *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU338I message was issued when *
* LOAD INTO TABLE with IGNOREFIELDS YES *
* was specified with a DECFLOAT(16) or *
* DECFLOAT(34) field, which did not *
* correspond to columns in the target *
* table. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A LOAD INTO TABLE with IGNOREFIELDS YES was specified with a
DECFLOAT(16) or DECFLOAT(34) field. MSGDSNU338I(INVALID COLUMN
SPECIFICATION) message was issued for the field when the field
did not correspond to columns in the loaded table.
The problem occured because two local variables were not set
properly for DECFLOAT(16) and DECFLOAT(34) field types.
The LOAD utility code has been modified to correct the reported
problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53520
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURUFL PM53520
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53520 DSNURUFL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURUFL
LISTEND
UK76231 COVER LETTER END
1
UK76247 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55096 -
****************************************************************
* USERS AFFECTED: DB2 V10 data sharing users running in *
* compatibility mode. *
****************************************************************
* PROBLEM DESCRIPTION: For certain DDL operations, drain *
* locks may be held on partitions *
* past commit. *
* *
* When running in coexistence mode with *
* a V8 or V9 member in the data sharing *
* group, the following abends may occur *
* when running certain utilities: *
* - ABEND04E RC00C202AA in DSNB1SWD *
* on a V10 member *
* - ABEND04E RC00C202B2 in DSNB1PPP *
* on a V8 or V9 member *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When certain DDL operations are performed against a partitioned
table space or index (including ALTER ADD COLUMN, ALTER ADD
PART, ALTER LOCKSIZE, and several others), it is necessary to
acquire a drain on the entire object. In V10 New Function Mode,
this requires only a single drain on part 0, but in V10 Compat
Mode a drain on each individual part must also be acquired.
For these additional drains, the tracking is not in place to
release the drain locks at commit time.
Additionally, when utilities running on a V10 member request a
Drain All on an entire partitioned table space or index, it is
also necessary to acquire drains on the individual parts, and
to send a notification to other members that the drain is being
done. However, the notification is being sent before the part-
level drain lock is acquired, resulting in a timing window where
a V8 or V9 member can reopen the partition. This can result in
a pair of abends (ABEND04E RC00C202AA on the V10 member, along
with ABEND04E RC00C202B2 on the V8 or V9 member).
The drain logic has been modified to track the additional drains
acquired in Compatibility Mode, to ensure that they will be
released at commit. Additionally, the notification to other
members has been moved to after the partition drain lock is
acquired.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55096
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 PM55096
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PM55096 DSNB1DRA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DRA
LISTEND
UK76247 COVER LETTER END
UK76249 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54095 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and DB2 9 for *
* z/OS *
****************************************************************
* PROBLEM DESCRIPTION: 1. Documented offsets for IFCA fields *
* IFCAR0 and IFCAR15 are incorrect. *
* *
* 2. Documented description of field *
* QW0199BP is incorrect. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. Offsets to fields IFCAR0 and IFCAR15 in DSNDIFCA are
only correct for READS request for IFCID129. For IFI
commands, these offsets are incorrect.
2. Contents of field QW0199BP is the bufferpool ID. However,
that ID is represented differently if the IFCID199 is obtained
via an IFI READS request as opposed to IFCID199 that is written
as part of a statistics trace to all other destinations.
1. Define 2 new fields IFCACR0 and IFCACR15 to store the return
and reason codes for an IFI command.
2. Correctly describe the contents of QW0199BP.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54095
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDIFCA PM54095
DSNDQW02 PM54095
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54095 DSNDIFCA DSNDQW02
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
1 DSNDIFCA
DSNDQW02
LISTEND
UK76249 COVER LETTER END
UK76251 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53952 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS executing a SELECT *
* statement with LOB data retrieved. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90D01 occurs at *
* DSNOTCSO+519C while materializing the *
* LOB data from the SELECT statement. *
****************************************************************
* RECOMMENDATION: When selecting LOB data, DB2 would normally *
* hold a lock and a page latch to serialize *
* with other concurrent SQL operations. A *
* lock sometimes can be avoided if the data *
* row is committed already, so a page latch is *
* used for serialization. While retrieving *
* the LOB column data, the page latch could be *
* released and re-acquired again and some *
* verifications are performed to ensure the *
* data is not modified after the release of *
* the page latch. If the data is modified *
* which is the customer's case, then DB2 would *
* re-examine the page again. DB2 did not *
* reset an internal flag to indicate the data *
* is 'uncommitted', instead it returns this *
* 'uncommitted' data which caused the abend *
* later. *
****************************************************************
DB2 code has been fixed to reset an internal flag to indicate
the data is 'uncommitted' to force DB2 to acquire the lock.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53952
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRNXT PM53952
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53952 DSNIRNXT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRNXT
1 LISTEND
UK76251 COVER LETTER END
UK76309 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM38329 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD INCURSOR *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNL406I is issued during -STOP DDF *
* processing for each LOAD INCURSOR *
* utility that had been previously *
* executed that loaded data from a remote *
* location. MSGDSNL423I is then issued *
* during a subsequent -START DDF. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD INCURSOR specifying a SELECT from a table from a remote
site and utilizing TCP/IP completes with RC0 and the table
is loaded correctly. However, when a -STOP DDF command is
issued, one DSNL406I message (THREAD luwid=token AT PARTICIPANT
location MAY BE INDOUBT BECAUSE OF A COMMUNICATION FAILURE. DB2
COMMITTED THE THREAD. INFORMATION RECORDED IN TRACE RECORD WITH
IFCID=209 AND IFCID SEQUENCE NUMBER=seq-no) is issued for each
of the above utilities executed due to DDF considering them
indoubt threads.
During a subsequent -START DDF command, DDF indoubt thread
processing handled each of the above and issued one DSNL423I -
message (AUTOMATIC RESOLUTION OF luwid=token WITH PARTICIPANT
location RESULTED IN COMMIT) for each one of them.
This problem occurs due to an inconsistency between DDF and LOAD
INCURSOR processing in conjunction with a two-phase commit
optimization technique utilized by DDF.
Note that this problem only occurs if the Communications Data
Base is configured to access the remote location via TCP/IP
connections.
LOAD INCURSOR utility code and DDF processing code have been
changed to coordinate the two-phase commit processing in order
to eliminate the potential of a DDF related indoubt thread.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM38329
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM38329 has modified CSECTs in both the
DSNUT101 and DSNLDTML load modules, affecting the
utility batch and DB2 DDF address spaces. After the PTF has
been applied, it will become active in the utility batch address
1 space immediately upon job submission, while it will not take
effect in the DB2 DDF address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DDF address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCMT2 PM38329
DSNUGSIT PM38329
DSNURILD PM38329
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM38329 DSNLCMT2 DSNUGSIT DSNURILD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCMT2
DSNUGSIT
DSNURILD
LISTEND
UK76309 COVER LETTER END
UK76352 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56535 -
****************************************************************
* USERS AFFECTED: DB2 V10 NFM mode users with a mix of pseudo *
* delete eligible (PGIDFREE=0) and non-pseudo *
* delete page types (older) in a UTS table *
* space may be impacted. *
****************************************************************
* PROBLEM DESCRIPTION: RC00C90105 DSNIKDEF:0C30 . *
* DSNU518I Broken Page error X'0C30' . *
* DSN1990I DSN1CPGD CODE=X'0C28' . *
* Other similar broken page error codes *
* may be seen. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During cross-partition update operations, rids for pointer rows
are stored in a rid list and subsequently removed from the page
during COMMIT Phase processing. The code that handles removal of
the pointer rows was not setting a flag correctly to distinguish
between pseudo delete (DB2 V10 currently committed) page types
and non-pseudo deleted (pre-V10 NFM format) page types. As a
result, the pointer row was left as an orphan entry on the page.
DSN1COPY, COPY utility with CHECKPAGE (default) and internal
DB2 checks will detect the extra six bytes that is unaccounted
for in PGFREE and various abends are taken. The orphan pointer
1 row can be removed by running the REORG utility.
DB2 code has been changed to set the pseudo delete flag
correctly for the corresponding page format.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56535
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 PM56535
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56535 DSNIKDEF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIKDEF
LISTEND
UK76352 COVER LETTER END
UK76370 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55991 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of utility inline statistics *
* processing and RUNSTATS utility. *
****************************************************************
* PROBLEM DESCRIPTION: A REORG utility with inline statistics *
* ended with a RC8 after a message *
* MSGDSNU622I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REORG with STATISTICS option issued a message DSNU622I - ...
CATALOG UPDATE FOR ... NOT SUCCESSFUL, REASON = 00C9008E,
because of the catalog table access failure. Then the utility
failed with a RC8.
The problem occurred because the return code from the catalog
table access was saved directly for the statistics update.
DSNU622I is a warning message and should cause a RC4 instead of
a RC8. This message may be issued for the following catalog
tables:
SYSCOLUMS
SYSCOLUMS_HIST
SYSINDEXES
SYSINDEXES_HIST
The code has been modified to return RC4 when DSNU622I is
issued.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55991
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
DSNUSEF2 PM55991
DSNUSEOF PM55991
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55991 DSNUSEF2 DSNUSEOF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSEF2
DSNUSEOF
LISTEND
UK76370 COVER LETTER END
UK76379 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54017 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS customers using ALTER TABLE *
* ALTER COLUMN with the SET DEFAULT or DROP *
* DEFAULT clause on user-defined type (UDT) *
* column. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 *
* DSNXIDDL.DSNXI14:P043 may occur *
* on ALTER TABLE ALTER COLUMN with the *
* SET DEFAULT or DROP DEFAULT clause *
* specified. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 DSNXIDDL.DSNXI14:P043 may occur
on ALTER TABLE ALTER COLUMN with the SET DEFAULT or DROP
DEFAULT clause, when the column specified is a UDT column
where the SYSCOLUMNS.DATATYPEID and SYSCOLUMNS.SOURCETYPEID
are both zero.
ALTER TABLE ALTER COLUMN with the SET DEFAULT and DROP
DEFAULT clause has been fixed to handle UDT columns
where the SYSCOLUMNS.DATATYPEID and SYSCOLUMNS.SOURCETYPEID
are both zero.
ADDITIONAL KEYWORDS:
SQLALTER
SQLUDT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54017
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
DSNXIALC PM54017
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54017 DSNXIALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIALC
LISTEND
UK76379 COVER LETTER END
UK76387 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56207 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS user of SQL *
* statement containing multiple OUTER JOIN, *
* table expression, VIEW or common table *
* expressions, and indexes defined on *
* key-expression of LIKE predicate. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at location *
* DSNXOKEX:M160 may occur when an SQL *
* statement satisfies all of following *
* conditions: *
* *
* 1. the SQL contains a table expression, *
* VIEW or common table expression *
* which is nested in multiple OUTER *
* JOIN; *
* 2. the table expression, VIEW or common *
* table expression mentioned in *
* condition #1 contains one LIKE *
* predicate in its WHERE clause; *
* 3. an index on expression(IOE) is *
* defined, and the key of IOE is *
* referenced the left expression of *
* the LIKE predicate in condition #2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at location DSNXOKEX:M160 may occur when
an SQL statement satisfies all of the following conditions:
1. the SQL contains a table expression, VIEW or common table
expression which is nested in multiple OUTER JOIN;
2. the table expression, VIEW or common table expression
mentioned in condition #1 contains a LIKE predicate in its
WHERE clause;
3. an index on expression(IOE) is defined, and the key of IOE
is referenced the left expression of the LIKE predicate in
condition #2.
1
The following example helps to illustrate the problem:
CREATE TABLE T1(C11 CHAR(5), C12 CHAR(5));
CREATE TABLE T2(C21 CHAR(5), C22 CHAR(5));
CREATE TABLE T3(C31 CHAR(5), C32 CHAR(5));
CREATE INDEX IOE1 ON T1(UPPER(C11, 'TESTIOE') ASC);
SELECT TE1.C12
FROM TABLE (SELECT C11, C12
FROM T1
WHERE UPPER(C11, 'TESTIOE') LIKE 'AB%'
AND C12 = 'ABC') AS TE1
LEFT OUTER JOIN T2
ON TE1.C11 = T2.C21
LEFT OUTER JOIN T3
ON T2.C22 = T3.C32;
DB2 didn't handle the LIKE predicate correctly and caused ABEND.
The code in DB2 has been modified correctly to process LIKE
predicate.
Additional keywords: SQLLEFTJOIN SQLTABLEEXPR SQLLIKE
SQLINDEXONEXP SQLFULLJOIN SQLVIEW SQLCTE
SQLOUTERJOIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56207
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOKEX PM56207
DSNXOWPT PM56207
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56207 DSNXOKEX DSNXOWPT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOKEX
DSNXOWPT
LISTEND
UK76387 COVER LETTER END
UK76404 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55595 -
****************************************************************
* USERS AFFECTED: All DB2 Z/OS users that use Set Log Suspend *
* command. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E WITH RC00C200B0 in DSNB1REL *
1 * or ABEND04E WITH RC00C202B1 in DSNB1PER *
* or ABEND04E WITH RC00C202B2 in DSNB1PPP *
* when processing SET Log Suspend command *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Processing a Set Log Suspend, Data Manager misinterpreted the
parameter list format, from Buffer Manager, to allocate internal
structures. An object was not claimed because of this
misinterpretation. This may later cause an ABEND04E
with RC00C200B0, RC00C202B1 or RC00C202B2.
Data Manager component was changed to correctly
interpret the parameter list, and issue a claim for the
object.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55595
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PIT PM55595
DSNUVABK PM55595
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55595 DSNB1PIT DSNUVABK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PIT
DSNUVABK
LISTEND
UK76404 COVER LETTER END
UK76407 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56549 -
****************************************************************
* USERS AFFECTED: DB2 V10 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 or ABEND12F in DSNB1TST during *
* DB2 shutdown. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abends may occur during DB2 shutdown if DB2 has outstanding
HSM recall requests. The abends are due to two problems in
DSNB1TST:
- DSNB1TST issues a WAIT on an ECB list, which contains
31-bit ECB pointers. However, one of the ECBs is in
stack storage above the bar.
- The timer exit routine doesn't correctly handle being
driven in amode(64).
1 DSNB1TST has been modified to acquire its stack storage below
the bar, and to handle having its timer exit being driven in
amode(64).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56549
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1TST PM56549
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56549 DSNB1TST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1TST
LISTEND
UK76407 COVER LETTER END
UK76421 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51989 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of SELECT *
* from INSERT, UPDATE, DELETE, or MERGE *
* statement where host variables or parameter *
* markers are contained, and bound with REOPT *
* 'ONCE', 'ALWAYS' or 'AUTO' option. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E 00E70005 at location *
* DSNXGRDS.DSNXORHV M101 may occur when *
* a SQL statement satisfies all of the *
* following conditions: *
* *
* 1. the SQL statement is SELECT from *
* INSERT, UPDATE, DELETE or MERGE; *
* 2. host variables or parameter markers *
* are contained in the SELECT part, *
* and also in the INSERT, UPDATE, *
* DELETE or MERGE part; *
* 3. the SQL statement is bound with the *
* option: REOPT 'ONCE', 'ALWAYS' or *
* 'AUTO'. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E 00E70005 at location DSNXGRDS.DSNXORHV M101 may
occur when a SQL statement satisfies all of the following
conditions:
1. the SQL statement is SELECT from INSERT, UPDATE, DELETE or
1 MERGE;
2. host variables or parameter markers are contained in the
SELECT part, and also in the INSERT, UPDATE, DELETE or MERGE
part;
3. the SQL statement is bound with the option: REOPT 'ONCE',
'ALWAYS' or 'AUTO'.
An example with following pattern helps to illustrate the
problem:
(Note that: 'val1' and 'val2' could indicate host variable or
parameter markers.)
CREATE TABLE TAB1 (C1 CHAR(5), C2 CHAR(10));
An application(such as written with C language):
main()
{
......
SELECT A.C2
FROM FINAL TABLE
(UPDATE TAB1
SET C1 = 'ABC'
WHERE C2 = :val1) AS A
WHERE A.C1 = :val2;
......
}
BIND PACKAGE(...) MEMBER(...) REOPT(ONCE);
DB2 didn't handle the the host variable or parameter markers in
the above SQL correctly and caused the ABEND.
DB2 is updated correctly to handle the parameter markers
or host variables in SELECT from INSERT, UPDATE, DELETE
or MERGE statement with bind option REOPT 'ONCE', 'ALWAYS'
or 'AUTO'.
Additional Keywords: SQLSELWUPDATE SQLHOSTVAR SQLPMK
SQLPMARKER PARAMETERMARKER
SQLSELWDELETE SQLSELWMERGE
SQLSELWINSERT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51989
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 PM51989
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51989 DSNXORHV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORHV
1 LISTEND
UK76421 COVER LETTER END
UK76431 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54294 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, DB2 for z/OS V9.1, *
* and DB2 for z/OS V10 users of the *
* IFCID flat file (DSNWMSGS). *
****************************************************************
* PROBLEM DESCRIPTION: DSNWMSGS needs to be udpated to *
* reflect changes since the *
* last quarter of 2011. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Updates to the IFCID flat file (DSNWMSGS) since the last
quarter of 2011 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 UDB for z/OS V8
- DB2 for z/OS V9.1
- DB2 for z/OS V10
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54294
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 PM54294
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54294 DSNWMSGS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNWMSGS
LISTEND
UK76431 COVER LETTER END
UK76439 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56662 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C200C0 in DSNB5CMX, *
* DSNB5COM, DSNB5RAP, or DSNB5RDP. *
* *
1 * ABEND04E RC00C200A4 in DSNB5CMX, *
* DSNB5COM, DSNB5RAP, or DSNB5RDP. *
* *
* ABEND0C1 or ABEND0C4 in ICYEXIT. *
* *
* Various other abends in Media Manager. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abends are the result of an agent extending a dataset to an
additional volume, connecting to the dataset with a new DDNAME,
and disconnecting the old DDNAME, without detecting an active
I/O on the old DDNAME. Although the extend process correctly
finds all pages requiring an I/O wait, it may fail to actually
wait for some of them.
The extend logic has been modified to ensure that a wait will
be done for all required pages.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56662
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The ++HOLD and action is for DB2 users running in z/OS 1.12 or
higher only. See PM46045 APAR/PTF text for additional
information.
The following summarizes the interactions of DB2 APARs PM17542,
PM46045, and z/OS APARs OA36101, OA37361, and OA37362. It is
intended to help you determine when to apply DB2 and z/OS APARs,
and in what order.
1. PM17542 only - exposed to overlay and missing SMF I/O
counting at address space level. MEMDSENQMGMT irrelevent.
2. PM17542 with OA36101 - exposed to missing SMF I/O counting
at address space level only. MEMDSENQMGMT irrelevent.
3. PM17542 with OA36101, OA37361 & OA37362 - no longer exposed
to either problem.
4. PM17542 with PM46045 - S99DASUP setting now only turned on
when MEMDSENQMGMT is enabled. Exposed to overlay and
missing SMF I/O counting at address space level ONLY when
MEMDSENQMGMT is ENABLED.
5. PM17542 with PM46045 & OA36101 - S99DASUP setting now only
turned on when MEMDSENQMGMT is enabled. Exposed to missing
SMF I/O counting at address space level ONLY when
MEMDSENQMGMT is ENABLED.
6. PM17542 with PM46045, OA36101, OA37361 & OA37362 - no longer
exposed to either problem. Performance benefits for both
features introduced with PM17542 only available when
MEMDSENQMGMT is ENABLED.
1
Instructions on setting MEMDSENQMGMT to DISABLE or ENABLE:
----------------------------------------------------------
Work with your system programmer to complete one of the
following actions:
- Update the ALLOCxx parmlib member to set the SYSTEM
MEMDSENQMGMT value.
SYSTEM MEMDSENQMGMT(DISABLE) or
SYSTEM MEMDSENQMGMT(ENABLE)
- Issue system command SETALLOC
SETALLOC SYSTEM,MEMDSENQMGMT=DISABLE or
SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE
Note:
1. Updating the ALLOCxx parmlib is strongly recommended as it
remains effective across IPLs. You may apply the PTF and
update the ALLOCxx parmlib member at different times.
However the benefit of the APAR will only be available after
re-IPL with ALLOCxx changes or after issuing the SETALLOC
command as described above.
2. If SETALLOC SYSTEM,MEMDSENQMGMT command is used, a DB2
restart is required to make the change effective.
3. System command D ALLOC,OPTIONS can be used to display the
status of MEMDSENQMGMT in z/OS.
Sample DISPLAY output:
IEFA003I 15.35.15 ALLOC OPTIONS
SPACE PRIMARY: 4
SECONDARY: 24
:
SYSTEM IEFBR14_DELMIGDS: LEGACY
TAPELIB_PREF: EQUAL
REMIND_INTV: 90
VERIFY_UNCAT: FAIL
TEMPDSFORMAT: INCLUDELABEL
MEMDSENQMGMT: ENABLE
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1OST PM56662
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56662 DSNB1OST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1OST
LISTEND
1UK76439 COVER LETTER END
UK76444 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58212 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability fix. *
* There are no external symptoms. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR makes some serviceability corrections. There are
no external symptoms for this problem.
Code was changed for serviceability purposes. There are no
external effects.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58212
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX8EKG PM58212
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58212 DSNX8EKG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX8EKG
LISTEND
UK76444 COVER LETTER END
UK76445 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56206 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS XML users of the *
* XMLPARSE function in a Common Table *
* Expression (CTE). *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E2000D can occur at *
* location DSNOCLEN DSNSVSFB offset 0848 *
* (offset0848) when the XMLPARSE function *
* is used in a Common Table Expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E2000D can occur at location DSNOCLEN DSNSVSFB
offset 0848 (offset0848) when the XMLPARSE function is used in a
1 Common Table Expression.
The following CTE example illustrates the problem.
WITH T1 AS
(SELECT XMLSERIALIZE(XMLPARSE(
'<a><b><c>ABC</c></b></a>')
AS CLOB) AS T1_CLOB
FROM SYSIBM.SYSDUMMY1),
T2 AS
(SELECT XMLPARSE(T1_CLOB) AS T2_XML
FROM T1)
SELECT T1_CLOB, T2_XML
FROM T1, T2;
Inside the T2 CTE, T1_CLOB is the input for the XMLPARSE
function. It is also the result of XMLSERIALIZE function and it
has been serialized to a CLOB. DB2 does not handle the CLOB
internal structure correctly, which leads to the abend during
the clean up time.
The code in DB2 has been modified to avoid the abend when the
XMLPARSE function is used in an CTE (Common Table Expression).
Additional Keywords: SQLLOB SQLXML SQLXMLPARSE SQLCTE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56206
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOLSET PM56206
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56206 DSNOLSET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOLSET
LISTEND
UK76445 COVER LETTER END
UK76455 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51073 -
****************************************************************
* USERS AFFECTED: DB2 9 and 10 for z/OS users of NOT PADDED *
* Data Partitioned Secondary Index (DPSI) and *
* Index On Expression (IOE) *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may be returned by a *
* query if a NOT PADDED DPSI is used to *
* return rows in order and a matching *
1 * predicate of the index is a LIKE *
* predicate matching on a column *
* expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may produce incorrect output for 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.
For example,
SELECT C2
FROM T1
WHERE SUBSTR(C1, 1, 4) LIKE 'A%'
ORDER BY SUBSTR(C1, 1, 4);
There exists a NOT PADDED DSPI defined on T1 as below:
CREATE INDEX DPSI1
ON T1 (
SUBSTR(C1, 1, 4)
)
PARTITIONED
NOT PADDED;
If DPSI1 is used to return rows for the above query, the output
may be out of the order defined by the ORDER BY clause.
DB2 10 for z/OS can return the correct result if the selected
access path is an INDEX-ONLY access.
For example,
SELECT SUBSTR(C1, 1, 4)
FROM T1
WHERE SUBSTR(C1, 1, 4) LIKE 'A%'
ORDER BY SUBSTR(C1, 1, 4);
But DB2 9 for z/OS may return incorrect output even if INDEX
ONLY access is chosen.
Additional Keywords:
SQLINCORR SQLINCORROUT DB2INCORR/K SQLINDEXONEXP SQLLIKE DPSI
The optimizer must perform an additional sort to make sure the
returned rows are in order.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51073
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM51073:
A rebind is necessary to rebuild package and/or plan structures
1 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 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCCX PM51073
DSNXOGCX PM51073
DSNXOGOR PM51073
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51073 DSNXOCCX DSNXOGCX DSNXOGOR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCCX
DSNXOGCX
DSNXOGOR
LISTEND
UK76455 COVER LETTER END
1
UK76457 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55976 -
****************************************************************
* USERS AFFECTED: DB2 users with queries that can be *
* supported by index only access. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may make one of the following *
* access path choices resulting in poor *
* performance. *
* * An index may be selected that *
* cannot provide index only access *
* when an index only choice is *
* available. *
* * An index may be selected as *
* index only when another index *
* is also index only and can *
* provide superset matching. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Consider the following indexes...
IX1 (C1, C2)
IX2 (C2, C1, C3)
If index IX1 can provide index only access for a query, index
IX2 can also be index only. Further, if the query can match
on all three columns of IX2, that filtering is guaranteed to
be as good as or better than IX1 since the matching columns of
IX2 (C2,C1,C3) are a superset of the matching columns of
IX1 (C1,C2).
In DB2 9 for z/OS, this change will only be in effect if zparm
OPTIXOPREF is set to ON.
Additional keywords:
SQLACCESSPATH SQLPERFORMANCE INDEXONLY
DB2 has been changed to choose index only access
appropriately based on the scenarios described. Note that this
APAR does not always result in index only access being chosen
over index+data access as there are legitimate reasons
why an index+data choice can perform better.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55976
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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
1 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 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCSC PM55976
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55976 DSNXOCSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSC
LISTEND
UK76457 COVER LETTER END
UK76480 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49449 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of *
* DSN_COLDIST_TABLE *
****************************************************************
* PROBLEM DESCRIPTION: DSN_COLDIST_TABLE may contain the *
* following incorrect values: *
* 1. The FREQUENCYF column may display *
* a frequency greater than 100% *
* 2. The LOWVALUE and HIGHVALUE columns *
* may be prefixed by garbage values, *
* and may be truncated. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSN_COLDIST_TABLE may sometimes contain incorrect values in
the following fields:
1. The FREQUENCYF column may display a value over 100%
1 (e.g., 1.0000002393535539E+00), or the sum of the frequencies
for each COLVALUE in the table exceed 100% even after
taking rounding error into consideration.
2. The LOWVALUE and HIGHVALUE columns may be prefixed by
some garbage data when the data type of the column is
VARCHAR, VARGRAPHIC or VARBINARY. Also, the end of the data
may be truncated.
(e.g., HIGHVALUE='0010FFFFFFFFFFFFFFFFFFFFFFFFFFFF'
garbage value of '0010' precedes the actual high value.)
The FREQUENCYF column error can occur because of the
inaccurate precision of variables used to store the value.
The LOWVALUE/HIGHVALUE columns can contain garbage values
because of improper handling of the values for the specified
data types.
Additional Keywords:
SQLEXPLAIN
Code is corrected to address the problems described above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49449
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM53062:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM53062 corrects a problem that incorrect output may be
returned by a query with GROUP BY clause and a set function
with DISTINCT.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM38744:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM38744 corrects a problem of inaccurate cost estimation for an
index on the inner table in a join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOD16 PM49449
DSNXOGBM PM49449
DSNXOPRP PM49449
1 DSNXOPRS PM49449
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49449 DSNXOD16 DSNXOGBM DSNXOPRP DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOD16
DSNXOGBM
DSNXOPRP
DSNXOPRS
LISTEND
UK76480 COVER LETTER END
UK76482 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55105 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, V9 and V10 users of *
* Sequence. *
****************************************************************
* PROBLEM DESCRIPTION: When record length of SYSSEQUENCES was *
* larger than X'FF', incorrect before *
* image was saved in log. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When dealing with a row in catalog table SYSSEQUENCES page, DB2
code was using MVC to copy before image to log, but MVC can only
copy storage not larger than 256 bytes. So, the before image
will not be copied correctly if the storage length is bigger
than 256 bytes.
DB2 code is fixed to use DSNIMVCL to copy the before image to
log correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55105
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
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
DSNIQGSE PM55105
DSNIUMAV PM55105
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55105 DSNIQGSE DSNIUMAV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIQGSE
DSNIUMAV
LISTEND
UK76482 COVER LETTER END
UK76516 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56809 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2 Version 10 *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00D10341 in DSNJR103 *
* reading the logs with an IFI READS *
* for IFCID 306 application in a data *
* sharing environment. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While reading up to the current LRSN on the host member of
a data sharing group, DSNJR103 had read the current log CI
from the active log data set. The next CI was accessed from
the output buffer. A timing window exists where DSNJR103
can attempt to access the current LRH under construction,
which can result in the ABEND04E RC00D10341.
DSNJR103 has been changed so that the current LRH under
construction will not be accessed when reading up to the
end of the log LRSN.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56809
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 PM56809
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56809 DSNJR103
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJR103
LISTEND
UK76516 COVER LETTER END
1
UK76522 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57107 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG TABLESPACE SHRLEVEL CHANGE utility *
****************************************************************
* PROBLEM DESCRIPTION: RECOVER failed with ABEND04E RC00C90101 *
* in DSNIBHRE ERQUAL500E when using a *
* recovery base from an inline image copy *
* generated by a REORG TABLESPACE *
* SHRLEVEL CHANGE. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a RECOVER on a table space, and it used as its recovery
base an inline image copy dataset generated by a REORG
TABLESPACE SHRLEVEL CHANGE utility execution in the past.
The RECOVER utility failed with ABEND04E RC00C90101 in
DSNIBHRE ERQUAL500E during log apply because of a down level
page.
The reported problem is caused by an incorrect program logic
in REORG TABLESPACE SHRLEVEL CHANGE execution, where REORG can
miss copying incremental changes to the inline copy dataset
in the last log iteration if there are no log records applied
prior to the last log iteration.
Code has been modified to correct the REORG logic to correctly
copy the incremental changes to the inline copy dataset.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57107
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURLOG PM57107
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57107 DSNURLOG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURLOG
LISTEND
UK76522 COVER LETTER END
UK76527 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49158 -
****************************************************************
1 * USERS AFFECTED: All users of DB2 UDB for z/OS V8, *
* DB2 9 for z/OS, or DB2 10 for z/OS who use *
* DSN1COPY with the CHECK option. *
****************************************************************
* PROBLEM DESCRIPTION: DSN1COPY CHECK does not validate *
* segment chains *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently, DSN1COPY does not check for invalid segment chains
within a page.
An invalid segment chain can lead to later issues, such
as a +100 SQLCODE (SQLCODE100)
DSN1COPY is modified to check the validity of segment chains
within a page when the CHECK option is specified.
If a duplicate first segment is encountered, the following
message will be printed:
DSN1990I DSN1COPY BROKEN PAGE. PAGENUMBER = 00000001.
REASON: SEGMENTED SPACMAP:DUPLICATE FIRST SEGMENT.
SERVICE INFO: CODE= 'D6A'X SEGOBID=segment_obid
If a duplicate last segment is encountered, the following
message will be printed:
DSN1990I DSN1COPY BROKEN PAGE. PAGENUMBER = 00000001.
REASON: SEGMENTED SPACMAP:DUPLICATE LAST SEGMENT.
SERVICE INFO: CODE= 'D6B'X SEGOBID=segment_obid
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49158
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN1COPY PM49158
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49158 DSN1COPY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN1COPY
LISTEND
UK76527 COVER LETTER END
UK76530 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56449 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those with applications that *
* utilize global transactions that (outbound) *
1 * access remote downstream locations. *
****************************************************************
* PROBLEM DESCRIPTION: Damaged data may occur if a global *
* transaction (XID) related thread *
* undergoes rollback processing but *
* the rollback must be forwarded to *
* a remote downstream location. *
* Symptoms may include: *
* . Abend 04E-00C90101 DSNIBHRE:5007 *
* . Abend 04E-00C90101 DSNKDLE :500A *
* . Abend 04E-00C90101 DSNIBHUN:500C *
* . Message DSNB212I DSNB1CFC *
* . Message DSNB217I *
* . Message DSNB250E DSNKUNR2 *
* . Message DSNI005I DSNIREDO *
* . Message DSNI006I DSNISREC *
* . Message DSNI010I *
* . Message DSNI012I *
* . Message DSNI014I DSNIBHUN DSNIBHRE *
* . Message DSNI042I DSNISREC *
* . Message DSNI043I DSNISREC *
* . Message DSNI044I DSNISREC *
* . Message DSNI049I DSNISREC *
* . Message DSNU086I *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Via application environments that support XA XIDs, multiple
DB2 for z/OS threads can be created that are related to the
same Global Transaction (XID). If the application logic is such
that one or more of these XID related threads also accesses a
remote location and then the application causes a rollback,
all changes in all related threads at all locations must be
aborted. When a rollback must be forwarded to a remote
(downstream) location, a timing condition can occur that may
cause an invalid sequence of abort processing among all global
transaction related threads. If the invalid abort sequence
occurs, data may be damaged.
DB2 Global Transaction abort processing has been changed to
tolerate a timing condition where the abort processing may be
taken over by another (Global Transaction) related thread.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56449
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNRGTTM PM56449
DSNRUAGT PM56449
DSNRUA02 PM56449
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56449 DSNRGTTM DSNRUAGT DSNRUA02
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNRGTTM
DSNRUAGT
DSNRUA02
LISTEND
UK76530 COVER LETTER END
UK76577 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56385 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the TIMESTAMP *
* built-in function while using a DATE exit. *
****************************************************************
* PROBLEM DESCRIPTION: When executing a query using the *
* TIMESTAMP built-in function while *
* employing an EBCDIC DATE exit, an *
* incorrect result can be returned. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 10 for z/OS, when executing a query using the TIMESTAMP
built-in function with a string argument while employing an
EBCDIC DATE exit, DSNXVDTX, an incorrect result can be returned.
In DB2 9 for z/OS, for the same scenario, the DATE exit is
not invoked and a correct result is returned.
For example, each of the following two queries produce an
incorrect result of '2008-10-28-00.00.00.000000'. Both
invoke the EBCDIC DATE exit using an input string which
can result from the GENERATE_UNIQUE function.
SELECT TIMESTAMP (X'00C8A3B022402AE28C00010401')
FROM SYSIBM.SYSDUMMY1 ;
SELECT TIMESTAMP (X'00C8A3B022402AE28C00010401')
FROM SYSIBM.SYSDUMMYE ;
For comparison purposes, using the same input string, please
note that each of the following two queries produce a correct
result of '2011-11-07-20.16.04.145838'. Neither invoke the
EBCDIC DATE exit.
SELECT TIMESTAMP (X'00C8A3B022402AE28C00010401')
FROM SYSIBM.SYSDUMMYA ;
SELECT TIMESTAMP (X'00C8A3B022402AE28C00010401')
FROM SYSIBM.SYSDUMMYU ;
The difference in the results occurs as follows. The first two
queries return an incorrect result in DB2 10 for z/OS but not
1 in DB2 9 for z/OS. The reason for this is that the validation
order has changed. In DB2 10, the validation order
checks the result of the DATE exit followed by DB2 internal
validation. In DB2 9, the validation order is opposite and the
DATE exit may not be invoked. The TIMESTAMP built-in function
supports more arguments in DB2 10.
In the reported case, the incorrect result occurs in v10 when
the DATE exit is invoked and incorrectly returns a RC 0, "no
errors are detected". The exit should've returned an error or
RC 4. Because the exit is in error, the validation code path
processing returns an incorrect result. If the DATE exit
returns RC 4 as it should, the correct result is returned for
the first two queries. However, the DATE exit should not have
been invoked.
So, the problem occurs for two reasons. The validation order has
changed in DB2 v10, and the EBCDIC DATE exit being employed is
in error. The same exit was used in DB2 9 but was never invoked
by DB2 during validation processing because of the validation
order.
Please note.
(1). In the error case, if the DATE exit returned RC 4 as it
should've, the correct result is returned.
(2). This problem can occur similarly for users of an ASCII
(DSNXVDTA) or UNICODE (DSNXVDTU) DATE exit. Also, this
validation processing can cause an incorrect result to be
returned for the GENERATE_UNIQUE() function as well.
For example, the following query can return an incorrect result
SELECT UNIQ, UTS, CURRENT TIMESTAMP AS TS, COUNT(*)
FROM
(SELECT UNIQ, TIMESTAMP(UNIQ) + CURRENT TIMEZONE AS UTS
FROM
(SELECT GENERATE_UNIQUE() AS UNIQ
FROM SYSIBM.SYSDUMMY1) A
) B
WHERE UTS < CURRENT TIMESTAMP - 1 HOUR
GROUP BY UTS
HAVING COUNT(*) < 1 ;
The code in DB2 is modified to change the validation order to
what it is in DB2 9. This will allow the DATE exit to not
necessarily be invoked and the validation is performed by DB2
allowing the correct result to be returned.
Additional Keywords: SQLTIMESTAMP INCORROUT SQLINCORR
SQLINCORROUT DB2INCORR/K SQLGENUNIQUE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56385
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
Please note. If you are using DATE exits, this concerns you.
If you are using a DATE exit, specifically an EBCDIC, ASCII, or
UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make
sure it is functioning properly. If it is, a query referencing
the TIMESTAMP built-in function should work correctly and no
action is necessary. If however the exit is not working
properly and the query referencing the TIMESTAMP built-in
function worked in DB2 9 but is now not working in DB2 10 (i.e.
it does not return the expected result), then please ensure that
the exit is coded and working properly.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRTIM PM56385
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56385 DSNXRTIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRTIM
LISTEND
UK76577 COVER LETTER END
UK76578 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53818 -
****************************************************************
* USERS AFFECTED: All Users of the DSNTIJEN job *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXOFN3:M200 *
* occurred when invoking an SQL scalar *
* function after running the DSNTIJEN *
* job. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 DSNXOFN3:M200 occurred when invoking an
SQL scalar function after running the DSNTIJEN job.
The abend occurred because the DSNTIJEN job code was not
properly handling the last data row in the SYSVIEWS table
space.
DB2 code has been updated to prevent future occurrences of the
problem.
***Action for PM53818:
This PTF corrects the problem where SQL scalar functions
became unusable after running the DSNTIJEN job.
1 If the DSNTIJEN job has not completed successfully, you should
apply this PTF first before starting or continuing the DSNTIJEN
job.
If the DSNTIJEN job has already completed without this PTF,
you can identify any affected SQL scalar functions by running
the following query:
SELECT R.SCHEMA
,R.NAME
,R.SPECIFICNAME
FROM SYSIBM.SYSROUTINES AS R
WHERE R.INLINE = 'Y' AND
R.ORIGIN = 'Q' AND
LENGTH(R.PARSETREE) = 0;
Any rows returned from the above query identify the affected
SQL scalar functions. You will need to drop and re-create them
to correct the problem.
You do not need to run the query if the DSNTIJEN job has
not been run or DB2 is running in CONVERSION mode, otherwise
this query may return no rows or a negative SQLCODE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53818
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM53818:
This PTF corrects the problem where SQL scalar functions
became unusable after running the DSNTIJEN job.
If the DSNTIJEN job has not completed successfully, you should
apply this PTF first before starting or continuing the DSNTIJEN
job.
If the DSNTIJEN job has already completed without this PTF,
you can identify any affected SQL scalar functions by running
the following query:
SELECT R.SCHEMA
,R.NAME
,R.SPECIFICNAME
FROM SYSIBM.SYSROUTINES AS R
WHERE R.INLINE = 'Y' AND
R.ORIGIN = 'Q' AND
LENGTH(R.PARSETREE) = 0;
Any rows returned from the above query identify the affected
SQL scalar functions. You will need to drop and re-create them
to correct the problem.
You do not need to run the query if the DSNTIJEN job has
not been run or DB2 is running in CONVERSION mode, otherwise
1 this query may return no rows or a negative SQLCODE.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUECML PM53818
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53818 DSNUECML
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECML
LISTEND
UK76578 COVER LETTER END
UK76589 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55941 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users whose *
* query with OPTIMIZE FOR n ROWS or FETCH *
* FIRST n ROWS ONLY contains a subquery. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 might choose a non-correlated *
* subquery instead of correlated *
* subquery access path for a query with *
* OPTIMIZE FOR n ROWS or FETCH FIRST *
* n ROWS ONLY *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 might choose an inefficient access path for a query with
OPTIMIZE FOR n ROWS or FETCH FIRST n ROWS ONLY when it chooses
a non-correlated subquery access path instead of a correlated
subquery access path.
The problems mentioned above are fixed so that DB2 will not
meet such a problem in that situation.
ADDITIONAL KEYWORDS:
SQLSUBQUERY SQLNONCORRSUBQ SQLCORRSUBQ SQLOFNR SQLFFNR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55941
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM55941:
See PM55941 APAR/PTF text for additional information about
why a REBIND is necessary.
PM55941 corrects a problem of a query with OPTIMIZE FOR n ROWS
or FETCH FIRST n ROWS ONLY where DB2 chooses the
1 non-correlated subquery access path instead of the
correlated subquery access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCS PM55941
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55941 DSNXOCS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCS
LISTEND
UK76589 COVER LETTER END
UK76596 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49168 -
****************************************************************
* USERS AFFECTED: All DB2 sysplex parallelism users. *
****************************************************************
* PROBLEM DESCRIPTION: Sysplex query parallelism thread hang *
* in DSNTTSPD UK20421 +0DF0 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Sysplex query parallelism thread hang in DSNTTSPD UK20421 +0DF0
due to DB2 internal defects. For certain DB2 sysplex parallelism
queries, it is possible to running into a timing window when DB2
parallel task have been done with its processing, but its status
has not been updated before it is checked. This will cause the
mother process suspend without being resumed and cause what we
observed in this problem.
The problem is not query specific, but may depend on the amount
of data processed as well as the speed of parallel processes
which will in turn cause the deadlock.
DB2 has been fixed to avoid a deadlock when running in
sysplex parallelism.
Additional Keywords: PARALLELISM SYSPLEX SQLSYSPLEXP
DB2PARALL/K SQLPARALLELIM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49168
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 DSNXPPIP PM49168
DSNXPRE2 PM49168
DSNXPRE3 PM49168
DSNXPSNP PM49168
DSNXRIPE PM49168
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49168 DSNXPPIP DSNXPRE2 DSNXPRE3 DSNXPSNP DSNXRIPE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXPPIP
DSNXPRE2
DSNXPRE3
DSNXPSNP
DSNXRIPE
LISTEND
UK76596 COVER LETTER END
UK76609 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53501 -
****************************************************************
* USERS AFFECTED: All DB2 users who issue an ALTER TABLESPACE *
* to assign a buffer pool with a different *
* page size. *
****************************************************************
* PROBLEM DESCRIPTION: After ALTER TABLESPACE BUFFERPOOL, *
* REPAIR DBD TEST/DIAGNOSE can report *
* the following errors, *
* *
* DSNUEDFI - OBD X'0001' A FILE OBD HAS *
* THE FOLLOWING DIFFERENCES *
* DSNUEDFI - OBDS DIFFER AT OFFSET *
* X'0000004A' OBDFINUM *
* DSNUEDFI - EXISTING VALUE X'0200' *
* DSNUEDFI - REBUILT VALUE X'0100' *
* DSNUEDDR - OBD X'0001' COMPARISON *
* COMPLETE -- 1 ERRORS WERE FOUND *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a table space buffer pool is altered, the internal data
structure is not updated to reflect the change of the buffer
pool size. As a result, REPAIR DBD TEST/DIAGNOSE reports the
OBD errors. Customer can incorrectly receive resource not
available (RNA) condition due to page set full.
DB2 has been changed to set the internal data sturcture
correctly after table space buffer pool is altered.
Applying this apar can not fix the broken OBD. REPAIR DBD
REBUILD can fix the problem.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM53501
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDAFI PM53501
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53501 DSNGDAFI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDAFI
LISTEND
UK76609 COVER LETTER END
UK76610 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54699 -
****************************************************************
* USERS AFFECTED: All users of DSNTIJPA, a premigration health *
* check job for DB2 Version 10 for z/OS that *
* is shipped in DB2 UDB for z/OS Version 8 and *
* DB2 Version 9.1 for z/OS, are affected by *
* this change. *
* *
* All users of DSNTIJPM, a premigration health *
* check job for DB2 Version 10 for z/OS that *
* is shipped in DB2 Version 10, are affected *
* by this change. *
****************************************************************
* PROBLEM DESCRIPTION: The following concerns pertain to the *
* DB2 10 for z/OS premigration report *
* jobs: *
* * DSNTIJPM in V10 *
* * DSNTIJPA in V8 and V9 *
* *
* (1) Report 11 identifies previous- *
* release DB2 sample plans (that do *
* not require customer action) *
* *
* (2) Report 13 is not clear that after *
* migration to V10 each listed *
* package will be incrementally *
* rebound until it is explicitly *
* rebound. *
* *
* (3) Report 29 *
* (a) Does not handle delimited *
* identifiers when scanning *
* SQL statements *
* (b) Can encounter one or more of *
1 * the following errors, causing *
* job step DSNTPMQ to end with a *
* non-zero return code: *
* - SQLCODE -104 / SQLCODE104 in *
* conjunction with message *
* IRX0026I Error running, line *
* nnnn: Invalid whole number *
* - I/O error occurred in *
* "Write_source_dsn". Event:
*
* EXECIO DISKW REPORT29 rc= 1 *
* - IRX0040I Error running *
* DSNTPMQ, line nnnn: Incorrect *
* call to routine *
* (c) Can run for extended periods *
* with no progress indication *
* (d) Does not output the current SQL *
* statement when reporting an *
* unexpected SQLCODE *
* *
* (4) Reports 30, 31, and 32: Contain *
* typographical errors in code for *
* input/output condition handling *
* *
* (5) A report is needed to identify *
* existing simple table space *
* *
* (6) A report is needed to identify *
* trigger packages that need to be *
* rebound before migrating to V10. *
* *
* (7) A report is needed to identify *
* triggers that need to be recreated *
* before migrating to V10. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
Two equivalent premigration checkout jobs are provided for DB2
for z/OS Version 10:
* DSNTIJPA is shipped with DB2 Versions 8 and 9 in order to
provide you the ability to begin checking the catalog and
directory for concerns that must be remedied before commencing
migration to DB2 Version 10.
* The DSNTIJPM job shipped with DB2 Version 10 is equivalent to
and serves the same purpose as DSNTIJPA.
This APAR corrects various problems with DSNTIJPA and DSNTIJPM:
(1) Report 11 includes previous-release DB2 sample plans (that
do not require customer action)
Report 11 lists plans that have been bound directly from
DBRMs. In V10, plans can be bound only from packages, so
the report explains how to convert identified plans, and
also recommends updating BIND statements for those plans.
Currently, the report can include DB2 sample plans from V8
1 and V9. However, it is not essential to convert such plans
because they are of limited interest in V10.
(2) Report 13 is not clearly worded.
Report 13 lists packages that are bound with parallelism.
After migration to V10, any such package will be bound
incrementally whenever executed until it has been explicitly
rebound on V10.
Currently, the wording of the report does not emphasize that
such packages should be explicitly as soon as you migrate to
V10.
(3) Report 29 processing has the following problems:
(a) When scanning SQL statements, it does not handle
delimited identifiers
(b) It can encounter one or more of the following errors,
causing job step DSNTPMQ to end with a non-zero return
code:
- SQLCODE -104 / SQLCODE104 in conjunction with message
IRX0026I Error running, line nnnn: Invalid whole
number
- I/O error occurred in "Write_source_dsn". Event:
EXECIO DISKW REPORT29 rc= 1
- IRX0040I Error running DSNTPMQ, line nnnn: Incorrect
call to routine
(c) When running for extended periods, it does not provide
any progress indication
(d) When reporting an unexpected SQLCODE, it does not output
the current SQL statement
Report 29 identifies packages that contain self-referencing
SQL statements on tables and views on which the package
owner lacks SELECT authority. Currently:
(a) SQL statement scanning bypasses delimited identifiers.
(b) The following runtime errors can interrupt processing:
- The SQLCODE -104 error occurs when shallow parsing of
a candidate package returns a string that contains
an apostrophe character.
- The I/O error occurs when the length of a self-
referencing SQL statement being printed exceeds the
maximum record length for report 29.
- The IRX0040I error occurs when processing encounters
a trigger package having an invalid statement section
number (SECTNOI) value in the SYSIBM.SYSPACKSTMT
catalog table. The cause of the invalid SECTNOI
values was corrected by APAR PK72349. However, any
existing invalid SECTNOI values will remain until the
associated triggers are dropped and recreated.
(c) For large DB2 catalogs or those containing numerous
or complex packages, report 29 processing can require
several hours to complete. An indicator is needed to
show that processing is progressing, as by it is not
suspended on the same package or plan.
1
(d) When an unexpected SQLCODE is received during report
29 processing, diagnostics should include the SQL
statement that received that SQLCODE.
(4) Reports 30, 31, and 32: Code for handling input/output
conditions currently contains typographical errors that
need to be corrected.
(5) A report is needed to identify existing simple table spaces
A simple table space is a table space that is neither
partitioned nor segmented. Although DB2 V10 can use
existing simple table spaces and allows you to alter data,
update data, or retrieve data from them, it does not allow
you to create them. If you accidentally drop a simple
tablespace in V10, you will be unable to recover it.
Therefore, it is recommended that before migrating to V10
you move your data in simple table spaces to table spaces
having a preferred table space type.
(6) A report is needed to identify trigger packages that need
to be rebound before migration to V10.
In V10, use of triggers that have a trigger package that
references a DB2 special register and that was last bound
prior to DB2 Version 8 will fail with SQLCODE -723 (AN ERROR
OCCURRED IN A TRIGGERED SQL STATEMENT IN trigger-name) and
SQLCODE -909 (THE OBJECT HAS BEEN DELETED OR ALTERED) until
it is rebound. Therefore, to avoid interruptions, you are
recommended to rebind such packages prior to migrating to
V10.
(7) A report is needed to identify trigger packages that need
to be recreated before migration to V10.
Triggers created in V8 prior to applying PTF UK42129 (fixes
APAR PK72349) can have an invalid statement section number
(SECTNOI) entry in the SYSIBM.SYSPACKSTMT catalog table.
UK42129 fixes the cause of the problem but requires you to
drop and recreate affected triggers in order to correct
packages that have an invalid SECTNOI value. To avoid
potential problems when using affected triggers, you are
recommended to recreate them as soon as possible.
In response, DSNTIJPM and DSNTIJPA are modified as follows:
(1) Report 29 is modified to prevent failures caused by:
- Strings that contain an apostrophe character
- Output that exceeds the maximum record length
- Errors caused by an invalid value in the SECTNOI column
of the SYSIBM.SYSPACKSTMT table.
(2) Report 29 is also modified to activate a progress indicator
after 6 hours of elapsed processing time. The indicator
writes the following diagnostics to the SYSTSPRT DD:
1 (a) A startup message
Report 29 long run trace initiated
(b) The name of the package or plan currently being analyzed
(c) Tracing of calls to routines used by report 29
(d) A termination message
Report 29 Long run trace terminated
This message appears when the next package or plan
is selected for analysis.
The progress indicator is triggered thereafter every 6
hours of elapsed time until the report 29 processing
completes.
(3) Report 11 is modified to exclude DB2 V8 and V9 sample
plans. The report text is also modified to indicate that
these plans do not need to be considered.
(4) Report 13 is reworded to emphasize that the packages it
lists need to be rebound explicitly after migration to
V10 in order to avoid the expense and overhead of
incremental binding.
(5) Report 33 is added to identify existing simple table spaces
(other than DB2 system and sample table spaces).
(6) Report 34 is added to identify trigger packages that
reference DB2 special registers and that were last bound
prior to DB2 V8.
(7) Report 35 is added to identify trigger packages that have
an invalid statement section number (SECTNOI) in the
SYSIBM.SYSPACKSTMT catalog table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54699
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM54699 (V10)
This PTF modifies V10 premigration checkout job DSNTIJPM. If
you maintain a customized copy of this job then after applying
this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPM
- Delete all lines and copy in the DSNTIJPM member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 V10, run the updated
customized job to check for conditions that may affect your
migration.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIJPM PM54699
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54699 DSNTIJPM
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIJPM
LISTEND
UK76610 COVER LETTER END
UK76631 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57017 -
****************************************************************
* USERS AFFECTED: All IRLM210 (HIR2101), IRLM220 (HIR2220) *
* and IRLM230 (HIR2230) users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C1 may occur in rare case when *
* IRLM calls IMS/DB2 Resume Exit from *
* DXRRL110. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM may call IMS/DB2 Resume Exit with address '80000000'x in
RLPWREXT from DXRRL110 which results in ABEND0C1 with PSW being
in low core. This may happen in a rare case where IRLM
overwrites the request suspend bits in the DBMS RLPL before
returning to the caller, causing the Suspend Exit call to be
skipped. If the caller happens to reuse that RLPL for another
request to IRLM just before IRLM resumes the earlier request,
it results in ABEND0C1.
This is a very rare timing window in IRLM exposed by the race
condition between completion of the original and the processing
of the queued request.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM57017
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL1K0 PM57017
DXRRL2Q0 PM57017
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57017 DXRRL1K0 DXRRL2Q0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL1K0
DXRRL2Q0
LISTEND
UK76631 COVER LETTER END
1
UK76636 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57322 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS, and DB2 10 for z/OS *
* REORG TABLESPACE utility users with *
* PM43132/UK73230 or PM49317/UK73284 applied *
****************************************************************
* PROBLEM DESCRIPTION: This APAR addresses two related issues *
* that may occur after PTF UK73230 (V9) *
* for APAR PM43132 or PTF UK73284 (V10) *
* for APAR PM49317 has been applied. *
* *
* 1. REORG fails with ABEND04E RC00E40005 *
* after MSGICE046A SORT CAPACITY EXCEEDED *
* on a compressed table space with option *
* KEEPDICTIONARY specified due to the *
* average row length estimated too low *
* as reported in MSGICE098I. *
* *
* 2. ABENDS0C9 at DSNURFIT+x'DAB0' *
* when SYSTABLESPACESTATS.DATASIZE is *
* excessively large. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
PM43132 and PM49317 modified the calculation of the estimated
average row length when ALTER ADDed or changed columns exist.
For cases where records needed to be decompressed even though
KEEPDICTIONARY was specified, the average row length of the
rows processed was larger than the estimated average row length.
Decompression would be necessary for altered columns or when
REORG is run with the DISCARD option. DFSORT message ICE098I
AVERAGE RECORD LENGTH - PROCESSED: nnn, EXPECTED: mmm would
report this difference before the utility failed.
When calculating the average row length from a corrupted
Real-Time statistics DATASIZE value, an overflow with ABEND0C9
could occur when the stored value was excessively large.
Average row length calculation was modified to make sure that
decompression is taken into account correctly and not to use
DATASIZE values that are out of range for the given table space
definition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57322
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 PM57322
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57322 DSNURFIT
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFIT
LISTEND
UK76636 COVER LETTER END
UK76642 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55518 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -725 from DSNLXENV when SET *
* CURRENT PACKAGE PATH value contains *
* blanks. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote requester connects to a DB2 10 for z/OS server. The
requester sends a SET CURRENT PACKAGE PATH statement where the
value to be assigned contains one or more blanks. For example,
the following statement contains a valid embedded blank after
the comma.
. SET CURRENT PACKAGE PATH = 'COLLID1', 'COLLID2'
When the DB2 10 for z/OS server parses the SET statement value,
it erroneously returns a SQLCODE -725 for a valid embedded
blank.
NOTE: The same SQLCODE -725 error can occur for SET CURRENT PATH
and SET CURRENT FUNCTION PATH statement.
DB2 10 for z/OS server has been corrected to accept valid
embedded blanks for the SET CURRENT PACKAGE PATH, SET CURRENT
PATH, and SET CURRENT FUNCTION PATH statements.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55518
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLZOSR PM55518
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55518 DSNLZOSR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLZOSR
LISTEND
UK76642 COVER LETTER END
1UK76643 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54771 -
****************************************************************
* USERS AFFECTED: All DB2 IMS Attachment users. *
****************************************************************
* PROBLEM DESCRIPTION: The DB2 IMS Attachment prepare to *
* commit code returns RC4 and RC00D30101 *
* as a vote no, and IMS re-queues the *
* transaction which causes a loop of *
* the commit and re-queuing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR will address the reported problem in which an IMS
transaction issues a commit on a distributed connection and the
DB2 Attachment prepare to commit code returns with a vote no,
RC4 RC0D30101. IMS re-queues the transaction, which will do
another commit that also fails, resulting in a loop.
The underlying cause of the commit on the remote connection is
RACF failures at the remote DB2.
Module DSNMDR00 has been modified to return RC8 when a commit on
a distributed connection gets RC00D30101.
COMPONENT: 5740-IY100-HIYAA10
APARS FIXED: PM54771
SPECIAL CONDITIONS:
COPYRIGHT: 5740-IY100 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNMDR00 PM54771
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54771 DSNMDR00
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNMDR00
LISTEND
UK76643 COVER LETTER END
UK76645 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56542 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users with zparm NPGTHRSH *
* set to a non-zero value or executing *
* queries containing either ... *
* * VOLATILE tables *
* * Predicates for which optimizer *
* estimates zero rows will qualify. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 10 for z/OS may incorrectly use the *
1 * index probing feature. This could lead *
* to increased prepare times and/or *
* inefficient access paths. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 10 for z/OS may use index probing under any of the
following conditions:
* Zparm NPGTHRSH is set to a non-zero value.
* A query references a table defined as VOLATILE.
* DB2 determines that no rows will qualify based on
a predicate or index.
In the process of index probing, DB2 could incorrectly...
* Probe the index when no search value is available (either
from the query text or via REOPT).
* Determine that all rows qualify for the predicate or index
when there are zero rows in the table.
The increased prepare time and/or inefficient access paths
resulting from this problem could lead to poor performance.
Additional keywords:
SQLPERFORMANCE SQLACCESSPATH
DB2 will only perform an index probe when a probe value is
provided either as a literal in the query or via REOPT. Also,
if the index probe determines the table has zero rows, DB2 will
determine the filter factor based on catalog statistics.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56542
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGBM PM56542
DSNXOIXP PM56542
DSNXOPRP PM56542
DSNXOPRS PM56542
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56542 DSNXOGBM DSNXOIXP DSNXOPRP DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBM
DSNXOIXP
DSNXOPRP
DSNXOPRS
LISTEND
UK76645 COVER LETTER END
1
UK76650 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52012 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/Os REORG utility users *
****************************************************************
* PROBLEM DESCRIPTION: Introduction of a new zParm to control *
* the default behavior of REORG *
* TABLESPACE LIST partition processing. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
Currently by default behavior, REORG TABLESPACE LIST on a
partitioned table space will result in a single REORG execution
including all the adjacently specified partitions in the
LISTDEF statement.
For example:
LISTDEF L INCLUDE TABLESPACE DBB.TSS PARTLEVEL 3
INCLUDE TABLESPACE DBB.TSS PARTLEVEL 4
INCLUDE TABLESPACE DBB.TSS PARTLEVEL 8
REORG TABLESPACE LIST L
The above will result in a single REORG execution reorganizing
data partitions 3, 4 and 8 in the same utility operation, as if
REORG TABLESPACE PART (3,4,8) is specified.
While a new PARALLEL keyword is introduced via APAR PM25525 /
PTF UK64588 to override this default behavior in a case by case
basis, many users find this option limiting as they prefer the
behavior of reorganizing LISTDEF partitions one at a time
serially (e.g. due to DASD resource constraint) and they cannot
modify a large number of utility jobs to specify the overriding
PARALLEL keyword.
As a result, this APAR introduces a new DB2 subsystem parameter
( zParm ) named REORG_LIST_PROCESSING. This allows the user to
specify the default setting of the PARALLEL option
when deciding whether REORG would process the LISTDEF partitions
in parallel or serially.
Code has been modified to implement the aforementioned
system zParm for REORG TABLESPACE LIST processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52012
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Actions for PM52012
This PTF adds a new DB2 subsystem parameter in DSN6SPRM named
REORG_LIST_PROCESSING that allows you to specify the default
setting for the PARALLEL option of the DB2 REORG TABLESPACE
utility. The PARALLEL option indicates whether REORG TABLESPACE
1 will process all partitions specified in the input LISTDEF
statement in a single utility execution (PARALLEL YES) or
process each in a separate utility execution (PARALLEL NO).
Valid options for DSN6SPRM.REORG_LIST_PROCESSING are:
* PARALLEL: REORG TABLESPACE will assume PARALLEL
YES when the PARALLEL keyword is not
specified in the utility control
statement.
==> This is the default setting
* SERIAL : REORG TABLESPACE will assume PARALLEL
NO when the PARALLEL keyword is not
specified in the utility control
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter REORG_LIST_PROCESSING=<x>,
where <x> is PARALLEL or SERIAL, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
REORG_LIST_PROCESSING here, the value will be set to the
default of PARALLEL when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
1 ----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for REORG_LIST_PROCESSING to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library.
You need to add these entries to all private copies of your
CLIST output DSNTIDxx member. In each such copy, add the
following lines:
REORG_LIST_PROCESSING CHAR M NONE NONE <x>
Change <x> to the value you specified for
REORG_LIST_PROCESSING in step (2), above.
If you do not add REORG_LIST_PROCESSING to a DSNTIDxx
member, the DB2 installation CLIST will assume
REORG_LIST_PROCESSING=PARALLEL when run with that member
as input.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PM52012
DSNDQWPZ PM52012
DSNDSPRM PM52012
DSNTIDXA PM52012
DSNTIDXB PM52012
DSNTIJUZ PM52012
DSNTINST PM52012
DSNTXAZP PM52012
DSNUGDDM PM52012
DSNWZIFA PM52012
DSN6SPRM PM52012
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52012 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ
DSNTINST DSNTXAZP DSNUGDDM DSNWZIFA DSN6SPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
DSNUGDDM
DSNWZIFA
MACROS
DSN@XAZP
DSNDQWPZ
DSNDSPRM
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6SPRM
1 LISTEND
UK76650 COVER LETTER END
UK76651 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56004 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of XML. *
****************************************************************
* PROBLEM DESCRIPTION: In DB2 9 for z/OS: *
* *
* ABEND04E RC00E70005 *
* DSNNXML.DSNNORES:M390 *
* *
* ABEND04E RC00E70005 *
* DSNNXML.DSNNOINS:M210 *
* *
* Incorrect XML result parsing an *
* XML document *
* *
* In DB2 10 for z/OS: *
* *
* ABEND04E RC00E70005 *
* DSNNXML.DSNNORES:M430 *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 9 for z/OS, ABEND04E RC00E70005 DSNNXML.DSNNORES:M390
or ABEND04E RC00E70005 DSNNXML.DSNNOINS:M210 could occur when
a large XML document is parsed. For the problem to occur,
the XML document needs to be over 120K bytes, and there must
be a large text node over 15K bytes. The position of the
large text node within the document caused logic to handle a
boundary condition to fail. In DB2 10 for z/OS, this problem
occurs as ABEND04E RC00E70005 DSNNXML.DSNNORES:M430.
In DB2 9 for z/OS, incorrect XML result can occur when parsing
an XML document. A text node, attribute node, comment
node or processing instruction node that's greater than 15K
can be truncated incorrectly if there are namespace
declarations in the XML document. There was an error in
calculating the maximum length of XML records that contained
these large nodes if there were namespace declarations.
Also, in DB2 9 for z/OS, incorrect XML result can occur when
parsing an XML document because an XML document was converted
to UTF-8 twice. There was a logic error in detecting the
XML document was already converted to UTF-8 when the XML
document was passed in as a CLOB variable. This caused the
XML document to be converted to UTF-8 a second time from
the encoding in the XML declaration.
DB2 was fixed to correct the XML parsing problems.
1 Additional keywords: SQLXML XMLALL
DSNNORES:M430 DSNNORES M430 :M430
DSNNOINS:M210 DSNNOINS M210 :M210
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56004
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOBXI PM56004
DSNNOCCN PM56004
DSNNORCN PM56004
DSNNORES PM56004
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56004 DSNNOBXI DSNNOCCN DSNNORCN DSNNORES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOBXI
DSNNOCCN
DSNNORCN
DSNNORES
LISTEND
UK76651 COVER LETTER END
UK76653 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56661 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL *
* statement using tables where the column is *
* defined with field procedure and referenced *
* in user defined function of ORDER BY clause. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC70005 at location DSNXOGA *
* P001 may occur when an SQL statement *
* satisfies all of following conditions: *
* *
* 1. a column is defined with field *
* procedure and referenced in SELECT *
* list using AS clause; *
* 2. the name specified in AS clause *
* corresponding to the column in *
* condition #1 is used in user-defined *
* function as an input parameter or in *
* expression(such as CAST, CASE, etc); *
* 3. this user defined function or *
* expression in #2 is used in ORDER BY *
* clause. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An ABEND04E RC70005 at location DSNXOGA P001 may occur when an
SQL statement satisfies all of the following conditions:
1. a column is defined with field procedure and referenced in
SELECT list using AS clause;
2. the name specified in AS clause corresponding to the column
in condition #1 is used in user-defined function as an input
parameter or in expression(such as CAST, CASE, etc);
3. this user defined function or expression in #2 is used in
ORDER BY clause.
An example helps to illustrate this problem.
First of all, make an assumption that:
(1) 'FPC' is the name of field procedure defined by user;
(2) 'UDF' is the name of function defined by user.
CREATE TABLE TEST.T1
(COL1 CHAR(8) FIELDPROC FPC,
COL2 VARCHAR(10));
SELECT TAB.COL1 AS C1
FROM TEST.T1 AS TAB
ORDER BY UDF(C1);
DB2 didn't handle the field procedure column that is referenced
in UDF of ORDER BY clause correctly and caused the ABEND.
The code in DB2 has been modified correctly to process an SQL
statement containing field procedure, user-defined function and
ORDER BY clause.
Additional keywords: SQLUDF SQLORDERBY SQLFIELDPROC SQLALIAS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56661
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODTG PM56661
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56661 DSNXODTG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODTG
LISTEND
UK76653 COVER LETTER END
UK76689 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58412 -
1 ****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of trace *
* IFCID 311 - Global Temp Table Usage *
****************************************************************
* PROBLEM DESCRIPTION: Field QW0311QN_OFF in trace IFCID 311 *
* (Global Temp Table Usage) may contain a *
* non-zero value by mistake, falsely *
* implying that field QW0311QN - TEMP TAB *
* CREATOR is truncated *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Field QW0311QN_OFF in trace IFCID 311 may be left uninitialized
by mistake, falsely implying that field QW0311QN is truncated.
Code has been updated to ensure that IFCID 311 field
QW0311QN_OFF is initialized.
Additional keywords: SQLCGTT CGTT IFCID311
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58412
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 PM58412
DSNIWRCC PM58412
DSNIWTTA PM58412
DSNIWTTC PM58412
DSNIWTTD PM58412
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58412 DSNIWKFL DSNIWRCC DSNIWTTA DSNIWTTC DSNIWTTD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWKFL
DSNIWRCC
DSNIWTTA
DSNIWTTC
DSNIWTTD
LISTEND
UK76689 COVER LETTER END
UK76698 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51913 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users with user *
* defined indexes on DB2 catalog. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90110 with ERQUAL5004 *
* in DSNICTBU when creating a user table. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
"DROP INDEX" of a user defined index on a catalog table and
"CREATE TABLE" of a user table were running concurrently when
"CREATE TABLE" encountered ABEND04E RC00C90110 with
ERQUAL5004
in DSNICTBU.
Investigation shows that there is a timing window where "CREATE
TABLE" still references the old OBD (object description) of the
user defined index on the catalog, even though it has already
been successfully dropped.
This timing window is closed by proper serialization between
jobs that intend to update DB2 catalog.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51913
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 PM51913
DSNICUBC PM51913
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51913 DSNIBCTD DSNICUBC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBCTD
DSNICUBC
LISTEND
UK76698 COVER LETTER END
UK76699 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56907 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the DB2 Trace *
* with IFCID 248 activated to trace output *
* host variables using a decimal data type. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 rc10 can occur at location *
* DSNWVCOL +10A6 (OFFSET10A6) when the *
* DB2 Trace is activated with IFCID 248 *
* to trace output host variables using a *
* decimal data type. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 rc10 can occur unexpectedly at location DSNWVCOL
+10A6 (OFFSET10A6) when the DB2 Trace is activated with IFCID
248 (or IFCID248) to trace output host variables using a decimal
1 data type.
When IFCID 248 is enabled to trace output host variables that
have a decimal data type, DB2 does not handle the decimal length
properly which leads to the ABEND.
The code in DB2 has been modified to correct the condition
leading to the abend when using the DB2 Trace with IFCID248 to
trace output host variables with a decimal data type.
Additional Keywords: IFCID248
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56907
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRTHV PM56907
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56907 DSNXRTHV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRTHV
LISTEND
UK76699 COVER LETTER END
UK76766 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56573 -
****************************************************************
* USERS AFFECTED: Users of materialized query tables (MQT) *
* based on views using DROP TABLESPACE or *
* DROP DATABASE. *
****************************************************************
* PROBLEM DESCRIPTION: When an MQT references a view whose *
* base table resides in a different *
* table space, indexes on the MQT may *
* have orphaned index clusters when *
* DROP TABLESPACE is executed on the *
* table space containing the base *
* table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR addresses the following problems:
1. Orphaned index clusters of MQTs based on views
o When an MQT references a view and the view references
a table that resides in a different TABLE SPACE than
the MQT and DROP TABLESPACE is executed on the table
space containing the view's base table, indexes on the MQT
1 may be orphaned.
o When an MQT references a view and the view references
a table that resides in a different DATABASE than the
MQT and DROP DATABASE is executed on the database
containing the view's base table, indexes on the MQT may be
orphaned.
2. Unexpected SQLCODE -601 on CREATE INDEX due to orphaned
index clusters of MQTs as described in problem 1.
DROP TABLESPACE and DROP DATABASE statements have been fixed
to drop index clusters for indexes on MQTs referencing views.
This APAR will not delete existing orphaned index clusters.
Users may manually delete the data sets of the orphaned
index clusters.
ADDITIONAL KEYWORDS:
SQLDROP
SQLMQT
SQLVIEW
SQLCREATE
SQLCODE601
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56573
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIDVW PM56573
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56573 DSNXIDVW
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIDVW
LISTEND
UK76766 COVER LETTER END
UK76774 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57752 -
****************************************************************
* USERS AFFECTED: All DB2 10 users of IFI 306 with editproc *
* capability. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20003 IN DSNSVBK+X'070E' *
* WITH QCAPTURE MSGASN0621E WHEN DECODING *
* A LOG RECORD FOR A TABLE WITH AN *
* EDITPROC DEFINED. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
When decoding Change Data Capture (CDC) log records with a user
provided editproc routine using IFI 306 interface, the storage
used to process each log record is not being freed. This results
in an accumulation of storage (512 byte increments) and
eventually any application trying to request storage in DBM1
address space fails on storage shortage error code RC00E20003.
The DB2 IFI 306 logic is changed to avoid the storage growth
when decoding the log record with user supplied editproc.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57752
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 PM57752
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57752 DSNIDCML
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDCML
LISTEND
UK76774 COVER LETTER END
UK76782 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM49346 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE551 received when a user with *
* system DBADM authority tried to *
* create a table for another user *
* involving a user defined data type. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQLCODE551 received when a user with system DBADM tried to
create a table for another user involving a user defined
data type even though system DBADM authority implicitly
has usage on user defined types.
SQLCODE551 can also be received while using system DBADM
authority for creating or altering a table or view for another
user involving a user defined type or a user defined function.
When user defined function is involved, system DBADM authority
needs to have execute on the function.
Authorization did not take into consideration the creator
1 having system DBADM authority and USAGE on user defined
types or EXECUTE on user defined functions.
DB2 code is changed to allow system DBADM authority to behave
correctly in the above stated scenarios.
Additional keywords: SYSDBADM SQLCODE551
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM49346
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
The "RACF Access Control Module Guide" (SC19-2982-01)
is updated with the changes below.
Chapter 14: RACF authorization checking reference
- In "System privileges" section, a note is added for
SYSDBADM.
SYSDBADM
XAPLPRIV value: DB2AAUTHU
Privcode 287 (x'11F')
The user must have sufficient authority to:
One of these resources: In class:
------------------------------------------------------------
DB2-subsystem.SYSDBADM MDSNSM or GDSNSM
DB2-subsystem.SYSCTRL DSNADM
DB2-subsystem.SYSADM DSNADM
Note: DB2® turns on bit 7 of the XAPLFLG1 field for a user table
that includes user defined data type or user defined function.
If this bit is on, the RACF® access control module bypasses
checking for the SYSCTRL authority.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXA02 PM49346
DSNXA2UM PM49346
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM49346 DSNXA02 DSNXA2UM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXA02
DSNXA2UM
LISTEND
UK76782 COVER LETTER END
UK76785 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM58869 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those where DB2 for z/OS is *
* accessed as a DRDA server via SNA. *
****************************************************************
* PROBLEM DESCRIPTION: DSNL500I message, with sense 0864000n, *
* is issued unnecessarily when a remote *
* application Connects to a DB2 for z/OS *
* server, via SNA, but performs no SQL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application (DRDA) Connects to a DB2 for z/OS server,
via SNA, but does not execute any SQL. When the connection is
terminated, the DB2 for z/OS server may issue message DSNL500I
with sense 0864000n.
Any application behavior that Connects to a remote server for
the purpose of executing SQL, but then does not execute SQL, is
considered erroneous because it consumes network and system
resources (CPU and storage) in order to perform no valuable
work. The application itself will see no errors and operate
successfully, but users should still try to modify their
applications in order to eliminate this erroneous behavior
since it unnecessarily wastes resources.
Although the DSNL500I message may be indicative of this
erroneous remote application behavior, the message itself is
considered to be noise and generates unnecessary concern since
the remote application itself executes successfully.
The DSNL500I message serves no purpose when there is no active
transaction (Unit of Work) because it may represent erroneous
but successful remote application behavior. And under the same
circumstances, no equivalent message would be issued had a
TCP/IP connection been established instead. As a result, DB2
has been changed to suppress the DSNL500I message in this case.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58869
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLVRPL PM58869
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58869 DSNLVRPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLVRPL
LISTEND
UK76785 COVER LETTER END
1
UK76802 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57388 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users with PE PTF UK66087 *
* applied who are running queries containing *
* subqueries and unique key access. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may incorrectly determine the sort *
* order of the data returned by a query *
* if all the following conditions are *
* true. *
* *
* * The query contains an IN or EXISTS *
* subquery. *
* *
* * The IN predicate or correlation *
* predicates in the EXISTS subquery *
* reference a unique key in a table *
* outside the subquery. *
* *
* * There exists a local predicate or *
* set of local predicates on at *
* least one table in the query that *
* is guaranteed to qualify a single *
* row based on a unique index. *
* *
* * PE PTF UK66087 is applied. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Due to this problem, DB2 may
* Return data in an incorrect sort order when ORDER BY is
specified.
* Return incorrect results when sort merge join is used or
GROUP BY or DISTINCT are used in the query.
* Choose an inefficient access path that leads to poor
query performance.
Additional keywords:
SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLPERFORMANCE
SQLACCESSPATH SQLSMJ SQLMSJ SMJ MSJ SQLORDERBY SQLSUBQUERY
SQLCORRSUBQ SQLNONCORRSUBQ SQLGROUPBY SQLDISTINCT
DB2 now correctly recognizes the sorted order of the data.
This will avoid all incorrect output scenarios described
as well as allow DB2 to select more optimal access paths
under these conditions.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57388
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
***Action for PM57388:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM57388 corrects a problem in which DB2 does not properly
determine the sorted order of the data for a query. This
can result in incorrect output and/or poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCSN PM57388
DSNXOCSP PM57388
DSNXOPTH PM57388
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57388 DSNXOCSN DSNXOCSP DSNXOPTH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSN
DSNXOCSP
DSNXOPTH
LISTEND
UK76802 COVER LETTER END
UK76803 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56388 -
****************************************************************
* USERS AFFECTED: All DB2 users running RECOVER to point in *
* time with consistency. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIRSET *
* ERQUAL5001 DURING RECOVER TO *
* PIT WITH CONSISTENCY *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Abend DSNIRSET:5001 occurred because the internal
abend flag was on from a previous DSNIBHUN abend
during RECOVER to PIT with consistency (e.g.
ABEND04E RC00C90101 DSNIBHUN ERQUAL500x). DSNIBHUN
did not reset the internal abend flag properly at
its retry process.
DB2 code is changed to properly reset the internal abend
flag during RECOVER to PIT with consistency.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM56388
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 PM56388
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56388 DSNIBHUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBHUN
LISTEND
UK76803 COVER LETTER END
UK76806 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54662 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* using .NET applications to call a stored *
* procedure on DB2 10 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: After a DB2 for z/OS database server *
* is migrated to Version 10, a .NET *
* application using the IBM Data Server *
* driver calls a stored procedure on the *
* migrated server. The CALL fails with *
* the CLI error message CLI0102E, *
* 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 .NET application did not *
* encounter this error before the DB2 *
* server was migrated to V10. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
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
1 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, .NET has strong-typing semantics and this change in
DB2 server behavior may cause some .NET applications to fail
with the CLI error message CLI0102E, 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 .NET application so
that it satisfies .NET semantics for strong-typing and, thus,
conforms to good .NET programming practices.
Although changing problematic application CALL statements to
conform to good .NET programming practices, as described
above, is the optimal corrective action before migrating or
upon migrating to DB2 Version 10, another alternative action
is to use new support added in this PTF to allow migration to
V10 to complete without first making all application changes.
.
This APAR adds an online-changeable subsystem parameter in
DSN6FAC called DDF_COMPATIBILITY that can be used to specify
whether DDF returns stored procedure parameters according to
their declared types (V10 behavior) or according to the types
of the arguments specified in the CALL statement (pre-V10
behavior) when a non-Java application is using an IBM Data
server driver at Version 9.* and below.
Refer to the PTF COVERLETTER for details.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54662
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM54662 (V10):
This PTF adds an online-changeable subsystem parameter in
DSN6FAC called DDF_COMPATIBILITY that can be used to specify
whether DDF returns stored procedure parameters according to
their declared types (V10 behavior) or according to the types
of the arguments specified in the CALL statement (pre-V10
behavior). Valid settings for DDF_COMPATIBILITY are:
* null : V10 behavior is maintained. DDF returns
stored procedure parameters according their
declared types.
==> This is the default setting
* SP_PARMS_NJV: Pre-V10 behavior is used for stored procedure
CALLs from IBM Data Server for non-Java
clients, Version 9.* and below. DDF converts
the data from a stored procedure's declared
SQL type to the argument type specified in
the CALL statement.
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
1 (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
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add either the keyword parameter 'DDF_COMPATIBILITY=,' or
'DDF_COMPATIBILITY=SP_PARMS_NJV,' to the invocation of the
DSN6FAC macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
DDF_COMPATIBILITY here, the value will be set to
the default of null when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for DDF_COMPATIBILITY
to the CLIST default input members in the SDSNSAMP target
library. You need to add these entries to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
DDF_COMPATIBILITY CHARR M NONE NONE <x>
Change <x> to SP_PARMS_NJV if you specified
'DDF_COMPATIBILITY=SP_PARMS_NJV,' in step (2), above.
Otherwise, change <x> to NULL
If you do not add DDF_COMPATIBILITY to a DSNTIDxx
member, the DB2 installation CLIST will assume
'DDF_COMPATIBILITY=,' when run with that member as input.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSN@XAZP PM54662
DSNDQWPZ PM54662
DSNLXXSS PM54662
DSNLZD00 PM54662
DSNLZS02 PM54662
DSNLZVDA PM54662
DSNTIDXA PM54662
DSNTIDXB PM54662
DSNTIJUZ PM54662
DSNTINST PM54662
DSNTXAZP PM54662
DSNWZIFA PM54662
DSN6FAC PM54662
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54662 DSN@XAZP DSNDQWPZ DSNLXXSS DSNLZD00 DSNLZS02 DSNLZVDA
DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA
DSN6FAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXXSS
DSNLZD00
DSNLZS02
DSNLZVDA
DSNTXAZP
DSNWZIFA
MACROS
DSN@XAZP
DSNDQWPZ
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6FAC
LISTEND
UK76806 COVER LETTER END
UK76808 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56036 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Execution of a dynamic statement *
* results in an intermittent SQLCODE -518 *
* when connected to a DB2 10 for z/OS *
* intermediate server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An application requester at Site 1 connects to a DB2 10 for z/OS
1 intermediate server at Site 2. The application's package was
previously bound at Site 2 with the REOPT(ONCE) option which
results in deferred prepare behavior. The application issues a
PREPARE for a dynamic statement that contains a 3-part name or
alias reference to a downstream server at Site 3. The
intermediate server at Site 2 receives the PREPARE request from
Site 1, but erroneously did not forward the PREPARE to Site 3.
When the subsequent EXECUTE for the dynamic statement is
received, Site 2 forwards it to Site 3. The Site 3 server
attempts to EXECUTE the unprepared statement resulting in
SQLCODE -518.
NOTE: This problem occurs for DB2 10 for z/OS intermediate
servers, and when the application package is bound
DEFER(PREPARE) or REOPT(ONCE|AUTO|ALWAYS).
DB2 has been corrected to always forward the PREPARE statement
to a downstream server regardless of how the application's
package was bound at the intermediate server.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56036
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXPRS PM56036
DSNLZD00 PM56036
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56036 DSNLXPRS DSNLZD00
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXPRS
DSNLZD00
LISTEND
UK76808 COVER LETTER END
UK76814 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57433 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of *
* DISPLAY THREAD command with DETAIL option. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC0000003B *
* at DSNXGRDS . DSNXESQI +0128 / +0136 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DETAIL option is used for DISPLAY THREAD command,
DB2 displays additional information about active, inactive,
and indoubt threads. In the reported case a thread just
completed its task and became no longer available while DB2
1 was collecting the additional information for the thread.
This small timing window caused the reported abend.
DB2 code has been changed to handle the small timing window
for DISPLAY THREAD command with DETAIL option.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57433
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXESQI PM57433
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57433 DSNXESQI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXESQI
LISTEND
UK76814 COVER LETTER END
UK76819 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55938 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users whose *
* query contains an EXISTS subquery and the *
* table or tables in the subquery have a *
* DPSI defined on it. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 might choose a inefficient access *
* path instead of a DPSI access path for *
* the EXISTS subquery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may not give the right cost reduction for the DPSI access
path in the EXISTS subquery. When the problem occurs, it might
result in a poorly performing access path being selected by the
DB2 optimizer.
The problems mentioned above are fixed so that DB2 will not
meet such a problem in that situation.
ADDITIONAL KEYWORDS:
SQLEXISTS SQLACCESSPATH
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55938
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM55938:
1
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCCX PM55938
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55938 DSNXOCCX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCCX
LISTEND
UK76819 COVER LETTER END
UK76827 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58954 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 restart may stall after issuing *
* DSNR021I DSNRRGRC DB2 SUBSYSTEM MUST *
* PERFORM GROUP RESTART FOR PEER MEMBERS *
* when IRLM startup issues a REBUILD *
* for the lock structure. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The second member of a 2-way data sharing group was being
restarted while the other member was already active. During
IRLM startup MSGDXR156I REBUILDING LOCK STRUCTURE TO CHANGE THE
GROUP FUNCTION LEVEL was issued. If the DB2 task issuing the
IDENTIFY to IRLM gets delayed, the STATUS exit receiving the
new lock structure version IDs (VIDs) may store the VIDs
in the DSB block before the IDENTIFY stores the original
lock structure VIDs, resulting in the regression of the lock
structure VIDs. The active member receives the lock
REBUILD notification and updates the new lock structre VIDs
in the SCA. The regressed lock structure VIDs for the
restarting member can cause restart to stall in DSNRRGRC
after incorrectly issuing MSGDSNR021I DSNRRGRC DB2 SUBSYSTEM
MUST PERFORM GROUP RESTART FOR PEER MEMBERS.
1 DSNTLIDE has been changed to detect this situation and to
avoid regressing the lock structure VIDs if a lock structure
REBUILD occurs during IRLM startup.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58954
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTLIDE PM58954
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58954 DSNTLIDE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTLIDE
LISTEND
UK76827 COVER LETTER END
UK76834 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57000 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users of RECOVER utility. *
****************************************************************
* PROBLEM DESCRIPTION: A RECOVER TOCOPY utility recovered a *
* segmented table space with an incorrect *
* image copy which was not for that table *
* space. A following COPY utility then *
* abended with ABENDS0C4 RC0000003B along *
* with the message MSGDSNU1408I. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A RECOVER TOCOPY utility ran on a segmented table space. It
restored an image copy which was not for that table space but
had a same name with a valid image copy without error. A
following COPY utility for that table space issued a message
DSNU1408I - SOURCE DATA SET DOES NOT MATCH TABLESPACE ..., and
then abended with ABEND0C4 RC0000003B at DSNUBASI + x'15CC'.
This problem occurred because the RECOVER utility didn't
recognize the header page of the image copy for the segmented
table space, so skipped the objects checking before restore.
The problem applied to any RECOVER when restoring an image copy.
The RECOVER code has been modified to do the check for the
segmented table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57000
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
DSNUCBAL PM57000
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57000 DSNUCBAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBAL
LISTEND
UK76834 COVER LETTER END
UK76844 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57774 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Lost spacemap updates in data sharing. *
* *
* Corrupted data can result in any of *
* the following symptoms: *
* - 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: *
****************************************************************
In DB2 V10, it is possible for an S-mode spacemap page P-lock to
persist past the point of physically closing the table space.
If the table space is reopened, and the spacemap page updated
again, the P-lock will be reacquired and connected to the new
page buffer. However, the P-lock may be released in the process
of stealing the old page buffer, which still indicates that the
P-lock is held. The page in the new buffer therefore does not
have the protection of the page P-lock and may become regressed.
DB2 has been modified to ensure that S-mode spacemap page
P-locks will no longer be held on to after interest in the page
is released, so that there is no possibility of them surviving
a physical close.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57774
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
DSNB1REL PM57774
DSNB1RWI PM57774
DSNB5SCM PM57774
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57774 DSNB1REL DSNB1RWI DSNB5SCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1REL
DSNB1RWI
DSNB5SCM
LISTEND
UK76844 COVER LETTER END
UK76845 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55814 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may collect incomplete buffer pool *
* statistical data. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DB2 collects buffer pool statistical data concurrently,
some buffer pools may be skipped due to a serialization problem.
DB2 has been fixed to properly serialize while collecting
statistics for buffer pools.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55814
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 PM55814
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55814 DSNB1TSD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1TSD
LISTEND
UK76845 COVER LETTER END
UK76846 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM57194 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNB1DDN. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DB2 releases a drain lock on a single partition, it
incorrectly accesses internal control blocks for all partitions.
It may encounter an abend if it uses an invalid pointer for a
partition that is closed by another agent.
DB2 has been fixed to avoid accessing all partitions while
releasing a drain lock for a single partition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57194
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1DDN PM57194
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57194 DSNB1DDN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DDN
LISTEND
UK76846 COVER LETTER END
UK76847 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57358 -
****************************************************************
* USERS AFFECTED: All DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNB250E DSNB5SCM A PAGE RANGE WAS *
* ADDED TO THE LOGICAL PAGE LIST *
* LPL REASON TYPE=LOCK *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an I/O request is interrupted by a cancel, the resource
recovery routine reissues a write to DASD for the first page,
which incorrectly initializes the tracking information needed
for the next page. Since DB2 fails to recover the next page
and leaves it in a locked state, a subsequent attempt to update
that page can fail and put it into LPL.
DB2 has been fixed to preserve the tracking information during
a recovery of a cancelled I/O request.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57358
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1IOR PM57358
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57358 DSNB1IOR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1IOR
LISTEND
UK76847 COVER LETTER END
UK76862 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58290 -
****************************************************************
* USERS AFFECTED: All DB2 users using -ALTER BUFFERPOOL *
* VPSIZE(0) to delete a buffer pool used by *
* an index on a declared global temporary *
* table (DGTT). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90110 in DSNIFPSC *
* ERQUAL5002 and crashes DB2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When -ALTER BUFFERPOOL command is processed to change the VPSIZE
to 0, DB2 unsuccessfully tries to close a page set for a DGTT
index because it is unable to locate a DGTT index OBD in a
workfile global DBD. DGTT index OBDs are created in a private
DBD specific to an agent. -ALTER BUFFERPOOL command abends and
brings down DB2.
DB2 has been fixed to avoid closing a DGTT index page set when
its buffer pool is deleted through -ALTER BUFFERPOOL VPSIZE(0)
command.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58290
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1ABP PM58290
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58290 DSNB1ABP
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1ABP
LISTEND
UK76862 COVER LETTER END
UK76865 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55921 -
****************************************************************
* USERS AFFECTED: All users of IFC on DB2 10 on z/OS and DB2 *
* 9 on z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: DSNW140I message is missing when -START *
* TRACE command cannot find an available *
* OP destination and destination OPX is *
* specified. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When -START TRACE command specifies DEST(OPX) option, IFC will
look for the first available OP destination. If no available OP
destination exists, the -START TRACE command should fail
and message DSNW140I should be written to the console.
Due to an error in start trace logic, -START TRACE succeeds and
no error message is written. Such a trace would have no
valid destination and will not produce any IFCIDs.
Correct the error in start trace logic to fail the -START
TRACE command when no valid OP destination is found.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55921
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWVCM1 PM55921
DSNWVCST PM55921
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55921 DSNWVCM1 DSNWVCST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVCM1
DSNWVCST
LISTEND
UK76865 COVER LETTER END
1UK76867 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55820 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and DB2 9 for *
* z/OS *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C6 on a bad branch from DSNTLRES *
* after cancelling an agent suspended in *
* CSECT DSNTLSUS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an agent suspended in IRLM is cancelled while being
resumed by IRLM, the agent can be deallocated prior to
the resume. Currently, the IRLM resume exit obtains the
address of the SRB dispatcher from agent owned storage.
Deallocation of the agent may cause the address storage to
be reused such that in improper branch address is used after
resume.
The address of the SRB dispatcher is no longer being loaded
from the agent structure of the resumed agent by the IRLM resume
exit. It is loaded from the MVS control structure instead.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55820
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTLRES PM55820
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55820 DSNTLRES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTLRES
LISTEND
UK76867 COVER LETTER END
UK76870 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55373 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those who enabled IFCID 180 *
* tracing. *
****************************************************************
* PROBLEM DESCRIPTION: Thread loops in DSNLCITR or DSNLCVTR *
* if IFCID 180 tracing is started. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
When IFCID 180 tracing is enabled, DDF related logic is
incorrectly interpreting user data as a DRDA code point and
hence gets into a tight loop.
DB2 for z/OS processing has been changed to correctly recognize
user data and not misinterpret it as a DRDA code point.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55373
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCITR PM55373
DSNLCVTR PM55373
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55373 DSNLCITR DSNLCVTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCITR
DSNLCVTR
LISTEND
UK76870 COVER LETTER END
UK76912 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58376 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically when remote systems are *
* accessed via SNA connections, and only *
* if APAR PM52087 is applied. *
****************************************************************
* PROBLEM DESCRIPTION: Message DSNL501I incorrectly issued. *
* The mode name may appear as blank, or *
* it may appear valid but is actually *
* invalid because the name is padded *
* with binary zeros. *
* The problem only occurs after applying *
* APAR PM52087. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
APAR PM52087 implemented a change that allowed DDF logic to
honor the VarChar(24) nature of the SYSIBM.LUNAMES SYSMODENAMES
column but did not consider that the resultant mode name
variable (extracted from SYSIBM.LUNAMES) must therefore be
padded or initialized with blanks. The invalid padding and/or
initialization can cause a DSNL501I message condition and hence
prevent access to the remote system.
1
When extracting the SYSMODENAME value from the SYSIBM.LUNAMES
row, DSNLVCLM has been changed to first initialize the result
variable to blanks in order to accommodate values that are less
than 8 characters.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58376
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
***Documentation for PM52087:
Please see the PTF cover letter for more information.
This APAR/PTF changes the description for DB2 reason code
00D31030. The change will be documented in the DB2 for z/OS
Codes manual and in the Information Management Software for
z/OS Solutions Information Center.
The explanation for DB2 reason code '00D31030'X is updated to
include the following new bullet item:
. The SYSMODENAME column in the SYSIBM.LUNAMES table in the
communications database (CDB) is greater than 8 bytes.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLVCLM PM58376
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58376 DSNLVCLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLVCLM
LISTEND
UK76912 COVER LETTER END
UK76936 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57492 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of graphic data with sort merge join, *
* COUNT DISTINCT or COUNT_BIG DISTINCT. *
****************************************************************
* PROBLEM DESCRIPTION: Problem 1: *
* Possible incorrect output for an SQL *
* statement with sort merge join and a *
* join predicate that compares graphic *
* data. *
* Problem 2: *
* Possible incorrect output for an SQL *
* statement using COUNT DISTINCT or *
* COUNT_BIG DISTINCT on a vargraphic *
1 * column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Problem 1:
The incorrect output can occur for an SQL statement with a sort
merge join where the join predicate is on graphic data. DB2
generates a derived predicate on the inner table. The MIN or
MAX value calculated for the derived predicate may be incorrect
depending on the data in the join predicate column.
The following example may cause the reported incorrect output:
CREATE TABLE TAB1
(I INTEGER NOT NULL, VG VARGRAPHIC(10));
CREATE TABLE TAB2
(I INTEGER NOT NULL, VG VARGRAPHIC(10));
CREATE UNIQUE INDEX IDX1 ON TAB1(I);
CREATE UNIQUE INDEX IDX2 ON TAB2(I);
insert the following 4 rows into both tables TAB1 and TAB2
VALUES( 1,UX'00420020');
VALUES( 2,UX'00420043');
VALUES( 3,UX'004200200020');
VALUES( 4,UX'0042');
SELECT T1.I,T2.I, HEX(T1.VG)
FROM TAB1 T1, TAB2 T2
WHERE (T2.VG = T1.VG) ;
The query returns less rows than expected. For this example,
the query returns 9 rows instead of the expected 10 rows.
Problem 2 :
The incorrect output occurs because the vargraphic data
is compared incorrectly during the COUNT DISTINCT or
COUNT_BIG DISTINCT comparison.
The following example may cause the reported incorrect output:
Using the same tables as problem 1 with the following data
in both tables.
VALUES( 1, UX'004200430000');
VALUES( 2, UX'00420043');
VALUES( 3, UX'004200430020');
VALUES( 4, UX'0042004300000000');
VALUES( 5, UX'0042004300200020');
SELECT COUNT_BIG (DISTINCT T1.VG),
COUNT (DISTINCT T1.VG)
FROM T1, T2
WHERE (T2.VG = T1.VG)
1 The count returned is 5 instead of 3. Rows 2, 3 and 5 have
the same value. Some duplicate rows are incorrectly counted.
This problem only occurs when the count is evaluated after data
retrieval and after any sorts (PLAN_TABLE column COLUMN_FN_EVAL
is blank).
DB2 has been fixed to compare the graphic data correctly
for derived predicates in sort merge join, COUNT DISTINCT and
COUNT_BIG DISTINCT.
Additional keywords : SQLSMJ SQLCOUNT SQLCOUNTBIG SQLGRAPHIC
SQLINCORROUT SQLINCORR SQLINCORR/K
SQLDISTINCT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57492
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM57492:
See PM57492 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57492 corrects an incorrect output problem where the join
predicate involves graphic data and there is a derived
predicate for inner table of a sort merge join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGSFL PM57492
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57492 DSNXGSFL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGSFL
LISTEND
UK76936 COVER LETTER END
UK76938 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58526 -
****************************************************************
* USERS AFFECTED: All users of SQLPL Routines with DEGREE ANY *
****************************************************************
* PROBLEM DESCRIPTION: Storage leak in the DBM1 address *
* space for long running threads that *
1 * run SQLPL routines with the option *
* DEGREE ANY. *
* . *
* DB2 may ABEND04E with one of the *
* following reason codes: *
* RC00E20003 RC00E20004 RC00E2000B *
* RC00E2000C . *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Excessive storage growth occurs in the DBM1 address space
when long running threads run several static sql queries
inside SQLPL routines that participate in sql query
parallelism. This occurs when you specify the DEGREE ANY
option on the SQLPL routine CREATE or ALTER statement.
.
A control block used in the processing of sql query
parallelism under SQLPL routines was not properly freed.
.
.
DB2 code has changed to free the storage.
.
.
Additional Keywords:
parallelism sqlparallelism sqlcpup sqliop sysplex sqlsysplexp
sqlprocedure native sqlsp sqlstoredproc sqludf sqlnativesqlpl
DB2PARALL/K DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58526
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXECMP PM58526
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58526 DSNXECMP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXECMP
LISTEND
UK76938 COVER LETTER END
UK76959 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58308 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD FORMAT INTERNAL on an *
* index controlled partitioned table space *
1 ****************************************************************
* PROBLEM DESCRIPTION: LOAD FORMAT INTERNAL loads records into *
* the wrong partition(s) when using *
* index controlled partitioning *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD FORMAT INTERNAL was run on an index controlled partitioned
table space. When the indexed column(s) were not the first
defined columns in the table certain internal control block
fields were not set up correctly, resulting in records being
loaded into the incorrect partition.
LOAD FORMAT INTERNAL code has been changed to correctly set up
an internal control block when loading an index controlled table
space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58308
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURUTS PM58308
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58308 DSNURUTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURUTS
LISTEND
UK76959 COVER LETTER END
UK76961 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58403 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of index on *
* expression. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E 00E70005 at DSNXOTL:M990 *
* could occur when a SQL statement *
* references an expression which has *
* an index on expression defined and *
* there's a resource conflict(i.e. dead *
* lock) when retrieving the index on *
* expression from the catalog table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E 00E70005 at DSNXOTL:M990 could occur when
a SQL statement references an expression which has
an index on expression defined and there's a resource
1 conflict(i.e. deadlock) when retrieving the index on
expression from the catalog table.
DB2 is updated to issue SQLCODE , such as -901, -904, when
there's error occurred during retrieving the index on
expression from catalog table instead of abend.
Additional Keywords: SQLINDEXONEXP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58403
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTL PM58403
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58403 DSNXOTL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTL
LISTEND
UK76961 COVER LETTER END
UK76994 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57190 -
****************************************************************
* USERS AFFECTED: All DB2 V10 HDBAA10 installs. *
****************************************************************
* PROBLEM DESCRIPTION: IBM serviceability code enhancement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This code is for IBM service and developement to enable and
use as necessary while servicing customer problems.
Serviceability code updates.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57190
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTADL PM57190
DSNTSLIN PM57190
DSNTSLIP PM57190
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57190 DSNTADL DSNTSLIN DSNTSLIP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNTADL
DSNTSLIN
DSNTSLIP
LISTEND
UK76994 COVER LETTER END
UK76996 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54213 -
****************************************************************
* USERS AFFECTED: All DB2 Users of START DATABASE(DSNDB06) *
* SPACE(*) Command. *
****************************************************************
* PROBLEM DESCRIPTION: Some catalog indexes and table spaces *
* remain in STOPPED state after START *
* DATABASE(DSNDB06) SPACE(*) command is *
* issued. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There is an internal structure where DB2 keeps a list of all
catalog objects. If DB2 is running in CM8 mode, some objects
in the list do not exist until they are created after running
the DSNTIJEN job as part of migration to NFM.
The START DATABASE(DSNDB06) SPACE(*) command uses this list
to process all the index and table spaces in the catalog when
it cannot access to the catalog (for example, after running
the STOP DATABASE(DSNDB06) SPACE(*) command).
When the START command is run in CM8 mode, it stopped
processing after the first non-existing object in the list.
DB2 code has been updated to correct the problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54213
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXKFUN PM54213
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54213 DSNXKFUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXKFUN
LISTEND
UK76996 COVER LETTER END
1
UK76997 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57219 -
****************************************************************
* USERS AFFECTED: DB2 users of stored procedures and *
* user defined functions (UDFs). *
****************************************************************
* PROBLEM DESCRIPTION: During stored procedure execution, *
* the following abend happened: *
* ABEND0C4 RC3B DSNX9GPL +14A6 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During stored procedure execution,
a pointer points to the storage which
didn't get set due to a storage
allocation failure.
Later, in the stored procedure recovery
DB2 tried to reference the pointer and
that resulted in the 0C4 abend.
DB2 code has been fixed to ensure the pointer is valid before
referencing it.
Additional keywords:
SQLSP
SQLSTOREDPROC
SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57219
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 PM57219
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57219 DSNX9GPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9GPL
LISTEND
UK76997 COVER LETTER END
UK76999 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57235 -
****************************************************************
1 * USERS AFFECTED: DB2 10 for z/OS users of stored procedures *
* and user defined functions(UDFs). *
****************************************************************
* PROBLEM DESCRIPTION: After an stored procedure abend and *
* RRS error, following abend occurred: *
* ABEND0C4 AT DSNX9WLS UK65416 +2E9E *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend was because a pointer passed to the ESTAE was
invalid since the compiler incorrectly optimized the
variable and therefore we lost the pointer.
DB2 code has been changed to force no optimization for variables
used in ESTAE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57235
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9WLS PM57235
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57235 DSNX9WLS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9WLS
LISTEND
UK76999 COVER LETTER END
UK77001 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55933 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR adds XML storage *
* serviceability trace. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR adds XML storage serviceability trace.
IFCID 367 is enabled to support XML storage serviceability
trace.
Additional keywords: IFCID367 XMLALL SQLXML
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55933
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
DSNDQWHS PM55933
DSNDQW05 PM55933
DSNWVINT PM55933
DSNXMLSM PM55933
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55933 DSNDQWHS DSNDQW05 DSNWVINT DSNXMLSM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVINT
DSNXMLSM
MACROS
DSNDQWHS
DSNDQW05
LISTEND
UK77001 COVER LETTER END
UK77003 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55479 -
****************************************************************
* USERS AFFECTED: DB2 9 and 10 for z/OS users of DECIMAL data *
* type. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000010 in DSNXOGBM OFFSET *
* BE2C may occur or an inefficient access *
* path may be chosen for a query with *
* a predicate on a DECIMAL column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 incorrectly handles the length of histogram statistics of
a DECIMAL column. This problem may result in either of the
following symptoms:
1. Inefficient access path may be chosen for a query with a
predicate on a DECIMAL column if histogram statistics
is collected on this DECIMAL column or multi-column histogram
statistics is collected on a COLGROUP including this DECIMAL
column.
2. An ABEND0C4 RC00000010 in DSNXOGBM OFFSET BE2C may occur if
the DECIMAL column is a leading key of an index and index
probing is used for the query.
Index probing is applicable for DB2 10 for z/OS only and may be
used under any of the following conditions:
* Zparm NPGTHRSH is set to a non-zero value.
* A query references a table defined as VOLATILE.
1 * DB2 determines that no rows will qualify based on
a predicate or index.
Additional Keywords:
ABEND0C4 RC00000010 in DSNXOGBM SQLACCESSPATH SQLPERFORMANCE
DECIMAL
Code has been modified to handle the length of histogram
statistics of a DECIMAL column correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55479
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
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 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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGBM PM55479
DSNXOGNC PM55479
DSNXOPRS PM55479
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55479 DSNXOGBM DSNXOGNC DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBM
DSNXOGNC
DSNXOPRS
1 LISTEND
UK77003 COVER LETTER END
UK77005 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54505 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of the *
* XMLEXISTS function. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND 04E RC00E70005 can occur at *
* location DSNXRRP:M700 when using the *
* XMLEXISTS function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 can occur at location DSNXRRP M700 when
using an XMLEXISTS predicate.
The abend occurs after an SQLCODE -952 is issued when processing
is interrupted by a client cancel request. The SQLCODE occurs
while processing the XMLEXISTS predicate. DB2 does not return
the SQLCODE correctly and subsequently abends.
The following query illustrates how this abend can occur while
negative SQLCODE occurs during processing the XMLEXISTS
predicate.
SELECT CUSTOMER_ID,CUS_XML
FROM TB
WHERE XMLEXISTS('/a/b c=xs:decimal(5) /d' passing CUS_XML)
AND XMLEXISTS('/a/b c=111 //d e=8 ' passing CUS_XML);
DB2 has been changed to return the SQLCODE correctly.
Additional Keywords : SQLXML XMLEXISTS SQLCODE952
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54505
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRRP PM54505
DSNXRRP9 PM54505
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54505 DSNXRRP DSNXRRP9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRRP
DSNXRRP9
LISTEND
1UK77005 COVER LETTER END
UK77007 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56814 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the MODIFY *
* RECOVERY utility. *
****************************************************************
* PROBLEM DESCRIPTION: MODIFY RECOVERY executed on a V10 NFM *
* data sharing system receives ABEND04E *
* RC00E40190 RC00C900BF (IRLM out of *
* storage condition). *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
The MODIFY RECOVERY utility executed on a V10 NFM data sharing
system receives ABEND04E 00E40190 00C900BF (IRLM out of storage
condition) when there are a very large number of
SYSIBM.SYSLGRNX records to delete.
In V10 NFM, locksize for SYSLGRNX has been changed from
page level locking to row level locking, so the number of total
locks requested by MODIFY RECOVERY can increase dramatically.
The MODIFY RECOVERY utility has been changed to commit more
aggressively during the deletion of SYSLGRNX records so that
the row level locks are released more frequently.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56814
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 PM56814
DSNUMDEL PM56814
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56814 DSNUBCOP DSNUMDEL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBCOP
DSNUMDEL
LISTEND
UK77007 COVER LETTER END
UK77031 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM47075 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of partitioning keys *
* or user-defined default values on timestamp *
1 * columns *
****************************************************************
* PROBLEM DESCRIPTION: DB2 10 for z/OS users of timestamp *
* column in partitioning key receive *
* ABEND04E at location DSNXICDM:P103 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
On DB2 10 for z/OS, if a user specifies X'FF' as a partitioning
key value for a timestamp column on a CREATE TABLE statement,
and the table encoding scheme is EBCDIC or ASCII, they will
incorrectly receive ABEND04E RC00E70005.
Users may also receive this abend when specifying X'FF' as a
default value for a timestamp column and table encoding scheme
is EBCDIC or ASCII.
For the cases where X'FF' is specified as a key for a timestamp
column in the last partition, SQLCODE678 will now be correctly
issued. Users may specify MAXVALUE instead if that is their
intention for the last partition.
SQlCODE574 will now be issued when X'FF' is specified as a
default value for a timestamp column.
Additional Keywords:
SQLCODE574
SQLCODE678
SQLCREATE
SQLALTER
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM47075
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICDM PM47075
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM47075 DSNXICDM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICDM
LISTEND
UK77031 COVER LETTER END
UK77038 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54034 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of *
* SQL inline table user defined *
* function and common table *
1 * expression. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect out may occur for an *
* SQL statement that satisfies the *
* following conditions: *
* 1. The SQL statement references to *
* an SQL inline table user defined *
* function multiple times with *
* different arguments. *
* 2. The SQL inline table user defined *
* function contains a common table *
* expression which references to *
* the parameter of the SQL inline *
* table user defined function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect out may occur for an SQL statement that satisfies
the following conditions:
1. The SQL statement references to an SQL inline table user
defined function multiple times with different arguments.
2. The SQL inline table user defined function contains a common
table expression which references to the parameter of the SQL
inline table user defined function.
For Example,
CREATE FUNCTION TUDF_CTE (P1 INT)
RETURNS TABLE (C1 INT)
LANGUAGE SQL
SPECIFIC MYTUDF2
NOT DETERMINISTIC
READS SQL DATA
RETURN
WITH CTE_T (C1) AS
( SELECT P1
FROM T1
UNION ALL
SELECT C1+1 FROM CTE_T WHERE C1 < 3
)
SELECT C1 FROM CTE_T;
SELECT * FROM TABLE (TUDF_CTE(2))TX,
TABLE (TUDF_CTE(3))TZ;
Incorrect output may occur for the SELECT statement above
because the common table expression inside the SQL inline table
user defined function is not handled correctly.
DB2 was fixed to handle the common table expression inside the
SQL inline table user defined function correctly.
Additional Key words: SQLINCORR SQLINCORROUT
INCORROUT DB2INCORR/K
SQLCTE SQLINLINE
SQLTABLEUDF
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54034
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM54955:
See PM54955 APAR/PTF text for additional information about
why a REBIND is necessary.
PM54955 corrects a problem of incorrect output for a query that
references a scalar fullselect in its predicate and runs in
parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM54034:
See PM54034 APAR/PTF text for additional information about
why a REBIND is necessary.
PM54034 corrects a problem of incorrect output for an
SQL statement that references to an SQL inline table
user defined function multiple times with different
arguments and the SQL inline table user defined function
contains a common table expression.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM30064:
See PM30064 APAR/PTF text for additional information about
why a REBIND is necessary.
PM30064 made an performance enhancement for a query satisfying
all of the following conditions:
1. The query contains host variables or parameter markers.
2. The query references a view or table expression which
contains UNION ALL and returns a LOB column.
To make this fix effective for a static application, it must 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:
After application of the PTF, the data length calculated of
CONCAT() function may be less than its previous DESCRIBE when
all of the following conditions are satisfied:
1
1. the type of one parameter of CONCAT() is GRAPHIC;
2. the other parameter of CONCAT() is scalar full-select, whose
type is also GRAPHIC.
Since there is no data in the extra length of CONCAT() prior to
applying this APAR, no problem would be caused after this APAR
is applied. If applications using DESCRIBE is impacted, proper
actions should be taken.
If the DSNTIAUL sample program is used correctly to generate a
LOAD utility control statement, then after application of this
PTF, the new control statement generated may not match the data
length of the CONCAT() function with scalar full-select from the
previous control statement. Proper action should be taken if
such mismatch is observed.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOACR PM54034
DSNXOB2 PM54034
DSNXODSO PM54034
DSNXOEXC PM54034
DSNXOFD PM54034
DSNXOIWS PM54034
DSNXOOS2 PM54034
DSNXOP0 PM54034
DSNXOVC PM54034
DSNXOVD PM54034
DSNXOV0 PM54034
DSNXOV1 PM54034
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54034 DSNXOACR DSNXOB2 DSNXODSO DSNXOEXC DSNXOFD DSNXOIWS
DSNXOOS2 DSNXOP0 DSNXOVC DSNXOVD DSNXOV0 DSNXOV1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOACR
DSNXOB2
DSNXODSO
DSNXOEXC
DSNXOFD
DSNXOIWS
DSNXOOS2
DSNXOP0
DSNXOVC
DSNXOVD
DSNXOV0
DSNXOV1
LISTEND
UK77038 COVER LETTER END
UK77041 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM55143 -
****************************************************************
* USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE *
* command. *
****************************************************************
* PROBLEM DESCRIPTION: The -DISPLAY DATABASE command could *
* generate ABEND04E RC00F9000C in *
* DSN9PREP.DSN9SCNP because of *
* ill-formed multi line message blocks. *
* Or a storage overlay, which could *
* result in one of the following: *
* ABENDS0C4 RC0000003B in DSNTXSTB *
* ABEND04E RC00E20008 in DSNSLD1 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The -DISPLAY DATABASE command could generate ABEND04E
RC00F9000C in DSN9PREP.DSN9SCNP because ill-formed multi line
message blocks could be created when errors occurred during the
actual issuing of a message but additional actions and messages
continued to be carried out.
The -DISPLAY DATABASE command was changed to always end the
processing and printing of messages when errors occurred during
the generation of any message.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55143
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 PM55143
DSNTDMUL PM55143
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55143 DSNTDMST DSNTDMUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDMST
DSNTDMUL
LISTEND
UK77041 COVER LETTER END
UK77085 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60044 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 does not terminate following *
* a -STOP DB2,MODE(FORCE) command. The *
1 * stop-work TCB is waiting for the ENQ *
* on the SSI path to become available, *
* but is held by a WLM SPAS address *
* space TCB. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During -STOP DB2,MODE(FORCE) processing, a TCB in a WLM
stored procedure address space was ABTERMed with an
S04E-00E50013 while going through normal end-of-task
processing. The ABTERM hit while the TCB was suspended on
a task switch to issue a DSNX905I message. ABEND recovery
in estae DSN3SSES did wait for the message request to
complete, but did not reset a deferred recovery flag.
DSN3SSES then issued a Term-thread request which suspended
for a purge-stack SRB to complete. Since the deferred
recovery flag was still on, the purge-stack SRB did not
resume the WLM SPAS TCB, which was holding a SHR ENQ on
the SSI resource SYSZDSN3.ERLYOLRH. This ENQ prevented
DB2 from shutting down.
DSN3SSES has been changed to reset the deferred recovery flag
after waiting for the message request to complete. This will
allow estae recovery and DB2 shutdown to complete.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60044
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3SSES PM60044
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60044 DSN3SSES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3SSES
LISTEND
UK77085 COVER LETTER END
UK77096 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51663 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG SHRLEVEL *
* REFERENCE with deferred ALTER materilization *
* on CDC catalog table objects. *
****************************************************************
* PROBLEM DESCRIPTION: Data Capture flag is not logged for *
* catalog table updates by REORG SHRLEVEL *
* REFERENCE with deferred ALTER *
* materialization. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
A REORG SHRLEVEL REFERENCE is run on a table space after it has
been altered to a partitioned-by-growth attribute. The REORG
modifies catalog tables which have DATA CAPTURE CHANGES defined,
but those log records generated for these updates have not been
logged as 'Data Capture'.
DB2 code has been fixed to log 'Data Capture' flag on catalog
update during the REORG materializing pending ALTER.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51663
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDILS PM51663
DSNILREP PM51663
DSNIQGSE PM51663
DSNIREPR PM51663
DSNISDLE PM51663
DSNISGRT PM51663
DSNISMRT PM51663
DSNUGPAM PM51663
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51663 DSNIDILS DSNILREP DSNIQGSE DSNIREPR DSNISDLE DSNISGRT
DSNISMRT DSNUGPAM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDILS
DSNILREP
DSNIQGSE
DSNIREPR
DSNISDLE
DSNISGRT
DSNISMRT
DSNUGPAM
LISTEND
UK77096 COVER LETTER END
UK77101 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56810 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the *
* XMLSERIALIZE function in a remote *
* application when Dynamic Data Format is *
* enabled to retrieve XML data. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at location *
1 * DSNOGETD:5065 (ERQUAL5065) can occur *
* when the XMLSERIALIZE function is used *
* from a remote application when Dynamic *
* Data Format is enabled to retrieve XML *
* data. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00C90101 at location DSNOGETD 5065 can occur when
the XMLSERIALIZE function is used from a remote application when
Dynamic Data Format is enabled to retrieve XML data.
The following Java example illustrates the problem.
1. Create a Table with an XML column.
CREATE TABLE T1(C1 INT, X1 XML);
2. Populate the Table on a remote server by inserting
two large XML files of different sizes into the
Table T1.
INSERT INTO T1 VALUES(1,?);
INSERT INTO T1 VALUES(2,?);
3. Create a remote application connected through the JDBC
driver, by default the Dynamic Data Format is enabled.
//select from remote table T1
String query = "SELECT C1,XMLSERIALIZE(X1 AS CLOB)
FROM T1 WHERE C1 IN ( 1,2 )";
PreparedStatement pstmt = con.prepareStatement(query);
ResultSet rs = pstmt.executeQuery();
while (rs.next()) {
System.out.println("C1:" + rs.getInt(1));
System.out.println("XML:" + rs.getString(2));
}
4. Execute the remote application.
When the remote application is executed, DB2 does not handle
the XMLSERIALIZE function properly which leads to the ABEND04E
failure mentioned above.
The code in DB2 has been modified to process the XMLSERIALIZE
function when Dynamic Data Format is ENABLED to prevent the
ABEND04E from occurring.
Additional Keywords: SQLLOB SQLXML SQLXMLSERIALIZE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56810
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
DSNOLMAT PM56810
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56810 DSNOLMAT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOLMAT
LISTEND
UK77101 COVER LETTER END
UK77102 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55070 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS NFM users of UTS table spaces*
* defined for row level locking that are *
* performing SQL UPDATE may see broken pages *
* during backout processing. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISMCP ERQUAL501E *
* ABEND04E RC00C90105 DSNIBHUN:0C2C *
* ABEND04E RC00C90105 DSNIBHUN ERQUAL0C2C *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 V10 New Function Mode, the page format for UTS table
spaces has changed to handle pseudo deleted rows. For data
pages with pseudo delete format, the space search logic
allowed an insert operation to proceed by invoking compaction
of holes on that page, even though the page was not committed.
This resulted in space that was freed up (by shortening of a
row during an UPDATE operation) getting reused even if that
agent had not completed commit processing. The abends occur
when the update agent encounters a failure, and now needs to
backout to the before image of the row. The larger row size
will no longer fit on the page.
DB2 code has been corrected to disallow page compaction in the
case where a page has not been fully committed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55070
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 PM55070
DSNISGRT PM55070
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PM55070 DSNIREPR DSNISGRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIREPR
DSNISGRT
LISTEND
UK77102 COVER LETTER END
UK77107 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54383 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 z/OS threads do not terminate *
* after being cancelled if the thread *
* is waiting for a reply from a remote *
* downstream location (via a TCP/IP *
* connection). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Under the following conditions, a DB2 for z/OS thread will
not terminate if it is cancelled while waiting for a (TCP/IP)
reply from a remote downstream location.
. An allied (requester) thread is explicitly cancelled via a
z/OS CANCEL command.
. An allied (requester) thread is explicitly cancelled via a
DB2 for z/OS CANCEL (DDF) THREAD command.
. A DBAT (server thread) is explicitly cancelled via a
DB2 for z/OS CANCEL (DDF) THREAD command.
. A DBAT (server thread) is implicitly cancelled via a
connection loss event relative to a remote upstream
location.
To allow the thread termination to complete, intervention is
currently required to terminate the TCP/IP connection to the
remote downstream location. This intervention procedure is
currently documented in the "Usage notes" section of the
DB2 for z/OS "CANCEL THREAD" command in the DB2 for z/OS
Command Reference manual. This procedure works but it can
be a difficult procedure to manage, especially if there
a many TCP/IP connections to consider.
Relative to the cancelled thread, DB2 cancel processing has been
changed to automatically terminate all downstream TCP/IP
connections that could potentially be waiting for a reply from
the remote downstream location. This allows the cancel
operation to be fully honored.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54383
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
DSNLCNCL PM54383
DSNLCTCA PM54383
DSNLILLM PM54383
DSNLILOS PM54383
DSNLIRQP PM54383
DSNLVLOS PM54383
DSNVCT PM54383
DSNVDISC PM54383
HDBAA10J PM54383
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54383 DSNLCNCL DSNLCTCA DSNLILLM DSNLILOS DSNLIRQP DSNLVLOS
DSNVCT DSNVDISC HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCNCL
DSNLCTCA
DSNLILLM
DSNLILOS
DSNLIRQP
DSNLVLOS
DSNVCT
DSNVDISC
LISTEND
UK77107 COVER LETTER END
UK77111 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58831 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS Command Line *
* Processor (CLP). *
****************************************************************
* PROBLEM DESCRIPTION: DB2 for z/OS Command Line Processor *
* does not return the DSNC101I command *
* completed successfully message *
* for SQL statements which succeed with *
* a SQLCODE > 0. *
****************************************************************
* RECOMMENDATION: Apply PTF *
****************************************************************
DB2 for z/OS Command Line Processor does not return the
DSNC101I command completed successfully message for SQL
SQL statements which succeed with SQLCODE > 0.
Instead, CLP returns the SQLERRMC message tokens, SQLCODE
and SQLSTATE from the SQLCA.
DB2 for z/OS Command Line Processor has been corrected to
return the DSNC101I command completed successfully message
for SQL statements which succeed with a SQLCODE > 0.
1 For statements which receive SQLCODE +217 while running
under special register EXPLAIN MODE=EXPLAIN, CLP returns
the SQLERRMC message tokens, SQLCODE, and SQLSTATE from
the SQLCA.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58831
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNCLP PM58831
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58831 DSNCLP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNCLP
LISTEND
UK77111 COVER LETTER END
UK77113 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57727 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN *
* and DSNTIJNF jobs to migrate to new function *
* mode (NFM). *
****************************************************************
* PROBLEM DESCRIPTION: During the DB2 10 for z/OS ENFM *
* process, a compressed SPT01 directory *
* table space will lose it's compression *
* dictionary. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
When running the DSNTIJEN and DSNTIJNF jobs to migrate to
new-function mode, a compressed SPT01 directory table space
will lose its compression dictionary. This happens when the
compression dictionary is not copied to the shadow data set
during ENFM REORG processing.
Code has been modified so that the SPT01 compression dictionary
is saved during the DB2 10 for z/OS ENFM process. This is only
necessary when SPT01 is using compression.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57727
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUECM0 PM57727
1 DSNURPDC PM57727
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57727 DSNUECM0 DSNURPDC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUECM0
DSNURPDC
LISTEND
UK77113 COVER LETTER END
UK77157 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56841 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E50079 in CSECT *
* DSNVSRX may occur due to concurrent *
* cancel processing. DB2 may subsequently *
* terminate with a RC00E50054. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The suspend ROB is marked for cancel in the suspended agent
but not cleared by cancel processing. A resuming agent may
free the cancelled ROB prior to the suspended agent being
dispatched. If another cancel is issued against the suspended
agent, it will fail accessing the freed suspend ROB that
remains in the suspended agent.
DB2 cancel logic has been changed to clear the suspend ROB in
the suspended agent. This prevents future cancels from
potentially accessing a freed ROB and abending with an ABEND04E
RC00E50079.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56841
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVSRX PM56841
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56841 DSNVSRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVSRX
LISTEND
1UK77157 COVER LETTER END
UK77170 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM40724 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the following *
* built-in functions: *
* *
* 1. LTRIM *
* 2. RTRIM *
* 3. REPLACE *
* 4. ROUND *
* 5. STRIP *
* 6. TRIM *
* 7. TRUNCATE or TRUNC *
****************************************************************
* PROBLEM DESCRIPTION: The following built-in functions are *
* being extended with this apar to accept *
* optional parameters. *
* *
* 1. LTRIM *
* 2. RTRIM *
* 3. REPLACE *
* 4. ROUND *
* 5. TRUNCATE or TRUNC *
* *
* Also, the TRIM function is being *
* introduced and documentation changes *
* are needed for the STRIP function as a *
* result of adding the new TRIM function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. The following built-in functions are being extended to accept
optional parameters in DB2 NFM (New Function Mode).
LTRIM and RTRIM
Extend the functions to accept a second (optional)
parameter (trim-characters).
REPLACE
Extend the function to make the third parameter
(replace-string) optional. If replace-string is not
specified, the default is an empty string, and nothing
replaces the string that is removed from the source string.
ROUND
Extend the function to make the second parameter
(numeric-expression-1) optional and in the syntax diagram
1 show zero above the line as the default.
TRUNCATE or TRUNC
Extend the function to make the second parameter
(numeric-expression-1) optional and in the syntax diagram
show zero above the line as the default.
2. Introduce a new built-in function, TRIM, which is very
similar to the STRIP function which has been supported by
DB2 for z/OS for several releases. A sourced function
cannot be defined on the TRIM function.
3. Documentation changes are needed for the STRIP built-in
function as a result of adding the new TRIM function. The
details will be described under the TRIM function and the
STRIP function will point to the description for the TRIM
function.
4. Correct the execution for an SQL statement that invokes
the STRIP built-in function using a single multi-byte
mixed data strip-character. Previously an SQLCODE -171 was
returned for this kind of query.
This apar is the enabling APAR for APAR PM38326, the pre-
conditioning apar. Together, these two apars are extending the
following built-in functions to accept optional parameters in
DB2 NFM (New Function Mode).
1. LTRIM
2. RTRIM
3. REPLACE
4. ROUND
5. TRUNCATE or TRUNC
Also, the TRIM function is being introduced.
Please note. As a result of this apar, please note that
documentation changes are being made to the "DB2 10 for z/OS SQL
Reference" as well to further describe the use of these
functions. Please reference the included ++HOLD, or the
recently updated publication for details and specifics.
ADDITIONAL KEYWORDS: SQLLTRIM SQLRTRIM SQLREPLACE SQLROUND
SQLSTRIP SQLTRIM SQLTRUNCATE SQLCODE171
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM40724
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PM40724 APAR/PTF text for additional information about why
a REBIND is necessary. APAR PM38326 is the necessary
1 pre-conditioning apar for this APAR.
PM40724 corrects the problem of an SQLCODE -171 issued for a
query that references the STRIP built-in function containing
a single multi-byte mixed data strip-character.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
MULTSYS:
PM40724 is an APAR that includes changes to support functional
extensions to the existing built-in functions and to introduce
a new built-in function that will be enabled once this APAR is
applied in DB2 NFM (New Function Mode).
Earlier, pre-conditioning APAR PM38326 was delivered.
In a data sharing group, the pre-conditioning APAR should be
applied to all members before applying this enabling APAR to any
member. The code change is enabled once this enabling APAR is
applied.
The functional extensions to the following existing built-in
functions are enabled by APAR PM40724.
1. LTRIM
2. RTRIM
3. REPLACE
4. ROUND
5. STRIP
6. TRUNCATE
The new built-in function called, TRIM, is introduced by APAR
PM40724. This APAR also corrects the problem of an SQLCODE
-171 issued for a query that references the STRIP built-in
function containing a single multi-byte mixed data
strip-character.
DOCUMENTATION:
See PM40724 APAR/PTF text for additional information.
PM40724 introduces the following changes to externals:
LTRIM
The LTRIM function removes bytes from the beginning of a string
expression based on the content of a trim expression.
>>--LTRIM--(--string-expression---+--------------------+-)-><
'-,--trim-expression-'
The LTRIM function removes all of the characters that are
contained in trim-expression from the beginning of
string-expression. The search is done by comparing the binary
representation of each character (which consists of one or more
1 bytes) in trim-expression to the bytes at the beginning of
string-expression. If the string-expression is defined as
FOR BIT DATA, the search is done by comparing each byte in
trim-expression to the byte at the beginning of
string-expression.
string-expression
An expression that specifies the source string. The argument
must be an expression that returns a value that is a built-in
string data type that is not a LOB, or a numeric data type. If
the value is not a string data type, it is implicitly cast
to VARCHAR before the function is evaluated.
If string-expression is not FOR BIT DATA, trim-expression must
not be FOR BIT DATA.
trim-expression
An expression that specifies the characters to remove from the
beginning of string-expression. The expression must return a
value that is a built-in string data type that is not a LOB, or
a numeric data type. If the value is not a string data type,
it is implicitly cast to VARCHAR before the function is
evaluated.
The default for trim-expression depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
a blank. If not EBCDIC, X'20' represents a blank.
string-expression and trim-expression must have compatible data
types. If string-expression and trim-expression have different
CCSID sets, trim-expression is converted to the CCSID of
string-expression.
The result of the function depends on the data type of
string-expression.
VARCHAR if string-expression is a character string. If
string-expression is defined as FOR BIT DATA the result
is FOR BIT DATA.
VARGRAPHIC if string-expression is a graphic string.
1
VARBINARY if string-expression is a binary string.
The length attribute of the result is the same as the length
attribute of string-expression.
The actual length of the result for a character or binary string
is the length of string-expression minus the number of bytes
that are removed. The actual length of the result for a graphic
string is the length (in the number of double byte characters)
of string-expression minus the number of double byte characters
removed. If all of the characters are removed, the result is an
empty string (the length is zero).
If any argument can be null, the result can be null; if any
argument is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Refer to LTRIM section in the DB2 10 for z/OS SQL Reference
for more information.
RTRIM
The RTRIM function removes bytes from the end of a string
expression based on the content of a trim expression.
>>--RTRIM--(--string-expression---+--------------------+-)-><
'-,--trim-expression-'
The RTRIM function removes all of the characters contained in
trim-expression from the end of string-expression.
The search is done by comparing the binary representation of
each character (which consists of one or more bytes) in
trim-expression to the bytes at the end of
string-expression. If the string-expression is defined as
FOR BIT DATA, the search is done by comparing each byte in
trim-expression to the byte at the end of string-expression.
string-expression
An expression that specifies the source string. The argument
must be an expression that returns a value that is a built-in
string data type that is not a LOB, or a numeric data type. If
the value is not a string data type, it is implicitly cast
to VARCHAR before the function is evaluated.
If string-expression is not FOR BIT DATA, trim-expression must
not be FOR BIT DATA.
trim-expression
An expression that specifies the characters to remove from the
end of string-expression. The expression must return a
1 value that is a built-in string data type that is not a LOB, or
a numeric data type. If the value is not a string data type,
it is implicitly cast to VARCHAR before the function is
evaluated.
The default for trim-expression depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
a blank. When not EBCDIC, X'20' represents a blank.
string-expression and trim-expression must have compatible data
types. If string-expression and trim-expression have different
CCSID sets, trim-expression is converted to the CCSID of
string-expression.
The result of the function depends on the data type of
string-expression.
VARCHAR if string-expression is a character string. If
string-expression is defined as FOR BIT DATA the result
is FOR BIT DATA.
VARGRAPHIC if string-expression is a graphic string.
VARBINARY if string-expression is a binary string.
The length attribute of the result is the same as the length
attribute of string-expression.
The actual length of the result for a character or binary string
is the length of string-expression minus the number of bytes
removed. The actual length of the result for a graphic
string is the length (in number of double byte characters) of
string-expression minus the number of double byte characters
removed. If all of the characters are removed, the result is an
empty string (the length is zero).
If any argument can be null, the result can be null; if any
argument is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Refer to RTRIM section in the DB2 10 for z/OS SQL Reference
1 for more information.
REPLACE
>>-REPLACE-(-source-string-,-search-string-+-----------------+->
',-replace-string-'
>-)-><
replace-string
An expression that specifies the replacement string. The
expression must return a value that is a built-in character
string, graphic string, or binary string data type that is not
a LOB.
The argument can also be a numeric data type. The numeric
argument is implicitly cast to a VARCHAR data type.
If replace-string is not specified or is an empty string,
nothing replaces the string that is removed from the source
string.
Refer to REPLACE section in the DB2 10 for z/OS SQL Reference
for more information.
ROUND
.-,--0-------------------.
>>-ROUND-(--numeric-expression-1-+------------------------+-)-><
'-,-numeric-expression-2-'
Refer to ROUND section in the DB2 10 for z/OS SQL Reference
for more information.
TRUNCATE or TRUNC
.-,--0------------------.
>>-+TRUNCATE-+-(-numeric-expression1-+-----------------------+->
'-TRUNC---' '-,-numeric-expression2-'
>-)-><
Refer to TRUNCATE section in the DB2 10 for z/OS SQL Reference
for more information.
STRIP
The STRIP function is similar to the TRIM scalar function.
Refer to TRIM section in the DB2 10 for z/OS SQL Reference
for more information.
1 TRIM
The TRIM function removes bytes from the beginning, from the
end, or from both the beginning and end of a string expression.
>>--TRIM--(--+----------------------------------------+-->
| .-BOTH-----. |
'-+----------+--+----------------+--FROM-'
|-B--------| '-trim-constant--'
|-LEADING--|
|-L--------|
|-TRAILING-|
'-T--------'
>--string-expression---)--------------------------------><
The schema is SYSIBM.
The first argument, if specified, indicates whether characters
are removed from the end or the beginning of the string. If the
first argument is not specified, the characters are removed from
both the end and the beginning of the string.
trim-constant
Specifies a constant that indicates the binary, SBCS, or DBCS
character that is to be removed. If string-expression is a
character string, trim-constant must be an SBCS or DBCS
single-character (2 bytes) constant. If string-expression is a
binary string, trim-constant must be a single-byte binary string
constant. If string-expression is a DBCS graphic or DBCS-only
string, trim-constant must be a graphic constant that consists
of a single DBCS character.
The default for trim-constant depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
a blank. When not EBCDIC, X'20' represents a blank.
string-expression
An expression that returns a value that is a built-in character
1 string data type, graphic data type, binary string data type, or
numeric data type. string-expression must not be a LOB.
If string-expression is numeric, it is cast to a character
string before the function is evaluated. For more information
about converting numeric to a character string, see VARCHAR.
string-expression and trim-expression must have compatible data
types.
The data type of the result depends on the data type of
string-expression:
If string-expression is a character string data type, the
result is VARCHAR. If string-expression is defined as
FOR BIT DATA the result is FOR BIT DATA.
If string-expression is a graphic string data type, the
result is VARGRAPHIC.
If string-expression is a binary string data type, the
result is VARBINARY.
The length attribute of the result is the same as the length
attribute string-expression. The actual length of the result is
the length of string-expression minus the number of characters
removed. If all of the characters are removed, the result is
an empty string.
If string-expression can be null, the result can be null; if
string-expression is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Example: Assume the host variable HELLO of type CHAR(9) has a
value of 'Hello '.
SELECT TRIM(:HELLO), TRIM(TRAILING FROM :HELLO)
FROM SYSIBM.SYSDUMMY1
Results in 'Hello' and ' Hello' respectively.
Example: Assume the host variable BALANCE of type CHAR(9) has a
value of '000345.50'.
SELECT TRIM(L '0' FROM :BALANCE)
FROM SYSIBM.SYSDUMMY1
Results in '345.50'
Refer to TRIM section in the DB2 10 for z/OS SQL Reference.
ACTION:
This PTF corrects the problem of an SQLCODE -171 issued for a
query that references the STRIP built-in function containing a
single multi-byte mixed data strip-character.
If after applying both apars PM38326 and PM40724, the failing
1 query still returns an SQLCODE -171 or for a static query a
rebind does not resolve the problem, one or more of the
following actions may need to be performed depending on the
makeup of the query.
1. Views.
Regenerate views using the ALTER VIEW REGENERATE statement.
2. Materialized query tables (MQT).
Drop and recreate the MQTs.
3. SQL table UDFs.
Drop and recreate the UDFs.
4. SQL scalar UDFs.
Regenerate functions using the ALTER FUNCTION REGENERATE.
statement.
5. SQL native procedures.
Regenerate procedures using the ALTER PROCEDURE REGENERATE
statement.
6. Row permissions and column masks.
Regenerate using the ALTER PERMISSION REGENERATE or
ALTER MASK REGENERATE statement.
7. Indexes with key expressions.
Regenerate indexes using the ALTER INDEX REGENERATE
statement.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHSMF2 PM40724
DSNXGSFN PM40724
DSNXOBFA PM40724
DSNXOBFF PM40724
DSNXOBF3 PM40724
DSNXOBF4 PM40724
DSNXODTR PM40724
DSNXOFN2 PM40724
DSNXOW2D PM40724
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM40724 DSNHSMF2 DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3 DSNXOBF4
DSNXODTR DSNXOFN2 DSNXOW2D
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHSMF2
1 DSNXGSFN
DSNXOBFA
DSNXOBFF
DSNXOBF3
DSNXOBF4
DSNXODTR
DSNXOFN2
DSNXOW2D
LISTEND
UK77170 COVER LETTER END
UK77195 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51830 -
****************************************************************
* USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS *
* USERS OF TEMPLATE UTILITY WITH PCTPRIME *
* SPECIFIED AND PM34577 APPLIED. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDD37 WHEN USING TEMPLATE WITH *
* PCTPRIME TO DEFINE AN OUTPUT *
* DATA SET WHICH IS VERY SMALL *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User defined a TEMPLATE and ran a DB2 utility which
estimated the primary allocation size to be very small.
The user's specification of PCTPRIME further reduced
this estimate to a rounded value of zero. Normally,
when this situation is detected a nonzero value is
passed as the secondary quantity to prevent the
allocation from failing.
PTFs UK68767 (V9) and UK68768 (V10) for APAR PM34577
fixed a problem in which allocations could fail
because there was not enough space available to honor
the request. It did so by capping the size of the
secondary allocation to be no larger than the primary
allocation if the user used PCTPRIME or MAXPRIME to
limit the size of the primary allocation.
In this case, the use of PCTPRIME resulted in a
primary allocation size of zero. The code in PM34577
then reduced the secondary allocation to match,
making them both zero, which led to the job abending
with ABENDD37.
TEMPLATE utility code added by PM34577 was modified to not
reduce the size of the secondary allocation request if the
primary size to be requested is zero.
PM52891 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and all DB2 10 for z/OS *
* users of utilities. *
****************************************************************
* PROBLEM DESCRIPTION: DSNU1015I ERROR ALLOCATING DATA SET *
* CODE=X'02380000' The return code *
1 * indicates there is no space left in *
* the TIOT (task input output table). *
* MESSAGE IKJ56220I MAXIMUM NUMBER OF *
* DATA SET ALLOCATIONS ALLOWED BY YOUR *
* SESSION, may also be issued. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
MSGDSNU1015I ERROR ALLOCATING DATA SET dsname RC0238 was
issued during the LOAD of a table. It is also possible
that MSGIKJ56220I MAXIMUM NUMBER OF DATA SET ALLOCATIONS
HAS BEEN REACHED, YOU SHOULD FREE UNUSED DATA SETS can
be issued. This problem happened because DB2 does not use
an XTIOT.
DB2 utilities were changed to allow the use of a XTIOT. DB2
utilities will use a XTIOT, which resides above the 16M
line, instead of a TIOT if NON_VSAM_XTIOT=YES is specified
in the DEVSUPxx member of SYS1.PARMLIB and is used by the
IPL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51830,PM52891
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBCDA PM52891
DSNUBCKB PM52891
DSNUGDYN PM51830 PM52891
DSNUGSDA PM52891
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51830 DSNUGDYN
PM52891 DSNUBCDA DSNUBCKB DSNUGDYN DSNUGSDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBCDA
DSNUBCKB
DSNUGDYN
DSNUGSDA
LISTEND
UK77195 COVER LETTER END
UK77197 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58812 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of queries which are candidates for multiple *
* index access selection. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E rc00C90301 can occur at *
1 * location DSNXGRDS.DSNXRRID +0B92 (for *
* v9) because the requested RIDMAP can *
* not be found in the specified CUB. *
* *
* This problem is more likely to occur *
* for queries which are candidates for *
* multiple index access selection. These *
* include queries that involve the *
* sorting, intersection (ANDing), or *
* union (ORing) of RIDs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E rc00C90301 can occur at location DSNXGRDS.DSNXRRID
offset +0B92 (offset0B92) for v9 because the requested RIDMAP
can not be found in the specified CUB.
This problem is more likely to occur for queries which are
candidates for multiple index access selection when the sorting,
intersection, or union of RIDs encounters some problem with the
final output RIDMAP and needs to free it.
Some variables which are associated with the RIDMAP need to be
reset to insure that residual RIDMAP information is not
referenced unnecessarily.
DB2 has been modified to clean up residual information when a
RIDMAP is freed during sort processing. This will insure that
any variables associated with the RIDMAP are reset so that
residual RIDMAP information is not referenced unnecessarily.
Additional Keywords: SQLSORT SQLAND SQLOR SQLINTERSECT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58812
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSFIN PM58812
DSNXSFML PM58812
DSNXSFPR PM58812
DSNXSFRT PM58812
DSNXSFUN PM58812
DSNXSMIN PM58812
DSNXSMRL PM58812
DSNXSPRM PM58812
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58812 DSNXSFIN DSNXSFML DSNXSFPR DSNXSFRT DSNXSFUN DSNXSMIN
DSNXSMRL DSNXSPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSFIN
1 DSNXSFML
DSNXSFPR
DSNXSFRT
DSNXSFUN
DSNXSMIN
DSNXSMRL
DSNXSPRM
LISTEND
UK77197 COVER LETTER END
UK77206 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54179 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who use *
* system-level backups (SLB) on tape for *
* object level recovery. *
****************************************************************
* PROBLEM DESCRIPTION: The RECOVER utility with the *
* TOLOGPOINT and FROMDUMP options *
* specified fails with msgDSNU1522I and *
* RC8 if the object has been REORG'ed *
* since the SLB was created. *
* .. *
* The RECOVER utility with the DSNUM n *
* option specified on a non partitioned *
* object may restore all pieces instead *
* of just one piece if a SLB on tape *
* is used as the recovery base. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. The RECOVER utility with the TOLOGPOINT and FROMDUMP options
specified fails with msgDSNU1522I and RC8 if the object has
been REORG'ed since the SLB was created. This problem can occur
for point in time recoveries when the SLB has been dumped to
tape.
The RECOVER job output shows:
DSNU1522I THE DFSMSHSM CALL TO RESTORE obj-type db.obj-name
FAILED WITH RC = X'00000042' AND REASON CODE = X'00000012'
SEE THE JOB LOG FOR DFSMSHSM MESSAGES INDICATING THE CAUSE
OF THE ERROR
..
The DFSMShsm system log shows:
ARC1801I FAST REPLICATION DATA SET RECOVERY IS
ARC1801I (CONT.) STARTING FOR DATA SET
ARC1801I (CONT.) data-set-name,
ARC1812I OPERATION=SCAN FOR CATALOG INFORMATION DATA
ARC1812I (CONT.) SET=icf-catalog-name FOR COPY
ARC1812I (CONT.) POOL=db-copypool HAS COMPLETED WITH RETURN
ARC1812I (CONT.) CODE=0004 AND REASON CODE=0000
ARC1860I THE FOLLOWING 0001 DATA SET(S) FAILED DURING
ARC1860I (CONT.) FAST REPLICATION DATA SET RECOVERY:
ARC1860I (CONT.) data-set-name,
1 COPYPOOL=db-copypool
ARC1866, RC=1
ARC1802I FAST REPLICATION DATA SET RECOVERY HAS
ARC1802I (CONT.) COMPLETED FOR DATA SET
ARC1802I (CONT.) data-set-name,
ARC1802I (CONT.) ON date, FUNCTION RC=0008,
MAXIMUM DATA SET
ARC1802I (CONT.) RC=0066
..
The DFSMShsm messages indicate that the RECOVER utility
passed a data set name with the wrong IPREFIX. This problem
can occur if a REORG had been executed on the object after
the SLB was created.
..
2. The RECOVER utility with the DSNUM n option specified
for a non partitioned object may restore all pieces instead
of just one piece if the SLB used as the recovery base has
been dumped to tape.
..
Additional keywords: RC08 RC42 RC12 msgARC1801I
msgARC1812I msgARC1860I msgARC1802I PIT
The RECOVER utility has been corrected to pass the data set
name to DFSMShsm with a correct IPREFIX during point in time
recovery when using an SLB as a recovery base.
..
The RECOVER utility has been corrected to honor the DSNUM
option specification when recovering non partitioned objects
from a SLB on tape.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54179
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCBRT PM54179
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54179 DSNUCBRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBRT
LISTEND
UK77206 COVER LETTER END
UK77229 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56537 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V9 and V10 users using *
* indexes. *
****************************************************************
1 * PROBLEM DESCRIPTION: Serviceability enhancement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Serviceability enhancement.
Serviceability enhancement.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56537
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 PM56537
DSNDSPRM PM56537
DSNKDLE PM56537
DSN6SPRC PM56537
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56537 DSNDQWPZ DSNDSPRM DSNKDLE DSN6SPRC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKDLE
MACROS
DSNDQWPZ
DSNDSPRM
DSN6SPRC
LISTEND
UK77229 COVER LETTER END
UK77248 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56084 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the JCC Type 2 *
* Driver (JCCT2ZOS) Limited Block Fetch. *
****************************************************************
* PROBLEM DESCRIPTION: This apar addresses the following four *
* issues for DB2 V10 z/OS users connected *
* from the JCC Type 2 Driver when using *
* Limited Block Fetch. *
* *
* 1. DB2 incorrectly issues an SQLCODE423 *
* for a LOB Locator when a null LOB *
* value is previously fetched. *
* *
* 2. Incorrect output happens when a not *
* NULL XML column is fetched. *
* *
* 3. DB2 incorrectly issues an SQLCODE303 *
* when the XML (binary XML) and LOB *
1 * data types are fetched. *
* *
* 4. DB2 incorrectly returns *
* non-progressiveStreaming for a LOB *
* data type when a *
* progressiveStreaming format is *
* requested using a static SQLJ *
* statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This apar addresses the following four issues for DB2 V10 z/OS
users connected from the JCC Type 2 Driver (JCCT2ZOS) when using
Limited Block Fetch.
1. DB2 incorrectly issues an SQLCODE423 for a LOB Locator
when a NULL LOB value is previously fetched.
This problem occurs when both progressiveStreaming and
FullyMaterializeLobData are disabled for the JCC Type 2
Driver, and a NULL LOB value is previously fetched.
When the first not NULL LOB value is retrieved and
used through a LOB Locator, DB2 incorrectly issues an
SQLCODE423 because it does not handle the LOB value
and LOB Locator value properly..
2. Incorrect output happens when a not NULL XML column is
fetched.
DB2 does not set the nullability information properly
at bind time. This leads to an incorrect value written
for the NULL byte when retrieving a not NULL XML column
via Limited Block Fetch for the JCC Type 2 Driver.
3. DB2 incorrectly issues an SQLCODE303 when an XML (binary
XML) and LOB data type are fetched.
DB2 does not handle the data type conversion properly
when both XML (binary XML) and LOB data are fetched with
progressiveStreaming ON and FullyMaterialzeLobData OFF in
the JCC Type 2 Driver Release 4 (JCCV4).
4. DB2 incorrectly returns non-progressiveStreaming for a LOB
data type when a progressiveStreaming format is requested
for a static SQLJ statement.
A static SQLJ statement is used to fetch a LOB data type
and non-progressiveStreaming is requested for LOB Locator
format from a JCC Type 2 connection with Limited Block
Fetch. The connection is reset using
sqlj.runtime.ConnectionContext.KEEP_CONNECTION. If the
same SQLJ statement is executed again, this time
progressiveStreaming is requested for LOB data format if
there is no COMMIT statement between these two SQLJ
statements but DB2 returns the incorrect
non-progressiveStreaming format.
1 The code in DB2 has been modified to correct the four problems
mentioned.
Additional Keywords: JCCT2ZOS SQLCODE303 SQLCODE423 SQLLOB
SQLXML SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56084
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM56084:
See PM56084 APAR/PTF text for additional information about
why a REBIND is necessary.
Please note that the second problem addressed by PM56084 is
required to have the static application rebound.
Incorrect output can occur when a not NULL XML column is
fetched.
DB2 does not set the nullability information properly
at bind time which leads to an incorrect value written
for the NULL byte when retrieving a not NULL XML column
for the JCC Type 2 Driver with Limited Block Fetch.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM38688:
See PM38688 APAR/PTF text for additional information about
why a REBIND is necessary.
PM38688 corrects a problem of incorrect out when query contains
EXCEPT and UNION
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGOU2 PM56084
DSNXGRTM PM56084
DSNXROH2 PM56084
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56084 DSNXGOU2 DSNXGRTM DSNXROH2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNXGOU2
DSNXGRTM
DSNXROH2
LISTEND
UK77248 COVER LETTER END
UK77249 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57594 -
****************************************************************
* USERS AFFECTED: For all DB2 for z/OS users who use star *
* join. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output (more rows are *
* returned) can happen when: *
* 1. Star join access is chosen *
* (JOIN_TYPE = 'S' in PLAN_TABLE *
* output), AND *
* 2. The index used on the fact table *
* is unique, AND *
* 3. The join columns from the dimension *
* table have duplicates. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output (more rows are returned) can occur on a star
join query. The problem happens when star join access
(JOIN_TYPE = 'S' in PLAN_TABLE output) is used, the fact
table index is unique, and the dimension table has duplicate
rows. When going through the rows in the dimension table,
some of the rows are evalulated more than once.
Additional Keywords:
SQLSTARJOIN SQLINCORR INCORROUT STARJOIN DB2INCORR/K
The logic to handle dimension table duplicates has been fixed
to resolve the incorrect output problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57594
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISJNN PM57594
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57594 DSNISJNN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISJNN
1 LISTEND
UK77249 COVER LETTER END
UK77338 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58429 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 terminated with ABND04E RC00C200D8 *
* in DSNB1SWS due to bad vertical *
* deferred write queue (VDWQ). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a page set changes its p-lock from X to SIX, its dirty
pages are written to the group buffer pool (GBP). If a
synchronous DASD write happens simultaneously, the DASD write
may remove a buffer from the VDWQ even though the buffer is
already removed by the GBP write. This may cause bad VDWQ.
When detecting it, DB2 terminates.
The DASD write logic has been modified to not remove a buffer
from VDWQ if the buffer is not in VDWQ.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58429
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5COM PM58429
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58429 DSNB5COM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5COM
LISTEND
UK77338 COVER LETTER END
UK77339 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57506 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Entire page sets in LPL when STOP DB2 *
* with CASTOUT YES after restarting DB2 *
* LIGHT with indoubt jobs *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
Restart LIGHT normally ends with automatic DB2 shutdown
without castout. When jobs are indoubt, DB2 is not shut
down. If users issue STOP DB2 with CASTOUT YES, the castout
procedure may work on page sets not physically opened and
cause entire page sets to be put into LPL.
DB2 code has been changed to reinforce CASTOUT NO for
RESTART LIGHT.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57506
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CPL PM57506
DSNB1CPS PM57506
DSNB1PMT PM57506
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57506 DSNB1CPL DSNB1CPS DSNB1PMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPL
DSNB1CPS
DSNB1PMT
LISTEND
UK77339 COVER LETTER END
UK77366 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58087 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: A DSNL044I message may be erroneously *
* issued with invalid values, such as *
* return code and reason code, when a *
* -STOP DDF MODE(SUSPEND) or a subsequent *
* -START DDF command is issued. *
* Example: *
* DSNL044I DSNLSSRS MVS IWMSRDRS *
* LOCATION= MACRO FAILED *
* WITH RETCODE='00383EE5'X AND *
* RSNCODE='C6C5C240'X *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During -STOP DDF MODE(SUSPEND) and subsequent -START DDF
processing, DDF invokes z/OS WLM to deregister or register the
location aliases and utilizes separate variables to record the
outcome for each alias. However, DDF only declares variables
1 for the static aliases and hence the values for dynamic aliases
contain residual data. After invoking z/OS WLM for each defined
alias, DDF checks for bad return codes and issues a DSNL044I
message to indicate any failures. If a dynamic alias was never
specified, and hence z/OS WLM was not invoked, the corresponding
return code will contain residual data. If this residual data
appears to be a valid z/OS WLM return code, DDF erroneously
issues the DSNL044I message.
DB2 processing has been changed to declare and initialize
variables for z/OS WLM return codes for both static and
dynamic location aliases.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58087
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLILNR PM58087
DSNLSSRS PM58087
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58087 DSNLILNR DSNLSSRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLILNR
DSNLSSRS
LISTEND
UK77366 COVER LETTER END
UK77367 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56977 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users with table spaces or *
* indexes defined as GBPCACHE ALL. *
****************************************************************
* PROBLEM DESCRIPTION: Lost updates in data sharing for *
* GBPCACHE ALL objects. *
* *
* Corrupted data can result in any of *
* the following symptoms: *
* - 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. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
For GBPCACHE ALL objects, when a page is read from DASD it is
immediately written out as a clean page to the GBP. There
is a possibility that between the DASD read and the GBP write,
the same page was modified by another member, written to the
GBP as a changed page, and then cast out to DASD. In this case
the write of the clean page (which is now down-level) will be
successful and a subsequent update using that copy of the page
as a base will regress the prior update.
The clean page write logic has been modified to include a
version comparison, so that if the page being written is older
than the version reflected in the GBP directory entry, the write
will fail. The write will also be blocked if no GBP directory
entry exists.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56977
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 PM56977
DSNB5WCS PM56977
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56977 DSNB5SC2 DSNB5WCS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5SC2
DSNB5WCS
LISTEND
UK77367 COVER LETTER END
UK77376 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59818 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS or DB2 10 for z/OS *
* users of UNLOAD FORMAT INTERNAL *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E2002F DSNSVSFM OFFSET0794 *
* during an UNLOAD FORMAT INTERNAL *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An UNLOAD FORMAT INTERNAL utility abended with an ABEND04E
RC00E2002F DSNSVSFM +x'0794'. The abend was due to an
overlay of storage because UNLOAD did not take into account
the length of the record prefix.
UNLOAD code has been modified to add in the record header when
computing the length of the row.
1 DB2OVRLAY/K DB2OVRLAY/M
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59818
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULIA PM59818
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59818 DSNUULIA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULIA
LISTEND
UK77376 COVER LETTER END
UK77380 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55252 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users *
* *
****************************************************************
* PROBLEM DESCRIPTION: 1.MSGDSNX232E RC00C20269 *
* TYPE 00000201 *
* RESOURCE DSNDB01.DSNDB01X *
* received during start of DB2 *
* in SYSPITR mode *
* *
* 2.MSGDSNW108I received during *
* start of DB2 with ACCESS(MAINT) *
* option, when audit policies are *
* defined to be started at start up *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1.When DB2 is started in SYSPITR mode, message like the
following is received:
DSNX232E RC00C20269 TYPE 00000201 RESOURCE DSNDB01.DSNDB01X
This is because DB2 tried to access the catalog
to find out if there are audit policies that need to be
started, when the catalog is unavailable.
Similar DSNX232E message can be received during start of
DB2 with DEFER ALL specified.
2.When DB2 is started with ACCESS(MAINT) option, DSNW108I
message may be received incorrectly, if audit policies are
defined to be started at DB2 start up. The audit policy
name is not retrieved from the catalog, which caused
1 the audit policy not to be started.
Code has been changed to
1.Not start the audit policies at DB2 start up during start of
DB2 in SYSPITR mode or with DEFER ALL specified.
2.Start the audit policies that are defined to be started at
DB2 start up, when DB2 is started with ACCESS(MAINT) option,
but not with SYSPITR mode, DEFER ALL or RESTART LIGHT mode.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55252
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWACDF PM55252
DSNXAMAP PM55252
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55252 DSNWACDF DSNXAMAP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWACDF
DSNXAMAP
LISTEND
UK77380 COVER LETTER END
UK77407 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55788 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC0000003B at DSNXCEET+01A4 *
* may occur when DB2 thread is cancelled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a thread that requires LE environment within DB2 subsystem
is cancelled ABEND 0C4 at DSNXCEET+01A4 may occur. The abend
occurs when DB2 is attempting to free the un-freed LE
environment token that was left over due to the abnormal thread
termination.
DB2 code was changed to properly free LE token.
ADDITIONAL KEYWORDS: SQLLE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55788
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
DSNXCEES PM55788
DSNXCEET PM55788
DSNXINIT PM55788
DSNXLEBS PM55788
DSNXLEDL PM55788
DSNXLEFS PM55788
DSNXLEGS PM55788
DSNXLEII PM55788
DSNXLELD PM55788
DSNXLEMS PM55788
DSNXLEPE PM55788
DSNXLESL PM55788
DSNXLEST PM55788
DSNXLETI PM55788
DSNXLEUE PM55788
DSNXRLE PM55788
DSNXRLEI PM55788
DSNXRLET PM55788
DSNXRLE9 PM55788
DSNXRLI9 PM55788
DSNXRLNU PM55788
DSNXRLT9 PM55788
DSNXRLU9 PM55788
DSNXRUFS PM55788
DSNXRUS9 PM55788
DSNXTERM PM55788
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55788 DSNXCEES DSNXCEET DSNXINIT DSNXLEBS DSNXLEDL DSNXLEFS
DSNXLEGS DSNXLEII DSNXLELD DSNXLEMS DSNXLEPE DSNXLESL
DSNXLEST DSNXLETI DSNXLEUE DSNXRLE DSNXRLEI DSNXRLET
DSNXRLE9 DSNXRLI9 DSNXRLNU DSNXRLT9 DSNXRLU9 DSNXRUFS
DSNXRUS9 DSNXTERM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXCEES
DSNXCEET
DSNXINIT
DSNXLEBS
DSNXLEDL
DSNXLEFS
DSNXLEGS
DSNXLEII
DSNXLELD
DSNXLEMS
DSNXLEPE
DSNXLESL
DSNXLEST
DSNXLETI
DSNXLEUE
1 DSNXRLE
DSNXRLEI
DSNXRLET
DSNXRLE9
DSNXRLI9
DSNXRLNU
DSNXRLT9
DSNXRLU9
DSNXRUFS
DSNXRUS9
DSNXTERM
LISTEND
UK77407 COVER LETTER END
UK77410 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55357 -
****************************************************************
* USERS AFFECTED: Internal performance enhancement *
****************************************************************
* PROBLEM DESCRIPTION: Internal performance enhancement *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Internal performance enhancement
(Internal reference: DK1629)
Internal performance enhancement
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55357
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1GET PM55357
DSNDQWPZ PM55357
DSNDSPRM PM55357
DSNIONX2 PM55357
DSNIOST2 PM55357
DSNIRIDR PM55357
DSNISFXP PM55357
DSNZOVTB PM55357
DSN6SPRC PM55357
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55357 DSNB1GET DSNDQWPZ DSNDSPRM DSNIONX2 DSNIOST2 DSNIRIDR
DSNISFXP DSNZOVTB DSN6SPRC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1GET
DSNIONX2
1 DSNIOST2
DSNIRIDR
DSNISFXP
DSNZOVTB
MACROS
DSNDQWPZ
DSNDSPRM
DSN6SPRC
LISTEND
UK77410 COVER LETTER END
UK77426 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57630 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and DB2 *
* 10 for z/OS users of character conversions *
* from CCSID 367 to CCSID 937. *
****************************************************************
* PROBLEM DESCRIPTION: Problem 1: *
* SQLCODE331 may be incorrectly returned *
* for an SQL statement that converts *
* characters from CCSID 367 to CCSID 937 *
* Problem 2: *
* ABEND0C4 at DSNXGRDS DSNXVTRS +0C16 *
* may occur on Version 10 only when DB2 *
* is calling a conversion procedure. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Problem 1:
The conversion procedure DSNXVTWC in SYSIBM.SYSSTRINGS is
called to translate characters from CCSID 367 to CCSID 937.
This conversion procedure incorrectly returns an error for
strings greater than 408 characters. DB2 issues SQLCODE -331
due to the error code 20 from the conversion procedure.
It has also been determined that the DSNXVTWC procedure
translation differs from Unicode services for the following
three characters when translating from CCSID 367 to CCSID 937.
SM060000 Ý '5B'x
SM080000 ¨ '5D'x
SD150000 ¬ '5E'x
The DSNXVWTC procedure translates the characters '5B'x, '5D'x,
and '5E'x to '4A'x, '6A'x, and '5F'x respectively.
Unicode services translates the characters '5B'x, '5D'x, and
'5E'x to 'BA'x, 'BB'x, and 'B0'x respectively. All other
characters are translated the same by DSNXVTWC and Unicode
services.
1 Unicode services returns the correct translation.
The following is a table to help illustrate the changes:
-----------------------------------------------------------
|GCGID |character| CCSID | CCSID 937 | CCSID 937 |
| | | 367 | (by DSNXVWTC) | by UCS |
-----------------------------------------------------------
|SM060000 | Ý | '5B'x | '4A'x |'BA'x |
-----------------------------------------------------------
|SM080000 | ¨ | '5D'x | '6A'x |'BB'x |
-----------------------------------------------------------
|SD150000 | ¬ | '5E'x | '5F'x |'B0'x |
-----------------------------------------------------------
The following is an example where the -331 sqlcode is issued :
CREATE TABLE T1 (C1 VARCHAR(409)
FOR SBCS DATA)
CCSID UNICODE;
INSERT INTO T1 VALUES (
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
'AAAAAAAAAAAAAAAAAAAAAAAAA');
EXEC SQL DECLARE :hv1 VARIABLE CCSID 937;
EXEC SQL DECLARE C1 CURSOR FOR
SELECT C1 FROM T1 ;
EXEC SQL OPEN C1;
EXEC SQL FETCH C1 INTO :hv1 ; <--- SQLCODE -331
Problem 2:
The abend in DSNXVTRS +0C16 can occur for any character
translation where a conversion procedure is called. The
problem only exists on Version 10. The abend occurs because
a pointer is referenced that has not been set.
DB2 code has been changed to invoke Unicode services instead of
the conversion procedure DSNXVTWC when translating
characters from CCSID 367 to CCSID 937. DB2 code will ignore
the row for this translation in SYSIBM.SYSSTRINGS. DB2 code has
also been changed to set the pointer correctly so the 0C4 abend
no longer occurs.
After applying this PTF the following three characters will be
translated differently.
1 SM060000 Ý '5B'x
SM080000 ¨ '5D'x
SD150000 ¬ '5E'x
Prior to applying this PTF, the DSNXVWTC proc is called and the
characters '5B'x, '5D'x, and '5E'x are translated to '4A'x,
'6A'x, and '5F'x respectively.
After applying this PTF, Unicode services is called and the
characters '5B'x, '5D'x, and '5E'x are translated to 'BA'x,
'BB'x, and 'B0'x respectively. All other characters are
translated the same by DSNXVTWC and Unicode services.
The following is a table to help illustrate the changes:
-----------------------------------------------------------
|GCGID |character| CCSID | CCSID 937 | CCSID 937 |
| | | 367 | (by DSNXVWTC) | by UCS |
-----------------------------------------------------------
|SM060000 | Ý | '5B'x | '4A'x |'BA'x |
-----------------------------------------------------------
|SM080000 | ¨ | '5D'x | '6A'x |'BB'x |
-----------------------------------------------------------
|SD150000 | ¬ | '5E'x | '5F'x |'B0'x |
-----------------------------------------------------------
If you have any applications that depend on these translated
values they may need to be modified to handle the correct
values.
Additional keywords : SQLCODE331
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57630
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM57630:
PM57630 corrects a problem where SQLCODE -331 is issued
incorrectly when translating characters from CCSID 367 to
CCSID 937.
DB2 code has been changed to invoke Unicode services instead of
the conversion procedure DSNXVTWC when translating
characters from CCSID 367 to CCSID 937. DB2 code will ignore
the row for this translation in SYSIBM.SYSSTRINGS.
After applying this PTF the following three characters will be
translated differently.
SM060000 Ý '5B'x
SM080000 ¨ '5D'x
SD150000 ¬ '5E'x
Prior to applying this PTF, the DSNXVWTC proc is called and the
1 characters '5B'x, '5D'x, and '5E'x are translated to '4A'x,
'6A'x, and '5F'x respectively.
After applying this PTF, Unicode services is called and the
characters '5B'x, '5D'x, and '5E'x are translated to 'BA'x,
'BB'x, and 'B0'x respectively. All other characters are
translated the same by DSNXVTWC and Unicode services.
The following is a table to help illustrate the changes:
-----------------------------------------------------------
|GCGID |character| CCSID | CCSID 937 | CCSID 937 |
| | | 367 | (by DSNXVWTC) | by UCS |
-----------------------------------------------------------
|SM060000 | Ý | '5B'x | '4A'x |'BA'x |
-----------------------------------------------------------
|SM080000 | ¨ | '5D'x | '6A'x |'BB'x |
-----------------------------------------------------------
|SD150000 | ¬ | '5E'x | '5F'x |'B0'x |
-----------------------------------------------------------
If you have any applications that depend on these translated
values they may need to be modified to handle the correct
values.
See PM57630 APAR/PTF text for additional information.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXVTRS PM57630
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57630 DSNXVTRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXVTRS
LISTEND
UK77426 COVER LETTER END
UK77430 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58802 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of XML. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE may be 0 even when there is an *
* abend during XML parsing which cause *
* INSERT or UPDATE or LOAD unsuccessful. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 calls z/OS XMLSS functions to parse XML documents. The
SQLCA is not formatted when there are abends in XMLSS.
The above DB2 10 for z/OS problem was fixed to issue SQLCODE
-904 when there are abends in XMLSS.
1
Additional keywords: XMLALL SQLXML SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58802
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOPAR PM58802
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58802 DSNNOPAR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOPAR
LISTEND
UK77430 COVER LETTER END
UK77451 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60145 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS Version 8 users who execute *
* ALTER TABLE ADD PARTITION ENDING AT where *
* the table is in a table space with more than *
* 1022 partitions and there is a partitioned *
* index defined on the table. *
****************************************************************
* PROBLEM DESCRIPTION: After ALTER TABLE ADD PARTITION ENDING *
* AT, REPAIR DBD DIAGNOSE may return the *
* following errors, *
* *
* OBDS DIFFER AT OFFSET X'000001B0' *
* OBDPISTO(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'60' *
* OBDS DIFFER AT OFFSET X'000001C8' *
* OBDPSRPG(6) *
* EXISTING VALUE X'00000000' *
* REBUILT VALUE X'00140002' *
* OBDS DIFFER AT OFFSET X'000001B1' *
* OBDPIPFS(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'1E' *
* OBDS DIFFER AT OFFSET X'000001B2' *
* OBDPIFPG(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'0A' *
* OBDS DIFFER AT OFFSET X'000001DC' *
* OBDPSIID(6) *
* EXISTING VALUE X'00000000' *
1 * REBUILT VALUE X'C4E2D5C3' *
* EXISTING VALUE '....' *
* REBUILT VALUE 'DSNC' *
* OBDS DIFFER AT OFFSET X'000001E0' *
* OBDPSIIX(6) *
* EXISTING VALUE X'00000000' *
* REBUILT VALUE X'C1E34040' *
* OBDS DIFFER AT OFFSET X'000001E4' *
* OBDPSIQP(6) *
* EXISTING VALUE X'0000' *
* REBUILT VALUE X'000C' *
* OBDS DIFFER AT OFFSET X'000001E6' *
* OBDPSISQ(6) *
* EXISTING VALUE X'0000' *
* REBUILT VALUE X'000C' *
* OBDS DIFFER AT OFFSET X'000001EA' *
* OBDPSIUP(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'D7' *
* OBDS DIFFER AT OFFSET X'000001EB' *
* OBDPSISU(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'D7' *
* OBDS DIFFER AT OFFSET X'000001EC' *
* OBDPSIUH(6) *
* EXISTING VALUE X'00' *
* REBUILT VALUE X'D7' *
* *
* run a query against that table hit *
* this abend, *
* *
* ABND04E RC00C90101 at LOC= *
* DSNK2DM .DSNKTRAV ERQUAL5010 *
* *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After applying PM08714/UK63926, customer may hit the following
problems,
When there are many partitions defined, an ALTER TABLE ADD
PARTITION ENDING AT could cause a DB2 internal data structure
index OBD incorrectly stored, which results in REPAIR DBD
DIAGNOSE errors and the abend mentioned above.
DB2 code has been changed to make sure the OBD is correct
after ALTER TABLE ADD PARTITION ENDING AT.
For DB2 for z/OS Version 8 users,
when the number of partitions is greater than 1022 and there is
a partitioned index on the table, alter add a partition will
cause the OBD to be broken.
This apar does not fix the problem which was introduced before
the apar was applied. REPAIR DBD REBUILD can be used to fix the
broken OBD, or drop all partitioned indexes and re-create them
1 can also fix the broken OBD.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60145
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDADP PM60145
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60145 DSNGDADP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDADP
LISTEND
UK77451 COVER LETTER END
UK77481 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59933 -
****************************************************************
* USERS AFFECTED: All DB2 z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: When the recovery routine for DSNAPRHX *
* processes an ABEND13E a service *
* task may be left not resynchronized. *
* This may cause an ABEND04E RC00E50705 *
* in DSNVEUS3 and an ABEND04E RC00D30002 *
* in DSNLCITR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Module DSNAPRHX should be changed to avoid leaving a service
task not resynchronized.
Module DSNAPRHX has been updated to perform additional
verification during recovery for an ABEND13E.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PM59933
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)
1 -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
DSNAPRHX PM59933
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59933 DSNAPRHX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRHX
LISTEND
UK77481 COVER LETTER END
UK77500 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56845 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users whose queries utilize *
* the OPTIMIZE FOR 1 ROW clause. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may choose an inappropriate access *
* path when the OPTIMIZE FOR 1 ROW clause *
* is used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In all versions of DB2, the OPTIMIZE FOR 1 ROW clause requests
DB2 to choose an access path that avoids a sort if one exists.
In DB2 versions prior to DB2 10, there is a possibility to
obtain an access path with a sort even though that access path
choice is strongly discouraged. In DB2 10, when an access path
exists that does not require a sort, DB2 will not compete
access paths with sorts. Instead DB2 will choose the lowest
cost access path that does not require a sort.
This APAR provides an option to return to the previous
OPTIMIZE FOR 1 ROW behavior prior to DB2 10. As such, it does
not eliminate the risk of an inefficient access path being
chosen with OPTIMIZE FOR 1 ROW when the efficient access path
requires a sort. However, it does limit that exposure to what
already existed in DB2 prior to DB2 10.
This APAR introduces ZPARM OPT1ROWBLOCKSORT to control the
behavior of the OPTIMIZE FOR 1 ROW clause. When determining
how to set this ZPARM consider the following...
* OPT1ROWBLOCKSORT=ENABLE guarantees that an access path
without a sort will be chosen if one exists. As such,
1 if an index exists to support the requested order, DB2
may use this index to avoid a sort even if this means
scanning all the data. In some cases, this may yield an
inefficient access path.
* OPT1ROWBLOCKSORT=DISABLE allows DB2 to consider access
paths that require a sort. However, these access path
choices will be strongly discouraged. This is the
behavior present in DB2 9 and previous releases. If the
goal of coding the OPTIMIZE FOR 1 ROW clause is to disable
a sort or if the best access path requires a sort, this may
yield an inefficient access path.
* With either zparm setting, DB2 will continue to prefer
access paths without sorts for queries with the OPTIMIZE
FOR 1 ROW clause. If this is not the desired behavior, the
application should either remove the OPTIMIZE FOR 1 ROW
clause or change it to OPTIMIZE FOR n ROWS where n is
greater than 1.
* The OPTIMIZE FOR 1 ROW clause will avoid access paths
containing list prefetch and multi-index access. This
behavior is not changed with either zparm setting.
* Sometimes materialization and sorts are unavoidable. In
these cases, the OPTIMIZE FOR 1 ROW clause can be ignored.
This behavior is not changed with either zparm setting.
For queries that need sorts, the recommended solution is to
avoid coding the OPTIMIZE FOR 1 ROW clause. Without the
OPTIMIZE FOR 1 ROW clause, DB2 will choose access paths based on
cost and will not make an effort to avoid sorts.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE SQLOFNR
Code is changed to provide an option to revert to the behavior
of DB2 9 and earlier versions of DB2 for OPTIMIZE FOR 1 ROW.
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: PM56845
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM56845:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM56845 allows you to specify whether, for queries
that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access
paths that require sort when there exists at least one access
path that avoids sort.
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.
ACTION:
***Action for PM56845:
This PTF adds a new DB2 subsystem parameter in DSN6SPRM named
OPT1ROWBLOCKSORT that allows you to specify whether, for queries
that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access
paths that require sort when there exists at least one access
path that avoids sort. Valid options are:
* ENABLE : When OPTIMIZE FOR 1 ROW is used with a query, DB2
will disable sort access paths when a no-sort choice
is available.
* DISABLE: DB2 will strongly discourage sort access paths and is
unlikely to choose sort access paths, but there will
be a chance a sort access path can win. This is the
behavior which was present in DB2 9 and prior
releases.
==> This is the default setting
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter OPT1ROWBLOCKSORT=<x>,
where <x> is DISABLE or ENABLE, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
1 OPT1ROWBLOCKSORT here, the value will be set to the
default of DISABLE when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for OPT1ROWBLOCKSORT to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library.
You need to add these entries to all private copies of your
CLIST output DSNTIDxx member. In each such copy, add the
following lines:
OPT1ROWBLOCKSORT CHAR G DISABLE ENABLE <x>
Change <x> to the value you specified for
OPT1ROWBLOCKSORT in step (2), above.
If you do not add OPT1ROWBLOCKSORT to a DSNTIDxx
member, the DB2 installation CLIST will assume
OPT1ROWBLOCKSORT=DISABLE when run with that member
as input.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PM56845
DSNDQWPZ PM56845
DSNDSPRM PM56845
DSNTIDXA PM56845
DSNTIDXB PM56845
DSNTIJUZ PM56845
DSNTINST PM56845
DSNTXAZP PM56845
DSNWZIFA PM56845
DSNXOGP PM56845
DSNXOMPS PM56845
DSN6SPRM PM56845
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56845 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ
DSNTINST DSNTXAZP DSNWZIFA DSNXOGP DSNXOMPS DSN6SPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
DSNWZIFA
DSNXOGP
DSNXOMPS
1
MACROS
DSN@XAZP
DSNDQWPZ
DSNDSPRM
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6SPRM
LISTEND
UK77500 COVER LETTER END
UK77506 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53462 -
****************************************************************
* USERS AFFECTED: DB2 8, 9 and 10 for z/OS users of *
* applications with DECLARE GLOBAL TEMPORARY *
* TABLES ( DGTT ) defined with ON COMMIT *
* DELETE ROWS and the application also has an *
* SQL cursor WITH HOLD that references the *
* DGTT. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrout may be returned for first *
* SQL FETCH of a WITH HOLD cursor that *
* references a DECLARE GLOBAL TEMPORARY *
* TABLE defined with default attribute *
* ON COMMIT DELETE ROWS, if a COMMIT *
* occurs between the SQL OPEN for the *
* cursor and that first SQL FETCH. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrout SQLCODE +100 may be returned for first SQL FETCH of
a WITH HOLD cursor that references a DECLARE GLOBAL TEMPORARY
TABLE defined with default attribute ON COMMIT DELETE ROWS, if
a COMMIT occurs between the SQL OPEN for the cursor and that
first SQL FETCH.
Not all queries referencing DGTTs in this scenario will have
this problem. Only simpler queries for which DB2 does not
need to capture temporary results from the DGTT before
returning the final query result will exhibit this error.
The following scenario presents an example of this simpler
query case where the incorrout may occur:
EXEC SQL DECLARE GLOBAL TEMPORARY TABLE DGTT1
(
C1 INT,
C2 CHAR(10) ,
)
ON COMMIT DELETE ROWS;
1 EXEC SQL INSERT INTO SESSION.DGTT1 VALUES
(:hv1,:hv2);
EXEC SQL DECLARE C1 CURSOR WITH HOLD FOR
SELECT * FROM SESSION.DGTT1;
EXEC SQL OPEN C1;
EXEC SQL COMMIT;
EXEC SQL FETCH FROM C1 INTO :hv3, :hv4,
SQLCODE +100 might be returned incorrectly for the FETCH if
a commit is done between the SQL OPEN cursor and the first
FETCH for that cursor.
The SQLCODE +100 invalidly occurred on the FETCH because, on
the COMMIT DB2 deleted the rows of the DGTT as directed by
the DGTT attribute ON COMMIT DELETE ROWS. However, if a DGTT is
referenced by an 'open' and WITH HOLD cursor at the time of
the COMMIT, DB2 should not delete the DGTT rows. In this
specific case of COMMIT between the SQL OPEN and first FETCH,
DB2 did not remember that a WITH HOLD cursor was still open
on the DGTT, and therefore incorrectly deleted the DGTT
rows, resulting in the SQLCODE +100 on the first FETCH.
Another scenario where this problem may occur is if the
WITH HOLD cursor on the DGTT is also a WITH RETURN result set
for a DB2 stored procedure that is defined COMMIT ON RETURN YES,
and the first FETCH for this result set is actually issued by
by the client/caller of the stored procedure after returning
from the stored procedure and DB2 performed an implicit COMMIT
upon return from that stored procedure (as directed by stored
proc attribute COMMIT ON RETURN) before the caller's first
FETCH.
Besides SQLCODE +100 , other unexpected incorrout results may
occur if the DGTT is only one of several tables referenced in
the query and the results of the DGTT are input to other parts
of the query.
To avoid the problem described above, you can do any one of
following:
(1) If appropriate do not issue a COMMIT between the SQL OPEN
cursor (that references the DGTT) and the first SQL FETCH
for the cursor, or
(2) Define the DGTT as ON COMMIT PRESERVE ROWS
(3) If this WITH HOLD cursor is also a WITH RETURN result set
for a DB2 stored procedure and the stored proc is defined
COMMIT ON RETURN YES, and the first FETCH for the result
set is actually issued by the client/caller instead of by
the stored proc, issue the SQL statement ALTER PROCEDURE
schema. procedure-name COMMIT ON RETURN NO
to remove the COMMIT ON RETURN YES attribute from the stored
proc. On return from the stored proc DB2 then will *not*
1 perform the implicit COMMIT that would occur between the SQL
OPEN cursor (that is 'inside' the stored procedure) and
the caller's/client's first FETCH of the WITH RETURN cursor
result set that references the DGTT.
The DB2 code is modified to correct the conditions leading to
to the INCORRECT OUTPUT.
Additional Keywords: SQLINCORR SQLINCORROUT DB2INCORR/K
SQLDGTT SQLCOMMIT SQLCODE100
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53462
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXESX4 PM53462
DSNXOCU PM53462
DSNXOMS PM53462
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53462 DSNXESX4 DSNXOCU DSNXOMS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXESX4
DSNXOCU
DSNXOMS
LISTEND
UK77506 COVER LETTER END
UK77518 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56624 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS *
* users of SQL/XML publishing functions *
* running plans and packages bound in DB2 8 *
* for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect result from SQL/XML *
* publishing functions because special *
* characters were not converted to their *
* XML entity representation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem of special characters not converted to their XML
entity representation occurred when a plan or package,
that was bound in DB2 8 for z/OS, was run on DB2 9 for z/OS
or DB2 10 for z/OS. For the problem to occur, the special
character must be used in an input argument to a SQL/XML
publishing function such as XMLELEMENT, XMLFOREST, XMLCONCAT
1 or XMLAGG.
The problem occurs for these special characters:
Special character Entity representation
_________________ _____________________
& &
< <
> >
The following is an example of a SQL statement with the
problem:
SELECT XML2CLOB(
XMLELEMENT(NAME "e1", 'A & B')
) INTO :HVCLOB1
FROM SYSIBM.SYSDUMMY1;
Instead of returning '<e1>A & B</e1>', the SELECT
incorrectly returned '<e1>A & B</e1>'.
Additional keywords: SQLXML XMLALL XMLINCORR DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56624
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXXAGG PM56624
DSNXXGEN PM56624
DSNXXTTM PM56624
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56624 DSNXXAGG DSNXXGEN DSNXXTTM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXXAGG
DSNXXGEN
DSNXXTTM
LISTEND
UK77518 COVER LETTER END
UK77548 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58511 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of SET function query with CPU parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect result is returned from a SET *
1 * function query while running in CPU *
* Parallelism mode on a partitioned *
* tablespace that has been alter rotated. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result is returned When a SET function query is
running in CPU parallelism on a partitioned tablespace that has
been alter rotated. The child task failed to recognize the
boundary of the range and continued to process the part beyond
it's range. The rows from the same partition were returned by
multiple child tasks causing incorrect output.
DB2 code was changed to correctly recognize the end of the range
during the SET function pageset scan processing.
ADDITIONAL KEYWORDS: INCORROUT SQLPARA SQLINCORROUT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58511
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISFS PM58511
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58511 DSNISFS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISFS
LISTEND
UK77548 COVER LETTER END
UK77556 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58839 -
****************************************************************
* USERS AFFECTED: All DB2 users who do remote BIND. *
****************************************************************
* PROBLEM DESCRIPTION: Remote BIND process may cause other *
* processes to hang for a considerable *
* amount of time. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a user binds a package on a remote server, DB2 acquires an
exclusive package lock before validating the SYSPACKAGE record
and checking the users' authorization. This creates an issue
when there is a problem in the package initialization process,
such as the record already exists or the user is not authorized
to bind. DB2 may continue to hold the lock on the package for
a considerable amount of time before the lock is released even
1 if the bind fails, and this can cause other processes such as an
online transaction to hang.
DB2 has been fixed to not obtain an exclusive lock if the remote
bind fails because the record exists and ACTION(ADD) is in
effect. If the remote bind fails due to other problems in the
BEGIN BIND (package initialization) step such as an
authorization error, and the package lock has been acquired,
DB2 will release the package lock before returning back to
the requester.
Keywords: PERFM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58839
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBAS PM58839
DSNTBCM2 PM58839
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58839 DSNTBAS DSNTBCM2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBAS
DSNTBCM2
LISTEND
UK77556 COVER LETTER END
UK77572 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53629 -
INTEGRITY PROBLEM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53629
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
INTEGRITY:
INTEGRITY SET: UK77572,UK77576
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWAAPI PM53629
DSNWACDF PM53629
DSN9SCNP PM53629
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53629 DSNWAAPI DSNWACDF DSN9SCNP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNWAAPI
DSNWACDF
DSN9SCNP
LISTEND
UK77572 COVER LETTER END
UK77584 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM45650 -
****************************************************************
* USERS AFFECTED: All DB2 z/OS v10 users of Recover *
* Utility with Backout Yes option on *
* LOB table space *
****************************************************************
* PROBLEM DESCRIPTION: The LOB data may be unrecoverable by *
* applying log records from running *
* Recover Utility with Backout Yes *
* Option. As the result, a possible *
* LOB data corruption could happen *
* without any indication. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the log apply phase of the RECOVER BACKOUT YES
utility, only the LOG records of space map pages are
processed. From the set of log records defined by the
log range of Recover utility, any insert of LOB data reused
previous deleted space, so this LOB data can not be recovered.
As the result, LOB data could be corrupted without giving
any feedback to the user.
DB2 code has been modified to mark LOB invalid under the
situation when the LOB can not be recovered from the
Recover Utility with Backout Yes processing. As the result,
a SQL -904 with reason code '00C900D0' will be issued
when this LOB data is accessed after the Recover Utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM45650
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOLADS PM45650
DSNONLLE PM45650
DSNOTCSO PM45650
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM45650 DSNOLADS DSNONLLE DSNOTCSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOLADS
1 DSNONLLE
DSNOTCSO
LISTEND
UK77584 COVER LETTER END
UK77633 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM54671 -
****************************************************************
* USERS AFFECTED: AE PM51083 FIX COMPLETION *
****************************************************************
* PROBLEM DESCRIPTION: AE PM51083 FIX COMPLETION *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PM51083 FIX COMPLETION
AE PM51083 FIX COMPLETION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM54671
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFLC PM54671
DSNGEPDL PM54671
DSNGEPLC PM54671
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM54671 DSNGEFLC DSNGEPDL DSNGEPLC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFLC
DSNGEPDL
DSNGEPLC
LISTEND
UK77633 COVER LETTER END
UK77636 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51643 -
****************************************************************
* USERS AFFECTED: All DB2 package users. *
****************************************************************
* PROBLEM DESCRIPTION: Customer could receive an abend *
* DSNXECWA:M700 on ROLLBACK. *
* There could be other unexpected *
* behaviors. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
When a package execution hit an error, DB2 could incorrectly
unlock S-lock on the package which could result in the above
problems.
DB2 has been changed to avoid unlocking the package when an
error occurs which fixes the problem hit by the customer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51643
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFLC PM51643
DSNGEPLC PM51643
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51643 DSNGEFLC DSNGEPLC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFLC
DSNGEPLC
LISTEND
UK77636 COVER LETTER END
UK77652 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53042 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 users of CP parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: Insufficient information present in *
* dumps while diagnosing CP parallelism- *
* related problems. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Insufficient information present in dumps while diagnosing
CP parallelism-related problems.
Code has been added to enhance serviceability in the CP
parallelism area.
Additional Keywords: SQLCPUP SQLPARALLELISM SQLCPUP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53042
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTTTC PM53042
DSNTTTGC PM53042
1 DSNXECLN PM53042
DSNXEUFP PM53042
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53042 DSNTTTC DSNTTTGC DSNXECLN DSNXEUFP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTTTC
DSNTTTGC
DSNXECLN
DSNXEUFP
LISTEND
UK77652 COVER LETTER END
UK77666 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58114 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 9 for z/OS *
* customers that issue *
* LOCK TABLE IN SHARE MODE or LOCK TABLE *
* IN EXCLUSIVE MODE on a Partition By *
* Growth (PBG) table space can potentially *
* experience data regression when a new *
* partition is added. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNICUMW ERQUAL5003 *
* Data loss due to regressed pages. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For a PBG table space, locks are taken at each partition level
instead of the entire table or table space when a LOCK TABLE IN
EXCLUSIVE MODE SQL statement is issued. After the LOCK TABLE
operation completed, another agent was allowed to proceed with
an insert operation that forced the creation of a new partition.
The agent that issued the LOCK TABLE then regressed the data
rows in the new partition as it should have had exclusive access
to the entire table.
DB2 code has been changed to detect if all partitions are locked
in exclusive or shared modes and to then avoid growing the PBG
table space into a new partition by another agent that is doing
SQL INSERT or UPDATE operations.
The failing agent will get a RC00C9008E return code to indicate
a lock timeout condition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58114
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 DSNISUPI PM58114
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58114 DSNISUPI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISUPI
LISTEND
UK77666 COVER LETTER END
UK77693 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59950 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who using *
* UPDATE ... WHERE CURRENT OF. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC38 at DSNXGTRE+0346 may *
* occur on UPDATE WHERE CURRENT OF *
* if the SET clause contains a CASE *
* expression with an EXISTS subquery *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC38 at DSNXGTRE+0346 on UPDATE WHERE CURRENT OF may
occur if the SET clause of the UPDATE contains a CASE expression
with an EXISTS subquery. A plan may not be built for the
query block containing the EXISTS subquery, which leads to
the abend.
Additional Keywords:
SQLUPDATE WCO SQLCASE SQLEXISTS SQLSUBQUERY
Code is changed to allow the plan for the EXISTS subquery to be
built.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59950
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PM52694 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM52694 fixes a query costing problem when the query has outer
join and FETCH FIRST n ROWS ONLY or OPTIMIZE FOR n ROWS.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1 DSNXOGP PM59950
DSNXOPB PM59950
DSNXOPCO PM59950
DSNXOPLM PM59950
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59950 DSNXOGP DSNXOPB DSNXOPCO DSNXOPLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGP
DSNXOPB
DSNXOPCO
DSNXOPLM
LISTEND
UK77693 COVER LETTER END
UK77699 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58858 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKCEST ERQUAL5004 *
* occurred during BIND or PREPARE of *
* reversed range predicate *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C90101 DSNKCEST ERQUAL5004 occurred during BIND or
PREPARE of reversed range predicate where value is a VARCHAR.
An incorrect comparison of the range predicate values led DB2
to believe the values were in ascending order, but were not.
This eventually led to the abend.
In the following 2 examples, the range predicate is expected to
be in ascending order, which means value2 is less than or equal
to value3:
1. value1 BETWEEN value2 AND value3
2. value1 >= value2 AND value1 <= value3
DB2 has been updated to correctly compare the range predicate.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58858
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 PM58858
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58858 DSNKCEST
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKCEST
LISTEND
UK77699 COVER LETTER END
UK77733 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58284 -
****************************************************************
* USERS AFFECTED: All DB2 z/OS users of SELECT query via *
* a NPI index. *
****************************************************************
* PROBLEM DESCRIPTION: When a SELECT query with NPI index *
* access ran into an abort, the SELECT *
* job is hung. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A SELECT job is hung after an abort due to its recovery process
is in the loop. The recovery process did not properly managed
by the function which caused the loop.
DB2 code is fixed to properly manage the recovery process.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58284
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIONX2 PM58284
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58284 DSNIONX2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIONX2
LISTEND
UK77733 COVER LETTER END
UK77737 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56989 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Pages added to LPL while recovering *
* a postponed-abort UR. Console message *
* MSGDSNB250E with CSECT name DSNIBMOC *
1 * or DSNIIMPD, and reason LOGAPPLY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Pages are added to LPL due to postponed recovery being unable
to open a page set because of an incomplete checkpoint log
record.
A page set checkpoint log record may be incomplete due to the
page set control blocks being freed earlier in restart. A
"special open" is done to create these blocks, but they may
be immediately freed.
DB2 has been modified to ensure that a page set's PB0 control
block is kept if it was created on behalf of a "special open"
request, so that its information will be logged in the next
page set checkpoint log record.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56989
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CPS PM56989
DSNB1OPP PM56989
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56989 DSNB1CPS DSNB1OPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPS
DSNB1OPP
LISTEND
UK77737 COVER LETTER END
UK77739 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57878 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of XQuery *
* constructor expressions. *
****************************************************************
* PROBLEM DESCRIPTION: When the XQuery constructor *
* expressions are nested in the FLWOR *
* expression, the performance can be *
* improved. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the XQuery constructor expressions are nested in the FLWOR
expression, the performance can be improved by deferring the
construction of the XQuery constructor expressions after all
1 the data has been evaluated and do the construction once.
For example:
In the following query, the element constructor for element
node c is nested in the FLWOR expression.
SELECT XMLQUERY(
'<Output>
{ for $a in $X/a/b
return
<c> { $a } </c>
}
</Output>'
PASSING XMLCOL AS X)
FROM T1;
Currently, DB2 will construct the element constructor for
element node c in each loop when the return clause is
evaluated. Assume that the FLWOR expression loops 10 times,
then the element constructor for element node c will be
constructed 10 times.
DB2 is modified to defer the construction until later when the
XML data is referenced, so we can do the construction only once
and improve performance.
Additional keywords: SQLXML XMLXQUERY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57878
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 PM57878
DSNNOBSE PM57878
DSNNOBXI PM57878
DSNNOCCN PM57878
DSNNORCN PM57878
DSNNORES PM57878
DSNNORSQ PM57878
DSNNOSCO PM57878
DSNNOSER PM57878
DSNNOXMV PM57878
DSNNQFLR PM57878
DSNNQOB PM57878
DSNNQOPM PM57878
DSNNQTOP PM57878
DSNNQXCA PM57878
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57878 DSNNOBSC DSNNOBSE DSNNOBXI DSNNOCCN DSNNORCN DSNNORES
DSNNORSQ DSNNOSCO DSNNOSER DSNNOXMV DSNNQFLR DSNNQOB
DSNNQOPM DSNNQTOP DSNNQXCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOBSC
1 DSNNOBSE
DSNNOBXI
DSNNOCCN
DSNNORCN
DSNNORES
DSNNORSQ
DSNNOSCO
DSNNOSER
DSNNOXMV
DSNNQFLR
DSNNQOB
DSNNQOPM
DSNNQTOP
DSNNQXCA
LISTEND
UK77739 COVER LETTER END
UK77743 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59401 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of FlashCopy *
* image copies with the COPYTOCOPY, REORG, *
* and RECOVER utilities. *
****************************************************************
* PROBLEM DESCRIPTION: DSNU1408I followed by ABENDSC03 *
* during the COPYTOCOPY utility when a *
* FlashCopy image copy is used as input. *
* .. *
* RECOVER utility terminates with *
* DSNU514I RC8 when a sequential *
* image copy created from a FlashCopy *
* image copy is used as a recovery *
* base. *
* .. *
* REORG utility issues DSNU341I *
* for directory table space *
* DSNDB01.SYSSPUXB even if a FlashCopy *
* image copy exists, then abends with *
* ABEND04E RC00E40024. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During COPYTOCOPY processing on a list, if more than one of
the objects is partitioned or has multiple pieces, and uses
a FlashCopy image copy (FCIC) taken at the space level
(e.g., DSNUM ALL) as input, then msgDSNU1408I SOURCE DATA SET
DOES NOT MATCH, followed by an ABENDC03 could occur. In
addition, msgDSNU1403i DATA SET WITH STARTRBA IS IN USE BY
COPYTOCOPY, is only issued once even if multiple FCIC data
sets are used to create a sequential image copy at the
space level.
..
The RECOVER utility with the DSNUM ALL option could terminate
1 with msgDSNU514I DATA SET LEVEL RECOVERY IS REQUIRED, and
RC8 when a sequential image copy created from a FCIC is used
as a recovery base. The SYSCOPY.CPYDSNM column in the
SYSCOPY record inserted by COPYTOCOPY for the sequential copy
incorrectly contained a non zero value. SYSCOPY.CPYDSNM
should have contained a zero because the sequential image
copy is at the space level.
..
The REORG utility may incorrectly issue msgDSNU341I IMAGE COPY
MUST BE TAKEN BEFORE REORG CAN BE RUN ON THE CATALOG OR
DIRECTORY, on a catalog or directory table space even if a
FCIC exists as a backup. In addition, if a LOB table space
is the target object, then an ABEND04E RC00E40024 might
occur after an error in REORG initialization processing.
COPYTOCOPY has been modified to correctly handle FCICs taken
at the space level, in regards to data set handling and the
contents of the SYSCOPY record (which is used by RECOVER).
MsgDSNU1403I is now issued for each FCIC used as input to
create a space level sequential image copy.
..
REORG has been modified to correctly recognize a FCIC as a
recovery base. The ABEND04E RC00E40024 that could occur for
LOB table spaces after an error in REORG intialization has
been fixed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59401
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM59401 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGFRP PM59401
DSNURORG PM59401
DSNU2ASR PM59401
DSNU2ASW PM59401
DSNU2BCC PM59401
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59401 DSNUGFRP DSNURORG DSNU2ASR DSNU2ASW DSNU2BCC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNUGFRP
DSNURORG
DSNU2ASR
DSNU2ASW
DSNU2BCC
LISTEND
UK77743 COVER LETTER END
UK77745 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59280 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 users with "alias *
* resolution enabled" for applications bound *
* with REOPT bind option and that issue *
* distributed dynamic SQL statements that *
* specify an ALIAS to refer to remote objects *
* at a remote Application Server (AS), where *
* "alias resolution enabled" is defined as
*
* follows: *
* *
* For DB2 9, *
* DB2 subsystem parameter *
* DSN6SPRM.DRDA_RESOLVE_ALIAS = YES *
* *
* For DB2 10, *
* alias resolution enabled by default *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -104 issued by an Application *
* Server (AS) for an inbound dynamic SQL *
* statement that originally used an alias *
* to refer to a remote table at that *
* server. At the DB2 9 or 10 for z/OS *
* Application Requester (AR) where the *
* distributed dynamic SQL statement *
* originated, *
* - the application is bound with option *
* REOPT(ONCE|AUTO|VARS|ALWAYS), and *
* - "alias resolution enabled"
*
****************************************************************
* RECOMMENDATION: *
****************************************************************
On a DB2 9 or 10 for z/OS Application Requester (AR) where
alias resolution is enabled, an application bound with bind
option REOPT( ONCE | AUTO | VAR | ALWAYS ) issued a distributed
dynamic SQL statement that used an ALIAS to refer to a remote
object at an Application Server (AS). At that target AS, the
dynamic SQL statement failed with SQLCODE -104 during the
prepare of the dynamic statement, and the SQLCODE104 was
returned to the user application at the DB2 9 or 10 for z/OS AR.
The target remote AS may or may not be a DB2 for z/OS AS. The
dynamic statement should not have have failed with SQLCODE104.
.
1 Note that enabling alias resolution means that the DB2 AR should
resolve any aliases specified in distributed SQL statements
before the SQL statements are sent outbound to the target remote
AS, so DB2 performs the alias resolution using values defined
for that ALIAS at the DB2 AR, not at the target AS. So the DB2
AR modifies the outbound SQL statement text by replacing the
alias with the associated DB2 AR defined value, therefore the
alias is no longer part of the outbound statement text sent to
the target AS and the alias is not resolved there.
.
The SQLCODE -104 occurred at the target remote AS because
the DB2 9 or 10 for z/OS AR passed an incorrect CCSID to
the target AS for this modified outbound dynamic SQL statement,
when the DB2 AR application issuing the dynamic SQL statement
is bound REOPT(ONCE|AUTO|VARS|ALWAYS).
.
This SQLCODE -104 failure when using aliases does not occur when
either the DB2 AR application is bound REOPT( NONE ), which is
the DB2 default, or when alias resolution is disabled.
DB2 9 and 10 for z/OS AR code has been changed to pass the
correct statement CCSID to the target remote AS for the dynamic
SQL scenario described above.
.
*************************************************************
* The PTF for PM59280 *must* be applied to the DB2 for z/OS *
* Application Requester subsystem in order to resolve *
* the SQLCODE104 that occurs at the target remote AS. *
* There is no PTF change to apply to the target remote AS *
* where the SQLCODE104 occurred. *
*************************************************************
.
Additional Search Keywords: SQLCODE104 SQLDRDA DB2DDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59280
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
*** Action for PM59280 ***
This fix corrects a SQLCODE104 symptom observed at the server
site (site2), but to correct the problem this fix must be
applied to the DB2 for z/OS requester site (site1) where
alias resolution is enabled.
Review the PTF cover letter for further explanation of
the requester (site1) applications that are affected.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDP PM59280
DSNXEDS1 PM59280
DSNXEPM PM59280
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59280 DSNXEDP DSNXEDS1 DSNXEPM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXEDP
DSNXEDS1
DSNXEPM
LISTEND
UK77745 COVER LETTER END
UK77769 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53240 -
****************************************************************
* USERS AFFECTED: Users of DB2 10 for z/OS who have altered a *
* table space to hash organization but have *
* not yet REORG'd the table space *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C7 DSNIRNXT OFFSET B390 with *
* DELETE from Universal Table Space *
* Partition By Growth with COMPRESS YES *
* option after ALTER ADD HASH *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem occurs when the Partition By Growth table space
is in an intermediate state of ALTERed to hash but not yet
converted to hash (pending hash state), DB2 incorrectly takes
the dictionary from the wrong partition to compress a record
during DML INSERT transaction. A subsequent DML attempts to
decompress a record using the dictionary from the partition in
which the row resides. This results in an abend ABEND0C7 on
DSNIRNXT+B390 because the dictionary used to decompress the
record is different from the dictionary that was used to
compress the record.
Not setting the correct partition could cause other failures.
DB2 is changed to correctly compress a record using the
dictionary of a partition in which the record is inserted.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53240
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISRTI PM53240
DSNURFIT PM53240
DSNURORG PM53240
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53240 DSNISRTI DSNURFIT DSNURORG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISRTI
1 DSNURFIT
DSNURORG
LISTEND
UK77769 COVER LETTER END
UK77778 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57087 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: GRECP recovery fails with ABEND04E *
* RC00C90101 in DSNKUNR2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A timing window between two members connecting to a group
buffer pool (GBP) causes the first member completing the
connection to take a structure checkpoint with incorrect
recovery LRSN of the second member. If the next structure
checkpoint happens after the second member's DB2 checkpoint,
page sets using the GBP may get incorrect recovery LRSN. If
the GBP is purged or DB2 crashes, the recovery may fail
with abends.
DB2 GBP connection logic has been modified to initialize the
member recovery LRSNs correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57087
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1GC1 PM57087
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57087 DSNB1GC1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1GC1
LISTEND
UK77778 COVER LETTER END
UK77822 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55897 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of Field Procedures or FIELDPROCS. *
****************************************************************
1 * PROBLEM DESCRIPTION: Field procedures (aka fieldprocs) that *
* are loaded via the DB2 service task for *
* various threads use can be freed *
* prematurely if for some reason the *
* service task terminates. This can *
* result in various ABEND0C1 or ABEND0C4 *
* kinds of abends when one of these *
* threads references a freed fieldproc. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Field procedures (aka fieldprocs) that are loaded via the DB2
service task for various threads use can be freed prematurely if
for some reason the service task terminates. This can result in
various ABEND0C1 or ABEND0C4 kinds of abends when one of these
threads references a freed fieldproc.
The following scenario illustrates the reported problem.
A DB2 Thread (1) is active using the DB2 service task. It gets
held up during the LOADing of a fieldproc. A second DB2 Thread
(2) comes in and attempts to LOAD a fieldproc under the same
service task. Thread (2) queues up for the service task
currently held by Thread (1). Thread (2) is canceled as it
seems to be held up, by a -CANCEL THREAD command. Thread (1)
now resumes. Thread (2) terminates with an ABEND04E rc00E50013
in DSNXVEUS3 once Thread (1) completes service task processing.
The service task TCB will abend and any fieldprocs that were
LOADed by this TCB will go away. Sometime later when Thread (1)
references the fieldproc it LOADed (which has been freed), an
ABEND0C1 can occur because the fieldproc is no longer resident.
The code in DB2 is modified to change how it manages field
procedures. The mechanism DB2 uses to manage fieldprocs
(loading and freeing) has been reworked to use a different
scheme. This new scheme will protect fieldprocs that have been
loaded while DB2 is running. This will prevent ABENDs that can
occur when a thread references a fieldproc, which it loaded,
resumes after having been inactive, suspended, or held up for
some reason or some period of time.
Additional Keywords: SQLFIELDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55897
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 PM55897
DSNIENSR PM55897
DSNILDBP PM55897
DSNIREDR PM55897
DSNITEDI PM55897
DSNSVBK PM55897
DSNSVPL PM55897
DSNTSTRT PM55897
1 DSNXIFLM PM55897
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55897 DSNIDCML DSNIENSR DSNILDBP DSNIREDR DSNITEDI DSNSVBK
DSNSVPL DSNTSTRT DSNXIFLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDCML
DSNIENSR
DSNILDBP
DSNIREDR
DSNITEDI
DSNSVBK
DSNSVPL
DSNTSTRT
DSNXIFLM
LISTEND
UK77822 COVER LETTER END
UK77835 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61324 -
****************************************************************
* USERS AFFECTED: All users of IFI 306 with compressed tables. *
****************************************************************
* PROBLEM DESCRIPTION: QREP THREAD GOT ABEND04E DSNIBMCL:500B *
* OR ABEND04C IN DSNIDCML AFTER PARTITION *
* NUMBER HAD BEEN CHANGED TO SMALLER *
* VALUE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When decompressing log records for the partition table space, if
the original table space is dropped and a new table space is
re-created with a smaller number of partitions, decompression of
the log record for the original partition table space, using IFI
306, may encounter abend Abend04E in DSNIBMCL:5008 during
opening a partition which is higher than the current maximum
partition. This is possible when IFI 306 capture has fallen
behind and still processing an old partition table space's log
record. To return an error return code is a right action for DB2
to take but DB2 can avoid the abend by detecting that the table
space was dropped an re-created with a smaller number of
partition size. To avoid this abend, DB2 will return "invalid
dictionary (00C20064)" reason code to the IFI 306 application
for each log record that DB2 sees for the old partition table
space log record.
DB2 log is modified to return "invalid dictionary (00C90064)"
diagnostic reason code rather than abending with Abend04E in
DSNIBMCL:500B while decompressing log records for partition
table space.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM61324
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 PM61324
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61324 DSNIDCML
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDCML
LISTEND
UK77835 COVER LETTER END
UK77843 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56690 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of UNLOAD utility to *
* unload DATE column to TIMESTAMP EXTERNAL *
****************************************************************
* PROBLEM DESCRIPTION: When UNLOAD DATE column to TIMESTAMP *
* EXTERNAL and length not specified, *
* the output is 19 bytes long instead of *
* 26 bytes long. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When running UNLOAD utility using the following syntax:
UNLOAD TABLESPACE database.tablespace
FROM TABLE creator.table
(DATE POSITION(*) TIMESTAMP EXTERNAL)
SYSREC output is:
2011-01-01.00.00.00
But it should look like this:
2011-01-01.00.00.00.000000
The problem happens because we introduced timestamp precision in
DB2 10 for z/OS. DATE is considered with no precision, so zero
precision timestamp is always unloaded for DATE column. Although
timestamp precision is new feature, UNLOAD should generate 26
byte timestamp (precision 6) as default.
In addition, if the length specified for TIMESTAMP EXTERNAL is
26, as in the following syntax:
UNLOAD TABLESPACE database.tablespace
1 FROM TABLE creator.table
(DATE POSITION(*) TIMESTAMP EXTERNAL(26))
SYSREC output is:
2011-01-01.00.00.00 -- 19 byte timestamp plus 7 padding blanks
But it should look like this:
2011-01-01.00.00.00.000000
Unload should generate 26 byte timestamp for length specified
equal to 26 as well.
UNLOAD utility is modified to generate 26 byte timestamp
(precision 6) in SYSREC when no length specified or length
specified equal to 26 for UNLOAD DATE column to TIMESTAMP
EXTERNAL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56690
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM56690:
See PM56690 APAR/PTF text for additional information.
PM56690 changes the output in SYSREC for UNLOAD DATE column to
TIMESTAMP EXTERNAL with no length specified from 19 byte
timestamp to 26 byte timestamp; with length specified equal to
26, the output is changed from 19 byte timestamp plus 7 padding
blanks to 26 byte timestamp.
New applications or procedures developed on DB2 10 for z/OS
using the UNLOAD output may be affected by this modification and
may need to be changed accordingly.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULVA PM56690
DSNUUUFA PM56690
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56690 DSNUULVA DSNUUUFA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULVA
DSNUUUFA
LISTEND
UK77843 COVER LETTER END
UK77844 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58875 -
****************************************************************
1 * USERS AFFECTED: All DB2 10 for z/OS users of UNLOAD utility *
* unloading LOB data using FRVs *
****************************************************************
* PROBLEM DESCRIPTION: Incorrout may occur during an UNLOAD *
* from a table with a LOB column if the *
* data is in reordered row format (RRF) *
* and the UNLOAD uses (a) File Reference *
* Variable(s) (FRV) to unload the LOB *
* data. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
The UNLOAD utility, using FRVs, unloaded LOB data from a table
which is in reordered row format. Some of the nonzero LOB data
did not get unloaded, resulting in an FRV name of zeros
blanks instead of a valid HFS file or PDS member name.
The problem happened because UNLOAD improperly used an internal
flag setting for LOB column processing for RRF table spaces.
Additional Keywords:DB2INCORR/K
UNLOAD utility is modified to correct the reported problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58875
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 PM58875
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58875 DSNUULVA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULVA
LISTEND
UK77844 COVER LETTER END
UK77857 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58732 -
****************************************************************
* USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who *
* are also using IDAA ( IBM DB2 Analytics *
* Accelerator ) *
****************************************************************
* PROBLEM DESCRIPTION: This APAR contains the following fixes *
* for DB2 IDAA support: *
* *
* 1. Before this APAR, a query with at *
* least one common table expression *
1 * (CTE) and converted query length *
* greater than 32K bytes would return *
* SQLCODE -901 when offloaded to IDAA. *
* *
* 2.Before this APAR, a query with at *
* least one UNION, UNION ALL, *
* INTERSECT, INTERSECT ALL, EXCEPT, *
* EXCEPT ALL with a SELECT list item *
* that involves an aggregate function *
* for a decimal, date, time, or *
* timestamp result column would *
* return SQLCODE -904 when offloaded to *
* IDAA. *
* *
* 3. When user requests DB2 IDAA offload *
* for a query run from a DB2 package *
* that is bound REOPT(AUTO) and *
* the query validly does not qualify *
* for IDAA offload but is run in DB2 *
* instead, the following DB2 application *
* abend is possible during a second or *
* later OPEN cursor when DB2 does an *
* implicit reoptimization re-prepare of *
* the query for the Dynamic Statement *
* Cache: *
* ABEND04E RC00E70005 at DSNXERT :P115 *
* *
* 4. When using DB2 DSNTEP4 to run *
* dynamic SQL queries and user requested *
* IDAA offload for those queries, and *
* Dynamic Statement Caching is not *
* active, the following SQL error *
* invalidly occurred: *
* SQLCODE -249 SQLERRP = DSNLXRSQ *
* *
* 5. DB2 does not support IDAA offload *
* for a dynamic SQL query that is *
* on the same input line that begins *
* with an SQL simple comment (--) *
* and a linefeed is used to separate *
* the SQL simple comment from the *
* SQL query. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR contains the following fixes for DB2 IDAA offload
support of queries:
.
1. Before this APAR, a query with at least one common table
expression (CTE) and converted query length greater than 32K
bytes would return SQLCODE -901 when offloaded to IDAA. To
determine the converted query length, EXPLAIN the query and
select LENGTH(QI_DATA) from DSN_QUERYINFO_TABLE.
.
2.Before this APAR, a query with at least one UNION, UNION ALL,
1 INTERSECT, INTERSECT ALL, EXCEPT, EXCEPT ALL with a SELECT list
item that involves an aggregate function for a decimal, date,
time, or timestamp result column would return SQLCODE -904 when
offloaded to IDAA.
For a date, time or timestamp result column, the SQLCODE -904
is returned when offloaded to IDAA only if one of the SELECT
list items invovles a constant.
For example:
SELECT MAX('02/24/2012')
FROM T1
UNION ALL
SELECT MAX(C15DATE)
FROM T2;
For a decimal result column, the SQLCODE -904 is always
returned when offloaded to IDAA.
For example:
SELECT MAX(C8DECIMAL)
FROM T1
UNION ALL
SELECT MAX(C8DECIMAL)
FROM T2;
.
3. The user requested DB2 IDAA offload for a query from a DB2
package that is bound with bind option REOPT(AUTO) and DB2
Dynamic Statement Caching ( DSC ) is active. For whatever
valid reason the query is not eligible for IDAA offload and is
cached in the DSC and run in DB2 instead. During the second or
later OPEN cursor for the query running in DB2, the following
DB2 application abend is possible when DB2 does an implicit
reoptimization re-prepare of the query for the DB2 DSC (due to
the REOPT(AUTO) behavior):
ABEND04E RC00E70005 at DSNXGRDS . DSNXERT :P115
The DB2 abend occurred because DB2 did not correctly handle
the implicit reopt re-prepare for this query that was not
offloaded to IDAA. This REOPT(AUTO) problem only occurs when
the user has requested IDAA offload and DB2 validly does not
offload the query.
.
4. When using DB2 DSNTEP4 to run dynamic SQL queries and user
requested IDAA offload for those queries, and Dynamic Statement
Caching (DSC) is not active, the following SQL error occurred:
DSNT408I SQLCODE = -249, ERROR: DEFINITION OF ROWSET ACCESS
FOR CURSOR <unknown> IS INCONSISTENT WITH THE FETCH
ORIENTATION CLAUSE SPECIFIED
DSNT418I SQLSTATE = 24523 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNLXRSQ SQL PROCEDURE DETECTING ERROR
.
This error is issued by DB2. The error does not occur when DSC
is active.
.
DSNTEP4 default cursor behavior is ROWSET and 100 rows for
a fetch. DB2 IDAA offload is not supported for ROWSET queries
and multi-row fetching, so DB2 does not offload such queries
(by design). Instead, DB2 runs the query in DB2. However,
the query should not have failed with SQLCODE249 but should have
run successfully in DB2. If DSC is active in this scenario,
1 the query runs successfully. The SQLCODE249 occurred invalidly
because, when DSC is not active DB2 did not correctly handle
the ROWSET query and the SQLCODE249 resulted. It is not a TEP4
error or problem.
.
This SQLCODE249 can also occur if another application or vendor
product attempted to run a query with ROWSET in this same IDAA
offload request scenario.
.
5. An SQL simple comment starts with the characters '--', and
any characters that follow '--' on the same input line are
considered as a comment, even if what follows is an SQL
statement. However, if a linefeed character is embedded or
used on that input line to separate the comment from the
SQL statement specified, then the SQL statement is not
considered part of the SQL simple comment.
In this linefeed case, if that simple comment line is input
for a dynamic SQL statement and the SQL statement specified
is a query, DB2 does not consider the dynamic query for
IDAA offload.
1. Code is fixed to offload a query with at least one CTE
and converted query length greater than 32K bytes if there
are no other restrictions preventing the query from offloading.
.
2. Code is fixed to offload a query involving a UNION,
UNION ALL, INTERSECT, INTERSECT ALL, EXCEPT, EXCEPT ALL with
a SELECT list item that is a decimal, date, time, or timestamp
result column.
.
3. DB2 REOPT(AUTO) support was changed to correctly handle
the DB2 implicit reoptimization re-prepare on OPEN for a query
that did not qualify for DB2 IDAA offload.
.
4. DB2 was changed to correctly run a ROWSET query in DB2 when
the user requested IDAA offload and Dynamic Statement Caching
is not active. The ROWSET query is correctly *not* offloaded to
IDAA.
.
5. DB2 now supports IDAA offload for a dynamic SQL query that
is on the same input line that begins with an SQL simple
comment (--) and a linefeed is used to separate the SQL
simple comment from the SQL query.
.
Additional Search Keywords:
IDAAV2R1/K SQLCODE904 SQLCODE901 SQLUNION SQLUNIONALL
SQLINTERSECT SQLINTERSECTALL SQLEXCEPT SQLEXCEPTALL
REOPT AUTO SQLDYNSTMTCACHE AB04E OFFSETP115 00E70005
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58732
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDP PM58732
DSNXONZC PM58732
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58732 DSNXEDP DSNXONZC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDP
DSNXONZC
LISTEND
UK77857 COVER LETTER END
UK77877 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58723 -
****************************************************************
* USERS AFFECTED: All HIR2220 (IRLM 220) and HIR2230 (IRLM230) *
* users DATASHARING SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: Raise the limit of number of Lock Table *
* Entries (LTEs) in the CF lock structure *
* to the maximum (2G) supported by XES. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM limits the number of CF lock structure table entries (LTEs)
to a maximum value of 1G. Since the maximum LTEs supported by
XES is 2G, IRLM should not limit the LTEs and let it expand if
the lock structure size could support a bigger lock table size.
IRLM may not be able to start if the lock structure size in the
CFRM policy is set to a value greater than 4G. IRLM global
initialization may timeout and ABENDU2025 in DXRRL732.
MSGDXR133I is also issued by IRLM for global initialization
timeout.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
IRLM will support up to 2G Lock Tables Entries for the CF lock
structure. IRLM will also support lock structure SIZE/INITSIZE
greater than 4G as specified in the CFRM policy for the lock
structure.
Following references in the DB2 books will be updated:
1. IRLM Messages and Codes:
Explanation of DXR177I message
F irlmproc,SET,TRACE=nnn
LTE
When nnnnnnnn is LTE, xxxx is a value between 0 and 2048
and represents the number of Lock Table Entries available
1 in the Coupling Facility. The value must be either zero or
a power of two with each increment representing 1048576
entries.
2. DB2 Commands
Start irlmproc
LTE= nnnn
Specifies the number of lock table entries that are
required in the units of 1048576 entries. LTE= can
have a value of blank,zero, or any exact power of two
up to 2048(inclusive).
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM58723
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL010 PM58723
DXRRL020 PM58723
DXRRL1S1 PM58723
DXRRL240 PM58723
DXRRL710 PM58723
DXRRL712 PM58723
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58723 DXRRL010 DXRRL020 DXRRL1S1 DXRRL240 DXRRL710 DXRRL712
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL010
DXRRL020
DXRRL1S1
DXRRL240
DXRRL710
DXRRL712
LISTEND
UK77877 COVER LETTER END
UK77885 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59540 -
****************************************************************
* USERS AFFECTED: All HIR2220(IRLM220) and HIR2230(IRLM230) *
* users. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM ABEND0C4 in DXRRL24F while *
* performing deadlock processing. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
Under certain scenarios, the number of waiters can be very
1 big. With large number of waiters, the size of the TWFG
(transaction wait-for graph), which is built by the deadlock
process, can exceed 16 mega-bytes (16 MB). IRLM deadlock
logic fails to clear storage that is beyond 16 MB. The
un-initialized storage causes the ABENDS0C4.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code in deadlock logic is modified to initialize storage
that is bigger than 16 MB.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM59540
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL24C PM59540
DXRRL24I PM59540
DXRRL247 PM59540
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59540 DXRRL24C DXRRL24I DXRRL247
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL24C
DXRRL24I
DXRRL247
LISTEND
UK77885 COVER LETTER END
UK77887 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51208 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REORG *
* TABLESPACE SHRLEVEL CHANGE on tables *
* that have data types TRANSACTION START ID, *
* ROW BEGIN or ROW END *
****************************************************************
* PROBLEM DESCRIPTION: Problem 1: *
* ---------- *
* ABEND04E RC00C90101 DSNINUKY ERQUAL5002 *
* during REORG TABLESPACE SHRLEVEL CHANGE *
* log apply phase, while processing SQL *
* UPDATE log record of table containing *
* TRANSACTION START ID, ROW BEGIN or ROW *
* END column *
* *
* Problem 2: *
* ---------- *
1 * For table containing TRANSACTION START *
* ID or ROW BEGIN column, applying SQL *
* INSERT log records during REORG *
* TABLESPACE SHRLEVEL CHANGE log *
* apply phase mistakenly generates new *
* values for TRANSACTION START ID and *
* ROW BEGIN column *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During online REORG log apply phase, an SQL UPDATE log record
was being applied for a table that contained a TRANSACTION START
ID, ROW BEGIN or ROW END column (which typically means it is a
temporal table but it need not be). The aforementioned abend
took place because the code was not allowing for an 'update' of
such non-updatable columns.
However, during online REORG, the code should allow for their
update because the column values come from the log record.
For the same kinds of tables, there is also a second problem:
applying SQL INSERT log records during REORG TABLESPACE SHRLEVEL
CHANGE log apply phase mistakenly generates new values for
TRANSACTION START ID and ROW BEGIN columns. The reason for this
issue is that a communication bit between utility and data
manager (regarding avoiding the generation of such columns) was
mistakenly off.
Code has been changed to allow for an update of TRANSACTION
START ID, ROW BEGIN and ROW END columns during online REORG log
apply phase.
Also, code has been changed to turn on the bit to avoid
generating TRANSACTION START ID and ROW BEGIN columns during
REORG log apply of SQL INSERT log records, so that new values
are not generated.
Additional keywords: SQLSPTT SQLBITEMPORAL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51208
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 PM51208
DSNIMRST PM51208
DSNINUKY PM51208
DSNURLAP PM51208
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51208 DSNILREP DSNIMRST DSNINUKY DSNURLAP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
1 DSNIMRST
DSNINUKY
DSNURLAP
LISTEND
UK77887 COVER LETTER END
UK77907 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59711 -
****************************************************************
* USERS AFFECTED: All V10 DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E50001 in DSNB1TMR *
* ABEND0F8 RC00000010 in DSNB1TMR *
* ABEND04E RC00C2010F in DSNB1LTS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a rare scenario when a latch waiter is timed out and
dequeued, a serialization problem on the timer queue causes the
timer service task to abend. This may lead to a secondary abend
and bring down DB2.
DB2 has been fixed to properly serialize the operation of
dequeuing a timed out latch waiter.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59711
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1TMR PM59711
DSNB1ULT PM59711
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59711 DSNB1TMR DSNB1ULT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1TMR
DSNB1ULT
LISTEND
UK77907 COVER LETTER END
UK77919 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58113 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the LOAD and *
* REORG utility. *
****************************************************************
1 * PROBLEM DESCRIPTION: ABEND04E RC00E20005 DSNSVBK OFFSET1AB6 *
* during a LOAD REPLACE of a compressed *
* segmented table space with multiple *
* tables. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a LOAD REPLACE INTO TABLE...WHEN on a segmented
compressed table space into multiple tables. The LOAD abended
in the RELOAD phase with an ABEND04E RC00E20005 DSNIRLPG
DSNSVBK x'1AB6'.
The abend was due to a storage overlay caused by a work area
for data records with an inadequate length.
This problem can also occur during the REORG utility.
Additional Symptoms:
ABENDS0C4 DSNSVBK OFFSET1302 x'1302'
ABEND0C4 DSNUGSTA OFFSET1D48 x'1D48'
ABEND04E RC00E2002F DSNSVSFM OFFSET0734 x'0734'
Code was modified to obtain the correct size work area.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58113
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
APAR PM54727 has corrected an issue where REORG REBALANCE on a
partitioned table space with an editproc defined can result in
corrupted limit key values in the DB2 catalog and directory.
In the event that the above limit key corruption has occurred,
user can repair the catalog/directory by manually altering the
limit keys to the correct value on the affected table space /
partitions, and then run a REORG TABLESPACE utility to remove
the restrictive REORP status.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFIT PM58113
DSNURPLI PM58113
DSNURPUI PM58113
DSNURWBF PM58113
DSNURWI PM58113
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58113 DSNURFIT DSNURPLI DSNURPUI DSNURWBF DSNURWI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFIT
DSNURPLI
DSNURPUI
DSNURWBF
DSNURWI
LISTEND
UK77919 COVER LETTER END
1
UK77920 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52237 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS XML users of *
* the XMLTABLE function. *
****************************************************************
* PROBLEM DESCRIPTION: An SQLCODE904 (or -904) with reason *
* code rc00D50001 or rc00D50002 can be *
* issued from DSNXRXML when using an *
* XMLTABLE function, such as XMLPARSE, as *
* the argument of the XMLTABLE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An SQLCODE904 (or -904) with reason code rc00D50001 or
rc00D50002 can be issued from DSNXRXML when using the XMLTABLE
function, such as XMLPARSE, as the argument of the XMLTABLE
function.
The following example can illustrate the problem.
SELECT X.*
FROM T1,
XMLTABLE('/a/b'
PASSING XMLPARSE(C1)
COLUMNS C INTEGER PATH 'c') AS X ;
For each row returned from XMLTABLE, the XMLPARSE function
will be called to parse the XML document (C1) which can
utilize a lot of storage. However, for each XML document,
we only need to parse once. The argument of the XMLTABLE
function should be called only once for each row in T1.
But currently it is called for each row returned by XMLTABLE.
Please note. The amount of storage used is dependent on the
size of the XML document and how many rows are returned from the
XMLTABLE function.
The code in DB2 which processes the XMLTABLE function is
modified to parse the XML document only once. This can
significantly lessen the amount of storage the XMLTABLE function
utilizes. This will reduce the chance of receiving a 'resource
unavailable' condition, i.e. an SQLCODE -904, with reason code
rc00D50001 or rc00D50002.
Additional Keywords: SQLXML SQLXMLTABLE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52237
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
***Action for PM52237
See PM52237 APAR/PTF text for additional information about
why a REBIND is necessary.
Apar PM52237 reduces the XML storage usage so as not to exceed
the specified zparm limit. As a result, this will reduce the
chance of receiving an SQLCODE904 (or SQLCODE -904), a Resource
Unavailable condition with reason code rc00D50001 or rc00D50002,
which means excessive storage used for XMLTABLE.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEMG1 PM52237
DSNXGRTS PM52237
DSNXREOJ PM52237
DSNXREO9 PM52237
DSNXRFN PM52237
DSNXRFN9 PM52237
DSNXROJ1 PM52237
DSNXROJ9 PM52237
DSNXRSFN PM52237
DSNXRSGB PM52237
DSNXRSG9 PM52237
DSNXRSN9 PM52237
DSNXRT1J PM52237
DSNXRT19 PM52237
DSNXSBUC PM52237
DSNXSIND PM52237
DSNXSING PM52237
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52237 DSNXEMG1 DSNXGRTS DSNXREOJ DSNXREO9 DSNXRFN DSNXRFN9
DSNXROJ1 DSNXROJ9 DSNXRSFN DSNXRSGB DSNXRSG9 DSNXRSN9
DSNXRT1J DSNXRT19 DSNXSBUC DSNXSIND DSNXSING
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEMG1
DSNXGRTS
DSNXREOJ
DSNXREO9
DSNXRFN
DSNXRFN9
DSNXROJ1
DSNXROJ9
DSNXRSFN
DSNXRSGB
DSNXRSG9
DSNXRSN9
1 DSNXRT1J
DSNXRT19
DSNXSBUC
DSNXSIND
DSNXSING
LISTEND
UK77920 COVER LETTER END
UK77942 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61894 -
****************************************************************
* USERS AFFECTED: All DB2 for zOS users of DGTTs (Declared *
* Global Temporary Tables). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 ERQUAL5002 in *
* DSNGDCMT following a cancel of a *
* read-only thread using DGTTs. DB2 *
* then terminated with RC00F30420. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A read-only thread using DGTTs was canceled during COMMIT-2
processing after the COMMIT-2 broadcast, but before the
progress flags in the ACE were reset. The residual progress
flags resulted in an ABEND04E RC00C90101 in DSNGDCMT during
thread deallocation. This caused DB2 to terminate with
RC00F30420.
DSNVIALC has been changed to ensure the ACE progress flags
have been reset prior to the deallocation broadcast.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61894
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVIALC PM61894
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61894 DSNVIALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVIALC
LISTEND
UK77942 COVER LETTER END
UK77953 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM51171 -
1 ****************************************************************
* USERS AFFECTED: All users of IFCID 58 on DB2 10 (for z/OS) *
****************************************************************
* PROBLEM DESCRIPTION: 1. Some execution statistics are not *
* recorded for statement-level *
* performance metrics pointed to by *
* QWT02R30 in IFCID58. *
* . *
* 2. IFCID 59 was not being cut on *
* certain EXEC SQL OPEN DRDA scenarios. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. IFCID 58 reports execution statistics for statement level
traces. In several SQL statements, certain execution statistics
reported for the following IFCID058 fields in the QWT02R30
data block were not being recorded. The statements affected
were the SELECT, INSERT, UPDATE, and MERGE SQL statements for
the following QWT02R30 fields.
.
QW0058ST (number of sorts)
QW0058IS (number of index scans)
QW0058TB (number of table space scans)
.
2. DB2 10 for z/OS RDA protocol bundles the initial SQL FETCH
query block within the SQL OPEN statement.
For this bundled SQL FETCH statement, an IFCID 59 trace record
was not recorded. Instead, DB2 may record the following trace
records:
.
Scenario 1:
IFCID65 OPEN (bundled SQL FETCH)
IFCID58 END
.
Scenario 2:
IFCID65 OPEN (bundled SQL FETCH)
IFCID66 CLOSE
IFCID58 END
DB2 code has been modified to update the QWT02R30 fields
stated in the PROBLEM SUMMARY section reported by the
IFCID 58 trace record.
.
DB2 code has been modified to record an IFCID 59 trace record
when the DRDA protocol has determined to bundle the SQL FETCH
query block within the SQL OPEN statement.
.
RELATED KEYWORDS: PERFM SQLSTATS IFCID58 IFCID59
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM51171
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 DSNXERT PM51171
DSNXSFTP PM51171
DSNXSORI PM51171
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM51171 DSNXERT DSNXSFTP DSNXSORI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXERT
DSNXSFTP
DSNXSORI
LISTEND
UK77953 COVER LETTER END
UK77956 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60173 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS version 9 and 10 users of *
* sensitive static scrollable cursors. *
****************************************************************
* PROBLEM DESCRIPTION: Unexpected SQLCODE +222 or incorrect *
* output while fetching records by a *
* sensitive static scrollable cursor to *
* tables in compressed table space or *
* tables with edit procs defined on. *
* Additional keywords: DB2INCORR/K, *
* SQLCODE222 *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Unexpected SQLCODE +222 or incorrect output was met when
following conditions were met:
1. CURSOR was declared as SENSITIVE STATIC SCROLLABLE,
2. Query contained WHERE clause,
3. No table columns in select list,
4. Table resided in compressed tablespace, OR the table had
edit proc defined on,
5. Index scan was applied.
The reason is that DB2 didn't decompress or decode the record
before reevaluating the record using the WHERE clause.
DB2 code has been fixed to make sure records will be
decompressed or decoded before reevaluation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60173
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 PM60173
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60173 DSNIRSET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRSET
LISTEND
UK77956 COVER LETTER END
UK77963 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61424 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 RESTART FAILED WITH STORAGE ABEND *
* 04E RC00E2000C IN DSNSVSVB OFFSET0AC2 *
* AND ALL STORAGE USED FOR RESTART TABLE *
* STORAGE POOL WAS EXHAUSTED. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DB2 restart, Data Manager (DM) builds the Data Base
Restart Table (DBRT) entry for each active (R/W state) page set.
These entries are later used to open the pageset if necessary.
However, each DBRT entry gets very large if there are
Non-Partition Index (NPI) involved, especially, the NPIs on
Partition By Growth (PBG) table spaces. If the DB2 restart
involves several thousands of such PBGs and several thousands
NPIs then the storage pool (ACOMPH12 or ACOMPH20) used to build
DBRT entries gets exhausted which results in DB2 abnormally
terminated with reason code RC00E2000C. To avoid this storage
constraint during DB2 restart, Data Manager Restart (DMRR) logic
will acquire the minimum amount of storage for control blocks
(PDA/PDP) to open the data set. This will significantly reduce
the storage needed to build all the necessary control blocks
(DBRT entry, PDA, PDP), hence avoid the global out of storage
condition during DB2 restart.
DB2 restart logic is modified to reduce the storage usage to
avoid global storage shortage which prevents DB2 from
restarting.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61424
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1OPP PM61424
DSNIERST PM61424
DSNIRCSB PM61424
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61424 DSNB1OPP DSNIERST DSNIRCSB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1OPP
DSNIERST
DSNIRCSB
LISTEND
UK77963 COVER LETTER END
UK77992 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59835 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of OLAP MIN and *
* MAX specifications *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXGRDS *
* DSNXRWND M190 for an OLAP specification *
* moving MIN or MAX *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The ABEND04E RC00E70005 at DSNXGRDS DSNXRWND M190 for the
OLAP specification moving MAX can occur when the first value
in the window is the smallest possible value for the input
expression's data type. For example, the smallest DATE value
is '0001-01-01' :
CREATE TABLE T1 (DATECOL DATE, C2 INT);
INSERT INTO T1 VALUES('0001-01-01',1);
SELECT MAX(DATECOL) OVER(ORDER BY C2)
FROM T1;
The abend can occur for OLAP moving MIN when the first value
in the window is the largest possible value for the input
expression's data type. For example, the largest DATE value
is '9999-12-31' :
CREATE TABLE T1 (DATECOL DATE, C2 INT);
INSERT INTO T1 VALUES('9999-12-31',1);
SELECT MIN(DATECOL) OVER(ORDER BY C2)
FROM T1;
The abend may occur for any of the following input expression
data types: CHAR, GRAPHIC, DATE, TIME, TIMESTAMP, BINARY,
SMALLINT, DECFLOAT, DECIMAL, VARCHAR and VARGRAPHIC
DB2 has been corrected to set an internal field correctly
for the OLAP specifications MIN and MAX. This will prevent
1 the abend.
Additional keywords : SQLMIN SQLMAX
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59835
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRCSF PM59835
DSNXRGBJ PM59835
DSNXRRSQ PM59835
DSNXRSFJ PM59835
DSNXRSFN PM59835
DSNXRSGB PM59835
DSNXRSJ PM59835
DSNXRWND PM59835
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59835 DSNXRCSF DSNXRGBJ DSNXRRSQ DSNXRSFJ DSNXRSFN DSNXRSGB
DSNXRSJ DSNXRWND
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRCSF
DSNXRGBJ
DSNXRRSQ
DSNXRSFJ
DSNXRSFN
DSNXRSGB
DSNXRSJ
DSNXRWND
LISTEND
UK77992 COVER LETTER END
UK77996 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60856 -
****************************************************************
* USERS AFFECTED: All users of DB2. *
****************************************************************
* PROBLEM DESCRIPTION: Looping between CSECTs DSNTAAL and *
* DSNTBAB occurs during plan autobind *
* attempts. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
By default, DB2 10 for z/OS automatically rebinds a plan that
was bound with DBRMs and converts it to use a package list.
The test to see if the plan was bound with DBRMs is incorrectly
dependent on a structure that may not exist, which could result
in an automatic rebind attempt. Automatic rebind process will
1 verify if the plan was bound with DBRMs. If it determines that
the plan was not bound with DBRMs, automatic rebind will not
occur. This results in an infinite loop in agent allocation and
automatic rebind modules (CSECTs DSNTAAL and DSNTBAB).
DB2 has been modified to correctly test for DBRMs during plan
allocation.
Keywords: AUTOBIND AUTBND LOOPING
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60856
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTAAL PM60856
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60856 DSNTAAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTAAL
LISTEND
UK77996 COVER LETTER END
UK77997 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57745 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of an SQL *
* statement that returns data in the type of *
* DBCLOB. *
****************************************************************
* PROBLEM DESCRIPTION: Storage overlay could happen for an *
* SQL statement that returns data in the *
* type of DBCLOB. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Storage overlay could happen for an SQL statement that returns
data in the type of DBCLOB.
An example is shown below:
CREATE TABLE TBDBCLOB
(CINT INT,
CSTRING VARCHAR(50),
CDBCLOB DBCLOB(125)
);
SELECT CINT, CSTRING, CDBCLOB
FROM TBDBCLOB
1 ORDER BY 1, 2;
DB2 did not correctly process the item CDBCLOB in the select
list, which might cause the storage overlay.
DB2 has been modified to correctly process the DBCLOB type item
in the select list, so there will be no the storage overlay.
Additional keywords: SQLLOB SMCOVERLAY DB2OVRLAY/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57745
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM57745:
See PM57745 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57745 corrects a problem that storage overlay could happen
for an SQL statement that returns data in the type of DBCLOB.
To make this fix effective for a static application, it must 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 PM57745
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57745 DSNXOSL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSL
LISTEND
UK77997 COVER LETTER END
UK78003 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59811 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS Utility Users *
****************************************************************
* PROBLEM DESCRIPTION: DB2 internal change to support future *
* functions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR does not address or fix any current problem in DB2.
It contains the changes in support of future functions.
This apar does not have any external symptoms.
1
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59811
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDIS PM59811
DSNUGTE0 PM59811
DSNUGUCC PM59811
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59811 DSNUGDIS DSNUGTE0 DSNUGUCC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDIS
DSNUGTE0
DSNUGUCC
LISTEND
UK78003 COVER LETTER END
UK78004 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57420 -
****************************************************************
* USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who *
* use ISOLATION(CS) with CURRENTDATA(YES) *
****************************************************************
* PROBLEM DESCRIPTION: SQL code -811 or +100 may be issued *
* intermittently for a singleton, *
* non-cursor SELECT when using *
* ISOLATION(CS) and CURRENTDATA(YES). *
* Even though there is a single row *
* in the expected result, -811 or *
* +100 may be issued intermittently *
* on the SELECT when there is *
* concurrent update activity on the *
* table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQL code -811 or +100 may be issued intermittently for a
singleton, non-cursor SELECT when using ISOLATION(CS) and
CURRENTDATA(YES). Even though there is a single row in the
expected result, -811 or +100 may be issued intermittently
on the SELECT when there is concurrent update activity on the
table. Because lock avoidance is used in this situation,
the concurrent update activity may cause the row to not
be seen, or to be read twice, resulting in +100 or -811,
respectively.
1 Additional Keywords:
SQLCODE811 SQLCODE100
Code is changed so that a S page/row lock will be obtained for
a singleton SELECT with ISOLATION(CS) and CURRENTDATA(YES).
As a result, you may experience less concurrency for such
queries when the lock is held.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57420
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM57420:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM57420 corrects a problem where lock avoidance is being
used for a singleton, non-cursor SELECT when ISOLATION(CS)
is used with CURRENTDATA(YES). Concurrent updates may yield
inconsistent results for the SELECT.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM56626:
See PM56626 APAR/PTF text for additional information about
why a REBIND is necessary.
PM56626 allows users to define a dynamic scroll cursor whose
SELECT statment contains a subquery such that the base object
of the outer subselect, and of the subquery, is the same, but
with the conditions that (1) FOR FETCH ONLY is specified in
the SELECT statement, and (2) the base object is accessed via
the index to avoid any sort or materialization.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM51623:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM51623 corrects a problem that an inefficient access path may
be chosen for a DELETE statement against a VIEW on which an
INSTEAD OF DELETE trigger is defined.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
1 affected by this change.
DB2BIND:
***Action for PM30690:
See PM30690 APAR/PTF text for additional information about
why a REBIND is necessary.
PM30690 corrects a problem of an infinite loop for a MERGE
statement with update.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGPS PM57420
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57420 DSNXOGPS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGPS
LISTEND
UK78004 COVER LETTER END
UK78007 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60622 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/Os *
* users of REORG SHRLEVEL NONE PART. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU340I - ERROR LOADING INDEX, *
* DUPLICATE KEY, during a REORG SHRLEVEL *
* NONE PART m:n on a partitioned table *
* space with a unique non-partitioned *
* index running concurrently with SQL. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A REORG TABLESPACE SHRLEVEL NONE PART was run on a table with
unique NPI's concurrently with SQL. The REORG failed with RC8
and DSNU340I - ERROR LOADING INDEX, DUPLICATE KEY. The
duplicate keys were keys inserted into parts of the NPI that
were not being REORGed.
Current design allowed a window where these duplicate NPI keys
could be inserted.
REORG TABLESPACE SHRLEVEL NONE has been changed to perform
pseudo deletes of unique and unique where not null NPI index
keys instead of physical deletes, to catch colliding inserts
1 and updates to partitions that are not part of the REORG.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60622
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKREST PM60622
DSNURBXA PM60622
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60622 DSNKREST DSNURBXA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKREST
DSNURBXA
LISTEND
UK78007 COVER LETTER END
UK78030 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60720 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C1-00000001 can occur at a *
* DB2 10 for z/OS system after APAR *
* PM50436 (PTF UK76105) is applied. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DB2 10 for z/OS system, acting as a requester, connects to
a remote server via TCPIP. During the connect process, DB2
invokes a z/OS TIMEUSED macro with ECT(YES) parameter in order
to operate in a 64-bit stack environment.
An ECT(YES) related instruction is not available on some older
hardware that the DB2 10 for z/OS system can run on, and the
absence of the hardware instruction support cause the reported
0C1 abend.
DB2 has been changed to use the z/OS TIMEUSED service such that
it will operate in all hardware environments.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60720
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCITR PM60720
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60720 DSNLCITR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCITR
LISTEND
UK78030 COVER LETTER END
UK78100 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61435 -
****************************************************************
* USERS AFFECTED: All users of DB2. *
****************************************************************
* PROBLEM DESCRIPTION: LONG RUNNING DB2 RESTART DURING GRECP *
* RECOVERY DUE TO INFLIGHT UR FROM FLA *
* TASK. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During LPL or GRECP recovery, when needed, Data Space Manager
(DSM) may need to add a new volume for a data set. This event is
rare but when it happens it is logged. However, today, it is
logged as UR related. This causes a new UR created. If the long
running recovery job is cancelled or abnormally terminated, it
may leave the UR in in-flight state. During restart, DB2 will
process all the log records associated with the UR created
during GRECP recovery. This resulted in excessive long DB2
forward and backward recovery phase.
The DB2 logic is modified so that adding volume will be logged
as non-UR related so no new UR is created just to log this
event.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61435
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRWHL PM61435
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61435 DSNIRWHL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRWHL
LISTEND
UK78100 COVER LETTER END
1
UK78109 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61445 -
****************************************************************
* USERS AFFECTED: All users of Restore System Utility. *
****************************************************************
* PROBLEM DESCRIPTION: Abend04E RC00E20005 in module *
* DSNIFLAF.DSNSVB+09AC during Restore *
* System log apply. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During Restore System log apply phase, when Fast Log Apply is
active, PBA (Agent Page set Block) entries for each object is
built and freed by log apply write task. When Restore system log
apply is terminated, the read task should not try to free the
storage. It will be freed by the write log apply task when it
completes its processing. That will avoid storage manager abend
when freeing the block which belongs to different CT pool.
The restore system log apply logic is changed to avoid storage
manager abend by properly handling storage management.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61445
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIFLAF PM61445
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61445 DSNIFLAF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFLAF
LISTEND
UK78109 COVER LETTER END
UK78112 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59558 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of empty *
* LOBs as input to DB2 in a distributed *
* environment. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E20003 or RC00E20016 *
* from module DSNSVBK can occur when a *
* distributed application uses empty LOB *
* data as the input to DB2, if CCSID *
* conversion is needed between the input *
1 * LOB and the target object. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E20003 or RC00E20016 from module DSNSVBK can
occur when a distributed application uses an empty LOB as the
input to DB2, if CCSID conversion is needed between the input
LOB and the target data object.
The following example illustrates the problem.
1. Create an EBCDIC Table with a LOB column on a remote server.
CREATE TABLE T1 (ID INT, C1 CLOB(1M));
2. Use Java distributed application to insert empty LOB data for
Table T1.
String sql = "INSERT INTO T1(ID, C1) VALUES( ?, ? )";
PreparedStatement pst = con.prepareStatement(sql);
//0.xml is a empty file
java.io.File file1 = new java.io.File("0.xml");
for(int i=0;i<1000;i++)
{
pst.setInt(1, i);
//Empty LOB is inserted into column C1 and its length
//is not specified
pst.setAsciiStream(2,
new java.io.FileInputStream(file1),
-1);
pst.addBatch();
}
pst.executeBatch();
3. When the JAVA application is executed against the remote
server, the empty LOB being inserted into DB2 is in a streaming
format and CCSID conversion is needed for the LOB because JAVA
uses a CCSID 1208 encoding scheme and T1 is created with an
EBCDIC encoding scheme. DB2 (LOB manager) does not free the
pre-allocated conversion buffer for empty LOBs when a streaming
format is used. If this occurs frequently, this can result in a
memory leak which can lead to a "short-on-storage" condition
which can eventually result in an ABEND04E from DSNSVBK.
The code in DB2 is modified to free the pre-allocated conversion
buffer from LOB manager to prevent the creation of a memory leak
or "short-on-storage" condition.
1
Additional Keywords: SQLLOB SQLCCSID SQLSTORAGE DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59558
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOGETD PM59558
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59558 DSNOGETD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOGETD
LISTEND
UK78112 COVER LETTER END
UK78130 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61113 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of queries that perform a GROUP BY (sort) *
* for very large amounts of data. *
****************************************************************
* PROBLEM DESCRIPTION: A DB2 thread could not be cancelled *
* while looping in module DSNXSRCY which *
* is used for GROUP BY processing and *
* performs a bucket sort. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A DB2 thread could not be cancelled while looping in module
DSNXSRCY. The loop occurs while performing GROUP BY processing
using a bucket sort for a very large number of records.
This problem occurs when the counter of the number of deleted
rows from the input records exceeds 4G records. The variable to
handle this counter is limited because of its FIXED(32)
definition (or 4G), while the buffer for the deletion of the
actual rows has a FIXED(63) definition. This is a mismatch.
So, when a comparison check is performed to stop the processing
loop of input records for sort, once the 4G counter limit is
reached, the check will always fail because the counter becomes
an incorrect value (a small number). Hence, the loop continues.
Please note that the chance of hitting this loop is small as it
is dependent on a very large number of input records to be
processed for GROUP BY sort of which more than 4G are to be
1 discarded.
DB2 has been modified to redefine the counter field to be the
same as the definition for the number of rows to be deleted
field. This will prevent the loop from occurring.
Additional Keywords: SQLSORT SQLGROUPBY LOOPDSNXSRCY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61113
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSRCY PM61113
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61113 DSNXSRCY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSRCY
LISTEND
UK78130 COVER LETTER END
UK78134 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57731 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of *
* ALTER TABLE ALTER PARTITION ENDING AT *
****************************************************************
* PROBLEM DESCRIPTION: REORG may result in ABEND04E *
* RC00E70005 DSNIRFNX:5014 when *
* run subsequent to ALTER TABLE *
* ALTER PARTITION ENDING AT. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
REORG may result in ABEND04E RC00E70005 DSNIRFNX:5014,
incorrect output, or other unexpected results when run
subsequent to ALTER TABLE ALTER PARTITION ENDING AT because
DB2 failed to set affected partitions to REORG-Pending during
limit key alterations.
ALTER TABLE ALTER PARTITION ENDING AT has been modified to
set set affected partitions to REORG-pending when needed.
ADDITIONAL KEYWORDS:
INCORROUT
SQLALTER
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM57731
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 PM57731
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57731 DSNGDART
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDART
LISTEND
UK78134 COVER LETTER END
UK78166 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61055 -
****************************************************************
* USERS AFFECTED: All DB2 users in a data-sharing environment *
* using LOB columns. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNB250E DSNB5SCM A PAGE RANGE WAS *
* ADDED TO THE LOGICAL PAGE LIST *
* LPL TRACE ID=00000003 *
* LPL REASON TYPE=LOCK *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There is a timing window between I/O request building and
I/O request processing for a synchronous DASD write. When this
timing window is hit by a cancel, we lose the tracking
information that is needed by the I/O recovery routine to unlock
the pages. When another agent tries to access these pages
unsuccessfully, these locked pages are placed in the logical
page list (LPL).
DB2 has been fixed to preserve the tracking information for the
recovery routine to properly process and unlock the pages.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61055
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5CMX PM61055
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61055 DSNB5CMX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNB5CMX
LISTEND
UK78166 COVER LETTER END
UK78170 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM59155 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of DATE and TIME exits. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E rc00E40340 can occur at *
* location DSNUTILA.DSNURWBG+61A0 *
* (OFFSET61A0) when using the DB2 LOAD *
* utility and a DATE exit. *
* *
* An SQLCODE185 can be issued from *
* DSNXOLTD location -320 for an SQL *
* INSERT statement when using a DATE *
* exit. *
* *
* An unexpected SQLCODE -181 (SQLCODE181) *
* can occur from DSNXRTIM location 116 *
* when using a DATE exit. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E rc00E40340 can occur at location DSNUTILA DSNURWBG
+61A0 (OFFSET61A0) when using the DB2 LOAD utility and a DATE
exit. In the reported case an EBCDIC DATE exit DSNXVDTX was
installed. An unexpected SQLCODE185 is returned to DB2
utilities prior to the abend.
Also, an SQLCODE185 (or SQLCODE -185) can be issued from
DSNXOLTD location -320 for an SQL INSERT statement when using a
DATE exit.
The problem is contingent on employing a DATE exit, and
populating a table that has at least a DATE and TIME column
defined as
DATE WITH DEFAULT NULL
TIME WITH DEFAULT NULL
For both problems, the failure occurs because DB2 incorrectly
checks a DECP DATE exit specification in a cast character-to-
time conversion routine instead of a DECP TIME exit
specification. As a result, the default EBCDIC time exit
DSNXVTMX is invoked when it should not be since no time exit was
installed. The exit returns a rc16 and the conversion routine
then incorrectly returns a false SQLCODE185 or -185.
1
The following simple example can illustrate how the failure can
occur for an SQL INSERT statement.
Step 1. Specify the following DSNHDECP settings
SCCSID=277
DATE=LOCAL
DATELEN=10
TIME=ISO
TIMELEN=0
Step 2. Setup and install local DATE exits.
Step 3. Define the following simple Table.
CREATE TABLE TABLE1
(STATUS_DATE DECIMAL(8 , 0) NOT NULL
,STATUS_TYPE CHARACTER(1) FOR SBCS DATA NOT NULL
,PROCESS_DATE DATE WITH DEFAULT NULL
,PROCESS_TIME TIME WITH DEFAULT NULL
) CCSID EBCDIC ;
Step 4. Insert the following two rows into Table TABLE1.
INSERT INTO TABLE1 VALUES (0,'D','20110307',' ');
INSERT INTO TABLE1 VALUES (0,'D','20110513','16.03.46');
Step 5. An SQLCODE -185 can occur from DSNXOLTD location -320.
Please note that the same problem is likely to occur if using
an ASCII (DSNXVDTA) or UNICODE (DSNXVDTU) DATE exit.
Additionally, for DB2 10 for z/OS users, an unexpected SQLCODE
-181 (SQLCODE181) can occur from DSNXRTIM location 116 when
using a DATE exit. This error does not occur in v9.
The failure occurs because DB2 is not checking the converted
source length properly following the DATE exit invocation. As a
result, an incorrect length is checked leading to an unexpected
SQLCODE.
The following examples illustrate some simple failing cases.
When using DSNXVDTX the EBCDIC DATE exit.
SELECT DATE('1-02-12') FROM SYSIBM.SYSDUMMY1;
SELECT DATE('01-2-12') FROM SYSIBM.SYSDUMMY1;
1
Result: SQLCODE -181 DSNXRTIM loc 116
When using DSNXVDTA the ASCII DATE exit.
SELECT DATE('1-02-12') FROM SYSIBM.SYSDUMMYA;
SELECT DATE('01-2-12') FROM SYSIBM.SYSDUMMYA;
Result: SQLCODE -181 DSNXRTIM loc 116
In each of the above cases, if the DATE exit works properly to
validate the input DATE format, DB2 should support the desired
format and check the proper converted source length according to
the DECP specification.
The code in DB2 v10 is modified to correct the checking of the
DECP specifications for TIME exits in the cast character-to-time
routine. This will prevent the incorrect SQLCODE185 from being
issued for both the DB2 LOAD utility and the SQL INSERT
statement.
Also, corrections are made to a few other cast character-to-time
routines for both DB2 v9 and v10 to check DECP specifications
for TIME exits (instead of for DATE exits) to prevent false
SQLCODE185 or SQL code -185 errors.
Additionally, in DB2 v10, DB2 will check the proper source
length after the DATE exit validates the input date and a
successful conversion has occurred. This will prevent the error
path from being taken resulting in an unexpected SQLCODE181 or
-181.
Additional Keywords: SQLDATE SQLTIME SQLINSERT SQLMIGRATION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM59155
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
Please note. If you are using DATE exits, this concerns you.
If you are using a DATE exit, specifically an EBCDIC, ASCII, or
UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make
sure it is functioning properly. If it is, a query referencing
the TIMESTAMP built-in function should work correctly and no
action is necessary. If however the exit is not working
properly and the query referencing the TIMESTAMP built-in
function worked in DB2 9 but is now not working in DB2 10 (i.e.
it does not return the expected result), then please ensure that
the exit is coded and working properly.
ACTION:
The following behavior difference may be noticed with the
application of this apar.
1
Please note that this apar corrects an instance where an
incorrect SQLCODE180 could be issued. Instead, an SQLCODE181
should be issued. So, any static applications that check for an
SQLCODE180 (or -180) should also be checking for an SQLCODE181
(or -181).
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDEC PM59155
DSNXRDE9 PM59155
DSNXRGPL PM59155
DSNXRIB9 PM59155
DSNXRID9 PM59155
DSNXRIHB PM59155
DSNXRIHD PM59155
DSNXRIHR PM59155
DSNXRIHS PM59155
DSNXRINT PM59155
DSNXRIS9 PM59155
DSNXRITV PM59155
DSNXRIT9 PM59155
DSNXRLET PM59155
DSNXRNT9 PM59155
DSNXRPL9 PM59155
DSNXRSBC PM59155
DSNXRSPL PM59155
DSNXRTIM PM59155
DSNXRTI9 PM59155
DSNXVDTT PM59155
DSNXVDT2 PM59155
DSNXVT29 PM59155
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM59155 DSNXRDEC DSNXRDE9 DSNXRGPL DSNXRIB9 DSNXRID9 DSNXRIHB
DSNXRIHD DSNXRIHR DSNXRIHS DSNXRINT DSNXRIS9 DSNXRITV
DSNXRIT9 DSNXRLET DSNXRNT9 DSNXRPL9 DSNXRSBC DSNXRSPL
DSNXRTIM DSNXRTI9 DSNXVDTT DSNXVDT2 DSNXVT29
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDEC
DSNXRDE9
DSNXRGPL
DSNXRIB9
DSNXRID9
DSNXRIHB
DSNXRIHD
DSNXRIHR
DSNXRIHS
DSNXRINT
DSNXRIS9
DSNXRITV
DSNXRIT9
DSNXRLET
DSNXRNT9
1 DSNXRPL9
DSNXRSBC
DSNXRSPL
DSNXRTIM
DSNXRTI9
DSNXVDTT
DSNXVDT2
DSNXVT29
LISTEND
UK78170 COVER LETTER END
UK78176 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57956 -
****************************************************************
* USERS AFFECTED: All DB2 users who use native SQLPL stored *
* procedures with PLANMGMT(OFF) and *
* APREUSE(ERROR). *
****************************************************************
* PROBLEM DESCRIPTION: When running a native SQLPL stored *
* procedure, customers can receive *
* the following abends, *
* ABEND0C4 RC00000010 DSNXELX +176A *
* ABEND04E RC00C90101 DSNGEPLC ERQUAL500A *
* *
* when rebinding a native SQLPL stored *
* procedure, the following abend *
* could occur, *
* RC00C90101 DSNGEPDL ERQUAL50FD *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When rebinding a native SQLPL stored procedure with
PLANMGMT(OFF) and APREUSE(ERROR), a section (section 1) of the
package could be removed incorrectly from disk, which causes
above abends.
DB2 has been changed such that the section one will not be
removed by rebinding a native SQLP stored procedure with
PLANMGMT(OFF) and APREUSE(ERROR).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57956
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
Applying this apar will not fix the package which is already
broken. The customer can run the following query to find all
native stored procedures and ALTER REGENERATE these procedures
can correct the broken package.
SELECT * FROM SYSIBM.SYSPACKAGE WHERE PLANMGMT NOT IN ('E','B')
AND APREUSE NOT IN ('N',' ') AND (TYPE='N' OR TYPE='F')
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEPDL PM57956
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57956 DSNGEPDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPDL
LISTEND
UK78176 COVER LETTER END
UK78180 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58294 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of REORG TABLESPACE utility with DISCARD *
****************************************************************
* PROBLEM DESCRIPTION: A REORG TABLESPACE DISCARD of a table *
* with a LOB column which is greater *
* than 32k failed with MSGDSNU297I and *
* ended with RC8, even though user *
* omitted both DISCARDDN option and the *
* SYSDISC DD statement in the input JCL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A REORG TABLESPACE DISCARD was run on a table with a LOB column
which was defined greater than 32k. The REORG failed with
message DSNU297I - COMPOSITE RECORD SIZE TOO LARGE FOR xxx.xxx,
even though DISCARDDN and SYSDISC DD statement were omitted.
REORG DISCARD without DISCARDDN option and SYSDISC DD
statement will not discard records into a data set, so the
message DSNU297I should be skipped in this case.
The REORG code has been modified to avoid issuing DSNU297I
if DISCARD is specified without DISCARDDN option and SYSDISC
DD statement. And the REORG will discard records without
saving them in a data set.
This APAR also requires a documentation change in Utility Guide
and Reference:
Changed option for utility REORG:
DISCARD
Specifies that records that meet the specified WHEN conditions
are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or
UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD
statement in the JCL, discarded records are saved in the
| associated data set. Otherwise, the utility discards records
| without saving them in a data set.
You can specify any SHRLEVEL option with DISCARD; however, if
1 you specify SHRLEVEL CHANGE, modifications that are made
during the reorganization to data rows that match the discard
criteria are not permitted. In this case, REORG TABLESPACE
terminates with an error.
If you specify DISCARD, rows are decompressed and edit
routines are decoded. If you also specify DISCARD to a file,
rows are decoded by field procedure, and the following columns
are converted to DB2 external format:
(1)SMALLINT
(2)INTEGER
(3)FLOAT
(4)DECIMAL
(5)TIME
(6)TIMESTAMP
Otherwise, edit routines or field procedures are bypassed on
both the UNLOAD and RELOAD phases for table spaces. Validation
procedures are not invoked during either phase.
Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY
option.
| You cannot specify DISCARD for a base table with LOB columns
| unless the discard records are less than 32k or you want to
| discard records without saving them in a data set.
You cannot specify DISCARD for a base table with XML columns
or for an XML table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58294
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
PM58294 introduces the following changes to the DB2 10 for z/OS
Utility Guide and Reference:
Changed option for utility REORG:
DISCARD
Specifies that records that meet the specified WHEN conditions
are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or
UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD
statement in the JCL, discarded records are saved in the
| associated data set. Otherwise, the utility discards records
| without saving them in a data set.
You can specify any SHRLEVEL option with DISCARD; however, if
you specify SHRLEVEL CHANGE, modifications that are made
during the reorganization to data rows that match the discard
criteria are not permitted. In this case, REORG TABLESPACE
terminates with an error.
If you specify DISCARD, rows are decompressed and edit
routines are decoded. If you also specify DISCARD to a file,
rows are decoded by field procedure, and the following columns
1 are converted to DB2 external format:
(1)SMALLINT
(2)INTEGER
(3)FLOAT
(4)DECIMAL
(5)TIME
(6)TIMESTAMP
Otherwise, edit routines or field procedures are bypassed on
both the UNLOAD and RELOAD phases for table spaces. Validation
procedures are not invoked during either phase.
Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY
option.
| You cannot specify DISCARD for a base table with LOB columns
| unless the discard records are less than 32k or you want to
| discard records without saving them in a data set.
You cannot specify DISCARD for a base table with XML columns
or for an XML table space.
REORG TABLESPACE DISCARD cannot be specified on a
system-maintained temporal table space when versioning is
active. When versioning is active and DISCARD is specified,
REORG TABLESPACE fails with message DSNU076I and return code
8.
ACTION:
The PTF for APAR PM58294 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURFTB PM58294
DSNURORG PM58294
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58294 DSNURFTB DSNURORG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURFTB
DSNURORG
LISTEND
UK78180 COVER LETTER END
1
UK78202 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60737 -
****************************************************************
* USERS AFFECTED: All DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: FOR A DR EXERCISE, AFTER GRECP *
* PROCESSING COMPLETED, CHECK INDEX *
* ABENDED 04E-RC00C90101 DSNKNXT2 *
* ERQUAL5004 with DATA INCONSISTENCIES. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During GRECP or LPL Recovery, if "buffer Pool Full" condition
is
detected, DB2 GRECP/LPL recovery terminates. This could leave
data/indexes in inconsistent state. The reason for data/index
inconsistency is because error for the early termination was not
propagated correctly to the top level recovery routine. This
resulted in the top level recovery routine incorrectly removing
the GRECP/LPL state without completing the data/index recovery.
To avoid this failure, Data Manager Recovery logic is modified
to isolate the objects associated with the buffer pool full
condition (RC00C200E9) and continue with the recovery of other
objects.
The DB2 Recovery logic is modified to terminate the recovery of
those objects that are affected by buffer pool full condition
and continue the recovery of other unaffected objects to
completion.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60737
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIFLAA PM60737
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60737 DSNIFLAA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFLAA
LISTEND
UK78202 COVER LETTER END
UK78206 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57645 -
****************************************************************
* USERS AFFECTED: All IRLM230 (HIR2230) users. *
1 ****************************************************************
* PROBLEM DESCRIPTION: IRLM abendS0C4 in DXRRL400 while trying *
* to free a variable length storage. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM storage manager is called to release the storage of a
variable length QE. The address of this QE in the register
contains invalid value in its high-half causing the S0C4 abend.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
The high-halves of registers are cleared before calling storage
manager to release variable length storage.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM57645
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 PM57645
DXRRL711 PM57645
DXRRL712 PM57645
DXRRL720 PM57645
DXRRL730 PM57645
DXRRL731 PM57645
DXRRL750 PM57645
DXRRL790 PM57645
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57645 DXRRL710 DXRRL711 DXRRL712 DXRRL720 DXRRL730 DXRRL731
DXRRL750 DXRRL790
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL710
DXRRL711
DXRRL712
DXRRL720
DXRRL730
DXRRL731
DXRRL750
DXRRL790
LISTEND
UK78206 COVER LETTER END
UK78211 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62102 -
****************************************************************
* USERS AFFECTED: All users of DB2 Data Sharing. *
1 ****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 IN DSNIARPL+190E DURING *
* POSTPONED ABORT RECOVERY *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During Postponed Abort (PA) recovery, when all the PA Unit of
Recovery (UR) are recovered, Data Manager restart (DMRR) logic
goes through the restart table entries to make sure that all the
exception status has been reset. However, when auto-GRECP
recovery is running in parallel with the postponed abort
recovery and when, both, PA recovery and GRECP recovery ends
around the same time, restart table entry (DBRT_DB) for GRECP
object may have been removed from restart table by auto-GRECP
process. PA recovery process does not differentiate between the
restart table entry for GRECP recovery object and PA object.
This results in program exception error during end of PA
recovery. The proper action for PA end of recovery logic is to
avoid looking at the restart table entries when auto-grecp
recovery is active. Auto-GRECP recovery logic will remove the
restart table entries when it is done processing all log records
for all objects.
DB2 Postponed Abort logic is modified to avoid program exception
error when processing Data Base Restart Table entries.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62102
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIARPL PM62102
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62102 DSNIARPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIARPL
LISTEND
UK78211 COVER LETTER END
UK78230 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60499 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS or DB2 10 for z/OS users *
* of the REORG TABLESPACE utility with the *
* PART keyword. *
****************************************************************
* PROBLEM DESCRIPTION: This is the DB2 Utilities Suite *
* companion APAR to DB2 for z/OS *
* APAR PM55051. The two APAR fixes *
1 * must be applied at the same time. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Failure to apply this APAR fix with PM55051 will cause
the new SORTNPSI keyword for REORG TABLESPACE PART
to be rejected as invalid.
Apply the PTF for PM60499 at the same time the PTF for
PM55051 is applied.
COMPONENT: 5740-XYR00-JDBAA1K
APARS FIXED: PM60499
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for PM60499 is a companion fix and requires the fix
for APAR PM55051 for FMID HDBAA10 to be applied.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUFFMM PM60499
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60499 DSNUFFMM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUFFMM
LISTEND
UK78230 COVER LETTER END
UK78235 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58420 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: High class 14 latch (LC14) contention, *
* on BMVTPBXL latch. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Latch contention may exist on the BMVTPBXL latch, which
serializes the pageset hash chains, if there are a large
number of concurrent jobs either starting up or committing
concurrently.
To reduce LC14 contention, the single BMVTPBXL latch has been
replaced by multiple latches (one for each pageset hash chain).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58420
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
DSNB1CPS PM58420
DSNB1LRR PM58420
DSNB1OFA PM58420
DSNB1OPS PM58420
DSNB1PMI PM58420
DSNB1PMT PM58420
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58420 DSNB1CPS DSNB1LRR DSNB1OFA DSNB1OPS DSNB1PMI DSNB1PMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPS
DSNB1LRR
DSNB1OFA
DSNB1OPS
DSNB1PMI
DSNB1PMT
LISTEND
UK78235 COVER LETTER END
UK78247 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60056 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: Code is being added to support a future *
* function of DB2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Code is being added to support a future function of DB2. The
function being added will be enabled at a later date.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60056
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 PM60056
DSNF7DIR PM60056
DSN7GCHK PM60056
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60056 DSNFMDIR DSNF7DIR DSN7GCHK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNFMDIR
DSNF7DIR
DSN7GCHK
LISTEND
UK78247 COVER LETTER END
UK78277 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60349 -
****************************************************************
* USERS AFFECTED: All DB2 V10 users. *
****************************************************************
* PROBLEM DESCRIPTION: ECSA or private 31bit storage may be *
* lost to the system for the duration of *
* this DB2 instance if the abend occurs *
* while within DB2 storage mananger code. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When threads abend while in DB2 storage manager 31bit variable
storage code holding any of the latches used to serialize
storage management, the recovery module dsnsrsup would receive
control. As part of the recovery process, it attempts to
validate that the storage pool still has integrity by analyzing
the segments. The code to do this segment verification, failed
to count the bytes attributed to being quad word bounded so the
length of the segment didn't match the byte count. When this
occurs, those segments are placed on the phbrshb damaged segment
chain so that no new storage is allocated from them. They are
not freed, since portions of the storage may still be in use.
The available ECSA or DB2 address space private 31bit storage
may be reduced for the duration of this DB2 instance if the
abends occur while the abending thread is within DB2 storage
manager code, and the abending thread is accessing one of the
system pools. Only a recycle of DB2 will recover the affected
storage in that case.
RC00E20003,RC00E2000B,RC00E2000C,RC00E2000D,RC00E20011
RC00E20013,RC00E2001F,RC00E20021,RC00E20022,RC00E20025
RC00E20001,RC00E50013
L2 Diagnosis:
If this apar is the cause of the shortage, a phb with the
affected storage type will be found having a very large chain
of shbs, starting with phbrshb. Logrec entries for the affected
phb should also exist, showing SMC recovery was entered.
The recovery code has been changed to properly calculate the
number of bytes in each segment while making the validation
check.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60349
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 DSNSRSUP PM60349
DSNSVBK PM60349
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60349 DSNSRSUP DSNSVBK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNSRSUP
DSNSVBK
LISTEND
UK78277 COVER LETTER END
UK78286 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61161 -
****************************************************************
* USERS AFFECTED: DB2 9 and DB2 10 for z/OS users of hybrid *
* join and varbinary data *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may be returned for a *
* query that references varbinary data *
* and involves a hybrid join access path. *
* The value of the varbinary column has *
* the same value instead of the value *
* for each row. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The incorrect output may occur for a query using hybrid join
which references varbinary data. The inner table has an
index which is clustered and no sort is needed (hybrid join
case 2). The varbinary column is selected from the outer table.
The problem occurs when the internal buffer for the varbinary
data is greater than 256 bytes. The buffer length includes
the declared length of the column plus 2 bytes for length and
1 byte for null if the data type is nullable.
For example, the following query uses hybrid join where T1
is the outer table and T2 is the inner table.
CREATE TABLE T1 (C1 INT, C2 VARBINARY(254));
CREATE TABLE T2 (C1 INT, C2 VARBINARY(254));
CREATE UNIQUE INDEX IX1 ON T1(C1);
CREATE UNIQUE INDEX IX2 ON T2(C1) CLUSTER;
INSERT INTO T1 VALUES(1,VARBINARY('11111'));
INSERT INTO T1 VALUES(2,VARBINARY('22222'));
INSERT INTO T1 VALUES(3,VARBINARY('33333'));
INSERT INTO T2 VALUES(1,VARBINARY('44444'));
INSERT INTO T2 VALUES(2,VARBINARY('55555'));
1 INSERT INTO T2 VALUES(3,VARBINARY('66666'));
SELECT A.C1, A.C2, B.C2
FROM T1 A, T2 B
WHERE A.C1 = B.C1
The value returned for A.C2 may be incorrect if the
length of the varbinary column buffer is more than
256 bytes. The following is the incorrect data returned:
C1 A.C2 B.C2
-- ----- -----
1 33333 44444
2 33333 55555
3 33333 66666
The result should be :
C1 A.C2 B.C2
-- ----- -----
1 11111 44444
2 22222 55555
3 33333 66666
DB2 has been fixed to correctly move the varbinary data using
the actual length instead of the declared length. This will
prevent the incorrect output.
Additional keywords : SQLHYBRIDJOIN SQLVARBINARY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61161
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 PM61161
DSNXRFH9 PM61161
DSNXRFJ9 PM61161
DSNXRGBJ PM61161
DSNXRGB9 PM61161
DSNXRSFJ PM61161
DSNXRT3J PM61161
DSNXRT39 PM61161
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61161 DSNXRFHJ DSNXRFH9 DSNXRFJ9 DSNXRGBJ DSNXRGB9 DSNXRSFJ
DSNXRT3J DSNXRT39
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRFHJ
DSNXRFH9
DSNXRFJ9
DSNXRGBJ
1 DSNXRGB9
DSNXRSFJ
DSNXRT3J
DSNXRT39
LISTEND
UK78286 COVER LETTER END
UK78307 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62572 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN *
* job. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU777I and RC8 during *
* DSNTIJEN step ENFM0100 due to lock *
* contention during step ENFM0097. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
The DB2 10 for z/OS ENFM process failed with RC08 in the
ENFM0100 step of the DSNTIJEN job. Message DSNU777I - DSNUECM0
CATENFM CONVERT STATUS - TABLE SPACE CONVERSION ORDER ERROR
was issued. This happened because of an undetected lock
contention failure during the SWITCH phase of the ENFM0097 ENFM
REORG step of the DSNTIJEN job.
This failure left the indexes on the tables in the SYSPKAGE
table space broken. These indexes needed to be rebuilt to
get functionality back.
In this post failure state it's possible to lose recently
inserted catalog data.
Additional Keywords: DSNIOST2 ERQUAL5005 DSNIOST2:5005
RC00C90101 ABEND04E RC00C90D01 DSNOTCSO OFFSET569C
Utility code has been changed to detect the reported lock
contention problem during the ENFM REORG SWITCH phase process.
Detecting this ENFM REORG SWITCH phase problem will prevent
the DB2 indexes from being broken during the ENFM process,
internal information from advancing past where it should in
failure situations, and post problem catalog information data
loss.
With this code fix, the previously undetected lock contention
problem will be seen and the ENFM process will fail with RC=8
and the following abend:
ABEND04E RC00E400AF DSNURSWD OFFSET942E
In this abend case the DB2 indexes will still be operational and
the DSNTIJEN job can be resubmitted once the problem causing the
ENFM failure has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM62572
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 PM62572
DSNURSWD PM62572
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62572 DSNGEDLC DSNURSWD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEDLC
DSNURSWD
LISTEND
UK78307 COVER LETTER END
UK78358 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58947 -
****************************************************************
* USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS *
* USERS OF RECOVER UTILITY WHEN RECOVERING A *
* PARTITIONED OBJECT TO A PRIOR POINT AND A *
* SYSTEM LEVEL BACKUP IS USED TO RESTORE THE *
* OBJECT *
****************************************************************
* PROBLEM DESCRIPTION: RESIDUAL DATA EXISTS IN PARTITIONED *
* OBJECT AFTER BEING RECOVERED BY *
* RECOVER UTILITY WITH DSNUM ALL AND *
* TO A POINT IN TIME BEFORE PARTITIONS *
* WERE ADDED AND A SYSTEM LEVEL *
* BACKUP WAS USED AS A BASE FOR *
* RECOVERY *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran the following scenario on a PBG (partitioned by
growth) table space with 4 partitions:
1. BACKUP SYSTEM utility was run, establishing a system-level
backup (SLB) for use as a recovery base.
2. rows were inserted which caused the table space to grow
from 4 partitions to 5. (Note that using the ALTER command
to add a 5th part explicitly to a non-PBG object would be
equivalent to this step and such a scenario is also addressed
by this apar.)
3. RECOVER utility DSNUM ALL with TORBA or TOLOGPOINT was
run to a point before the 5th part was added. The SLB was
correctly used as a recovery base.
The RECOVER job appeared to complete successfully, but it was
later found that the newly added partition (part 5) was not
1 reset by the utility, and the data in this partition
effectively remained in the table space. This led also to
unexpected error ranges (WEPR) and pending status issues for
the affected object.
The reason this happened is that when an SLB was used as a
recovery base, the partitions added after the SLB was made were
not properly reset.
Code was changed in RECOVER utility to reset added parts
when using an SLB as a recovery base and recovering to a
point in time before the parts were added.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58947
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCALA PM58947
DSNUCARS PM58947
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58947 DSNUCALA DSNUCARS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCALA
DSNUCARS
LISTEND
UK78358 COVER LETTER END
UK78390 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60236 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: PREPARE or BIND can take longer *
* than expected. *
* *
* The z/OS Catalog Search Interface *
* is being invoked during every index *
* probe. If many statements are being *
* prepared or bound concurrently, the *
* single DB2 CSI request service task *
* can become a bottleneck. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
PM48727 added the ability to skip index probing when an index
data set is migrated by HSM. The Catalog Services Interface
(CSI) is used to detect when a data set is migrated.
However, there is only one DB2 service task that performs
the CSI requests.
1
When concurrent index probes are performed, PREPARE or BIND
performance can suffer.
DB2 is enhanced to only request the migrated status of a data
set when the index is closed prior to doing the index probe.
If the index data set is open it implies the data set can't be
migrated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60236
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 PM60236
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60236 DSNKCEST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKCEST
LISTEND
UK78390 COVER LETTER END
UK78404 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60650 -
****************************************************************
* USERS AFFECTED: ALL V10 DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNV508I DSNVMON - DB2 DBM1 BELOW *
* THE BAR STORAGE *
* *
* ABEND04E RC00E20003 in DSNSVBK *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DBM1 address space is consuming a large amount of available
31-bit below-the-bar storage. This problem is caused by DB2
scheduling asynchronous DASD write requests faster than the
write engines could process them. These requests are queued up
in a below-the-bar storage pool.
DB2 has been modified to help alleviate below-the-bar storage
shortages for a specific scenario: When a buffer pool's vertical
deferred write threshold is reached, for the same page set or
partition, DB2 will avoid scheduling multiple asynchronous DASD
write requests if one is already in the queue waiting to be
processed by the next available write engine.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60650
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
DSNB5COM PM60650
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60650 DSNB5COM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5COM
LISTEND
UK78404 COVER LETTER END
UK78406 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58820 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS version 9 and version 10 *
* users of normal restart in Data Sharing *
* environment. *
****************************************************************
* PROBLEM DESCRIPTION: Data regression problem due to down *
* level page written to GBP at restart *
* REDO phase. Following symptoms are *
* possible: *
* 1. ABENDs due to data/index mismatching *
* 2. CHECK DATA/INDEX reports error. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During single (individual) member restart, in the data sharing
determination of whether or not to apply the redo log for
in-commit UR is done after making the page dirty. This results
in potential page regression, if other non-restarting member
also happens to modify the same page. To avoid the page
regression, rather than unconditionally marking the page dirty,
the log apply routine should make sure that the insert log
record really needs to be re-applied during restart. If the
insert row specified by the redo log record already exists in
the page then it can skip the log record hence avoid unnecessary
writing out of the page that was not updated and wiping out the
data update made by other members.
DB2 code has been fixed to avoid apply the REDO log of INSERT
if the INSERT has been written out already.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58820
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBHRE PM58820
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58820 DSNIBHRE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBHRE
LISTEND
UK78406 COVER LETTER END
UK78414 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61031 -
****************************************************************
* USERS AFFECTED: All users for DB2 10 for z/OS *
* of IFCID 401 trace. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E, RC00E2000F *
* at DSNSLD4 . DSNSVSFB +0858 *
* or *
* ABEND04E, RC00E70005 *
* at DSNXGRDS . DSNXVTRS +0A8A *
* or any other symptom is possible *
* due to the storage overlay. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When READS requests from an IFI application are issued for
IFCID 0401 while IFCID 0400 is active, DB2 returns a certain
number of IFCID 0401 records at a time for all statements in
the EDM pool. When more than that number of FCID 0401 records
are requested by an IFI application and returned by DB2, the
buffer for the IFCID 0401 records in DB2 is reused.
.
In the reported cases, when the buffer is reused, the residual
values in the buffer caused the storage overlay.
.
DB2 has been modified to clean the residual values in the
buffer for IFCID 0401 records when it's reused.
Additional Keywords: .
SMCOVERLAY
DB2OVRLAY/K
IFCID401
IFCID400
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61031
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXERDS PM61031
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61031 DSNXERDS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXERDS
LISTEND
UK78414 COVER LETTER END
UK78418 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58322 -
****************************************************************
* USERS AFFECTED: All DB2 10 users who insert into or delete *
* from a view where the view references a DB2 *
* directory table *
****************************************************************
* PROBLEM DESCRIPTION: A negative SQLCODE should have been *
* issued for the insert or delete *
* operation in the statements such as *
* INSERT, DELETE, MERGE, or SELECT FROM *
* those where the object table references *
* a view and the view definition *
* references a DB2 directory table such *
* as SYSLGRNX. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A negative SQLCODE is missing during the insert or delete
operation in the statements such as INSERT, DELETE, MERGE,
or SELECT FROM those where the object table references a
view and the view definition references a DB2 directory
table such as SYSLGRNX. For example:
SYSADM does the following:
CREATE VIEW SYSLGRNX AS SELECT * FROM SYSIBM.SYSLGRNX;
USRT001 does the following:
INSERT INTO SYSADM.SYSLGRNX
(LGRDBID , LGRPSID , LGRUCDT , LGRUCTM , LGRSRBA ,
LGRSPBA , LGRPART , LGRSLRSN , LGRELRSN , LGRMEMB )
VALUES
(2 , 3 , '010100' , '010100' , '0000' ,
'0000' , '0000' , '0000' , '02' );
==> succeeds but SQLCODE -607 is expected
DB2 did not block the INSERT statement correctly.
Notice that the following UPDATE statement receives proper -151
1 because the columns in the directory table are not updatable.
UPDATE SYSADM.SYSLGRNX SET LGRDBID = 2;
==> fails with SQLCODE -151
DB2 has been modified to ensure the proper negative SQLCODE
is issued when inserts into or deletes from a view where the
view references a DB2 directory table.
Additional keywords: SQLCODE607 SQLDIRECTORY SQLINSERT
SQLDELETE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58322
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM58322:
See PM58322 APAR/PTF text for additional information about
why a REBIND is necessary.
PM58322 corrects a problem of missing a negative SQLCODE
on the insert or delete operation in the statements such
as INSERT, DELETE, MERGE, or SELECT FROM those where the
object table references a view and the view definition
references a DB2 directory table such as SYSLGRNX.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOVC PM58322
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58322 DSNXOVC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOVC
LISTEND
UK78418 COVER LETTER END
UK78426 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57441 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of utilities. *
****************************************************************
* PROBLEM DESCRIPTION: THIS IS A SERVICEABILITY APAR WHICH *
1 * DOES NOT AFFECT ANY EXTERNAL FUNCTION. *
* NO PROBLEM IS FIXED BY THIS APAR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This is a serviceability apar for DB2 for z/OS utilities.
No problem is fixed by this apar.
Serviceability apar only.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57441
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBBCD PM57441
DSNUGFCB PM57441
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57441 DSNUBBCD DSNUGFCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBBCD
DSNUGFCB
LISTEND
UK78426 COVER LETTER END
UK78449 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62077 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND 0C4-00000004 DSNLTINT+0B9E *
* in DB2 10 for z/OS only, leading to *
* DB2 termination with 00E50702. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When processing an inbound SQL Interrupt request from a remote
client system, DSNLTINT is "soft canceled" via an
04E-00E50013
abend (as a result of a TCP/IP loss event) while attempting
to acquire a latch. DSNLTINT recovery processing, relative to
the 04E-00E50013 abend, receives abend 0C4-00000004 because
the addressability to a control block (PRE) was not assured
for the benefit of recovery processing.
The DB2 subsystem terminates with reason code 00E50702 because
an abend was encountered during abend recovery processing.
This condition occurs only in DB2 10 for z/OS.
DSNLTINT has been changed to no longer reference the (PRE)
control block during abend recovery processing since this
1 reference is not necessary.
Note: Although the reported symptom occurs only in DB2 10
for z/OS environments, the change is also applied to
DB2 9 for z/OS in order to eliminate the potential for
the problem in the future.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62077
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTINT PM62077
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62077 DSNLTINT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTINT
LISTEND
UK78449 COVER LETTER END
UK78472 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM56612 -
****************************************************************
* USERS AFFECTED: DB2 9 and DB2 10 users of native SQL *
* procedures and Bind Deploy. *
****************************************************************
* PROBLEM DESCRIPTION: When a user is doing a Bind Deploy *
* of a native SQL procedure to a *
* data sharing system while at the *
* period of time where the Bind *
* Deploy has not finished yet, SQL *
* Call statements are being made to *
* that particular procedure in the *
* same system the SQL Call statements *
* may get SQLCODE440 and subsequent *
* SQL Call statements to that procedure *
* may keep getting intermittent *
* SQLCODE440 even after the Bind Deploy *
* has successfully finished. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This issue is caused by a timing window in the stored procedure
resolution cache invalidation during commit processing. At end
of Bind Deploy processing, the cache is invalidating an entry
and at the same time an SQL Call statement comes and add another
entry resulting in cached information that is inconsistent with
the catalog information.
1
Cache entry invalidation process is improved to eliminate timing
window that can result in cache inconsistencies.
Additional Keywords:
SQLPL SQLNATVESQLPL SQLPROCEDURE SQLSP SQLSTOREDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM56612
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXECW PM56612
DSNXECWA PM56612
DSNXECWU PM56612
DSNXIART PM56612
DSNXICRT PM56612
DSNXIDRT PM56612
DSNXI14 PM56612
DSNXMIT2 PM56612
DSNX9CCM PM56612
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM56612 DSNXECW DSNXECWA DSNXECWU DSNXIART DSNXICRT DSNXIDRT
DSNXI14 DSNXMIT2 DSNX9CCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXECW
DSNXECWA
DSNXECWU
DSNXIART
DSNXICRT
DSNXIDRT
DSNXI14
DSNXMIT2
DSNX9CCM
LISTEND
UK78472 COVER LETTER END
UK78476 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58562 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of alter table functions (data Versioning). *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability APAR for an ABEND04E *
* RC00c90101 in DSNISUPI 2002 vrace2002. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
When a specific table version record is inserted to a system
page of a partition, the RID of the record is updated to the
header page of that partition. This code is added to aid in
diagnose of a problem that the incorrect header page is being
updated with the RID of the record. This code will not solve
the reported abend, but will detect the incorrect header page
problem at an early stage.
DB2 code is changed to have a sanity check on the partition
number of the header page and system page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58562
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIFOD PM58562
DSNISMRS PM58562
DSNISRTI PM58562
DSNIVOBD PM58562
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58562 DSNIFOD DSNISMRS DSNISRTI DSNIVOBD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFOD
DSNISMRS
DSNISRTI
DSNIVOBD
LISTEND
UK78476 COVER LETTER END
UK78514 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53243 -
****************************************************************
* USERS AFFECTED: All DB2 users who use DB2 instrumentation *
* for Stored Procedure and User-Defined *
* Function performance and tuning analysis. *
****************************************************************
* PROBLEM DESCRIPTION: Stored Procedure (SP) and User-Defined *
* Function (UDF) performance and tuning *
* analysis is difficult when multiple *
* procedures or functions are involved. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Stored Procedure (SP) and User-Defined Function (UDF)
performance and tuning analysis has typically been performed
via a combination of IFCID3 and IFCID239.
IFCID3 provides plan level information and aggregates all
1 executions of SPs or UDFs into common fields. This can create
difficulty when tuning multiple procedures or functions that
are executed in a given transaction.
IFCID239 is also used for performance and tuning analysis at
the package level. This provides better granularity than IFCID3
but still may not be sufficient for all transactions.
If a procedure or function is executed multiple times, the
variation between executions cannot be identified.
Instrumentation enhancements are needed.
Multiple IFCID enhancements are implemented to provide more
effective performance and tuning analysis of Stored Procedures
and User-Defined Functions.
* IFCID233 is written at the beginning and end of a Stored
Procedure or User-Defined Function invocation. This record
is enhanced with the invoking statement ID, the invoking
statement type, the version ID (applies only to versioned
procedures), and the routine ID.
Note: The routine ID may be zero if a REBIND is not performed
for packages containing CALL statements where the stored
procedure name is a literal.
See DSNDQW02 for mapping details.
* New IFCIDs 380 and 381 are created for Stored Procedure and
User-Defined Function detail respectively. These records have
two data sections. Data section 1 is mapped by QW0233. Data
section 2 is mapped by QW0380 which includes CP, specialty
engine, and elapsed time details for nested activity. A
series of 380 and/or 381 records can be used to determine the
amount of class 1 and class 2 CP, specialty engine, and
elapsed time relative to the execution of a given Stored
Procedure or User-Defined Function.
See DSNDQW05 for mapping details.
* New IFCIDs 497, 498, and 499 are created for statement level
detail. These records track dynamic and static DML statements
executed by a transaction, including those executed within a
Stored Procedure or User-Defined Function. A series of
IFCID 497, 498, and/or 499 records can be used to determine
the statements executed for a given transaction.
Note: Any packages containing static SQL statements that
existed prior to DB2 10 must be rebound in DB2 10 NFM (not
necessarily with this APAR applied) in order to obtain a
valid statement ID.
See DSNDQW05 for mapping details.
* A new performance class 24 is created to encapsulate IFCID380
and IFCID499 for stored procedure detail analysis.
For users who are interested in exploiting the functions
provided via this APAR, the following actions need to be
considered:
* For a CALL statement to a DB2 for z/OS Stored Procedure, the
Stored Procedure name can be identified via a literal or by
using a host variable or parameter marker. When using a
literal for the stored procedure name, and in order to
benefit from the enhancement that provides a valid routine ID
in various IFCID records, the packages that contain the CALL
statement must be rebound after this APAR is applied.
1 * For an SQL statement that invokes a DB2 for z/OS User-Defined
Function, and in order to benefit from the enhancement to
provide a valid routine ID in various IFCID records, the
packages that contain the SQL statement must be rebound after
this APAR is applied.
* The mapping of IFCID233 remains compatible with prior
versions and no immediate change is required. However,
applications that parse this record will need to be changed
in order to exploit the new fields.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM53243
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM53243 (V10):
For users who are interested in exploiting the functions
provided via this PTF, the following actions need to be
considered:
* For a CALL statement to a DB2 for z/OS Stored Procedure, the
Stored Procedure name can be identified via a literal or by
using a host variable or parameter marker. When using a
literal for the stored procedure name, and in order to
benefit from the enhancement that provides a valid routine ID
in various IFCID records, the packages that contain the CALL
statement must be rebound after this PTF is applied.
* For an SQL statement that invokes a DB2 for z/OS User-Defined
Function, and in order to benefit from the enhancement to
provide a valid routine ID in various IFCID records, the
packages that contain the SQL statement must be rebound after
this PTF is applied.
* The mapping of IFCID233 remains compatible with prior
versions and no immediate change is required. However,
applications that parse this record will need to be changed
in order to exploit the new fields.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWAC PM53243
DSNDQWHS PM53243
DSNDQW02 PM53243
DSNDQW03 PM53243
DSNDQW05 PM53243
DSNLCDG2 PM53243
DSNLCMSL PM53243
DSNLXOQS PM53243
DSNLXPRS PM53243
DSNLXXSS PM53243
DSNLZMON PM53243
DSNTXSTA PM53243
DSNTXSTB PM53243
DSNWVINT PM53243
DSNWVZSA PM53243
DSNXEDP PM53243
DSNXERT PM53243
DSNXERT2 PM53243
1 DSNXGCAL PM53243
DSNXGUDF PM53243
DSNXRCUF PM53243
DSNXRRTN PM53243
DSNXRUC9 PM53243
DSNXRUFC PM53243
DSNXRUFM PM53243
DSNXRUF9 PM53243
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53243 DSNDQWAC DSNDQWHS DSNDQW02 DSNDQW03 DSNDQW05 DSNLCDG2
DSNLCMSL DSNLXOQS DSNLXPRS DSNLXXSS DSNLZMON DSNTXSTA
DSNTXSTB DSNWVINT DSNWVZSA DSNXEDP DSNXERT DSNXERT2
DSNXGCAL DSNXGUDF DSNXRCUF DSNXRRTN DSNXRUC9 DSNXRUFC
DSNXRUFM DSNXRUF9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCDG2
DSNLCMSL
DSNLXOQS
DSNLXPRS
DSNLXXSS
DSNLZMON
DSNTXSTA
DSNTXSTB
DSNWVINT
DSNWVZSA
DSNXEDP
DSNXERT
DSNXERT2
DSNXGCAL
DSNXGUDF
DSNXRCUF
DSNXRRTN
DSNXRUC9
DSNXRUFC
DSNXRUFM
DSNXRUF9
MACROS
DSNDQWAC
DSNDQWHS
DSNDQW02
DSNDQW03
DSNDQW05
LISTEND
UK78514 COVER LETTER END
UK78526 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58951 -
****************************************************************
1 * 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.63.131 is provided by *
* this APAR ( JCCV363131 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V10, DB2 z/OS V9 and *
* the alternate supplemental driver *
* for DB2 z/OS V8. ( JCCZOSDB2V10, *
* JCCZOSDB2V9, JCCZOSDB2V8) *
* *
* This APAR delivers a service bundling *
* to release 3.63 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 Connectivities: Under multi-threaded environment,
PreparedStatement.getObject() call on character columns may
throw java.io.CharConversionException due to conversion
process is not thread safe. This problem has been fixed.
(wsdbu01043986)
____________________________________________________________
All Connectivities: When an application calls setNull(int,
int) or setObject(int, Object, int) with SQLXML(XML) as the
sqlType against DB2 server that doesn't support XML, driver
will pass XML type to the server and let server to complain
that the XML type is not supported. Now the driver will throw
Exception with message "Data type XML is not supported on the
target server." (wsdbu01045433)
____________________________________________________________
Type-4 Connectivity: While connecting to the DB2 server with
sysplex enabled, if the primary server is down, driver hangs
while trying to connect to alternate servers. This problem has
been fixed. (wsdbu01024083)
____________________________________________________________
Type-4 Connectivity: An application may crash with Java error
"IOException: Too many open files" after it has run for some
time. This problem has been fixed. (wsdbu01044440)
____________________________________________________________
Type-4 Connectivity: Driver uses JDK InetAddress.getHostName()
and InetAddress.getCanonicalHostName() methods to figure out
the host name of an IP Address. This can perform terrible if
1 the DNS lookup is not setup in the user environment. Driver has
provided a new driver level global property to disable the use
of these methods. The new property name is
db2.jcc.enableInetAddressGetHostName which can be set in the
driver's Configuration Property file or via a JVM property.
The default is set to "True" which means the driver will
continue to use InetAddress.getHostName() and
InetAddress.getCanonicalHostName() methods to figure out
the host name of an IP Address. If the property is set to
"False", driver will stop calling these methods and use JDK's
InetAddress.getHostAddress() call instead. (wsdbu01023484)
____________________________________________________________
Type-4 Connectivity: When Abnormal End Unit of Work Condition
happens and driver trace is on, Exception with message "DSS
chained with same id at end of same id chain parse. ERRORCODE
=-4499" may happen. This has been fixed. (wsdbu01037806)
____________________________________________________________
Type-4 Connectivity: After migrating to z/OS DB2 V10 NFM,
an application using deferPrepare, sendDataAsIs, or
CALL statement, with an input TIMESTAMP parameter
targeting a TIMESTAMP column and set using
PreparedStatement.setTimestamp() with a value of
"0001-01-01 00:00:00.000000" or "9999-12-31
23:59:59.999999",
may result in an SQLException with SQLCODE181 (-181).
This problem has been fixed (wsdbu01042885)
____________________________________________________________
Type-4 XA Connectivity: In a workload balancing environment,
if an XA transaction fails at XA Commit with XAER_RMFAIL, then
that transport (socket) should be closed. Driver was not
closing that transport and subsequent use of that transport
has resulted in SQLCODE30090 (-30090). This has been fixed.
(wsdbu01009695)
____________________________________________________________
Type-2 z/OS Connectivity: When using Java stored procedure,
a NullPointerException may occur during connect. This problem
has been fixed. (wsdbu01025969)
____________________________________________________________
Type-2 z/OS Connectivity: Previously, the driver traces
incorrect Target server licensing restrictions and License
editions information. This problem has been fixed.
(wsdbu01043450)
____________________________________________________________
Type-2 z/OS Connectivity: SQLCODE501(-501) was returned on
PreparedStatement.executeBatch() if the statement was created
from Connection.prepareStatement (insertSqlText,
Statement.RETURN_GENERATED_KEYS) and the target table's
identity column was not declared as GENERATED ALWAYS AS
IDENTITY. This problem has been fixed. (wsdbu01031986)
____________________________________________________________
Type-2 z/OS Connectivity: A java.lang.NullPointerException is
encountered when trying to retrieve a MultiRow Fetch (MRF)
error message using Get Diagnostics. This has been fixed.
(wsdbu01018427)
____________________________________________________________
Type-2 z/OS Connectivity: Type-2 z/OS connection properties,
pkList, planName, accountingInterval, charOutputSize, ssid,
1 sendCharInputsUTF8, and maxRowsetSize cannot be set via URL.
This problem has been fixed (wsdbu01010270)
____________________________________________________________
SQLJ ALL Connectivities: Incorrect code was generated for an
SQL SELECT INTO statement using a common table expression
specified with the "WITH" keyword. SQLJ Translator issued the
Warning "Value returned by SQL query is not assigned to a
variable." The SQLJ runtime threw the following SQLException
when the program was run "Method executeUpdate cannot be used
for query." The SQLJ translator was fixed to generate correct
code. After applying the APAR re-translate the sqlj program,
Customize/Bind again. (wsdbu01043533)
____________________________________________________________
SQLJ ALL Connectivities: In a WebSphere environment, an SQLJ
application may hit a NullPointerException thrown from the
SQLJ Runtime with the method getCurrentTime() in the stack
trace. Tracing code in the SQLJ Runtime was not thread-safe.
This problem has been fixed. (wsdbu01041605 )
____________________________________________________________
SQLJ ALL Connectivities: When the option -pkgversion AUTO is
used, the SQLJ Customizer now generates a version String in
the following format YYYY-MM-DD-HH.MM.SS.nnnnnn. This version
String is recorded in the serialized Profile and is used in
the subsequent Bind. (wsdbu01030687)
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: PM58951
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 PM58951
DSNAQJBB PM58951
DSNAQJB1 PM58951
DSNAQJB2 PM58951
DSNAQJB3 PM58951
DSNAQJB4 PM58951
DSNAQJB5 PM58951
1 DSNAQJB6 PM58951
DSNAQJB7 PM58951
DSNAQJB8 PM58951
DSNAQJC1 PM58951
DSNAQJC2 PM58951
DSNAQJC3 PM58951
DSNAQJC4 PM58951
DSNAQJRM PM58951
DSNAQJS1 PM58951
DSNAQJS2 PM58951
DSNAQ3CA PM58951
DSNAQ3CC PM58951
DSNAQ3CE PM58951
DSNAQ3CF PM58951
DSNAQ3CM PM58951
DSNAQ3C0 PM58951
DSNAQ3C1 PM58951
DSNAQ3C2 PM58951
DSNAQ3C3 PM58951
DSNAQ3C4 PM58951
DSNAQ3C5 PM58951
DSNAQ3C6 PM58951
DSNAQ3C7 PM58951
DSNAQ3C8 PM58951
DSNAQ3C9 PM58951
DSNAQ3E1 PM58951
DSNAQ6CC PM58951
DSNAQ6CE PM58951
DSNAQ6CF PM58951
DSNAQ6CM PM58951
DSNAQ6C0 PM58951
DSNAQ6C1 PM58951
DSNAQ6C2 PM58951
DSNAQ6C3 PM58951
DSNAQ6C4 PM58951
DSNAQ6C5 PM58951
DSNAQ6C6 PM58951
DSNAQ6C7 PM58951
DSNAQ6C9 PM58951
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58951 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
1 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
MACROS
DSNAQJBA
DSNAQJBB
DSNAQJB1
DSNAQJB2
DSNAQJB3
DSNAQJB4
DSNAQJB5
DSNAQJB6
DSNAQJB7
DSNAQJB8
DSNAQJC1
DSNAQJC2
DSNAQJC3
DSNAQJC4
DSNAQJRM
DSNAQJS1
DSNAQJS2
DSNAQ3E1
LISTEND
UK78526 COVER LETTER END
UK78529 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58952 -
****************************************************************
* USERS AFFECTED: All Users of the IBM Data *
* Server Driver for JDBC and SQLJ *
1 ****************************************************************
* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and *
* SQLJ version 4.13.136 is provided by *
* this APAR ( JCCV413136 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for both DB2 z/OS V10 and DB2 z/OS V9 *
* ( JCCZOSDB2V10, JCCZOSDB2V9 ) *
* *
* This APAR delivers a service bundling *
* to release 4.13 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 Connectivities: Under multi-threaded environment,
PreparedStatement.getObject() call on character columns may
throw java.io.CharConversionException due to conversion
process is not thread safe. This problem has been fixed.
(wsdbu01043986)
____________________________________________________________
All Connectivities: When an application calls setSQLXML(int,
java.sql.SQLXML), or setNull(int, int) and
setObject(int, Object, int) with SQLXML (XML) as the sqlType
against DB2 server that doesn't support XML, driver will pass
XML type to the server and let server to complain that the XML
type is not supported. Now the driver will throw Exception
with message "Data type XML is not supported on the target
server." (wsdbu01045433)
____________________________________________________________
Type-4 Connectivity: While connecting to the DB2 server with
sysplex enabled, if the primary server is down, driver hangs
while trying to connect to alternate servers. This problem has
been fixed. (wsdbu01024083)
____________________________________________________________
Type-4 Connectivity: While calling Stored Procedure with
parameter of Struct type with size more than 84, driver sends
out corrupted DRDA package which may cause DB2 server to crash.
This problem has been fixed. (wsdbu01023598)
____________________________________________________________
Type-4 Connectivity: An application may crash with Java error
"IOException: Too many open files" after it has run for some
time. This problem has been fixed. (wsdbu01044440)
____________________________________________________________
Type-4 Connectivity: Driver uses JDK InetAddress.getHostName()
1 and InetAddress.getCanonicalHostName() methods to figure out
the host name of an IP Address. This can perform terrible if
the DNS lookup is not setup in the user environment. Driver has
provided a new driver level global property to disable the use
of these methods. The new property name is
db2.jcc.enableInetAddressGetHostName which can be set in the
driver's Configuration Property file or via a JVM property.
The default is set to "True" which means the driver will
continue to use InetAddress.getHostName() and
InetAddress.getCanonicalHostName() methods to figure out
the host name of an IP Address. If the property is set to
"False", driver will stop calling these methods and use JDK's
InetAddress.getHostAddress() call instead. (wsdbu01023484)
____________________________________________________________
Type-4 Connectivity: When Abnormal End Unit of Work Condition
happens and driver trace is on, Exception with message "DSS
chained with same id at end of same id chain parse. ERRORCODE
=-4499" may happen. This has been fixed. (wsdbu01037806)
____________________________________________________________
Type-4 Connectivity: After migrating to z/OS DB2 V10 NFM,
an application using deferPrepare, sendDataAsIs, or
CALL statement, with an input TIMESTAMP parameter
targeting a TIMESTAMP column and set using
PreparedStatement.setTimestamp() with a value of
"0001-01-01 00:00:00.000000" or "9999-12-31
23:59:59.999999",
may result in an SQLException with SQLCODE181 (-181).
This problem has been fixed (wsdbu01042885)
____________________________________________________________
Type-4 XA Connectivity: In a workload balancing environment,
if an XA transaction fails at XA Commit with XAER_RMFAIL, then
that transport (socket) should be closed. Driver was not
closing that transport and subsequent use of that transport
has resulted in SQLCODE30090 (-30090). This has been fixed.
(wsdbu01009695)
____________________________________________________________
Type-2 z/OS Connectivity: When using Java stored procedure,
a NullPointerException may occur during connect. This problem
has been fixed. (wsdbu01025969)
____________________________________________________________
Type-2 z/OS Connectivity: Previously, the driver traces
incorrect Target server licensing restrictions and License
editions information. This problem has been fixed.
(wsdbu01043450)
____________________________________________________________
Type-2 z/OS Connectivity: SQLCODE501(-501) was returned on
PreparedStatement.executeBatch() if the statement was created
from Connection.prepareStatement (insertSqlText,
Statement.RETURN_GENERATED_KEYS) and the target table's
identity column was not declared as GENERATED ALWAYS AS
IDENTITY. This problem has been fixed. (wsdbu01031986)
____________________________________________________________
Type-2 z/OS Connectivity: A java.lang.NullPointerException is
encountered when trying to retrieve a MultiRow Fetch (MRF)
error message using Get Diagnostics. This has been fixed.
(wsdbu01018427)
____________________________________________________________
1 Type-2 z/OS Connectivity: Type-2 z/OS connection properties,
pkList, planName, accountingInterval, charOutputSize, ssid,
sendCharInputsUTF8, and maxRowsetSize cannot be set via URL.
This problem has been fixed (wsdbu01010270)
____________________________________________________________
SQLJ ALL Connectivities: Incorrect code was generated for an
SQL SELECT INTO statement using a common table expression
specified with the "WITH" keyword. SQLJ Translator issued the
Warning "Value returned by SQL query is not assigned to a
variable." The SQLJ runtime threw the following SQLException
when the program was run "Method executeUpdate cannot be used
for query." The SQLJ translator was fixed to generate correct
code. After applying the APAR re-translate the sqlj program,
Customize/Bind again. (wsdbu01043533)
____________________________________________________________
SQLJ ALL Connectivities: In a WebSphere environment, an SQLJ
application may hit a NullPointerException thrown from the
SQLJ Runtime with the method getCurrentTime() in the stack
trace. Tracing code in the SQLJ Runtime was not thread-safe.
This problem has been fixed. (wsdbu01041605 )
____________________________________________________________
SQLJ ALL Connectivities: When the option -pkgversion AUTO is
used, the SQLJ Customizer now generates a version String in
the following format YYYY-MM-DD-HH.MM.SS.nnnnnn. This version
String is recorded in the serialized Profile and is used in
the subsequent Bind. (wsdbu01030687)
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: PM58952
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
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 PM58952
DSNAJJC2 PM58952
DSNAJ3CC PM58952
DSNAJ3CE PM58952
DSNAJ3CF PM58952
1 DSNAJ3CM PM58952
DSNAJ3C0 PM58952
DSNAJ3C1 PM58952
DSNAJ3C2 PM58952
DSNAJ3C3 PM58952
DSNAJ3C4 PM58952
DSNAJ3C5 PM58952
DSNAJ3C6 PM58952
DSNAJ3C7 PM58952
DSNAJ3C9 PM58952
DSNAJ6CC PM58952
DSNAJ6CE PM58952
DSNAJ6CF PM58952
DSNAJ6CM PM58952
DSNAJ6C0 PM58952
DSNAJ6C1 PM58952
DSNAJ6C2 PM58952
DSNAJ6C3 PM58952
DSNAJ6C4 PM58952
DSNAJ6C5 PM58952
DSNAJ6C6 PM58952
DSNAJ6C7 PM58952
DSNAJ6C9 PM58952
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58952 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
DSNAJ3C5
DSNAJ3C6
DSNAJ3C7
DSNAJ3C9
DSNAJ6CC
DSNAJ6CE
DSNAJ6CF
DSNAJ6CM
DSNAJ6C0
DSNAJ6C1
DSNAJ6C2
DSNAJ6C3
DSNAJ6C4
1 DSNAJ6C5
DSNAJ6C6
DSNAJ6C7
DSNAJ6C9
MACROS
DSNAJJC1
DSNAJJC2
LISTEND
UK78529 COVER LETTER END
UK78575 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61434 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* EXISTS predicates and the XMLTABLE function. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 returns an incorrect result for a *
* query that contains a SELECT statement *
* with an EXISTS predicate and uses the *
* XMLTABLE function in a subquery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 returns an incorrect result for a query that contains a
SELECT statement with an EXISTS predicate and uses the XMLTABLE
function in a subquery.
The following example can illustrate the problem.
1. Create two tables and populate them.
CREATE TABLE T1 (C1 INTEGER, X1 XML);
INSERT INTO T1 (C1,X1)
VALUES (20,'<a><c>21</c></a>');
INSERT INTO T1 (C1,X1)
VALUES (20,'<a><c>20</c></a>');
CREATE TABLE T2 (C1 INTEGER, C2 INTEGER);
INSERT INTO T2 (C1, C2)
VALUES (20, 20);
INSERT INTO T2 (C1, C2)
VALUES (20, 21);
2. Issue a SELECT statement that uses an EXISTS predicate
and the XMLTABLE function is in the subquery.
1
SELECT C1,C2 FROM T2
WHERE EXISTS
(SELECT * FROM T1,
XMLTABLE('/a'
PASSING X1
COLUMNS
"C2" INTEGER path 'c' ) AS X
WHERE T2.C1 = T1.C1 AND
T2.C2 = X.C2)
OR C2 = 100;
The query returns this result.
+---------------------------------+
| C1 | C2 |
+---------------------------------+
1_| 20 | 20 |
+---------------------------------+
However, the following result is expected.
+---------------------------------+
| C1 | C2 |
+---------------------------------+
1_| 20 | 20 |
2_| 20 | 21 |
+---------------------------------+
DB2 code does not handle the XMLTABLE function for an EXISTS
predicate properly. This leads to an incorrect result when a
subsequent row is fetched to qualify.
The code in DB2 has been modified to not return an incorrect
result in the scenario described.
Additional Keywords: SQLXMLTABLE SQLEXISTS SQLINCORR INCORROUT
SQLINCORROUT DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61434
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNQMD PM61434
DSNNQTOP PM61434
DSNXRBND PM61434
DSNXRBN9 PM61434
DSNXRDOC PM61434
DSNXRDO9 PM61434
DSNXRPUF PM61434
DSNXRXML PM61434
DSNXRXM9 PM61434
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61434 DSNNQMD DSNNQTOP DSNXRBND DSNXRBN9 DSNXRDOC DSNXRDO9
DSNXRPUF DSNXRXML DSNXRXM9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNQMD
DSNNQTOP
DSNXRBND
DSNXRBN9
DSNXRDOC
DSNXRDO9
DSNXRPUF
DSNXRXML
DSNXRXM9
LISTEND
UK78575 COVER LETTER END
UK78581 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55928 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: This is a preconditioning APAR for the *
* APAR PM56631, which is a new function *
* APAR that introduces new built-in *
* functions PACK and UNPACK. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
New built-in functions PACK and UNPACK are introduced to DB2 10
via two APARs: PM55928 (preconditioning APAR) and PM56631
(enabling APAR).
Please refer to the PM56631 closing text for the description of
the new functions.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55928
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM51654:
See PM51654 APAR/PTF text for additional information about
why a REBIND is necessary.
PM51654 corrects a problem when incorrect output could happen
for a complex SQL statement or view with an outer join and a
correlated sub-query.
To make this fix effective for a static application, it must be
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 PM47058:
See PM47058 APAR/PTF text for additional information about
why a REBIND is necessary.
PM47058 corrects a problem of incorrect output when an SQL
statement satisfies all of the following conditions:
1. table expression with sideway reference is defined in this
SQL statement;
2. LEFT OUTER JOIN is involved in this SQL statement;
3. CPU parallelism setting is enabled.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM41296:
See PM41296 APAR/PTF text for additional information about
why a REBIND is necessary.
PM41296 corrects a problem of an SQL statement which defines a
table expression one the preserved side of LEFT OUTER JOIN, and
a CASE statement or non-column expression is defined in the
SELECT list of the table expression and is referenced in the SQL
statement.
Performance may regress when a SQL statement satisfies all of
the following conditions:
1. OUTER JOIN is contained, and the preserved side is defined
with table expression;
2. a CASE statement or non-column expression is defined in the
SELECT list of the above table expression;
3. a table expression column which corresponds to the CASE
statement or non-column expression from condition #2 is
referenced in predicate of the SQL statement.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
MULTSYS:
***Action for PM55928:
PM55928 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via another APAR
PM56631. At this time, all of the changes are transparent to the
user. In a data sharing group, this pre-conditioning APAR should
be applied to all members before the later enabling APAR PM56631
1 is applied to any member. The new function is not enabled until
the enabling APAR PM56631 is applied.
If the new function will not be used, then there is no need to
take precautions for rolling through the pre-conditioning PTF
ahead of the enabling PTF. Instead, both pre-conditioning PTF
and enabling PTF can be rolled through together.
In addition, because the new function can only be used in DB2 10
New Function Mode (NFM), both pre-conditioning PTF and enabling
PTF can be rolled through together on DB2 10 CM subsystems.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEBR PM55928
DSNXGRTM PM55928
DSNXGSFN PM55928
DSNXOBFA PM55928
DSNXOBFF PM55928
DSNXOBF3 PM55928
DSNXOBF4 PM55928
DSNXODSO PM55928
DSNXODTR PM55928
DSNXODTX PM55928
DSNXOFN2 PM55928
DSNXOMTX PM55928
DSNXOOS1 PM55928
DSNXOP0 PM55928
DSNXOSCF PM55928
DSNXOVP PM55928
DSNXRBIN PM55928
DSNXRNUL PM55928
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55928 DSNXEBR DSNXGRTM DSNXGSFN DSNXOBFA DSNXOBFF DSNXOBF3
DSNXOBF4 DSNXODSO DSNXODTR DSNXODTX DSNXOFN2 DSNXOMTX
DSNXOOS1 DSNXOP0 DSNXOSCF DSNXOVP DSNXRBIN DSNXRNUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXGRTM
DSNXGSFN
DSNXOBFA
DSNXOBFF
DSNXOBF3
DSNXOBF4
DSNXODSO
DSNXODTR
DSNXODTX
DSNXOFN2
DSNXOMTX
DSNXOOS1
DSNXOP0
DSNXOSCF
DSNXOVP
DSNXRBIN
1 DSNXRNUL
LISTEND
UK78581 COVER LETTER END
UK78606 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62787 -
****************************************************************
* USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230) *
* users DATASHARING SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: 1. ABEND0C9 in DXRRL732 during IRLM *
* startup while IRLM lock structure *
* rebuild was going on. *
* *
* 2. In IRLM 230 (only) *
* --------------------- *
* - ABENDu2025 in DXRRL2U0 on starting *
* IRLM member due to incorrect IRLM ID *
* usage may also trigger lock structure *
* rebuild as it may max out available *
* connections to the lock strcuture. *
* *
* *
* - ABENDB78-14 in DXRRL070 on FREEMAIN *
* call just after initialization failure *
* DXR116E IRL1001 INITIALIZATION FAILED, *
* CODE=09 DETECTED BY DXRRL0C0 *
* *
* - ABEND0C4-10 in *
* COMPON=TIMER SUPERVISION,COMPID=SC1CV, *
* ISSUER=IEAVRTI1,TIMER FRR *
* after attempt to start IRLM several *
* times on a system. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
1. During IRLM startup, DXRRL732 may do calculations to check
the lock structure usage and incorrectly run into a divide by
zero error causing DXRRL732 to issue ABEND0C9. It may happen
while this member is disconnected from the group and waiting
for IRLM lock structure rebuild to be over. There is a
timing window between IRLM health check run and IRLM trying
re-connect to the lock structure. IRLM health check logic
may find RLE usecount (RLMRLEUS) being non-zero before
reconnect is done and total RLE count (RHTLKRLE) being set.
2. In IRLM 230 (only)
------------------
- Attempt to start IRLM with an IRLM ID already in use by
another IRLM member results in ABENDu2025. This leaves the new
connection to the lock structure in 'Failed Persistent' state.
The increased connection count may also result in reaching the
threshold set for IRLM to rebuild lock structure to allow more
1 connections. This rebuild can be avoided. IRLM should not leave
the failed persistent connection for duplicated IRLM id failure
around.
- During a restart failure IRLM may see ABENDB78-14 in DXRRL070
on a FREEMAIN request for IRLM branch vector table as it did not
get the CML lock to perform the FREEMAIN operation.
- During a restart failure IRLM may not have obtained the
deadlock work area when IRLM ESATE in DXRRL070 gets driven. IRLM
may pick up low core storage to issues DEQ TQE for Deadlock TQE.
This could result in ABEND0C4-10 in TIMER FRR routine in MVS.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
This APAR provids following solutions:
For IRLM 220 and IRLM 230:
-------------------------
A timing window between IRLM health check and IRLM re-connect
to the lock structure is corrected to avoid ABEND0C9 in
DXRRL732.
For IRLM 230 (only):
--------------------
- IRLM will force clear the failed persistent connection when
it disconnects and ABENDu2025 due to duplicate IRLM id.
- IRLM will get the CML lock before calling FREEMAIN to free
the storage for branch vector table (RLMFBTA), to prevent the
ABENDB78-14 in DXRRL070.
- IRLM will ensure that deadlock TQE was obtained before it
attempts to Dequeue the TQE, to prevent ABEND0C4-10 in
timer FRR routine.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM62787
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL070 PM62787
DXRRL711 PM62787
DXRRL732 PM62787
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62787 DXRRL070 DXRRL711 DXRRL732
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL070
DXRRL711
DXRRL732
1
LISTEND
UK78606 COVER LETTER END
UK78609 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61260 -
****************************************************************
* USERS AFFECTED: All DB2 users who cancel a job. *
****************************************************************
* PROBLEM DESCRIPTION: Customer could hit RC00C90101 DSNGEFBK *
* ERQUAL5003 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After applying PM45071, DB2 error handling could incorrectly
restore storage which causes the above abend.
A second problem not related to apar PM45071 is there could be
a storage leak after the cancel.
DB2 code has been changed to avoid restoring the storage unless
it is needed.
This apar also fixes storage leakage caused by a cancel.
keywords: DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61260
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEGFB PM61260
DSNGEPLC PM61260
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61260 DSNGEGFB DSNGEPLC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEGFB
DSNGEPLC
LISTEND
UK78609 COVER LETTER END
UK78632 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM57632 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS utility users *
****************************************************************
1 * PROBLEM DESCRIPTION: Serviceability *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
Serviceability.
Serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM57632
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM57632 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the function the PTF
addresses will not be enabled.
The fix for APAR PM57632 is a companion fix. It requires the
fix for APAR PM60438, for FMID JDBAA1K to be applied.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNFMDIR PM57632
DSNFUDRD PM57632
DSNUGBPL PM57632
DSNUGEPL PM57632
DSNUGPPF PM57632
DSNUGPRS PM57632
DSNUGRAR PM57632
DSNUGRSO PM57632
DSNUGSUG PM57632
DSNUGSUU PM57632
DSNUIEPL PM57632
DSNUMSGD PM57632
DSNURCON PM57632
DSNURELD PM57632
DSNURILD PM57632
DSNURPLD PM57632
DSNURPLL PM57632
DSNURPPD PM57632
DSNURPPI PM57632
DSNURWBF PM57632
DSNURWI PM57632
DSNURWIF PM57632
DSNURWRF PM57632
DSNURWT PM57632
HDBAA10J PM57632
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM57632 DSNFMDIR DSNFUDRD DSNUGBPL DSNUGEPL DSNUGPPF DSNUGPRS
DSNUGRAR DSNUGRSO DSNUGSUG DSNUGSUU DSNUIEPL DSNUMSGD
DSNURCON DSNURELD DSNURILD DSNURPLD DSNURPLL DSNURPPD
DSNURPPI DSNURWBF DSNURWI DSNURWIF DSNURWRF DSNURWT
HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFMDIR
DSNFUDRD
DSNUGBPL
DSNUGEPL
DSNUGPPF
DSNUGPRS
DSNUGRAR
DSNUGRSO
DSNUGSUG
DSNUGSUU
DSNUIEPL
DSNUMSGD
DSNURCON
DSNURELD
DSNURILD
DSNURPLD
DSNURPLL
DSNURPPD
DSNURPPI
DSNURWBF
DSNURWI
DSNURWIF
DSNURWRF
DSNURWT
LISTEND
UK78632 COVER LETTER END
UK78633 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60438 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS utility users *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability. *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
Serviceability.
Serviceability.
The fix for APAR PM60438 is a companion fix. It requires the
fix for APAR PM57632, for FMID HDBAA10 to be applied.
COMPONENT: 5740-XYR00-JDBAA1K
APARS FIXED: PM60438
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The fix for APAR PM60438 is a companion fix. It requires the
fix for APAR PM57632, for FMID HDBAA10 to be applied.
ACTION:
The fix for APAR PM42560 is a companion fix. It requires the
fix for APAR PM27962, for FMID HDBAA10 to be applied.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUFFMF PM60438
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60438 DSNUFFMF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUFFMF
LISTEND
UK78633 COVER LETTER END
UK78678 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60732 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS users *
* All DB2 10 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: Index space map search for free page *
* during index page split takes a long *
* time for large indexes and causes *
* time-outs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 attempts to avoid the cost of an index pageset extend by
first searching all index space map pages for a free page
during index page split. This exhaustive search may take a long
time for large indexes and cause time-outs.
Additional Keywords: MSGDSNT501I RC00C20255
The index space map search algorithm has been enhanced to
utilize page list prefetch for faster search processing. By
reducing the amount of time needed to perform exhaustive space
map searches, this enhancement may reduce the number of
time-outs caused by index space map searches.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60732
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
DSNKSALO PM60732
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60732 DSNKSALO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKSALO
LISTEND
UK78678 COVER LETTER END
UK78700 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60533 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users (CM and above) of *
* ALTER TABLE ADD COLUMN on tables used by *
* bound application plans *
****************************************************************
* PROBLEM DESCRIPTION: The APAR addresses two problems: *
* *
* 1. Incorrect output is possible on *
* tables which have gone through ALTER *
* TABLE ADD COLUMN since arrival to 10 *
* CM or higher, without a subsequent *
* rebind on plans/packages using such *
* tables. *
* *
* 2. ABEND04E RC00E20003 *
* DSNIGSEL.DSNSVBK+070E due to storage *
* leak in the internal DB2 storage pool *
* that is used for P Procs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Problem 1:
In DB2 10 CM or higher, incorrout is possible for a table that
has gone through ALTER TABLE ADD COLUMN in 10 and a REORG, but
no rebind has been done on plans/packages using that table.
In DB2 10, a new, faster predicate evaluation mechanism takes
over - the Predicate Proc (P Proc). The P Proc gets built at
bind time as long as the selection expression does not involve
host variables with LIKE / NOT LIKE predicate. DDL ALTER
TABLE ADD COLUMN will not invalidate bound plans/packages
containing the P Proc. If a REORG is run after the DDL ALTER
ADD COLUMN and then the plan/package itself, the plan/package
may get incorrect output because the P Proc in it may be
affected by the change in positions of columns after REORG and
all rows are currentlevel-versioned.
1 The following is a sample scenario that exposes this problem:
(1) Populate the table with some rows
(2) BIND an SQL SELECT application that does not use host
variables with LIKE/NOT LIKE
(3) ALTER TABLE ADD COLUMN (rows now become downlevel-versioned)
(4) REORG (rows now become currentlevel-versioned)
(5) Run the SQL SELECT application -> Incorrout
Problem 2:
Storage leak may occur in internal DB2 pool CTLNGSTP, with the
pool showing a large number of P Procs built (eyecatcher
'Selp') for the same MSIB block, when rows are downlevel-
versioned. This is not OK because there should be only one
P Proc per MSIB. The symptom of this second problem is
ABEND04E RC00E20003 DSNIGSEL.DSNSVBK+070E.
The root cause for the storage leak is that DB2 forgets to
reset an internal record counter for P Proc building. The
counter keeps incrementing and overflows, leading to a new
P Proc being built every 65,000+ rows.
The following is a sample scenario that exposes this second
problem:
(1) Populate the table with a very large number of rows
(e.g. 70,000+)
(2) BIND an SQL SELECT application that does not use host
variables with LIKE/NOT LIKE
(3) ALTER TABLE ADD COLUMN (rows now become downlevel-versioned)
(4) Run the SQL SELECT application -> Storage leak with Selp's
DB2 code is fixed to associate the table version with the P Proc
that was built at bind time.
At execution time, DB2 will compare the versions of the
evaluated row and the bind-time P Proc. If they match, the code
will use the bind-time P Proc, otherwise it will build a new
P Proc on the fly.
Due to this building of P Proc at execution time, after applying
this PTF, applications that have not been rebound since ALTER
TABLE ADD COLUMN might experience performance degradation. To
improve the performance of these applications, they can be
rebound.
For any table that has gone through ALTER TABLE ADD COLUMN since
arrival in 10, a query such as this one can be used to identify
any plans/packages that use the table but have not been rebound
since the ALTER:
SELECT PKG.COLLID, PKG.NAME, PKG.TYPE
FROM SYSIBM.SYSPACKAGE PKG,
SYSIBM.SYSPACKDEP PKD,
SYSIBM.SYSTABLES TAB,
1 SYSIBM.SYSCOLUMNS COL
WHERE PKG.COLLID = PKD.DCOLLID
AND PKG.NAME = PKD.DNAME
AND PKG.CONTOKEN = PKD.DCONTOKEN
AND TAB.CREATOR = PKD.BQUALIFIER
AND TAB.NAME = PKD.BNAME
AND PKD.BTYPE = 'T'
AND TAB.CREATOR = COL.TBCREATOR
AND TAB.NAME= COL.TBNAME
AND TAB.CREATEDTS < COL.CREATEDTS
AND COL.CREATEDTS > PKG.BINDTIME;
Additional keywords: DB2INCORR/K SQLINCORR SQLINCORROUT
DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60533
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM60533:
See PM60533 APAR/PTF text for additional information about
why a REBIND is recommended.
After you apply this PTF, some applications might experience
performance degradation. To improve the performance of those
applications, rebind their plans and packages.
Review the PTF cover letter to determine which, if any,
applications could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIACCH PM60533
DSNIADR PM60533
DSNICRFT PM60533
DSNIESEN PM60533
DSNIGSEL PM60533
DSNIHSET PM60533
DSNIMNEX PM60533
DSNIONX2 PM60533
DSNIOST2 PM60533
DSNIRNXT PM60533
DSNIRPRE PM60533
DSNIRSET PM60533
DSNISFRL PM60533
DSNISFS PM60533
DSNISFWL PM60533
DSNISFX2 PM60533
DSNISRID PM60533
DSNIWNRF PM60533
DSNUUSEL PM60533
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60533 DSNIACCH DSNIADR DSNICRFT DSNIESEN DSNIGSEL DSNIHSET
DSNIMNEX DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNIRSET
1 DSNISFRL DSNISFS DSNISFWL DSNISFX2 DSNISRID DSNIWNRF
DSNUUSEL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNIADR
DSNICRFT
DSNIESEN
DSNIGSEL
DSNIHSET
DSNIMNEX
DSNIONX2
DSNIOST2
DSNIRNXT
DSNIRPRE
DSNIRSET
DSNISFRL
DSNISFS
DSNISFWL
DSNISFX2
DSNISRID
DSNIWNRF
DSNUUSEL
LISTEND
UK78700 COVER LETTER END
UK78722 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63188 -
****************************************************************
* USERS AFFECTED: All DB2 10 users of RESTORE SYSTEM Utility. *
****************************************************************
* PROBLEM DESCRIPTION: RESTORE SYSTEM UTILITY LOG APPLY PHASE *
* ABENDED ON RC00E40311 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During Restore System log apply phase, Data Manager (DM)
acquires the storage for Page set Description Block (PDA) and
Piece Description Block (PDP) for each active (R/W state)
recoverable page set. These blocks are used to open the page
set, if necessary. However, each block entry gets very large
when Non-Partition Indexes (NPIs) are involved,
especially the NPIs on Partition By Growth (PBG) table spaces.
If RESTORE SYSTEM involves several thousand of such PBGs and
several thousand NPIs then the storage pool (ACOMPH21 or
CT64BSTP) used to build PDA/PDP blocks gets exhausted which
results in Restore System terminating with the reason code
RC00E40311. To avoid this storage constraint during RESTORE
SYSTEM, Data Manager Restart (DMRR) logic will acquire the
minimum amount of storage for control blocks (PDA/PDP) needed
to open the data set. This will significantly reduce the
1 storage needed to build all the necessary PDA/PDP control
blocks, thus avoiding out of storage condition during RESTORE
SYSTEM log apply phase.
DB2 RESTORE SYSTEM logic is modified to reduce the storage usage
to avoid storage shortage which prevents premature termination
of RESTORE SYSTEM log apply phase.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63188
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILOGA PM63188
DSNIRCSB PM63188
DSNIRSTR PM63188
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63188 DSNILOGA DSNIRCSB DSNIRSTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILOGA
DSNIRCSB
DSNIRSTR
LISTEND
UK78722 COVER LETTER END
UK78723 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61344 -
****************************************************************
* USERS AFFECTED: All DB2 users of stored procedure packages. *
****************************************************************
* PROBLEM DESCRIPTION: An EDM POOL FULL condition occurred *
* with the following console message: *
* DSNT500I DSNGEPLC RESOURCE *
* UNAVAILABLE *
* REASON 00C90089 *
* TYPE 00000600 *
* NAME EDM POOL SPACE *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An application was designed to make several updates to a table
without a commit. The table has an update trigger that invokes
a stored procedure to make an update to a similar table on a
remote DB2. The first time the application would run without
any problems. The second time the application was run the
application would fail with a resource unavailable on the
remote system:
DSNT500I DSNGEPLC RESOURCE
1 UNAVAILABLE
REASON 00C90089
TYPE 00000600
NAME EDM POOL SPACE
When a stored procedure accesses a remote DB2 it can cause
multiple copies of package sections to be loaded into the EDM
pool until a commit is issued to release the storage. DB2
code looks at the storage used during each run of a package to
optimize future executions. This code incorrectly caused
larger blocks of storage to be used for each section on the
subsequent runs causing the full condition. The storage would
be freed on commit.
Multiple copies of packages sections can also occur at the
local DB2 by repeated calls to a stored procedure when the
stored procedure result sets are left open. Subsequent runs
of the same workload could also cause the resource
unavailable error.
A second problem was discovered on a DB2 V9. The type was
incorrectly displayed as 600 in the DSNT500I message . It
should have shown a type of 605.
The code has been updated to correct both problems.
Additional Keywords: MSGDSNT500I RC00C90089 SQLSP SQLSTOREDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61344
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 PM61344
DSNGESFR PM61344
DSNXELX PM61344
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61344 DSNGEPLC DSNGESFR DSNXELX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPLC
DSNGESFR
DSNXELX
LISTEND
UK78723 COVER LETTER END
UK78782 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62301 -
1 ****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 in DSNB1CMS, followed by DB2 *
* abnormal termination. *
* *
* ABEND0C4 may also occur in numerous *
* other DSNBxxxx CSECTs. *
* *
* ABEND04E RC00C20305 in DSNB1SWS. *
* *
* Looping in DSNB1CMS or DSNB1CHK. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For DB2 V10 in data sharing, there's a possibility that a
pageset or partition being physically closed will have its PB0
control block sitting on the deferred write queue (DWQ) when the
code reaches the point of either freeing the PB0 or putting it
on the dormant PB0 chain. Although code exists to detect this
and remove the PB0 from the DWQ, it is not properly serialized
with other processes which may be concurrently removing it.
This may allow the close to free the PB0 or link it to the
dormant chain while it is still pointed to by another PB0 on the
DWQ, which in turn can cause processes going through the DWQ to
run into freed storage, or active PB0s to be incorrectly freed.
The most likely symptom is an ABEND0C4 in DSNB1CMS or some other
DSNBxxxx module, possibly causing DB2 to crash.
The physical close logic has been modified to acquire the DWQ
latch before checking to see if the PB0 is on the DWQ.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62301
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 PM62301
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62301 DSNB1CPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPP
LISTEND
UK78782 COVER LETTER END
UK78785 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55803 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
1 * users of the following DDL statements: *
* ALTER INDEX *
* ALTER TABLE *
* ALTER TABLESPACE *
* DROP INDEX *
* DROP TABLE *
* DROP TABLESPACE *
****************************************************************
* PROBLEM DESCRIPTION: DML may result in ABEND04E *
* RC00C90101 DSNIONX2:2007 when *
* running concurrently with ALTER *
* TABLESPACE MAXPARTITIONS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DML may result in ABEND04E RC00C90101 DSNIONX2:2007 when
running concurrently with ALTER TABLESPACE MAXPARTITIONS due
to a timing window problem. Unexpected results and other
ABEND04E RC00C90101 such as DSNISGRT:2005, DSNIOST2:200F,
DSNKINSL:5033, and DSNKDLE:500A may also occur.
Additionally, running the following DDL statements
concurrently with DML may also have a similar timing window
problem which may cause data corruption and other unexpected
results.
ALTER INDEX
ALTER TABLE
ALTER TABLESPACE
DROP INDEX
DROP TABLE
DROP TABLESPACE
The following statements have been modified to acquire an
update lock on SYSIBM.SYSTABLESPACE for the object's
associated table space to prevent a possible timing window
problem.
ALTER INDEX
ALTER TABLE
ALTER TABLESPACE
DROP INDEX
DROP TABLE
DROP TABLESPACE
As a result, running concurrent DML with the above DDLs may
be more likely to result in a timeout (SQLCODE -904, SQLCODE
-911, SQLCODE -913). This APAR will not fix existing objects.
ADDITIONAL KEYWORDS:
SQLDROP
SQLALTER
SQLCODE904
SQLCODE911
SQLCODE913
DB2INCORR/K
SQLINCORR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55803
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
PM57001 introduces the following changes to externals and the
approximate text will be added to the V10 DB2 SQL Reference.
This text is subject to change.
Changed option for ALTER TABLESPACE MAXPARTITIONS:
Specifies that the table space is partition-by-growth. integer
specifies the maximum number of partitions to which the table
| space can grow or shrink. integer must be in the range of 1 to
4096, depending on the value that is in effect for DSSIZE and
the page size of the table space, and must not be less than
| the number of physical partitions already allocated for the
table space. See CREATE TABLESPACE for more information about
how DSSIZE and the page size are related.
Information about this changed option will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIAIX PM55803
DSNXIATS PM55803
DSNXIDIX PM55803
DSNXIDTB PM55803
DSNXIDTS PM55803
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55803 DSNXIAIX DSNXIATS DSNXIDIX DSNXIDTB DSNXIDTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIAIX
DSNXIATS
DSNXIDIX
DSNXIDTB
DSNXIDTS
LISTEND
UK78785 COVER LETTER END
UK78787 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60674 -
****************************************************************
* USERS AFFECTED: All DB2 z/OS V10 users of Universal Table *
* Space or Segmented table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: High latch contention on the space *
* map page when batch job scales *
* workload to approximately 130 *
* concurrent processes running in a *
1 * one-way data sharing environment. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A S or X page latch is acquired to update the space map page.
The high volume of parallel concurrent insert transactions
can increase the frequency of space map page latch contention
within the same data sharing member. As a result, insert
performance is degraded.
DB2 code is modified to classify the update activities of
a space map page into critical and non-critical updates.
The data page space setting from empty to non-empty or
non-full to full are considered as critical updates.
Any other data page space class updates are considered
non-critical updates.
As a result, a conditional s-latch is used to perform a
non-critical update. If the s-latch can not be obtained, then
the information on the space map page will still be updated
except there is the possibility this information will not
be written out to the group buffer pool or DASD.
In addition, the data page in the buffer pool will not be
released until the subsequent insert for compressed table
space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60674
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISGRT PM60674
DSNISGSU PM60674
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60674 DSNISGRT DSNISGSU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGRT
DSNISGSU
LISTEND
UK78787 COVER LETTER END
UK78788 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61352 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* customers who use CREATE TABLE with OBID 1 *
* specified. *
****************************************************************
* PROBLEM DESCRIPTION: Performing a version-generating *
* alter on a table with an OBID of 1 *
1 * may result in unexpected output on *
* subsequent insert. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Specifying CREATE TABLE with OBID 1 is incorrectly allowed.
As a result, performing a version generating alter on a
table with OBID 1 may result in unexpected results on
subsequent operations such as DML, LOAD, and REORG. Other
unexpected errors may also occur.
DB2 has been modified to issue SQLCODE -736 when CREATE TABLE
is specified with OBID 1. Existing tables with OBID 1 should
be dropped and recreated with a different OBID.
A query, such as the sample query below may be used to
identify tables with OBID 1.
SELECT * FROM SYSIBM.SYSTABLES
WHERE OBID = 1
AND ( TYPE = 'T'
OR TYPE = 'M'
OR TYPE = 'H' ) ;
The approximate text will be updated in the DB2 SQL Reference
and Codes manual. This text is subject to change.
=============
SQL Reference
=============
CREATE TABLE->OBID integer
Identifies the OBID to be used for this table. An OBID is
the identifier for an object's internal descriptor. The
| integer must be greater than 1 and not identify an existing
or previously used OBID of the database. If you omit OBID,
DB2 generates a value.
=====
Codes
=====
-736
The specified OBID does not fall within the acceptable range
| for OBIDs, which is 2 to 32767.
ADDITIONAL KEYWORDS:
SQLCREATE
SQLALTER
DB2INCORR/K
SQLINCORR
SQLINCORROUT
SQLCODE736
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61352
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
1 PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE
is specified with OBID 1. The approximate text will be
updated in the DB2 SQL Reference and Codes manual. This text
is subject to change.
=============
SQL Reference
=============
CREATE TABLE->OBID integer
Identifies the OBID to be used for this table. An OBID is
the identifier for an object's internal descriptor. The
| integer must be greater than 1 and not identify an existing
or previously used OBID of the database. If you omit OBID,
DB2 generates a value.
=====
Codes
=====
-736
The specified OBID does not fall within the acceptable range
| for OBIDs, which is 2 to 32767.
ACTION:
PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE
is specified with OBID 1. Existing tables with OBID 1 should
be dropped and recreated with a different OBID.
A query, such as the sample query below may be used to
identify tables with OBID 1.
SELECT * FROM SYSIBM.SYSTABLES
WHERE OBID = 1
AND ( TYPE = 'T'
OR TYPE = 'M'
OR TYPE = 'H' ) ;
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICTB PM61352
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61352 DSNXICTB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICTB
LISTEND
UK78788 COVER LETTER END
UK78834 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60751 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS NFM users who used a *
* LOCK TABLE statement on a UTS table AFTER *
1 * performing a commit for a cursor hold select *
* from the same table. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND 04E-RC00C90101 in DSNICMTC *
* ERQUAL1005. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A commit ran into an abend with RC00C90101 ERQUAL1005 which
indicates an invalid lock token while DB2 attempts to modify a
mass delete lock on a UTS table from COMM+1 to COMM duration.
For a UTS table under z/OS 10 system NFM, DB2 mistakenly
acquired a mass delete lock for the table under the LOCK TABLE
statement.
DB2 code is modified to skip the acquisition of a mass delete
lock for a UTS table under the LOCK TABLE statement in NFM.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60751
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILRBK PM60751
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60751 DSNILRBK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILRBK
LISTEND
UK78834 COVER LETTER END
UK78883 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63007 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of *
* DB2 inactive connections with distributed *
* applications bound with KEEPDYNAMIC(YES) *
****************************************************************
* PROBLEM DESCRIPTION: On a DB2 10 for z/OS Application Server *
* the following DB2 abend occurred for *
* a distributed application bound *
* KEEPDYNAMIC(YES) and issuing dynamic *
* SQL COMMITs when DB2 inactive *
* connections are used: *
* ABEND04E RC00D31010 AT DSNLQINA :0015 *
* *
* On a DB2 9 for z/OS Application Server, *
* for the above scenario other unexpected *
* errors or DB2 DDF abends may occur. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
When using DB2 10 for z/OS inactive connections (DSN6FAC
CMTSTAT=INACTIVE), DB2 internal sanity-check abend
.
ABEND04E RC00D31010 at DSNLQINA :0015
.
occurred at the DB2 10 for z/OS Application Server (AS) for
a distributed application, if the application is bound
KEEPDYNAMIC(YES) and issues
- either a dynamic SQL COMMIT without performing previous SQL
operations in that UOW (unit-of-work), or
- successive dynamic SQL COMMITs without intervening SQL
operations between the COMMITs.
The DSNLQINA abend occurs on the second COMMIT when DB2 attempts
to 'inactivate' the distributed DB2 connection. The abend is
intended and detects when DB2 has inconsistent internal
KEEPDYNAMIC indicators for the DB2 distributed thread at
the point when DB2 DDF attempts to inactivate the distributed
connection. For the COMMIT scenarios described above,
this DB2 internal inconsistency resulted, hence the DSNLQINA
abend.
DB2 AS code was modified to correctly handle the previously
described distributed KEEPDYNAMIC with COMMIT scenarios when
using DB2 DDF inactive connections.
.
Additional keywords: AB04E 00D31010 OFFSET0015
DB2DDF DB2DRDA DB2INACTIVE SQLDRDA
SQLCOMMIT SQLDYNAM CMTSTAT INACTIVE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63007
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXERT PM63007
DSNXERT2 PM63007
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63007 DSNXERT DSNXERT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXERT
DSNXERT2
LISTEND
UK78883 COVER LETTER END
UK78929 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60130 -
1 ****************************************************************
* USERS AFFECTED: DB2 10 for z/OS internal testing users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 INTERNAL SERVICEABILITY CHANGE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 INTERNAL SERVICEABILITY.
Code change for DB2 INTERNAL SERVICEABILITY.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60130
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWHS PM60130
DSNICPGE PM60130
DSNIDILS PM60130
DSNILREP PM60130
DSNISGRT PM60130
DSNISMRT PM60130
DSNWVINT PM60130
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60130 DSNDQWHS DSNICPGE DSNIDILS DSNILREP DSNISGRT DSNISMRT
DSNWVINT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICPGE
DSNIDILS
DSNILREP
DSNISGRT
DSNISMRT
DSNWVINT
MACROS
DSNDQWHS
LISTEND
UK78929 COVER LETTER END
UK79001 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60340 -
****************************************************************
* USERS AFFECTED: All users of DB2 UDB for z/OS Version 9 *
* ODBC/CLI and DB2 10 for z/OS ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: After applying V9 PTF UK71562 and *
* V10 PTF UK71561, if a group attachment *
* name is specified for the *
* MVSDEFAULTSSID keyword in the ODBC *
1 * initialization file, SQLAllocConnect() *
* or SQLAllocHandle() with SQL_HANDLE_DBC *
* may fail with CAF attachment errors *
* (SQLSTATE 58004) when running in a *
* multi-threaded environment with *
* MVSATTACHTYPE=RRSAF and MULTICONTEXT=0. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a group attachment name is specified for the MVSDEFAULTSSID
keyword in the ODBC initialization (INI) file, recent changes
by APAR PM25678 introduced an error that could cause
SQLAllocConnect() or SQLAllocHandle() to fail with a CAF
attachment error when allocating a connection handle with
MVSATTACHTYPE=RRSAF, resulting in an error message similar to
the following being returned to the application:
{DB2 FOR OS/390}{ODBC DRIVER} SQLSTATE=58004 ERRLOC=2:171:3
CAF "CLOSE" failed using DB2 system:xxxx
RC=40404040 and REASON=d3c1e3c5
where xxxx is the DB2 subsystem name.
This problem can occur under certain scenarios when ODBC uses
the DB2 subsystem's member name to attach to DB2. Because the
member name is not found in the initialization file, the driver
defaults to using CAF.
Code has been changed to correctly preserve the group attachment
name in certain scenarios when the subsystem's member name
is used to attach to DB2.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PM60340
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
This PTF introduces the following changes to DB2 ODBC externals:
New DB2 ODBC for z/OS initialization keywords described as
follows.
LIMITEDBLOCKFETCH = 0 | 1
This keyword is a performance optimization keyword that
specifies whether DB2 ODBC is to attempt limited block fetch
when fetching result sets from the connected data source.
0 = Limited block fetch is not used. 0 is the default.
1 = DB2 ODBC attempts to use limited block fetch. If blocking
is supported at the server for the result set that is
being fetched, DB2 ODBC retrieves as many rows as it can
fit in a query data block in a single fetch request.
QUERYDATASIZE = integer
This keyword specifies the amount of query data, in bytes, that
DB2 returns on each FETCH operation when limited block fetch is
enabled. The default value is 32767. Possible values are:
32767 294911 557055 819199
65535 327679 589823 851967
1 98303 360447 622591 884735
131071 393215 655359 917503
163839 425983 688127 950271
196607 458751 720895 983039
229375 491519 753663 1015807
262143 524287 786431 1048575
If you specify a value that is not a valid value, DB2 ODBC sets
QUERYDATASIZE to the nearest valid value.
Information about the new DB2 ODBC initialization keywords
and DB2 ODBC limited block fetch will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.
DOCUMENTATION:
*** Documentation for PM25678 (Version 10)
A new initialization keyword, INTERRUPT, has been added to allow
you to specify the interrupt processing mode when SQLCancel()
is called to cancel the processing on a statement.
Complete documentation for the SQLCancel() API will be provided
in the DB2 10 for z/OS ODBC Guide and Reference and in the
Information Management Software for z/OS Solutions Information
Center.
ACTION:
*** Action for PM32032 (Version 10)
The following database request module (DBRM) is updated by
this PTF:
DSNCLIQR
Application of this PTF requires a BIND PACKAGE for the above
package. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
ACTION:
The following database request modules (DBRMs) are updated by
this PTF:
DSNCLINF
DSNCLIC1
DSNCLIMS
DSNCLIQR
DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only)
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
1 for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
This PTF introduces two new DB2 ODBC initialization keywords
LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block
fetch. Limited block fetch is a performance optimization that
enables applications to improve the performance of FETCH
operations when connected to a local DB2 for z/OS server.
If limited block fetch is not desired, no further action is
necessary other than rebinding the DBRMs listed above;
otherwise please note the following.
When you enable limited block fetch, the data that is returned
to your application might not reflect the data that has been
committed to the source table. If your application fetches
data from tables that are updated by other users, or if your
application uses savepoints and issues ROLLBACK TO SAVEPOINT
to manage transactions, you should disable limited block fetch.
ACTION:
This PTF updates DB2 ODBC for z/OS database request module
(DBRM) DSNCLIC1.
After you apply this PTF, you need to run the BIND PACKAGE
command to recreate the package for DSNCLIC1. Failure to bind
the required package could result in SQLCODE -805 at application
run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
prefix.SDSNSAMP data set for an example of how to perform the
BIND command.
ACTION:
The following database request modules (DBRMs) for ODBC
DB2 for z/OS are updated by this PTF:
DSNCLIMS
DSNCLIC1
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
SDSNSAMP dataset for an example of how to perform the
BIND command.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG0J PM60340
DSNAOCLI PM60340
DSNAOSDK PM60340
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60340 DSNAOG0J DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNAOC24
DSNAOC03
DSNAOC06
DSNAOC28
CLIMVSF6
DSNAOC27
DSNAOC22
DSNAOC14
DSNAOC15
DSNAOC1U
DSNAOG02
DSNAOG24
DSNAOG03
DSNAOG04
DSNAOG1R
DSNAOG05
DSNAOG06
DSNAOG28
DSNAOG08
DSNAOG0A
DSNAOG1Q
DSNAOG1S
DSNAOG0C
DSNAOG0E
DSNAOG0I
DSNAOG0J
DSNAOG0O
DSNAOG1W
DSNAOG25
DSNAOG0Q
DSNAOG0R
DSNAOG27
DSNAOG0S
DSNAOG0T
DSNAOG26
DSNAOG0U
DSNAOG22
DSNAOG0W
DSNAOG13
DSNAOG14
DSNAOG15
DSNAOG16
DSNAOG1V
DSNAOG17
DSNAOG1U
DSNAOCLI
DSNAOTRC
DSNAOC0G
DSNAOC0F
DSNAOC21
DSNAOC0P
DSNAOC07
DSNAOG0G
DSNAOG0F
DSNAOG21
1 DSNAOG0P
DSNAOG07
DSNAOC1L
DSNAOG1L
MACROS
DSN@LIC1
DSN@LIMS
DSN@LINF
DSN@LIQR
DSN@LIV1
DSNAOSDK
LISTEND
UK79001 COVER LETTER END
UK79004 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61555 -
****************************************************************
* USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) *
* SYSPLEXDS DATASHARING users. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM issued message: *
* *
* DXR139E IRLMxxx IXLREBLD(STOP) REQUEST *
* FAILED, RETURN=0C REASON=020C0C36 *
* *
* then abended U2022 while joining the *
* data sharing group. *
* *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
The structure was in duplexing mode. A member with a lower
function level tried to join the group. IRLM initiated a lock
structure rebuild to bring the whole group to the same function
level.
In order to start a coexist rebuild, IRLM stopped the
on-going duplex rebuild, built and queued a rebuild QE. Before
the stop duplex rebuild was completed, the rebuild start QE was
processed. This caused the IXLREBLD START failed with RC=0C and
REASON=020C0C36.
Also, message MSGDXR139E had the incorrect IXLREBLD request.
The request type should be IXLREBLD START instead of IXLREBLD
STOP.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code is added to prevent the queueing of the rebuild QE
before the structure falls back to simplex mode.
1 Also, the IXLREBLD request type in message DXR139E is
corrected from IXLREBLD(STOP) to IXLREBLD(START).
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PM61555
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL070 PM61555
DXRRL710 PM61555
DXRRL712 PM61555
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61555 DXRRL070 DXRRL710 DXRRL712
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL070
DXRRL710
DXRRL712
LISTEND
UK79004 COVER LETTER END
UK79008 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61349 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of DECRYPT built-in functions. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 rc4 can occur at location *
* DSNXRSBC+4F8E OFFSET4F8E or at *
* DSNXRSBC+7842 OFFSET7842 (v9 offsets) *
* when using a DECRYPT built-in function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 rc4 can occur at location DSNXRSBC+4F8E when using
the DECRYPT_CHAR built-in function or at location DSNXRSBC+7842
when using the DECRYPT_BIT built-in function. The failure
occurs when DB2 tries to set a null byte for a non-nullable
result when trying to setup issuing an SQLCODE20224 (SQL code
+20224) WARNING. A null byte should not be set if the result is
non-nullable. Instead, an SQLCODE -20224 should be expected.
The problem was reported using a CTE query but the problem can
occur otherwise.
The following examples help to illustrate the problem.
1 EXAMPLE 1.
Step 1. Create the following Table.
CREATE TABLE T1_PRICE (
PRICE_DATE DATE NOT NULL,
LAST_CHANGED TIMESTAMP NOT NULL,
LAST_UPDATED_BY VARBINARY(48) NOT NULL )
CCSID EBCDIC ;
Step 2. Perform the following insert using an ENCRYPTION
password.
SET ENCRYPTION PASSWORD 'DOGCAT';
INSERT INTO T1_PRICE VALUES
('2007-02-09', '2007-02-08-09.23.14.340567',
ENCRYPT_TDES(CAST('TechBBB' AS BINARY)));
Step 3. Perform the following query which will result in an
ABEND0C4 rc4 at location DSNXRSBC+4F8E.
SELECT DECRYPT_CHAR(LAST_UPDATED_BY)
FROM T1_PRICE T1 ;
Since the first argument can't be null, the result can't be null
so an SQLCODE20224 (or -20224) is the expected result.
SQLCODE = -20224, ERROR: ENCRYPTED DATA THAT WAS ORIGINALLY A
BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING
EXAMPLE 2.
If in the first example, column LAST_UPDATED_BY is defined as
VARBINARY(48), the query
SELECT DECRYPT_CHAR(LAST_UPDATED_BY)
FROM T1_PRICE T1 ;
does not result in an ABEND. However, the expected result is an
SQLCODE20224 (or +20224) because since the first argument can be
null, the result can be null.
EXAMPLE 3.
When using a CTE, these two cases result in an abend.
ENCRYPT can be specified as a synonym for ENCRYPT_TDES.
Case 1. This query referencing the DECRYPT_CHAR function
results in an ABEND0C4 rc4 at location DSNXRSBC+4F8E.
1 WITH ENCR AS ( SELECT ENCRYPT( CAST
('F53F47DA-ED1C-E8C9-47C9-369C7418D3B2'
AS BINARY ), 'MSTAR ' ) AS CRYPVAL
FROM SYSIBM.SYSDUMMY1 )
SELECT DECRYPT_CHAR ( CRYPVAL,'MSTAR ') FROM ENCR;
Case 2. This query referencing the DECRYPT_BIT function
results in an ABEND0C4 rc4 at location DSNXRSBC+7842.
WITH ENCR AS ( SELECT ENCRYPT( CAST
('F53F47DA-ED1C-E8C9-47C9-369C7418D3B2'
AS BINARY ), 'MSTAR ' ) AS CRYPVAL
FROM SYSIBM.SYSDUMMY1 )
SELECT DECRYPT_BIT ( CRYPVAL,'MSTAR ') FROM ENCR;
Since the first argument can't be null, the result can't be null
so an SQLCODE20224 (or -20224) is the expected result.
SQLCODE = -20224, ERROR: ENCRYPTED DATA THAT WAS ORIGINALLY A
BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING
In the error case, since the result cannot be nullable, DB2
should not be trying to issue an +20224 WARNING. Instead, an
SQLCODE -20224 ERROR should be issued.
If the result can be nullable, an SQLCODE +20224 WARNING will be
issued with a friendly null.
If the result is not-nullable, an SQLCODE -20224 ERROR will be
issued.
Additionally, please note the following.
1. Similar failures can occur when using the DECRYPT_DB built-in
function.
2. The same problems described above when using the
DECRYPT_CHAR or DECRYPT_BIT built-in functions can also occur
when an SQLCODE331 condition is detected. If the result can be
nullable, an SQLCODE +331 WARNING will be issued with a friendly
null. If the result is not-nullable, an SQLCODE -331 ERROR will
be issued.
The code in DB2 runtime is modified to set the null byte
properly for the result of one of the DECRYPT functions,
DECRYPT_CHAR, DECRYPT_BIT, or DECRYPT_DB. This will prevent the
abend from occurring and allow the proper SQLCODE20224 to be
issued as expected. That is, a +20224 is issued for a nullable
result with a friendly null or a -20224 is issued for a not
nullable result. The same condition is corrected for SQLCODE331.
Additional Keywords: SQLDECRYPT SQLENCRYPT SQLCODE20224
SQLCODE331
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61349
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
DSNXRDBC PM61349
DSNXRDB9 PM61349
DSNXRSBC PM61349
DSNXRSB9 PM61349
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61349 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDBC
DSNXRDB9
DSNXRSBC
DSNXRSB9
LISTEND
UK79008 COVER LETTER END
UK79011 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63099 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* queries that contain an IN predicate and *
* INLIST access ('N', INLIST access path *
* selection ) is chosen. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result set (less rows than *
* expected) may be returned for a query *
* that contains an IN predicate and *
* INLIST access ('N', INLIST access *
* path selection) is chosen. *
* *
* The INLIST contains an element which is *
* a nullable host variable whose data *
* type and/or length differs from the *
* table column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result set (less rows than expected) may be
returned for a query that contains an IN predicate with INLIST
access ('N', INLIST access path selection is chosen).
The INLIST contains an element which is a NULLABLE host variable
whose datatype and/or length are different from the table
column.
The following example helps illustrate a failing case.
1 1. Create a Table.
CREATE TABLE SYSADM.LINEITEM (
L_QUANTITY FLOAT NOT NULL,
L_COMMENT VARCHAR(3) NOT NULL) ;
2. Create an Index.
CREATE INDEX INDEX1 ON SYSADM.LINEITEM (L_COMMENT) ;
3. Populate the Table.
Insert some data into the Table.
4. Select from the Table.
SELECT L_COMMENT, L_QUANTITY
FROM SYSADM.LINEITEM
WHERE L_QUANTITY = 17
AND L_COMMENT IN (:inCm1 :iCm1, :inCm2 :iCm2,
:inCm3 :iCm3, :inCm4 :iCm4,
:inCm5 :iCm5)
ORDER BY L_COMMENT ;
5. Check the results.
For the above query, please note the following:
a. The L_COMMENT column has an index defined on it.
b. The L_COMMENT column is defined as VARCHAR(3) NOT NULL.
c. When preparing the query, INLIST access ('N') is chosen.
d. Given, in the above query, the 2nd host variable
has a value of 'acco'. It has a length of 4.
e. In the above query, the host variable's length of 4 is
longer than the length of L_COMMENT column which is 3.
f. In this case, if the input value of the 3rd host variable
is NULL, DB2 may potentially skip all other host variables
in the INLIST which follow which are nullable.
As a result, an incorrect result set (less rows than expected)
may be returned because DB2 does not process the INLIST element
correctly after the 'failed length comparison' for an INLIST
element.
The code in DB2 is modified to process queries that contain an
IN LIST properly.
Additional Keywords: SQLIN INLIST SQLINCORR SQLINCORROUT
INCORROUT DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63099
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
DSNXRFC PM63099
DSNXRFC9 PM63099
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63099 DSNXRFC DSNXRFC9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRFC
DSNXRFC9
LISTEND
UK79011 COVER LETTER END
UK79013 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM64065 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of utilities. *
****************************************************************
* PROBLEM DESCRIPTION: THIS IS A FLASHCOPY SERVICEABILITY *
* ENHANCEMENT WHICH DOES NOT AFFECT *
* ANY EXTERNAL FUNCTION. *
* NO PROBLEM IS FIXED BY THIS APAR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This is a serviceability enhancement for DB2 for z/OS Flashcopy
utilities.
Serviceability apar only.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM64065
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM64065 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
ACTION:
After applying the fix for PM31180 in DB2 10 for z/OS,
1 FLASHCOPY IMAGE COPIES of partitioned objects with more
than one partition or of linear objects containing more than
one piece will insert a string of the form
database-name.space-name into the DSNAME (data set name)
column of the SYSCOPY record it writes for the FLASHCOPY
record with DSNUM 0, similar to SYSCOPY records that are
currently written for various types of non-backup activity.
This is done to prevent invalid data set names from being
written in these records. Users or automated programs
sensitive to the contents of SYSIBM.SYSCOPY are advised.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCASA PM64065
DSNUGFCB PM64065
DSNUGFCR PM64065
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM64065 DSNUCASA DSNUGFCB DSNUGFCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCASA
DSNUGFCB
DSNUGFCR
LISTEND
UK79013 COVER LETTER END
UK79014 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62449 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS V10 users of segmented table *
* space which contains a table with OBID = 1 *
****************************************************************
* PROBLEM DESCRIPTION: Reorg of segmented table space skips *
* records whose table OBID equals to 1 *
* and causes data loss. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 for z/OS uses 1 as OBID for system page which stores data
versioning records from ALTER table statement.
In DB2 V10, during unload phase of REORG SORTDATA NO of
segmented table space, any record belonging to user table that
has OBID 1 was processed as a data versioning record. Therefore,
these records were skipped during unload phase of the REORG
utility and resulted in data loss. Other utilities include
UNLOAD, Runstats, etc.
To identify any victim tables, the customer can check the
catalog table SYSIBM.SYSTABLES with the following query:
SELECT CREATOR, NAME FROM SYSIBM.SYSTABLES WHERE OBID = 1;
1 DDL APAR PM61352 blocks creation of table with OBID = 1. So with
PM61352 applied, no new tables will hit such data loss problem.
DB2 data manager code is fixed to check the system segment flag
for user table space instead of OBID = 1 for system segments.
Since some catalog or directory tables may not have system
segment flag set, DB2 will continue to use OBD = 1 to identify
the system segments for catalog and directory tables.
As the result, this fix will avoid the data loss problem against
tables whose OBID is 1 during table space scan by Utilities,etc.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62449
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISNPG PM62449
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62449 DSNISNPG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISNPG
LISTEND
UK79014 COVER LETTER END
UK79015 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62096 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of LOAD SHRLEVEL *
* CHANGE loading LOB data with file reference *
* variables (FRV). *
****************************************************************
* PROBLEM DESCRIPTION: A LOAD RESUME SHRLEVEL CHANGE with FRV *
* LOB data abended with ABEND04E *
* RC00E40350 DSNURWBF OFFSETE87C after a *
* duplicate index key was detected. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A LOAD RESUME SHRLEVEL CHANGE was loading LOB data with an FRV
into a table which has only one LOB column. A duplicate index
key was detected and message DSNU1117I was issued. The LOAD
utility abended with ABEND04E RC00E40350 at DSNURWBF + x'E87C'
with RC00C90077.
This problem occurred because the LOAD utility was trying to
release the storage of a non-existent LOB locator during the
clean up processing.
The same abend would occur when processing an empty FRV LOB.
1 The code has been changed to check if the LOB locator exists
before releasing it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62096
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 PM62096
DSNURWBG PM62096
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62096 DSNURWBF DSNURWBG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURWBF
DSNURWBG
LISTEND
UK79015 COVER LETTER END
UK79017 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62825 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of UNLOAD utility *
****************************************************************
* PROBLEM DESCRIPTION: 1. UNLOAD DELIMITED of a table with a *
* DECFLOAT column results in INCORROUT *
* in DB2 9. *
* *
* 2. UNLOAD of a table with a nullable *
* varying length column results in *
* INCORROUT in DB2 10. *
* *
* 3. UNLOAD of a table with a DECFLOAT *
* column followed by a character column *
* results in INCORROUT in both DB2 9 and *
* DB2 10. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. INCORROUT happened when executing UNLOAD DELIMITED against a
table with a DECFLOAT column in DB2 9.
The problem happened because a local variable was not set
properly for DECFLOAT columns.
2. INCORROUT happened when executing UNLOAD against a table that
was in basic row format (BRF) and contained a nullable varying
length column in DB2 10.
1
The problem happened because the output pointer was not set
properly for nullable varying length columns.
3. INCORROUT happened when executing UNLOAD against a table that
was in basic row format and contained a DECFLOAT column
followed by a character column (including varying length
column). This error occurs in both DB2 9 and DB2 10.
The internal length of a DECFLOAT column is one more than the
defined/external length. UNLOAD used the internal length
instead of the external length causing the output record to be
formatted incorrectly.
Additional Keywords: DB2INCORR/K
1. UNLOAD has been changed to correctly set the variable for
DECFLOAT columns in DB2 9.
2. UNLOAD has been changed to correctly set the output pointer
for nullable varying length columns in DB2 10.
3. UNLOAD has been changed to format an output row containing a
DECFLOAT column followed by a character column correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62825
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULCA PM62825
DSNUULXA PM62825
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62825 DSNUULCA DSNUULXA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULCA
DSNUULXA
LISTEND
UK79017 COVER LETTER END
UK79062 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62259 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of OLAP *
* specifications. *
****************************************************************
* PROBLEM DESCRIPTION: (1) V9 and V10: *
* Incorrect output may occur for a query *
* that contains an OLAP specification and *
1 * a subquery predicate. *
* (2) V10: *
* ABENDOC4 RC00000038 DSNXOWIN+104A may *
* occur when a query contains multiple *
* OLAP specifications other than RANK, *
* DENSE_RANK, and ROW_NUMBER. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
(1) V9 and V10:
Incorrect output may occur for a query that contains an OLAP
specification and a subquery predicate.
The following is an example of such a failing scenario:
SELECT ROW_NUMBER() OVER(ORDER BY C1)
FROM T1
WHERE T1.C2 IN (SELECT ...)
Note: There is an index on T1.C1 and no sort miniplan for the
OLAP specification. The subquery is transformed into a
correlated virtual table.
(2) V10:
OC4 ABEND RC00000038 DSNXOWIN+104A may occur when a query
contains multiple OLAP specifications other than RANK,
DENSE_RANK, and ROW_NUMBER.
The following is an example of such a failing scenario:
SELECT SUM(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
AVG(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
MIN(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
MIN(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
MAX(C1) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
MAX(C2) OVER (PARTITION BY..ORDER BY..ROWS BETWEEN..),
....
FROM (SELECT ...) TX;
DB2 is modified to process OLAP specifications correctly.
Additional keywords: SQLSUBQUERY SQLRANK SQLDENSERANK
SQLROWNUMBER SQLINCORR INCORROUT
SQLINCORROUT DB2INCORR/K SQLOLAP
ABENDOC4 RC00000038 in DSNXOWIN
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62259
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM62259:
See PM62259 APAR/PTF text for additional information about
why a REBIND is necessary.
PM62259 corrects a problem of incorrect output when a query
contains OLAP specifications and a subquery predicate. This
APAR also corrects ABENDOC4 RC00000038 DSNXOWIN+104A when a
query contains multiple OLAP specifications other than RANK,
DENSE_RANK, and ROW_NUMBER.
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
DSNXOGA PM62259
DSNXOWIN PM62259
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62259 DSNXOGA DSNXOWIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGA
DSNXOWIN
LISTEND
UK79062 COVER LETTER END
UK79065 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61724 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of LOBs in a *
* distributed environment. *
****************************************************************
* PROBLEM DESCRIPTION: When a LOB receives input data longer *
* than its defined length which is *
* defined about 2MB via an insert into a *
* remote table with streaming, DB2 *
* inserts the data into the LOB using the *
* defined length without issuing an *
* SQLCODE -433. Instead, DB2 should not *
* insert the LOB and issue an SQLCODE *
* -433. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a LOB receives input data which is longer than its defined
length which is defined about 2MB from an insert into a remote
table with streaming, DB2 inserts the data into the LOB using
the defined length without issuing an SQLCODE -433. Instead,
DB2 should not insert the LOB and issue an SQLCODE -433.
The following example helps illustrate the problem.
1. Create a Table T1 with a CLOB column on a remote server.
CREATE TABLE T1 (C1 CLOB(2097152));
2. Write a JAVA application which inserts a CLOB with size
1 of 2097153 bytes using streaming into Table T1.
//Make a connection to remote server
PreparedStatement ins = con.prepareStatement(
"INSERT INTO T1 (C1) values (?)");
//clob.txt is file with size of 2097153 bytes
File file = new File("clob.txt");
Reader fileReader = (Reader) new BufferedReader(
new FileReader(file));
//Insert into T1 using streaming
ins.setCharacterStream(1, fileReader, -1);
ins.execute();
3. Execute the application.
When the JAVA application is executed, even with a CLOB size
that is larger than the C1 defined length, DB2 incorrectly
inserts data into the LOB column up to the size of the defined
length without issuing an SQLCODE -433 because DB2 code does not
handle the input length for a LOB properly during the streaming
process.
The code in DB2 has been modified to issue an SQLCODE -433
instead of inserting the row (LOB) when the length condition is
detected.
Additional Keywords: SQLLOB SQLCODE433 SQLINSERT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61724
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOLINS PM61724
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61724 DSNOLINS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOLINS
LISTEND
UK79065 COVER LETTER END
UK79067 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62038 -
****************************************************************
1 * USERS AFFECTED: DB2 10 for z/OS users of parallel in-list *
* (PLAN_TABLE ACCESSTYPE = 'N' and *
* ACCESS_PGROUP_ID > 0 on the same row) *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output may occur when a *
* query runs in parallel in-list *
* (PLAN_TABLE's ACCESSTYPE = 'N' and *
* ACCESS_PGROUP_ID > 0 on the same row) *
* and after the index column which is *
* covered by the in-list predicate, there *
* are also other predicates applied on at *
* least one more index column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect output may occur when a query runs in parallel
in-list (PLAN_TABLE's ACCESSTYPE = 'N' and
ACCESS_PGROUP_ID > 0 on the same row), and after the index
column which is covered by the in-list predicate, there are
also other predicates applied on at least one more index column.
The error occurs because when setting the parallel high/low
partition key for the in-list parallel group, DB2 overlooks the
other indexable predicate. Hence, the parallel group's high/low
partition key is not set up correctly.
The following is an example of such failing query:
SELECT C1, C2, SUM(CX), SUM(CY)
FROM T1
WHERE C1 IN (1, 2, 3, 4, 5)
AND C2 < 3
GROUP BY C1, C2
ORDER BY 1;
and an INDEX is defined on columns (C1, C2, C3, C4, C5).
DB2 is modified to also take the rest of the indexable
predicates into account besides the in-list predicate when
setting up the parallel in-list group partition key high/low
boundary.
Additional Keywords: PARALLELISM SQLPARALLELISM SQLINCORR
INCORROUT SQLINCORROUT DB2INCORR/K SQLIN
DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62038
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM62038:
See PM62038 APAR/PTF text for additional information about
why a REBIND is necessary.
PM62038 corrects a problem of incorrect output that may occur
when a query runs in parallel in-list (PLAN_TABLE's
1 ACCESSTYPE = 'N' and ACCESS_PGROUP_ID > 0); and after the
index column which is covered by the in-list predicate,
there are also other predicates applied on at least one more
index column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLDL PM62038
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62038 DSNXOLDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLDL
LISTEND
UK79067 COVER LETTER END
UK79117 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM53161 -
****************************************************************
* USERS AFFECTED: 1. All DB2 10 for z/OS Using Universal *
* table space or segmented table space. *
* 2. All DB2 user of z/OS V9 and V10 *
* Utility with inline copy. *
****************************************************************
* PROBLEM DESCRIPTION: 1. Insert may fail with ABEND code *
* 0C4-00000038,DSNIDM.DSNISGRT+8DDE *
* due to invalid space map page *
* pointer. *
* 2. Unpredictable error due to broken *
* segment chain when inline copy is *
* used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1. An invalid pointer to a space map page was referenced to
when updating space map page during insert. As the result,
insert abended at DSNISGRT.
2. A DWORD partition number was passed as parameter to inline
copy, while the called module declared the parameter as WORD,
so, the input parameter was truncated.
As the result, inline copy might skip some pages and cause
unpredictable result if the inline copyis used.
DB2 code is fixed to use correct pointer to space map page and
proper-length parameter as partition number.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PM53161
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 PM53161
DSNISGNS PM53161
DSNISGRT PM53161
DSNOPPLS PM53161
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM53161 DSNISEGF DSNISGNS DSNISGRT DSNOPPLS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISEGF
DSNISGNS
DSNISGRT
DSNOPPLS
LISTEND
UK79117 COVER LETTER END
UK79163 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61540 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* data sharing users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000011 DSNIDBGN+'0DC0'x *
* during DBET notify exit processing *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While processing DBET notify exit, ABEND0C4 RC00000011 in
DSNIDBGN + '0DC0'x was encountered.
Investigation showed that the notify exit processing was trying
to access a control block that had already been freed. In
addition, said storage had just been free-mained by Storage
Manager's contraction.
In the reported scenario, DB2 remained up, however it is still
possible for DB2 to come down due to this issue.
DB2 was updated to make sure it has a valid control block prior
to accessing it.
Unrelated to the issue above, this APAR is being used to add
serviceability to DBET. Following the apply of the APAR, these
diagnostic dumps may be generated:
ABEND04E RC00C90101 DSNIDBGC ERQUAL5220 - for the case where a
1 partition was not found
ABEND04E RC00C90101 DSNIDBGC ERQUAL5221 - for the case where a
returned DBET entry does not include
the desired partition
ABEND04E RC00C9008E DSNIDBLK - for the case where DBET
encounters a timeout on the DBET
hash lock (around the time
MSGDSNT501I with RC00C900C0 and
TYPE00002105 is generated). Before
this APAR, a dump was still generated
for timeouts however the dump title
was using RC00C90088, which is a
reason code for deadlocks, not
timeouts.
For DBET hash lock deadlock cases, DB2 already generates
diagnostic dump ABEND04E RC00C90088 DSNIDBLK and this is not
being changed by this APAR.
In addition, please note that for the DSNIDBLK abends, the other
data sharing members in the group will continue to generate
diagnostic dump ABEND04E RC00C90101 DSNIDBGN ERQUAL5006 as was
done before ths APAR.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61540
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBGC PM61540
DSNIDBGN PM61540
DSNIDBLK PM61540
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61540 DSNIDBGC DSNIDBGN DSNIDBLK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBGC
DSNIDBGN
DSNIDBLK
LISTEND
UK79163 COVER LETTER END
UK79178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62576 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of GRECP/LPL *
* recovery. *
1 ****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E50701 DSNVGEPL. *
* DSNVEUS2+0A2A DB2 crash during *
* GRECP/LPL RECOVERY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The abend in DSNVEUS2 was due to a prior abend in
DSNIBHRE during GRECP/LPL recovery. The abend
initiated in this recovery process turned on the error
information bit, but did not reset it at re-try process.
This caused the commit done at EU completion to fail
DB2's recovery process is modified to reset the error
information bit at re-try time in case of any abend
during GRECP/LPL recovery.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62576
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 PM62576
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62576 DSNIB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIB
LISTEND
UK79178 COVER LETTER END
UK79180 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM58352 -
****************************************************************
* USERS AFFECTED: ALL DB2 10 FOR z/OS USERS OF FLASHCOPY *
* IMAGE COPY AND RECOVER UTILITIES. *
****************************************************************
* PROBLEM DESCRIPTION: RECOVER OF A NON-PARTITIONED OBJECT *
* FROM A FLASHCOPY IMAGE COPY RESTORES *
* THE WRONG INSTANCE NAME TO SOME *
* LINEAR PIECES *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran COPY utility to make a FLASHCOPY IMAGE COPY
of a multipiece linear non-partitioned object. All
IPREFIX values for all pieces were 'I0001.'
When RECOVER was run using the FLASHCOPY, the user
noticed that intermittently, some, but not all, of the
linear pieces were restored with an IPREFIX of 'J0001.'
1 For non-partitioned objects a mixture of 'I' and 'J'
instances is not valid, and this can lead to a variety
of unpredictable symptoms due to the potential broken
data that could result.
This problem was due to incorrect logic within RECOVER
utility when determining the correct IPREFIX for the
data sets.
additional keywords: table space tablespace
index space indexspace
RECOVER utility code was changed to fix how IPREFIX values
are determined for non-partitioned objects when using
FLASHCOPY IMAGE COPIES.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM58352
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 PM58352
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM58352 DSNUCBMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBMT
LISTEND
UK79180 COVER LETTER END
UK79230 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM48742 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and 10 for z/OS users of *
* pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes two problems: *
* 1.Incorrect output may be obtained when *
* an XML value index with key type of *
* SQL DECFLOAT is used. *
* 2.SQLCODE -16061 is incorrectly issued *
* (on DB2 10) and incorrect output or *
* DSNXGRDS.DSNXEFDA:M120 abend may *
* occur (on DB2 9) for implicit casting *
* of invalid format of special values *
* to numeric type in XPath predicates *
* for general comparison when no *
* matching index found. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 This APAR fixes two problems:
1.Incorrect output may be obtained when an XML index with key
type of SQL DECFLOAT is used. There are two possible causes:
a. On DB2 9, there is a logic error in generating index key
values for floating point data that conforms to the pattern
(0-9)*.0+(1-9)+E... (* means 0 or more, + means 1 or more).
In other words, the pattern has one or more 0s following .
and then followed by non-zero digit(s) and then E.
For example, wrong key values would be generated for
1.05E20, 123.000078E-1 etc. but not for 1.00E3.
b. NaN, INF and -INF are special values that are valid in XML
value space while other variations such as nan, nAN, iNf,
+NaN, -NaN, +INF are not valid. On DB2 9, decfloat index
entries for valid special values INF and -INF are missed
to be created. While on DB2 10, decfloat index entries for
invalid format of INF such as inf, InF, +INF, etc. are
wrongly created with the same value as INF and decfloat
index entries for -iNf, -Inf etc. are also wrongly created
with the same value as -INF.
For example, an XML index with SQL DECFLOAT type is created
CREATE TABLE T1 (ID INTEGER, DOC XML);
CREATE INDEX INDX1 ON T1 (DOC)
GENERATE KEY USING XMLPATTERN '/a/b' AS SQL DECFLOAT ;
Suppose four rows are inserted
INSERT INTO T1 (ID, DOC)
VALUES(1,'<a><b>1.0E20</b></a>');
INSERT INTO T1 (ID, DOC)
VALUES(2,'<a><b>1.05E20</b></a>');
INSERT INTO T1 (ID, DOC)
VALUES(3,'<a><b>iNf</b></a>');
INSERT INTO T1 (ID, DOC)
VALUES(4,'<a><b>INF</b></a>');
If user has a query below
SELECT ID FROM T1
WHERE XMLEXISTS('/a[b>10000]' PASSING DOC);
The corrct output should have 3 rows returned with IDs 1,2 and
4. On DB2 9, only 1 row is returned with ID 1. The ID 2 row is
missing due to cause a and ID 4 row is missing due to cause
b. On DB2 10, all 4 rows are returned with IDs 1,2,3 and 4.
The ID 3 row is incorrectly output due to cause b.
2.When performing general comparison of a node with a numeric
value in XPath predicates while there is no matching index,
implicit casting is carried out first to try to convert the
node's value to numeric type. On DB2 9, DSNXGRDS.DSNXEFDA:M120
may occur when the node's value is some invalid format of
special values such as iNf, NAN. For some other invalid format
such as +INF, it is treated as INF and incorrect output may be
obtained. As stated above, only NaN, INF and -INF are valid
special values in XML while other variations are invalid.
On DB2 10, SQLCODE -16061 is incorrectly issued for implicit
casting of invalid format of special values to numeric type
in XPath predicates for general comparison. The correct way
is to ignore invalid format of special values just as ignoring
a random string when casting them to numeric type. In doing
1 so, the query result is consistent with when there is a
matching index ("aaa", "-NaN" are ignored at index
creation
time with no corresponding index entries created).
Suppose we have the same DDL as above but the index INDX1 is
dropped. For the same above query, DB2 9 gets
DSNXGRDS.DSNXEFDA:M120 abend since the error handling is not
handled correctly. DB2 10 issues SQLCODE -16061. The correct
output should be consistent with when INDX1 is present.
DB2 is changed to have correct decfloat index entries created
for XML values; It is also changed to ignore the implicit
casting error of invalid format of special values to XML numeric
values when performing general comparison in XPath predicates.
Additional Keywords: XMLALL XMLINDEX SQLDECFLOAT SQLXML
INCORROUT DB2INCOR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM48742
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
See PM48742 APAR/PTF text in the PTF cover letter for
additional information about this APAR.
This APAR fixes two problems - one is incorrect index entries
created for an XML value index with key type SQL DECFLOAT;
another is incorrectly issuing SQLCODE -16061 when performing
general comparison of invalid format of special values to
numeric type in XPath predicates when no matching index exists.
To make this fix effective for an application, users need to
check if there is any XML value index with key type SQL DECFLOAT
in use. If so, users need to run CHECK INDEX on such index after
the application of this PTF to see it reports any data/index
mismatch. REBUILD INDEX needs to be done for index with mismatch
issue. 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
DSNNKGEN PM48742
DSNNQDTM PM48742
DSNNQIV PM48742
DSNNQOPM PM48742
DSNNQOPN PM48742
DSNNQOPR PM48742
DSNNQOPS PM48742
DSNNQRES PM48742
DSNNQTOP PM48742
DSNNQXCA PM48742
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM48742 DSNNKGEN DSNNQDTM DSNNQIV DSNNQOPM DSNNQOPN DSNNQOPR
DSNNQOPS DSNNQRES DSNNQTOP DSNNQXCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNNKGEN
DSNNQDTM
DSNNQIV
DSNNQOPM
DSNNQOPN
DSNNQOPR
DSNNQOPS
DSNNQRES
DSNNQTOP
DSNNQXCA
LISTEND
UK79230 COVER LETTER END
UK79240 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM60142 -
****************************************************************
* USERS AFFECTED: All DB2 Data Sharing users of the ACCESS *
* DATABASE, DISPLAY DATABASE, START DATABASE *
* and STOP DATABASE commands. *
****************************************************************
* PROBLEM DESCRIPTION: Data Sharing users of the DB2 ACCESS, *
* DATABASE, DISPLAY DATABASE, START *
* DATABASE and STOP DATABASE commands *
* could generate ABEND04E RC00C90101 in *
* DSNGEDFR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Data Sharing users of the DB2 ACCESS, DATABASE, DISPLAY
DATABASE, START DATABASE and STOP DATABASE commands could
generate ABEND04E RC00C90101 in DSNGEDFR if objects were
dropped across the Data Sharing Group during command
processing.
The ACCESS DATABASE, DISPLAY DATABASE, START DATABASE and STOP
DATABASE commands were changed to not free remote objects that
could not be located.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60142
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDNOT PM60142
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60142 DSNTDNOT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNTDNOT
LISTEND
UK79240 COVER LETTER END
UK79241 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61565 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL *
* statement containing 'simple-when' CASE *
* expression where columns defined with field *
* procedure. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect output may occur when an *
* SQL statement satisfies all of the *
* following conditions: *
* *
* 1. SQL contains 'simple-when' CASE *
* expression; *
* 2. the column which is under CASE *
* clause is defined with field *
* procedure; *
* 3. constants are under WHEN clause. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect output may occur when an SQL statement satisfies
all of the following conditions:
1. SQL contains 'simple-when' CASE expression;
2. the column which is under CASE clause is defined with field
procedure;
3. constants are under WHEN clause.
The following examples help to illustrate the problem:
CREATE TABLE TEST.T1
(COL1 VARCHAR(5) FIELDPROC FPCVD4);
INSERT INTO TEST.T1
VALUES('ABC');
Query #1:
SELECT CASE COL1
WHEN 'ABC'
THEN '+'
ELSE '?'
END
FROM TEST.T1;
The result '?' instead of '+' is returned, which is incorrect.
Query #2:
SELECT 1
FROM TEST.T1
WHERE CASE COL1
1 WHEN 'ABC'
THEN '+'
ELSE '?'
END = '+';
No row is returned, which is also incorrect.
DB2 didn't handle the column defined with field procedure in
'simple-when' CASE expression correctly, and caused incorrect
output.
The code in DB2 has been modified correctly to handle the column
defined with field procedure in 'simple-when' CASE expression.
Additional keywords: SQLCASE SQLWHEN SQLFIELDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61565
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM61565:
See PM61565 APAR/PTF text for additional information about
why a REBIND is necessary.
PM61565 corrects a problem of incorrect output when an SQL
statement satisfies all of the following conditions:
1. SQL contains 'simple-when' CASE expression;
2. the column which is under CASE clause is defined with field
procedure;
3. constants are under WHEN clause.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEXC PM61565
DSNXOEXG PM61565
DSNXOOSG PM61565
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61565 DSNXOEXC DSNXOEXG DSNXOOSG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEXC
DSNXOEXG
DSNXOOSG
LISTEND
UK79241 COVER LETTER END
UK79281 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PM60826 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of queries that *
* use workfiles (CM and above) *
****************************************************************
* PROBLEM DESCRIPTION: Problem 1: *
* *
* INCORROUT returned after repeated SQL *
* OPEN cursor for a query that uses *
* LIKE :host-var or '?' (parameter *
* marker) predicate when the host-var *
* value includes a pattern or escape *
* expression and the user application *
* changes the host-var value between *
* the initial OPEN cursor and *
* a subsequent OPEN cursor. *
* *
* Problem 2: *
* *
* Storage leak possible on queries that *
* use workfiles *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Problem 1:
----------
In certain cases of a query / SELECT that specifies a LIKE
:host-variable or '?' (parameter marker) predicate and the user
application's input host-variable value includes a pattern or
escape expression, incorrout is returned after the second or
later SQL OPEN or execution of that query (following an SQL
CLOSE cursor) within the same transaction and the user
application changed the LIKE host-var value since the first OPEN
or execution of the query.
The certain cases of incorrout for the above described scenario
are when DB2 determines that --
(1) the query results must be 'staged' into an internal DB2
workfile before returning the result to the user
application, and
(2) DB2 needs to apply the LIKE :host-var /'?' predicate to
that workfile result.
If DB2 applies this specific LIKE predicate directly to
the base table rows themselves, the incorrout does not occur.
DB2 Development determined that the problem occurs due to DB2
internal predicate optimization done for this specific case of
LIKE :host-var / '?' predicate (as previously described) when
applied to a DB2 internal workfile result. This predicate
optimization should be destroyed on the SQL CLOSE for the query
and new predicate optimization built on a subsequent re-OPEN for
the query, when a new input value for the LIKE :host-var / '?'
would be considered when building the predicate optimization.
1 However, in this incorrout case using workfile results,
the optimization is not redone on a subsequent re-OPEN of
the query when the :host-var value could have changed since
the initial SQL OPEN. Therefore, the re-OPEN used predicate
optimization that was built using the input LIKE :host-var value
from the initial OPEN for the query.
This incorrout for this specific LIKE predicate case may also
occur for other SQL statements where this LIKE predicate can be
used.
Example of a query that exposed this problem:
SELECT A, B, C, D
FROM TAB1
WHERE C = ? AND E LIKE ?
Problem 2:
----------
Storage leak may occur after continued runs of queries that use
workfiles. The leak involves the so-called P Procs (predicate
procs), new in V10 CM and higher, when they are built for
workfiles. The eyecatcher in the dump is 'SelP'.
The problem is that these procs are acquired but not freed.
Example of a query for this problem is same as for Problem 1.
Both problems are corrected by disabling the building of P Procs
when it comes to workfile processing.
Additional keywords: SQLINCORR SQLINCORROUT DB2INCORR/K
PARAMETERMARKER SQLPMARKER SQLPMK
SQLLIKE SQLHOSTVAR DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM60826
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIWNRF PM60826
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM60826 DSNIWNRF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWNRF
LISTEND
UK79281 COVER LETTER END
1UK79290 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM64396 -
****************************************************************
* USERS AFFECTED: All users of DB2 statistics record IFCID2. *
****************************************************************
* PROBLEM DESCRIPTION: The following conditions are reported: *
* 1. If more than 25 group or local *
* bufferpools are in use, fields *
* QBSTPID and QBGLGN will contain *
* incorrect values in the first *
* repeating group of an overflow *
* IFCID2 record. *
* 2. The assembler mapping for DSNDQ8ST *
* is incorrect as field Q8STQUEW is *
* missing. *
* Both issues arise after installing *
* APAR PM50435/PTF UK76014. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following conditions are reported:
1. APAR PM50435 did not recompile all necessary parts for
changes made to DSNDQWS1. This results in incorrect
processing such that QBSTPID and QBGLGN become increased by
a value of 28.
2. APAR PM50435 did not account for DSNDQ8ST field Q8STQUEW.
DB2 is changed as follows:
1. All remaining recompiles have been included such that
overflow IFCID2 records will have correct values for QBSTPID
and QBGLGN.
2. The assembler mapping for DSNDQ8ST has been corrected to
include field Q8STQUEW.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM64396
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQ8ST PM64396
DSNWVZD1 PM64396
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM64396 DSNDQ8ST DSNWVZD1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWVZD1
MACROS
DSNDQ8ST
LISTEND
1UK79290 COVER LETTER END
UK79316 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM55239 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users *
* of IBM Text Search. *
****************************************************************
* PROBLEM DESCRIPTION: This apar provides the new release *
* IBM TextSearch for DB2 for *
* z/OS and a new Text Search *
* stored procedure: SYSTS_ALTER. *
****************************************************************
* RECOMMENDATION: This apar provides the new release IBM Text *
* Search that replaces for Omnifind *
* Text Search. All the users of Text *
* Search for DB2 z/OS need to install or *
* migrate to the new server. *
* *
* The user needs to follow ++HOLD *
* instructions to download, install or *
* migrate the new release IBM Text Search. *
* *
* This apar also provides the new stored *
* procedure, SYSTS_ALTER, that can modify *
* the options of existing index which was *
* created by SYSTS_CREATE. *
* *
* More information about using SYSTS_ALTER in *
* "IBM Text Search for DB2 for z/OS" book at
*
* "chapter 5 Administration stored procedures *
* for Text Search". *
****************************************************************
For using the new features of IBM Text Search, the user
needs to apply this apar, follow instructions in ++HOLD and the
IBM Text Search document to install, migration to the new server
and bind the Text Search packages.
Here are the links of IBM Text Search documents:
V1R2:
http://publib.boulder.ibm.com/epubs/pdf/dsntsk16.pdf
V1R3:
http://publib.boulder.ibm.com/epubs/pdf/dsntsm03.pdf
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM55239
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM56722 (V10)
1 This PTF modifies program DSNTRIN to install and configure the
SYSPROC.ADMIN_INFO_SQL stored procedure in all modes of DB2 10
for z/OS. Previously, ADMIN_INFO_SQL (which is useful for
gathering DB2 diagnostic and tuning data) was not installed in
conversion mode after migration from DB2 UDB for z/OS Version 8.
If you migrated to DB2 V10 from DB2 V8 and DB2 is not yet in
new-function mode then after applying this PTF you need to take
the following action:
Run your copy of job DSNTIJRT with MODE(INSTALL) to install
and configure SYSPROC.ADMIN_INFO_SQL.
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:
This PTF provides two new features:
-- The Omnifind Text Search is moving to a new release,
IBM Text Search for DB2 z/OS (IBMTS).
-- A new stored procedure, SYSPROC.SYSTS_ALTER, can be
used to modify the options of an existing IBM Text Search
index.
If you have already installed or migrated to DB2 10 for z/OS,
you need to perform the following actions after applying this
PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Copy updated DB2 installation panels to alternate libraries
(3) Update your customized copy of job DSNTIJRT
(4) Update private copies of the DSNTIDxx CLIST input member
(5) Run installation job DSNTIJRT to install new objects
(6) Run installation job DSNTIJRV to validate new objects
Detailed guidance for these actions is given further below.
If you currently use or want to use IBM Text Search for DB2
for z/OS, you need to perform these additional actions:
(I) Download the most current version of IBMTS
(II) New IBMTS users: Install the IBMTS server
(III) Existing users: Migrate to IBMTS from OmniFind server
(IV) Add the new stored procedure SYSPROC.SYSTS_ALTER.
(V) Where to find more information
Detailed guidance for these actions is given further below.
1 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Actions for all customers
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
***********************************************************
* This action is required for all V10 customers
***********************************************************
This PTF modifies CLIST members DSNTINST, DSNTINSV, and
DSNTINS1 in the prefix.SDSNCLST target library only.
You need to redo any record format changes and reapply any
tailoring you have done to your private copies of these
CLISTs. You may also want to move them to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed
by job DSNTIJVC reside.
----------------------------------------------------------------
(2) Copy updated DB2 installation panels to alternate libraries
***********************************************************
* This action is required for all V10 customers who maintain
* copies of the DB2 installation panels outside of SMP/E:
***********************************************************
This PTF modifies the DB2 installation panels DSNTIPRA and
DSNTIPRJ in the prefix.SDSNSPFP target library.
If you keep the DB2 installation panels in a different
library then after applying this PTF, you need to copy the
updated panels to that library.
----------------------------------------------------------------
(3) Update customized copies of installation job DSNTIJRT
***********************************************************
* This action is required for all V10 customers
***********************************************************
This PTF modifies installation job DSNTIJRT in the
prefix.SDSNSAMP target library. After you apply this PTF,
you need to add the following to the list of configuration
control statements under the CFIGIN DD in your customized
copy of DSNTIJRT:
SYSPROC.SYSTS_ALTER
WLMENV(DSNWLM_GENERAL)
GRANTTO(PUBLIC)
Notes:
(a) Always leave a blank line between each configuration
control statement
(b) Inspect each of the new configuration control statement
and if required:
- Change the WLMENV parameter settings to the names of
the WLM environment you use to run these routines at
your site
- Change the GRANTTO parameter setting to the
authorization IDs that need access to the routines
- Optionally add the PKGOWNER option
----------------------------------------------------------------
(4) Update private copies of the DSNTIDxx CLIST input member
***********************************************************
1 * This action is required for all V10 customers
***********************************************************
This PTF adds entries to store values entered into new
fields on installation panel DSNTIPRL:
- RTJ09ACL: GRANT EXECUTE setting for
SYSPROC.SYSTS_ALTER
- RTJ09PKO: PACKAGE OWNER setting for
SYSPROC.SYSTS_ALTER
- RTJ09WLM: WLM ENV NAME setting for
SYSPROC.SYSTS_ALTER
You need to make the same changes to all private copies of
your CLIST output (DSNTIDxx) member. In each such copy,
add the following lines:
RTJ09ACL CHAR M NONE NONE PUBLIC
RTJ09PKO CHAR M NONE NONE NULL
RTJ09WLM CHAR M NONE NONE DSNWLM_GENERAL
The values shown in the 6th column are the DB2-supplied
default settings. If you specified different settings in
action (3) above, change the settings in column 6
accordingly.
----------------------------------------------------------------
(5) Run installation job DSNTIJRT to install new objects
***********************************************************
* This action is optional for V10 customers
***********************************************************
After you have completed the above actions, run your updated
copy of job DSNTIJRT to install and grant access to
the new routine, SYSPROC.SYSTS_ALTER, and to rebind the
packages for the IBM Text Search routines.
----------------------------------------------------------------
(6) Run installation job DSNTIJRV to validate new objects
***********************************************************
* This action is optional for V10 customers
***********************************************************
After you have completed the above actions, run your
customized copy of job DSNTIJRV to validate installation and
configuration of SYSPROC.SYSTS_ALTER.
----------------------------------------------------------------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Additional actions for Text Search customers
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The users need to follow the instructions in the
"IBM Text Search for DB2 for z/OS" book to define
the Text Search stored procedures and enable Text Search.
The following information will refer to the "IBM Text Search
for DB2 for z/OS" book.
----------------------------------------------------------------
(I) Download the most current version of IBMTS
1 ***********************************************************
* This action is required for Text Search customers
***********************************************************
Download the most current version which is FIX R1L5 from the
following Web site:
http://www.ibm.com/software/data/db2/zos/downloads/oftss.html
On this Web site, download the zip file and the readme file
for IBMTS Text Search for DB2 for z/OS.
The following shows the names of the zip files
of IBMTS Text Search Servers:
Linux32 - TextSearchServer_setuplinux32.zip
Linux64 - TextSearchServer_setuplinux64.zip
Window32 - TextSearchServer_setupwin32.zip
Window64 - TextSearchServer_setupwin64.zip
zLinux - TextSearchServer_setupzlinux.zip
For Window32/64: right click the zip then choose extract
option
For Linux32/Linux64/zlinux:
chmod 755 TextSearchServer_setupxxxx.zip
unzip TextSearchServer_setupxxxx.zip
To install or update the IBMTS server, please refer to
the following publications:
--readme.html: document that accompanies the installation
file.
--"Installation, Administration, and Reference": the
product documentation for the IBM Text Search for DB2
z/OS.
----------------------------------------------------------------
(II) New IBMTS users: Install the IBMTS server
***********************************************************
* This action is required for Text Search customers
***********************************************************
To install the IBMTS server, the user needs to follow:
Chapter 4. Installing and configuring text search functions
--Installing IBM Text Search for DB2 z/OS.
(for the new installation).
or
--Installing fixes on top of the current server.
(install IBMTS server on the existing server).
----------------------------------------------------------------
(III) Existing users: Migrate to IBMTS from OmniFind server
***********************************************************
* This action is required for Text Search customers
***********************************************************
For existing users to migrate IBMTS from OmniFind server
1 they need to follow:
Chapter 4. Installing and configuring text search functions
--Migrating to IBM Text Search for DB2 for z/OS
from OmniFind Text Search.
----------------------------------------------------------------
(IV) Add the new stored procedure SYSPROC.SYSTS_ALTER.
***********************************************************
* This action is required for Text Search customers
***********************************************************
Refer to steps (5) and (6) of the section above titled
"Actions for all customers"
----------------------------------------------------------------
(V) Where to find more information
----------------------------------------------------------------
The user can look for more information for the new
SYSTS_ALTER stored procedure at:
Chapter 5. Administration stored procedures for text search
SYSPROC.SYSTS_ALTER.
ACTION:
Please note that the following ACTIONS need to be performed
with respect to this apar:
1. Run your copy of job DSNTIJRT with MODE(INSTALL) to
bind, and grant access to the Text Search stored
procedures.
2. Refresh WLM environment defined for Text Search
stored procedures:
v wlm,applenv=wlmname,refresh
3. Refresh DB2 to make sure it will pick up the new
Text Search modules.
4. This apar introduces the text search server level R2L11. To
update the text search server, download the most current
version which is FIX R2L11, from the following Web site:
http://www.ibm.com/software/data/db2/zos/downloads/oftss.html
From this Web site, click Download OmniFind Text Search
Server for DB2 for z/OS.
The following shows the names of the files that start the
silent installation or update of a Text Search server.
1. Linux - TS_fixR2L11linux_i586.bin
2. zLinux - TS_fixR2L11zlinux.bin
3. Windows - TS_fixR2L11win32.exe
To install or update the server, please reference the
following publications:
1
"Instructions for installing": readme.html
document that accompanies the installation file.
"Installation, Administration, and Reference": The product
documentation for the IBM Text Search for DB2 z/OS and the
IBM OmniFind Text Search Server.
5. This apar provides the fix related to the backup index table.
After applying this APAR the users should run
SYSTS_UPDATE with ALLROWS options for all the indexes
aready created with option UPDATEWITHBACKUP = 1
to make sure the backup index table refreshed with the full
collection.
Note that UPDATEWITHBACKUP = 1 is default option for
SYSTS_CREATE, there for all most the indexes are created
with this option.
The users can use the following SQL statement to
look for the indexes created before applying this APAR
with UPDATEWITHBACKUP = 1
select a.indexid, indexschema, indexname, parameter, value
from sysibmts.systextindexes a, sysibmts.systextconfiguration
where a.indexid = b.indexid and parameter = 'UPDATEWITHBACKUP'
and value = '1'
Assume that the index SCHEMA1.IVC2 has UPDATEWITHBACKUP = 1
then the users need to run SYSTS_UPDATE with option ALLROWS
for this index:
CALL SYSPROC.SYSTS_UPDATE('SCHEMA1','IVC2','ALLROWS')
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@O001 PM55239
DSN@O002 PM55239
DSN@O004 PM55239
DSN@O005 PM55239
DSN@O007 PM55239
DSN@O008 PM55239
DSN@O009 PM55239
DSN@O011 PM55239
DSN@O012 PM55239
DSN@O013 PM55239
DSN@O014 PM55239
DSN@O015 PM55239
DSN@O016 PM55239
DSN@O017 PM55239
DSN@O019 PM55239
DSN@O021 PM55239
DSN@RIN PM55239
DSN@RVFY PM55239
DSN@XAZP PM55239
DSNTESR PM55239
DSNTIDXA PM55239
DSNTIDXB PM55239
1 DSNTIJRT PM55239
DSNTINST PM55239
DSNTINSV PM55239
DSNTINS1 PM55239
DSNTIPRA PM55239
DSNTIPRJ PM55239
DSNTRIN PM55239
DSNTRVFY PM55239
DSNTXAZP PM55239
DSNXRCUF PM55239
DSNXRRTN PM55239
DSN5OCA3 PM55239
DSN5OCA6 PM55239
DSN5OCO3 PM55239
DSN5OCO6 PM55239
DSN5OCU3 PM55239
DSN5OCU6 PM55239
DSN5OPAL PM55239
DSN5OPCR PM55239
DSN5OPDR PM55239
DSN5OPMS PM55239
DSN5OPRE PM55239
DSN5OPSD PM55239
DSN5OPSP PM55239
DSN5OPST PM55239
DSN5OPTO PM55239
DSN5OPUP PM55239
DSN5OTMS PM55239
DSN5OTS PM55239
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM55239 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 DSN@RIN DSN@RVFY
DSN@XAZP DSNTESR DSNTIDXA DSNTIDXB DSNTIJRT DSNTINST
DSNTINSV DSNTINS1 DSNTIPRA DSNTIPRJ DSNTRIN DSNTRVFY
DSNTXAZP DSNXRCUF DSNXRRTN 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:
MODULES
DSNTRIN
DSNTRVFY
DSNTXAZP
DSNXRCUF
DSNXRRTN
MACROS
DSN@O001
DSN@O002
DSN@O004
DSN@O005
DSN@O007
1 DSN@O008
DSN@O009
DSN@O011
DSN@O012
DSN@O013
DSN@O014
DSN@O015
DSN@O016
DSN@O017
DSN@O019
DSN@O021
DSN@RIN
DSN@RVFY
DSN@XAZP
DSNTESR
DSNTIDXA
DSNTIDXB
DSNTIJRT
DSNTINST
DSNTINSV
DSNTINS1
DSNTIPRA
DSNTIPRJ
DSN5OCA3
DSN5OCA6
DSN5OCO3
DSN5OCO6
DSN5OCU3
DSN5OCU6
DSN5OPAL
DSN5OPCR
DSN5OPDR
DSN5OPMS
DSN5OPRE
DSN5OPSD
DSN5OPSP
DSN5OPST
DSN5OPTO
DSN5OPUP
DSN5OTMS
DSN5OTS
LISTEND
UK79316 COVER LETTER END
UK79319 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM64651 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of queries which *
* are candidates for multiple index access *
* selection or where RIDs are to be sorted. *
****************************************************************
* PROBLEM DESCRIPTION: A performance degradation can occur *
* when using quicksort to sort RIDs that *
1 * are entered into the RIDMAP in *
* descending order. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A performance degradation can occur when using quicksort to sort
RIDs that (all) enter the RIDMAP in descending order.
The problem with the quicksort sorting method is that it
performs poorly when the data is already sorted or in near
sorted order. If for example, the data is in pure descending
order, after the first pass through quicksort, the data will be
in near sorted order and the performance will degrade
significantly.
DB2 has been modified to process the situation differently when
it detects that ALL OF THE DATA is in descending order coming
into quicksort. Now, DB2 will perform a very quick swap of the
data and exit sort once the "swap" has completed. This will
significantly improve the performance for this situation.
Additional Keywords: SQLSORT SQLRID
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM64651
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSQSG PM64651
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM64651 DSNXSQSG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSQSG
LISTEND
UK79319 COVER LETTER END
UK79333 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM64206 -
****************************************************************
* USERS AFFECTED: All DB2 users who run REPAIR DBD. *
****************************************************************
* PROBLEM DESCRIPTION: When run REPAIR DBD DIAGNOSE/TEST/ *
* REBUILD, the following error message *
* could be returned, *
* *
* DSNU778I -DB2B DSNUEXDL - ERROR *
* PROCESSING SQL STATEMENT - *
* SQL CODE IS: -270 *
* SQLERRP: DSNXOTL *
1 * SQLERRD: FFFFFF91 00000000 00000000 *
* FFFFFFFF 00000000 00000000 *
* SQL MESSAGE TEXT: FUNCTION NOT *
* SUPPORTED *
* SQL STATEMENT: *
* CREATE TRIGGER DV01E170 AFTER DELETE *
* ON RR#DBX.DV01T170 REFERENCING OLD *
* A FOR EACH ROW MODE DB2SQL BEGIN *
* ATOMIC UPDATE DVV01180 SET *
* AENDERUNG_TS_FACH = CURRENT TIMESTAMP *
* WHERE PROBLEMNUMMER = *
* A.PROBLEMNUMMER ; END *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If the database has trigger defined, REPAIR DBD needs to
rebuild trigger OBD based on catalog information. Due to a DB2
round up mode bug, create trigger failed with the above SQL
message. It can occur only for triggers created before V9.
DB2 has been changed so that REPAIR DBD can create trigger
successfully.
Additional Keyword: SQLCREATE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM64206
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUEXDL PM64206
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM64206 DSNUEXDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUEXDL
LISTEND
UK79333 COVER LETTER END
UK79373 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63986 -
****************************************************************
* USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML *
* index *
****************************************************************
* PROBLEM DESCRIPTION: For some XML documents, the XML index *
* key entries might be missing. This *
* causes incorrect results when the XML *
* index is used by XMLEXISTS or XMLTABLE *
1 * functions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For some XML documents, the XML index key entries might be
missing. This causes incorrect results when the XML index is
used by XMLEXISTS or XMLTABLE functions.
When the XML document is inserted into an XML column, the XML
document is converted into XML records and inserted into the
XML table. The XML index key entries are generated based on the
XML data in each XML record. It is possible that the top element
node is placed in a different record from the record that
contains the document node. In this case, the matching of the
XMLPATTERN will fail and index key entries are not generated.
Incorrect output will occur when the index is used.
DB2 is modified to ensure that the XML index key entries are
inserted when the top element node is not in the same record
as the document node.
Additional keywords: XMLALL XMLINDEXES XMLINCORR DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63986
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
See PM63986 APAR/PTF text in the PTF cover letter for
additional information about this APAR.
PM63986 fixes the problem that the XML index key entry might not
be inserted for some XML document. This may cause incorrect
output when the index is used.
To make this fix effective for the existing XML index, please
run CHECK INDEX on the XML index after application of this PTF
and rebuild the XML index if there is any data/index mismatch.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNKGEN PM63986
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63986 DSNNKGEN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNKGEN
LISTEND
UK79373 COVER LETTER END
UK79393 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM64327 -
1 ****************************************************************
* USERS AFFECTED: ALL DB2 10 for z/OS users that have indexes *
* defined on ROWID columns *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect results can occur when a *
* ROWID predicate is evaluated during *
* index access for an SQL query, DELETE *
* or UPDATE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Comparison between internal and external formats of ROWID
failed because incorrect lengths were compared. This caused
incorrect results to be returned.
Additional Keywords:
SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLINDEX
DB2 has been modified to make sure ROWID comparisons are
done with correct lengths - based on the ROWID format.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM64327
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIGSEL PM64327
DSNKBIDP PM64327
DSNKFIDP PM64327
DSNKGSEL PM64327
DSNKIXDB PM64327
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM64327 DSNIGSEL DSNKBIDP DSNKFIDP DSNKGSEL DSNKIXDB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIGSEL
DSNKBIDP
DSNKFIDP
DSNKGSEL
DSNKIXDB
LISTEND
UK79393 COVER LETTER END
UK79400 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62450 -
****************************************************************
* USERS AFFECTED: All DB2 for zOS Version 10 users with PTF *
* UK77157 applied. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E50DA1 may occur in *
1 * CSECT DSNVSRX after a thread is *
* cancelled. This abend will result in *
* DB2 termination. This may occur after *
* PM56841 is applied to DB2 10 systems. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Cancel processing clears EBSuspRob to indicate the suspending
agent has been resumed. A timing window exists such that the
suspending agent may validate the EBSuspRob prior to suspension.
This check incorrectly detects a state error due to the field
being cleared.
The state check has been corrected to tolerate the clearing
of EBSuspRob by cancel processing. This will prevent an
ABEND04E RC00E50DA1 in the window prior to suspension for
the cancelled agent.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62450
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVSRX PM62450
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62450 DSNVSRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVSRX
LISTEND
UK79400 COVER LETTER END
UK79404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79406 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79421 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79441 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM65232 -
****************************************************************
* USERS AFFECTED: Users of DB2 for z/OS preparing a *
* very large SELECT statement with *
* many AND/OR predicates. *
****************************************************************
* PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE *
* FOLLOWING REPORTED SYMPTOMS: *
* *
* ABEND04E RC00E2000E *
* CSECT DSNXOCCA.DSNSVSFB OFFSET0834 *
* *
* PROBLEM SCENARIO: *
* *
1 * The reported error occurred when *
* attempting to acquire some internal *
* storage. The pointer to the storage *
* was corrupted causing the abend. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SUMMARY OF DB2 EVENTS:
DB2 was attempting to acquire more storage to accommodate the
size of a large statement with many OR predicates. This
resulted in an error as the pointer to the new storage was
corrupted because it was overlayed.
PROBLEM CONCLUSION:
DB2 has been fixed to point to the correct address when
acquiring new storage.
ADDITIONAL KEYWORDS:
PREPARE SQLSTORAGE SQLAND SQLOR MIDX DB2OVRLAY/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM65232
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGCM PM65232
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM65232 DSNXOGCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGCM
LISTEND
UK79441 COVER LETTER END
UK79447 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM61976 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and DB2 *
* 10 for z/OS REORG SORTDATA NO utility users *
* with table partitioned objects when the *
* REORG uses a clustering NPI (nonpartitioned *
* index) to unload data, whose columns match *
* the columns of the PARTITION BY clause of *
* the table *
****************************************************************
* PROBLEM DESCRIPTION: After applying APAR PM44475 (UK73344 in *
* V10, UK73346 in V9, UK73345 in V8) *
* REORG SORTDATA NO on a table-controlled *
* table space unloads all data into *
* partition 1 when the utility uses a *
1 * nonpartitioned clustering index whose *
* columns match the columns of the *
* PARTITION BY clause of the table *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After applying APAR PM44475, a REORG TABLESPACE SORTDATA NO on a
table controlled partitioned table space with a nonpartitioned
index (NPI) as the clustering index, defined on the same columns
and in the same order as the limit key, may unload all data into
partition 1.
Investigation showed that the PM44475 APAR logic was missing the
code to determine which partition the row should be loaded into
when the NPI is used to unload data in the context of that APAR.
Without that missing code the partition determination always
defaulted to partition 1.
In the reported scenario, this problem was exposed by SQL SELECT
COUNT(*) with the predicate using the partitioning key, however
other incorrect output symptoms are possible also.
Code has been added to the data manager component of DB2 to
return the correct partition number to the utility, ensuring
that data is reloaded into correct partitions.
Additional keywords: DB2INCORR/K SQLINCORR SQLINCORROUT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM61976
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
APAR PM58177 has enabled REORG TABLESPACE SHRLEVEL CHANGE to
accept a user defined mapping table created in a
partition-by-growth ( PBG ) table space.
The Utility Guide and Reference has been updated with the
following information, under the REORG TABLESPACE utility in
section titled 'Mapping table and SHRLEVEL CHANGE' :
Before running REORG TABLESPACE with SHRLEVEL CHANGE on a
table space with non-LOB data, you must create a mapping
table and index for the table space. The table space that
| contains the mapping table must be either classic segmented
| or a partition-by-growth table space, and cannot be the
table space to be reorganized.
DOCUMENTATION:
See PM47356 APAR/PTF text for additional information.
This APAR/PTF modifies the DB2 Utility Guide and Reference
and the Messages manual. The change will be documented in
the DB2 Utility Guide and Reference and Messages, and in the
Information Management Software for z/OS Solutions Information
Center.
The change is as follows.
1 In the Utility Guide and Reference, under REORG TABLESPACE,
Option descriptions, SORTDATA option:
SORTDATA
NO
Specifies that the data is to be unloaded in the order
of the clustering index. SORTDATA NO cannot be specified
| with SHRLEVEL CHANGE or if the table space is in REORG-
| PENDING. Specify SORTDATA NO if one of the following
conditions is true:
* The data is in or near perfect clustering order, the
| table space is not in REORP, and the REORG utility is
used to reclaim space from dropped tables.
* The data is very large, an insufficient amount of disk
| space is available for sorting, and the table space is
not in REORP.
In the Messages manual, under DSNU messages:
DSNU070I csect-name KEYWORD OR OPERAND x
INVALID WITH y
Explanation: The use of a keyword or operand is
| inconsistent with another keyword, operand or condition.
| x and y The keywords, operands or conditions that
cannot be used together.
System action: The control statement in error is
rejected and processing is halted.
User response: Correct the control statement in error
and resubmit the job.
| Problem determination: The REORG TABLESPACE
| utility issues this message when the keywords, operands or
| conditions are not allowed to be used in combination.
ACTION:
***Action for PM59605
This PTF modifies the DB2 installation CLIST member DSNTINST
to fix a bug that causes it to ignore the NEWFUN setting
specified in the DSNTIDxx input member when the CLIST is run
in UPDATE mode.
This PTF modifies DSNTINST in the SDSNCLST target library only.
If you have already installed or migrated to this version of DB2
then after applying this PTF, you need to redo any record format
changes and reapply any tailoring you have done to your copies
of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by job
DSNTIJVC reside.
ACTION:
The PTF for APAR PM55051 has modified CSECTs in both the
1 DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the function the PTF
provides will not be available.
PM55051 provides support for REORG TABLESPACE PART SORT NPSIs
(Non-partitioned Secondary Indexes).
This is a performance enhancement to part-level REORG involving
NPSIs intended to improve elapsed time.
Since the removal of the BUILD2 phase for partition-level REORG
in DB2 9, the performance of REORG was degraded in some cases
due to the cost of building shadow NPSIs. Shadow NPSIs are
populated initially with keys of parts which are not in the
scope of the REORG during the UNLOAD phase. Then keys from parts
within the scope of the REORG are sorted and inserted into the
shadow NPSI during the SORT and REBUILD phases, respectively.
Significant performance improvement can be achieved by sorting
all keys of the NPSI in the same sort operation and rebuilding
the index from the entire set of sorted keys. This APAR will add
functionality to improve performance while leaving the old
behavior intact and allow the customer to control the behavior
through the installation panel and a keyword.
This APAR modifies the processing of non-partitioned secondary
indexes for REORG TABLESPACE PART SHRLEVEL CHANGE/REFERENCE
when NPSIs are defined on the table space. Processing of NPSIs
in this case will now be done in one of two ways as
documented in the UNLOAD phase section of Execution Phase
of REORG TABLESPACE in the Utility Guide and Reference.
1. During UNLOAD, one or more subtasks unload NPSI keys from
parts not within the scope of the REORG and build the shadow
NPSI. Keys from parts within the scope of the REORG are
generated from the reorganized data rows, sorted, and inserted
in the shadow index.
2. During UNLOAD, one or more subtasks processes NPSI keys from
parts not within the scope of the REORG. These keys are routed
to a sort process to be sorted with the keys from parts within
the scope of the REORG. The shadow NPSI is built from this
sorted set of keys.
A new message is issued when all keys of an NPSI are sorted
during a part-level REORG TABLESPACE. A new keyword is added
on REORG to control the sorting of all NPSI keys during a
part-level REORG TABLESPACE. The zparm controlling the sorting
of all NPSI keys during a part-level REORG is extended to
1 allow more options.
----------------------------------------------------------------
Changes to Messages and Codes
DSNU1242I
csect-name ALL KEYS OF A NON-PARTITIONED SECONDARY INDEX WILL
BE SORTED
Explanation
During a part-level REORG all keys of a non-partitioned
secondary index will be sorted before rebuilding the index.
This is controlled by the keyword SORTNPSI and the zparm
REORG_PART_SORT_NPSI. When SORTNPSI is specified as YES or AUTO
all keys may be sorted. When SORTNPSI is not specified,
and REORG_PART_SORT_NPSI is set to YES or AUTO, all keys may
be sorted.
System action
Processing is continues.
Severity
0 (informational)
----------------------------------------------------------------
Changes to Utility Guide and Reference
A new keyword SORTNPSI is added to control the method of
building an NPSI during REORG TABLESPACE PART. Options of AUTO,
YES, and NO are available on the keyword. A default is not
applicable in this case because the value will be determined
by zparm REORG_PART_SORT_NPSI if the keyword is not specified.
.-FORCE--NONE----. (3)
>--+----------------+--------+-----------------+--------------->
+-FORCE--READERS-+ +-SORTNPSI AUTO---+
'-FORCE--ALL-----' '-SORTNPSI YES----'
'-SORTNPSI NO-----'
3. The default for SORTNPSI is the value of the
REORG_PART_SORT_NPSI subsystem parameter.
SORTNPSI
Specifies when REORG TABLESPACE PART should sort all keys of a
non-partitioned secondary index. This keyword is ignored for
a REORG that is not partition-level or a REORG with no
non-partitioned secondary indexes. If SORTNPSI is not specified
the value will be determined by zparm REORG_PART_SORT_NPSI.
The benefit of sorting all keys of a non-partitioned secondary
index increases as the ratio of data reorganized to total data
in the table space increases.
AUTO
Specifies that if sorting all keys of the non-partitioned
secondary indexes improves the elapsed time and CPU
performance, all keys are sorted.
1
YES
Specifies that if sorting all keys of the non-partitioned
secondary indexes improves the elapsed time, all keys are
sorted.
NO
Specifies that only keys of the non-partitioned secondary
indexes that are in the scope of the REORG are sorted.
The default value is the value of subsystem parameter
REORG_PART_SORT_NPSI.
----------------------------------------------------------------
Changes to DB2 Installation
This APAR modifies the DSN6SPRM.REORG_PART_SORT_NPSI subsystem
parameter.
REORG_PART_SORT_NPSI specifies the default method of building
an NPSI during REORG TABLESPACE PART when the SORTNPSI
keyword is not provided in the utility control statement.
Valid settings for REORG_PART_SORT_NPSI are AUTO, NO, and YES.
The default setting is NO.
REORG_PART_SORT_NPSI is online changeable and has member scope
in data sharing.
DSN6SPRM: The REORG_PART_SORT_NPSI parameter is added with a
range of AUTO, NO, and YES. The default setting is NO.
DSNTIJUZ: The REORG_PART_SORT_NPSI parameter is added under
the DSN6SPRM invocation with a default setting of NO.
----------------------------------------------------------------
Changes to DB2 instrumentation
DSNDQWPZ: Field QWP4RPSNE is modified to trace the
REORG_PART_SORT_NPSI internal setting:
. . .
QWP4RPSN DS CL1 REORG_PART_SORT_NPSI
* * A=AUTO, N=NO, Y=YES
. . .
The IFCID 106 formatter stored procedures, SYSPROC.DSNWZP and
SYSPROC.ADMIN_INFO_SYSPARM are updated to report the
REORG_PART_SORT_NPSI setting.
----------------------------------------------------------------
This PTF adds an online-changeable subsystem parameter in
DSN6SPRM called REORG_PART_SORT_NPSI that can be used to specify
the default method of building a non-partitioned secondary index
(NPSI) during REORG TABLESPACE PART. This setting will be used
1 when the SORTNPSI keyword is not provided in the utility control
statement. The SORTNPSI keyword specifies whether REORG
TABLESPACE PART should decide to sort all keys of a NPSI and how
to make that decision. The setting is ignored for a REORG which
is not part-level or a REORG with no NPSIs. Valid settings for
this parameter are:
* AUTO: Specifies that if sorting all keys of the NPSI(s)
improves the elapsed time and CPU performance, all
keys are sorted.
* YES : Specifies that if sorting all keys of the NPSI(s)
improves the elapsed time, all keys are sorted.
* NO : Specifies that only keys of the NPSI(s) that are in
the scope of the REORG are sorted.
=> This is the default setting
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is recommended for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter REORG_PART_SORT_NPSI=<x>,
where <x> is AUTO, NO, or YES, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
REORG_PART_SORT_NPSI here, the value will be set to
the default of NO when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
1 This PTF adds an entry for REORG_PART_SORT_NPSI
to the CLIST default input members in the SDSNSAMP target
library. You need to add these entries to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
REORG_PART_SORT_NPSI CHARR M AUTO YES$ <x>
Change <x> to the value you specified for
REORG_PART_SORT_NPSI in step (2), above.
If you do not add REORG_PART_SORT_NPSI to a DSNTIDxx
member, the DB2 installation CLIST will assume
REORG_PART_SORT_NPSI=NO when run with that member as
input.
ACTION:
APAR PM54727 has corrected an issue where REORG REBALANCE on a
partitioned table space with an editproc defined can result in
corrupted limit key values in the DB2 catalog and directory.
In the event that the above limit key corruption has occurred,
user can repair the catalog/directory by manually altering the
limit keys to the correct value on the affected table space /
partitions, and then run a REORG TABLESPACE utility to remove
the restrictive REORP status.
ACTION:
Action for PM53254:
The PTF of PM53254 adds a new system parameter called
REORG_IGNORE_FREESPACE, which specifies whether the REORG
TABLESPACE utility should ignore the PCTFREE and FREEPAGE values
when reloading data rows into a Partition By Growth (PBG)
table space in the following circumstances:
- When reorganizing a subset of the PBG partition(s)
- When the table in the PBG table space has LOB column(s)
Valid settings for REORG_IGNORE_FREESPACE are NO and YES.
The default is NO, meaning that the PCTFREE and FREEPAGE values
will be honored by the REORG TABLESPACE utility.
To incorporate this fix the DB2 initialization parameter module,
DSNZPARM, will need to be reassembled and re-linked by
running the DB2 install clist DSNTINST using UPDATE mode.
Insure that the output sample library name specified in panel
DSNTIPT is not the same as an existing library name from a
previous execution of the DSNTINST clist as the clist processing
will delete all members delete all members of the data set name
specified.
Note: Customers who receive return code 8 and message "ASMA939U
Unable to load external function module - DSNTIXL" when
applying this PTF need to refer to Info APAR II13979.
If you have already installed or migrated to this release of
DB2, you need to take the following actions after applying this
PTF:
1 (1) Optional: Update your DB2 subsystem parameter (DSNZPxxx)
modules:
* Add the keyword parameter
REORG_IGNORE_FREESPACE=<n>,
where <n> is either NO or YES (NO is recommended) to the
invocation of the DSN6SPRM macro in your customized
version of the installation job DSNTIJUZ. Make sure to
add a continuation character in column 72 if needed. If
you omit adding REORG_IGNORE_FREESPACE here, the value
will be set to the default of NO when you assemble the
DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified,
to assemble and link the load module.
* After the job completes, you must either use the SET
SYSPARM command or stop and start DB2 for the change to
take effect.
(2) Required: Update your private copies of the CLIST defaults
(DSNTIDxx) member:
This PTF adds an entry for REORG_IGNORE_FREESPACE to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output (DSNTIDxx) member for DB2.
In each such copy, add the following line:
REORG_IGNORE_FREESPACE CHAR M NO YES <n>
where <n> is the value you specified for
REORG_IGNORE_FREESPACE when you modified DSNTIJUZ in step
(1), above. Specify NO for <n> if you bypassed step (1).
(3) Required: Update customized copies of installation CLIST
member DSNTINST:
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
ACTION:
*** Action for PM47659 ***
This APAR has changed the UNLOAD utility to utilize the
RUNSTATS NPAGES statistic from SYSIBM.SYSTABLES to estimate
the space needed for the SYSREC data set.
A RUNSTATS against the target table space is recommended
prior to the UNLOAD to ensure the accurate estimation
for space requirement.
ACTION:
The PTF for APAR PM47356 has modified the REORG TABLESPACE
utility to issue the following message and end with RC8 when
REORG TABLESPACE SORTDATA NO is run against a non-Partition-
By-Growth (non-PBG) partitioned table space in REORG-PENDING
(REORP). A REORG TABLESPACE SORTDATA YES is required to remove
the REORP state.
MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH
1 'TABLE SPACE IN REORG PENDING'
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIONX2 PM61976
DSNIOST2 PM61976
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM61976 DSNIONX2 DSNIOST2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFMDIR
DSNFUDRD
DSNIONX2
DSNIOST2
DSNIRLPG
DSNISRTI
DSNTXAZP
DSNUCINM
DSNUCINT
DSNUCLGR
DSNUCRUL
DSNUGPPM
DSNUGPRS
DSNUGPRT
DSNUGRST
DSNUKINM
DSNUKINT
DSNUKIUL
DSNUKSRI
DSNUKXCH
DSNUMSGD
DSNURBXA
DSNURBXD
DSNURBXE
DSNURFBR
DSNURFIT
DSNURILD
DSNURLXL
DSNURORG
DSNURPCT
DSNURPIB
DSNURPLD
DSNURPLI
DSNURPPL
DSNURPRD
DSNURPTB
DSNURPUI
DSNURSCN
DSNURSWD
DSNURULN
DSNURWBF
DSNURWI
DSNURWIK
DSNUSITS
1 DSNUSTBL
DSNUULJA
DSNUULXA
DSNWZIFA
MACROS
DSN@XAZP
DSNDQWPZ
DSNDSPRM
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6SPRM
LISTEND
UK79447 COVER LETTER END
UK79505 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62673 -
****************************************************************
* USERS AFFECTED: All users of CHECK DATA on a hash table in *
* a PBG table space where the table has a *
* LOB column. *
****************************************************************
* PROBLEM DESCRIPTION: CHECK DATA utility erroneously reports *
* missing entries in AUX index for a LOB *
* table space *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When CHECK DATA processes a row in a table with a LOB column,
it needs to know the partition number of the row so that it can
locate the correct auxiliary index for the LOB data.
For rows in a PBG table space that are overflow rows, the row
may reside in a different partition from the pointer subrecord.
The LOB table space is associated with the partition of the
overflow row. When processing a hash table in a PBG table
space, CHECK DATA was using the partition number of the
pointer subrecord instead of the partition number of the
overflow row to try to locate the LOB data.
Code is changed such that CHECK DATA uses the partition
number of the overflow record to find the auxiliary index
associated with the LOB table space.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62673
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 PM62673
DSNIOST2 PM62673
DSNIRFNX PM62673
1 DSNUKSCT PM62673
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62673 DSNIACCH DSNIOST2 DSNIRFNX DSNUKSCT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIACCH
DSNIOST2
DSNIRFNX
DSNUKSCT
LISTEND
UK79505 COVER LETTER END
UK79544 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63562 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of UTS (PBG) Partition By *
* Growth table spaces that run ALTER TABLE *
* ADD / ALTER column operations. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90206 DSNIIDIS ERQUAL5002 *
* Other variations on RC00C90206 abends *
* may be seen as well. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For users that perform ALTER TABLE ADD or ALTER of a column,
DB2 needs to handle data versioning for the updated rows to
bring these to current version format. Part of this process
involves adding system pages to the UTS target partition. This
insert of the system page can fail for a number of reasons
including partition full conditions. DB2 error checking will
handle the partition full condition by looking for space in
other partitions. For non-partition full error conditions,
DB2 was failing to perform similar error checking and to then
drive the search to another PBG partition. As a result the SQL
operation kept running although the system page insert failed.
DB2 code has been corrected to look for space in other PBG
partitions when there is a failure to insert the system page
in the current partition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63562
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISUPI PM63562
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63562 DSNISUPI
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISUPI
LISTEND
UK79544 COVER LETTER END
UK79553 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63502 -
****************************************************************
* USERS AFFECTED: All DB2 users of Compression dictionary. *
****************************************************************
* PROBLEM DESCRIPTION: Abend04E RC00E30001 occurred at *
* DSNTGSCC.DSNTLDU +06CC. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While DB2 was reading the Compression dictionary into the
internal control block, an abend04E 00C90101 occurred at
DSNIZLDR. Since the PRR exit routine was not invoked, the
Compression dictionary load lock was not released. When the
thread went through deallocation process, IRLM was called to
unlock the Compression dictionary load lock. Because the lock
duration was invalid, IRLM failed the unlock request and caused
the abend04E RC00E30001 at DSNTLDU.
DB2 code was changed to the corrected lock duration and used the
corrected option when the PRR is created.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63502
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIZLDR PM63502
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63502 DSNIZLDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIZLDR
LISTEND
UK79553 COVER LETTER END
UK79562 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79589 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79602 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79619 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79630 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
1UK79665 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79683 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79701 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79710 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79762 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79770 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63979 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
* of UNLOAD with FROMCOPY/FROMCOPYDDN option. *
****************************************************************
* PROBLEM DESCRIPTION: Message spool flooded by MSGDSNU1239I *
* and MSGDSNU1219I messages during an *
* UNLOAD FROMCOPYDDN, and abended with *
* ABENDS0C4 RC00000038 at DSNUULCA *
* OFFSET7074 if MAXERR integer(>=2) was *
* specified, and then the DB2 subsystem *
* abended with ABEND04E RC00E20028 along *
* with the message DSNV086E - DB2 *
* ABNORMAL TERMINATION REASON=00F30801. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User procedures caused DSNU1239I - VERSION version-number OBDREC
WAS NOT FOUND IN OBID object-id during an UNLOAD FROMCOPYDDN.
This message along with DSNU1219I - THE NUMBER OF RECORDS
IN ERROR REACHED THE LIMIT nnnn were issued too many times and
flooded the message spool if no MAXERR specified or MAXERR 1.
If MAXERR integer(>=2), the UNLOAD abended with ABEND0C4 RC38
at DSNUULCA + x'7074' on DB2 9 for z/OS and ABEND0C4 RC11 at
DSNUULCA + x'3B4A' on DB2 10. It may lead to the DB2 subsystem
abnormally terminated with ABEND04E RC00E20028 and MSGDSNV086E
- DB2 ABNORMAL TERMINATION REASON=00F30801.
This problem occurred because UNLOAD was not handling the return
code correctly and issuing messages for every single record,
including beyond the MAXERR value.
UNLOAD code has been modified to correct the reported problems.
And if MAXERR is 0 or greater than 2000, UNLOAD will now stop
issuing the DSNU1239I message once 2000 of them have been
issued and issue MSGDSNU1140I stating this fact but will still
continue processing until MAXERR has been reached.
This APAR also introduces the following changes to the
Messages publication:
Description change for message DSNU1140I:
DSNU1140I
csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR
message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY
Explanation
The number of instances of the indicated message issued during a
utility operation has exceeded the maximum number permitted.
1 csect-name
The name of the control section that issued the message.
max-messages
The maximum number of messages that are issued before this
message is issued. This value is controlled by the utility that
issues message DSNU1140I.
message-number
The message number that has reached the limit and is now
suppressed.
| Example 1: The LOAD utility issues message DSNU1140I after
2000 instances of any of the following messages: DSNU313I,
DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have
triggered the suppressed message are still discarded.
| Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message
| DSNU1140I after 2000 instances of message DSNU1239I, when
| MAXERR is specified to greater than 2000 or 0. Any rows that
| would have triggered the suppressed message are still not
| unloaded.
System action
Processing continues.
No additional instances of message-number messages are issued.
Only the issuance of the message is suppressed. Any action that
is associated with the suppressed message number still occurs.
User response
No action is required.
Severity
0
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63979
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
PM63979 introduces the following changes to the Messages
publication:
Description change for message DSNU1140I:
DSNU1140I
csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR
message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY
Explanation
The number of instances of the indicated message issued during a
utility operation has exceeded the maximum number permitted.
csect-name
The name of the control section that issued the message.
max-messages
The maximum number of messages that are issued before this
1 message is issued. This value is controlled by the utility that
issues message DSNU1140I.
message-number
The message number that has reached the limit and is now
suppressed.
| Example 1: The LOAD utility issues message DSNU1140I after
2000 instances of any of the following messages: DSNU313I,
DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have
triggered the suppressed message are still discarded.
| Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message
| DSNU1140I after 2000 instances of message DSNU1239I, when
| MAXERR is specified to greater than 2000 or 0. Any rows that
| would have triggered the suppressed message are still not
| unloaded.
System action
Processing continues.
No additional instances of message-number messages are issued.
Only the issuance of the message is suppressed. Any action that
is associated with the suppressed message number still occurs.
User response
No action is required.
Severity
0
ACTION:
The PTF for APAR PM63979 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
To make this fix effective for a static application, it must be
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
ACTION:
The PTF for APAR PM50005 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
1 utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
ACTION:
***Action for PM50006:
It should be noted that the removal of these UNLOAD restrictions
will now allow clone and/or base table data to be UNLOADed
using image copy data sets from the other table in the clone
relationship as follows:
1 - UNLOAD from base table using a clone table image copy.
2 - UNLOAD from clone table using a base table image copy.
And in these cases the MSGDSNU1227I and MSGDSNU1408I messages
will no longer be issued and the return codes will be zero with
this APAR fix.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULCA PM63979
DSNUULCB PM63979
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63979 DSNUULCA DSNUULCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULCA
DSNUULCB
LISTEND
UK79770 COVER LETTER END
UK79774 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79820 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM66305 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the *
* -DISPLAY UTILITY or -TERM UTILITY *
* commands. *
****************************************************************
* PROBLEM DESCRIPTION: Customer ran a -DISPLAY UTIL command *
* while a BACKUP SYSTEM utility was *
* running. This resulted in an ABENDS0C4 *
* DSNUGDIS+x'5030'. This failure may *
* also occur on the -TERM UTIL command *
* or while a RESTORE SYSTEM utility is *
* running. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This abend can only occur when there is a BACKUP SYSTEM or
RESTORE SYSTEM utility running at the time of the command.
1 It can occur on both the -DISPLAY UTIL and -TERM UTIL commands.
This abend is caused by a 31-bit address being passed into an
internal routine which expects a 64 bit address.
Additional Keywords: OFFSET5030
The two addresses passed to the internal routine were changed
to 64-bit.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM66305
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDIS PM66305
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM66305 DSNUGDIS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDIS
LISTEND
UK79820 COVER LETTER END
UK79823 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79832 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79871 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62786 -
****************************************************************
* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS *
* utility users of LOAD with TRUSTED CONTEXT *
****************************************************************
* PROBLEM DESCRIPTION: LOAD with TRUSTED CONTEXT results in *
* storage growth of subpool 231 in the *
* DBM1 address space *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD with TRUSTED CONTEXT results in subpool 231 storage growth
in the DBM1 address space. This is due to LOAD subtasks
overlaying the address of one of their control blocks with the
address of a control block from the LOAD main task. This caused
the storage of the original control block to not be freed when
the subtask went through deallocation which, in turn, resulted
in the DBM1 address space running low on storage.
LOAD code has been modified to save the pointer for the subtask
control block before overlaying it with the pointer from the
main task control block.
Subsystem Services code has been changed to make sure pointers
are set up correctly so the utility subtask control blocks can
1 be deallocated correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62786
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PM62786 has modified CSECTs in both the
DSNUT101 and DSN3AMGP load modules, affecting the utility batch
and DB2 MSTR address spaces. After the PTF has been applied, it
will become active in the utility batch address space
immediately upon job submission, while it will not take effect
in the DB2 MSTR address space until DB2 is stopped and started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 MSTR address spaces, the problem the PTF
addresses will not be resolved.
ACTION:
The PTF for APAR PM25135 has modified CSECTs in both the
DSNUT101 and DSN3AMGP load modules, affecting the utility batch
and DB2 MSTR address spaces. After the PTF has been applied, it
will become active in the utility batch address space
immediately upon job submission, while it will not take effect
in the DB2 MSTR address space until DB2 is stopped and started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 MSTR address spaces, the problem the PTF
addresses will not be resolved.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGSIT PM62786
DSN3EOT0 PM62786
DSN3ID30 PM62786
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62786 DSNUGSIT DSN3EOT0 DSN3ID30
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGSIT
DSN3EOT0
DSN3ID30
LISTEND
UK79871 COVER LETTER END
UK79876 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM66288 -
****************************************************************
1 * USERS AFFECTED: All DB2 9 for z/OS users using PADDED *
* indexes. *
* All DB2 10 for z/OS users using PADDED *
* indexes. *
****************************************************************
* PROBLEM DESCRIPTION: Multiple symptoms may occur during *
* ALTER ADD COLUMN to both table and *
* padded index while specifying DEFAULT *
* value: *
* - SQLCODE901 *
* - ABEND0C4 DSNKIXDB *
* - ABEND04E RC00E20005 DSNB1CPP *
* DSNSVBK *
* - ABNED04E RC00E2000F DSNKIXDB *
* DSNSVSFB *
* - Bring DB2 subsystem down *
* RC00D94001 or RC00D93001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incorrect padding of DEFAULT value may occur when ALTER ADD
COLUMN of VARCHAR field is done to both table and padded index.
Incorrect padding caused overlay of storage and various ABEND
symptoms and sometimes caused termination of DB2.
Additional Keywords: DB2OVRLAY/K SQLALTER DB2ABTERM DB2TERM
DB2 has been modified to use correct padding on PADDED index
when DEFAULT value is specified and padding is necessary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM66288
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKIXDB PM66288
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM66288 DSNKIXDB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKIXDB
LISTEND
UK79876 COVER LETTER END
UK79881 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79911 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63684 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users *
* of XMLTABLE and outer join. *
1 ****************************************************************
* PROBLEM DESCRIPTION: An infinite loop may occur for *
* a SELECT statement that contains an *
* XMLTABLE and multiple outer joins. *
****************************************************************
* RECOMMENDATION: *
* *
****************************************************************
An infinite loop may occur for a SELECT statement that contains
an XMLTABLE and multiple outer joins.
DB2 was fixed to process the statement that contains XMLTABLE
and multiple outer join correctly.
Additional Keywords: SQLOUTERJOIN SQLXML LOOPDSNXORMQ
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63684
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXQRWC PM63684
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63684 DSNXQRWC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXQRWC
LISTEND
UK79911 COVER LETTER END
UK79995 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM62554 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS 10 users running packages *
* last bound on prior releases, with ENABLE *
* or DISABLE bind option specified. *
****************************************************************
* PROBLEM DESCRIPTION: Storage shortage may occur on systems *
* running packages bound prior to DB2 10 *
* and bound with ENABLE or DISABLE bind *
* option. This could result in ABEND04E *
* RC00E2000C in DSNSVSVB and subsystem *
* termination. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running packages bound prior to DB2 10, the package must be
puffed to DB2 10 format. The puffing code for ENABLE and DISABLE
bind options allocates a separate storage for the new format.
This storage is freed at thread deallocation.
1
If the package was also bound with RELEASE(COMMIT), the package
is freed at commit while the thread could continue to run. If
the application commits and re-allocates this package
repeatedly, it could result in system storage being used up by
the storage allocated for puffing of ENABLE and DISABLE bind
options. This could result in storage shortage and ABEND04E
RC00E2000C at DSNSVSVB and subsequent subsystem termination.
DB2 has been modified to free the storage allocated for puffing
of ENABLE and DISABLE bind options earlier instead of waiting
until thread deallocation.
Keywords: DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM62554
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEAAL PM62554
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM62554 DSNXEAAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEAAL
LISTEND
UK79995 COVER LETTER END
UK80106 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80113 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM52724 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of SQL mass delete *
* and the RECOVER utility with the BACKOUT *
* YES option. *
****************************************************************
* PROBLEM DESCRIPTION: After the application of PTF UK66327 *
* (APAR PM30991), an application issuing *
* millions of SQL mass deletes on a *
* user table without commits caused *
* lock escalation to occur on catalog *
* table space DSNDB06.SYSCOPY resulting *
* in contention for COPY utility jobs *
* executing at the same time. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After the application of PTF UK66327 (APAR PM30991), an
application issuing millions of SQL mass deletes on a user
1 table without any commits caused lock escalation to occur
on catalog table space DSNDB06.SYSCOPY resulting in timeouts
for COPY utility jobs executing at the same time.
PTF UK66327/APAR PM30991, added code to insert a
SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' (L-M) when
a SQL mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER
TABLE ROTATE PARTITION is executed on a segmented or universal
table space. This SYSCOPY record was used to prohibit a
subsequent RECOVER BACKOUT YES since the deleted data is not
logged for these activities. See the closing text of PM30991
for more details.
The insert of the L-M SYSCOPY record can cause problems
for some customers, if SQL mass deletes are heavily used
without commits. In addition to contention on SYSCOPY, the
large number of SYSCOPY records inserted will cause the
SYSCOPY table space to grow.
The L-M SYSCOPY record will no longer be inserted for SQL
mass delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE
ROTATE PARTITION on segmented or UTS tables spaces. The
RECOVER utility will continue to check for the L-M SYSCOPY
record and issue msgDSNU556I (RECOVER CANNOT PROCEED FOR...
BECAUSE A SYSCOPY RECORD HAS BEEN ENCOUNTERED...) if found.
A new diagnostic log record is written for SQL mass delete,
TRUNCATE TABLE, and DROP TABLE. DSN1LOGP has been modified
to format the new diagnostic log record.
The RECOVER utility with the BACKOUT YES option will issue
a new message, msgDSNU1544I, if the diagnostic log record is
encountered during the LOGCSR or LOGUNDO phase:
..
DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type
obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER
TABLE ACTIVITY
..
Explanation: BACKOUT YES was specified for the RECOVER utility,
but it cannot proceed because a prior SQL mass
DELETE, TRUNCATE TABLE, or DROP TABLE occurred
on the object. The deleted data for these
activities are not logged, hence cannot be backed
out. The recovery is prohibited when this kind of
activity has occurred between the recovery point
(specified by TOLOGPOINT or TORBA) and the current
time.
..
System action: The utility terminates processing.
..
User response: Remove the BACKOUT YES option from the RECOVER
utility statement and resubmit the job. This
will recover the list of objects by restoring a
backup then applying the logs forward to the
recovery point.
..
Severity: 8 (error)
..
Note that if the table space has indexes or auxiliary objects
(LOB or XML table spaces and all auxiliary indexes) RECOVER
BACKOUT YES is not supported on these objects when SQL mass
1 delete, TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE
PARTITION has occurred on the base table space.
The new diagnostic log record is not needed for the ALTER
TABLE ROTATE PARTITION case because a SYSCOPY record with
ICTYPE='A' and STYPE='R' is already inserted. In this case,
RECOVER with the BACKOUT YES option will be prohibited with
msgDSNU556I.
A change has been made to the RECOVER utility with the
BACKOUT YES option to delay the setting of RECP on the target
objects. The setting of RECP on the target objects has been
moved from the LOGCSR phase to the beginning of the LOGUNDO
phase, because the objects are not updated until the LOGUNDO
phase.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM52724
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
With the PTF for PM52724, a new DB2 message, DSNU1544I, will
be issued during the RECOVER utility with the BACKOUT YES
option if the recovery cannot proceed:
..
DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type
obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER
TABLE ACTIVITY
..
Explanation: BACKOUT YES was specified for the RECOVER utility,
but it cannot proceed because a prior SQL mass
DELETE, TRUNCATE TABLE, or DROP TABLE occurred
on the object. The deleted data for these
activities are not logged, hence cannot be backed
out. The recovery is prohibited when this kind of
activity has occurred between the recovery point
(specified by TOLOGPOINT or TORBA) and the current
time.
..
System action: The utility terminates processing.
..
User response: Remove the BACKOUT YES option from the RECOVER
utility statement and resubmit the job. This
will recover the list of objects by restoring a
backup then applying the logs forward to the
recovery point.
..
Severity: 8 (error)
..
See the closing text of PM52724 for details.
ACTION:
After the application of the PTF for APAR PM52724, the
SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will no
longer be inserted for SQL mass delete, TRUNCATE TABLE,
DROP TABLE, or ALTER TABLE ROTATE PARTITION on segmented or
universal table spaces (UTS).
..
A new DB2 message, DSNU1544I, will now be issued during the
1 RECOVER utility with the BACKOUT YES option if the recovery
cannot proceed:
..
DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type
obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER
TABLE ACTIVITY
..
Explanation: BACKOUT YES was specified for the RECOVER utility,
but it cannot proceed because a prior SQL mass
DELETE, TRUNCATE TABLE, or DROP TABLE occurred
on the object. The deleted data for these
activities are not logged, hence cannot be backed
out. The recovery is prohibited when this kind of
activity has occurred between the recovery point
(specified by TOLOGPOINT or TORBA) and the current
time.
..
System action: The utility terminates processing.
..
User response: Remove the BACKOUT YES option from the RECOVER
utility statement and resubmit the job. This
will recover the list of objects by restoring a
backup then applying the logs forward to the
recovery point.
..
Severity: 8 (error)
..
See the closing text of PM52724 for details.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNFMDIR PM52724
DSNFUDRE PM52724
DSNILDOR PM52724
DSNIRCSR PM52724
DSNISEGD PM52724
DSNIUNDO PM52724
DSNKMDEL PM52724
DSNODALN PM52724
DSNUADP1 PM52724
DSNUBINS PM52724
DSNUCALA PM52724
DSNUCALC PM52724
DSNUCALU PM52724
DSNUCASA PM52724
DSNUMSGE PM52724
DSNUYAS2 PM52724
DSN1LDET PM52724
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM52724 DSNFMDIR DSNFUDRE DSNILDOR DSNIRCSR DSNISEGD DSNIUNDO
DSNKMDEL DSNODALN DSNUADP1 DSNUBINS DSNUCALA DSNUCALC
DSNUCALU DSNUCASA DSNUMSGE DSNUYAS2 DSN1LDET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNFMDIR
DSNFUDRE
DSNILDOR
DSNIRCSR
DSNISEGD
DSNIUNDO
DSNKMDEL
DSNODALN
DSNUADP1
DSNUBINS
DSNUCALA
DSNUCALC
DSNUCALU
DSNUCASA
DSNUMSGE
DSNUYAS2
DSN1LDET
LISTEND
UK80113 COVER LETTER END
UK80120 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM63700 -
****************************************************************
* USERS AFFECTED: All DB2 V10 for z/OS users of FETCH CURRENT *
* CONTINUE LOB using JCC Type 2 Driver *
* (JCCT2ZOS) with Limited Block Fetch enabled. *
****************************************************************
* PROBLEM DESCRIPTION: After the application of apar PM56893 *
* (v10 ptf UK76986), an ABEND04E *
* RC00E70007 can occur for DB2 when an *
* application performs a FETCH CURRENT *
* CONTINUE operation on a LOB or XML *
* column using the JCC Type 2 driver with *
* Limited Block Fetch (LBF). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After the application of apar PM56893 (v10 ptf UK76986), an
ABEND04E RC00E70007 can occur for DB2 when an application
performs a FETCH CURRENT CONTINUE operation on a LOB or XML
column using the JCC Type 2 driver with Limited Block Fetch
(LBF).
This problem occurs because DB2 engine code does not set the
length of a LOB or XML column correctly for the JCC Type 2
driver which eventually leads to the abend.
The code in DB2 has been modified to correct the condition
which leads to the abend.
Additional Keywords: JCCT2ZOS SQLLOB SQLXML
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM63700
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
DSNOLMA2 PM63700
DSNOPGN2 PM63700
DSNXELFC PM63700
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM63700 DSNOLMA2 DSNOPGN2 DSNXELFC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOLMA2
DSNOPGN2
DSNXELFC
LISTEND
UK80120 COVER LETTER END
UK80191 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80199 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80206 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80231 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80240 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80243 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80259 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80291 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80299 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80327 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80337 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80357 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80359 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80363 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80372 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80407 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80414 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80439 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80447 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80449 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80459 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80493 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80522 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80523 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80525 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80552 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80559 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80662 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80672 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80785 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80830 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80840 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80868 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
1UK80897 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80910 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80929 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80931 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80981 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81001 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81020 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81022 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81023 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81045 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81046 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81064 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81147 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81174 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81177 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81178 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81181 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81223 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81241 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81263 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81271 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81304 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81306 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
READY
END
|
1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES
READY
%HOLDDATA WDB2I.R.DB2101S.SMPPTS
IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED
UK71333 HOLD DATA START
UK71333 HOLD DATA END
UK72025 HOLD DATA START
UK72025 HOLD DATA END
UK72077 HOLD DATA START
UK72077 HOLD DATA END
UK72081 HOLD DATA START
UK72081 HOLD DATA END
UK72088 HOLD DATA START
UK72088 HOLD DATA END
UK72091 HOLD DATA START
UK72091 HOLD DATA END
UK72268 HOLD DATA START
UK72268 HOLD DATA END
UK72303 HOLD DATA START
UK72303 HOLD DATA END
UK72345 HOLD DATA START
++ HOLD(UK72345) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271)
COMMENT
(***Action for PM43934:
See PM43934 APAR/PTF text for additional information about
why a REBIND is necessary.
PM43934 corrects a problem that can lead to an ABEND04E
RC00E70005 at location DSNXESX2:P404.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK66763) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271)
COMMENT
(***Action for PM28718:
1 See PM28718 APAR/PTF text for additional information about
why a REBIND is necessary.
PM28718 corrects a problem of incorrect output when running
a query which SELECT from MERGE when the UPDATE clause is in
row expression format and the MERGE contains an INCLUDE column
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK72345 HOLD DATA END
UK72373 HOLD DATA START
++ HOLD(UK72373) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11271)
COMMENT
(***Action for PM39078:
See PM39078 APAR/PTF text for additional information about
why a REBIND is necessary.
PM39078 corrects a problem of missing warning message when a
query which references an XML column that does not support
multiple XML versions and it is bound with the USE CURRENTLY
COMMITTED option.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK72373) SYS FMID(HDBAA10) REASON(DOC) DATE(11271)
COMMENT
(Existing warning SQLCODE +20002 is changed by this APAR/PTF.
The change will be documented in the DB2 Codes, SQL Reference,
Command Reference manuals respectively.
The texts for SQLCODE +20002 are:
+20002
THE clause SPECIFICATION IS IGNORED FOR OBJECT object-name
Explanation
This message is issued in response to a clause specification
that was ignored on a query statement.
System action
The statement is processed.
User response
To stop receiving this message, avoid
ACCESSCONCURRENTRESOLUTION(UseCurrentlyCommitted) bind option
for a plan or package accessing non-versioned XML, or
avoid a statement (accessing non-versioned XML) prepared with
"Use Currently Committed" attribute.
User response needs real action:
1
If an XML column does not support multiple XML versions,
you can convert to an XML column that supports multiple XML
versions by following these steps:
1. Unload the data from the table that contains the XML
columns.
2. Drop the table.
3. Create the table in a universal table space. The new
table supports multiple XML versions.
4. Load the data into the table.
SQLSTATE
01624).
UK72373 HOLD DATA END
UK72444 HOLD DATA START
UK72444 HOLD DATA END
UK72447 HOLD DATA START
UK72447 HOLD DATA END
UK72517 HOLD DATA START
UK72517 HOLD DATA END
UK72540 HOLD DATA START
UK72540 HOLD DATA END
UK72550 HOLD DATA START
UK72550 HOLD DATA END
UK72558 HOLD DATA START
UK72558 HOLD DATA END
UK72603 HOLD DATA START
UK72603 HOLD DATA END
UK72625 HOLD DATA START
UK72625 HOLD DATA END
UK72687 HOLD DATA START
UK72687 HOLD DATA END
UK72741 HOLD DATA START
UK72741 HOLD DATA END
1UK72775 HOLD DATA START
UK72775 HOLD DATA END
UK72786 HOLD DATA START
UK72786 HOLD DATA END
UK72803 HOLD DATA START
++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(DOC) DATE(11284)
COMMENT
(This PTF introduces the following changes to DB2 ODBC externals:
New DB2 ODBC for z/OS initialization keywords described as
follows.
LIMITEDBLOCKFETCH = 0 | 1
This keyword is a performance optimization keyword that
specifies whether DB2 ODBC is to attempt limited block fetch
when fetching result sets from the connected data source.
0 = Limited block fetch is not used. 0 is the default.
1 = DB2 ODBC attempts to use limited block fetch. If blocking
is supported at the server for the result set that is
being fetched, DB2 ODBC retrieves as many rows as it can
fit in a query data block in a single fetch request.
QUERYDATASIZE = integer
This keyword specifies the amount of query data, in bytes, that
DB2 returns on each FETCH operation when limited block fetch is
enabled. The default value is 32767. Possible values are:
32767 294911 557055 819199
65535 327679 589823 851967
98303 360447 622591 884735
131071 393215 655359 917503
163839 425983 688127 950271
196607 458751 720895 983039
229375 491519 753663 1015807
262143 524287 786431 1048575
If you specify a value that is not a valid value, DB2 ODBC sets
QUERYDATASIZE to the nearest valid value.
Information about the new DB2 ODBC initialization keywords
and DB2 ODBC limited block fetch will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.).
++ HOLD(UK67822) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284)
COMMENT
(*** Action for PM32032 (Version 10)
The following database request module (DBRM) is updated by
this PTF:
DSNCLIQR
Application of this PTF requires a BIND PACKAGE for the above
package. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
1
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.).
++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284)
COMMENT
(The following database request modules (DBRMs) are updated by
this PTF:
DSNCLINF
DSNCLIC1
DSNCLIMS
DSNCLIQR
DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only)
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
This PTF introduces two new DB2 ODBC initialization keywords
LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block
fetch. Limited block fetch is a performance optimization that
enables applications to improve the performance of FETCH
operations when connected to a local DB2 for z/OS server.
If limited block fetch is not desired, no further action is
necessary other than rebinding the DBRMs listed above;
otherwise please note the following.
When you enable limited block fetch, the data that is returned
to your application might not reflect the data that has been
committed to the source table. If your application fetches
data from tables that are updated by other users, or if your
application uses savepoints and issues ROLLBACK TO SAVEPOINT
to manage transactions, you should disable limited block fetch.).
++ HOLD(UK60517) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284)
COMMENT
(
This PTF updates DB2 ODBC for z/OS database request module
(DBRM) DSNCLIC1.
After you apply this PTF, you need to run the BIND PACKAGE
command to recreate the package for DSNCLIC1. Failure to bind
the required package could result in SQLCODE -805 at application
run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
prefix.SDSNSAMP data set for an example of how to perform the
BIND command.).
++ HOLD(UK56516) SYS FMID(JDBAA17) REASON(ACTION) DATE(11284)
COMMENT
1 (The following database request modules (DBRMs) for ODBC
DB2 for z/OS are updated by this PTF:
DSNCLIMS
DSNCLIC1
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
SDSNSAMP dataset for an example of how to perform the
BIND command.).
UK72803 HOLD DATA END
UK72809 HOLD DATA START
UK72809 HOLD DATA END
UK72834 HOLD DATA START
UK72834 HOLD DATA END
UK72870 HOLD DATA START
UK72870 HOLD DATA END
UK72880 HOLD DATA START
UK72880 HOLD DATA END
UK72946 HOLD DATA START
++ HOLD(UK72946) SYS FMID(J2AG210) REASON(ACTION) DATE(11287)
COMMENT
(This apar provides the functions to retrieve the current
and surrounding grid cells from a starting point.
For the existing users, if they like to use this function
then submit 2 last steps: CREATE01 and BINDSK19 of
DSN5SENB job.
For the new users should follow the instructions contained
in the book
IBM Spatial Support for DB2 z/OS to enable Spatial
functionality.).
UK72946 HOLD DATA END
UK72958 HOLD DATA START
UK72958 HOLD DATA END
UK72974 HOLD DATA START
++ HOLD(UK72974) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11287)
COMMENT
(***Action for PM48011:
1 A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM48011 corrects a problem of inaccurate cost estimation for
a query with subqueries that is correlated to multiple tables
or with a correlated subquery predicate under a non-boolean
term predicate.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK72974 HOLD DATA END
UK72985 HOLD DATA START
UK72985 HOLD DATA END
UK73058 HOLD DATA START
UK73058 HOLD DATA END
UK73079 HOLD DATA START
UK73079 HOLD DATA END
UK73137 HOLD DATA START
++ HOLD(UK73137) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(11294)
COMMENT
(PM44216 is an enabling APAR that includes additional support
for the subsystem parameter XML_RANDOMIZE_DOCID (added by
APAR PM31487). The additional support is enabled when
XML_RANDOMIZE_DOCID is set to YES.
Users who are not creating tables with XML columns on
data-sharing systems will not be affected by PM44210/PM44216.
For users who will create new tables with XML columns in
a data-sharing group and intend to enable the parameter
XML_RANDOMIZE_DOCID, the pre-conditioning APAR PM44210
for DB2 9 for z/OS and the pre-conditioning APAR PM31486
for DB2 10 for z/OS must be applied to all data-sharing
members before enabling APAR PM44216 is applied to any member.).
UK73137 HOLD DATA END
UK73147 HOLD DATA START
UK73147 HOLD DATA END
UK73165 HOLD DATA START
++ HOLD(UK73165) SYS FMID(HDBAA10) REASON(ACTION) DATE(11297)
COMMENT
(The PTF for APAR PM47687 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility batch
1 and DB2 DBM1 address spaces. After the PTF has been applied, it
will become active in the utility batch address space
immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
UK73165 HOLD DATA END
UK73178 HOLD DATA START
UK73178 HOLD DATA END
UK73180 HOLD DATA START
++ HOLD(UK73180) SYS FMID(HDBAA10) REASON(ACTION) DATE(11297)
COMMENT
(***Action for PM37057 (V10):
This APAR/PTF provides additional enhancements to the
DB2 10 for z/OS support for client access using a digital
certificate.
DB2 10 for z/OS remote connection authentication processing has
been enhanced to ensure remote client's that accesses DB2 using
a digital certificate are properly authenticated when the
remote client user ID is different from the certificate user ID.
To implement client access to DB2 using a digital certificate,
users need to define a trusted context at the DB2 server where
the system authorization ID is set to the value of the user ID
associated with the client certificate. The trusted context
would need to include all the user IDs that are allowed to use
it (such as, remote client user IDs or the mapped user IDs if
z/OS identity name filtering is configured).
Example: A client certificate is registered to RACF and it is
associated with user ID, CERTID01. A remote client application
is configured to access DB2 using a digital certificate and
its user ID provided to DB2 is USER01. To define the trusted
context at the DB2 server, users might consider the following
sample DDL:
CREATE TRUSTED CONTEXT CTXT1
BASED UPON CONNECTION USING CERTID01
NO DEFAULT ROLE ENABLE
ATTRIBUTES(ADDRESS '1.2.3.4')
WITH USE FOR USER01;
See PM37057 APAR/PTF text for additional information.).
UK73180 HOLD DATA END
UK73264 HOLD DATA START
UK73264 HOLD DATA END
1
UK73432 HOLD DATA START
UK73432 HOLD DATA END
UK73436 HOLD DATA START
UK73436 HOLD DATA END
UK73478 HOLD DATA START
++ HOLD(UK73478) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(11306)
COMMENT
(***Action for PM35190:
See PM35190 APAR/PTF text for additional information.
PM35190 is the enabling APAR that introduces the new function
support to allow selects from some Directory objects. Earlier,
a pre-conditioning APAR PM42331 was delivered and will be
needed. In a data sharing group, this pre-conditioning APAR
should be applied to all members before applying this ENABLING
APAR to any member. The new function will be enabled once this
ENABLING APAR is applied and DB2 enters NFM or once this
ENABLING APAR is applied and a special CATMAINT is run with the
input:
CATMAINT UPDATE UNLDDN PM35190).
++ HOLD(UK73478) SYS FMID(HDBAA10) REASON(DOC) DATE(11306)
COMMENT
(***Action for PM35190:
See PM35190 APAR/PTF text for additional information.
This APAR/PTF changes the text of SQL code -607. The change
will be documented in the DB2 Codes manual and in the
Information Management Software for z/OS Solutions Information
Center.
A new bullet under the example for SQL code -607:
- The operation is on a directory object and the unit of work
could not be converted to UR. For example:
UPDATE T1 SET C1 =
(SELECT C1 FROM T1) WHERE EXISTS(SELECT LGR SYSIBM.SYSLGRNX);
in this case, the SELECT against a directory object can not
be converted to UR.).
++ HOLD(UK72772) SYS FMID(HDBAA10) REASON(ACTION) DATE(11306)
COMMENT
(See PM47932 APAR/PTF text for additional information.
This PTF fixes the default maximum number of databases that can
be created implicitly.
Applying this PTF will not remove existing implicit databases
1 or update the current maximum number of implicit databases
allowed.
You can use the following query to find out the current maximum
number of implicit databases allowed:
SELECT MAXVALUE FROM SYSIBM.SYSSEQUENCES
WHERE SCHEMA = 'SYSIBM'
AND NAME = 'DSNSEQ_IMPLICITDB';
You can use the following statement to alter it:
ALTER SEQUENCE SYSIBM.DSNSEQ_IMPLICITDB MAXVALUE <number>
This <number> can be DB2's new default value of 10000 or any
valid value as allowed by the ALTER SEQUENCE statement.).
UK73478 HOLD DATA END
UK73534 HOLD DATA START
UK73534 HOLD DATA END
UK73587 HOLD DATA START
UK73587 HOLD DATA END
UK73600 HOLD DATA START
UK73600 HOLD DATA END
UK73617 HOLD DATA START
UK73617 HOLD DATA END
UK73625 HOLD DATA START
UK73625 HOLD DATA END
UK73649 HOLD DATA START
UK73649 HOLD DATA END
UK73663 HOLD DATA START
++ HOLD(UK73663) SYS FMID(HDBAA10) REASON(ACTION) DATE(11312)
COMMENT
(This PTF corrects a problem where rows containing
incorrectly truncated data are inserted into explain tables
DSN_FUNCTION_TABLE and DSN_PREDICAT_TABLE. As a result,
subsequent SELECTs on these tables received SQLCODE -331.
After applying this PTF, you must delete the rows that
are currently in the tables causing -331 to stop receiving
the SQL code.).
UK73663 HOLD DATA END
1UK73677 HOLD DATA START
UK73677 HOLD DATA END
UK73691 HOLD DATA START
UK73691 HOLD DATA END
UK73695 HOLD DATA START
UK73695 HOLD DATA END
UK73750 HOLD DATA START
UK73750 HOLD DATA END
UK73797 HOLD DATA START
++ HOLD(UK73797) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11315)
COMMENT
(***Action for PM50507:
See PM50507 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50507 corrects a problem of the DB2 optimizer in calculating
the cost of hash access for a hash-organized table. The
fix will get a more accurate estimation of hash access,
and enable the DB2 optimizer to choose hash access methods over
other suboptimal method(s).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK72787) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11315)
COMMENT
(A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM45292 corrects a problem in which a DB2 intentional abend may
occur when a query contains the RID function.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK73797 HOLD DATA END
UK73808 HOLD DATA START
UK73808 HOLD DATA END
UK73842 HOLD DATA START
UK73842 HOLD DATA END
1
UK73863 HOLD DATA START
++ HOLD(UK70468) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11319)
COMMENT
(***Action for PM38744:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM38744 corrects a problem of inaccurate cost estimation for an
index on the inner table in a join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK73863 HOLD DATA END
UK73908 HOLD DATA START
++ HOLD(UK73908) SYS FMID(HDBAA10) REASON(ACTION) DATE(11320)
COMMENT
(The PTF for APAR PM50893 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
UK73908 HOLD DATA END
UK73938 HOLD DATA START
UK73938 HOLD DATA END
UK73941 HOLD DATA START
UK73941 HOLD DATA END
UK73956 HOLD DATA START
UK73956 HOLD DATA END
UK74004 HOLD DATA START
UK74004 HOLD DATA END
UK74043 HOLD DATA START
UK74043 HOLD DATA END
1
UK74044 HOLD DATA START
UK74044 HOLD DATA END
UK74063 HOLD DATA START
UK74063 HOLD DATA END
UK74123 HOLD DATA START
UK74123 HOLD DATA END
UK74131 HOLD DATA START
UK74131 HOLD DATA END
UK74181 HOLD DATA START
UK74181 HOLD DATA END
UK74244 HOLD DATA START
UK74244 HOLD DATA END
UK74247 HOLD DATA START
UK74247 HOLD DATA END
UK74314 HOLD DATA START
UK74314 HOLD DATA END
UK74373 HOLD DATA START
++ HOLD(UK66610) SYS FMID(HDBAA10) REASON(DOC) DATE(11334)
COMMENT
(The fix for APAR PM25652, introduces a new special option,
RRTHashOvrFlwRatio. The Utility Guide and Reference and
The Application Programming Guide documentation on DSNACCOX
will have a new description of RRTHashOvrFlwRatio as follows:
Syntax:
-|---+---' '--------------+---|-
+-RRTHashOvrFlwRatio-+
'- -1 ---------------'
Description:
RRTHashOvrFlwRatio
Specifies a criterion for recommending that the REORG utility
is run on a table space. If the following conditions are true,
DSNACCOX recommends running REORG:
- The hash access overflow index is being used for access.
- The number of hash access overflow index entries divided by
the total number of rows (expressed as a percentage) is
1 greater than RRTHashOvrFlwRatio.
RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The
default value is ' 15'. A plus sign (+) preceding or following
the value, or a plus sign by itself indicates that the DSNACCOX
stored procedure returns the calculated ratio value in the
result set. A negative value indicates that the criterion is
not used.
The ratio of hash access overflow index entries to the total
number of rows is returned in column RRTHashOvrFlwRatPCT of the
result set.
Figure 4. DSNACCOX formula for recommending a REORG on a table
space has an additional criteria:
(((QueryType='REORG' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL')) AND
(REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR
(NACTIVE IS NULL OR NACTIVE > 5) AND
((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND
REORGINSERTS > RRTInsertsAbs) OR
(((REORGDELETE x 100) / TOTALROWS > RRTDeletesPct) AND
REORGDELETE > RRTDeleteAbs) OR
(REORGCLUSTERSENS > 0 AND
(REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR
((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR
| (Object is not using hash organization and ((SPACE x 1024) /
RRTDataSpaceRat)) OR
((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS >
RRTIndRefLimit) OR
REORGMASSDELETE > RRTMassDelLimit OR
EXTENTS > ExtentLimit) OR
| ((QueryType='REORG' OR QueryType='ALL') AND
| ObjectType='ALL' * AND
| Overflow index hash access is used**, AND
| ((overflow index TOTALENTRY x 100) / TOTALROWS >
RRTHashOvrFlwRatio)) OR
((QueryType='RESTRICT' OR QueryType='ALL') AND
(ObjectType='TS' OR ObjectType='ALL') AND
The table space is in advisory or informational reorg
pending status)
|Note:
| * ObjectType='ALL' must be specified to use this criteria.
| for this criterion to be used. If ObjectType='TS' or
| ObjectType='IX' is specified, and '+' is specified for
| RRTHashOvrFlwRatio, an error message is issued. If
| ObjectType='TS' or ObjectType='IX' is specified, and
| '+' is not specified for RRTHashOvrFlwRatio, this
| criterion is not used.
| ** The overflow index is used when SYSINDEXES.HASH ='Y' AND
| SYSINDEXSPACESTATS.REORGINDEXACCESS > 0.
Add the following table entry to table for the
1 "DSNACCOX OUTPUT" section.
Result set row for second DSNACCOX result set
----------------------------------------------------------------
|Column name | Data type |Description |
----------------------------------------------------------------
|RRTHashOvrFlwRatPCT| Double |This is an optional column, |
| | |and it is being returned when |
| | |there is a plus (+) sign in |
| | |the RRTHashOverFlwRatio. |
| | | |
| | |If OBJECTTYPE is ALL and REORG|
| | |is YES, the ratio of Hash |
| | |Access overflow index entries |
| | |to the total number of rows, |
| | |expressed as a percentage. |
| | |Otherwise null. |
| | | |
| | |If the ratio of Hash Access |
| | |overflow index entries to the |
| | |total number of rows does not |
| | |exceed the value specified for|
| | |RRTHashOvrFlwRatio or meet the|
| | |criteria requirement, this |
| | |value is null. |
----------------------------------------------------------------).
++ HOLD(UK66610) SYS FMID(HDBAA10) REASON(ACTION) DATE(11334)
COMMENT
(Post-apply actions after applying the fix for APAR PM25652:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this is
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity).
UK74373 HOLD DATA END
UK74375 HOLD DATA START
UK74375 HOLD DATA END
UK74383 HOLD DATA START
UK74383 HOLD DATA END
UK74390 HOLD DATA START
UK74390 HOLD DATA END
UK74399 HOLD DATA START
++ HOLD(UK74399) SYS FMID(HDBAA10) REASON(DELETE) DATE(11335)
COMMENT
(This PTF deletes the module DSNADMJ5.
This PTF deletes the module DSNXEAS.
1 This PTF deletes the module DSNXEAS1.
This PTF deletes the module DSNXESID.
This PTF deletes the module DSN7GBRS.).
UK74399 HOLD DATA END
UK74453 HOLD DATA START
UK74453 HOLD DATA END
UK74462 HOLD DATA START
UK74462 HOLD DATA END
UK74477 HOLD DATA START
UK74477 HOLD DATA END
UK74482 HOLD DATA START
++ HOLD(UK74482) SYS FMID(HDBAA10) REASON(ACTION) DATE(11338)
COMMENT
(This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. It also modifies
DSNADMSB, a program that can be used to call
SYSPROC.ADMIN_INFO_SQL. Finally, it modifies the DB2 V10
installation process, relocating responsibility for binding the
DSNADMSB package and plan from job DSNTIJSG to job DSNTIJRT.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRMs DSNADMSS
and DSNADMSB
---------------------------------------------------------------
==> This action is required for all V10 customers
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2 supplied stored
procedures.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
---------------------------------------------------------------
(2) Refresh the WLM environment
---------------------------------------------------------------
1 ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL
stored procedure need to take this action after applying
the PTF
Issue the following VARY MVS command from the console to
refresh the WLM application environment:
VARY WLM,APPLENV=!wlmenv!,REFRESH
where !wlmenv! is the name of the WLM application
environment for running the SYSPROC.ADMIN_INFO_SQL stored
procedure.
---------------------------------------------------------------
(3) Update your customized copy of job DSNTIJSG
---------------------------------------------------------------
==> All DB2 V10 customers who maintain a customized copy of DB2
installation job DSNTIJSG need to take this action after
applying the PTF
(a) Edit your customized copy of DSNTIJSG.
(b) In job step DSNTIRU, locate and remove the bind package
and bind plan statements for DSNADMSB. DSNADMSB is now
bound as necessary when you run job DSNTIJRT.
(c) In job step DSNTIJG, locate and remove the grant
statement for PLAN DSNADMSB. Authority to execute
DSNADMSB is now granted when you run job DSNTIJRT
according to the authorization IDs in the GRANTTO list
of the configuration statement for stored procedure
SYSPROC.ADMIN_INFO_SQL.
(d) Save your changes.).
++ HOLD(UK70375) SYS FMID(HDBAA10) REASON(ACTION) DATE(11338)
COMMENT
(This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. It also modifies
DSNADMSB, a program that can be used to call
SYSPROC.ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2 supplied stored
procedures.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
1 changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
---------------------------------------------------------------
(2) Refresh the WLM environment
---------------------------------------------------------------
==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL
stored procedure need to take this action after applying
the PTF
Issue the following VARY MVS command from the console to
refresh the WLM application environment:
VARY WLM,APPLENV=!wlmenv!,REFRESH
where !wlmenv! is the name of the WLM application
environment for running the SYSPROC.ADMIN_INFO_SQL stored
procedure.
---------------------------------------------------------------
(3) Rebind the package for DSNADMSB
---------------------------------------------------------------
==> All DB2 V10 customers who use the DSNADMSB program to call
the SYSPROC.ADMIN_INFO_SQL stored procedure need to take
this action after applying the PTF
Submit a job that contains the following BIND statements:
BIND PACKAGE(DSNADMSB) MEM(DSNADMSB) -
ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) -
LIBRARY('<prefix>.SDSNDBRM')
where <prefix> is the high-level qualifier for the
target DB2 subsystem.).
UK74482 HOLD DATA END
UK74491 HOLD DATA START
++ HOLD(UK74491) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046)
COMMENT
(***Action for PM53780:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM53780 corrects a problem in which incorrect statistics are
used for a DGTT or CGTT when the table is empty.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
1++ HOLD(UK73797) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046)
COMMENT
(***Action for PM50507:
See PM50507 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50507 corrects a problem of the DB2 optimizer in calculating
the cost of hash access for a hash-organized table. The
fix will get a more accurate estimation of hash access,
and enable the DB2 optimizer to choose hash access methods over
other suboptimal method(s).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK72787) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12046)
COMMENT
(A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM45292 corrects a problem in which a DB2 intentional abend may
occur when a query contains the RID function.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK74491 HOLD DATA END
UK74503 HOLD DATA START
UK74503 HOLD DATA END
UK74527 HOLD DATA START
UK74527 HOLD DATA END
UK74534 HOLD DATA START
UK74534 HOLD DATA END
UK74535 HOLD DATA START
++ HOLD(UK74535) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340)
COMMENT
(In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.).
++ HOLD(UK68665) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340)
COMMENT
(In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2,EARLY command.).
++ HOLD(UK66483) SYS FMID(HIZAA10) REASON(ACTION) DATE(11340)
1 COMMENT
(In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.).
UK74535 HOLD DATA END
UK74537 HOLD DATA START
UK74537 HOLD DATA END
UK74555 HOLD DATA START
UK74555 HOLD DATA END
UK74560 HOLD DATA START
++ HOLD(UK74560) SYS FMID(HDBAA10) REASON(ACTION) DATE(11341)
COMMENT
(This PTF fixes an 0C4 abend in the user-defined function
DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) when it is processing
a DB2 scheduler task that has multiple execution statuses.
***************************************************************
Actions for customers who are already using DB2 V10:
***************************************************************
***********************************************************
* This action is required for all V10 customers
***********************************************************
Run your customized copy of job DSNTIJRT with MODE(INSTALL)
to alter the scratchpad length of the modified user-defined
function DSNADM.ADMIN_TASK_STATUS(MAX_HISTORY) from 16 to
8208 and to bind this function's DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UK74560 HOLD DATA END
UK74587 HOLD DATA START
UK74587 HOLD DATA END
UK74596 HOLD DATA START
UK74596 HOLD DATA END
UK74623 HOLD DATA START
1UK74623 HOLD DATA END
UK74648 HOLD DATA START
UK74648 HOLD DATA END
UK74649 HOLD DATA START
UK74649 HOLD DATA END
UK74659 HOLD DATA START
UK74659 HOLD DATA END
UK74716 HOLD DATA START
++ HOLD(UK74716) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11346)
COMMENT
(***Action for PM52371:
See PM52371 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52371 corrects a problem of unexpected SQLCODE -161 issued
for an INSERT into SYMMETRIC view statement.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK74716 HOLD DATA END
UK74718 HOLD DATA START
UK74718 HOLD DATA END
UK74721 HOLD DATA START
UK74721 HOLD DATA END
UK74725 HOLD DATA START
UK74725 HOLD DATA END
UK74731 HOLD DATA START
UK74731 HOLD DATA END
UK74737 HOLD DATA START
UK74737 HOLD DATA END
UK74745 HOLD DATA START
UK74745 HOLD DATA END
1
UK74747 HOLD DATA START
UK74747 HOLD DATA END
UK74778 HOLD DATA START
UK74778 HOLD DATA END
UK74779 HOLD DATA START
++ HOLD(UK74779) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11347)
COMMENT
(***Action for PM52548:
See PM52548 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52548 fixes an abend 0C4 RC00000038 DSNISPBM + 1A64 that can
occur during query execution for queries containing IS NULL
or LIKE predicates.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71244) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11347)
COMMENT
(***Action for PM38082:
See PM38082 APAR/PTF text for additional information about
why a REBIND is necessary.
PM38082 corrects a query performance problem involving
significant loss of page range screening for queries with
multi-column partitioning keys and predicates with host
variables or parameter markers on those columns.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK64444) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11347)
COMMENT
(See PM25059 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM25059 corrects a problem where the page range reduction
is done incorrectly. It may cause DB2 to choose a plan with
an extra GROUP BY / ORDER BY sort where it is not needed.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK74779 HOLD DATA END
1
UK74807 HOLD DATA START
UK74807 HOLD DATA END
UK74815 HOLD DATA START
UK74815 HOLD DATA END
UK74866 HOLD DATA START
++ HOLD(UK74866) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(11349)
COMMENT
(***Action for PM50516:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM50516 corrects a problem in which an incorrect compound
filter factor is computed when there is data skew and that
data skew is represented by frequency statistics.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK74866 HOLD DATA END
UK74868 HOLD DATA START
UK74868 HOLD DATA END
UK74881 HOLD DATA START
UK74881 HOLD DATA END
UK74884 HOLD DATA START
UK74884 HOLD DATA END
UK74911 HOLD DATA START
UK74911 HOLD DATA END
UK74922 HOLD DATA START
UK74922 HOLD DATA END
UK74940 HOLD DATA START
UK74940 HOLD DATA END
UK74968 HOLD DATA START
UK74968 HOLD DATA END
1UK74981 HOLD DATA START
UK74981 HOLD DATA END
UK74989 HOLD DATA START
UK74989 HOLD DATA END
UK75093 HOLD DATA START
UK75093 HOLD DATA END
UK75105 HOLD DATA START
UK75105 HOLD DATA END
UK75106 HOLD DATA START
UK75106 HOLD DATA END
UK75161 HOLD DATA START
++ HOLD(UK75161) SYS FMID(HDBAA10) REASON(ACTION) DATE(11365)
COMMENT
(The PTF for APAR PM47255 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
UK75161 HOLD DATA END
UK75202 HOLD DATA START
UK75202 HOLD DATA END
UK75208 HOLD DATA START
UK75208 HOLD DATA END
UK75229 HOLD DATA START
UK75229 HOLD DATA END
UK75234 HOLD DATA START
UK75234 HOLD DATA END
UK75262 HOLD DATA START
1UK75262 HOLD DATA END
UK75286 HOLD DATA START
UK75286 HOLD DATA END
UK75291 HOLD DATA START
++ HOLD(UK75291) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12009)
COMMENT
(***Action for PM49645:
See PM49645 APAR/PTF text for additional information about
why a REBIND is necessary.
PM49645 corrects a problem of abend0E4 at DSNXESX2:M999
for a SELECT from INSERT/UPDATE/MERGE/DELETE statement
that contain an include column and an EXISTS correlated
subquery.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71122) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12009)
COMMENT
(See PM43916 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM43916 corrects a problem where a query with
INSERT/UPDATE/DELETE within a SELECT statement hits SQLCODE
-20478 error since the estimated query cost has a mismatch
between the SQLCA and GET DIAGNOSTICS area.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK75291 HOLD DATA END
UK75294 HOLD DATA START
UK75294 HOLD DATA END
UK75317 HOLD DATA START
UK75317 HOLD DATA END
UK75322 HOLD DATA START
UK75322 HOLD DATA END
UK75335 HOLD DATA START
UK75335 HOLD DATA END
1
UK75385 HOLD DATA START
UK75385 HOLD DATA END
UK75395 HOLD DATA START
UK75395 HOLD DATA END
UK75452 HOLD DATA START
UK75452 HOLD DATA END
UK75551 HOLD DATA START
UK75551 HOLD DATA END
UK75581 HOLD DATA START
++ HOLD(UK75581) SYS FMID(HDBAA10) REASON(ACTION) DATE(12019)
COMMENT
(The PTF for PM54759 fixes the stored procedure
SYSPROC.ADMIN_UTL_MONITOR so that the task it adds to the DB2
scheduler task list to execute the stored procedure
SYSPROC.ADMIN_UTL_EXECUTE can be executed by the DB2 scheduler
when DECIMAL=COMMA is enabled in DSNHDECP.
See the PTF cover letter for more information.
***************************************************************
Actions for DB2 10 for z/OS customers who are using
the DB2-supplied stored procedures
SYSPROC.ADMIN_UTL_MONITOR and
SYSPROC.ADMIN_UTL_EXECUTE in conjunction
with the DB2 administrative task scheduler
***************************************************************
After applying this PTF, you need to remove the task
'DB2 AUTO PROCEDURE EXECUTE' from the DB2 scheduler task list.
This action is detailed below:
(1) Ensure that the DB2 scheduler is up and running. If
scheduler is not running, execute the following console
command:
START DSNADMT
where DSNADMT is the name of the scheduler.
(2) Invoke the user-defined function ADMIN_TASK_LIST to
determine if the task 'DB2 AUTO PROCEDURE EXECUTE' is in the
DB2 scheduler task list, by issuing the following SQL
statement:
SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T
WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE';
A JOB example for this action is given below in the JOB
1 EXAMPLES section.
When no such task exists proceed to step (4). Otherwise,
proceed to step (3), below.
(3) Remove task 'DB2 AUTO PROCEDURE EXECUTE' from the DB2
scheduler task list by invoking the DB2-supplied stored
procedure SYSPROC.ADMIN_TASK_REMOVE:
CALL SYSPROC.ADMIN_TASK_REMOVE
(task-name, return-code, message)
with the input parameter 'task-name' set to
'DB2 AUTO PROCEDURE EXECUTE'.
'return-code' and 'message' are output parameters.
A JOB example of using DB2 REXX Language Support for this
action is given below in the JOB EXAMPLES section.
(4) If the DB2 scheduler was started in step (1),
stop the scheduler by executing the following console
command:
MODIFY DSNADMT,APPL=SHUTDOWN
where DSNADMT is the name of the scheduler.
***************************************************************
JOB EXAMPLES
***************************************************************
Prior to running any example, customize it for your system by
adding a valid job card and modifying the examples as indicated
below.
***************************************************************
STEP (2) EXAMPLE
QUERY DSNADM.ADMIN_TASK_LIST
Required actions: 1. In lines 1-3,14 replace 'DSN!!0' with the
prefix of the target library for DB2 V10
2. In line 12 replace '!DSN!' with your DB2
subsystem name
3. In line 13 replace 'DSNTEP!!' with the
plan name for DSNTEP2 on your DB2
***************************************************************
//JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR
// DD DSN=DSN!!0.SDSNLOAD,DISP=SHR
// DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR
//DSNTEP2 EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSTSIN DD *
1 DSN SYSTEM(!DSN!)
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP!!) -
LIB('DSN!!0.RUNLIB.LOAD') PARMS('/ALIGN(MID)')
END
//SYSIN DD *
SELECT TASK_NAME FROM TABLE (DSNADM.ADMIN_TASK_LIST()) AS T
WHERE TASK_NAME = 'DB2 AUTO PROCEDURE EXECUTE'
***************************************************************
STEP (3) EXAMPLE
CALL SYSPROC.ADMIN_TASK_REMOVE
Required actions: 1. In lines 1-3 replace 'DSN!!0' with the
prefix of the target library for DB2 V10
2. In line 10 replace '#' with a forward
slash '/'. Closing comment sequence
is not allowed within ++HOLD text.
3. In line 11 replace '!DSN!' with your DB2
subsystem name
***************************************************************
//JOBLIB DD DSN=DSN!!0.SDSNEXIT,DISP=SHR
// DD DSN=DSN!!0.SDSNLOAD,DISP=SHR
// DD DSN=DSN!!0.RUNLIB.LOAD,DISP=SHR
//REXX EXEC PGM=IEBUPDTE,PARM='NEW'
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(2,1,1)),
// DSORG=PO,BLKSIZE=0,RECFM=FB,LRECL=80
//SYSIN DD *
./ ADD NAME=CALLSP
/* REXX *#
SSID = !DSN!
TASKNAME = 'DB2 AUTO PROCEDURE EXECUTE'
RETCODE = 12
MESSAGE = COPIES(' ',1332)
"SUBCOM DSNREXX"
IF RC <> 0 THEN
S_RC = RXSUBCOM('ADD','DSNREXX','DSNREXX')
ADDRESS DSNREXX "CONNECT" SSID
IF SQLCODE = 0 THEN DO
SAY 'CONNECTED TO ' SSID
ADDRESS DSNREXX "EXECSQL CALL ",
"SYSPROC.ADMIN_TASK_REMOVE(",
":TASKNAME, :RETCODE, :MESSAGE)"
IF SQLCODE <> 0 THEN
SAY 'FAILURE DURING SP CALL SQLCODE =' SQLCODE SQLERRMC
ELSE DO
IF RETCODE <> 0 THEN
SAY 'FAILURE RETURNED FROM SP.' RETCODE ' ' MESSAGE
ELSE
SAY 'TASK WAS REMOVED'
END
1 ADDRESS DSNREXX "DISCONNECT"
END
ELSE
SAY 'CONNECTION FAILED'
S_RC = RXSUBCOM('DELETE','DSNREXX','DSNREXX')
EXIT RETCODE
/*
//CALL EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20,
// PARM='%CALLSP'
//SYSPROC DD DSN=*.REXX.SYSUT2,DISP=(OLD,DELETE)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
***************************************************************
END OF JOB EXAMPLES
***************************************************************).
UK75581 HOLD DATA END
UK75583 HOLD DATA START
UK75583 HOLD DATA END
UK75587 HOLD DATA START
++ HOLD(UK75587) SYS FMID(J2AG210) REASON(ACTION) DATE(12024)
COMMENT
(This APAR is a replacement for apar PM47333, ptf UK72946.
This apar provides the function to retrieve the current
and surrounding grid cells from a starting point.
For existing users, if they would like to use this function,
please submit the last two steps (CREATE01 and BINDSK19) of the
DSN5SENB job.
For new users, please follow the instructions contained in the
publication "IBM Spatial Support for DB2 z/OS" to enable
Spatial
functionality.).
++ HOLD(UK72946) SYS FMID(J2AG210) REASON(ACTION) DATE(12024)
COMMENT
(This apar provides the functions to retrieve the current
and surrounding grid cells from a starting point.
For the existing users, if they like to use this function
then submit 2 last steps: CREATE01 and BINDSK19 of
DSN5SENB job.
For the new users should follow the instructions contained
in the book
IBM Spatial Support for DB2 z/OS to enable Spatial
functionality.).
UK75587 HOLD DATA END
UK75634 HOLD DATA START
UK75634 HOLD DATA END
1
UK75674 HOLD DATA START
UK75674 HOLD DATA END
UK75687 HOLD DATA START
UK75687 HOLD DATA END
UK75766 HOLD DATA START
++ HOLD(UK71709) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12027)
COMMENT
(***Action for PM44942:
See PM44942 APAR/PTF text for additional information about
why a REBIND is necessary.
PM44942 corrects a problem of a poorly performing access path
caused by incorrect filter factor estimation for a compound
predicate when frequency or histogram statistics exist, or
column cardinality is 1 or 2.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK69998) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12027)
COMMENT
(***Action for PM32384:
See PM32384 APAR/PTF text for additional information about
why a REBIND is necessary.
PM32384 corrects a problem of inaccurate index filter factor
estimate when multi-column cardinality exists in some cases
which may result in an inefficient access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK75766 HOLD DATA END
UK75779 HOLD DATA START
UK75779 HOLD DATA END
UK75785 HOLD DATA START
UK75785 HOLD DATA END
UK75836 HOLD DATA START
UK75836 HOLD DATA END
1UK75883 HOLD DATA START
UK75883 HOLD DATA END
UK75906 HOLD DATA START
++ HOLD(UK75906) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12034)
COMMENT
(See PM53285 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM53285 fixes an execution time abend when a query contains a
user-defined function and is run in parallelism.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK75906 HOLD DATA END
UK75933 HOLD DATA START
++ HOLD(UK75933) SYS FMID(HIZAA10) REASON(ACTION) DATE(12034)
COMMENT
(In order for this PTF to be fully effective, an IPL with CLPA or
REFRESH DB2,EARLY is required. The DB2 member should be
stopped before issuing the REFRESH DB2, EARLY command.).
UK75933 HOLD DATA END
UK75943 HOLD DATA START
UK75943 HOLD DATA END
UK75946 HOLD DATA START
UK75946 HOLD DATA END
UK75949 HOLD DATA START
++ HOLD(UK75949) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036)
COMMENT
(***Action for PM50451:
See PM50451 APAR/PTF text for additional information about
why a REBIND is necessary.
PM50451 corrects a problem of ABEND04E RC00E72018 at CSECT
DSNXSBUC offset 3E7A may happen when running query with
groupby clause and parallelism enabled.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK72877) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036)
COMMENT
(***Action for PM45209:
1
See PM45209 APAR/PTF text for additional information about
why a REBIND is necessary.
PM45209 corrects a problem of incorrect output on query
containing aggregate function distinct w/o group by and running
with dpsi index and parallelism.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71915) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036)
COMMENT
(***Action for PM43740:
See PM43740 APAR/PTF text for additional information about
why a REBIND is necessary.
PM43740 corrects a problem of ABEND04E RC00E70005 in DSNXGDT2
M201 may occur when one of the following condition met:
1. a UNION/INTERSECT/EXCEPT query with COUNT COLUMN function,
MIN/MAX aggregate function in the selection list and the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
2. Or a UNION ALL/INTERSECT ALL/EXCEPT ALL query with ORDER BY
clause and COUNT COLUMN function, MIN/MAX aggregate function
in the selection list. Also,the input of the COUNT COLUMN
function, MIN/MAX aggregate function has FIELD PROC defined
on it running in parallel.
3. Or a query with ORDER BY clause and a COUNT COLUMN function,
MIN/MAX aggregate function in the selection list. Also, the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
4. Or a SELECT DISTINCT statement with COUNT COLUMN function,
MIN/MAX aggregate function in the selection list. Also, the
input of the COUNT COLUMN function, MIN/MAX aggregate
function has FIELD PROC defined on it running in parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71922) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036)
COMMENT
(***Action for PM39444:
See PM39444 APAR/PTF text for additional information about
why a REBIND is necessary.
PM39444 corrects a problem of ABEND04E RC00E72018 at DSNXSTSE
offset 0A9C may occur when a query contains a column function
in the selection list and its result data type is a LOB running
in parallel.
To make this fix effective for a static application, it must be
1 rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK68830) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12036)
COMMENT
(***Action for PM36118:
See PM36118 APAR/PTF text for additional information about
why a REBIND is necessary.
PM36118 corrects a problem of ABEND0C4 RC00000011 DSNXRSGB
offset 5E5C may occur when view has duplicate group by
columns
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK75949 HOLD DATA END
UK75956 HOLD DATA START
UK75956 HOLD DATA END
UK75960 HOLD DATA START
UK75960 HOLD DATA END
UK75989 HOLD DATA START
UK75989 HOLD DATA END
UK76053 HOLD DATA START
++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(DOC) DATE(12040)
COMMENT
(See PM47356 APAR/PTF text for additional information.
This APAR/PTF modifies the DB2 Utility Guide and Reference
and the Messages manual. The change will be documented in
the DB2 Utility Guide and Reference and Messages, and in the
Information Management Software for z/OS Solutions Information
Center.
The change is as follows.
In the Utility Guide and Reference, under REORG TABLESPACE,
Option descriptions, SORTDATA option:
SORTDATA
NO
Specifies that the data is to be unloaded in the order
of the clustering index. SORTDATA NO cannot be specified
| with SHRLEVEL CHANGE or if the table space is in REORG-
| PENDING. Specify SORTDATA NO if one of the following
conditions is true:
1
* The data is in or near perfect clustering order, the
| table space is not in REORP, and the REORG utility is
used to reclaim space from dropped tables.
* The data is very large, an insufficient amount of disk
| space is available for sorting, and the table space is
not in REORP.
In the Messages manual, under DSNU messages:
DSNU070I csect-name KEYWORD OR OPERAND x
INVALID WITH y
Explanation: The use of a keyword or operand is
| inconsistent with another keyword, operand or condition.
| x and y The keywords, operands or conditions that
cannot be used together.
System action: The control statement in error is
rejected and processing is halted.
User response: Correct the control statement in error
and resubmit the job.
| Problem determination: The REORG TABLESPACE
| utility issues this message when the keywords, operands or
| conditions are not allowed to be used in combination.).
++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(ACTION) DATE(12040)
COMMENT
(The PTF for APAR PM47356 has modified the REORG TABLESPACE
utility to issue the following message and end with RC8 when
REORG TABLESPACE SORTDATA NO is run against a non-Partition-
By-Growth (non-PBG) partitioned table space in REORG-PENDING
(REORP). A REORG TABLESPACE SORTDATA YES is required to remove
the REORP state.
MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH
'TABLE SPACE IN REORG PENDING').
UK76053 HOLD DATA END
UK76071 HOLD DATA START
UK76071 HOLD DATA END
UK76083 HOLD DATA START
UK76083 HOLD DATA END
UK76086 HOLD DATA START
UK76086 HOLD DATA END
UK76093 HOLD DATA START
UK76093 HOLD DATA END
1
UK76109 HOLD DATA START
UK76109 HOLD DATA END
UK76110 HOLD DATA START
UK76110 HOLD DATA END
UK76112 HOLD DATA START
UK76112 HOLD DATA END
UK76113 HOLD DATA START
UK76113 HOLD DATA END
UK76147 HOLD DATA START
UK76147 HOLD DATA END
UK76148 HOLD DATA START
UK76148 HOLD DATA END
UK76153 HOLD DATA START
UK76153 HOLD DATA END
UK76155 HOLD DATA START
UK76155 HOLD DATA END
UK76162 HOLD DATA START
++ HOLD(UK76162) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12044)
COMMENT
(***Action for PM49443:
See PM49443 APAR/PTF text for additional information about
why a REBIND is necessary.
PM49443 allows LIKE predicates with the UPPER scalar function
to become indexable.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK73601) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12044)
COMMENT
(***Action for PM48939:
See PM48939 APAR/PTF text for additional information about
why a REBIND is necessary.
1 PM48939 corrects a problem of incorrect output may occur when a
pair-wise join query uses a multi-column index between dimension
table and Fact table and there is a Fact table local predicate
covered by the same multi-column index.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76162 HOLD DATA END
UK76164 HOLD DATA START
UK76164 HOLD DATA END
UK76178 HOLD DATA START
UK76178 HOLD DATA END
UK76206 HOLD DATA START
UK76206 HOLD DATA END
UK76209 HOLD DATA START
UK76209 HOLD DATA END
UK76211 HOLD DATA START
++ HOLD(UK76211) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12045)
COMMENT
(A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM50592 corrects a performance problem when a pair-wise join
plan is used for a short-running query with estimated elapsed
time less than 0.5 second. In that case, the actual elapsed
time may be over 0.5 sec.
To make this fix effective for a static application, it must
be rebound after application of this PTF. Review the PTF
cover letter to determine which, if any, applications could be
affected by this change.).
UK76211 HOLD DATA END
UK76231 HOLD DATA START
UK76231 HOLD DATA END
UK76247 HOLD DATA START
UK76247 HOLD DATA END
UK76249 HOLD DATA START
UK76249 HOLD DATA END
1
UK76251 HOLD DATA START
UK76251 HOLD DATA END
UK76309 HOLD DATA START
++ HOLD(UK76309) SYS FMID(HDBAA10) REASON(ACTION) DATE(12047)
COMMENT
(The PTF for APAR PM38329 has modified CSECTs in both the
DSNUT101 and DSNLDTML load modules, affecting the
utility batch and DB2 DDF address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DDF address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DDF address spaces, the problem the PTF
addresses will not be resolved.).
UK76309 HOLD DATA END
UK76352 HOLD DATA START
UK76352 HOLD DATA END
UK76370 HOLD DATA START
UK76370 HOLD DATA END
UK76379 HOLD DATA START
UK76379 HOLD DATA END
UK76387 HOLD DATA START
UK76387 HOLD DATA END
UK76404 HOLD DATA START
UK76404 HOLD DATA END
UK76407 HOLD DATA START
UK76407 HOLD DATA END
UK76421 HOLD DATA START
UK76421 HOLD DATA END
UK76431 HOLD DATA START
UK76431 HOLD DATA END
1
UK76439 HOLD DATA START
++ HOLD(UK73300) SYS FMID(HDBAA10) REASON(ACTION) DATE(12053)
COMMENT
(The ++HOLD and action is for DB2 users running in z/OS 1.12 or
higher only. See PM46045 APAR/PTF text for additional
information.
The following summarizes the interactions of DB2 APARs PM17542,
PM46045, and z/OS APARs OA36101, OA37361, and OA37362. It is
intended to help you determine when to apply DB2 and z/OS APARs,
and in what order.
1. PM17542 only - exposed to overlay and missing SMF I/O
counting at address space level. MEMDSENQMGMT irrelevent.
2. PM17542 with OA36101 - exposed to missing SMF I/O counting
at address space level only. MEMDSENQMGMT irrelevent.
3. PM17542 with OA36101, OA37361 & OA37362 - no longer exposed
to either problem.
4. PM17542 with PM46045 - S99DASUP setting now only turned on
when MEMDSENQMGMT is enabled. Exposed to overlay and
missing SMF I/O counting at address space level ONLY when
MEMDSENQMGMT is ENABLED.
5. PM17542 with PM46045 & OA36101 - S99DASUP setting now only
turned on when MEMDSENQMGMT is enabled. Exposed to missing
SMF I/O counting at address space level ONLY when
MEMDSENQMGMT is ENABLED.
6. PM17542 with PM46045, OA36101, OA37361 & OA37362 - no longer
exposed to either problem. Performance benefits for both
features introduced with PM17542 only available when
MEMDSENQMGMT is ENABLED.
Instructions on setting MEMDSENQMGMT to DISABLE or ENABLE:
----------------------------------------------------------
Work with your system programmer to complete one of the
following actions:
- Update the ALLOCxx parmlib member to set the SYSTEM
MEMDSENQMGMT value.
SYSTEM MEMDSENQMGMT(DISABLE) or
SYSTEM MEMDSENQMGMT(ENABLE)
- Issue system command SETALLOC
SETALLOC SYSTEM,MEMDSENQMGMT=DISABLE or
SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE
Note:
1. Updating the ALLOCxx parmlib is strongly recommended as it
1 remains effective across IPLs. You may apply the PTF and
update the ALLOCxx parmlib member at different times.
However the benefit of the APAR will only be available after
re-IPL with ALLOCxx changes or after issuing the SETALLOC
command as described above.
2. If SETALLOC SYSTEM,MEMDSENQMGMT command is used, a DB2
restart is required to make the change effective.
3. System command D ALLOC,OPTIONS can be used to display the
status of MEMDSENQMGMT in z/OS.
Sample DISPLAY output:
IEFA003I 15.35.15 ALLOC OPTIONS
SPACE PRIMARY: 4
SECONDARY: 24
:
SYSTEM IEFBR14_DELMIGDS: LEGACY
TAPELIB_PREF: EQUAL
REMIND_INTV: 90
VERIFY_UNCAT: FAIL
TEMPDSFORMAT: INCLUDELABEL
MEMDSENQMGMT: ENABLE).
UK76439 HOLD DATA END
UK76444 HOLD DATA START
UK76444 HOLD DATA END
UK76445 HOLD DATA START
UK76445 HOLD DATA END
UK76455 HOLD DATA START
++ HOLD(UK76455) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM51073:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM51073 corrects a problem that incorrect output may be returned
by a query if a NOT PADDED DPSI is used to return rows in order
and a matching predicate of the index is a LIKE predicate
matching on a column expression.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71025) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM40235:
1 A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PM40235 corrects a problem in which an unpredictable access
path may be chosen when index-only access is possible.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71000) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM39849:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM39849 corrects a problem that DB2 may choose an inefficient
access path while there exists an efficient index access path
with screening predicates.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76455 HOLD DATA END
UK76457 HOLD DATA START
++ HOLD(UK76457) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM55976:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM55976 corrects a problem in which the most appropriate index
only access may not be selected.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK75265) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM52549:
See PM52549 APAR/PTF text for additional information about
why a REBIND is necessary.
PM52549 corrects a problem of SQLCODE=-510 when doing a
BIND/REBIND on a FOR UPDATE cursor and IN-list direct table
access is attempted.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
1 letter to determine which, if any, applications could be
affected by this change.).
UK76457 HOLD DATA END
UK76480 HOLD DATA START
++ HOLD(UK75592) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM53062:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM53062 corrects a problem that incorrect output may be
returned by a query with GROUP BY clause and a set function
with DISTINCT.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK70468) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12059)
COMMENT
(***Action for PM38744:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM38744 corrects a problem of inaccurate cost estimation for an
index on the inner table in a join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76480 HOLD DATA END
UK76482 HOLD DATA START
++ HOLD(UK63012) SYS FMID(HDBAA10) REASON(ACTION) DATE(12059)
COMMENT
(----------------------------------------------------------------
THE PM25093 CORRECTION APPLIED ON ONE DB2 DATA SHARING MEMBER IS
NOT DEPENDENT ON ITS BEING APPLIED ON ALL OTHER DB2 DATA SHARING
MEMBERS. HOWEVER, IF A SEQUENCE OBJECT IS SHARED BY APPLICATIONS
ON MULTIPLE DB2 MEMBERS IN A DATA SHARING ENVIRONMENT, IT IS
ADVISED THAT THE PTF OF APAR PM25093 SHOULD BE APPLIED ON ALL
THE DB2 DATA SHARING MEMBERS WHERE THOSE APPLICATIONS WILL BE
RUN.
----------------------------------------------------------------).
UK76482 HOLD DATA END
UK76516 HOLD DATA START
UK76516 HOLD DATA END
1
UK76522 HOLD DATA START
UK76522 HOLD DATA END
UK76527 HOLD DATA START
UK76527 HOLD DATA END
UK76530 HOLD DATA START
UK76530 HOLD DATA END
UK76577 HOLD DATA START
++ HOLD(UK76577) SYS FMID(HDBAA10) REASON(ACTION) DATE(12058)
COMMENT
(Please note. If you are using DATE exits, this concerns you.
If you are using a DATE exit, specifically an EBCDIC, ASCII, or
UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make
sure it is functioning properly. If it is, a query referencing
the TIMESTAMP built-in function should work correctly and no
action is necessary. If however the exit is not working
properly and the query referencing the TIMESTAMP built-in
function worked in DB2 9 but is now not working in DB2 10 (i.e.
it does not return the expected result), then please ensure that
the exit is coded and working properly.).
UK76577 HOLD DATA END
UK76578 HOLD DATA START
++ HOLD(UK76578) SYS FMID(HDBAA10) REASON(ACTION) DATE(12059)
COMMENT
(***Action for PM53818:
This PTF corrects the problem where SQL scalar functions
became unusable after running the DSNTIJEN job.
If the DSNTIJEN job has not completed successfully, you should
apply this PTF first before starting or continuing the DSNTIJEN
job.
If the DSNTIJEN job has already completed without this PTF,
you can identify any affected SQL scalar functions by running
the following query:
SELECT R.SCHEMA
,R.NAME
,R.SPECIFICNAME
FROM SYSIBM.SYSROUTINES AS R
WHERE R.INLINE = 'Y' AND
R.ORIGIN = 'Q' AND
LENGTH(R.PARSETREE) = 0;
Any rows returned from the above query identify the affected
SQL scalar functions. You will need to drop and re-create them
1 to correct the problem.
You do not need to run the query if the DSNTIJEN job has
not been run or DB2 is running in CONVERSION mode, otherwise
this query may return no rows or a negative SQLCODE.).
UK76578 HOLD DATA END
UK76589 HOLD DATA START
++ HOLD(UK76589) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12058)
COMMENT
(***Action for PM55941:
See PM55941 APAR/PTF text for additional information about
why a REBIND is necessary.
PM55941 corrects a problem of a query with OPTIMIZE FOR n ROWS
or FETCH FIRST n ROWS ONLY where DB2 chooses the
non-correlated subquery access path instead of the
correlated subquery access path.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76589 HOLD DATA END
UK76596 HOLD DATA START
UK76596 HOLD DATA END
UK76609 HOLD DATA START
UK76609 HOLD DATA END
UK76610 HOLD DATA START
++ HOLD(UK76610) SYS FMID(HDBAA10) REASON(ACTION) DATE(12062)
COMMENT
(***Action for PM54699 (V10)
This PTF modifies V10 premigration checkout job DSNTIJPM. If
you maintain a customized copy of this job then after applying
this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPM
- Delete all lines and copy in the DSNTIJPM member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 V10, run the updated
customized job to check for conditions that may affect your
migration.).
UK76610 HOLD DATA END
UK76631 HOLD DATA START
1UK76631 HOLD DATA END
UK76636 HOLD DATA START
UK76636 HOLD DATA END
UK76642 HOLD DATA START
UK76642 HOLD DATA END
UK76643 HOLD DATA START
UK76643 HOLD DATA END
UK76645 HOLD DATA START
UK76645 HOLD DATA END
UK76650 HOLD DATA START
++ HOLD(UK76650) SYS FMID(HDBAA10) REASON(ACTION) DATE(12066)
COMMENT
(***Actions for PM52012
This PTF adds a new DB2 subsystem parameter in DSN6SPRM named
REORG_LIST_PROCESSING that allows you to specify the default
setting for the PARALLEL option of the DB2 REORG TABLESPACE
utility. The PARALLEL option indicates whether REORG TABLESPACE
will process all partitions specified in the input LISTDEF
statement in a single utility execution (PARALLEL YES) or
process each in a separate utility execution (PARALLEL NO).
Valid options for DSN6SPRM.REORG_LIST_PROCESSING are:
* PARALLEL: REORG TABLESPACE will assume PARALLEL
YES when the PARALLEL keyword is not
specified in the utility control
statement.
==> This is the default setting
* SERIAL : REORG TABLESPACE will assume PARALLEL
NO when the PARALLEL keyword is not
specified in the utility control
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
1 target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter REORG_LIST_PROCESSING=<x>,
where <x> is PARALLEL or SERIAL, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
REORG_LIST_PROCESSING here, the value will be set to the
default of PARALLEL when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for REORG_LIST_PROCESSING to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library.
You need to add these entries to all private copies of your
CLIST output DSNTIDxx member. In each such copy, add the
following lines:
REORG_LIST_PROCESSING CHAR M NONE NONE <x>
Change <x> to the value you specified for
REORG_LIST_PROCESSING in step (2), above.
If you do not add REORG_LIST_PROCESSING to a DSNTIDxx
member, the DB2 installation CLIST will assume
REORG_LIST_PROCESSING=PARALLEL when run with that member
as input.).
UK76650 HOLD DATA END
UK76651 HOLD DATA START
UK76651 HOLD DATA END
1UK76653 HOLD DATA START
UK76653 HOLD DATA END
UK76689 HOLD DATA START
UK76689 HOLD DATA END
UK76698 HOLD DATA START
UK76698 HOLD DATA END
UK76699 HOLD DATA START
UK76699 HOLD DATA END
UK76766 HOLD DATA START
UK76766 HOLD DATA END
UK76774 HOLD DATA START
UK76774 HOLD DATA END
UK76782 HOLD DATA START
++ HOLD(UK76782) SYS FMID(HDBAA10) REASON(DOC) DATE(12062)
COMMENT
(The "RACF Access Control Module Guide" (SC19-2982-01)
is updated with the changes below.
Chapter 14: RACF authorization checking reference
- In "System privileges" section, a note is added for SYSDBADM.
SYSDBADM
XAPLPRIV value: DB2AAUTHU
Privcode 287 (x'11F')
The user must have sufficient authority to:
One of these resources: In class:
------------------------------------------------------------
DB2-subsystem.SYSDBADM MDSNSM or GDSNSM
DB2-subsystem.SYSCTRL DSNADM
DB2-subsystem.SYSADM DSNADM
Note: DB2® turns on bit 7 of the XAPLFLG1 field for a user table
that includes user defined data type or user defined function.
If this bit is on, the RACF® access control module bypasses
checking for the SYSCTRL authority.).
UK76782 HOLD DATA END
UK76785 HOLD DATA START
1UK76785 HOLD DATA END
UK76802 HOLD DATA START
++ HOLD(UK76802) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12069)
COMMENT
(***Action for PM57388:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM57388 corrects a problem in which DB2 does not properly
determine the sorted order of the data for a query. This
can result in incorrect output and/or poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76802 HOLD DATA END
UK76803 HOLD DATA START
UK76803 HOLD DATA END
UK76806 HOLD DATA START
++ HOLD(UK76806) SYS FMID(HDBAA10) REASON(ACTION) DATE(12065)
COMMENT
(***Action for PM54662 (V10):
This PTF adds an online-changeable subsystem parameter in
DSN6FAC called DDF_COMPATIBILITY that can be used to specify
whether DDF returns stored procedure parameters according to
their declared types (V10 behavior) or according to the types
of the arguments specified in the CALL statement (pre-V10
behavior). Valid settings for DDF_COMPATIBILITY are:
* null : V10 behavior is maintained. DDF returns
stored procedure parameters according their
declared types.
==> This is the default setting
* SP_PARMS_NJV: Pre-V10 behavior is used for stored procedure
CALLs from IBM Data Server for non-Java
clients, Version 9.* and below. DDF converts
the data from a stored procedure's declared
SQL type to the argument type specified in
the CALL statement.
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
1 ----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is recommended for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add either the keyword parameter 'DDF_COMPATIBILITY=,' or
'DDF_COMPATIBILITY=SP_PARMS_NJV,' to the invocation of the
DSN6FAC macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
DDF_COMPATIBILITY here, the value will be set to
the default of null when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for DDF_COMPATIBILITY
to the CLIST default input members in the SDSNSAMP target
library. You need to add these entries to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
DDF_COMPATIBILITY CHARR M NONE NONE <x>
Change <x> to SP_PARMS_NJV if you specified
'DDF_COMPATIBILITY=SP_PARMS_NJV,' in step (2), above.
Otherwise, change <x> to NULL
If you do not add DDF_COMPATIBILITY to a DSNTIDxx
member, the DB2 installation CLIST will assume
'DDF_COMPATIBILITY=,' when run with that member as input.).
UK76806 HOLD DATA END
UK76808 HOLD DATA START
UK76808 HOLD DATA END
1UK76814 HOLD DATA START
UK76814 HOLD DATA END
UK76819 HOLD DATA START
++ HOLD(UK76819) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12065)
COMMENT
(***Action for PM55938:
See PM55938 APAR/PTF text for additional information about
why a REBIND is necessary.
PM55938 corrects a problem of choosing an inefficient access
path instead of a DPSI index access path for a query with an
EXISTS subquery.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76819 HOLD DATA END
UK76827 HOLD DATA START
UK76827 HOLD DATA END
UK76834 HOLD DATA START
UK76834 HOLD DATA END
UK76844 HOLD DATA START
UK76844 HOLD DATA END
UK76845 HOLD DATA START
UK76845 HOLD DATA END
UK76846 HOLD DATA START
UK76846 HOLD DATA END
UK76847 HOLD DATA START
UK76847 HOLD DATA END
UK76862 HOLD DATA START
UK76862 HOLD DATA END
UK76865 HOLD DATA START
UK76865 HOLD DATA END
UK76867 HOLD DATA START
1UK76867 HOLD DATA END
UK76870 HOLD DATA START
UK76870 HOLD DATA END
UK76912 HOLD DATA START
++ HOLD(UK75700) SYS FMID(HDBAA10) REASON(DOC) DATE(12068)
COMMENT
(***Documentation for PM52087:
Please see the PTF cover letter for more information.
This APAR/PTF changes the description for DB2 reason code
00D31030. The change will be documented in the DB2 for z/OS
Codes manual and in the Information Management Software for
z/OS Solutions Information Center.
The explanation for DB2 reason code '00D31030'X is updated to
include the following new bullet item:
. The SYSMODENAME column in the SYSIBM.LUNAMES table in the
communications database (CDB) is greater than 8 bytes.).
UK76912 HOLD DATA END
UK76936 HOLD DATA START
++ HOLD(UK76936) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12073)
COMMENT
(***Action for PM57492:
See PM57492 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57492 corrects an incorrect output problem where the join
predicate involves graphic data and there is a derived
predicate for inner table of a sort merge join.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK76936 HOLD DATA END
UK76938 HOLD DATA START
UK76938 HOLD DATA END
UK76959 HOLD DATA START
UK76959 HOLD DATA END
UK76961 HOLD DATA START
UK76961 HOLD DATA END
1UK76994 HOLD DATA START
UK76994 HOLD DATA END
UK76996 HOLD DATA START
UK76996 HOLD DATA END
UK76997 HOLD DATA START
UK76997 HOLD DATA END
UK76999 HOLD DATA START
UK76999 HOLD DATA END
UK77001 HOLD DATA START
UK77001 HOLD DATA END
UK77003 HOLD DATA START
++ HOLD(UK77003) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12072)
COMMENT
(***Action for PM55479:
See PM55479 APAR/PTF text for additional information about
why a REBIND is necessary.
PM55479 corrects a problem that DB2 incorrectly handles the
length of histogram statistics of a DECIMAL column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK74866) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12072)
COMMENT
(***Action for PM50516:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM50516 corrects a problem in which an incorrect compound
filter factor is computed when there is data skew and that
data skew is represented by frequency statistics.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK77003 HOLD DATA END
UK77005 HOLD DATA START
UK77005 HOLD DATA END
1
UK77007 HOLD DATA START
UK77007 HOLD DATA END
UK77031 HOLD DATA START
UK77031 HOLD DATA END
UK77038 HOLD DATA START
++ HOLD(UK76315) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076)
COMMENT
(***Action for PM54955:
See PM54955 APAR/PTF text for additional information about
why a REBIND is necessary.
PM54955 corrects a problem of incorrect output for a query that
references a scalar fullselect in its predicate and runs in
parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK77038) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076)
COMMENT
(***Action for PM54034:
See PM54034 APAR/PTF text for additional information about
why a REBIND is necessary.
PM54034 corrects a problem of incorrect output for an
SQL statement that references to an SQL inline table
user defined function multiple times with different
arguments and the SQL inline table user defined function
contains a common table expression.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK65976) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12076)
COMMENT
(***Action for PM30064:
See PM30064 APAR/PTF text for additional information about
why a REBIND is necessary.
PM30064 made an performance enhancement for a query satisfying
all of the following conditions:
1. The query contains host variables or parameter markers.
2. The query references a view or table expression which
contains UNION ALL and returns a LOB column.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK76977) SYS FMID(HDBAA10) REASON(ACTION) DATE(12076)
COMMENT
(After application of the PTF, the data length calculated of
CONCAT() function may be less than its previous DESCRIBE when
all of the following conditions are satisfied:
1. the type of one parameter of CONCAT() is GRAPHIC;
2. the other parameter of CONCAT() is scalar full-select, whose
type is also GRAPHIC.
Since there is no data in the extra length of CONCAT() prior to
applying this APAR, no problem would be caused after this APAR
is applied. If applications using DESCRIBE is impacted, proper
actions should be taken.
If the DSNTIAUL sample program is used correctly to generate a
LOAD utility control statement, then after application of this
PTF, the new control statement generated may not match the data
length of the CONCAT() function with scalar full-select from the
previous control statement. Proper action should be taken if
such mismatch is observed.).
UK77038 HOLD DATA END
UK77041 HOLD DATA START
UK77041 HOLD DATA END
UK77085 HOLD DATA START
UK77085 HOLD DATA END
UK77096 HOLD DATA START
UK77096 HOLD DATA END
UK77101 HOLD DATA START
UK77101 HOLD DATA END
UK77102 HOLD DATA START
UK77102 HOLD DATA END
UK77107 HOLD DATA START
UK77107 HOLD DATA END
UK77111 HOLD DATA START
UK77111 HOLD DATA END
1UK77113 HOLD DATA START
UK77113 HOLD DATA END
UK77157 HOLD DATA START
UK77157 HOLD DATA END
UK77170 HOLD DATA START
++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12079)
COMMENT
(See PM40724 APAR/PTF text for additional information about why
a REBIND is necessary. APAR PM38326 is the necessary
pre-conditioning apar for this APAR.
PM40724 corrects the problem of an SQLCODE -171 issued for a
query that references the STRIP built-in function containing
a single multi-byte mixed data strip-character.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(12079)
COMMENT
(PM40724 is an APAR that includes changes to support functional
extensions to the existing built-in functions and to introduce
a new built-in function that will be enabled once this APAR is
applied in DB2 NFM (New Function Mode).
Earlier, pre-conditioning APAR PM38326 was delivered.
In a data sharing group, the pre-conditioning APAR should be
applied to all members before applying this enabling APAR to any
member. The code change is enabled once this enabling APAR is
applied.
The functional extensions to the following existing built-in
functions are enabled by APAR PM40724.
1. LTRIM
2. RTRIM
3. REPLACE
4. ROUND
5. STRIP
6. TRUNCATE
The new built-in function called, TRIM, is introduced by APAR
PM40724. This APAR also corrects the problem of an SQLCODE
-171 issued for a query that references the STRIP built-in
function containing a single multi-byte mixed data
strip-character.).
++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(DOC) DATE(12079)
COMMENT
(See PM40724 APAR/PTF text for additional information.
PM40724 introduces the following changes to externals:
1
LTRIM
The LTRIM function removes bytes from the beginning of a string
expression based on the content of a trim expression.
>>--LTRIM--(--string-expression---+--------------------+-)-><
'-,--trim-expression-'
The LTRIM function removes all of the characters that are
contained in trim-expression from the beginning of
string-expression. The search is done by comparing the binary
representation of each character (which consists of one or more
bytes) in trim-expression to the bytes at the beginning of
string-expression. If the string-expression is defined as
FOR BIT DATA, the search is done by comparing each byte in
trim-expression to the byte at the beginning of
string-expression.
string-expression
An expression that specifies the source string. The argument
must be an expression that returns a value that is a built-in
string data type that is not a LOB, or a numeric data type. If
the value is not a string data type, it is implicitly cast
to VARCHAR before the function is evaluated.
If string-expression is not FOR BIT DATA, trim-expression must
not be FOR BIT DATA.
trim-expression
An expression that specifies the characters to remove from the
beginning of string-expression. The expression must return a
value that is a built-in string data type that is not a LOB, or
a numeric data type. If the value is not a string data type,
it is implicitly cast to VARCHAR before the function is
evaluated.
The default for trim-expression depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
1 a blank. If not EBCDIC, X'20' represents a blank.
string-expression and trim-expression must have compatible data
types. If string-expression and trim-expression have different
CCSID sets, trim-expression is converted to the CCSID of
string-expression.
The result of the function depends on the data type of
string-expression.
VARCHAR if string-expression is a character string. If
string-expression is defined as FOR BIT DATA the result
is FOR BIT DATA.
VARGRAPHIC if string-expression is a graphic string.
VARBINARY if string-expression is a binary string.
The length attribute of the result is the same as the length
attribute of string-expression.
The actual length of the result for a character or binary string
is the length of string-expression minus the number of bytes
that are removed. The actual length of the result for a graphic
string is the length (in the number of double byte characters)
of string-expression minus the number of double byte characters
removed. If all of the characters are removed, the result is an
empty string (the length is zero).
If any argument can be null, the result can be null; if any
argument is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Refer to LTRIM section in the DB2 10 for z/OS SQL Reference
for more information.
RTRIM
The RTRIM function removes bytes from the end of a string
expression based on the content of a trim expression.
>>--RTRIM--(--string-expression---+--------------------+-)-><
'-,--trim-expression-'
The RTRIM function removes all of the characters contained in
trim-expression from the end of string-expression.
The search is done by comparing the binary representation of
each character (which consists of one or more bytes) in
trim-expression to the bytes at the end of
string-expression. If the string-expression is defined as
FOR BIT DATA, the search is done by comparing each byte in
trim-expression to the byte at the end of string-expression.
1
string-expression
An expression that specifies the source string. The argument
must be an expression that returns a value that is a built-in
string data type that is not a LOB, or a numeric data type. If
the value is not a string data type, it is implicitly cast
to VARCHAR before the function is evaluated.
If string-expression is not FOR BIT DATA, trim-expression must
not be FOR BIT DATA.
trim-expression
An expression that specifies the characters to remove from the
end of string-expression. The expression must return a
value that is a built-in string data type that is not a LOB, or
a numeric data type. If the value is not a string data type,
it is implicitly cast to VARCHAR before the function is
evaluated.
The default for trim-expression depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
a blank. When not EBCDIC, X'20' represents a blank.
string-expression and trim-expression must have compatible data
types. If string-expression and trim-expression have different
CCSID sets, trim-expression is converted to the CCSID of
string-expression.
The result of the function depends on the data type of
string-expression.
VARCHAR if string-expression is a character string. If
string-expression is defined as FOR BIT DATA the result
is FOR BIT DATA.
VARGRAPHIC if string-expression is a graphic string.
VARBINARY if string-expression is a binary string.
The length attribute of the result is the same as the length
attribute of string-expression.
1
The actual length of the result for a character or binary string
is the length of string-expression minus the number of bytes
removed. The actual length of the result for a graphic
string is the length (in number of double byte characters) of
string-expression minus the number of double byte characters
removed. If all of the characters are removed, the result is an
empty string (the length is zero).
If any argument can be null, the result can be null; if any
argument is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Refer to RTRIM section in the DB2 10 for z/OS SQL Reference
for more information.
REPLACE
>>-REPLACE-(-source-string-,-search-string-+-----------------+->
',-replace-string-'
>-)-><
replace-string
An expression that specifies the replacement string. The
expression must return a value that is a built-in character
string, graphic string, or binary string data type that is not
a LOB.
The argument can also be a numeric data type. The numeric
argument is implicitly cast to a VARCHAR data type.
If replace-string is not specified or is an empty string,
nothing replaces the string that is removed from the source
string.
Refer to REPLACE section in the DB2 10 for z/OS SQL Reference
for more information.
ROUND
.-,--0-------------------.
>>-ROUND-(--numeric-expression-1-+------------------------+-)-><
'-,-numeric-expression-2-'
Refer to ROUND section in the DB2 10 for z/OS SQL Reference
for more information.
TRUNCATE or TRUNC
.-,--0------------------.
>>-+TRUNCATE-+-(-numeric-expression1-+-----------------------+->
'-TRUNC---' '-,-numeric-expression2-'
1
>-)-><
Refer to TRUNCATE section in the DB2 10 for z/OS SQL Reference
for more information.
STRIP
The STRIP function is similar to the TRIM scalar function.
Refer to TRIM section in the DB2 10 for z/OS SQL Reference
for more information.
TRIM
The TRIM function removes bytes from the beginning, from the
end, or from both the beginning and end of a string expression.
>>--TRIM--(--+----------------------------------------+-->
| .-BOTH-----. |
'-+----------+--+----------------+--FROM-'
|-B--------| '-trim-constant--'
|-LEADING--|
|-L--------|
|-TRAILING-|
'-T--------'
>--string-expression---)--------------------------------><
The schema is SYSIBM.
The first argument, if specified, indicates whether characters
are removed from the end or the beginning of the string. If the
first argument is not specified, the characters are removed from
both the end and the beginning of the string.
trim-constant
Specifies a constant that indicates the binary, SBCS, or DBCS
character that is to be removed. If string-expression is a
character string, trim-constant must be an SBCS or DBCS
single-character (2 bytes) constant. If string-expression is a
binary string, trim-constant must be a single-byte binary string
constant. If string-expression is a DBCS graphic or DBCS-only
string, trim-constant must be a graphic constant that consists
of a single DBCS character.
The default for trim-constant depends on the data type of
string-expression:
A DBCS blank if string-expression is a DBCS graphic string.
For ASCII, the CCSID determines the hex value that
represents a DBCS blank. For example, for Japanese
(CCSID 301), X'8140' represents a DBCS while for
1 Simplified Chinese, X'A1A1' represents a DBCS blank. For
EBCDIC, X'4040' represents a DBCS blank.
A UTF-16 or UCS-2 blank (X'0020') if string-expression is a
Unicode graphic string.
A value of X'00' if string-expression is a binary string.
Otherwise, a single byte blank. For EBCDIC, X'40' represents
a blank. When not EBCDIC, X'20' represents a blank.
string-expression
An expression that returns a value that is a built-in character
string data type, graphic data type, binary string data type, or
numeric data type. string-expression must not be a LOB.
If string-expression is numeric, it is cast to a character
string before the function is evaluated. For more information
about converting numeric to a character string, see VARCHAR.
string-expression and trim-expression must have compatible data
types.
The data type of the result depends on the data type of
string-expression:
If string-expression is a character string data type, the
result is VARCHAR. If string-expression is defined as
FOR BIT DATA the result is FOR BIT DATA.
If string-expression is a graphic string data type, the
result is VARGRAPHIC.
If string-expression is a binary string data type, the
result is VARBINARY.
The length attribute of the result is the same as the length
attribute string-expression. The actual length of the result is
the length of string-expression minus the number of characters
removed. If all of the characters are removed, the result is
an empty string.
If string-expression can be null, the result can be null; if
string-expression is null, the result is the null value.
The CCSID of the result is the same as that of string-expression
Example: Assume the host variable HELLO of type CHAR(9) has a
value of 'Hello '.
SELECT TRIM(:HELLO), TRIM(TRAILING FROM :HELLO)
FROM SYSIBM.SYSDUMMY1
Results in 'Hello' and ' Hello' respectively.
1 Example: Assume the host variable BALANCE of type CHAR(9) has a
value of '000345.50'.
SELECT TRIM(L '0' FROM :BALANCE)
FROM SYSIBM.SYSDUMMY1
Results in '345.50'
Refer to TRIM section in the DB2 10 for z/OS SQL Reference.).
++ HOLD(UK77170) SYS FMID(HDBAA10) REASON(ACTION) DATE(12079)
COMMENT
(This PTF corrects the problem of an SQLCODE -171 issued for a
query that references the STRIP built-in function containing a
single multi-byte mixed data strip-character.
If after applying both apars PM38326 and PM40724, the failing
query still returns an SQLCODE -171 or for a static query a
rebind does not resolve the problem, one or more of the
following actions may need to be performed depending on the
makeup of the query.
1. Views.
Regenerate views using the ALTER VIEW REGENERATE statement.
2. Materialized query tables (MQT).
Drop and recreate the MQTs.
3. SQL table UDFs.
Drop and recreate the UDFs.
4. SQL scalar UDFs.
Regenerate functions using the ALTER FUNCTION REGENERATE.
statement.
5. SQL native procedures.
Regenerate procedures using the ALTER PROCEDURE REGENERATE
statement.
6. Row permissions and column masks.
Regenerate using the ALTER PERMISSION REGENERATE or
ALTER MASK REGENERATE statement.
7. Indexes with key expressions.
Regenerate indexes using the ALTER INDEX REGENERATE
statement.).
UK77170 HOLD DATA END
UK77195 HOLD DATA START
1UK77195 HOLD DATA END
UK77197 HOLD DATA START
UK77197 HOLD DATA END
UK77206 HOLD DATA START
UK77206 HOLD DATA END
UK77229 HOLD DATA START
UK77229 HOLD DATA END
UK77248 HOLD DATA START
++ HOLD(UK77248) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12085)
COMMENT
(***Action for PM56084:
See PM56084 APAR/PTF text for additional information about
why a REBIND is necessary.
Please note that the second problem addressed by PM56084 is
required to have the static application rebound.
Incorrect output can occur when a not NULL XML column is
fetched.
DB2 does not set the nullability information properly
at bind time which leads to an incorrect value written
for the NULL byte when retrieving a not NULL XML column
for the JCC Type 2 Driver with Limited Block Fetch.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK69995) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12085)
COMMENT
(***Action for PM38688:
See PM38688 APAR/PTF text for additional information about
why a REBIND is necessary.
PM38688 corrects a problem of incorrect out when query contains
EXCEPT and UNION
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK77248 HOLD DATA END
UK77249 HOLD DATA START
1UK77249 HOLD DATA END
UK77338 HOLD DATA START
UK77338 HOLD DATA END
UK77339 HOLD DATA START
UK77339 HOLD DATA END
UK77366 HOLD DATA START
UK77366 HOLD DATA END
UK77367 HOLD DATA START
UK77367 HOLD DATA END
UK77376 HOLD DATA START
UK77376 HOLD DATA END
UK77380 HOLD DATA START
UK77380 HOLD DATA END
UK77407 HOLD DATA START
UK77407 HOLD DATA END
UK77410 HOLD DATA START
UK77410 HOLD DATA END
UK77426 HOLD DATA START
++ HOLD(UK77426) SYS FMID(HDBAA10) REASON(ACTION) DATE(12087)
COMMENT
(***Action for PM57630:
PM57630 corrects a problem where SQLCODE -331 is issued
incorrectly when translating characters from CCSID 367 to
CCSID 937.
DB2 code has been changed to invoke Unicode services instead of
the conversion procedure DSNXVTWC when translating
characters from CCSID 367 to CCSID 937. DB2 code will ignore
the row for this translation in SYSIBM.SYSSTRINGS.
After applying this PTF the following three characters will be
translated differently.
SM060000 Ý '5B'x
SM080000 ¨ '5D'x
SD150000 ¬ '5E'x
1 Prior to applying this PTF, the DSNXVWTC proc is called and the
characters '5B'x, '5D'x, and '5E'x are translated to '4A'x,
'6A'x, and '5F'x respectively.
After applying this PTF, Unicode services is called and the
characters '5B'x, '5D'x, and '5E'x are translated to 'BA'x,
'BB'x, and 'B0'x respectively. All other characters are
translated the same by DSNXVTWC and Unicode services.
The following is a table to help illustrate the changes:
-----------------------------------------------------------
|GCGID |character| CCSID | CCSID 937 | CCSID 937 |
| | | 367 | (by DSNXVWTC) | by UCS |
-----------------------------------------------------------
|SM060000 | Ý | '5B'x | '4A'x |'BA'x |
-----------------------------------------------------------
|SM080000 | ¨ | '5D'x | '6A'x |'BB'x |
-----------------------------------------------------------
|SD150000 | ¬ | '5E'x | '5F'x |'B0'x |
-----------------------------------------------------------
If you have any applications that depend on these translated
values they may need to be modified to handle the correct
values.
See PM57630 APAR/PTF text for additional information.).
UK77426 HOLD DATA END
UK77430 HOLD DATA START
UK77430 HOLD DATA END
UK77451 HOLD DATA START
UK77451 HOLD DATA END
UK77481 HOLD DATA START
++ HOLD(UK77481) SYS FMID(HIZAA10) REASON(ACTION) DATE(12090)
COMMENT
(This PTF requires either an ERLY code refresh or a re-IPL of
zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
the PTF.).
UK77481 HOLD DATA END
UK77500 HOLD DATA START
1++ HOLD(UK77500) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12090)
COMMENT
(***Action for PM56845:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM56845 allows you to specify whether, for queries
that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access
paths that require sort when there exists at least one access
path that avoids sort.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK77500) SYS FMID(HDBAA10) REASON(ACTION) DATE(12090)
COMMENT
(***Action for PM56845:
This PTF adds a new DB2 subsystem parameter in DSN6SPRM named
OPT1ROWBLOCKSORT that allows you to specify whether, for queries
that specify OPTIMIZE FOR 1 ROW, DB2 is to block all access
paths that require sort when there exists at least one access
path that avoids sort. Valid options are:
* ENABLE : When OPTIMIZE FOR 1 ROW is used with a query, DB2
will disable sort access paths when a no-sort choice
is available.
* DISABLE: DB2 will strongly discourage sort access paths and is
unlikely to choose sort access paths, but there will
be a chance a sort access path can win. This is the
behavior which was present in DB2 9 and prior
releases.
==> This is the default setting
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
1 ----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter OPT1ROWBLOCKSORT=<x>,
where <x> is DISABLE or ENABLE, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
OPT1ROWBLOCKSORT here, the value will be set to the
default of DISABLE when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for OPT1ROWBLOCKSORT to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library.
You need to add these entries to all private copies of your
CLIST output DSNTIDxx member. In each such copy, add the
following lines:
OPT1ROWBLOCKSORT CHAR G DISABLE ENABLE <x>
Change <x> to the value you specified for
OPT1ROWBLOCKSORT in step (2), above.
If you do not add OPT1ROWBLOCKSORT to a DSNTIDxx
member, the DB2 installation CLIST will assume
OPT1ROWBLOCKSORT=DISABLE when run with that member
as input.).
UK77500 HOLD DATA END
UK77506 HOLD DATA START
UK77506 HOLD DATA END
UK77518 HOLD DATA START
UK77518 HOLD DATA END
UK77548 HOLD DATA START
UK77548 HOLD DATA END
1
UK77556 HOLD DATA START
UK77556 HOLD DATA END
UK77572 HOLD DATA START
UK77572 HOLD DATA END
UK77584 HOLD DATA START
UK77584 HOLD DATA END
UK77633 HOLD DATA START
UK77633 HOLD DATA END
UK77636 HOLD DATA START
UK77636 HOLD DATA END
UK77652 HOLD DATA START
UK77652 HOLD DATA END
UK77666 HOLD DATA START
UK77666 HOLD DATA END
UK77693 HOLD DATA START
++ HOLD(UK74927) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12095)
COMMENT
(See PM52694 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
PM52694 fixes a query costing problem when the query has outer
join and FETCH FIRST n ROWS ONLY or OPTIMIZE FOR n ROWS.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK77693 HOLD DATA END
UK77699 HOLD DATA START
UK77699 HOLD DATA END
UK77733 HOLD DATA START
UK77733 HOLD DATA END
UK77737 HOLD DATA START
UK77737 HOLD DATA END
1
UK77739 HOLD DATA START
UK77739 HOLD DATA END
UK77743 HOLD DATA START
++ HOLD(UK77743) SYS FMID(HDBAA10) REASON(ACTION) DATE(12100)
COMMENT
(The PTF for APAR PM59401 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
UK77743 HOLD DATA END
UK77745 HOLD DATA START
++ HOLD(UK77745) SYS FMID(HDBAA10) REASON(ACTION) DATE(12102)
COMMENT
(*** Action for PM59280 ***
This fix corrects a SQLCODE104 symptom observed at the server
site (site2), but to correct the problem this fix must be
applied to the DB2 for z/OS requester site (site1) where
alias resolution is enabled.
Review the PTF cover letter for further explanation of
the requester (site1) applications that are affected.).
UK77745 HOLD DATA END
UK77769 HOLD DATA START
UK77769 HOLD DATA END
UK77778 HOLD DATA START
UK77778 HOLD DATA END
UK77822 HOLD DATA START
UK77822 HOLD DATA END
UK77835 HOLD DATA START
UK77835 HOLD DATA END
UK77843 HOLD DATA START
1++ HOLD(UK77843) SYS FMID(HDBAA10) REASON(ACTION) DATE(12101)
COMMENT
(***Action for PM56690:
See PM56690 APAR/PTF text for additional information.
PM56690 changes the output in SYSREC for UNLOAD DATE column to
TIMESTAMP EXTERNAL with no length specified from 19 byte
timestamp to 26 byte timestamp; with length specified equal to
26, the output is changed from 19 byte timestamp plus 7 padding
blanks to 26 byte timestamp.
New applications or procedures developed on DB2 10 for z/OS
using the UNLOAD output may be affected by this modification and
may need to be changed accordingly.).
UK77843 HOLD DATA END
UK77844 HOLD DATA START
UK77844 HOLD DATA END
UK77857 HOLD DATA START
UK77857 HOLD DATA END
UK77877 HOLD DATA START
UK77877 HOLD DATA END
UK77885 HOLD DATA START
UK77885 HOLD DATA END
UK77887 HOLD DATA START
UK77887 HOLD DATA END
UK77907 HOLD DATA START
UK77907 HOLD DATA END
UK77919 HOLD DATA START
++ HOLD(UK76492) SYS FMID(HDBAA10) REASON(ACTION) DATE(12103)
COMMENT
(APAR PM54727 has corrected an issue where REORG REBALANCE on a
partitioned table space with an editproc defined can result in
corrupted limit key values in the DB2 catalog and directory.
In the event that the above limit key corruption has occurred,
user can repair the catalog/directory by manually altering the
limit keys to the correct value on the affected table space /
partitions, and then run a REORG TABLESPACE utility to remove
the restrictive REORP status.).
UK77919 HOLD DATA END
1
UK77920 HOLD DATA START
++ HOLD(UK77920) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12104)
COMMENT
(***Action for PM52237
See PM52237 APAR/PTF text for additional information about
why a REBIND is necessary.
Apar PM52237 reduces the XML storage usage so as not to exceed
the specified zparm limit. As a result, this will reduce the
chance of receiving an SQLCODE904 (or SQLCODE -904), a Resource
Unavailable condition with reason code rc00D50001 or rc00D50002,
which means excessive storage used for XMLTABLE.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK77920 HOLD DATA END
UK77942 HOLD DATA START
UK77942 HOLD DATA END
UK77953 HOLD DATA START
UK77953 HOLD DATA END
UK77956 HOLD DATA START
UK77956 HOLD DATA END
UK77963 HOLD DATA START
UK77963 HOLD DATA END
UK77992 HOLD DATA START
UK77992 HOLD DATA END
UK77996 HOLD DATA START
UK77996 HOLD DATA END
UK77997 HOLD DATA START
++ HOLD(UK77997) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12111)
COMMENT
(***Action for PM57745:
See PM57745 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57745 corrects a problem that storage overlay could happen
for an SQL statement that returns data in the type of DBCLOB.
1
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK77997 HOLD DATA END
UK78003 HOLD DATA START
UK78003 HOLD DATA END
UK78004 HOLD DATA START
++ HOLD(UK78004) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107)
COMMENT
(***Action for PM57420:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PM57420 corrects a problem where lock avoidance is being
used for a singleton, non-cursor SELECT when ISOLATION(CS)
is used with CURRENTDATA(YES). Concurrent updates may yield
inconsistent results for the SELECT.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK77847) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107)
COMMENT
(***Action for PM56626:
See PM56626 APAR/PTF text for additional information about
why a REBIND is necessary.
PM56626 allows users to define a dynamic scroll cursor whose
SELECT statment contains a subquery such that the base object
of the outer subselect, and of the subquery, is the same, but
with the conditions that (1) FOR FETCH ONLY is specified in
the SELECT statement, and (2) the base object is accessed via
the index to avoid any sort or materialization.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK75154) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107)
COMMENT
(***Action for PM51623:
A rebind is necessary to rebuild package and/or plan structures
based on the changes in this APAR.
PM51623 corrects a problem that an inefficient access path may
be chosen for a DELETE statement against a VIEW on which an
1 INSTEAD OF DELETE trigger is defined.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK65223) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12107)
COMMENT
(***Action for PM30690:
See PM30690 APAR/PTF text for additional information about
why a REBIND is necessary.
PM30690 corrects a problem of an infinite loop for a MERGE
statement with update.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK78004 HOLD DATA END
UK78007 HOLD DATA START
UK78007 HOLD DATA END
UK78030 HOLD DATA START
UK78030 HOLD DATA END
UK78100 HOLD DATA START
UK78100 HOLD DATA END
UK78109 HOLD DATA START
UK78109 HOLD DATA END
UK78112 HOLD DATA START
UK78112 HOLD DATA END
UK78130 HOLD DATA START
UK78130 HOLD DATA END
UK78134 HOLD DATA START
UK78134 HOLD DATA END
UK78166 HOLD DATA START
UK78166 HOLD DATA END
UK78170 HOLD DATA START
1++ HOLD(UK76577) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111)
COMMENT
(Please note. If you are using DATE exits, this concerns you.
If you are using a DATE exit, specifically an EBCDIC, ASCII, or
UNICODE DATE exit (DSNXVDTX, DSNXVDTA, or DSNXVDTU), please make
sure it is functioning properly. If it is, a query referencing
the TIMESTAMP built-in function should work correctly and no
action is necessary. If however the exit is not working
properly and the query referencing the TIMESTAMP built-in
function worked in DB2 9 but is now not working in DB2 10 (i.e.
it does not return the expected result), then please ensure that
the exit is coded and working properly.).
++ HOLD(UK74371) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111)
COMMENT
(The following behavior difference may be noticed with the
application of this apar.
Please note that this apar corrects an instance where an
incorrect SQLCODE180 could be issued. Instead, an SQLCODE181
should be issued. So, any static applications that check for an
SQLCODE180 (or -180) should also be checking for an SQLCODE181
(or -181).).
UK78170 HOLD DATA END
UK78176 HOLD DATA START
++ HOLD(UK78176) SYS FMID(HDBAA10) REASON(ACTION) DATE(12111)
COMMENT
(Applying this apar will not fix the package which is already
broken. The customer can run the following query to find all
native stored procedures and ALTER REGENERATE these procedures
can correct the broken package.
SELECT * FROM SYSIBM.SYSPACKAGE WHERE PLANMGMT NOT IN ('E','B')
AND APREUSE NOT IN ('N',' ') AND (TYPE='N' OR TYPE='F')).
UK78176 HOLD DATA END
UK78180 HOLD DATA START
++ HOLD(UK78180) SYS FMID(HDBAA10) REASON(DOC) DATE(12117)
COMMENT
(PM58294 introduces the following changes to the DB2 10 for z/OS
Utility Guide and Reference:
Changed option for utility REORG:
DISCARD
Specifies that records that meet the specified WHEN conditions
are to be discarded during REORG TABLESPACE UNLOAD CONTINUE or
UNLOAD PAUSE. If you specify DISCARDDN or a SYSDISC DD
statement in the JCL, discarded records are saved in the
| associated data set. Otherwise, the utility discards records
| without saving them in a data set.
You can specify any SHRLEVEL option with DISCARD; however, if
you specify SHRLEVEL CHANGE, modifications that are made
1 during the reorganization to data rows that match the discard
criteria are not permitted. In this case, REORG TABLESPACE
terminates with an error.
If you specify DISCARD, rows are decompressed and edit
routines are decoded. If you also specify DISCARD to a file,
rows are decoded by field procedure, and the following columns
are converted to DB2 external format:
(1)SMALLINT
(2)INTEGER
(3)FLOAT
(4)DECIMAL
(5)TIME
(6)TIMESTAMP
Otherwise, edit routines or field procedures are bypassed on
both the UNLOAD and RELOAD phases for table spaces. Validation
procedures are not invoked during either phase.
Do not specify DISCARD with the UNLOAD EXTERNAL or UNLOAD ONLY
option.
| You cannot specify DISCARD for a base table with LOB columns
| unless the discard records are less than 32k or you want to
| discard records without saving them in a data set.
You cannot specify DISCARD for a base table with XML columns
or for an XML table space.
REORG TABLESPACE DISCARD cannot be specified on a
system-maintained temporal table space when versioning is
active. When versioning is active and DISCARD is specified,
REORG TABLESPACE fails with message DSNU076I and return code
8.).
++ HOLD(UK78180) SYS FMID(HDBAA10) REASON(ACTION) DATE(12117)
COMMENT
(The PTF for APAR PM58294 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
UK78180 HOLD DATA END
UK78202 HOLD DATA START
UK78202 HOLD DATA END
UK78206 HOLD DATA START
1UK78206 HOLD DATA END
UK78211 HOLD DATA START
UK78211 HOLD DATA END
UK78230 HOLD DATA START
++ HOLD(UK78230) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12115)
COMMENT
(The PTF for PM60499 is a companion fix and requires the fix
for APAR PM55051 for FMID HDBAA10 to be applied.).
UK78230 HOLD DATA END
UK78235 HOLD DATA START
UK78235 HOLD DATA END
UK78247 HOLD DATA START
UK78247 HOLD DATA END
UK78277 HOLD DATA START
UK78277 HOLD DATA END
UK78286 HOLD DATA START
UK78286 HOLD DATA END
UK78307 HOLD DATA START
UK78307 HOLD DATA END
UK78358 HOLD DATA START
UK78358 HOLD DATA END
UK78390 HOLD DATA START
UK78390 HOLD DATA END
UK78404 HOLD DATA START
UK78404 HOLD DATA END
UK78406 HOLD DATA START
UK78406 HOLD DATA END
UK78414 HOLD DATA START
UK78414 HOLD DATA END
UK78418 HOLD DATA START
1++ HOLD(UK78418) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12122)
COMMENT
(***Action for PM58322:
See PM58322 APAR/PTF text for additional information about
why a REBIND is necessary.
PM58322 corrects a problem of missing a negative SQLCODE
on the insert or delete operation in the statements such
as INSERT, DELETE, MERGE, or SELECT FROM those where the
object table references a view and the view definition
references a DB2 directory table such as SYSLGRNX.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK78418 HOLD DATA END
UK78426 HOLD DATA START
UK78426 HOLD DATA END
UK78449 HOLD DATA START
UK78449 HOLD DATA END
UK78472 HOLD DATA START
UK78472 HOLD DATA END
UK78476 HOLD DATA START
UK78476 HOLD DATA END
UK78514 HOLD DATA START
++ HOLD(UK78514) SYS FMID(HDBAA10) REASON(ACTION) DATE(12125)
COMMENT
(***Action for PM53243 (V10):
For users who are interested in exploiting the functions
provided via this PTF, the following actions need to be
considered:
* For a CALL statement to a DB2 for z/OS Stored Procedure, the
Stored Procedure name can be identified via a literal or by
using a host variable or parameter marker. When using a
literal for the stored procedure name, and in order to
benefit from the enhancement that provides a valid routine ID
in various IFCID records, the packages that contain the CALL
statement must be rebound after this PTF is applied.
* For an SQL statement that invokes a DB2 for z/OS User-Defined
Function, and in order to benefit from the enhancement to
provide a valid routine ID in various IFCID records, the
packages that contain the SQL statement must be rebound after
this PTF is applied.
1 * The mapping of IFCID233 remains compatible with prior
versions and no immediate change is required. However,
applications that parse this record will need to be changed
in order to exploit the new fields.).
UK78514 HOLD DATA END
UK78526 HOLD DATA START
++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(12125)
COMMENT
(***Action for PM58951
____________________________________________________________
This PTF contains a fix for a defect in the SQLJ translator.
Incorrect code was generated for an SQL SELECT INTO statement
using a common table expression specified with the "WITH"
keyword. To make this fix effective for any impacted SQLJ
program, after applying the APAR, you must re-translate the
SQLJ program, then you must run the SQLJ Binder (db2sqljbind)
again on the affected profiles and rebind the profiles.
See PM58951 APAR/PTF text in the PTF cover letter for
further information about this problem. Reference entry
with (wsdbu01043533) identifier.).
UK78526 HOLD DATA END
UK78529 HOLD DATA START
++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(12126)
COMMENT
(***Action for PM58952
____________________________________________________________
This PTF contains a fix for a defect in the SQLJ translator.
Incorrect code was generated for an SQL SELECT INTO statement
using a common table expression specified with the "WITH"
keyword. To make this fix effective for any impacted SQLJ
program, after applying the APAR, you must re-translate the
SQLJ program, then you must run the SQLJ Binder (db2sqljbind)
again on the affected profiles and rebind the profiles.
See PM58952 APAR/PTF text in the PTF cover letter for
further information about this problem. Reference entry
with (wsdbu01043533) identifier.).
UK78529 HOLD DATA END
UK78575 HOLD DATA START
UK78575 HOLD DATA END
UK78581 HOLD DATA START
++ HOLD(UK75209) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129)
COMMENT
(***Action for PM51654:
1 See PM51654 APAR/PTF text for additional information about
why a REBIND is necessary.
PM51654 corrects a problem when incorrect output could happen
for a complex SQL statement or view with an outer join and a
correlated sub-query.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK73620) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129)
COMMENT
(***Action for PM47058:
See PM47058 APAR/PTF text for additional information about
why a REBIND is necessary.
PM47058 corrects a problem of incorrect output when an SQL
statement satisfies all of the following conditions:
1. table expression with sideway reference is defined in this
SQL statement;
2. LEFT OUTER JOIN is involved in this SQL statement;
3. CPU parallelism setting is enabled.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK71528) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12129)
COMMENT
(***Action for PM41296:
See PM41296 APAR/PTF text for additional information about
why a REBIND is necessary.
PM41296 corrects a problem of an SQL statement which defines a
table expression one the preserved side of LEFT OUTER JOIN, and
a CASE statement or non-column expression is defined in the
SELECT list of the table expression and is referenced in the SQL
statement.
Performance may regress when a SQL statement satisfies all of
the following conditions:
1. OUTER JOIN is contained, and the preserved side is defined
with table expression;
2. a CASE statement or non-column expression is defined in the
SELECT list of the above table expression;
3. a table expression column which corresponds to the CASE
statement or non-column expression from condition #2 is
referenced in predicate of the SQL statement.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
1 letter to determine which, if any, applications could be
affected by this change.).
++ HOLD(UK78581) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(12129)
COMMENT
(***Action for PM55928:
PM55928 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via another APAR
PM56631. At this time, all of the changes are transparent to the
user. In a data sharing group, this pre-conditioning APAR should
be applied to all members before the later enabling APAR PM56631
is applied to any member. The new function is not enabled until
the enabling APAR PM56631 is applied.
If the new function will not be used, then there is no need to
take precautions for rolling through the pre-conditioning PTF
ahead of the enabling PTF. Instead, both pre-conditioning PTF
and enabling PTF can be rolled through together.
In addition, because the new function can only be used in DB2 10
New Function Mode (NFM), both pre-conditioning PTF and enabling
PTF can be rolled through together on DB2 10 CM subsystems.).
UK78581 HOLD DATA END
UK78606 HOLD DATA START
UK78606 HOLD DATA END
UK78609 HOLD DATA START
UK78609 HOLD DATA END
UK78632 HOLD DATA START
++ HOLD(UK78632) SYS FMID(HDBAA10) REASON(ACTION) DATE(12130)
COMMENT
(The PTF for APAR PM57632 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the function the PTF
addresses will not be enabled.
The fix for APAR PM57632 is a companion fix. It requires the
fix for APAR PM60438, for FMID JDBAA1K to be applied.).
UK78632 HOLD DATA END
UK78633 HOLD DATA START
++ HOLD(UK78633) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12130)
1 COMMENT
(The fix for APAR PM60438 is a companion fix. It requires the
fix for APAR PM57632, for FMID HDBAA10 to be applied.).
++ HOLD(UK71420) SYS FMID(JDBAA1K) REASON(ACTION) DATE(12130)
COMMENT
(The fix for APAR PM42560 is a companion fix. It requires the
fix for APAR PM27962, for FMID HDBAA10 to be applied.).
UK78633 HOLD DATA END
UK78678 HOLD DATA START
UK78678 HOLD DATA END
UK78700 HOLD DATA START
++ HOLD(UK78700) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12132)
COMMENT
(***Action for PM60533:
See PM60533 APAR/PTF text for additional information about
why a REBIND is recommended.
After you apply this PTF, some applications might experience
performance degradation. To improve the performance of those
applications, rebind their plans and packages.
Review the PTF cover letter to determine which, if any,
applications could be affected by this change.).
UK78700 HOLD DATA END
UK78722 HOLD DATA START
UK78722 HOLD DATA END
UK78723 HOLD DATA START
UK78723 HOLD DATA END
UK78782 HOLD DATA START
UK78782 HOLD DATA END
UK78785 HOLD DATA START
++ HOLD(UK78522) SYS FMID(HDBAA10) REASON(DOC) DATE(12137)
COMMENT
(PM57001 introduces the following changes to externals and the
approximate text will be added to the V10 DB2 SQL Reference.
This text is subject to change.
Changed option for ALTER TABLESPACE MAXPARTITIONS:
Specifies that the table space is partition-by-growth. integer
specifies the maximum number of partitions to which the table
| space can grow or shrink. integer must be in the range of 1 to
4096, depending on the value that is in effect for DSSIZE and
the page size of the table space, and must not be less than
1 | the number of physical partitions already allocated for the
table space. See CREATE TABLESPACE for more information about
how DSSIZE and the page size are related.
Information about this changed option will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.).
UK78785 HOLD DATA END
UK78787 HOLD DATA START
UK78787 HOLD DATA END
UK78788 HOLD DATA START
++ HOLD(UK78788) SYS FMID(HDBAA10) REASON(DOC) DATE(12137)
COMMENT
(PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE
is specified with OBID 1. The approximate text will be
updated in the DB2 SQL Reference and Codes manual. This text
is subject to change.
=============
SQL Reference
=============
CREATE TABLE->OBID integer
Identifies the OBID to be used for this table. An OBID is
the identifier for an object's internal descriptor. The
| integer must be greater than 1 and not identify an existing
or previously used OBID of the database. If you omit OBID,
DB2 generates a value.
=====
Codes
=====
-736
The specified OBID does not fall within the acceptable range
| for OBIDs, which is 2 to 32767.).
++ HOLD(UK78788) SYS FMID(HDBAA10) REASON(ACTION) DATE(12137)
COMMENT
(PM61532 modifies DB2 to issue SQLCODE -736 when CREATE TABLE
is specified with OBID 1. Existing tables with OBID 1 should
be dropped and recreated with a different OBID.
A query, such as the sample query below may be used to
identify tables with OBID 1.
SELECT * FROM SYSIBM.SYSTABLES
WHERE OBID = 1
AND ( TYPE = 'T'
OR TYPE = 'M'
OR TYPE = 'H' ) ;).
UK78788 HOLD DATA END
1UK78834 HOLD DATA START
UK78834 HOLD DATA END
UK78883 HOLD DATA START
UK78883 HOLD DATA END
UK78929 HOLD DATA START
UK78929 HOLD DATA END
UK79001 HOLD DATA START
++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(DOC) DATE(12144)
COMMENT
(This PTF introduces the following changes to DB2 ODBC externals:
New DB2 ODBC for z/OS initialization keywords described as
follows.
LIMITEDBLOCKFETCH = 0 | 1
This keyword is a performance optimization keyword that
specifies whether DB2 ODBC is to attempt limited block fetch
when fetching result sets from the connected data source.
0 = Limited block fetch is not used. 0 is the default.
1 = DB2 ODBC attempts to use limited block fetch. If blocking
is supported at the server for the result set that is
being fetched, DB2 ODBC retrieves as many rows as it can
fit in a query data block in a single fetch request.
QUERYDATASIZE = integer
This keyword specifies the amount of query data, in bytes, that
DB2 returns on each FETCH operation when limited block fetch is
enabled. The default value is 32767. Possible values are:
32767 294911 557055 819199
65535 327679 589823 851967
98303 360447 622591 884735
131071 393215 655359 917503
163839 425983 688127 950271
196607 458751 720895 983039
229375 491519 753663 1015807
262143 524287 786431 1048575
If you specify a value that is not a valid value, DB2 ODBC sets
QUERYDATASIZE to the nearest valid value.
Information about the new DB2 ODBC initialization keywords
and DB2 ODBC limited block fetch will be included in the
Information Management Software for z/OS Solutions Information
Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
later date.).
++ HOLD(UK71561) SYS FMID(JDBAA17) REASON(DOC) DATE(12144)
COMMENT
(*** Documentation for PM25678 (Version 10)
A new initialization keyword, INTERRUPT, has been added to allow
you to specify the interrupt processing mode when SQLCancel()
is called to cancel the processing on a statement.
1
Complete documentation for the SQLCancel() API will be provided
in the DB2 10 for z/OS ODBC Guide and Reference and in the
Information Management Software for z/OS Solutions Information
Center.).
++ HOLD(UK67822) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144)
COMMENT
(*** Action for PM32032 (Version 10)
The following database request module (DBRM) is updated by
this PTF:
DSNCLIQR
Application of this PTF requires a BIND PACKAGE for the above
package. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.).
++ HOLD(UK72803) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144)
COMMENT
(The following database request modules (DBRMs) are updated by
this PTF:
DSNCLINF
DSNCLIC1
DSNCLIMS
DSNCLIQR
DSNCLIV1 (DB2 for Linux, UNIX, and Windows servers only)
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 CLI bind job DSNTIJCL in the
SDSNSAMP data set for an example of how to perform the
BIND command. Also, refer to the prolog of DSNTIJCL
for specific instructions on how to bind each DBRM and
on how to customize the DSNTIJCL job for use at your site.
This PTF introduces two new DB2 ODBC initialization keywords
LIMITEDBLOCKFETCH and QUERYDATASIZE, to enable limited block
fetch. Limited block fetch is a performance optimization that
enables applications to improve the performance of FETCH
operations when connected to a local DB2 for z/OS server.
If limited block fetch is not desired, no further action is
necessary other than rebinding the DBRMs listed above;
otherwise please note the following.
When you enable limited block fetch, the data that is returned
to your application might not reflect the data that has been
committed to the source table. If your application fetches
data from tables that are updated by other users, or if your
application uses savepoints and issues ROLLBACK TO SAVEPOINT
to manage transactions, you should disable limited block fetch.).
1++ HOLD(UK60517) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144)
COMMENT
(
This PTF updates DB2 ODBC for z/OS database request module
(DBRM) DSNCLIC1.
After you apply this PTF, you need to run the BIND PACKAGE
command to recreate the package for DSNCLIC1. Failure to bind
the required package could result in SQLCODE -805 at application
run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
prefix.SDSNSAMP data set for an example of how to perform the
BIND command.).
++ HOLD(UK56516) SYS FMID(JDBAA17) REASON(ACTION) DATE(12144)
COMMENT
(The following database request modules (DBRMs) for ODBC
DB2 for z/OS are updated by this PTF:
DSNCLIMS
DSNCLIC1
Application of this PTF requires a BIND PACKAGE for the above
packages. Failure to rebind the required packages could result
in SQLCODE=-805 at application run time.
Refer to the sample DB2 ODBC bind job DSNTIJCL in the
SDSNSAMP dataset for an example of how to perform the
BIND command.).
UK79001 HOLD DATA END
UK79004 HOLD DATA START
UK79004 HOLD DATA END
UK79008 HOLD DATA START
UK79008 HOLD DATA END
UK79011 HOLD DATA START
UK79011 HOLD DATA END
UK79013 HOLD DATA START
++ HOLD(UK79013) SYS FMID(HDBAA10) REASON(ACTION) DATE(12144)
COMMENT
(The PTF for APAR PM64065 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the utility
batch and DB2 DBM1 address spaces. After the PTF has been
applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
1 sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
++ HOLD(UK69216) SYS FMID(HDBAA10) REASON(ACTION) DATE(12144)
COMMENT
( After applying the fix for PM31180 in DB2 10 for z/OS,
FLASHCOPY IMAGE COPIES of partitioned objects with more
than one partition or of linear objects containing more than
one piece will insert a string of the form
database-name.space-name into the DSNAME (data set name)
column of the SYSCOPY record it writes for the FLASHCOPY
record with DSNUM 0, similar to SYSCOPY records that are
currently written for various types of non-backup activity.
This is done to prevent invalid data set names from being
written in these records. Users or automated programs
sensitive to the contents of SYSIBM.SYSCOPY are advised.).
UK79013 HOLD DATA END
UK79014 HOLD DATA START
UK79014 HOLD DATA END
UK79015 HOLD DATA START
UK79015 HOLD DATA END
UK79017 HOLD DATA START
UK79017 HOLD DATA END
UK79062 HOLD DATA START
++ HOLD(UK79062) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12145)
COMMENT
(***Action for PM62259:
See PM62259 APAR/PTF text for additional information about
why a REBIND is necessary.
PM62259 corrects a problem of incorrect output when a query
contains OLAP specifications and a subquery predicate. This
APAR also corrects ABENDOC4 RC00000038 DSNXOWIN+104A when a
query contains multiple OLAP specifications other than RANK,
DENSE_RANK, and ROW_NUMBER.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK79062 HOLD DATA END
UK79065 HOLD DATA START
UK79065 HOLD DATA END
1
UK79067 HOLD DATA START
++ HOLD(UK79067) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12145)
COMMENT
(***Action for PM62038:
See PM62038 APAR/PTF text for additional information about
why a REBIND is necessary.
PM62038 corrects a problem of incorrect output that may occur
when a query runs in parallel in-list (PLAN_TABLE's
ACCESSTYPE = 'N' and ACCESS_PGROUP_ID > 0); and after the
index column which is covered by the in-list predicate,
there are also other predicates applied on at least one more
index column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK79067 HOLD DATA END
UK79117 HOLD DATA START
UK79117 HOLD DATA END
UK79163 HOLD DATA START
UK79163 HOLD DATA END
UK79178 HOLD DATA START
UK79178 HOLD DATA END
UK79180 HOLD DATA START
UK79180 HOLD DATA END
UK79230 HOLD DATA START
++ HOLD(UK79230) SYS FMID(HDBAA10) REASON(ACTION) DATE(12152)
COMMENT
(See PM48742 APAR/PTF text in the PTF cover letter for
additional information about this APAR.
This APAR fixes two problems - one is incorrect index entries
created for an XML value index with key type SQL DECFLOAT;
another is incorrectly issuing SQLCODE -16061 when performing
general comparison of invalid format of special values to
numeric type in XPath predicates when no matching index exists.
To make this fix effective for an application, users need to
check if there is any XML value index with key type SQL DECFLOAT
in use. If so, users need to run CHECK INDEX on such index after
the application of this PTF to see it reports any data/index
mismatch. REBUILD INDEX needs to be done for index with mismatch
1 issue. Review the PTF cover letter to determine which, if any,
applications could be affected by this change.).
UK79230 HOLD DATA END
UK79240 HOLD DATA START
UK79240 HOLD DATA END
UK79241 HOLD DATA START
++ HOLD(UK79241) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(12152)
COMMENT
(***Action for PM61565:
See PM61565 APAR/PTF text for additional information about
why a REBIND is necessary.
PM61565 corrects a problem of incorrect output when an SQL
statement satisfies all of the following conditions:
1. SQL contains 'simple-when' CASE expression;
2. the column which is under CASE clause is defined with field
procedure;
3. constants are under WHEN clause.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UK79241 HOLD DATA END
UK79281 HOLD DATA START
UK79281 HOLD DATA END
UK79290 HOLD DATA START
UK79290 HOLD DATA END
UK79316 HOLD DATA START
++ HOLD(UK74411) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156)
COMMENT
(***Action for PM56722 (V10)
This PTF modifies program DSNTRIN to install and configure the
SYSPROC.ADMIN_INFO_SQL stored procedure in all modes of DB2 10
for z/OS. Previously, ADMIN_INFO_SQL (which is useful for
gathering DB2 diagnostic and tuning data) was not installed in
conversion mode after migration from DB2 UDB for z/OS Version 8.
If you migrated to DB2 V10 from DB2 V8 and DB2 is not yet in
new-function mode then after applying this PTF you need to take
the following action:
Run your copy of job DSNTIJRT with MODE(INSTALL) to install
and configure SYSPROC.ADMIN_INFO_SQL.
1
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
++ HOLD(UK79316) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156)
COMMENT
(This PTF provides two new features:
-- The Omnifind Text Search is moving to a new release,
IBM Text Search for DB2 z/OS (IBMTS).
-- A new stored procedure, SYSPROC.SYSTS_ALTER, can be
used to modify the options of an existing IBM Text Search
index.
If you have already installed or migrated to DB2 10 for z/OS,
you need to perform the following actions after applying this
PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Copy updated DB2 installation panels to alternate libraries
(3) Update your customized copy of job DSNTIJRT
(4) Update private copies of the DSNTIDxx CLIST input member
(5) Run installation job DSNTIJRT to install new objects
(6) Run installation job DSNTIJRV to validate new objects
Detailed guidance for these actions is given further below.
If you currently use or want to use IBM Text Search for DB2
for z/OS, you need to perform these additional actions:
(I) Download the most current version of IBMTS
(II) New IBMTS users: Install the IBMTS server
(III) Existing users: Migrate to IBMTS from OmniFind server
(IV) Add the new stored procedure SYSPROC.SYSTS_ALTER.
(V) Where to find more information
Detailed guidance for these actions is given further below.
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Actions for all customers
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
***********************************************************
* This action is required for all V10 customers
***********************************************************
This PTF modifies CLIST members DSNTINST, DSNTINSV, and
DSNTINS1 in the prefix.SDSNCLST target library only.
You need to redo any record format changes and reapply any
1 tailoring you have done to your private copies of these
CLISTs. You may also want to move them to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed
by job DSNTIJVC reside.
----------------------------------------------------------------
(2) Copy updated DB2 installation panels to alternate libraries
***********************************************************
* This action is required for all V10 customers who maintain
* copies of the DB2 installation panels outside of SMP/E:
***********************************************************
This PTF modifies the DB2 installation panels DSNTIPRA and
DSNTIPRJ in the prefix.SDSNSPFP target library.
If you keep the DB2 installation panels in a different
library then after applying this PTF, you need to copy the
updated panels to that library.
----------------------------------------------------------------
(3) Update customized copies of installation job DSNTIJRT
***********************************************************
* This action is required for all V10 customers
***********************************************************
This PTF modifies installation job DSNTIJRT in the
prefix.SDSNSAMP target library. After you apply this PTF,
you need to add the following to the list of configuration
control statements under the CFIGIN DD in your customized
copy of DSNTIJRT:
SYSPROC.SYSTS_ALTER
WLMENV(DSNWLM_GENERAL)
GRANTTO(PUBLIC)
Notes:
(a) Always leave a blank line between each configuration
control statement
(b) Inspect each of the new configuration control statement
and if required:
- Change the WLMENV parameter settings to the names of
the WLM environment you use to run these routines at
your site
- Change the GRANTTO parameter setting to the
authorization IDs that need access to the routines
- Optionally add the PKGOWNER option
----------------------------------------------------------------
(4) Update private copies of the DSNTIDxx CLIST input member
***********************************************************
* This action is required for all V10 customers
***********************************************************
This PTF adds entries to store values entered into new
fields on installation panel DSNTIPRL:
- RTJ09ACL: GRANT EXECUTE setting for
SYSPROC.SYSTS_ALTER
- RTJ09PKO: PACKAGE OWNER setting for
SYSPROC.SYSTS_ALTER
- RTJ09WLM: WLM ENV NAME setting for
SYSPROC.SYSTS_ALTER
1 You need to make the same changes to all private copies of
your CLIST output (DSNTIDxx) member. In each such copy,
add the following lines:
RTJ09ACL CHAR M NONE NONE PUBLIC
RTJ09PKO CHAR M NONE NONE NULL
RTJ09WLM CHAR M NONE NONE DSNWLM_GENERAL
The values shown in the 6th column are the DB2-supplied
default settings. If you specified different settings in
action (3) above, change the settings in column 6
accordingly.
----------------------------------------------------------------
(5) Run installation job DSNTIJRT to install new objects
***********************************************************
* This action is optional for V10 customers
***********************************************************
After you have completed the above actions, run your updated
copy of job DSNTIJRT to install and grant access to
the new routine, SYSPROC.SYSTS_ALTER, and to rebind the
packages for the IBM Text Search routines.
----------------------------------------------------------------
(6) Run installation job DSNTIJRV to validate new objects
***********************************************************
* This action is optional for V10 customers
***********************************************************
After you have completed the above actions, run your
customized copy of job DSNTIJRV to validate installation and
configuration of SYSPROC.SYSTS_ALTER.
----------------------------------------------------------------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Additional actions for Text Search customers
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The users need to follow the instructions in the
"IBM Text Search for DB2 for z/OS" book to define
the Text Search stored procedures and enable Text Search.
The following information will refer to the "IBM Text Search
for DB2 for z/OS" book.
----------------------------------------------------------------
(I) Download the most current version of IBMTS
***********************************************************
* This action is required for Text Search customers
***********************************************************
Download the most current version which is FIX R1L5 from the
following Web site:
http://www.ibm.com/software/data/db2/zos/downloads/oftss.html
On this Web site, download the zip file and the readme file
for IBMTS Text Search for DB2 for z/OS.
1 The following shows the names of the zip files
of IBMTS Text Search Servers:
Linux32 - TextSearchServer_setuplinux32.zip
Linux64 - TextSearchServer_setuplinux64.zip
Window32 - TextSearchServer_setupwin32.zip
Window64 - TextSearchServer_setupwin64.zip
zLinux - TextSearchServer_setupzlinux.zip
For Window32/64: right click the zip then choose extract
option
For Linux32/Linux64/zlinux:
chmod 755 TextSearchServer_setupxxxx.zip
unzip TextSearchServer_setupxxxx.zip
To install or update the IBMTS server, please refer to
the following publications:
--readme.html: document that accompanies the installation
file.
--"Installation, Administration, and Reference": the
product documentation for the IBM Text Search for DB2
z/OS.
----------------------------------------------------------------
(II) New IBMTS users: Install the IBMTS server
***********************************************************
* This action is required for Text Search customers
***********************************************************
To install the IBMTS server, the user needs to follow:
Chapter 4. Installing and configuring text search functions
--Installing IBM Text Search for DB2 z/OS.
(for the new installation).
or
--Installing fixes on top of the current server.
(install IBMTS server on the existing server).
----------------------------------------------------------------
(III) Existing users: Migrate to IBMTS from OmniFind server
***********************************************************
* This action is required for Text Search customers
***********************************************************
For existing users to migrate IBMTS from OmniFind server
they need to follow:
Chapter 4. Installing and configuring text search functions
--Migrating to IBM Text Search for DB2 for z/OS
from OmniFind Text Search.
----------------------------------------------------------------
(IV) Add the new stored procedure SYSPROC.SYSTS_ALTER.
***********************************************************
* This action is required for Text Search customers
***********************************************************
Refer to steps (5) and (6) of the section above titled
1 "Actions for all customers"
----------------------------------------------------------------
(V) Where to find more information
----------------------------------------------------------------
The user can look for more information for the new
SYSTS_ALTER stored procedure at:
Chapter 5. Administration stored procedures for text search
SYSPROC.SYSTS_ALTER.).
++ HOLD(UK67507) SYS FMID(HDBAA10) REASON(ACTION) DATE(12156)
COMMENT
(Please note that the following ACTIONS need to be performed
with respect to this apar:
1. Run your copy of job DSNTIJRT with MODE(INSTALL) to
bind, and grant access to the Text Search stored
procedures.
2. Refresh WLM environment defined for Text Search
stored procedures:
v wlm,applenv=wlmname,refresh
3. Refresh DB2 to make sure it will pick up the new
Text Search modules.
4. This apar introduces the text search server level R2L11. To
update the text search server, download the most current
version which is FIX R2L11, from the following Web site:
http://www.ibm.com/software/data/db2/zos/downloads/oftss.html
From this Web site, click Download OmniFind Text Search
Server for DB2 for z/OS.
The following shows the names of the files that start the
silent installation or update of a Text Search server.
1. Linux - TS_fixR2L11linux_i586.bin
2. zLinux - TS_fixR2L11zlinux.bin
3. Windows - TS_fixR2L11win32.exe
To install or update the server, please reference the
following publications:
"Instructions for installing": readme.html
document that accompanies the installation file.
"Installation, Administration, and Reference": The product
documentation for the IBM Text Search for DB2 z/OS and the
IBM OmniFind Text Search Server.
5. This apar provides the fix related to the backup index table.
After applying this APAR the users should run
1 SYSTS_UPDATE with ALLROWS options for all the indexes
aready created with option UPDATEWITHBACKUP = 1
to make sure the backup index table refreshed with the full
collection.
Note that UPDATEWITHBACKUP = 1 is default option for
SYSTS_CREATE, there for all most the indexes are created
with this option.
The users can use the following SQL statement to
look for the indexes created before applying this APAR
with UPDATEWITHBACKUP = 1
select a.indexid, indexschema, indexname, parameter, value
from sysibmts.systextindexes a, sysibmts.systextconfiguration
where a.indexid = b.indexid and parameter = 'UPDATEWITHBACKUP'
and value = '1'
Assume that the index SCHEMA1.IVC2 has UPDATEWITHBACKUP = 1
then the users need to run SYSTS_UPDATE with option ALLROWS
for this index:
CALL SYSPROC.SYSTS_UPDATE('SCHEMA1','IVC2','ALLROWS')).
UK79316 HOLD DATA END
UK79319 HOLD DATA START
UK79319 HOLD DATA END
UK79333 HOLD DATA START
UK79333 HOLD DATA END
UK79373 HOLD DATA START
++ HOLD(UK79373) SYS FMID(HDBAA10) REASON(ACTION) DATE(12158)
COMMENT
(See PM63986 APAR/PTF text in the PTF cover letter for
additional information about this APAR.
PM63986 fixes the problem that the XML index key entry might not
be inserted for some XML document. This may cause incorrect
output when the index is used.
To make this fix effective for the existing XML index, please
run CHECK INDEX on the XML index after application of this PTF
and rebuild the XML index if there is any data/index mismatch.).
UK79373 HOLD DATA END
UK79393 HOLD DATA START
UK79393 HOLD DATA END
UK79400 HOLD DATA START
UK79400 HOLD DATA END
1UK79404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79406 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79421 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79441 HOLD DATA START
UK79441 HOLD DATA END
UK79447 HOLD DATA START
++ HOLD(UK78241) SYS FMID(HDBAA10) REASON(DOC) DATE(12160)
COMMENT
(APAR PM58177 has enabled REORG TABLESPACE SHRLEVEL CHANGE to
accept a user defined mapping table created in a
partition-by-growth ( PBG ) table space.
The Utility Guide and Reference has been updated with the
following information, under the REORG TABLESPACE utility in
section titled 'Mapping table and SHRLEVEL CHANGE' :
Before running REORG TABLESPACE with SHRLEVEL CHANGE on a
table space with non-LOB data, you must create a mapping
table and index for the table space. The table space that
| contains the mapping table must be either classic segmented
| or a partition-by-growth table space, and cannot be the
table space to be reorganized.).
++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(DOC) DATE(12160)
COMMENT
(See PM47356 APAR/PTF text for additional information.
This APAR/PTF modifies the DB2 Utility Guide and Reference
and the Messages manual. The change will be documented in
the DB2 Utility Guide and Reference and Messages, and in the
Information Management Software for z/OS Solutions Information
Center.
The change is as follows.
In the Utility Guide and Reference, under REORG TABLESPACE,
Option descriptions, SORTDATA option:
SORTDATA
NO
Specifies that the data is to be unloaded in the order
of the clustering index. SORTDATA NO cannot be specified
| with SHRLEVEL CHANGE or if the table space is in REORG-
| PENDING. Specify SORTDATA NO if one of the following
conditions is true:
* The data is in or near perfect clustering order, the
| table space is not in REORP, and the REORG utility is
used to reclaim space from dropped tables.
* The data is very large, an insufficient amount of disk
| space is available for sorting, and the table space is
not in REORP.
In the Messages manual, under DSNU messages:
1
DSNU070I csect-name KEYWORD OR OPERAND x
INVALID WITH y
Explanation: The use of a keyword or operand is
| inconsistent with another keyword, operand or condition.
| x and y The keywords, operands or conditions that
cannot be used together.
System action: The control statement in error is
rejected and processing is halted.
User response: Correct the control statement in error
and resubmit the job.
| Problem determination: The REORG TABLESPACE
| utility issues this message when the keywords, operands or
| conditions are not allowed to be used in combination.).
++ HOLD(UK77573) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(***Action for PM59605
This PTF modifies the DB2 installation CLIST member DSNTINST
to fix a bug that causes it to ignore the NEWFUN setting
specified in the DSNTIDxx input member when the CLIST is run
in UPDATE mode.
This PTF modifies DSNTINST in the SDSNCLST target library only.
If you have already installed or migrated to this version of DB2
then after applying this PTF, you need to redo any record format
changes and reapply any tailoring you have done to your copies
of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by job
DSNTIJVC reside.).
++ HOLD(UK78229) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(The PTF for APAR PM55051 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the function the PTF
provides will not be available.
PM55051 provides support for REORG TABLESPACE PART SORT NPSIs
(Non-partitioned Secondary Indexes).
This is a performance enhancement to part-level REORG involving
1 NPSIs intended to improve elapsed time.
Since the removal of the BUILD2 phase for partition-level REORG
in DB2 9, the performance of REORG was degraded in some cases
due to the cost of building shadow NPSIs. Shadow NPSIs are
populated initially with keys of parts which are not in the
scope of the REORG during the UNLOAD phase. Then keys from parts
within the scope of the REORG are sorted and inserted into the
shadow NPSI during the SORT and REBUILD phases, respectively.
Significant performance improvement can be achieved by sorting
all keys of the NPSI in the same sort operation and rebuilding
the index from the entire set of sorted keys. This APAR will add
functionality to improve performance while leaving the old
behavior intact and allow the customer to control the behavior
through the installation panel and a keyword.
This APAR modifies the processing of non-partitioned secondary
indexes for REORG TABLESPACE PART SHRLEVEL CHANGE/REFERENCE
when NPSIs are defined on the table space. Processing of NPSIs
in this case will now be done in one of two ways as
documented in the UNLOAD phase section of Execution Phase
of REORG TABLESPACE in the Utility Guide and Reference.
1. During UNLOAD, one or more subtasks unload NPSI keys from
parts not within the scope of the REORG and build the shadow
NPSI. Keys from parts within the scope of the REORG are
generated from the reorganized data rows, sorted, and inserted
in the shadow index.
2. During UNLOAD, one or more subtasks processes NPSI keys from
parts not within the scope of the REORG. These keys are routed
to a sort process to be sorted with the keys from parts within
the scope of the REORG. The shadow NPSI is built from this
sorted set of keys.
A new message is issued when all keys of an NPSI are sorted
during a part-level REORG TABLESPACE. A new keyword is added
on REORG to control the sorting of all NPSI keys during a
part-level REORG TABLESPACE. The zparm controlling the sorting
of all NPSI keys during a part-level REORG is extended to
allow more options.
----------------------------------------------------------------
Changes to Messages and Codes
DSNU1242I
csect-name ALL KEYS OF A NON-PARTITIONED SECONDARY INDEX WILL
BE SORTED
Explanation
During a part-level REORG all keys of a non-partitioned
secondary index will be sorted before rebuilding the index.
This is controlled by the keyword SORTNPSI and the zparm
REORG_PART_SORT_NPSI. When SORTNPSI is specified as YES or AUTO
all keys may be sorted. When SORTNPSI is not specified,
and REORG_PART_SORT_NPSI is set to YES or AUTO, all keys may
be sorted.
1 System action
Processing is continues.
Severity
0 (informational)
----------------------------------------------------------------
Changes to Utility Guide and Reference
A new keyword SORTNPSI is added to control the method of
building an NPSI during REORG TABLESPACE PART. Options of AUTO,
YES, and NO are available on the keyword. A default is not
applicable in this case because the value will be determined
by zparm REORG_PART_SORT_NPSI if the keyword is not specified.
.-FORCE--NONE----. (3)
>--+----------------+--------+-----------------+--------------->
+-FORCE--READERS-+ +-SORTNPSI AUTO---+
'-FORCE--ALL-----' '-SORTNPSI YES----'
'-SORTNPSI NO-----'
3. The default for SORTNPSI is the value of the
REORG_PART_SORT_NPSI subsystem parameter.
SORTNPSI
Specifies when REORG TABLESPACE PART should sort all keys of a
non-partitioned secondary index. This keyword is ignored for
a REORG that is not partition-level or a REORG with no
non-partitioned secondary indexes. If SORTNPSI is not specified
the value will be determined by zparm REORG_PART_SORT_NPSI.
The benefit of sorting all keys of a non-partitioned secondary
index increases as the ratio of data reorganized to total data
in the table space increases.
AUTO
Specifies that if sorting all keys of the non-partitioned
secondary indexes improves the elapsed time and CPU
performance, all keys are sorted.
YES
Specifies that if sorting all keys of the non-partitioned
secondary indexes improves the elapsed time, all keys are
sorted.
NO
Specifies that only keys of the non-partitioned secondary
indexes that are in the scope of the REORG are sorted.
The default value is the value of subsystem parameter
REORG_PART_SORT_NPSI.
----------------------------------------------------------------
Changes to DB2 Installation
This APAR modifies the DSN6SPRM.REORG_PART_SORT_NPSI subsystem
parameter.
1
REORG_PART_SORT_NPSI specifies the default method of building
an NPSI during REORG TABLESPACE PART when the SORTNPSI
keyword is not provided in the utility control statement.
Valid settings for REORG_PART_SORT_NPSI are AUTO, NO, and YES.
The default setting is NO.
REORG_PART_SORT_NPSI is online changeable and has member scope
in data sharing.
DSN6SPRM: The REORG_PART_SORT_NPSI parameter is added with a
range of AUTO, NO, and YES. The default setting is NO.
DSNTIJUZ: The REORG_PART_SORT_NPSI parameter is added under
the DSN6SPRM invocation with a default setting of NO.
----------------------------------------------------------------
Changes to DB2 instrumentation
DSNDQWPZ: Field QWP4RPSNE is modified to trace the
REORG_PART_SORT_NPSI internal setting:
. . .
QWP4RPSN DS CL1 REORG_PART_SORT_NPSI
* * A=AUTO, N=NO, Y=YES
. . .
The IFCID 106 formatter stored procedures, SYSPROC.DSNWZP and
SYSPROC.ADMIN_INFO_SYSPARM are updated to report the
REORG_PART_SORT_NPSI setting.
----------------------------------------------------------------
This PTF adds an online-changeable subsystem parameter in
DSN6SPRM called REORG_PART_SORT_NPSI that can be used to specify
the default method of building a non-partitioned secondary index
(NPSI) during REORG TABLESPACE PART. This setting will be used
when the SORTNPSI keyword is not provided in the utility control
statement. The SORTNPSI keyword specifies whether REORG
TABLESPACE PART should decide to sort all keys of a NPSI and how
to make that decision. The setting is ignored for a REORG which
is not part-level or a REORG with no NPSIs. Valid settings for
this parameter are:
* AUTO: Specifies that if sorting all keys of the NPSI(s)
improves the elapsed time and CPU performance, all
keys are sorted.
* YES : Specifies that if sorting all keys of the NPSI(s)
improves the elapsed time, all keys are sorted.
* NO : Specifies that only keys of the NPSI(s) that are in
the scope of the REORG are sorted.
=> This is the default setting
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
1 (2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is recommended for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you
need to update your customized copy of this job as follows:
* Add the keyword parameter REORG_PART_SORT_NPSI=<x>,
where <x> is AUTO, NO, or YES, to the invocation of the
DSN6SPRM macro. Make sure to add a continuation character
in column 72 if needed. If you omit adding
REORG_PART_SORT_NPSI here, the value will be set to
the default of NO when you assemble the DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
----------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
----------------------------------------------------------------
==> This action is required for all customers
This PTF adds an entry for REORG_PART_SORT_NPSI
to the CLIST default input members in the SDSNSAMP target
library. You need to add these entries to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
REORG_PART_SORT_NPSI CHARR M AUTO YES$ <x>
Change <x> to the value you specified for
REORG_PART_SORT_NPSI in step (2), above.
If you do not add REORG_PART_SORT_NPSI to a DSNTIDxx
member, the DB2 installation CLIST will assume
REORG_PART_SORT_NPSI=NO when run with that member as
input.).
++ HOLD(UK76492) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(APAR PM54727 has corrected an issue where REORG REBALANCE on a
1 partitioned table space with an editproc defined can result in
corrupted limit key values in the DB2 catalog and directory.
In the event that the above limit key corruption has occurred,
user can repair the catalog/directory by manually altering the
limit keys to the correct value on the affected table space /
partitions, and then run a REORG TABLESPACE utility to remove
the restrictive REORP status.).
++ HOLD(UK78208) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(Action for PM53254:
The PTF of PM53254 adds a new system parameter called
REORG_IGNORE_FREESPACE, which specifies whether the REORG
TABLESPACE utility should ignore the PCTFREE and FREEPAGE values
when reloading data rows into a Partition By Growth (PBG)
table space in the following circumstances:
- When reorganizing a subset of the PBG partition(s)
- When the table in the PBG table space has LOB column(s)
Valid settings for REORG_IGNORE_FREESPACE are NO and YES.
The default is NO, meaning that the PCTFREE and FREEPAGE values
will be honored by the REORG TABLESPACE utility.
To incorporate this fix the DB2 initialization parameter module,
DSNZPARM, will need to be reassembled and re-linked by
running the DB2 install clist DSNTINST using UPDATE mode.
Insure that the output sample library name specified in panel
DSNTIPT is not the same as an existing library name from a
previous execution of the DSNTINST clist as the clist processing
will delete all members delete all members of the data set name
specified.
Note: Customers who receive return code 8 and message "ASMA939U
Unable to load external function module - DSNTIXL" when
applying this PTF need to refer to Info APAR II13979.
If you have already installed or migrated to this release of
DB2, you need to take the following actions after applying this
PTF:
(1) Optional: Update your DB2 subsystem parameter (DSNZPxxx)
modules:
* Add the keyword parameter
REORG_IGNORE_FREESPACE=<n>,
where <n> is either NO or YES (NO is recommended) to the
invocation of the DSN6SPRM macro in your customized
version of the installation job DSNTIJUZ. Make sure to
add a continuation character in column 72 if needed. If
you omit adding REORG_IGNORE_FREESPACE here, the value
will be set to the default of NO when you assemble the
DSNZPxxx module.
* Run the first two steps of the DSNTIJUZ job you modified,
to assemble and link the load module.
* After the job completes, you must either use the SET
SYSPARM command or stop and start DB2 for the change to
take effect.
1
(2) Required: Update your private copies of the CLIST defaults
(DSNTIDxx) member:
This PTF adds an entry for REORG_IGNORE_FREESPACE to the
CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output (DSNTIDxx) member for DB2.
In each such copy, add the following line:
REORG_IGNORE_FREESPACE CHAR M NO YES <n>
where <n> is the value you specified for
REORG_IGNORE_FREESPACE when you modified DSNTIJUZ in step
(1), above. Specify NO for <n> if you bypassed step (1).
(3) Required: Update customized copies of installation CLIST
member DSNTINST:
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.).
++ HOLD(UK74936) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(*** Action for PM47659 ***
This APAR has changed the UNLOAD utility to utilize the
RUNSTATS NPAGES statistic from SYSIBM.SYSTABLES to estimate
the space needed for the SYSREC data set.
A RUNSTATS against the target table space is recommended
prior to the UNLOAD to ensure the accurate estimation
for space requirement.).
++ HOLD(UK76053) SYS FMID(HDBAA10) REASON(ACTION) DATE(12160)
COMMENT
(The PTF for APAR PM47356 has modified the REORG TABLESPACE
utility to issue the following message and end with RC8 when
REORG TABLESPACE SORTDATA NO is run against a non-Partition-
By-Growth (non-PBG) partitioned table space in REORG-PENDING
(REORP). A REORG TABLESPACE SORTDATA YES is required to remove
the REORP state.
MSGDSNU070I - KEYWORD OR OPERAND 'SORTDATA NO' INVALID WITH
'TABLE SPACE IN REORG PENDING').
UK79447 HOLD DATA END
UK79505 HOLD DATA START
UK79505 HOLD DATA END
UK79544 HOLD DATA START
UK79544 HOLD DATA END
UK79553 HOLD DATA START
UK79553 HOLD DATA END
1
UK79562 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79589 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79602 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79619 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79630 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79665 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79683 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79701 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79710 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79762 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79770 HOLD DATA START
++ HOLD(UK79770) SYS FMID(HDBAA10) REASON(DOC) DATE(12176)
COMMENT
(PM63979 introduces the following changes to the Messages
publication:
Description change for message DSNU1140I:
DSNU1140I
csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR
message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY
Explanation
The number of instances of the indicated message issued during a
utility operation has exceeded the maximum number permitted.
csect-name
The name of the control section that issued the message.
max-messages
The maximum number of messages that are issued before this
message is issued. This value is controlled by the utility that
issues message DSNU1140I.
message-number
The message number that has reached the limit and is now
suppressed.
| Example 1: The LOAD utility issues message DSNU1140I after
2000 instances of any of the following messages: DSNU313I,
DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have
triggered the suppressed message are still discarded.
| Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message
| DSNU1140I after 2000 instances of message DSNU1239I, when
| MAXERR is specified to greater than 2000 or 0. Any rows that
| would have triggered the suppressed message are still not
| unloaded.
System action
Processing continues.
No additional instances of message-number messages are issued.
Only the issuance of the message is suppressed. Any action that
is associated with the suppressed message number still occurs.
1
User response
No action is required.
Severity
0).
++ HOLD(UK79770) SYS FMID(HDBAA10) REASON(ACTION) DATE(12176)
COMMENT
(The PTF for APAR PM63979 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
To make this fix effective for a static application, it must be
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.).
++ HOLD(UK75124) SYS FMID(HDBAA10) REASON(ACTION) DATE(12176)
COMMENT
(The PTF for APAR PM50005 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
utility batch and DB2 DBM1 address spaces. After the PTF has
been applied, it will become active in the utility batch address
space immediately upon job submission, while it will not take
effect in the DB2 DBM1 address space until DB2 is stopped and
started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 DBM1 address spaces, the problem the PTF
addresses will not be resolved.
***Action for PM50006:
It should be noted that the removal of these UNLOAD restrictions
will now allow clone and/or base table data to be UNLOADed
using image copy data sets from the other table in the clone
relationship as follows:
1 - UNLOAD from base table using a clone table image copy.
2 - UNLOAD from clone table using a base table image copy.
And in these cases the MSGDSNU1227I and MSGDSNU1408I messages
will no longer be issued and the return codes will be zero with
this APAR fix.).
UK79770 HOLD DATA END
UK79774 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79820 HOLD DATA START
UK79820 HOLD DATA END
1
UK79823 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79832 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79871 HOLD DATA START
++ HOLD(UK79871) SYS FMID(HDBAA10) REASON(ACTION) DATE(12179)
COMMENT
(The PTF for APAR PM62786 has modified CSECTs in both the
DSNUT101 and DSN3AMGP load modules, affecting the utility batch
and DB2 MSTR address spaces. After the PTF has been applied, it
will become active in the utility batch address space
immediately upon job submission, while it will not take effect
in the DB2 MSTR address space until DB2 is stopped and started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 MSTR address spaces, the problem the PTF
addresses will not be resolved.).
++ HOLD(UK62466) SYS FMID(HDBAA10) REASON(ACTION) DATE(12179)
COMMENT
(The PTF for APAR PM25135 has modified CSECTs in both the
DSNUT101 and DSN3AMGP load modules, affecting the utility batch
and DB2 MSTR address spaces. After the PTF has been applied, it
will become active in the utility batch address space
immediately upon job submission, while it will not take effect
in the DB2 MSTR address space until DB2 is stopped and started.
The PTF does not have to be applied to all members in a data
sharing environment simultaneously, and may be staged across
each member. However, until the fix is active in both the
utility batch and DB2 MSTR address spaces, the problem the PTF
addresses will not be resolved.).
UK79871 HOLD DATA END
UK79876 HOLD DATA START
UK79876 HOLD DATA END
UK79881 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK79911 HOLD DATA START
UK79911 HOLD DATA END
UK79995 HOLD DATA START
UK79995 HOLD DATA END
UK80106 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80113 HOLD DATA START
++ HOLD(UK80113) SYS FMID(HDBAA10) REASON(DOC) DATE(12188)
COMMENT
(With the PTF for PM52724, a new DB2 message, DSNU1544I, will
be issued during the RECOVER utility with the BACKOUT YES
option if the recovery cannot proceed:
1 ..
DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type
obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER
TABLE ACTIVITY
..
Explanation: BACKOUT YES was specified for the RECOVER utility,
but it cannot proceed because a prior SQL mass
DELETE, TRUNCATE TABLE, or DROP TABLE occurred
on the object. The deleted data for these
activities are not logged, hence cannot be backed
out. The recovery is prohibited when this kind of
activity has occurred between the recovery point
(specified by TOLOGPOINT or TORBA) and the current
time.
..
System action: The utility terminates processing.
..
User response: Remove the BACKOUT YES option from the RECOVER
utility statement and resubmit the job. This
will recover the list of objects by restoring a
backup then applying the logs forward to the
recovery point.
..
Severity: 8 (error)
..
See the closing text of PM52724 for details.).
++ HOLD(UK80113) SYS FMID(HDBAA10) REASON(ACTION) DATE(12188)
COMMENT
(After the application of the PTF for APAR PM52724, the
SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will no
longer be inserted for SQL mass delete, TRUNCATE TABLE,
DROP TABLE, or ALTER TABLE ROTATE PARTITION on segmented or
universal table spaces (UTS).
..
A new DB2 message, DSNU1544I, will now be issued during the
RECOVER utility with the BACKOUT YES option if the recovery
cannot proceed:
..
DSNU1544I csect RECOVER BACKOUT YES CANNOT PROCEED ON obj-type
obj-qual.obj-nm DUE TO SQL MASS DELETE OR OTHER
TABLE ACTIVITY
..
Explanation: BACKOUT YES was specified for the RECOVER utility,
but it cannot proceed because a prior SQL mass
DELETE, TRUNCATE TABLE, or DROP TABLE occurred
on the object. The deleted data for these
activities are not logged, hence cannot be backed
out. The recovery is prohibited when this kind of
activity has occurred between the recovery point
(specified by TOLOGPOINT or TORBA) and the current
time.
..
System action: The utility terminates processing.
..
User response: Remove the BACKOUT YES option from the RECOVER
utility statement and resubmit the job. This
1 will recover the list of objects by restoring a
backup then applying the logs forward to the
recovery point.
..
Severity: 8 (error)
..
See the closing text of PM52724 for details.).
UK80113 HOLD DATA END
UK80120 HOLD DATA START
UK80120 HOLD DATA END
UK80191 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80199 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80206 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80231 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80240 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80243 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80259 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80291 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80299 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80327 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80337 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80357 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80359 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80363 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80372 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80404 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80407 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80414 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80439 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80447 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80449 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80459 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80493 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80522 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80523 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80525 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80552 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80559 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80662 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80672 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80678 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80785 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80830 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80840 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80868 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80897 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80910 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80929 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80931 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK80981 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81001 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81020 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81022 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
1UK81023 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81045 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81046 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81064 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81147 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81174 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81177 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81178 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81181 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81223 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81241 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81263 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81271 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81304 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
UK81306 ACCEPTED - (NOT IN PTS) - NO COVER LETTER
READY
END
| |
Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release Level AC00 
AC00 Cover Letters.txt