Scope: All DB2 Users
Effective Date: 10/12/2015
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 AI00 (IBM RSU1507+)
Justification: IBM DB2 software frequently requires actions to be taken to fully implement the fixes being applied. Often these actions are the type of work done by DBA's (Database Administrators) and/or application support staff. As an example, many fixes require DB2 binds to implement the maintenance. If these actions aren't taken, the fixes generally will not take effect, though most often will not cause any adverse effect otherwise.
Benefits to Users: Alert non-systems support staff of actions they may need to take to fully implement maintenance fixes supplied by the vendor.
Details: Please see the attachments for the details on the fixes being applied with this current level of maintenance and any hold actions that may be required. Please note, that the actions required for subsystem level items are handled by Z_SW_TDS_DB2_SYSTEM team, and need not be addressed by application developers or DBA's.
Primary Contact: Cathy Puzzuoli (336-765-9045)
Secondary Contact: TDSDB2@HP.COM
UI16510 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10449 -
****************************************************************
* USERS AFFECTED: All DB2 11, DB2 10 and DB2 9 for z/OS *
* Utilities users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E400E1 occurred when Reorg *
* triggered a Real Time Statistics (RTS) *
* update. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a RTS update that was triggered by an Utility, DB2
incorrectly updated an internal control block field used to
track utility processing.
As a result, the utility failed with RC00E400E1 when attempting
to update the indexes.
DB2 code has been modified to correctly update the internal
control block field.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10449
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIPSI PI10449
DSNIRTSX PI10449
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10449 DSNIPSI DSNIRTSX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIPSI
DSNIRTSX
LISTEND
UI16510 COVER LETTER END
UI17758 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM91237 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users whose queries are *
* dynamic, or use REOPT(ALWAYS) for static *
* queries. *
****************************************************************
1 * PROBLEM DESCRIPTION: If a query is dynamic, or REOPT(ALWAYS) *
* is used for a static query, DB2 may *
* hold unnecessary claims on the *
* table space or index space during the *
* access path selection for the *
* following conditions of a table *
* referenced by the query: *
* *
* 1. Statistics indicate the table is *
* empty, or *
* 2. Table is defined as VOLATILE and *
* missing statistics (CARDF=-1), or *
* 3. Statistics indicate qualifying *
* partitions of the table are *
* empty, or *
* 4. Subsystem parameter NPGTHRSH is set *
* to a non-zero value, and NPAGES *
* for the table in SYSIBM.SYSTABLES *
* is smaller than NPGTHRSH, and the *
* table is missing statistics *
* (CARDF=-1). *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For a dynamic query, or a static query with REOPT(ALWAYS), one
or more of following problems could occur:
* DB2 may acquire unnecessary claims during prepare or
incremental bind;
* DB2 may incorrectly hold claims until the end of prepare or
incremental bind;
* DB2 may open pagesets at prepare or incremental bind causing
unnecessarily long prepare/incremental bind time.
These problems may occur when any of the following conditions
exists:
1. Catalog statistics indicate the table is empty, or
2. The table is defined as VOLATILE and missing statistics
(i.e., CARDF=-1), or
3. Statistics indicate qualifying partitions of the table are
empty, or
4. Subsystem parameter NPGTHRSH is set as a non-zero value, and
the table's NPAGES value in the catalog is smaller than
NPGTHRSH, and the table is missing statistics (i.e.,
CARDF=-1).
For the above situations, the DB2 optimizer needs to access the
Real-time Statistics (RTS) in memory to retrieve the real-time
statistics for access path selection, which requires a hold on
claims on the underlying objects. Such claims, however, may
not get released by the end of access path selection.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE INDEXPROBING
Code is changed to solve the problem described above. A new
1 interface of Real-time Statistics (RTS) is introduced in this
APAR to allow the DB2 optimizer to access RTS in the catalog to
reduce the need to hold claims which are required when accessing
the in-memory RTS. The held claims are released at the end
of the access path selection. Since in-memory RTS information
may differ slightly from the catalog RTS tables, the DB2
optimizer may select a different access path for such queries
and there is some risk of query performance regression.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM91237
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIIEPL PM91237
DSNIRTSF PM91237
DSNIRTSX PM91237
DSNXORTS PM91237
HDBAA10J PM91237
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM91237 DSNIIEPL DSNIRTSF DSNIRTSX DSNXORTS HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIIEPL
DSNIRTSF
DSNIRTSX
DSNXORTS
LISTEND
UI17758 COVER LETTER END
UI20649 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI14839 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 IN CSECT DSNILKTO *
* ERQUAL1004 when processing INDOUBT URs *
* during DB2 RESTART. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DB2 restart, if multiple indoubt Unit of
Recovery (URs) have the interest on the same resource,
Data Manger (DM) reacquires parent lock on behalf of
each indoubt UR. However, the request to reacquire
the parent lock for each subsequent indoubt UR is
inconsistent with the currently established locking
protocol. This results in second parent lock request
denied for the same resource.
1 To avoid this locking failure, DM restart logic will
make sure that appropriate locking protocol is used
to reacquire the parent lock for the first indoubt UR
and acquire the same parent lock for the subsequent
indoubt URs when sharing the same resource.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI14839
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILKTO PI14839
DSNIXLKP PI14839
DSNWDFDM PI14839
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI14839 DSNILKTO DSNIXLKP DSNWDFDM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILKTO
DSNIXLKP
DSNWDFDM
LISTEND
UI20649 COVER LETTER END
UI20718 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI07515 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: New DSN6FAC DDF Compatibility *
* specifications are required to help *
* users compensate for unexpected *
* behavior of remote client application *
* environments. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Users have observed unexpected behavior in remote client
application environments where remote client environment
related changes are necessary in order to tolerate or
correct the situation.
The following situations are considered:
o Idle Thread Time-Out serviceability:
When a DDF Idle Thread Time-Out event occurs, DB2 (DDF) will
terminate the network connection and abort the work related
to the idle transaction. DB2 also returns companion
serviceability information, in the form of a DRDA AGNPRMRM
(AGeNt PeRManent error Reply Message) reply, to assist the
remote client application environment in identifying the
1 source, or cause, of the failed connection.
Some remote client application environments are not prepared
to tolerate the change in behavior that they may see as a
result of this serviceability related reply.
For example, remote client application environments may not
be prepared to tolerate an ERROR CODE -1224 or SQL1224N that
is returned instead of an ERROR CODE -4499 or SQL30081N that
they may have been accustomed to.
o Prior version dependency:
Some remote client application environments may not be
prepared to tolerate a new version of DB2, even when the
DB2 (server) version is still operating in Conversion Mode.
For example, this may lead to erroneous SQLCODE -4700
conditions due to an incorrect attempt, by the remote client
application environment, to utilize DB2 New Function that
is not yet available.
Remote client application environment changes are necessary
to tolerate or correct the condition but these changes may
take time to implement and/or deploy. As a result, DB2 for
z/OS changes are required to allow users to compensate for
the condition and hence allow remote client application
environments to continue operating until the necessary client
environment related changes can be deployed.
To help users bridge the gap until the remote client
application environment adjustments can be made, DB2 will
provide two new DSNZPARM DSN6FAC DDF_COMPATIBILITY keyword
specifications:
o Disable Idle Thread Time-Out serviceability:
The DDF_COMPATIBILITY DISABLE_ITTO_EXCPTN specification can
be used, perhaps in conjunction with other DDF_COMPATIBILITY
specifications, to cause DB2 to sacrifice the Idle Thread
Time-Out serviceability information that is normally returned
to remote client application environments.
This specification can be changed on-line.
When this specification is provided, Idle Thread Time-Out
events will cause the connection to be terminated only, and
DB2 will not return companion serviceability information that
identifies the source of the connection termination.
o Prior version dependency:
The DDF_COMPATIBILITY IDNTFY_Vnn_PRIOR_VER specification can
be used, perhaps in conjunction with other DDF_COMPATIBILITY
specifications, to cause DB2 to identify itself, and its DRDA
functionality, relative to the prior version that DB2 was
migrated from.
This specification applies only to CM, ENFM, CM*, or ENFM*
migration environments. It does not apply once DB2 is
migrated to NFM.
This specification can be changed on-line.
This specification allows remote client application
environments to believe that they are still operating with
the prior version of DB2 where the applications are known to
behave correctly.
Users should understand that these specifications are only
intended to be a temporary measure until the remote client
application environment can be modified to tolerate the
1 condition.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI07515
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI20069 (DB2 10)
This PTF modifies the DB2 installation CLIST default input
members, DSNTIDXA and DSNTIDXB. It corrects an error in the
CLIST range checking of the settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. If you have already installed or migrated
to DB2 10, you need to make the correction in your private
DSNTIDxx members. Edit each such member, locate the entries for
SIMULATED_CPU_COUNT and SIMULATED_CPU_SPEED, and change the
fifth field to NONE. In other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <y>
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <z>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <y>
SIMULATED_CPU_SPEED CHARR G OFF NONE <z>
where <y> is the current setting of SIMULATED_CPU_COUNT
and <z> is the current setting of SIMULATED_CPU_SPEED. Save
your changes.
ACTION:
***Action for PI07515 (DB2 10)
This PTF adds two new options, DISABLE_ITTO_EXCPTN and
IDNTFY_V10_PRIOR_VER, to the DSN6FAC.DDF_COMPATIBILITY subsystem
parameter.
- DISABLE_ITTO_EXCPTN:
Disables Idle Thread Time-Out
related serviceability information
from being returned to remote client
environments.
- IDNTFY_V10_PRIOR_VER:
Return information to ALL remote
clients to reflect New Function
support and product signature of
prior version where DB2 was migrated
from. DB2 essentially identifies
itself as the prior version.
Does not apply in NFM. Applies
only in CMn / ENFM and CMn* / ENFM*.
These options can be specified individually,
together, or in combination with other DDF_COMPATIBILITY
options. Examples:
DDF_COMPATIBILITY=
DDF_COMPATIBILITY=DISABLE_ITTO_EXCPTN
DDF_COMPATIBILITY=IDNTFY_V10_PRIOR_VER
1 DDF_COMPATIBILITY=(DISABLE_ITTO_EXCPTN,IDNTFY_V10_PRIOR_VER)
DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_ITTO_EXCPTN)
In DB2 data sharing, it is recommended to use the same
DDF_COMPATIBILITY setting on all members of the group.
The default for DDF_COMPATIBILITY is null (as shown in the first
example above) meaning that DB2 10 DDF behavior is maintained
with all clients.
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is recommended for all customers.
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers who want to use
one or both of the new DDF_COMPATIBILITY options,
DISABLE_ITTO_EXCPTN and IDNTFY_V10_PRIOR_VER.
After applying this PTF, edit your customized copy of
job DSNTIJUZ as follows:
* Add or update the DDF_COMPATIBILITY keyword parameter in
the invocation of the DSN6FAC macro and specify a setting
of DISABLE_ITTO_EXCPTN, IDNTFY_V10_PRIOR_VER, or both.
For example:
DDF_COMPATIBILITY=DISABLE_ITTO_EXCPTN
DDF_COMPATIBILITY=IDNTFY_V10_PRIOR_VER
If additional options are needed, use the list format,
for example:
DDF_COMPATIBILITY=(DISABLE_ITTO_EXCPTN,IDNTFY_V10_PRIOR_VER)
You can also use the list format to specify one or both
of the new options in combination with one or more
other DDF_COMPATIBILITY options. 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
1 SYSPARM command or stop and restart DB2 for the change to
take effect.
---------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers
This PTF modifies the entry for DDF_COMPATIBILITY in the
CLIST default input members in the SDSNSAMP target library
You need to add or update this entry in all private copies
of your CLIST output DSNTIDxx member. In each such copy,
convert any existing DDF_COMPATIBILITY entry that has this
format:
DDF_COMPATIBILITY CHARR M NONE NONE <x>
or this format:
DDF_COMPATIBILITY STR M <x>
or this format:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M <y>
to this format:
DDF_COMPATIBILITY LLST M <x>
DDF_COMPATIBILITY1 LLST M <y>
DDF_COMPATIBILITY2 LLST M NULL
DDF_COMPATIBILITY3 LLST M NULL
DDF_COMPATIBILITY4 LLST M NULL
where <y> is NULL is the previous format was CHARR or STR.
Change <x> to the setting you specified in step (2),
above. If necessary, you can continue the setting onto the
DDF_COMPATIBILITYx entries by splitting it after a comma.
For example:
DDF_COMPATIBILITY LLST M SP_PARMS_NJV,DISABLE_IMPCAST_NJV,
DDF_COMPATIBILITY1 LLST M DISABLE_IMPCAST_JV,IGNORE_TZ,
DDF_COMPATIBILITY2 LLST M SP_PARMS_JV,DISABLE_ITTO_EXCPTN,
DDF_COMPATIBILITY3 LLST M IDNTFY_V10_PRIOR_VER
DDF_COMPATIBILITY4 LLST M NULL
If you do not add entries for DDF_COMPATIBILITY to a
DSNTIDxx member, the DB2 installation CLIST will assume
'DDF_COMPATIBILITY=,' when run with that member as input.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
1 DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWPZ PI07515
DSNDQW02 PI07515
DSNLCTRC PI07515
DSNLTEXC PI07515
DSNTIDXA PI07515
DSNTIDXB PI07515
DSNTINST PI07515
DSNWZIFA PI07515
DSN6FAC PI07515
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI07515 DSNDQWPZ DSNDQW02 DSNLCTRC DSNLTEXC DSNTIDXA DSNTIDXB
DSNTINST DSNWZIFA DSN6FAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCTRC
DSNLTEXC
DSNWZIFA
MACROS
DSNDQWPZ
DSNDQW02
DSNTIDXA
DSNTIDXB
DSNTINST
DSN6FAC
LISTEND
UI20718 COVER LETTER END
UI21416 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20314 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of EBCDIC mixed *
* data and the RTRIM, LTRIM or STRIP scalar *
* functions. *
****************************************************************
* PROBLEM DESCRIPTION: After migrating to Version 10, the *
* scalar functions RTRIM, LTRIM and STRIP *
* may return an SQLCODE -171 if the *
* input expression is an invalid EBCDIC *
* mixed data string. In Version 9, some *
* invalid EBCDIC mixed data strings were *
* tolerated. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 Version 10 provided extended functionality for the LTRIM,
1 RTRIM and STRIP functions. With these extensions, the following
behaviors changed :
1. If the input argument to LTRIM or RTRIM is an invalid EBCDIC
mixed data string, Version 10 may return SQLCODE -171. For this
format, Version 9 did not return an SQLCODE. For example,
C1 contains X'40400F0F4040'
(two consecutive shift-in control characters(X'0F') is illegal)
SELECT RTRIM(C1) FROM T;
V10 returns -171 sqlcode
V9 returns X'40400F0F'
2.In DB2 Version 10, a shift-out control character (X'0E')
followed by a shift-in control character (X'0F') is removed
when trimming blanks. In DB2 Version 9, this combination of
control characters is not removed. For example:
C1 contains X'40400E0F4040'
SELECT RTRIM(C1) FROM T;
V10 returns the empty string
V9 returns X'40400E0F'
To provide relief on Version 10 for this incompatible
change for EBCDIC mixed data input to the RTRIM, LTRIM and
STRIP functions, this APAR will :
1. Document the incompatible changes in the Application and SQL
release incompatiblities for migration section of the manual.
2. Add a new value V9_TRIM for the BIF_COMPATIBILITY system
parameter to provide a system-wide switch to get the version 9
behavior for RTRIM, LTRIM and STRIP. Setting BIF_COMPATIBILITY
to V9_TRIM would also include the Version 9 behavior indicated
by V9_DECIMAL_VARCHAR. This apar does not change the default
value of BIF_COMPATIBILITY, which is CURRENT for new
installations, and V9_DECIMAL_VARCHAR for systems migrating to
DB2 Version 10. The V9_TRIM value only applies when the
data is EBCDIC.
3. Write IFCID 366 trace records when the Version 9 RTRIM, LTRIM
or STRIP are being used. A new value "10" will be used for
the
function type field QW0366FN. See APARs PM29124 and PM66095
for more details on IFCID 366.
4. Add LTRIM, RTRIM and STRIP to the SYSCOMPAT_V9 and SYSCURRENT
schemas to provide a way for a specific SQL statement
or application to choose between the Version 9 and Version 10
behavior. The schema names must be in front of SYSIBM in the
path to be effective. The schemas and zparm values are used
during function resolution to determine which LTRIM, RTRIM
or STRIP function will be invoked (Version 9 or Version 10).
1 Packages bound before Version 10 will continue to get the
Version 9 behavior on migration to Version 10. When a package
is bound on Version 10 after applying this apar, the
BIF_COMPATIBILITY parameter or current path will be used to
determine the behavior of the LTRIM, RTRIM or STRIP functions.
Materialized query tables and indexes on expression created
before Version 10 that reference these functions will need
to be dropped and recreated with the BIF_COMPATIBILITY
parameter or current path value set appropriately to get the
Version 9 behavior. If a reference statement has a different
behavior that is specified by the BIF_COMPATIBILITY parameter
or a different current path, the materialized query table
or expression based index is not used.
Views and inline SQL functions use the behavior of the SQL
statement that references the object. It is possible for
references to the same view or function in different
applications to get different behavior for these functions.
Additional keywords : SQLMIGRATION SQLRTRIM SQLLTRIM SQLSTRIP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20314
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI20314:
See PI20314 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20314 adds BIF_COMPATIBILITY support for the RTRIM, LTRIM
and STRIP built-in functions.
To make this fix effective for a static application, it must be
rebound after application of this PTF. The BIF_COMPATIBILITY
system parameter should be set to V9_TRIM before rebinding.
Review the PTF cover letter to determine which, if any,
applications could be affected by this change.
ACTION:
***Action for PI20314 (DB2 10)
This PTF adds a new option called V9_TRIM to the DSN6SPRM
BIF_COMPATIBILITY subsystem parameter. It can be used by DB2
10 customers who store mixed-byte EBCDIC data on DB2 to obtain
toleration of certain errors in mixed-byte EBCDIC strings:
- V9_TRIM: For decimal input, the
CHAR, VARCHAR, CAST( ... AS CHAR)
and CAST( ... as VARCHAR) built-in
functions behave as they do when
BIF_COMPATIBILITY is set to
V9_DECIMAL_VARCHAR. In addition,
the LTRIM, RTRIM, and STRIP built-in
functions behave like DB2 V9 with
1 respect to tolerating invalid EBCDIC
mixed data strings and treatment of
EBCDIC control characters X'0E0F'.
For DB2 data sharing it is recommended but not required that all
members use the same setting.
The BIF_COMPATIBILITY parameter is externalized on installation
panel DSNTIPX as BIF COMPATIBILITY. DSNTIPX has been updated to
accept the new V9_TRIM 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) Copy updated DB2 installation panels to alternate libraries
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Modify and rebind any applications that use the LTRIM,
RTRIM, or STRIP built-in functions.
----------------------------------------------------------------
(1) 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 DB2 installation panels DSNTIPX in the
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 DSNTIP8 panel to that library.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers who want to use
the new V9_TRIM option of DSN6SPRM.BIF_COMPATIBILITY:
After applying this PTF, edit your customized copy of
job DSNTIJUZ as follows:
* Add or update the keyword parameter
BIF_COMPATIBILITY=V9_TRIM to the invocation of the
DSN6SPRM macro in your customized copy of installation job
DSNTIJUZ. Make sure to add a continuation character in
column 72 if needed. If you omit adding BIF_COMPATIBILITY
here, the value will be set to the default of CURRENT 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 who want to use
the new V9_TRIM option of DSN6SPRM.BIF_COMPATIBILITY:
After applying this PTF, edit all private copies of your
your CLIST output DSNTIDxx member, locate the entry for
BIF_COMPATIBILITY, and set the last field to V9_TRIM:
BIF_COMPATIBILITY CHAR G NONE NONE V9_TRIM
----------------------------------------------------------------
(4) Application and object changes may be needed when applying
this PTF. The actions depend on the value of the
BIF_COMPATIBILITY system parameter. See PI20314 APAR/PTF
text for additional details.
----------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIPX PI20314
DSNWZIFA PI20314
DSNXGSFN PI20314
DSNXOFN2 PI20314
DSNXORFN PI20314
DSNXOXEX PI20314
DSNXRDBC PI20314
DSNXRDB9 PI20314
DSNXRMA9 PI20314
DSNXRME9 PI20314
DSNXRMXA PI20314
DSNXRMXE PI20314
DSNXRSBC PI20314
DSNXRSB9 PI20314
DSN6SPRM PI20314
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20314 DSNTIPX DSNWZIFA DSNXGSFN DSNXOFN2 DSNXORFN DSNXOXEX
DSNXRDBC DSNXRDB9 DSNXRMA9 DSNXRME9 DSNXRMXA DSNXRMXE
DSNXRSBC DSNXRSB9 DSN6SPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWZIFA
DSNXGSFN
DSNXOFN2
DSNXORFN
DSNXOXEX
DSNXRDBC
DSNXRDB9
DSNXRMA9
DSNXRME9
DSNXRMXA
DSNXRMXE
DSNXRSBC
1 DSNXRSB9
MACROS
DSNTIPX
DSN6SPRM
LISTEND
UI21416 COVER LETTER END
UI21468 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12327 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the RECOVER utility with the *
* BACKOUT YES option. *
****************************************************************
* PROBLEM DESCRIPTION: Users do not have an easy method of *
* determining whether the RECOVER *
* utility with BACKOUT YES will be *
* prohibited due to SQL mass DELETE, *
* TRUNCATE TABLE, or DROP TABLE *
* activity on a segmented table space *
* or universal table space (UTS). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently users cannot determine from the REPORT RECOVERY
output whether or not RECOVER BACKOUT YES will be prohibited
due to SQL mass DELETE (DELETE without a WHERE clause),
TRUNCATE TABLE, or DROP TABLE activity on a segmented table
space or UTS.
..
A SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' (L-M)
was defined to help identify these situations (APAR PM30991)
but was later removed (APAR PM52724) and replaced with a new
diagnostic log record that was written for SQL mass DELETE,
TRUNCATE TABLE, or DROP TABLE. The diagnostic log record
is used by RECOVER to detect SQL activity that prohibts
the use of the BACKOUT YES option, but there is no external
indication for users.
..
Other issues addressed by this APAR:
- Garbled index name in msgDSNU1544I for RECOVER INDEX
BACKOUT YES.
- RECOVER BACKOUT YES is incorrectly prohibited when an
SQL mass DELETE, TRUNCATE TABLE, DROP TABLE, or ALTER
TABLE ROTATE PARTITION was rolled back.
..
Additional keywords: DSNU1544I DSNU556I RC08
This APAR adds code to insert a single L-M SYSCOPY record for
each table in a commit scope where an SQL mass DELETE, TRUNCATE
TABLE, or DROP TABLE was executed on a table in a segmented
table space or UTS. The L-M SYSCOPY record will be inserted
during commit processing.
1 - If many SQL mass deletes are executed on a single table in a
commit scope, only one L-M SYSCOPY record will be inserted.
- If many SQL mass deletes are executed on different tables in
a commit scope, one L-M SYSCOPY record will be inserted for
each table.
The REPORT RECOVERY utility output will display the L-M record
in the SYSCOPY section of the report.
..
RECOVER BACKOUT YES to a point in time prior to the
START_RBA of the L-M SYSCOPY record will be prohibited with
msgDSNU1544I and RC8. If the table space has indexes
(with the COPY YES attribute) or auxiliary objects (LOB or
XML tablespaces and auxiliary indexes) RECOVER BACKOUT
YES will also be prohibited on these objects when mass
DELETE, TRUNCATE TABLE, or DROP TABLE has occurred on the
base (segmented or UTS) table space.
..
The L-M SYSCOPY record columns will contain:
ICTYPE='L',
STYPE='M',
DBNAME=database-name,
TSNAME=tablespace-name,
LOWDSNUM=OBID of affected table,
START_RBA=RBA or LRSN during commit processing
..
The other two issues have been corrected:
- The index name in msgDSNU1544I for RECOVER INDEX BACKOUT
YES displays correctly.
- RECOVER BACKOUT YES is not prohibited for SQL mass DELETE,
TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION
activity that was rolled back.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12327
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
After the application of the PTF for APAR PI12327, a single
SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will be
inserted per commit scope for SQL mass DELETE, TRUNCATE TABLE,
or DROP TABLE executed on a table in a segmented or universal
table space (UTS). See the closing text for APAR PI12327
for more details.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNFUDRE PI12327
DSNICMT1 PI12327
DSNICMT2 PI12327
DSNIRCSR PI12327
DSNISEGD PI12327
DSNIUNDO PI12327
DSNUADP1 PI12327
DSNUCASA PI12327
DSNUMSGE PI12327
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI12327 DSNFUDRE DSNICMT1 DSNICMT2 DSNIRCSR DSNISEGD DSNIUNDO
DSNUADP1 DSNUCASA DSNUMSGE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFUDRE
DSNICMT1
DSNICMT2
DSNIRCSR
DSNISEGD
DSNIUNDO
DSNUADP1
DSNUCASA
DSNUMSGE
LISTEND
UI21468 COVER LETTER END
UI21494 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18635 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER TOCOPY of nonpartitioned *
* indexes. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU524I and RC8 during a RECOVER *
* INDEXSPACE DSNUM n TOCOPY of a multi- *
* piece nonpartitioned index (NPI) with *
* FlashCopy image copies (FCIC). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A RECOVER utility job specifying the TOCOPY option and DSNUM n
for one piece of a multi-piece nonpartitioned index (NPI)
failed with MSGDSNU524I when the TOCOPY data set specified
was a FlashCopy Image Copy.
DSNU524I -ssid ddd hh:mm:ss.hs DSNUCAIN - INVALID DATA SET OR
PARTITION NUMBER n SPECIFIED FOR INDEXSPACE dbname.ixspname
DSNUM is not allowed for a nonpartitioned index.
Recovery of the entire index is required. When a FlashCopy
image copy is made of an NPI, one FlashCopy data set is made
for each target object data set. If a FlashCopy is to be
used for a later RECOVER TOCOPY job, each piece of an NPI
needs to be recovered separately by using DSNUM n with the
respective FlashCopy data set specified.
RECOVER TOCOPY is changed to allow the use of DSNUM n
for an NPI if the TOCOPY data set is a FlashCopy image
copy. Message DSNU524I will no longer be issued.
It is strongly recommended that all pieces of any
nonpartitioned object be kept in sync at all times. If
1 recovery to a prior point is needed, all pieces should be
recovered to the same logical point in time, regardless of
the type of recovery base or which point-in-time keywords
are preferred.
The DB2 Utilities Guide will be updated to reflect the changes
made by this APAR and to clarify the conditions under which
DSNUM n may or may not be specified for RECOVER utility.
Specifically, the following footnote is added to the RECOVER
utility syntax diagram for the DSNUM option that can be
specified with TOCOPY:
| DSNUM integer is not valid for nonpartitioned indexes
| unless the data set that is specified for TOCOPY is a
| FlashCopy image copy.
To support the proper placement of this footnote, portions of
the RECOVER utility syntax diagram are restructured. These
documentation changes are listed for reference:
>>-RECOVER------------------------------------------------->
>--+-+-LIST--listdef-name-----------+-list-options-spec-+-->
| | .--------------------------. | |
| | V .-DSNUM--ALL--------. | | |
| '--obj.+---------------------+-' |
| '-DSNUM--integer----' |
| +-recover-options-spec-------------------------------+
'-object--PAGE--page-number--+----------+------------'
'-CONTINUE-'
.-LOGRANGES--YES----.
>--+-------+--+--------------+--+-------------------+-----><
'-CLONE-' +-LOCALSITE----+ | |
'-RECOVERYSITE-' '-LOGRANGES--NO-----'
...
recover-options-spec:
| .-DSNUM--ALL-------------.
| >>-object--+------------------------+---------------------->
| | (1) |
| '-DSNUM--integer---------'
>--+-TOCOPY--data-set-- ...
|
+-TOLASTCOPY-- ...
|
+-TOLASTFULLCOPY-- ...
|
'-ERROR--RANGE-- ...
1 Also under RECOVER utility, a portion of the explanation of the
DSNUM keyword is modIFIED AS FOLLOWS:
Identifies a partition within a partitioned table space or
a partitioned index, or identifies a data set within a
nonpartitioned table space that is to be recovered.
| You cannot specify a logical partition of a nonpartitioned
| index.
| You cannot specify a single data set of a nonpartitioned
| index unless the data set that is specified for TOCOPY
| is a FlashCopy image copy. However, to ensure consistency,
| all data sets of a nonpartitioned index should be recovered
| to the same point in time.
Alternatively, the option can recover the entire table space
or index space.
...
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18635
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
The fix for APAR PI18635 changes RECOVER utility to allow
the use of DSNUM n in the case where TOCOPY is used, the
target object is a single piece of a nonpartitioned index
(NPI), and the specified copy data set is a FlashCopy image
copy.
The DB2 Utilities Guide will be updated to reflect the changes
made by this APAR and to clarify the conditions under which
DSNUM n may or may not be specified for RECOVER utility.
Specifically, the following footnote is added to the RECOVER
utility syntax diagram for the DSNUM option that can be
specified with TOCOPY:
| DSNUM integer is not valid for nonpartitioned indexes
| unless the data set that is specified for TOCOPY is a
| FlashCopy image copy.
To support the proper placement of this footnote, portions of
the RECOVER utility syntax diagram are restructured. These
documentation changes are listed for reference:
>>-RECOVER------------------------------------------------->
>--+-+-LIST--listdef-name-----------+-list-options-spec-+-->
| | .--------------------------. | |
| | V .-DSNUM--ALL--------. | | |
| '--obj.+---------------------+-' |
| '-DSNUM--integer----' |
| +-recover-options-spec-------------------------------+
'-object--PAGE--page-number--+----------+------------'
'-CONTINUE-'
.-LOGRANGES--YES----.
1 >--+-------+--+--------------+--+-------------------+-----><
'-CLONE-' +-LOCALSITE----+ | |
'-RECOVERYSITE-' '-LOGRANGES--NO-----'
...
recover-options-spec:
| .-DSNUM--ALL-------------.
| >>-object--+------------------------+---------------------->
| | (1) |
| '-DSNUM--integer---------'
>--+-TOCOPY--data-set-- ...
|
+-TOLASTCOPY-- ...
|
+-TOLASTFULLCOPY-- ...
|
'-ERROR--RANGE-- ...
Also under RECOVER utility, a portion of the explanation of the
DSNUM keyword is modified as follows:
Identifies a partition within a partitioned table space or
a partitioned index, or identifies a data set within a
nonpartitioned table space that is to be recovered.
| You cannot specify a logical partition of a nonpartitioned
| index.
| You cannot specify a single data set of a nonpartitioned
| index unless the data set that is specified for TOCOPY
| is a FlashCopy image copy. However, to ensure consistency,
| all data sets of a nonpartitioned index should be recovered
| to the same point in time.
Alternatively, the option can recover the entire table space
or index space.
...
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCAIN PI18635
DSNUCASA PI18635
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18635 DSNUCAIN DSNUCASA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCAIN
DSNUCASA
LISTEND
UI21494 COVER LETTER END
1UI21511 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22378 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* that contains residual join predicates and *
* inner table of the join is direct index *
* access. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIOST2:5002 *
* may occur when a user issues a query *
* that satisfies the conditions below: *
* *
* 1. The query contains residual join *
* predicates. *
* 2. The inner table of the join is *
* direct index access. *
* 3. columns from inner table all *
* belongs to the index keys. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C90101 in DSNIOST2:5002 may occur for a query
that satisfies the conditions below:
1. The query contains residual join predicates.
2. The inner table of the join is direct index access.
3. columns from inner table all belongs to the index keys.
For example,
SELECT B.C1
FROM A, B
WHERE A.C1 = ?
AND A.C2 = INTEGER(B.C2)
Index IX(C1, C2) is chosen on table B
The join sequence is A joins Table B. The residual join
predicate A.C2 = INTEGER(B.C2) is applied at inner table B.
The columns B.C1 and B.C2 on inner table B are all the
index keys of IX.
ADDITIONAL KEYWORDS:
ABEND04E RC00C90101 SQLJOIN INDEXPROBING
The problems mentioned above are fixed so that DB2 will not
abend in that situation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22378
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI22378:
See PI22378 APAR/PTF text for additional information about
1 why a REBIND is necessary.
PI22378 corrects a problem ABEND04E RC00C90101 when the query
contains residual join predicates. When the predicate is
applied, the columns from inner table are the index keys of a
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
DSNXORES PI22378
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22378 DSNXORES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORES
LISTEND
UI21511 COVER LETTER END
UI21563 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18028 -
****************************************************************
* USERS AFFECTED: All DB2 Version 10 / 11 for z/OS using the *
* TRUNCATE statement operates on classic *
* segmented or Universal Table space *
****************************************************************
* PROBLEM DESCRIPTION: High get page count during the *
* space search after TRUNCATE statement *
* operates on classic Segmented or *
* Universal Table space *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the exhaustive search for insert, if the page false
lead count is exceeded after a few pages are searched within
the space map page, the algorithm will search more pages before
moving on to the next step. The segment chain of the last data
page within the space map page is the anchor point of the
next set of data pages to be searched. The high get page
count occurs when the segment chain within the space map
is not in physical acceding sequence. As a result,
the same set of segments will be searched repeatedly when the
process continues to exceed the data false lead count and
further leads to a high get page count.
The possible cause for the segment chain being out of physical
sequence is Truncate or mass delete.
DB2 code is modified to limit the search of the same set
1 of data pages to no more than 2 times.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18028
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 PI18028
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18028 DSNISGSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGSC
LISTEND
UI21563 COVER LETTER END
UI21565 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21134 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the MODIFY STATISTICS utility. *
****************************************************************
* PROBLEM DESCRIPTION: The MODIFY STATISTICS utility failed *
* when run on a user-defined index on *
* a DB2 catalog table. The user-defined *
* index did exist but MODIFY STATISTICS *
* failed with RC8 and the following *
* DSNU104I message being issued: *
* *
* DSNU1014I DSNUGMAP - INDEXSPACE *
* DSNDB06.SYSDBAUT NOT FOUND *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A user-defined index called SYSDBAUTH was created on the
SYSDBAUTH catalog table in DB2 10 for z/OS. When created, this
index had a SYSINDEXES.INDEXSPACE column value of 'SYSDBAUT'
which came from DB2 using the first eight characters of the
index name.
This 'SYSDBAUT' index space name is identical to a catalog table
space name that existed until it was dropped during the
DB2 10 for z/OS ENFM process.
The MODIFY STATISTICS INDEXSPACE utility was run specifying
the 'SYSDBAUT' INDEXSPACE name. DB2 utility processing tried
to validate that the index space name exists. Since it was an
index on a DB2 catalog object we first tried to validate the
name using internal catalog object name tables. DB2 utility
1 processing found a match on the 'SYSDBAUT' name but the entry
located was for the dropped SYSDBAUT table space and not the
user-defined index whose index space name was also 'SYSDBAUT'.
Since the entry located was not for an index space the
MODIFY STATISTICS INDEXSPACE utility incorrectly determined
that the index space did not exist and it failed with a RC8
with the following DSNU1014I message appearing in the job
output:
DSNU1014I -DB2A DSNUGMAP - INDEXSPACE DSNDB06.SYSDBAUT
NOT FOUND
Additional keyword: MSGDSNU1014I
DB2 CREATE INDEX code has been modified so that user-defined
indexes on DB2 catalog tables will not be given index space
names that are the same as other DB2 object names.
If indexes already exist where the index space names match
another catalog object name then do the following:
1 - Apply the PTF for this APAR.
2 - Drop the index.
3 - Recreate the index. This will create the same index with an
index space name that doesn't conflict with any other
catalog object name.
While the reported problem involved the MODIFY STATISTICS
INDEXSPACE utility, other utilities that take index space
names as input would also have problems similar to the
reported failure.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21134
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
DB2 will not allow catalog index names to be different from
their index space names.
Applying this APAR/PTF will not change any index spaces names
created incorrectly if customer already have migrated to
DB2 V10. Please run the following query to identify which
catalog index spaces names do not match their catalog index name
SELECT NAME, CREATOR, TBNAME, INDEXSPACE, DBID, OBID
FROM
SYSIBM.SYSINDEXES
WHERE
NAME ¬= INDEXSPACE AND
DBID = 6 AND
1 (OBID NOT BETWEEN 400 AND 599 AND
OBID NOT BETWEEN 900 AND 1699)
If the above query returns rows, you should contact IBM
support for further assistance.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICX3 PI21134
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21134 DSNXICX3
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICX3
LISTEND
UI21565 COVER LETTER END
UI21622 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM77754 -
****************************************************************
* USERS AFFECTED: All DB2 V10 NFM users of the DB2 *
* LOAD REPLACE/REORG utility and/or hash table *
* spaces. *
****************************************************************
* PROBLEM DESCRIPTION: While running DB2 utility, DB2 *
* encounters an 04E-00C90101 abend such *
* as the following: *
* DB2A,ABND=04E-00C90101,U=SYSADM, *
* M=N ,C=111.DM-DSNIHDFM,M=DSNTFRCV, *
* LOC=DSNIDM .DSNIFOD :500B *
****************************************************************
* RECOMMENDATION: If last physical page is not in the part *
* that is being processed, and the hash *
* space may be in the previous partition, *
* then DB2 may abend. *
****************************************************************
Each existing partition is being processed to format hash home
page during the pageset format phase of LOAD REPLACE/REORG
utility. When DB2 processes the partition that is beyond the
last physical hash home page, 04E-00C90101 abend can be
encountered when formatting hash home page beyond designated
hash space.
DB2 code is changed to have a proper interface between pageset
format process and LOAD REPLACE/REORG utility to process up to
the partition that covers the last physical hash home page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM77754
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
DSNIFOD PM77754
DSNUGRST PM77754
DSNURFIT PM77754
DSNURRST PM77754
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM77754 DSNIFOD DSNUGRST DSNURFIT DSNURRST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFOD
DSNUGRST
DSNURFIT
DSNURRST
LISTEND
UI21622 COVER LETTER END
UI21655 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25578 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and all DB2 11 for z/OS *
* users of the RECOVER utility. *
****************************************************************
* PROBLEM DESCRIPTION: Adding serviceability for the RECOVER *
* utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Adding serviceability for the RECOVER utility.
Added serviceability for the RECOVER utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25578
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCATM PI25578
DSNUCBDR PI25578
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25578 DSNUCATM DSNUCBDR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCATM
DSNUCBDR
LISTEND
UI21655 COVER LETTER END
1
UI21703 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22231 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of ALTER TRUSTED CONTEXT statement. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXIATX P097 *
* on V11 or an ABEND0C4 RC00000038 at *
* DSNXIATX OFFSET 3930 on V10 may occur *
* when executing an ALTER TRUSTED CONTEXT *
* context-name REPLACE USE FOR statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXIATX P097 on V11 or an ABEND0C4
RC00000038 at DSNXIATX OFFSET 3930 on V10 may occur when
executing an ALTER TRUSTED CONTEXT context-name REPLACE USE FOR
statement. When evaluating the attributes of REPLACE USE FOR
clause, DB2 does not process it correctly. The failing symptoms
may not be limited to those described here, others may also
occur.
Following is an example of such failing scenario:
CREATE TRUSTED CONTEXT MYCONTEXT
BASED UPON CONNECTION USING SYSTEM AUTHID ADMF001
ATTRIBUTES ( JOBNAME 'ABCDEFG' )
WITH USE FOR ADMF001 ;
ALTER TRUSTED CONTEXT MYCONTEXT
REPLACE USE FOR ADMF001;
DB2 is modified to process the attribute of REPLACE USE FOR
clause correctly.
Additional Keywords: ABEND04E RC00E70005
ABEND0C4 RC00000038
SQLALTER SQLTRUSTED
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22231
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIATX PI22231
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22231 DSNXIATX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIATX
1
LISTEND
UI21703 COVER LETTER END
UI21712 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23177 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOB and parallelism. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXORLI P001 *
* may occur when a query contains a LOB *
* column and the LOB defined length is *
* greater than 32767 ('7FFF'x) running in *
* parallel. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXORLI P001 may occur when a query
contains a LOB column and the LOB defined length is greater than
32767 ('7FFF'x) running in parallel. When DB2 calculate the
buffer length of this LOB column, it does not calculate it
correctly.
Following is an example of such failing query:
SELECT (CASE WHEN TM.COL_VCHAR IS NOT NULL
THEN TM.COL_VCHAR
ELSE TB.COL_LOB1) AS REMARK
FROM TM LEFT OUTER JOIN TB
ON TM.ID = TB.ID
WHERE CREATE_DATE BETWEEN '2013-01-01' AND '2013-12-31'
;
NOTE: COL_LOB1 is defined as CLOB(512000)
DB2 is modified to calculate the LOB column defined length
correctly for the parallelism.
Additional Keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K
SQLLOB ABEND04E RC00E70005
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23177
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM90902:
See PM90902 APAR/PTF text for additional information about
why a REBIND is necessary.
PM90902 corrects a problem of a SQLCODE -180 is issued when a
query contains a scalar function in the selection list which is
also be referenced in ORDER BY clause running on parallel.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM81200:
See PM81200 APAR/PTF text for additional information about
why a REBIND is necessary.
PM81200 corrects a problem of ABEND04E RC00C90101 at
DSNIBNRF:5007 when a query's selection list contains a scalar
full-select item participated in arithmetic calculation 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 PI23177:
See PI23177 APAR/PTF text for additional information about
why a REBIND is necessary.
PI23177 corrects a problem an ABEND04E RC00E70005 at DSNXORLI
P001 may occur when a query contains a LOB column and its
defined length is greater than 32767 ('7FFF'x) running in
parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCON PI23177
DSNXOGRL PI23177
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23177 DSNXOCON DSNXOGRL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCON
DSNXOGRL
LISTEND
UI21712 COVER LETTER END
UI21770 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24175 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of the *
1 * PACK function with a numeric or varying *
* length column argument. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC00000004 at location *
* DSNXGRDS DSNXOBFF OFFSETAC44 may occur *
* when a statement contains the PACK *
* function and the data type of one *
* argument of the PACK function is *
* VARCHAR, SMALLINT, INTEGER, BIGINT, *
* FLOAT(4), DECIMAL, or VARBINARY. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create TABLE T1.
CREATE TABLE T1(
C1 INTEGER,
C2 DECIMAL(1,0),
C3 FLOAT(4)
);
Step 2. SELECT statement with PACK function.
SELECT PACK(CCSID 1208, C1, C2, C3) FROM T1;
DB2 does not process the PACK function properly which can
result in the ABEND.
DB2 has been modified to correctly process the PACK function
with a numeric or varying length column argument.
Additional keywords: SQLFUNCTION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24175
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI22793:
See PI22793 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22793 corrects a problem that incorrect output could happen
for an SQL statement containing a function VARCHAR_FORMAT on a
FOR BIT DATA column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBFA PI24175
DSNXOBFF PI24175
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24175 DSNXOBFA DSNXOBFF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBFA
DSNXOBFF
LISTEND
UI21770 COVER LETTER END
UI21797 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21510 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE PART SORTNPSI YES *
* or REORG INDEX SHRLEVEL NONE *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect TOTALENTRIES value in *
* SYSIBM.SYSINDEXSPACESTATS after a REORG *
* TABLESPACE PART SORTNPSI YES or REORG *
* INDEX SHRLEVEL NONE *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
After user runs a REORG TABLESPACE PART SORTNPSI YES on a large
table space or a REORG INDEX SHRLEVEL NONE on a large index, the
value of TOTALENTRIES column in SYSIBM.SYSINDEXSPACESTATS can
get truncated because an internal variable that holds the number
of index keys reloaded can overflow during Real-time statistics
(RTS) processing.
DB2 RTS code has been modified to avoid overflow on number of
index keys reloaded during REORG.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21510
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKLOD2 PI21510
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21510 DSNKLOD2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKLOD2
1
LISTEND
UI21797 COVER LETTER END
UI21804 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24500 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: The IFCID 256 IFCID256 trace is not *
* always written when group buffer pool *
* attributes are modified via the *
* -ALTER GROUPBUFFERPOOL command. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The -ALTER GROUPBUFFERPOOL command logic incorrectly restricts
the writing of the IFCID 256 trace to only those commands which
modify the RATIO attribute.
The -ALTER GROUPBUFFERPOOL command code has been modified to
write the IFCID 256 trace record regardless of which attributes
were modified.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24500
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1AGB PI24500
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24500 DSNB1AGB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1AGB
LISTEND
UI21804 COVER LETTER END
UI21817 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22487 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of none *
* segmented table space in data sharing *
* environment. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNISMRT *
* ERQUAL 0C04 during insert execution. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
In data sharing environment, insert from one DB2 member against
a non segmented table space picked up a candidate page, but some
concurrent transaction from another DB2 member might use the
same page as system page or dictionary page.
After the inserter detected the inconsistency later, the
forementioned ABEND happened.
DB2 code has been modified to do further page type check to
eliminate the window. If the candidate page is found to be
system page or dictionary page, DB2 will skip the page and
search for another one.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22487
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISMRT PI22487
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22487 DSNISMRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISMRT
LISTEND
UI21817 COVER LETTER END
UI21822 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23064 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of SQL *
* statement containing RID() function and *
* tables which may be rewritten by MQTs *
* (Materialized Query Table). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND 04E00E2000F at location DSNXOXM. *
* DSNSVSFB OFFSET08EA may occur when *
* a SQL statement satisfies all of *
* following conditions: *
* 1. RID() function is used; *
* 2. MQT rewrite is effective. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND 04E00E2000F at location DSNXOXM.DSNSVSFB OFFSET08EA may
occur when an SQL statement satisfies all of the following
conditions:
1. RID() function is used;
2. MQT rewrite is effective.
1
The following example helps to illustrate this problem.
DDL:
CREATE TABLE TAB1(C1 INT, C2 CHAR(5));
CREATE TABLE TAB2(C1 INT, C2 CHAR(5));
CREATE TABLE MQT_1 AS
(SELECT C1, C2
FROM TAB2
WHERE C1 > 0)
DATA INITIALLY DEFERRED
REFRESH DEFERRED
MAINTAINED BY USER;
UPDATE SYSIBM.SYSTABLES
SET CARD = 100000, CARDF = 100000,
NPAGES = 10000, NPAGESF = 10000
WHERE NAME = 'MQT_1';
SQL:
SET CURRENT MAINTAINED TYPES = ALL;
SET CURRENT REFRESH AGE = ANY;
SELECT RID(A), A.C1
FROM TAB1 AS A
WHERE A.C2 IN (SELECT B.C2
FROM TAB2 AS B
WHERE B.C1 > 5)
ORDER BY 1, 2;
Note that, table TAB2 could be rewritten by table: MQT_1.
DB2 didn't process the RID() function with MQT correctly and
caused ABEND.
DB2 code is modified correctly to process RID() function used in
conjunction with MQT.
Additional keywords: SQLMQT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23064
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOXCP PI23064
DSNXOXM PI23064
DSNXOXRS PI23064
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23064 DSNXOXCP DSNXOXM DSNXOXRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOXCP
DSNXOXM
DSNXOXRS
1 LISTEND
UI21822 COVER LETTER END
UI21878 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23308 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG utility *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability for REORG utility. *
****************************************************************
* RECOMMENDATION: Apply PTF when available. *
****************************************************************
Serviceability for REORG utility.
Serviceability for REORG utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23308
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 PI23308
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23308 DSNURLOG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURLOG
LISTEND
UI21878 COVER LETTER END
UI21891 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20953 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users of DGTT tables. *
****************************************************************
* PROBLEM DESCRIPTION: Users of Declared Global Temporary *
* Tables that perform a mass delete *
* operation then followed by SQL *
* INSERT and ON COMMIT DELETE sequence in *
* their application, may see high logging *
* rates and space usage for the DB2 work *
* files. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For Declared Global Temporary Tables, DB2 has to allow for any
rollback after a MASS DELETE operation. As a result, the DB2
1 code has stringent selection criteria for obtaining a new
candidate segment for an SQL INSERT operation.
The following application sequence which should not be too
common, can lead to excessive logging and space utilization.
- the DGTT is declared with ON COMMIT DELETE ROWS
- the application code begins with a Mass DELETE from table
- small number of INSERTs are done into the DGTT
- COMMIT
- this application sequence is then run for a very large
number of INSERTs.
Candidate segment entries were disqualified to allow for
any rollback after any mass delete operation.
DB2 code has now been changed to reuse any qualifying segment
entries that are not part of the mass delete process for the
current unit of work.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20953
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 PI20953
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20953 DSNISGNS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGNS
LISTEND
UI21891 COVER LETTER END
UI21894 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21796 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* DB2 10 and DB2 11 for z/OS only. *
****************************************************************
* PROBLEM DESCRIPTION: The following problems are reported: *
* o Abend 04E-00E2000C *
* DSNLZMON.DSNSVSVB+0AD8 associated to *
* the (GR4) 'DDIS Agent Storage Pool' *
* storage pool. *
* o Under certain DB2/DDF hopping cases, *
* the requested MONITORRD may not be *
* returned to a remote requester. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 The following problems are reported:
o Under some conditions, DB2/DDF fails to free DRDA MONITORRD
related storage. This leads to a memory leak and over time
results in abend 04E-00E2000C DSNLZMON.DSNSVSVB+0AD8 where
GR4 refers to a 'DDIS Agent Storage Pool' storage pool.
o Under some DB2/DDF hopping cases, a DRDA Monitor request
received from a remote requester is not forwarded (hopped)
to a remote server. This prevents a DRDA MONITORRD from
being returned to the remote requester as it expects.
DB2 is changed as follows:
o The DRDA MONITORRD related storage will be freed after its
use is complete.
o The Monitor request is now forwarded to the remote server.
As a result, a DRDA MONITORRD is now returned to the remote
requester as expected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21796
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLZHC1 PI21796
DSNLZRTM PI21796
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21796 DSNLZHC1 DSNLZRTM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLZHC1
DSNLZRTM
LISTEND
UI21894 COVER LETTER END
UI21904 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20632 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who run *
* IFCID 22 *
****************************************************************
* PROBLEM DESCRIPTION: PLANNAME in IFCID 22 can sometimes be *
* displayed in Unicode instead of EBCDIC *
* when DB2 subsystem parameter UIFCIDS *
* is set to YES *
****************************************************************
* RECOMMENDATION: *
****************************************************************
PLANNAME (QW0022PN) in the IFCID 22 trace record can sometimes
be displayed in Unicode instead of EBCDIC when UIFCIDS=YES.
QW0022PN should be displayed in EBCDIC regardless of the
1 value of subsystem parameter UIFCIDS.
Additional Keywords:
IFCID22 IFCID022
Code is changed to display QW0022PN in EBCDIC regardless of the
value of UIFCIDS. However, as before, if a conversion error
occurs and the field cannot be displayed in EBCDIC, then the
field will be displayed unconverted. A new flag QW0022ER
will be turned on if the conversion error occurs indicating
that QW0022PN is being displayed in Unicode.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20632
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
IFCID 22 is updated to include a new flag QW0022ER to indicate
if existing field QW0022PN (plan name or package name) is
displayed in Unicode instead of EBCDIC. If a CCSID
translation error occurs for QW0022PN, QW0022ER will be
turned on to indicate QW0022PN is in Unicode.
The new field is added under flags QW0022FG:
. . .
QW0022FG DS XL1 FLAGS
QW0022HT EQU X'80' 1 IF OPTIMIZATION HINTS WERE USED
QW0022ER EQU X'40' 1 IF CONVERSION ERROR ON QW0022PN
AND QW0022PN IS IN UNICODE
. . .
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQW00 PI20632
DSNXOTR1 PI20632
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20632 DSNDQW00 DSNXOTR1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTR1
MACROS
DSNDQW00
LISTEND
UI21904 COVER LETTER END
UI21961 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24730 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of BIND QUERY *
****************************************************************
* PROBLEM DESCRIPTION: BIND QUERY removes rows from SYSQUERY *
1 * tables for the wrong package when *
* HINT_SCOPE=1 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When BIND QUERY processes input from DSN_USERQUERY_TABLE it
should replace any matching rows from SYSQUERY tables before
inserting the new SYSQUERY information. When BIND QUERY is
determining whether the current row should be deleted for the
case with DSN_USERQUERY_TABLE.HINT_SCOPE=1, checking of the
package name is incorrectly skipped. This can cause a
SYSQUERY row for a different package to be incorrectly
removed. This problem will only occur if a SYSQUERY row
exists with the same schema, collection, version, and SQL text
as the new DSN_USERQUERY_TABLE row.
Additional Keywords:
BINDQUERY
DB2 code has been changed to avoid incorrectly removing
rows from SYSQUERY tables on BIND QUERY.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24730
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOIQY PI24730
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24730 DSNXOIQY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOIQY
LISTEND
UI21961 COVER LETTER END
UI21988 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI15555 -
****************************************************************
* USERS AFFECTED: All users of utilities on DB2 10 for z/OS *
* and DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: The COPY utility abended with ABEND04E *
* RC00E40022 RC00C90088 after *
* encountering a deadlock condition *
* between locks on two DSNDB01.SYSUTILX *
* pages. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 When multiple utility jobs are executing at the same time, it
is possible for the jobs to get into a deadlock situation
between SYSUTILX page locks due to pseudo-deleted index
entries in index SYSIBM.DSNLUX02.
The customer was executing multiple COPY utility jobs at
the same time and one of the COPY jobs abended with ABEND04E
RC00E40022 RC00C90088 after deadlocking with another job.
The console syslog showed these messages:
DSNT375I PLAN=DSNUTIL WITH
CORRELATION-ID=job-name1
CONNECTION-ID=UTILITY
IS DEADLOCKED WITH PLAN=DSNUTIL WITH
CORRELATION-ID=job-name2
CONNECTION-ID=UTILITY
ON MEMBER memid
DSNT500I DSNUGRAR RESOURCE UNAVAILABLE
REASON 00C90088
TYPE 0000302
NAME DSNDB01.SYSUTILX.X'00004A'
This problem can occur for any combination of utility jobs
not just COPY jobs.
Additional keywords: MSGDSNT375I MSGDSNT500I TYPE302
The utility logic which updates information in SYSUTILX
has been modified to decrease the chances of encountering
deadlocks on SYSUTILX pages when multiple utilities are
executing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI15555
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKFTCH PI15555
DSNKNXT2 PI15555
DSNUGAGS PI15555
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI15555 DSNKFTCH DSNKNXT2 DSNUGAGS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKFTCH
DSNKNXT2
DSNUGAGS
LISTEND
UI21988 COVER LETTER END
UI22011 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22121 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
1 * users of the DSNACCOX stored procedure. *
****************************************************************
* PROBLEM DESCRIPTION: DSNACCOX utility stored procedure does *
* not recommend a REORG for a table space *
* when REORGCLUSTERSENS is NULL. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
DB2 10 for z/OS included the addition of column REORGCLUSTERSENS
to SYSIBM.SYSTABLESPACESTATS. The value of REORGCLUSTERSENS in
SYSTABLESPACESTATS was set to NULL for all existing rows. The
utility stored procedure DSNACCOX incorporates this new column
when recommending a REORG. However, DSNACCOX was not accounting
for a NULL value for REORGCLUSTERSENS so tables with a NULL
value were never selected for a REORG.
Utility stored procedure DSNACCOX has been modified to tolerate
a NULL value for column REORGCLUSTERSENS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22121
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM90617:
See PM90617 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM90617:
(a)STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b)Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
DB2BIND:
***Action for PM88775:
See PM88775 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM88775:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
DB2BIND:
***Action for PI06664:
See PI06664 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PI06664:
(a)STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b)Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
DOCUMENTATION:
PM74794 introduces the following changes to the DB2 10 for z/OS
Utility Guide and Reference -
1 Appendix B. DB2-supplied stored procedures for utility
operations
Section - DSNACCOX stored procedure
Chapter - DSNACCOX output
Table 145 - Result set row for second DSNACCOX result set
| NAME VARCHAR(128) Table space name, index name, or
| index space name. Index space
| name is used if the row is added
| as a result of checking a
| restricted state and the index
| name is not available at the time.
Information about this changed information will be
included in the Information Management Software for z/OS
Solutions Information Center
(http://publib.boulder.ibm.com/infocenter/imzic) at a later
date.
ACTION:
***Action for PM90617:
See PM90617 APAR/PTF text for additional information.
After applying the fix for PM90617, DSNACCOX will reverse
the recommendation based on percentage criterion on an
object with TOTALROWS or TOTALENTRIES of zero. If TOTALROWS
or TOTALENTRIES is zero, we now rely on the related absolute
criteria.
ACTION:
***Action for PM74794:
See PM74794 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM74794:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this is
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
ACTION:
After you apply the PTF for APAR PM61574, Non Partitioned Index
is no longer recommended for reorg or runstats when chklevel
32 is specified and any of the ts partitioned is recommended for
reorg or runstats.
ACTION:
***Action for PI22121:
See PI22121 APAR/PTF text for additional information.
The package for DSNACCOX SQL statement support needs to be bound
after applying the fix for APAR PI22121.
An example of how to do this is:
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
1 ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
ACTION:
The package for DSNACCOX needs to be bound after applying the
fix for APAR PI15366. An example of how to do this is:
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
ACTION:
PLEASE NOTE:
After applying the fix for APAR PI06664, DSNACCOX will reverse
the recommendation based on percentage criterion on the object
with TOTALROWS or TOTALENTRIES of zero. If the TOTALROWS or
TOTALENTRIES is zero, we now rely on the related absolute
criteria.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@CCOX PI22121
DSNACCOX PI22121
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22121 DSN@CCOX DSNACCOX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNACCOX
MACROS
DSN@CCOX
LISTEND
UI22011 COVER LETTER END
UI22013 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24985 -
****************************************************************
* USERS AFFECTED: All DB2 users of plan authorization cache. *
****************************************************************
* PROBLEM DESCRIPTION: User may receive ABEND0C4 *
* RC00000038 DSNTGSCC DSNTAUTH +03B6 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When plan authorization cache is used, DB2 could access null
address pointer which results in the above abend.
DB2 code has been changed to check for a null pointer
before referencing it.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI24985
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTAUTH PI24985
DSNXARU2 PI24985
DSNXEAAL PI24985
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24985 DSNTAUTH DSNXARU2 DSNXEAAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTAUTH
DSNXARU2
DSNXEAAL
LISTEND
UI22013 COVER LETTER END
UI22067 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23400 -
****************************************************************
* USERS AFFECTED: All DB2 V10 and V11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 will issue a new message DSNY028I *
* and terminate with an ABEND04E *
* RC00E80163 if an incompatible level of *
* ERLY code is being used with the DB2 *
* subsystem that is starting. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 will issue a new message DSNY028I and terminate with an
ABEND04E RC00E80163 if an incompatible level of ERLY code is
being used.
DB2 is compatible with the previous, current and next version
of ERLY code. DB2 V10 is an exception, in that it is
compatible with ERLY V8, V9, V10 and V11.
The support provided in this APAR will start with DB2 V10
checking whether the ERLY code is V10 or V11. Starting with
DB2 V11, each version of DB2 will check whether the ERLY code
is the previous, current, or next version of ERLY code.
MSGDSNY028I
RC00E80163 RSN00E80163
.
DB2 for z/OS Messages and DB2 for z/OS Codes with be updated
with the following text for message DSNY028I and reason code
00E80163.
.
1 DSNY028I
csect-name DB2 version ERLY CODE IS NOT COMPATIBLE WITH THIS
RELEASE OF DB2
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
csect-name
The name of the control section that issued the message.
version
The version of the ERLY code.
.
System action
DB2 startup abnormally terminates with reason code 00E800163.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
.
00E80163
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
System action
DB2 startup abnormally terminates.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
DB2 has been updated to issue a new message DSNY028I if an
incompatible level of ERLY code is being used with the DB2
subsystem that is starting.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23400
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DOCUMENTATION:
DB2 will issue a new message DSNY028I and terminate with an
ABEND04E RC00E80163 if the DB2 subsystem is being started
with an incompatible level of DB2 ERLY code.
.
DSNY028I
csect-name DB2 version ERLY CODE IS NOT COMPATIBLE WITH THIS
RELEASE OF DB2
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
csect-name
The name of the control section that issued the message.
version
The version of the ERLY code.
.
System action
DB2 startup abnormally terminates with reason code 00E800163.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
.
00E80163
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
System action
DB2 startup abnormally terminates.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
DOCUMENTATION:
DB2 will issue a new message DSNY028I and terminate with an
ABEND04E RC00E80163 if the DB2 subsystem is being started
with an incompatible level of DB2 ERLY code.
1 .
DSNY028I
csect-name DB2 version ERLY CODE IS NOT COMPATIBLE WITH THIS
RELEASE OF DB2
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
csect-name
The name of the control section that issued the message.
version
The version of the ERLY code.
.
System action
DB2 startup abnormally terminates with reason code 00E800163.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you re specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
.
00E80163
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
System action
DB2 startup abnormally terminates.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you re specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNYASCP PI23400
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23400 DSNYASCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNYASCP
LISTEND
UI22067 COVER LETTER END
UI22080 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25905 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* customers who use the stored procedure *
* SYSPROC.ADMIN_INFO_SQL or the batch program *
* DSNADMSB to collect DB2 environmental *
* service data. *
****************************************************************
* PROBLEM DESCRIPTION: After executing the DDL statements *
* generated by ADMIN_INFO_SQL or *
* DSNADMSB for the RTS table *
* SYSINDEXSPACESTATS, only the data for *
* the last partition of a partitioned *
* index is recreated. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ADMIN_INFO_SQL and DSNADMSB are not recreating the
SYSINDEXSPACESTATS data for the first n-1 partitions of a
partitioned index, where n is the number of partitions for the
index. They deleted all the rows for the first n-1 partitions
that were inserted right before.
ADMIN_INFO_SQL and DSNADMSB are modified to delete all the rows
in the RTS table SYSINDEXSPACESTATS that are related to a
partitioned index only once, right before the data for the
partitions of the index are inserted.
ADDITIONAL KEYWORDS:
SQLSP SQLSTOREDPROC ADMININFOSQL SQLSTATS DSNADMSB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25905
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM94681 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede the instructions for any previous PTF on
ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
1 ---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS.After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
DB2BIND:
***Action for PI25905 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
DB2BIND:
***Action for PI21058 (DB2 10 for z/OS)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
1 (1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates program module DSNADMSS and the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to bind
the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
ACTION:
***Action for PI07646 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede any previous PTF instructions.
If you have already installed or migrated to DB2 V10, you need
to take the following action after applying this PTF:
---------------------------------------------------------------
Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMSS PI25905
DSNADMSS PI25905
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25905 DSN@DMSS DSNADMSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMSS
MACROS
DSN@DMSS
LISTEND
UI22080 COVER LETTER END
UI22093 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI10830 -
****************************************************************
* USERS AFFECTED: All Users of DB2 Restore System Utility. *
****************************************************************
* PROBLEM DESCRIPTION: (1) Abend04e RC00c2010e in *
* dsnidm.dsnb1lpl+18f8 during Restore *
* System Log apply. (2) Abend0c4-00000038 *
* in dsnidm.dsnicmt2+7fba during Restore *
* System log apply. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
(1) During restore system log apply, if opening the data set
fails, log apply logic is to put the page into LPL. However, the
log range provided for the LPL pages is not calculated
correctly. This results in abend in csect DSNB1LPL while adding
pages into LPL in the DBET. (2) During restore system log apply,
Data Manager (DM) performs periodic commit. This commit will
update a Recovery Base Log Point (RBLP) in DBD01 header page.
Starting in DB2 z/OS for V10, DBD01 is defined as Partition by
Growth (PBG). However, during the opening of DBD01, all the
internal attributes required for the PBG is not set up
correctly. This results in abend while locating Data Versioning
(DVO) control block during Commit processing. The DM log apply
logic is changed so that DBD01 will be correctly marked as PBG
object when it is opened for update.
DB2 Restore System log apply is changed to avoid failure when
marking objects in LPL and avoid DBD01 failure during commit
processing after the restore system log apply is completed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI10830
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
DSNIBMOC PI10830
DSNIRSTR PI10830
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI10830 DSNIBMOC DSNIRSTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBMOC
DSNIRSTR
LISTEND
UI22093 COVER LETTER END
UI22144 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23252 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement whose SELECT list contains an *
* EXISTS subquery with SELECT DISTINCT. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E72048 at location *
* DSNXGRDS DSNXSORI OFFSET5718 (for V10) *
* or OFFSET6996 (for V11) could happen *
* when executing an SQL statement that *
* satisfies all of the following *
* conditions. ABEND0C4 RC00000038 at *
* location DSNXGRDS DSNXOD8 OFFSET1F3A *
* (for V10) or OFFSET1F5A (for V11) could *
* happen when doing EXPLAIN for an SQL *
* statement that satisfies all of the *
* following conditions. *
* *
* 1. It contains a CASE expression in the *
* SELECT list. *
* 2. The CASE expression contains an *
* EXISTS subquery in the WHEN clause. *
* 3. The EXISTS subquery contains a table *
* expression with SELECT DISTINCT. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1 (
C1 VARCHAR(10)
,C2 VARCHAR(10)
);
SELECT
CASE WHEN EXISTS
(SELECT *
1 FROM (SELECT DISTINCT C1, C2
FROM T1) TX
)
THEN 1
ELSE 2
END
FROM SYSIBM.SYSDUMMY1
;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLCASE SQLWHEN SQLEXISTS SQLTABLEEXPR
SQLSUBQUERY SQLDISTINCT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23252
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI23252:
See PI23252 APAR/PTF text for additional information about
why a REBIND is necessary.
PI23252 corrects following problems:
ABEND04E RC00E72048 at location DSNXGRDS DSNXSORI OFFSET5718
(for V10) or OFFSET6996 (for V11) could happen when executing an
SQL statement that satisfies all of the following conditions.
ABEND0C4 RC00000038 at location DSNXGRDS DSNXOD8 OFFSET1F3A (for
V10) or OFFSET1F5A (for V11) could happen when doing EXPLAIN for
an SQL statement that satisfies all of the following conditions.
1. It contains a CASE expression in the SELECT list.
2. The CASE expression contains an EXISTS subquery in the WHEN
clause.
3. The EXISTS subquery contains a table expression with SELECT
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEXT PI23252
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23252 DSNXOEXT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNXOEXT
LISTEND
UI22144 COVER LETTER END
UI22183 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25076 -
****************************************************************
* USERS AFFECTED: DB2 users of external stored procedures *
* and User Defined Functions (UDFs) with *
* ASUTIME LIMIT specified. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE905 message displays an *
* incorrect value for CPU SECONDS *
* LIMIT. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The CPU SECONDS LIMIT is calculated from the ASUTIME LIMIT
specified in the Create Procedure statement. When it is
converted to the printable EBCDIC value, the conversion
is incorrect and results in the wrong value that is displayed
in the SQLCODE905 message.
DB2 code is modified so that correct value can be calculated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25076
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9TIM PI25076
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25076 DSNX9TIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9TIM
LISTEND
UI22183 COVER LETTER END
UI22195 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI08409 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of range list access *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may select an inefficient access *
* path for a query with a predicate on *
1 * a timestamp column when a range list *
* access path would be more efficient. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may incorrectly select an inefficient access path for a
static query when a more efficient range list access path
(ACCESSTYPE='NR') exists. This problem can occur when a
predicate eligible for index matching or index screening in a
range list leg references a timestamp column. For example,
SELECT COUNT(*)
FROM T1
WHERE C1 > :HV1
OR (C1 = :HV1
AND TIMESTAMP_COL > :HV2)
Index IX1 (C1,TIMESTAMP_COL)
This query should be eligible for a range list access path
matching on index IX1, but a range list access path will not
be selected without this APAR due to the presence of timestamp
column TIMESTAMP_COL in the last predicate.
If the query were prepared dynamically the efficient range list
access path would be chosen.
For DB2 10 only, zparm PGRNGSCR must be set to YES in order
to obtain the more efficient range list access path for static
queries. The PGRNGSCR zparm doesn't exist in DB2 11. DB2 11
always has the PGRNGSCR=YES behavior.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE RANGELIST SQLRANGELIST SQLTIMESTAMP
DB2 code has been corrected so that the presence of a predicate
on a timestamp column does not preclude a range list access
path.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI08409
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI19010:
See PI19010 APAR/PTF text for additional information about
why a REBIND is necessary.
PI19010 corrects a problem of ABEND0C4 RC00E70005 at location
DSNXRRP OFFSETM110 can occur for an SQL statement that contains
an after join or during join predicate which contains a
timestamp column and a string host variable.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
1 DB2BIND:
***Action for PI11756:
See PI11756 APAR/PTF text for additional information about
why a REBIND is necessary.
PI11756 corrects a problem of 'less rows than expected' were
inserted for an offloaded IBM DB2 Analytics Accelerator
'INSERT from SELECT' stetement.
To make this fix effective for a static application, it must 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 PI08409:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI08409 corrects a problem in which an inefficient access path
may be selected by DB2 when a range list access path
(ACCESSTYPE='NR') would be more efficient.
To make this fix effective for a static application, zparm
PGRNGSCR must be set to YES and the application rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, applications could be affected by this
change.
MULTSYS:
PI08409 is an enabling APAR. In a data sharing group,
pre-conditioning APAR PI16179 must be applied to all members
before the enabling APAR (PI08409) is applied to any member.
The code change is not enabled until the enabling APAR PI08409
is applied.
PI08409 corrects a problem of performance regression for static
SQL queries when an inefficient access path is selected and a
more efficient range list access path exists. The problem
can occur when a predicate eligible for index matching or
index screening in a range list leg references a timestamp
column.
ACTION:
***Action for PI08409:
ZPARM PGRNGSCR must be set to YES to enable the fix in this
APAR.
PI08409 corrects a problem in which an inefficient access path
may be selected by DB2 when a range list access path
(ACCESSTYPE='NR') would be more efficient.
To make this fix effective for a static application, zparm
PGRNGSCR must be set to YES and the application rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, applications could be affected by this
change.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRTM PI08409
DSNXGSFN PI08409
DSNXOGOR PI08409
DSNXOW2C PI08409
DSNXOW2D PI08409
DSNXRBND PI08409
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI08409 DSNXGRTM DSNXGSFN DSNXOGOR DSNXOW2C DSNXOW2D DSNXRBND
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGRTM
DSNXGSFN
DSNXOGOR
DSNXOW2C
DSNXOW2D
DSNXRBND
LISTEND
UI22195 COVER LETTER END
UI22197 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20555 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC/CLI and DB2 Version 11 for z/OS *
* ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: The ODBC driver currently utilizes a *
* process level mutex to protect data *
* areas shared across multiple LE *
* threads. When running a highly *
* threaded ODBC application, contention *
* for this mutex can become a bottleneck *
* as more threads are competing for the *
* same source, thus causing performance *
* degradation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Certain ODBC data objects, such as the connection and statement
handles, are allocated from a global storage area that is
shared across multiple threads. The ODBC driver uses a process
level mutex to guarantee serialized access to this shared
storage area, but the mutex can become highly contended when
a large number of threads are spawned.
Code has been changed to make the mutex latching more
selective, allowing more concurrent thread use of the APIs
at the connection and statement levels.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI20555
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC03 PI20555
DSNAOC1U PI20555
DSNAOG03 PI20555
DSNAOG08 PI20555
DSNAOG0A PI20555
DSNAOG1Q PI20555
DSNAOG0E PI20555
DSNAOG0J PI20555
DSNAOG0O PI20555
DSNAOG17 PI20555
DSNAOG1U PI20555
DSNAOCLI PI20555
DSNAOSDK PI20555
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20555 DSNAOC03 DSNAOC1U DSNAOG03 DSNAOG08 DSNAOG0A DSNAOG1Q
DSNAOG0E DSNAOG0J DSNAOG0O DSNAOG17 DSNAOG1U DSNAOCLI
DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC03
DSNAOC1U
DSNAOG03
DSNAOG08
DSNAOG0A
DSNAOG1Q
DSNAOG0E
DSNAOG0J
DSNAOG0O
DSNAOG17
DSNAOG1U
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI22197 COVER LETTER END
UI22236 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24101 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of DSN1SMFP utility. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSN1404I or MSGDSN1406I issued or *
* ABENDS0C1 when running DSN1SMFP to *
1 * format DB2 audit trace. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following problems can happen when running DSN1SMFP:
1. DSN1SMFP ends with RC8 and the following message is issued in
the end of job report when IFCID140 trace data does not
include any SQL statement:
DSN1404I DSN1SMFP ERROR: INPUT RECORD 0000000772 (SMF TYPE
102, IFCID TYPE 00140) WAS PROCESSED WITH WARNINGS
2. The following message can be issued in the report of IFCID145
if the trace data was written by a system with ZPARM
UIFCIDS=YES:
DSN1406I DSN1SMFP ERROR: AN UNEXPECTED RETURN CODE OF
0000000008 WAS RECEIVED DURING CONVERSION OF DATA
FROM UNICODE TO EBCDIC
3. DSN1SMFP can ABEND0C1 when processing trace data from
a DB2 system with ZPARM setting UIFCIDS=YES.
DSN1SMFP utility has been modified to correct the aforementioned
problems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24101
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN1SMFP PI24101
HDBAA10J PI24101
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24101 DSN1SMFP HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN1SMFP
LISTEND
UI22236 COVER LETTER END
UI22271 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26982 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users gathering STATISTICS on an index *
* on expression using RUNSTATS or inline *
* STATISTICS. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect AVGKEYLEN in SYSINDEXES and *
* SYSINDEXPART for an XML NODE ID index *
1 * running RUNSTATS. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A RUNSTATS utility was run on a table with an XML column.
The AVGKEYLEN in SYSIBM.SYSINDEXES and SYSIBM.SYSINDEXPART
was incorrect, often showing a negative or very large value.
RUNSTATS was using a variable in the calculation of AVGKEYLEN
which represented the number of VARBIN columns in the NODEID
index but the variable was not set.
This problem can occur for any Index on Expression (IOE) and
can occur during inline STATISTICS (LOAD, REORG, REBUILD INDEX).
RUNSTATS was modified to fix the aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26982
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSIIX PI26982
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26982 DSNUSIIX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSIIX
LISTEND
UI22271 COVER LETTER END
UI22273 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24860 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the REORG utility with the *
* KEEPDICTIONARY option. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIZLDR:5002 *
* during REORG KEEPDICTIONARY utility *
* after an ALTER TABLESPACE BUFFERPOOL *
* is run. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An ALTER TABLESPACE BUFFERPOOL BP1 was run against a compressed
table space. A subsequent REORG TABLESPACE KEEPDICTIONARY
utility was run, but failed with ABEND04E RC00C90101 ERQUAL5002.
When REORG is materializing a pending ALTER which changes the
BUFFERPOOL size, a new dictionary should be built.
REORG code has been modified to ignore the KEEPDICTIONARY
1 option when an ALTER TABLESPACE BUFFERPOOL change is
pending and will build a new dictionary.
This change will be documented in the Utility Guide and
Reference manual, under the REORG utility, the KEEPDICTIONARY
option:
Possible reasons for not specifying KEEPDICTIONARY are:
| If REORG is materializing a pending alter of the buffer
| pool, REORG builds a new dictionary. DB2 ignores the
| KEEPDICTIONARY option if REORG is materializing a
| buffer pool change.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24860
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
See PI24860 APAR/PTF text for additional information.
PI24860 has modified the REORG utility to ignore the
KEEPDICTIONARY option when an ALTER TABLESPACE BUFFERPOOL
change is pending and instead, REORG will build a new
dictionary.
This change will be documented in the Utility Guide and
Reference manual, under the REORG utility, the KEEPDICTIONARY
option:
Possible reasons for not specifying KEEPDICTIONARY are:
| If REORG is materializing a pending alter of the buffer
| pool, REORG builds a new dictionary. DB2 ignores the
| KEEPDICTIONARY option if REORG is materializing a
| buffer pool change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGPAL PI24860
DSNURFIT PI24860
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24860 DSNUGPAL DSNURFIT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGPAL
DSNURFIT
LISTEND
UI22273 COVER LETTER END
UI22319 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI22831 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: Code analysis has found that a zero *
* pointer could be used in some code *
* paths. However, no problems have been *
* reported resulting from it. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Code analysis has found that there are some cases where a zero
pointer could be used to reference storage. However, no
problems have been reported resulting from it but this could
cause an abend or other unpredictable results.
DB2 code has been modified to check pointer before using it to
reference storage. This will help prevent unexpected abends or
possibly unpredictable results.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22831
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXSR PI22831
DSNLZRPA PI22831
DSNLZR00 PI22831
DSNLZS00 PI22831
DSNT1SRQ PI22831
DSNXGMRG PI22831
DSNXGRTS PI22831
DSNXGSFN PI22831
DSNXGTRE PI22831
DSNXSWFM PI22831
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22831 DSNLXSR DSNLZRPA DSNLZR00 DSNLZS00 DSNT1SRQ DSNXGMRG
DSNXGRTS DSNXGSFN DSNXGTRE DSNXSWFM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXSR
DSNLZRPA
DSNLZR00
DSNLZS00
DSNT1SRQ
DSNXGMRG
DSNXGRTS
DSNXGSFN
DSNXGTRE
DSNXSWFM
LISTEND
UI22319 COVER LETTER END
1
UI22335 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21015 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* who use IFCID 269 trace in UNICODE. *
****************************************************************
* PROBLEM DESCRIPTION: IFCID 269 trace records contained *
* an invalid length for the SYSTEM *
* AUTHID used to establish a trusted *
* connection when tracing in UNICODE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When tracing IFCID 269 in UNICODE the length of the SYSTEM
AUTHID used to establish the trusted connection was invalid.
This is because DB2 did not set the length correctly when
writing the trace record.
Code has been changed such that when the SYSTEM AUTHID used to
establish the trusted connection is copied over to the trace
field, the length is set correctly.
ADDITIONAL KEYWORDS:
SQLTRUSTED IFCID269
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21015
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXATIM PI21015
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21015 DSNXATIM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXATIM
LISTEND
UI22335 COVER LETTER END
UI22337 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI17176 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* who bind plans and packages in a trusted *
* connection. *
****************************************************************
* PROBLEM DESCRIPTION: Ownership record in SYSIBM.SYSPLANAUTH *
1 * and SYSIBM.SYSPACKAUTH may not be *
* updated correctly when a plan or *
* package whose owner is a role is *
* rebound in a non-trusted connection. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a plan or package whose owner is a role is rebound in a
non-trusted connection where the new owner is an
authorization ID with the same name as the role, then the
ownership record in SYSPLANAUTH / SYSPACKAUTH table is not
updated correctly. This is because DB2 did not consider the
authorization ID type when making the updates.
The problem can also occur if the original plan/package owner
is an authorization ID and the plan/package is rebound in a
trusted connection with role as object owner and the role name
is the same as the owner authorization ID.
Code has been changed to consider the authorization ID type
when updating the ownership record in SYSPLANAUTH / SYSPACKAUTH
in the above scenarios.
ADDITIONAL KEYWORDS:
SQLTRUSTED
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI17176
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBCM1 PI17176
DSNTBCM2 PI17176
DSNTBRB PI17176
DSNTBRB2 PI17176
DSNXA04 PI17176
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI17176 DSNTBCM1 DSNTBCM2 DSNTBRB DSNTBRB2 DSNXA04
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBCM1
DSNTBCM2
DSNTBRB
DSNTBRB2
DSNXA04
LISTEND
UI22337 COVER LETTER END
UI22341 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20676 -
1 ****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users who run a *
* REBIND PACKAGE command *
****************************************************************
* PROBLEM DESCRIPTION: When a package is bound with the option *
* SQLERROR(CONTINUE) successfully, the *
* subsequent REBIND of the same package *
* fails with some SQL error. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a package is bound with the option SQLERROR(CONTINUE), the
subsequent REBIND of the same package fails with some SQL error.
The root cause is the REBIND code doesn't pick up the value of
SQLERROR from the catalog table.
Code has been changed so the REBIND process can pick up the
value of SQLERROR from the catalog table and the REBIND runs
successfully.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20676
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTBRB2 PI20676
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20676 DSNTBRB2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTBRB2
LISTEND
UI22341 COVER LETTER END
UI22349 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23275 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER utility *
****************************************************************
* PROBLEM DESCRIPTION: Endless loop during RECOVER TOLOGPOINT *
* of a segmented table space when system- *
* level backup (SLB) was used as recover *
* base. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran RECOVER TOLOGPOINT to recover a segmented table space
1 to a point in the log that was prior to the time when the first
table was created in the table space. The RECOVER utility chose
an SLB as the recover base for the object and the object was
restored successfully, but the utility began looping after
LOGAPPLY phase, in the UTILTERM phase.
The problem occurs when an SLB is used by RECOVER and the data
copy pool definition has a capture catalog attribute of 'R'
(required) or 'P' (preferred). It is due to an incorrectly set
flag, which can cause a loop when building the first segment
chain for the segmented table space.
RECOVER utility has been modified to work correctly when an SLB
is used as a recovery base for TOLOGPOINT.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23275
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 PI23275
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23275 DSNUCALA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCALA
LISTEND
UI22349 COVER LETTER END
UI22351 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23276 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD SPANNED YES. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E4D5D2 DSNUGSTB + '1B34'x *
* during a LOAD SPANNED YES utility with *
* SYSDISC directed to SYSOUT *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
ABEND04E RC00E4D5D2 at DSNUGSTB OFFSET1B34 occurred when user
ran a LOAD SPANNED YES with SYSDISC specified as DD SYSOUT=*.
SYSDISC datasets should have the same DCB characteristics as
SYSREC datasets, so directing SYSDISC to SYSOUT is not allowed,
MSGDSNU034I should be issued in this case.
LOAD SPANNED YES has been modified to issue message DSNU034I and
abend with reason code RC00E40070 when SYSDISC is directed to
SYSOUT and the SYSREC data set has LRECL=32768 or greater.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23276
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURILD PI23276
DSNURPPL PI23276
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23276 DSNURILD DSNURPPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURILD
DSNURPPL
LISTEND
UI22351 COVER LETTER END
UI22450 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24425 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users with queries containing *
* nested ANDs and ORs. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 may occur in DSNXGRDS.DSNXOGCM *
* for a query with nested ANDs and ORs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If DB2 is unable to obtain storage for costing of a multi-index
access path, DB2 will abandon the multi-index access path choice
and free all related storage. For a query with nested ANDs and
ORs, DB2 might incorrectly continue costing the multi-index
access path choice after the related storage has been freed.
This may lead to an ABEND0C4 at various locations in
DSNXGRDS.DSNXOGCM.
Since the ABEND0C4 occurs based on reference to freed storage,
this problem may be intermittent depending on the contents
of the freed storage.
Additional Keywords:
SQLOR SQLSTORAGE
DB2 code has been fixed to correctly terminate multi-index
costing once a storage limit has been hit and multi-index
costing related storage has been freed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24425
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
DSNXOGCM PI24425
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24425 DSNXOGCM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGCM
LISTEND
UI22450 COVER LETTER END
UI22470 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25728 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the DB2 scheduler for *
* administrative tasks. *
****************************************************************
* PROBLEM DESCRIPTION: When a triggering task (e.g., task A) *
* is updated, the scheduler incorrectly *
* schedules the task that is normally *
* triggered by task A for immediate *
* execution, although the triggering *
* task was not executing when the update *
* was performed. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
The scheduler is incorrectly scheduling a triggered task
for immediate execution when its triggering task is updated
and the triggering task is not executing during the update.
The scheduler is modified to not schedule a triggered task
for immediate execution when its triggering task is updated
and the triggering task is not executing during the update.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25728
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
After applying this PTF on DB2 10 for z/OS
==========================================
The following post-apply actions are required of all current
V10 customers that use the DB2 scheduler.
To activate the changes in this PTF you need to take the
following additional actions:
(1) Stop the scheduler for administrative tasks.
1 (2) Start the scheduler for administrative tasks.
Each of these actions is detailed below.
(1) Stop the scheduler for administrative tasks.
If the scheduler is running, stop it first by executing
the following console command:
MODIFY DSNADMT,APPL=SHUTDOWN
where DSNADMT is the name of the scheduler.
(2) Start the scheduler for administrative tasks.
Start the scheduler by executing the following console
command:
START DSNADMT
where DSNADMT is the name of the scheduler.
ACTION:
***Action for PI25728 (DB2 10 for z/OS)
This PTF modifies the DB2 scheduler for administrative tasks
so that when a triggering task is updated while it is not
executing, the scheduler will not automatically schedule its
triggered task for immediate execution.
Post-apply actions for this PTF:
--------------------------------
If you have already installed or migrated to DB2 10 for z/OS
then after applying this PTF you need to take the following
actions after applying this PTF:
(1) Stop the DB2 scheduler for administrative tasks.
(2) Start the DB2 scheduler for administrative tasks.
These actions are detailed below.
----------------------------------------------------------------
(1) Stop the DB2 scheduler for administrative tasks.
***********************************************************
* This action is required for all DB2 10 customers who use
* the DB2 scheduler for administrative tasks, i.e., the
* DSN6SPRM.ADMTPROC subsystem parameter setting is not
* null (in which case it specifies the name of the
* scheduler).
***********************************************************
If the DB2 scheduler is running, stop it first by executing
the following console command:
MODIFY DSNADMT,APPL=SHUTDOWN
where DSNADMT is the name of the scheduler.
----------------------------------------------------------------
(2) Start the DB2 scheduler for administrative tasks.
***********************************************************
* This action is required for all DB2 10 customers who use
* the DB2 scheduler for administrative tasks, i.e., the
* DSN6SPRM.ADMTPROC subsystem parameter setting is not
* null (in which case it specifies the name of the
* scheduler).
***********************************************************
To start the DB2 scheduler again, execute the following
console command:
1 START DSNADMT
where DSNADMT is the name of the scheduler.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNA6SCH PI25728
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25728 DSNA6SCH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNA6SCH
LISTEND
UI22470 COVER LETTER END
UI22482 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18897 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and DB2 11 for *
* z/OS of ODBC/CLI or the CLI Driver *
* provided with DB2 for Linux, Unix, and *
* Windows version 8 and above that connect to *
* DB2 10 for z/OS or DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: When JDBC method getTables() or ODBC *
* function SQLTables() is called, new *
* table type 'ACCEL-ONLY TABLE' that was *
* added starting from DB2 10 for z/OS *
* is still reported as 'TABLE' in *
* TABLE_TYPE column of the returned *
* result set. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR *
****************************************************************
The metadata stored procedure, SYSIBM.SQLTables, is used when
a JDBC application calls getTables() or an ODBC application
calls SQLTables(). The TABLE_TYPE column in the returned result
set still reports new table type 'ACCEL-ONLY TABLE' as 'TABLE'.
SYSIBM.SQLTables may also return extra rows in the result set
when multiple table types, other than 'TABLE', are specified for
getTables() and SQLTables().
Metadata procedure SYSIBM.SQLTables enables new function to
report extended table type information which includes one new
table type and 4 new columns. When users enable the new
function through the JDBC or ODBC driver, the result set
returned from SYSIBM.SQLTables will report the new table type
'ACCEL-ONLY TABLE' in TABLE_TYPE column. The 4 new columns
added at the end of current existing columns are
TEMPORAL_TABLE_TYPE, IS_ACCELERATED, ACCEL_ARCHIVE_STATUS,
and IS_ARCHIVE_ENABLED. Column IS_ARCHIVE_ENABLED is only
supported from DB2 z/OS V11.
Additional changes have been made in SYSIBM.SQLTables metadata
1 procedure to return correct result set when multiple table
types are specified.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18897
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI19131 (DB2 10)
This APAR modifies DSNTRIN, the installation and configuration
tool for DB2-supplied stored procedures and user-defined
functions (UDFs), to correct invalid syntax in the generated
create statement for the SYSTOOLS.REGSP stored procedure. It
also modifies DSNTRIN to detect and alter existing instances
of SYSTOOLS.REGSP that are defined with the error.
If you have already installed or migrated to DB2 10, you need to
run your copy of job DSNTIJRT with MODE(INSTALL) to check for
and correct problems with the SYSTOOLS.REGSP stored procedure.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
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 modifies Database Metadata(DBMD) stored procedure
SYSIBM.SQLTables, as follows:
* Support new keyword EXTENDEDTABLEINFO = 0|1. Default value
is 0.
* Report 'ACCEL-ONLY TABLE' in TABLE_TYPE .
* 3 new columns are appended at the end of current result set.
(1) TEMPORAL_TABLE_TYPE VARCHAR(11)
Valid values: 'SYSTEM'|'APPLICATION'| 'BITEMPORAL'|''
(2) IS_ACCELERATED VARCHAR(3)
Valid values: 'YES'|'NO'
(3) ACCEL_ARCHIVE_STATUS CHAR(1)
Valid values: 'A'|'B'|'C'|X'|''
It also modifies SYSIBM.SQLTABLETYPES, a table used by stored
procedure SYSIBM.SQLTables, as follows:
* A new column, IS_EXTENDEDTYPE, is added. It is defined as
SMALLINT NOT NULL with DEFAULT 0.
* A new row, for TABLE_TYPE='ACCEL-ONLY TABLE' is added.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
1 If you have already installed or migrated to DB2 10 then,
you need to take the following actions after applying
this PTF:
Procedures for these actions are given below.
----------------------------------------------------------------
(1) Run installation job DSNTIJRT to alter SYSIBM.SQLTABLETYPES
and add the new column, insert the new row, then bind DBRM
DSNATBLU
==> This action is required for all V10 customers
Run your copy of job DSNTIJRT with MODE(INSTALL) to alter
SYSIBM.SQLTABLETYPES and add the new column, insert the new
row, and to bind the DBRM DSNATBLU and refresh the package
for DBMD stored procedure SYSIBM.SQLTABLES. Note: The
bind request for DSNATBLU will return warnings if the
SYSACCEL.SYSACCELERATEDTABLES does not exist on DB2.
This is expected if the DB2 does not use an accelerator
product.
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) REORG the DSNATPDB.DSNATPTS table space
==> This action is required for all V10 customers
Alteration of SYSIBM.SQLTABLETYPES by DSNTIJRT to add the
new column places the containing table space,
DSNATPDB.DSNATPTS, in Advisory REORG Pending (AREO*)
status. The table space is available but needs to be
reorganized for optimal performance. Therefore, run the
REORG TABLESPACE utility with SHRLEVEL CHANGE or SHRLEVEL
REFERENCE on the entire table space.
(3) Refresh the WLM environment
Issue the following VARY MVS command to refresh the WLM
application environment
VARY WLM,APPLENV=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application
environment in which the Database Metadata stored procedure
SYSIBM.SQLTables is running.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@RIN PI18897
DSN@TBLU PI18897
DSNATBLU PI18897
DSNTESR PI18897
DSNTRIN PI18897
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18897 DSN@RIN DSN@TBLU DSNATBLU DSNTESR DSNTRIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNATBLU
DSNTRIN
MACROS
DSN@RIN
DSN@TBLU
DSNTESR
LISTEND
UI22482 COVER LETTER END
UI22484 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21877 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of STOSPACE *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 RC10 at DSNUTSSA +x'4218' *
* occurs when running the STOSPACE *
* utility. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
STOSPACE was run covering all STOGROUPs and abended with an
ABEND0C4 RC10 at DSNUTSSA OFFSET4218. The abend occurred when
STOSPACE attempted to gather information from a data base
descriptor that had been deallocated.
STOSPACE code has been changed to fix the aforementioned
problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21877
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUTSSA PI21877
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21877 DSNUTSSA
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUTSSA
LISTEND
UI22484 COVER LETTER END
UI22529 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27014 -
****************************************************************
* USERS AFFECTED: All users of DB2 MQI user-defined-functions *
* DB2 10 for z/OS and DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Calling the UDF DB2MQ.MQRECEIVEALLCLOB *
* with 2 VARCHAR parameters returns *
* SQLCODE -444. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
The DB2MQ.MQRECEIVEALLCLOB UDF has multiple signatures, each
distinguished by the number and type of parameters passed. Each
signature executes using a different alias of module DSNMQUDF in
the SDSNLOAD library. Currently, the signature that accepts
two VARCHAR parameters fails with SQLCODE -444 because its
alias, DSN2XC2, is not defined in SDSNLOAD.
To fix the problem, the alias 'DSN2XC2' is added to the JCLIN
for the DSNMQUDF module in DB2 10 for z/OS and DB2 11 for z/OS.
All the users of DB2 MQI user-define-functions need to apply
this APAR so they can execute the UDF DB2MQ.MQRECEIVEALLCLOB
with 2 VARCHAR parameters correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27014
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF updates DSNMQHLP, the DBRM for for the DB2 MQI
user-defined functions. After applying the PTF, all customers
should run installation job DSNTIJRT with MODE(INSTALL) to bind
a new version of package DSNMQUDF.DSNMQHLP. 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.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@QHLP PI27014
DSNMQUDF PI27014
HDBAA10J PI27014
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27014 DSN@QHLP DSNMQUDF HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNMQUDF
MACROS
DSN@QHLP
LISTEND
UI22529 COVER LETTER END
UI22578 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI06843 -
****************************************************************
* USERS AFFECTED: All DB2 10 & 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ADMF Local BCT subpool was at maximum *
* size and additional storage requests *
* recieved RSN00E20004. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There was a storage constraint in the ADMF local BCT
subpool, where DBET storage occupied most of the subpool.
Because of this, not all of the DBET entries could be
processed. Moving the DBET storage in ADMF local BCT
subpool to its own above the bar pool will alleviate
the storage constraint.
DBET storage will now be acquired from ADMF DBET CL20 subpool
above the bar. Additional storage can be allocated for must
complete agents when the pool is full to avoid a DB2 susbsystem
crash.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI06843
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
***Action for PM91547:
PM91547 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
1 Earlier, a pre-conditioning APAR PM69760 was delivered. In a
data sharing group, this 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 following APAR enables the fix for the problem of timeout by
SCA REBUILD when a concurrent mainline DBET updater happens to
be in the notify exit path.
MULTSYS:
***Action for PM74803:
PM74803 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
Earlier, a pre-conditioning APAR PM69760 was delivered. In a
data sharing group, this 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 following APAR enables the fix for the problem of timeout by
SCA REBUILD when a concurrent mainline DBET updater happens to
be in the notify exit path.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDADP PI06843
DSNGDVUT PI06843
DSNIBCUR PI06843
DSNIDBAB PI06843
DSNIDBAE PI06843
DSNIDBBD PI06843
DSNIDBDA PI06843
DSNIDBDF PI06843
DSNIDBDG PI06843
DSNIDBDM PI06843
DSNIDBDR PI06843
DSNIDBDS PI06843
DSNIDBDW PI06843
DSNIDBEL PI06843
DSNIDBFA PI06843
DSNIDBGC PI06843
DSNIDBGN PI06843
DSNIDBGR PI06843
DSNIDBHK PI06843
DSNIDBIN PI06843
DSNIDBLG PI06843
DSNIDBLK PI06843
DSNIDBMC PI06843
DSNIDBMF PI06843
DSNIDBMG PI06843
DSNIDBMS PI06843
DSNIDBNG PI06843
DSNIDBNI PI06843
DSNIDBNW PI06843
DSNIDBPL PI06843
DSNIDBPX PI06843
DSNIDBRP PI06843
DSNIDBSE PI06843
DSNIDRCT PI06843
DSNILSTS PI06843
1 DSNIRTSX PI06843
DSNISREC PI06843
DSNSCON2 PI06843
DSNSVSVB PI06843
DSNTDINQ PI06843
DSNTDMST PI06843
DSNTSTRT PI06843
DSNUDISD PI06843
DSNUGSRX PI06843
DSNUGTE0 PI06843
DSNUKRDY PI06843
DSNURSWD PI06843
DSNURWT PI06843
DSNWDFDM PI06843
DSNXIENF PI06843
DSNXIRCO PI06843
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI06843 DSNGDADP DSNGDVUT DSNIBCUR DSNIDBAB DSNIDBAE DSNIDBBD
DSNIDBDA DSNIDBDF DSNIDBDG DSNIDBDM DSNIDBDR DSNIDBDS
DSNIDBDW DSNIDBEL DSNIDBFA DSNIDBGC DSNIDBGN DSNIDBGR
DSNIDBHK DSNIDBIN DSNIDBLG DSNIDBLK DSNIDBMC DSNIDBMF
DSNIDBMG DSNIDBMS DSNIDBNG DSNIDBNI DSNIDBNW DSNIDBPL
DSNIDBPX DSNIDBRP DSNIDBSE DSNIDRCT DSNILSTS DSNIRTSX
DSNISREC DSNSCON2 DSNSVSVB DSNTDINQ DSNTDMST DSNTSTRT
DSNUDISD DSNUGSRX DSNUGTE0 DSNUKRDY DSNURSWD DSNURWT
DSNWDFDM DSNXIENF DSNXIRCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDADP
DSNGDVUT
DSNIBCUR
DSNIDBAB
DSNIDBAE
DSNIDBBD
DSNIDBDA
DSNIDBDF
DSNIDBDG
DSNIDBDM
DSNIDBDR
DSNIDBDS
DSNIDBDW
DSNIDBEL
DSNIDBFA
DSNIDBGC
DSNIDBGN
DSNIDBGR
DSNIDBHK
DSNIDBIN
DSNIDBLG
DSNIDBLK
DSNIDBMC
DSNIDBMF
DSNIDBMG
1 DSNIDBMS
DSNIDBNG
DSNIDBNI
DSNIDBNW
DSNIDBPL
DSNIDBPX
DSNIDBRP
DSNIDBSE
DSNIDRCT
DSNILSTS
DSNIRTSX
DSNISREC
DSNSCON2
DSNSVSVB
DSNTDINQ
DSNTDMST
DSNTSTRT
DSNUDISD
DSNUGSRX
DSNUGTE0
DSNUKRDY
DSNURSWD
DSNURWT
DSNWDFDM
DSNXIENF
DSNXIRCO
LISTEND
UI22578 COVER LETTER END
UI22580 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21898 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of -DISPLAY DATABASE *
* command *
****************************************************************
* PROBLEM DESCRIPTION: 'NO SPACES FOUND' may be displayed *
* under msgDSNT397I when the spaces are *
* expected from -DISPLAY DATABASE *
* command. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a very rare case, a zero pointer may be used to address the
database display control block, causing SPACES not displayed.
The code is fixed to ensure that the display control block
exists before referencing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21898
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 DSNTDINQ PI21898
DSNTDMUL PI21898
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21898 DSNTDINQ DSNTDMUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDINQ
DSNTDMUL
LISTEND
UI22580 COVER LETTER END
UI22583 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24528 -
****************************************************************
* USERS AFFECTED: All DB2 11 for z/OS users of queries with *
* scrollable cursor and inline lob inside *
* scalar full select. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 AT DSNXOUWF:P010 *
* may occur for scrollable cursor when *
* select list contains a scalar *
* fullselect with inline lob column(s). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 AT DSNXOUWF:P010 may occur for scrollable
cursor when select list contains a scalar fullselect with inline
lob column(s).
An example for the error case is:
CREATE TABLE T6(C1 CLOB(10), C2 INT);
CREATE TABLE T7(C1 CLOB(10), C2 INT);
EXEC SQL DECLARE CS16A INSENSITIVE SCROLL CURSOR FOR
SELECT 1, (SELECT C1 FROM T6)
FROM T7;
The bindtime code in DB2 has been modified to correct the
conditions which can lead to the abend.
Additional Keywords: SQLLOB ABEND04E RC00C90101 SQLSCROLL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24528
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PM27871 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
1 APAR PM27871 corrects problems that can cause an incorrect
output for sensitive static scroll cursor when order by
DESC on a column that is not in the select list.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
See PI24528 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
Apar PI24528 corrects the conditions that can lead to the
occurrence of an ABEND04E RC00E70005 at location DSNXOUWF:P010
when executing a query scrollable cursor and inline lob.
To make this fix effective for a static application, it must 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
DSNXOUWF PI24528
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24528 DSNXOUWF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOUWF
LISTEND
UI22583 COVER LETTER END
UI22608 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24606 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD utility *
****************************************************************
* PROBLEM DESCRIPTION: Load utility serviceability *
****************************************************************
* RECOMMENDATION: Apply PTF when available *
****************************************************************
Load utility serviceability
Load utility serviceability
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24606
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 DSNUGSRX PI24606
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24606 DSNUGSRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGSRX
LISTEND
UI22608 COVER LETTER END
UI22638 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26411 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries that use multiple index access. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXRRID *
* ERQUALM104 can occur during the sorting *
* of RIDs if an error is encountered *
* when trying to acquire RIDMAP/RIDLIST *
* space which causes DB2 to use sort *
* storage (instead) which is not allowed *
* under certain circumstances. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXRRID ERQUALM104 can occur in DB2
when the sorting of RIDs encounters an error trying to acquire
RIDMAP/RIDLIST storage space, and then as a result, tries to use
existing sort storage which is not allowed under certain
circumstances.
So instead of abending, DB2 should return an SQLCODE error and
message to the user. That is, return an SQLCODE904 or -904
because there is no sort storage available (i.e. resource
unavailable).
DB2 has been modified to issue an SQLCODE -904 error and message
(resource unavailable) that no sort storage is available to
continue the operation.
Additional Keywords: SQLCODE904 SQLRID SQLSORT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26411
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 PI26411
1 DSNXSFIN PI26411
DSNXSFRT PI26411
DSNXSFUN PI26411
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26411 DSNXRRID DSNXSFIN DSNXSFRT DSNXSFUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRRID
DSNXSFIN
DSNXSFRT
DSNXSFUN
LISTEND
UI22638 COVER LETTER END
UI22651 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22964 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of queries with *
* equal predicates or IN predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may produce an inaccurate filter *
* factor estimation for an equal *
* predicate, an IN-list predicate or *
* an IN subquery predicate if index *
* probing is triggered. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may produce an inaccurate filter factor estimation for an
equal predicate, an IN-list predicate or an IN-subquery
predicate if index probing is triggered because the column
referenced by the predicate is the leading key of an index and
any of the below conditions is satisfied:
1. The table referenced by the predicate is a VOLATILE table;
2. The table's CARDF is less than the subsystem parameter
NPGTHRSH;
3. The table is empty according to statistics in DB2 catalog;
4. The qualified partitions are empty according to statistics
in the DB2 catalog.
Index probing is triggered only for dynamic queries or static
queries bound with REOPT(ALWAYS).
As a result of an inaccurate filter factor estimation, DB2 may
select an inefficient access path.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE INDEX PROBING FILTERFACTOR
DB2 code has been corrected to produce an accurate filter factor
1 estimation for the predicates described as above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22964
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODFE PI22964
DSNXODFT PI22964
DSNXOINQ PI22964
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22964 DSNXODFE DSNXODFT DSNXOINQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODFE
DSNXODFT
DSNXOINQ
LISTEND
UI22651 COVER LETTER END
UI22653 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24766 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement that contains a NOT NULL field *
* procedure column as an outer join column *
* when parallelism is enabled. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS DSNXORLI P010 could happen for *
* an SQL statement that contains a NOT *
* NULL field procedure column as an outer *
* join column when parallelism is *
* enabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1 (
C1 CHAR(10) NOT NULL FIELDPROC FPCVD4
,C2 CHAR(10)
);
CREATE TABLE T2 (
C1 CHAR(10) NOT NULL FIELDPROC FPCVD4
,C2 CHAR(10)
);
CREATE TABLE T3 (
C1 CHAR(10)
1 ,C2 CHAR(10)
);
SELECT T1.C1
FROM T1
LEFT OUTER JOIN T2
LEFT OUTER JOIN T3
ON T2.C2 = T3.C2
ON T1.C1 = T2.C1
;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLFIELDPROC SQLOUTERJOIN SQLFULLJOIN
SQLOUTER SQLFULL SQLJOIN SQLLEFTJOIN
SQLLEFT SQLRIGHTJOIN SQLRIGHT
PARALLELISM SQLPARALLELISM
DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24766
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCLP PI24766
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24766 DSNXOCLP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCLP
LISTEND
UI22653 COVER LETTER END
UI22677 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI11063 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOAD FORMAT SPANNED YES. *
****************************************************************
* PROBLEM DESCRIPTION: LOAD FORMAT SPANNED YES resulted in *
* ABEND0C4 RC00000004 DSNURWRF OFFSET104A *
* or *
* ABEND04E RC00E4D5D2 DSNURWRF OFFSET0E90 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 LOAD FORMAT SPANNED YES resulted in an abend when rows for
multiple tables were in SYSREC or when varying length fields
had invalid lengths.
Additional Keywords: ABENDS0C4 RC4 RC38 RC00000038
OFFSET116E +x'116E'
OFFSET10E6 +x'10E6'
OFFSET10E0 +x'10E0'
+x'104A'
+x'0E90'
Modified logic for LOAD FORMAT SPANNED YES to correctly process
rows from multiple tables in the same SYSREC and varying length
fields with invalid lengths.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI11063
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURWBG PI11063
DSNURWRF PI11063
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI11063 DSNURWBG DSNURWRF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURWBG
DSNURWRF
LISTEND
UI22677 COVER LETTER END
UI22693 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22125 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REORG REBALANCE when using *
* DATE=LOCAL in DSNHDECP *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40340 at DSNUDALT *
* +x'58F0' during REORG TABLESPACE *
* REBALANCE when DATE=LOCAL in DSNHDECP *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REORG TABLESPACE REBALANCE was run on a subsystem with
DATE=LOCAL defined in DSNHDECP. When attempting to update
SYSIBM.SYSTABLEPART with a new limitkey an invalid length was
used for the DATE which resulted in the ABEND04E RC00E40340 at
DSNUDALT OFFSET58F0.
REORG TABLESPACE REBALANCE code has been changed to use a proper
1 length of the DATE when DATE=LOCAL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22125
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM42922:
See PM37611 APAR/PTF text for additional information.
PM42922 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via PM37611. 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 enabling APAR, PM37611, is
applied. The new function is not enabled until PM37611 is
PM37611 removes the restriction and allows a timestamp with
time zone column in a partitioning key as long as it is the last
column in the partitioning key.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUDALT PI22125
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22125 DSNUDALT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUDALT
LISTEND
UI22693 COVER LETTER END
UI22701 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25347 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG utility. *
****************************************************************
* PROBLEM DESCRIPTION: REORG utility does not honor the new *
* DEADLINE value changed by ALTER UTILITY *
* command. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a REORG utility with DEADLINE parameter, and then
dynamically changed the parameter by using ALTER UTILITY with
option DEADLINE NONE, but the job still terminated with RC8 when
the old DEADLINE was met. The problem occurred when REORG was
running parallelism.
1 The problem happened because the subtasks were not checking for
an altered DEADLINE parameter correctly.
DB2 code has been modified to check the DEADLINE parameter
correctly when running parallelism.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25347
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGTCK PI25347
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25347 DSNUGTCK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGTCK
LISTEND
UI22701 COVER LETTER END
UI22703 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18675 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of Universal Table *
* Space (UTS) and Classic-Partitioned Table *
* Space *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIDBEL with *
* ERQUAL5222 during DBET Notify Exit *
* processing *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DBET Notify Exit processing, ABEND04E RC00C90101 in
DSNIDBEL with ERQUAL5222 may occur, where local DBET includes
a partition range with piece level information when processing
a large number of partitions in an exception state and some
or all of these partitions have piece level information on them.
The said problem is detected late in processing, making the
it difficult to diagnose the root cause.
Sevicability ABENDs have been added throughout DBET processing
to check if local DBET includes a partition range with piece
level information
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18675
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
DSNIDBAB PI18675
DSNIDBEL PI18675
DSNIDBMF PI18675
DSNIDBMS PI18675
DSNIDBSE PI18675
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18675 DSNIDBAB DSNIDBEL DSNIDBMF DSNIDBMS DSNIDBSE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBAB
DSNIDBEL
DSNIDBMF
DSNIDBMS
DSNIDBSE
LISTEND
UI22703 COVER LETTER END
UI22735 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27356 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN *
* ENFM processing job. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70006 DSNXIENF OFFSET256E *
* during DSNTIJEN job step ENFM0117. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
ENFM processing abended during the ENFM0117 step of the
DSNTIJEN job. ENFM0117 is an ENFM REORG step and it failed
during switch phase processing. The ENFM processing of the
SYSVIEWS catalog table space expects SYSVIEWS rows in the
SYSTABLES catalog table to have OBID column values that are
zero.
Most view rows have SYSTABLES.OBID column values that are
zero. But views that have INSTEAD OF triggers defined on them
will have non-zero SYSTABLES.OBID values.
In the reported problem the SYSTABLES.OBID column values for
views with SYSTABLES.TSNAME = 'SYSVIEWS' were non-zero and
because of that an incorrect code path was taken. This caused
the reported abend and failure of the ENFM process in step
ENFM0117:
ABND=04E-00E70006,LOC=DSNXIDDL.DSNXIENF+256E
Additional keywords: ABEND04E RC00E70006 DSNXIENF OFFSET256E
1 DB2MIGV10/K
ENFM processing code has been changed to properly handle view
records in SYSTABLES that have non-zero OBID values.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27356
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXIENF PI27356
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27356 DSNXIENF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXIENF
LISTEND
UI22735 COVER LETTER END
UI22766 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27501 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: A static SQL statement that contains *
* a predicate with a timestamp datatype *
* and a host variable is incorrectly *
* blocked from routing to an accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A static SQL statement that contains a predicate with a
timestamp datatype and a host variable is incorrectly
blocked from routing to an accelerator. EXPLAIN of the
statement will populate DSN_QUERYINFO_TABLE with REASON_CODE=15
and QI_DATA='(EXPR)'. If BIND option QUERYACCELERATION(ALL) or
GETACCELARCHIVE(YES) is used, SQLCODE -4742 reason code 15
is issued for the statement.
For example, the column C1 is a TIMESTAMP datatype:
DECLARE CURS01 WITH ROWSET POSITIONING FOR
SELECT MONTH
FROM T1
WHERE C1 > :HV WITH UR
END-EXEC
For static SQL queries that have been bound for acceleration
1 and have SQL statements similar to the above example, REBIND
the package for the failing query after applying this PTF.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLTIMESTAMP SQLCODE4742
DB2 code is fixed for expected results and behavior.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27501
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI27501:
See PI27501 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27501 corrects a problem for SQL query acceleration where
an SQL query is incorrectly blocked from routing to an
accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOEX1 PI27501
DSNXOOS1 PI27501
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27501 DSNXOEX1 DSNXOOS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOEX1
DSNXOOS1
LISTEND
UI22766 COVER LETTER END
UI22770 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26781 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users *
* in CM or ENFM mode. *
****************************************************************
* PROBLEM DESCRIPTION: When the Cursor Block (CUB) chain *
* is broken, DB2 may go into a endless *
* loop when creating a new CUB. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
For easy reference, DB2 keeps the CUB in different chains.
When deleting a CUB in CM/ENFM, DB2 didn't properly remove
it from all the chains. This could cause its next CUB pointer
points to itself and break the CUB chain in its internal Data
Base control block and then causes an endless loop on the next
create CUB call.
Fix made in DB2, when deleting a CUB in CM or ENFM, it'll now
properly remove it from all the chains, so it won't break the
CUB chain in its internal Data Base control block.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26781
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICUBC PI26781
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26781 DSNICUBC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICUBC
LISTEND
UI22770 COVER LETTER END
UI22775 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23932 -
****************************************************************
* USERS AFFECTED: All users of DSNTRVFY, the validation tool *
* for DB2-supplied stored procedures and *
* user-defined functions (UDFs) in DB2 10 *
* for z/OS and DB2 11 for z/OS, are affected *
* by this change. *
****************************************************************
* PROBLEM DESCRIPTION: One or more of the following errors *
* occurs when running job DSNTIJRV, job *
* step DSNTRVFY (program DSNTRVFY): *
* *
* (1) DSNTRVFY terminates with return *
* code 8 and these messages: *
* DSNT031I DSNTRVFY VALIDATION FOR *
* schema.routine FAILED *
* DSNT034I DSNTRVFY - AN ERROR WAS *
* ENCOUNTERED DURING CALL *
* TO ROUTINE, SQLCODE = *
* -204 *
* DSNT408I SQLCODE = -204, ERROR: *
* DSNTRVFY.VALIDATION_TABLE *
* IS AN UNDEFINED NAME *
1 * where schema.routine is one or more *
* of the following: *
* - DSNADM.ADMIN_TASK_LIST *
* - DSNADM.ADMIN_TASK_OUTPUT *
* - DSNADM.ADMIN_TASK_STATUS *
* - DSNADM.ADMIN_TASK_STATUSH *
* *
* (2) DSNTRVFY terminates with return *
* code 8 and these messages: *
* DSNT031I DSNTRVFY VALIDATION FOR *
* schema.routine FAILED *
* DSNT034I DSNTRVFY - AN ERROR WAS *
* ENCOUNTERED DURING CALL *
* TO ROUTINE, SQLCODE = *
* -180 *
* DSNT408I SQLCODE = -180, ERROR: *
* THE DATE, TIME, OR *
* TIMESTAMP VALUE *N IS *
* INVALID *
* where schema.routine is one or more *
* of the following: *
* - SYSPROC.ADMIN_TASK_ADD *
* - SYSPROC.ADMIN_TASK_UPDATE *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
Job DSNTIJRV executes program DSNTRVFY which can be used to
validate installation and configuration of DB2-supplied stored
procedures and UDFs. Currently, there are two problems that
can cause it to terminate with errors as described in the
problem description section:
(1) SQLCODE -204 because DSNTRVFY.VALIDATION_TABLE is
undefined
For validation of some DB2 administrative task scheduler
routines, DSNTRVFY creates a temporary table called
DSNTRVFY.VALIDATION_TABLE. Currently, DSNTRVFY does not
intercept and report errors creating that table at the
point where they occur. When DSNTRVFY subsequently
attempts to use the table, it receives the SQLCODE -204.
(2) SQLCODE -180 because DATE, TIME, or TIMESTAMP value is
invalid
For validation of some other DB2 administrative task
scheduler routines, DSNTRVFY uses a SELECT statement to
get the current timestamp from DB2. Currently, DSNTRVFY
does not report errors obtaining that timestamp at the
point where they occur. When DSNTRVFY subsequently
attempts to use the timestamp, it receives SQLCODE -180.
In response, this APAR corrects DSNTRVFY to intercept and report
errors creating DSNTRVFY.VALIDATION_TABLE and selecting the
current timestamp.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI23932
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@RVFY PI23932
DSNTRVFY PI23932
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23932 DSN@RVFY DSNTRVFY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTRVFY
MACROS
DSN@RVFY
LISTEND
UI22775 COVER LETTER END
UI22777 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23421 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of insert with *
* subselect statements using optimization *
* hints. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20029 at the location *
* DSNXOPTJ.DSNSVBK +1CE0 may occur when *
* binding/preparing an insert from *
* subselect statement with optimization *
* hints. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E20029 at the location DSNXOPTJ.DSNSVBK +1CE0 may
occur when binding/preparing an 'INSERT ... FROM subselect'
statement when all of the following conditions are satisfied:
1. Optimization hints are used;
2. There are duplicate rows in PLAN_TABLE matching the insert
query block;
3. The subselect contains a table expression, an outer join,
or UNION/UNION ALL.
DB2 may not be able to allocate sufficient storage for the
statement described as above to load the duplicate records and
may result in the ABEND.
Additional Keywords:
ABEND04E RC00E20029 DSNXOPTJ OFFSET1CE0 OPTHINT OPTHINTS SQLHINT
1 SQLINSWSELECT SQLUNION SQLUNIONALL SQLTABLEEXPR SQLOUTERJOIN
SQLFULLJOIN SQLOUTER DSNSVBK
DB2 code has been modified to correct the storage allocation
for the statements described to avoid the aforementioned ABEND.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23421
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPTJ PI23421
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23421 DSNXOPTJ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPTJ
LISTEND
UI22777 COVER LETTER END
UI22816 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21021 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* who are using, or plan to use, DB2 for z/OS *
* System Profile Monitoring (SPM) support. *
****************************************************************
* PROBLEM DESCRIPTION: An enhancement for monitoring idle *
* threads by using profiles is being *
* provided. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When remote client applications connect to a DB2 for z/OS (V10
or higher) server via TCP/IP, System Profile Monitoring (SPM)
support can be setup to monitor the idle time of a thread used
by client application connections. One aspect of the
monitoring of a thread's idle time is the ability to trigger
a warning condition when the thread's idle time has exceeded
a specified threshold rather than have the thread be canceled
due to exceeding the threshold. However, when a warning
condition is detected, only the information contained in
messages DSNT771I or DSNT772I is available but this does not
provide any information that identifies the thread which
exceeded the warning threshold.
DB2 has been changed to enhance the "Monitoring Idle
Threads by Using Profiles" capability of the System Profile
Monitoring (SPM) support. The ATTRIBUTE1 column of the
SYSIBM.DSN_PROFILE_ATTRIBUTES table can now contain a new
1 value, 'WARNING_MESSAGE_FOR_IDLE_TIMEOUT', for a row in the
table when the KEYWORD column has been set to
'MONITOR IDLE THREADS'. When SPM has been started with an
enabled warning monitor profile defined with the new ATTRIBUTE1
column value, and a thread servicing a client connection has
exceeded the specified threshold value, DB2 will now issue a
new DSNT773I message. Neither the thread nor the connection
will be terminated. The DSNT773I message will provide
information about the thread which exceeded the warning
idle time threshold, as follows:
DSNT773I csect-name SERVER DISTRIBUTED AGENT WITH
LUWID=luw-id=token
THREAD-INFO=thread-information
FOR LOCATION=location
RECEIVED IDLE THREAD TIMEOUT
WARNING DUE TO PROFILE ID=profile-id
Explanation
The information about the server thread which exceeded
a "MONITOR IDLE THREADS" monitor profile WARNING condition
is being displayed.
csect-name
The name of the control section that issued the message.
luw-id=token
The logical unit of work identifier (LUWID) and a
six-digit token value. The token value can be used in any
DB2 command that accepts a LUWID as input.
thread-information
Information about the thread. The information is presented
in a colon-delimited list that contains the following
segments:
* The primary authorization ID that is associated with the
thread.
In many distributed configurations, the primary
authorization ID that is used with DB2 is not
necessarily the user's ID.
* The name of the user's workstation.
* The ID of the user.
* The name of the application.
* The statement type for the previously executed
statement: dynamic or static.
* The statement identifier for the previously executed
statement, if available. The statement identifier can
be used to identify the particular SQL statement. For
1 static statements, the statement identifier correlates
to the STMT_ID column in the SYSIBM.SYSPACKSTMT table.
For dynamic statements, the statement identifier
correlates to the STMT_ID column in the
DSN_STATEMENT_CACHE_TABLE table. That statement might
not have contributed to the current failure.
* The name of the role that is associated with the thread.
* The correlation token that can be used to correlate work
at the remote system with work performed at the DB2
subsystem. The correlation token, if available, is
enclosed in '<' and '>' characters, and contains three
components, separated by periods:
- A 3 to 39 character IP address.
- A 1 to 8 character port address.
- A 12 character unique identifier.
An asterisk (*) in any segment indicates that the
information is not available.
location
This field contains the requester's IP address
profile-id
The profile ID of the monitor profile
(defined in DSN_PROFILE_TABLE) that detected the
condition.
This message might be followed by instances of message
DSNT771I indicating that WARNING MONITOR PROFILE conditions
have occurred.
Operator response
Notify the system programmer.
System programmer response
The message is being issued to provide information about
the thread which exceeded the WARNING condition. The
thread and connection remain active awaiting a subsequent
requester action. If the WARNING condition being exceeded
points to an application error, the information provided
can be used to identify the errant application.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21021
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
***Documentation for PI21021:
See PI21021 APAR/PTF text for additional information.
The following text contains the documentation of the function
provided by this APAR. The product documentation contained
in the Information Management Software for z/OS Solutions
1 Information Center will be updated at a later date.
System Profile Monitoring is being changed in the following
ways:
* a new ATTRIBUTE1 column value,
"WARNING_MESSAGE_FOR_IDLE_TIMEOUT", for a row in the
DSN_PROFILE_ATTRIBUTES table is being supported when the
KEYWORD column has the value "MONITOR IDLE THREADS"
* a new message, DSNT773I, will be issued when a thread has
exceeded the new WARNING_MESSAGE_FOR_IDLE_TIMEOUT
specified threshold.
* the base accounting trace record, as defined by DSNDQWAC,
is being enhanced to include the PROFILEID of the system
profile montoring table row (DSN_PROFILE_TABLE) which the
thread was identified to exceed, whether the threshold was
a warning or an exception.
New ATTRIBUTE1 Column Value for DSN_PROFILE_ATTRIBUTES Table
------------------------------------------------------------
In the documentation for "Managing DB2 Threads", there is an
existing subsection named "Monitoring idle threads by using
profiles". In step 2c of that section, the ATTRIBUTE1 column
can have values WARNING or EXCEPTION followed by either
_DIAGLEVEL1 or _DIAGLEVEL2. A new entry is being added to
the second part of the value as follows:
type_MESSAGE_FOR_IDLE_TIMEOUT
Where type can only be WARNING, DB2 will issue message,
DSNT773I, to display the information about the thread
which exceeded the warning threshold. DB2 will also
issue a console message, DSNT771I, which contains minimal
information. DB2 will only issue the DSNT773I message
once for the thread if it remains in an idle state. Once
a client request message is received, and a COMMIT or
ROLLBACK is performed with no resources active past the
end of the unit-of-work, DB2 will remove the warning
against the thread.
In the Table 1, "Summary of DSN_PROFILE_ATTRIBUTES values for
monitoring idle threads", a new value under the column with
heading, "ATTRIBUTE1 column", is being added as follows:
* WARNING_MESSAGE_FOR_IDLE_TIMEOUT
New Message DSNT773I
--------------------
DSNT773I csect-name SERVER DISTRIBUTED AGENT WITH
LUWID=luw-id=token
THREAD-INFO=thread-information
FOR LOCATION=location
RECEIVED IDLE THREAD TIMEOUT
WARNING DUE TO PROFILE ID=profile-id
1 Explanation
The information about the server thread which exceeded
a "MONITOR IDLE THREADS" monitor profile WARNING condition
is being displayed.
csect-name
The name of the control section that issued the message.
luw-id=token
The logical unit of work identifier (LUWID) and a
six-digit token value. The token value can be used in any
DB2 command that accepts a LUWID as input.
thread-information
Information about the thread. The information is presented
in a colon-delimited list that contains the following
segments:
* The primary authorization ID that is associated with the
thread.
In many distributed configurations, the primary
authorization ID that is used with DB2 is not
necessarily the user's ID.
* The name of the user's workstation.
* The ID of the user.
* The name of the application.
* The statement type for the previously executed
statement: dynamic or static.
* The statement identifier for the previously executed
statement, if available. The statement identifier can
be used to identify the particular SQL statement. For
static statements, the statement identifier correlates
to the STMT_ID column in the SYSIBM.SYSPACKSTMT table.
For dynamic statements, the statement identifier
correlates to the STMT_ID column in the
DSN_STATEMENT_CACHE_TABLE table. That statement might
not have contributed to the current failure.
* The name of the role that is associated with the thread.
* The correlation token that can be used to correlate work
at the remote system with work performed at the DB2
subsystem. The correlation token, if available, is
enclosed in '<' and '>' characters, and contains three
components, separated by periods:
- A 3 to 39 character IP address.
- A 1 to 8 character port address.
- A 12 character unique identifier.
1 An asterisk (*) in any segment indicates that the
information is not available.
location
This field contains the requester's IP address
profile-id
The profile ID of the monitor profile
(defined in DSN_PROFILE_TABLE) that detected the
condition.
This message might be followed by instances of message
DSNT771I indicating that WARNING MONITOR PROFILE conditions
have occurred.
Operator response
Notify the system programmer.
System programmer response
The message is being issued to provide information about
the thread which exceeded the WARNING condition. The
thread and connection remain active awaiting a subsequent
requester action. If the WARNING condition being exceeded
points to an application error, the information provided
can be used to identify the errant application.
Tracing "Monitor Idle Threads" Warning/Exception Conditions
-----------------------------------------------------------
A new paragraph is being added to our documentation in the
subsection named "Monitoring idle threads by using profiles"
of "Managing DB2 Threads", as follows:
"To understand which connection/thread exceeded a warning or
exception monitor profile, the accounting trace record of the
thread occurrence which experienced the condition will be
updated as follows:
* QWAC_PROFMON_TYPE - will be set to an 'E' for an exception
or a 'W' for a warning condition detected
* QWAC_PROFMON_PID - will be set to the 4-byte binary integer
value of the profile ID of the monitor profile (defined in
DSN_PROFILE_TABLE) that detected the condition
* if QWAC_PROFMON_TYPE is neither set to an 'E' nor a 'W',
then no monitor profile condition was detected for this
thread/connection accounting occurrence
Refer to the DSNWMSGS member of SDSNIVPD library or the
DSNDQWAC member of SDSNMACS library for a complete
description of the basic accounting trace fields.
Since a monitor profile exception condition will result in
thread level abend messages (DSNL027I/DSNL028I) being
displayed, a user can also create a warning monitor profile
which will result in a thread level message DSNT773I being
displayed when the warning threshold is exceeded. Refer to
1 the description of the ATTRIBUTE1 column value,
"WARNING_MESSAGE_FOR_IDLE_TIMEOUT".
Changes to IFCID 003 Record as described by DSNDQWAC
----------------------------------------------------
The accounting trace record (IFCID 003) as described by
DSNDQWAC is being changed as follows:
The current V10 DSNDWQAC contains the following in assembler:
...
QWACRU EQU *
DS CL8 * Reserved *
DS F * Reserved *
QWAC_PT_COUNT DS F * 1. For all non-rollup records = 0 *
* * 2. For a parallel query rollup record *
* * = number of parallel child agents *
* * rolled into this record *
* * 3. For a DDF/RRSAF rollup record = *
* * the number of parallel query child *
* * agents rolled into this record. *
* * These agents are NOT counted in *
* * QWACPCNT. *
QWACFLGS2 DS H
QWAC_RU_PARQRY EQU X'8000' * This record contains parallel *
* * query rollup data. *
DS CL6
QWAC_PQS EQU *
DS CL12 * Reserved *
QWAC_ACCEL EQU *
...
DSNDQWAC in assembler is being changed as follows:
...
QWACRU EQU *
DS CL8 * Reserved *
DS F * Reserved *
QWAC_PT_COUNT DS F * 1. For all non-rollup records = 0 *
* * 2. For a parallel query rollup record *
* * = number of parallel child agents *
* * rolled into this record *
* * 3. For a DDF/RRSAF rollup record = *
* * the number of parallel query child *
* * agents rolled into this record. *
* * These agents are NOT counted in *
* * QWACPCNT. *
QWACFLGS2 DS H
QWAC_RU_PARQRY EQU X'8000' * This record contains parallel *
* * query rollup data. *
QWAC_PROFMON EQU * * Thread profile monitoring info *
QWAC_PROFMON_TYPE DS CL1 * Profile monitoring type *
* * (E=excp, W=warn) *
DS CL1
QWAC_PROFMON_PID DS F * Profile table row id value *
QWAC_PQS EQU *
DS CL12 * Reserved *
QWAC_ACCEL EQU *
1 ...
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQWAC PI21021
DSNFMDIR PI21021
DSNFTDIR PI21021
DSNLEDDA PI21021
DSNT1RSP PI21021
DSNWVZSA PI21021
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21021 DSNDQWAC DSNFMDIR DSNFTDIR DSNLEDDA DSNT1RSP DSNWVZSA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFMDIR
DSNFTDIR
DSNLEDDA
DSNT1RSP
DSNWVZSA
MACROS
DSNDQWAC
LISTEND
UI22816 COVER LETTER END
UI22853 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21963 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users with a target data base in *
* Read-or-Replication-Only (RREPL) status *
****************************************************************
* PROBLEM DESCRIPTION: LOAD of a table space with its data *
* base in RREPL status, abends with *
* ABEND04E RC00E40009 but leaves objects *
* in UTUT status. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD of a table space was attempted but the data base had been
started in the RREPL state. This resulted in an ABEND04E
RC00E40009 and the objects were left in UTUT status.
The error occurred because the utility initialization phase did
not take into account that the entire data base could be in
RREPL. This resulted in the utility continuing on, placing the
objects in UTUT. When access to the table space was attempted,
MSGDSNT500I - RESOURCE UNAVAILABLE REASON 00C90224 TYPE 100
NAME dbname was issued followed by an ABEND04E RC00E40009 and
the objects were left in UTUT status.
1 This error can occur with any utility not allowed to run when
the object or objects are in RREPL.
Additional Keywords: DSNT500I DSNU0590I 00E40009 RC00C90224
Code has been changed to check for the data base being in RREPL,
and have the utility issue message MSGDSNU590I - RESOURCE NOT
AVAILABLE, REASON=X'00C90224', ON dbname PROHIBITS PROCESSING
for that data base and end with RC8.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21963
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDTC PI21963
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21963 DSNUGDTC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDTC
LISTEND
UI22853 COVER LETTER END
UI22900 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28198 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Delays during LPL recovery, while *
* accessing DSNDB01.SYSLGRNX. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The LPL log apply process may unnecessarily insert a row into
SYSLGRNX, even though it is not generating any new log records.
This may cause delays or failures if SYSLGRNX is unavailable.
The pageset pseudo-open process has been modified to recognize
LPL recovery as a non-logging process, which does not require
any SYSLGRNX coverage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28198
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1SWS PI28198
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI28198 DSNB1SWS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1SWS
LISTEND
UI22900 COVER LETTER END
UI22911 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27833 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS customers running the *
* DSNTIJEN job. *
****************************************************************
* PROBLEM DESCRIPTION: DSNTIJEN fails at step ENFM0027 with *
* MSGDSNU341I stating image copy was *
* not taken but SYSIBM.SYSCOPY shows *
* an image copy is available. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The internal structure for index DSNUCH01 on table
SYSIBM.SYSCOPY was incorrect. A select from this table that
uses the index DSNUCH01 would return incorrect values for the
DBNAME.
The DSNTIJEN job would use index DSNUCH01 to look for an image
copy before the ENFM steps are processed. Because the internal
structure was incorrect DSNTIJEN would not see the image copy
and issue message DSNU341I indicating that the image copy is
needed and stops the DSNTIJEN job. Code has been added to
correct the internal structure when the catalog DBD is loaded so
the image copy will be seen when the DSNUCH01 index is used.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27833
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEPUF PI27833
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27833 DSNGEPUF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPUF
LISTEND
UI22911 COVER LETTER END
1
UI22920 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22697 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of an accelerated *
* static SQL query. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes the following *
* problems for static query *
* acceleration: *
* (1) BIND / REBIND PACKAGE specifying *
* bind options QUERYACCELERATION(ALL) *
* or GETACCELARCHIVE(YES) fails with *
* SQLCODE -4742 RC=14 when a target *
* accelerated table exists on *
* a virtual accelerator *
* (2) An accelerated static query fails *
* at run time with SQLCODE -950 when *
* the targeted accelerated table *
* exists on a virtual accelerator *
* (3) AB04E at DSNLXREL . DSNSVSFB +08C6 *
* occurs when an accelerated static *
* SQL query is run when the target *
* accelerated table is archived *
* 'after' the last BIND / REBIND *
* PACKAGE bound the static query for *
* acceleration *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes the following problems found for static query
acceleration:
(1) BIND / REBIND PACKAGE with bind option
QUERYACCELERATION ( ALL ) or GETACCELARCHIVE ( YES ) fails
with SQLCODE -4742 and reason code 14 when a virtual
accelerator exists. This can occur when all of the
following conditions are true:
(a) A table exists on both a real and virtual accelerator
(b) The ALTEREDTS value in SYSACCEL.SYSACCELERATEDTABLES
for the table for the virtual accelerator is older than
ALTEREDTS in SYSIBM.SYSCOLUMNS for the table
(2) Execution of an accelerated static SQL query fails with
SQLCODE -950 when a virtual accelerator exists. This can
occur when a virtual accelerator is defined but stopped (or
not active) at BIND / REBIND PACKAGE.
(3) ABEND04E at DSNLXREL . DSNSVSFB OFFSET08C6 occurs when
an accelerated static SQL query is run when the target
accelerated table is archived 'after' the last BIND/REBIND
PACKAGE bound the static query for acceleration.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLCODE4742 SQLCODE950 ABEND04E
DB2 code is fixed for expected behavior.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22697
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI22697:
See PI22697 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22697 corrects a problem for SQL query acceleration when
a virtual accelerator exists or when an accelerated table
is archived on the accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDP PI22697
DSNXEPP PI22697
DSNXERT PI22697
DSNXERT2 PI22697
DSNXONZA PI22697
DSNXONZB PI22697
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22697 DSNXEDP DSNXEPP DSNXERT DSNXERT2 DSNXONZA DSNXONZB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDP
DSNXEPP
DSNXERT
DSNXERT2
DSNXONZA
DSNXONZB
LISTEND
UI22920 COVER LETTER END
UI22935 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26512 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Potentially long delays in the time it *
* takes for a read/write page set or *
* partition to be converted to read- *
* only (pseudo-close). *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
If a page set or partition is chosen as a candidate to be
pseudo-closed, based on meeting the PCLOSEN and/or PCLOSET
criteria, and if the process fails for any reason (such as
a failure on a conditional lock request), it may take a long
time before it is ever considered again. This is because the
tracking fields (last update time, and number of checkpoints
since last update) are reset before the attempt is made.
In order to meet the PCLOSEN criteria a second time, the
object must once again go through that many checkpoints
without being updated.
In order to meet the PCLOSET criteria a second time, the
object must first be updated again, and then that amount
of time must pass again without any further updates.
For an object which is never updated again, and for a high
PCLOSEN value (or infrequent DB2 checkpoints), the pseudo-
close may never happen at all.
The pseudo-close process has been modified to no longer reset
the tracking fields before attempting a pseudo-close. This will
allow the object to be chosen again during the next cycle.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26512
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1PCP PI26512
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26512 DSNB1PCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1PCP
LISTEND
UI22935 COVER LETTER END
UI22952 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27751 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement with a view containing nested *
* table expressions with multiple 'SELECT *' *
* and a SELECT list item without a name. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXGRDS DSNXOFL M120 could happen for *
* an SQL statement with a view satisfying *
1 * all of the following conditions: *
* *
* 1. It contains multiple nested table *
* expressions. *
* 2. It contains multiple 'SELECT *' and *
* a SELECT list item without a name. *
* 3. The table expressions are *
* materialized. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE VIEW V1(C1) AS
SELECT * FROM (
SELECT * FROM (
SELECT RAND()
FROM SYSIBM.SYSDUMMY1
) AS TX1
ORDER BY 1
) AS TX1
;
SELECT * FROM V1;
;
DB2 did not correctly process the aforementioned SQL statement,
which caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLVIEW SQLTABLEEXPR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27751
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTDA PI27751
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27751 DSNXOTDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTDA
LISTEND
UI22952 COVER LETTER END
UI22954 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22357 -
1 ****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI and *
* DB2 11 for z/OS ODBC/CLI calling a stored *
* procedure in a vendor escape clause. *
****************************************************************
* PROBLEM DESCRIPTION: When an ODBC application calls a *
* stored procedure in a vendor escape *
* clause with literals used in the *
* procedure's parameters, an incorrect *
* result may be returned. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an ODBC application calls a stored procedure in a vendor
escape clause with literals used in the procedure's parameters,
the ODBC driver incorrectly parses the literals in
the call statement. This results in wrong data being passed to
the stored procedure causing an incorrect result being returned
to the calling application.
The code has been changed to correctly parse the literals in the
parameters and send correct data to DB2 when the procedure is
called in a vendor escape clause.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI22357
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
*** Action for PI22357 (Version 10)
This PTF includes the following updated DBRM for the ODBC
executable modules DSNAOCLI, DSNAOCLX, and DSNAO64C:
DSNCLIQR
After applying the PTF, all customers who use these modules
need to bind the package of the DBRM DSNCLIQR.
For example:
BIND PACKAGE (<location-name>.DSNAOCLI) MEMBER(DSNCLIQR)
ACTION(ADD) ENCODING(EBCDIC)
where <location-name> is the location of the DBRM where
the package binds and where the description of the
package resides.
Failure to bind the required packages could result in
SQLCODE=-805 at application run time.
Also, refer to the prolog of the CLI sample bind job DSNTIJCL
in your SDSNSAMP data set for specific instructions on how to
customize the BIND command for binding the DBRMs/packages and
the application plan at your site.
*** Attention: DB2 data sharing customers need to bind the
package only once, after applying the PTF on the first
member.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG0T PI22357
DSN@LIQR PI22357
DSNAOCLI PI22357
DSNAOSDK PI22357
DSNAOC0P PI22357
DSNAOG0P PI22357
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22357 DSNAOG0T DSN@LIQR DSNAOCLI DSNAOSDK DSNAOC0P DSNAOG0P
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOG0T
DSNAOCLI
DSNAOC0P
DSNAOG0P
MACROS
DSN@LIQR
DSNAOSDK
LISTEND
UI22954 COVER LETTER END
UI22984 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26766 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 users of native SQL *
* stored procedures. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNITCUS 5002 *
* following a CANCEL THREAD *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a native SQL procedure processed a COMMIT, a cancel
thread command was issued. However, that command was not
honored immediately, causing the stored procedure to continue
executing, past the COMMIT.
Some time later, another COMMIT was issued. The cancel
thread command from earlier caused this COMMIT to fail, and
go into abort processing and free certain internal structures.
The next SQL statement in this procedure referred to these
freed structures, resulting in the reported ABEND.
DB2 code has been changed to detect that a cancel thread
was issued, and will re-issue the cancel thread's ABEND
reason code 00E50013 at the end of COMMIT, so DB2 would
not erroneously continue processing.
1 Additional Keywords: SQLNATIVESQLPL ABEND RC00E50013
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26766
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM53253:
See PM53253 APAR/PTF text for additional information.
PM53253 corrects a problem of SQLCODE -805 encountered when
calling a Native SQL Procedure at a site that does not have
maintenance UK60802 (V9) or UK65480 (V10) applied, after the
procedure was deployed in a BIND PACKAGE DEPLOY command from
another site that does have maintenance UK60802 (V9) or
UK65480 (V10) applied.
To make this fix effective, apply this fix to all target sites
specified by BIND PACKAGE DEPLOY commands.
You can issue an sql ALTER PROCEDURE REGENERATE statement for
the procedure that fails with SQLCODE805 to allow subsequent
calls to be successful.
The order of maintenance across distributed subsystems
determines whether or not you will receive the SQLCODE805 error.
To circumvent the error, first apply this fix (or UK60802 or
UK65480) to all target sites specified by BIND PACKAGE DEPLOY
commands, and then apply this fix (or UK60802 or UK65480) to
the requesting sites.
The order of maintenance and the issuance of the BIND PACKAGE
DEPLOY command also determines whether or not you will receive
the SQLCODE805 error. If this fix (or UK60802 or UK65480) is
applied to all systems before any BIND PACKAGE DEPLOY commands
are issued, then the subject error will not occur.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNRCAFR PI26766
DSNXESPL PI26766
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26766 DSNRCAFR DSNXESPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNRCAFR
DSNXESPL
LISTEND
UI22984 COVER LETTER END
UI22987 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI25244 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement containing a temporal table and a *
* period-specification. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output could happen for an *
* SQL statement containing a temporal *
* table and a period-specification when *
* parallelism is enabled and an index is *
* created on the period columns. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 CHAR(10),
C2 DATE NOT NULL,
C3 DATE NOT NULL,
PERIOD BUSINESS_TIME(C2, C3)
)
;
CREATE INDEX IX1
ON T1(C2, C3)
;
SELECT *
FROM T1
FOR BUSINESS_TIME AS OF '01/01/2014'
;
DB2 did not correctly process the SELECT statements, which
caused the incorrect output.
DB2 has been modified to correctly process the SQL statement
containing a temporal table and a period-specification, so there
will be no incorrect output.
Additional keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLBITEMPORAL SQLSPTT SQLAPTT
PARALLELISM SQLPARALLELISM DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25244
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI25244:
See PI25244 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25244 corrects a problem that incorrect output could happen
for an SQL statement containing a temporal table and a
period-specification when parallelism is enabled and an index
is created on the period columns.
1
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOBM PI25244
DSNXOW2D PI25244
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25244 DSNXOBM DSNXOW2D
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBM
DSNXOW2D
LISTEND
UI22987 COVER LETTER END
UI22993 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22468 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS who *
* use GROUP BY and parallelism *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E72018 can occur in *
* DSNXSORI+481E during execution time for *
* a query meeting the following *
* conditions: *
* 1. The query contains GROUP BY *
* 2. An attempt is made to use an index *
* to support the GROUP BY *
* 3. The index chosen from #2 is on a *
* different table than the table *
* containing the columns referenced *
* in the GROUP BY *
* 4. More than one GROUP BY column maps *
* to the same column in the chosen *
* index *
* 5. Parallelism is used on the query *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E72018 can occur in DSNXSORI +481E during execution
time for a query meeting the following conditions:
1. The query contains GROUP BY;
2. An attempt is made to use an index to support the GROUP BY
grouping;
3. The index chosen from #2 is on a different table than the
table containing the columns referenced in the GROUP BY;
4. More than one GROUP BY column maps to the same column
1 in the chosen index; and
5. Parallelism is used on the query.
DB2 may attempt to use an index from a different table to
support the GROUP BY grouping if there are equal predicates
between the GROUP BY columns and the columns in the index key of
the other table.
For example:
SELECT A.C1, A.C2, A.C3, MAX(A.C4)
FROM A, B
WHERE A.C1 = B.C1 AND
A.C2 = B.C1 AND
A.C3 = B.C3
GROUP BY A.C1, A.C2, A.C3;
An index exists on table B: IXB (C1, C3)
Since A.C1 and A.C2 both equal B.C1, A.C2 is a redundant
GROUP BY column. This can cause a duplicate column to be
added to the GROUP BY list, which leads to the abend in
execution time.
Additional Keywords:
SQLGROUPBY OFFSET481E SQLPARALLELISM PARALLELISM
DB2PARALL/K
Code is updated to recognize the redundant GROUP BY column and
process it correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22468
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI22468:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI22468 corrects a problem where ABEND04E RC00E72018 can
occur in DSNXSORI+481E during execution time for a query
meeting the following conditions:
1. The query contains GROUP BY;
2. An attempt is made to use an index to support the GROUP BY
grouping;
3. The index chosen from #2 is on a different table than the
table containing the columns referenced in the
GROUP BY;
4. More than one GROUP BY column maps to the same column
in the chosen index; and
5. Parallelism is used on the query.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
1 CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOLM1 PI22468
DSNXOPRP PI22468
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22468 DSNXOLM1 DSNXOPRP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOLM1
DSNXOPRP
LISTEND
UI22993 COVER LETTER END
UI23000 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28565 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC10 in DSNB1CMS while DB2 *
* was shutting down per the -STOP DB2 *
* command. DB2 then terminated *
* abnormally with MSGDSNV086E and *
* RC00E50702. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DB2 shutdown, suspended SRBs in the DB2 DBM1 address
space are resumed for SRB termination. There is a small
timing window where the SRB could be purged, resulting in
an ABEND47B, after the DSNVSRRX FRR has been deleted. The
purge ABEND would then drive a lower FRR, which could abend
as much of the DB2 DBM1 storage and code has already been
freed at this point. In the failing case, an ABEND0C4 RC10
occurred attempting to drive recovery code in DSNB1CMS
but the module was already deleted.
The SRB termination code that executes during DB2 shutdown
has been changed to eliminate this timing window.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28565
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVASTM PI28565
DSNVSRX PI28565
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28565 DSNVASTM DSNVSRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNVASTM
DSNVSRX
LISTEND
UI23000 COVER LETTER END
UI23007 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20064 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* debug a native SQL routine executed at the *
* remote server using Unified Debugger or the *
* SQL Debugger *
****************************************************************
* PROBLEM DESCRIPTION: The following abends can be encountered *
* when processing a stored procedure or *
* User-Defined Function (UDF) in debug *
* mode: *
* *
* ABEND04E RC00D35001 *
* LOC=DSNLZLLM.DSNLZS00:0086 *
* *
* ABEND04E RC00D35011 *
* LOC=DSNLZLLM.DSNLZS00:0309 *
* *
* ABEND04E RC00D35011 *
* LOC=DSNLZLLM.DSNLZS00:003C *
* *
* ABEND04E RC00E70005 in *
* DSNXRBND:M666 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In one of the scenarios, ABEND04E RC00D35001 in DSNLZS00
error location 0086 was encountered when terminating an
execution of an SQLPL stored procedure in debug mode.
Further investigation indicates that the error return code was
percolated back. However, the error SQLCODE was cleared. This
can result in the aforementioned abends.
DB2 code has been modified so that SQLCODE is not cleared when
an error is encountered during debug mode.
Additional Keywords: SQLSP SQLNATIVESQLPL DEBUGMODE
SQLDEBUGMODE SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20064
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
DSNXESTR PI20064
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20064 DSNXESTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXESTR
LISTEND
UI23007 COVER LETTER END
UI23031 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18490 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users running *
* a large number of concurrent LOADs. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20029 when DSNIDBEL *
* tried to free a DBET block because *
* the block had already been freed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There is a small timing window when the DBET hash chain is
unlatched so that a notify to other data sharing members
can take place. When the latch is reacquired, a change
has been made to one of the objects and it does not get
properly processed. Storage for some of the objects is
freed and orphaned.
When updating an object with piece information, make sure
that the piece information is not freed prematurely.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI18490
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBAB PI18490
DSNIDBAE PI18490
DSNIDBBD PI18490
DSNIDBDA PI18490
DSNIDBDF PI18490
DSNIDBDG PI18490
DSNIDBDM PI18490
DSNIDBDR PI18490
DSNIDBDW PI18490
DSNIDBEL PI18490
DSNIDBGC PI18490
DSNIDBGN PI18490
1 DSNIDBHK PI18490
DSNIDBIN PI18490
DSNIDBMC PI18490
DSNIDBMF PI18490
DSNIDBMG PI18490
DSNIDBNG PI18490
DSNIDBPL PI18490
DSNIDBPX PI18490
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI18490 DSNIDBAB DSNIDBAE DSNIDBBD DSNIDBDA DSNIDBDF DSNIDBDG
DSNIDBDM DSNIDBDR DSNIDBDW DSNIDBEL DSNIDBGC DSNIDBGN
DSNIDBHK DSNIDBIN DSNIDBMC DSNIDBMF DSNIDBMG DSNIDBNG
DSNIDBPL DSNIDBPX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBAB
DSNIDBAE
DSNIDBBD
DSNIDBDA
DSNIDBDF
DSNIDBDG
DSNIDBDM
DSNIDBDR
DSNIDBDW
DSNIDBEL
DSNIDBGC
DSNIDBGN
DSNIDBHK
DSNIDBIN
DSNIDBMC
DSNIDBMF
DSNIDBMG
DSNIDBNG
DSNIDBPL
DSNIDBPX
LISTEND
UI23031 COVER LETTER END
UI23078 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28320 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Long GRECP recovery time, or ABEND04E *
* RC00D1032B in DSNJR103. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When marking a page set or partition GRECP, DB2 may include log
ranges from members beyond the highest recorded connecting
1 member ID. However, the starting LRSN for such members does
not get advanced during GBP checkpoint processing, so the GRECP
recovery process may end up searching for log records which are
very old, or even unavailable. This can cause the recovery to
take an unnecessarily long time, or to fail completely.
The GBP checkpoint processing has been modified to ensure that
the recovery LRSN is advanced for all members included in the
recovery member list.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28320
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5SCO PI28320
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28320 DSNB5SCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB5SCO
LISTEND
UI23078 COVER LETTER END
UI23080 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29108 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: 04E-00E20002 DSNLTAS1.DSNSVBK +1956 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote, site1, client application accesses a DB2 for z/OS
(V10 or higher) server, site2, and executes SQL that refers to
another remote server, site3. Relative to DB2 for z/OS site2,
this scenario represents a "hopping" case because site2
receives SQL from site1 but must "hop" the SQL to site3.
The site2 DB2 for z/OS SYSIBM.IPNAMES (Communications DataBase,
CDB) table is defined such that site3 requires userid and
password authentication credentials (SECURITY_OUT='P'). In
this case, DB2 for z/OS at site2 will automatically attempt to
encrypt the authentication credentials since ICSF services are
available. However, site3 indicates that it does not support
encryption (perhaps site3 is also DB2 for z/OS where ICSF
services are not available) in which case site2 will retry
with a less secure form of authentication (perhaps clear text).
During this retry processing, storage related to the failed
encrypted attempt must be freed but the attributes associated
with this storage free request are invalid which leads to the
1 reported abend.
Note: This invalid storage free request will only occur in
DB2 for z/OS "hopping" scenarios.
As a circumvention, users can take one of the following
actions:
o Make the necessary changes at site3 to allow encrypted
authentication credentials to be accepted.
If site3 is also DB2 for z/OS, ICSF services should be made
available.
o Stop ICSF at site2.
Site2 will use clear text authentication credentials with
site3.
o Change the site2 SYSIBM.IPNAMES table SECURITY_OUT column,
relative to site3, to specify 'A' or 'R'.
Note: Site3 must be configured to tolerate this form of
authentication.
Site2 will not attempt to used encrypted credentials.
DB2 is changed to specify the correct attributes when freeing
storage related to a (hop related) failed encrypted access
attempt.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29108
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTAS1 PI29108
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29108 DSNLTAS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTAS1
LISTEND
UI23080 COVER LETTER END
UI23102 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20477 -
****************************************************************
* USERS AFFECTED: All DB2 10,11 for zOS users of referential *
* constraints. *
****************************************************************
* PROBLEM DESCRIPTION: CHECK DATA utility may abend and *
* issue messages MSGDSNU299I and *
* MSGDSNU017 with RC00E400D0 when *
* the index on a primary key has an *
* INCLUDE column. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
CHECK DATA utility may get DSNU299I CHARACTER CONVERSION
FAILED and DSNU017I with RC00E400D0, if a tablespace has a
parent table with a primary index that was created with an
INCLUDE column.
When CHECK DATA attempts to find a parent row for a
row in a child table, it constructs a key from the foreign
key columns of the child table in a format to match the
primary key of the parent table.
In doing so, DB2 incorrectly included the non-ordering keys
which resulted in the error messages and the abend of the
CHECK DATA utility.
DB2 code has been modified to correctly construct a key from
the foreign key columns to use for finding the primary key of
the parent table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20477
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRELF PI20477
DSNIRELU PI20477
DSNUKIFK PI20477
DSNURCRI PI20477
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20477 DSNIRELF DSNIRELU DSNUKIFK DSNURCRI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRELF
DSNIRELU
DSNUKIFK
DSNURCRI
LISTEND
UI23102 COVER LETTER END
UI23130 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24642 -
****************************************************************
* USERS AFFECTED: All DB2 Lobs users. *
****************************************************************
* PROBLEM DESCRIPTION: Abend04E DSNIOLAD ERQUAL5021 occurred *
* during UNDO of an uncommitted delete *
* LOB and found that the LOB space class *
* was marked 'unallocated' by mistake. *
* It should have been 'deallocated'. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 DB2 has some good sam code that would change 'deallocated'
space to 'unallocated' space, if it is determined that the
'deallocated' space is committed. But the committedness
test was fuzzy, so DB2 sometimes prematurely reset the
'deallocated' space to 'unallocated' due to this fuzzy
committedness test.
If the application wants to rollback a lob that had been
marked prematuredly to 'unallocated', rollback does not
like it and issues the ABEND04E DSNOLADS:5021.
DB2 code is changed to remove the fuzzy committedness test
for the LOB space class modification to avoid changing the
space class to 'unallocated' prematurely.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24642
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNODEAL PI24642
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24642 DSNODEAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNODEAL
LISTEND
UI23130 COVER LETTER END
UI23132 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22668 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of CURRENTLY COMMITTED semantic *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNICUMW ERQUAL5003 *
* occurred during DELETE operation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Using CURRENTLY COMMITTED semantic, two transactions attempted
to DELETE the same row.
While the first transaction successfully held the lock, the
second transaction was allowed to skip the lock because index
access to the row incorrectly honored CURRENTLY COMMITTED
semantic for DELETE. CURRENTLY COMMITTED semantic applies to
READ transactions.
Additional Key words:
CONCURRENTACCESSRESOLUTION, USECURRENTLYCOMMITTED
1 USE CURRENTLY COMMITTED
DB2 code has been updated to honor CURRENTLY COMMITTED semantic
on read transactions only.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22668
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKFLST PI22668
DSNKFPRV PI22668
DSNKFTCH PI22668
DSNKNXT2 PI22668
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22668 DSNKFLST DSNKFPRV DSNKFTCH DSNKNXT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKFLST
DSNKFPRV
DSNKFTCH
DSNKNXT2
LISTEND
UI23132 COVER LETTER END
UI23184 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27810 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Remote SQL CALL statement results *
* in ABEND04E-00D3000E *
* LOC=DSNLXGLM.DSNLXRSL+2734 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An application running on a DB2 for z/OS requester, Site1,
connects to a remote server, Site2. The application calls a
stored procedure at Site2 successfully. The application then
issues a RELEASE of Site2, followed by a CONNECT to Site2,
followed by a COMMIT. The application calls the stored
procedure again, resulting in ABEND04E-00D3000E
LOC=DSNLXGLM.DSNLXRSL+2734 at Site1.
Note: This error can occur for remote SQL statements other
than CALL. For these cases, an ABEND04E-00D3000E may occur
in any of these modules:
DSNLXGLM.DSNLXMRF DSNLXGLM.DSNLXRAX DSNLXGLM.DSNLXRBF
DSNLXGLM.DSNLXRCL DSNLXGLM.DSNLXRDT DSNLXGLM.DSNLXRFT
DSNLXGLM.DSNLXROP DSNLXGLM.DSNLXRSQ
The problem occurs because the CONNECT that was issued between
1 the RELEASE and COMMIT caused an internal inconsistency with
the connection state maintained by DB2.
A CONNECT statement should not reverse the effects of a pending
release state. DB2 has been changed to maintain the pending
release state after a CONNECT.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27810
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXRCN PI27810
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27810 DSNLXRCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXRCN
LISTEND
UI23184 COVER LETTER END
UI23196 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21590 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -904 00D300F4 DSNLTAS1, and *
* message DSNL031I with REASON=00D300F4 *
* and ERRORID=DSNLTAS10002, when *
* accessing a remote DB2/LUW server *
* configured with AUTHENTICATION CLIENT. *
* The problem occurs after APAR PM68029. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote DB2/LUW server is configured to allow Already Verified
access (user-id, only, but no password) via the AUTHENTICATION
CLIENT database manager configuration specification. However,
the DB2 z/OS SYSIBM.IPNAMES (Communications DataBase, CDB)
table is defined to use SECURITY_OUT='P' (Password)
authentication when accessing the remote DB2/LUW server.
The first access to the remote DB2/LUW server will succeed but
the second and subsequent access to the DB2/LUW server will
fail with SQLCODE -904 indicating reason 00D300F4 from CSECT
DSNLTAS1. A DSNL031I message may also be issued indicating
REASON=00D300F4 and ERRORID=DSNLTAS10002.
After the first access to the DB2/LUW server, DB2 z/OS
requester processing caches information to reflect that the
authentication characteristics should be downgraded from
1 Password to Already Verified. But APAR PM68029 implemented a
change to always use the CDB defined security characteristics
instead of the information reflected in the cache. This was
done in an effort to synchronize the security characteristics
with the CDB defined specification but PM68029 did not consider
that an upgrade (to password authentication) will not be
honored by DB2/LUW AUTHENTICATION CLIENT configured servers.
To circumvent the condition, the DB2 for z/OS CDB can be
changed, from SECURITY_OUT='P', to SECURITY_OUT='A' in order to
be consistent with the DB2/LUW server security requirements.
DB2 has been changed to recognize that AUTHENTICATION CLIENT
configured DB2/LUW servers will not allow an upgrade to the
password based authentication defined in the DB2 for z/OS CDB.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21590
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTCCN PI21590
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21590 DSNLTCCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTCCN
LISTEND
UI23196 COVER LETTER END
UI23213 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29090 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* COPY utility users *
****************************************************************
* PROBLEM DESCRIPTION: COPY UTILITY SERVICEABILITY *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
COPY UTILITY SERVICEABILITY
COPY UTILITY SERVICEABILITY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29090
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The fix for APAR PI29090 requires the fix for APAR PM29188, for
FMID JDBAA1K to be applied.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDDC PI29090
DSNUGPRT PI29090
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29090 DSNUGDDC DSNUGPRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDDC
DSNUGPRT
LISTEND
UI23213 COVER LETTER END
UI23214 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29188 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* COPY utility users. *
****************************************************************
* PROBLEM DESCRIPTION: COMPANION APAR FOR PI29090 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
COMPANION APAR FOR PI29090
COMPANION APAR FOR PI29090
COMPONENT: 5740-XYR00-JDBAA1K
APARS FIXED: PI29188
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The fix for APAR PI29188 requires the fix for APAR PM29090, for
FMID HDBAA10 to be applied.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUFFMC PI29188
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29188 DSNUFFMC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUFFMC
LISTEND
UI23214 COVER LETTER END
UI23220 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI28042 -
****************************************************************
* USERS AFFECTED: All users of DSNTIAUL in DB2 Version 10 and *
* DB2 Version 11 for z/OS are affected by this *
* change. *
****************************************************************
* PROBLEM DESCRIPTION: In SQL mode, DSNTIAUL terminates with *
* the message: *
* DSNT502I ERROR IN DSNTIAUL SQL INPUT: *
* ... *
* and *
* DSNT404I SQLCODE = 495... *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
DSNTIAUL is a sample dynamic SQL processing application that is
used primarily to unload data from DB2 tables to an externalized
format. DSNTIAUL also generates a LOAD control statement that
can be used in conjunction with the DB2 LOAD utility to load the
externalized data back into DB2.
Currently, in SQL mode, DSNTIAUL terminates when DB2 returns
warning SQLCODE +495 to indicate that the cost estimate of
processing the prepare of the current SQL statement exceeded the
warning threshold value specified in the DB2 resource limit
specification table (RLST). SQLCODE +495 is also issued if DB2's
cost category value was "B", and the default action specified
in the RLF_CATEGORY_B column in the RLST is to issue a warning.
After SQLCODE +495, the SQL statement is fully PREPAREd and
can be processed further. However, DSNTIAUL terminates after
generating a formatted SQL message because in SQL mode it
expects only SQLCODE +098, SQLCODE +394, or SQLCODE +395 from
PREPARE. Those SQLCODEs are guaranteed to put the offset of
the terminating semicolon of the SQL statement in SQLERRD(5) of
the SQLCA, and DSNTIAUL exploits this behavior to parse
individual SQL statements from an input buffer containing one or
more SQL statements.
Investigation reveals that SQLERRD(5) will contain the offset
of the terminating semicolon when PREPARE returns SQLCODEs
+495. Therefore, DSNTIAUL is modified to accept SQLCODEs +495
from PREPARE. This change prevents DSNTIAUL from terminating
as described above.
When PREPARE returns SQLCODE +495, DSNTIAUL now echoes the
current SQL statement to SYSPRINT, followed by the message:
SQL WARNING DURING EXECUTE IMMEDIATE
and:
DSNT404I SQLCODE = 495 ...
Processing then continues on the current statement. When this
statement and any remaining have been processed, DSNTIAUL will
set return code 4 unless a higher return code has been set due
to other errors.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28042
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
(2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.
DB2BIND:
This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
(2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.
DB2BIND:
This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
1 (2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIAUL PI28042
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28042 DSNTIAUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIAUL
LISTEND
UI23220 COVER LETTER END
UI23242 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28990 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries that can use a sparse index and *
* contain a subquery using multi-row insert *
* when row permissions are enabled. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E72018 at DSNXSTSG +500 *
* (OFFSET500) can occur for a query when *
* a sparse index (that has already been *
* built) needs to be rebuilt for a *
* specific sort. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E72018 at DSNXSTSG +500 can occur for a given
query when a sparse index (that has already been built) for the
specific sort needs to be rebuilt for the same specific sort.
This issue can happen when row permissions are enabled and the
query contains a subquery which uses multi-row insert which can
cause the sparse index to be rebuilt for each inserted row.
DB2 has been modified to clean up a sparse index for a specific
sort if it gets invoked again to re-sort which will require
rebuilding the sparse index.
Additional Keywords: SQLSPARSEINDEX SQLMRI
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28990
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
DSNXSMRE PI28990
DSNXSMRG PI28990
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28990 DSNXSMRE DSNXSMRG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSMRE
DSNXSMRG
LISTEND
UI23242 COVER LETTER END
UI23245 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25743 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* parallelism user of sort-merge join with *
* merge-composite (MERGC = 'Y' in the PLAN_ *
* TABLE). *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E72018 at DSNXSORI *
* OFFSET 5E02 may occur when a sort- *
* merge join query with merge-composite *
* (MERGC = 'Y' in the PLAN_TABLE) runs in *
* parallel and the sort-merge join join *
* predicate has different nullability, *
* data type, or data length. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E72018 at DSNXSORI OFFSET 5E02 may occur when a
sort-merge join query with merge-composite (MERGC = 'Y' in the
PLAN_TABLE) runs in parallel and the sort-merge join join
predicate has different nullability, data type, or data length.
When DB2 processes the merge-composite, it does not handle the
mismatched join predicate correctly in parallel code path.
So, SORT misinterprets the value of the join column and caused
the abend.
Following is an example of such failing query:
SELECT V3.C1, V1.C4, V2.C4, V3.C5, V3.C6
FROM VIEW1 V1, VIEW2 V2, VIEW3 V3
WHERE ((V3.C1 BETWEEN '2014-08-01' AND '2014-08-31'))
AND V3.C2 = V2.C2
AND V3.C3 = V1.C3
FOR FETCH ONLY
;
NOTE: VIEW1, VIEW2, and VIEW3 are complex VIEWs.
1 DB2 is modified to handle the mismatched join predicate of
sort-merge join with merge-composite correctly in parallelism.
Additional Keywords: PARALLELISM SQLPARALLELISM DB2PARALL/K
SQLSMJ SQLMSJ SMJ MSJ ABEND04E
RC00E72018 DSNXSORI OFFSET5E02
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25743
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI25743:
See PI25743 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25743 corrects a problem an ABEND04E RC00E72018 at DSNXSORI
OFFSET 5E02 may occur when a sort-merge join query with
merge-composite runs on parallel and the join predicate has
different nullability, data type, or data length.
To make this fix effective for a static application, it must 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
DSNXOGP PI25743
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25743 DSNXOGP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGP
LISTEND
UI23245 COVER LETTER END
UI23249 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25299 -
****************************************************************
* USERS AFFECTED: DB2 users with AUTOSIZE(YES) buffer pools. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect size values reported to WLM *
* for AUTOSIZE(YES) buffer pools with *
* page sizes other than 4K. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 needs to report the current, active, minimum, and maximum
buffer pool sizes to WLM as counts of 4K blocks. However, the
conversion from pages to 4K blocks for page sizes other than
1 4K is done incorrectly.
The code to report buffer pool sizes to WLM has been modified
to provide correct values for buffer pools with page sizes
larger than 4K.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25299
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1WLM PI25299
DSNB1WRA PI25299
DSNB5WDC PI25299
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25299 DSNB1WLM DSNB1WRA DSNB5WDC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1WLM
DSNB1WRA
DSNB5WDC
LISTEND
UI23249 COVER LETTER END
UI23268 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28667 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a SQL *
* statement containing UNION ALL and one of *
* the sub-query select list of UNION ALL *
* references an item with CLOB or DBCLOB *
* data type. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at location *
* DSNIDM DSNOTFLA ERQUAL5009 may occur *
* when a statement satisfies all of the *
* following list of conditions: *
* *
* 1. A fullselect statement contains *
* UNION ALL. *
* *
* 2. One of the sub-query select list of *
* UNION ALL references an item with *
* CLOB or DBCLOB data type. *
* *
* 3. The corresponding of other sub-query *
* select list of UNION ALL is a *
* literal. *
* *
* *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create TABLE T1 and T2.
CREATE TABLE TEST.T1(
C1 INTEGER,
C2 CLOB(2)
)
CCSID UNICODE;
CREATE TABLE TEST.T2(
C1 FLOAT,
C2 CHAR(2)
)
CCSID EBCDIC;
Step 2. Populate Table T1 and T2.
INSERT INTO TEST.T1 VALUES (1, 'CC');
INSERT INTO TEST.T2 VALUES (2, 'CC');
INSERT INTO TEST.T1 VALUES (3, 'CC');
INSERT INTO TEST.T2 VALUES (4, 'CC');
Step 3. statement which can cause ABEND04E.
SELECT C1 , C2
FROM TEST.T1
UNION ALL
SELECT C1 , 'A' AS C2
FROM TEST.T2;
DB2 does not process the data type conversion of literal 'A'
properly which can result in the ABEND.
DB2 has been modified correctly to process data type conversion
to avoid the ABEND.
Additional keywords: SQLUNIONALL SQLLOB
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28667
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM92790:
See PM92790 APAR/PTF text for additional information about
why a REBIND is necessary.
PM92790 corrects a problem that ABEND04E RC00E70005 at the
location DSNXGRDS DSNXGSFN M628 could happen or SQLCODE -180
1 could be incorrectly issued for an SQL statement that satisfies
all of the following conditions:
1. It contains a table expression or view with SET operator.
2. The CCSIDs of the tables in the SET operation branches are
different.
3. A Date or Timestamp item is in the SELECT list of one of the
SET operation branches.
To make this fix effective for a static application, it must 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 PI28667:
See PI28667 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28667 corrects a problem of ABEND04E RC00C90101 at location
DSNIDM DSNOTFLA ERQUAL5009 when a statement satisfies all of the
following list of conditions:
1. A fullselect statement contains UNION ALL.
2. One of the sub-query select list of UNION ALL references
an item with CLOB or DBCLOB data type.
3. The corresponding of other sub-query select list of UNION
ALL is a literal.
To make this fix effective for a static application, it must 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 PI24608:
See PI24608 APAR/PTF text for additional information about
why a REBIND is necessary.
PI24608 corrects a problem of ABEND04E RC00C900D0 at location
DSNXGRDS DSNXROHB OFFSETCD80 when a statement satisfies all of
the following list of conditions:
1. A fullselect statement contains UNION ALL.
2. One of the sub-query select list of UNION ALL references a
column with BLOB data type.
3. The corresponding of other sub-query select list of UNION ALL
is BINARY or VARBINARY data type.
To make this fix effective for a static application, it must 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 DSNXOCT PI28667
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28667 DSNXOCT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCT
LISTEND
UI23268 COVER LETTER END
UI23270 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27805 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY utility *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40517 DSNUFOBD + x'09F6' *
* can occur during a COPY of *
* DSNDB06.SYSCOPY, DSNDB06.DSNUCH01, *
* DSNDB06.DSNUCX01, or DSNDB06.SYSTSCPY *
* (DB2 11 for z/OS) in a list with *
* objects created in a different *
* database. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
DB2 does not allow DSNDB06.SYSCOPY, DSNDB06.SYSTSCPY and the
indexes over them to be copied in a list with other objects.
User tried to COPY index spaces DSNDB06.DSNUCH01 and
DSNDB06.DSNUCX01 in a list along with other objects from a
different database. Message DSNU537I (object is not allowed in
the list) should be issued in this case, but instead ABEND04E
RC00E40517 at DSNUFOBD OFFSET09F6 happened because COPY utility
could not locate the OBD for one of the unexpected objects.
Additional problems:
In a user database, if a table space or index space is created
using the name SYSLGRNX, DSNLLX01, or DSNLLX02, COPY utility
would allow the user created object to be copied in the same
list as DSNDB01.SYSLGRNX or its indexes. This is incorrect,
COPY utility should issue MSGDSNU537I and terminate with RC8 in
this case.
A similar problem can happen with user objects sharing a space
name with DSNDB01.SYSUTILX or its indexes.
COPY utility has been modified to issue MSGDSNU537I in the
aforementioned scenarios.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27805
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
DSNUBACI PI27805
DSNUBAII PI27805
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27805 DSNUBACI DSNUBAII
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBACI
DSNUBAII
LISTEND
UI23270 COVER LETTER END
UI23272 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI12166 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY LIST SHRLEVEL CHANGE utility *
* with OPTIONS EVENT(ITEMERROR,SKIP) in a data *
* sharing environment. *
****************************************************************
* PROBLEM DESCRIPTION: COPY LIST SHRLEVEL CHANGE on a list of *
* table spaces failed with ABEND04E *
* RC00C90101 DSNICTBU:5001 when DROP *
* TABLESPACE ran concurrently on another *
* member in a data sharing environment. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a COPY LIST SHRLEVEL CHANGE with OPTIONS EVENT
(ITEMERROR,SKIP) on a list of table spaces. During the COPY,
a table space in the LIST was dropped by another data sharing
member after its copy was complete. Then COPY abended when
copying a table space in the same database where the dropped
table space existed.
The abend occurred because COPY was not able to properly
reconcile the DBD information for this database.
The COPY utility has been modified to properly handle this case
where a DROP TABLESPACE has occurred on one of table spaces in
the list.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI12166
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBADR PI12166
DSNUBAII PI12166
1 DSNUBAI2 PI12166
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI12166 DSNUBADR DSNUBAII DSNUBAI2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBADR
DSNUBAII
DSNUBAI2
LISTEND
UI23272 COVER LETTER END
UI23287 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25510 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: -START DATABASE command may fail *
* RC00C200EA (DRAIN FAILURE) when *
* resolving the LPL pages. *
* *
* The output from -DISPLAY DATABASE LPL *
* command may unintentionally contain *
* the string 'DBETE' in the dashed line *
* under the column header 'LPL PAGES'. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When clearing the LPL pages, the page set type for a table space
is not set correctly by the command processor, hence causing a
DRAIN ALL to be issued when not all the pages of the page set
are in LPL. If there are other concurrent read claimers, -START
command may fail RC00C200EA unnecessarily.
When displaying the dashed line under the column header, the
length is not set correctly by -DISPLAY command processor. As a
result, the string 'DBETE' may show up under the column header
'LPL PAGES'.
The code has been changed to correctly set the page set type and
the length of the column header 'LPL PAGES'.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25510
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 PI25510
DSNISREC PI25510
DSNTDMUL PI25510
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25510 DSNILSTS DSNISREC DSNTDMUL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILSTS
DSNISREC
DSNTDMUL
LISTEND
UI23287 COVER LETTER END
UI23292 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22118 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REBUILD INDEX *
****************************************************************
* PROBLEM DESCRIPTION: REBUILD INDEX abends with ABENDS0C9 RC9 *
* at DSNUCINM +x'30E6' *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
After having its indexes dropped, a table was loaded with over
5 million pages of data rows with LOAD REPLACE and without any
statistics being gathered. Without STATISTICS on the LOAD, the
number of pages for that table space is not updated so it
maintained the small number of pages it had from before the
LOAD.
When REBUILD INDEX was run, DB2 attempted to calculate the
number of rows in the table for its index(es). However, the
number of data pages in the table was very high but the number
of table space pages was low from a previous catalog update so
the algorithm, which used 31-bit variables, could not handle the
arithmetic calculations and the ABEND0C9 occurred.
It should be noted that if LOAD REPLACE is not run with the
STATISTICS keyword, RUNSTATS should be run before the rebuilding
of any indexes.
Code has been changed to use larger variables in the calculation
of rows per table to help avoid the aforementioned error.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22118
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCINM PI22118
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22118 DSNUCINM
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCINM
LISTEND
UI23292 COVER LETTER END
UI23324 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27090 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 may occur in module *
* DSN3AUCN when a CICS coordinator is *
* connecting to DB2, and other CICS *
* connections for that coordinator may *
* then receive RC00F30037 when they try *
* to connect to DB2. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 may occur in module DSN3AUCN when the CICS
coordinator is connecting to DB2. Because the coordinator
failed to connect to DB2, other CICS connections for that
coordinator may receive RC00F30037 when they try to connect
to DB2.
This problem occurs when the CICS coordinator had previously
terminated while it had an indoubt UR. In this case, the
SVS pointer was not cleared during that termination processing.
The next connection by the CICS coordinator gets the ABEND0C4.
Module DSN3ID80 has been updated to free the SVS if a CICS
coordinator connection has an indoubt UR when it terminates.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27090
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3ID80 PI27090
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27090 DSN3ID80
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3ID80
LISTEND
UI23324 COVER LETTER END
1
UI23329 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21998 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of LOAD with multiple LOAD *
* utilities in the same job step *
****************************************************************
* PROBLEM DESCRIPTION: LOAD INTO TABLE ENFORCE NO results in *
* an ABEND04E RC00E20029 at DSNSVBK *
* +x'1CE0'. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
Multiple LOAD INTO TABLE ENFORCE NO utilities were run
sequentially in the same jobstep. A control block was built for
a LOAD of a table that had referential integrity and when that
LOAD was completed, the control block was deallocated but a
residual pointer to the storage block remained. When the next
LOAD was executed, on a table with no referential integrity, an
attempt was made to deallocate that same storage because of the
residual pointer which resulted in the ABEND04E RC00E20029 at
DSNSVBK OFFSET1CE0.
Utility clean-up code has been changed to clear the pointer to
this particular storage.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21998
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 PI21998
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21998 DSNUGUCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGUCA
LISTEND
UI23329 COVER LETTER END
UI23333 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27766 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR updates DB2 installation job *
* DSNTIJAS with an optional step to *
1 * protect the tables required for query *
* acceleration from being *
* unintentionally dropped. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR updates DB2 installation job DSNTIJAS with an
optional step to protect the tables required for query
acceleration from being unintentionally dropped.
Keywords:
IDAAV3R1/K IDAAV4R1/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27766
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
This PTF modifies DSNTIJAS, the job for creating the DB2 for
z/OS accelerator database, DSNACCEL. It adds a new, optional
job step that can be used to add RESTRICT ON DROP to the tables
in DSNACCEL to prevent them from being accidentally dropped.
If you have already installed or migrated to this version of DB2
and you maintain a customized copy of job DSNTIJAS then after
applying this PTF, you can add the new job step to the end of
your DSNTIJAS job. You can also run this job step to add
RESTRICT ON DROP to the tables in your accelerator database.
To update your DSNTIJAS job:
(1) Copy the new job step, DSNTICR, including the comment block,
from prefix.SDSNSAMP(DSNTIJAS) into your DSNTIJAS job.
(2) Customize job step DSNTICR for your DB2:
(A) Change the subsystem name '!DSN!' to the SSID of your
DB2.
(B) Change 'DSN!!0' to the prefix of the target library for
DB2.
(C) Change 'DSNTIA!!' to the plan name for DSNTIAD on your
DB2.
To add RESTRICT ON DROP to the tables in your accelerator
database, uncomment job step DSNTICR and then start your
DSNTIJAS job from job step DSNTICR.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIJAS PI27766
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27766 DSNTIJAS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIJAS
1
LISTEND
UI23333 COVER LETTER END
UI23379 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI20544 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of the *
* XMLPARSE and XMLTABLE functions. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE904 with RC00D50001 or *
* RC00D50002 and RESOURCE 0000090A is *
* issued or ABEND04E RC00E70005 *
* DSNNQXCA M111 occurs when the query *
* contains XMLPARSE and its output is *
* passed into XMLTABLE function for *
* further processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the output of the XMLPARSE is passed into XMLTABLE, the
storage used to store the internal XML document generated by the
XMLPARSE function is not released after the XML data has been
processed and is no longer referenced. This causes the XML
storage usage to accumulate. When processing a large amount of
XML documents, the XML storage usage will hit the XML storage
limit and cause SQLCODE -904 to be issued or ABEND04E RC00E70005
DSNNQXCA M111 to occur.
For example:
The following CREATE TABLE statement will create a table with
a VARCHAR column to store an XML document in textual form.
CREATE TABLE T1
(
I1 INTEGER
,C1 VARCHAR(32000)
);
The following query will call XMLPARSE to parse the XML
document into internal XML format and then pass the XML
document into XMLTABLE function for further processing. After
XMLTABLE processes the XML document, the XML document is not
referenced and the storage to store the internal XML document
can be released.
SELECT XT.*
FROM T1,
XMLTABLE('$x/a/b'
PASSING XMLPARSE(C1) AS "x"
COLUMNS
CC VARCHAR(3) PATH 'c',
DD VARCHAR(3) PATH 'd'
) AS XT;
1
The storage used to store the internal XML data is not
released. So when T1 has very large amount of XML documents,
the XML storage usage will hit the XML storage limit. This
causes SQLCODE -904 to be issued or ABEND04E RC00E70005
DSNNQXCA M111 to occur.
DB2 is modified to release the XML storage used to hold the
XMLPARSE output, so the XML storage usage will not accumulate
and SQLCODE -904 will not be issued.
Additional keywords: SQLXML XMLALL SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI20544
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PI20544 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20544 corrects a problem of XML storage not being released
when the query includes XMLPARSE function and its output is
passed into XMLTABLE function for further processing.
To make this fix effective for a static application, it must 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:
PI20544 is the enabling APAR that corrects the problem where
XML storage is not being released when the query includes
XMLPARSE function and its output is passed into XMLTABLE
function for further processing.
Earlier, a pre-conditioning APAR PI19349 was delivered that is
required. In a data sharing group, this pre-conditioning APAR
should be applied to all members before applying this enabling
APAR to any member.
The fix will be enabled once this enabling APAR is applied.
If the 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 PTFs can be rolled through
together.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRTM PI20544
DSNXGUDF PI20544
DSNXOOS2 PI20544
DSNX5TOP PI20544
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI20544 DSNXGRTM DSNXGUDF DSNXOOS2 DSNX5TOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNXGRTM
DSNXGUDF
DSNXOOS2
DSNX5TOP
LISTEND
UI23379 COVER LETTER END
UI23390 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27768 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY utility on table spaces that *
* are simultaneously ALTERED to partition *
* by growth (PBG) table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C20305, RC00C20040, *
* RC00E40195, RC00E40347 on COPY utility *
* on a list of objects which includes *
* table spaces changed to PBG during the *
* execution of the COPY job. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran COPY utility on a list of objects with SHRLEVEL
CHANGE and preceded by OPTIONS EVENT ( ITEMERROR, SKIP ).
The list included a table space that was changed from
nonpartitioned to partition by growth (PBG) with an
ALTER TABLESPACE statement. A REORG utility to
materialize the ALTER completed after the COPY job started
but before the COPY job began copying that object.
The job failed with various abends and secondary reason codes:
00E40195 (force write error on request of utility) in DSNUBADR
+X'1B84' OFFSET1B84 or DSNUBADR +X'1E0E OFFSET1E0E
00C20040 (data set is not opened)
00C20305 (buffer manager function requested against invalid
object)
00E40347 (utility subtask abend)
These failures were caused by COPY utility not correctly
updating all necessary internal information for all objects
in the list prior to copying them.
Note that this problem only occurs when both SHRLEVEL CHANGE
and OPTIONS EVENT (ITEMERROR, SKIP) are used.
Copy utility code was changed to update fields indicating the
object type just prior to copying each object, when SHRLEVEL
CHANGE and OPTIONS EVENT (ITEMERROR,SKIP) is used.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27768
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 DSNUBADR PI27768
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27768 DSNUBADR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBADR
LISTEND
UI23390 COVER LETTER END
UI23402 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28213 -
****************************************************************
* USERS AFFECTED: All DB2 users of LOB and NOT LOGGED objects. *
****************************************************************
* PROBLEM DESCRIPTION: AVOID SETTING RECP FOR NOT LOGGED OR *
* LOG(NO) LOB DURING RESTART *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Today, during DB2 restart, if there is any logging activity
against NOT LOGGED objects, it will be marked in RECP or
RBDP/PSRBD. This results in users to run recover utility to
remove this exception state. However, for the LOB space DB2
always logs space map pages which is sufficient to recover LOB
space during restart. This APAR will avoid unconditionally
marking not logged LOBs in RECP. This will allow normal
completion of LOB space recovery during restart.
DB2 restart logic for not logged objects is modified to avoid
unconditionally marking LOB in RECP (Recover Pending) state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28213
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIECUR PI28213
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28213 DSNIECUR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIECUR
LISTEND
UI23402 COVER LETTER END
1UI23423 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27485 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of CREATE *
* SEQUENCE *
****************************************************************
* PROBLEM DESCRIPTION: Due to massive number of concurrent *
* requests of sequence creation, CREATE *
* SEQUENCE may misleadingly result in *
* SQLCODE20005, the internal ID limit of *
* 2147483391 of sequence has been *
* exceeded *
****************************************************************
* RECOMMENDATION: *
****************************************************************
On massively concurrent requests of sequence creation, DB2
will issue SQLCODE20005 on generating a unique sequence ID
when a max 100 times of retries has been reached. This may be
a misleading message as the internal ID limit may have not
been reached.
DB2 has been modified to improve the retry process such that
it correctly issues SQLCODE20005 when the internal limit of
available sequence IDs has been actually reached. The new logic
also allows DB2 to reuse dropped sequence IDs.
Additional Keywords
SQLCREATE
SQLSEQUENCE
SQLCODE20005
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27485
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 PI27485
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27485 DSNXICQ1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICQ1
LISTEND
UI23423 COVER LETTER END
UI23426 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25854 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who *
* execute SQL including sort merge join with *
* sort on outer table or inner table. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -670 may occur when the *
* following conditions are met: *
* *
* 1. A query is executed with sort *
* merge join. *
* 2. The sort record key length exceeds *
* page size. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When executing or binding a query with sort merge join and
the sort record key length exceeds the page size,
SQLCODE -670 may occur.
For example:
Original SQL:
SELECT *
FROM T1, T2
WHERE T1.C1 = T2.C1
DB2 executes the query by sort merge join. T1.C1 is nullable,
and T2.C1 is not null. The length of T2.C1 is bigger than
32k, so the record key length may exceed the page size if
the DB2 optimizer chooses sort merge join.
ADDITIONAL KEYWORDS:
SQLSMJ SQLMSJ SMJ MSJ SQLCODE670
The problems mentioned above are fixed so that DB2 will choose
an access path which will not result in a sort key that is
too long.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25854
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM57853:
See PM57853 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57853 corrects a problem with incorrect output (less rows
found) that may occur on a query with a join if an index on
the outer table is chosen where predicates exist on multiple
columns of the index, and sort merge join is performed.
To make this fix effective for a static application, it must 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 PM42245:
See PM42245 APAR/PTF text for additional information about
why a REBIND is necessary.
PM42245 corrects a problem of incorrect output that can occur
when a subquery is transformed into a join and sort merge join
is chosen.
To make this fix effective for a static application, it must 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
DSNXOCSK PI25854
DSNXOPSK PI25854
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25854 DSNXOCSK DSNXOPSK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSK
DSNXOPSK
LISTEND
UI23426 COVER LETTER END
UI23428 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24693 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of queries with *
* multiple references on the same table. *
****************************************************************
1 * PROBLEM DESCRIPTION: DB2 may select an inefficient access *
* path for a dynamic query or a static *
* query bound with REOPT(ALWAYS) if the *
* query contains multiple references of *
* a partitioned table and the qualified *
* partitions are empty according to *
* statistics in catalog. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may select an inefficient access path for a dynamic query
or a static query bound with REOPT(ALWAYS) if the query contains
multiple table references on the same partitioned table and the
qualified partitions are empty according to statistics in
catalog.
For example,
SELECT *
FROM T1
WHERE C1 BETWEEN 10001 AND 20000
AND C2 = 10
UNION
SELECT *
FROM T1
WHERE C1 BETWEEN 10001 AND 20000
AND C2 = 10;
If the table T1 is partitioned by C1 and the qualified
partitions are empty according to statistics, DB2 will use real
time statistics (RTS) to help get a more accurate cost
estimation. However, the RTS may only be used for the first
reference of the table when there are multiple references for
the same table T1. Consequently, DB2 may select an
inefficient access path for the query described as above.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE SQLRTS PAGERANGE
DB2 is enhanced to utilize real time statistics to get a more
accurate cost estimation for the cases described as above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24693
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPRS PI24693
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24693 DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPRS
1
LISTEND
UI23428 COVER LETTER END
UI23439 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM93662 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS data sharing users *
* who have non-partitioning indexes *
* defined and delete the SCA structure. *
* e.g.:SETXCF FORCE,STR,STRNM=DSNCAT_SCA *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E in DSNIDM.DSNISREC:5009 may *
* occur when starting DB2 after the SCA *
* structure has been deleted. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Group restart may incorrectly apply the logs during Current
Status Rebuild (CSR) for a non-partitioning index (NPI).
This may result in NPIs with old DBET states incorrectly
returning or ABEND04E in DSNIDM.DSNISREC:5009 when starting
DB2.
Code has been modified to correctly apply the logs for NPIs
during group restart.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM93662
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 PM93662
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM93662 DSNIDBNI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBNI
LISTEND
UI23439 COVER LETTER END
UI23510 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28511 -
****************************************************************
* USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230) *
* users and data sharing users sysplexds. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM abended U2025 in DXRRL2R0 after *
1 * a MODIFY ABEND,NODUMP command. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
By PI09491, IRLM tries to eliminate abendu2025 if IXLRT
REQUEST(UPDATENTRY) is failed with IxlRsnCodeNoRTEntry after
MODIFY ABEND,NODUMP command. However, code checks 4 bytes
RSNCODE incorrectly and it causes IRLM still issues abendu2025.
Additional keywords: ABEND2025
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code is changed to use the last 2 bytes of RSNCODE as the reason
code for IXLRT call.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI28511
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2R0 PI28511
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28511 DXRRL2R0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2R0
LISTEND
UI23510 COVER LETTER END
UI23552 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28671 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS *
* customers who may run mass delete table *
* jobs on multi-table table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNT501I RC00C90088 deadlock on the *
* Real-time Statistics (RTS) catalog *
* table (SYSIBM.SYSTABLESPACESTATS) may *
* occur when running multiple SQL mass *
* delete jobs on multi-table table *
* spaces concurrently. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
Deadlock may occur on SYSIBM.SYSTABLESPACESTATS table when
1 running multiple mass delete jobs on multi-table table spaces
concurrently. Below is a possible scenario for a deadlock.
Job #1 mass deletes table 1 in table space A without a commit.
Job #2 mass deletes table 3 in table space B without a commit.
Job #2 mass deletes table 2 in table space A.
Job #1 mass deletes table 4 in table space B.
SYSIBM.SYSTABLESPACESTATS table maintains statistics at the
table space level and not at the table level.
When job #1 mass deletes table 1 in table space A, a row level
lock is obtained for table space A.
Similarly, job #2 obtains a row level lock for table space B
when it mass deletes table 3 in table space B.
Because job #1 does not commit, job #2 that mass deletes
table 2 in table space A needs to wait for the lock to be
released by job #1.
In the mean time, job #1 that mass deletes table 4 in
table space B waits for job #2 to release the lock on table
space B.
A deadlock is detected.
MSGDSNT375I, MSGDSNT376I, and/or DSNT501I may be issued.
Additional keywords: DSNT375I DSNT376I SYSTABLESPACESTATS
RTS mass delete processing has been modified to resolve the
reported deadlock problem.
Following a mass delete, some of the RTS statistics, such as
TOTALROWS, DATASIZE, and NPAGES, may become null. This is
mainly because, for a multi-table table space, the number of
records removed by a mass delete on a table is unknown.
With this APAR fix applied, the period when the RTS data may
stay nulls becomes longer as in-memory statistics are not
externalized during a mass delete.
In a data sharing environment, RTS statistics may not be
accurate. This problem will be addressed by a future APAR.
While it is not necessary to apply the APAR fix on all data
sharing members at once, the fix does need to be on members
that may run mass delete jobs on multi-table table spaces
concurrently.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28671
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PI28671 corrects a deadlock problem that
occurs when running multiple SQL mass delete jobs on
multi-table table spaces concurrently.
1 The PTF does not need to be applied to all data sharing members
at once.
However, it should be applied to all members where multiple
SQL mass delete jobs on multi-table table spaces are run,
in order to avoid deadlocks.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRTSU PI28671
DSNIRTSX PI28671
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28671 DSNIRTSU DSNIRTSX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRTSU
DSNIRTSX
LISTEND
UI23552 COVER LETTER END
UI23563 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24971 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC/CLI and DB2 Version 11 for z/OS *
* ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: When AUTOCOMMIT is off, insertion of *
* SQL_C_WCHAR data into a VARCHAR or *
* LONG VARCHAR column of length greater *
* than 16352 may fail with various *
* abends or SQLCODE -804 reason code 9 *
* if data bound with a different C data *
* type is inserted into the column *
* prior to the failure. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When inserting SQL_C_WCHAR data into a VARCHAR or LONG VARCHAR
column of length greater than 16352, ODBC needs to allocate
a double SQLDA for the input data. However, if data was
previously inserted into the column using a different C data
type with a single SQLDA, ODBC failed to allocate a larger
SQLDA for the SQL_C_WCHAR data, resulting in various abends
or SQLCODE -804 reason code 9.
Code has been changed to acquire the correct amount of storage
for the SQLDA.
Additional sympton: SQLCODE804
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI24971
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC22 PI24971
DSNAOG0U PI24971
DSNAOG22 PI24971
DSNAOCLI PI24971
DSNAOSDK PI24971
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24971 DSNAOC22 DSNAOG0U DSNAOG22 DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC22
DSNAOG0U
DSNAOG22
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI23563 COVER LETTER END
UI23565 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24100 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of pureXML *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNQOPM:M460 or *
* ABEND04E RC00E70005 DSNNQOPN:M001 may *
* occur when processing the SQL/XML *
* functions and the z/OS Language *
* Environment is not available. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When the z/OS Language Environment is not available, an error
return code is returned when starting the C shell. This error
return code is not handled properly which causes the ABEND.
DB2 is modified to issue error message instead of the ABEND when
the z/OS Language Environment is not available.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24100
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
DSNNQDTM PI24100
DSNNQIV PI24100
DSNNQOPM PI24100
DSNNQOPN PI24100
DSNNQOPR PI24100
DSNNQOPS PI24100
DSNNQRES PI24100
DSNNQXCA PI24100
DSNXQNR PI24100
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24100 DSNNQDTM DSNNQIV DSNNQOPM DSNNQOPN DSNNQOPR DSNNQOPS
DSNNQRES DSNNQXCA DSNXQNR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNQDTM
DSNNQIV
DSNNQOPM
DSNNQOPN
DSNNQOPR
DSNNQOPS
DSNNQRES
DSNNQXCA
DSNXQNR
LISTEND
UI23565 COVER LETTER END
UI23567 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM94679 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* who are using, or plan to use, DB2 for z/OS *
* System Profile Monitoring (SPM) support. *
****************************************************************
* PROBLEM DESCRIPTION: The following problems are reported: *
* * A DB2 for z/OS server unexpectedly *
* rejects new connections with message *
* DSNT772I, csect DSNLILNR and reason *
* code 00E30504. *
* * A DB2 for z/OS server intermittently *
* rejects new connections from *
* different DB2 for z/OS requesters on *
* the same z/OS LPAR. *
* Remote client applications will likely *
* receive SQLCODE -30081. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following problems are reported:
* When an asterisk ('*') character value is specified for any
1 profile monitoring filter criteria, DB2 uses the action
attributes to control the monitoring of all connections or
threads that do not match a more specific profile.
For example, consider a SYSIBM.DSN_PROFILE_TABLE row that is
populated with the LOCATION column set to an asterisk ('*').
A corresponding SYSIBM.DSN_PROFILE_ATTRIBUTES table row is
populated with the KEYWORDS column set to "MONITOR
CONNECTIONS", the ATTRIBUTE1 column set to "EXCEPTION",
and
the ATTRIBUTE2 column set to a value of 10. When such a
profile is activated (-START PROFILE command), DB2 would
collectively limit the maximum number of connections to the
subsystem to a total of 10 connections, if no other specific
(value is not an '*') profile was activated.
However, when a specific value profile was also activated,
the count of the connections which match its filter value is
also erroneously applied against the threshold specified in
the asterisk ('*') monitoring profile. This error causes the
DB2 server to unexpectedly reject inbound connections, as
reflected by message DSNT772I DSNLILNR 00E30504.
* Another case of client applications receiving unexpected
connection failures occurs when those applications are
utilizing different DB2 for z/OS requesters which operate
on the same z/OS LPAR, and hence have the same source TCP/IP
address. When a DB2 for z/OS server receives a new
connection, it cannot distinguish if a specific requesting
client has reached its particular connection threshold or
not. The server can only determine if the threshold of
connections has been reached from a particular TCP/IP
address. This could lead to connection requests being
unexpectedly rejected when a monitoring connections profile
is activated with a filter of a specific value or an asterisk
('*') value.
When the connections are rejected by the DB2 for z/OS server,
remote applications will likely receive SQLCODE -30081.
DB2 server processing is changed as follows:
* A filtering criteria value of an asterisk ('*') for a
profile that monitors connections or threads will now be used
as the separate threshold value for each connection or thread
whose filtering value does not match a specific value profile.
For example, if a threshold value of 10 is specified for a
profile that monitors connections with an asterisk ('*')
filter criteria, and no other specific value profile is
activated, then any particular client connecting from any
remote TCP/IP address would be allowed to establish up to 10
connections to the DB2 server (as long as the CONDBAT
subsystem parameter value is not exceeded). If a specific
value profile is also activated, the threshold of the
specific profile will apply only against connections or
threads whose filter value matches the specific profile.
No other profiles will be examined or applied.
* When a remote DB2 for z/OS requester attempts to connect to
the DB2 for z/OS server, the requester's location name will
now be used to match against any monitoring threads profile
which has a specific location name style of value for the
LOCATION filtering criteria. For any other client type, the
1 name of the requested server location will be used.
This change cannot be used to limit the number of connections
from a particular DB2 for z/OS requester location because
DB2 must accept the connection in order to determine the
requester's location name.
Users can however impose a thread limit. By activating a
profile that monitors threads with a threshold of concurrent
threads and a filter value to be matched against a requesting
DB2 for z/OS location name, users can limit concurrent thread
activity attributed to the requester DB2 for z/OS location.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM94679
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLAGNT PM94679
DSNLCTRC PM94679
DSNLILNR PM94679
DSNLIRTR PM94679
DSNLQDIS PM94679
DSNLQINA PM94679
DSNLTACC PM94679
DSNLTACT PM94679
DSNLTEXC PM94679
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM94679 DSNLAGNT DSNLCTRC DSNLILNR DSNLIRTR DSNLQDIS DSNLQINA
DSNLTACC DSNLTACT DSNLTEXC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLAGNT
DSNLCTRC
DSNLILNR
DSNLIRTR
DSNLQDIS
DSNLQINA
DSNLTACC
DSNLTACT
DSNLTEXC
LISTEND
UI23567 COVER LETTER END
UI23584 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26379 -
****************************************************************
* USERS AFFECTED: DB2 V10 and V11 SQL users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIRSET *
* erqual5007 because DB2 does not *
1 * expect to encounter a zero page. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In DB2 Data Sharing environment, an index page may contain data
rids that are not committed and the data page is not known to
another data sharing member. During index scan, DB2 tolerates
zero page due to the above condition. When the last page read
in was done by Index Scan on a data page that is not in its
buffer pool, a zero page was given. When table space scan
is called to process a data page, any unreleased page from
previous accesses need to be released, zero page is not
expected. So the abend04E rc00c90101 erqual5007 is generated.
DB2 code is changed to allow zero page to be released.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26379
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 PI26379
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26379 DSNIRSET
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRSET
LISTEND
UI23584 COVER LETTER END
UI23590 COVER LETTER START
PROBLEM DESCRIPTION(S):
PM95737 -
****************************************************************
* USERS AFFECTED: All DB2 V10 NFM users of hash table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101, DSNIFOD ERQUAL5063 *
* during insert after ALTER ADD PARTITION *
* on a hash table space. *
* Or ABEND 04E RC00C90101, DSNIFOD *
* ERQUAL501C when insert into a hash *
* table space. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During ALTER ADD PARTITION on a hash table space, the system
page was not reserved for the new added partition. The system
page was inserted into the first segment, but later reserved
dictionary segments will overlay the system page during format
hash process. Which will lead to ABEND04E RC00C90101, DSNIFOD
ERQUAL5063
1 We also fixed another problem in the apar
ABEND04E RC00C90101, DSNIFOD ERQUAL501C occurs during insert
into a hash table space, because the last physical hash page
of the hash table space was not calculated correctly.
DB2 code has been modified to fix the aforementioned problems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PM95737
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 PM95737
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PM95737 DSNIFOD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFOD
LISTEND
UI23590 COVER LETTER END
UI23629 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26675 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNOSER M590 may *
* occur when inserting an XML value *
* without the document node into a table *
* and later on trying to serialize the *
* XML value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E70005 DSNNOSER M590 may occur when inserting an
XML value without the document node into a table and later on
trying to serialize the XML value.
DB2 is modified so the ABEND will not occur.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26675
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNOIRT PI26675
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI26675 DSNNOIRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNOIRT
LISTEND
UI23629 COVER LETTER END
UI23631 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29727 -
****************************************************************
* USERS AFFECTED: All users requested by DB2 service to run *
* DSNJCNVB REPAIR in response to orphan BSDS *
* records. *
****************************************************************
* PROBLEM DESCRIPTION: Minor change to the REPAIR option *
* of the DSNJCNVB utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Minor DSNJCNVB change.
DB2 Version 10 retro-fit of a minor change made in DB2
Version 11 APAR PI22934 that applies to DB2 Version 10.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29727
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJCNVB PI29727
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29727 DSNJCNVB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJCNVB
LISTEND
UI23631 COVER LETTER END
UI23644 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28421 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: An invalid DRDA reply may be returned *
* when a remote client accesses DB2 via *
1 * a SECPORT that is not configured to *
* accept secured traffic. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote client application attempts to access a DB2 for z/OS
server via its secure port (SECPORT), as opposed to its
standard SQL port (TCPPORT), but the connection is not
configured for secure traffic. As a result, DB2 issues message
DSNL031I with reason code 00D31205 and rejects the connection,
which is expected.
However, if DB2 received a chained DRDA command sequence, DB2
will return an invalid DRDA reply.
When a 00D31205 reason code condition is detected as part of a
DRDA chained command sequence, DB2 has been changed to return a
DRDA compliant reply. DB2 will now return a DRDA PRCCNVRM
(CoNVersational PRotoCol error Reply Message) reply containing
DRDA SRVDGN (SeRVer DiaGNostic) information that actually
describes the 00D31205 reason code condition that was detected
at the DB2 server.
Users should be aware that external symptoms may appear to have
not changed. That is, prior to the change, the application
will have likely received SQLCODE -30020, which is associated
to a non compliant DRDA reply. With the change, an SQLCODE
-30020 will likely still be returned, although it will now be
associated to a different cause (the reply is now DRDA
compliant but an unexpected error was still encountered).
In order to prevent the -30020 condition, users should take
action as described by the DB2 for z/OS 00D31205 reason code.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28421
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTEXC PI28421
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28421 DSNLTEXC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTEXC
LISTEND
UI23644 COVER LETTER END
UI23664 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26783 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
1 * users of the UNLOAD FORMAT INTERNAL with *
* UNLDDN defined as binary USS PIPE or FILE - *
* TEMPLATE PATH FILEDATA=BINARY *
****************************************************************
* PROBLEM DESCRIPTION: DFSMS takes too long to write the *
* block when the target of UNLOAD FORMAT *
* INTERNAL is a BINARY USS file or pipe. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When UNLOAD FORMAT INTERNAL passes a buffer to DFSMS to be
written to the USS file or pipe, the DFSMS process to remove the
Record Descriptor Word - RDW takes too long.
UNLOAD has been changed when UNLOADING FORMAT INTERNAL to a
binary USS file or pipe ( UNLDDN to TEMPLATE PATH
FILEDATA=BINARY ) to improve performance.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26783
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
DFSMS APAR OA41617 is required and must be installed in order
to alleviate the problem reported for PM87248.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDYN PI26783
DSNUGSDA PI26783
DSNUULDB PI26783
DSNUULMB PI26783
DSNUULPB PI26783
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26783 DSNUGDYN DSNUGSDA DSNUULDB DSNUULMB DSNUULPB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDYN
DSNUGSDA
DSNUULDB
DSNUULMB
DSNUULPB
LISTEND
UI23664 COVER LETTER END
UI23677 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26905 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of -START DATABASE *
* SPACE command in data sharing environment. *
****************************************************************
* PROBLEM DESCRIPTION: -START DATABASE SPACE PART command on *
1 * an NPI in GRECP status may get ABEND04E *
* RC00C90101 DSNISREC ERQUAL5001 or *
* ERQUAL535B. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The recovery of NPI in GRECP is improperly processed at part
level. As a result DSNISREC abends RC00C90101.
The code is changed to issue msgDSNT316I if -START DB SP PART
command is entered on an NPI in GRECP status.
Explanation of DSNT316I from DB2 Messages publication:
The START DATABASE command was specified for a logical partition
of a nonpartitioned index which has pages in the logical page
list (LPL) or is marked group buffer pool recovery pending
(GRECP). To start a nonpartitioned index with one of these
exception conditions, the START DB command must be specified
without the PART keyword.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26905
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTDCST PI26905
DSNTDINQ PI26905
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26905 DSNTDCST DSNTDINQ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTDCST
DSNTDINQ
LISTEND
UI23677 COVER LETTER END
UI23682 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25068 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V10 and V11 users of *
* LOAD SHRLEVEL CHANGE on a table space *
* defined with the COMPRESS YES and *
* LOCKSIZE TABLESPACE options together. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISMRT ERQUAL1003 *
* when LOAD SHRLEVEL CHANGE utility was *
* running on a table space defined with *
* COMPRESS YES and LOCKSIZE TABLESPACE. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
When LOAD SHRLEVEL CHANGE utility was run on a table space
defined with COMPRESS YES and LOCKSIZE TABLESPACE options,
the dictionary-build process, which was triggered by the insert,
tried to get page lock for dictionary page but there was
no partition lock due to the LOCKSIZE TABLESPACE specification.
So the lock request failed. Hence the abend.
DB2 code has been modified to check the gross lock before
trying to get the page lock for a dictionary page. DB2 will
skip the dictionary page lock when a gross lock is held.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25068
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIZLDL PI25068
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25068 DSNIZLDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIZLDL
LISTEND
UI23682 COVER LETTER END
UI23693 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27691 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of -ACCESS DATABASE *
* MODE(OPEN) command *
****************************************************************
* PROBLEM DESCRIPTION: -ACCESS DATABASE (*) SPACE(*) *
* MODE(OPEN) receives many msgDSNI045I *
* REASON 00C20113 on the console after *
* the number of concurrently open data *
* sets exceeds the zparm DSMAX value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The command processor continues to open the next object even
after getting the DSMAX error RC00C20113. As a result, more
DSNI045I messages may keep displaying on the console until all
the objects are processed.
The code is changed to stop scheduling the service tasks for
OPEN process after encountering DSMAX error.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27691
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
DSNILSTS PI27691
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27691 DSNILSTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILSTS
LISTEND
UI23693 COVER LETTER END
UI23707 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29725 -
****************************************************************
* USERS AFFECTED: All DB2 users of the IBM Data Analytics *
* Accelerator (IDAA). *
****************************************************************
* PROBLEM DESCRIPTION: The following symptoms may occur *
* during a remote query offload: *
* . Abend 04E-00D35011 at *
* DSNLZLLM.DSNLZHR0:0050 *
* . Abend 04E-00D31010 at *
* DSNLIGLM.DSNLCBFM:0005 *
* . Abend 04E-00D31010 at *
* DSNLIGLM.DSNLCCNR:001B *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A remote application connects to a DB2 for z/OS server that is
configured to utilize two or more IDAA servers. The remote
application executes many queries which DB2 offloads across the
multiple IDAA servers. During fetch of the result sets, DB2
may route the fetch to the wrong IDAA server, leading to the
reported abends.
DB2 has been changed to route fetch requests to the correct
IDAA server.
Additional Keywords: IDAAV2R1/K IDAAV3R1/K IDAAV4R1/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29725
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXOQS PI29725
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29725 DSNLXOQS
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXOQS
LISTEND
UI23707 COVER LETTER END
UI23768 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26954 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C20221 in DSNB5DEL, or *
* lost update of a header page, while *
* running concurrent utilities. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a QUIESCE utility is run concurrently with a COPY for the
same table space, the QUIESCE may drive a castout request which
will attempt to purge the header page from the GBP. If an
unusual timing window is hit, where the purge comes immediately
after the COPY has written the header page to the GBP, the purge
may attempt to delete a changed version of the header page. If
the GBP is in a CFLEVEL 17 coupling facility, and if PI09009 is
not applied, then the purge may result in an ABEND04E RC00C20221
in DSNB5DEL. Otherwise, the header page will be successfully
purged and the updates made by the COPY could be lost - this can
result in unnecessary setting of the dirty bits in spacemap
pages later on.
The pseudo-close logic has been modified to no longer request a
purge of the header page when a non-logging updater (e.g. COPY)
is running.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26954
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 PI26954
DSNB5DEL PI26954
DSNB5PCO PI26954
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26954 DSNB1CPL DSNB5DEL DSNB5PCO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPL
DSNB5DEL
1 DSNB5PCO
LISTEND
UI23768 COVER LETTER END
UI23773 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25569 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* customers. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNT376I is issued when an RTS *
* daemon fails to release a row level *
* lock on RTS catalog table, *
* SYSIBM.SYSTABLESPACESTATS or *
* SYSIBM.SYSINDEXSPACESTATS. *
* MSGDSNT501I may follow with reason *
* code 00C9008E. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
DSNT376I with CORRELATION-ID=014.RTSTST00 and DSNT501I
with RC00C9008E are issued for a time out when an RTS daemon
fails to release a row level lock on RTS catalog tables
SYSIBM.SYSTABLESPACESTATS or SYSIBM.SYSINDEXSPACESTATS.
The problem occurs because an internal variable is
inadvertently set to 'BCT' when it should remain as 'RTS'.
This causes the daemon to not release the lock at a commit.
Because the RTS daemon continues to hold on to the lock, when
others attempt to get a lock on the same row, time out occurs
and the messages are issued.
Additional Keywords: Real-time Statistics
The internal variable setting for RTS daemon has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25569
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRTSU PI25569
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25569 DSNIRTSU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRTSU
LISTEND
1UI23773 COVER LETTER END
UI23778 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29114 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: After DB2 has terminated abnormally, *
* Context Services has called the *
* DB2 exit processor which receives *
* an ABEND0C4 when attempting to *
* reference control blocks that have *
* already been freed. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
After DB2 has terminated abnormally, Context Services has
called the DB2 context exit processor which receives
an ABEND0C4 when attempting to reference control blocks
that have already been freed.
Module DSN3RRSX has been updated to avoid the ABEND0C4.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI29114
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3RRSX PI29114
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29114 DSN3RRSX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3RRSX
LISTEND
UI23778 COVER LETTER END
UI23781 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI28619 -
****************************************************************
* USERS AFFECTED: All DB2 10 & 11 users for z/OS with DELETE *
* rule defined in a RI relationship. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90110 DSNIRELS ERQUAL500B *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a DELETE rule for referential constraint is defined,
DB2 attempts to extract the relationship key from the parent OBD
to process a SQL DELETE statement by calling an internal
procedure. The error handling of this procedure is missing,
resulting in an invalid DBD to locate the parent OBD being used,
that causes a DB2 ABEND04E RC00C90110 DSNIRELS ERQUAL500B.
DB2 is changed to add error handling for this internal procedure
when extracting a relationship key from the parent OBD.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28619
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 PI28619
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28619 DSNIRELS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRELS
LISTEND
UI23781 COVER LETTER END
UI23806 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27321 -
****************************************************************
* USERS AFFECTED: All DB2 Data Sharing users *
****************************************************************
* PROBLEM DESCRIPTION: Always enable Fast Log Apply (FLA) for *
* Group Buffer Pool (GBP) Recovery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Today, Fast Log Apply (FLA) is used when multiple table spaces
or indexes are involved in Group Buffer Pool (GBP) recovery
either using START DataBase command or trigger automatically by
DB2. This may result in slower recovery time, if the table space
or index is a partition and multiple partitions being recovered.
The typical GBP recovery has a much wider log range than LPL
recovery so it is possible that using FLA will improve the GBP
1 recovery time. This is not always the case since it depends on
how many log records being applied for a given GRECP object.
This APAR will always used FLA during GBP recovery. It is still
possible that GBP recovery may not use FLA, if all FLA storage
is allocated or there is a shortage of storage in a buffer pool.
DB2 GBP recovery logic is modified to use FLA whenever possible.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27321
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDEFR PI27321
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27321 DSNIDEFR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDEFR
LISTEND
UI23806 COVER LETTER END
UI23855 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI19708 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 for z/OS *
* ODBC/CLI and DB2 Version 11 for z/OS *
* ODBC/CLI. *
****************************************************************
* PROBLEM DESCRIPTION: Following an RRS service call, ODBC *
* generates unnecessary cdump if *
* RRS is not available or has been *
* restarted *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a global transaction is initiated by an ODBC application,
the ODBC driver issues an RRS ATRSPSP2 or ATR4SPSP service call
to acquire information on the state of the transaction and
to perform cleanup when the transaction completes.
In case RRS is not available or has been restarted, this
service call can fail with return code ATR_NOT_AVAILABLE
or ATR_WAS_NOT_AVAILABLE. For both conditions, the driver
does not need to generate a storage dump.
The driver code has been changed to not generate a storage
dump when an RRS service call fails with ATR_NOT_AVAILABLE or
ATR_WAS_NOT_AVAILABLE.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI19708
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG1W PI19708
DSNAOCLI PI19708
DSNAOSDK PI19708
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI19708 DSNAOG1W DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOG1W
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI23855 COVER LETTER END
UI23887 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28113 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the COPY utility. *
****************************************************************
* PROBLEM DESCRIPTION: COPY utility serviceability. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
COPY utility serviceability.
COPY utility serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28113
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBASA PI28113
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28113 DSNUBASA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBASA
LISTEND
UI23887 COVER LETTER END
1
UI23898 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28357 -
****************************************************************
* USERS AFFECTED: DB2 users of external stored procedures *
* and User Defined Functions (UDFs). *
****************************************************************
* PROBLEM DESCRIPTION: If the APPLENV parameter is missing in *
* the WLM start up JCL, ABEND0C4 in *
* DSNX9WLM might happen when the WLM *
* stored procedure address space starts. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a WLM SPAS starts, DB2 code will search the input
parameter string in the WLM start up JCL and locate the value
for parameter APPLENV. If the value for APPLENV is missing, DB2
code incorrectly calculates the position and therefore results
in ABEND0C4 in DSNX9WLM.
DB2 code has been modified to issue the following message
to the console instead of abending:
+DSNX981E DSNX9WLM THE PARAMETER APPLEN CONTAINS AN
INVALID VALUE PROC= xxxxxxxx
Additional Keyword: MSGDSNX981E
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28357
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNX9WLM PI28357
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28357 DSNX9WLM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX9WLM
LISTEND
UI23898 COVER LETTER END
UI23938 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28081 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
1 * PROBLEM DESCRIPTION: ABEND0C4 in DSNB5COM. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A timing window exists during the physical close of a table
space or index, in which a DASD write engine may be running
after a page set control block has been freed. Although the
close drives writes and awaits their completion before freeing
blocks, it's possible for an additional write to be scheduled
if the page set is still on the deferred write queue, even
though it has no modified pages.
The page set physical close code has been modified to ensure
that the object is removed from the deferred write queue, and
no write engines can possibly still be processing it, before
allowing control blocks to be freed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28081
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 PI28081
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28081 DSNB1CPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPP
LISTEND
UI23938 COVER LETTER END
UI23953 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25489 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of queries *
* with OR predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may select an inefficient range *
* list access plan over an efficient *
* single index access plan for a query *
* with OR predicates. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may select an inefficient range list access plan over an
efficient single index access plan for a query with OR
predicates.
In particular, the problem may happen when the single index
access has a good matching filter factor while the range list
1 access has many ranges and can match a superset of matching
columns of the single index access plan.
For example,
SELECT *
FROM T1
WHERE C1=?
AND (C2=? OR C2=? OR C2=? OR C2=? OR C2=? OR C2=? OR
C2=? OR C2=? OR C2=? OR C2=? OR C2=? OR C2 IS NULL);
There are 2 indexes defined on T1 - IX1(C1) and IX2(C1,C2). If
the predicate "C1=?" is very selective, the single index
access
plan could be more efficient as the range list access plan may
probe the index IX2 many times. However, DB2 may incorrectly
favor the range list access plan because it can match a
superset of matching columns of IX1.
Additional Keywords:
SQLACCESSPATH SQLPERFORMANCE SQLRANGELIST RANGELIST
DB2 has been modified to select the efficient access path based
on cost estimation for the cases described as above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25489
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI25489:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI25489 corrects a problem that DB2 may select an inefficient
range list access plan over an efficient single index access
plan for a query with OR predicates if the range list access
plan matches a superset of matching columns of the single
index access plan.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCSC PI25489
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25489 DSNXOCSC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCSC
LISTEND
UI23953 COVER LETTER END
1
UI23959 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27928 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* native SQL PL procedures with LOBs (Large *
* Objects). *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result can be returned *
* from a procedure that uses the SUBSTR *
* function with LOB objects. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result can be returned from a procedure that uses
the SUBSTR function with LOB objects.
The incorrect result can occur because DB2 fails to propagate
the resultant LOB length correctly when creating a LOB locator
from another LOB locator.
The following example helps to illustrate the problem.
Step 1. Create a Table with a LOB column.
CREATE TABLE TCLOB ( C1 CHAR(12), C2 CLOB(1K), C3 SMALLINT);
Step 2. Create a procedure with LOB parameters.
CREATE PROCEDURE CLOBSP1 (IN PARM1 CLOB(1K),
OUT PARM2 CLOB(1K),
OUT PARM3 CLOB(1K))
VERSION V1
LANGUAGE SQL
DISALLOW DEBUG MODE
MODIFIES SQL DATA
WLM ENVIRONMENT FOR DEBUG MODE DSNXWLM
SPBODY:BEGIN
SET PARM2 =SUBSTR(PARM1,1,9)|| '679'||SUBSTR(PARM1,13,3);
SET PARM3 =SUBSTR(PARM2,1,3)||'1234'||SUBSTR(PARM2,7,10);
INSERT INTO TCLOB VALUES ('CLOBSP1ROW1', PARM2,LENGTH(PARM2));
INSERT INTO TCLOB VALUES ('CLOBSP1ROW2', PARM3,LENGTH(PARM3));
END SPBODY!
Step 3. When executing this procedure, an incorrect result can
be returned.
DB2 code has been modified to correct the problem which can
result in an incorrect result being returned when using a LOB
1 with the SUBSTR function for a native SQL procedure.
Additional Keywords: DB2INCORR/K INCORROUT SQLLOB
SQLINCORROUT SQLSUBSTR SQLUDF
SQLSP SQLNATIVESQLPL SQLSTOREDPROCEDURE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27928
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOTCSO PI27928
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27928 DSNOTCSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOTCSO
LISTEND
UI23959 COVER LETTER END
UI24011 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28696 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG utility with a multi-table *
* table space. *
****************************************************************
* PROBLEM DESCRIPTION: Storage overlays can occur during *
* a REORG TABLESPACE of a multi-table *
* table space that has dropped tables. *
* The following dumps may be issued: *
* - ABEND0C4 RC00000038 DSNUGSTA *
* OFFSET1F48 *
* - ABEND04E RC00E20005 DSNSVBK *
* OFFSET1AB6 *
* - ABEND04E RC00E2000E DSNSVSFM *
* OFFSET078A *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While REORG is running on a multi-table table space, DB2 doesn't
include the size of a dropped table when determining the size of
the storage to allocate for a work area that is used for
decompressing or editproc decoding records.
Later it tries to use the work area, which leads to the storage
overlay because the allocated storage is of insufficient size.
DB2 code has been modified to ensure that the work area is of
maximum size needed to handle any dropped tables.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI28696
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRFNX PI28696
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28696 DSNIRFNX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRFNX
LISTEND
UI24011 COVER LETTER END
UI24030 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25055 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Page parity errors, reported by message *
* DSNT500I from CSECT DSNB1GSR, with *
* reason code RC00C200FD. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In data sharing, one member reading a page from DASD while
another member is writing the same page may experience an
intermittent page parity error due to seeing partial results.
The existing redrive logic may not always correct the problem
because it is possible for more than one read to take place
before the write completes.
The page parity read redrive logic has been enhanced to perform
additional re-reads if necessary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25055
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB5RAP PI25055
DSNB5RDP PI25055
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25055 DSNB5RAP DSNB5RDP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNB5RAP
DSNB5RDP
LISTEND
UI24030 COVER LETTER END
UI24056 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25434 -
****************************************************************
* USERS AFFECTED: All LOB users of DB2 10 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -904 with reason code *
* RC00C90D01 during a SELECT of a LOB *
* column when using isolation(UR) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When selecting a LOB column using isolation(UR), the matching
index entry in the auxiliary index for the LOB could not be
found. This occurred because the entry in the index has been
physically deleted. The index entry was physcially deleted
because the SELECT did not claim the auxiliary index in time.
DB2 code is changed to claim the aux index earlier to narrow
down this window.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25434
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISELL PI25434
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25434 DSNISELL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISELL
LISTEND
UI24056 COVER LETTER END
UI24074 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26116 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE SORTDATA YES *
* following an ALTER TABLE PARTITION to change *
* the limitkey. *
****************************************************************
1 * PROBLEM DESCRIPTION: DSNU241I shows an inadequate *
* compression dictionary was built during *
* a REORG TABLESPACE SORTDATA YES with *
* partitions in REORG PENDING (REORP). *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An ALTER PARTITION x ENDING AT (new limit_key) placed partitions
in REORP. A REORG TABLESPACE SORTDATA YES was run to build new
compression dictionaries and reorganize the data. MSGDSNU241I
for one or more of the partitions showed that the dictionaries
were built from too few rows resulting in a very low compression
ratio for the partition(s).
When REORG TABLESPACE is run after limit keys are altered, it's
possible to unload the rows out of partition order. Although
REORG will continue building the dictionary, it did not process
enough rows for the dictionary.
REORG has been modified to correct the aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26116
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURSCN PI26116
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26116 DSNURSCN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURSCN
LISTEND
UI24074 COVER LETTER END
UI24090 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30406 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 users of ridlist access and *
* USE CURRENTLY COMMITTED concurrent access *
* resolution. *
****************************************************************
* PROBLEM DESCRIPTION: Ridlist access timed out due to waiting *
* for delete transaction to commit even *
* though USE CURRENTLY COMMITTED is used *
* as CONCURRENT ACCESS RESOLUTION. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a query uses ridlist access, and Currently Committed is used
as CONCURRENT ACCESS RESOLUTION, it still waits for the delete
1 transaction to commit. As a consequence, the query times out.
DB2 code has been modified to let ridlist access honor USE
CURRENTLY COMMITTED semantic.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30406
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISRID PI30406
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30406 DSNISRID
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISRID
LISTEND
UI24090 COVER LETTER END
UI24100 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27220 -
****************************************************************
* USERS AFFECTED: ALL DB2 10, 11 for z/OS users of CREATE AUX *
* TABLE. *
****************************************************************
* PROBLEM DESCRIPTION: CREATE AUX TABLE abend with ABEND04E *
* RC00E40601 at DSNUEXDL offset 14EE and *
* SQLCODE -204 during migration process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 incorrectly checks the database creator length instead of
database name length. This problem occurs whenever an
auxiliary table is created and there might be other unexpected
symptoms. The following paths are affected:
1. CREATE AUXILIARY TABLE.
2. CREATE TABLE with LOB column where DB2 implicitly creates
the supporting auxiliary objects.
3. ALTER TABLE ADD LOB column where DB2 implicitly creates the
supporting auxiliary objects.
4. CATMAINT migration that creates auxiliary catalog tables
(V9 to V10, and V10 to V11).
5. Whenever a partition is grown or added to a table space
with LOB columns.
DB2 has been modified to check the correct name length and
convert the database name correctly.
Additional Keywords:
ABEND04E
DB2MIGV10/K
1 DB2MIGV11/K
SQLALTER
SQLCREATE
SQLCODE204
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27220
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICB7 PI27220
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27220 DSNXICB7
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICB7
LISTEND
UI24100 COVER LETTER END
UI24111 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25747 -
****************************************************************
* USERS AFFECTED: All DB2 users with PPRC enabled DASD *
* subsystems. *
****************************************************************
* PROBLEM DESCRIPTION: Provide support for zHyperWrite for *
* active log data sets. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides support for using zHyperWrite with DB2
active log data sets. A new ZPARM, REMOTE_COPY_SW_ACCEL
enables or disables the use of zHyperWrite. The default
is disabled. Enabling the function may improve active log
write performance if the active log data sets reside on PPRC
volumes. Improved active log write performance may result in
improved response time for DB2 operations that must ensure the
log records have been externalized before continuing. When
zHyperWrite is enabled, increased SRB time in the xxxxMSTR
address space may be observed.
MSGDSNJ370I is updated to indicate the status of zHyperWrite
usage for the active log data sets. The following line is
added to the output of the -DISPLAY LOG command:
SOFTWARE ACCELERATION IS <accel-status>
where <accel-status> is either ENABLED or DISABLED.
1 The PTFs for the following APARs are required for DB2 to use
zHyperWrite. If the PTFs are not installed, the request to
use zHyperWrite will be ignored and the I/O will be processed
as though zHyperWrite was not requested.
DFSMS APARs:
OA41906
OA43661
OA43662
OA43663
OA44973
OA45125
z/OS APARs:
OA43453
OA44240
OA45662
zHyperWrite D/TDS8870 D/T8870
There is no negative effect if zHyperWrite is requested and
the active log data sets are not on PPRC enabled volumes.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25747
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
PM99151 introduces the following changes to externals:
The command response messages for the -DISPLAY ARCHIVE command
are being changed to prevent the truncation of the archive log
data set name when the data set name exceeds 42 characters in
length. The archive read data lines follow the DSNJ322I
header message. To avoid the possible data set name
truncation, the STATUS column in the archive log data lines
will be changed from 6 characters to 4 characters. For
example - before the APAR change:
DSNJ322I @ DISPLAY ARCHIVE REPORT FOLLOWS-
COUNT TIME
(TAPE UNITS) (MIN,SEC)
DSNZPARM 3 0,00
CURRENT 3 0,00
===============================================
ADDR STATUS CORR-ID VOLSER DATASET_NAME
BUSY SHEDDEN A00780 DSNC000.VA1A.ARCLG1.D13277.....
And after the APAR change:
DSNJ322I @ DISPLAY ARCHIVE REPORT FOLLOWS-
COUNT TIME
(TAPE UNITS) (MIN,SEC)
DSNZPARM 3 0,00
CURRENT 3 0,00
===============================================
ADDR STAT CORR-ID VOLSER DATASET_NAME
1 BUSY SHEDDEN A00780 DSNC000.VA1A.ARCLG1.D13277......
END OF DISPLAY ARCHIVE REPORT.
DSN9022I @ DSNJC001 '-DIS ARC' NORMAL COMPLETION
The STATUS column heading is being changed to STAT.
Also, the AVAIL status is being changed to AVL and the
RECALL status is being changed to RCAL. If there is
automation in place that parses the -DISPLAY ARCHIVE
command response messages, adjustments will have to be
made to account for these changes.
Information about these changed messages 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:
This PTF modifies message DSNJ370I output by the -DISPLAY LOG
command to indicate whether or not zHyperWrite will be requested
when writing the active log data sets.
DSNJ370I csect-name LOG DISPLAY
CURRENT COPY1 LOG = <dsname1> IS <pct>% FULL
CURRENT COPY2 LOG = <dsname2> IS <pct>% FULL
H/W RBA = <hw-rba>
H/O RBA = <ho-rba>
FULL LOGS TO OFFLOAD = nn OF mm,
OFFLOAD TASK IS <status>
SOFTWARE ACCELERATION IS <accel-status>
The last line of the DSNJ370I message is new with this PTF. The
rest of the message is unchanged.
Values for <accel-status> are
ENABLED - zHyperWrite will be requested for active log writes
DISABLED - zHyperWrite will not be used for active log writes
If zHyperWrite is requested, but the active log resides on a
volume that does not support zHyperWrite, the zHyperWrite
option is ignored and the log write is done as though
zHyperWrite was not requested.
This PTF adds a new DB2 subsystem parameter in DSN6LOGP called
REMOTE_COPY_SW_ACCEL that can be used to specify whether DB2
should use software to control the remote copy process for
active log output in PPRC environments. Valid settings are:
* DISABLE: Means that the hardware PPRC
function is used if available;
this setting is appropriate for
non-PPRC environments.
==> This is the default setting
* ENABLE : Means that host software is used;
this option can improve overall DB2
performance in PPRC environments at
the expense of some additional SRB
CPU time in the xxxxMSTR address
1 space. z/OS Version 2 Release 1
or later is required to support
this function.
The setting of REMOTE_COPY_SW_ACCEL is changeable via the
-SET SYSPARM command.
To use zHyperWrite, the following z/OS APARs are required:
OA41906
OA43661
OA43662
OA43663
OA44973
OA45125
OA43453
OA44240
OA45662
If these APARs are not installed, the setting of
REMOTE_COPY_SW_ACCEL has no effect. DB2 will function as if
DISABLE was specified.
---------------------------------------------------------------
If you have already installed or migrated to this version of
DB2, you need to take the following actions after applying this
PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
---------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
==> This action is 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 REMOTE_COPY_SW_ACCEL=<x>
(where <x> is DISABLE or ENABLE) to the invocation of the
DSN6LOGP macro. Make sure to add a continuation
1 character in column 72 if needed. If you omit adding
REMOTE_COPY_SW_ACCEL 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 REMOTE_COPY_SW_ACCEL to
the CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
REMOTE_COPY_SW_ACCEL CHAR M DISABLE ENABLE <x>
Change <x> to the value you specified for
REMOTE_COPY_SW_ACCEL in step (2), above.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
----------------------------------------------------------
ACTION:
To use zHyperWrite for active log data set writes, several
actions are required:
- Set the new REMOTE_COPY_SW_ACCEL ZPARM to ENABLE
- Apply the z/OS maintenance listed in the ++HOLD DOC
- Install microcode level 7.4 on DS8870 DASD subsystems where
active log data sets reside.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI25747
DSNDQWPZ PI25747
DSNFJDIR PI25747
DSNFMDIR PI25747
DSNJCHGZ PI25747
DSNJC00A PI25747
DSNJDS02 PI25747
DSNJDS03 PI25747
DSNJS001 PI25747
1 DSNJW009 PI25747
DSNJW107 PI25747
DSNTIDXA PI25747
DSNTIDXB PI25747
DSNTIJUZ PI25747
DSNTINST PI25747
DSNTXAZP PI25747
DSNWZIFA PI25747
DSN6LOGP PI25747
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25747 DSN@XAZP DSNDQWPZ DSNFJDIR DSNFMDIR DSNJCHGZ DSNJC00A
DSNJDS02 DSNJDS03 DSNJS001 DSNJW009 DSNJW107 DSNTIDXA
DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSN6LOGP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNFJDIR
DSNFMDIR
DSNJCHGZ
DSNJC00A
DSNJDS02
DSNJDS03
DSNJS001
DSNJW009
DSNJW107
DSNTXAZP
DSNWZIFA
MACROS
DSN@XAZP
DSNDQWPZ
DSNTIDXA
DSNTIDXB
DSNTIJUZ
DSNTINST
DSN6LOGP
LISTEND
UI24111 COVER LETTER END
UI24115 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31215 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of UNLOAD utility with WHEN clause. *
****************************************************************
* PROBLEM DESCRIPTION: INCORROUT happened when an UNLOAD FROM *
* TABLE table_name WHEN col LIKE val was *
* running on a UNICODE table, and the *
* column in the LIKE predicate was a *
* fixed length and nullable column. *
****************************************************************
1 * RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
An UNLOAD FROM TABLE table_name WHEN col LIKE val was unloading
data from a UNICODE table. The column in the LIKE predicate was
a fixed length and nullable column. The data unloaded was not
expected.
The problem occurred because an internal pointer was incorrectly
set when CCSID conversion was needed. This occurs when the
table is UNICODE and the SYSIN is EBCDIC or the table is EBCDIC
and the SYSIN is UNICODE.
The same problem could happen for NOT LIKE predicate with fixed
length and nullable column, as well as REORG DISCARD WHEN.
The code has been modified to correctly setup the internal
pointer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31215
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUUGMS PI31215
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31215 DSNUUGMS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUUGMS
LISTEND
UI24115 COVER LETTER END
UI24155 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31086 -
****************************************************************
* USERS AFFECTED: All users of the SYSPROC.WLM_REFRESH stored *
* procedure in DB2 10 for z/OS and DB2 11 for *
* z/OS are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: When the SYSPROC.WLM_REFRESH stored *
* procedure is called with the SSID *
* input parameter set to null or blanks, *
* all of the following errors occur: *
* - The call fails with SQLCODE -430 *
* - The address space of the WLM *
* environment indicates this error: *
* USER COMPLETION CODE=4039 *
* REASON CODE=00000000 *
* - The CEEDUMP of the WLM address *
* space contains the following *
* message: *
* CEE3250C The system or user abend *
1 * S72A R=00000010 was *
* issued. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
WLM_REFRESH is a DB2-supplied stored procedure that can be
called by an authorized user to request refresh of a specified
WLM environment on a remote or local system. The external module
for WLM_REFRESH is called DSNTWR.
When WLM_REFRESH is called with a null or blank SSID input
parameter setting, DSNTWR starts a subtask called DSNTWRE to
query DB2 for the subsystem name and the data sharing group
attach name. SSID is assigned the group attach name if one
is defined, otherwise it is assigned the subsystem name.
DSNTWR uses the z/OS ATTACHX macro to start DSNTWRE as a
subtask. Currently, the control parameter list passed to
DSNTWRE is not initialized correctly (only the first four
bytes are initialized). As a result, the attach request
can fail with the symptoms noted in the problem description
section.
This APAR modifies DSNTWR to correct initialization of the
control parameter list for attaching DSNTWRE as a subtask.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31086
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI31086
This PTF modifies DSNTWR, the external module for the
SYSPROC.WLM_REFRESH stored procedure. It fixes a bug that
can cause SYSPROC.WLM_REFRESH to fail with abend S72A reason
code 10 when called with a NULL or blank SSID parameter.
Post-apply actions for this PTF:
-------------------------------
If you have already installed or migrated to this version of
DB2, you need to take the following actions after applying this
PTF:
(1) Rebuild or delete any private copies of module DSNTWR
(2) Bind the package for DSNTWR
----------------------------------------------------------------
(1) Rebuild or delete any private copies of module DSNTWR
***********************************************************
* This action is required for all customers who maintain
* a private copy of DSNTWR, the external module for
* WLM_REFRESH
***********************************************************
This PTF updates DSNTWR, the DB2-supplied load module for
WLM_REFRESH, in the prefix.SDSNLOAD library. It also
updates DSNTWRS, the sample source code for DSNTWR, in the
prefix.SDSNSAMP library.
1
If you maintain a private copy of module DSNTWR, you either
need to delete it in order to use the DB2-supplied DSNTWR
module instead or you need to update it to include the
changes introduced by this PTF.
To continue maintaining your own DSNTWR module, proceed
as follows:
(a) Compare your source code to that in member DSNTWRS of
the prefix.SDSNSAMP library to identify necessary code
changes.
(b) After completing your code changes, use job steps
PH06WS01 and PH06WS02 of your customized copy of job
DSNTEJ6W to prepare an updated DSNTWR module and to bind
a package from the updated DBRM.
----------------------------------------------------------------
(2) Bind the package for DSNTWR
***********************************************************
* This action is required for all customers who use the
* DB2-supplied DSNTWR module
***********************************************************
This PTF updates DSNTWR, the external module for WLM_REFRESH
plus the DBRM for DSNTWR. After applying this PTF, proceed
as follows to bind a package from the updated DSNTWR DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@WR PI31086
DSNTWR PI31086
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31086 DSN@WR DSNTWR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTWR
MACROS
DSN@WR
1 LISTEND
UI24155 COVER LETTER END
UI24164 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27903 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LOB. *
****************************************************************
* PROBLEM DESCRIPTION: When executing CREATE TABLE with a LOB *
* column in an implicitly defined table *
* space on RRF disabled DB2 system *
* (RRF = OFF), an extra base table record *
* will be inserted into SYSIBM.SYSCOPY *
* catalog table. *
* *
* If a REPAIR DBD DIAGNOSE/TEST utility *
* job is executed against the database *
* where the newly created table resides, *
* errors will be reported. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When executing CREATE TABLE with a LOB column in an implicitly
defined table space on RRF disabled DB2 system (RRF = OFF), an
extra base table record is incorrectly inserted into SYSIBM.
SYSCOPY catalog table.
If a REPAIR DBD DIAGNOSE/TEST utility job is executed against
the database where the newly created table resides, errors will
be reported. Following are the sample error message:
DSNU922I DSNUEDDR - OBD X'0001' MISSING IN REBUILT DBD
DSNU913I DSNUEDDR - OBD X'0001' COMPARISON COMPLETE -- 1
ERRORS WERE FOUND
DSNU922I DSNUEDDR - OBD X'0002' MISSING IN REBUILT DBD
DSNU913I DSNUEDDR - OBD X'0002' COMPARISON COMPLETE -- 1
ERRORS WERE FOUND
DSNU915I DSNUEDLO - OBD X'0001' E-X'00000F3C' R-X'00000000'
A FILE OBD IS MISSING IN THE REBUILT
DBD
DSNU915I DSNUEDLO - OBD X'0002' E-X'00000E04' R-X'00000000'
A FILE PAGESET OBD IS MISSING IN THE
REBUILT DBD
DSNU915I DSNUEDLO - OBD X'0003' E-X'00000D84' R-X'00000F3C'
A FILE OBD FOR TABLESPACE MYTBRLOB
DSNU915I DSNUEDLO - OBD X'0004' E-X'00000C4C' R-X'00000E04'
A FILE PAGESET OBD FOR TABLESPACE
MYTBRLOB
DSNU915I DSNUEDLO - OBD X'0005' E-X'00000AC4' R-X'00000C7C'
A RECORD-TYPE OBD IN TABLESPACE
MYTBRLOB
1 DSNU915I DSNUEDLO - OBD X'0006' E-X'000009C4' R-X'00000B7C'
AN INDEX FANSET OBD FOR INDEX
MYTB1UZ1
DSNU915I DSNUEDLO - OBD X'0007' E-X'000008C8' R-X'00000A80'
AN INDEX PAGESET OBD FOR INDEX
MYTB1UZ1
DSNU915I DSNUEDLO - OBD X'0008' E-X'00000848' R-X'00000A00'
A FILE OBD FOR TABLESPACE LLYD1KXJ
DSNU915I DSNUEDLO - OBD X'0009' E-X'00000710' R-X'000008C8'
A FILE PAGESET OBD FOR TABLESPACE
LLYD1KXJ
DSNU915I DSNUEDLO - OBD X'000A' E-X'000005AC' R-X'00000764'
A RECORD-TYPE OBD IN TABLESPACE
LLYD1KXJ
DSNU915I DSNUEDLO - OBD X'000B' E-X'00000544' R-X'000006FC'
AN AUX. RELATIONSHIP OBD IN TABLE
MYTB_LOB
DSNU915I DSNUEDLO - OBD X'000C' E-X'00000438' R-X'000005F0'
AN INDEX FANSET OBD FOR INDEX
IMYTBRST
DSNU915I DSNUEDLO - OBD X'000D' E-X'0000033C' R-X'000004F4'
AN INDEX PAGESET OBD FOR INDEX
IMYTBRST
DSNU912I DSNUEDLO - OBD LISTING COMPLETE -- 2 ERRORS WERE
FOUND
There may be other unexpected symptoms.
When DB2 creates the implicitly defined table space for the base
table with a LOB column in it, DB2 accidentally inserts an extra
base table record in SYSCOPY catalog table if the RRF (REORDERED
ROW FORMAT) is disabled. This extra SYSCOPY record, its
START_RBA, ICTIME, and TIMESTAMP column value are slightly
different than the previous inserted record.
Following is an example of such failing scenario:
1. Create a table with a LOB column in an implicitly defined
table space:
CREATE TABLE MYTB_LOB
(REPORT_KEY VARGRAPHIC(119) NOT NULL WITH DEFAULT ' ',
STATUS_TEXT CLOB(500 M) WITH DEFAULT NULL
INLINE LENGTH 2000,
CONSTRAINT REPORT_KEY
PRIMARY KEY (REPORT_KEY))
PARTITION BY SIZE EVERY 64G
AUDIT NONE
DATA CAPTURE NONE
CCSID UNICODE
BUFFERPOOL BP16K0
NOT VOLATILE
APPEND NO !
2. An extra row can be found in the SYSCOPY catalog table:
1 SELECT *
FROM SYSIBM.SYSCOPY
WHERE DBNAME = (SELECT DBNAME
FROM SYSIBM.SYSTABLES
WHERE NAME = 'MYTB_LOB')
!
3. Executing a REPAIR DBD DIAGNOSE/TEST utility job, errors
will be reported
REPAIR DBD DIAGNOSE DATABASE DSN00009
Applying APAR PI27903 will not remove the existing extra
record in SYSCOPY catalog table. If needed, user could either
1. DROP the affected tables, then recreate them to remove the
extra row in SYSCOPY table.
2. Or execute a utility MODIFY RECOVERY job to remove it:
MODIFY RECOVERY TABLESPACE database-name.table-space-name
DELETE AGE(*)
Then execute a utility REPAIR DBD REBUILD job to fix the
DBD error:
REPAIR DBD REBUILD DATABASE database-name
Please note, if user elects the option 2, after the MODIFY
RECOVERY TABLESPACE job executed, the extra SYSCOPY record is
removed. However, the REPAIR DBD DIAGNOSE/TEST job still reports
error. In order to fix it, users needs to execute the REPAIR DBD
REBUILD job to correct it.
DB2 has been modified to not insert an extra base table space
record in SYSCOPY catalog table when creating an implicitly
defined table space for a table with a LOB column in it in the
RRF disabled system.
Additional keywords: SQLCREATE SQLLOB
REPAIRDBD
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27903
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
Applying APAR PI27903 will not remove the existing extra record
from SYSIBM.SYSCOPY catalog table.
If needed, after applying APAR PI27903, the user could either
1. DROP the affected tables, then recreate them to remove the
extra SYSCOPY record.
2. OR execute a utility MODIFY RECOVERY job to remove it:
MODIFY RECOVERY TABLESPACE database-name.table-space-name
DELETE AGE(*)
Then execute a utility REPAIR DBD REBUILD job to fix the
DBD error:
REPAIR DBD REBUILD DATABASE database-name
1 Please note, if user elects the option 2, after the MODIFY
RECOVERY TABLESPACE job executed, the extra SYSCOPY record will
be removed. However, the REPAIR DBD DIAGNOSE/TEST job still
reports error. In order to fix it, users needs to execute the
REPAIR DBD REBUILD job to correct it.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXICTS PI27903
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27903 DSNXICTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXICTS
LISTEND
UI24164 COVER LETTER END
UI24178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28180 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE utility *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40316 DSNURSCN + x'42AA' *
* occurred when a REORG TABLESPACE *
* SORTDATA NO was terminated in UNLOAD *
* phase by -TERM UTILITY command *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran a REORG TABLESPACE SORTDATA NO and issued -TERM UTILITY
command to terminate the execution of this utility job step when
the REORG was running in the UNLOAD phase. ABEND04E RC00E40316
at DSNURSCN OFFSET42AA happened because the REORG utility did
not terminate the execution properly and continued to unload
data.
REORG TABLESPACE SORTDATA NO has been modified to terminate
properly when it's terminated by -TERM UTILITY command.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28180
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURULD PI28180
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28180 DSNURULD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNURULD
LISTEND
UI24178 COVER LETTER END
UI24187 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29292 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users that have active *
* logs defined as striped data sets. If *
* the active log copy 1 data sets have a *
* different number of stripes than the copy 2 *
* active log data sets the problem is more *
* likely to occur. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00D1F001 during xxxxMSTR *
* address space initialization, followed *
* by ABEND04F and termination of the DB2 *
* subsystem. The failure only occurs if *
* all of the following conditions are *
* met: *
* 1. The active log data sets are striped *
* 2. The subsystem parameters specify *
* dual logging (DSN6LOGP parameter *
* TWOACTV is set to YES) *
* 3. The DB2 subsystem was abnormally *
* terminated due to a failure in z/OS, *
* a failure in IRLM, a failure in DB2, *
* a cancel or force of one of the DB2 *
* address spaces or the IRLM address *
* space or failure of either the *
* processor that the DB2 subsystem *
* was active on or the DASD subsystem *
* that contained one or more stripes *
* of the active log data set(s). *
* 4. The last write to the active logs *
* spanned more than one stripe and *
* did not complete for all stripes. *
* An incomplete copy or mirror of the *
* active log data sets can place the *
* logs in the same condition since it *
* may result in a state that is the *
* same as could be caused by an I/O *
* that did not complete. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a DB2 subsystem is using striped active logs, the restart
process will check the two copies for inconsistencies due to
an I/O not being completed when expected. In the reported
failure, the number of stripes in the active log data sets
was different and the number of CIs in the last write I/O was
1 exactly the same as the difference in the number of stripes.
When this happens and the log copy with less stripes has more
data written (i.e., the logical end has a higher RBA value), the
comparison to determine whether or not the last CI in each
stripe overlaps between copies may be incorrect. This in turn
causes a subsequent internal logic check to fail, resulting
in the ABEND04E RSN00D1F001.
The end of data set consistency checking between stripes of an
active log has been updated to handle the reported problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29292
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 PI29292
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29292 DSNJW009
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW009
LISTEND
UI24187 COVER LETTER END
UI24191 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26030 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 and *
* DB2 Version 11 for z/OS ODBC/CLI driver *
****************************************************************
* PROBLEM DESCRIPTION: Positioned update statement failed *
* with SQLSTATE 34000 indicating that *
* the cursor name is invalid. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a positioned update statement is issued, cursor name on
the positioned update statement is not recognized. SQLPrepare()
failed with SQLSTATE 34000.
The following example illustrates the problem:
1. Prepare a select statement on statement handle 1 to generate
a result set.
2. Call SQlSetCursorName to associate a cursor name with
statement handle 1.
rc=SQLSetCursorName(hstmt1, (char *)"ABC", SQL_NTS);
1
3. Execute the select statement.
4. Allocate statement handle 2 to execute the positioned update.
5. Prepare the positioned update statement with cursor name
'ABC'.
strcpy((char*) sqlstmt2,
"UPDATE ADMF001.TAB1 SET COL1 = ? WHERE CURRENT OF
ABC");
rc = SQLPrepare(hstmt2, sqlstmt2, SQL_NTS);
SQLPrepare() failed with the following error message:
sqlstate=34000
sqlcode=-99999
error={DB2 FOR OS/390} {ODBC DRIVER} SQLSTATE=34000
ERRLOC=2:109:2
The driver code has been changed to recognize the cursor name
on the positioned update statement.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI26030
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG0A PI26030
DSNAOCLI PI26030
DSNAOSDK PI26030
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26030 DSNAOG0A DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOG0A
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI24191 COVER LETTER END
UI24195 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27190 -
****************************************************************
* USERS AFFECTED: All users of DSNTRVFY, the validation tool *
* for DB2-supplied stored procedures and *
* user-defined functions (UDFs) in DB2 10 *
* for z/OS and DB2 11 for z/OS, are affected *
1 * by this change. *
****************************************************************
* PROBLEM DESCRIPTION: One or both of the following errors *
* occurs when running job DSNTIJRV, job *
* step DSNTRVFY (program DSNTRVFY): *
* *
* (1) DSNTRVFY terminates with return *
* code 8 and one or more occurrences *
* of these messages: *
* DSNT031I DSNTRVFY VALIDATION FOR *
* schema.routine FAILED *
* DSNT034I DSNTRVFY - AN ERROR WAS *
* ENCOUNTERED DURING CALL *
* TO ROUTINE, SQLCODE = *
* -302 *
* DSNT408I SQLCODE = -302, ERROR: *
* THE VALUE OF INPUT *
* VARIABLE OR PARAMETER *
* NUMBER n IS INVALID OR *
* TOO LARGE FOR THE TARGET *
* COLUMN OR THE TARGET *
* VALUE *
* *
* (2) DSNTRVFY runs normally but issues *
* a DISPLAY WLM,APPLENV=* request *
* for every DB2-supplied routine *
* that has a WLM ENVIRONMENT setting *
* of DSNWLM_NOT_ENABLED. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
Job DSNTIJRV executes program DSNTRVFY which can be used to
validate installation and configuration of DB2-supplied stored
procedures and UDFs. Currently, there are two problems
affecting DSNTRVFY:
(1) SQLCODE -302 because of the value of an input parameter is
invalid:
For most DB2-supplied routines, DSNTRVFY performs a CALL
as a final validation check. Currently, some parameter
values in the calls may be improperly initialized which can
result in the SQLCODE -302.
(2) A superfluous DISPLAY WLM,APPLENV=* command is issued to
z/OS whenever a DB2-supplied routine has a WLM environment
setting of DSNWLM_NOT_ENABLED:
Validation of a DB2-supplied routine can be bypassed by
setting its WLM environment to DSNWLM_NOT_ENABLED. For
each such routine, DSNTRVFY will display this message:
DSNT026I DSNTRVFY VALIDATION FOR schema.routine WAS NOT
PERFORMED BECAUSE THE ROUTINE IS NOT ENABLED ON
THIS DB2 SUBSYSTEM
and indicate a status of "* BYPASSED" in the end-of-job
summary report.
1
This provision works but currently a code bug causes
DSNTRVFY to issue a superfluous DISPLAY WLM,APPLENV=*
request to z/OS whenever it encounters a routine that has a
WLM environment setting of DSNWLM_NOT_ENABLED.
To address the problem with SQLCODE -302 errors, this APAR
modifies DSNTRVFY to fully initialize storage for parameter
values passed in calls to DB2-supplied routines.
This APAR also fixes a code bug that causes a superfluous
DISPLAY WLM,APPLENV=* command to be issued to z/OS whenever
a routine has a WLM environment setting of DSNWLM_NOT_ENABLED.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27190
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@RVFY PI27190
DSNTRVFY PI27190
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27190 DSN@RVFY DSNTRVFY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTRVFY
MACROS
DSN@RVFY
LISTEND
UI24195 COVER LETTER END
UI24205 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26452 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the UNLOAD utility with SPANNED *
* YES and SYSREC on TAPE utilizing Large *
* Block Interface (LBI). *
****************************************************************
* PROBLEM DESCRIPTION: Endless loop during an UNLOAD utility *
* with SPANNED YES and the unload *
* (SYSREC) data set is on TAPE and *
* using Large Block Interface (LBI). *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An UNLOAD SPANNED YES utility of a LOB table space went into an
endless loop and had to be cancelled. The unload SYSREC data
1 set was on TAPE and TAPEBLKSZLIM=65535 was set in SYS1.PARMLIB
to utilize LBI. UNLOAD SPANNED YES does not support the Large
Block Interface and will now ignore a block size that is greater
than 32 KB.
UNLOAD SPANNED YES utility code has been modified to ignore the
Large Block Interface for the SYSREC data set on TAPE. The
data set will utilize system determined blocksize (SDB) and
the records will continue to be written in the variable blocked
spanned format.
The Utility Guide and Reference manual has been updated to
document that UNLOAD SPANNED YES ignores the Large Block
Interface. It will be added to the following sections:
Data sets that online utilities use
UNLOAD utility under the SPANNED keyword
UNLOAD utility under Unloading data in spanned record format
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26452
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
APAR PI26452 has modified the UNLOAD SPANNED YES utility to
ignore the Large Block Interface for output data sets. The
data set will use system determined block size (SDB) and the
records will continue to be written in the variable blocked
spanned format.
The Utility Guide and Reference manual has been updated to
document that UNLOAD SPANNED YES ignores the Large Block
Interface. It will be added to the following sections:
Data sets that online utilities use
UNLOAD utility under the SPANNED keyword
UNLOAD utility under Unloading data in spanned record format
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGSDA PI26452
DSNUULDB PI26452
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26452 DSNUGSDA DSNUULDB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGSDA
DSNUULDB
LISTEND
UI24205 COVER LETTER END
UI24212 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI28196 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNGDCOB ERQUAL5025 *
* during create index when running *
* concurrently with COPY SHRLEVEL CHANGE *
* of DSNDB06.SYSTSVOL. *
* *
* MSGDSNT501I RC00C90083 DSNDB06.SYSTSVOL *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During CREATE INDEX, a read claim on the SYSTSVOL may
unnecessarily receive a DBET error 00C90083 due to a concurrent
utility COPY job on SYSTSVOL. The error code is not handled
correctly and causes an abend in DSNGDCOB.
The code is changed to grant the read claim properly. The error
handling is improved when retrieving the catalog information.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28196
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNPGSGI PI28196
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28196 DSNPGSGI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNPGSGI
LISTEND
UI24212 COVER LETTER END
UI24216 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29294 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users that *
* explicitly cast decimal data to character *
* data. *
****************************************************************
* PROBLEM DESCRIPTION: A trailing decimal point is incorrectly *
* returned when casting a decimal number *
* to a character string. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following SQL can return an incorrect result due to an
uninitialized variable. The trailing decimal point should not
1 be returned if the system parameter BIF_COMPATIBILITY is
CURRENT.
SELECT CHAR(DECIMAL(11111)) FROM SYSIBM.SYSDUMMY1;
The value '11111.' may be returned incorrectly. The trailing
decimal point should not be included in this result.
The correct result is '11111'.
DB2 has been changed to not reference the uninitialized variable
so that the trailing decimal point is not returned.
Additional keywords : SQLDECIMAL SQLCHAR SQLVARCHAR SQLMIGRATION
SQLINCORR INCORROUT SQLINCORROUT DB2INCORR
SQLCAST
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29294
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDBC PI29294
DSNXRIHB PI29294
DSNXRIHD PI29294
DSNXRIHR PI29294
DSNXRIHS PI29294
DSNXROHB PI29294
DSNXROHR PI29294
DSNXROHS PI29294
DSNXROH2 PI29294
DSNXRPPL PI29294
DSNXRSBC PI29294
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29294 DSNXRDBC DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXROHB
DSNXROHR DSNXROHS DSNXROH2 DSNXRPPL DSNXRSBC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDBC
DSNXRIHB
DSNXRIHD
DSNXRIHR
DSNXRIHS
DSNXROHB
DSNXROHR
DSNXROHS
DSNXROH2
DSNXRPPL
DSNXRSBC
LISTEND
1UI24216 COVER LETTER END
UI24218 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29910 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries that use XML. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXXMRD *
* ERQUAL M130 can occur when the XML *
* sort modules can not obtain the *
* necessary storage for XML blocks. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 can occur at location DSNXXMRD ERQUAL
M130 when an XML sort module can not obtain the necessary
storage for XML blocks. The abend occurs because DB2 checks
an incorrect reason code.
The DB2 XML sort modules have been modified to check the proper
reason code when no storage is available for XML blocks. This
will prevent the reported abend.
Additional Keywords: SQLXML
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29910
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDOC PI29910
DSNXXMIN PI29910
DSNXXMRD PI29910
DSNXXMUN PI29910
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29910 DSNXRDOC DSNXXMIN DSNXXMRD DSNXXMUN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDOC
DSNXXMIN
DSNXXMRD
DSNXXMUN
LISTEND
UI24218 COVER LETTER END
UI24226 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27645 -
1 ****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* DB2 10 for z/OS or higher. *
****************************************************************
* PROBLEM DESCRIPTION: Remote VM application intermittently *
* receives SQLCODE -30020, with a *
* reason-code of X'1245' and a *
* sub-code of X'0100', when accessing a *
* DB2 10/11 for z/OS server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A DB2 for z/OS server receives a DRDA connection request from a
remote DB2 for VM requester application. Part of establishing
a DRDA connection is the exchange of a DRDA Correlation Token
(CRRTKN). The value is used to correlate work between the DRDA
requester and server.
When a requester, such as DB2 for VM, does not provide a CRRTKN
as part of its DRDA connection request, DB2 for z/OS, as the
server, must build and return a CRRTKN.
New function in DB2 10 for z/OS introduced a logic error that
may cause a DB2 for z/OS server to generate an incorrect CRRTKN
value to be returned back to a requester. The error occurs
intermittently depending on if the system time-stamp value
happens to contain a X'40', in which case the CRRTKN value is
incorrectly truncated.
A DB2 for VM requester detects the error and returns SQLCODE
-30020 to the requesting application with the reason-code token
set to X'1245', indicating a DRDA Conversation Protocol Error
(PRCCNVRM), and the sub-code token set to X'0100', indicating
that the error was detected at the requester. The connection
is also terminated.
Note: The application can retry its connection request to the
DB2 for z/OS server and it will likely succeed.
DB2 for z/OS server processing has been changed to generate and
return a valid DRDA CRRTKN value as part of the response to a
DRDA connection request that requires a CRRTKN value.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27645
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLTACC PI27645
DSNLZSRM PI27645
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27645 DSNLTACC DSNLZSRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLTACC
DSNLZSRM
1
LISTEND
UI24226 COVER LETTER END
UI24239 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29998 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER with objects involved in *
* a clone relationship. *
****************************************************************
* PROBLEM DESCRIPTION: Image copies of clone objects taken *
* before an EXCHANGE could not be used by *
* RECOVER with TOLOGPOINT if the *
* specified PIT recovery was after the *
* EXCHANGE. In these cases the RECOVER *
* jobs fail with RC=8 and message *
* MSGDSNU556I being displayed. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
In a clone table relationship, an image copy was taken of the
clone table. Later an EXCHANGE was done. A TOLOGPOINT point in
time RECOVER was attempted where the specified RBA/LRSN was
later than the EXCHANGE RBA/LRSN and the recovery failed when
it should have worked. Instead, the job failed with RC=8 and
with message DSNU556I being displayed in the job output.
RECOVER code has been changed to correct the reported problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29998
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCASA PI29998
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29998 DSNUCASA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCASA
LISTEND
UI24239 COVER LETTER END
UI24258 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29519 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
1 * RUNSTATS or inline STATISTICS utility *
* users gathering statistics on large *
* partitioned objects *
****************************************************************
* PROBLEM DESCRIPTION: REORG with inline STATISTICS resulted *
* in LOCK ESCALATIONS on the catalog *
* tables and ABEND04E RC00C90205 *
* in DSNIOST2 + x'504A' *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When REORG with inline STATISTICS was executed on large
partitioned objects with 2500 parts, it resulted in
lock escalations on the catalog tables during frequency
statistics aggregation processing. The REORG utility
abended with ABEND04E RC00C90205 in DSNIOST2 OFFSET504A.
MSGDSNI021I were issued for resource names
such as SYSIBM.SYSCOLDISTSTATS and SYSIBM.SYSINDEXSTATS
in DSNDB06.SYSSTATS.
LOCK ESCALATIONS should be avoided for catalog and directory
objects.
Code was modified to prevent lock escalations
on the catalog table during frequency statistics
aggregation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29519
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSACD PI29519
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29519 DSNUSACD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSACD
LISTEND
UI24258 COVER LETTER END
UI24275 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30350 -
****************************************************************
* USERS AFFECTED: All DB2 users of real time statistics for *
* last used information in SYSPACKAGE *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E in DSNICUMW rc=RC00c90101 *
* Erqual 5003. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 maintains a list of real time statistic (RTS)
control blocks to keep track of package execution. The RTS
service task periodically externalizes the last used
information to the SYSPACKAGE table. DB2 tried to update
the last used information after a package had been deleted
causing ABEND04E in DSNICUMW:5003 RC00C90101. This problem
can only occur if DISABLE_EDMRTS = NO.
DB2 code has been changed to not update the last used
information if a package has been deleted.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30350
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGERTS PI30350
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30350 DSNGERTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGERTS
LISTEND
UI24275 COVER LETTER END
UI24290 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28059 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a *
* trigger that has a CASE expression with an *
* EXISTS predicate in the search-condition in *
* the diagnostic-string-expression of a SIGNAL *
* statement or in the expression of a VALUES *
* statement. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at the location *
* DSNXGRDS DSNXOEXT OFFSET10BA in V10 or *
* OFFSET107C in V11 could happen when *
* creating a trigger that qualifies all *
* of the following conditions: *
* *
* 1. It contains a SIGNAL statement or a *
* VALUES statement. *
* 2. A CASE expression is in the *
* diagnostic-string-expression of the *
* SIGNAL statement or the expression *
* of the VALUES statement. *
1 * 3. The CASE expression contains an *
* EXISTS predicate in the *
* search-condition. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 INT
) #
CREATE TRIGGER TG1
NO CASCADE BEFORE INSERT ON T1
REFERENCING NEW AS NEW_ROW
FOR EACH ROW MODE DB2SQL
WHEN (NEW_ROW.C1 > 100)
BEGIN ATOMIC
SIGNAL SQLSTATE '75001'
(CASE
WHEN EXISTS (
SELECT 1
FROM SYSIBM.SYSDUMMY1)
THEN 'JUST FOR TEST'
END
);
END #
SQLCODE582 and SQLCODE20100 should be issued for the CREATE
TRIGGER statement. However, DB2 did not correctly process it. So
it caused the reported ABEND0C4.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND, and SQLCODE582 and
SQLCODE2010 will be issued.
Additional keywords: SQLTRIGGER SQLCASE SQLWHEN SQLEXISTS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28059
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCPD PI28059
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28059 DSNXOCPD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCPD
LISTEND
UI24290 COVER LETTER END
1
UI24292 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29116 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement referencing an user defined *
* inlined SQL scalar function or an user *
* defined SQL table function with a different *
* DECFLOAT rounding mode used when creating *
* the function. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE270 could be received for an SQL *
* statement referencing an user defined *
* inlined SQL scalar function or an user *
* defined SQL table function if a *
* different DECFLOAT rounding mode was *
* used when creating the function, even *
* there is no DECFLOAT referenced in the *
* function. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
SET CURRENT DECFLOAT ROUNDING MODE='ROUND_CEILING';
CREATE FUNCTION FUN1()
RETURNS INTEGER
LANGUAGE SQL
NO EXTERNAL ACTION
DETERMINISTIC
RETURN 0;
SET CURRENT DECFLOAT ROUNDING MODE='ROUND_HALF_EVEN';
SELECT FUN1()
FROM SYSIBM.SYSDUMMY1;
SQLCODE270 is received for the last SELECT statement. There are
no DECFLOAT referenced in the function, so it is not reasonable
to issue an SQLCODE because of the different DECFLOAT rounding
mode.
DB2 has been modified to do not issue the SQLCODE270 for the
aforementioned SQL statement.
Additional keywords: SQLUDF SQLTUDF SQLTABLEUDF SQLDECFLOAT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29116
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOFN3 PI29116
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29116 DSNXOFN3
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOFN3
LISTEND
UI24292 COVER LETTER END
UI24305 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25214 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS or *
* DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Serviceability.
Serviceability.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25214
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PI25214 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.
The fix for APAR PI25214 requires the fix for APAR PI26321, for
FMID JDBAA1K to be applied.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGDDF PI25214
DSNUGPPF PI25214
DSNUGPRT PI25214
DSNUGPRV PI25214
DSNUGUTC PI25214
DSNURDIS PI25214
DSNURELD PI25214
1 DSNURWBF PI25214
DSNURWI PI25214
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25214 DSNUGDDF DSNUGPPF DSNUGPRT DSNUGPRV DSNUGUTC DSNURDIS
DSNURELD DSNURWBF DSNURWI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGDDF
DSNUGPPF
DSNUGPRT
DSNUGPRV
DSNUGUTC
DSNURDIS
DSNURELD
DSNURWBF
DSNURWI
LISTEND
UI24305 COVER LETTER END
UI24307 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26321 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS or *
* DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: Serviceability *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Serviceability
Serviceability
COMPONENT: 5740-XYR00-JDBAA1K
APARS FIXED: PI26321
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 PI26321
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26321 DSNUFFMF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNUFFMF
LISTEND
UI24307 COVER LETTER END
UI24317 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27181 -
****************************************************************
* USERS AFFECTED: DB2 z/OS users of Like predicate on Unicode *
* data columns. *
****************************************************************
* PROBLEM DESCRIPTION: When using an Unicode data column on a *
* LIKE predicate, the query takes longer *
* to run. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The code that processes Unicode data columns in a LIKE predicate
is using unnecessary routines to perform some simple operations.
This results in more CPU usage.
The DB2 Unicode Like predicate code was changed to reduce
instructions by eliminating unnecessary routines and imbed
the simple code inline.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27181
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIUL16 PI27181
DSNIUL8 PI27181
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27181 DSNIUL16 DSNIUL8
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIUL16
DSNIUL8
LISTEND
UI24317 COVER LETTER END
UI24332 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27007 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of XQUERY *
* functions. *
1 ****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNXMLSM M098 may *
* occur when processing the SQL/XML *
* functions, such as: XMLQUERY, XMLTABLE *
* XMLEXISTS and XMLMODIFY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When processing the SQL/XML functions, an XML storage token
may not be cleaned up after the query finishes the processing.
When the query is called again, the referencing of the left
over token may cause the ABEND04E RC00E70005 DSNXMLSM M098
ABEND.
DB2 is modified to clean up this XML storage token after the
query finishes the processing.
Additional keywords: SQLXML XMLALL XML
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27007
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PI27007 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27007 implements the code to clean up the XML storage token
after the query finishes the processing. So the DSNXMLSM M098
ABEND will not occur when the same query is called again.
To make this fix effective for a static application, it must 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
DSNX5XGR PI27007
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27007 DSNX5XGR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNX5XGR
LISTEND
UI24332 COVER LETTER END
UI24338 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30766 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of CHECK DATA utility *
1 ****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU728I during a CHECK DATA FOR *
* EXCEPTION utility with an exception *
* table created using LIKE clause *
* on a temporal table *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
User ran a CHECK DATA FOR EXCEPTION utility against a temporal
table which has a row change timestamp column, a row-begin
column, a row-end column or a transaction-start-ID column,
and the exception table was created with LIKE clause against
the temporal table. The CHECK DATA utility failed with message
DSNU728I - INVALID EXCEPTION TABLE exception-table FOR THE
dependent-table and ended with RC8.
The problem happened because the above mentioned columns in
the exception table have different DEFAULT attributes with the
original columns and the CHECK DATA utility did not tolerate
this difference.
The CHECK DATA utility code was changed to tolerate the column
difference in DEFAULT attributes between source and exception
tables when the column is a row change timestamp column, a
transaction-start-ID column, a row-begin column, or a row-end
column.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30766
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUKINE PI30766
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30766 DSNUKINE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUKINE
LISTEND
UI24338 COVER LETTER END
UI24340 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30767 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of UNLOAD utility *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU036I and ABEND04E RC00E40070 *
* during an UNLOAD utility with PUNCHDDN *
* keyword but without corresponding DD *
1 * card or TEMPLATE *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
An UNLOAD utility with PUNCHDDN keyword failed with message
DSNU036I - UNABLE TO OPEN DCB FOR DDNAME xxxx and ABEND04E
RC00E40070 when the corresponding DD card or TEMPLATE was not
provided.
The UNLOAD utility code is modified to issue message DSNU047I -
A REQUIRED DD CARD OR TEMPLATE IS MISSING. NAME=missing-dd
and end with RC8 when PUNCHDDN is specified without
corresponding DD card or TEMPLATE data set.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30767
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUUNLD PI30767
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30767 DSNUUNLD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUUNLD
LISTEND
UI24340 COVER LETTER END
UI24359 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI22531 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of DB2 *
* acceleration for dynamic queries who *
* also what to use DB2 Dynamic Statement *
* Caching for those accelerated dynamic *
* queries. *
* *
* *
* *
****************************************************************
* PROBLEM DESCRIPTION: The use of an accelerator enables high *
* performance for executing complex *
* analytic queries. Prior to this new *
* function APAR, DB2 for z/OS did not *
* support Dynamic Statement Caching for *
* accelerated dynamic queries so a *
* PREPARE of an accelerated dynamic *
* query required the "full" non-cache
*
* prepare process without the benefit *
* of statement caching that is available *
1 * to dynamic queries that do not run *
* accelerated. *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This new function APAR now extends Dynamic Statement Cache
(DSC) support to dynamic queries that are accelerated to an
accelerator. This significantly improves performance of
PREPAREs for accelerated dynamic queries because these
PREPAREs can now benefit from the usage of the DSC as do
queries that are not accelerated.
.
No changes are needed to enable Dynamic Statement Cache support
for accelerated dynamic queries if Dynamic Statement Caching is
already enabled for the DB2 subsystem.
.
This APAR introduces the following changes to the DB2 table
DYNAMIC_STATEMENT_CACHE_TABLE:
(1) New CHAR(10) column ACCELERATED is added.
ACCELERATED identifies whether a cached dynamic query was
prepared for acceleration to an accelerator server.
.
Possible values for column ACCELERATED are:
NO
The cached statement was not prepared for acceleration.
This is the default value for a cached dynamic statement.
This is also the value for a cached query under the following
conditions:
- The QUERY ACCELERATION behavior was not specified or was
explicitly set to NONE when the dynamic query was prepared.
- A QUERY ACCELERATION behavior other than ALL was specified
when the dynamic query was prepared, but DB2 did not prepare
the query for acceleration because the query did not
qualify for acceleration according to the QUERY ACCELERATION
behavior specified.
DB2 will consider this cache entry as a possible cache match
during any of these prepare scenarios previously described,
unless a QUERY ACCELERATION behavior is specified but the query
can never be accelerated (see the description of the column
value NEVER below).
.
YES
The cached query was prepared for acceleration to an accelerator
server when a QUERY ACCELERATION behavior was specified. If a
QUERY ACCELERATION behavior is specified when a dynamic query
1 is prepared, DB2 can consider this cache entry for a possible
cache match during the prepare of the dynamic query. If the
QUERY ACCELERATION behavior is not specified or is explicitly
set to NONE when the query is prepared, DB2 will not consider
this cache entry for a cache matched during the prepare.
.
NEVER
The cached query was not prepared for acceleration when a QUERY
ACCELERATION behavior was specified for the prepare, because
the query can never be accelerated.
· If the QUERY ACCELERATION behavior is set to ENABLE, ENABLE
WITH FAILBACK, or ELIGIBLE for the prepare of the query,
DB2 will consider this cache entry first as a possible cache
match during the prepare, to verify if the query has been
previously cached as 'never can be accelerated'.
· If the QUERY ACCELERATION behavior is set to ALL for the
prepare of the query, DB2 will not consider this cache
entry as a possible cache match during the prepare.
· If the QUERY ACCELERATION behavior is not specified or
is explicitly set to NONE for the prepare of the query,
DB2 will not consider this cache entry as a possible cache
match during the prepare.
.
With this APAR/PTF applied, when QUERY ACCELERATION behavior is
used for a DB2 subsystem that has DB2 Dynamic Statement Caching
(DSC) active, it is possible for a cached query to have
multiple entries in the DSC, which is then reflected in the
table DSN_STATEMENT_CACHE_TABLE. This can occur if the same
dynamic query is run by applications that do not use QUERY
ACCELERATION, as well as, by applications that "do" use QUERY
ACCELERATION on the same DB2 subsystem.
.
Query acceleration behavior is specified by either the
DB2 subsystem parameter QUERY_ACCELERATION, the
QUERYACCELERATION bind option, or the CURRENT QUERY
ACCELERATION special register. The precedence order
(lowest to highest) is:
· The QUERY_ACCELERATION subsystem parameter
· The QUERYACCELERATION bind option, if specified
· An explicit SET CURRENT QUERY ACCELERATION statement
.
(2) This APAR also introduces these additional columns to the
table DYNAMIC_STATEMENT_CACHE_TABLE. These columns are
for future DB2 use and will be described and used
in a future DB2 APAR/PTF:
EXPANSION_REASON CHAR(2) NOT NULL WITH DEFAULT
...
STAT_ACC_ELAP BIGINT NOT NULL WITH DEFAULT
STAT_ACC_CPU BIGINT NOT NULL WITH DEFAULT
STAT_ACC_ROW BIGINT NOT NULL WITH DEFAULT
STAT_ACC_BYTE BIGINT NOT NULL WITH DEFAULT
STAT_ACC_1ROW BIGINT NOT NULL WITH DEFAULT
STAT_ACC_DB2 BIGINT NOT NULL WITH DEFAULT
STAT_ACC_EXEC BIGINT NOT NULL WITH DEFAULT
STAT_ACC_WAIT BIGINT NOT NULL WITH DEFAULT
ACCEL_OFFLOAD_ELIGIBLE CHAR(1) NOT NULL WITH DEFAULT 'N'
1 ACCELERATOR_NAME VARCHAR(128) WITH DEFAULT NULL
new function support of dsc for idaa
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI22531
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
MULTSYS:
PI22531 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
Earlier, a pre-conditioning APAR PI21188 was delivered. In a
data sharing group, this 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 following APAR enables the support for Dynamic Statement
Cache for accelerated dynamic queries.
ACTION:
This PTF adds the following columns to the DB2 10
DSN_STATEMENT_CACHE_TABLE:
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT
"ACCELERATED" CHAR(10) NOT NULL WITH DEFAULT
'NO'
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES'))
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL WITH DEFAULT
'N'
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT
NULL
No action is required after applying this PTF to a DB2 subsystem
or data sharing group that is currently in DB2 10 conversion
mode. After DB2 enters new-function mode, follow directions in
the DB2 10 Installation Guide for migrating explain tables to
DB2 10 format.
If you have installed or migrated to DB2 10 new-function mode,
you need to take the following actions after applying this PTF:
(1) Update your existing DSN_STATEMENT_CACHE_TABLE tables to the
new format
(2) Update your customized copy of sample DDL member DSNTESC
Detailed guidance follows:
----------------------------------------------------------------
(1) Update your existing DSN_STATEMENT_CACHE_TABLE tables to the
new format
----------------------------------------------------------------
=> This action is required for all customers who have created
one or more DSN_STATEMENT_CACHE_TABLE tables:
(1) Use the following query to identify creators of existing
1 DSN_STATEMENT_CACHE_TABLE tables that are in the old
DB2 10 format:
SELECT TBCREATOR
FROM SYSIBM.SYSCOLUMNS
WHERE TBNAME = 'DSN_STATEMENT_CACHE_TABLE'
GROUP BY TBCREATOR, TBNAME
HAVING( MAX(COLNO) < 68 );
(2) Use job DSNTIJXA to update the
DSN_STATEMENT_CACHE_TABLE for each creator identified
by the query. Alternatively, you can process the
following statements to add the new columns:
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCELERATED" CHAR(10) NOT NULL
WITH DEFAULT 'NO'
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES'));
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL
WITH DEFAULT 'N';
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT NULL;
Note: Altering the table will cause the containing table
space to be placed in advisory REORG pending state.
REORG the table space to clear this state.
----------------------------------------------------------------
(2) Update your customized copy of sample DDL member DSNTESC
----------------------------------------------------------------
=> This action is required for all customers who maintain
customized copies of DSNTESC
Edit DSNTESC, locate the CREATE TABLE statement for
1 DSN_STATEMENT_CACHE_TABLE, and proceed as follows:
(a) Add a comma to the end of the specification for the
STAT_SUS_LOG column
(b) Add the following column specifications after the one
for STAT_SUS_LOG:
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT,
"ACCELERATED" CHAR(10) NOT NULL WITH DEFAULT
'NO',
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES')),
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT,
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL WITH DEFAULT
'N',
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT
NULL
(c) Save your changes
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTESC PI22531
DSNTXTA PI22531
DSNTXTB PI22531
DSNXEADW PI22531
DSNXECL PI22531
DSNXECLF PI22531
DSNXECLN PI22531
DSNXECW PI22531
DSNXECWA PI22531
DSNXECWU PI22531
DSNXEDP PI22531
DSNXEDSC PI22531
DSNXEDS1 PI22531
DSNXEPM PI22531
DSNXERT PI22531
DSNXERT2 PI22531
DSNXEUFP PI22531
DSNXEUF0 PI22531
DSNXMIT2 PI22531
DSNXODML PI22531
DSNXOD12 PI22531
DSNXOIN PI22531
DSNXONZA PI22531
DSNXONZB PI22531
DSNXRFF PI22531
DSNXRFN PI22531
DSNXRIWS PI22531
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI22531 DSNTESC DSNTXTA DSNTXTB DSNXEADW DSNXECL DSNXECLF
DSNXECLN DSNXECW DSNXECWA DSNXECWU DSNXEDP DSNXEDSC
1 DSNXEDS1 DSNXEPM DSNXERT DSNXERT2 DSNXEUFP DSNXEUF0
DSNXMIT2 DSNXODML DSNXOD12 DSNXOIN DSNXONZA DSNXONZB
DSNXRFF DSNXRFN DSNXRIWS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEADW
DSNXECL
DSNXECLF
DSNXECLN
DSNXECW
DSNXECWA
DSNXECWU
DSNXEDP
DSNXEDSC
DSNXEDS1
DSNXEPM
DSNXERT
DSNXERT2
DSNXEUFP
DSNXEUF0
DSNXMIT2
DSNXODML
DSNXOD12
DSNXOIN
DSNXONZA
DSNXONZB
DSNXRFF
DSNXRFN
DSNXRIWS
MACROS
DSNTESC
DSNTXTA
DSNTXTB
LISTEND
UI24359 COVER LETTER END
UI24366 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27495 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS utility users of REORG *
* TABLESPACE *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNU304I incorrectly issued for a *
* LOAD or REORG that failed during RELOAD *
* phase initialization *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A REORG TABLESPACE or LOAD utility incorrectly issued DSNU303I
to indicate the number of records loaded, after it failed
1 during RELOAD phase initialization before attempting to load
any records. A similar problem can happen with messages
DSNU304I, DSNU1114I and DSNU1121I, all of which report number
of records loaded at the partition or table level.
Additional keywords: MSGDSNU304I, MSGDSNU1114I, MSGDSNU1121I
LOAD and REORG TABLESPACE will no longer issue the reload phase
count messages at the partition or table level when an error is
encountered before loading the first data record.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27495
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PI27495 has modified CSECTs in both the
DSNUT110 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
DSNURILD PI27495
DSNURWT PI27495
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27495 DSNURILD DSNURWT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURILD
DSNURWT
LISTEND
UI24366 COVER LETTER END
UI24369 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI21983 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of HASHED *
* table. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90105 at DSNIDM *
* DSNIDILS ERQUAL0C41 when a SQL DELETE *
* is performed against a table space *
1 * organized by Hash with LOG NO option. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While deleting from a table space that is organized by Hash and
is defined as LOG NO, DB2 does not set restore hash chain flags
properly, resulting in a DB2 abend ABEND04E RC00C90105 at
DSNIDM DSNIDILS ERQUAL0C41.
DB2 code is modified to properly restore hash chain flags for
a hash organized table space defined with LOG NO.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI21983
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 PI21983
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI21983 DSNIDILS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDILS
LISTEND
UI24369 COVER LETTER END
UI24371 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30355 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of ROWID *
* and direct row access. *
****************************************************************
* PROBLEM DESCRIPTION: Performance degradation could occur *
* when using direct row access with a *
* ROWID column in the predicate to *
* retrieve data from a partitioned table *
* space. Performance degradation will *
* be more severe if the back up access *
* path is table space scan. *
* In rare cases, it is possible to get *
* incorrect output when using direct row *
* access with a ROWID column in the *
* predicate to retrieve data from a *
* partitioned table space (Universal *
* table space and classic table space). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a ROWID column is retrieved from a partitioned table
space, it could be returned with incorrect information about
1 the location of the row in the table. When this ROWID value
is then used to retrieve data using direct row access, it will
be unable to find the row at the location provided in the
ROWID and will need to use the back up access path to find the
row. This will result in an access path that is slower than
direct row access.
It is also possible when using the ROWID value and direct row
access for DB2 to be unable to find a row in a partitioned
table space when the row has moved, for example, due to a
REORG. In this case, DB2 may not be able to detect that the row
has moved and will return 'record not found' even though the
row exists in the table.
DB2 code is changed to return the correct location information
when a ROWID column is selected from a table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30355
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
When selecting columns from a partitioned table space
(Universal table space and classic table space) using direct
row access with a ROWID column in the predicate , optimized
code to perform the select will be bypassed due to an error.
This could lead to performance degradation or incorrect
output. To rectify, rebind the plan or package.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIZMOV PI30355
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30355 DSNIZMOV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIZMOV
LISTEND
UI24371 COVER LETTER END
UI24394 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32351 -
****************************************************************
* USERS AFFECTED: All DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C200C3 DSNB1REL+0E50 *
* during GRECP recovery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During data recovery log apply, if the page read request fails
for any reason (in this case it failed with RC00C200FD - page
parity error), Data Manager (DM) log apply will terminate the
1 data recovery for that object. If the data recovery being
terminated is GRECP/LPL then DM will issue DSNI005I message.
However, before issuing DSNI005I message, it retrieves
the object's Data base/table space/index space name
using the DB2 directory tables. If the directory object
(DBD01 and/or its associated indexes) itself is in GRECP/LPL
state then it is possible that DB2 data recovery may
encountered Abend04E with the reason code of RC00C200C3.
This error condition could have been avoided, if the
log apply routine were to clear the resource name in CT
(cursor Table) before accessing directory table to retrieve
object's Data base/table space name.
DB2 data recovery logic is modified to avoid abend while
releasing the page buffer of the directory object that could be
in GRECP/LPL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32351
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 PI32351
DSNIREDO PI32351
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32351 DSNILOGA DSNIREDO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILOGA
DSNIREDO
LISTEND
UI24394 COVER LETTER END
UI24463 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29113 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* triggers with the TIMESTAMP and DECIMAL data *
* types. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result or an abend can *
* occur when a transition table (which *
* contains a TIMESTAMP or DECIMAL column) *
* of a trigger is passed as a table *
* locator argument to a stored procedure *
* (SP) or user-defined function (UDF) if *
* the precision of the TIMESTAMP column *
* or the precision/scale of the DECIMAL *
* column of the transition table differs *
* from that of the defined INPUT *
1 * parameter of the SP or UDF. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result or an abend can occur when a transition
table of a trigger is passed as a table locator argument to a
stored procedure (SP) or user-defined function (UDF). The
problem can occur if the transition table contains a TIMESTAMP
column with a different precision from that of the defined INPUT
parameter of the SP or UDF. Furthermore, an incorrect result
can also occur if the transition table contains a DECIMAL column
with a different precision/scale from that of the defined INPUT
parameter of the SP or UDF.
The following example helps to illustrate the problem when using
TIMESTAMP data type.
Step 1. Set the statement termination character.
--#SET TERMINATOR !
Step 2. Create two tables T1 and T2, each with a TIMESTAMP
column but with a different precision.
CREATE TABLE T1 (
ROW_ID ROWID NOT NULL GENERATED ALWAYS,
C1 TIMESTAMP(6) WITH TIME ZONE,
ID INTEGER NOT NULL)!
CREATE TABLE T2 (
ROW_ID ROWID NOT NULL GENERATED ALWAYS,
C1 TIMESTAMP(5) WITH TIME ZONE,
ID INTEGER NOT NULL)!
Step 3: Create stored procedure SP1.
CREATE PROCEDURE SP1
(IN TB1 TABLE LIKE T2 AS LOCATOR)
DYNAMIC RESULT SETS 2
APPLICATION ENCODING SCHEME UNICODE
BEGIN
INSERT INTO T2
(C1, ID)
SELECT C1, ID
FROM TABLE (TB1 LIKE T2);
END!
Step 3: Define an AFTER INSERT Trigger TR1 on Table T1.
CREATE TRIGGER TR1
AFTER INSERT ON T1
REFERENCING NEW TABLE AS NEW_TB
1 FOR EACH ROW
MODE DB2SQL
BEGIN ATOMIC
CALL SP1 (TABLE NEW_TB);
END!
Step 4: Insert data into Table T1 to fire the trigger.
INSERT INTO T1 VALUES
(DEFAULT,
'2010-4-1-12.34.56.123456-7:00',
100)!
Step 5: Perform the following select statement on Table T2.
SELECT TIMESTAMP_TZ(C1)
FROM T2
WHERE ID = 100!
DB2 fails to check the precision of the TIMESTAMP columns in
the above case, thus unexpected data could be inserted into
Table T2. As a result, an ABEND04E RC00E70005 can occur at
location DSNXGRDS DSNXRTIM P047.
Please note: The abend can occur at different locations
depending on how the TIMESTAMP column is used. As an example,
an ABEND04E RC00E70005 can occur at location DSNXGRDS DSNXROHB
M201 when selecting C1 instead of selecting TIMESTAMP_TZ(C1).
In general, an incorrect result or abend can occur for the
aforementioned example when using a TIMESTAMP data type because
DB2 does not check the precision or an incorrect result can be
returned when using a DECIMAL data type because DB2 does not
check the precision or scale.
The code in DB2 is modified to add TIMESTAMP precision checking
and DECIMAL precision/scale checking. This will avoid both the
incorrect result and abend, and if the precision and scale are
not the same, an SQLCODE -4735 will be issued.
Additional keywords: DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT SQLCODE4735 SQLDECIMAL
SQLTIMESTAMP SQLTIMESTAMPTZ
SQLTRIGGER SQLSP SQLSTOREDPROC SQLUDF
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29113
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRCTC PI29113
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI29113 DSNXRCTC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRCTC
LISTEND
UI24463 COVER LETTER END
UI24479 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31466 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* UNICODE inlined LOB columns with queries *
* that involve table expressions and LIKE *
* predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 could generate an incorrect result *
* set for a query that includes a UNICODE *
* inlined LOB column for a LIKE predicate *
* and table expression. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 could generate an incorrect result set for a query that
includes a UNICODE inlined LOB column for a LIKE predicate that
is contained by a table expression.
The following example helps to illustrate such a query.
Step 1. Create a table, TABLE1, with a LOB column.
CREATE TABLE TABLE1
(COLNO SMALLINT NOT NULL WITH DEFAULT ,
COLNAME CLOB(1M) NOT NULL WITH DEFAULT ,
COL_ROWID ROWID NOT NULL GENERATED ALWAYS
) CCSID UNICODE;
Step 2. Insert two rows into TABLE1.
INSERT INTO TABLE1 (COLNO, COLNAME)
VALUES (01,'SORT_UNIQ');
INSERT INTO TABLE1 (COLNO, COLNAME)
VALUES (02,'SORT_JOIN');
Step 3. Perform the following select statement that includes
a table expression that includes a LIKE predicate on the
LOB column.
SELECT FLG AS "FLG",
1 MIN(FLG) AS "MIN-F",
MAX(FLG) AS "MAX-F",
COUNT(*) AS "#ROWS"
FROM (SELECT CASE
WHEN COLNAME LIKE 'SORT_U%'
THEN 'S-U'
ELSE '?'
END AS FLG
FROM TABLE1
WHERE COLNAME LIKE 'SORT_U%'
)AS TX2
GROUP BY FLG ;
Step 4. Check the results.
The incorrect result returned is as follows.
+--------------------------------------+
| FLG | MIN-F | MAX-F | #ROWS |
+--------------------------------------+
1_| ? | S-U | S-U | 1 |
+--------------------------------------+
The expected result is as follows.
+--------------------------------------+
| FLG | MIN-F | MAX-F | #ROWS |
+--------------------------------------+
1_| S-U | S-U | S-U | 1 |
+--------------------------------------+
DB2 is modified to generate a correct result for the problem
query.
Additional Keywords: SQLLOB SQLCCSID SQLLIKE SQLINCORR
INCORROUT SQLINCORROUT DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31466
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOUL8 PI31466
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31466 DSNOUL8
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOUL8
LISTEND
1UI24479 COVER LETTER END
UI24488 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29001 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: If DB2 crashes while performing GRECP *
* recovery, objects may be incorrectly *
* marked RECP or RBDB during the next *
* restart. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
GRECP recovery opens objects as non-recoverable, and requests
that page set control log records (PSCRs) not be written. But
in some cases a checkpoint PSCR may be written, indicating that
the object is non-recoverable. If DB2 crashes before the GRECP
recovery is complete, restart will see this PSCR and mark the
object RECP (for a table space) or RBDP (for an index).
The DB2 page set checkpoint logging process has been modified
to ensure that objects opened for GRECP recovery with the
"suppress PSCR" option will not be logged.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29001
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CHK PI29001
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29001 DSNB1CHK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CHK
LISTEND
UI24488 COVER LETTER END
UI24494 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26615 -
****************************************************************
* USERS AFFECTED: All users of the following command: *
* DISPLAY DATABASE(*) SPACENAM(*) LPL ONLY *
* LIMIT(*) *
****************************************************************
* PROBLEM DESCRIPTION: DISPLAY DATABASE(*) SPACENAM(*) *
* with LPL ONLY and LIMIT(*) clauses *
1 * specified may result in unnecessary *
* output, though the output is not *
* incorrect and does not affect DB2 *
* functionality. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DISPLAY DATABASE(*) SPACENAM(*) LPL ONLY LIMIT(*) may result
in unnecessary output. The excess output is not incorrect
and does not affect DB2 functionality. However the objects
displayed do not contain objects in LPL and do not need
to be included in the output.
Example of results:
DSNT360I - ***********************************
DSNT361I - * DISPLAY DATABASE SUMMARY
* GLOBAL LPL
DSNT360I - ***********************************
DSNT362I - DATABASE = DSNDB01 STATUS = RW
DBD LENGTH = 14200
DSNT397I -
NAME TYPE PART STATUS LPL PAGES
-------- ---- ----- ----------------- ------------------DBETE
******* DISPLAY OF DATABASE DSNDB01 ENDED *************
DSNT360I - ***********************************
DSNT362I - DATABASE = xxxxxxxx STATUS = RW
DBD LENGTH = 3496898
DSNT397I -
NAME TYPE PART STATUS LPL PAGES
-------- ---- ----- ----------------- ------------------DBETE
******* DISPLAY OF DATABASE xxxxxxxx ENDED *************
DISPLAY DATABASE(*) SPACENAM(*) LPL ONLY LIMIT(*) has been
modified to remove the unecessary output.
When the said command is executed and there are no objects
returned, the output will look similar to the following
example:
DSNT367I -DB2A NO INFORMATION AVAILABLE
DSN9022I -DB2A DSNTDDIS 'DISPLAY DATABASE' NORMAL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26615
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBRP PI26615
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26615 DSNIDBRP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBRP
1 LISTEND
UI24494 COVER LETTER END
UI24530 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30791 -
****************************************************************
* USERS AFFECTED: All DB2 11 for z/OS users of SQL statement *
* containing multiple set operators. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E72018 at location *
* DSNXGRDS.DSNXSINE: 1342 may occur when *
* an SQL statement satisfies all of the *
* following conditions: *
* *
* 1. a table expression or VIEW (VW#1) *
* is defined with multiple *
* set operators. *
* 2. another table expression or VIEW *
* referenced in VW#1 is also defined *
* with multiple set operators. *
* *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem:
DDL:
CREATE TABLE T1(C1 CHAR(1), C2 VARCHAR(1), C3 INT);
CREATE TABLE T2(C1 CHAR(1), C2 VARCHAR(1), C3 INT);
INSERT INTO T1 VALUES('A', 'B', 12);
INSERT INTO T2 VALUES('A', 'B', 12);
CREATE VIEW V1(C11, C2, C3) AS
SELECT C1, C2, C3 FROM T1
UNION ALL
SELECT C1, C2, C3 FROM T2;
SQL:
SELECT DISTINCT 1
FROM (SELECT '' AS C11, C2, RAND() FROM T1
UNION
SELECT C1 AS C11, C2, RAND() FROM T2
UNION
SELECT C11, C2, C3 FROM V1
UNION ALL
SELECT C1 AS C11, C2, C3 FROM T1
UNION ALL
SELECT '' AS C11, C2, C3 FROM T2
) AS TX ;
DB2 didn't transform SQL statement by UNION distribution
correctly and caused ABEND.
1
DB2 has been modified correctly to handle the ABEND in
aformentioned SQL statement.
Keyword: SQLUNION SQLUNIONALL SQLVIEW SQLTABLEEXPR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30791
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM88698:
See PM88698 APAR/PTF text for additional information about
why a REBIND is necessary.
PM88698 corrects a problem that incorrect output could happen
for an SQL statement that contains special registers in GRPOUP
BY and a view or table expression with UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI08763:
See PI08763 APAR/PTF text for additional information about
why a REBIND is necessary.
PI08763 corrects a problem of incorrect output for an SQL
statement that contains OUTER JOIN and subquery predicate,
where the subquery predicate contains a table expression or
view with UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI08206:
See PI08206 APAR/PTF text for additional information about
why a REBIND is necessary.
PI08206 corrects the following problems:
An ABEND0C4 RC00000038 at location DSNXGRDS DSNXOCT OFFSET0540
or ABEND0C4 RC00000004 at location DSNXGRDS DSNXRBND OFFSET0814
may occur when an SQL statement satisfies following conditions:
1. a statement contains nested UNION/UNION ALL with ORDER BY
clause.
2. some sort-keys in the ORDER BY clause is not referenced
in the select list.
1
Incorrect output may occur when a SQL statement contains nested
UNION/UNION ALL with FETCH FIRST clause.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODSO PI30791
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30791 DSNXODSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODSO
LISTEND
UI24530 COVER LETTER END
UI24539 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26175 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of star join. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E2000C in DSNXOSJO *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E2000C in DSNXOSJO may occur when both of the
following conditions are met.
* Star join is enabled (STARJOIN zparm is not set to DISABLE).
* An index is defined on the fact table with a large number of
columns.
Additional Keywords:
SQLSTARJOIN SQLSTORAGE
DB2 code has been modified to require less storage when
optimizing queries referencing fact tables that have indexes
with many columns.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26175
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOSJO PI26175
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26175 DSNXOSJO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSJO
LISTEND
UI24539 COVER LETTER END
UI24541 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30113 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of XMLEXISTS predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may produce an incorrect filter *
* factor estimate for an XMLEXISTS *
* predicate with multiple range *
* conditions on the same element. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may produce an incorrect filter factor estimate for an
XMLEXISTS predicate. This problem can occur when the XMLEXISTS
predicate contains multiple range conditions on the same
element. For example,
SELECT ...
FROM T1
WHERE XMLEXISTS('/A/BÝ.>= 10 and .<= 20¨' PASSING C1)
The incorrect filter factor estimate may lead to an inefficient
access path and poor query performance.
Additional Keywords:
SQLPERFORMANCE SQLACCESSPATH SQLXML
DB2 code has been corrected to accurately estimate the
filtering for an XMLEXISTS predicate for the scenario described.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30113
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI30113:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI30113 corrects a problem of an incorrect filter factor for
an XMLEXISTS predicate with multiple range conditions on the
same element. The incorrect filter factor could lead to an
1 inefficient access path and poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODFX PI30113
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30113 DSNXODFX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODFX
LISTEND
UI24541 COVER LETTER END
UI24553 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28350 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* RUNSTATS utility users gathering *
* SPACE statistics *
****************************************************************
* PROBLEM DESCRIPTION: 1. The SPACE columns (SPACE,SPACEF) in *
* SYSTABLESPACE and SYSINDEXES not set *
* to -1 for DEFINE NO objects. The *
* aggregate catalog statistics not set *
* for DEFINE NO index objects during *
* index scan. *
* *
* 2. The SPACE integer columns were not *
* updated by RUNSTATS in SYSTABLESPACE *
* and SYSINDEXES catalog tables. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
1. When RUNSTATS utility was executed on DEFINE NO objects,
the SPACE columns (SPACE, SPACEF) in SYSIBM.SYSTABLESPACE
were not set to -1 value during the table space scan.
During the index scan, the aggregate statistics for
DEFINE NO index objects were not set. The update of the
aggregate catalog tables such as SYSIBM.SYSCOLUMNS and
SYSIBM.SYSINDEXES were skipped.
2. The SPACE integer columns in SYSTABLESPACE and SYSINDEXES
were skipped during RUNSTATS execution. This problem will also
occur during inline statistics.
Code was modified to set the SPACE and the SPACEF columns
in SYSIBM.SYSTABLESPACE to -1 for DEFINE NO
1 objects during the table space scan.
Code was modified to set the SPACE and the SPACEF columns
in SYSIBM.SYSINDEXES to -1 for DEFINE NO index objects
during the index space scan.
Code was modified to update the SPACE integer columns in
SYSTABLESPACE and SYSINDEXES catalog tables by
RUNSTATS/Inline STATISTICS utility.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28350
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSEOF PI28350
DSNUSUIX PI28350
DSNUSUTS PI28350
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28350 DSNUSEOF DSNUSUIX DSNUSUTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSEOF
DSNUSUIX
DSNUSUTS
LISTEND
UI24553 COVER LETTER END
UI24579 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29318 -
****************************************************************
* USERS AFFECTED: All DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 ABNORMAL TERMINATION *
* REASON=00F30420 running REORG utility *
* with FORCE option *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When REORG FORCE issues a cancel to terminate threads with
claims, the cancel occurs on a deferred termination service
task and causes DB2 to crash.
DB2 has been updated to not cancel system agents and terminating
agents to avoid bringing down DB2, when cancel is issued by
REORG FORCE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29318
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
DSNB1DRA PI29318
DSNB1LDA PI29318
DSNB1LDN PI29318
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29318 DSNB1DRA DSNB1LDA DSNB1LDN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DRA
DSNB1LDA
DSNB1LDN
LISTEND
UI24579 COVER LETTER END
UI24586 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25760 -
****************************************************************
* USERS AFFECTED: All DB2 users of the field QISEKLRU *
****************************************************************
* PROBLEM DESCRIPTION: The value for stealable pages QISEKLRU *
* is sometimes incorrect, for example the *
* number of STEALABLE PAGES could be *
* greater than the number of PAGES IN *
* SKELETON POOL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There is a timing window where two concurrent executions of
packages could modify the counter of STEALABLE PAGES at the same
time, which causes the incorrect values for QISEKLRU.
DB2 code has been changed to close the timing window to make
sure the correct number of pages is used to update steal-able
stats.
Additional keywords: IFCID002
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25760
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFBK PI25760
DSNGEFLC PI25760
DSNGEFSP PI25760
DSNGEPLC PI25760
DSNGERBK PI25760
1 CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25760 DSNGEFBK DSNGEFLC DSNGEFSP DSNGEPLC DSNGERBK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFBK
DSNGEFLC
DSNGEFSP
DSNGEPLC
DSNGERBK
LISTEND
UI24586 COVER LETTER END
UI24591 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31030 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of triggers *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -501 is issued on a SELECT *
* statement inside a trigger after *
* SQLCODE -438 is raised in the trigger. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a trigger raises SQLCODE -438 as a result of the
RAISE_ERROR function, a RESIGNAL statement, or a SIGNAL
SQLSTATE statement, the cursor of the SELECT statement under
the execution is implicitly closed. The cursor is driven to be
closed again afterwards resulting in SQLCODE -501.
.
It's also possible that a trigger encounters SQLCODE -501 on
a SELECT statement even with other errors besides SQLCODE -438
if the cursor of the SELECT statement is implicitly closed
after the errors.
DB2 has been changed to close the cursor only once after
an error was encountered on a SELECT statement inside a trigger.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31030
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEXAT PI31030
DSNXEXBT PI31030
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31030 DSNXEXAT DSNXEXBT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
1 DSNXEXAT
DSNXEXBT
LISTEND
UI24591 COVER LETTER END
UI24595 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28244 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC0000003B DSNNAOUT OFFSET1504 *
* occurs when a remote query returns *
* an empty XML document. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 RC0000003B DSNNAOUT OFFSET1504 occurs when a remote
query returns an empty XML document.
For example:
The following statements will connect to a remote DB2 and
issue a query which returns an empty XML document.
CONNECT TO STLEC1B;
SELECT XMLQUERY('/a/c'
PASSING
XMLPARSE('<a><b>1</b><b>2</b></a>'))
FROM SYSIBM.SYSDUMMYU;
CONNECT RESET;
When the statements are executed, the ABEND0C4 RC0000003B
DSNNAOUT OFFSET1504 will occur.
DB2 is modified, so the ABEND0C4 RC0000003B DSNNAOUT OFFSET1504
will not occur.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28244
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNNAOUT PI28244
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28244 DSNNAOUT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNAOUT
1
LISTEND
UI24595 COVER LETTER END
UI24600 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29729 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Open failure for a table space or index *
* due to the use of the wrong data set *
* name (instance node has incorrect "I"
*
* or "J" qualifier). The failure and the
*
* incorrect data set name may be shown *
* by MSGDSNB207I along with a logrec *
* entry for an ABEND04E RC00C200E2, or *
* by MSGDSNP012I. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In an unusual situation in data sharing, a job requesting a
drain (typically a command, utility or DDL statement) may drive
a "castout takeover" if it is trying to get control of a page
set from a member who is unable to perform a necessary castout.
In this case, the draining member may have to do a physical
open using information gathered from the OBD. This logic fails
to check some critical OBD fields, notably those controlling
whether the instance node of the data set name is prefixed by
"I" or "J". This can lead to an open failure and
consequential
drain failure if the wrong data set name is used.
The castout takeover logic has been modified to check some
additional critical OBD fields when performing a physical open.
These include the instance type, GBPCACHE attribute, and the
index compression and copy attributes.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29729
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 PI29729
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29729 DSNB1DRA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1DRA
LISTEND
UI24600 COVER LETTER END
1
UI24602 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27353 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of SQL statement *
* containing SET statement. *
****************************************************************
* PROBLEM DESCRIPTION: DSNH901I may be issued during *
* precompile stage when all of the *
* following conditions are satisfied: *
* 1. a special register is assigned to *
* a host variable; *
* 2. above is referenced in *
* host programming language. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Following example helps to illustrate the problem:
1. Suppose a host variable :C1 is defined as TIMESTAMP data
type in a COBOL application;
2. following assignment statement is used within this COBOL
statement program:
EXEC SQL
SET C1 = CURRENT TIMESTAMP <--- without colon(:)
END-EXEC
DB2 didn't correctly handle the host-variable in target
side of SET statement when colon is missing, which caused
DSNH901I.
DB2 has been modified to correctly process above SET statement.
Additional keywords: DSNH901I
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27353
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHANAL PI27353
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27353 DSNHANAL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHANAL
LISTEND
UI24602 COVER LETTER END
UI24603 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI29024 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of CREATE *
* INDEX statement. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE -104 is not issued as expected *
* when a column is qualified in CREATE *
* INDEX statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Following example helps to illustrate the problem.
1. CREATE TABLE TEST.TAB(C1 INT, C2, CHAR(10));
2. CREATE INDEX TEST.IDX_1 ON TEST.TAB(TAB.C1);
SQLCODE -104 should be issued against the above CREATE INDEX
statement, since a column must not be qualified. But DB2 did
not detect this qualified column TAB.C1 correctly, and resulted
in INDEX TEST.IDX_1 being created successfully.
Another example is: CREATE INDEX TEST.IDX_1 ON TEST.TAB(C1. C2);
Users expect to create an INDEX with two keys C1 and C2, but
there is only one key C2 within this INDEX, since C1 is
considered as the qualifier of C2 due to comma is missing.
DB2 has been modified correctly to issue SQLCODE -104 when a
column is qualified in CREATE INDEX statement.
Additional keywords: INDEX, DSNH104I, SQLCODE104
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29024
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI29024:
See PI29024 APAR/PTF text for additional information about
why an ACTION is necessary.
PI29024 corrects a problem which SQLCODE -104 is not issued as
that expected when a column is qualified in CREATE INDEX
statement.
To make this fix effective for an INDEX creation, the object
must be dropped and recreated after application of this PTF.
Review the letter to determine which, if any, applications
could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHSM2 PI29024
DSNHSM2V PI29024
DSNHSM5X PI29024
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29024 DSNHSM2 DSNHSM2V DSNHSM5X
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHSM2
DSNHSM2V
DSNHSM5X
LISTEND
UI24603 COVER LETTER END
UI24624 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27803 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REORG TABLESPACE SHRLEVEL NONE *
****************************************************************
* PROBLEM DESCRIPTION: REORG TABLESPACE PART SHRLEVEL NONE was *
* cancelled in SORTBLD phase and index *
* was not left in REBUILD PENDING state. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
REORG TABLESPACE SHRLEVEL NONE at PART level with DISCARD was
run on a partitioned table space with one or more
non-partitioned indexes. The job was cancelled in the SORTBLD
phase and the non-partitioned index was not left in REBUILD
PENDING upon termination of the REORG utility. This results in a
broken index and running the CHECK INDEX utility will issue:
DSNU711I - NO ROW FOR INDEX ENTRY
The problem occurred because REORG incorrectly reset the REBUILD
PENDING status on the non-partitioned index too early after
DISCARD processing left the data partition empty.
Additional keywords: MSGDSNU711I, RBDP, NPI
The code was changed so that if there are records discarded
by a part level REORG TABLESPACE SHRLEVEL NONE, the REBUILD
PENDING status on non-partitioned indexes will not be reset
until the indexes are rebuilt.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27803
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURICP PI27803
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27803 DSNURICP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1 MODULES
DSNURICP
LISTEND
UI24624 COVER LETTER END
UI24647 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26670 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS utility users of *
* REORG REBALANCE with LIMITKEY containing *
* a BIGINT *
****************************************************************
* PROBLEM DESCRIPTION: REORG REBALANCE places the hexadecimal *
* value for a BIGINT column, of the new *
* limitkey, into the LIMITKEY column of *
* SYSIBM.SYSTABLEPART *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
REORG REBALANCE was run on a table space with a BIGINT column
as (part of) the limitkey. A SELECT on SYSIBM.SYSTABLEPART shows
that the key value for the BIGINT column of the new LIMITKEYs
are in hexadecimal instead of a readable integer.
For example, for a 4 partition table space, following the
rebalance, a SELECT shows:
+----------------------
| LIMITKEY
+----------------------
1_| '800000000000EA60'X
2_| '80000000000186A0'X
3_| '8000000000030D40'X
4_| 99999999
+----------------------
instead of:
+----------------------
| LIMITKEY
+----------------------
1_| 60000
2_| 100000
3_| 200000
4_| 99999999
+----------------------
It should be noted that although this column did not show the
character value for the BIGINT column, the actual limitkey was
still correct.
REORG REBALANCE code has been changed to convert the hexadecimal
value of a BIGINT column to readable integer for the LIMITKEY
column in the SYSIBM.SYSTABLEPART catalog.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI26670
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM42922:
See PM37611 APAR/PTF text for additional information.
PM42922 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via PM37611. 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 enabling APAR, PM37611, is
applied. The new function is not enabled until PM37611 is
PM37611 removes the restriction and allows a timestamp with
time zone column in a partitioning key as long as it is the last
column in the partitioning key.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUDALT PI26670
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26670 DSNUDALT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUDALT
LISTEND
UI24647 COVER LETTER END
UI24648 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25433 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of REORG *
****************************************************************
* PROBLEM DESCRIPTION: Real-Time Statistics (RTS) and *
* SYSIBM.SYSTABLESPACESTATS row(s) are *
* invalid following a REORG TABLESPACE *
* that had abended before the SWITCH *
* phase had completed. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A REORG utility was run to materialize a pending ALTER to change
the table space from segmented to Partition By Growth (PBG). The
REORG abended while in the SWITCH phase and was terminated with
the -TERM UTILITY command. A DROP was done to drop the pending
ALTER followed by a REORG that completed with RC0.
1
A SELECT from SYSIBM.SYSTABLESPACESTATS for that table space
shows two rows instead of only one:
+-----------------------------------------------+
| DBID | PSID | PARTITION | INSTANCE |
+-----------------------------------------------+
1_| 278 | 2 | 0 | 1 |
2_| 278 | 2 | 1 | 1 | <<< wrong
+-----------------------------------------------+
The error occurred because the -TERM UTILITY command did not
coordinate with Real-Time Statistics to delete its contol
block(s) for the partition(s) shadow(s) that had been created.
-TERM UTILITY command processing and RTS code have been changed
to have RTS invalidate any of its control block(s) created for
the aforementioned scenerio.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25433
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRTSX PI25433
DSNUGTER PI25433
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25433 DSNIRTSX DSNUGTER
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRTSX
DSNUGTER
LISTEND
UI24648 COVER LETTER END
UI24653 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29855 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of statement- *
* level access path hints. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may issue SQLCODE +395 with reason *
* code '48' for a query with a statement- *
* level access path hint while a *
* PLAN_TABLE hint with the same access *
* path can be successfully applied to *
* the same query. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 DB2 may issue SQLCODE +395 with reason code '48' for a query
with a statement-level access path hint while a PLAN_TABLE
optimization hint with the same access path can be successfully
applied to the same query.
In particular, this problem likely happens when the query has
subqueries and the hint was generated on an old version of DB2,
e.g., V8 or earlier release.
Additional Keywords:
OPTHINT OPTHINTS SQLCODE395 SQLCODE394
DB2 has been modified to apply the statement-level access path
hint for cases described as above to make the statement-level
access path hint and PLAN_TABLE optimization hint consistent.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29855
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPTH PI29855
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29855 DSNXOPTH
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPTH
LISTEND
UI24653 COVER LETTER END
UI24671 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31441 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* native SQL procedures with LOBs (Large *
* Objects). *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at *
* location DSNONLLE ERQUAL5003 when *
* executing statements inside native SQL *
* procedures (SQLPL) which invoke both *
* the CONCAT and SUBSTR built-in *
* functions using LOB SQLPL variables as *
* input. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00C90101 at DSNONLLE ERQUAL5003 can occur when
executing statements inside an SQLPL procedure which exploit
both the CONCAT and SUBSTR built-in functions (BIFs) using LOB
1 SQLPL variables as input.
The reason for the intentional abend is that DB2 fails to
validate an internal pointer before mapping a structure to its
storage. As a result, subsequent operations can fail because of
invalid contents.
The following example can help illustrate a failing case.
Step 1. Create an SQLPL procedure that accepts LOB input and
generates four iterations.
CREATE PROCEDURE PI31441 (IN PARM1 CLOB(1K),
OUT PARM2 CLOB(1K),
OUT PARM3 CLOB(1K))
VERSION V1
LANGUAGE SQL
DISALLOW DEBUG MODE
MODIFIES SQL DATA
WLM ENVIRONMENT FOR DEBUG MODE DSNXWLM
SPBODY:BEGIN
DECLARE SSPOS INTEGER;
DECLARE SEPOS INTEGER;
DECLARE LEN1 INTEGER;
DECLARE INSERT_STR VARCHAR(100);
DECLARE OV CHAR(26);
DECLARE SEARCH_STR VARCHAR(50);
DECLARE LOGKEY VARCHAR(26);
DECLARE POS_LOG_KEY VARCHAR(26);
SET LEN1 = LENGTH(PARM1);
-- 1st iteration
SET SEARCH_STR = LOWER('<last_updt_time/>');
SET OV = CURRENT TIMESTAMP;
SET INSERT_STR = LOWER('<last_updt_time>' || CHAR(OV) ||
'</last_updt_time>');
SET SSPOS = POSSTR(PARM1, SEARCH_STR);
IF SSPOS > 0 THEN
SET SEPOS = SSPOS + LENGTH(SEARCH_STR);
SET PARM1 = SUBSTR(PARM1, 1, SSPOS-1) ||INSERT_STR ||
SUBSTR(PARM1, SEPOS, LEN1-SEPOS+1);
SET PARM2 = SUBSTR(PARM1,1,LENGTH(PARM1));
SET LEN1 = LENGTH(PARM1);
END IF;
-- 2nd iteration
SET SEARCH_STR = LOWER('<qt_nbr/>');
SET INSERT_STR = LOWER('<qt_nbr>' || RIGHT(DIGITS(1234567),9)
|| '</qt_nbr>');
SET SSPOS = POSSTR(PARM1, SEARCH_STR);
IF SSPOS > 0 THEN
SET SEPOS = SSPOS + LENGTH(SEARCH_STR);
1 SET PARM1 = SUBSTR(PARM1, 1, SSPOS-1) ||INSERT_STR ||
SUBSTR(PARM1, SEPOS, LEN1-SEPOS+1);
SET PARM2 = SUBSTR(PARM1,1,LENGTH(PARM1));
SET LEN1 = LENGTH(PARM1);
END IF;
-- 3rd iteration
SET SEARCH_STR = LOWER('<quote_key/>');
SET INSERT_STR = LOWER('<quote_key>' || CHAR(OV) ||
'</quote_key>');
SET SSPOS = POSSTR(PARM1, SEARCH_STR);
IF SSPOS > 0 THEN
SET SEPOS = SSPOS + LENGTH(SEARCH_STR);
SET PARM1 = SUBSTR(PARM1, 1, SSPOS-1) ||INSERT_STR ||
SUBSTR(PARM1, SEPOS, LEN1-SEPOS+1);
SET PARM2 = SUBSTR(PARM1,1,LENGTH(PARM1));
SET LEN1 = LENGTH(PARM1);
END IF;
-- 4th iteration
SET POS_LOG_KEY = CURRENT TIMESTAMP;
SET LOGKEY = REPLACE(POS_LOG_KEY,'.','');
SET LOGKEY = REPLACE(POS_LOG_KEY,'-','');
SET LOGKEY = POS_LOG_KEY ||
SUBSTR(LOGKEY, LENGTH(POS_LOG_KEY), 1) || 'SB';
SET SEARCH_STR = LOWER('<pos_logkey/>');
SET INSERT_STR = LOWER('<pos_logkey>' || LOGKEY ||
'</pos_logkey>');
SET SSPOS = POSSTR(PARM1, SEARCH_STR);
IF SSPOS > 0 THEN
SET SEPOS = SSPOS + LENGTH(SEARCH_STR);
SET PARM1 = SUBSTR(PARM1, 1, SSPOS-1) ||INSERT_STR ||
SUBSTR(PARM1, SEPOS, LEN1-SEPOS+1);
SET PARM2 = SUBSTR(PARM1,1,LENGTH(PARM1));
SET LEN1 = LENGTH(PARM1);
END IF;
END SPBODY!
Step 2. Execute this SQLPL procedure.
When executing this SQLPL procedure which consists of four
iterations, the above aforementioned abend can occur.
DB2 is modified to ensure the pointer is non-zero before mapping
structural data to it.
Additional keywords: SQLLOB SQLNATIVESQLPL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31441
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 PI31441
1 DSNOTCSO PI31441
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31441 DSNONLLE DSNOTCSO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNONLLE
DSNOTCSO
LISTEND
UI24671 COVER LETTER END
UI24683 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30641 -
****************************************************************
* USERS AFFECTED: Users of DB2 10 or DB2 11 for *
* z/OS installation job, DSNTEJ1S, which *
* invokes the schema processor. *
****************************************************************
* PROBLEM DESCRIPTION: When using DB2 supplied installation *
* sample job, DSNTEJ1S, it may abend with *
* SYSTEM COMPLETION CODE=0C4 REASON CODE *
* = 00000038 when DSNHSP is invoked. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using DB2 supplied installation sample job, DSNTEJ1S,
it may abend with SYSTEM COMPLETION CODE=0C4
REASON CODE = 00000038 when DSNHSP is invoked.
The code is changed to fix the abend.
Additional Keywords: ABEND0C4 RC38 DSNHSP
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30641
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@SPMN PI30641
DSNHSPMN PI30641
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30641 DSN@SPMN DSNHSPMN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHSPMN
MACROS
DSN@SPMN
1
LISTEND
UI24683 COVER LETTER END
UI24685 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32253 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those who are enabling, or *
* plan to enable, inbound TCP/IP location *
* aliases with a SECPORT. *
****************************************************************
* PROBLEM DESCRIPTION: Location alias secure port listening *
* is not activated after DDF start-up. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A dynamic location alias is defined via the -MODIFY DDF ALIAS
command. The alias is also defined with a secure port via an
additional -MODIFY DDF ALIAS SECPORT command. The alias is
then started via the -MODIFY DDF ALIAS START command and
inbound TCP/IP connections targeting the secure port will
succeed. DDF (or DB2) is then stopped and subsequently
started. The -DISPLAY DDF DETAIL command report indicates that
the alias is started but inbound TCP/IP connections targeting
the secure port will fail. The alias SECPORT access can be
reactivated by using the -MODIFY DDF ALIAS command to stop and
start the alias.
A similar problem occurs when a location alias with a secure
port is statically defined via the DDF ALIAS statement of the
DSNJU003 Change Log Inventory utility. However, a statically
defined location alias cannot be stopped and restarted and
therefore its secure port listening capability can never be
activated.
DDF start processing has been changed to activate the secure
port listening of all started dynamically defined location
aliases and all statically defined location aliases.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32253
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 PI32253
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32253 DSNLILNR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLILNR
1
LISTEND
UI24685 COVER LETTER END
UI24705 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29747 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: A long-running GBP link failure process *
* with correlation-ID 010.GBPLNK01 may *
* block access to a GBP, or to table *
* spaces and indexes associated with it, *
* resulting in various failures including *
* MSGDSNT501I with reason code *
* RC00C200EA. *
* *
* The link failure process may be kicked *
* off inappropriately during a duplexing *
* rebuild stop, with a message similar *
* to the following: *
* *
* DSNB313I DB2A DSNB1GBR *
* GROUP BUFFER POOL GBP0 *
* TO BE DISCONNECTED *
* REASON=LOSSCONN *
* LOSSCONN PERCENTAGE=0 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During a duplexing rebuild stop, DB2 will attempt an access to
the GBP which, if it fails, will drive link failure processing.
It should simply complete the stop of the rebuild, and let XES
drive any further failure processing as necessary.
The GBP link failure process performs a close of every page set
using the buffer pool, when it need only be concerned with the
GBP-dependent ones. The extra processing prolongs the process
and makes it more disruptive.
The handling of the duplexing rebuild stop has been modified to
no longer check the access to the GBP and potentially drive
link failure.
The GBP link failure processing has been modified to only do a
close for objects which are GBP-dependent.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29747
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1GBR PI29747
DSNB1LNK PI29747
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29747 DSNB1GBR DSNB1LNK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1GBR
DSNB1LNK
LISTEND
UI24705 COVER LETTER END
UI24711 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29986 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS user of DGTT *
* (Declared Global Temporary Table) *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIMLIK *
* ERQUAL500A during DGTT access with *
* like predicate and index access path *
* is applied *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If MIXED DECP value is set to YES, query against a DGTT table
using like predicate applied index access path, DB2 might use
0 as mixed CCSID for the encoding scheme of the DGTT.
As the consequence, the abend at DSNIMLIK occured.
DB2 code has been modified to make sure mixed CCSID for DGTT
is correctly set in above scenario.
PI34333 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of DGTT *
* (Declared Global Temporary Table) *
****************************************************************
* PROBLEM DESCRIPTION: AE PI29986 FIX COMPLETION. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI29986 FIX COMPLETION.
AE PI29986 FIX COMPLETION.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29986,PI34333
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 PI29986 PI34333
DSNIOST2 PI29986 PI34333
DSNIRIDL PI29986 PI34333
DSNISFX2 PI29986 PI34333
1 DSNIXLDI PI29986 PI34333
DSNKFLRR PI29986 PI34333
DSNKFLST PI29986 PI34333
DSNKFPRV PI34333
DSNKFTCH PI29986 PI34333
DSNKFTRR PI29986 PI34333
DSNKNXT2 PI29986 PI34333
DSNOLDEL PI29986 PI34333
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29986 DSNIONX2 DSNIOST2 DSNIRIDL DSNISFX2 DSNIXLDI DSNKFLRR
DSNKFLST DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL
PI34333 DSNIONX2 DSNIOST2 DSNIRIDL DSNISFX2 DSNIXLDI DSNKFLRR
DSNKFLST DSNKFPRV DSNKFTCH DSNKFTRR DSNKNXT2 DSNOLDEL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIONX2
DSNIOST2
DSNIRIDL
DSNISFX2
DSNIXLDI
DSNKFLRR
DSNKFLST
DSNKFPRV
DSNKFTCH
DSNKFTRR
DSNKNXT2
DSNOLDEL
LISTEND
UI24711 COVER LETTER END
UI24713 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23083 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users who use IBM DB2 *
* Analytics Accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: Currently, IBM DB2 Analytics *
* Accelerator customers can use the DB2 *
* accounting and statistics traces to *
* evaluate metrics per DB2 subsystem or *
* per thread. However, customers would *
* like the ability to track metrics at *
* the statement granularity to better *
* manage and plan their workloads. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This new function APAR now enables Accelerator Statement Level
Monitoring support in IFCID 316 and 401.
1 This APAR has functional dependency on the IBM DB2 Analytics
Accelerator V4 or higher. Without the server support, no
statement level monitoring metric will be reported.
This APAR enables DB2 to report SQL statement's eligibility to
be executed on the accelerators and to report SQL Statement
Level Monitoring statistics for queries that are accelerated.
The statement's eligibility and statistics will be reported in
the IFCID 316, 401 trace records and the
DSN_STATEMENT_CACHE_TABLE.
The DSN_STATEMENT_CACHE_TABLE changes:
1. The ACCEL_OFFLOAD_ELIGIBLE column will be set to 'Y' when
DB2 determines a dynamic cached query is eligible to be
executed on the IBM DB2 Analytics Accelerator, when zparm
or special register for accelerator modeling is enabled.
'N' is the default value. The statement is not eligible
for acceleration.
2. The following columns in DSN_STATEMENT_CACHE_TABLE are
filled with execution statistics as the dynamic cached
statement is actually accelerated (column ACCELERATED is
'YES'). These columns' description is listed below:
Column Data Type Description
-----------------------------------------------------------
STAT_ACC_ELAP BIGINT Accumulated accelerator Elapsed
time
-----------------------------------------------------------
STAT_ACC_CPU BIGINT Accumulated accelerator CPU time
-----------------------------------------------------------
STAT_ACC_ROW BIGINT Accumulated # of rows returned
from accelerator
-----------------------------------------------------------
STAT_ACC_BYTE BIGINT Accumulated # of bytes returned
from accelerator
-----------------------------------------------------------
STAT_ACC_1ROW BIGINT Time waited for 1st row of query
result to be available from
accelerator
-----------------------------------------------------------
STAT_ACC_DB2 BIGINT Total time accelerator waited
for DB2 to request query results
-----------------------------------------------------------
STAT_ACC_EXEC BIGINT Accumulated accelerator
Execution time
-----------------------------------------------------------
STAT_ACC_WAIT BIGINT Accumulated accelerator queue
Wait time
-----------------------------------------------------------
3. The ACCELERATOR_NAME column contains the concatenated
name(s) of accelerator(s) where the query is accelerated.
Instrumentation changes:
1 1. IFCID 316 is changed to report when a cached statement is
eligible for execution on an accelerator. When a cached
statement is accelerated, this trace record also contains
statistics of the dynamic statement's acceleration in
QW0316's R20 section per accelerator. The 316 changes are
reflected in the DSNDQW04 copy file and related DB2
documentation on IFCID 316.
2. IFCID 401 is changed to report when a static statement is
eligible for execution on an accelerator. When a statement
is accelerated, this trace record also contains statistics
of the static statement's acceleration in QW0401's R20
section per accelerator. The 401 changes are reflected in
the DSNDQW05 copy file and related DB2 documentation on
IFCID 401.
Reference:
IDAAV4R1/K
DB2 will now support Accelerator Statement Level Monitoring.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23083
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
This new function APAR now enables Accelerator Statement Level
Monitoring support in IFCID 316 and 401.
This APAR has functional dependency on the IBM DB2 Analytics
Accelerator V4 or higher. Without the server support, no
statement level monitoring metric will be reported.
This APAR enables DB2 to report SQL statement's eligibility to
be executed on the accelerators and to report SQL Statement
Level Monitoring statistics for queries that are accelerated.
The statement's eligibility and statistics will be reported in
the IFCID 316, 401 trace records and the
DSN_STATEMENT_CACHE_TABLE.
The DSN_STATEMENT_CACHE_TABLE changes:
1. The ACCEL_OFFLOAD_ELIGIBLE column will be set to 'Y' when
DB2 determines a dynamic cached query is eligible to be
executed on the IBM DB2 Analytics Accelerator, when zparm
or special register for accelerator modeling is enabled.
'N' is the default value. The statement is not eligible
for acceleration.
2. The following columns in DSN_STATEMENT_CACHE_TABLE are
filled with execution statistics as the dynamic cached
statement is actually accelerated (column ACCELERATED is
'YES'). These columns' description is listed below:
Column Data Type Description
-----------------------------------------------------------
STAT_ACC_ELAP BIGINT Accumulated accelerator Elapsed
1 time
-----------------------------------------------------------
STAT_ACC_CPU BIGINT Accumulated accelerator CPU time
-----------------------------------------------------------
STAT_ACC_ROW BIGINT Accumulated # of rows returned
from accelerator
-----------------------------------------------------------
STAT_ACC_BYTE BIGINT Accumulated # of bytes returned
from accelerator
-----------------------------------------------------------
STAT_ACC_1ROW BIGINT Time waited for 1st row of query
result to be available from
accelerator
-----------------------------------------------------------
STAT_ACC_DB2 BIGINT Total time accelerator waited
for DB2 to request query results
-----------------------------------------------------------
STAT_ACC_EXEC BIGINT Accumulated accelerator
Execution time
-----------------------------------------------------------
STAT_ACC_WAIT BIGINT Accumulated accelerator queue
Wait time
-----------------------------------------------------------
3. The ACCELERATOR_NAME column contains the concatenated
name(s) of accelerator(s) where the query is accelerated.
Instrumentation changes:
1. IFCID 316 is changed to report when a cached statement is
eligible for execution on an accelerator. When a cached
statement is accelerated, this trace record also contains
statistics of the dynamic statement's acceleration in
QW0316's R20 section per accelerator. The 316 changes are
reflected in the DSNDQW04 copy file and related DB2
documentation on IFCID 316.
2. IFCID 401 is changed to report when a static statement is
eligible for execution on an accelerator. When a statement
is accelerated, this trace record also contains statistics
of the static statement's acceleration in QW0401's R20
section per accelerator. The 401 changes are reflected in
the DSNDQW05 copy file and related DB2 documentation on
IFCID 401.
ACTION:
The package name and collection ID fields of IFCID 360
will now be written out as EBCDIC if the zparm UIFCIDS
is set to NO, and UNICODE if the zparm is YES.
Please note that existing applications that read these
fields may need to be changed appropriately.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQW04 PI23083
DSNDQW05 PI23083
DSNGEPLC PI23083
1 DSNGEPSH PI23083
DSNLXCQH PI23083
DSNLXHIM PI23083
DSNLXHNO PI23083
DSNLXHOC PI23083
DSNLXHPR PI23083
DSNLXHSE PI23083
DSNLXHSP PI23083
DSNLXMRF PI23083
DSNLXRAX PI23083
DSNLXRBF PI23083
DSNLXRCL PI23083
DSNLXRCM PI23083
DSNLXRCN PI23083
DSNLXRDT PI23083
DSNLXRFT PI23083
DSNLXRLS PI23083
DSNLXROP PI23083
DSNLXRSL PI23083
DSNLXRSQ PI23083
DSNLXRUW PI23083
DSNLXSET PI23083
DSNLZHC0 PI23083
DSNLZHC1 PI23083
DSNLZHC2 PI23083
DSNLZHP0 PI23083
DSNLZHP1 PI23083
DSNLZHP2 PI23083
DSNLZHP3 PI23083
DSNLZHR0 PI23083
DSNLZHR1 PI23083
DSNLZMON PI23083
DSNLZRPA PI23083
DSNLZR00 PI23083
DSNTBAR PI23083
DSNTBCM PI23083
DSNWARDS PI23083
DSNXECL PI23083
DSNXECLF PI23083
DSNXECLN PI23083
DSNXECNT PI23083
DSNXECSS PI23083
DSNXECST PI23083
DSNXECW PI23083
DSNXECWA PI23083
DSNXECWU PI23083
DSNXEDS1 PI23083
DSNXEIST PI23083
DSNXELX PI23083
DSNXEPM PI23083
DSNXERDS PI23083
DSNXERT PI23083
DSNXERT2 PI23083
DSNXESET PI23083
DSNXEUCS PI23083
DSNXEUFP PI23083
1 DSNXEUF0 PI23083
DSNXMIT2 PI23083
DSNXOD12 PI23083
DSNXRCUF PI23083
DSNXRRTN PI23083
DSNX8EKG PI23083
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23083 DSNDQW04 DSNDQW05 DSNGEPLC DSNGEPSH DSNLXCQH DSNLXHIM
DSNLXHNO DSNLXHOC DSNLXHPR DSNLXHSE DSNLXHSP DSNLXMRF
DSNLXRAX DSNLXRBF DSNLXRCL DSNLXRCM DSNLXRCN DSNLXRDT
DSNLXRFT DSNLXRLS DSNLXROP DSNLXRSL DSNLXRSQ DSNLXRUW
DSNLXSET DSNLZHC0 DSNLZHC1 DSNLZHC2 DSNLZHP0 DSNLZHP1
DSNLZHP2 DSNLZHP3 DSNLZHR0 DSNLZHR1 DSNLZMON DSNLZRPA
DSNLZR00 DSNTBAR DSNTBCM DSNWARDS DSNXECL DSNXECLF
DSNXECLN DSNXECNT DSNXECSS DSNXECST DSNXECW DSNXECWA
DSNXECWU DSNXEDS1 DSNXEIST DSNXELX DSNXEPM DSNXERDS
DSNXERT DSNXERT2 DSNXESET DSNXEUCS DSNXEUFP DSNXEUF0
DSNXMIT2 DSNXOD12 DSNXRCUF DSNXRRTN DSNX8EKG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEPLC
DSNGEPSH
DSNLXCQH
DSNLXHIM
DSNLXHNO
DSNLXHOC
DSNLXHPR
DSNLXHSE
DSNLXHSP
DSNLXMRF
DSNLXRAX
DSNLXRBF
DSNLXRCL
DSNLXRCM
DSNLXRCN
DSNLXRDT
DSNLXRFT
DSNLXRLS
DSNLXROP
DSNLXRSL
DSNLXRSQ
DSNLXRUW
DSNLXSET
DSNLZHC0
DSNLZHC1
DSNLZHC2
DSNLZHP0
DSNLZHP1
DSNLZHP2
DSNLZHP3
DSNLZHR0
DSNLZHR1
DSNLZMON
1 DSNLZRPA
DSNLZR00
DSNTBAR
DSNTBCM
DSNWARDS
DSNXECL
DSNXECLF
DSNXECLN
DSNXECNT
DSNXECSS
DSNXECST
DSNXECW
DSNXECWA
DSNXECWU
DSNXEDS1
DSNXEIST
DSNXELX
DSNXEPM
DSNXERDS
DSNXERT
DSNXERT2
DSNXESET
DSNXEUCS
DSNXEUFP
DSNXEUF0
DSNXMIT2
DSNXOD12
DSNXRCUF
DSNXRRTN
DSNX8EKG
MACROS
DSNDQW04
DSNDQW05
LISTEND
UI24713 COVER LETTER END
UI24719 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31169 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users who run *
* REBIND PACKAGE command. *
****************************************************************
* PROBLEM DESCRIPTION: REBIND PACKAGE command fails when the *
* collection name or package name is *
* delimited and the collection or package *
* name contains special characters. An *
* example is as follows. *
* *
* CREATE PROCEDURE
"MySchema"."My/Proc1" *
* *
* REBIND
PACKAGE("MySchema"."My/Proc1") *
* *
1 * After the CREATE statement successfully *
* creates the procedure, REBIND PACKAGE *
* for the procedure fails because of the *
* special character '/'. Note that other *
* special characters used in a delimited *
* name have the same symptom. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
REBIND PACKAGE command fails when the collection name or package
name is delimited and the collection or package name contains
special characters. An example is as follows.
CREATE PROCEDURE "MySchema"."My/Proc1"
REBIND PACKAGE("MySchema"."My/Proc1")
After the CREATE statement successfully creates the procedure,
REBIND PACKAGE for the procedure fails because of the special
character '/'. Note that other special characters used in a
delimited name have the same symptom.
The root cause is DB2 incorrectly blocked the special characters
in delimited collection names and package names.
Code has been modified to allow the special characters in the
delimited collection names and package names. The problem
reported in this APAR is fixed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31169
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNECP46 PI31169
DSNECP55 PI31169
DSNECP71 PI31169
DSNECP72 PI31169
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31169 DSNECP46 DSNECP55 DSNECP71 DSNECP72
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNECP46
DSNECP55
DSNECP71
DSNECP72
LISTEND
UI24719 COVER LETTER END
UI24723 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI30645 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of native SQL *
* procedures. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result set can be returned *
* from a query that resides in a native *
* SQL procedure if it references the same *
* input VARGRAPHIC SQL variable more than *
* once. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result set can be returned from a query that
references the same input VARGRAPHIC SQL variable more than once
if it resides in a native SQL procedure.
The following example helps to illustrate the problem.
1. Create a Table TESTY and insert a row.
CREATE TABLE TESTY (ID1 VARGRAPHIC(10), ID2 VARGRAPHIC(10));
INSERT INTO TESTY values ( '02','02');
2. Create a native SQL procedure SP1 that references the table.
CREATE PROCEDURE SP1
( IN V_ID VARGRAPHIC(10) CCSID UNICODE )
LANGUAGE SQL
RESULT SETS 1
BEGIN
DECLARE SQLERRM VARCHAR(255);
DECLARE SQLCODE INTEGER DEFAULT 0;
DECLARE CUR_PROD CURSOR WITH RETURN FOR
SELECT ID1, ID2
FROM TESTY
WHERE ID1 = V_ID
AND ID2 = V_ID ;
OPEN CUR_PROD;
END?
Please note: The input VARGRAPHIC SQL variable V_ID
is referenced twice in the SELECT statement above.
3. An application calls the SQL procedure SP1 and fetches using
the cursor CUR_PROD.
DCL HV1 GRAPHIC(10) VARYING;
DCL HV2 GRAPHIC(10) VARYING;
DCL HIND1 BIN FIXED(15);
DCL HIND2 BIN FIXED(15);
1 DECLARE LOC1 SQL TYPE IS RESULT_SET_LOCATOR VARYING;
EXEC SQL CALL SP1('02');
EXEC SQL
ASSOCIATE RESULT SET LOCATORS (:LOC1) WITH PROCEDURE SP1;
EXEC SQL
ALLOCATE Cur_Prod CURSOR FOR RESULT SET :LOC1;
EXEC SQL
FETCH Cur_Prod INTO :HV1:HIND1, :HV2:HIND2;
4. Check the results.
The FETCH statement returns an incorrect result for column ID1
and ID2 because DB2 does not handle the VARGRAPHIC length
properly inside a native SQL procedure when it is referenced
more than once. This problem was corrected in DB2 9 for z/OS by
apar PM20787.
The code in DB2 has been modified to correct the problem which
results from referencing a vargraphic SQLPL variable in a query
within a procedure more than once.
Additional Keywords : SQLINCORR SQLINCORROUT INCORROUT DB2INCORR
SQLPROCEDURE VARGRAPHIC SQLNATIVESQLPL
SQLGRAPHIC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30645
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
See PI30645 APAR/PTF text for additional information about
why an ACTION is necessary.
PI30645 corrects a problem of incorrect output when running
a native SQL procedure which contains an SQL statement that
references a VARGRAPHIC type SQL variable multiple times.
After the application of this PTF, ALTER PROCEDURE REGENERATE is
required for each native SQL procedure that is affected.
Review the PTF cover letter to determine which, if any, native
SQL procedures could be affected by this change.
ACTION:
PI11454 corrects a problem that incorrect statement number and
section number could be generated when a native SQL procedure
or non-inline SQL scalar function satisfies following
conditions:
1. CREATE PROCEDURE/FUNCTION statement contains at least 2
assignment-statements that references user-defined function
(UDF) or built-in function(BIF).
2. One of the assignment-statement references a UDF which does
not exist during bind time.
1 3. One of the assignment-statement references a BIF.
After the application of this PTF, ALTER PROCEDURE/FUNCTION
REGENERATE is required for each native SQL procedure/SQL scalar
function that is affected.
Review the PTF cover letter to determine which, if any, native
SQL procedure and SQL scalar function could be affected by
this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOYPL PI30645
DSNXRPL9 PI30645
DSNXRSPL PI30645
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30645 DSNXOYPL DSNXRPL9 DSNXRSPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOYPL
DSNXRPL9
DSNXRSPL
LISTEND
UI24723 COVER LETTER END
UI24725 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31554 -
****************************************************************
* USERS AFFECTED: All users of the DB2-supplied stored *
* procedure SYSPROC.ADMIN_INFO_SYSPARM, *
* DB2 10 for z/OS and DB2 11 for z/OS, *
* are affected by this change. *
****************************************************************
* PROBLEM DESCRIPTION: The ADDITIONAL_INFO column of the *
* last result set row returned by *
* ADMIN_INFO_SYSPARM is blank. The *
* keyword ONLINE= is missing from *
* this column. *
****************************************************************
* RECOMMENDATION: APPLY PTF *
****************************************************************
The ADDITIONAL_INFO column of the last result set row is
blank due to storage overlay. Currently, the procedure result
set columns are not properly initialized which can result in
storage overlay.
To address this problem, this APAR modifies ADMIN_INFO_SYSPARM
to properly initialize storage for the procedure result set
columns.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31554
SPECIAL CONDITIONS:
1 COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI31554 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SYSPARM to properly initialize storage
for the procedure result set columns.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the ADMIN_INFO_SYSPARM DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMIZ PI31554
DSNADMIZ PI31554
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31554 DSN@DMIZ DSNADMIZ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMIZ
MACROS
DSN@DMIZ
LISTEND
UI24725 COVER LETTER END
UI24742 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29985 -
****************************************************************
* USERS AFFECTED: Users of clone tables, pending definition *
* changes, and REORG are affected. *
****************************************************************
* PROBLEM DESCRIPTION: *
* REORG tablespace may hit the following *
1 * error, *
* *
* DSNU387I DSNURSWT SWITCH PHASE COMPLETE *
* DSNU428I DSNURSWT DB2 IMAGE COPY *
* SUCCESSFUL FOR TABLESPACE TESTDB.TESTTS *
* DSNT500I DSNUGBAC RESOURCE UNAVAILABLE *
* REASON 00C20112 *
* TYPE 00000220 *
* NAME DSNC000.DSNDBC.TESTDB.TESTTS. *
* J0002.A001 *
* DSNU017I DSNUGBAC UTILITY DATA BASE *
* SERVICES MEMORY EXECUTION ABENDED, *
* REASON=X'00E40009' CAUSE=X'00C20112' *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The above error and other unexpected results may occur
when REORG materializes pending definition changes and the
field SYSTABLESPACE.INSTANCE value is 2.
The following scenario can result in REORG failure
1. Create table TAB1
2. Alter table TAB1 to add a clone TAB1CLONE
3. Exchange data between base and clone table
4. Alter table TAB1 Drop clone
5. Do a pending alter to the containing table space of TAB1
6. Run REORG on the table space to materialize pending alter
REORG has been modified to handle materializing pending
definition changes when SYSTABLESPACE.INSTANCE field has a
value of 2.
ADDITIONAL KEYWORDS: SQLCLONE SQLALTER RC00C20112
MSGDSNU387I MSGDSNU428I MSGDSNT500I MSGDSNU017I
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29985
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDPND PI29985
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29985 DSNGDPND
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDPND
LISTEND
UI24742 COVER LETTER END
1
UI24783 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27375 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of UNLOAD and using File *
* Reference Variables (FRV) *
****************************************************************
* PROBLEM DESCRIPTION: UNLOAD of a table with an XML column *
* using an FRV issues message *
* MSGDSNU283I - XML ERROR *
* SQLCODE = -452 *
* SQLERRM = data_set_name(member) 13 *
* SQLSTATE = 428A1 *
* and ends with RC8 *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
RUNSTATS was run on a newly created, empty table containing an
XML column, followed by a LOAD without the STATISTICS keyword.
An UNLOAD of the table, using an FRV for the XML column, issued:
DSNU283I - XML ERROR
SQLCODE = -452
SQLERRM = data_set_name(member) 13
SQLSTATE = 428A1
and ended with RC8.
An examination of the JES dataset for the DBM1 address space
shows:
MSGIEC217I - B14-10 specifying the partition data set (PDS) for
the XML member(s).
The TEMPLATE statement for the XML data specified DSNTYPE(PDS)
and did not specify DIR for the number of directory blocks
desired so UNLOAD attempted to calculate it. Because RUNSTATS
had been run on the empty table, the number of directory blocks
needed was calculated to be 0.
When the attempt was made to write the first XML member to the
PDS, the above error occurred because of there being no
directory blocks. This in turn caused message DSNU283I - XML
ERROR SQLCODE=-452 SQLSTATE=428A1 to be issued and the utility
ended with RC8.
This error can also occur with the table containing a LOB
column.
ADDITIONAL KEYWORDS: SQLCODE452 ICE217I ABENDB14 RC10
UNLOAD FRV code has been changed to use a default value of 50
directory blocks when a value of 0 has been calculated.
It should be noted that this change is being made to help in the
unloading of a table with LOB and/or XML columns and a minimal
1 number of rows. Valid statistics still need to be present so
that an accurate number of directory blocks can be calculated.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27375
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULDB PI27375
DSNUULPB PI27375
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27375 DSNUULDB DSNUULPB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULDB
DSNUULPB
LISTEND
UI24783 COVER LETTER END
UI24844 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30180 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for Z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 at DSNICMT2+8E0C during Commit *
* process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During commit process, DB2 mistakenly accessed an already
freed internal control block for some internal information
regarding its proior Row Set process. This caused
ABND=0C4-00000038 at DSNICMT2+8E0C.
Fix made in DB2 to properly check the validity of the
internal control block before accessing it.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30180
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICMT2 PI30180
DSNITCUS PI30180
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30180 DSNICMT2 DSNITCUS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNICMT2
DSNITCUS
LISTEND
UI24844 COVER LETTER END
UI24889 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30243 -
****************************************************************
* USERS AFFECTED: All users of DSNTXAZP, the DSNTIDxx refresh *
* tool, in DB2 10 for z/OS and DB2 11 for z/OS *
* who apply a fixing PTF for APAR PI07515: *
* - UI20718: DB2 10 for z/OS *
* - UI20719: DB2 11 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: One of the ++HOLD actions in the fixing *
* PTFs for PI07515 instructs users of *
* program DSNTXAZP to bind a package for *
* DSNTXAZP with ACTION(ADD). That bind *
* request fails with return code 8 and *
* these messages: *
* DSNT237I -DSN DSNTBCM2 BIND ADD *
* ERROR USING auth AUTHORITY *
* PACKAGE = location.DSNTXAZP.- *
* DSNTXAZP.(version) *
* ALREADY EXISTS *
* DSNT233I -DSN UNSUCCESSFUL BIND FOR *
* PACKAGE = location.DSNTXAZP.- *
* DSNTXAZP.(version) *
* where 'location' is DB2's location name *
* and 'version' is a DSNTXAZP DBRM *
* version ID. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF. *
****************************************************************
APAR PI07515 provides new options for DB2 subsystem parameter
DSN6FAC.DDF_COMPATIBILITY to help users compensate for
unexpected behavior of remote client application environments.
In order to provide additional space to store the new options,
PI07515 changed the format of the DB2 installation CLIST input
(DSNTIDxx) member entries for DDF_COMPATIBILITY from this:
DDF_COMPATIBILITY LSTR M <a>
DDF_COMPATIBILITY1 LSTR M <b>
to this:
DDF_COMPATIBILITY LLST M <a>
DDF_COMPATIBILITY1 LLST M <b>
DDF_COMPATIBILITY2 LLST M <c>
DDF_COMPATIBILITY3 LLST M <d>
DDF_COMPATIBILITY4 LLST M <e>
However, PI07515 failed to include a change to DSNTXAZP, the
1 refresh tool for DSNTIDxx members, to make it use the new
format.
Both fixing PTFs for PI07515 contain a ++HOLD action that
instructs users of DSNTXAZP to bind a package for it using
ACTION(ADD). Because the intended update of DSNTXAZP was not
included in the PTFs for PI07515, its DBRM and module are
unchanged when you apply the PTF. If a package is already bound
from the existing DSNTXAZP DBRM in prefix.SDSNDBRM, the bind
with ACTION(ADD) request fails with the symptoms noted in the
problem description section of this APAR.
This APAR provides the missing DSNTXAZP changes that were not
included in PI07515.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30243
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI30243
This PTF modifies DSNTXAZP, a program that can be used to
refresh a DB2 installation CLIST input (DSNTIDxx) member with
DB2's current subsystem parameter, DSNHDECP parameter, and
buffer pool settings. If you have already installed or migrated
to this version of DB2 and you use DSNTXAZP then you need to
update the package: Submit a job that contains the following
BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
ACTION:
***Action for PI29286 (DB2 10)
This PTF modifies DSNTXAZP, the DSNTIDxx refresh tool to fix
an error that causes the wrong MAX VALUE setting to be assigned
to the DSNTIDxx entries for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED.
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 private copies of the DSNTIDxx CLIST input member
(2) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
You need to verify that your DSNTIDxx members have the
1 appropriate MAX VALUE settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. For each private DSNTIDxx member, proceed
as follows:
(a) Edit the member
(b) Locate the entry for SIMULATED_CPU_COUNT. If the fifth
field (MAX VALUE) specifies 255, change it to NONE. In
other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <x>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <x>
where <x> is the current setting of SIMULATED_CPU_COUNT.
(c) Locate the entry for SIMULATED_CPU_SPEED. If the fifth
field (MAX VALUE) specifies 2147483647, change it to NONE.
In other words, change this format:
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <y>
to this:
SIMULATED_CPU_SPEED CHARR G OFF NONE <y>
where <y> is the current setting of SIMULATED_CPU_SPEED.
(d) Save any changes you made and proceed to your next DSNTIDxx
member
Repeat steps (a) - (d) for each DSNTIDxx member.
---------------------------------------------------------------
(2) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI30243
DSNTIDXA PI30243
DSNTXAZP PI30243
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30243 DSN@XAZP DSNTIDXA DSNTXAZP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
MACROS
DSN@XAZP
1 DSNTIDXA
LISTEND
UI24889 COVER LETTER END
UI24910 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27892 -
****************************************************************
* USERS AFFECTED: All users of JSON support for DB2 10 for *
* z/OS *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXGRDS *
* DSNXRFN ERQUALM102 may occur when using *
* JSON functionality *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may abend with ABEND04E RC00E70005 at DSNXGRDS DSNXRFN
ERQUALM102 when processing an SQL query for JSON functionality.
The problem occurs because a return code is not set correctly.
DB2 has been changed to set an internal return code correctly
when processing an SQL query involving JSON functionality.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27892
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQW05 PI27892
DSNXRUFM PI27892
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27892 DSNDQW05 DSNXRUFM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRUFM
MACROS
DSNDQW05
LISTEND
UI24910 COVER LETTER END
UI24919 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29723 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* UPDATE that initially violates the unique *
1 * index constraint and needs deferred key *
* processing. *
****************************************************************
* PROBLEM DESCRIPTION: After the application of APAR PI13190 *
* (PTF UI19571/UI19572) an ABEND04E can *
* occur in DSNXGRDS DSNXRUP2 +4650 or in *
* DSNXGRDS DSNXRUP2 +299A during the *
* UPDATE statement that updates a column *
* that is part of a unique index key. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The ABEND may occur during the UPDATE statement processing when
the UPDATE initially violates the unique index constraint and
needs deferred key processing.
Additional conditions necessary for the ABEND to occur are:
1. UPDATE is using one of the following RID accesses for
qualifying and positioning of the rows to be updated:
List prefetch (PLAN_TABLE PREFETCH column has value 'L')
Multiple index access (PLAN_TABLE ACCESSTYPE column has
value 'M','MI', or 'MU').
2. RID list overflow to a work file must occur.
An example scenario is as follows:
1. There exists a unique index on one of the columns.
e.g.: CREATE TABLE T1 (C1 INT, C2 INT);
CREATE UNIQUE INDEX IX1 ON T1(C1);
2. A searched UPDATE is issued which:
a. Updates the unique index column so that it initially
violates the uniqueness constraint.
b. Uses List Prefetch as part of an access path.
c. Qualifies large number of rows to cause RID overflow.
d. RIDs are overflown to a work file.
e.g.: UPDATE T1
SET C1 = C1+1
WHERE C1 > 0;
3. At the end of UPDATE processing, an ABEND may occur.
DB2 code was modified to prevent the ABEND during the clean
up of the deferred key UPDATE.
Additional Keywords: SQLUPDATE DSNXRUP2 OFFSET299A
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29723
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXREOJ PI29723
DSNXRFF PI29723
DSNXRFN PI29723
DSNXROJ1 PI29723
1 DSNXRSFN PI29723
DSNXRSGB PI29723
DSNXRT1J PI29723
DSNXSBUC PI29723
DSNXSIND PI29723
DSNXSING PI29723
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29723 DSNXREOJ DSNXRFF DSNXRFN DSNXROJ1 DSNXRSFN DSNXRSGB
DSNXRT1J DSNXSBUC DSNXSIND DSNXSING
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXREOJ
DSNXRFF
DSNXRFN
DSNXROJ1
DSNXRSFN
DSNXRSGB
DSNXRT1J
DSNXSBUC
DSNXSIND
DSNXSING
LISTEND
UI24919 COVER LETTER END
UI24926 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31951 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of LISTDEF utility. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E4001C occurred when a *
* LISTDEF with TABLESPACES keyword *
* referenced a list which contained a *
* directory index space. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A LISTDEF was defined as LISTDEF LIST2 INCLUDE TABLESPACES LIST
LIST1. LIST1 contained a directory index space. The utility
job received ABEND04E RC00E4001C while expanding LIST2, because
the table space information LISTDEF needed from the DB2 catalog
is not available for catalog or directory objects.
The message DSNU1002 with return code 8 should have been issued
for this case.
Note that the same problem exists for lists containing catalog
index spaces.
LISTDEF code has been modified to enforce the existing
restriction on the use of LISTDEF clauses with the TABLESPACES
keyword on other lists containing catalog or directory index
spaces, or with the INDEXSPACES keyword on lists containing
1 catalog or directory table spaces.
MSGDSNU1002 (INVALID KEYWORD SPECIFIED ON CLAUSE) with RC8 will
now be issued in these cases.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31951
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 PI31951
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31951 DSNUILSA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUILSA
LISTEND
UI24926 COVER LETTER END
UI24950 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31824 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: The page set is put in WEPR state with *
* MSGDSNB224I MSGDSNU086I after LPL *
* recovery encountering a drain write *
* failure RC00C200EA. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
LPL page recovery processing issues drain write, which may fail
due to other concurrent writers. Instead of skipping this
object for further processing, it may continue and incorrectly
set the page set in WEPR state.
The code is changed to skip the object for further LPL recovery
when requested drain write fails. The pages will remain in LPL
state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31824
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISREC PI31824
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31824 DSNISREC
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISREC
LISTEND
UI24950 COVER LETTER END
UI24953 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31855 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users *
* of Profile Manager *
****************************************************************
* PROBLEM DESCRIPTION: The truncated value of PRDID column in *
* SYSIBM.DSN_PROFILE_HISTORY table *
* when the equivalent column in *
* SYSIBM.DSN_PROFILE_TABLE has the *
* maximum(8-character-length) value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When inserting the result of START PROFILE command for each
profile row in SYSIBM.DSN_PROFILE_TABLE into
SYSIBM.DSN_PROFILE_HISTORY table, the maximum(8-character-
length) value of PRDID column was not correctly handled.
That resulted in the truncated value of PRDID column in
SYSIBM.DSN_PROFILE_HISTORY.
DB2 has been modified to correctly handle the maximum
PRDID column value when inserting into
SYSIBM.DSN_PROFILE_HISTORY table.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31855
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNT1RSP PI31855
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31855 DSNT1RSP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNT1RSP
LISTEND
UI24953 COVER LETTER END
UI24966 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI28688 -
****************************************************************
* USERS AFFECTED: DB2 10 and DB2 11 for z/OS users with a *
* query containing left outer join or right *
* outer join. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may choose to add an unnecessary *
* sort for queries, when the following *
* conditions are satisfied: *
* 1. The query has left outer join or *
* right outer join; *
* 2. The preserved side is a table *
* expression with an ORDER BY clause, *
* GROUP BY clause, or DISTINCT. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may add an unnecessary sort to the access path if all of
the following conditions are true.
* The query has a left outer join or right outer join.
* The preserved side is a table expression with an ORDER BY
clause, GROUP BY clause, or DISTINCT.
For example,
SQL:
SELECT *
FROM T1
LEFT OUTER JOIN TABLE
(
SELECT *
FROM T2
WHERE T2.C1 = T1.C1
ORDER BY T2.C2
FETCH FIRST 1 ROW ONLY
) E1
ON 1 = 1
LEFT OUTER JOIN T3
ON 1 = 1;
With an index on table T2 as (C1, C2). The table expression E1
is on the preserved side of the left outer join, and the ORDER
BY can be satisfied with the index. DB2 may add a sort plan
for the table expression E1. As a result of the additional
sort, query performance may be negatively impacted.
Additional keywords:
SQLACCESSPATH SQLPERFORMANCE SQLORDERBY SQLGROUPBY SQLDISTINCT
SQLLEFTJOIN SQLLEFT SQLRIGHTJOIN SQLRIGHT
The unnecessary sort is removed if the index can support the
ordering requirements.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28688
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
***Action for PI28688:
See PI28688 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28688 corrects a problem that DB2 may add an unnecessary sort
to the access path when the query has left outer join or right
outer join. Also, the preserved side is a table expression
with an ORDER BY clause, GROUP BY clause, or 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 PI27160:
See PI27160 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27160 corrects a problem about filter factor when the query
contains table with unique index on expression which has only
1 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
DSNXOPRS PI28688
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28688 DSNXOPRS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPRS
LISTEND
UI24966 COVER LETTER END
UI24968 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30688 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement containing a sub-query and a *
* predicate with a literal number that is long *
* to be converted to DECFLOAT. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location *
* DSNXOLTN M780, DSNXOLTI M660, DSNXOLTH *
* M560 or DSNXOLTB M660 could happen for *
* an SQL statement that satisfies all of *
1 * the following conditions: *
* *
* 1. It contains a sub-query. *
* 2. It contains a predicate with a *
* column and a literal number. *
* 3. The column of the predicate is not *
* DECFLOAT and the literal number is *
* converted to DECFLOAT as it is long. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 DECIMAL
,C2 INTEGER
);
SELECT 1
FROM T1
WHERE C2 = 5
AND C1 = 22222333333444444.55555566666777777
AND C2 > (
SELECT 2
FROM T1
WHERE C2 = 3
)
;
The ABEND at the location DSNXOLTN M780 would happen for the
SELECT statement. If C1 was INTEGER, the location of the ABEND
would be DSNXOLTI M660; If C1 was SMALLINT, the location of the
ABEND would be DSNXOLTH M560; If C1 was BIGINT, the location of
the ABEND would be DSNXOLTB M660. DB2 did not correctly process
the aforementioned SQL statement, so it caused the ABEND.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLDECFLOAT SQLSUBQUERY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30688
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM87166:
See PM87166 APAR/PTF text for additional information about
why a REBIND is necessary.
PM87166 corrects a problem of Incorrect output may occur
with UK92607 (V10) or UK92608 (V9). The non correlated SQL
statement that uses constant <> constant predicate where
the constants are integer, bigint or binary and the length
of the constants are different may receive incorrect output.
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PM80911:
See PM80911 APAR/PTF text for additional information about
why a REBIND is necessary.
PM80911 enhances the performance of a non correlated
SQL statements with predicates involving constant
comparisons.
The performance of a non correlated SELECT statement can be
improved if it has a predicate that always evaluates to
false because it is a not equal comparison between two
constants that have the same values. The query can be executed
without accessing the tables in the FROM clause because
the predicate is always evaluated to false
To make this fix effective for a static application, it must 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 PM76608:
See PM76608 APAR/PTF text for additional information about
why a REBIND is necessary.
PM76608 corrects a problem that incorrect output could happen
for an SQL statement that contains FETCH FIRST n ROWS ONLY in a
table expression, on which there is a predicate.
The access path of the SQL statement maybe changed after
applying PM76608, as predicates will not be push down to the
table expression that contains FETCH FIRST n ROWS ONLY.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPRU PI30688
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30688 DSNXOPRU
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPRU
1 LISTEND
UI24968 COVER LETTER END
UI24970 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29183 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS v10 and V11 users. *
****************************************************************
* PROBLEM DESCRIPTION: Infinite loop in DSNIDMPS during *
* DUMP collection. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 ran into an infinite loop when collecting a DUMP, because
DB2 referenced what was released storage.
DB2 code has been modified to fix the looping problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29183
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDMPS PI29183
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29183 DSNIDMPS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDMPS
LISTEND
UI24970 COVER LETTER END
UI24990 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32317 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users running UPDATE *
* statements under dynamic cache option. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 thread is in a loop while running *
* UPDATE statements. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While running with UPDATE statements under dynamic cache
environment, an existing UPROC is invalidated due to
inconsistent table definitions are detected which caused a loop
in the update process.
DB2 code is modified to properly handle the UPROC invalidation
1 by requesting a rebuild of a new UPROC.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32317
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 PI32317
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32317 DSNILREP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
LISTEND
UI24990 COVER LETTER END
UI25013 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31888 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the *
* SQRT (square root) function. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result can occur when an *
* SQL statement uses the SQRT function *
* with an input of 0. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running an SQL statement that includes the SQRT (square
root) function, an incorrect result can be returned if the
input to the SQRT function is zero.
The following example helps to illustrate the problem.
Step 1. Create a Table T1 with one DOUBLE column and insert
a row into the table.
CREATE TABLE T1 (C1 DOUBLE);
INSERT INTO T1 VALUES(0);
Step 2. Perform the following select statement against Table T1.
SELECT SQRT(C1) FROM T1;
The value for SQRT(C1) can be incorrectly returned as NULL when
1 the expected result should be 0.0. This can occur when DB2
inadvertently accesses low storage to check nullability.
However, since low storage contents can be unpredictable, this
can lead to an unpredictable, unexpected, or incorrect result.
Please note: This problem can also occur for other data types
besides DOUBLE.
The code in DB2 has been modified to prevent accessing
low storage when not necessary. This will prevent
returning an incorrect result for the SQRT function.
Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT SQLBIF SQLSQRT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31888
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDOU PI31888
DSNXRNUM PI31888
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31888 DSNXRDOU DSNXRNUM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDOU
DSNXRNUM
LISTEND
UI25013 COVER LETTER END
UI25035 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI25969 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of GROUP BY *
* with SUBSTR *
****************************************************************
* PROBLEM DESCRIPTION: Possible incorrect output can occur for *
* a query using SUBSTR in a GROUP BY if *
* the SUBSTR requires a cast *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Possible incorrect output can occur for a query containing
SUBSTR in a GROUP BY that requires a cast. If an index
exists on the column in the SUBSTR function, a sort for
GROUP BY could be incorrectly missed, leading to incorrect
output.
For example:
1 SELECT SUBSTR(C1, 1, 1), MAX(C2)
FROM T1
WHERE SUBSTR(C1, 1, 1) IN ('1', '2')
GROUP BY SUBSTR(C1,1,1);
C1 is declared as SMALLINT and an index IX1 exists on C1:
IX1(C1)
A cast is required to cast C1 to a character string to
perform the SUBSTR. This type of query could get
incorrect output.
Additional Keywords:
SQLGROUPBY SQLSUBSTR SQLINCORROUT INCORROUT SQLINCORR
DB2INCORR/K
Code is updated to ensure that the required sort for GROUP BY is
added for the situation described above. There is some chance
of experiencing some performance regression for these types of
queries with the added sort, but the sort is necessary to
ensure correct output.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI25969
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI25969:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI25969 corrects a problem of possible incorrect output for
a query containing GROUP BY on a SUBSTR of a column which
requires a cast.
To make this fix effective for a static application, it must 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
DSNXOGBE PI25969
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI25969 DSNXOGBE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBE
LISTEND
UI25035 COVER LETTER END
UI25047 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33294 -
1 ****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4-11 in DSNRIURS following a *
* cancel ABEND04E RC00E50013 during *
* resolve-indoubt processing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Following a cancel ABEND04E RC00E50013 during resolve-indoubt
processing, the FRR in DSNRIURS received an ABEND0C4 RC11
due to incorrect control block addressability.
Control block addressability in the DSNRIURS FRR has been
corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33294
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNRIURS PI33294
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33294 DSNRIURS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNRIURS
LISTEND
UI25047 COVER LETTER END
UI25064 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30747 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER utility. *
****************************************************************
* PROBLEM DESCRIPTION: Lock timeouts due to lock escalation *
* on the DB2 catalog during RECOVER *
* utility. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
User ran RECOVER utility to a prior point in time on a
large list of objects with referential relationships. While
it was running, the job took a significant number of locks
on DSNDB06.SYSTSTPT and other DB2 catalog objects.
Eventually this led to
DSNI031I - LOCK ESCALATION HAS OCCURRED
issued to the console, followed by messages DSNT376I and
DSNT501I and ABEND04E REASON 00C9008E DSNILMCL TYPE 00000210
1 indicating timeouts on DB2 catalog objects.
The lock escalation led to contention with other jobs needing
to serialize on the DB2 catalog, leading to slower throughput
and timeouts in some cases.
This problem could also occur for RECOVER to the current
point in time, and/or recovery on objects without referential
relationships.
Additional keywords: MSGDSNT501I MSGDSNT376I MSGDSNI031I
RC00C9008E MSGDSNT500I DSNT500I MSGDSNU972I DSNU972I
TOLOGPOINT TORBA
Code was changed in the RECOVER utility to prevent lock
escalations on catalog and directory objects.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30747
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUCAIN PI30747
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30747 DSNUCAIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCAIN
LISTEND
UI25064 COVER LETTER END
UI25066 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29707 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the TEMPLATE utility. *
****************************************************************
* PROBLEM DESCRIPTION: Users cannot expand their utility *
* TEMPLATE-defined data set names (DSNs) *
* using local time for &TIME. and &DATE.
*
* substitution variables in DB2 10 for *
* z/OS. All such variables use Universal *
* Coordinated Time (UTC) for TEMPLATE *
* name expansions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
TIME LOCAL function and keywords for TEMPLATE utility are not
available in DB2 10 for z/OS.
The TEMPLATE TIME LOCAL | UTC keywords are added to DB2 10
for z/OS by PI29707, along with the related subsystem
parameter and installation support. The function is the
1 same as that available in DB2 11 for z/OS. The new function
is available in Conversion Mode (CM).
DB2 11 for z/OS is modified to allow TEMPLATE TIME keywords
and existing function to be available in CM mode as well.
The Utility Guide and Reference for DB2 V10 is modified to add
the new keywords and explain their function, similar to the
following, under TEMPLATE utility, common-options subheading:
. . .
>------------------------------------------------------------->
|----TIME---|--LOCAL----|
|---UTC-----|
TIME
Specifies time used in expansion of date and time DSN
variables. The default TIME value is determined by the
TEMPLATE_TIME subsystem parameter.
Tip: Set all DB2 data sharing members to the same value.
LOCAL
Use local time at the DB2 server in the expansion of date
and time in DSN variables.
UTC
Use Coordinated Universal Time (UTC) in the expansion of
date and time in DSN variables.
Subsystem Parameter:
The PTF for PI29707 adds a new DB2 subsystem parameter in
DSN6SPRM called TEMPLATE_TIME that specifies the default
setting for the TIME option of the DB2 TEMPLATE utility,
which is used when the TEMPLATE statement does not specify
the TIME option. Valid settings are:
* LOCAL: Means that the local time is used.
* UTC : Means that Coordinated Universal Time is used.
===> This is the default setting
If you have already installed or migrated to DB2 10, you need to
take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
---------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
==> This action is required for all customers
1 This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
---------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
==> This action is required for all customers
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 TEMPLATE_TIME=<x>
(where <x> is UTC or LOCAL) to the invocation of the
DSN6SPRM macro. Make sure to add a continuation
character in column 72 if needed. If you omit adding
TEMPLATE_TIME here, the value will be set to
the default of UTC 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 TEMPLATE_TIME to
the CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
TEMPLATE_TIME CHAR G LOCAL UTC <x>
Change <x> to the value you specified for
TEMPLATE_TIME in step (2), above.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI29707
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PI30243
This PTF modifies DSNTXAZP, a program that can be used to
refresh a DB2 installation CLIST input (DSNTIDxx) member with
DB2's current subsystem parameter, DSNHDECP parameter, and
buffer pool settings. If you have already installed or migrated
to this version of DB2 and you use DSNTXAZP then you need to
update the package: Submit a job that contains the following
BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
ACTION:
PI29707 introduces the following changes to externals:
New option for TEMPLATE utility:
TIME
Specifies time used in expansion of date and time DSN
variables. The default TIME value is determined by the
TEMPLATE_TIME subsystem parameter.
Tip: Set all DB2 data sharing members to the same value.
LOCAL
Use local time at the DB2 server in the expansion of date
and time in DSN variables.
UTC
Use Coordinated Universal Time (UTC) in the expansion of
date and time in DSN variables.
New subsystem parameter for DSN6SPRM:
TEMPLATE_TIME
Specifies the default setting for the TIME option of the
DB2 TEMPLATE utility, which is used when the TEMPLATE
statement does not specify the TIME option. Valid settings
are:
* LOCAL: Means that the local time is used.
* UTC : Means that Coordinated Universal Time is used.
===> This is the default setting
Information about these changes will be included in the DB2 for
z/OS collection in the IBM Knowledge Center
(http://www-01.ibm.com/support/knowledgecenter/
1 SSEPEK/db2z_prodhome.html)
at a later date.
If you have already installed or migrated to DB2 10, you need to
take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
---------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
---------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you need
to update your customized copy of this job as follows:
* Add the keyword parameter TEMPLATE_TIME=<x>
(where <x> is UTC or LOCAL) to the invocation of the
DSN6SPRM macro. Make sure to add a continuation
character in column 72 if needed. If you omit adding
TEMPLATE_TIME here, the value will be set to
the default of UTC 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 TEMPLATE_TIME to
the CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
TEMPLATE_TIME CHAR G LOCAL UTC <x>
1 Change <x> to the value you specified for
TEMPLATE_TIME in step (2), above.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
ACTION:
***Action for PI29286 (DB2 10)
This PTF modifies DSNTXAZP, the DSNTIDxx refresh tool to fix
an error that causes the wrong MAX VALUE setting to be assigned
to the DSNTIDxx entries for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED.
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 private copies of the DSNTIDxx CLIST input member
(2) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
You need to verify that your DSNTIDxx members have the
appropriate MAX VALUE settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. For each private DSNTIDxx member, proceed
as follows:
(a) Edit the member
(b) Locate the entry for SIMULATED_CPU_COUNT. If the fifth
field (MAX VALUE) specifies 255, change it to NONE. In
other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <x>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <x>
where <x> is the current setting of SIMULATED_CPU_COUNT.
(c) Locate the entry for SIMULATED_CPU_SPEED. If the fifth
field (MAX VALUE) specifies 2147483647, change it to NONE.
In other words, change this format:
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <y>
to this:
SIMULATED_CPU_SPEED CHARR G OFF NONE <y>
where <y> is the current setting of SIMULATED_CPU_SPEED.
1
(d) Save any changes you made and proceed to your next DSNTIDxx
member
Repeat steps (a) - (d) for each DSNTIDxx member.
---------------------------------------------------------------
(2) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@XAZP PI29707
DSNDQWPZ PI29707
DSNDSPRM PI29707
DSNTIDXA PI29707
DSNTIDXB PI29707
DSNTIJUZ PI29707
DSNTINST PI29707
DSNTXAZP PI29707
DSNUFCMR PI29707
DSNUGPRT PI29707
DSNUGTDS PI29707
DSNWZIFA PI29707
DSN6SPRM PI29707
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29707 DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ
DSNTINST DSNTXAZP DSNUFCMR DSNUGPRT DSNUGTDS DSNWZIFA
DSN6SPRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNTXAZP
DSNUFCMR
DSNUGPRT
DSNUGTDS
DSNWZIFA
MACROS
DSN@XAZP
DSNDQWPZ
DSNDSPRM
DSNTIDXA
DSNTIDXB
1 DSNTIJUZ
DSNTINST
DSN6SPRM
LISTEND
UI25066 COVER LETTER END
UI25092 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32732 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* utility users of LOAD with CCSID translation *
* and TRUNCATE *
****************************************************************
* PROBLEM DESCRIPTION: LOAD with CCSID translation of a CHAR *
* column specifying TRUNCATE, results in *
* wrong data being loaded into the column *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
LOAD of a unicode table with mixed data, utilizing CCSID
translation and specifying TRUNCATE for a CHAR column resulted
in the wrong data being loaded into that column. This was
because the LOAD did not truncate the multibyte characters at
their character boundary, which caused some multibyte characters
to be partly loaded.
Additional keywords - INCORROUT
LOAD code has been changed to truncate the mixed data at a
character boundary for the aforementioned cases.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32732
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURWBG PI32732
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32732 DSNURWBG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURWBG
LISTEND
UI25092 COVER LETTER END
UI25097 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31854 -
1 ****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS and DB2 11 for *
* z/OS who use the stored procedure *
* SYSPROC.ADMIN_INFO_SQL or the batch program *
* DSNADMSB. *
****************************************************************
* PROBLEM DESCRIPTION: CREATE INDEX statements generated by *
* stored procedure SYSPROC.ADMIN_INFO_SQL *
* for indexes that have an INCLUDE clause *
* with only one column can fail *
* processing with SQLCODE -199. *
****************************************************************
* RECOMMENDATION: Apply the fixing PTF for this APAR. *
****************************************************************
ADMIN_INFO_SQL and DSNADMSB are not generating the DDL
correctly for indexes with INCLUDE column. Right parenthesis
will be missed when only one column exists in the INCLUDE
clause.
An example of this case is as below:
CREATE UNIQUE INDEX IDX1 ON TAB1(C1 ASC) INCLUDE(C2) CLUSTER;
The DDL generated by ADMIN_INFO_SQL is like this:
CREATE UNIQUE INDEX IDX1 ON TAB1(C1 ASC) INCLUDE(C2 CLUSTER;
ADMIN_INFO_SQL and DSNADMSB are modified to generate correct
index with INCLUDE column when only one column exists in the
INCLUDE clause.
ADDITIONAL KEYWORDS:
SQLSP SQLSTOREDPROC ADMININFOSQL DSNADMSB SQLINCLUDE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31854
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM94681 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede the instructions for any previous PTF on
ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS.After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
1 bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
DB2BIND:
***Action for PI31854 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
DB2BIND:
***Action for PI25905 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
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.
DB2BIND:
***Action for PI21058 (DB2 10 for z/OS)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates program module DSNADMSS and the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to bind
the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.
ACTION:
***Action for PI30399 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to DB2 10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
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.
ACTION:
***Action for PI07646 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede any previous PTF instructions.
If you have already installed or migrated to DB2 V10, you need
to take the following action after applying this PTF:
---------------------------------------------------------------
Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@DMSS PI31854
DSNADMSS PI31854
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31854 DSN@DMSS DSNADMSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNADMSS
MACROS
DSN@DMSS
LISTEND
1UI25097 COVER LETTER END
UI25124 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30216 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the LOAD, UNLOAD and REORG *
* TABLESPACE utilities. *
****************************************************************
* PROBLEM DESCRIPTION: 1.ABEND04E RC00E40018 and MSGDSNU095I *
* during a RESTART of a REORG TABLESPACE *
* PART utility. *
* *
* 2.MSGDSNU082I and RC8 for a LOAD using *
* the SYSPUNCH data set from a prior *
* UNLOAD utility. *
* *
* 3.MSGDSNU1233I and RC8 for an UNLOAD *
* utility. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
1.A REORG TABLESPACE PART utility was restarted in the SWITCH
phase but abended with an ABEND04E RC00E40018 and
DSNU095I - UTILITY 'REORG' INCONSISTENT WITH LAST INVOCATION.
2.A LOAD utility using the utility statement (SYSPUNCH) from
a prior UNLOAD utility ended with RC8 with
DSNU082I - INVALID KEYWORD - BINARYXML issued for INTEGER and
CHAR columns. The utility statement did not include a field
specification list.
3.An UNLOAD utility on a table with DECIMAL columns and no
field specification list ended with RC8 with
DSNU1233I - DATA IS TOO LONG FOR FIELD name, TABLE name
All three problems were caused by the utility either using
a residual or invalid pointer.
Code has been modified to correct the aforementioned problems.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30216
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGPRS PI30216
DSNUULGL PI30216
DSNUULVA PI30216
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30216 DSNUGPRS DSNUULGL DSNUULVA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNUGPRS
DSNUULGL
DSNUULVA
LISTEND
UI25124 COVER LETTER END
UI25133 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28562 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users with PI06647 / UI16531 UI16532 *
* applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40317 DSNUFOBD OFFSET9A6 *
* with DSNU283I SQLCODE -20465 and *
* RC00C90110 during a LOAD FORMAT SPANNED *
* YES of BINARYXML data when PI06647 *
* UI16531 or UI16532 is applied. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
With PI06647 UI16531 (DB2 10) or UI16532 (DB2 11) applied, a
LOAD FORMAT SPANNED YES of an XML column loading BINARYXML
data abended with an ABEND04E RC00E40317 DSNUFOBD x'09A6'
with MSGDSNU283I SQLCODE20465 and RC00C90110. The LOAD utility
was loading the XML data with a structure that was setup
incorrectly for BINARYXML data.
LOAD code has been modified to build the correct structures
needed to insert the BINARYXML data.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28562
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 PI28562
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28562 DSNURWBF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURWBF
LISTEND
UI25133 COVER LETTER END
UI25153 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI32837 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the *
* CORRELATION built-in aggregate function. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result set (containing *
* unexpected and 'out of range' *
* correlation values) can be returned *
* from a query that references the *
* CORRELATION built-in aggregate function *
* and contains a GROUP BY. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result set containing unexpected or 'out of range'
correlation values can be returned from a query that references
the CORRELATION aggregate built-in function. The query contains
a GROUP BY and the problem can occur if there is more than one
group.
The following example provides a failing case.
Step 1. Create a Table T1.
CREATE TABLE T1 (
PROD_ID INTEGER NOT NULL
,BUS_DATE DATE NOT NULL
,C_MONTH INTEGER NOT NULL
,TIME_HRZN_NUM SMALLINT NOT NULL
,SETTLED_AMT DECIMAL(8,2) NOT NULL
) ;
Step 2. Insert data into Table T1.
INSERT INTO T1 VALUES(
1111, '2015-01-28', 1, 1, 2000.00);
INSERT INTO T1 VALUES(
1111, '2015-01-27', 2, 1, 3000.00);
INSERT INTO T1 VALUES(
1111, '2015-01-26', 1, 1, 6000.00);
INSERT INTO T1 VALUES(
1111, '2015-01-25', 2, 1, 7000.00);
Step 3. Run the following query.
SELECT
CORRELATION(A.SETTLED_AMT, A.SETTLED_AMT+1)
FROM T1 A
1 WHERE A.PROD_ID = 1111
AND A.C_MONTH IN (1,2)
AND A.TIME_HRZN_NUM = 1
GROUP BY A.C_MONTH ;
Step 4. Check the results.
The unexpected or incorrect result is
-------------------------+
1_| 1.000000000000000E+00 |
2_| ? | <=== incorrect
-------------------------+
or something like
-------------------------+
1_| 1.000000000000000E+00 |
2_| 1.610769704821793E+00 | <=== incorrect
-------------------------+
The expected or correct result is
+------------------------+
1_| 1.000000000000000E+00 |
2_| 1.000000000000000E+00 |
+------------------------+
The second correlation value is not only incorrect but it can
fall outside the range of an acceptable correlation value.
The code in DB2 is modified to allow a correct result to be
returned for the CORRELATION function.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLBIF SQLCORRELATION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32837
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI32837:
See PI32837 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32837 corrects a bind time problem that can cause an incorrect
result set to be returned for queries that contain the
CORRELATION built-in aggregate 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
DSNXGSDV PI32837
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32837 DSNXGSDV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGSDV
LISTEND
UI25153 COVER LETTER END
UI25178 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30749 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users *
* who have applied PI14839/UI20649 *
* /UI20650 *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 IN CSECT DSNIXLKP+0538 *
* when processing INDOUBT URs *
* during DB2 RESTART, and PI14839 *
* /UI20649/UI20650 was previously *
* applied. *
****************************************************************
* RECOMMENDATION: Apply the corrective PTF when it is *
* available. *
****************************************************************
After PI14839/UI20649/UI20650 was applied, during
DB2 restart, when processing the log to acquire the
exclusive lock on pageset,table or database, an
internal pointer to the database recovery control
table was not set with the correct memory address,
causing the 0C4 abend.
DSNIXLKP is modified to correctly set the local pointer to
the database recovery control block.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30749
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIXLKP PI30749
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30749 DSNIXLKP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIXLKP
LISTEND
1UI25178 COVER LETTER END
UI25180 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI18152 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM2.3) users data sharing in *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: High IRLM CPU time may be observed some *
* times due to spike in locking in data *
* sharing. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM CPU time may increase during and after a big number of
child lock processing in IRLM. The number of child locks to be
propagated to XES could be in hundreds of thousands. If a large
number of these requests are heuristically converted to async
in XES, IRLM Complete Exit may run into issues like - contention
on CML lock to get new storage, page faults to get storage from
existing pool. This could lead to delay in XES SRB processing
which may also show IXL045E message on console. Systems running
low on REAL storage could experience excessive paging activity
which drives up CPU time.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
In this APAR IRLM is enhancing the child lock processing logic.
IRLM will estimate the size of storage required to process all
child locks requests asynchronously in the Complete Exit. IRLM
will pre-allocate this storage and use a block from this for
any asynchronous complete. This storage will be released at
the end when the child lock processing is complete. IRLM will
not use QEFX pool for child props of size greater than 1000.
Not expanding the QEFX pool for such cases, will reduce the
number of page faults in accessing QEFX pool segments and hence
improve the CPU time in the Complete Exit processing.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI18152
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2T0 PI18152
DXRRL2T1 PI18152
DXRRL200 PI18152
DXRRL732 PI18152
DXRRL780 PI18152
DXRRL790 PI18152
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI18152 DXRRL2T0 DXRRL2T1 DXRRL200 DXRRL732 DXRRL780 DXRRL790
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2T0
DXRRL2T1
DXRRL200
DXRRL732
DXRRL780
DXRRL790
LISTEND
UI25180 COVER LETTER END
UI25181 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28370 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM 2.3) users data sharing *
* SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may issue ABEND04E RC00C90101 in *
* DSNISRID due to incorrect feedback on *
* a lock rejection from IRLM. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
DB2 may get unexpected feedback from IRLM on a lock rejection
causing it to issue ABEND04E RC00C90101 in DSNISRID. In some
situation IRLM may not set an appropriate reason for rejection
when a conditional lock request was found incompatible. IRLM
sets RC=8 with RLPRCB13 = YES, which is not expected and
handled by the caller in DB2. Dump taken by DB2 is too late to
find the root cause of this problem. More serviceability is
needed to find request parameters when it was processed in IRLM.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
This APAR adds serviceability code in IRLM to take diagnostic
dumps of all members in a data sharing group when IRLM detects
that the conditional attribute in the RLPL was different than
than what was known to IRLM in the UDB at the time of request
processing. IRLM will also set the correct feedback code so that
the DB2 caller would not issue 00C90101 abend in DSNISRID.
As another change in this APAR, IRLM will suppress more than one
diagnostic dump issued from DXRRL2T0 for lock rejection due to
an incompatible retain lock held in IRLM. User can re-enable
this existing trap (when needed) by issuing IRLM modify command
F irlmproc,diag,none
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI28370
1 SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL2T0 PI28370
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28370 DXRRL2T0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL2T0
LISTEND
UI25181 COVER LETTER END
UI25211 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33529 -
****************************************************************
* USERS AFFECTED: All data sharing users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: A QRep thread reading the DB2 logs *
* with the IFI READS for IFCID 306 *
* facility began looping in DSNJR106 *
* after another DB2 member in the *
* data sharing group was going through *
* the RBA reset procedure including *
* a cold start back to RBA zero. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A QRep thread was reading the DB2 logs with the IFC READS for
IFCID 306 facility while another member in the data sharing
group was doing a cold start to reset the log RBA back to
RBA zero. Processing an F-Call from the QRep thread, DB2 read
the peer BSDS records for the COPY2 active logs right after
the active log entries were reset to 'empty' (no RBA range)
as a result of the peer member cold start. Since no COPY2
active logs contained an RBA range, DB2 freed the obsolete
LDSD blocks but did not clear the COPY2 LDSD anchors for the
log search routines. A subsequent log inventory search then
went into a loop in DSNJR106 as the LDSD storage had been
reused. The invalid LDSD anchors can also result in an
ABEND0C4 in DSNJPOPN or an ABEND04E RC00E20029 in DSNSVBK.
The logic error in DSNJPOPN has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33529
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 DSNJPOPN PI33529
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33529 DSNJPOPN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJPOPN
LISTEND
UI25211 COVER LETTER END
UI25213 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32543 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
* of queries containing non-correlated EXISTS *
* subqueries. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may incorrectly overestimate the *
* cost to execute a non-correlated EXISTS *
* subquery. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may overestimate the cost to execute a non-correlated EXISTS
subquery. For example,
SELECT ...
FROM T1
WHERE EXISTS (
SELECT 1
FROM T2
)
It is possible that the incorrect cost estimation may result
in a poor access path choice and resulting poor query
performance. The incorrect cost estimate is more likely to
affect the predictive governor by prohibiting quick running
queries from executing based on the incorrect estimated cost.
Additional Keywords:
SQLPERFORMANCE SQLACCESSPATH SQLEXISTS SQLSUBQUERY
SQLNONCORRSUBQ
DB2 code has been changed to more accurately estimate the cost
of a non-correlated EXISTS subquery.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32543
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI32543:
1 A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI32543 corrects a problem in which DB2 may overestimate the
cost of a non-correlated EXISTS subquery. This may lead to
an inefficient access path and poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTS2 PI32543
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32543 DSNXOTS2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTS2
LISTEND
UI25213 COVER LETTER END
UI25223 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32623 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users who encounter *
* an SQLCODE -904 with reason code RC00E70081 *
* during DROP, ALTER, or RENAME, or, get an *
* ABEND04E dump with a module name of 'DSN' *
* at logical offset P000. *
* *
****************************************************************
* PROBLEM DESCRIPTION: When DB2 issues SQLCODE -904 with *
* reason code RC00E7910D during the long *
* prepare of a dynamic SQL statement, *
* cleanup processing can be incomplete *
* which leaves the cached SQL statement *
* in an inconsistent state. This can *
* cause various and unpredictable *
* abends and sqlcodes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An SQLCODE -904 with reason code RC00E70081 can occur subsequent
to receiving an SQLCODE -904 with reason code RC00E7910D
(storage shortage) when inserting a dynamic SQL statement into
the dynamic statement cache during the PREPARE process.
The failure of inserting the statement into the cache is not
detected and leaves control block structures in a half-built
1 state. This scenario could cause the use counts in the dynamic
statement cache to get out of sync, which will eventually result
in a hard -904 RC00E70081 that is not resolvable without
recycling the member whose count is off.
DB2 will correctly inspect the return code from the dependency
manager to ensure a consistent cache entry.
Additional keywords: SQLDYNSTMTCACHE SQLALTER,
SQLDROP SQLRENAME SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32623
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXEDS1 PI32623
DSNXEIST PI32623
DSNXEUCS PI32623
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32623 DSNXEDS1 DSNXEIST DSNXEUCS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDS1
DSNXEIST
DSNXEUCS
LISTEND
UI25223 COVER LETTER END
UI25234 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30393 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* RUNSTATS utility users collecting *
* frequency statistics on column groups. *
****************************************************************
* PROBLEM DESCRIPTION: RUNSTATS TABLESPACE inserted rows *
* into SYSCOLDIST catalog table for *
* an empty table. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
When RUNSTATS TABLESPACE TABLE COLGROUP was executed
on an empty table, the utility inserted a row into the
SYSIBM.SYSCOLDIST catalog table.
When the target table is empty, no statistics rows
should be inserted into SYSCOLDIST catalog table.
Code was modified to avoid inserting rows in the SYSCOLDIST
catalog table when the target object is empty.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30393
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUSEF2 PI30393
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30393 DSNUSEF2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUSEF2
LISTEND
UI25234 COVER LETTER END
UI25236 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28566 -
****************************************************************
* USERS AFFECTED: DB2 10 and DB2 11 for z/OS users with a *
* query containing equal predicates with a *
* parameter marker and IN-list predicates. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may choose to add an inefficient *
* access path, when the following *
* conditions are satisfied: *
* 1. The query has equal predicates with *
* a parameter marker; *
* 2. The query has IN-list predicates; *
* 3. The equal predicates and IN-list *
* predicates may be matching *
* predicates; and *
* 4. BIND with REOPT(ONCE) option. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may choose an inefficient access path, when the query has
equal predicates with a parameter marker and in-list predicates
which may be matching predicates, and the query is bound
with the REOPT(ONCE) option.
For example,
SQL:
SELECT *
FROM T1
WHERE C1 = ?
AND C2 IN (1, 2, 3);
There is an equal predicate with a parameter marker as C1 = ?,
1 and also an in-list predicate C2 IN (1, 2, 3). There is an
index IX1(C1, C2) on the table T1. The predicate C1 = ? and
C2 IN (1, 2, 3) are potential matching predicates. If the
query is bound with REOPT(ONCE), DB2 may choose an inefficient
access path.
Additional keywords:
SQLACCESSPATH SQLPERFORMANCE SQLIN SQLEQUAL PARAMETERMARKER
SQLPMARKER SQLPMK
Code is fixed to solve the problem described as above. The
DB2 optimizer would choose efficient access path in that
situation.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28566
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI15740:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI15740 corrects a problem where incorrect output can occur
for a query which uses a range list access path and contains
multiple range predicates on the same column in the same
direction.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOGBM PI28566
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28566 DSNXOGBM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOGBM
LISTEND
UI25236 COVER LETTER END
UI25240 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30161 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users with locking protocol *
* 2 active. *
****************************************************************
* PROBLEM DESCRIPTION: An entire table space or partition *
* added to LPL by a castout engine. *
1 * The MSGDSNB250E shows a CSECT name of *
* DSNB5PCO, a page range of X'00000000' *
* to X'FFFFFFFF', and an LPL reason type *
* of CASTOUT. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
With locking protocol 2 active, a table space or partition
P-lock may be acquired and upgraded while the object is not
physically open. DB2 already avoids acquiring castout
ownership on this type of an upgrade request. However, if a
request to acquire the P-lock was held up by other requests,
it may detect that the P-lock is already held - and upgraded -
while it was waiting. The detection of an upgraded P-lock at
this point can acquire castout ownership, which may later put
pages into LPL if castout is requested and the object is still
not physically open.
The pageset P-lock acquisition code has been modified to detect
that it was invoked for a protocol 2 "dummy open", and in
that
case to not acquire castout ownership even if the P-lock is
held in an upgraded state.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30161
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1OPL PI30161
DSNB1OPP PI30161
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30161 DSNB1OPL DSNB1OPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1OPL
DSNB1OPP
LISTEND
UI25240 COVER LETTER END
UI25277 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31068 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result or an abend can *
* occur if DB2 inadvertently attempts to *
* access storage for a null byte with *
* respect to data that is defined as 'not *
* null' when executing an SQL statement. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
An incorrect result or an abend can occur if DB2 inadvertently
attempts to access storage for a null byte for data that is
defined as 'not null'.
This can occur when DB2 tries to reference the address of the
null byte for an internal data buffer containing data defined as
'not null'. Because this address can be in low storage, the
contents can be unpredictable which can lead to an unexpected,
unpredictable, or undesirable result.
Some of the possible symptoms include:
1. An incorrect result can be returned.
2. An SQLCODE -304, SQLCODE -330, SQLCODE -420, SQLCODE -443, or
SQLCODE -545 can be issued on behalf of the processing for an
incorrect result.
3. An ABEND04E RC00E70005 can occur at location
DSNXGRDS DSNXRFC P004.
The code in DB2 has been modified to prevent accessing storage
for the 'null byte' when not necessary. This will allow a
correct result to be returned.
Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT SQLCODE304 SQLCODE330
SQLCODE420 SQLCODE443 SQLCODE545
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31068
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 PI31068
DSNXRINT PI31068
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31068 DSNXRCSF DSNXRINT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRCSF
DSNXRINT
LISTEND
UI25277 COVER LETTER END
UI25296 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29478 -
1 ****************************************************************
* USERS AFFECTED: All Users of DB2 version 10 *
* and DB2 version 11 for z/OS ODBC/CLI driver *
****************************************************************
* PROBLEM DESCRIPTION: The Shift-In character '0F' is missing *
* in the result returned when fetching *
* data into EBCDIC mixed and setting *
* the ODBC initialization keyword *
* LIMITEDBLOCKFETCH to 1. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The Shift-In character '0F' is missing in the result returned
when fetching data into EBCDIC mixed and setting the ODBC
initialization keyword LIMITEDBLOCKFETCH to 1.
The following example illustrates the problem:
1. Set LIMITEDBLOCKFETCH=1 in the ODBC INI file.
2. Prepare a SELECT statement which selects a VARCHAR column
from a UNICODE table. The column returned in the result
set contains mixed data.
3. Call SQLBindCol()to bind the column.
4. Execute the SELECT statement.
5. Fetch the column into EBCDIC mixed CCSID 939.
Check the returned data in HEX.
Expected value: X'0e466346cb48b948e20f'
Actual returned value is : X'0e466346cb48b948e2'
The ODBC driver is modified to return the correct result when
fetching data into EBCDIC mixed and setting LIMITEDBLOCKFETCH
to 1.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI29478
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOG1V PI29478
DSNAOCLI PI29478
DSNAOSDK PI29478
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29478 DSNAOG1V DSNAOCLI DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOG1V
DSNAOCLI
1
MACROS
DSNAOSDK
LISTEND
UI25296 COVER LETTER END
UI25309 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32172 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM 2.3) and HIR2220 (IRLM2.2) *
* users data sharing SYSPLEXDS. *
****************************************************************
* PROBLEM DESCRIPTION: Lock requests from DB2/IMS may receive *
* out of CF lock structure storage error *
* and requesting workunits may terminate. *
* This can continue even after CF lock *
* structure storage (RLE usage) have been *
* relieved. *
* MSGDXR142E for 80% lock structure in- *
* use was issued but DXR142E for 90% use *
* may never come out. IMS may continue to *
* issue abendu3307. DB2 may also continue *
* to issue MSGDSNT501I with 00C900BF *
* reason code, even after other members *
* report that the CF Lock structure *
* storage shortage conditions have been *
* relieved and MSGDXR169I was issued. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM monitors CF lock structure RLE usage count and starts
rejecting new lock requests that are not must-complete when
the RLE usage is 90% or more. IRLM healthcheck logic would
trigger queries at 90% usage to the CF lock structure to update
the RLE usage count periodically. An error in IRLM calculation
in the health check logic may find the usage as 89% only for 90%
structure full condition. As a result, IRLM does not issue the
CF query to correct the RLE usage count.
GEN:
KEYWORDS:
SYSPLEXDS
*** END IMS KEYWORDS ***
With this APAR, IRLM health check code that computes percentage
full conditions of RLE storage in the CF lock structure, is
corrected. When the structure is 90% full, IRLM health check
will issue IXLMG call at 3 seconds interval to periodically
update the current RLE usage until the RLE usage becomes less
than 90% in use.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI32172
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
1 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL272 PI32172
DXRRL732 PI32172
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32172 DXRRL272 DXRRL732
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DXRRL272
DXRRL732
LISTEND
UI25309 COVER LETTER END
UI25345 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30794 -
****************************************************************
* USERS AFFECTED: DB2 users of the command processor where *
* the input command exceeds 256 characters *
* and contains lower case text within quotes. *
****************************************************************
* PROBLEM DESCRIPTION: Lower case text contained within quotes *
* is not honored. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The DB2 command processor initially folds all commands to upper
case prior to processing the contents within. The command
processor will not fold text to upper case if the string is
between quotes.
.
When the command text is longer than 256 characters, the input
is processed 256 bytes at a time. When this occurs and text
within the quotes does not end within this boundary,
the next 256 bytes will be processed as unquoted and will
accidentally fold the rest of the string.
DB2 has been modified to honor the text within the quotes
if it exceeds the 256 byte boundary.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30794
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN9SCN0 PI30794
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30794 DSN9SCN0
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN9SCN0
LISTEND
UI25345 COVER LETTER END
UI25349 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29850 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS V9, V10 and V11 users of *
* SELECT with global Temp Table are used. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E50002 at DSNIPSBL+04F0 *
* while canceling a SELECT from a global *
* temp table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a SELECT from a global temp table job is canceled, the
recovery process in DB2 did not properly reset a latch flag
which caused an abend at DSNIPSBL+04F0 later.
DB2 code has been modified to properly reset the latch flag in
the recovery process.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29850
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIWKFD PI29850
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29850 DSNIWKFD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWKFD
LISTEND
UI25349 COVER LETTER END
UI25369 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30140 -
****************************************************************
* USERS AFFECTED: All DB2 10 & 11 for z/OS users that use *
* EXPLAIN on a query with a type CAST function *
* can be affected. *
****************************************************************
1 * PROBLEM DESCRIPTION: Incorrect output length on a cast to *
* GRAPHIC or VARGRAPHIC type in *
* DSN_PREDICAT_TABLE when explaining *
* a query. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
When we do an EXPLAIN plan for a SELECT statement with GRAPHIC
or VARGRAPHIC type casting on a column, we'll get an incorrect
length for GRAPHIC and VARGRAPHIC types.
ex.
EXPLAIN PLAN SET QUERYNO = 1 FOR
SELECT C1 FROM T1
WHERE CAST(C1 AS VARGRAPHIC(5)) = 'abc';
EXPLAIN output for TEXT column in DSN_PREDICAT_TABLE.
-------------------------------------------
| CAST("T1"."C1" AS VARGRAPHIC(10))='abc' |
-------------------------------------------
For the example above, TEXT field in DSN_PREDICAT_TABLE shows
VARGRAPHIC length as VARGRAPHIC(10) which is twice the length
being specified. The same problem occurs with GRAPHIC type as
well. The reason that we are seeing a '10' as the length for
VARGRAPHIC or GRAPHIC type is because we wrote a double-byte
character string size out to the DSN_PREDICAT_TABLE instead
of its specified length.
DB2 code has been corrected to accurately write the specified
length for a cast to GRAPHIC & VARGRAHPIC types in the
DSN_PREDICAT_TABLE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30140
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODTX PI30140
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30140 DSNXODTX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODTX
LISTEND
UI25369 COVER LETTER END
UI25413 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI31611 -
****************************************************************
* USERS AFFECTED: All DB2 11, 10 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABND=0C4-00000004 at DSNB1ABO+2E4 *
* during agent de-allocation process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When de-allocating an agent, DB2 freed an internal control
block that's needed for its page set logical close process.
This caused the ABND=0C4-00000004 at DSNB1ABO+2E4.
Fixes made in DB2 to close the page set first before freeing
its internal control block that's still needed in its page
set close process.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31611
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDALC PI31611
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31611 DSNIDALC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDALC
LISTEND
UI25413 COVER LETTER END
UI25417 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32067 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* that using scrollable sensitive cursor with *
* nullable fieldproc. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNICMAT *
* ERQUAL5006 may occur for select using *
* scrollable sensitive cursor with *
* nullalbe fieldproc. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C90101 at DSNICMAT ERQUAL5006 may occur for select
using scrollable sensitive cursor with nullalbe fieldproc.
An example for the error case is:
1
CREATE TABLE T3(C1 INT, C2 CHAR(4) FIELDPROC FPCVD4);
EXEC SQL DECLARE CUR1 SENSITIVE STATIC SCROLL CURSOR WITH HOLD
SELECT C2 FROM T3;
The bindtime code in DB2 has been modified to correct the
conditions which can lead to the abend.
Additional Keywords: ABEND04E RC00C90101 SQLSENSITIVE
SQLSCROLL SQLFIELDPROC SQLNULL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32067
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PI32067 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
Apar PI32067 corrects the conditions that can lead to the
occurrence of an ABEND04E RC00C90101 at DSNICMAT ERQUAL5006
for select using scrollable sensitive cursor with fieldproc.
To make this fix effective for a static application, it must 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
DSNXOSCR PI32067
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32067 DSNXOSCR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOSCR
LISTEND
UI25417 COVER LETTER END
UI25443 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32144 -
****************************************************************
* USERS AFFECTED: Users of the DB2 10 or DB2 11 for z/OS *
* PL/1 precompiler. *
****************************************************************
* PROBLEM DESCRIPTION: Precompiler messages are incorrectly *
* not issued during precompile of PL/1 *
* variable declarations. *
****************************************************************
1 * RECOMMENDATION: *
****************************************************************
Precompiler messages are incorrectly not issued when
precompiling PL/1 host variable declarations.
An example where a message could be incorrectly not issued
might occur when a comment causes a CCSID conversion error
like this:
DCL 1 struct1, / * non-convertable chars * /
3 field1;
The correct behavior is that the precompiler should issue
message DSNH331I.
DB2 code is modified so the precompiler correctly issues
the missing messages.
ADDITIONAL KEYWORDS: PRECOMPILER PL/1 CONVERSION
SUBSTITUTION CHARACTERS
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32144
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNHLIST PI32144
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32144 DSNHLIST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHLIST
LISTEND
UI25443 COVER LETTER END
UI25461 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32145 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of LOBs *
* (Large Objects) in the distributed *
* environment. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC11 at location DSNIDM *
* DSNOGETD OFFSET2926 or an incorrect *
* result can occur in the distributed *
* environment when a remote application *
* inserts into a table containing a *
* LOB column several times using *
* different host variable data types. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 RC11 at location DSNIDM DSNOGETD OFFSET2926 or an
incorrect result can occur in the distributed environment when
a remote application inserts into the LOB column of a table
several times, using host variables with different data types.
The following example helps to illustrate the problem.
1. Create a Table with one INT column and one CLOB column.
! Connect application to a database server
EXEC SQL CONNECT TO STLEC2;
CREATE TABLE T1 (C1 INT, C2 CLOB(1M));
2. From an application, define three HOSTVARs and an INSERT
statement.
DCL HVCLOB SQL TYPE IS CLOB(1M);
DCL HVCHAR CHAR(100) VARYING;
DCL HVINT BIN FIXED(31);
DCL MYSTR1 CHAR(100) VARYING;
MYSTR1 = 'INSERT INTO T1 VALUES(?,?)';
3. Set the hostvars and prepare the SQL statement.
EXEC SQL CONNECT TO STLEC2;
EXEC SQL SET :HVCLOB = REPEAT('DDF CLOB',2000);
EXEC SQL SET :HVCHAR = 'ADMF CLOB';
EXEC SQL PREPARE STMT1 FROM :MYSTR1;
4. From the application to be run in a distributed environment,
execute the INSERT statement twice.
DO HVINT = 1 TO 2;
IF (HVINT = 1) THEN
DO;
EXEC SQL EXECUTE STMT1 USING :HVINT, :HVCLOB;
END;
ELSE
DO;
EXEC SQL EXECUTE STMT1 USING :HVINT, :HVCHAR;
END;
END;
1 DB2 does not clear the residual information from the first
insert before performing the second insert. This can mislead
the LOB processing and result in the abend mentioned above.
Please note however that the offset 2926 can differ. Also, an
incorrect result can be returned depending on the size of the
input CLOB data.
The code in DB2 is modified to clear the residual information of
the previous SQL statement. This will prevent the abend or
incorrect result.
Additional Keywords: SQLLOB DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT SQLHOSTVAR
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32145
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRIB9 PI32145
DSNXRID9 PI32145
DSNXRIHB PI32145
DSNXRIHD PI32145
DSNXRIHR PI32145
DSNXRIHS PI32145
DSNXRIS9 PI32145
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32145 DSNXRIB9 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS
DSNXRIS9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRIB9
DSNXRID9
DSNXRIHB
DSNXRIHD
DSNXRIHR
DSNXRIHS
DSNXRIS9
LISTEND
UI25461 COVER LETTER END
UI25492 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30408 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users with *
* Data Partition Secondary Index (DPSI). *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIRSET:2004 *
* was issued from a Fetch Next process *
1 * with a Hold cursor on a DPSI. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 keeps its position on a DPSI in its Cursor Block (CUB).
But mistakenly assume the position is still good after commit.
When the position has been changed, DB2 tried to use the
old position to fetch next record, it failed a sanity check
with ABEND04E RC00C90101 at DSNIRSET:2004.
Fixes made in DB2 to preserve its position in the CUB if there
is still a cursor held on the DPSI.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30408
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICMTC PI30408
DSNIFDPO PI30408
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30408 DSNICMTC DSNIFDPO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICMTC
DSNIFDPO
LISTEND
UI25492 COVER LETTER END
UI25502 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31186 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of pureXML. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E70005 DSNNQIV M111 may *
* occur when the SQL/XML function is *
* called. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an internal error occurs, the error return code is not
handled properly which causes the ABEND04E RC00E70005 DSNNQIV
M111 to occur.
DB2 is modified to return the error, instead of ABEND.
Additional keywords: SQLXML XMLALL SQLFUNCTION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31186
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
DSNNQDTM PI31186
DSNNQIV PI31186
DSNNQMD PI31186
DSNNQOPM PI31186
DSNNQOPN PI31186
DSNNQOPR PI31186
DSNNQOPS PI31186
DSNNQRES PI31186
DSNNQTOP PI31186
DSNNQXCA PI31186
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31186 DSNNQDTM DSNNQIV DSNNQMD DSNNQOPM DSNNQOPN DSNNQOPR
DSNNQOPS DSNNQRES DSNNQTOP DSNNQXCA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNNQDTM
DSNNQIV
DSNNQMD
DSNNQOPM
DSNNQOPN
DSNNQOPR
DSNNQOPS
DSNNQRES
DSNNQTOP
DSNNQXCA
LISTEND
UI25502 COVER LETTER END
UI25504 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33530 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users using *
* indexes. *
****************************************************************
* PROBLEM DESCRIPTION: RUNSTATS utility abended with ABEND04E *
* RC00E2000F MODDSNIDALC MODDSNSVSFB *
* OFFSET08C6 while processing an index. *
* DB2 subsystem crashed after this abend. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While running RUNSTATS utility on an index, if the index is
disorganized, index manager reads index non leaf pages in order
to prefetch index leaf pages. In this process, index manager
needs to copy an index key from the non-leaf page to the Cursor
Block(CUB) dynamic storage area, in order to save the last page
that was prefetched. When there are no keys(IPNKEYS=0) on the
1 non-leaf page that was last processed, Index Manager
could move invalid storage and overlay the CUB dynamic
storage area. This will cause an abend
ABEND04E RC00E2000F DSNIDALC.DSNSVSFB OFFSET08C6
during thread deallocation time.
This error could also happen when running REORG INDEX utility,
CHECK INDEX utility or SQL using index access.
Index Manager code has been updated so in the index leaf page
list prfetch code path, Index Manager will only copy the index
key from a non-leaf page, if there is at least one key on the
page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33530
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 PI33530
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33530 DSNKLFPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKLFPR
LISTEND
UI25504 COVER LETTER END
UI25528 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31819 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS Data Sharing *
* Users *
****************************************************************
* PROBLEM DESCRIPTION: HIGH CPU PEAKS IN XCFAS *
****************************************************************
* RECOMMENDATION: *
****************************************************************
High CPU peaks in XCFAS was caused by short spin loops in XES
waiting for Cross-system extended services (XES) SHR/EXCL lock,
IXLSHR. This lock was held by DB2.
DB2 was holding the Cross-system extended services (XES)
SHR/EXCL lock, while acquiring information regarding the
for SCA or LOCK1 structures in the coupling facility (CF).
DB2 was modified such that it will hold the IXLSHR lock for a
short period of time.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31819
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
DSN7GCMD PI31819
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31819 DSN7GCMD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN7GCMD
LISTEND
UI25528 COVER LETTER END
UI25534 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31527 -
****************************************************************
* USERS AFFECTED: DB2 z/OS V10 and V11 queries using the *
* Data Partitioned Secondary Index (DPSI) *
* with a WHERE clause. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20004 DSNSVBK +'0718' *
* and the caller is DSNIGSEL. Large *
* number of SelP and SelK blocks were *
* requested by DSNIGSEL and DSNKGSEL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABENDS04E RC00E20004 occurred due to ADMF storage pool full.
The storage was filled with a rather large number of SELK and
SELP storage blocks. These SELK and SELP storage blocks were
acquired repeatedly for the same query, causing the storage
pool to be full.
DB2 code was fixed to acquire the SELP and SELK storage
block correctly. This error is only relevant to queries
using DPSI indexes.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31527
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIFDPO PI31527
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31527 DSNIFDPO
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFDPO
1
LISTEND
UI25534 COVER LETTER END
UI25537 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31472 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* XMLMODIFY function. *
****************************************************************
* PROBLEM DESCRIPTION: When using XMLMODIFY function to update *
* XML documents in multiple rows, if the *
* SET clause includes a sideway reference *
* of the table, then only one row is *
* updated, even though the message says *
* SUCCESSFUL UPDATE OF more then one *
* ROW(S). *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using XMLMODIFY function to update XML documents in
multiple rows, if the SET clause includes a sideway reference
of the table, then only one row is updated, even though the
message says SUCCESSFUL UPDATE OF more then one ROW(S).
For example:
The table T1 is create by following CREATE statement.
CREATE TABLE T1
(
I1 INTEGER,
X1 XML
);
Three records are inserted into the table as below.
INSERT INTO T1 VALUES(1,
'<a><b>n</b></a>');
INSERT INTO T1 VALUES(2,
'<a><b>n</b></a>');
INSERT INTO T1 VALUES(3,
'<a><b>n</b></a>');
Below is the UPDATE statement to change the value of b node
to 'y', if the value of b node is not already in 'y'.
UPDATE T1 A
SET X1 =
XMLMODIFY(
'replace value of node /a/b with $Z',
'y' AS "Z")
WHERE (SELECT XMLCAST(XMLQUERY('/a/b' PASSING X1)
AS CHAR(1))
FROM T1 E
WHERE A.I1 = E.I1)
<> 'y';
1 The UPDATE statement returns zero SQLCODE with following
message.
SUCCESSFUL UPDATE OF 3 ROW(S)
But after querying the data, only the third row is updated as
below.
<?xml version="1.0"
encoding="IBM037"?><a><b>n</b></a>
<?xml version="1.0"
encoding="IBM037"?><a><b>n</b></a>
<?xml version="1.0"
encoding="IBM037"?><a><b>y</b></a>
DB2 is modified so all the qualified rows are updated.
Additional keywords: SQLXML XMLALL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31472
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 PI31472
DSNNQMD PI31472
DSNNQTOP PI31472
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31472 DSNILREP DSNNQMD DSNNQTOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILREP
DSNNQMD
DSNNQTOP
LISTEND
UI25537 COVER LETTER END
UI25539 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32491 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* REORG TABLESPACE utility users. *
****************************************************************
* PROBLEM DESCRIPTION: REORG does not exploit full possible *
* degree of unload/reload parallelism *
* when running with DB2 Sort for z/OS *
* due to memory constraints below the *
* line indicated by DSNU397I NUMBER OF *
* TASKS CONSTRAINED BY VIRTUAL STORAGE *
* BELOW. Utility elapsed time performance *
* may not be optimal in that case. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
1 ****************************************************************
REORG may not run with optimal degree of data unload/reload
parallelism due to an expected memory constraint below the line
when running with DB2 Sort which would be indicated by
MSGDSNU397I.
In addition, REORG is performing an unnecessary scan of dirty
pages at the beginning of the LOG phase which can result in
extended elapsed time.
Estimation of the below the line memory consumption when
running with DB2 Sort has been improved to allow more tasks
to run in parallel. REORG logic has also been modified to
bypass the unnecessary dirty page scan at the beginning of
the LOG phase.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32491
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 PI32491
DSNURPCT PI32491
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32491 DSNURLOG DSNURPCT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURLOG
DSNURPCT
LISTEND
UI25539 COVER LETTER END
UI25544 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32834 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of CHECK INDEX, CHECK DATA or *
* CHECK LOB with SHRLEVEL CHANGE *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS0C4 DSNUGSDA OFFSET5B96 during *
* a CHECK INDEX SHRLEVEL CHANGE utility *
* that had been terminated. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A -TERM UTIL of a CHECK INDEX SHRLEVEL CHANGE utility abended
with an ABEND0C4 DSNUGSDA +x'5B96'. During termination
processing, a residual pointer was used to close a data set
causing the abend. The data set had been deallocated and the
pointer should be zeroed.
1
This problem can also occur for a CHECK LOB SHRLEVEL CHANGE,
and a CHECK DATA SHRLEVEL CHANGE.
CHECK has been modified to zero the data set pointer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32834
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUKCOP PI32834
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32834 DSNUKCOP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUKCOP
LISTEND
UI25544 COVER LETTER END
UI25546 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31438 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS RRSAF users. *
****************************************************************
* PROBLEM DESCRIPTION: An RRSAF thead is hung after an *
* ABENDEC6 and MVS cancel processing. *
* Message DSNR048I is issued for the *
* hang backout. The RRSAF threads are *
* suspended in either DSNB5RDP or *
* DSNB1TIMR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An RRSAF thead is hung after an ABENDEC6 and MVS cancel
processing. Message DSNR048I is issued for the hang.
The RRSAF threads are suspended in either DSNB5RDP or
DSNB1TMR.
RRS implicit Backout is called with the
ATRXFlagApplicationAsyncAbend flag set.
DB2 has been updated to also check for the ABENDEC6.
The ABEND222, ABEND13E and ABENDEC6 checking have
also been put into the RRSAF exit recovery routine.
COMPONENT: 5740-XYR01-HIZAA10
APARS FIXED: PI31438
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
This PTF updates the ERLY code. After you apply this fix,
1 you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY
ACTION:
This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY
ACTION:
This PTF requires either an ERLY code refresh or a re-IPL
of zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
the PTF.
ACTION:
***Action for PI18566:
This PTF requires either an ERLY code refresh or a re-IPL of
zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
the PTF.
ACTION:
This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1 1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAPRHX PI31438
DSN3RRXF PI31438
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31438 DSNAPRHX DSN3RRXF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAPRHX
DSN3RRXF
LISTEND
UI25546 COVER LETTER END
UI25563 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31597 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users *
* who are using, or plan to use, *
* High Performance DBAT support. That is, *
* users which operate DDF with option *
* PKGREL(BNDOPT). *
****************************************************************
* PROBLEM DESCRIPTION: Threads unexpectedly hold package and *
* table space intent locks. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 10 for z/OS introduced a new DDF server thread processing
mode called High Performance DBATs. With APAR PI20352, DB2
was changed to address situations where the activation of High
Performance DBATs could lead to an increase in the CPU consumed
to process distributed client requests. The change enabled the
pooling of high performance DBATs when the requesting client
connection (using the DBAT) was terminated.
When a High Performance DBAT is allowed to be pooled, as a
result of the PI20352 change, any client connection could
potentially be serviced by this DBAT - even a client
connection that was not enabled to utilize a High
Performance DBAT. This results in application connections
having (or inheriting) unexpected "package allocation" and/or
"table space intent" locks from other unrelated applications.
DB2 has been changed to restore the prior (to APAR PI20352)
PKGREL(BNDOPT) behavior. But in order to accommodate client
environments where any connection can utilize High Performance
DBATs, DB2 has also been changed to support a new BNDPOOL
High Performance DBAT processing option value via the
1 -MODIFY DDF PKGREL(BNDPOOL) command.
When DDF has been modified to run with a PKGREL value of
BNDOPT, DDF will (again) terminate a High Performance DBAT
when the client connection terminates.
When DDF has been modified to run with a (new) PKGREL value of
BNDPOOL, DDF will pool a high performance DBAT when the client
connection terminates.
Thus, for those customers who configure client environments
with or without the ability to use High Performance DBATs, a
PKGREL value of BNDOPT may be the preferred value. For
those customers who just configure DDF server resources to
allow any client connection to use High Performance DBATs,
a PKGREL value of BNDPOOL may be the preferred value.
Documentation changes are required to describe the function
provided by this APAR.
Changes to the DB2 10 and DB2 11 Messages Manuals.
---------------------------------------------------------------
The explanation text of messages DSNL004I and DSNL302I is
changed:
* The description of the BNDOPT value of the PKGREL DDF
processing option is changed to have an additional paragraph
as follows:
When a connection which has used a high performance DBAT
terminates, the high performance DBAT will also be
deallocated.
* A description of a new PKGREL DDF processing option value,
BNDPOOL, is added as follows:
BNDPOOL
DDF processing for the BNDPOOL option value will be the
same as the BNDOPT option value with the following
exception: when a connection which has used a high
performance DBAT terminates, the high performance DBAT
will be pooled. The pooled DBAT can then be used by
any other connection which presents a request to this
DB2 subsystem.
Changes to the DB2 10 and DB2 11 Command Reference manuals.
---------------------------------------------------------------
The description of the PKGREL option of the MODIFY DDF command
is replaced with the following:
PKGREL
Specifies whether DB2 honors the bind options of packages that
are used for remote client processing. The PKGREL option also
controls the disposition of high performance DBATs when a
1 client connection which has used a high performance DBAT has
terminated.
BNDOPT
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
by a terminating client connection will be deallocated.
BNDOPT is the default value of the MODIFY DDF PKGREL command.
BNDPOOL
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
by terminating a client connection will be pooled.
COMMIT
The rules of the RELEASE(COMMIT) bind option are applied to
any package that is used for remote client processing. COMMIT
is the default value when the CMTSTAT subsystem parameter is
set to ACTIVE. If the MODIFY DDF PKGREL command had never been
issued, then COMMIT is the default value. No high performance
DBATs exist while the PKGREL option is set to COMMIT.
The usages notes of the -MODIFY DDF command is changed as
follows:
When to use PKGREL options: You can specify that DDF uses the
PKGREL(BNDOPT) or PKGREL(BNDPOOL) option during normal
production operating hours. For environments where client
configurations control the use of packages which were bound
with the RELEASE(DEALLOCATE) bind option, BNDOPT will be the
preferred value of the PKGREL option. For environments where
any client is capable of using packages bound with the
RELEASE(DEALLOCATE) bind option, BNDPOOL will be the preferred
value of the PKGREL option. Either option value offers
improved performance by reducing the amount of CPU costs for
allocating and deallocating packages. However, packages that
run under the rules of the RELEASE(DEALLOCATE) bind option are
likely to remain allocated and prevent maintenance activities
such as objects modifications and bind operations.
Consequently, you can use the PKGREL(COMMIT) option during
routine and emergency maintenance periods.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31597
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
***Documentation for PI31597:
See PI31597 APAR/PTF text for additional information.
Documentation changes are required to describe the function
provided by this APAR. The product documentation contained
1 in the DB2 for z/OS Knowledge Center will be updated at a
later date.
Changes to the DB2 10 and DB2 11 Messages Manuals.
---------------------------------------------------------------
The explanation text of messages DSNL004I and DSNL302I is
changed:
* The description of the BNDOPT value of the PKGREL DDF
processing option is changed to have an additional paragraph
as follows:
When a connection which has used a high performance DBAT
terminates, the high performance DBAT will also be
deallocated.
* A description of a new PKGREL DDF processing option value,
BNDPOOL, is added as follows:
BNDPOOL
DDF processing for the BNDPOOL option value will be the
same as the BNDOPT option value with the following
exception: when a connection which has used a high
performance DBAT terminates, the high performance DBAT
will be pooled. The pooled DBAT can then be used by
any other connection which presents a request to this
DB2 subsystem.
Changes to the DB2 10 and DB2 11 Command Reference manuals.
---------------------------------------------------------------
The description of the PKGREL option of the MODIFY DDF command
is replaced with the following:
PKGREL
Specifies whether DB2 honors the bind options of packages that
are used for remote client processing. The PKGREL option also
controls the disposition of high performance DBATs when a
client connection which has used a high performance DBAT has
terminated.
BNDOPT
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
by a terminating client connection will be deallocated.
BNDOPT is the default value of the MODIFY DDF PKGREL command.
BNDPOOL
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
1 by terminating a client connection will be pooled.
COMMIT
The rules of the RELEASE(COMMIT) bind option are applied to
any package that is used for remote client processing. COMMIT
is the default value when the CMTSTAT subsystem parameter is
set to ACTIVE. If the MODIFY DDF PKGREL command had never been
issued, then COMMIT is the default value. No high performance
DBATs exist while the PKGREL option is set to COMMIT.
The usages notes of the -MODIFY DDF command is changed as
follows:
When to use PKGREL options: You can specify that DDF uses the
PKGREL(BNDOPT) or PKGREL(BNDPOOL) option during normal
production operating hours. For environments where client
configurations control the use of packages which were bound
with the RELEASE(DEALLOCATE) bind option, BNDOPT will be the
preferred value of the PKGREL option. For environments where
any client is capable of using packages bound with the
RELEASE(DEALLOCATE) bind option, BNDPOOL will be the preferred
value of the PKGREL option. Either option value offers
improved performance by reducing the amount of CPU costs for
allocating and deallocating packages. However, packages that
run under the rules of the RELEASE(DEALLOCATE) bind option are
likely to remain allocated and prevent maintenance activities
such as objects modifications and bind operations.
Consequently, you can use the PKGREL(COMMIT) option during
routine and emergency maintenance periods.
ACTION:
***Action for PI31597:
For users which operate DDF with PKGREL(BNDOPT) option, as
shown by a -DISPLAY DDF command, this APAR may be of interest
to you.
High Performance DBAT processing is activated when the PKGREL
value is set to BNDOPT. APAR PI20352 changed the behavior
of High Performance DBAT processing. This APAR, PI31597, will
restore the prior (to PI20352) behavior of High Performance
DBAT processing.
For those users which desire the High Performance DBAT
processing behavior to be as provided by APAR PI20352, a
-MODIFY DFF PKGREL(BNDPOOL) command can now be issued.
See PTF cover letter for more information.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGEFLC PI31597
DSNGEPLC PI31597
DSNLEDDA PI31597
DSNLQCTL PI31597
DSNLQDIS PI31597
DSNLSSST PI31597
DSNLTDDF PI31597
DSNLTMDF PI31597
DSNLXPRS PI31597
DSN9SCNA PI31597
1
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31597 DSNGEFLC DSNGEPLC DSNLEDDA DSNLQCTL DSNLQDIS DSNLSSST
DSNLTDDF DSNLTMDF DSNLXPRS DSN9SCNA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGEFLC
DSNGEPLC
DSNLEDDA
DSNLQCTL
DSNLQDIS
DSNLSSST
DSNLTDDF
DSNLTMDF
DSNLXPRS
DSN9SCNA
LISTEND
UI25563 COVER LETTER END
UI25565 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33612 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 may occur in module DSNWVSR1 *
* when there is an invalid CCB pointer. *
* This CCB pointer should have been *
* cleared earlier by module DSNVFACE. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 may occur in module DSNWVSR1
when it finds an invalid CCB pointer.
Module DSNVFACE has been updated to clear the CCB pointer.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33612
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVFACE PI33612
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33612 DSNVFACE
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVFACE
1 LISTEND
UI25565 COVER LETTER END
UI25570 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29239 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER and COPY utility with *
* PI05573/UI15308/UI15309 applied *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC10 at DSNUCBMT + x'8C66' *
* occurred during RECOVER PARALLEL of a *
* list of objects with PI05573/UI15308/ *
* UI15309 applied. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
With PI05573 / UI15308 / UI15309 applied, RECOVER PARALLEL of a
list of objects may ABENDS0C4 RC10 at DSNUCBMT OFFSET8C66
because RECOVER utility may use an incorrect index to check for
subtasks. The problem happens when there are not enough tape
drives to support the degree of parallelism.
This problem happens intermittently and a similar problem may
also happen with COPY PARALLEL.
Additional Keywords: DSNUBBID OFFSET6FC4
RECOVER and COPY utilities have been modified to use the correct
index to check for subtasks during parallel processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29239
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBBID PI29239
DSNUCBMT PI29239
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29239 DSNUBBID DSNUCBMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBBID
DSNUCBMT
LISTEND
UI25570 COVER LETTER END
UI25614 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI32640 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: An incorrect result can occur if DB2 *
* inadvertently attempts to access *
* storage for a null byte with respect *
* to data that is defined as 'not null' *
* when executing an SQL statement. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result can occur if DB2 inadvertently attempts to
access storage for a null byte for data that is defined as
'not null'.
This can occur when DB2 tries to reference the address of the
null byte for an internal data buffer containing data defined
as 'not null'. Because this address can be in low storage, the
contents can be unpredictable which can lead to an unexpected,
unpredictable, or undesirable result.
Some of the possible symptoms include:
1 An incorrect result can be returned for an SQL statement
using any of the following functionality : NORMALIZE_STRING
function, ARRAY_NEXT function, ARRAY_PRIOR function or
DATE/TIME durations.
2 An SQLCODE -470 can be issued on behalf of the processing of
an incorrect result.
The code in DB2 has been modified to prevent accessing storage
for the 'null byte' when not necessary. This will allow a
correct result to be returned.
Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
SQLINCORROUT SQLCODE470 SQLSP
SQLSTOREDPROC
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32640
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
***Action for PM41805:
See PM41805 APAR/PTF text for additional information about
why further ACTION might be necessary.
PM41805 corrects a problem that can occur when DATETIME
arithmetic returns a NULL value. However, DB2 does not zero out
the data part of the result and can leave it containing "bad"
data. Eventually, this can cause an incorrect result to be
returned.
For the recreate example described in the apar PM41805 text, if
the incorrect data already exists in the database, the following
simple example (steps) might be helpful in correcting it.
1
1. Drop the index which has the LAST_DATE column as one of the
index keys.
DROP INDEX I1;
COMMIT;
2. Apply the PTF for apar PM41805 and recycle DB2.
3. Rerun the UPDATE statement which causes the incorrect result.
UPDATE T1
SET LAST_DATE =
LAST_DATE - ((DAYS('07/20/2010') - DAYS('05/28/2009'))DAYS);
4. Recreate the dropped index.
CREATE INDEX I1
ON T1 (IDN ASC, LAST_DATE ASC);
COMMIT;
5. Execute the SELECT statement (again) which uses index access
and references the LAST_DATE column as a stage 1 predicate.
SELECT * FROM T1 WHERE IDN = 2 AND LAST_DATE IS NULL;
After the application of apar PM41805 and re-running the UPDATE
statement in Step 3., a correct NULL value will correct/replace
the "bad" null value in the table. Once the same index is
recreated, and the LAST_DATE column is referenced as a stage 1
predicate in the SELECT query, a correct result will be
returned.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXRDTF PI32640
DSNXRDT9 PI32640
DSNXRPPL PI32640
DSNXRSB2 PI32640
DSNXRS39 PI32640
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32640 DSNXRDTF DSNXRDT9 DSNXRPPL DSNXRSB2 DSNXRS39
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXRDTF
DSNXRDT9
DSNXRPPL
DSNXRSB2
DSNXRS39
LISTEND
UI25614 COVER LETTER END
1
UI25616 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33252 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a static *
* cursor UPDATE SQL statement whose right side *
* of the SET clause is an expression *
* containing a correlated scalar-fullselect. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output could happen for a *
* static cursor UPDATE SQL statement *
* whose right hand side of the SET clause *
* is an expression containing a *
* correlated scalar-fullselect. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1 (
C1 CHAR(9)
, C2 INT
);
CREATE TABLE T2 (
C1 CHAR(9)
, C2 INT
);
INSERT INTO T1 VALUES ('888888888',33);
INSERT INTO T1 VALUES ('111111111',33);
INSERT INTO T2 VALUES ('222222222',66);
INSERT INTO T2 VALUES ('111111111',22);
INSERT INTO T2 VALUES ('333333333',55);
A program with following static SQL statements:
DECLARE CUR1 CURSOR
WITH HOLD FOR
SELECT C1, C2
FROM T1 A FOR UPDATE OF C2
...
UPDATE T1 A
SET C2 =
(COALESCE ((SELECT C2
FROM T2 B
WHERE A.C1 = B.C1), 1))
WHERE CURRENT OF CUR1
The UPDATE statement should change the row ('111111111',33) of
T1 to ('111111111',22), while it was incorrectly changed to
('111111111',1).
DB2 has been modified to correctly process the aforementioned
UPDATE SQL statement, and there will be no incorrect output.
1
Additional keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLUPDATE SQLSUBQUERY
SQLCORRSUBQ SQLSCALAR SQLFULLSELECT
SQLSCALARFULSEL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33252
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI33252:
See PI33252 APAR/PTF text for additional information about
why a REBIND is necessary.
PI33252 corrects a problem that incorrect output could happen
for a static cursor UPDATE SQL statement whose right hand side
of the SET clause is an expression containing a correlated
scalar-fullselect.
To make this fix effective for a static application, it must 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
DSNXOST PI33252
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33252 DSNXOST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOST
LISTEND
UI25616 COVER LETTER END
UI25631 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29949 -
****************************************************************
* USERS AFFECTED: DB2 z/OS v10 and v11 workfile users. *
****************************************************************
* PROBLEM DESCRIPTION: For DB2-managed non-PBG workfile *
* table space, if PRIQTY is > 2G *
* and SECQTY = 0, the table space would *
* grow into multiple pieces. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For DB2-managed non-PBG workfile table spaces, having the
definition of SECQTY = 0 should govern that no additional
piece be created.
1 DB2 code is changed to not create additional pieces for non-PBG
workfile pagesets with SECQTY of 0.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29949
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIBWAC PI29949
DSNPXTN0 PI29949
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29949 DSNIBWAC DSNPXTN0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIBWAC
DSNPXTN0
LISTEND
UI25631 COVER LETTER END
UI25679 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32265 -
****************************************************************
* USERS AFFECTED: All DB2 zOS select from insert and insert *
* users with mixed BRF and RRF partitions in *
* a PBG table space. *
****************************************************************
* PROBLEM DESCRIPTION: After installing apar PI29436, various *
* errors appeared. Problem symptoms *
* include but not limit to the following: *
* abend04E 00C90101 DSNIDM.DSNISGRT:5362 *
* abend04E 00c90216 DSNIDM.DSNIOST2:53CD *
* abend04E 00c90101 DSNIDM.DSNIMOFR:501B *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a PBG table space has mixed BRF/RRF partitions, Insert or
Select from Insert could mistakenly add an incorrect record
format data onto the table. The mistake was caused by that
the original target partition for the insert is to an RRF
partition, but the RRF partition did not have the space for
the insert, so the next available space is on an BRF partition.
The data record is converted to BRF, but the partition becomes
full, the insert ends up in another RRF partition. The data
written to the final destination got mixed up and an incorrect
record format row is written out to the table.
Code is corrected to handle the data record so that the correct
data format is used.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI32265
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 PI32265
DSNISRTI PI32265
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32265 DSNISGRT DSNISRTI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGRT
DSNISRTI
LISTEND
UI25679 COVER LETTER END
UI25718 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32031 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of REBUILD INDEX for logical partition *
* of non-partitioned index (NPI). *
****************************************************************
* PROBLEM DESCRIPTION: A REBUILD INDEX for a logical partition *
* of a descending NPI abended with *
* ABEND04E RC00C90101 at DSNKINSL:5033. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A REBUILD INDEX was running on a NPI which was defined on a
nullable and variable length column with DESC keyword. It
abended with ABEND04E RC00C90101 at DSNKINSL ERQUAL5033.
The problem occurred because an internal variable was
incorrectly initialized for the varying length index key.
REBUILD INDEX code has been modified to initialize the internal
variable correctly.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32031
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
With the application of the PTF for PI29608, REBUILD INDEX code
has been changed to issue a maximum of 2000 DSNU340I messages
for duplicate keys. The utility will issue message DSNU1140I -
MESSAGE LIMIT OF 2000 HAS BEEN REACHED FOR THE DSNU340I
MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY once this
level has been reached. REBUILD INDEX will continue processing
the current index(es) and will continue to end with RC8 due to
1 the duplicate keys being found.
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURBXC PI32031
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32031 DSNURBXC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURBXC
LISTEND
UI25718 COVER LETTER END
UI25720 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI26468 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of part level online REORG with *
* SORTNPSI NO. *
****************************************************************
* PROBLEM DESCRIPTION: A partition level REORG TABLESPACE *
* SHRLEVEL REFERENCE or CHANGE with *
* SORTNPSI NO on a table space with a *
* non-partitioned index (NPI) reset the *
* NPI real-time statistics (RTS) in *
* SYSINDEXSPACESTATS.REORGINSERTS to zero *
* which should be the count of the *
* index entries inserted into the NPI. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A part level REORG SHRLEVEL CHANGE with SORTNPSI NO was run on
a table space with a NPI. The index RTS value REORGINSERTS in
the catalog table SYSIBM.SYSINDEXSPACESTATS was reset to zero by
this REORG.
However, this count should reflect the index entries which were
inserted to the NPI.
REORG and RTS code has been modified to not reset
SYSINDEXSPACESTATS REORGINSERTS and REORGAPPENDINSERT. These
statistics will be updated during the REORG to reflect the
count of index entries which are inserted into the NPI during a
partition level REORG SHRLEVEL REFERENCE or CHANGE with SORTNPSI
NO.
The following columns of this table are updated accordingly:
REORGDELETES
REORGPSEUDODELETES
REORGMASSDELETE
REORGNUMLEVELS
REORGLEAFNEAR
REORGLEAFFAR
REORGINDEXACCESS
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI26468
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIRTSX PI26468
DSNURSWD PI26468
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI26468 DSNIRTSX DSNURSWD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIRTSX
DSNURSWD
LISTEND
UI25720 COVER LETTER END
UI25733 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28835 -
****************************************************************
* USERS AFFECTED: All HIR2230 (IRLM230) users. *
****************************************************************
* PROBLEM DESCRIPTION: IRLM abended S0C4 in DXRRL400 and then *
* DB2 failed with reason code 00C202AB *
* and 00C90093. *
****************************************************************
* RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
****************************************************************
IRLM variable pool segment header was overlaid. An IRLM storage
request for a variable element returned an address with dirty
high-half. This caused ABENDS0C4 in IRLM storage manager.
GEN:
KEYWORDS:
*** END IMS KEYWORDS ***
Code is added to clear the high-half of the variable pool
element address before returning to the requester.
COMPONENT: 5695-16401-HIR2230
APARS FIXED: PI28835
SPECIAL CONDITIONS:
COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DXRRL400 PI28835
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28835 DXRRL400
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DXRRL400
LISTEND
UI25733 COVER LETTER END
UI25757 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32663 -
****************************************************************
* USERS AFFECTED: All DB2 V11 and DB2 V10 for z/OS users of *
* IFI 306. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00000038 DSNIDCML+550 when *
* Decompressing a log record with *
* compressed data. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When decompressing log record using IFI 306, Data Manager
execute an internal procedure to find the internal Descriptor
of the Object (OBD). If the compressed object is dropped, this
internal procedure failed to save the non-zero return code into
an internal DM control block for the caller. It results in the
caller of this procedure ignore the Resource Not Available (RNA)
exception and then cause the reported problem.
DB2 is changed to save the return code to the DM internal
control block correctly to make sure the caller of this
internal procedure is informed about any RNA exception.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32663
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIPSFI PI32663
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32663 DSNIPSFI
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIPSFI
LISTEND
UI25757 COVER LETTER END
UI25760 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33674 -
****************************************************************
1 * USERS AFFECTED: All DB2 V10 and V11 for z/OS users of LOB *
* Table Space. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNOFLMP ERQUAL2001 *
* WHEN LOB TABLE SPACE IS FULL. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If the LOB table space is full and has reached its last valid
piece, the get page procedure will exit with return code 16 and
reason code 'C20064'. But DB2 checks the wrong registers to
handle this exception. It causes DB2 take the reported abend
instead of the SQLCODE -904.
DB2 is changed to make sure the correct registers will be
checked to handle the full LOB tablespace exception.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33674
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNOFLMP PI33674
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33674 DSNOFLMP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNOFLMP
LISTEND
UI25760 COVER LETTER END
UI25775 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31608 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RC38 in DSNVSRRX, typically *
* after some other abend. In the *
* reported instance, there was an *
* ABEND058 RC8 at the beginning of the *
* abend sequence. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DSNVSRRX is entered due to percolation from a prior abend.
If the thread involved is long-term suspended, register 2
may not be set correctly for execution of the recovery
routine. In the reported case, this caused an ABEND0C4 RC38
but in general the results are unpredictable.
General purpose register 2 should be set to a value that was
1 saved earlier. The initialization code of DSNVSRRX has been
corrected to set register 2 as expected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31608
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 PI31608
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31608 DSNVSRRX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVSRRX
LISTEND
UI25775 COVER LETTER END
UI25778 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34956 -
****************************************************************
* USERS AFFECTED: AE PI28996 FIX COMPLETION *
****************************************************************
* PROBLEM DESCRIPTION: AE PI28996 FIX COMPLETION *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI28996 FIX COMPLETION
AE PI28996 FIX COMPLETION
PI28996 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of QUERY ACCELERATION *
* ELIGIBLE or ALL behaviors *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE352 or SQLCODE904 returned for *
* an accelerated query in a CLI *
* application when all of the following *
* conditions apply: *
* - the accelerated query has a WHERE *
* predicate that references a DATE *
* column with an associated host *
* variable or parameter marker ('?') *
* instead of a literal constant, and *
* - the accelerated query is prepared or *
* bound using QUERY ACCELERATION *
* ELIGIBLE or ALL behaviors *
****************************************************************
* RECOMMENDATION: *
****************************************************************
1 SQLCODE352 or SQLCODE904 returned for an accelerated query in
a CLI application when all of the following conditions apply:
- the accelerated query has a WHERE predicate that references
a DATE column with an associated host variable or parameter
marker ('?') instead of a literal constant, as in
the following simple example:
SELECT * FROM table-name
WHERE DATE-column > ?
FOR FETCH ONLY
- the accelerated query is prepared or bound using
QUERY ACCELERATION ELIGIBLE or ALL behaviors.
.
If CLI deferred prepare is enabled (i.e., the DeferredPrepare
configuration keyword has a value of 1), then DB2 returns
SQLCODE -352 .
If CLI deferred prepare is disabled (i.e., the DeferredPrepare
configuration keyword has a value of 0), then DB2 returns
SQLCODE = -904 REASON = 00E7000E TYPE = 00001080 and
accelerator message text =
' HY000: ERROR: Bad date external representation ...'
.
The failure occurs due to DB2 returning incorrect DESCRIBE
INPUT information to the CLI client for the host variable
associated with the DATE column referenced in the query's WHERE
predicate. The incorrect DESCRIBE INPUT information was returned
because DB2 did not perform the full existing DB2 semantic
processing during the PREPARE or bind of an SQL query when
using QUERY ACCELERATION ELIGIBLE or ALL behaviors.
.
The reported failure does not occur when using
QUERY ACCELERATION ENABLE or ENABLE WITH FAILBACK behaviors.
.
After the PTF for PI28996 is applied, when you use QUERY
ACCELERATION ELIGIBLE or ALL behaviors, DB2 will now perform
the standard existing DB2 full semantic processing and error
checking that is already done for a query prepared either for
acceleration using QUERY ACCELERATION ENABLE or for running
'only' in DB2 (QUERY ACCELERATION NONE). This includes
DB2 generating the DESCRIBE INPUT information that is needed for
the failing case reported in this APAR. So now a query will get
consistent DB2 semantic processing and error checking whether
the query is prepared for acceleration or for running 'only' in
DB2. As a result, if the first time you ran a certain query was
with QUERY ACCELERATION ELIGIBLE or ALL behavior and you had
never run the query 'only' in DB2 before (QUERY ACCEL NONE),
after the PTF is applied DB2 may now validly fail the query with
-SQLCODEs during PREPARE or bind time where DB2 did not before,
because the existing full DB2 semantic error checking is 'now'
used for QUERY ACCELERATION ELIGIBLE or ALL behaviors. Note that
the query already fails the same way when using QUERY
ACCELERATION ENABLE behavior or when prepared to run only in DB2
(QUERY ACCELERATION NONE). If you have run the query 'only' in
DB2 before or with QUERY ACCELERATION ENABLE behavior prior to
using ELIGIBLE or ALL behaviors, then you will not see this
change in DB2 error checking because your query is already
valid.
1 DB2 QUERY ACCELERATION ELIGIBLE and ALL behaviors were changed
to build correct DESCRIBE INPUT information for WHERE predicate
host variables. Additionally, for ELIGIBLE and ALL behaviors
DB2 will now perform the standard existing DB2 error and
semantic checking that is already done for ENABLE acceleration
behavior or for running 'only' in DB2.
.
Additional search keywords: IDAAV3R1/K IDAAV4R1/K
QUERYACCELERATION
SQLCODE352 SQLCODE904
SQLHOSTVAR PARAMETERMARKER SQLPMK
SQLPMARKER
.
.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34956
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI28863:
See PI28863 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28863 corrects a problem of SQLCODE504 from DSNXEPP is
received during a remote rebind for an UPDATE WHERE CURRENT OF
statement with an invalid cursor and the statement was bound
successfully with SQLERROR(CONTINUE).
To make this fix effective for a static application, it must 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 PI28996:
PI28996 APAR/PTF is only for DB2 query acceleration to
an accelerator. After the PTF for PI28996 is applied,
when using QUERY ACCELERATION ELIGIBLE or ALL behaviors for
certain queries that have never before run 'only' in DB2,
DB2 may now validly fail those queries with existing -SQLCODEs
during PREPARE or bind time if those queries fail the existing
DB2 semantic error checking. Prior to this APAR, the 'full' DB2
semantic error checking was not done for accelerated queries
when using QUERY ACCELERATION ELIGIBLE or ALL behaviors.
Please see APAR/PTF closing text for more information.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODML PI34956
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34956 DSNXODML
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODML
1 DSNXOEXE
DSNXOOS2
LISTEND
UI25778 COVER LETTER END
UI25795 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31567 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of DSN1COPY and DSN1PRNT utilities *
****************************************************************
* PROBLEM DESCRIPTION: 1) MSGDSN1954I issued during a DSN1COPY *
* utility copying from a non-first piece *
* of a linear table space *
* *
* 2) No page printed when a DSN1PRNT *
* utility was done for the non-first *
* piece of a linear table space which was *
* not empty *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A DSN1COPY utility was used to copy from a non-first piece of a
linear table space. DSN1954I - DSN1COPY PARAMETER PAGESIZE OR
LOB IS MISSING OR INCORRECTLY SPECIFIED was issued. The DSN1COPY
job ended with RC8.
A DSN1PRNT utility against a non-first piece of a linear table
space resulted in no page printed and ended with RC8 even though
there were non-zero pages in the piece.
This problem occurred because DSN1COPY and DSN1PRNT incorrectly
determined that the first data page was a LOB header page.
DSN1COPY and DSN1PRNT code have been modified to check the input
VSAM data set name to determine if it is a LOB data set when the
LOB keyword is not specified. As a result, when the input data
set is a non-first piece VSAM data set and the LOB keyword is
not specified, DSN1COPY and DSN1PRNT will determine that the
input data set is a non-LOB data set.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31567
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 PI31567
DSN1PRNT PI31567
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31567 DSN1COPY DSN1PRNT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSN1COPY
DSN1PRNT
LISTEND
UI25795 COVER LETTER END
UI25797 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32212 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of DSN1COPY on image copies of a *
* compressed index. *
****************************************************************
* PROBLEM DESCRIPTION: DSN1COPY on an image copy of a *
* compressed index issued MSGDSN1990I *
* and ended with RC8 *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A DSN1COPY was used to copy a full image copy of a compressed
index. Message DSN1990I - DSN1CPIP BROKEN PAGE. PAGE NUMBER =
00000002. REASON: FREE SPACE AVAILABLE INVALID. SERVICE INFO:
CODE= 'D64'X XCALFRSP=nnnn IPFREESP=mmmm was issued. The
DSN1COPY job ended with RC8.
This problem occurred because a local variable was not set
properly.
The DSN1COPY utility code has been modified to correct the
aforementioned problem.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32212
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 PI32212
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32212 DSN1COPY
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN1COPY
LISTEND
UI25797 COVER LETTER END
UI25824 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI34702 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users and DB2 11 for *
* z/OS users of the UNLOAD utility with *
* SPANNED YES. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E40070 DSNUGSDA during a *
* LOAD utility using FORMAT SPANNED YES. *
* The UNLOAD TABLESPACE SPANNED YES *
* utility that created the file did *
* not meet criteria for SPANNED, so *
* the data was not in variable spanned *
* format (VBS). *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
A LOAD utility was expecting the SYSREC file produced
from an UNLOAD TABLESPACE SPANNED YES to be in VBS format. It
did not meet criteria for SPANNED, so it was in variable blocked
format. This resulted in various abends during the LOAD utility
execution.
As documented in the Utility Guide and Reference, the
explanation for SPANNED YES, it states that a field
specification list is required with all LOB and XML columns
specified at the end of the field specification list, with no
length or position specified for those columns.
If a field specification list is not included on an UNLOAD
TABLESPACE SPANNED YES utility statement, the LOAD statement
produced for the SYSPUNCH data set will include a field
specification list with the columns of the table listed in
DDL order, it will not include the FORMAT SPANNED YES keywords
and the data will not be unloaded into a VBS data set in spanned
record format. Using the LOAD statement with SPANNED YES for
this file may cause various utility abends including an
ABEND04E RC00E40070 DSNUGSDA,
RC00C90101 DSNOALLO ERQUAL5022, DSNOALLO ERQUAL2007, RC00E40350
and a RC00C200D8.
UNLOAD utility code was modified to issue MSGDSNU073I
if a field specification list was not included when specifying
UNLOAD SPANNED YES.
DSNU073I - KEYWORD 'SPANNED YES' IGNORED
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34702
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUUUFA PI34702
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34702 DSNUUUFA
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUUUFA
LISTEND
UI25824 COVER LETTER END
UI25835 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28601 -
****************************************************************
* USERS AFFECTED: All users of DB2 Version 10 and *
* DB2 Version 11 for z/OS ODBC/CLI driver *
****************************************************************
* PROBLEM DESCRIPTION: When LIMITEDBLOCKFETCH=1, incorrect *
* data is returned when: *
* 1. fetching from a numeric column into *
* a buffer of C type SQL_C_DECIMAL64 *
* or SQL_C_DECIMAL128. *
* 2. fetching from a DECFLOAT column *
* into a buffer of C type SQL_C_LONG, *
* SQL_C_SHORT, SQL_C_BIGINT, *
* SQL_C_FLOAT, SQL_C_DOUBLE, *
* SQL_C_DECIMAL64, or *
* SQL_C_DECIMAL128. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When LIMITEDBLOCKFETCH=1, incorrect data is returned when
fetching DECFLOAT data as follows:
1. fetching from a DECIMAL, NUMERIC, SMALLINT, INTEGER, REAL,
DOUBLE, FLOAT, or BIGINT column into a buffer of C type
SQL_C_DECIMAL64 or SQL_C_DECIMAL128.
2. fetching from a DECFLOAT(16) or DECFLOAT(34) column into
a buffer of C type SQL_C_LONG, SQL_C_SHORT, SQL_C_BIGINT,
SQL_C_FLOAT, SQL_C_DOUBLE, SQL_C_DECIMAL64, or
SQL_C_DECIMAL128.
The following example illustrates the problem:
1. Set LIMITEDBLOCKFETCH=1 in the INI file.
2. Prepare and execute the following SELECT statement with a
result set column bound with C data type SQL_C_DECIMAL128:
SELECT DECFLOAT('2001.1',34) FROM SYSIBM.SYSDUMMY1
3. Prepare and execute the following SELECT statement with
a WHERE clause containing a parameter marker bound with
C data type SQL_C_DECIMAL128 and SQL type SQL_DECFLOAT
using the column data from previous SELECT:
1 SELECT 1 FROM SYSIBM.SYSDUMMY1
WHERE DECFLOAT('2001.1',34) = ?
4. SQLFetch() returns SQL_NO_DATA_FOUND.
Code has been changed to correctly process DECFLOAT data.
COMPONENT: 5740-XYR02-JDBAA17
APARS FIXED: PI28601
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAOC28 PI28601
DSNAOC27 PI28601
DSNAOG05 PI28601
DSNAOG28 PI28601
DSNAOG27 PI28601
DSNAOCLI PI28601
DSNAOSDK PI28601
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28601 DSNAOC28 DSNAOC27 DSNAOG05 DSNAOG28 DSNAOG27 DSNAOCLI
DSNAOSDK
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAOC28
DSNAOC27
DSNAOG05
DSNAOG28
DSNAOG27
DSNAOCLI
MACROS
DSNAOSDK
LISTEND
UI25835 COVER LETTER END
UI25837 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27821 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users with *
* programs using host variables *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C89011 can occur for *
* a query containing a syntax error *
* involving a host variable *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00C89011 can occur for a query containing a syntax
error involving a host variable. If there is a host
1 variable following a colon that is out of place, the
abend can occur.
For example:
EXEC SQL
CALL P123.PROC1(
:WORK-PARM1 :WORK-HV-IND1 ,
:WORK-PARM2 :WORK-HV-IND2 ,
:WORK-PARM3 :WORK-HV-IND3 ,
:WORK-PARM4 :WORK-HV-IND4 ,
:WORK-PARM5 ) :WORK-HV-IND5
:WORK-HV-IND5 is in the wrong location, and an abend
occurs.
An error message DSNH104I will be issued for the above error
instead of an abend.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI27821
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI31373:
See PI31373 APAR/PTF text for additional information about
why a REBIND is necessary.
PI31373 corrects a problem of SQLCODE -302, when all of
following conditions are satisfied:
1. A host structure and an extended indicator array are defined
in host programming language;
2. one of the fields in the above host structure is defined with
DECIMAL type;
3. both of the above structures are used in an SQL statement;
4. the table referenced in the above SQL statement is a remote
table and locates on a federation server.
To make this fix effective for a static application, it must 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
DSNHNBRM PI27821
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27821 DSNHNBRM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNHNBRM
LISTEND
UI25837 COVER LETTER END
1UI25841 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI35386 -
****************************************************************
* USERS AFFECTED: All users of DB2 for zOS. *
****************************************************************
* PROBLEM DESCRIPTION: MSGDSNJ105I LOG WRITE ERROR with ERROR *
* STATUS=0024030C issued by DSNJW207 *
* attempting to format the last *
* control area of an active log data *
* set that is just less that 4 GB in *
* size. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An active log data set that was just under the maximum size
of 4 GB, was not fully formatted when added to the DB2 log
inventory. DSNJW207 was called to format ahead of the log
writes, and over-flowed a 32 bit variable when calculating
the end of the format range, attempting to format the last
control area in the data set. The end of the range was then
less then the start of the format range, causing the format
request to fail. DSNJW207 then issued the following message:
DSNJ105I DSNJW207 LOG WRITE ERROR
DSNAME=log-data-set-name, LOGRBA=log-rba-value, ERROR
STATUS=0024030C
DB2 then truncated the active log data set and switched to
the next available log data set for this log copy. LISTCAT
output for the truncated log data set will show that the
high used RBA is slightly less than the high allocated RBA.
This error will repeat each time the log data set becomes
the current active log data set.
The format range calculation in DSNJW207 has been corrected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35386
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJW207 PI35386
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35386 DSNJW207
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW207
LISTEND
UI25841 COVER LETTER END
UI25853 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI33994 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of a SQL *
* statement containing SENSITIVE STATIC *
* SCROLL CURSOR and EXISTS or IN predicate *
* with correlated subquery. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC00000038 at location *
* DSNXGRDS DSNXOSCR OFFSET345E or *
* ABEND04E RC00C90101 at location *
* DSNIDM DSNICUBC OFFSET5015 may occur *
* when a SQL statement contains SENSITIVE *
* STATIC SCROLL CURSOR and EXISTS or IN *
* predicate with correlated subquery. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create TABLE T1 and T2.
CREATE TABLE T1 (
C1 VARCHAR(30),
C2 INT
);
CREATE TABLE T2 (
C1 VARCHAR(30),
C2 INT
);
Step 2. statement which may cause ABEND.
EXEC SQL
DECLARE C21 SENSITIVE STATIC SCROLL CURSOR FOR
SELECT T1.C2
FROM T1
WHERE EXISTS (SELECT 1
FROM T2
WHERE T2.C1 = T1.C1 AND T2.C2 IN (5, 6));
DB2 does not process the statement with sensitive static
scrollable cursor properly which may result in the ABEND.
After applying the APAR, access path or performance may be
changed.
DB2 has been modified correctly to process sensitive static
scrollable cursor to avoid the ABEND.
Additional Keywords: SQLSCROLL SQLSENSITIVE SQLEXISTS
SQLSUBQUERY SQLCORRSUBQ SQLINSUBQ
SQLACCESSPATH SQLPERFORMANCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33994
1 SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM95113:
See PM95113 APAR/PTF text for additional information about
why a REBIND is necessary.
PM95113 improves the performance of query that contains a
correlated IN or EXISTS subquery predicate with a field
procedure on the correlated predicate 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 PM67966:
See PM67966 APAR/PTF text for additional information about
why a REBIND is necessary.
PM67966 corrects a problem that can result in an incorrect
result set, more rows than expected, being returned for a query
that contains a correlated subquery for an EXISTS predicate, and
there is a unique index on expression defined on the table that
is referenced in the 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:
***Action for PI33994:
See PI33994 APAR/PTF text for additional information about
why a REBIND is necessary.
PI33994 corrects a problem of ABEND0C4 RC00000038 at location
DSNXGRDS DSNXOSCR OFFSET345E or ABEND04E RC00C90101 at location
DSNIDM DSNICUBC OFFSET5015 when a SQL statement contains
SENSITIVE STATIC SCROLL CURSOR and EXISTS or IN predicate with
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.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOQJ1 PI33994
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33994 DSNXOQJ1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXOQJ1
LISTEND
UI25853 COVER LETTER END
UI25882 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32868 -
****************************************************************
* USERS AFFECTED: All DB2 users of IDENTITY column as *
* index-controlled partitioning key and ZPARM *
* IX_TB_PART_CONV_EXCLUDE is set to YES. *
****************************************************************
* PROBLEM DESCRIPTION: After dropping a partitioning index on *
* an index-controlled partitioned table, *
* LOAD UTILITY to *
* reload data (replace mode) failed *
* with DSNU256I DSNUROFL - INVALID *
* PARTITION SPECIFICATION. *
* *
* REPAIR DBD DIAGNOSE shows the error, *
* *
* DSNU920I DSNUEDRT OBDS DIFFER AT *
* OFFSET X'0000023A' OBDRX2IE *
* DSNU904I DSNUEDRT EXISTING VALUE X'10' *
* DSNU905I DSNUEDRT REBUILT VALUE X'00' *
* DSNU913I DSNUEDDR OBD X'0003' *
* COMPARISON COMPLETE 1 ERRORS WERE FOUND *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When dropping a partitioning index on an index-controlled
partitioned table space, DB2 automatically converts
the index-controlled partitioned table space to a
table-controlled partitioned table space.
If ZPARM IX_TB_PART_CONV_EXCLUDE is set to YES, when converting
from index-controlled partitioning and defining the table's
partitioning key, DB2 excludes any trailing columns in the
partitioning index's index key if no limit key values are
specified for those columns.
If the IDENTITY column is excluded from the partitioning key
column, after dropping such index, an internal control block is
incorrectly set, which results in the above failure.
DB2 has been changed to make sure the internal control block is
correctly set after dropping the index.
ADDITIONAL KEYWORDS: SQLDROP MSGDSNU256I
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32868
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
DSNGDART PI32868
DSNGEPUF PI32868
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32868 DSNGDART DSNGEPUF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDART
DSNGEPUF
LISTEND
UI25882 COVER LETTER END
UI25884 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33532 -
****************************************************************
* USERS AFFECTED: All DB2 users who have index-controlled *
* partitioned table spaces created prior to *
* DB2 V6 *
****************************************************************
* PROBLEM DESCRIPTION: After converting an index-controlled *
* partitioned table space to a *
* table-controlled partitioned table *
* space, the last partition is in REORG *
* pending status. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the conversion from an index-controlled partitioned
table space to a table-controlled partitioned table space,
the last partition may inccorectly be set to REORP when all
of the following conditions are true:
o Subsystem parameter IX_TB_PART_CONV_EXCLUDE is set to YES
o The table space was converted from an index-controlled
partitioned table space to table-controlled partitioned
table space
o Only significant columns of the partitioning index were
used to define the new limit keys.
DB2 code has been changed to access the limit key correctly to
avoid setting the last partition REORG pending.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33532
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 DSNGDART PI33532
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33532 DSNGDART
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDART
LISTEND
UI25884 COVER LETTER END
UI25887 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33698 -
**********************PI28918***********************************
* USERS AFFECTED: All DB2 users who create an index on a *
* Declared Global Temporary Table DGTT. *
****************************************************************
* PROBLEM DESCRIPTION: Customer may hit ABEND RC00C90083 when *
* creating an index on DGTT, *
* if IMAGECOPY OF DBD01 SHRELEVEL CHANGE *
* occurs concurrently. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 blocks creating an index if DBD01 is used by a UTILITY,
since DBD01 is not accessible to update OBD changes.
However if the creating index is on a DGTT, DB2 does not
update the OBD in DBD01.
DB2 code has been changed to not block creating index on DGTT.
Additional Keywords: SQLDGTT
****************************************************************
*************************PI33698********************************
* USERS AFFECTED: AE PI28918 FIX COMPLETION *
****************************************************************
* PROBLEM DESCRIPTION: AE PI28918 FIX COMPLETION *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI28918 FIX COMPLETION
AE PI28918 FIX COMPLETION
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33698
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDCOB PI33698
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33698 DSNGDCOB
1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDCOB
LISTEND
UI25887 COVER LETTER END
UI25891 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34121 -
****************************************************************
* USERS AFFECTED: DB2 zOS v10 and v11 DGTT users. *
****************************************************************
* PROBLEM DESCRIPTION: AE PI24531 fix completion. *
* Abend04E rc00C90101 in DSNIBHUN:500E *
* occurred after a job using DGTT *
* was cancelled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
AE PI24531 fix completion.
After a job is cancelled, DB2 tried to undo the DGTT changes.
During log-apply, a down-levelled page was read from DASD,
which resulted with DSNIBHUN ERQUAL500E error.
AE PI24531 fix completion
For DGTT, these tables are temporary in nature, the data
on these tables would not be kept after task deallocation.
DB2 code is changed to skip page recovery on DGTT pages,
and to bypass log apply on broken DGTT data pages (PGBROKEN).
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34121
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1RTR PI34121
DSNIB PI34121
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34121 DSNB1RTR DSNIB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1RTR
DSNIB
LISTEND
UI25891 COVER LETTER END
UI25894 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI30962 -
****************************************************************
* USERS AFFECTED: DB2 zOS v10 and v11 queries using the *
* ridlist access path. *
****************************************************************
* PROBLEM DESCRIPTION: ABENDS04E RC00C20306 in DSNB1LTX was *
* encountered when running a SQL query *
* that is using a RIDLIST access path. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The error occurred during the query processing, since a page
latch was not held when a page p-lock was requested.
DB2 RIDLIST code is changed to make sure that a page latch
is held before requesting the page p-lock.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30962
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNISFRL PI30962
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30962 DSNISFRL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISFRL
LISTEND
UI25894 COVER LETTER END
UI25905 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32991 -
****************************************************************
* USERS AFFECTED: All DB2 10 AND DB2 11 for z/OS users using *
* indexes. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKINSL *
* ERQUAL5033 was encountered *
* AFTER DB2 RESTART. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During LPAR failure testing, an index manager log record
was not properly written to DASD prior to the failure,
resulting in the following abend after the subsequent DB2
restart:
ABEND04E RC00C90101 DSNKINSL erqual5033
Index manager code was changed to check
1 if proper index page latch is held and the index page is marked
as dirty before a key is inserted into an index leaf page or
deleted from an index leaf page.
Following diagnostic abends could be issued when index manager
code detects missing page latch or page set write error:
Abend04E RC00C90101 DSNKINSL ERQUAL506E
Abend04E RC00C90101 DSNKINSL ERQUAL506F
Abend04E RC00C90101 DSNKDLE ERQUAL506E
Abend04E RC00C90101 DSNKDLE ERQUAL506F
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32991
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKDLE PI32991
DSNKINSL PI32991
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32991 DSNKDLE DSNKINSL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKDLE
DSNKINSL
LISTEND
UI25905 COVER LETTER END
UI25944 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI36900 -
****************************************************************
* USERS AFFECTED: All IFCID 306 users who specifies PSID *
* filtering (WQALWQLF). *
****************************************************************
* PROBLEM DESCRIPTION: IFI READ ABENDS0C4 PIC04 RC04 IN *
* DSNIDLGR OFFSET2F6E WHILE PROCESSING *
* LOG RECORDS FOR COMPRESSED TABLE *
* SPACES. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When PSID selection block is specified (WQALWQLS) in IFCID 306
READS request for compressed log record, it is possible that DB2
read routine while updating log record's header information may
access storage beyond the boundary of the IFI 306 buffer which
results in programming exception error (Abend0C4). This error
condition is timing related. The timing window is possible only
when log read buffer is filled with the requested log records
and there are less than 12 spare bytes remaining in the buffer.
When this timing window is encountered, DB2 read routine tries
to access storage beyond the actual size of the buffer which
1 results in addressability exception in csect DSNIDLGR. When this
error occurs, DB2 will returned resource unavailable reason code
(00E60863), along with the entire IFI 306 buffer with all the
log records successfully read and decompressed, to the caller of
IFCID 306.
DB2 log read logic is modified to avoid accessing storage beyond
the size of IFI 306 buffer that application has supplied.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI36900
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDLGR PI36900
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI36900 DSNIDLGR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDLGR
LISTEND
UI25944 COVER LETTER END
UI25954 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30603 -
****************************************************************
* USERS AFFECTED: All DB2 users of IFC trace facility *
****************************************************************
* PROBLEM DESCRIPTION: DB2 trace facility stops or becomes *
* inactive with IFI RC/RSNC=00000008/ *
* 00E60831 primarily because of X22 or *
* X3E abends. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
IFI RC/RSNC=00000008/00E60831 was introduced to make sure that
a misbehaving DB2 system would shut down the trace facility if
too many abends occur. DB2 has been counting X22 and X3E
abends as part of the threshold, causing the IFC trace
facility to stop operating.
DB2 has been modified to not count X22 and X3E abends as part
of the threshold.
Keywords: ABEND222 ABENDx22 ABEND13E ABENDx3E
RC08 RC00E60831
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30603
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
DSNWAFRR PI30603
DSNWVFRR PI30603
DSNWVZSA PI30603
DSNWVZSS PI30603
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30603 DSNWAFRR DSNWVFRR DSNWVZSA DSNWVZSS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWAFRR
DSNWVFRR
DSNWVZSA
DSNWVZSS
LISTEND
UI25954 COVER LETTER END
UI25960 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31707 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users with *
* queries involving partitioned tables and *
* a table function *
****************************************************************
* PROBLEM DESCRIPTION: DB2 may give incorrect output for a *
* query with a table function when: *
* *
* 1. The table is partitioned with only 1 *
* limit key; or only the leading column *
* of the partitioning key has limits *
* specified; or there is more than one *
* column but the column limit for other *
* columns are always the maximum *
* allowable value for that column. *
* *
* 2. DB2 uses an EQUAL predicate with *
* a table function parameter that limits *
* the partitions for page range access. *
* *
* 3. The Plan Table shows PAGE_RANGE='Y' *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 may give incorrect output for a partitioned table when the
table is partitioned with only 1 limit key and DB2 uses an
EQUAL predicate on a table function parameter to limit the
partitions for page range access.
A sample query looks like this:
1 CREATE FUNCTION T (P1 CHAR(5), P2 DATE)
RETURNS TABLE (R1 INTEGER)
RETURN
SELECT C3
FROM T1
WHERE C1 = P1
AND C2 = P2
Partitioning index on (C1), or (C1,C2) with limit keys on C1
only. And the EQUAL predicate with C1 contains table function
parameter P1. DB2 may give incorrect output in this situation.
When the problem occurs, it might result in incorrect output.
ADDITIONAL KEYWORDS: SQLACCESSPATH PAGERANGE SQLTABLEFUNCTION
SQLINCORROUT SQLINCORR INCORROUT DB2INCORR/K
With this logic corrected, DB2 will give correct output for
queries involving partitioned tables with only 1 limited key
and a table function.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31707
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI31707:
See PI31707 APAR/PTF text for additional information about
why a REBIND is necessary.
PI31707 corrects a problem that DB2 may give incorrect output
for a query with a table function where there is only 1 limited
key on the partition table and there is an equal predicate
between the partition limit key and a table function parameter.
To make this fix effective for a static application, it must 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 PI26227:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI26227 corrects a problem in which incorrect output may be
generated for a query with an IS NULL predicate on a
partitioning column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPG2 PI31707
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI31707 DSNXOPG2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPG2
LISTEND
UI25960 COVER LETTER END
UI25970 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32797 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of the DSNTIJEN *
* ENFM processing job. *
****************************************************************
* PROBLEM DESCRIPTION: Residual data sets from a failed ENFM *
* REORG prevented a resubmit of the *
* DSNTIJEN job from being successful. In *
* these cases the resubmitted DSNTIJEN *
* job fails with an ABEND04E RC00E4031C. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
A DB2 ENFM REORG failed and left new directory object data sets
around that interfered with a later resubmit of the DSNTIJEN
job.
A DSNT500I message in the DSNTIJEN job output will indicate the
name of the residual data set that interfered with the ENFM
process:
DSNT500I DSNUGBAC - RESOURCE UNAVAILABLE
REASON 00D70025
TYPE 00000220
NAME nnnnnnn.DSNDBC.DSNDB01.SYSSPUXA.J0001.A001
The MVS console may also list DSNP009I, DSNP010I, and DSNP027I
messages that also indicate the problem with the residual
data sets.
The specified data set names in these DSNT500I messages are most
likely going to be from one of the new directory objects that
are created during DSNTIJEN steps ENFM0027 and ENFM0037.
The above DSNT500I message example lists a 'J' data set name
but the problem could be because of the 'I' data set for the
object. Both the 'I' and 'J' data sets for these objects must
not exist before the DSNTIJEN job is resubmitted.
If the failure happened during SPT01 DSNTIJEN job step ENFM0027
then ensure there are no 'I' or 'J' data sets for the following
objects: SYSSPUXA, SYSSPUXB, DSNSPDXA, and DSNSPEXA
1 If the failure happened during DBD01 DSNTIJEN job step ENFM0037
then ensure there are no 'I' or 'J' data sets for the following
objects: DSNDB1XA and DSNDB01X
If another data set name appears in a DSNT500I message then IBM
support should be contacted.
Additional keywords: DB2MIGV10/K MSGDSNT500I
RC00D70025 RC00E4031C
MSGDSNP009I MSGDSNP010I
MSGDSNP027I
DB2 code has been changed so that it will clean up the
necessary data sets in the event of a failure in the ENFM
processing of a directory table space.
The residual data sets will only be cleaned up for ENFM
failures that happen after this new APAR code is put on a
subsystem.
The new APAR code will not delete any residual data sets that
might exist from a previous DSNTIJEN ENFM process failure.
These data sets should be cleaned up before the DSNTIJEN job
is resubmitted.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32797
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNURRNM PI32797
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32797 DSNURRNM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNURRNM
LISTEND
UI25970 COVER LETTER END
UI25987 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33337 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of a native SQL *
* procedure or compiled SQL scalar function *
* containing a statement with a SQL variable *
* which references a user defined data type. *
* All DB2 11 for z/OS users of a native SQL *
* procedure or compiled SQL scalar function. *
* *
1 ****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E2000C at location *
* DSNXOYP1 DSNSVSVB OFFSET0B06 may occur *
* when a SQL statement satisfies the *
* following list of conditions: *
* *
* For DB2 10: *
* *
* A native SQL procedure or compiled *
* SQL scalar function contains a *
* statement with a SQL variable which *
* references a user defined data type. *
* *
* For DB2 11: *
* *
* A native SQL procedure or compiled *
* SQL scalar function may cause *
* possible memory leak in general. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following example helps to illustrate the problem.
Step 1. Create objects.
CREATE TABLE T1(
C1 VARCHAR(8),
C2 VARCHAR(2)
)!
Step 2. Statements which may cause ABEND.
For DB2 10 and 11:
Example#1:
CREATE TYPE MYINT AS INTEGER!
CREATE PROCEDURE P1()
BEGIN
DECLARE VAR1 MYINT;
SET VAR1 = 5;
END!
For DB2 11 only:
Example#2:
CREATE VARIABLE VAR2 VARCHAR(8)!
CREATE PROCEDURE P1()
BEGIN
DECLARE VAR1 VARCHAR(8);
SET VAR1 = VAR2;
END!
Example#3:
CREATE PROCEDURE P1()
1 BEGIN
DECLARE VAR1 VARCHAR(8);
SET VAR1 = ( SELECT C1 FROM T1
FETCH FIRST 1 ROWS ONLY);
END !
DB2 does not free storage properly when process column C1
which may result in the ABEND.
The ABEND occurs because DB2 run out of storage since the
storage that are allocated when processing the statement
CREATE PROCEDURE isn't freed.
DB2 has been modified correctly to free storage when
processing a native SQL procedure or compiled SQL scalar
function.
Additional Keywords: SQLSP SQLSTOREDPROC SQLNATIVESQLPL
SQLUDF SQLSTORAGE DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33337
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
PI19842 corrects a problem of ABEND04E RC00E70005 at location
DSNXGRDS DSNXSTRC M777 or other unexpected ABEND0C4 or ABEND04E
or unexpected SQLCODE -104 during rebind when a compiled SQL
scalar function contains a RETURN statement which returns an
expression with special register CURRENT SERVER, CURRENT
PACKAGESET or CURRENT PACKAGE PATH.
After the application of this PTF, ALTER FUNCTION REGENERATE is
required for each SQL scalar function that is affected.
Review the PTF cover letter to determine which, if any, compiled
SQL scalar function could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOYCS PI33337
DSNXOYDA PI33337
DSNXOYIF PI33337
DSNXOYPL PI33337
DSNXOYP0 PI33337
DSNXOYTR PI33337
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33337 DSNXOYCS DSNXOYDA DSNXOYIF DSNXOYPL DSNXOYP0 DSNXOYTR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOYCS
DSNXOYDA
1 DSNXOYIF
DSNXOYPL
DSNXOYP0
DSNXOYTR
LISTEND
UI25987 COVER LETTER END
UI26008 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33932 -
****************************************************************
* USERS AFFECTED: DB2 data sharing users. *
****************************************************************
* PROBLEM DESCRIPTION: Threads hanging while attempting to *
* access an index, or a particular page *
* within the index. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a split is performed on a GBP-dependent index, a "deferred
synchronous write" protocol is used on the pages involved in the
split, in which a list of pages is forced out at a particular
time. The problem is, the pages in this list are tracked at the
data set level, and a split for a non-partitioned index can
involve pages in multiple data sets. When a data set change is
detected while adding a page to the list, DB2 can lose track of
a page, which will remained locked for a write indefinitely.
Any subsequent agent attempting to access such a locked page
will hang. Eventually, DB2 checkpoint processing will kick off
a cleanup routine which will acquire a write drain on the index.
This process will also hang, making the entire index unavailable
for updates.
The "deferred synchronous write" logic for index splits has
been modified to correctly handle non-partitioned indexes with
multiple data sets.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33932
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1ULT PI33932
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33932 DSNB1ULT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1ULT
LISTEND
UI26008 COVER LETTER END
1
UI26012 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34684 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS, and DB2 11 for z/OS *
* utility users with DB2 Sort for z/OS V2R1 *
* and PI19784/UI21041/UI21042 applied. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 utilities using DB2 Sort V2.1 and *
* PTFs UI21041 or UI21042 applied may *
* encounter the following errors: *
* 1. ABEND0C4 RC0000003B DSNSVBK+X'11B0' *
* 2. ABEND04E RC00E40005 DSNUGSOR+X'1C18' *
* 3. MSGCNK998E UNSUCESSFUL SORT 6CC OR *
* 4. ABNDU8ED from DB2 Sort 2.1. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
With PI19784 applied, the following problems may occur
in utility sort processing with DB2 Sort 2.1:
1. Incorrect utility storage management resulting in ABENDS0C4
at DSNSVBK OFFSET11B0
2. Incorrect block level sort parameter information being passed
to DB2 Sort 2.1 resulting in ABENDU8ED
3. MSGCNK998E UNSUCCESSFUL SORT 6CC and/or
4. ABEND04E RC00E40005 at DSNUGSOR OFFSET1C18
The above errors do not occur with DB2 Sort 1.3 or with DB2 Sort
2.1 without the PTFs for PI19784 applied.
Code has been changed to correct the above errors.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34684
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUGALC PI34684
DSNUGSOR PI34684
DSNUGSTA PI34684
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34684 DSNUGALC DSNUGSOR DSNUGSTA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUGALC
DSNUGSOR
DSNUGSTA
LISTEND
UI26012 COVER LETTER END
1
UI26059 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI16259 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS version 10 and version 11 *
* users of compressed table space. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIOST2:5005, *
* ABEND04E RC00C90206 DSNIIDIS:5002 *
* happened after an incomplete *
* dictionary was left in the pageset. *
****************************************************************
* RECOMMENDATION: Load utility modules load a 'dummy' *
* dictionary into the pageset temporarily *
* and then replace it with a valid dictionary *
* within the same LOAD process. Normally *
* the dummy dictionary should never be left *
* in the pageset. Under abnormal *
* circumstances a dummy dictionary may get *
* left in the pageset. *
* *
* In a data sharing environment, if one *
* member, DB2B, accessing the table space had *
* already copied the invalid dictionary to *
* memory at pageset-open time, then another *
* member, DB2A, inserting more rows detects *
* that the dictionary is invalid and therefore *
* builds a new one and inserts compressed *
* rows, and then member DB2B reads the *
* compressed rows, it will run into problems. *
****************************************************************
The possibility of an incomplete LOAD process leaving an
invalid dictionary in the pageset is very rare and has not
happened in the last 2 years.
The Customer's pageset that had the incomplete dictionary
and caused problems was inactive and had a more-than-2-years
old dictionary when the pageset was opened, with no record
of how it got left there.
DB2 code has been modified such that a dictionary that is
marked as incomplete in the pageset will never be copied
to memory at pageset open time on any member.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI16259
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The DB2 10 for z/OS PTF for APAR PM37479 has modified the REORG
utility to use the maximum record length for tables that are
compressed and defined with MAXROWS 1 and the KEEPDICTIONARY
keyword is NOT specified on the utility statement. This change
will usually require additional sort work space for the data
1 sort.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1CPP PI16259
DSNIPPS PI16259
DSNIZLDL PI16259
DSNIZLDR PI16259
DSNUGPSV PI16259
DSNURFIT PI16259
DSNURPDC PI16259
DSNURSWD PI16259
DSNURWBF PI16259
DSNURWI PI16259
DSNURWIR PI16259
DSNURWT PI16259
DSNUZLCR PI16259
DSNXEDT4 PI16259
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI16259 DSNB1CPP DSNIPPS DSNIZLDL DSNIZLDR DSNUGPSV DSNURFIT
DSNURPDC DSNURSWD DSNURWBF DSNURWI DSNURWIR DSNURWT
DSNUZLCR DSNXEDT4
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPP
DSNIPPS
DSNIZLDL
DSNIZLDR
DSNUGPSV
DSNURFIT
DSNURPDC
DSNURSWD
DSNURWBF
DSNURWI
DSNURWIR
DSNURWT
DSNUZLCR
DSNXEDT4
LISTEND
UI26059 COVER LETTER END
UI26106 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33082 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Lost updates when DB2 crashes and *
* restarts following LPL recovery. *
* *
* Corrupted data can result in any of *
* the following symptoms: *
1 * - 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: *
****************************************************************
For a table space or index with a page size of 32K and a CI size
of 4K, it is necessary to acquire the system PITR lock before
performing a DASD write. If the PITR lock request fails, the
pages which were being written will be put into LPL with
message DSNB250E showing a CSECT name of DSNB5COM and a reason
of "LOCK". However, the error handling fails to reset an
"I/O in progress" indication in the page buffer control
block.
Subsequent LPL recovery will drive writes for these pages, but
the writes will be skipped due to the "I/O in progress"
status,
and the pages will remain dirty in the buffer pool. They may
eventually be written out if the page set is physically closed,
but if DB2 crashes and restarts before that happens, the pages
may remain down-level if the log records for the unexternalized
updates are older than the system restart point.
The DASD write logic has been modified to ensure that the page
buffer control blocks are cleaned up properly when the I/O is
skipped due to a failure acquiring the PITR lock.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33082
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1REL PI33082
DSNB5COM PI33082
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33082 DSNB1REL DSNB5COM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1REL
DSNB5COM
LISTEND
UI26106 COVER LETTER END
UI26153 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32232 -
****************************************************************
* USERS AFFECTED: DB2 users. *
1 ****************************************************************
* PROBLEM DESCRIPTION: Broken data in a partitioned table *
* space, caused by using the wrong part's *
* space map page for allocating a new *
* segment. *
* *
* 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: *
****************************************************************
During a table space partition physical close, a cached space
map page number is at one point set to a hard-coded value of 1
(i.e. the first spacemap page in part 1). If the close is able
to complete normally, it will end up being corrected to have
the page number of the first spacemap page of that partition.
However, if the close request was conditional (e.g. for DSMAX),
it may not complete and will leave the incorrect spacemap page
number cached. This can cause broken data later on if it is
used for segment allocation, since a segment that's free in
part 1 may contain data in a different part.
The partition physical close logic has been modified to store
the correct spacemap page number for the partition being closed.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32232
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 PI32232
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32232 DSNB1CPP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CPP
LISTEND
UI26153 COVER LETTER END
UI26201 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34901 -
****************************************************************
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.67.49 is provided by *
* this APAR ( JCCV36749 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V11, DB2 z/OS V10, *
* DB2 z/OS V9 and alternate supplemental *
* driver for DB2 z/OS V8 ( JCCZOSDB2V11, *
* JCCZOSDB2V10, JCCZOSDB2V9, JCCZOSDB2V8) *
* *
* This APAR delivers a new release (3.67) *
* 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:
_______________________________________________________________
Type-4 Connectivity: SQLJ customization on a
3-tier connection fails with ERRORCODE4499(-4499),
after rollback is sent on the connection.
"Execution failed due to a distribution protocol error that
caused deallocation of the conversation A DRDA Data Stream
Syntax Error was detected. Reason: 0x1900. ERRORCODE=-4499,
SQLSTATE=58009".
This problem has been fixed. (RTC 33509)
_______________________________________________________________
Type-4 Connectivity: When JCC driver hits the limit for
seamless retries, SQL20542N will now be thrown instead of
ERRORCODE4228(-4228) .
This problem has been fixed. (RTC 32315)
_______________________________________________________________
Type-4 Connectivity: Due to best member calculation prior
to flowing any query, a member that initially failed for a
query may get picked again during seamless failover, which
is incorrect. This can causes sub-optimal reroute behavior
or seamless failover failures such as SQLCODE20542N in high
frequency.
Note: There are cases where SQLCODE20542N is issued correctly.
This problem has been fixed. (RTC 41553)
_______________________________________________________________
Type-4 Connectivity: In case of reuse JCC closes all the open
statements, which can cause start of a new transaction on the
1 server. This results in the connection unfit to be reused and
possible occurrence of Conversational Protocol Error
exception: "Execution failed due to a distribution protocol
error that caused deallocation of the conversation. A DRDA
Conversational Protocol Error was detected.
Reason: 0x1245. ERRORCODE=-4499, SQLSTATE=58009"
This problem has been fixed. (RTC 25374)
_______________________________________________________________
Type-4 Connectivity: A batch update may fail with
SQLCODE302 (-302) and SqlState=22001 if it's using
setDBStringAsByte to set Unicode text and the first row of the
same batch had null for the same column.
This problem has been fixed. (RTC 31674)
______________________________________________________________
Type-4 XA Connectivity: Driver does not close a non-XA
transaction (with autocommit on) in case of an exception in
execution. After the exception, the transaction remains open
causing the next XA start to fail. A symptom of this issue is a
global transaction failing to start with XA Exception
"XAER_OUTSIDE ERRORCODE=-4228", ERRORCODE4228(-4228)
immediately after a local transaction has completed on the XA
connection with autocommit on.
This problem has been fixed. (RTC 28121)
_______________________________________________________________
Type-4 Connectivity: The driver frees a transport on
receiving a RLSCONV REUSE reply for a COMMIT request even
when there is a new UOW chained to the COMMIT. The
symptoms in an application would indicate loss of session
data or other failures that can be associated with the
transport having been switched in the middle of a UOW.
This problem has been fixed. (RTC 45936)
_______________________________________________________________
Type-4 Connectivity: During XA transaction,
connection processing may hang due to a server outage
preventing failover to an available alternate DB2 members to
succeed. In a WebSphere environment, the condition is
marked by WebSphere warning messages, that indicate threads
have been hung for a long time. The thread stack
traces show the thread is waiting in a socket read call.
Socket read is a common driver activity so an
XA Connection and a coinciding server failure are
necessary to be present simultaneously to indicate this
error condition.
This problem has been fixed. (RTC 39487)
_______________________________________________________________
Type-4 Connectivity: Subsequent to a failover, in a client
reroute environment, the client info special registers
sometimes do not get replayed on the rerouted connection.
This problem has been fixed. (RTC 33125)
_______________________________________________________________
Type-4 Connectivity: JCC driver throws a SQLCODE799(+799)
warning when client info values set using the generic
special register. Example as below:
prop.put ("specialRegisters","CURRENT
CLIENT_APPLNAME=testApp")
DriverManager.getConnection(url,prop)
This problem has been fixed. (RTC 35263)
1 _______________________________________________________________
Type-4 Connectivity: When the JCC driver is connected to a data
sharing group and carrying out an
automatic client reroute, there are situations when the
creation of a TCP/IP socket to a member of the data
sharing group succeeds, but subsequent flows fail. The
driver may not handle such errors correctly and cause
reroute not to succeed or incorrectly throws a SQLCODE30108N
when a reroute may not actually have succeeded.
This problem has been fixed. (RTC 31222)
_______________________________________________________________
Type-4 Connectivity:
getJccSpecialRegisterProperties method call
from JCC fails with SQLCODE4700(-4700) error.
This is due to JCC trying to get the value of
CLIENT_CORR_TOKEN special register which is
absent in DB2 V11 CM or lower. JCC should avoid sending
request to get the value of CLIENT_CORR_TOKEN in these cases.
This problem has been fixed.(RTC 47261)
_______________________________________________________________
Type-4 Connectivity:
During a XA transaction if the first SQL fails with
SQLCODE204(-204) or SQLCODE727(-727) then the subsequent
attempt to prepare a select query on a second
table will fail with following exception.
"Error executing XAResource.start(). Server returned
XAER_PROTO. ERRORCODE=-4203, SQLSTATE=null"
SQLCODE204(-204) or SQLCODE727(-727) errors will not prevent
transaction from starting.
This problem has been fixed. (RTC 39374)
_______________________________________________________________
All Connectivities: Support a new value
DB2BaseDataSource.CONNECTION_CLOSE_WITH_COMMIT (3) for
"connectionCloseWithInFlightTransaction" driver property.
This value allows an application to indicate that if a
connection is closed in the middle of a transaction and
autoCommit disabled, then any uncommitted operations should
be implicitly committed before closing the connection. No
exception is raised to the application.
(RTC 47251)
_______________________________________________________________
Type 4 Connectivity: Enhancement to support commandTimeout
on ResultSet and DatabaseMetaData operations. With this
enhancement, any configured commandTimeout value should apply
to ResultSet and DatabaseMetaData operations such as
ResultSet.next() and DataBaseMetadata.getCatalogs().
(RTC 31075)
_______________________________________________________________
All Connectivities: The driver throws SQLException with
ERRORCODE4463(-4463), SQLSTATE=4261,
"Error parsing <Data Type> literal value starting at index
<index>. Error Detail: Invalid character '^M' found in
<Data Type> literal. Full SQL statement
text=<statement text> ERRORCODE=-4463, SQLSTATE=42601",
when a CALL statement is constructed with embedded CR-LF
between parameters as below:
1 CALL CALL_FUNCTION_NAME(PARAM1,PARAM2,<CR-LF>
PARAM3,PARAM4)
This defect has been fixed.
(RTC 37914)
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: PI34901
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 PI34901
DSNAQJBB PI34901
DSNAQJB1 PI34901
DSNAQJB2 PI34901
DSNAQJB3 PI34901
DSNAQJB4 PI34901
DSNAQJB5 PI34901
DSNAQJB6 PI34901
DSNAQJB7 PI34901
DSNAQJB8 PI34901
DSNAQJC1 PI34901
DSNAQJC2 PI34901
DSNAQJC3 PI34901
DSNAQJC4 PI34901
DSNAQJRM PI34901
DSNAQJS1 PI34901
DSNAQJS2 PI34901
DSNAQ3CA PI34901
DSNAQ3CC PI34901
DSNAQ3CE PI34901
DSNAQ3CF PI34901
DSNAQ3CM PI34901
DSNAQ3C0 PI34901
DSNAQ3C1 PI34901
DSNAQ3C2 PI34901
DSNAQ3C3 PI34901
DSNAQ3C4 PI34901
1 DSNAQ3C5 PI34901
DSNAQ3C6 PI34901
DSNAQ3C7 PI34901
DSNAQ3C8 PI34901
DSNAQ3C9 PI34901
DSNAQ3E1 PI34901
DSNAQ6CC PI34901
DSNAQ6CE PI34901
DSNAQ6CF PI34901
DSNAQ6CM PI34901
DSNAQ6C0 PI34901
DSNAQ6C1 PI34901
DSNAQ6C2 PI34901
DSNAQ6C3 PI34901
DSNAQ6C4 PI34901
DSNAQ6C5 PI34901
DSNAQ6C6 PI34901
DSNAQ6C7 PI34901
DSNAQ6C9 PI34901
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34901 DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4
DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2
DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3CA
DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1
DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7
DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ6CC DSNAQ6CE DSNAQ6CF
DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4
DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAQ3CA
DSNAQ3CC
DSNAQ3CE
DSNAQ3CF
DSNAQ3CM
DSNAQ3C0
DSNAQ3C1
DSNAQ3C2
DSNAQ3C3
DSNAQ3C4
DSNAQ3C5
DSNAQ3C6
DSNAQ3C7
DSNAQ3C8
DSNAQ3C9
DSNAQ6CC
DSNAQ6CE
DSNAQ6CF
DSNAQ6CM
DSNAQ6C0
DSNAQ6C1
DSNAQ6C2
DSNAQ6C3
1 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
UI26201 COVER LETTER END
UI26208 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34903 -
****************************************************************
* USERS AFFECTED: All Users of the IBM Data *
* Server Driver for JDBC and SQLJ *
****************************************************************
* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and *
* SQLJ version 4.17.55 is provided by *
* this APAR ( JCCV41755 ) *
* *
* This APAR is applicable to IBM Data *
* Sever Driver for JDBC and SQLJ *
* for DB2 z/OS V11, DB2 z/OS V10 and *
* DB2 z/OS V9( JCCZOSDB2V11, *
* JCCZOSDB2V10, JCCZOSDB2V9 ) *
* *
* This APAR delivers a new release (4.17) *
* 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: *
1 ****************************************************************
JCC sub-category keywords:
JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ
The following changes are delivered in this APAR:
_______________________________________________________________
Type-4 Connectivity: SQLJ customization on a
3-tier connection fails with ERRORCODE4499(-4499),
after rollback is sent on the connection.
"Execution failed due to a distribution protocol error that
caused deallocation of the conversation A DRDA Data Stream
Syntax Error was detected. Reason: 0x1900. ERRORCODE=-4499,
SQLSTATE=58009".
This problem has been fixed. (RTC 33509)
_______________________________________________________________
Type-4 Connectivity: When JCC driver hits the limit for
seamless retries, SQL20542N will now be thrown instead of
ERRORCODE4228(-4228) .
This problem has been fixed. (RTC 32315)
_______________________________________________________________
Type-4 Connectivity: Due to best member calculation prior
to flowing any query, a member that initially failed for a
query may get picked again during seamless failover, which
is incorrect. This can causes sub-optimal reroute behavior
or seamless failover failures such as SQLCODE20542N in high
frequency.
Note: There are cases where SQLCODE20542N is issued correctly.
This problem has been fixed. (RTC 41553)
_______________________________________________________________
Type-4 Connectivity: In case of reuse JCC closes all the open
statements, which can cause start of a new transaction on the
server. This results in the connection unfit to be reused and
possible occurrence of Conversational Protocol Error
exception: "Execution failed due to a distribution protocol
error that caused deallocation of the conversation. A DRDA
Conversational Protocol Error was detected.
Reason: 0x1245. ERRORCODE=-4499, SQLSTATE=58009"
This problem has been fixed. (RTC 25374)
_______________________________________________________________
Type-4 Connectivity: A batch update may fail with
SQLCODE302 (-302) and SqlState=22001 if it's using
setDBStringAsByte to set Unicode text and the first row of the
same batch had null for the same column.
This problem has been fixed. (RTC 31674)
______________________________________________________________
Type-4 XA Connectivity: Driver does not close a non-XA
transaction (with autocommit on) in case of an exception in
execution. After the exception, the transaction remains open
causing the next XA start to fail. A symptom of this issue is a
global transaction failing to start with XA Exception
"XAER_OUTSIDE ERRORCODE=-4228", ERRORCODE4228(-4228)
immediately after a local transaction has completed on the XA
connection with autocommit on.
This problem has been fixed. (RTC 28121)
_______________________________________________________________
Type-4 Connectivity: The driver frees a transport on
1 receiving a RLSCONV REUSE reply for a COMMIT request even
when there is a new UOW chained to the COMMIT. The
symptoms in an application would indicate loss of session
data or other failures that can be associated with the
transport having been switched in the middle of a UOW.
This problem has been fixed. (RTC 45936)
_______________________________________________________________
Type-4 Connectivity: During XA transaction,
connection processing may hang due to a server outage
preventing failover to an available alternate DB2 members to
succeed. In a WebSphere environment, the condition is
marked by WebSphere warning messages, that indicate threads
have been hung for a long time. The thread stack
traces show the thread is waiting in a socket read call.
Socket read is a common driver activity so an
XA Connection and a coinciding server failure are
necessary to be present simultaneously to indicate this
error condition.
This problem has been fixed. (RTC 39487)
_______________________________________________________________
Type-4 Connectivity: Subsequent to a failover, in a client
reroute environment, the client info special registers
sometimes do not get replayed on the rerouted connection.
This problem has been fixed. (RTC 33125)
_______________________________________________________________
Type-4 Connectivity: JCC driver throws a SQLCODE799(+799)
warning when client info values set using the generic
special register. Example as below:
prop.put ("specialRegisters","CURRENT
CLIENT_APPLNAME=testApp")
DriverManager.getConnection(url,prop)
This problem has been fixed. (RTC 35263)
_______________________________________________________________
Type-4 Connectivity: When the JCC driver is connected to a data
sharing group and carrying out an
automatic client reroute, there are situations when the
creation of a TCP/IP socket to a member of the data
sharing group succeeds, but subsequent flows fail. The
driver may not handle such errors correctly and cause
reroute not to succeed or incorrectly throws a SQLCODE30108N
when a reroute may not actually have succeeded.
This problem has been fixed. (RTC 31222)
_______________________________________________________________
Type-4 Connectivity:
getJccSpecialRegisterProperties method call
from JCC fails with SQLCODE4700(-4700) error.
This is due to JCC trying to get the value of
CLIENT_CORR_TOKEN special register which is
absent in DB2 V11 CM or lower. JCC should avoid sending
request to get the value of CLIENT_CORR_TOKEN in these cases.
This problem has been fixed.(RTC 47261)
_______________________________________________________________
Type-4 Connectivity:
During a XA transaction if the first SQL fails with
SQLCODE204(-204) or SQLCODE727(-727) then the subsequent
attempt to prepare a select query on a second
table will fail with following exception.
1 "Error executing XAResource.start(). Server returned
XAER_PROTO. ERRORCODE=-4203, SQLSTATE=null"
SQLCODE204(-204) or SQLCODE727(-727) errors will not prevent
transaction from starting.
This problem has been fixed. (RTC 39374)
_______________________________________________________________
All Connectivities: Support a new value
DB2BaseDataSource.CONNECTION_CLOSE_WITH_COMMIT (3) for
"connectionCloseWithInFlightTransaction" driver property.
This value allows an application to indicate that if a
connection is closed in the middle of a transaction and
autoCommit disabled, then any uncommitted operations should
be implicitly committed before closing the connection. No
exception is raised to the application.
(RTC 47251)
_______________________________________________________________
Type 4 Connectivity: Enhancement to support commandTimeout
on ResultSet and DatabaseMetaData operations. With this
enhancement, any configured commandTimeout value should apply
to ResultSet and DatabaseMetaData operations such as
ResultSet.next() and DataBaseMetadata.getCatalogs().
(RTC 31075)
_______________________________________________________________
All Connectivities: The driver throws SQLException with
ERRORCODE4463(-4463), SQLSTATE=4261,
"Error parsing <Data Type> literal value starting at index
<index>. Error Detail: Invalid character '^M' found in
<Data Type> literal. Full SQL statement
text=<statement text> ERRORCODE=-4463, SQLSTATE=42601",
when a CALL statement is constructed with embedded CR-LF
between parameters as below:
CALL CALL_FUNCTION_NAME(PARAM1,PARAM2,<CR-LF>
PARAM3,PARAM4)
This defect has been fixed.
(RTC 37914)
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: PI34903
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
1 further information about this problem. Reference entry
with (wsdbu01043533) identifier.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNAJJC1 PI34903
DSNAJJC2 PI34903
DSNAJ3CC PI34903
DSNAJ3CE PI34903
DSNAJ3CF PI34903
DSNAJ3CM PI34903
DSNAJ3C0 PI34903
DSNAJ3C1 PI34903
DSNAJ3C2 PI34903
DSNAJ3C3 PI34903
DSNAJ3C4 PI34903
DSNAJ3C5 PI34903
DSNAJ3C6 PI34903
DSNAJ3C7 PI34903
DSNAJ3C9 PI34903
DSNAJ6CC PI34903
DSNAJ6CE PI34903
DSNAJ6CF PI34903
DSNAJ6CM PI34903
DSNAJ6C0 PI34903
DSNAJ6C1 PI34903
DSNAJ6C2 PI34903
DSNAJ6C3 PI34903
DSNAJ6C4 PI34903
DSNAJ6C5 PI34903
DSNAJ6C6 PI34903
DSNAJ6C7 PI34903
DSNAJ6C9 PI34903
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34903 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
1 DSNAJ6CC
DSNAJ6CE
DSNAJ6CF
DSNAJ6CM
DSNAJ6C0
DSNAJ6C1
DSNAJ6C2
DSNAJ6C3
DSNAJ6C4
DSNAJ6C5
DSNAJ6C6
DSNAJ6C7
DSNAJ6C9
MACROS
DSNAJJC1
DSNAJJC2
LISTEND
UI26208 COVER LETTER END
UI26240 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34186 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users and DB2 11 for *
* z/OS users of queries with LIKE predicate *
* on UNICODE column. *
****************************************************************
* PROBLEM DESCRIPTION: Poor performance for a query with *
* predicate column LIKE 'l%'" (lower case *
* L) when the column is defined as an *
* UNICODE column. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Poor performance for a query with predicate column LIKE 'l%'"
(lower case L) when the column is defined as an UNICODE column.
An example of the error is shown below:
create index i1 on T1(c1);
C1 is a unicode column
select * from T1
where c1 like 'l%';
The bindtime code in DB2 is modified to correct the conditions
leading to the poor performance.
Additional Keywords: SQLLIKE SQLINDEX SQLWHERE SQLPERFORMANCE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34186
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1 DB2BIND:
See Pi34186 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
APAR Pi34186 corrects a problem that can cause poor performance
for query contains LIKE predicate on unicode 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
DSNXOBM PI34186
DSNXOIXP PI34186
DSNXORGL PI34186
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34186 DSNXOBM DSNXOIXP DSNXORGL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOBM
DSNXOIXP
DSNXORGL
LISTEND
UI26240 COVER LETTER END
UI26243 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30220 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of *
* INSTEAD OF trigger on a view having *
* DECFLOAT column with user defined default *
* value *
****************************************************************
* PROBLEM DESCRIPTION: REPAIR DBD DIAGNOSE reports error with *
* the OBD of the view on which an *
* INSTEAD OF trigger was created *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For a view that has DECFLOAT column with user defined default
value, the creation of INSTEAD OF trigger on it incorrectly
handles the user defined value and results in incorrect
internal default value stored in the OBD. These are known
and possible symptoms:
o The subsequent REPAIR DBD DIAGNOSE might report
inconsistencies between the existing OBD and rebuilt OBD.
o The incorrect default value stored in OBD may be used when
the INSTEAD OF trigger is activated.
1 o There may be other unpredictable symptoms.
DB2 has been modified to correctly handle INSTEAD OF trigger
on view having DECFLOAT column with user defined default value.
Applying the fix does not correct existing broken objects but
it helps to correctly identify them.
After applying this fix, the following can be done to fix the
broken objects:
o Run REPAIR DBD DIAGNOSE
- Obtain the OBID 'xxxx', DBID 'yyyy' of OBD that has
incorrect information
- Run the following query to determine the name of the
INSTEAD OF triggers defined on the view
SELECT A.NAME
FROM SYSIBM.SYSTRIGGERS A,
SYSIBM.SYSTABLES B
WHERE A.TBNAME = B.NAME AND
A.TBOWNER = B.CREATOR AND
B.TYPE = 'V' AND
B.OBID = xxxx AND
B.DBID = yyyy
o Drop and recreate all INSTEAD OF triggers defined on the view
Additional Keywords
SQLCREATE
SQLVIEW
SQLTRIGGER
SQLDECFLOAT
SQLINCORR
SQLINCORROUT
DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30220
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
PM95281 introduces the following changes to externals:
Changed messages or codes:
For SQLCODE -20523, the following explanation is updated
under reason code 1:
Explanation: ....
1 The table must not be any of the following tables:
* System-period temporal table. The table was defined as
a system-period temporal table by a previous statement,
or the current statement defines the table as a system
period temporal table.
1 Changed option for SQL statement ALTER TABLE:
Under ALTER TABLE USE HISTORY TABLE history-table-name,
the following restriction is updated:
...
history-table name must identify a table that exists at
the current server and must not identify one of the
following tables:
...
- a system-period temporal table. The table was defined
as a system-period temporal table by a previous
statement, or the current statement defines the table
as a system-period temporal table (SQLSTATE 428HX,
SQLCODE -20523 with reason code 1).
ACTION:
This PTF corrected a problem where DB2 did not restrict the
use of versioning table properly. This allowed invalid
tables to be used as the history table. Applying the PTF
however does not fix existing problems and user will need to
take the following action to correct the problem on their
system.
Please use a query to identify any tables that use themselves
as their own history table. The following is a sample
query:
SELECT CREATOR, NAME, TYPE, DBNAME,
TSNAME, DBID, OBID, COLCOUNT,
CREATEDTS, ALTEREDTS, RELCREATED,
VERSIONING_SCHEMA,
VERSIONING_TABLE
FROM SYSIBM.SYSTABLES
WHERE CREATOR = VERSIONING_SCHEMA
AND NAME = VERSIONING_TABLE;
After the tables are identified, please run an ALTER TABLE
DROP VERSIONING statement on each of the tables to correct
the self referencing problem. However the data of the
affected tables can still be down level and incorrect. User
will need to examine the data to see if any other correction
is necessary.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISB5 PI30220
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30220 DSNXISB5
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISB5
LISTEND
UI26243 COVER LETTER END
1UI26268 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32630 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users *
* use IFCID 0020 or 0218 and have *
* UI23652,UI23854,UI23651 or UI23853 *
* applied. *
****************************************************************
* PROBLEM DESCRIPTION: With UI23652, UI23854, UI23651 or *
* UI23853 applied, DB2 users with trace *
* record size for IFCID 0020 or IFCID *
* 0218 greater than 5000 bytes may *
* experience following abend : *
* ABND=0E0-00000028 at DSNWVCOL+10DA *
* ABND=0C4-00000038 at DSNWVCOL+0D82 *
* ABND=0E0-00000028 at DSNWVCOL+0D72 *
* ABND=0C4-00000038 at DSNWVCOL+01FC *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For trace record size greater then 5000 bytes, DB2 didn't
properly initialize the internal trace control block during
IFCID 0020 & 0218 processing. This caused the ABND=0E0-00000028
or ABND=0C4-00000038.
Fixes made in DB2 to properly initialize the internal trace
control block for IFCID 0020 & 0218 processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32630
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNICMT2 PI32630
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32630 DSNICMT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNICMT2
LISTEND
UI26268 COVER LETTER END
UI26294 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI37089 -
****************************************************************
* USERS AFFECTED: All users of RESTORE SYSTEM Utility *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 LOC=DSNIDM.DSNIBMDP+02EC *
* during RESTORE SYSTEM log apply phase. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
During RESTORE SYSTEM log apply open the data set request failed
because the storage pool reached it's maximum limit (2G). This
happens only when RESTORE SYSTEM is interrupted by cancelling
DB2 subsystem where RESTORE SYSTEM is running. When DB2
subsystem
is restarted it does use the ACOMPH20 to build the information
about each objects it processed. However, at the end of restart,
it does not clean up the storage for those objects, results in
shortage of storage when the RESTORE SYSTEM utility is
restarted. To avoid future storage shortage, Data Manager (DM)
end of SYSPITR (System Level Point-in-time recovery) restart
logic will make sure to free all the storage acquired during
restart.
RESTORE SYSTEM log apply logic is modified to avoid future
storage shortage by freeing up acquired storage during DB2
subsystem restart.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI37089
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 PI37089
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI37089 DSNIERST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIERST
LISTEND
UI26294 COVER LETTER END
UI26306 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI24284 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users who use IBM DB2 *
* Analytics Accelerator. *
* Specifically where: *
* - the (DSNTIPR) DDF THREADS (DSN6FAC *
* CMTSTAT) subsystem parameter is set to *
* INACTIVE, and *
* - remote (distributed) client applications *
* execute SQL that gets offloaded to an *
* accelerator. *
****************************************************************
* PROBLEM DESCRIPTION: More concurrent active DBATs are *
* required when distributed client *
1 * requests access an accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When DB2 is configured with the (DSNTIPR) DDF THREADS (DSN6FAC
CMTSTAT) subsystems parameter set to INACTIVE, a distributed
server thread (DBAT) is pooled at the end of a transaction so
that the DBAT will be available to service requests from other
remote client connections.
However, when a distributed client's requests lead to an
accelerator being accessed, the DBAT is prevented from being
pooled even if an active offloaded query no longer exists.
This leads to a higher number of concurrent active DBATS.
DB2 has been changed to allow the pooling of DBATs when an
accelerator is no longer being utilized.
Note: Standard pooling/inactivation rules still apply.
For example, open WITH HOLD cursors, including
offloaded queries, and KeepDynamic packages will still
prevent pooling.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI24284
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PI29102 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29102 corrects a problem for SQL query acceleration where
the query to be offloaded is a self-referencing INSERT with
sub-select.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
ACTION:
*** Action for PI10774 ***
Users should be aware that there MAY be operational issues as
a result of this change because more remote application
environments will have to stay active, after rollback
processing, IF the application executes SQL that can be
off-loaded to an accelerator.
Basically, the operational impact of this change occurs as a
result of requiring an increased number of DB2 threads (DBATs)
and remote client system network connections (to the DB2
server) in order to service the same amount of remote
application work.
Possible symptoms may include:
. Increased storage utilization symptoms due to additional
threads (DBATs) that may now be required.
. Performance degradation, perhaps due to the queuing that may
occur as a result of reaching or approaching the MAXDBAT
1 resource limit.
. High rate of unexpected "Idle Thread Time-out" conditions
(message DSNL030I with reason code 00D3003B) that may result
in unexpected remote application failures.
. Remote client "connection concentrator" environments may
also
be adversely affected as a result of their inability to pool
connections on a transaction (rollback) boundary.
Any potential exposure to these symptoms only occurs with
respect to remote applications that access DB2, as a server,
and then utilize an accelerator AND issue rollback. The
rollback has an effect even if it is executed after accelerator
access is complete. Since exposure is based on the execution
of a rollback, which is not typical, it is unlikely that users
will be affected, but it is possible.
After applying this change, users should monitor their system
for these symptoms. The symptoms may be normal under the
circumstances and measures may be necessary to address the
condition.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLCDG1 PI24284
DSNLCDP1 PI24284
DSNLCITR PI24284
DSNLCMBE PI24284
DSNLCSRR PI24284
DSNLDALB PI24284
DSNLIAAC PI24284
DSNLIRCA PI24284
DSNLISDA PI24284
DSNLQINA PI24284
DSNLTGBK PI24284
DSNLTSET PI24284
DSNLXCMT PI24284
DSNLXCQH PI24284
DSNLXMRF PI24284
DSNLXPCA PI24284
DSNLXRBF PI24284
DSNLXRCN PI24284
DSNLXREL PI24284
DSNLXRFT PI24284
DSNLXROP PI24284
DSNLZMON PI24284
DSNTABA PI24284
DSNTADL PI24284
DSNVDTA PI24284
DSNWVZSA PI24284
DSNXONZA PI24284
DSNXONZB PI24284
DSNX8API PI24284
DSNX8CDA PI24284
DSNX8CLN PI24284
DSNX8EPL PI24284
DSNX8SMF PI24284
DSNX8STA PI24284
DSNX8STO PI24284
DSNX8WAC PI24284
1 HDBAA10J PI24284
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI24284 DSNLCDG1 DSNLCDP1 DSNLCITR DSNLCMBE DSNLCSRR DSNLDALB
DSNLIAAC DSNLIRCA DSNLISDA DSNLQINA DSNLTGBK DSNLTSET
DSNLXCMT DSNLXCQH DSNLXMRF DSNLXPCA DSNLXRBF DSNLXRCN
DSNLXREL DSNLXRFT DSNLXROP DSNLZMON DSNTABA DSNTADL
DSNVDTA DSNWVZSA DSNXONZA DSNXONZB DSNX8API DSNX8CDA
DSNX8CLN DSNX8EPL DSNX8SMF DSNX8STA DSNX8STO DSNX8WAC
HDBAA10J
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLCDG1
DSNLCDP1
DSNLCITR
DSNLCMBE
DSNLCSRR
DSNLDALB
DSNLIAAC
DSNLIRCA
DSNLISDA
DSNLQINA
DSNLTGBK
DSNLTSET
DSNLXCMT
DSNLXCQH
DSNLXMRF
DSNLXPCA
DSNLXRBF
DSNLXRCN
DSNLXREL
DSNLXRFT
DSNLXROP
DSNLZMON
DSNTABA
DSNTADL
DSNVDTA
DSNWVZSA
DSNXONZA
DSNXONZB
DSNX8API
DSNX8CDA
DSNX8CLN
DSNX8EPL
DSNX8SMF
DSNX8STA
DSNX8STO
DSNX8WAC
LISTEND
UI26306 COVER LETTER END
UI26326 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI35913 -
****************************************************************
* USERS AFFECTED: DB2 users. *
****************************************************************
* PROBLEM DESCRIPTION: Delays when extending a DB2-managed *
* table space or index to an additional *
* volume. Wait time is accumulated under *
* "EXT/DEL/DEF" service task wait.
*
* *
* While the agent driving the extend is *
* suspended, other agents trying to *
* access the same table space or index *
* may suffer lock timeouts (for example, *
* on the extend lock). *
* *
* Keywords: PERFM DB2HANG SQLPERFORMANCE *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When extending a table space or index to an additional volume,
it is necessary to reopen the VSAM data set one or more times.
This is followed by a close of the old DDNAME. Before this
close is done, the reopen logic waits for any in-progress DASD
I/Os to complete, since they may have been initiated using the
old DDNAME. If the close is done while such I/Os are in
progress, various failures (abends in Media Manager, pages put
into LPL, DB2 crashing) could result.
In some cases, the I/O waits can take an extended amount of
time, for example if an agent performing an I/O is not getting
dispatched, or if it was canceled and hasn't yet gone through
the abort process. Long waits are more likely in data sharing
since it is necessary to wait for active castout engines, and
a castout engine may be doing a long series of writes - which
can potentially take several minutes.
The data set reopen logic, used during an extend to another
volume, has been modified such that it no longer waits for DASD
I/Os to complete before closing the old DDNAME (the close of the
old DDNAME is not critical to the extend process, and only needs
to be done when the table space or index is physically closed).
Instead, the old DDNAME will now be tracked for a later close,
which may be done by the system pseudo-close processor after
several minutes have gone by, or during physical close.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35913
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
1 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
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
1 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
DSNB1CST PI35913
DSNB1OST PI35913
DSNB1PCP PI35913
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35913 DSNB1CST DSNB1OST DSNB1PCP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1CST
DSNB1OST
DSNB1PCP
LISTEND
UI26326 COVER LETTER END
UI26352 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33409 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of REVOKE *
* statement and materialized query table (MQT) *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC0000003A at DSNXIDTB *
* offsetD3E0 may occur when a user issues *
* a REVOKE statement and the revoked *
* authorization id privilege is used to *
* create a materialized query table (MQT) *
* with AUDIT option. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 RC0000003A at DSNXIDTB offsetD3E0 may occur when a
user issues a REVOKE statement and the revoked authorization id
privilege is used to create a materialized query table (MQT)
with AUDIT option. This may also occur for the MQT table with
security label and if audit trace is on for that MQT table.
Another possible symptom is the IFCID 142 trace record field
1 QW0142TX statement text may contain garbage.
When DB2 revokes an authorization id privilege, an object might
be dropped if a privilege is revoked that was used to create the
object. And DB2 did not process the internal DROP MQT table
correctly.
Following is an example of such failing scenario:
1. Grant a privilege to a user:
GRANT SYSADM TO USRT002;
2. The grantee creates a MQT table with AUDIT option:
CREATE TABLE MQTSYSTABLES AS (
SELECT TX.*
FROM SYSIBM.SYSTABLES TX
WHERE TX.OBID > 3
)
DATA INITIALLY DEFERRED REFRESH DEFERRED
DISABLE QUERY OPTIMIZATION
AUDIT CHANGES;
3. Refresh MQT table:
REFRESH TABLE MQTSYSTABLES;
4. Revoke the grantee privilege:
REVOKE SYSADM FROM USRT002 ;
DB2 has been modified to process the internal DROP process
correctly.
Additional Keywords: SQLMQT SQLREVOKE IFCID142
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33409
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQW02 PI33409
DSNWMSGS PI33409
DSNXA11 PI33409
DSNXIDTB PI33409
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33409 DSNDQW02 DSNWMSGS DSNXA11 DSNXIDTB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXA11
DSNXIDTB
MACROS
DSNDQW02
DSNWMSGS
1 LISTEND
UI26352 COVER LETTER END
UI26382 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30859 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: Additional functions are added for a *
* query optimization serviceability *
* feature for restricted use for query *
* acceleration. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Additional functions are added for a query optimization
serviceability feature for restricted use for query
acceleration.
Contact IBM Support to determine if this serviceability
feature should be used.
For static SQL queries that have been bound for acceleration
and will use the new function above, after applying
this PTF, REBIND the package.
Additional keywords:
IDAAV4R1/K CTEHINT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30859
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI35715:
PI35715 corrects a problem that incorrect output, ABEND04E
RC00E70005 at the location DSNXGRDS DSNXGMVE M628, or other
unexpected problems could happen when rebinding a native SQL
procedure with the option WITH EXPLAIN and EXPLAIN tables in
older format.
To make this fix effective, the package of the native SQL
procedure, which has been rebound with the option WITH EXPLAIN
and EXPLAIN tables in older format, must be rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, native SQL procedure could be affected
by this change.
DB2BIND:
***Action for PI30859:
See PI30859 APAR/PTF text for additional information about
1 why a REBIND is necessary.
PI30859 enables new function for execution on an
accelerator.
To make this new function effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLXRSQ PI30859
DSNLZOSR PI30859
DSNXEDP PI30859
DSNXEDSC PI30859
DSNXEDS1 PI30859
DSNXEPM PI30859
DSNXEPP PI30859
DSNXERT2 PI30859
DSNXOD3 PI30859
DSNXONZO PI30859
DSNXOOP PI30859
DSNXOVD PI30859
DSNXOV0 PI30859
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30859 DSNLXRSQ DSNLZOSR DSNXEDP DSNXEDSC DSNXEDS1 DSNXEPM
DSNXEPP DSNXERT2 DSNXOD3 DSNXONZO DSNXOOP DSNXOVD
DSNXOV0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLXRSQ
DSNLZOSR
DSNXEDP
DSNXEDSC
DSNXEDS1
DSNXEPM
DSNXEPP
DSNXERT2
DSNXOD3
DSNXONZO
DSNXOOP
DSNXOVD
DSNXOV0
LISTEND
UI26382 COVER LETTER END
UI26402 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30375 -
****************************************************************
1 * USERS AFFECTED: All users of DB2 10 for z/OS who use query *
* acceleration *
****************************************************************
* PROBLEM DESCRIPTION: Query acceleration -- IDT *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Query acceleration -- IDT
Additional Keywords:
IDAAV4R1/K
Query acceleration -- IDT
PI30375 also needs APARs PI30376, PI30377, and PI31445.
Please refer to PI30376 for details.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30375
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNDQ8AC PI30375
DSNDQ8ST PI30375
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30375 DSNDQ8AC DSNDQ8ST
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNDQ8AC
DSNDQ8ST
LISTEND
UI26402 COVER LETTER END
UI26404 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30376 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who use query *
* acceleration *
****************************************************************
* PROBLEM DESCRIPTION: 1.This APAR adds a new feature: *
* IDT (In-Database Transformation) *
* to help users take full *
* advantage of the fast *
* speed of an accelerator for *
* operations which only occur on *
* an accelerator. *
* To achieve this, new table type *
* AOT (Accelerator-Only Table) is *
* added to DB2 and the accelerator. *
* The characteristic of this new *
* table type is that when CREATE *
1 * TABLE is issued, the table will be *
* created on both DB2 and the *
* accelerator. However, data only *
* exists on the accelerator; i.e., *
* DML could only be executed on *
* the accelerator. *
* *
* 2.Enable offloading of a Temporal *
* query to an accelerator. *
* Currently only Business Time *
* is supported. *
* 3.Block offloading when the *
* length of nchar/nvarchar is > *
* 16000 in the converted query. *
* SQLCODE -4742 with reason code *
* 11 will be issued. *
* 4.Fix SQLCODE -904 "Invalid SQL *
* Statement" for an offloaded *
* query which includes a minus *
* literal string. *
* 5.Fix 04E-00E70005 DSNXOMSF:P170. *
* After the fix, SQLCODE -4742 *
* with reason code 11 is issued *
* for an unsupported statement *
* that contains MEDIAN. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An accelerator improves query performance dramatically.
However, some operations involving huge data movement
could not take full advantage of the fast speed of
an accelerator. For example, some user applications
save the intermediate result set to a table.
This table is populated by INSERT with SELECT
and the table will be used for the next
step e.g.,data transformation. There is no need to backup
this table as the data can always be recreated from the
insert statement. With the current DB2 accelerator support,
an application needs to explicitly invoke a stored
procedure to create a table in the accelerator, which does
not work for some tool-generated statements. In addition,
only the SELECT part of the INSERT statement can be
accelerated, which leads to high CPU overhead if the
SELECT results in a large result set. What's
more, INSERT occurs on DB2 only, so the subsequent DML
cannot run in the accelerator because the accelerator does
not have the data that is newly inserted, or it still needs to
explicitly invoke the stored procedure to load the data.
This new function APAR now resolves the above scenario with
the introduction of a new table type: AOT (Accelerator Only
Table). With the Accelerator Only Table, the whole process
above is automated and enabled on the accelerator: The table
is automatically created in the accelerator when the CREATE
is issued on DB2. Data is automatically inserted in the
1 accelerator when the INSERT is issued on DB2 and the data
only exists in the accelerator, not on DB2. The query that
references the AOT will be accelerated (If not, DB2
DB2 will issue SQLCODE -4742).
Summary of Syntax/Semantics change:
1. CREATE TABLE ......
IN ACCELERATOR <accelerator-name>
(a). New clause IN ACCELERATOR <accelerator-name> Specifies
that the table is an Accelerator-Only Table.
"accelerator-name" specifies the accelerator that the
table will be defined in.
(b). The DB2 Catalog contains the table and column
definitions. TYPE is 'D' (definition only) for an AOT.
The data of the table exists only in the
accelerator, not in DB2.
(c). When IN ACCELERATOR option is specified, CREATE table
will also implicitly create the corresponding table in
the accelerator and populate the DB2
SYSACCEL.SYSACCELERATEDTABLES pseudo catalog table.
(d). CURRENT QUERY ACCELERATION special register does not
need to be set for the successful creation of an AOT.
(e). When IN ACCELERATOR clause is specified, some options
of the CREATE TABLE are not allowed. Refer to the
corresponding documentation for details.
2. DROP TABLE
If the table is defined as Accelerator-Only table, DROP
TABLE will also implicitly
(a) Drop the table from the accelerator.
(b) Delete the row from SYSACCEL.SYSACCELERATEDTABLES
pseudo catalog table
(c) CURRENT QUERY ACCELERATION special register does not
need to be set for the successful drop of the table.
The accelerator does not necessarily need to be active
at the time of DROP.
(d) DROP table will issue a new warning message +4748 with
a specific reason code under the following situations:
Reason 1: A row corresponding to the table does not
exist in the SYSACCELERATEDTABLES catalog
table
Reason 2: The accelerator server is not available for
one of the following reasons:
The accelerator server has not been started.
The accelerator server was started in EXPLAIN
ONLY mode
The accelerator server was started in
maintenance mode
The accelerator server accelerator does not
exist
Reason 3: A DRDA error was encountered
3. DML
DML that references this table, for example,
INSERT/UPDATE/DELETE/SELECT
1 must be executed in the accelerator, not in DB2. If the
statement type is not supported by the accelerator or if
the statement contains any expression that is not
supported by the accelerator, DB2 will return SQLCODE
-4742. CURRENT QUERY ACCELERATION cannot be NONE if
INSERT/UPDATE/DELETE/SELECT references an
accelerator-only table. Otherwise, -4742 will be issued.
4. Utilities: Except for RUNSTATS and REPAIR, the rest of the
utility statements--for example, LOAD, REORG, UNLOAD, etc.--
are not allowed on this table. RUNSTATS for Accelerator-Only
tables will leave all statistics as -1.
5. Accelerator-Only Table is supported in a static
application.
6. All the existing authorization rules apply and are
enforced by DB2.
7. Accelerator Alias. An Alias could be created for a
specific accelerator name.
8. Explain
New reason code 22
New values(22) for DSN_QUERYINFO_TABLE columns REASON_CODE
and QI_DATA are added:
22 The statement references an accelerator-only table,
but the statement is not offloadable. For example:
MERGE statement references an Accelerator-Only table.
UPDATE or DELETE statement references an
Accelerator-Only table, but the target table of
the UPDATE or DELETE is a regular DB2 table:
UPDATE DB2_TABLE SET ..(SELECT .. FROM
ACCEL_ONLY_TABLE)
INSERT, UPDATE or DELETE of a row expression with
subselect.
UPDATE ACCEL_ONLY_TABLE SET (C1, C2) =
(SELECT C3, C4 FROM TABLE2);
When the target table of INSERT/UPDATE/DELETE is an
Accelerator-Only Table, the plan table contains one row
with ACCESSTYPE as 'A'.
For EXPLAIN of a statement that references an
Accelerator-Only Table and is not eligible for query
acceleration, PLAN_TABLE output will be similar
to the above examples, except ACCESSTYPE will have
a value of blank, and for a SELECT statement,
QBLOCK_TYPE='PRUNED'.
9. Catalog statistics
RUNSTATS for an Accelerator-Only Table will leave all
statistics as -1.
The catalog statistics fields will need to be modified
to reflect this. The following is an example.
1 NPAGES: Total number of pages that include rows of the
table. The value is -1 if statistics have not
been gathered, or the row describes a view, an
alias, a created temporary table, an
Accelerator-Only table or an auxiliary table.
This column can be updated.
PCTPAGES: .....
assigned to the table. The value is -1 if
statistics have not been gathered, or the row
describes a view, alias, created temporary table,
an Acceleraor-Only table or auxiliary table.
This column can be updated.
Additional Keywords:
IDAAV4R1/K SQLCODE904 ABEND04E RC00E70005 SQLCODE4742
SQLMEDIAN
This APAR requires APARs PI30375, PI30377, and PI31445.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30376
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
See PI30376 APAR/PTF text for additional information about
why a REBIND is necessary.
PI30376 1. Enable offloading of a Temporal query to an
accelerator. Only Business Time is supported.
2. Block offloading to an accelerator when the length of
nchar/nvarchar is > 16000 in the converted query.
SQLCODE -4742 with reason code = 11 will be issued.
3. Fix SQLCODE -904 "Invalid SQL Statement" for an
offloading query which includes minus literal
string.
For example, SELECT * FROM T1 WHERE C2 IN ('-9','-1')
4. Fix abend 04E-00E70005 DSNXOMSF:P170. After the fix,
SQLCODE -4742 with reason code = 11 is issued for
an unsupported statement that contains MEDIAN.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
***Action for PI29176:
See PI29176 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29176 corrects a problem for SQL query acceleration when
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
1 must 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 PI27501:
See PI27501 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27501 corrects a problem for SQL query acceleration where
an SQL query is incorrectly blocked from routing to an
accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
***Action for PI26089:
See PI26089 APAR/PTF text for additional information about
why a REBIND is necessary.
PI26089 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
***Action for PI25743:
See PI25743 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25743 corrects a problem an ABEND04E RC00E72018 at DSNXSORI
OFFSET 5E02 may occur when a sort-merge join query with
merge-composite runs on parallel and the join predicate has
different nullability, data type, or data length.
To make this fix effective for a static application, it must 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 PI22945:
See PI22945 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22945 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
1
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
***Action for PI22413:
See PI22413 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22413 enables the following new functions for execution on an
accelerator:
(1) DECODE
(2) LTRIM and RTRIM with two arguments
(3) TRIM
(4) NVL
To make any of the new functions effective for a static
application that contains accelerated static SQL queries,
the application must be rebound after application of this PTF.
Review the PTF cover letter to determine which,if any,
applications could be affected by this change.
DB2BIND:
***Action for PI20688:
See PI20688 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20688 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
See PI14495 APAR/PTF text for additional information about
why a REBIND is necessary.
PI14495 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an IBM DB2 Analytics Accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DB2BIND:
***Action for PI14368:
See PI14368 APAR/PTF text for additional information about
1 why a REBIND is necessary.
PI14368 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
DOCUMENTATION:
***************************************************************
The following messages and codes are changed in
PI30376/PI30377/PI31445:
***************************************************************
The message/code text shown here is approximate and is subject
to change before it is published in the DB2 manuals.
(a) New messages -4747:
-4747 THE CREATE OR ALTER TABLE STATEMENT FAILED BECAUSE SOME
FUNCTIONALITY WAS SPECIFIED IN THE TABLE DEFINITION THAT IS NOT
SUPPORTED WITH THE TABLE TYPE. UNSUPPORTED FUNCTIONALITY:
functionality-keyword.
......
(b) Changed messages -159 THE STATEMENT REFERENCES object-name
WHICH IDENTIFIES AN actual-type RATHER THAN AN expected-type. A
CREATE MASK or CREATE PERMISSION statement must name a base
table that exists on the server. The table must not be a
system-period temporal table or a history table or an
accelerator-only table.
(c) Changed messages -270 FUNCTION NOT SUPPORTED
Explanation:
......
ALTER TABLE or CREATE TABLE statements:
.....
A CREATE TABLE statement must not contain a LIKE clause
and an IN ACCELERATOR clause.
A CREATE TABLE statement must not contain a LIKE clause
that references an accelerator-only table.
A CREATE TABLE statement must not contain an AS fullselect
clause and an IN ACCELERATOR clause.
A CREATE TABLE statement must not contain an AS fullselect
clause where the fullselect references an
accelerator-only table.
A CREATE TABLE statement must not contain a materialized
query definition and an IN ACCELERATOR clause.
A CREATE or ALTER TABLE statement must not define a Unicode
column in an EBCDIC table if the table is an
accelerator-only table.
......
1 CREATE MASK statements:
A CREATE MASK statement must not define a mask for an
accelerator-only table.
CREATE PERMISSION statements:
A CREATE PERMISSION statement must not define a column
permission for an accelerator-only table.
DECLARE GLOBAL TEMPORARY TABLE statements
The LIKE clause of a DECLARE GLOBAL TEMPORARY TABLE
must not reference an accelerator-only table.
TRIGGER statements
A CREATE [or ALTER] TRIGGER statement must not reference
an accelerator-only table in the body of the trigger.
A CREATE TRIGGER statement with INSTEAD OF clause specified
must not reference a view that references an
accelerator-only table in the body of the trigger.
(d) Changed messages -350 column-name WAS IMPLICITLY OR
EXPLICITLY REFERENCED IN A CONTEXT IN WHICH IT CANNOT BE USED
Explanation:
.......
A LOB column cannot be:
Defined in an accelerator-only table.
(e) Changed messages -637 DUPLICATE keyword-name KEYWORD OR
CLAUSE.
......
IN ACCELERATOR can only be specified once.
(f) Changed messages -650 THE ALTER STATEMENT CANNOT BE
EXECUTED, REASON reason-code
28 ALTER TABLE is not allowed when the table is an
accelerator-only table.
29 ALTER TABLESPACE is not allowed when the table space
contains an accelerator-only table.
(g) Changed messages -669 THE OBJECT CANNOT BE
EXPLICITLY DROPPED. REASON reason-code
......
0007 The DROP TABLESPACE statement or DROP DATABASE
statement attempted to drop a table space or database
that contains an accelerator-only table.
(h) Changed messages -750 THE SOURCE TABLE source-name
CANNOT BE RENAMED OR ALTERED AS SPECIFIED
Possible reasons for this error include, but are not limited to:
The table is an accelerator-only table.
(i) Changed messages -766 THE OBJECT OF A STATEMENT IS A TABLE
1 FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
......
Accelerator-only table
An accelerator-only table must not be specified in any of the
following statements:
1. A CREATE SYNONYM statement to define a synonym.
2. A CREATE TRIGGER statement to define a trigger for the
accelerator-only table.
3. A LOCK TABLE statement.
4. A CREATE INDEX
(j) Changed messages -817 THE SQL STATEMENT CANNOT BE
EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED DATA
CHANGE UPDATE OPERATION.
Explanation: The application attempted to execute an SQL
statement that would result in updates to user data or to the
subsystem catalog. This is prohibited for one of the following
reasons:
......
A CREATE TABLE statement for an accelerator-only table was fo
followed by a data change operation for an accelerator-only
table.
(k) Changed messages -7008 object-name NOT VALID FOR OPERATION
(reason-code)
17
A CREATE TRIGGER statement was issued, but the trigger cannot
be created because an INSTEAD OF trigger cannot be defined
on a view that has other views dependent on it, or the view
references an accelerator-only table, or an AFTER trigger
cannot be defined on a table that has a clone defined.
(l) Changed messages -20058 THE FULLSELECT SPECIFIED FOR
MATERIALIZED QUERY TABLE table-name IS NOT VALID.
The fullselect cannot contain a reference to a created
global temporary table, a declared global temporary table,
an accelerator-only table, or another materialized query
table.
(m) Changed messages -20240 INVALID SPECIFICATION
OF A SECURITY LABEL COLUMN table-name.column-name REASON
CODE reason-code
......
9
A security label column cannot be defined for an
accelerator-only table.
(n) Changed messages -20474 PERMISSION OR MASK CANNOT
BE CREATED FOR THE object-name OBJECT OF THE object-type TYPE.
REASON CODE reason-code.
......
17 One of the following situations occurred:
......
An accelerator-only table
1 39 The definition references an accelerator-only table.
(o) Changed messages -4742 THE STATEMENT CANNOT BE
EXECUTED BY DB2 OR IN THE ACCELERATOR (REASON reason-code)
......
The statement cannot be executed by DB2 if any of the following
conditions are true:
...
The statement references an accelerator-only table.
......
The statement cannot be executed by an accelerator server if any
condition that is indicated by a reason code is true.
......
22
The statement references an accelerator-only table,
but the statement is not offloadable. For example:
MERGE statement references an accelerator-only table.
UPDATE or DELETE statement references an accelerator-only
table,but the target table of the UPDATE, DELETE is a
normal table:
UPDATE DB2_TABLE SET .. (SELECT .. FROM
ACCEL_ONLY_TABLE).
INSERT, UPDATE or DELETE of a row expression with
subselect:
UPDATE ACCEL_ONLY_TABLE SET (C1, C2) = (SELECT C3, C4
TABLE2);
......
Programmer response: Use the reason code to determine the
cause of the failure, and take the appropriate action:
….....
22
Ensure the statement does not references an
accelerator-only table, or replace the accelerator-only
table with a DB2 table so that the query can be executed
in DB2.
(p) New warning message: +4748
+4748 THE statement STATEMENT FOR OBJECT object-name WAS
SUCCESSFUL ON THE DB2 SERVER. THE OBJECT MAY NOT HAVE BEEN
SUCCESSFULLY PROCESSED ON THE ACCELERATOR SERVER FOR
REASON reason-code
......
***************************************************************
Monitoring and Accounting Changes:
***************************************************************
The following is the new System Level Statistic Counters:
Q8STOPNC Total accumulated number of SQL Open statements sent
to IDAA by this DB2.
Q8STINSC Total accumulated number of SQL Insert statements
sent to IDAA by this DB2.
1 Q8STUPDC Total accumulated number of SQL Update statements
sent to IDAA by this DB2.
Q8STDELC Total accumulated number of SQL Delete statements
sent to IDAA by this DB2.
Q8STDRPC Total accumulated number of SQL Drop statements sent
IDAA by this DB2.
Q8STCRTC Total accumulated number of SQL Create statements
sent IDAA by this DB2.
Q8STCMTC Total accumulated number of SQL Commit statements
sent to IDAA by this DB2.
Q8STRBKC Total accumulated number of SQL Rollback statements
sent to IDAA by this DB2.
The new accounting fields (thread level):
Q8ACOPNC Total accumulated number of SQL Open statements
sent to IDAA by this thread.
Q8ACINSC Total accumulated number of SQL Insert statements
sent to IDAA by this thread.
Q8ACUPDC Total accumulated number of SQL Update statements
sent to IDAA by this thread.
Q8ACDELC Total accumulated number of SQL Delete statements
sent to IDAA by this thread.
Q8ACDRPC Total accumulated number of SQL Drop statements
sent to IDAA by this thread.
Q8ACCRTC Total accumulated number of SQL Create statements
sent to IDAA by this thread.
Q8ACCMTC Total accumulated number of SQL Commit statements
sent to IDAA by this thread.
Q8ACRBKC Total accumulated number of SQL Rollback statements
sent to IDAA by this thread.
Q8ACROWI Total accumulated number of rows inserted to IDAA by
this thread.
Q8ACROWU Total accumulated number of rows updated on IDAA by
this thread.
Q8ACROWD Total accumulated number of rows deleted on IDAA by
this thread.
Q8ACROWC Total accumulated number of rows returned by IDAA
to this thread.
Statement level:
For query processing, the following statement level counters are
defined (see Monitoring Counters Exchanged With DB2).
The semantics and values for those counters are slightly
different for INSERT/UPDATE/DELETE statements:
QW0316AROW - always set to 0 because DML statements return
no result set.
QW0316ABYT - always set to 0 because DML statements return
no result set.
QW0316TW1R - always set to 0 because DML statements have
no such wait times.
QW0316TWDB2 - always set to 0 because DML statements have
no such wait times.
ACTION:
Impacted packages must be DROP and CREATE'd or
ALTER REGENERATE'd after applying this PTF.
1
To find potentially impacted packages, this query may be used:
SELECT DISTINCT PKG.COLLID, PKG.NAME, HEX(PKG.CONTOKEN)
FROM SYSIBM.SYSPACKSTMT AS PKS, SYSIBM.SYSPACKAGE AS PKG
WHERE LENGTH(PKS.STMT) > 3499 AND PKG.TYPE = 'N' AND
PKG.COLLID = PKS.COLLID AND PKG.NAME=PKS.NAME AND
PKG.CONTOKEN = PKS.CONTOKEN;
Please note that the query results may identify false positives.
That is, not all of the packages identified may be impacted.
Alternatively, one may opt to only attempt the ALTER REGENERATE
or DROP and CREATE after encountering the -104 during REBIND.
ACTION:
The query provided in the ++HOLD of PM78210/UK90728 has
been updated to exclude views.
PM78210 fixes CREATE TABLE to define implicit table spaces
in reordered row format(RRF) when all of the following
conditions are true:
o DSNZPARM SPRMRRF is set to DISABLE
o The CREATE TABLE statement is specified with the BUFFERPOOL
clause
o The CREATE TABLE statement defines an inline LOB column
PM78210 does not fix existing objects. A query, such as
the sample query below may be used to determine whether table
spaces containing tables with inline LOB columns have partitions
which are in basic row format (BRF). The sample query may not
take into account all customer environments and scenarios.
The query output should be analyzed to verify the table spaces
returned are in BRF and contain tables with inline LOB columns
If so, the table spaces must be dropped and recreated after
PM78210 has been applied.
SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION
FROM SYSIBM.SYSCOLUMNS COL,
SYSIBM.SYSTABLES TAB,
SYSIBM.SYSTABLEPART TPT
WHERE
(( COL.DATATYPEID = 404
OR COL.DATATYPEID = 408
OR COL.DATATYPEID = 412
OR COL.SOURCETYPEID = 404
OR COL.SOURCETYPEID = 408
OR COL.SOURCETYPEID = 412 )
AND COL.TBCREATOR = TAB.CREATOR
AND COL.TBNAME = TAB.NAME
AND TAB.DBNAME = TPT.DBNAME
AND TAB.TSNAME = TPT.TSNAME
AND COL.LENGTH > 4
AND TPT.FORMAT = ' '
AND TAB.TYPE <> 'V' );
ACTION:
PM78210 fixes CREATE TABLE to define implicit table spaces
1 in reordered row format(RRF) when all of the following
conditions are true:
o DSNZPARM SPRMRRF is set to DISABLE
o The CREATE TABLE statement is specified with the BUFFERPOOL
clause
o The CREATE TABLE statement defines an inline LOB column
This APAR does not fix existing objects. A query, such as
the sample query below may be used to determine whether table
spaces containing tables with inline LOB columns have partitions
which are in basic row format (BRF). Affected table spaces
must be dropped and recreated after this apar is applied.
SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION
FROM SYSIBM.SYSCOLUMNS COL,
SYSIBM.SYSTABLES TAB,
SYSIBM.SYSTABLEPART TPT
WHERE
( ( COL.DATATYPEID = 404
OR COL.DATATYPEID = 408
OR COL.DATATYPEID = 412
OR COL.SOURCETYPEID = 404
OR COL.SOURCETYPEID = 408
OR COL.SOURCETYPEID = 412 )
AND COL.TBCREATOR = TAB.CREATOR
AND COL.TBNAME = TAB.NAME
AND TAB.DBNAME = TPT.DBNAME
AND TAB.TSNAME = TPT.TSNAME
AND COL.LENGTH > 4
AND TPT.FORMAT = ' ' );
ACTION:
***Action for PI16184:
See PI16184 APAR/PTF text for additional information about
why a REBIND is necessary.
PI16184 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an IBM DB2 Analytics Accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNGDBRT PI30376
DSNHAPLY PI30376
DSNHERRM PI30376
DSNHPTAB PI30376
DSNHSM5 PI30376
DSNHSM6A PI30376
DSNHSYMH PI30376
DSNTABA PI30376
DSNTADL PI30376
DSNTAEA PI30376
1 DSNTBBP2 PI30376
DSNTBRB2 PI30376
DSNTIAM PI30376
DSNTIA1 PI30376
DSNTLRAC PI30376
DSNUEXDB PI30376
DSNXEAAL PI30376
DSNXEBPG PI30376
DSNXECL PI30376
DSNXECLF PI30376
DSNXECLN PI30376
DSNXECW PI30376
DSNXECWA PI30376
DSNXECWU PI30376
DSNXEDP PI30376
DSNXEDSC PI30376
DSNXEDS1 PI30376
DSNXEPM PI30376
DSNXEPP PI30376
DSNXERBP PI30376
DSNXERT PI30376
DSNXERT2 PI30376
DSNXESQL PI30376
DSNXEUF0 PI30376
DSNXIAB9 PI30376
DSNXIAPR PI30376
DSNXIATB PI30376
DSNXIATS PI30376
DSNXICB3 PI30376
DSNXICIX PI30376
DSNXICPR PI30376
DSNXICSY PI30376
DSNXICTB PI30376
DSNXICTR PI30376
DSNXIDCL PI30376
DSNXIDPR PI30376
DSNXIDTB PI30376
DSNXIRTB PI30376
DSNXISB1 PI30376
DSNXISB6 PI30376
DSNXISB8 PI30376
DSNXISUB PI30376
DSNXI14 PI30376
DSNXI15 PI30376
DSNXMIT2 PI30376
DSNXODML PI30376
DSNXOD1 PI30376
DSNXOD3 PI30376
DSNXOD5 PI30376
DSNXOEX1 PI30376
DSNXOGP PI30376
DSNXOIN PI30376
DSNXOIWS PI30376
DSNXOLTD PI30376
DSNXOMQT PI30376
DSNXONZA PI30376
1 DSNXONZB PI30376
DSNXONZC PI30376
DSNXONZH PI30376
DSNXONZO PI30376
DSNXONZQ PI30376
DSNXONZS PI30376
DSNXOOP PI30376
DSNXOOS1 PI30376
DSNXOP0 PI30376
DSNXORFN PI30376
DSNXOTG PI30376
DSNXOTL PI30376
DSNXOVD PI30376
DSNXOW1 PI30376
DSNXTAD PI30376
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30376 DSNGDBRT DSNHAPLY DSNHERRM DSNHPTAB DSNHSM5 DSNHSM6A
DSNHSYMH DSNTABA DSNTADL DSNTAEA DSNTBBP2 DSNTBRB2
DSNTIAM DSNTIA1 DSNTLRAC DSNUEXDB DSNXEAAL DSNXEBPG
DSNXECL DSNXECLF DSNXECLN DSNXECW DSNXECWA DSNXECWU
DSNXEDP DSNXEDSC DSNXEDS1 DSNXEPM DSNXEPP DSNXERBP
DSNXERT DSNXERT2 DSNXESQL DSNXEUF0 DSNXIAB9 DSNXIAPR
DSNXIATB DSNXIATS DSNXICB3 DSNXICIX DSNXICPR DSNXICSY
DSNXICTB DSNXICTR DSNXIDCL DSNXIDPR DSNXIDTB DSNXIRTB
DSNXISB1 DSNXISB6 DSNXISB8 DSNXISUB DSNXI14 DSNXI15
DSNXMIT2 DSNXODML DSNXOD1 DSNXOD3 DSNXOD5 DSNXOEX1
DSNXOGP DSNXOIN DSNXOIWS DSNXOLTD DSNXOMQT DSNXONZA
DSNXONZB DSNXONZC DSNXONZH DSNXONZO DSNXONZQ DSNXONZS
DSNXOOP DSNXOOS1 DSNXOP0 DSNXORFN DSNXOTG DSNXOTL
DSNXOVD DSNXOW1 DSNXTAD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNGDBRT
DSNHAPLY
DSNHERRM
DSNHPTAB
DSNHSM5
DSNHSM6A
DSNHSYMH
DSNTABA
DSNTADL
DSNTAEA
DSNTBBP2
DSNTBRB2
DSNTIAM
DSNTIA1
DSNTLRAC
DSNUEXDB
DSNXEAAL
DSNXEBPG
DSNXECL
DSNXECLF
DSNXECLN
1 DSNXECW
DSNXECWA
DSNXECWU
DSNXEDP
DSNXEDSC
DSNXEDS1
DSNXEPM
DSNXEPP
DSNXERBP
DSNXERT
DSNXERT2
DSNXESQL
DSNXEUF0
DSNXIAB9
DSNXIAPR
DSNXIATB
DSNXIATS
DSNXICB3
DSNXICIX
DSNXICPR
DSNXICSY
DSNXICTB
DSNXICTR
DSNXIDCL
DSNXIDPR
DSNXIDTB
DSNXIRTB
DSNXISB1
DSNXISB6
DSNXISB8
DSNXISUB
DSNXI14
DSNXI15
DSNXMIT2
DSNXODML
DSNXOD1
DSNXOD3
DSNXOD5
DSNXOEX1
DSNXOGP
DSNXOIN
DSNXOIWS
DSNXOLTD
DSNXOMQT
DSNXONZA
DSNXONZB
DSNXONZC
DSNXONZH
DSNXONZO
DSNXONZQ
DSNXONZS
DSNXOOP
DSNXOOS1
DSNXOP0
DSNXORFN
DSNXOTG
1 DSNXOTL
DSNXOVD
DSNXOW1
DSNXTAD
LISTEND
UI26404 COVER LETTER END
UI26406 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30377 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS using query *
* acceleration *
****************************************************************
* PROBLEM DESCRIPTION: Query acceleration -- IDT *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Query acceleration -- IDT
Additional Keywords:
IDAAV4R1/K
Query acceleration -- IDT
PI30377 also needs APARs PI30375, PI30376, and PI31445.
Please see PI30376 for details.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30377
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DOCUMENTATION:
*** Documentation for PI17163 ***
The following new reason code is added to the DB2 Codes manual.
00D34451
Explanation: A remote application connected to a DB2 server and
issued an SQL statement that contains a three-part name or alias
that refers to a table or view at a remote location. However,
the remote reference actually resolves to the local DB2 server
location. This situation can occur when the SQL statement
refers to a location alias but the package for the application
was bound before the location alias was defined.
System action: The SQL statement is rejected.
User response: Bind the application package at the server after
the location alias has been defined. For a data sharing group,
ensure that the location alias is defined on all members.
Problem determination: Use the -DISPLAY DDF command to
determine the location aliases for the server. Ensure that any
location alias references in the application exist at the
server when the package is bound.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNLBABR PI30377
DSNLCAIA PI30377
DSNLCBFM PI30377
DSNLCCDR PI30377
DSNLCCLO PI30377
DSNLCCNR PI30377
DSNLCDG1 PI30377
DSNLCDG2 PI30377
DSNLCDP1 PI30377
DSNLCITR PI30377
DSNLCKDS PI30377
DSNLCMBE PI30377
DSNLCMRL PI30377
DSNLCMSL PI30377
DSNLCMT1 PI30377
DSNLCRFL PI30377
DSNLCRNC PI30377
DSNLCRSY PI30377
DSNLCRTD PI30377
DSNLCSRR PI30377
DSNLCTCN PI30377
DSNLCTDR PI30377
DSNLCTRC PI30377
DSNLCVTR PI30377
DSNLCXLI PI30377
DSNLDALB PI30377
DSNLIAAC PI30377
DSNLIRCA PI30377
DSNLIRTR PI30377
DSNLISDA PI30377
DSNLQACT PI30377
DSNLQINA PI30377
DSNLTBST PI30377
DSNLTCCN PI30377
DSNLTCN2 PI30377
DSNLTDSR PI30377
DSNLTGBK PI30377
DSNLTINT PI30377
DSNLTPNL PI30377
DSNLTRDL PI30377
DSNLTSET PI30377
DSNLTUOW PI30377
DSNLVXMV PI30377
DSNLXCMT PI30377
DSNLXCM2 PI30377
DSNLXCQH PI30377
DSNLXGET PI30377
DSNLXGVR PI30377
DSNLXHCN PI30377
DSNLXHIM PI30377
DSNLXHNO PI30377
DSNLXHOC PI30377
DSNLXHPR PI30377
DSNLXHSE PI30377
1 DSNLXHSP PI30377
DSNLXMRF PI30377
DSNLXOQS PI30377
DSNLXPAL PI30377
DSNLXPCA PI30377
DSNLXPRS PI30377
DSNLXRAX PI30377
DSNLXRBF PI30377
DSNLXRBT PI30377
DSNLXRCL PI30377
DSNLXRCM PI30377
DSNLXRCN PI30377
DSNLXRCX PI30377
DSNLXRDT PI30377
DSNLXREL PI30377
DSNLXRFT PI30377
DSNLXRLS PI30377
DSNLXROP PI30377
DSNLXRQX PI30377
DSNLXRSL PI30377
DSNLXRSQ PI30377
DSNLXRSS PI30377
DSNLXRUW PI30377
DSNLXSET PI30377
DSNLXSR PI30377
DSNLXSSR PI30377
DSNLXXSS PI30377
DSNLZHC0 PI30377
DSNLZHC1 PI30377
DSNLZHC2 PI30377
DSNLZHP0 PI30377
DSNLZHP1 PI30377
DSNLZHP2 PI30377
DSNLZHP3 PI30377
DSNLZHR0 PI30377
DSNLZHR1 PI30377
DSNLZMON PI30377
DSNLZRCD PI30377
DSNLZRDS PI30377
DSNLZRPA PI30377
DSNLZR00 PI30377
DSNLZSRD PI30377
DSNLZSRM PI30377
DSNLZSR2 PI30377
DSNLZSR3 PI30377
DSNLZSR4 PI30377
DSNLZS00 PI30377
DSNLZS01 PI30377
DSNLZS02 PI30377
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30377 DSNLBABR DSNLCAIA DSNLCBFM DSNLCCDR DSNLCCLO DSNLCCNR
DSNLCDG1 DSNLCDG2 DSNLCDP1 DSNLCITR DSNLCKDS DSNLCMBE
DSNLCMRL DSNLCMSL DSNLCMT1 DSNLCRFL DSNLCRNC DSNLCRSY
DSNLCRTD DSNLCSRR DSNLCTCN DSNLCTDR DSNLCTRC DSNLCVTR
DSNLCXLI DSNLDALB DSNLIAAC DSNLIRCA DSNLIRTR DSNLISDA
1 DSNLQACT DSNLQINA DSNLTBST DSNLTCCN DSNLTCN2 DSNLTDSR
DSNLTGBK DSNLTINT DSNLTPNL DSNLTRDL DSNLTSET DSNLTUOW
DSNLVXMV DSNLXCMT DSNLXCM2 DSNLXCQH DSNLXGET DSNLXGVR
DSNLXHCN DSNLXHIM DSNLXHNO DSNLXHOC DSNLXHPR DSNLXHSE
DSNLXHSP DSNLXMRF DSNLXOQS DSNLXPAL DSNLXPCA DSNLXPRS
DSNLXRAX DSNLXRBF DSNLXRBT DSNLXRCL DSNLXRCM DSNLXRCN
DSNLXRCX DSNLXRDT DSNLXREL DSNLXRFT DSNLXRLS DSNLXROP
DSNLXRQX DSNLXRSL DSNLXRSQ DSNLXRSS DSNLXRUW DSNLXSET
DSNLXSR DSNLXSSR DSNLXXSS DSNLZHC0 DSNLZHC1 DSNLZHC2
DSNLZHP0 DSNLZHP1 DSNLZHP2 DSNLZHP3 DSNLZHR0 DSNLZHR1
DSNLZMON DSNLZRCD DSNLZRDS DSNLZRPA DSNLZR00 DSNLZSRD
DSNLZSRM DSNLZSR2 DSNLZSR3 DSNLZSR4 DSNLZS00 DSNLZS01
DSNLZS02
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNLBABR
DSNLCAIA
DSNLCBFM
DSNLCCDR
DSNLCCLO
DSNLCCNR
DSNLCDG1
DSNLCDG2
DSNLCDP1
DSNLCITR
DSNLCKDS
DSNLCMBE
DSNLCMRL
DSNLCMSL
DSNLCMT1
DSNLCRFL
DSNLCRNC
DSNLCRSY
DSNLCRTD
DSNLCSRR
DSNLCTCN
DSNLCTDR
DSNLCTRC
DSNLCVTR
DSNLCXLI
DSNLDALB
DSNLIAAC
DSNLIRCA
DSNLIRTR
DSNLISDA
DSNLQACT
DSNLQINA
DSNLTBST
DSNLTCCN
DSNLTCN2
DSNLTDSR
DSNLTGBK
DSNLTINT
DSNLTPNL
1 DSNLTRDL
DSNLTSET
DSNLTUOW
DSNLVXMV
DSNLXCMT
DSNLXCM2
DSNLXCQH
DSNLXGET
DSNLXGVR
DSNLXHCN
DSNLXHIM
DSNLXHNO
DSNLXHOC
DSNLXHPR
DSNLXHSE
DSNLXHSP
DSNLXMRF
DSNLXOQS
DSNLXPAL
DSNLXPCA
DSNLXPRS
DSNLXRAX
DSNLXRBF
DSNLXRBT
DSNLXRCL
DSNLXRCM
DSNLXRCN
DSNLXRCX
DSNLXRDT
DSNLXREL
DSNLXRFT
DSNLXRLS
DSNLXROP
DSNLXRQX
DSNLXRSL
DSNLXRSQ
DSNLXRSS
DSNLXRUW
DSNLXSET
DSNLXSR
DSNLXSSR
DSNLXXSS
DSNLZHC0
DSNLZHC1
DSNLZHC2
DSNLZHP0
DSNLZHP1
DSNLZHP2
DSNLZHP3
DSNLZHR0
DSNLZHR1
DSNLZMON
DSNLZRCD
DSNLZRDS
DSNLZRPA
DSNLZR00
1 DSNLZSRD
DSNLZSRM
DSNLZSR2
DSNLZSR3
DSNLZSR4
DSNLZS00
DSNLZS01
DSNLZS02
LISTEND
UI26406 COVER LETTER END
UI26408 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI31445 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS using query *
* acceleration *
****************************************************************
* PROBLEM DESCRIPTION: Query acceleration -- IDT *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Query acceleration -- IDT
Additional Keywords:
IDAAV4R1/K
Query acceleration -- IDT
PI31445 also needs APARs PI30375, PI30376, and PI30377.
Please refer to PI30376 for details.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI31445
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNB1TAD PI31445
DSNFMDIR PI31445
DSNFUDRB PI31445
DSNTBAB2 PI31445
DSNTBCM PI31445
DSNTBCM5 PI31445
DSNTBFR2 PI31445
DSNTBSPL PI31445
DSNTXACT PI31445
DSNTXSTB PI31445
DSNUGMAP PI31445
DSNUGMSB PI31445
DSNUMSGB PI31445
DSNURLIM PI31445
DSNUSDRA PI31445
DSNUSDRB PI31445
DSNUSDRC PI31445
DSNUSITS PI31445
1 DSNVDTA PI31445
DSNWAACT PI31445
DSNWAAPI PI31445
DSNWACDF PI31445
DSNWAFRR PI31445
DSNWARDS PI31445
DSNWVAPR PI31445
DSNWVCSP PI31445
DSNWVCST PI31445
DSNWVSMT PI31445
DSNWVZIT PI31445
DSNWVZPS PI31445
DSNWVZSA PI31445
DSNWZDG2 PI31445
DSNX8API PI31445
DSNX8CDA PI31445
DSNX8CMD PI31445
DSNX8CTG PI31445
DSNX8EKG PI31445
DSNX8INI PI31445
DSNX8IN2 PI31445
DSNX8SMF PI31445
DSNX8STA PI31445
DSNX8STO PI31445
DSNX8WAC PI31445
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI31445 DSNB1TAD DSNFMDIR DSNFUDRB DSNTBAB2 DSNTBCM DSNTBCM5
DSNTBFR2 DSNTBSPL DSNTXACT DSNTXSTB DSNUGMAP DSNUGMSB
DSNUMSGB DSNURLIM DSNUSDRA DSNUSDRB DSNUSDRC DSNUSITS
DSNVDTA DSNWAACT DSNWAAPI DSNWACDF DSNWAFRR DSNWARDS
DSNWVAPR DSNWVCSP DSNWVCST DSNWVSMT DSNWVZIT DSNWVZPS
DSNWVZSA DSNWZDG2 DSNX8API DSNX8CDA DSNX8CMD DSNX8CTG
DSNX8EKG DSNX8INI DSNX8IN2 DSNX8SMF DSNX8STA DSNX8STO
DSNX8WAC
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNB1TAD
DSNFMDIR
DSNFUDRB
DSNTBAB2
DSNTBCM
DSNTBCM5
DSNTBFR2
DSNTBSPL
DSNTXACT
DSNTXSTB
DSNUGMAP
DSNUGMSB
DSNUMSGB
DSNURLIM
DSNUSDRA
DSNUSDRB
DSNUSDRC
1 DSNUSITS
DSNVDTA
DSNWAACT
DSNWAAPI
DSNWACDF
DSNWAFRR
DSNWARDS
DSNWVAPR
DSNWVCSP
DSNWVCST
DSNWVSMT
DSNWVZIT
DSNWVZPS
DSNWVZSA
DSNWZDG2
DSNX8API
DSNX8CDA
DSNX8CMD
DSNX8CTG
DSNX8EKG
DSNX8INI
DSNX8IN2
DSNX8SMF
DSNX8STA
DSNX8STO
DSNX8WAC
LISTEND
UI26408 COVER LETTER END
UI26503 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34364 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of COPY utility on compressed objects *
* with reset RBA enabled on a non-data sharing *
* system. *
****************************************************************
* PROBLEM DESCRIPTION: COPY FULL YES with DSNZPARM, SPRMRRBA, *
* enabled did not reset the dictionary *
* version for the dictionary built by *
* Compress-On-Insert *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
COPY FULL YES with DSNZPARM, SPRMRRBA, enabled did not reset
the dictionary version for the dictionary pages in the DB2 data
on a non data sharing system. This caused a subsequent Q
replication product to fail with error message ASN0011E with
reason code RC00C90064
The compression dictionary in the target object was created
by compress-on-insert, in a form COPY utility did not handle
properly.
1
Additional keywords:
MSGASN0011E RC00C90064
COPY FULL YES with DSNZPARM, SPRMRRBA, enabled has been modified
to reset the dictionary version number for DB2 dictionary
created during insert.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34364
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUBASA PI34364
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34364 DSNUBASA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUBASA
LISTEND
UI26503 COVER LETTER END
UI26663 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI27273 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users of classic *
* segmented table space. *
****************************************************************
* PROBLEM DESCRIPTION: Various abends due to first segment *
* missing, such as *
* ABEND04E RC00C90101 at DSNKINSL *
* ERQUAL5033 *
* or *
* ABEND04E RC00C90101 at DSNIBHUN *
* ERQUAL500C *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Inserting to a classic segmented table space could drive
rebuilding segment by allocating the first segment for the
table. But since the first segment allocation is logged as
REDO/UNDO type, the insert aborting will rollback the
allocation. Once the segment is allocated, concurrent threads
can insert rows to the newly allocated segment. If the
transaction that allocated the new segment rolls back then
segment is rolled back along with record that was inserted by
other concurrent threads. As a result, record could be lost.
DB2 code has been modified to write REDO only log record for
segment allocation from segment rebuilding process.
COMPONENT: 5740-XYR00-HDBAA10
1 APARS FIXED: PI27273
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 PI27273
DSNILPG PI27273
DSNISEGF PI27273
DSNISEGR PI27273
DSNISHPI PI27273
DSNISMRS PI27273
DSNISRTI PI27273
DSNISUPI PI27273
DSNITLPE PI27273
DSNIVOBD PI27273
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI27273 DSNIFOD DSNILPG DSNISEGF DSNISEGR DSNISHPI DSNISMRS
DSNISRTI DSNISUPI DSNITLPE DSNIVOBD
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIFOD
DSNILPG
DSNISEGF
DSNISEGR
DSNISHPI
DSNISMRS
DSNISRTI
DSNISUPI
DSNITLPE
DSNIVOBD
LISTEND
UI26663 COVER LETTER END
UI26665 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34271 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement that contains an UNION, EXCEPT *
* or INTERSECT and a column with a field *
* procedure. *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect output could happen for an *
* SQL statement that satisfies all of the *
* following conditions: *
* *
* 1. It contains an UNION, EXCEPT or *
* INTERSECT in the top level of the *
* statement. *
* 2. A column in the select list contains *
1 * a field procedure. *
* 3. The field-decoding length is bigger *
* than the column length. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An example is shown below:
CREATE TABLE T1(
C1 CHAR(10),
C2 CHAR(10) FIELDPROC FLDPROC1,
C3 CHAR(10)
);
SELECT C1, C2, C3
FROM T1
WHERE C1 = 1
UNION
SELECT C1, C2, C3
FROM T1
WHERE C1 = 2
;
FLDPROC1 is a field procedure, and the field-decoding length is
bigger than the column C2 length 10. DB2 did not correctly
process the aforementioned SQL statement, which caused incorrect
output.
DB2 has been modified to correctly process the aforementioned
SQL statement, and there will be no incorrect output.
Additional keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLUNION SQLINTERSECT
SQLEXCEPT
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34271
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI34271:
See PI34271 APAR/PTF text for additional information about
why a REBIND is necessary.
PI34271 corrects a problem that incorrect output could happen
for an SQL statement that satisfies all of the following
conditions:
1. It contains an UNION, EXCEPT or INTERSECT in the top level of
the statement.
2. A column in the select list contains a field procedure.
3. The field-decoding length is bigger than the column length.
To make this fix effective for a static application, it must 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 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTF PI34271
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34271 DSNXOTF
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTF
LISTEND
UI26665 COVER LETTER END
UI26711 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32723 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of the LOAD utility *
* on compressed table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: LOAD utility on compressed table space *
* when DB2 came down unexpectedly. When *
* DB2 is restarted, the objects were in *
* RECP,LPL,CHKP. Automatic LPL recovery *
* resulted in DSNI005I with RC00C900A0. *
* Attempts to RECOVER or START DB *
* resulted in DSNT501I with RC00C200EC *
* or RC00C9007F. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
While LOAD was running, after formatting the dictionary page,
a synchronous write of the header page with the dictionary info
was set. That guarantees that the next open will try to load the
dictionary pages. However, DB2 came down before the dictionary
pages were written. So, when DB2 restarts, log apply failed
and put the dictionary pages into LPL and fail any open request
because the header page says the dictionary pages are supposed
to be there when they are not.
DB2 code is changed to do synchronous writes for dictionary
pages. This would enable Log Apply to work properly, so the
dictionary pages would be recovered at the log apply time.
The pages would not be put on LPL.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32723
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIZLDL PI32723
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI32723 DSNIZLDL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIZLDL
LISTEND
UI26711 COVER LETTER END
UI26764 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29894 -
****************************************************************
* USERS AFFECTED: All users of DB2 for z/OS who use *
* query acceleration. *
****************************************************************
* PROBLEM DESCRIPTION: This APAR fixes the following problems *
* for query acceleration: *
* (1) The function TIME() with a string *
* timestamp constant, host variable *
* or parameter marker value can *
* incorrectly return microseconds. *
* (2) REFRESH TABLE is incorrectly *
* evaluated for acceleration. *
* (3) DB2 V11 only: the function *
* TIMESTAMPDIFF may return -904 when *
* executed on an accelerator. *
* (4) DB2 V10 only: An 04E abend *
* DSNXVTRS:M420 may occur for *
* a statement with GET ACCEL ARCHIVE *
* = YES when none of the tables *
* have any partitions in the PRO *
* restricted status and subsystem *
* parameter CACHEDYN=YES. *
* (5) DB2 V10 and V11: Add support to *
* honor the FETCH FIRST n ROWS *
* ONLY clause for an accelerated *
* dynamic cursor query that contains *
* a set operator like UNION ALL. *
* (6) DB2 V10 and V11:An SQL *
* statement with DECODE and a *
* result expression of NULL should *
* not execute on an accelerator. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR fixes the following problems for query acceleration:
(1) The function TIME() with a string timestamp constant,
host variable or parameter marker value can incorrectly
return microseconds.
(2) REFRESH TABLE is incorrectly evaluated for acceleration,
but is never executed on an accelerator.
EXPLAIN of a REFRESH TABLE statement when
1 QUERY ACCELERATION = ENABLE, ENABLE WITH FAILBACK,
ELIGBLE, or ALL incorrectly populates PLAN_TABLE and
DSN_QUERYINFO_TABLE indicating that REFRESH TABLE
can execute on an accelerator. Executing a REFRESH TABLE
statement when QUERY ACCELERATION=ALL incorrectly issues
SQLCODE -4742.
(3) DB2 V11 only: the function TIMESTAMPDIFF may return -904
when executed on an accelerator.
(4) DB2 V10 only: An 04E abend DSNXVTRS:M420 may occur for
a statement with GET ACCEL ARCHIVE= YES when none of the
tables have any partitions in the PRO restricted status
and subsystem parameter CACHEDYN=YES.
(5) DB2 V10 and V11: Add support to honor the FETCH FIRST n
ROWS ONLY clause for an accelerated dynamic cursor query
that contains a set operator like UNION ALL.
(6) DB2 V10 and V11:An SQL statement with DECODE and a
result expression of NULL should not execute on an
accelerator.
For static SQL queries that have been bound for acceleration
and will use any of functions above, REBIND the package
for the failing query after applying this PTF.
Keywords:
IDAAV3R1/K IDAAV4R1/K SQLCODE4742 SQLEXPLAIN SQLTIME
SQLREFRESHTABLE SQLINCORROUT SQLINCORR INCORROUT DB2INCORR/K
SQLCODE904 SQLTIMESTAMPDIFF
ABEND04E RC00E70005 DSNXVTRS M420 SQLFFNR SQLDECODE
DB2 code is fixed:
(1) The correct result is returned for TIME().
(2) EXPLAIN of a REFRESH TABLE statement will not populate
DSN_QUERYINFO_TABLE. PLAN_TABLE will have a DB2 access path.
Executing REFRESH TABLE when QUERY ACCELERATION=ALL will now
execute on DB2.
(3) The correct result is returned for TIMESTAMPDIFF().
(4) The statement executes properly.
(5) The FETCH FIRST n ROWS clause is honored for acceleration.
(6) The statement no longer executes on an accelerator.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29894
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI29894:
See PI29894 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29894 corrects a problem for SQL query acceleration where
there are errors when routed to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
1 could be affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXODML PI29894
DSNXOEX1 PI29894
DSNXONZC PI29894
DSNXONZO PI29894
DSNXONZQ PI29894
DSNXONZS PI29894
DSNXOOP PI29894
DSNXOOS1 PI29894
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29894 DSNXODML DSNXOEX1 DSNXONZC DSNXONZO DSNXONZQ DSNXONZS
DSNXOOP DSNXOOS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXODML
DSNXOEX1
DSNXONZC
DSNXONZO
DSNXONZQ
DSNXONZS
DSNXOOP
DSNXOOS1
LISTEND
UI26764 COVER LETTER END
UI26785 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32931 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users *
* of queries containing predicates. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at *
* location DSNXRDOU P011 or DSNXRDEC P005 *
* when processing queries containing *
* predicates. Code analysis has found *
* that a zero pointer could be used in *
* some code paths. However, no problems *
* have been reported resulting from it. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Code analysis has found that there are some cases where a zero
pointer could be used to reference storage. However, no
problems have been reported resulting from it but this could
cause an abend at location DSNXRDOU P011 or DSNXRDEC P005.
The code in DB2 has been modified to correct the problem of
referencing the incorrect storage location during bind time to
prevent the invalid execution structures from being created.
1 COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32931
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI32931:
See PI32931 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32931 corrects a problem of an ABEND04E RC00E70005 in
DSNXRDOU:P011 or DSNXRDEC:P005.
To make this fix effective for a static application, it must 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
DSNXGINB PI32931
DSNXGRTS PI32931
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32931 DSNXGINB DSNXGRTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGINB
DSNXGRTS
LISTEND
UI26785 COVER LETTER END
UI26790 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI29198 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: -DISPLAY THREAD SERVICE(WAIT) command *
* entered an infinite loop. In the *
* reported instance, this occurred on a *
* z/OS image that had only one processor *
* which prevented other work from *
* executing. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
-DISPLAY THREAD SERVICE(WAIT) attempts to increase the priority
of threads that are holding DB2 latches which, in turn, are
blocking the execution of other threads. In the reported
failure, corruption of an agent chain resulted in an infinite
loop while attempting to determine which thread held a latch
that was being waited on by other threads.
1 DSNVDTA was modified to recognize possible looped agent
structures and not continue processing the thread if the
processing being done is not critical. Abends may occur
if looped structures are detected, either as part of the
-DISPLAY THREAD command or other DB2 processing.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI29198
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNVDTA PI29198
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI29198 DSNVDTA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNVDTA
LISTEND
UI26790 COVER LETTER END
UI26836 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI35991 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users running MODIFY *
* UTILITY *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E 00C90101 in DSNIDBDF 5004 *
* when running MODIFY Utility. *
* Multiple DB2 members crashed. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running the MODIFY Utility, the DBET gets out of sync
and detects a problem with the local copy of the DBET when
processing a notify exit. This causes many of the data sharing
members to abend and crash.
When copying data to a member during a notify exit, a flag
telling DBET that there is piece data was not accurately
set. This flag said that there was no piece data for this
dbetdb and because of that, a copy of the data from the SCA
was moved over data in the dbetdb that had piece data, making
the piece data invalid. This lead to an abend for inconsistent
data and lead to the crash of several members.
Servicablity is added to DBET code to check for inconsistencies
in the DBET before issuing a notify to other members. This
limits the exposure of the problem to the originating member
and keeps the other members from crashing with the same abend.
Piece diagnostic information has been added to help with
1 debugging. Cleanup of piece information is now done when
the piece storage is released so there is no residual states
left in the DBET structure.
To fix the problem with the invalid piece data flag, checking
is done to make sure there is piece data before copying the
data from the SCA to the member's dbetdb.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35991
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBAB PI35991
DSNIDBBD PI35991
DSNIDBDA PI35991
DSNIDBDF PI35991
DSNIDBDG PI35991
DSNIDBDM PI35991
DSNIDBDR PI35991
DSNIDBDW PI35991
DSNIDBEL PI35991
DSNIDBFA PI35991
DSNIDBGC PI35991
DSNIDBGN PI35991
DSNIDBHK PI35991
DSNIDBIN PI35991
DSNIDBMC PI35991
DSNIDBMF PI35991
DSNIDBMG PI35991
DSNIDBMS PI35991
DSNIDBNG PI35991
DSNIDBNI PI35991
DSNIDBPL PI35991
DSNIDBPX PI35991
DSNIDBSE PI35991
DSNPXTN0 PI35991
DSNWDFDM PI35991
DSN1LDET PI35991
DSN1LOUT PI35991
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35991 DSNIDBAB DSNIDBBD DSNIDBDA DSNIDBDF DSNIDBDG DSNIDBDM
DSNIDBDR DSNIDBDW DSNIDBEL DSNIDBFA DSNIDBGC DSNIDBGN
DSNIDBHK DSNIDBIN DSNIDBMC DSNIDBMF DSNIDBMG DSNIDBMS
DSNIDBNG DSNIDBNI DSNIDBPL DSNIDBPX DSNIDBSE DSNPXTN0
DSNWDFDM DSN1LDET DSN1LOUT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBAB
DSNIDBBD
DSNIDBDA
DSNIDBDF
DSNIDBDG
1 DSNIDBDM
DSNIDBDR
DSNIDBDW
DSNIDBEL
DSNIDBFA
DSNIDBGC
DSNIDBGN
DSNIDBHK
DSNIDBIN
DSNIDBMC
DSNIDBMF
DSNIDBMG
DSNIDBMS
DSNIDBNG
DSNIDBNI
DSNIDBPL
DSNIDBPX
DSNIDBSE
DSNPXTN0
DSNWDFDM
DSN1LDET
DSN1LOUT
LISTEND
UI26836 COVER LETTER END
UI26847 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI32550 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* containing columns defined with field *
* procedures(FIELDPROC) *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4 RC00000038 can occur at *
* location DSNXGRDS DSNXRBND OFFSET01A0 *
* for a query containing column defined *
* with a field procedure(FIELDPROC) when *
* intermediate query result is stored in *
* a work file. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND0C4 RC00000038 can occur at location DSNXRBND offset
01A0 for a query containing column defined with a field
procedure(FIELDPROC) when intermediate query result is stored
in a work file. DB2 incorrectly accessed low-core storage while
saving the column name in an internal structure. This can result
in storage overlay upto 255 bytes depending on the data in the
low-core storage location.
Additional known symptoms of the problem include:
ABEND0C4 RC00000038 at location DSNXGRTM offset 487A
ABEND0C4 RC00000038 at location DSNXGRTS offset 86C4
ABEND04E RC00E70005 at location DSNXESX4:P403.
1 DB2 has been modified to build the internal structure correctly.
Additional Keywords : SQLFIELDPROC DB2OVRLAY/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI32550
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PM59265:
See PM59265 APAR/PTF text for additional information about
why a REBIND is necessary.
PM59265 corrects a problem of ABEND0C4 RC00000004 IN DSNXRBND
OFFSET189A
To make this fix effective for a static application, it must 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 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:
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.
DB2BIND:
***Action for PI32550:
See PI32550 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32550 corrects a problem for a query that contains a column
define with a field procedure(FIELDPROC).
1 To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI26285:
See PI26285 APAR/PTF text for additional information about
why a REBIND is necessary.
This apar corrects a problem that can cause DB2 to return an
incorrect result, more rows than expected. The problem can
occur for a query that includes a large indexable IN-List with
many NULL elements that DB2 does not process properly.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGCAL PI32550
DSNXGDTV PI32550
DSNXGMRG PI32550
DSNXGMVE PI32550
DSNXGOU2 PI32550
DSNXGRM1 PI32550
DSNXGRTM PI32550
DSNXGRTS PI32550
DSNXGSC2 PI32550
DSNXGSFN PI32550
DSNXGUDF PI32550
DSNXGVCM PI32550
DSNXGXGN PI32550
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI32550 DSNXGCAL DSNXGDTV DSNXGMRG DSNXGMVE DSNXGOU2 DSNXGRM1
DSNXGRTM DSNXGRTS DSNXGSC2 DSNXGSFN DSNXGUDF DSNXGVCM
DSNXGXGN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXGCAL
DSNXGDTV
DSNXGMRG
DSNXGMVE
DSNXGOU2
DSNXGRM1
DSNXGRTM
DSNXGRTS
DSNXGSC2
DSNXGSFN
DSNXGUDF
DSNXGVCM
DSNXGXGN
1 LISTEND
UI26847 COVER LETTER END
UI27006 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38328 -
****************************************************************
* USERS AFFECTED: All DB2 10, 11 for z/OS users with *
* Partition By Growth (PBG) table spaces. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E with RC00C90207 in DSNIOW *
* at ERQUAL5003 when fetching an *
* overflow record. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When lock escalation happened on a PBG and all currently
allocated partitions were already escalated to a X or S lock,
DB2 overlooked the fact that this PBG can still grow and
add additional partitions until it reaches the maximum
partition number. This can lead DB2 mistakenly thinking
it has the gross lock on the whole PBG table space
and then making updates without proper locking.
Fixes made in DB2, so that when lock escalation happens on a
PBG, DB2 won't consider it has the gross lock on this PBG,
unless all its partitions, upto and including the maximum,
are x or s locked.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38328
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILKES PI38328
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38328 DSNILKES
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILKES
LISTEND
UI27006 COVER LETTER END
UI27008 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38662 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users. *
****************************************************************
* PROBLEM DESCRIPTION: Internal check log / force log *
1 * processing may not externalize *
* the log to the requested RBA. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 internal processing may request that the log buffers be
written to disk up to a specified log RBA value. In certain
situations where a partially full log buffer has already been
written to disk, the request may be ignored if it is for an
RBA that is within the same buffer (log CI) that has already
been written. The results of this are typically benign, but
may cause inconsisteny abends if it happens and a system
failure prevents the log CI from being externalized later. In
the reported scenario, a GBP write to the coupling facility
completed, but the coresponding check log did not write the
updated log CI to disk before the subsystem failed.
Reported symptoms include:
MSGDSNU709I, ABEND04E RC00C90101 ERQUAL5033 in DSNKINSL,
Inconsistency between an index and a table, i.e., a row with
no matching index entry or an index entry with no matching
row in the base table.
Check log / log force processing has been updated to take into
account multiple requests to write the same log CI when there
have been additional log records moved into that CI.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38662
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNJW101 PI38662
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38662 DSNJW101
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNJW101
LISTEND
UI27008 COVER LETTER END
UI27053 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI23551 -
****************************************************************
* USERS AFFECTED: ALL DB2 10 and DB2 11 for z/OS users using *
* UNIQUE indexes and INCLUDE columns are *
* present. *
****************************************************************
* PROBLEM DESCRIPTION: SQLERRD(3) in SQLCA was incorrectly set *
* during SQL UPDATE and UNIQUE INDEX with *
1 * INCLUDE column(s) was used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SQLERRD(3) in SQLCA, number of rows affected, was incorrectly
set during SQL UPDATE and UNIQUE INDEX with INCLUDE column(s)
was used.
The key comparison routine incorrectly compared the INCLUDE
portion of the key and caused rows counter to incorrectly
increase.
Additional Keywords: DB2INCORR/K, INCORROUT, SQLINCORROUT
SQLINCLUDE, SQLUPDATE
The index key comparison routine has been updated to correctly
compare keys when INCLUDE columns are present during an SQL
UPDATE.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI23551
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKBULD PI23551
DSNKCEST PI23551
DSNKDLE PI23551
DSNKFLRR PI23551
DSNKFLST PI23551
DSNKFPRV PI23551
DSNKFTCH PI23551
DSNKFTRR PI23551
DSNKINSL PI23551
DSNKLFPR PI23551
DSNKLOD2 PI23551
DSNKNXT2 PI23551
DSNKPOSI PI23551
DSNKREST PI23551
DSNKTRAV PI23551
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI23551 DSNKBULD DSNKCEST DSNKDLE DSNKFLRR DSNKFLST DSNKFPRV
DSNKFTCH DSNKFTRR DSNKINSL DSNKLFPR DSNKLOD2 DSNKNXT2
DSNKPOSI DSNKREST DSNKTRAV
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKBULD
DSNKCEST
DSNKDLE
DSNKFLRR
DSNKFLST
DSNKFPRV
DSNKFTCH
1 DSNKFTRR
DSNKINSL
DSNKLFPR
DSNKLOD2
DSNKNXT2
DSNKPOSI
DSNKREST
DSNKTRAV
LISTEND
UI27053 COVER LETTER END
UI27070 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI33465 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER utility *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C7 at DSNIRFNX + 'B4AC'x during *
* REBUILD INDEX ALL of a multi-piece *
* segmented table space after it was *
* recovered by RECOVER TOLOGPOINT using a *
* system-level backup (SLB) as a recovery *
* base. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran RECOVER TOLOGPOINT utility to recover a multi-piece
segmented table space. The RECOVER utility chose an SLB as the
recovery base for the object and completed successfully. A
following REBUILD INDEX ALL utility abended with ABENDS0C7 at
DSNIRFNX OFFSETB4AC because only the data set name of the first
piece of the object contained the correct instance prefix (first
character of the fifth-level qualifier in the data set name, can
be 'I' or 'J') after the table space was recovered.
The problem occurred because a REORG with default option
FASTSWITCH YES was run against the table space after the SLB was
taken, so the current instance prefix of the table space was
different than the instance prefix of the data sets included in
the SLB, and RECOVER TOLOGPOINT utility only changed the data
set name of the first piece of the object to use the current
instance prefix.
RECOVER TOLOGPOINT has been modified to change all the pieces
of a segmented table space restored from an SLB to use the
correct instance prefix.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI33465
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
The PTF for APAR PI33465 has modified CSECTs in both the
DSNUT101 and DSNUTILA load modules, affecting the
1 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
DSNUCAIN PI33465
DSNUCALA PI33465
DSNUCARS PI33465
DSNUCBMT PI33465
DSNUCBRT PI33465
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI33465 DSNUCAIN DSNUCALA DSNUCARS DSNUCBMT DSNUCBRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCAIN
DSNUCALA
DSNUCARS
DSNUCBMT
DSNUCBRT
LISTEND
UI27070 COVER LETTER END
UI27120 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI35773 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of TEMPORAL TABLE with RANGE LIST *
* access type (ACCESSTYPE = 'NR' in *
* PLAN_TABLE). *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXORGL *
* P110 may occur when a query contains *
* a temporal table with range list *
* access type after APAR PI25244 is *
* applied. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E70005 at DSNXORGL:P110 may occur when a query
contains a temporal table with range list access type after
APAR PI25244 is applied.
1 When DB2 process the information set for the temporal table
predicate, it does not handle it correctly.
Following is an example of such failing scenario:
CREATE TABLE MYTAB01
(C1 CHAR(2),
C2 CHAR(2),
C3 CHAR(2),
SYS_BEG_D TIMESTAMP(12) NOT NULL,
SYS_END_D TIMESTAMP(12) NOT NULL,
PERIOD SYSTEM_TIME (SYS_BEG_D, SYS_END_D) );
CREATE INDEX IDX01 ON MYTAB01
(C1, C2, SYS_BEG_D);
CREATE TABLE MYTAB01_HST
(C1 CHAR(2),
C2 CHAR(2),
C3 CHAR(2),
SYS_BEG_D TIMESTAMP(12) NOT NULL,
SYS_END_D TIMESTAMP(12) NOT NULL );
CREATE INDEX IDX01_HST ON MYTAB01_HST
(C1, C2, SYS_BEG_D);
SELECT *
FROM MYTAB01
FOR SYSTEM_TIME BETWEEN '0001-01-01-00.00.00.000000000000'
AND '9999-12-31-00.00.00.000000000000'
WHERE C1 = 'AA'
AND ( (C2 > 'MM')
OR ( C2 = 'CC'
AND SYS_BEG_D > '1990-01-01-00.00.00.000000000000')
) ;
DB2 has been modified to process the temporal predicate
correctly for the range list access type.
Additional Keywords: SWLSPTT SQLAPTT SQLBITEMPORAL
SQLRANGELIST
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35773
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI35773:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI35773 corrects a problem of ABEND04E RC00E70005 AT DSNXORGL
P110 when using a TEMPORAL table with RANGE LIST ACCESS TYPE.
To make this fix effective for a static application, it must 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 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXORGL PI35773
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35773 DSNXORGL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXORGL
LISTEND
UI27120 COVER LETTER END
UI27166 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30965 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users of hash-organized *
* table spaces *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISHPI ERQUAL500A *
* or DSNISGSC ERQUAL5017 may occur *
* because DB2 was trying to insert a *
* record to a page in hash home area, *
* which was supposed to be inserted to *
* an overflow page. *
* This is due to the wrong segment number *
* when determining an overflow candidate *
* page. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 tries to insert a record to an overflow area page after the
record is rejected to be inserted to pages in hash home area.
While determining an overflow candidate page, the segment
number was wrong, which led to the candidate page located in
hash home area. Then ABEND04E RC00C90101 at DSNISHPI ERQUAL500A
or ABEND04E RC00C90101 DSNISGSC ERQUAL5017 may occurr.
DB2 code is changed to add sanity check to ensure the space
search process only searching hash over flow space if it is
a record that can not fit into its hash home page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30965
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 PI30965
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30965 DSNISGSC
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGSC
LISTEND
UI27166 COVER LETTER END
UI27208 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI34115 -
INTEGRITY PROBLEM
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34115
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
INTEGRITY:
INTEGRITY SET: UI27208,UI27258
ACTION:
Run the following query:
SELECT SUBSTR(R.SCHEMA||'.'||R.NAME,1,36) TRIGGER
, SUBSTR(R.TBOWNER||'.'||R.TBNAME,1,36) TABLE
, SUBSTR(R.OWNER,1,10) OWNER
FROM SYSIBM.SYSTRIGGERS R
WHERE NOT EXISTS(SELECT 1 FROM SYSIBM.SYSTABAUTH TA
WHERE R.TBNAME = TA.TTNAME
AND R.TBOWNER = TA.TCREATOR
AND ( (R.OWNER = TA.GRANTEE AND
R.OWNERTYPE = TA.GRANTEETYPE)
OR
(TA.GRANTEETYPE = ' ' AND
TA.GRANTEE = 'PUBLIC')
)
AND TA.SELECTAUTH <> ' '
)
AND NOT EXISTS(SELECT 1 FROM SYSIBM.SYSUSERAUTH UA
WHERE ( (R.OWNERTYPE = UA.GRANTEETYPE AND
R.OWNER = UA.GRANTEE)
OR
(UA.GRANTEETYPE = ' ' AND
UA.GRANTEE = 'PUBLIC')
)
AND (UA.SYSADMAUTH <> ' ' OR
UA.DATAACCESSAUTH <> ' '
)
)
AND NOT EXISTS(SELECT 1 FROM SYSIBM.SYSDBAUTH DA
, SYSIBM.SYSTABLES T
WHERE R.TBNAME = T.NAME
AND R.TBOWNER = T.CREATOR
AND T.DBNAME = DA.NAME
1 AND ( (R.OWNERTYPE = DA.GRANTEETYPE AND
R.OWNER = DA.GRANTEE)
OR
(DA.GRANTEETYPE = ' ' AND
DA.GRANTEE = 'PUBLIC')
)
AND DA.DBADMAUTH <> ' '
)
AND XMLEXISTS(
'if (fn:matches($s,"REFERENCING +OLD
","i")) then(1)
else
if (fn:matches($s,"REFERENCING +NEW
","i")) then(1)
else
if (fn:matches($s,"REFERENCING +OLD_TABLE
","i"))
then(1)
else
if (fn:matches($s,"REFERENCING +NEW_TABLE
","i"))
then(1)
else ()'
PASSING XMLCAST(R.STATEMENT AS XML) as "s");
To make this fix effective, after application of this PTF,
for each qualified trigger from the above query, issue REBIND
TRIGGER PACKAGE command without the EXPLAIN(ONLY) specification
to its trigger package.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOTG PI34115
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34115 DSNXOTG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOTG
LISTEND
UI27208 COVER LETTER END
UI27289 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38592 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of queries *
* that can use a sparse index. *
****************************************************************
* PROBLEM DESCRIPTION: An intermittent incorrect result can *
* occur for a query that uses a sparse *
* index for a large volume of data if the *
* sparse index chooses the combination of *
* using both an in-memory and physical *
* workfile for sort processing. *
****************************************************************
* RECOMMENDATION: *
1 ****************************************************************
An incorrect result can occur intermittently for a query that
uses a sparse index when a large volume of data is involved if
the sparse index chooses to use the combination of both
in-memory and physical workfiles.
In the reported case, the result is considered incorrect because
only a single decimal value in 125k rows of output is not as
expected. Also, the incorrect result did not occur if the
MXDTCACH zparm is set to a value of 0 in which case DB2 would
use only physical workfiles for the sparse index but performance
may be less than desirable.
Also, increasing the value of MXDTCACH is a possible workaround.
This would allow DB2 to allocate enough in-memory workfile
space. However, the failing case is when both in-memory and
physical workfiles are used for the sparse index since the query
references a large volume of data and the MXDTCACH is set to the
default value of 20. It should be noted that it is still
possible to use both kinds of workfiles even if MXDTCACH is set
to its maximum (512) if the volume of data is extremely large.
The underlying cause of the problem occurs when sparse index
processing needs to hash into both kinds of workfiles and if
duplicates and collisions are present, the collisions are not
handled properly.
DB2 has been modified to walk the collision chain correctly when
dividing the sparse index between in-memory and physical
workfiles to make sure it moves over all duplicates correctly.
This will prevent the incorrect result that can occur.
Additional Keywords: SQLSPARSEINDEX SPARSEINDEX
INCORROUT SQLINCORR
SQLINCORROUT DB2INCORR/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38592
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXSMRE PI38592
DSNXSMRG PI38592
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38592 DSNXSMRE DSNXSMRG
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSMRE
DSNXSMRG
LISTEND
UI27289 COVER LETTER END
1
UI27412 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI39542 -
****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who have *
* applied PI30859/UI26382 and who: *
* (1) Use views created in DB2 for *
* z/OS V8 or later. *
* Or, *
* (2) Use query acceleration and have *
* an accelerated query with the *
* converted accelerated query text *
* longer than 32K bytes. *
****************************************************************
* PROBLEM DESCRIPTION: After PI30859/UI26382 is applied, *
* the following issues may occur: *
* (1) during BIND or PREPARE time an *
* ABEND04E RC00E70005 in DSNXOV0:M101 *
* may occur for an SQL statement that *
* references a view created in *
* DB2 for z/OS V8 or later. *
* (2) With PTF for IBM DB2 Analytics *
* Accelerator APAR PI30282 applied, *
* SQLCODE -725 may occur when *
* executing an accelerated query with *
* converted statement text longer *
* than 32K bytes. *
****************************************************************
* RECOMMENDATION: Apply the corrective PTF when it is *
* available. *
****************************************************************
After PI30859/UI26382 is applied:
(1) During BIND or PREPARE time, an ABEND04E RC00E70005 in
DSNXOV0:M101 may occur for an SQL statement that references
a view created in DB2 V8 or later.
(2) With PTF for IBM DB2 Analytics Accelerator APAR PI30282
applied, SQLCODE -725 may occur when executing an
accelerated query with converted statement text longer
than 32K bytes. This is caused by incorrect pointer
assignment that causes incorrect serviceability texts
to be propagated to the accelerator.
Keywords:
ABEND04E SQLVIEW IDAAV4R1/K
DB2 code is fixed so that the abend and SQLCODE -725
as described in the scenarios above do not occur.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI39542
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 DSNXEDS1 PI39542
DSNXOV0 PI39542
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI39542 DSNXEDS1 DSNXOV0
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDS1
DSNXOV0
LISTEND
UI27412 COVER LETTER END
UI27526 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI36222 -
****************************************************************
* USERS AFFECTED: DB2 10 and 11 for z/OS users who have *
* applied PI11316/UI19815/UI19816. *
****************************************************************
* PROBLEM DESCRIPTION: PI11316/UI19815/UI19816 is missing *
* ++HOLD information that instructs users *
* to drop and recreate affected indexes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
APAR PI11316's closing text states that users are required to
drop and recreate user-created catalog indexes in
DB2 10 enabling new-function mode and higher after applying
PI11316/UI19815/UI19816. However, the APAR's ++HOLDs
inadvertently omitted such instructions and users may not be
aware they need to drop and recreate these indexes until
PI11316's pre-migration check jobs warn them to.
The ++HOLDs have been updated to instruct users to drop and
recreate the affected indexes. No DB2 code or logic has been
modified.
The following is the added text for the DB2 10 ++HOLD:
DB2 is modified to make all new catalog indexes DB2-managed and
be created in the DB2 catalog data space. Applying this PTF does
not convert existing user-created catalog indexes. In DB2 10
enabling new-function mode and higher, these indexes must be
dropped and recreated for them to function correctly. Please
refer to APAR PI11316 for additional details.
The following is the added text for the DB2 11 ++HOLD:
DB2 is modified to make all new catalog indexes DB2-managed and
be created in the DB2 catalog data space. Applying this PTF
does not convert existing user-created catalog indexes. These
indexes must be dropped and recreated for them to function
correctly. Please refer to APAR PI11316 for additional details.
1
Additional Keywords:
SQLMIGRATION
DB2MIGV10/K
DB2MIGV11/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI36222
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
ACTION:
DB2 is modified to make all new catalog indexes DB2-managed and
be created in the DB2 catalog data space. Applying this PTF does
not convert existing user-created catalog indexes. In DB2 10
enabling new-function mode and higher, these indexes must be
dropped and recreated for them to function correctly. Please
refer to APAR PI11316 for additional details.
This PTF modifies the DB2 10 premigration check-out job,
DSNTIJPM. If you maintain a customized copy of this job, then
after applying this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPM
- Delete all lines and copy in the DSNTIJPM member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 10, run the updated
customized job to check for conditions that might affect your
migration.
This PTF also modifies the DB2 11 premigration check-out job,
DSNTIJPB. If you maintain a customized copy of this job, then
after applying this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPB
- Delete all lines and copy in the DSNTIJPB member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 11, run the updated
customized job to check for conditions that might affect your
migration.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNTIJPM PI36222
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI36222 DSNTIJPM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MACROS
DSNTIJPM
LISTEND
UI27526 COVER LETTER END
1
UI27718 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI37899 -
****************************************************************
* USERS AFFECTED: DB2 for z/OS V10 users of static plans or *
* packages that involve view or table *
* materialization, if those packages were *
* last bound on V8. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNGDVRT ERQUAL5005 *
* or SQL ERROR CODE -404 issued *
* incorrectly for SQL statements *
* involving materialized table or view *
* when running static packages or plans *
* bound on V8 and with PTF UI19029 *
* applied. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Plans or packages executing in DB2 V10 that involve view or
table materialization and were last bound in DB2 V8 can
result in an internal inconsistency processing the length
of variable length columns, resulting in
RC00C90101 DSNGDVRT ERQUAL5005 or SQL ERROR CODE -404.
This problem only occurs in V10 for plans or packages bound
in V8, and only if PTF UI19029 is applied.
Code has been changed in V10 to correctly handle the length of
variable length columns during view or table materialization
for static applications last bound in V8.
Additional keywords: SQLVIEW SQLCTE SQLCODE404
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI37899
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 PI37899
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI37899 DSNIWKFL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIWKFL
LISTEND
UI27718 COVER LETTER END
UI27719 COVER LETTER START
PROBLEM DESCRIPTION(S):
1 PI34082 -
****************************************************************
* USERS AFFECTED: All DB2 V11 and DB2 V10 for z/OS users of *
* real time statistic data *
****************************************************************
* PROBLEM DESCRIPTION: The value of NPAGES in the *
* SYSIBM.SYSTABLESPACESTATS table *
* is greater than the value of *
* NACTIVE column *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The NPAGES value of the SYSIBM.SYSTABLESPACESTATS table is
maintained during DML operations.
This counter is incremented when the first active row is
inserted into the page. However, there is a scenario that can
result in a page being counted multiple times during an insert
operation. This is because the counter is incremented by
multiple transactions first before the target data page is
serialized. As a result, the value can be larger than NACTIVE.
DB2 code is changed to delay counting the page until record
is inserted to a page.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI34082
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 PI34082
DSNISMRT PI34082
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI34082 DSNISGRT DSNISMRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGRT
DSNISMRT
LISTEND
UI27719 COVER LETTER END
UI27750 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI36937 -
****************************************************************
* USERS AFFECTED: All DB2 for z/OS users of segmented table *
* spaces running inserts across data sharing *
* members. *
****************************************************************
* PROBLEM DESCRIPTION: A table space scan did not show any *
* rows in the table but index access *
* did find data rows. *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
For segmented table spaces under page level locking (PLL), DB2
attempts to avoid unnecessary overhead when processing the space
map page. There was a narrow timing window when a space map
entry for a data page was marked as empty on a rollback on one
data sharing member. A second member reused that data page but
was referencing an old copy of the space map page. On the first
insert to that data page, the second member did not detect that
the space class entry had changed. As a result the new changes
to the space map were not written out. A subsequent table space
scan would then skip over that data page as the space map entry
shows an empty status.
DB2 code has been changed to update the space map page under
this narrow timing window.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI36937
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 PI36937
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI36937 DSNISGRT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNISGRT
LISTEND
UI27750 COVER LETTER END
UI27759 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI35093 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of the UNLOAD TABLESPACE FROMCOPY *
* utility with PI13075/UI17926/UI17927 applied *
****************************************************************
* PROBLEM DESCRIPTION: Message DSNU1211I - INPUT DATA SET IS *
* NOT AN IMAGE COPY and RC8 during an *
* UNLOAD TABLESPACE FROMCOPY utility *
* when the COPY is of a partitioned table *
* space and HPGDSSZ='00000000'x and *
* PI13075 UI17926/UI17927 is applied. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available *
****************************************************************
After applying PI13075 (UI17926/UI17927) an UNLOAD TABLESPACE
FROMCOPY utility failed with MSGDSNU1211I - INPUT DATA SET IS
1 NOT AN IMAGE COPY and ended with RC8. The table space was
created partitioned with DSSIZE 8G in DB2 for z/OS V8 and had
not been REORGed after migrating to DB2 10 for z/OS. The
header page contained HPGDSSZ='00000000'x.
PI13075 modified UNLOAD to use the DSSIZE value from the header
page of the COPY to avoid problems when calculating the
partition number from the DSSIZE when an ALTER TABLESPACE DSSIZE
occurs after the COPY was taken. If HPGDSSZ was zero, UNLOAD
used a default value for DSSIZE. This caused a problem for
table spaces that were created (or altered) with a DSSIZE that
was not a default value.
UNLOAD TABLESPACE FROMCOPY utility code has been modified
to no longer use a default value for DSSIZE if HPGDSSZ=0
and instead will use the current information from the OBD.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35093
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNUULCB PI35093
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35093 DSNUULCB
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUULCB
LISTEND
UI27759 COVER LETTER END
UI27781 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI39512 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* application-period temporal tables. *
****************************************************************
* PROBLEM DESCRIPTION: A delete from an application-period *
* temporal table can delete an entire row *
* although the statement specified a *
* period-clause. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An incorrect result can be returned for a query that references
a temporal table following a DELETE operation against it that
contains an IN-List and uses IN-List access.
The following example helps to illustrate a failing case.
1 Step 1. Create a temporal table.
CREATE TABLE INFO (
INFO_ID DECIMAL(11, 0) NOT NULL
,INFO_STARTDATE DATE NOT NULL
,INFO_ENDDATE DATE NOT NULL
...
,PERIOD BUSINESS_TIME(INFO_STARTDATE, INFO_ENDDATE)
,PRIMARY KEY (INFO_ID,
BUSINESS_TIME WITHOUT OVERLAPS) ) ;
Step 2. Insert a row of data into the table.
INSERT INTO INFO
VALUES(1234567.,'2014-03-01','2014-09-01',...);
So, we start with the INFO Table containing a single row.
+----------------------------------------------
| INFO_ID | INFO_STARTDATE | INFO_ENDDATE |
+----------------------------------------------
1_| 1234567 | 2014-03-01 | 2014-09-01 |
+----------------------------------------------
Step 3. Create an additional table and insert a row of data.
CREATE TABLE INFO_CTL (
INFO_ID DECIMAL(11, 0) NOT NULL
...
, PRIMARY KEY (INFO_ID) );
INSERT INTO INFO_CTL VALUES(1234567., ... );
Step 4. Perform the following DELETE against the temporal table
that contains an IN-List.
DELETE FROM INFO FOR PORTION OF BUSINESS_TIME FROM
'2014-06-03' TO '2014-08-15'
WHERE INFO_ID IN (SELECT B.INFO_ID FROM INFO_CTL B) ;
Step 5. Check the results of the temporal table.
SELECT * FROM INFO
WHERE INFO_ID IN(
SELECT B.INFO_ID
FROM INFO_CTL B,
...
WHERE ... );
This query incorrectly returns 0 rows.
1 The expected results should be two rows as follows.
+-----------------------------------------------
| INFO_ID | INFO_STARTDATE | INFO_ENDDATE |
+-----------------------------------------------
1_| 1234567 | 2014-03-01 | 2014-06-03 |
2_| 1234567 | 2014-08-15 | 2014-09-01 |
+-----------------------------------------------
The problem occurs when performing the DELETE operation against
the temporal table with IN-List access. DB2 is treating the
'delete' as a normal table delete instead of a temporal table
delete.
Please note: This problem was reported when the INFO Table has
an access type of "IN-List" for the DELETE operation. Other
incorrect results can occur depending on how the 'deleted
portion' brackets the version dates. Similar problems can occur
when performing an UPDATE instead of a DELETE.
The code in DB2 bind time is modified to correct the problem
when deleting from or updating a temporal table when using
IN-List access. This will allow the proper result to be
returned when querying the temporal table following a delete
from the table.
Additional Keywords: SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLBITEMPORAL SQLDELETE
SQLUPDATE SQLINLIST SQLINSUBQ
SQLTEMPORAL
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI39512
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI39512:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI39512 corrects a problem that can occur when modifying a
temporal table via an UPDATE or DELETE operation when using
IN-List access.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXGRTM PI39512
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI39512 DSNXGRTM
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
MODULES
DSNXGRTM
LISTEND
UI27781 COVER LETTER END
UI27888 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI35450 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically where an SQL statement is *
* associated to an ALIAS that resolves to a *
* remote server. *
* *
* DB2 10 for z/OS and DB2 11 for z/OS users *
* only. *
****************************************************************
* PROBLEM DESCRIPTION: A query executing at a remote server, *
* via an SQL ALIAS, may receive *
* SQLCODE -104 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Storage containing the modified, ALIAS related, statement was
prematurely freed and its corresponding pointer was cleared.
Subsequent processing used the null pointer as part of building
the SQLDA for the remote server. The incorrect information was
sent to the remote server resulting in the detection of an
SQLCODE -104 condition.
DB2 was modified to defer the free of the storage containing the
modified statement that is associated to an ALIAS.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI35450
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 PI35450
DSNXEDS1 PI35450
DSNXEPM PI35450
DSNXERT2 PI35450
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI35450 DSNXEDP DSNXEDS1 DSNXEPM DSNXERT2
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDP
DSNXEDS1
DSNXEPM
DSNXERT2
1
LISTEND
UI27888 COVER LETTER END
UI27936 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38037 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/os and DB2 11 for z/os *
* users using tables with referential *
* constraints. *
****************************************************************
* PROBLEM DESCRIPTION: Rows were inserted into the dependent *
* table while there was no parent row in *
* the parent table. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem could happen when there is an unique
where not null index defined on the dependent table
as the foreign key index. When inserting into the
dependent table, if the key being inserted has
the same value as an existing key with a pseudo delete
rid in the foreign key index, DB2 code could skip the
parent table checking, so a row could be inserted into
the dependent table while there is no corresponding
parent row in the parent table.
DB2 code has been updated to always perform the referential
constraint checking on the parent table when inserting
into the dependent table and the foreign key index is
defined as an unique where not null index.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38037
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNKINSL PI38037
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38037 DSNKINSL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKINSL
LISTEND
UI27936 COVER LETTER END
UI27999 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI37046 -
1 ****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users using *
* partitioned indexes. *
****************************************************************
* PROBLEM DESCRIPTION: Multiple symptoms may occur during *
* RECOVER INDOUBT processing: *
* - ABEND04E RC00C90101 DSNIDBMF *
* ERQUAL500B *
* - ABEND0C4 RC00000038 DSNB1LPL *
* OFFSET0B5C OFFSET0C02 *
* - ABEND04E RC00C90101 DSNIARPL *
* ERQUAL5008 *
* - Bring DB2 subsystem down MSGDSNV086 *
* RC00D98001 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Multiple symptoms may occur during RECOVER INDOUBT processing:
- ABEND04E RC00C90101 DSNIDBMF ERQUAL500B
- ABEND0C4 RC00000038 DSNB1LPL OFFSET0B5C OFFSET0C02
- ABEND04E RC00C90101 DSNIARPL ERQUAL5008
- Bring DB2 subsystem down MSGDSNV086 RC00D98001
During abort processing of transaction, a read error was
detected and DB2 attempted to write a compensation log record
that did not correspond to the current log record being
processed. The partition number was calculated based on the page
held and not the log record attempting to undo.
Additional keywords: DB2TERM DB2ABTERM
Index manager has been updated to correctly write compensation
log records when read error is detected.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI37046
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIUSME PI37046
DSNKINUR PI37046
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI37046 DSNIUSME DSNKINUR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIUSME
DSNKINUR
LISTEND
UI27999 COVER LETTER END
1UI28022 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI40695 -
****************************************************************
* USERS AFFECTED: All Users of DB2 10 and DB2 11 for z/OS. *
****************************************************************
* PROBLEM DESCRIPTION: DB2 restart does not always honor *
* Postponed Abort (PA) request. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During DB2 restart, regardless of restart light or normal
restart, long running Unit of Recovery (UR) does not always get
postponed. This is due to incorrect logic that decides when to
override the postponed abort. This restart code logic does not
always involve in this overriding decision making. That is why
users will not see this anomaly all the time. The specific
condition that is most likely to surface this problem is when
DB2 member's Relative Byte Offset (RBA) is higher than Log
Record Sequence Number (LRSN). To avoid this problem, DB2
restart log apply logic is corrected to always provide RBA value
to the routine that decides whether or not to override the
default or user supplied values for postpone abort in the ZPARM.
DB2 restart logic for Postpone Abort UR is modified to avoid
unnecessary long back out recovery time.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI40695
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNILHIS PI40695
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI40695 DSNILHIS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNILHIS
LISTEND
UI28022 COVER LETTER END
UI28034 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI36752 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users of RECOVER LIST utility. *
****************************************************************
* PROBLEM DESCRIPTION: RECOVER utility on a list of table *
* spaces failed with ABEND04E RC00C200E2 *
1 * when the last object to be restored has *
* a system level backup (SLB) as recovery *
* base. *
****************************************************************
* RECOMMENDATION: Apply corrective PTF when available. *
****************************************************************
User ran RECOVER utility on a list of objects, some of
which had a FlashCopy Image Copy (FCIC) as a recovery base
while the last object in the list had a system level backup
(SLB) as its recovery base. RECOVER failed with ABEND04E
RC00C200E2 because RECOVER mistakenly proceeded as though all
FCIC restores were complete when a SLB was used to restore
the last object in the list.
RECOVER utility code has been modified to correctly restore
objects with a FlashCopy Image Copy when the last object in
the list has a system level backup as its recovery base.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI36752
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 PI36752
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI36752 DSNUCBMT
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNUCBMT
LISTEND
UI28034 COVER LETTER END
UI28096 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38584 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL *
* statement that contains an arithmetic *
* expression with subtraction involving a *
* DATETIME and CHAR or VARCHAR operands. *
****************************************************************
* PROBLEM DESCRIPTION: In V10 and V11, the following problems *
* can occur. *
* *
* An ABEND0C7 RC00000000 at location *
* DSNXGRDS DSNXRDTF OFFSET4192 can occur *
* when executing a compiled SQL scalar *
* function or native SQL procedure *
* containing a Datetime arithmetic *
* expression with a subtraction operator. *
* *
1 * An SQLCODE -180 can be issued *
* incorrectly when binding an SQL *
* statement containing a Datetime *
* arithmetic expression with a *
* subtraction operator. *
* *
* *
* In V10, the following problems can also *
* occur. *
* *
* An unexpected SQLCODE -407 can be *
* issued when executing an SQL statement *
* containing a Datetime arithmetic *
* expression with a subtraction operator. *
* *
* Also, an incorrect result can be *
* returned when executing an SQL *
* statement containing a basic predicate *
* or BETWEEN predicate. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The following specifics help to further identify each problem.
The ABEND0C7 in DSNXRDTF problem is dependent on one of the
operands being an SQL variable which is a CHAR or VARCHAR.
The SQLCODE180 problem is dependent on one of the operands being
a special register CHAR or VARCHAR, a scalar fullselect with a
CHAR or VARCHAR result, or in V11 a global variable being a CHAR
or VARCHAR.
The SQLCODE407 problem in V10 is dependent on one of the
operands to be a CHAR or VARCHAR host variable or an SQL
variable having a NULL value.
The incorrect result problem in V10 is dependent on one of the
objects in the predicate or BETWEEN clause to be a non-column
expression to have a NULL value.
The following examples help to illustrate the listed problems.
Example 1.
An ABEND0C7 is issued while executing a CALL PROCEDURE
statement.
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
DECLARE IN_RFRSH_CHAR CHAR(10);
SET IN_RFRSH_CHAR = '2015-04-20';
SET NUM = (IN_RFRSH_CHAR - CURRENT DATE);
END!
Example 2.
1 An SQLCODE -180 is issued incorrectly from DSNXOLTD
while binding this statement.
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
SELECT CURRENT APPLICATION COMPATIBILITY - CURRENT DATE
INTO NUM FROM
SYSIBM.SYSDUMMY1;
END!
Please note that with this apar, the SQLCODE -180 will be
issued at execution time from DSNXRTIM when executing the
CALL PROCEDURE statement.
Example 3.
An unexpected SQLCODE -180 is issued while binding this
statement.
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
SELECT (SELECT '2015-08-25'
FROM SYSIBM.SYSDUMMY1) - CURRENT DATE
INTO NUM FROM
SYSIBM.SYSDUMMY1;
END!
Example 4.
In V11, an unexpected SQLCODE -180 is issued while binding
this statement.
CREATE VARIABLE VAR1 CHAR(10)!
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
SET VAR1 = '2015-04-30';
SELECT VAR1 - CURRENT DATE INTO NUM
FROM SYSIBM.SYSDUMMY1;
END!
Example 5.
In V10, an unexpected SQLCODE -407 is issued while executing
this CALL PROCEDURE statement.
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
DECLARE IN_RFRSH_CHAR CHAR(10) DEFAULT NULL;
DECLARE CRS1 CURSOR FOR
SELECT 6 FROM T1
WHERE 0 <> IN_RFRSH_CHAR - CURRENT DATE;
OPEN CRS1;
FETCH CRS1 INTO NUM;
END!
1 Example 6.
In V10, an incorrect result can be returned while executing
this CALL PROCEDURE statement.
CREATE TABLE T1(C1 INT);
INSERT INTO T1 VALUES(1);
CREATE PROCEDURE MYTEST2 (INOUT NUM INT)
BEGIN
DECLARE DATE_1 DATE DEFAULT NULL;
DECLARE CRS1 CURSOR FOR
SELECT 6 FROM T1
WHERE C1 <> DATE_1 - CURRENT DATE;
OPEN CRS1;
FETCH CRS1 INTO NUM;
END!
Please note that with this apar, the incorrect result for NUM of
6 will not be returned. Instead, an SQLCODE100 (row not found)
will be returned.
DB2 does not process an arithmetic expression with a subtraction
operator properly which can result in an abend, unexpected
SQLCODE, or an incorrect result.
DB2 has been modified to process an arithmetic expression with a
subtraction operator properly so as to avoid an abend,
unexpected SQLCODE, or incorrect result.
Additional keywords: SQLTIME SQLDATE SQLMINUS SQLTIMESTAMP
SQLTIMESTAMPTZ SQLSP SQLSTOREDPROC
SQLNATIVESQLPL SQLUDF
SQLCODE180 SQLCODE407 SQLCODE100
SQLINCORR INCORROUT SQLINCORROUT
DB2INCORR/K SQLHOSTVAR SQLNOTNULL
SQLSCALAR SQLFULLSELECT SQLSCALARFULSEL
SQLSPECIALREG
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38584
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI38584:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI38584 corrects the following problems in V10:
An ABEND0C7 RC00000000 at location DSNXGRDS DSNXRDTF OFFSET4192
can occur when executing a compiled SQL scalar function or
native SQL procedure containing a Datetime arithmetic expression
with a subtraction operator.
An unexpected SQLCODE -407 can be issued when executing an SQL
statement containing a Datetime arithmetic expression with a
1 subtraction operator.
Also, an incorrect result can be returned when executing an SQL
statement containing a basic predicate or BETWEEN 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.
ACTION:
PI38584 corrects the following problems in V10:
An ABEND0C7 RC00000000 at location DSNXGRDS DSNXRDTF OFFSET4192
can occur when executing a compiled SQL scalar function or
native SQL procedure containing a Datetime arithmetic expression
with a subtraction operator.
An unexpected SQLCODE -407 can be issued when executing an SQL
statement containing a Datetime arithmetic expression with a
subtraction operator.
Also, an incorrect result can be returned when executing an SQL
statement containing a basic predicate or BETWEEN predicate.
To make the fix effective for a native SQL PL, ALTER PROCEDURE/
FUNCTION REGENERATE statement can be used to regenerate the SQL
PL.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOMEX PI38584
DSNXOSDA PI38584
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38584 DSNXOMEX DSNXOSDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOMEX
DSNXOSDA
LISTEND
UI28096 COVER LETTER END
UI28171 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI36863 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS users that applied the *
* PI28425/UI24674 fix for Explain stored *
* procedure DSNAEXP will be affected. *
****************************************************************
* PROBLEM DESCRIPTION: SQLCODE805 RC=02 when calling SQLSP *
* DSNAEXP after PI28425/UI24674 is *
* applied (missing DBRM). *
1 ****************************************************************
* RECOMMENDATION: *
****************************************************************
After applying PI28425/UI24674 fix, a customer's program got
an exception message SQLCODE805 with RC=2 in regards to the
missing DBRM for the Explain stored procedure DSNAEXP.
Here is the example for the exception message:
"
The following error occurred when running stored procedure
SYSPROC.DSNAEXP. SQLCODE: -805; SQLSTATE: 51002. Resolve
this error and do operation again.
SQLCODE = -805
...
"
DSN@EXPL macro that handles DBRM for DSNAEXP was missing
from the fix as well as the ++HOLD card that requires a
rebind for the DBRM DSNAEXP was also missing.
Additional keywords:
SQLCODE805 DSNAEXPL
This fix corrects the missing DSN@EXPL macro in
PI28425/UI24674 fix for the Explain stored
procedure DSNAEXP and also added a ++HOLD card
requirement for the rebind DBRM DSNAEXP.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI36863
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> This action is required for all DB2 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
1 the PREVIEW option or customize and run the generated job.
---------------------------------------------------------------
(2) Refresh the WLM environment
---------------------------------------------------------------
************************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.
ACTION:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> 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
***********************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.
----------------------------------------------------------------
ACTION:
1 ---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> This action is required for all DB2 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
***********************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN@EXPL PI36863
DSNAEXPL PI36863
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI36863 DSN@EXPL DSNAEXPL
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNAEXPL
MACROS
DSN@EXPL
LISTEND
UI28171 COVER LETTER END
UI28188 COVER LETTER START
1 PROBLEM DESCRIPTION(S):
PI41828 -
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
****************************************************************
* PROBLEM DESCRIPTION: Abend 0C4-00000038 DSNLTPAI+0108 *
* followed by DB2 abnormal termination *
* with reason code 00F30420. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An IMS, CICS, or RRS based DB2 application updates data at a
remote server via DDF. The remote server, such as another DB2
for z/OS, also supports distributed Two Phase Commit protocols.
The application environment commits its changes but happens to
abend after phase 1, but before phase 2, of commit. The
associated DB2 allied thread must therefore be placed in an
indoubt state in which case DSN3TM00 is involved. DSNLTPAI
must also be involved due to the remote resources that are also
indoubt. If the residual (high half) contents of 64-bit
register 1 happens to be non zero, DSN3TM00 will pass an
invalid pointer value to DSNLTPAI which causes abend
0C4-00000038 DSNLTPAI+0108. The abend leads to a DB2 abnormal
termination with (message DSNV086E) reason code 00F30420.
DSN3TM00 has been changed to ensure that a proper pointer value
is established.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI41828
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSN3TM00 PI41828
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI41828 DSN3TM00
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSN3TM00
LISTEND
UI28188 COVER LETTER END
UI28270 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI30015 -
****************************************************************
* USERS AFFECTED: All DB2 for DB2 10 and DB2 11 *
* for z/OS users who use multiple *
* outer joins in a SELECT. *
****************************************************************
1 * PROBLEM DESCRIPTION: Incorrect output may occur *
* for an SQL statement using *
* multiple outer joins with *
* RIGHT JOIN or FULL OUTER JOIN *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Sample type of queries:
SELECT 1 FROM
tab1 a LEFT JOIN
tab2 b FULL OUTER JOIN tab3 c ON b.c1=c.c1
LEFT JOIN tab4 d ON c.c2 = d.c2
ON a.c3 = b.c3
SELECT 1 FROM
tab1 a LEFT JOIN
tab2 b RIGHT JOIN tab3 c ON b.c1=c.c1
LEFT JOIN tab4 d ON c.c2 = d.c2
ON a.c3 = b.c3
Incorrect out may occur for the query above because DB2 did
not process the FULL OUTER JOIN or RIGHT JOIN correctly during
query rewrite.
DB2 has been fixed to handle multiple outer joins when an
outer join workfile has been merged and base columns are
defined as NOT NULL and crosses into null padding join
operations and the full outer join is transformed into
a right join.
Additional Keywords: SQLOUTERJOIN SQLLEFTJOIN SQLFULLJOIN
SQLRIGHTJOIN SQLOUTER SQLLEFT SQLRIGHT
SQLFULL
SQLINCORR SQLINCORROUT INCORROUT
DB2INCORR/K DB2PARALL/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI30015
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI30015:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI30015 corrects a problem of incorrect output may occur
for an SQL statement using multiple outer joins with RIGHT JOIN
or FULL OUTER 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.
1 COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOCLP PI30015
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI30015 DSNXOCLP
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOCLP
LISTEND
UI28270 COVER LETTER END
UI28342 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI41431 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of *
* queries where parallelism needs to partition *
* RIDs into workfiles. *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND04E RC00E2000C at DSNGDCOB *
* DSNSVSVB (OFFSET0AD8) can occur when *
* parallelism needs to partition RIDs *
* into workfiles and finds that no *
* storage is available. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An ABEND04E RC00E2000C at DSNGDCOB DSNSVSVB (OFFSET +0AD8) can
occur when parallelism needs to partition the RIDs into
workfiles and finds no storage available.
The problem occurs because the module which performs the
partitioning kept on acquiring storage for an internal workfile
descriptor control block but never freed it upon exit. Thus, a
slow growing catalyst. So if an application is long running and
continues to use parallelism with this kind of RID partitioning,
then this storage can continue to accummulate resulting in a
short on storage condition.
DB2 has been modified to free the storage for the workfile
descriptor control block upon exit from the module that
acquires the storage. This will prevent the accumulation
and short-on-storage condition previously mentioned.
Additional Keywords: SQLRID PARALLELISM SQLPARALLELISM
DB2PARALL/K SQLSTORAGE DB2STGLK/K
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI41431
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
DSNXSFPR PI41431
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI41431 DSNXSFPR
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXSFPR
LISTEND
UI28342 COVER LETTER END
UI28625 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI39858 -
****************************************************************
* USERS AFFECTED: DB2 for zOS 10 and 11 users who have APAR *
* PI32623 applied and get SQLCODE -904 with *
* reason code RC00E7910D. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E30001 DSNT1SRQ +0CF0 *
* ABEND04E RC00E20009 *
* DSNXEDC3.DSNSVSFB +0940 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 calls a function to record the authorization
dependencies for a long prepare of a cacheable SQL statement
This function is overloaded to support both static and cached
dynamic SQL.
For cached dynamic SQL, DB2 saves the current values of a
global control block and assigns temporary values which
identify the cached dynamic statement. After returning from
the function call, these values are restored.
APAR PI32623 added code to call a cleanup routine and exit if
the function failed because a storage shortage condition was
detected. However, this checking code was added before the
global control block values were restored. Any subsequent SQL
will use these temporary values which can cause various and
unpredictable problems.
DB2 is changed to restore the global control block
values before exiting the long prepare process.
Additional Keywords:
SQLDYNSTMTCACHE
SQLCODE904
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI39858
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
DSNXEDS1 PI39858
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI39858 DSNXEDS1
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEDS1
LISTEND
UI28625 COVER LETTER END
UI28997 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI39264 -
****************************************************************
* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of *
* tables that use index-controlled *
* partitioning. *
****************************************************************
* PROBLEM DESCRIPTION: User received ABEND04E RC00E2000E *
* during COMMIT processing due to *
* storage overlay. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DB2 did not handle the last partition limit key value properly
during conversion from index-controlled to table-controlled
partitioning if the following conditions are true:
- zparm IX_TB_PART_CONV_EXCLUDE is turned on to exclude
insignificant trailing partitioning key columns and there is
at least one key column that is being excluded
- DECP has comma set as the separator (DECIMAL)
This resulted in DB2 overlaying storage which resulted in the
reported abends in subsequent DB2 processing. Note that this
problem can cause other unexpected symptoms during or after
the conversion. Some of the known ones are:
- ABEND04E RC00E2000E at LOC=DSNXEAB.DSNSVSFB+08C6
- ABEND04E RC00E2000E at LOC=DSNICUBC.DSNSVSFB+08C6
- ABEND0C4 RC00000038 at LOC=DSNXGRDS.DSNXODMH+1900
- ABEND0C4 RC00000010 at LOC=DSNXCEEI.DSNXCEET+00C8
- ABEND04E RC00E70005 at LOC=DSNXGRDS.DSNXVTRS M420
- incorrect SYSTABLEPART record with missing fields or broken
values
DB2 has been fixed to handle the last logical partition's limit
key value properly for the above conditions. However, this
will not fix the existing bad values on the customer system.
1 Due to the nature of the storage overlay, please contact DB2
support for help to fix any corrupted SYSTABLEPART record.
Additional Keywords:
ABEND04E
ABEND0C4
RC00D94001
RC00000038
RC00000010
RC00E70005
RC00C90101
SQLALTER
SQLDROP
SQLCREATE
REPAIR
SQLINSERT
SQLDELETE
SQLUPDATE
DB2OVRLAY/K
SMCOVERLAY
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI39264
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXISB6 PI39264
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI39264 DSNXISB6
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXISB6
LISTEND
UI28997 COVER LETTER END
UI29181 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38586 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS users of insert from *
* subselect statements with optimization hints *
* applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00E20027 at the location *
* DSNXOPTJ.DSNSVBK +1C02 or ABEND04E *
* RC00E20021 at the location *
* DSNXOPTJ.DSNSVBK +297E may *
* intermittently occur when *
* binding/preparing an insert from *
* subselect statement with optimization *
1 * hints applied after applying UI22777. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E RC00E20027 at the location DSNXOPTJ.DSNSVBK +1C02 or
ABEND04E RC00E20021 at the location DSNXOPTJ.DSNSVBK +297E may
intermittently occur when binding/preparing an insert from
subselect statement with an optimization hint applied, if the
subselect statement contains a UNION, an outer join or a table
expression.
Additional Keywords:
ABEND04E RC00E20027 DSNXOPTJ DSNSVBK OFFSET1C02 OFFSET297E
OPTHINT SQLHINT SQLFULLJOIN SQLOUTER
SQLINSWSELECT SQLUNION SQLUNIONALL SQLTABLEEXPR SQLOUTERJOIN
DB2 has been modified to solve the problem in the cases
described as above.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38586
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOPTJ PI38586
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI38586 DSNXOPTJ
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOPTJ
LISTEND
UI29181 COVER LETTER END
UI29293 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI38595 -
****************************************************************
* USERS AFFECTED: All DB2 10 and 11 for z/OS users using *
* materialized view, table expression *
* or common table expression with outer *
* joins and row or column access control *
* with PI16260 applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABND04E at DSNXEDS1.DSNSVSFB *
* OFFSET +08FA or ABEND0C4 RC00000010 *
* at DSNXGRDS.DSNXOCSK OFFSET +4868 *
* may occur with UI21017 (V10) *
* or UI21018 (V11) for an SQL statement *
* that satisfies all of the following *
* conditions: *
* 1. The SQL statement contains *
1 * outer joins and table expressions, *
* materialized view or common table *
* expressions. *
* 2. The SQL statement references *
* a table which is activated for *
* row or column access control. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
For Example,
CREATE TABLE T1 (SSN CHAR(11),
SALARY DEC(8,2));
CREATE TABLE T2 (SSN CHAR(11),
SALARY DEC(8,2));
CREATE UNIQUE INDEX T2IX ON T2(SSN,SALARY);
CREATE PERMISSION T2SSN_PERM ON T2
FOR ROWS WHERE SSN = '000000000'
ENFORCED FOR ALL ACCESS
ENABLE;
COMMIT;
ALTER TABLE T2 ACTIVATE ROW ACCESS CONTROL;
SELECT Y.CX FROM (
SELECT T1.SSN FROM T1 LEFT JOIN T2 ON T1.SSN = T2.SSN
AND T1.SALARY= T2.SALARY) Y(CX)
UNION ALL
SELECT X.CY FROM (SELECT RAND(),SSN FROM T1)X(CX, CY);
Abend may occur for the SQL statement above when table T2
is activated for row or column access control. The abend
occurs because DB2 does not free the storage correctly
when it performs query rewrite.
DB2 has been modified to correctly process the aforementioned
SQL statement, so there will be no ABEND.
Additional keywords: SQLCTE SQLTBLX SQLJOIN SQLOJ
SQLTBLEXPR SQLPERMISSION SQLMASK
SQLCOLUMNMASK SQLACCESS SQLCONTROL
SQLVIEW
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI38595
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
DB2BIND:
***Action for PI17479:
See PI17479 APAR/PTF text for additional information about
why a REBIND is necessary.
1
PI17479 corrects a problem that incorrect output could happen
for an SQL statement with a scalar-fullselect containing a table
expression or view with UNION ALL, when the SELECT item of the
scalar-fullselect is NOT NULL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI13861:
See PI13861 APAR/PTF text for additional information about
why a REBIND is necessary.
PI13861 corrects a problem of ABEND04E RC00E70005 at location
DSNXGRDS DSNXSINE M103 or DSNXSZK M103 when a SELECT statement
references SYSIBM.SYSDUMMY1, SYSIBM.SYSDUMMYE, SYSIBM.SYSDUMMYA,
or SYSIBM.SYSDUMMU tables and contains OLAP specification.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
DB2BIND:
***Action for PI09729:
See PI09729 APAR/PTF text for additional information about
why a REBIND is necessary.
PI09729 corrects a problem that ABEND04E RC00E70005 at the
location DSNXGRDS DSNXRDEC P005, DSNXRSBC P041, DSNXRINT P026,
DSNXRTIM P016 or DSNXRDOU P011 could happen for an SQL statement
satisfying all of the following conditions:
1. It contains a table expression or view with UNION ALL.
2. It contains a predicate with a host variable or parameter
marker.
3. The predicate is on a column from the table expression or
view.
4. The columns of the predicate in the UNION branches have
different nullabilties.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNXOB2 PI38595
DSNXOCU PI38595
DSNXOMTX PI38595
DSNXOTDA PI38595
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1 PI38595 DSNXOB2 DSNXOCU DSNXOMTX DSNXOTDA
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXOB2
DSNXOCU
DSNXOMTX
DSNXOTDA
LISTEND
UI29293 COVER LETTER END
UI29397 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI41936 -
****************************************************************
* USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS *
* users with single partition partitioned *
* tablespaces and have applied any of the *
* following: *
* PM74776(UK97675) *
* PM91237(UI17758) *
* PM96664(UI22640) *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIDM DSNKISPL *
* ERQUAL5003 occurs when a prepare of a *
* query incorrectly releases an existing *
* write claim, and when any of the *
* following PTFs were previously applied: *
* PM74776(UK97675) *
* PM91237(UI17758) *
* PM96664(UI22640) *
****************************************************************
* RECOMMENDATION: Apply the corrective PTF when it is *
* available. *
****************************************************************
After PM74776(UK97675), PM91237(UI17758), or PM96664(UI22640)
is applied, DB2 may incorrectly release a write claim during
prepare of a query. This can result in an ABEND04E RC00C90101
at DSNIDM DSNKISPL ERQUAL5003, leaving affected index in an
unusable state: Rebuild Pending (RBDP) and
Logical Page List (LPL). This problem can occur if the query
being prepared references a partitioned tablespace with only a
single partition.
Losing a write claim can allow the commit-lsn to advance,
leading another UR to treat uncommitted updates as
committed. It can also affect utility concurrency and
compatibility. Other symptoms might occur:
- Incorrect output, INCORROUT
- ABEND04E RC00C90101, RC00C90102, RC00C90105, or RC00C902xx
in various CSECTs
- Data/index inconsistencies reported by CHECK INDEX or
CHECK DATA utility
1 - Page regression reported by DSN1LOGP utility
- unique key violation
Additional Keywords: DB2INCORR/K, INCORROUT, SQLINCORR,
SQLINCORROUT, INDEXPROBING
DB2 code has been changed to handle the single partition
partitioned tablespace case correctly and not release existing
claims.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI41936
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 PI41936
DSNXORTS PI41936
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI41936 DSNKCEST DSNXORTS
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNKCEST
DSNXORTS
LISTEND
UI29397 COVER LETTER END
UI29492 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI28192 -
****************************************************************
* USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the *
* SUBSTRING built-in function. *
****************************************************************
* PROBLEM DESCRIPTION: APAR PI28192 is a pre-conditioning APAR *
* for PI40667, a later enabling APAR. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This APAR provides the necessary pre-conditioning or runtime
support which will be needed for a later apar PI40667 which will
deliver the enabling or bind time function support.
This apar serves as the pre-conditioning runtime support for a
later enabling apar which will provide the bind time support to
enable the new functionality.
Additional Keywords: SQLSUBSTRING
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI28192
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
DSNXEBR PI28192
DSNXRBIN PI28192
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI28192 DSNXEBR DSNXRBIN
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNXEBR
DSNXRBIN
LISTEND
UI29492 COVER LETTER END
UI29631 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI41421 -
****************************************************************
* USERS AFFECTED: All DB2 Users of the instrumentation *
* facility interface (IFI) with PTF UI25955 *
* or APAR PI30603 applied. *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 RSN00000004, *
* loc=DSNWAAP0.DSNWAFRR+0700 or similar *
* offset during an IFI call. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During an IFI call into DB2, the instrumentation facility
creates a functional recovery point. Whenever there is an ABEND
that occurs for a particular thread, code will call the
recovery entry point to release the appropriate resources.
The recovery routine set the PSW key incorrectly while checking
the SDWA structure.
SOLUTION:
DSNWAFRR has been modified to be in the correct PSW key during
the SDWA check.
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI41421
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNWAFRR PI41421
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI41421 DSNWAFRR
1 THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNWAFRR
LISTEND
UI29631 COVER LETTER END
UI30001 COVER LETTER START
PROBLEM DESCRIPTION(S):
PI42268 -
****************************************************************
* USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users *
****************************************************************
* PROBLEM DESCRIPTION: ABEND04E DSNIDBDF.DSNSVSVB+0B28 *
* may occur when the DBET storage *
* pool runs out of space. *
* This problem was introduced by *
* APAR PI18490 (PTFs UI23031 UI23032) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND04E DSNIDBDF.DSNSVSVB+0B28 may occur when the DBET
storage pool runs out of space. This is due to DBET failing
to free storage for the DBET_PC once it is no longer needed.
This may occur when there are many objects with DBET states
DBET has been modified to correctly free the DBET_PC storage
when it is no longer needed.
ADDITIONAL KEYWORDS:
DB2STGLK/K
SQLSTORAGE
COMPONENT: 5740-XYR00-HDBAA10
APARS FIXED: PI42268
SPECIAL CONDITIONS:
COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
COMMENTS:
CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
DSNIDBAB PI42268
DSNIDBEL PI42268
DSNIDBPL PI42268
DSNIDBPX PI42268
CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
PI42268 DSNIDBAB DSNIDBEL DSNIDBPL DSNIDBPX
THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
MODULES
DSNIDBAB
DSNIDBEL
DSNIDBPL
DSNIDBPX
1 LISTEND
UI30001 COVER LETTER END
READY
END
|
UI20718 HOLD DATA START
++ HOLD(UI20439) SYS FMID(HDBAA10) REASON(ACTION) DATE(14232)
COMMENT
(***Action for PI20069 (DB2 10)
This PTF modifies the DB2 installation CLIST default input
members, DSNTIDXA and DSNTIDXB. It corrects an error in the
CLIST range checking of the settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. If you have already installed or migrated
to DB2 10, you need to make the correction in your private
DSNTIDxx members. Edit each such member, locate the entries for
SIMULATED_CPU_COUNT and SIMULATED_CPU_SPEED, and change the
fifth field to NONE. In other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <y>
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <z>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <y>
SIMULATED_CPU_SPEED CHARR G OFF NONE <z>
where <y> is the current setting of SIMULATED_CPU_COUNT
and <z> is the current setting of SIMULATED_CPU_SPEED. Save
your changes.).
UI20718 HOLD DATA END
UI20718 HOLD DATA START
++ HOLD(UI20718) SYS FMID(HDBAA10) REASON(ACTION) DATE(14232)
COMMENT
(***Action for PI07515 (DB2 10)
This PTF adds two new options, DISABLE_ITTO_EXCPTN and
IDNTFY_V10_PRIOR_VER, to the DSN6FAC.DDF_COMPATIBILITY subsystem
parameter.
- DISABLE_ITTO_EXCPTN:
Disables Idle Thread Time-Out
related serviceability information
from being returned to remote client
environments.
- IDNTFY_V10_PRIOR_VER:
Return information to ALL remote
clients to reflect New Function
support and product signature of
prior version where DB2 was migrated
from. DB2 essentially identifies
itself as the prior version.
Does not apply in NFM. Applies
only in CMn / ENFM and CMn* / ENFM*.
These options can be specified individually,
together, or in combination with other DDF_COMPATIBILITY
options. Examples:
DDF_COMPATIBILITY=
DDF_COMPATIBILITY=DISABLE_ITTO_EXCPTN
DDF_COMPATIBILITY=IDNTFY_V10_PRIOR_VER
DDF_COMPATIBILITY=(DISABLE_ITTO_EXCPTN,IDNTFY_V10_PRIOR_VER)
DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_ITTO_EXCPTN)
In DB2 data sharing, it is recommended to use the same
DDF_COMPATIBILITY setting on all members of the group.
The default for DDF_COMPATIBILITY is null (as shown in the first
example above) meaning that DB2 10 DDF behavior is maintained
with all clients.
If you have already installed or migrated to this version of DB2
you need to take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
----------------------------------------------------------------
==> This action is recommended for all customers.
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers who want to use
one or both of the new DDF_COMPATIBILITY options,
DISABLE_ITTO_EXCPTN and IDNTFY_V10_PRIOR_VER.
After applying this PTF, edit your customized copy of
job DSNTIJUZ as follows:
* Add or update the DDF_COMPATIBILITY keyword parameter in
the invocation of the DSN6FAC macro and specify a setting
of DISABLE_ITTO_EXCPTN, IDNTFY_V10_PRIOR_VER, or both.
For example:
DDF_COMPATIBILITY=DISABLE_ITTO_EXCPTN
DDF_COMPATIBILITY=IDNTFY_V10_PRIOR_VER
If additional options are needed, use the list format,
for example:
DDF_COMPATIBILITY=(DISABLE_ITTO_EXCPTN,IDNTFY_V10_PRIOR_VER)
You can also use the list format to specify one or both
of the new options in combination with one or more
other DDF_COMPATIBILITY options. Make sure to add a
continuation character in column 72 if needed. If you
omit adding DDF_COMPATIBILITY here, the value will be set
to the default of null when you assemble the DSNZPxxx
module.
* Run the first two steps of the DSNTIJUZ job you modified.
* After the job completes, you must either use the -SET
SYSPARM command or stop and restart DB2 for the change to
take effect.
---------------------------------------------------------------
(3) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers
This PTF modifies the entry for DDF_COMPATIBILITY in the
CLIST default input members in the SDSNSAMP target library
You need to add or update this entry in all private copies
of your CLIST output DSNTIDxx member. In each such copy,
convert any existing DDF_COMPATIBILITY entry that has this
format:
DDF_COMPATIBILITY CHARR M NONE NONE <x>
or this format:
DDF_COMPATIBILITY STR M <x>
or this format:
DDF_COMPATIBILITY LSTR M <x>
DDF_COMPATIBILITY1 LSTR M <y>
to this format:
DDF_COMPATIBILITY LLST M <x>
DDF_COMPATIBILITY1 LLST M <y>
DDF_COMPATIBILITY2 LLST M NULL
DDF_COMPATIBILITY3 LLST M NULL
DDF_COMPATIBILITY4 LLST M NULL
where <y> is NULL is the previous format was CHARR or STR.
Change <x> to the setting you specified in step (2),
above. If necessary, you can continue the setting onto the
DDF_COMPATIBILITYx entries by splitting it after a comma.
For example:
DDF_COMPATIBILITY LLST M SP_PARMS_NJV,DISABLE_IMPCAST_NJV,
DDF_COMPATIBILITY1 LLST M DISABLE_IMPCAST_JV,IGNORE_TZ,
DDF_COMPATIBILITY2 LLST M SP_PARMS_JV,DISABLE_ITTO_EXCPTN,
DDF_COMPATIBILITY3 LLST M IDNTFY_V10_PRIOR_VER
DDF_COMPATIBILITY4 LLST M NULL
If you do not add entries for DDF_COMPATIBILITY to a
DSNTIDxx member, the DB2 installation CLIST will assume
'DDF_COMPATIBILITY=,' when run with that member as input.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------).
UI20718 HOLD DATA END
UI21416 HOLD DATA START
++ HOLD(UI21416) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14260)
COMMENT
(***Action for PI20314:
See PI20314 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20314 adds BIF_COMPATIBILITY support for the RTRIM, LTRIM
and STRIP built-in functions.
To make this fix effective for a static application, it must be
rebound after application of this PTF. The BIF_COMPATIBILITY
system parameter should be set to V9_TRIM before rebinding.
Review the PTF cover letter to determine which, if any,
applications could be affected by this change.).
UI21416 HOLD DATA END
UI21416 HOLD DATA START
++ HOLD(UI21416) SYS FMID(HDBAA10) REASON(ACTION) DATE(14260)
COMMENT
(***Action for PI20314 (DB2 10)
This PTF adds a new option called V9_TRIM to the DSN6SPRM
BIF_COMPATIBILITY subsystem parameter. It can be used by DB2
10 customers who store mixed-byte EBCDIC data on DB2 to obtain
toleration of certain errors in mixed-byte EBCDIC strings:
- V9_TRIM: For decimal input, the
CHAR, VARCHAR, CAST( ... AS CHAR)
and CAST( ... as VARCHAR) built-in
functions behave as they do when
BIF_COMPATIBILITY is set to
V9_DECIMAL_VARCHAR. In addition,
the LTRIM, RTRIM, and STRIP built-in
functions behave like DB2 V9 with
respect to tolerating invalid EBCDIC
mixed data strings and treatment of
EBCDIC control characters X'0E0F'.
For DB2 data sharing it is recommended but not required that all
members use the same setting.
The BIF_COMPATIBILITY parameter is externalized on installation
panel DSNTIPX as BIF COMPATIBILITY. DSNTIPX has been updated to
accept the new V9_TRIM 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) Copy updated DB2 installation panels to alternate libraries
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Modify and rebind any applications that use the LTRIM,
RTRIM, or STRIP built-in functions.
----------------------------------------------------------------
(1) 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 DB2 installation panels DSNTIPX in the
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 DSNTIP8 panel to that library.
----------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
----------------------------------------------------------------
==> This action is required for all customers who want to use
the new V9_TRIM option of DSN6SPRM.BIF_COMPATIBILITY:
After applying this PTF, edit your customized copy of
job DSNTIJUZ as follows:
* Add or update the keyword parameter
BIF_COMPATIBILITY=V9_TRIM to the invocation of the
DSN6SPRM macro in your customized copy of installation job
DSNTIJUZ. Make sure to add a continuation character in
column 72 if needed. If you omit adding BIF_COMPATIBILITY
here, the value will be set to the default of CURRENT 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 who want to use
the new V9_TRIM option of DSN6SPRM.BIF_COMPATIBILITY:
After applying this PTF, edit all private copies of your
your CLIST output DSNTIDxx member, locate the entry for
BIF_COMPATIBILITY, and set the last field to V9_TRIM:
BIF_COMPATIBILITY CHAR G NONE NONE V9_TRIM
----------------------------------------------------------------
(4) Application and object changes may be needed when applying
this PTF. The actions depend on the value of the
BIF_COMPATIBILITY system parameter. See PI20314 APAR/PTF
text for additional details.
----------------------------------------------------------------).
UI21416 HOLD DATA END
UI21468 HOLD DATA START
++ HOLD(UI21468) SYS FMID(HDBAA10) REASON(ACTION) DATE(14265)
COMMENT
(After the application of the PTF for APAR PI12327, a single
SYSIBM.SYSCOPY record with ICTYPE='L' and STYPE='M' will be
inserted per commit scope for SQL mass DELETE, TRUNCATE TABLE,
or DROP TABLE executed on a table in a segmented or universal
table space (UTS). See the closing text for APAR PI12327
for more details.).
UI21468 HOLD DATA END
UI21494 HOLD DATA START
++ HOLD(UI21494) SYS FMID(HDBAA10) REASON(DOC) DATE(14262)
COMMENT
(The fix for APAR PI18635 changes RECOVER utility to allow
the use of DSNUM n in the case where TOCOPY is used, the
target object is a single piece of a nonpartitioned index
(NPI), and the specified copy data set is a FlashCopy image
copy.
The DB2 Utilities Guide will be updated to reflect the changes
made by this APAR and to clarify the conditions under which
DSNUM n may or may not be specified for RECOVER utility.
Specifically, the following footnote is added to the RECOVER
utility syntax diagram for the DSNUM option that can be
specified with TOCOPY:
| DSNUM integer is not valid for nonpartitioned indexes
| unless the data set that is specified for TOCOPY is a
| FlashCopy image copy.
To support the proper placement of this footnote, portions of
the RECOVER utility syntax diagram are restructured. These
documentation changes are listed for reference:
>>-RECOVER------------------------------------------------->
>--+-+-LIST--listdef-name-----------+-list-options-spec-+-->
| | .--------------------------. | |
| | V .-DSNUM--ALL--------. | | |
| '--obj.+---------------------+-' |
| '-DSNUM--integer----' |
| +-recover-options-spec-------------------------------+
'-object--PAGE--page-number--+----------+------------'
'-CONTINUE-'
.-LOGRANGES--YES----.
>--+-------+--+--------------+--+-------------------+-----><
'-CLONE-' +-LOCALSITE----+ | |
'-RECOVERYSITE-' '-LOGRANGES--NO-----'
...
recover-options-spec:
| .-DSNUM--ALL-------------.
| >>-object--+------------------------+---------------------->
| | (1) |
| '-DSNUM--integer---------'
>--+-TOCOPY--data-set-- ...
|
+-TOLASTCOPY-- ...
|
+-TOLASTFULLCOPY-- ...
|
'-ERROR--RANGE-- ...
Also under RECOVER utility, a portion of the explanation of the
DSNUM keyword is modified as follows:
Identifies a partition within a partitioned table space or
a partitioned index, or identifies a data set within a
nonpartitioned table space that is to be recovered.
| You cannot specify a logical partition of a nonpartitioned
| index.
| You cannot specify a single data set of a nonpartitioned
| index unless the data set that is specified for TOCOPY
| is a FlashCopy image copy. However, to ensure consistency,
| all data sets of a nonpartitioned index should be recovered
| to the same point in time.
Alternatively, the option can recover the entire table space
or index space.
...).
UI21494 HOLD DATA END
UI21511 HOLD DATA START
++ HOLD(UI21511) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14265)
COMMENT
(***Action for PI22378:
See PI22378 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22378 corrects a problem ABEND04E RC00C90101 when the query
contains residual join predicates. When the predicate is
applied, the columns from inner table are the index keys of a
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.).
UI21511 HOLD DATA END
UI21565 HOLD DATA START
++ HOLD(UK64497) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14265)
COMMENT
(DB2 will not allow catalog index names to be different from
their index space names.
Applying this APAR/PTF will not change any index spaces names
created incorrectly if customer already have migrated to
DB2 V10. Please run the following query to identify which
catalog index spaces names do not match their catalog index name
SELECT NAME, CREATOR, TBNAME, INDEXSPACE, DBID, OBID
FROM
SYSIBM.SYSINDEXES
WHERE
NAME ¬= INDEXSPACE AND
DBID = 6 AND
(OBID NOT BETWEEN 400 AND 599 AND
OBID NOT BETWEEN 900 AND 1699)
If the above query returns rows, you should contact IBM
support for further assistance.).
UI21565 HOLD DATA END
UI21712 HOLD DATA START
++ HOLD(UK96188) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14268)
COMMENT
(***Action for PM90902:
See PM90902 APAR/PTF text for additional information about
why a REBIND is necessary.
PM90902 corrects a problem of a SQLCODE -180 is issued when a
query contains a scalar function in the selection list which is
also be referenced in ORDER BY clause running on parallel.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI21712 HOLD DATA END
UI21712 HOLD DATA START
++ HOLD(UK92645) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14268)
COMMENT
(***Action for PM81200:
See PM81200 APAR/PTF text for additional information about
why a REBIND is necessary.
PM81200 corrects a problem of ABEND04E RC00C90101 at
DSNIBNRF:5007 when a query's selection list contains a scalar
full-select item participated in arithmetic calculation 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.).
UI21712 HOLD DATA END
UI21712 HOLD DATA START
++ HOLD(UI21712) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14268)
COMMENT
(***Action for PI23177:
See PI23177 APAR/PTF text for additional information about
why a REBIND is necessary.
PI23177 corrects a problem an ABEND04E RC00E70005 at DSNXORLI
P001 may occur when a query contains a LOB column and its
defined length is greater than 32767 ('7FFF'x) 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.).
UI21712 HOLD DATA END
UI21770 HOLD DATA START
++ HOLD(UI21122) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14270)
COMMENT
(***Action for PI22793:
See PI22793 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22793 corrects a problem that incorrect output could happen
for an SQL statement containing a function VARCHAR_FORMAT on a
FOR BIT DATA column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI21770 HOLD DATA END
UI21904 HOLD DATA START
++ HOLD(UI21904) SYS FMID(HDBAA10) REASON(DOC) DATE(14274)
COMMENT
(IFCID 22 is updated to include a new flag QW0022ER to indicate
if existing field QW0022PN (plan name or package name) is
displayed in Unicode instead of EBCDIC. If a CCSID
translation error occurs for QW0022PN, QW0022ER will be
turned on to indicate QW0022PN is in Unicode.
The new field is added under flags QW0022FG:
. . .
QW0022FG DS XL1 FLAGS
QW0022HT EQU X'80' 1 IF OPTIMIZATION HINTS WERE USED
QW0022ER EQU X'40' 1 IF CONVERSION ERROR ON QW0022PN
AND QW0022PN IS IN UNICODE
. . .).
UI21904 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI12294) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14279)
COMMENT
(***Action for PM90617:
See PM90617 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM90617:
(a)STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b)Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UK97958) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14279)
COMMENT
( ***Action for PM88775:
See PM88775 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM88775:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI15181) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14279)
COMMENT
(***Action for PI06664:
See PI06664 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PI06664:
(a)STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b)Rebind package for DSNACCOX. An example on how to do this
is BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSNA10.SDSNDBRM')
(c)START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(DOC) DATE(14279)
COMMENT
(PM74794 introduces the following changes to the DB2 10 for z/OS
Utility Guide and Reference -
Appendix B. DB2-supplied stored procedures for utility
operations
Section - DSNACCOX stored procedure
Chapter - DSNACCOX output
Table 145 - Result set row for second DSNACCOX result set
| NAME VARCHAR(128) Table space name, index name, or
| index space name. Index space
| name is used if the row is added
| as a result of checking a
| restricted state and the index
| name is not available at the time.
Information about this changed information will be
included in the Information Management Software for z/OS
Solutions Information Center
(http://publib.boulder.ibm.com/infocenter/imzic) at a later
date.).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI12294) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
(***Action for PM90617:
See PM90617 APAR/PTF text for additional information.
After applying the fix for PM90617, DSNACCOX will reverse
the recommendation based on percentage criterion on an
object with TOTALROWS or TOTALENTRIES of zero. If TOTALROWS
or TOTALENTRIES is zero, we now rely on the related absolute
criteria.).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UK91351) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
( ***Action for PM74794:
See PM74794 APAR/PTF text for additional information.
Post-apply actions after applying the fix for APAR PM74794:
(a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
(b) Rebind package for DSNACCOX. An example on how to do this is
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.
(c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UK79842) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
(After you apply the PTF for APAR PM61574, Non Partitioned Index
is no longer recommended for reorg or runstats when chklevel
32 is specified and any of the ts partitioned is recommended for
reorg or runstats.).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI22011) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
( ***Action for PI22121:
See PI22121 APAR/PTF text for additional information.
The package for DSNACCOX SQL statement support needs to be bound
after applying the fix for APAR PI22121.
An example of how to do this is:
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI18727) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
(The package for DSNACCOX needs to be bound after applying the
fix for APAR PI15366. An example of how to do this is:
BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) -
LIBRARY('DSN!!0.SDSNDBRM')
Change 'DSN!!0' to the prefix of your target library name.).
UI22011 HOLD DATA END
UI22011 HOLD DATA START
++ HOLD(UI15181) SYS FMID(HDBAA10) REASON(ACTION) DATE(14279)
COMMENT
(PLEASE NOTE:
After applying the fix for APAR PI06664, DSNACCOX will reverse
the recommendation based on percentage criterion on the object
with TOTALROWS or TOTALENTRIES of zero. If the TOTALROWS or
TOTALENTRIES is zero, we now rely on the related absolute
criteria.).
UI22011 HOLD DATA END
UI22067 HOLD DATA START
++ HOLD(UI22067) SYS FMID(HDBAA10) REASON(DOC) DATE(14281)
COMMENT
(DB2 will issue a new message DSNY028I and terminate with an
ABEND04E RC00E80163 if the DB2 subsystem is being started
with an incompatible level of DB2 ERLY code.
.
DSNY028I
csect-name DB2 version ERLY CODE IS NOT COMPATIBLE WITH THIS
RELEASE OF DB2
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
csect-name
The name of the control section that issued the message.
version
The version of the ERLY code.
.
System action
DB2 startup abnormally terminates with reason code 00E800163.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
.
00E80163
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
System action
DB2 startup abnormally terminates.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you are specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
DB2 will issue a new message DSNY028I and terminate with an
ABEND04E RC00E80163 if the DB2 subsystem is being started
with an incompatible level of DB2 ERLY code.
.
DSNY028I
csect-name DB2 version ERLY CODE IS NOT COMPATIBLE WITH THIS
RELEASE OF DB2
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
csect-name
The name of the control section that issued the message.
version
The version of the ERLY code.
.
System action
DB2 startup abnormally terminates with reason code 00E800163.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you re specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.
.
00E80163
.
Explanation
A DB2 subsystem could not start because the DB2 ERLY code was
not at the correct level for the version of that DB2 subsystem.
.
System action
DB2 startup abnormally terminates.
.
System programmer response
To solve the problem, follow these steps:
1. Verify that you re specifying the correct
prefix.SDSNLINK library in your link list. If not,
correct the library name.
2. Install a version of the DB2 ERLY code that is compatible
with the DB2 version that you are starting.
See the corresponding DB2 Installation manual for
compatibility of ERLY code levels and DB2 versions.
3. Activate the ERLY code by performing a z/OS IPL or
issuing the command -REFRESH DB2,EARLY.).
UI22067 HOLD DATA END
UI22080 HOLD DATA START
++ HOLD(UI19545) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14282)
COMMENT
(***Action for PM94681 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede the instructions for any previous PTF on
ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS.After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
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.).
UI22080 HOLD DATA END
UI22080 HOLD DATA START
++ HOLD(UI22080) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14282)
COMMENT
(***Action for PI25905 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI22080 HOLD DATA END
UI22080 HOLD DATA START
++ HOLD(UI20314) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14282)
COMMENT
(***Action for PI21058 (DB2 10 for z/OS)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates program module DSNADMSS and the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to bind
the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI22080 HOLD DATA END
UI22080 HOLD DATA START
++ HOLD(UI15281) SYS FMID(HDBAA10) REASON(ACTION) DATE(14282)
COMMENT
(***Action for PI07646 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede any previous PTF instructions.
If you have already installed or migrated to DB2 V10, you need
to take the following action after applying this PTF:
---------------------------------------------------------------
Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI22080 HOLD DATA END
UI22144 HOLD DATA START
++ HOLD(UI22144) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14285)
COMMENT
(***Action for PI23252:
See PI23252 APAR/PTF text for additional information about
why a REBIND is necessary.
PI23252 corrects following problems:
ABEND04E RC00E72048 at location DSNXGRDS DSNXSORI OFFSET5718
(for V10) or OFFSET6996 (for V11) could happen when executing an
SQL statement that satisfies all of the following conditions.
ABEND0C4 RC00000038 at location DSNXGRDS DSNXOD8 OFFSET1F3A (for
V10) or OFFSET1F5A (for V11) could happen when doing EXPLAIN for
an SQL statement that satisfies all of the following conditions.
1. It contains a CASE expression in the SELECT list.
2. The CASE expression contains an EXISTS subquery in the WHEN
clause.
3. The EXISTS subquery contains a table expression with SELECT
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.).
UI22144 HOLD DATA END
UI22195 HOLD DATA START
++ HOLD(UI19129) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287)
COMMENT
(***Action for PI19010:
See PI19010 APAR/PTF text for additional information about
why a REBIND is necessary.
PI19010 corrects a problem of ABEND0C4 RC00E70005 at location
DSNXRRP OFFSETM110 can occur for an SQL statement that contains
an after join or during join predicate which contains a
timestamp column and a string host variable.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI22195 HOLD DATA END
UI22195 HOLD DATA START
++ HOLD(UI16685) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287)
COMMENT
(***Action for PI11756:
See PI11756 APAR/PTF text for additional information about
why a REBIND is necessary.
PI11756 corrects a problem of 'less rows than expected' were
inserted for an offloaded IBM DB2 Analytics Accelerator
'INSERT from SELECT' stetement.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI22195 HOLD DATA END
UI22195 HOLD DATA START
++ HOLD(UI22195) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14287)
COMMENT
(***Action for PI08409:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI08409 corrects a problem in which an inefficient access path
may be selected by DB2 when a range list access path
(ACCESSTYPE='NR') would be more efficient.
To make this fix effective for a static application, zparm
PGRNGSCR must be set to YES and the application rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, applications could be affected by this
change.).
UI22195 HOLD DATA END
UI22195 HOLD DATA START
++ HOLD(UI22195) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14287)
COMMENT
(PI08409 is an enabling APAR. In a data sharing group,
pre-conditioning APAR PI16179 must be applied to all members
before the enabling APAR (PI08409) is applied to any member.
The code change is not enabled until the enabling APAR PI08409
is applied.
PI08409 corrects a problem of performance regression for static
SQL queries when an inefficient access path is selected and a
more efficient range list access path exists. The problem
can occur when a predicate eligible for index matching or
index screening in a range list leg references a timestamp
column.).
UI22195 HOLD DATA END
UI22195 HOLD DATA START
++ HOLD(UI22195) SYS FMID(HDBAA10) REASON(ACTION) DATE(14287)
COMMENT
(***Action for PI08409:
ZPARM PGRNGSCR must be set to YES to enable the fix in this
APAR.
PI08409 corrects a problem in which an inefficient access path
may be selected by DB2 when a range list access path
(ACCESSTYPE='NR') would be more efficient.
To make this fix effective for a static application, zparm
PGRNGSCR must be set to YES and the application rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, applications could be affected by this
change.).
UI22195 HOLD DATA END
UI22273 HOLD DATA START
++ HOLD(UI22273) SYS FMID(HDBAA10) REASON(ACTION) DATE(14290)
COMMENT
(See PI24860 APAR/PTF text for additional information.
PI24860 has modified the REORG utility to ignore the
KEEPDICTIONARY option when an ALTER TABLESPACE BUFFERPOOL
change is pending and instead, REORG will build a new
dictionary.
This change will be documented in the Utility Guide and
Reference manual, under the REORG utility, the KEEPDICTIONARY
option:
Possible reasons for not specifying KEEPDICTIONARY are:
| If REORG is materializing a pending alter of the buffer
| pool, REORG builds a new dictionary. DB2 ignores the
| KEEPDICTIONARY option if REORG is materializing a
| buffer pool change.).
UI22273 HOLD DATA END
UI22470 HOLD DATA START
++ HOLD(UK63421) SYS FMID(HDBAA10) REASON(ACTION) DATE(14297)
COMMENT
(After applying this PTF on DB2 10 for z/OS
==========================================
The following post-apply actions are required of all current
V10 customers that use the DB2 scheduler.
To activate the changes in this PTF you need to take the
following additional actions:
(1) Stop the scheduler for administrative tasks.
(2) Start the scheduler for administrative tasks.
Each of these actions is detailed below.
(1) Stop the scheduler for administrative tasks.
If the scheduler is running, stop it first by executing
the following console command:
MODIFY DSNADMT,APPL=SHUTDOWN
where DSNADMT is the name of the scheduler.
(2) Start the scheduler for administrative tasks.
Start the scheduler by executing the following console
command:
START DSNADMT
where DSNADMT is the name of the scheduler.).
UI22470 HOLD DATA END
UI22470 HOLD DATA START
++ HOLD(UI22470) SYS FMID(HDBAA10) REASON(ACTION) DATE(14297)
COMMENT
(***Action for PI25728 (DB2 10 for z/OS)
This PTF modifies the DB2 scheduler for administrative tasks
so that when a triggering task is updated while it is not
executing, the scheduler will not automatically schedule its
triggered task for immediate execution.
Post-apply actions for this PTF:
--------------------------------
If you have already installed or migrated to DB2 10 for z/OS
then after applying this PTF you need to take the following
actions after applying this PTF:
(1) Stop the DB2 scheduler for administrative tasks.
(2) Start the DB2 scheduler for administrative tasks.
These actions are detailed below.
----------------------------------------------------------------
(1) Stop the DB2 scheduler for administrative tasks.
***********************************************************
* This action is required for all DB2 10 customers who use
* the DB2 scheduler for administrative tasks, i.e., the
* DSN6SPRM.ADMTPROC subsystem parameter setting is not
* null (in which case it specifies the name of the
* scheduler).
***********************************************************
If the DB2 scheduler is running, stop it first by executing
the following console command:
MODIFY DSNADMT,APPL=SHUTDOWN
where DSNADMT is the name of the scheduler.
----------------------------------------------------------------
(2) Start the DB2 scheduler for administrative tasks.
***********************************************************
* This action is required for all DB2 10 customers who use
* the DB2 scheduler for administrative tasks, i.e., the
* DSN6SPRM.ADMTPROC subsystem parameter setting is not
* null (in which case it specifies the name of the
* scheduler).
***********************************************************
To start the DB2 scheduler again, execute the following
console command:
START DSNADMT
where DSNADMT is the name of the scheduler.).
UI22470 HOLD DATA END
UI22482 HOLD DATA START
++ HOLD(UI21104) SYS FMID(HDBAA10) REASON(ACTION) DATE(14297)
COMMENT
(***Action for PI19131 (DB2 10)
This APAR modifies DSNTRIN, the installation and configuration
tool for DB2-supplied stored procedures and user-defined
functions (UDFs), to correct invalid syntax in the generated
create statement for the SYSTOOLS.REGSP stored procedure. It
also modifies DSNTRIN to detect and alter existing instances
of SYSTOOLS.REGSP that are defined with the error.
If you have already installed or migrated to DB2 10, you need to
run your copy of job DSNTIJRT with MODE(INSTALL) to check for
and correct problems with the SYSTOOLS.REGSP stored procedure.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI22482 HOLD DATA END
UI22482 HOLD DATA START
++ HOLD(UI22482) SYS FMID(HDBAA10) REASON(ACTION) DATE(14297)
COMMENT
(This PTF modifies Database Metadata(DBMD) stored procedure
SYSIBM.SQLTables, as follows:
* Support new keyword EXTENDEDTABLEINFO = 0|1. Default value
is 0.
* Report 'ACCEL-ONLY TABLE' in TABLE_TYPE .
* 3 new columns are appended at the end of current result set.
(1) TEMPORAL_TABLE_TYPE VARCHAR(11)
Valid values: 'SYSTEM'|'APPLICATION'| 'BITEMPORAL'|''
(2) IS_ACCELERATED VARCHAR(3)
Valid values: 'YES'|'NO'
(3) ACCEL_ARCHIVE_STATUS CHAR(1)
Valid values: 'A'|'B'|'C'|X'|''
It also modifies SYSIBM.SQLTABLETYPES, a table used by stored
procedure SYSIBM.SQLTables, as follows:
* A new column, IS_EXTENDEDTYPE, is added. It is defined as
SMALLINT NOT NULL with DEFAULT 0.
* A new row, for TABLE_TYPE='ACCEL-ONLY TABLE' is added.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to DB2 10 then,
you need to take the following actions after applying
this PTF:
Procedures for these actions are given below.
----------------------------------------------------------------
(1) Run installation job DSNTIJRT to alter SYSIBM.SQLTABLETYPES
and add the new column, insert the new row, then bind DBRM
DSNATBLU
==> This action is required for all V10 customers
Run your copy of job DSNTIJRT with MODE(INSTALL) to alter
SYSIBM.SQLTABLETYPES and add the new column, insert the new
row, and to bind the DBRM DSNATBLU and refresh the package
for DBMD stored procedure SYSIBM.SQLTABLES. Note: The
bind request for DSNATBLU will return warnings if the
SYSACCEL.SYSACCELERATEDTABLES does not exist on DB2.
This is expected if the DB2 does not use an accelerator
product.
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) REORG the DSNATPDB.DSNATPTS table space
==> This action is required for all V10 customers
Alteration of SYSIBM.SQLTABLETYPES by DSNTIJRT to add the
new column places the containing table space,
DSNATPDB.DSNATPTS, in Advisory REORG Pending (AREO*)
status. The table space is available but needs to be
reorganized for optimal performance. Therefore, run the
REORG TABLESPACE utility with SHRLEVEL CHANGE or SHRLEVEL
REFERENCE on the entire table space.
(3) Refresh the WLM environment
Issue the following VARY MVS command to refresh the WLM
application environment
VARY WLM,APPLENV=<wlmenv>,REFRESH
where <wlmenv> is the name of the WLM application
environment in which the Database Metadata stored procedure
SYSIBM.SQLTables is running.).
UI22482 HOLD DATA END
UI22529 HOLD DATA START
++ HOLD(UI22529) SYS FMID(HDBAA10) REASON(ACTION) DATE(14300)
COMMENT
(This PTF updates DSNMQHLP, the DBRM for for the DB2 MQI
user-defined functions. After applying the PTF, all customers
should run installation job DSNTIJRT with MODE(INSTALL) to bind
a new version of package DSNMQUDF.DSNMQHLP. 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.).
UI22529 HOLD DATA END
UI22578 HOLD DATA START
++ HOLD(UK97603) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14301)
COMMENT
(***Action for PM91547:
PM91547 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
Earlier, a pre-conditioning APAR PM69760 was delivered. In a
data sharing group, this 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 following APAR enables the fix for the problem of timeout by
SCA REBUILD when a concurrent mainline DBET updater happens to
be in the notify exit path.).
UI22578 HOLD DATA END
UI22578 HOLD DATA START
++ HOLD(UK90830) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14301)
COMMENT
(***Action for PM74803:
PM74803 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
Earlier, a pre-conditioning APAR PM69760 was delivered. In a
data sharing group, this 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 following APAR enables the fix for the problem of timeout by
SCA REBUILD when a concurrent mainline DBET updater happens to
be in the notify exit path.).
UI22578 HOLD DATA END
UI22583 HOLD DATA START
++ HOLD(UK64872) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14301)
COMMENT
(See PM27871 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
APAR PM27871 corrects problems that can cause an incorrect
output for sensitive static scroll cursor when order by
DESC on a column that is not in the select list.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI22583 HOLD DATA END
UI22583 HOLD DATA START
++ HOLD(UI22583) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14301)
COMMENT
(See PI24528 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
Apar PI24528 corrects the conditions that can lead to the
occurrence of an ABEND04E RC00E70005 at location DSNXOUWF:P010
when executing a query scrollable cursor and inline lob.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI22583 HOLD DATA END
UI22693 HOLD DATA START
++ HOLD(UK70649) SYS FMID(HDBAA10) REASON(ACTION) DATE(14304)
COMMENT
(***Action for PM42922:
See PM37611 APAR/PTF text for additional information.
PM42922 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via PM37611. 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 enabling APAR, PM37611, is
applied. The new function is not enabled until PM37611 is
PM37611 removes the restriction and allows a timestamp with
time zone column in a partitioning key as long as it is the last
column in the partitioning key.).
UI22693 HOLD DATA END
UI22766 HOLD DATA START
++ HOLD(UI22766) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14308)
COMMENT
(***Action for PI27501:
See PI27501 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27501 corrects a problem for SQL query acceleration where
an SQL query is incorrectly blocked from routing to an
accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI22766 HOLD DATA END
UI22816 HOLD DATA START
++ HOLD(UI22816) SYS FMID(HDBAA10) REASON(DOC) DATE(14309)
COMMENT
(***Documentation for PI21021:
See PI21021 APAR/PTF text for additional information.
The following text contains the documentation of the function
provided by this APAR. The product documentation contained
in the Information Management Software for z/OS Solutions
Information Center will be updated at a later date.
System Profile Monitoring is being changed in the following
ways:
* a new ATTRIBUTE1 column value,
"WARNING_MESSAGE_FOR_IDLE_TIMEOUT", for a row in the
DSN_PROFILE_ATTRIBUTES table is being supported when the
KEYWORD column has the value "MONITOR IDLE THREADS"
* a new message, DSNT773I, will be issued when a thread has
exceeded the new WARNING_MESSAGE_FOR_IDLE_TIMEOUT
specified threshold.
* the base accounting trace record, as defined by DSNDQWAC,
is being enhanced to include the PROFILEID of the system
profile montoring table row (DSN_PROFILE_TABLE) which the
thread was identified to exceed, whether the threshold was
a warning or an exception.
New ATTRIBUTE1 Column Value for DSN_PROFILE_ATTRIBUTES Table
------------------------------------------------------------
In the documentation for "Managing DB2 Threads", there is an
existing subsection named "Monitoring idle threads by using
profiles". In step 2c of that section, the ATTRIBUTE1 column
can have values WARNING or EXCEPTION followed by either
_DIAGLEVEL1 or _DIAGLEVEL2. A new entry is being added to
the second part of the value as follows:
type_MESSAGE_FOR_IDLE_TIMEOUT
Where type can only be WARNING, DB2 will issue message,
DSNT773I, to display the information about the thread
which exceeded the warning threshold. DB2 will also
issue a console message, DSNT771I, which contains minimal
information. DB2 will only issue the DSNT773I message
once for the thread if it remains in an idle state. Once
a client request message is received, and a COMMIT or
ROLLBACK is performed with no resources active past the
end of the unit-of-work, DB2 will remove the warning
against the thread.
In the Table 1, "Summary of DSN_PROFILE_ATTRIBUTES values for
monitoring idle threads", a new value under the column with
heading, "ATTRIBUTE1 column", is being added as follows:
* WARNING_MESSAGE_FOR_IDLE_TIMEOUT
New Message DSNT773I
--------------------
DSNT773I csect-name SERVER DISTRIBUTED AGENT WITH
LUWID=luw-id=token
THREAD-INFO=thread-information
FOR LOCATION=location
RECEIVED IDLE THREAD TIMEOUT
WARNING DUE TO PROFILE ID=profile-id
Explanation
The information about the server thread which exceeded
a "MONITOR IDLE THREADS" monitor profile WARNING condition
is being displayed.
csect-name
The name of the control section that issued the message.
luw-id=token
The logical unit of work identifier (LUWID) and a
six-digit token value. The token value can be used in any
DB2 command that accepts a LUWID as input.
thread-information
Information about the thread. The information is presented
in a colon-delimited list that contains the following
segments:
* The primary authorization ID that is associated with the
thread.
In many distributed configurations, the primary
authorization ID that is used with DB2 is not
necessarily the user's ID.
* The name of the user's workstation.
* The ID of the user.
* The name of the application.
* The statement type for the previously executed
statement: dynamic or static.
* The statement identifier for the previously executed
statement, if available. The statement identifier can
be used to identify the particular SQL statement. For
static statements, the statement identifier correlates
to the STMT_ID column in the SYSIBM.SYSPACKSTMT table.
For dynamic statements, the statement identifier
correlates to the STMT_ID column in the
DSN_STATEMENT_CACHE_TABLE table. That statement might
not have contributed to the current failure.
* The name of the role that is associated with the thread.
* The correlation token that can be used to correlate work
at the remote system with work performed at the DB2
subsystem. The correlation token, if available, is
enclosed in '<' and '>' characters, and contains three
components, separated by periods:
- A 3 to 39 character IP address.
- A 1 to 8 character port address.
- A 12 character unique identifier.
An asterisk (*) in any segment indicates that the
information is not available.
location
This field contains the requester's IP address
profile-id
The profile ID of the monitor profile
(defined in DSN_PROFILE_TABLE) that detected the
condition.
This message might be followed by instances of message
DSNT771I indicating that WARNING MONITOR PROFILE conditions
have occurred.
Operator response
Notify the system programmer.
System programmer response
The message is being issued to provide information about
the thread which exceeded the WARNING condition. The
thread and connection remain active awaiting a subsequent
requester action. If the WARNING condition being exceeded
points to an application error, the information provided
can be used to identify the errant application.
Tracing "Monitor Idle Threads" Warning/Exception Conditions
-----------------------------------------------------------
A new paragraph is being added to our documentation in the
subsection named "Monitoring idle threads by using profiles"
of "Managing DB2 Threads", as follows:
"To understand which connection/thread exceeded a warning or
exception monitor profile, the accounting trace record of the
thread occurrence which experienced the condition will be
updated as follows:
* QWAC_PROFMON_TYPE - will be set to an 'E' for an exception
or a 'W' for a warning condition detected
* QWAC_PROFMON_PID - will be set to the 4-byte binary integer
value of the profile ID of the monitor profile (defined in
DSN_PROFILE_TABLE) that detected the condition
* if QWAC_PROFMON_TYPE is neither set to an 'E' nor a 'W',
then no monitor profile condition was detected for this
thread/connection accounting occurrence
Refer to the DSNWMSGS member of SDSNIVPD library or the
DSNDQWAC member of SDSNMACS library for a complete
description of the basic accounting trace fields.
Since a monitor profile exception condition will result in
thread level abend messages (DSNL027I/DSNL028I) being
displayed, a user can also create a warning monitor profile
which will result in a thread level message DSNT773I being
displayed when the warning threshold is exceeded. Refer to
the description of the ATTRIBUTE1 column value,
"WARNING_MESSAGE_FOR_IDLE_TIMEOUT".
Changes to IFCID 003 Record as described by DSNDQWAC
----------------------------------------------------
The accounting trace record (IFCID 003) as described by
DSNDQWAC is being changed as follows:
The current V10 DSNDWQAC contains the following in assembler:
...
QWACRU EQU *
DS CL8 * Reserved *
DS F * Reserved *
QWAC_PT_COUNT DS F * 1. For all non-rollup records = 0 *
* * 2. For a parallel query rollup record *
* * = number of parallel child agents *
* * rolled into this record *
* * 3. For a DDF/RRSAF rollup record = *
* * the number of parallel query child *
* * agents rolled into this record. *
* * These agents are NOT counted in *
* * QWACPCNT. *
QWACFLGS2 DS H
QWAC_RU_PARQRY EQU X'8000' * This record contains parallel *
* * query rollup data. *
DS CL6
QWAC_PQS EQU *
DS CL12 * Reserved *
QWAC_ACCEL EQU *
...
DSNDQWAC in assembler is being changed as follows:
...
QWACRU EQU *
DS CL8 * Reserved *
DS F * Reserved *
QWAC_PT_COUNT DS F * 1. For all non-rollup records = 0 *
* * 2. For a parallel query rollup record *
* * = number of parallel child agents *
* * rolled into this record *
* * 3. For a DDF/RRSAF rollup record = *
* * the number of parallel query child *
* * agents rolled into this record. *
* * These agents are NOT counted in *
* * QWACPCNT. *
QWACFLGS2 DS H
QWAC_RU_PARQRY EQU X'8000' * This record contains parallel *
* * query rollup data. *
QWAC_PROFMON EQU * * Thread profile monitoring info *
QWAC_PROFMON_TYPE DS CL1 * Profile monitoring type *
* * (E=excp, W=warn) *
DS CL1
QWAC_PROFMON_PID DS F * Profile table row id value *
QWAC_PQS EQU *
DS CL12 * Reserved *
QWAC_ACCEL EQU *
...).
UI22816 HOLD DATA END
UI22920 HOLD DATA START
++ HOLD(UI22920) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14314)
COMMENT
(***Action for PI22697:
See PI22697 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22697 corrects a problem for SQL query acceleration when
a virtual accelerator exists or when an accelerated table
is archived on the accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI22920 HOLD DATA END
UI22954 HOLD DATA START
++ HOLD(UI22954) SYS FMID(JDBAA17) REASON(ACTION) DATE(14316)
COMMENT
(*** Action for PI22357 (Version 10)
This PTF includes the following updated DBRM for the ODBC
executable modules DSNAOCLI, DSNAOCLX, and DSNAO64C:
DSNCLIQR
After applying the PTF, all customers who use these modules
need to bind the package of the DBRM DSNCLIQR.
For example:
BIND PACKAGE (<location-name>.DSNAOCLI) MEMBER(DSNCLIQR)
ACTION(ADD) ENCODING(EBCDIC)
where <location-name> is the location of the DBRM where
the package binds and where the description of the
package resides.
Failure to bind the required packages could result in
SQLCODE=-805 at application run time.
Also, refer to the prolog of the CLI sample bind job DSNTIJCL
in your SDSNSAMP data set for specific instructions on how to
customize the BIND command for binding the DBRMs/packages and
the application plan at your site.
*** Attention: DB2 data sharing customers need to bind the
package only once, after applying the PTF on the first
member.).
UI22954 HOLD DATA END
UI22984 HOLD DATA START
++ HOLD(UK75442) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14316)
COMMENT
(***Action for PM53253:
See PM53253 APAR/PTF text for additional information.
PM53253 corrects a problem of SQLCODE -805 encountered when
calling a Native SQL Procedure at a site that does not have
maintenance UK60802 (V9) or UK65480 (V10) applied, after the
procedure was deployed in a BIND PACKAGE DEPLOY command from
another site that does have maintenance UK60802 (V9) or
UK65480 (V10) applied.
To make this fix effective, apply this fix to all target sites
specified by BIND PACKAGE DEPLOY commands.
You can issue an sql ALTER PROCEDURE REGENERATE statement for
the procedure that fails with SQLCODE805 to allow subsequent
calls to be successful.
The order of maintenance across distributed subsystems
determines whether or not you will receive the SQLCODE805 error.
To circumvent the error, first apply this fix (or UK60802 or
UK65480) to all target sites specified by BIND PACKAGE DEPLOY
commands, and then apply this fix (or UK60802 or UK65480) to
the requesting sites.
The order of maintenance and the issuance of the BIND PACKAGE
DEPLOY command also determines whether or not you will receive
the SQLCODE805 error. If this fix (or UK60802 or UK65480) is
applied to all systems before any BIND PACKAGE DEPLOY commands
are issued, then the subject error will not occur.).
UI22984 HOLD DATA END
UI22987 HOLD DATA START
++ HOLD(UI22987) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14316)
COMMENT
(***Action for PI25244:
See PI25244 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25244 corrects a problem that incorrect output could happen
for an SQL statement containing a temporal table and a
period-specification when parallelism is enabled and an index
is created on the period 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.).
UI22987 HOLD DATA END
UI22993 HOLD DATA START
++ HOLD(UI22993) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14317)
COMMENT
(***Action for PI22468:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI22468 corrects a problem where ABEND04E RC00E72018 can
occur in DSNXSORI+481E during execution time for a query
meeting the following conditions:
1. The query contains GROUP BY;
2. An attempt is made to use an index to support the GROUP BY
grouping;
3. The index chosen from #2 is on a different table than the
table containing the columns referenced in the
GROUP BY;
4. More than one GROUP BY column maps to the same column
in the chosen index; and
5. Parallelism is used on the query.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI22993 HOLD DATA END
UI23213 HOLD DATA START
++ HOLD(UI23213) SYS FMID(HDBAA10) REASON(ACTION) DATE(14323)
COMMENT
(The fix for APAR PI29090 requires the fix for APAR PM29188, for
FMID JDBAA1K to be applied.).
UI23213 HOLD DATA END
UI23214 HOLD DATA START
++ HOLD(UI23214) SYS FMID(JDBAA1K) REASON(ACTION) DATE(14323)
COMMENT
(The fix for APAR PI29188 requires the fix for APAR PM29090, for
FMID HDBAA10 to be applied.).
UI23214 HOLD DATA END
UI23220 HOLD DATA START
++ HOLD(UI18014) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14323)
COMMENT
(This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
(2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.).
UI23220 HOLD DATA END
UI23220 HOLD DATA START
++ HOLD(UI23220) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14323)
COMMENT
(This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
(2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.).
UI23220 HOLD DATA END
UI23220 HOLD DATA START
++ HOLD(UI23147) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14323)
COMMENT
(This PTF modifies the source code for DSNTIAUL (DB2 sample
unload program).
Applying the PTF updates only the DSNTIAUL source code. The
updates do not affect your current DSNTIAUL load module until
you reprepare and rebind it.
* On DB2 10 systems running in conversion mode (CM) or
enabling-new-function mode (ENFM), no action is required after
applying this PTF. The updates will be used when you run the
DB2 10 IVP jobs after DB2 enters new-function mode (NFM).
* On DB2 10 systems in new-function mode, you need to take the
following actions:
(1) If you use a modified version of DSNTIAUL, redo your
modifications
(2) Run your customized copy of IVP job DSNTEJ2A to assemble
and link-edit the load module and bind the plan for
DSNTIAUL. Running this job will also verify that the
DSNTIAUL was prepared and bound correctly.).
UI23220 HOLD DATA END
UI23245 HOLD DATA START
++ HOLD(UI23245) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14324)
COMMENT
(***Action for PI25743:
See PI25743 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25743 corrects a problem an ABEND04E RC00E72018 at DSNXSORI
OFFSET 5E02 may occur when a sort-merge join query with
merge-composite runs on parallel and the join predicate has
different nullability, data type, or data length.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23245 HOLD DATA END
UI23268 HOLD DATA START
++ HOLD(UK96752) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14324)
COMMENT
(***Action for PM92790:
See PM92790 APAR/PTF text for additional information about
why a REBIND is necessary.
PM92790 corrects a problem that ABEND04E RC00E70005 at the
location DSNXGRDS DSNXGSFN M628 could happen or SQLCODE -180
could be incorrectly issued for an SQL statement that satisfies
all of the following conditions:
1. It contains a table expression or view with SET operator.
2. The CCSIDs of the tables in the SET operation branches are
different.
3. A Date or Timestamp item is in the SELECT list of one of the
SET operation branches.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23268 HOLD DATA END
UI23268 HOLD DATA START
++ HOLD(UI23268) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14324)
COMMENT
(***Action for PI28667:
See PI28667 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28667 corrects a problem of ABEND04E RC00C90101 at location
DSNIDM DSNOTFLA ERQUAL5009 when a statement satisfies all of the
following list of conditions:
1. A fullselect statement contains UNION ALL.
2. One of the sub-query select list of UNION ALL references
an item with CLOB or DBCLOB data type.
3. The corresponding of other sub-query select list of UNION
ALL is a literal.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23268 HOLD DATA END
UI23268 HOLD DATA START
++ HOLD(UI21715) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14324)
COMMENT
(***Action for PI24608:
See PI24608 APAR/PTF text for additional information about
why a REBIND is necessary.
PI24608 corrects a problem of ABEND04E RC00C900D0 at location
DSNXGRDS DSNXROHB OFFSETCD80 when a statement satisfies all of
the following list of conditions:
1. A fullselect statement contains UNION ALL.
2. One of the sub-query select list of UNION ALL references a
column with BLOB data type.
3. The corresponding of other sub-query select list of UNION ALL
is BINARY or VARBINARY data type.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23268 HOLD DATA END
UI23333 HOLD DATA START
++ HOLD(UI23333) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14325)
COMMENT
(This PTF modifies DSNTIJAS, the job for creating the DB2 for
z/OS accelerator database, DSNACCEL. It adds a new, optional
job step that can be used to add RESTRICT ON DROP to the tables
in DSNACCEL to prevent them from being accidentally dropped.
If you have already installed or migrated to this version of DB2
and you maintain a customized copy of job DSNTIJAS then after
applying this PTF, you can add the new job step to the end of
your DSNTIJAS job. You can also run this job step to add
RESTRICT ON DROP to the tables in your accelerator database.
To update your DSNTIJAS job:
(1) Copy the new job step, DSNTICR, including the comment block,
from prefix.SDSNSAMP(DSNTIJAS) into your DSNTIJAS job.
(2) Customize job step DSNTICR for your DB2:
(A) Change the subsystem name '!DSN!' to the SSID of your
DB2.
(B) Change 'DSN!!0' to the prefix of the target library for
DB2.
(C) Change 'DSNTIA!!' to the plan name for DSNTIAD on your
DB2.
To add RESTRICT ON DROP to the tables in your accelerator
database, uncomment job step DSNTICR and then start your
DSNTIJAS job from job step DSNTICR.).
UI23333 HOLD DATA END
UI23379 HOLD DATA START
++ HOLD(UI23379) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14328)
COMMENT
(See PI20544 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20544 corrects a problem of XML storage not being released
when the query includes XMLPARSE function and its output is
passed into XMLTABLE function for further processing.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23379 HOLD DATA END
UI23379 HOLD DATA START
++ HOLD(UI23379) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14328)
COMMENT
(PI20544 is the enabling APAR that corrects the problem where
XML storage is not being released when the query includes
XMLPARSE function and its output is passed into XMLTABLE
function for further processing.
Earlier, a pre-conditioning APAR PI19349 was delivered that is
required. In a data sharing group, this pre-conditioning APAR
should be applied to all members before applying this enabling
APAR to any member.
The fix will be enabled once this enabling APAR is applied.
If the 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 PTFs can be rolled through
together.).
UI23379 HOLD DATA END
UI23423 HOLD DATA START
++ HOLD(UK73137) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(14329)
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.).
UI23423 HOLD DATA END
UI23426 HOLD DATA START
++ HOLD(UK80523) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14329)
COMMENT
(***Action for PM57853:
See PM57853 APAR/PTF text for additional information about
why a REBIND is necessary.
PM57853 corrects a problem with incorrect output (less rows
found) that may occur on a query with a join if an index on
the outer table is chosen where predicates exist on multiple
columns of the index, and sort merge join is performed.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23426 HOLD DATA END
UI23426 HOLD DATA START
++ HOLD(UK69881) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14329)
COMMENT
(***Action for PM42245:
See PM42245 APAR/PTF text for additional information about
why a REBIND is necessary.
PM42245 corrects a problem of incorrect output that can occur
when a subquery is transformed into a join and sort merge join
is chosen.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23426 HOLD DATA END
UI23552 HOLD DATA START
++ HOLD(UI23552) SYS FMID(HDBAA10) REASON(ACTION) DATE(14336)
COMMENT
(The PTF for APAR PI28671 corrects a deadlock problem that
occurs when running multiple SQL mass delete jobs on
multi-table table spaces concurrently.
The PTF does not need to be applied to all data sharing members
at once.
However, it should be applied to all members where multiple
SQL mass delete jobs on multi-table table spaces are run,
in order to avoid deadlocks.).
UI23552 HOLD DATA END
UI23664 HOLD DATA START
++ HOLD(UK96886) SYS FMID(HDBAA10) REASON(ACTION) DATE(14339)
COMMENT
(DFSMS APAR OA41617 is required and must be installed in order
to alleviate the problem reported for PM87248.).
UI23664 HOLD DATA END
UI23778 HOLD DATA START
++ HOLD(UI23778) SYS FMID(HIZAA10) REASON(ACTION) DATE(14344)
COMMENT
(This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY).
UI23778 HOLD DATA END
UI23953 HOLD DATA START
++ HOLD(UI23953) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(14350)
COMMENT
(***Action for PI25489:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI25489 corrects a problem that DB2 may select an inefficient
range list access plan over an efficient single index access
plan for a query with OR predicates if the range list access
plan matches a superset of matching columns of the single
index access plan.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI23953 HOLD DATA END
UI24111 HOLD DATA START
++ HOLD(UI12956) SYS FMID(HDBAA10) REASON(DOC) DATE(14357)
COMMENT
(PM99151 introduces the following changes to externals:
The command response messages for the -DISPLAY ARCHIVE command
are being changed to prevent the truncation of the archive log
data set name when the data set name exceeds 42 characters in
length. The archive read data lines follow the DSNJ322I
header message. To avoid the possible data set name
truncation, the STATUS column in the archive log data lines
will be changed from 6 characters to 4 characters. For
example - before the APAR change:
DSNJ322I @ DISPLAY ARCHIVE REPORT FOLLOWS-
COUNT TIME
(TAPE UNITS) (MIN,SEC)
DSNZPARM 3 0,00
CURRENT 3 0,00
===============================================
ADDR STATUS CORR-ID VOLSER DATASET_NAME
BUSY SHEDDEN A00780 DSNC000.VA1A.ARCLG1.D13277.....
And after the APAR change:
DSNJ322I @ DISPLAY ARCHIVE REPORT FOLLOWS-
COUNT TIME
(TAPE UNITS) (MIN,SEC)
DSNZPARM 3 0,00
CURRENT 3 0,00
===============================================
ADDR STAT CORR-ID VOLSER DATASET_NAME
BUSY SHEDDEN A00780 DSNC000.VA1A.ARCLG1.D13277......
END OF DISPLAY ARCHIVE REPORT.
DSN9022I @ DSNJC001 '-DIS ARC' NORMAL COMPLETION
The STATUS column heading is being changed to STAT.
Also, the AVAIL status is being changed to AVL and the
RECALL status is being changed to RCAL. If there is
automation in place that parses the -DISPLAY ARCHIVE
command response messages, adjustments will have to be
made to account for these changes.
Information about these changed messages 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.).
UI24111 HOLD DATA END
UI24111 HOLD DATA START
++ HOLD(UI24111) SYS FMID(HDBAA10) REASON(DOC) DATE(14357)
COMMENT
(This PTF modifies message DSNJ370I output by the -DISPLAY LOG
command to indicate whether or not zHyperWrite will be requested
when writing the active log data sets.
DSNJ370I csect-name LOG DISPLAY
CURRENT COPY1 LOG = <dsname1> IS <pct>% FULL
CURRENT COPY2 LOG = <dsname2> IS <pct>% FULL
H/W RBA = <hw-rba>
H/O RBA = <ho-rba>
FULL LOGS TO OFFLOAD = nn OF mm,
OFFLOAD TASK IS <status>
SOFTWARE ACCELERATION IS <accel-status>
The last line of the DSNJ370I message is new with this PTF. The
rest of the message is unchanged.
Values for <accel-status> are
ENABLED - zHyperWrite will be requested for active log writes
DISABLED - zHyperWrite will not be used for active log writes
If zHyperWrite is requested, but the active log resides on a
volume that does not support zHyperWrite, the zHyperWrite
option is ignored and the log write is done as though
zHyperWrite was not requested.
This PTF adds a new DB2 subsystem parameter in DSN6LOGP called
REMOTE_COPY_SW_ACCEL that can be used to specify whether DB2
should use software to control the remote copy process for
active log output in PPRC environments. Valid settings are:
* DISABLE: Means that the hardware PPRC
function is used if available;
this setting is appropriate for
non-PPRC environments.
==> This is the default setting
* ENABLE : Means that host software is used;
this option can improve overall DB2
performance in PPRC environments at
the expense of some additional SRB
CPU time in the xxxxMSTR address
space. z/OS Version 2 Release 1
or later is required to support
this function.
The setting of REMOTE_COPY_SW_ACCEL is changeable via the
-SET SYSPARM command.
To use zHyperWrite, the following z/OS APARs are required:
OA41906
OA43661
OA43662
OA43663
OA44973
OA45125
OA43453
OA44240
OA45662
If these APARs are not installed, the setting of
REMOTE_COPY_SW_ACCEL has no effect. DB2 will function as if
DISABLE was specified.
---------------------------------------------------------------
If you have already installed or migrated to this version of
DB2, you need to take the following actions after applying this
PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
---------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
==> This action is 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 REMOTE_COPY_SW_ACCEL=<x>
(where <x> is DISABLE or ENABLE) to the invocation of the
DSN6LOGP macro. Make sure to add a continuation
character in column 72 if needed. If you omit adding
REMOTE_COPY_SW_ACCEL 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 REMOTE_COPY_SW_ACCEL to
the CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
REMOTE_COPY_SW_ACCEL CHAR M DISABLE ENABLE <x>
Change <x> to the value you specified for
REMOTE_COPY_SW_ACCEL in step (2), above.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
----------------------------------------------------------).
UI24111 HOLD DATA END
UI24111 HOLD DATA START
++ HOLD(UI24111) SYS FMID(HDBAA10) REASON(ACTION) DATE(14357)
COMMENT
(To use zHyperWrite for active log data set writes, several
actions are required:
- Set the new REMOTE_COPY_SW_ACCEL ZPARM to ENABLE
- Apply the z/OS maintenance listed in the ++HOLD DOC
- Install microcode level 7.4 on DS8870 DASD subsystems where
active log data sets reside.).
UI24111 HOLD DATA END
UI24155 HOLD DATA START
++ HOLD(UI24155) SYS FMID(HDBAA10) REASON(ACTION) DATE(14363)
COMMENT
(***Action for PI31086
This PTF modifies DSNTWR, the external module for the
SYSPROC.WLM_REFRESH stored procedure. It fixes a bug that
can cause SYSPROC.WLM_REFRESH to fail with abend S72A reason
code 10 when called with a NULL or blank SSID parameter.
Post-apply actions for this PTF:
-------------------------------
If you have already installed or migrated to this version of
DB2, you need to take the following actions after applying this
PTF:
(1) Rebuild or delete any private copies of module DSNTWR
(2) Bind the package for DSNTWR
----------------------------------------------------------------
(1) Rebuild or delete any private copies of module DSNTWR
***********************************************************
* This action is required for all customers who maintain
* a private copy of DSNTWR, the external module for
* WLM_REFRESH
***********************************************************
This PTF updates DSNTWR, the DB2-supplied load module for
WLM_REFRESH, in the prefix.SDSNLOAD library. It also
updates DSNTWRS, the sample source code for DSNTWR, in the
prefix.SDSNSAMP library.
If you maintain a private copy of module DSNTWR, you either
need to delete it in order to use the DB2-supplied DSNTWR
module instead or you need to update it to include the
changes introduced by this PTF.
To continue maintaining your own DSNTWR module, proceed
as follows:
(a) Compare your source code to that in member DSNTWRS of
the prefix.SDSNSAMP library to identify necessary code
changes.
(b) After completing your code changes, use job steps
PH06WS01 and PH06WS02 of your customized copy of job
DSNTEJ6W to prepare an updated DSNTWR module and to bind
a package from the updated DBRM.
----------------------------------------------------------------
(2) Bind the package for DSNTWR
***********************************************************
* This action is required for all customers who use the
* DB2-supplied DSNTWR module
***********************************************************
This PTF updates DSNTWR, the external module for WLM_REFRESH
plus the DBRM for DSNTWR. After applying this PTF, proceed
as follows to bind a package from the updated DSNTWR DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI24155 HOLD DATA END
UI24164 HOLD DATA START
++ HOLD(UI24164) SYS FMID(HDBAA10) REASON(ACTION) DATE(14363)
COMMENT
(Applying APAR PI27903 will not remove the existing extra record
from SYSIBM.SYSCOPY catalog table.
If needed, after applying APAR PI27903, the user could either
1. DROP the affected tables, then recreate them to remove the
extra SYSCOPY record.
2. OR execute a utility MODIFY RECOVERY job to remove it:
MODIFY RECOVERY TABLESPACE database-name.table-space-name
DELETE AGE(*)
Then execute a utility REPAIR DBD REBUILD job to fix the
DBD error:
REPAIR DBD REBUILD DATABASE database-name
Please note, if user elects the option 2, after the MODIFY
RECOVERY TABLESPACE job executed, the extra SYSCOPY record will
be removed. However, the REPAIR DBD DIAGNOSE/TEST job still
reports error. In order to fix it, users needs to execute the
REPAIR DBD REBUILD job to correct it.).
UI24164 HOLD DATA END
UI24205 HOLD DATA START
++ HOLD(UI24205) SYS FMID(HDBAA10) REASON(ACTION) DATE(15005)
COMMENT
(APAR PI26452 has modified the UNLOAD SPANNED YES utility to
ignore the Large Block Interface for output data sets. The
data set will use system determined block size (SDB) and the
records will continue to be written in the variable blocked
spanned format.
The Utility Guide and Reference manual has been updated to
document that UNLOAD SPANNED YES ignores the Large Block
Interface. It will be added to the following sections:
Data sets that online utilities use
UNLOAD utility under the SPANNED keyword
UNLOAD utility under Unloading data in spanned record format).
UI24205 HOLD DATA END
UI24305 HOLD DATA START
++ HOLD(UI24305) SYS FMID(HDBAA10) REASON(ACTION) DATE(15009)
COMMENT
(The PTF for APAR PI25214 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.
The fix for APAR PI25214 requires the fix for APAR PI26321, for
FMID JDBAA1K to be applied.).
UI24305 HOLD DATA END
UI24307 HOLD DATA START
++ HOLD(UK78633) SYS FMID(JDBAA1K) REASON(ACTION) DATE(15009)
COMMENT
(The fix for APAR PM60438 is a companion fix. It requires the
fix for APAR PM57632, for FMID HDBAA10 to be applied.).
UI24307 HOLD DATA END
UI24307 HOLD DATA START
++ HOLD(UK71420) SYS FMID(JDBAA1K) REASON(ACTION) DATE(15009)
COMMENT
(The fix for APAR PM42560 is a companion fix. It requires the
fix for APAR PM27962, for FMID HDBAA10 to be applied.).
UI24307 HOLD DATA END
UI24332 HOLD DATA START
++ HOLD(UI24332) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15012)
COMMENT
(See PI27007 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27007 implements the code to clean up the XML storage token
after the query finishes the processing. So the DSNXMLSM M098
ABEND will not occur when the same query is called again.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24332 HOLD DATA END
UI24359 HOLD DATA START
++ HOLD(UI24359) SYS FMID(HDBAA10) REASON(MULTSYS) DATE(15013)
COMMENT
(PI22531 is an APAR that includes changes to support a functional
code change that will be enabled once this APAR is applied.
Earlier, a pre-conditioning APAR PI21188 was delivered. In a
data sharing group, this 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 following APAR enables the support for Dynamic Statement
Cache for accelerated dynamic queries.).
UI24359 HOLD DATA END
UI24359 HOLD DATA START
++ HOLD(UI24359) SYS FMID(HDBAA10) REASON(ACTION) DATE(15013)
COMMENT
(This PTF adds the following columns to the DB2 10
DSN_STATEMENT_CACHE_TABLE:
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT
"ACCELERATED" CHAR(10) NOT NULL WITH DEFAULT 'NO'
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES'))
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL WITH DEFAULT 'N'
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT NULL
No action is required after applying this PTF to a DB2 subsystem
or data sharing group that is currently in DB2 10 conversion
mode. After DB2 enters new-function mode, follow directions in
the DB2 10 Installation Guide for migrating explain tables to
DB2 10 format.
If you have installed or migrated to DB2 10 new-function mode,
you need to take the following actions after applying this PTF:
(1) Update your existing DSN_STATEMENT_CACHE_TABLE tables to the
new format
(2) Update your customized copy of sample DDL member DSNTESC
Detailed guidance follows:
----------------------------------------------------------------
(1) Update your existing DSN_STATEMENT_CACHE_TABLE tables to the
new format
----------------------------------------------------------------
=> This action is required for all customers who have created
one or more DSN_STATEMENT_CACHE_TABLE tables:
(1) Use the following query to identify creators of existing
DSN_STATEMENT_CACHE_TABLE tables that are in the old
DB2 10 format:
SELECT TBCREATOR
FROM SYSIBM.SYSCOLUMNS
WHERE TBNAME = 'DSN_STATEMENT_CACHE_TABLE'
GROUP BY TBCREATOR, TBNAME
HAVING( MAX(COLNO) < 68 );
(2) Use job DSNTIJXA to update the
DSN_STATEMENT_CACHE_TABLE for each creator identified
by the query. Alternatively, you can process the
following statements to add the new columns:
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCELERATED" CHAR(10) NOT NULL
WITH DEFAULT 'NO'
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES'));
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT;
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL
WITH DEFAULT 'N';
ALTER TABLE prefix.DSN_STATEMENT_CACHE_TABLE ADD COLUMN
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT NULL;
Note: Altering the table will cause the containing table
space to be placed in advisory REORG pending state.
REORG the table space to clear this state.
----------------------------------------------------------------
(2) Update your customized copy of sample DDL member DSNTESC
----------------------------------------------------------------
=> This action is required for all customers who maintain
customized copies of DSNTESC
Edit DSNTESC, locate the CREATE TABLE statement for
DSN_STATEMENT_CACHE_TABLE, and proceed as follows:
(a) Add a comma to the end of the specification for the
STAT_SUS_LOG column
(b) Add the following column specifications after the one
for STAT_SUS_LOG:
"EXPANSION_REASON" CHAR(2) NOT NULL WITH DEFAULT,
"ACCELERATED" CHAR(10) NOT NULL WITH DEFAULT 'NO',
CHECK("ACCELERATED"
IN('ACCEL_ONLY', 'NO',
'NEVER', 'YES')),
"STAT_ACC_ELAP" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_CPU" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_ROW" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_BYTE" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_1ROW" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_DB2" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_EXEC" BIGINT NOT NULL WITH DEFAULT,
"STAT_ACC_WAIT" BIGINT NOT NULL WITH DEFAULT,
"ACCEL_OFFLOAD_ELIGIBLE" CHAR(1) NOT NULL WITH DEFAULT 'N',
"ACCELERATOR_NAME" VARCHAR(128) WITH DEFAULT NULL
(c) Save your changes).
UI24359 HOLD DATA END
UI24366 HOLD DATA START
++ HOLD(UI24366) SYS FMID(HDBAA10) REASON(ACTION) DATE(15013)
COMMENT
(The PTF for APAR PI27495 has modified CSECTs in both the
DSNUT110 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.).
UI24366 HOLD DATA END
UI24371 HOLD DATA START
++ HOLD(UI24371) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15013)
COMMENT
(When selecting columns from a partitioned table space
(Universal table space and classic table space) using direct
row access with a ROWID column in the predicate , optimized
code to perform the select will be bypassed due to an error.
This could lead to performance degradation or incorrect
output. To rectify, rebind the plan or package.).
UI24371 HOLD DATA END
UI24530 HOLD DATA START
++ HOLD(UK95379) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15020)
COMMENT
(***Action for PM88698:
See PM88698 APAR/PTF text for additional information about
why a REBIND is necessary.
PM88698 corrects a problem that incorrect output could happen
for an SQL statement that contains special registers in GRPOUP
BY and a view or table expression with UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24530 HOLD DATA END
UI24530 HOLD DATA START
++ HOLD(UI15888) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15020)
COMMENT
(***Action for PI08763:
See PI08763 APAR/PTF text for additional information about
why a REBIND is necessary.
PI08763 corrects a problem of incorrect output for an SQL
statement that contains OUTER JOIN and subquery predicate,
where the subquery predicate contains a table expression or
view with UNION ALL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24530 HOLD DATA END
UI24530 HOLD DATA START
++ HOLD(UI15912) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15020)
COMMENT
(***Action for PI08206:
See PI08206 APAR/PTF text for additional information about
why a REBIND is necessary.
PI08206 corrects the following problems:
An ABEND0C4 RC00000038 at location DSNXGRDS DSNXOCT OFFSET0540
or ABEND0C4 RC00000004 at location DSNXGRDS DSNXRBND OFFSET0814
may occur when an SQL statement satisfies following conditions:
1. a statement contains nested UNION/UNION ALL with ORDER BY
clause.
2. some sort-keys in the ORDER BY clause is not referenced
in the select list.
Incorrect output may occur when a SQL statement contains nested
UNION/UNION ALL with FETCH FIRST clause.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24530 HOLD DATA END
UI24541 HOLD DATA START
++ HOLD(UI24541) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15021)
COMMENT
(***Action for PI30113:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI30113 corrects a problem of an incorrect filter factor for
an XMLEXISTS predicate with multiple range conditions on the
same element. The incorrect filter factor could lead to an
inefficient access path and poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24541 HOLD DATA END
UI24603 HOLD DATA START
++ HOLD(UI24603) SYS FMID(HDBAA10) REASON(ACTION) DATE(15022)
COMMENT
(***Action for PI29024:
See PI29024 APAR/PTF text for additional information about
why an ACTION is necessary.
PI29024 corrects a problem which SQLCODE -104 is not issued as
that expected when a column is qualified in CREATE INDEX
statement.
To make this fix effective for an INDEX creation, the object
must be dropped and recreated after application of this PTF.
Review the letter to determine which, if any, applications
could be affected by this change.).
UI24603 HOLD DATA END
UI24647 HOLD DATA START
++ HOLD(UK70649) SYS FMID(HDBAA10) REASON(ACTION) DATE(15023)
COMMENT
(***Action for PM42922:
See PM37611 APAR/PTF text for additional information.
PM42922 is a pre-conditioning APAR that includes changes to
support a new function that will be enabled via PM37611. 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 enabling APAR, PM37611, is
applied. The new function is not enabled until PM37611 is
PM37611 removes the restriction and allows a timestamp with
time zone column in a partitioning key as long as it is the last
column in the partitioning key.).
UI24647 HOLD DATA END
UI24713 HOLD DATA START
++ HOLD(UI24713) SYS FMID(HDBAA10) REASON(DOC) DATE(15027)
COMMENT
(This new function APAR now enables Accelerator Statement Level
Monitoring support in IFCID 316 and 401.
This APAR has functional dependency on the IBM DB2 Analytics
Accelerator V4 or higher. Without the server support, no
statement level monitoring metric will be reported.
This APAR enables DB2 to report SQL statement's eligibility to
be executed on the accelerators and to report SQL Statement
Level Monitoring statistics for queries that are accelerated.
The statement's eligibility and statistics will be reported in
the IFCID 316, 401 trace records and the
DSN_STATEMENT_CACHE_TABLE.
The DSN_STATEMENT_CACHE_TABLE changes:
1. The ACCEL_OFFLOAD_ELIGIBLE column will be set to 'Y' when
DB2 determines a dynamic cached query is eligible to be
executed on the IBM DB2 Analytics Accelerator, when zparm
or special register for accelerator modeling is enabled.
'N' is the default value. The statement is not eligible
for acceleration.
2. The following columns in DSN_STATEMENT_CACHE_TABLE are
filled with execution statistics as the dynamic cached
statement is actually accelerated (column ACCELERATED is
'YES'). These columns' description is listed below:
Column Data Type Description
-----------------------------------------------------------
STAT_ACC_ELAP BIGINT Accumulated accelerator Elapsed
time
-----------------------------------------------------------
STAT_ACC_CPU BIGINT Accumulated accelerator CPU time
-----------------------------------------------------------
STAT_ACC_ROW BIGINT Accumulated # of rows returned
from accelerator
-----------------------------------------------------------
STAT_ACC_BYTE BIGINT Accumulated # of bytes returned
from accelerator
-----------------------------------------------------------
STAT_ACC_1ROW BIGINT Time waited for 1st row of query
result to be available from
accelerator
-----------------------------------------------------------
STAT_ACC_DB2 BIGINT Total time accelerator waited
for DB2 to request query results
-----------------------------------------------------------
STAT_ACC_EXEC BIGINT Accumulated accelerator
Execution time
-----------------------------------------------------------
STAT_ACC_WAIT BIGINT Accumulated accelerator queue
Wait time
-----------------------------------------------------------
3. The ACCELERATOR_NAME column contains the concatenated
name(s) of accelerator(s) where the query is accelerated.
Instrumentation changes:
1. IFCID 316 is changed to report when a cached statement is
eligible for execution on an accelerator. When a cached
statement is accelerated, this trace record also contains
statistics of the dynamic statement's acceleration in
QW0316's R20 section per accelerator. The 316 changes are
reflected in the DSNDQW04 copy file and related DB2
documentation on IFCID 316.
2. IFCID 401 is changed to report when a static statement is
eligible for execution on an accelerator. When a statement
is accelerated, this trace record also contains statistics
of the static statement's acceleration in QW0401's R20
section per accelerator. The 401 changes are reflected in
the DSNDQW05 copy file and related DB2 documentation on
IFCID 401.).
UI24713 HOLD DATA END
UI24713 HOLD DATA START
++ HOLD(UI14233) SYS FMID(HDBAA10) REASON(ACTION) DATE(15027)
COMMENT
(The package name and collection ID fields of IFCID 360
will now be written out as EBCDIC if the zparm UIFCIDS
is set to NO, and UNICODE if the zparm is YES.
Please note that existing applications that read these
fields may need to be changed appropriately.).
UI24713 HOLD DATA END
UI24723 HOLD DATA START
++ HOLD(UI24723) SYS FMID(HDBAA10) REASON(ACTION) DATE(15028)
COMMENT
(See PI30645 APAR/PTF text for additional information about
why an ACTION is necessary.
PI30645 corrects a problem of incorrect output when running
a native SQL procedure which contains an SQL statement that
references a VARGRAPHIC type SQL variable multiple times.
After the application of this PTF, ALTER PROCEDURE REGENERATE is
required for each native SQL procedure that is affected.
Review the PTF cover letter to determine which, if any, native
SQL procedures could be affected by this change.).
UI24723 HOLD DATA END
UI24723 HOLD DATA START
++ HOLD(UI17182) SYS FMID(HDBAA10) REASON(ACTION) DATE(15028)
COMMENT
(PI11454 corrects a problem that incorrect statement number and
section number could be generated when a native SQL procedure
or non-inline SQL scalar function satisfies following
conditions:
1. CREATE PROCEDURE/FUNCTION statement contains at least 2
assignment-statements that references user-defined function
(UDF) or built-in function(BIF).
2. One of the assignment-statement references a UDF which does
not exist during bind time.
3. One of the assignment-statement references a BIF.
After the application of this PTF, ALTER PROCEDURE/FUNCTION
REGENERATE is required for each native SQL procedure/SQL scalar
function that is affected.
Review the PTF cover letter to determine which, if any, native
SQL procedure and SQL scalar function could be affected by
this change.).
UI24723 HOLD DATA END
UI24725 HOLD DATA START
++ HOLD(UI24725) SYS FMID(HDBAA10) REASON(ACTION) DATE(15028)
COMMENT
(***Action for PI31554 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SYSPARM to properly initialize storage
for the procedure result set columns.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the ADMIN_INFO_SYSPARM 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.).
UI24725 HOLD DATA END
UI24889 HOLD DATA START
++ HOLD(UI24889) SYS FMID(HDBAA10) REASON(ACTION) DATE(15033)
COMMENT
(***Action for PI30243
This PTF modifies DSNTXAZP, a program that can be used to
refresh a DB2 installation CLIST input (DSNTIDxx) member with
DB2's current subsystem parameter, DSNHDECP parameter, and
buffer pool settings. If you have already installed or migrated
to this version of DB2 and you use DSNTXAZP then you need to
update the package: Submit a job that contains the following
BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.).
UI24889 HOLD DATA END
UI24889 HOLD DATA START
++ HOLD(UI24189) SYS FMID(HDBAA10) REASON(ACTION) DATE(15033)
COMMENT
(***Action for PI29286 (DB2 10)
This PTF modifies DSNTXAZP, the DSNTIDxx refresh tool to fix
an error that causes the wrong MAX VALUE setting to be assigned
to the DSNTIDxx entries for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED.
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 private copies of the DSNTIDxx CLIST input member
(2) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
You need to verify that your DSNTIDxx members have the
appropriate MAX VALUE settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. For each private DSNTIDxx member, proceed
as follows:
(a) Edit the member
(b) Locate the entry for SIMULATED_CPU_COUNT. If the fifth
field (MAX VALUE) specifies 255, change it to NONE. In
other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <x>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <x>
where <x> is the current setting of SIMULATED_CPU_COUNT.
(c) Locate the entry for SIMULATED_CPU_SPEED. If the fifth
field (MAX VALUE) specifies 2147483647, change it to NONE.
In other words, change this format:
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <y>
to this:
SIMULATED_CPU_SPEED CHARR G OFF NONE <y>
where <y> is the current setting of SIMULATED_CPU_SPEED.
(d) Save any changes you made and proceed to your next DSNTIDxx
member
Repeat steps (a) - (d) for each DSNTIDxx member.
---------------------------------------------------------------
(2) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------).
UI24889 HOLD DATA END
UI24966 HOLD DATA START
++ HOLD(UI24966) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15035)
COMMENT
(***Action for PI28688:
See PI28688 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28688 corrects a problem that DB2 may add an unnecessary sort
to the access path when the query has left outer join or right
outer join. Also, the preserved side is a table expression
with an ORDER BY clause, GROUP BY clause, or 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.).
UI24966 HOLD DATA END
UI24966 HOLD DATA START
++ HOLD(UI24547) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15035)
COMMENT
(***Action for PI27160:
See PI27160 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27160 corrects a problem about filter factor when the query
contains table with unique index on expression which has only
1 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.).
UI24966 HOLD DATA END
UI24968 HOLD DATA START
++ HOLD(UK95210) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15035)
COMMENT
(***Action for PM87166:
See PM87166 APAR/PTF text for additional information about
why a REBIND is necessary.
PM87166 corrects a problem of Incorrect output may occur
with UK92607 (V10) or UK92608 (V9). The non correlated SQL
statement that uses constant <> constant predicate where
the constants are integer, bigint or binary and the length
of the constants are different may receive incorrect output.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24968 HOLD DATA END
UI24968 HOLD DATA START
++ HOLD(UK92607) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15035)
COMMENT
(***Action for PM80911:
See PM80911 APAR/PTF text for additional information about
why a REBIND is necessary.
PM80911 enhances the performance of a non correlated
SQL statements with predicates involving constant
comparisons.
The performance of a non correlated SELECT statement can be
improved if it has a predicate that always evaluates to
false because it is a not equal comparison between two
constants that have the same values. The query can be executed
without accessing the tables in the FROM clause because
the predicate is always evaluated to false
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24968 HOLD DATA END
UI24968 HOLD DATA START
++ HOLD(UK90311) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15035)
COMMENT
(***Action for PM76608:
See PM76608 APAR/PTF text for additional information about
why a REBIND is necessary.
PM76608 corrects a problem that incorrect output could happen
for an SQL statement that contains FETCH FIRST n ROWS ONLY in a
table expression, on which there is a predicate.
The access path of the SQL statement maybe changed after
applying PM76608, as predicates will not be push down to the
table expression that contains FETCH FIRST n ROWS ONLY.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI24968 HOLD DATA END
UI25035 HOLD DATA START
++ HOLD(UI25035) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15040)
COMMENT
(***Action for PI25969:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI25969 corrects a problem of possible incorrect output for
a query containing GROUP BY on a SUBSTR of a column which
requires a cast.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25035 HOLD DATA END
UI25066 HOLD DATA START
++ HOLD(UI24889) SYS FMID(HDBAA10) REASON(ACTION) DATE(15041)
COMMENT
(***Action for PI30243
This PTF modifies DSNTXAZP, a program that can be used to
refresh a DB2 installation CLIST input (DSNTIDxx) member with
DB2's current subsystem parameter, DSNHDECP parameter, and
buffer pool settings. If you have already installed or migrated
to this version of DB2 and you use DSNTXAZP then you need to
update the package: Submit a job that contains the following
BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.).
UI25066 HOLD DATA END
UI25066 HOLD DATA START
++ HOLD(UI25066) SYS FMID(HDBAA10) REASON(ACTION) DATE(15041)
COMMENT
(PI29707 introduces the following changes to externals:
New option for TEMPLATE utility:
TIME
Specifies time used in expansion of date and time DSN
variables. The default TIME value is determined by the
TEMPLATE_TIME subsystem parameter.
Tip: Set all DB2 data sharing members to the same value.
LOCAL
Use local time at the DB2 server in the expansion of date
and time in DSN variables.
UTC
Use Coordinated Universal Time (UTC) in the expansion of
date and time in DSN variables.
New subsystem parameter for DSN6SPRM:
TEMPLATE_TIME
Specifies the default setting for the TIME option of the
DB2 TEMPLATE utility, which is used when the TEMPLATE
statement does not specify the TIME option. Valid settings
are:
* LOCAL: Means that the local time is used.
* UTC : Means that Coordinated Universal Time is used.
===> This is the default setting
Information about these changes will be included in the DB2 for
z/OS collection in the IBM Knowledge Center
(http://www-01.ibm.com/support/knowledgecenter/
SSEPEK/db2z_prodhome.html)
at a later date.
If you have already installed or migrated to DB2 10, you need to
take the following actions after applying this PTF:
(1) Update customized copies of DB2 installation CLIST members
(2) Update your customized copy of job DSNTIJUZ
(3) Update private copies of the DSNTIDxx CLIST input member
(4) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
---------------------------------------------------------------
(1) Update customized copies of DB2 installation CLIST members
==> This action is required for all customers
This PTF modifies CLIST member DSNTINST in the SDSNCLST
target library only. You need to redo any record format
changes and reapply any tailoring you have done to your
copies of this CLIST. You may also want to move it to the
prefix.NEW.SDSNCLST data set, where the CLISTs processed by
job DSNTIJVC reside.
---------------------------------------------------------------
(2) Update your customized copy of job DSNTIJUZ
==> This action is required for all customers
This PTF modifies DB2 installation job DSNTIJUZ in the
SDSNSAMP target library. After applying this PTF, you need
to update your customized copy of this job as follows:
* Add the keyword parameter TEMPLATE_TIME=<x>
(where <x> is UTC or LOCAL) to the invocation of the
DSN6SPRM macro. Make sure to add a continuation
character in column 72 if needed. If you omit adding
TEMPLATE_TIME here, the value will be set to
the default of UTC 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 TEMPLATE_TIME to
the CLIST default input member, DSNTIDXA, in the SDSNSAMP
target library. You need to add this entry to all private
copies of your CLIST output DSNTIDxx member. In each such
copy, add the following line:
TEMPLATE_TIME CHAR G LOCAL UTC <x>
Change <x> to the value you specified for
TEMPLATE_TIME in step (2), above.
---------------------------------------------------------------
(4) Update the package for DSNTXAZP
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------).
UI25066 HOLD DATA END
UI25066 HOLD DATA START
++ HOLD(UI24189) SYS FMID(HDBAA10) REASON(ACTION) DATE(15041)
COMMENT
(***Action for PI29286 (DB2 10)
This PTF modifies DSNTXAZP, the DSNTIDxx refresh tool to fix
an error that causes the wrong MAX VALUE setting to be assigned
to the DSNTIDxx entries for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED.
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 private copies of the DSNTIDxx CLIST input member
(2) Update the package for DSNTXAZP
Detailed guidance for these actions follows:
----------------------------------------------------------------
(1) Update private copies of the DSNTIDxx CLIST input member
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
You need to verify that your DSNTIDxx members have the
appropriate MAX VALUE settings for SIMULATED_CPU_COUNT and
SIMULATED_CPU_SPEED. For each private DSNTIDxx member, proceed
as follows:
(a) Edit the member
(b) Locate the entry for SIMULATED_CPU_COUNT. If the fifth
field (MAX VALUE) specifies 255, change it to NONE. In
other words, change this format:
SIMULATED_CPU_COUNT CHARR G OFF 255 <x>
to this:
SIMULATED_CPU_COUNT CHARR G OFF NONE <x>
where <x> is the current setting of SIMULATED_CPU_COUNT.
(c) Locate the entry for SIMULATED_CPU_SPEED. If the fifth
field (MAX VALUE) specifies 2147483647, change it to NONE.
In other words, change this format:
SIMULATED_CPU_SPEED CHARR G OFF 2147483647 <y>
to this:
SIMULATED_CPU_SPEED CHARR G OFF NONE <y>
where <y> is the current setting of SIMULATED_CPU_SPEED.
(d) Save any changes you made and proceed to your next DSNTIDxx
member
Repeat steps (a) - (d) for each DSNTIDxx member.
---------------------------------------------------------------
(2) Update the package for DSNTXAZP
---------------------------------------------------------------
==> This action is required for all customers who use DSNTXAZP
to update DB2 CLIST input (DSNTIDXX) members
Submit a job that contains the following BIND statement:
BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
ACTION(ADD) ENCODING(EBCDIC) -
LIBRARY('prefix.SDSNDBRM')
where <prefix> is the high-level qualifier for the
DB2 subsystem target libraries.
---------------------------------------------------------------).
UI25066 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI19545) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15042)
COMMENT
(***Action for PM94681 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede the instructions for any previous PTF on
ADMIN_INFO_SQL.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS.After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
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.).
UI25097 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI25097) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15042)
COMMENT
(***Action for PI31854 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI25097 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI22080) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15042)
COMMENT
(***Action for PI25905 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to V10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI25097 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI20314) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15042)
COMMENT
(***Action for PI21058 (DB2 10 for z/OS)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data.
If you have already installed or migrated to DB2 V10, you need
to take the following actions after applying this PTF:
---------------------------------------------------------------
(1) Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates program module DSNADMSS and the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to bind
the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI25097 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI25095) SYS FMID(HDBAA10) REASON(ACTION) DATE(15042)
COMMENT
(***Action for PI30399 (DB2 10 for z/OS)
This PTF modifies the DB2-supplied stored procedure
SYSPROC.ADMIN_INFO_SQL and batch program DSNADMSB
which are used to collect DB2 environmental service data.
***************************************************************
Actions for customers who are already using DB2 10:
***************************************************************
If you have already installed or migrated to DB2 10, run your
copy of the installation job DSNTIJRT with MODE(INSTALL) to
bind the DSNADMSS DBRM.
If you have previously run DSNTIJRT, rerunning with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either rerun DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI25097 HOLD DATA END
UI25097 HOLD DATA START
++ HOLD(UI15281) SYS FMID(HDBAA10) REASON(ACTION) DATE(15042)
COMMENT
(***Action for PI07646 (DB2 10)
This PTF modifies DSNADMSS, the external module for
SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
to collect DB2 environmental service data. These instructions
supersede any previous PTF instructions.
If you have already installed or migrated to DB2 V10, you need
to take the following action after applying this PTF:
---------------------------------------------------------------
Run installation job DSNTIJRT to bind DBRM DSNADMSS
---------------------------------------------------------------
==> This action is required for all V10 customers.
This PTF updates programs module DSNADMSS plus the DBRM
for DSNADMSS. After applying this PTF, proceed as follows
to bind a package from the updated DSNADMSS DBRM.
Run your copy of job DSNTIJRT with MODE(INSTALL) to install,
bind, and grant access to the DB2-supplied stored
procedures.
If you have previously run DSNTIJRT, re-running with
MODE(INSTALL) will cause it to detect and correct only
missing and downlevel SQL objects and packages for
DB2-supplied routines.
Note: Use MODE(INSTALL-PREVIEW) to obtain a report of any
changes without processing them. The PREVIEW option will
also generate and output a JCL job to the JCLOUT DD that
contains any SQL and bind statements to be processed.
After reviewing the changes, either re-run DSNTIJRT without
the PREVIEW option or customize and run the generated job.).
UI25097 HOLD DATA END
UI25153 HOLD DATA START
++ HOLD(UI25153) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15044)
COMMENT
(***Action for PI32837:
See PI32837 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32837 corrects a bind time problem that can cause an incorrect
result set to be returned for queries that contain the
CORRELATION built-in aggregate 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.).
UI25153 HOLD DATA END
UI25213 HOLD DATA START
++ HOLD(UI25213) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15048)
COMMENT
(***Action for PI32543:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI32543 corrects a problem in which DB2 may overestimate the
cost of a non-correlated EXISTS subquery. This may lead to
an inefficient access path and poor query performance.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25213 HOLD DATA END
UI25236 HOLD DATA START
++ HOLD(UI22717) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15048)
COMMENT
(***Action for PI15740:
A rebind is necessary for static applications to rebuild
access paths based on changes in this APAR.
PI15740 corrects a problem where incorrect output can occur
for a query which uses a range list access path and contains
multiple range predicates on the same column in the same
direction.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25236 HOLD DATA END
UI25417 HOLD DATA START
++ HOLD(UI25417) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15055)
COMMENT
(See PI32067 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
Apar PI32067 corrects the conditions that can lead to the
occurrence of an ABEND04E RC00C90101 at DSNICMAT ERQUAL5006
for select using scrollable sensitive cursor with fieldproc.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25417 HOLD DATA END
UI25546 HOLD DATA START
++ HOLD(UI25546) SYS FMID(HIZAA10) REASON(ACTION) DATE(15058)
COMMENT
(This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY).
UI25546 HOLD DATA END
UI25546 HOLD DATA START
++ HOLD(UI24916) SYS FMID(HIZAA10) REASON(ACTION) DATE(15058)
COMMENT
(This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY).
UI25546 HOLD DATA END
UI25546 HOLD DATA START
++ HOLD(UI21178) SYS FMID(HIZAA10) REASON(ACTION) DATE(15058)
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.).
UI25546 HOLD DATA END
UI25546 HOLD DATA START
++ HOLD(UI18945) SYS FMID(HIZAA10) REASON(ACTION) DATE(15058)
COMMENT
(***Action for PI18566:
This PTF requires either an ERLY code refresh or a re-IPL of
zOS.
To refresh, enter the following commands after applying
the PTF:
MODIFY LLA,REFRESH
-STOP DB2 ... (only if the DB2 subsystem is started)
-REFRESH DB2,EARLY
-START DB2,PARM=...
These commands are not necessary if you re-IPL after applying
the PTF.).
UI25546 HOLD DATA END
UI25546 HOLD DATA START
++ HOLD(UI18548) SYS FMID(HIZAA10) REASON(ACTION) DATE(15058)
COMMENT
(This PTF updates the ERLY code. After you apply this fix,
you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
command.
The procedure for issuing the REFRESH command is:
1. Issue -STOP DB2
2. Issue MODIFY LLA,REFRESH
3. Issue -REFRESH DB2,EARLY).
UI25546 HOLD DATA END
UI25563 HOLD DATA START
++ HOLD(UI25563) SYS FMID(HDBAA10) REASON(DOC) DATE(15061)
COMMENT
(***Documentation for PI31597:
See PI31597 APAR/PTF text for additional information.
Documentation changes are required to describe the function
provided by this APAR. The product documentation contained
in the DB2 for z/OS Knowledge Center will be updated at a
later date.
Changes to the DB2 10 and DB2 11 Messages Manuals.
---------------------------------------------------------------
The explanation text of messages DSNL004I and DSNL302I is
changed:
* The description of the BNDOPT value of the PKGREL DDF
processing option is changed to have an additional paragraph
as follows:
When a connection which has used a high performance DBAT
terminates, the high performance DBAT will also be
deallocated.
* A description of a new PKGREL DDF processing option value,
BNDPOOL, is added as follows:
BNDPOOL
DDF processing for the BNDPOOL option value will be the
same as the BNDOPT option value with the following
exception: when a connection which has used a high
performance DBAT terminates, the high performance DBAT
will be pooled. The pooled DBAT can then be used by
any other connection which presents a request to this
DB2 subsystem.
Changes to the DB2 10 and DB2 11 Command Reference manuals.
---------------------------------------------------------------
The description of the PKGREL option of the MODIFY DDF command
is replaced with the following:
PKGREL
Specifies whether DB2 honors the bind options of packages that
are used for remote client processing. The PKGREL option also
controls the disposition of high performance DBATs when a
client connection which has used a high performance DBAT has
terminated.
BNDOPT
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
by a terminating client connection will be deallocated.
BNDOPT is the default value of the MODIFY DDF PKGREL command.
BNDPOOL
The rules of the RELEASE bind option that was specified when
the package was bound are applied to any package that is used
for remote client processing. The high performance DBAT used
by terminating a client connection will be pooled.
COMMIT
The rules of the RELEASE(COMMIT) bind option are applied to
any package that is used for remote client processing. COMMIT
is the default value when the CMTSTAT subsystem parameter is
set to ACTIVE. If the MODIFY DDF PKGREL command had never been
issued, then COMMIT is the default value. No high performance
DBATs exist while the PKGREL option is set to COMMIT.
The usages notes of the -MODIFY DDF command is changed as
follows:
When to use PKGREL options: You can specify that DDF uses the
PKGREL(BNDOPT) or PKGREL(BNDPOOL) option during normal
production operating hours. For environments where client
configurations control the use of packages which were bound
with the RELEASE(DEALLOCATE) bind option, BNDOPT will be the
preferred value of the PKGREL option. For environments where
any client is capable of using packages bound with the
RELEASE(DEALLOCATE) bind option, BNDPOOL will be the preferred
value of the PKGREL option. Either option value offers
improved performance by reducing the amount of CPU costs for
allocating and deallocating packages. However, packages that
run under the rules of the RELEASE(DEALLOCATE) bind option are
likely to remain allocated and prevent maintenance activities
such as objects modifications and bind operations.
Consequently, you can use the PKGREL(COMMIT) option during
routine and emergency maintenance periods.).
UI25563 HOLD DATA END
UI25563 HOLD DATA START
++ HOLD(UI25563) SYS FMID(HDBAA10) REASON(ACTION) DATE(15061)
COMMENT
(***Action for PI31597:
For users which operate DDF with PKGREL(BNDOPT) option, as
shown by a -DISPLAY DDF command, this APAR may be of interest
to you.
High Performance DBAT processing is activated when the PKGREL
value is set to BNDOPT. APAR PI20352 changed the behavior
of High Performance DBAT processing. This APAR, PI31597, will
restore the prior (to PI20352) behavior of High Performance
DBAT processing.
For those users which desire the High Performance DBAT
processing behavior to be as provided by APAR PI20352, a
-MODIFY DFF PKGREL(BNDPOOL) command can now be issued.
See PTF cover letter for more information.).
UI25563 HOLD DATA END
UI25614 HOLD DATA START
++ HOLD(UK70914) SYS FMID(HDBAA10) REASON(ACTION) DATE(15062)
COMMENT
(***Action for PM41805:
See PM41805 APAR/PTF text for additional information about
why further ACTION might be necessary.
PM41805 corrects a problem that can occur when DATETIME
arithmetic returns a NULL value. However, DB2 does not zero out
the data part of the result and can leave it containing "bad"
data. Eventually, this can cause an incorrect result to be
returned.
For the recreate example described in the apar PM41805 text, if
the incorrect data already exists in the database, the following
simple example (steps) might be helpful in correcting it.
1. Drop the index which has the LAST_DATE column as one of the
index keys.
DROP INDEX I1;
COMMIT;
2. Apply the PTF for apar PM41805 and recycle DB2.
3. Rerun the UPDATE statement which causes the incorrect result.
UPDATE T1
SET LAST_DATE =
LAST_DATE - ((DAYS('07/20/2010') - DAYS('05/28/2009'))DAYS);
4. Recreate the dropped index.
CREATE INDEX I1
ON T1 (IDN ASC, LAST_DATE ASC);
COMMIT;
5. Execute the SELECT statement (again) which uses index access
and references the LAST_DATE column as a stage 1 predicate.
SELECT * FROM T1 WHERE IDN = 2 AND LAST_DATE IS NULL;
After the application of apar PM41805 and re-running the UPDATE
statement in Step 3., a correct NULL value will correct/replace
the "bad" null value in the table. Once the same index is
recreated, and the LAST_DATE column is referenced as a stage 1
predicate in the SELECT query, a correct result will be
returned.).
UI25614 HOLD DATA END
UI25616 HOLD DATA START
++ HOLD(UI25616) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15063)
COMMENT
(***Action for PI33252:
See PI33252 APAR/PTF text for additional information about
why a REBIND is necessary.
PI33252 corrects a problem that incorrect output could happen
for a static cursor UPDATE SQL statement whose right hand side
of the SET clause is an expression containing a correlated
scalar-fullselect.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25616 HOLD DATA END
UI25778 HOLD DATA START
++ HOLD(UI24478) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15069)
COMMENT
(***Action for PI28863:
See PI28863 APAR/PTF text for additional information about
why a REBIND is necessary.
PI28863 corrects a problem of SQLCODE504 from DSNXEPP is
received during a remote rebind for an UPDATE WHERE CURRENT OF
statement with an invalid cursor and the statement was bound
successfully with SQLERROR(CONTINUE).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25778 HOLD DATA END
UI25778 HOLD DATA START
++ HOLD(UI25016) SYS FMID(HDBAA10) REASON(ACTION) DATE(15069)
COMMENT
(***Action for PI28996:
PI28996 APAR/PTF is only for DB2 query acceleration to
an accelerator. After the PTF for PI28996 is applied,
when using QUERY ACCELERATION ELIGIBLE or ALL behaviors for
certain queries that have never before run 'only' in DB2,
DB2 may now validly fail those queries with existing -SQLCODEs
during PREPARE or bind time if those queries fail the existing
DB2 semantic error checking. Prior to this APAR, the 'full' DB2
semantic error checking was not done for accelerated queries
when using QUERY ACCELERATION ELIGIBLE or ALL behaviors.
Please see APAR/PTF closing text for more information.).
UI25778 HOLD DATA END
UI25837 HOLD DATA START
++ HOLD(UI25072) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15070)
COMMENT
(***Action for PI31373:
See PI31373 APAR/PTF text for additional information about
why a REBIND is necessary.
PI31373 corrects a problem of SQLCODE -302, when all of
following conditions are satisfied:
1. A host structure and an extended indicator array are defined
in host programming language;
2. one of the fields in the above host structure is defined with
DECIMAL type;
3. both of the above structures are used in an SQL statement;
4. the table referenced in the above SQL statement is a remote
table and locates on a federation server.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25837 HOLD DATA END
UI25853 HOLD DATA START
++ HOLD(UI12045) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15070)
COMMENT
(***Action for PM95113:
See PM95113 APAR/PTF text for additional information about
why a REBIND is necessary.
PM95113 improves the performance of query that contains a
correlated IN or EXISTS subquery predicate with a field
procedure on the correlated predicate 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.).
UI25853 HOLD DATA END
UI25853 HOLD DATA START
++ HOLD(UK80840) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15070)
COMMENT
(***Action for PM67966:
See PM67966 APAR/PTF text for additional information about
why a REBIND is necessary.
PM67966 corrects a problem that can result in an incorrect
result set, more rows than expected, being returned for a query
that contains a correlated subquery for an EXISTS predicate, and
there is a unique index on expression defined on the table that
is referenced in the 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.).
UI25853 HOLD DATA END
UI25853 HOLD DATA START
++ HOLD(UI25853) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15070)
COMMENT
(***Action for PI33994:
See PI33994 APAR/PTF text for additional information about
why a REBIND is necessary.
PI33994 corrects a problem of ABEND0C4 RC00000038 at location
DSNXGRDS DSNXOSCR OFFSET345E or ABEND04E RC00C90101 at location
DSNIDM DSNICUBC OFFSET5015 when a SQL statement contains
SENSITIVE STATIC SCROLL CURSOR and EXISTS or IN predicate with
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.).
UI25853 HOLD DATA END
UI25960 HOLD DATA START
++ HOLD(UI25960) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15074)
COMMENT
(***Action for PI31707:
See PI31707 APAR/PTF text for additional information about
why a REBIND is necessary.
PI31707 corrects a problem that DB2 may give incorrect output
for a query with a table function where there is only 1 limited
key on the partition table and there is an equal predicate
between the partition limit key and a table function parameter.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25960 HOLD DATA END
UI25960 HOLD DATA START
++ HOLD(UI22684) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15074)
COMMENT
(***Action for PI26227:
A rebind is necessary for static applications to rebuild
access paths based on the changes in this APAR.
PI26227 corrects a problem in which incorrect output may be
generated for a query with an IS NULL predicate on a
partitioning column.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI25960 HOLD DATA END
UI25987 HOLD DATA START
++ HOLD(UI20621) SYS FMID(HDBAA10) REASON(ACTION) DATE(15076)
COMMENT
(PI19842 corrects a problem of ABEND04E RC00E70005 at location
DSNXGRDS DSNXSTRC M777 or other unexpected ABEND0C4 or ABEND04E
or unexpected SQLCODE -104 during rebind when a compiled SQL
scalar function contains a RETURN statement which returns an
expression with special register CURRENT SERVER, CURRENT
PACKAGESET or CURRENT PACKAGE PATH.
After the application of this PTF, ALTER FUNCTION REGENERATE is
required for each SQL scalar function that is affected.
Review the PTF cover letter to determine which, if any, compiled
SQL scalar function could be affected by this change.).
UI25987 HOLD DATA END
UI26059 HOLD DATA START
++ HOLD(UK71432) SYS FMID(HDBAA10) REASON(ACTION) DATE(15077)
COMMENT
(The DB2 10 for z/OS PTF for APAR PM37479 has modified the REORG
utility to use the maximum record length for tables that are
compressed and defined with MAXROWS 1 and the KEEPDICTIONARY
keyword is NOT specified on the utility statement. This change
will usually require additional sort work space for the data
sort.).
UI26059 HOLD DATA END
UI26201 HOLD DATA START
++ HOLD(UK78526) SYS FMID(JDBAA12) REASON(ACTION) DATE(15082)
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.).
UI26201 HOLD DATA END
UI26208 HOLD DATA START
++ HOLD(UK78529) SYS FMID(JDBAA12) REASON(ACTION) DATE(15082)
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.).
UI26208 HOLD DATA END
UI26240 HOLD DATA START
++ HOLD(UI26240) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15083)
COMMENT
(See Pi34186 APAR/PTF text in the PTF cover letter for
additional information about why a REBIND is necessary.
APAR Pi34186 corrects a problem that can cause poor performance
for query contains LIKE predicate on unicode 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.).
UI26240 HOLD DATA END
UI26243 HOLD DATA START
++ HOLD(UI13992) SYS FMID(HDBAA10) REASON(DOC) DATE(15083)
COMMENT
(PM95281 introduces the following changes to externals:
Changed messages or codes:
For SQLCODE -20523, the following explanation is updated
under reason code 1:
Explanation: ....
1 The table must not be any of the following tables:
* System-period temporal table. The table was defined as
a system-period temporal table by a previous statement,
or the current statement defines the table as a system
period temporal table.
Changed option for SQL statement ALTER TABLE:
Under ALTER TABLE USE HISTORY TABLE history-table-name,
the following restriction is updated:
...
history-table name must identify a table that exists at
the current server and must not identify one of the
following tables:
...
- a system-period temporal table. The table was defined
as a system-period temporal table by a previous
statement, or the current statement defines the table
as a system-period temporal table (SQLSTATE 428HX,
SQLCODE -20523 with reason code 1).).
UI26243 HOLD DATA END
UI26243 HOLD DATA START
++ HOLD(UI13992) SYS FMID(HDBAA10) REASON(ACTION) DATE(15083)
COMMENT
(This PTF corrected a problem where DB2 did not restrict the
use of versioning table properly. This allowed invalid
tables to be used as the history table. Applying the PTF
however does not fix existing problems and user will need to
take the following action to correct the problem on their
system.
Please use a query to identify any tables that use themselves
as their own history table. The following is a sample
query:
SELECT CREATOR, NAME, TYPE, DBNAME,
TSNAME, DBID, OBID, COLCOUNT,
CREATEDTS, ALTEREDTS, RELCREATED,
VERSIONING_SCHEMA,
VERSIONING_TABLE
FROM SYSIBM.SYSTABLES
WHERE CREATOR = VERSIONING_SCHEMA
AND NAME = VERSIONING_TABLE;
After the tables are identified, please run an ALTER TABLE
DROP VERSIONING statement on each of the tables to correct
the self referencing problem. However the data of the
affected tables can still be down level and incorrect. User
will need to examine the data to see if any other correction
is necessary.).
UI26243 HOLD DATA END
UI26306 HOLD DATA START
++ HOLD(UI24527) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15085)
COMMENT
(See PI29102 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29102 corrects a problem for SQL query acceleration where
the query to be offloaded is a self-referencing INSERT with
sub-select.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26306 HOLD DATA END
UI26306 HOLD DATA START
++ HOLD(UI15443) SYS FMID(HDBAA10) REASON(ACTION) DATE(15085)
COMMENT
(*** Action for PI10774 ***
Users should be aware that there MAY be operational issues as
a result of this change because more remote application
environments will have to stay active, after rollback
processing, IF the application executes SQL that can be
off-loaded to an accelerator.
Basically, the operational impact of this change occurs as a
result of requiring an increased number of DB2 threads (DBATs)
and remote client system network connections (to the DB2
server) in order to service the same amount of remote
application work.
Possible symptoms may include:
. Increased storage utilization symptoms due to additional
threads (DBATs) that may now be required.
. Performance degradation, perhaps due to the queuing that may
occur as a result of reaching or approaching the MAXDBAT
resource limit.
. High rate of unexpected "Idle Thread Time-out" conditions
(message DSNL030I with reason code 00D3003B) that may result
in unexpected remote application failures.
. Remote client "connection concentrator" environments may also
be adversely affected as a result of their inability to pool
connections on a transaction (rollback) boundary.
Any potential exposure to these symptoms only occurs with
respect to remote applications that access DB2, as a server,
and then utilize an accelerator AND issue rollback. The
rollback has an effect even if it is executed after accelerator
access is complete. Since exposure is based on the execution
of a rollback, which is not typical, it is unlikely that users
will be affected, but it is possible.
After applying this change, users should monitor their system
for these symptoms. The symptoms may be normal under the
circumstances and measures may be necessary to address the
condition.).
UI26306 HOLD DATA END
UI26326 HOLD DATA START
++ HOLD(UK73300) SYS FMID(HDBAA10) REASON(ACTION) DATE(15086)
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
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).
UI26326 HOLD DATA END
UI26382 HOLD DATA START
++ HOLD(UI26188) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15089)
COMMENT
(***Action for PI35715:
PI35715 corrects a problem that incorrect output, ABEND04E
RC00E70005 at the location DSNXGRDS DSNXGMVE M628, or other
unexpected problems could happen when rebinding a native SQL
procedure with the option WITH EXPLAIN and EXPLAIN tables in
older format.
To make this fix effective, the package of the native SQL
procedure, which has been rebound with the option WITH EXPLAIN
and EXPLAIN tables in older format, must be rebound after
application of this PTF. Review the PTF cover letter to
determine which, if any, native SQL procedure could be affected
by this change.).
UI26382 HOLD DATA END
UI26382 HOLD DATA START
++ HOLD(UI26382) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15089)
COMMENT
(***Action for PI30859:
See PI30859 APAR/PTF text for additional information about
why a REBIND is necessary.
PI30859 enables new function for execution on an
accelerator.
To make this new function effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26382 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI26404) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(See PI30376 APAR/PTF text for additional information about
why a REBIND is necessary.
PI30376 1. Enable offloading of a Temporal query to an
accelerator. Only Business Time is supported.
2. Block offloading to an accelerator when the length of
nchar/nvarchar is > 16000 in the converted query.
SQLCODE -4742 with reason code = 11 will be issued.
3. Fix SQLCODE -904 "Invalid SQL Statement" for an
offloading query which includes minus literal
string.
For example, SELECT * FROM T1 WHERE C2 IN ('-9','-1')
4. Fix abend 04E-00E70005 DSNXOMSF:P170. After the fix,
SQLCODE -4742 with reason code = 11 is issued for
an unsupported statement that contains MEDIAN.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI23690) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI29176:
See PI29176 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29176 corrects a problem for SQL query acceleration when
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI22766) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI27501:
See PI27501 APAR/PTF text for additional information about
why a REBIND is necessary.
PI27501 corrects a problem for SQL query acceleration where
an SQL query is incorrectly blocked from routing to an
accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI22157) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI26089:
See PI26089 APAR/PTF text for additional information about
why a REBIND is necessary.
PI26089 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI23245) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI25743:
See PI25743 APAR/PTF text for additional information about
why a REBIND is necessary.
PI25743 corrects a problem an ABEND04E RC00E72018 at DSNXSORI
OFFSET 5E02 may occur when a sort-merge join query with
merge-composite runs on parallel and the join predicate has
different nullability, data type, or data length.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI21946) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI22945:
See PI22945 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22945 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI26378) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI22413:
See PI22413 APAR/PTF text for additional information about
why a REBIND is necessary.
PI22413 enables the following new functions for execution on an
accelerator:
(1) DECODE
(2) LTRIM and RTRIM with two arguments
(3) TRIM
(4) NVL
To make any of the new functions effective for a static
application that contains accelerated static SQL queries,
the application must be rebound after application of this PTF.
Review the PTF cover letter to determine which,if any,
applications could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI20151) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI20688:
See PI20688 APAR/PTF text for additional information about
why a REBIND is necessary.
PI20688 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI17624) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(See PI14495 APAR/PTF text for additional information about
why a REBIND is necessary.
PI14495 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an IBM DB2 Analytics Accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI19207) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15090)
COMMENT
(***Action for PI14368:
See PI14368 APAR/PTF text for additional information about
why a REBIND is necessary.
PI14368 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI26404) SYS FMID(HDBAA10) REASON(DOC) DATE(15090)
COMMENT
(***************************************************************
The following messages and codes are changed in
PI30376/PI30377/PI31445:
***************************************************************
The message/code text shown here is approximate and is subject
to change before it is published in the DB2 manuals.
(a) New messages -4747:
-4747 THE CREATE OR ALTER TABLE STATEMENT FAILED BECAUSE SOME
FUNCTIONALITY WAS SPECIFIED IN THE TABLE DEFINITION THAT IS NOT
SUPPORTED WITH THE TABLE TYPE. UNSUPPORTED FUNCTIONALITY:
functionality-keyword.
......
(b) Changed messages -159 THE STATEMENT REFERENCES object-name
WHICH IDENTIFIES AN actual-type RATHER THAN AN expected-type. A
CREATE MASK or CREATE PERMISSION statement must name a base
table that exists on the server. The table must not be a
system-period temporal table or a history table or an
accelerator-only table.
(c) Changed messages -270 FUNCTION NOT SUPPORTED
Explanation:
......
ALTER TABLE or CREATE TABLE statements:
.....
A CREATE TABLE statement must not contain a LIKE clause
and an IN ACCELERATOR clause.
A CREATE TABLE statement must not contain a LIKE clause
that references an accelerator-only table.
A CREATE TABLE statement must not contain an AS fullselect
clause and an IN ACCELERATOR clause.
A CREATE TABLE statement must not contain an AS fullselect
clause where the fullselect references an
accelerator-only table.
A CREATE TABLE statement must not contain a materialized
query definition and an IN ACCELERATOR clause.
A CREATE or ALTER TABLE statement must not define a Unicode
column in an EBCDIC table if the table is an
accelerator-only table.
......
CREATE MASK statements:
A CREATE MASK statement must not define a mask for an
accelerator-only table.
CREATE PERMISSION statements:
A CREATE PERMISSION statement must not define a column
permission for an accelerator-only table.
DECLARE GLOBAL TEMPORARY TABLE statements
The LIKE clause of a DECLARE GLOBAL TEMPORARY TABLE
must not reference an accelerator-only table.
TRIGGER statements
A CREATE [or ALTER] TRIGGER statement must not reference
an accelerator-only table in the body of the trigger.
A CREATE TRIGGER statement with INSTEAD OF clause specified
must not reference a view that references an
accelerator-only table in the body of the trigger.
(d) Changed messages -350 column-name WAS IMPLICITLY OR
EXPLICITLY REFERENCED IN A CONTEXT IN WHICH IT CANNOT BE USED
Explanation:
.......
A LOB column cannot be:
Defined in an accelerator-only table.
(e) Changed messages -637 DUPLICATE keyword-name KEYWORD OR
CLAUSE.
......
IN ACCELERATOR can only be specified once.
(f) Changed messages -650 THE ALTER STATEMENT CANNOT BE
EXECUTED, REASON reason-code
28 ALTER TABLE is not allowed when the table is an
accelerator-only table.
29 ALTER TABLESPACE is not allowed when the table space
contains an accelerator-only table.
(g) Changed messages -669 THE OBJECT CANNOT BE
EXPLICITLY DROPPED. REASON reason-code
......
0007 The DROP TABLESPACE statement or DROP DATABASE
statement attempted to drop a table space or database
that contains an accelerator-only table.
(h) Changed messages -750 THE SOURCE TABLE source-name
CANNOT BE RENAMED OR ALTERED AS SPECIFIED
Possible reasons for this error include, but are not limited to:
The table is an accelerator-only table.
(i) Changed messages -766 THE OBJECT OF A STATEMENT IS A TABLE
FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
......
Accelerator-only table
An accelerator-only table must not be specified in any of the
following statements:
1. A CREATE SYNONYM statement to define a synonym.
2. A CREATE TRIGGER statement to define a trigger for the
accelerator-only table.
3. A LOCK TABLE statement.
4. A CREATE INDEX
(j) Changed messages -817 THE SQL STATEMENT CANNOT BE
EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED DATA
CHANGE UPDATE OPERATION.
Explanation: The application attempted to execute an SQL
statement that would result in updates to user data or to the
subsystem catalog. This is prohibited for one of the following
reasons:
......
A CREATE TABLE statement for an accelerator-only table was fo
followed by a data change operation for an accelerator-only
table.
(k) Changed messages -7008 object-name NOT VALID FOR OPERATION
(reason-code)
17
A CREATE TRIGGER statement was issued, but the trigger cannot
be created because an INSTEAD OF trigger cannot be defined
on a view that has other views dependent on it, or the view
references an accelerator-only table, or an AFTER trigger
cannot be defined on a table that has a clone defined.
(l) Changed messages -20058 THE FULLSELECT SPECIFIED FOR
MATERIALIZED QUERY TABLE table-name IS NOT VALID.
The fullselect cannot contain a reference to a created
global temporary table, a declared global temporary table,
an accelerator-only table, or another materialized query
table.
(m) Changed messages -20240 INVALID SPECIFICATION
OF A SECURITY LABEL COLUMN table-name.column-name REASON
CODE reason-code
......
9
A security label column cannot be defined for an
accelerator-only table.
(n) Changed messages -20474 PERMISSION OR MASK CANNOT
BE CREATED FOR THE object-name OBJECT OF THE object-type TYPE.
REASON CODE reason-code.
......
17 One of the following situations occurred:
......
An accelerator-only table
39 The definition references an accelerator-only table.
(o) Changed messages -4742 THE STATEMENT CANNOT BE
EXECUTED BY DB2 OR IN THE ACCELERATOR (REASON reason-code)
......
The statement cannot be executed by DB2 if any of the following
conditions are true:
...
The statement references an accelerator-only table.
......
The statement cannot be executed by an accelerator server if any
condition that is indicated by a reason code is true.
......
22
The statement references an accelerator-only table,
but the statement is not offloadable. For example:
MERGE statement references an accelerator-only table.
UPDATE or DELETE statement references an accelerator-only
table,but the target table of the UPDATE, DELETE is a
normal table:
UPDATE DB2_TABLE SET .. (SELECT .. FROM
ACCEL_ONLY_TABLE).
INSERT, UPDATE or DELETE of a row expression with
subselect:
UPDATE ACCEL_ONLY_TABLE SET (C1, C2) = (SELECT C3, C4
TABLE2);
......
Programmer response: Use the reason code to determine the
cause of the failure, and take the appropriate action:
….....
22
Ensure the statement does not references an
accelerator-only table, or replace the accelerator-only
table with a DB2 table so that the query can be executed
in DB2.
(p) New warning message: +4748
+4748 THE statement STATEMENT FOR OBJECT object-name WAS
SUCCESSFUL ON THE DB2 SERVER. THE OBJECT MAY NOT HAVE BEEN
SUCCESSFULLY PROCESSED ON THE ACCELERATOR SERVER FOR
REASON reason-code
......
***************************************************************
Monitoring and Accounting Changes:
***************************************************************
The following is the new System Level Statistic Counters:
Q8STOPNC Total accumulated number of SQL Open statements sent
to IDAA by this DB2.
Q8STINSC Total accumulated number of SQL Insert statements
sent to IDAA by this DB2.
Q8STUPDC Total accumulated number of SQL Update statements
sent to IDAA by this DB2.
Q8STDELC Total accumulated number of SQL Delete statements
sent to IDAA by this DB2.
Q8STDRPC Total accumulated number of SQL Drop statements sent
IDAA by this DB2.
Q8STCRTC Total accumulated number of SQL Create statements
sent IDAA by this DB2.
Q8STCMTC Total accumulated number of SQL Commit statements
sent to IDAA by this DB2.
Q8STRBKC Total accumulated number of SQL Rollback statements
sent to IDAA by this DB2.
The new accounting fields (thread level):
Q8ACOPNC Total accumulated number of SQL Open statements
sent to IDAA by this thread.
Q8ACINSC Total accumulated number of SQL Insert statements
sent to IDAA by this thread.
Q8ACUPDC Total accumulated number of SQL Update statements
sent to IDAA by this thread.
Q8ACDELC Total accumulated number of SQL Delete statements
sent to IDAA by this thread.
Q8ACDRPC Total accumulated number of SQL Drop statements
sent to IDAA by this thread.
Q8ACCRTC Total accumulated number of SQL Create statements
sent to IDAA by this thread.
Q8ACCMTC Total accumulated number of SQL Commit statements
sent to IDAA by this thread.
Q8ACRBKC Total accumulated number of SQL Rollback statements
sent to IDAA by this thread.
Q8ACROWI Total accumulated number of rows inserted to IDAA by
this thread.
Q8ACROWU Total accumulated number of rows updated on IDAA by
this thread.
Q8ACROWD Total accumulated number of rows deleted on IDAA by
this thread.
Q8ACROWC Total accumulated number of rows returned by IDAA
to this thread.
Statement level:
For query processing, the following statement level counters are
defined (see Monitoring Counters Exchanged With DB2).
The semantics and values for those counters are slightly
different for INSERT/UPDATE/DELETE statements:
QW0316AROW - always set to 0 because DML statements return
no result set.
QW0316ABYT - always set to 0 because DML statements return
no result set.
QW0316TW1R - always set to 0 because DML statements have
no such wait times.
QW0316TWDB2 - always set to 0 because DML statements have
no such wait times.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI12631) SYS FMID(HDBAA10) REASON(ACTION) DATE(15090)
COMMENT
(Impacted packages must be DROP and CREATE'd or
ALTER REGENERATE'd after applying this PTF.
To find potentially impacted packages, this query may be used:
SELECT DISTINCT PKG.COLLID, PKG.NAME, HEX(PKG.CONTOKEN)
FROM SYSIBM.SYSPACKSTMT AS PKS, SYSIBM.SYSPACKAGE AS PKG
WHERE LENGTH(PKS.STMT) > 3499 AND PKG.TYPE = 'N' AND
PKG.COLLID = PKS.COLLID AND PKG.NAME=PKS.NAME AND
PKG.CONTOKEN = PKS.CONTOKEN;
Please note that the query results may identify false positives.
That is, not all of the packages identified may be impacted.
Alternatively, one may opt to only attempt the ALTER REGENERATE
or DROP and CREATE after encountering the -104 during REBIND.).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UK96950) SYS FMID(HDBAA10) REASON(ACTION) DATE(15090)
COMMENT
(The query provided in the ++HOLD of PM78210/UK90728 has
been updated to exclude views.
PM78210 fixes CREATE TABLE to define implicit table spaces
in reordered row format(RRF) when all of the following
conditions are true:
o DSNZPARM SPRMRRF is set to DISABLE
o The CREATE TABLE statement is specified with the BUFFERPOOL
clause
o The CREATE TABLE statement defines an inline LOB column
PM78210 does not fix existing objects. A query, such as
the sample query below may be used to determine whether table
spaces containing tables with inline LOB columns have partitions
which are in basic row format (BRF). The sample query may not
take into account all customer environments and scenarios.
The query output should be analyzed to verify the table spaces
returned are in BRF and contain tables with inline LOB columns
If so, the table spaces must be dropped and recreated after
PM78210 has been applied.
SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION
FROM SYSIBM.SYSCOLUMNS COL,
SYSIBM.SYSTABLES TAB,
SYSIBM.SYSTABLEPART TPT
WHERE
(( COL.DATATYPEID = 404
OR COL.DATATYPEID = 408
OR COL.DATATYPEID = 412
OR COL.SOURCETYPEID = 404
OR COL.SOURCETYPEID = 408
OR COL.SOURCETYPEID = 412 )
AND COL.TBCREATOR = TAB.CREATOR
AND COL.TBNAME = TAB.NAME
AND TAB.DBNAME = TPT.DBNAME
AND TAB.TSNAME = TPT.TSNAME
AND COL.LENGTH > 4
AND TPT.FORMAT = ' '
AND TAB.TYPE <> 'V' );).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UK90728) SYS FMID(HDBAA10) REASON(ACTION) DATE(15090)
COMMENT
(PM78210 fixes CREATE TABLE to define implicit table spaces
in reordered row format(RRF) when all of the following
conditions are true:
o DSNZPARM SPRMRRF is set to DISABLE
o The CREATE TABLE statement is specified with the BUFFERPOOL
clause
o The CREATE TABLE statement defines an inline LOB column
This APAR does not fix existing objects. A query, such as
the sample query below may be used to determine whether table
spaces containing tables with inline LOB columns have partitions
which are in basic row format (BRF). Affected table spaces
must be dropped and recreated after this apar is applied.
SELECT TPT.DBNAME, TPT.TSNAME, TPT.PARTITION
FROM SYSIBM.SYSCOLUMNS COL,
SYSIBM.SYSTABLES TAB,
SYSIBM.SYSTABLEPART TPT
WHERE
( ( COL.DATATYPEID = 404
OR COL.DATATYPEID = 408
OR COL.DATATYPEID = 412
OR COL.SOURCETYPEID = 404
OR COL.SOURCETYPEID = 408
OR COL.SOURCETYPEID = 412 )
AND COL.TBCREATOR = TAB.CREATOR
AND COL.TBNAME = TAB.NAME
AND TAB.DBNAME = TPT.DBNAME
AND TAB.TSNAME = TPT.TSNAME
AND COL.LENGTH > 4
AND TPT.FORMAT = ' ' );).
UI26404 HOLD DATA END
UI26404 HOLD DATA START
++ HOLD(UI17690) SYS FMID(HDBAA10) REASON(ACTION) DATE(15090)
COMMENT
(***Action for PI16184:
See PI16184 APAR/PTF text for additional information about
why a REBIND is necessary.
PI16184 corrects a problem for SQL query acceleration where
there are errors in the DB2 modified query text that DB2
routes to an IBM DB2 Analytics Accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26404 HOLD DATA END
UI26406 HOLD DATA START
++ HOLD(UI19105) SYS FMID(HDBAA10) REASON(DOC) DATE(15090)
COMMENT
(*** Documentation for PI17163 ***
The following new reason code is added to the DB2 Codes manual.
00D34451
Explanation: A remote application connected to a DB2 server and
issued an SQL statement that contains a three-part name or alias
that refers to a table or view at a remote location. However,
the remote reference actually resolves to the local DB2 server
location. This situation can occur when the SQL statement
refers to a location alias but the package for the application
was bound before the location alias was defined.
System action: The SQL statement is rejected.
User response: Bind the application package at the server after
the location alias has been defined. For a data sharing group,
ensure that the location alias is defined on all members.
Problem determination: Use the -DISPLAY DDF command to
determine the location aliases for the server. Ensure that any
location alias references in the application exist at the
server when the package is bound.).
UI26406 HOLD DATA END
UI26665 HOLD DATA START
++ HOLD(UI26665) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15099)
COMMENT
(***Action for PI34271:
See PI34271 APAR/PTF text for additional information about
why a REBIND is necessary.
PI34271 corrects a problem that incorrect output could happen
for an SQL statement that satisfies all of the following
conditions:
1. It contains an UNION, EXCEPT or INTERSECT in the top level of
the statement.
2. A column in the select list contains a field procedure.
3. The field-decoding length is bigger than the column length.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26665 HOLD DATA END
UI26764 HOLD DATA START
++ HOLD(UI26764) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15105)
COMMENT
(***Action for PI29894:
See PI29894 APAR/PTF text for additional information about
why a REBIND is necessary.
PI29894 corrects a problem for SQL query acceleration where
there are errors when routed to an accelerator.
To make this fix effective for a static application
containing accelerated static SQL queries, the application
must be rebound after application of this PTF. Review the
PTF cover letter to determine which, if any, applications
could be affected by this change.).
UI26764 HOLD DATA END
UI26785 HOLD DATA START
++ HOLD(UI26785) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15105)
COMMENT
(***Action for PI32931:
See PI32931 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32931 corrects a problem of an ABEND04E RC00E70005 in
DSNXRDOU:P011 or DSNXRDEC:P005.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26785 HOLD DATA END
UI26847 HOLD DATA START
++ HOLD(UK77712) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15109)
COMMENT
(***Action for PM59265:
See PM59265 APAR/PTF text for additional information about
why a REBIND is necessary.
PM59265 corrects a problem of ABEND0C4 RC00000004 IN DSNXRBND
OFFSET189A
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26847 HOLD DATA END
UI26847 HOLD DATA START
++ HOLD(UK72345) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15109)
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.).
UI26847 HOLD DATA END
UI26847 HOLD DATA START
++ HOLD(UK66763) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15109)
COMMENT
(***Action for PM28718:
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.).
UI26847 HOLD DATA END
UI26847 HOLD DATA START
++ HOLD(UI26847) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15109)
COMMENT
(***Action for PI32550:
See PI32550 APAR/PTF text for additional information about
why a REBIND is necessary.
PI32550 corrects a problem for a query that contains a column
define with a field procedure(FIELDPROC).
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26847 HOLD DATA END
UI26847 HOLD DATA START
++ HOLD(UI22950) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15109)
COMMENT
(***Action for PI26285:
See PI26285 APAR/PTF text for additional information about
why a REBIND is necessary.
This apar corrects a problem that can cause DB2 to return an
incorrect result, more rows than expected. The problem can
occur for a query that includes a large indexable IN-List with
many NULL elements that DB2 does not process properly.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI26847 HOLD DATA END
UI27070 HOLD DATA START
++ HOLD(UI27070) SYS FMID(HDBAA10) REASON(ACTION) DATE(15116)
COMMENT
(The PTF for APAR PI33465 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.).
UI27070 HOLD DATA END
UI27120 HOLD DATA START
++ HOLD(UI27120) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15117)
COMMENT
(***Action for PI35773:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI35773 corrects a problem of ABEND04E RC00E70005 AT DSNXORGL
P110 when using a TEMPORAL table with RANGE LIST ACCESS TYPE.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI27120 HOLD DATA END
UI27208 HOLD DATA START
++ HOLD(UI27208) SYS FMID(HDBAA10) REASON(ACTION) DATE(15120)
COMMENT
(Run the following query:
SELECT SUBSTR(R.SCHEMA||'.'||R.NAME,1,36) TRIGGER
, SUBSTR(R.TBOWNER||'.'||R.TBNAME,1,36) TABLE
, SUBSTR(R.OWNER,1,10) OWNER
FROM SYSIBM.SYSTRIGGERS R
WHERE NOT EXISTS(SELECT 1 FROM SYSIBM.SYSTABAUTH TA
WHERE R.TBNAME = TA.TTNAME
AND R.TBOWNER = TA.TCREATOR
AND ( (R.OWNER = TA.GRANTEE AND
R.OWNERTYPE = TA.GRANTEETYPE)
OR
(TA.GRANTEETYPE = ' ' AND
TA.GRANTEE = 'PUBLIC')
)
AND TA.SELECTAUTH <> ' '
)
AND NOT EXISTS(SELECT 1 FROM SYSIBM.SYSUSERAUTH UA
WHERE ( (R.OWNERTYPE = UA.GRANTEETYPE AND
R.OWNER = UA.GRANTEE)
OR
(UA.GRANTEETYPE = ' ' AND
UA.GRANTEE = 'PUBLIC')
)
AND (UA.SYSADMAUTH <> ' ' OR
UA.DATAACCESSAUTH <> ' '
)
)
AND NOT EXISTS(SELECT 1 FROM SYSIBM.SYSDBAUTH DA
, SYSIBM.SYSTABLES T
WHERE R.TBNAME = T.NAME
AND R.TBOWNER = T.CREATOR
AND T.DBNAME = DA.NAME
AND ( (R.OWNERTYPE = DA.GRANTEETYPE AND
R.OWNER = DA.GRANTEE)
OR
(DA.GRANTEETYPE = ' ' AND
DA.GRANTEE = 'PUBLIC')
)
AND DA.DBADMAUTH <> ' '
)
AND XMLEXISTS(
'if (fn:matches($s,"REFERENCING +OLD ","i"))
then(1)
else
if (fn:matches($s,"REFERENCING +NEW ","i"))
then(1)
else
if (fn:matches($s,"REFERENCING +OLD_TABLE
","i"))
then(1)
else
if (fn:matches($s,"REFERENCING +NEW_TABLE
","i"))
then(1)
else ()'
PASSING XMLCAST(R.STATEMENT AS XML) as "s");
To make this fix effective, after application of this PTF,
for each qualified trigger from the above query, issue REBIND
TRIGGER PACKAGE command without the EXPLAIN(ONLY) specification
to its trigger package.).
UI27208 HOLD DATA END
UI27526 HOLD DATA START
++ HOLD(UI27526) SYS FMID(HDBAA10) REASON(ACTION) DATE(15131)
COMMENT
(DB2 is modified to make all new catalog indexes DB2-managed and
be created in the DB2 catalog data space. Applying this PTF does
not convert existing user-created catalog indexes. In DB2 10
enabling new-function mode and higher, these indexes must be
dropped and recreated for them to function correctly. Please
refer to APAR PI11316 for additional details.
This PTF modifies the DB2 10 premigration check-out job,
DSNTIJPM. If you maintain a customized copy of this job, then
after applying this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPM
- Delete all lines and copy in the DSNTIJPM member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 10, run the updated
customized job to check for conditions that might affect your
migration.
This PTF also modifies the DB2 11 premigration check-out job,
DSNTIJPB. If you maintain a customized copy of this job, then
after applying this PTF, you need to refresh it as follows:
- Edit your customized copy of DSNTIJPB
- Delete all lines and copy in the DSNTIJPB member from the
prefix.SDSNSAMP library
- Follow the directions in the job prolog to customize it for
your DB2
- If you are preparing to migrate to DB2 11, run the updated
customized job to check for conditions that might affect your
migration.).
UI27526 HOLD DATA END
UI27781 HOLD DATA START
++ HOLD(UI27781) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15139)
COMMENT
(***Action for PI39512:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI39512 corrects a problem that can occur when modifying a
temporal table via an UPDATE or DELETE operation when using
IN-List access.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI27781 HOLD DATA END
UI28096 HOLD DATA START
++ HOLD(UI28096) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15151)
COMMENT
(***Action for PI38584:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI38584 corrects the following problems in V10:
An ABEND0C7 RC00000000 at location DSNXGRDS DSNXRDTF OFFSET4192
can occur when executing a compiled SQL scalar function or
native SQL procedure containing a Datetime arithmetic expression
with a subtraction operator.
An unexpected SQLCODE -407 can be issued when executing an SQL
statement containing a Datetime arithmetic expression with a
subtraction operator.
Also, an incorrect result can be returned when executing an SQL
statement containing a basic predicate or BETWEEN 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.).
UI28096 HOLD DATA END
UI28096 HOLD DATA START
++ HOLD(UI28096) SYS FMID(HDBAA10) REASON(ACTION) DATE(15151)
COMMENT
(PI38584 corrects the following problems in V10:
An ABEND0C7 RC00000000 at location DSNXGRDS DSNXRDTF OFFSET4192
can occur when executing a compiled SQL scalar function or
native SQL procedure containing a Datetime arithmetic expression
with a subtraction operator.
An unexpected SQLCODE -407 can be issued when executing an SQL
statement containing a Datetime arithmetic expression with a
subtraction operator.
Also, an incorrect result can be returned when executing an SQL
statement containing a basic predicate or BETWEEN predicate.
To make the fix effective for a native SQL PL, ALTER PROCEDURE/
FUNCTION REGENERATE statement can be used to regenerate the SQL
PL.).
UI28096 HOLD DATA END
UI28171 HOLD DATA START
++ HOLD(UI28171) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15154)
COMMENT
(---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> This action is required for all DB2 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
---------------------------------------------------------------
************************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.).
UI28171 HOLD DATA END
UI28171 HOLD DATA START
++ HOLD(UK66001) SYS FMID(HDBAA10) REASON(ACTION) DATE(15154)
COMMENT
(---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> 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
***********************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.
----------------------------------------------------------------).
UI28171 HOLD DATA END
UI28171 HOLD DATA START
++ HOLD(UK61994) SYS FMID(HDBAA10) REASON(ACTION) DATE(15154)
COMMENT
(---------------------------------------------------------------
(1) Run installation job DSNTIJRT to rebind DBRM DSNAEXP
---------------------------------------------------------------
==> This action is required for all DB2 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
***********************************************************
* All DB2 V10 customers who use the DSNAEXP 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.DSNAEXP stored
procedure.).
UI28171 HOLD DATA END
UI28270 HOLD DATA START
++ HOLD(UI28270) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15156)
COMMENT
(***Action for PI30015:
A rebind is necessary for static applications to exercise
the code changes implemented by this APAR.
PI30015 corrects a problem of incorrect output may occur
for an SQL statement using multiple outer joins with RIGHT JOIN
or FULL OUTER 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.).
UI28270 HOLD DATA END
UI29293 HOLD DATA START
++ HOLD(UI19159) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15191)
COMMENT
(***Action for PI17479:
See PI17479 APAR/PTF text for additional information about
why a REBIND is necessary.
PI17479 corrects a problem that incorrect output could happen
for an SQL statement with a scalar-fullselect containing a table
expression or view with UNION ALL, when the SELECT item of the
scalar-fullselect is NOT NULL.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI29293 HOLD DATA END
UI29293 HOLD DATA START
++ HOLD(UI17994) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15191)
COMMENT
(***Action for PI13861:
See PI13861 APAR/PTF text for additional information about
why a REBIND is necessary.
PI13861 corrects a problem of ABEND04E RC00E70005 at location
DSNXGRDS DSNXSINE M103 or DSNXSZK M103 when a SELECT statement
references SYSIBM.SYSDUMMY1, SYSIBM.SYSDUMMYE, SYSIBM.SYSDUMMYA,
or SYSIBM.SYSDUMMU tables and contains OLAP specification.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI29293 HOLD DATA END
UI29293 HOLD DATA START
++ HOLD(UI17944) SYS FMID(HDBAA10) REASON(DB2BIND) DATE(15191)
COMMENT
(***Action for PI09729:
See PI09729 APAR/PTF text for additional information about
why a REBIND is necessary.
PI09729 corrects a problem that ABEND04E RC00E70005 at the
location DSNXGRDS DSNXRDEC P005, DSNXRSBC P041, DSNXRINT P026,
DSNXRTIM P016 or DSNXRDOU P011 could happen for an SQL statement
satisfying all of the following conditions:
1. It contains a table expression or view with UNION ALL.
2. It contains a predicate with a host variable or parameter
marker.
3. The predicate is on a column from the table expression or
view.
4. The columns of the predicate in the UNION branches have
different nullabilties.
To make this fix effective for a static application, it must be
rebound after application of this PTF. Review the PTF cover
letter to determine which, if any, applications could be
affected by this change.).
UI29293 HOLD DATA END
******************************
* HOLDDATA REASON ID SUMMARY *
******************************
REASON ID TOTALS
--------- ------
ACTION 72
DB2BIND 94
DOC 12
MULTSYS 6
______________________________
READY
END
| |
Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release level AI00 
AI00.covers.txt